yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] AnotherM1m:
are you running a fastboot rom downloaded from here? https://reindex-ot.github.io/

eea or global? do you have any module that modifies system?

There are users reporting error 20 after restoring imgs with magisk.

Just to be sure also try to boot into bootloader flash stock boot and then boot magisk patched one.

try also disabling all the module with the command mentioned to @paper88
[Nothing Phone 1] panni:
Seems like EEA (see screenshot).

No special fastboot rom running (all via official updater) since A12

Module list (hasn't changed for ages, except MGLRU disabler):

- ACC

- De-bloater (systemless)

- MGLRU disabler (by yourself)

- Denylist Unmount

- Fullscreen/Immersive Gestures (Q-T)

- Systemless Hosts

- Universal SafetyNet Fix 2.4.0-MOD_1.2 by kdrag0n/Displax

- Zygisk - LSPosed

Edit: MGLRU disabler disabled via magisk after restoring boot images, but not rebooted before trying offline updater.

I'd rather not to be honest. I've been able to completely ignore flashing stuff from fastboot since day 1 with this phone. With those "I bricked my device, help!" posts around here, I'd rather not risk a reinstall :X

Edit: Is MGLRU disabler the issue here? Might be obvious, but does it modify system? Sorry, tired :D
[Nothing Phone 1] AnotherM1m:
Which mglru disabler you have? It shouldn't prevent you from updating.

I have V3, i restored stock images with magisk, deactivated v3 module and then proceeded with ota offline updater after changing the time zone.
[Nothing Phone 1] panni:
Your latest one.

Flashing the current unpatched boot for 1.5.3 hotfix, then booting the magisk patched one worked - official OTA still errored out, though. Disabling MGLRU Disabler V3, reboot, then booting 1.5.3 magisk patched again worked. It's now updating (with official system OTA, not offline updater).

At least the system updater seems to detect changes from your module :O

Edit: still updating
[Nothing Phone 1] panni:
Yep, worked.

tl;dr, if you're getting error 20 or can't update to 1.5.4 (worked for me, might not actually be MGLRU Disabler's fault; rather a borked boot image):

- disable MGLRU Disabler V3

- adb reboot bootloader

- fastboot flash stock 1.5.3 hotfix boot

- fastboot boot patched 1.5.3 hotfix boot

- install OTA

- install magisk into inactive slot/OTA; reboot via magisk

profit.

Thanks @AnotherM1m as always!

Edit: No issues; root works; no MGLRU fixes necessary. They've actually listened. Baffling.
[Nothing Phone 1] BertProesmans:
It is not borked boot image.

It cannot be borked boot image.

It was borked boot image.

Pain. But something we all share ;D
[Nothing Phone 1] ferretmc:
Thank you so much for pointing out the solution.

For me it actually worked with my SpacewarEEA coming from 1.5.3 hotfix with magisk in this order:

set Timezone to China/Shanghai

disable MGLRU v3

adb reboot bootloader

fastboot flash boot <stock 1.5.3 fix boot>.img

boot to system

dial *#*#682#*#* and select the 1.5.4. OTA Image

...wait for it to finish (~10 mins)

adb reboot bootloader

fastboot boot <magisk_1.5.4>.img

install magisk through the app

cheers
[Nothing Phone 1] AnotherM1m:
nothing.tech/blogs/news/android-14-beta

Two things: Download server is really slow on eu west, ota_diff_20230428_222944_20230428_201717.zip the rollback file could be 154 full, i'll look into it tomorrow

Update: it's a rollback zip to 154 from UpsideDownCake, i don't know which nos version is this beta.

Upsate2: This beta has no Nothing OS version set. The easter egg's still A13's. Android's version set to UpsideDownCake.
[Nothing Phone 1] Chaotick:
Got 1.5.4 update in EU Poland :)
[Nothing Phone 1] BlackRazorPT:
I updated to 1.5.4 and my camera takes pictures with blur from a few meters away. I bought the smartphone and updated it right away, I don't know if it's the update or a hardware problem, anyone with the same problem?
[Nothing Phone 1] :
Everything is fine here.
[Nothing Phone 1] samflynn777:
Really appreciate what you guys are doing
[Nothing Phone 1] paper88:
Updated it few minutes ago to 1.5.4. Everything worked and i booted the patched img. Still cannot install magisk, I also flashed the img after but still not option in magisk. The same was on slot a currently, now im on slot b.

Any Ideas?
[Nothing Phone 1] AnotherM1m:
Flash 154 stock.

Redownload 1.5.4's magisk patched boot img from the first message in this thread.

Go into fastboot and boot that newly downloaded img.

Next direct install.
[Nothing Phone 1] caffeine01:
im trying to update from 1.5.3 to 1.5.3 hotfix so that i can then eventually install 1.5.4

but in the ota updater it gives me an engine error "DOWNLOAD_STATE_INITIALISATION_ERROR/20"

and im stumped because im using the stock 1.5.3 boot image
[Nothing Phone 1] AnotherM1m:
Can you post a screenshot of offline ota updater? Were you rooted before? By using you mean you flashed it to boot_a or boot?
[Nothing Phone 1] caffeine01:
I did fastboot flash boot <stock_boot.img> and the slot was on a, do i need to flash both slots? thats probably it ill do that now
[Nothing Phone 1] caffeine01:
i flashed both slots and thn booted into a as b was giving me bootloops, still not working
[Nothing Phone 1] Who-Lep:
My original device was the global version. After flashing these fastboot roms, it was converted to EEA. I had to re-convert mine to the global version with no root and locked bootloader in order to take ota's automatically and manually.
[Nothing Phone 1] AnotherM1m:
Are you on a fastboot rom?

What about flashing stock 153 with the command

fastboot flash boot *153 stock boot img*

And then

fastboot boot *153 patched boot img*

Use the images from the first message of this thread.
[Nothing Phone 1] caffeine01:
that did nothing

I fail to see how this is meant to do anything? I already flashed the stock boot and said that it wasnt working.
[Nothing Phone 1] AnotherM1m:
Are you using a fastboot rom?

I asked you to follow that procedure because one of the reason for error 20 to show is restoring an incorrect or an unknowingly corrupted boot img.

Since 153 has two versions people used the wrong ones on their devices (hotfix on non hotfix etc).

Error 20 is caused by partitions not stock (and fastboot roms seems to create problems).

Have you tried sideloading from recovery?
[Nothing Phone 1] caffeine01:
i did install sysrw which had me flash a super partition, ill try sideloading though. edit: sideloading didnt work

also i dont see why my rom would be a fastboot one unless thats normal.
[Nothing Phone 1] Ostry10:
I have similar problem. Im on 1.5.2 and I have tried to flash new wersions. I restored oryginal boot.img and Im still getting ERROR20.

Also tried to adb sideload and i have got this:

E: Failed to unmount /mnt/product/nt_log

Any help?
[Nothing Phone 1] AnotherM1m:
You have to disable any modules that modify /system or any other partition and restore them before updating.

fastboot roms are the ones linked around as full zips to restore/unbrick phones

Ota zips are incremental, you have to go one version after the other, you cannot try flashing multiple ones. You have to start from 153.

Do you have any module that modifies system or other partitions?

Are you sure the boot img restored is ok?
[Nothing Phone 1] caffeine01:
the boot image restore is okay, but the sysrw thing i applied isnt a magisk module and i dont have any magisk modules that edit the partitions. but sysrw does modify partitions and i dont have a backup (i think all it does is enable read/write on them) and so would i have to manually go through each partition and change it to read only and then re flash? i dont have any non read write backups. also i dont think that im using a fastboot rom, is there any way to check?
[Nothing Phone 1] Ostry10:
I tried to start from 1.5.3, disabled all modules and im sure i have restored oryginal boot.img
[Nothing Phone 1] AnotherM1m:
I don't know sysrw in particular but i saw there's also sysro to reset the partition to read only.

Do ypu know which modifications have you made to system? Have you modified other partitions?

You could get your fw full zip, get payload bin, extract it and then flash stock system and the other partitions you modified.
[Nothing Phone 1] AnotherM1m:
Go to fastboot, flash stock 152 boot and then boot 152 patched boot img to be sure with the commands mentioned above.

Redownload 153 incremental from 152 from the first message in the thread.

Error 20 is caused by non stock partitions, have you ever flashed a fastboot rom for unbrick to your phone?
[Nothing Phone 1] Ostry10:
@AnotherM1m

Yes, i bricked my phone and then unbricked it by lahaina_FastbootROM_v1.5.2 (installed on both partitions).
[Nothing Phone 1] AnotherM1m:
Were you on eea or global device? Is it now seen as eea or global?

Please test again to flash stock and boot magisk patched as mentioned above.

There are reports of people not being able to update their phones after installing fastboot roms.

For now the cause has not been found.

I saw some discrepancies with the vendor partition for example but i don't own a second phone to test things and verify what should be done.

@ot_inc help? Do you know anything about this?
[Nothing Phone 1] Ostry10:
EEA and still seen as EEA.

When im trying to update Via adb sideload im getting error:

E: Failed to unmount /mnt/product/nt_log

Maybe because of that i can update?
[Nothing Phone 1] AnotherM1m:
That error is also something that i always had trying to update with sideload.

If you can boot a patched boot img maybe we can find the reason for error 20, but it can be complex, are you in?

It can help a lot of people, using a terminal is required, but it shouldn't be too hard.

Termux or bash from adb debugging will be used.
[Nothing Phone 1] Ostry10:
Yeas, I can patch boot.img.
[Nothing Phone 1] AnotherM1m:
Ok firstly boot the patched boot img

open a terminal emulator, and send the "su" command to gain root priviledges.

now

cd /mnt/product/nt_log/ota_log/

You are now in the log folder for ota updates.

Do

ls

To have a list of files in the folder.

The files are multiple tar.gz files for older ota attempt but there should be one folder (one value not ending with tar.gz) with a modern date

Do

cd *name of the folder*

to open the folder, ls command should show you the structure of the folder and that there should be an ota.txt file

Now to copy that txt file to the root of the sdcard

cp ota.txt /sdcard/

Now on the root of the sdcard of the phone you should have the ota.txt log, send it to me privately through xda messages.
[Nothing Phone 1] RZ(One):
Could you share how you get to dump boot.img of any update? I'm seriously interested by this
[Nothing Phone 1] AnotherM1m:
I open a terminal emulator, send "su" command to gain root priviledges, then

cp /dev/block/by-name/boot(_a OR _b depending on the active slot) /sdcard/boot.img

For the stock boot img i go to /data with cd command then use stat to get the latest created magisk_backup_hash, open the folder and search it there.
[Nothing Phone 1] RZ(One):
How are you supposed to get su privilege before dumping the boot?
[Nothing Phone 1] AnotherM1m:
I always dumped after root, but i know the edl tool can be put in read mode to dump your phone or maybe set to only dump one partition.
[Nothing Phone 1] RZ(One):
well for example, how did you get 1.5.4 boot.img? assuming we don't have root support on the version
[Nothing Phone 1] AnotherM1m:
Updated from .3.hotfix to .4 with the ota magisk option so i booted 1.5.4 already rooted.

Otherwise i would have used edl tool.
[Nothing Phone 1] Ostry10:
I wrote to you privately.
[Nothing Phone 1] AnotherM1m:
Still searching for a solution with @Ostry10

The error is caused by uefisecapp sha256 hash not corresponding to the expected one.

Also thanks to the user we have the ota zip to 154 from 152! I've updated the main page

UPDATED THE REASON
[Nothing Phone 1] AnotherM1m:
Hello!

For everyone having problems updating with offline ota updater because of error 20, I've made a script that easily copies logs from the phone into the sdcard.

GitHub - LukeSkyD/NP1-OtaTxtExtractor: Bash script that searches for ota.txt and copies it to /sdcard, only tested on NP1

Bash script that searches for ota.txt and copies it to /sdcard, only tested on NP1 - LukeSkyD/NP1-OtaTxtExtractor

github.com

You need root to run this script.

The logs can be then copied here to find out why things are not working.

@Ostry10
[Nothing Phone 1] AnotherM1m:
Which sw version are you on?
[Nothing Phone 1] caffeine01:
1.5.3, trying to install hotfix ota
[Nothing Phone 1] AnotherM1m:
153 has bluetooth borked, 152 uefisecapp.

Hope we can alert reindex and people on this forum about this issue.
[Nothing Phone 1] caffeine01:
is there any way i can obtain a stock 1.5.3 bluetooth.img ?
[Nothing Phone 1] AnotherM1m:
Full zip 1.5.3

Or someone still on 1.5.3 could dump that image.
[Nothing Phone 1] AnotherM1m:
Try deleting play services data (i don't think it will work but trying doesn't cost anything)
[Nothing Phone 1] caffeine01:
is there a full 1.5.3 zip anywhere that you know of?
[Nothing Phone 1] AnotherM1m:
I haven't found one yet.
[Nothing Phone 1] caffeine01:
is virtualising the nothing phone an option? like, get the firmware installed in a virtual environment and dump all of the images to release a full firmware zip? could be automated as well so that whenever a new update is released it automatically installs, dumps and then uploads it
[Nothing Phone 1] AnotherM1m:
I thought about it but only found how to virtualize pixel phones, not nothing phone.

Never looked into this context if you can find anything please let us know!

It could be a great idea
[Nothing Phone 1] caffeine01:
I would need to virtualise the entire phones hardware or create stubs for it to cover the firmwares drivers and run it in an arm vm. Not impossible but definitely a huge feat.
[Nothing Phone 1] AnotherM1m:
Asking to nothing support for full zips could be easier to do... If they'll ever answer back
[Nothing Phone 1] svaethier:
So I've been getting the error 20 thing when trying to update to android 14 beta for the nothing phone and got the ota txt file so here's what it shows for me:

Spoiler content hidden.
[Nothing Phone 1] AnotherM1m:
Uefisecapp partition busted.

Have you flashed a fastboot rom?

EDIT: eea or global device? You are 154 right? Because i am and i could try dumping my uefisecapp since we both on 154
[Nothing Phone 1] svaethier:
Yes I am on 154 fastboot rom currently
[Nothing Phone 1] AnotherM1m:
I wrote to you privately

EDIT: user reported flashing my uefisecapp and being able to update! It's the right direction to fix fastboot roms not updating.

Now we need uefisecapp for 152 and bluetooth (and maybe other partitions) for 153
[Nothing Phone 1] caffeine01:
I thought about it and decided to look into it and found that apparently you can extract .img files from payload.bin, maybe we can do that for borked images.
[Nothing Phone 1] AnotherM1m:
We can extract good images from full zips.

There are tools for incremental otas zips but they don't produce good images.

I tried going from 1.1.7 (the latest know full zip) to 1.1.8 and then 1.5.2 but the uefisecapp image created with the tool was only 120KB while from 1.5 they should be 2.0MB

Also the images extracted from incrementals are not signed which means a different hash to the one needed.

We need full 152 if we want to restore partitions or full 154 if we want to directly update and skip all the hash checks.
[Nothing Phone 1] Sluzy:
Hello, I can't install Magisk on my phone.

I recently updated to 1.5.4 and patched the Magisk modified boot.img, and it seems to have patched the boot.img because I have an aplication (LiveBoot) that shows a live log when the device is turning on, before it shows the lockscreen, and that app only works with root, but for some reason when I open the Magisk app after booting with the modified boot.img it doesn't show it beeing installed and doesn't show the option to install it.

Can someone help me?

View attachment 5918925

Magisk shows like this

View attachment 5918927LSPosed shows like this

View attachment 5918931

And my apps detect root
[Nothing Phone 1] HermitDash:
bootloader ~> Flash patched magisk boot image ~> Reboot
[Nothing Phone 1] Sluzy:
Yes, I've done that, but but it stays on that state of semi flashed
[Nothing Phone 1] pyry666:
Always boot (dont flash it) patched image, Then direct install
[Nothing Phone 1] Sluzy:
I've boot the patched image but the direct install option doesn't show, its like in the screenshot of Magisk
[Nothing Phone 1] Ostry10:
@Sluzy Try to reinstall magisk app.
[Nothing Phone 1] Sluzy:
Tried that too, didn't work
[Nothing Phone 1] caffeine01:
well since .img files are pretty much just archives (not too dissimilar to .zip) couldnt you just get a working image from a previous version, then get the ota payload images leading up to the version you want and just extract them all and copy over the contents of the OTA image and overwrite? like, create a folder, extract all the files from a good bluetooth.img from a previous version into that folder, then do the same with all of the versions up to the one you are on/need.
[Nothing Phone 1] AnotherM1m:
I could be too nooby to do this.

Im starting from the full images from 1.1.7 then applying the updates with payload dumper.

But what payload dumper is extracting are not the correct images because of: 1) wrong partitions dimensions, 2) the images are not signed so the hash check which produce the error 20 will still fail.

