yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] bariz143:
Uodate failed whit this one. Error 20
[Nothing Phone 1] HofaTheRipper:
Got it!!! (extracted the stock boot in EDL):

Stock 1.5.2 boot:

96 MB file on MEGA

mega.nz

Magisk 1.5.2 boot:

96 MB file on MEGA

mega.nz
[Nothing Phone 1] HomeSnake00:
Will you still get OTA update if you side loaded the 1.5.1 beta?
[Nothing Phone 1] HofaTheRipper:
1.5.2 Incremental over 1.1.8:

https://android.googleapis.com/packages/ota-api/package/ae6c43b3022f2d554bd7a15e3dffb363e6b89000.zip
[Nothing Phone 1] Pho3nX:
Thanks for all your shared links/files mate :)

Thread updated !
[Nothing Phone 1] citrus13:
I am on spaceware -S1.1 xxxxxxxEEAi get error 20 and I'm on 1.1.8

No go for me
[Nothing Phone 1] adambera1987:
Same here, I'm on official 1.1.8 and getting error 20 when trying local update, will wait for ota.
[Nothing Phone 1] citrus13:
Yes. I think that may be best. I believe this should work but it's the same error I am getting. 😟
[Nothing Phone 1] Pho3nX:
Are you rooted ?

I have installed from the official push notification in my case and was on 1.5.1 Beta 2 with Hotfix and rooted.

If you are rooted you must go in Magisk > Uninstall > Restore Original Image. Only after you can download/update, if you don't restore image, you encounter a error.

If you are not rooted

The most simple (because the stable 1.5 is out) is to wait the Full ROM 1.5.2 package, you don't have Error 20 from Full ROM, only from OTA (verify check signature is different)
[Nothing Phone 1] Echse27:
Ah ok, so we have to wait for official release for none beta testers?

I got the same error 20 when i test to upgrade via offline updater and the linked file for 1.1.8.
[Nothing Phone 1] Ziomek64:
1.5.2 stable gives me error 20 when updating from 1.1.8. EEA
[Nothing Phone 1] Echse27:
look @ post #563
[Nothing Phone 1] Ziomek64:
This thread is at 540 only though. Which one are you reffering to
[Nothing Phone 1] Echse27:
Sorry i mean #536
[Nothing Phone 1] froz3nbug:
This should answer a lot of y'all queries regarding the availability of OTA update after sideloading.View attachment 5838947
[Nothing Phone 1] AnotherM1m:
I was on global 1.1.8, restored stock images via magisk, rebooted into recovery, adb sideloaded the update, returned

Error applying update: 45 (ErrorCode: kUnsupportedMinorPayloadVersion)

Rebooted into fastboot bootloader, booted 1.1.8 magisk patched and im back with the older sw version

I used the OTA in the thread does anyone know where i did wrong?

EDIT:

Restored images again, trying the procedure from the dialer this time.

When it will reboot automatically i'll try to push vol down to boot into fastboot and then boot the magisk patched boot and see how it goes

EDIT2:

"Everything" went fine i had issues with sideloading, doing the procedure from the dialer fixed everything

@Pho3nX the patched 1.5.2 boot img is not really patched, i lost root while booting that img, here's mine patched 1.5.2

magisk_patched-25200_TrVLh.img

drive.google.com
[Nothing Phone 1] TheHappyBuddhist:
He meant #536. Just a couple of posts above - the OP has explained it there.
[Nothing Phone 1] TheHappyBuddhist:
It is always better to patch the boot image ourselves. I have seen many users having trouble when using patched images from others. I guess there's some issues with device signature (maybe)? Just download the stock boot image, patch it from Magisk and flashing it is the way to go.
[Nothing Phone 1] HofaTheRipper:
Its better to patch it yourself, only boot the patched image and then do a direct slot install in magisk.... so the stock boot gets backed up by magisk and you can always restore it within magisk and have no problems with error 20 or so.
[Nothing Phone 1] luiwii:
Can you install the complete stable over beta 2, instead of the incremental one, by doing a factory reset?
[Nothing Phone 1] AnotherM1m:
@HofaTheRipper How did you find the otas zip?

Is there another 1.2GB 1.5.2 ota?

I'm seeing a lot of people with eea version having problems updating from 1.1.8 and in /META-INF/com/android/metadata there are these lines

View attachment 5839251

post-build looks ok, this fw unifies global and eea but pre-build it does not since it seems that SpacewarEEA is not checked and thus not accepted

It's my first time digging through these files so i don't know if i'm understanding correctly but could it be that there is still another ota zip somewhere for eea devices?

EDIT:

I'm sure this is the problem: in beta zips pre-build property has both spacewar and spacewarEEA which is missing here.

The 1.1.8 -> 1.5.2 zip is only for global devices.
[Nothing Phone 1] citrus13:
Hi. No I'm not rooted. Took 1.1.8 OTA. Is it possible to use a VPN for another country to then take the update or is this OTA update only for beta testers ATM?? Thank u

.
[Nothing Phone 1] AnotherM1m:
This update is open for everyone.

The file uploaded to this thread only works with global devices, eea devices are not checked so this is why many users are failing with error 20.

You could try with a VPN but maybe there is still no EEA OTA from 1.1.8

But trying takes seconds if you want to.
[Nothing Phone 1] HofaTheRipper:
i captured the incremental from 1.5.1 myself and found the 1.1.8 update in the global telegram group....

it could be, that the 1.1.8 update requires a global rom. 1.5.1 was unified so the update should work fine for both.

i have not found another update file.
[Nothing Phone 1] AnotherM1m:
1.5.1 is unified, you can check metadata file yourself and see that both devices are accepted

But 1.1.8 -> 1.5.2 ota is not.

Guess we have to wait for someone to logcat their phone and ota request to find the google url for 1.1.8 -> 1.5.2 eea

Thanks for your answer
[Nothing Phone 1] HofaTheRipper:
guess you have to wait for 1.5.2 release.... ATM its beta testers exclusive 😉
[Nothing Phone 1] citrus13:
I'm trying now. Is there a specific country that I could try?
[Nothing Phone 1] AnotherM1m:
India's got 1.1.8 to 1.5.2 if i remember correctly, also ukraine and czech republic, i don't know about others tho

(im not really fully sure about the countries, try a bunch of them if you can)
[Nothing Phone 1] citrus13:
View attachment 5839305

I tried many many countries using surfshark and when I try Mumbai India. I get this. All other countries that I tried showed as I'm updated on Android 12
[Nothing Phone 1] AnotherM1m:
So for now we have nothing for eea devices

if i find something i'll post here
[Nothing Phone 1] citrus13:
Awesome. Thank u
[Nothing Phone 1] Tan5en5:
Hi everyone,

I tried to update my phone with ota package from 1.1.7 Hotfix to 1.1.8 with dialer and sideload methods but i have an error :

Does anyone know why this error occured and how to fix this ?

This is the first time I've encountered this problem, I've never had a problem updating before with dialer method.

Thanks guys :)
[Nothing Phone 1] Pho3nX:
It's better to all people encounter Error 20 to simply wait the Full ROM 1.5.2 Stable officially. For sure a Full ROM package will be available, especially because it's the first build A13.
[Nothing Phone 1] Skrookey:
Is it possible somehow to downgrade to 1.1.7 and install the beta updates step by step?
[Nothing Phone 1] Pho3nX:
https://xdaforums.com/t/nothing-pho...ng-os-update-16-02-2023.4464039/post-87760837

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THE LINK ABOVE.

THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)

GOOD CONTINUATION TO ALL
[Nothing Phone 1] samy1111:
Update von Version 1.18 auf 1.52 Fehler 20
[Nothing Phone 1] aKay67:
View attachment 5842545

Story on Instagram
[Nothing Phone 1] FadedSaint90:
Hopefully today the official announcement will happen
[Nothing Phone 1] AnotherM1m:
getprop ro.product.system.name

After the 1.5.2 update returns

qssi

is there any other way to check if someone's on spacewar or spacewareea?
[Nothing Phone 1] aKay67:
Arrived in germany