Do you know any other way?
[Nothing Phone 1] gwolfu:
usually EU versions take bit more time because validation

this is same for any OEM
[Nothing Phone 1] UserNamist:
That hasn't been true for the previous updates though
[Nothing Phone 1] gwolfu:
Well am having same experience everywhere

Sometimes it can take a day or two, other is fast same day for everyone
[Nothing Phone 1] plasmotosis:
I got the global version (soacewars) and in Australia. Tried downloading the zip and using the dialer to install it. But it can't detect any update files. And when I browse and select it manually, the dialer just exits and nothing happens.

What's going on there?
[Nothing Phone 1] neilphetamine:
Create a folder named “ota” (without the quotes) at the root of the internal storage of your phone. Then copy the update ZIP file to that folder. Then try again with dialer.
[Nothing Phone 1] plasmotosis:
Awesome. That seems to have worked. It's updating now. Wish me luck 🤣🤞
[Nothing Phone 1] plasmotosis:
Update is complete. Notification background is now no longer black but more a light blackish colour but I already knew that was gonna happen from all the reports.

But now I also got some random word on the notification menu when I fully pull it down lol

12 (SKQ1.211230.001)

Any idea what that is?
[Nothing Phone 1] :
That's the build number
[Nothing Phone 1] neilphetamine:
It's normal if you enable "Developer Options"
[Nothing Phone 1] Wabbajackw:
Any risk to flash global stock rom on an european device?
[Nothing Phone 1] Gerard03:
I have some questions about unlocking bootloader and rooting it.

1-Do I loose the warranty by doing this?

2-Let say it bricks and it don't work anymore does warranty cover this?

3-I read it can be problems with bank apps by rooting it but you can hide magisk so it's not detected, does hiding really makes all apps work perfectly?

4-Will be able to update via OTA if I root it?

5-Do I loose my data if I do this?
[Nothing Phone 1] panni:
1: depends on the country. In the EU you don't

2: depends, you might be charged for the repair

3: again, depends. I got a very hard to get working TAN app from the DKB Bank to work and I'll happily link you to the tutorial. It's far from guaranteed, though, as root detection mechanisms are stupidly thorough now

4: yes. Restore original boot img from magisk manager, install the OTA, don't reboot, install magisk into the inactive slot, reboot

5: if you don't have an unlocked bootloader then yes, you lose all your data.

Hope this helps.
[Nothing Phone 1] Gerard03:
Ok thanks for all the info. Do you have it unlocked? (I suppose you have it if you know all this stuff) What benefits I get from doing this? Like what can I do that cannot be done without root
[Nothing Phone 1] panni:
There's no immediate benefits. I always unlock a new phone to have the option to root, while the phone is still virgin, so I don't have to reinstall everything once I decide to root.

I've been using a rooted phone forever, now mainly for charging control using ACC (limits how much the phone charges among other stuff, to keep the battery decent. The last phones I've done this with have basically 90% of day1 battery life after 3 years.).