View attachment 5843047
[Nothing Phone 1] Chaotick:
Android 13 update showed up on my NP1 in Poland. Cheers!
[Nothing Phone 1] HofaTheRipper:
getprop ro.product.name without system
[Nothing Phone 1] froz3nbug:
If anyone's updated their phone from A12 to A13 stable, can you tell what's the software version of the update?? is it 1.5 or 1.5.2??
[Nothing Phone 1] Chaotick:
It's Nothing OS 1.5.2
[Nothing Phone 1] panni:
Dirty flash over 1.1.8 successful.

Does anyone see "HD" above their mobile network icons all the time as well? It was LTE+/4G before.

Edit: Seems like that's VoLTE
[Nothing Phone 1] paper88:
Im on stable A12 1.1.8 (no beta) and got the update today, am I right that if the Version from today is also 1.5.2 i just patch the boot.img from above? So it should be the same as the user which was on beta?
[Nothing Phone 1] Mareckyyy:
EEA update from 1.1.8 no betaView attachment 5843199
[Nothing Phone 1] Giunta._:
hi guys i'm on 1.1.8 EEA rooted, today i've recived the A13 update but when i try to install it from settings it always fail. what i had to do to fix it?

I've already flashed the stock boot.img and removed magisk
[Nothing Phone 1] Ostry10:
Same here bro. Im in contact with support team, i've been talking through chat with them, now im waiting for answer on email.
[Nothing Phone 1] paper88:
I installed A13 and wanted to root again, i patched the boot img and flashed it over "fastboot flash boot file.img" but if i start the phone I just have the option "choose file and patch" in magisk and i cannot directly install, someone knows why?
[Nothing Phone 1] pyry666:
Why would you need to direct install if you already flashed patched.img? Its always safer just fasboot boot patched.img, then direct install..
[Nothing Phone 1] paper88:
I did this first and I couldn't do direct install then I tried the flash boot method and it also didnt workedView attachment 5843475
[Nothing Phone 1] pyry666:
Where did you get the boot.img from? (1.5.2). Maybe try dl it again and patch again. I managed to do that with out issues and with same magisk version 25.2 stable
[Nothing Phone 1] fmotta61:
Same here
[Nothing Phone 1] VaSU#:
Go to magisk manager and press uninstall

Click restore boot.img

Go to ota and install update

Let it finish the procedure until you get the press restart button

Go to magisk and patch boot.img of the inactive partition

Reboot.

This should give you root access and finish ota.
[Nothing Phone 1] fmotta61:
Solved by rebooting to bootloader, flashed stock boot image, rebooted.

Installed OTA.

Reboot to bootloader.

fastboot boot magiskpatched.img (or what is called). Attention: boot not flash.

Reboot and start Magisk, direct installation, reboot and voila.

Other method do not work because presumably you flashed magiskpatched.img directly and due to this Magisk cannot restore automatically boot image.
[Nothing Phone 1] VAN/:
Do you have the latest stock boot image?
[Nothing Phone 1] :
You can boot the previous version of 1.1.0. but don't flash!
[Nothing Phone 1] fmotta61:
Confirmed
[Nothing Phone 1] panni:
This worked flawlessly, thank you. No need to use adb/fastboot or flash anything.
[Nothing Phone 1] Sib64:
UPDATE - 02/08/2022

Go to the OP for the changelog (y)

European Nothing OS 1.1.2 - 02/08/2022 - NEW
[Nothing Phone 1] loubeat87:
Hey guys! Great post!

I'm in trouble right now with the Nothing. The phone is fantastic but I have some problems to configure Android Auto and then, testing with developer options both in the phone and AA, I accepted to install "Dynamic Updates" when it ended, it bootlooped in the same menu I show in the picture and I can't start. I noticed that I need to install boot image again but it will be great if someone explain me how to install.

It was all my fault, but I need help to fix it.

Thanks,View attachment 5676611
[Nothing Phone 1] Sib64:
OP UPDATED 04-08-2022

With NOTHING OS FULL 1.1.2 Global & EAA

and

Nothing Boot Files from OS Full 1.1.2 Global & EAA
[Nothing Phone 1] QTeknology:
EDL Mode is available without root or unlock the bootloader