And I use Nowakelock to limit the amount of times certain apps can wake the device (there are stupid ones that I use and need).

For my previous phone, the POCO F2 Pro, I needed root to use CustoMIUIzer to adjust some stupid UI decisions from Xiaomi.

Also, as stupid as it sounds, I like the cat and mouse game between Google and the other companies that try to prevent root, and the rooting scene. It makes no sense, as the average root user is probably more security savvy than the ones they supposedly protect by keeping root users from using their software.

Edit: ah, another benefit is being able to use backup tools that back up all your apps including the data, like SwiftBackup
[Nothing Phone 1] Gerard03:
Maybe I do like you and unlock so if I want to root it I can without restoring.

Why does apps like the ones for bank stop working because of root or unlocking bootloader? Or both?
[Nothing Phone 1] panni:
As far as my experience goes, they only dislike root, not an unlocked bootloader. Not sure if Netflix and other widevine L1 DRM apps still work. I use a magisk module to circumvent that, but I don't use my phone as a streaming device generally.

Try it. You can always relock your bootloader if something turns out to not work after unlocking.
[Nothing Phone 1] Gerard03:
Nice thanks for your time and have a great day.
[Nothing Phone 1] jkebwdn:
My device is on 1.1.3, I want to root but can’t find the 1.1.3 OTA online to extract the boot.img for patching. Is there a way I can get the OTA off my device for extracting boot?
[Nothing Phone 1] mystery007:
I think is possible to use the boot.img of 1.1.2
[Nothing Phone 1] dexlemaffo:
The local OTA update as it was described in a post here.