from fastboot

fastboot reboot-edl

from adb

adb reboot edl
[Nothing Phone 1] yquitumadbro:
Did you end up fixing this? I am trying to figure out how to do the same thing. My phone is stuck on that screen and nothing is getting it to come out of that screen I caan't figure out how to flash the stock boot.img either because when I try to it gives me an error. It says this View attachment 5677383
[Nothing Phone 1] QTeknology:
fastboot flash boot boot.img
[Nothing Phone 1] Sib64:
OP UPDATED 04-08-2022

Nothing OS Files with Global & EAA FULL versions 1.1.2

And a new tuto

Unbricking Nothing phone 1: Flash Stock Firmware with Fastboot
[Nothing Phone 1] pankspoo:
Can you please add automated.bat file which will flash all files automatically without typing everything
[Nothing Phone 1] Darkitz:
I have bricked my phone (i have the European version) and sadly those links in here are for OTA updates and full Firmwares.

Also: i have tried everything i have found, currently my phone is unbootable. I wonder if i can downgrade somehow so i can apply the OTA updates via the recovery and sideloading

Edit: oh yeah, i forgot to mention what the characteristics of my brick are, whenever i try to flash system.img onto the system partition i only get parition system_a not found, similar thing for vendor, system_ext, odm and product

Imma just wait till theres another update and imma flash it trough fastbootd.

Tbh all symptoms feel like i have some update that nobody else has?

The timestamp is different from every update i can find.
[Nothing Phone 1] hemanth.k:
Exactly this is the issue i came across in my time too.

Not a single timestamp matched the ones avilable on the internet.

I had a replacement done and hence couldnt go further to try it out.
[Nothing Phone 1] Darkitz:
i think part of the issue is that we cant flash those paritions.

It probably doesnt boot because we effectively mixed a system-parition (the one 'mystery version' we have) with boot and other stuff from another update (the one we flashed from the full packages).

Resulting in a version mismatch with those paritions.

Any rooted person that can get me partition table?
[Nothing Phone 1] fmotta61:
I was bricked too. Tried flashing with same errors.

Then I changed active partition from b to a. Nothing different.

But when I switched back to partition b it started again.

Don't know if this can help you too.

Anyway I didn't find a way to relock bootloader without bricking it.
[Nothing Phone 1] Darkitz:
Can confirm switching to slot b (using fastboot -ab) and then running all the commands to flash the images works perfectly. Big thanks
[Nothing Phone 1] paper88:
I downloaded it from this post site 1, patched already twice with 2 diffrent downloads. I was not on beta. Can you maybe attach your stock img here and i'll try to patch it
[Nothing Phone 1] pyry666:
https://xdaforums.com/t/rom-restore...t-rom-full-rom-boot-img-qfil-rom-edl.4523185/ I used one from that link from op. NonPatched one
[Nothing Phone 1] paper88:
Also not working :(
[Nothing Phone 1] paper88:
But i just saw I got my IOS Emoji back so it worked but after a restart it will go away
[Nothing Phone 1] pyry666:
Hmm, try to uninstall magisk completely. Modules and everything, maybe it works after that. I am clueless what could be wrong if that dont work
[Nothing Phone 1] paper88:
Superuser and modules are greyed out I cannot install or uninstall anything 😭
[Nothing Phone 1] pyry666:
It COULD be that some module was the culprit from the start. Dunno how you could remove them without wiping. Maybe with adb. Someone with more knowledge sure could help you better. I hope you get that sorted out

Edit: you could try flashing patched.img and then boot to safe mode and see if that allows you to remove modules and unistall magisk. No guarantees though
[Nothing Phone 1] paper88:
Alright I will check, thanks for help!
[Nothing Phone 1] dedors:
After updating with OTA, I'm on Spacewar-T1.5-230213-2131-EEA

Does that mean the builds aren't unified after all?

Still, rooting with the boot image from OT was flawless (fastboot boot patched.img, then direct install)
[Nothing Phone 1] trax69:
this boot file worked, thank you
[Nothing Phone 1] Zafael:
Anyone have full system 1.5.2 zip?

Not possible to upgrade due to wrong minor version (1.1.7 hotfix to beta) and wrong preupdate version (all other zip versions 117 to 118 or to 152) as for now system is identified as 1.1.7 hotfix 1669706700 fingerprint but wrong minor version.

In recovery mode there is warning about failed previous update so full os image should help
[Nothing Phone 1] AnotherM1m:
They are not (for now)

Here's the incremental for EEA from 1.1.8:

https://android.googleapis.com/packages/ota-api/package/6718db370773ad0191b970df545f54c4163a014e.zip

Here's the incremental for global from 1.1.8:

https://android.googleapis.com/packages/ota-api/package/ae6c43b3022f2d554bd7a15e3dffb363e6b89000.zip

EDIT:

I've looked at the two otas and this seems like the last not unified fw

The next one is probably going to be a single file for both versions
[Nothing Phone 1] chaoslos:
Anyway to downgrade from 1.1.8 EEA to 1.1.7 EEA without losing data? I'm on 1.1.8 but my phone still identifies with source build version 1669043157 (1.1.7) making updating to 1.5.2 impossible.
[Nothing Phone 1] Bnjalal:
I was on 1.1.7 hotfix EEA, grabbed the 1.5 then 1.5.1 then 1.5.1. hotfix and finally the latest stable

As far as im concerned, there is no 1.1.8 EEA or I wasnt able to load it for some reason
[Nothing Phone 1] chaoslos:
View attachment 5845147

Seems Like you somehow missed it. I looked at the ota ZIP for 1.1.8 (EEA) and my source build version should have been updated to 1673511228 but it was not.

Or might there be a way to force the installation of an ota update zip? I technically should be on the right version.

EDIT:

Found out that source build version is affected by the flash boot.img

I needed to flash 1.1.7 boot img onto 1.1.8 (for magisk) because there is no 1.1.8 EEA boot image available anywhere.

Can anyone provide a 1.1.8 EEA boot image?
[Nothing Phone 1] Ostry10:
Same here bro, right now i bricked my phone trying to update to 1.5.

Send me a message when youll find 1.1.8 EEA boot.img
[Nothing Phone 1] G.I.StaR:
hello, I need help, I can’t update my phone, it’s worth deleting root, it doesn’t help, vendor and boot put stock
[Nothing Phone 1] TheNewHEROBRINE:
Did you restore the stock boot image from Magisk?
[Nothing Phone 1] G.I.StaR:
I put the stock loader through adb, Magisk completely removed
[Nothing Phone 1] TheNewHEROBRINE:
Are you sure you put the exact boot image corresponding to your current firmware version?
[Nothing Phone 1] G.I.StaR:
yes global 1.1.8, downloaded here
[Nothing Phone 1] p4oeNix:
Hi all, anyone have any ideas how to change the system font? I am completely happy with it, I need it as an experiment

I have root 1.5.2
[Nothing Phone 1] chaoslos:
After setting up a Linux VM to run a 2 year old payload extractor program, I managed to get my hand on a 1.1.8 EEA boot.img :D I don't think anyone has uploaded that yet! Here
[Nothing Phone 1] Ostry10:
Nice :D Half hour ago I also unbricked my phone :D
[Nothing Phone 1] misiek998:
Can you help step by step update 1.1.8 with magisk and 1.1.7 boot? It is possible without losing data? I don't get OTA yet. I have same system build version Spacewar-S1.1-230112-1613EEA. sideload tought ADB failed because versions mismatch. thank you

I need for now disable magisk modules -> uninstall magisk / restore boot option -> reboot into fastboot -> flash your boot 1.1.8eea -> reboot and now I will get OTA update?
[Nothing Phone 1] AnotherM1m:
Wait, right now you are on what system? eea 1.1.8 but flashed 1.1.7 magisk patched boot?
[Nothing Phone 1] misiek998:
Yes I'm on 1.1.8 with 1.1.7 boot as first post this thread says.
[Nothing Phone 1] Chaotick:
Here is my first battery stat on oficiall 1.5.2. I think that idle discarge speed has improved when phone is not used and just getting notifications. And perhaps battery usage on 5G as well :) Compared the overall fluidity of OS responsiveness to a S23 and I pretty much don't see a diffrence.
[Nothing Phone 1] chaoslos:
If you are on 1.1.8 EEA and you already removed magisk.. reboot into bootloader and flash the 1.1.8 EEA boot image I provided. You can check your source build version (needs to be 1673511228 after flashing 1.1.8 EEA boot IMG) if you reboot via fastboot (in bootloader) into fastboot and then select the second option "enter recovery". If it then still does not work over the official nothing updater try over adb sideload and post the error.