set Timezone to China/Shanghai

disable MGLRU v3

adb reboot bootloader

fastboot flash boot <stock 1.5.3 fix boot>.img

boot to system

dial *#*#682#*#* and select the 1.5.4. OTA Image

...wait for it to finish (~10 mins)

adb reboot bootloader

fastboot boot <magisk_1.5.4>.img

install magisk through the app
[Nothing Phone 1] AnotherM1m:
Thanks but I don't need the local update procedure.

I need the full imgs of a fw we only have incremental zips of.

Reindex suggested GSIs.
[Nothing Phone 1] dexlemaffo:
Full images aren't available online unlike what Google does for its Pixel phones. So had to manage with the guide I quoted to update my sister's NP1 that she uses as a back up.
[Nothing Phone 1] caffeine01:
I also tried using that python payload dumper thing and it didnt work.

Unfortunately i cant think of another way right now but ill keep thinking lol
[Nothing Phone 1] Sonalk:
I can't dump the boot file with payload_dumper. it've worked perfectly before. Is it something to do with the OTA file?

Tried the pre-patched img file but the phone couldnt boot.
[Nothing Phone 1] AnotherM1m:
Have you tried to extract a boot image from an ota? It seems like they (images from payload dumper) are not signed (at least that's what i've read).

What slot is active? What file is not working? Is it from this thread?
[Nothing Phone 1] Sonalk:
I tried the files from Nothing phone Update Tracker here on XDA, both the regular and the incremental version. I even tried different forks of payload dumper, Python variant, one written in go and a GUI version. Received different error from all, i made a reddit post before with all the logs.