EDIT:

I successfully updated to 1.5.2 after flashing the 1.1.8 EEA boot image. (Without any data loss)
[Nothing Phone 1] misiek998:
After flashing boot 1.1.8 I have got right version:

adb shell getprop ro.build.fingerprint

Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys

BUT get error pushing OTA via recovery error 45 - error UnknownMinorPayloadVersion installation aborted

I try this

Incremental from EEA 1.1.8

From https://www.xda-developers.com/nothing-phone-1-nothing-os-update-tracker/

EDIT:

Pushed OTA via official app " *#*#682#*#* " installed, works... Now can you post 1.5.2 boot EEA magisk patched? :)

FOR Nothing/SpacewarEEA/Spacewar:13/TKQ1.220915.002/2302132131:user/release-keys

I think it is same than GLOBAL but I'm not sure I have

Spacewar-T1.5-230213-2131-EEA
[Nothing Phone 1] AnotherM1m:
Thank you for the help and the 1.1.8 eea boot img! Can i also ask you if with you phone and magisk you are able to patch it by selecting it and uploading the patched boot? Ty it is needed in this thread.

Perfect, try booting (not flashing, booting)

This boot.img

magisk_patched-25200_TrVLh.img

drive.google.com

After the boot is done open magisk and select direct install, reboot when it ask you to.

This will help you next time with ota updates.
[Nothing Phone 1] misiek998:
Confirm Boot above works and have root access, thank your help

View attachment 5846585
[Nothing Phone 1] AnotherM1m:
Nice, thank you for your feedback on the boot.img (which we now know that at least those are unified).

After booting remember to do direct installation on magisk to keep your root!

By doing this procedure magisk will save the original boot as a backup.

Next time you get an ota, uninstall magisk by opening it selecting uninstall and then select restore stock images (do not reboot).

Perform the ota, don't reboot, re open magisk and select install in the inactive slot.

This will allow you to perform the ota and reboot with the new rooted fw.
[Nothing Phone 1] xtcislove:
If i root i dont receive otas. I can download the ota package and install it with *#*#682#*#* but it reboots automatically so i cant install magisk to the inactive slot.

What am i missing?
[Nothing Phone 1] AnotherM1m:
Rooting shouldn't limit you from getting ota updates

Are you modifying /system or /vendor?

The dialer automatically reboots the phone

To keep root with this method hold vol down while the phone is booting to go into bootloader

Here boot a modified magisk boot img

After boot open magisk and select direct installation
[Nothing Phone 1] xtcislove:
Im using the following modules.

Magisk built-in BusyBox i know it install to system. Is this the problem? Can i uninstall the module and it fixes my ota ability?

I have the folllwing modules too but i dont know if they modify system or vendor:

Systemless hosts (probably not)

Universal SafetyNetFix

Universal GMS Doze
[Nothing Phone 1] AnotherM1m:
I don't think any of those modules are the problem.

But i don't know everything that can cause you problem, maybe in your area they are doing a staged rollout.

If you still have to receive the ota notification but want to update, the dialer method is the best

remember to watch out for the auto reboot and hold vol down to enter bootloader and boot the modified boot.
[Nothing Phone 1] xtcislove:
Built in busy box module is in system If I understand it right. I will test without it and with future updates. Thanks.
[Nothing Phone 1] Giunta._:
I guys someone have the vendor_boot.img of 1.1.8EEA? Thanks a lot
[Nothing Phone 1] 3lpico:
I have the same problem, did you find a solution by any chance ?