yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] AnotherM1m:
Yes, they changed how logs are done and i didn't had time to update it.

Error 20 is caused by a partition (or more) not being stock, follow this guide, dirty updates (and dirty installations of fw) are possible

GitHub - LukeSkyD/NP1-FLASH-ALL-SCRIPT: Script to flash fastboot rom to your NP1

Script to flash fastboot rom to your NP1. Contribute to LukeSkyD/NP1-FLASH-ALL-SCRIPT development by creating an account on GitHub.

github.com
[Nothing Phone 1] AnotherM1m:
First message updated

Added stock and magisk patched boot

Let me know if you encounter any problem.
[Nothing Phone 1] DiogoPdC:
Thank you so much will let you know how it goes
[Nothing Phone 1] Colonel Torchere:
So I have to reinstall 1.5.6 using this script and then sideload Nothing OS 2, right? Do I need to unroot my phone before this?
[Nothing Phone 1] AnotherM1m:
When you reinstall 1.5.6 with the script you already unroot (because it install all stock images) so you can directly update with the offline dialer updater or with the settings' menu
[Nothing Phone 1] EzerchE:
Is there a step by step tutorial to update 1.5.6 with root to 2.0.2 with root? I have read many pages but I am just confused.
[Nothing Phone 1] jnsson:
When I tried to update I got "Failed to set up expected mount for install; aborting". Anyone knows why?
[Nothing Phone 1] AnotherM1m:
Dont sideload from adb, perform the update from the dialer

If the dialer is failing with error 20 use this to reinstall the firmware you already have (without wiping)

GitHub - LukeSkyD/NP1-FLASH-ALL-SCRIPT: Script to flash fastboot rom to your NP1

Script to flash fastboot rom to your NP1. Contribute to LukeSkyD/NP1-FLASH-ALL-SCRIPT development by creating an account on GitHub.

github.com

You need both bootloader and critical partitions unlocked (unlocking one or all of them will wipe data)
[Nothing Phone 1] Colonel Torchere:
Still getting ERROR/20 even after i launched the script (and my phone did factory reset when i unlocked cricital partitions)
[Nothing Phone 1] AnotherM1m:
Did you flashed with flash all script from my repo (lukeskyd)?

Or you flashed with the script in the fastboot rom?

Did the script returned any error?
[Nothing Phone 1] Crushader:
I need help guys, I flashed the Android 14 beta months ago, and now I'm stuck, unable to update or change firmware either from OTA or ADB. The firmware version is shown as UpsideDownCake, I've tried all different versions of firmware but all the same error

If I try to update from OTA, I get this error: error code -2: pre-build-incremental is different from ro.build.date.utc. I changed the region and timezone to china shanghai but the error doesn't go away

If I use ADB sideload, I get E: failed to unmount /mnt/product/nt_log, and E: failed to set up expected mounts for install: aborting

What do I need to do to roll back to stable 1.5.6 or anything else aside from beta?
[Nothing Phone 1] AnotherM1m:
https://xdaforums.com/t/help-thread...-question-noob-friendly.4470203/post-88935393
[Nothing Phone 1] dsjiffry:
Hi, so I Updated to NOS 2.0, no problems so far... Just wanted to know if we still need the MGLRUDisabler Module if rooted?
[Nothing Phone 1] AnotherM1m:
Not needed since 1.5.4
[Nothing Phone 1] Mozie:
Hi guys, is there a way to get the full stock firmware instead of the incremental one which is also provided in this thread?
[Nothing Phone 1] AnotherM1m:
Re index fastboot roms are the closest of what you are asking for.

It seems like full zips are not released from nothing (for now).
[Nothing Phone 1] Mozie:
Hmmm interesting. Any idea why they wouldn't release them? It's been long time now since NP1 is released
[Nothing Phone 1] AnotherM1m:
Sorry no clue
[Nothing Phone 1] shailantani:
Heyyy.

I have rooted nothing phone running 1.5.6, I tried updating the phone to 2.0.2 through adb, but im getting this error too:

Failed to unmount /mnt/product/nt_log

failed to set up expected mounts for install aborting

Could you please help me out?

(I have all magisk modules disabled)
[Nothing Phone 1] AnotherM1m:
update with dialer method

remember to restore stock boot image before starting the update procedure
[Nothing Phone 1] shailantani:
I'm really sorry but im super beginner in this, but what do you mean restore stock boot image?

I have the new os 2.0.2's and current 1.5.6's stock boot image downloaded, what do I do with them again?

Again, im really sorry for these silly doubts :")

Do i just run "Fastboot Flash Boot Boot.Img " ? and if so, should I flash the current 1.5.6's boot image?
[Nothing Phone 1] AnotherM1m:
don't worry

read the whole thing before start launching commands

when you root, you create a new boot img which gets flashed to the phone

Ota updates check for partitions to be stock, if they detect any tampering the update is stopped.

so before starting an ota update if you are rooted you will have to flash again stock boot images.

if you rooted the RIGHT way (booting a patched boot img then opening magisk and selecting direct install)

you will have to open magisk, select uninstall and then restore stock images

if you rooted wrong by directly flashing the magisk patched boot yourself from bootloader, you will have to flash stock and then boot magisk patched boot

then update from the dialer, when the reboot message appears press the home button, do not close the updater or press the message, open magisk, select install, install on inactive slot

when magisk finishes, reopen the dialer and select reboot.
[Nothing Phone 1] AnotherM1m:
please ask this in the appropriate thread possibly in english

[HELP THREAD][Nothing Phone (1)] Ask Any Question, Noob Friendly

Hi Everyone, I have created this thread which will allow to gather, but also to help by bringing answers to the various problems which can meet the owners of the Phone(1). Unfortunately some of these problems cannot be solved here, in which case...

xdaforums.com
[Nothing Phone 1] whatsek:
Just a reminder, unlocking and relocking the bootloader will factory reset your device. Also be carefull locking a rooted phone with a patched boot image (for root) can result in a non booting phone.
[Nothing Phone 1] Wabbajackw:
Nobody answered me so i ask again, please somebody know if there is any risk to flash global stock rom on an european device ?
[Nothing Phone 1] lassetth:
I tried but got a message "wrong software".
[Nothing Phone 1] Wabbajackw:
Thank you for your answer and your test, so i need to wait i guess... I feel scammed... The phone is more expensive here, and we are last for OTA
[Nothing Phone 1] jkebwdn:
Thank you! I am on the EU version though, any chance you have the EU boot.img, or will it not matter? Also would you know if there is a way I can get these OTA's from the device myself without root? Would be happy to contribute these EU OTAs to the comminuty.
[Nothing Phone 1] danimus:
EU 1.1.3 OTA Update Links Available:

https://xdaforums.com/t/nothing-os-...uropean-nothing-phone-1.4482723/post-87328005
[Nothing Phone 1] Wabbajackw:
Yes, already updated, seems to have some new glyphs but impossible to use them exept in some third apps as WhatsApp
[Nothing Phone 1] Sib64:
Hey everyone,

I got back from holiday yesterday and will try to update the whole thing and respond to your posts ;) before I go back to work on Friday morning.

For those who are still on holiday or going on holiday, enjoy it 😎, for those who are at work, I wish you courage.🤝

Have a nice and good day all 👍
[Nothing Phone 1] Sib64:
OP with Full Nothing OS 1.1.3 updated 23/08/2022

Files for Nothing OS (stock boot) updated with boot for global & european 1.1.3
[Nothing Phone 1] sh4tteredd:
Is there any global FULL rom link from android.googleapis.com? (not afh)
[Nothing Phone 1] Sib64:
Sorry, but I don't have one. It's hard to have and find.

I only have AFH
[Nothing Phone 1] sh4tteredd:
maybe I found out how, the name of the original file downloaded from googleapis is the SHA1 of the file so maybe I can calculate it from the one that you have uploaded on AFH and it may works. from where did you get the full package global?
[Nothing Phone 1] HofaTheRipper:
Global Full (1.1.3):

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

Global Incremental (from 1.1.2):

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

EEA Full (1.1.3):

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

EEA Incremental (from 1.1.2):

https://android.googleapis.com/packages/ota-api/package/9441a6b477bf0a5ac205fa93ae37a341181b1341.zip
[Nothing Phone 1] sh4tteredd:
yeah i found it using the SHA1 trick, funny that it worked
[Nothing Phone 1] HofaTheRipper:
which SHA1 trick? explain it to me please
[Nothing Phone 1] sh4tteredd:
actually the link is made of:

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

Sib64 uploaded the zip on AFH, so I downloaded it, calculated the SHA1 and then substitute it in the link lol
[Nothing Phone 1] HofaTheRipper:
ahhh... ok 😂
[Nothing Phone 1] NightStrix:
Thank you for the great job !
[Nothing Phone 1] corpsus:
I already asked this in another thread but got no response, so trying here as well since related to updating.

---

I'm having trouble installing the latest 1.1.3 update. I'm rooted, so I followed the following procedure:

Restore default images in Magisk

Download and install update normally in Settings (without rebooting!)

Install in inactive slot in Magisk and reboot

I assumed update was successful, although I had lost root after rebooting. I re-patched the boot.img and thought nothing more of it. Until a few days later the phone notified me again of an available update, and I noticed I'm still on 1.1.2. I have again unrooted and restored stock boot.img, but now the OTA will not install. In settings I just get an error message "Couldn't update. Installation problem". If I try to sideload OTA through recovery, it says "Package is for source build 1658940712 but expected 1657910681".

Does anyone have any ideas what the problem is, or suggestions what I should try next?

I'm in the EU, so using the below OTA package posted earlier in this thread.

OTA Update 1.1.3 EU Incremental Update over 1.1.2​

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

Another question: If I were to try to flash the full package instead of OTA, would that require a wipe of the phone?
[Nothing Phone 1] gwolfu:
Try flashing full package via local update (more on how to do that, here - read full before doing)

No wipe will be needed.
[Nothing Phone 1] shailantani:
Thank you so much for explaining this!

I just realised I had rooted it the wrong way, could you perhaps explain just a teeny bit more on that?

So I have to flash the stock boot.img now? And then do I proceed with the update via dialer?

And after that I have to proceed with booting magisk img to get root access again right
[Nothing Phone 1] AnotherM1m:
HEADS UP EVERYONE

I wrote a guide about updating NP1, also while rooted

Nothing Phone (1) - Repo [ NOS ][ OTA ][ IMG ][ GUIDE ][ ROOT ]

Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with PHONE(1), you...

xdaforums.com

It's in the third message

Remember to never reboot with magisk, it does not work.

Let us know how it goes and if you encounter any difficulty
[Nothing Phone 1] AnotherM1m:
Updates:

Added 2.0.2.hotfix to incremental ota list, added stock and magisk patched boot, updated error 20 guide, added two guides to follow for updating the phone with steps to keep root

Fixed some formatting issues.
[Nothing Phone 1] Pepousek67:
View attachment 5994575

Small hotfix update for 2.0.2. came today via OTA. PS: this confirms that even after a manual update to 2.0.2, the update will come via OTA.
[Nothing Phone 1] shailantani:
Hey man, just wanted to thanks a ton for this guide!

It helped a lot :)

Also just one doubt, why doesnt the adb method work?
[Nothing Phone 1] AnotherM1m:
No problem i hope you were able to solve your issues, if not write here on the forum, no problem.

I have not investigated such issue, next update!
[Nothing Phone 1] lucy1983:
View attachment 5994635

The highlighted stock boot image is the one from today update? With the build number 230901?
[Nothing Phone 1] AnotherM1m:
yes, are you encountering any problems with it?
[Nothing Phone 1] lucy1983:
No. I'll try right now to use it to root my phone again. Because somehow I lost root by trying to update with the system updater app. There was a problem after installing Magisk on inactive slot, I could not restart using the system update app so I restarted from Magisk and I lost root.
[Nothing Phone 1] lucy1983:
This was the problem after installing Magisk on inactive slot.
[Nothing Phone 1] AnotherM1m:
yes, what i propose in the guides is what i achieved try after try.

Updating through settings' app blocks you from successfully rooting your phone with magisk.

The only way is to boot a mp boot image when the phone reboots with fastboot and then do direct installation.
[Nothing Phone 1] lucy1983:
I'm trying to do just that right now using another phone and the Bugjaeger app since my PC Is temporarily unavailable (monitor problem I think, just goes black after 3-4 minutes from starting Windows).
[Nothing Phone 1] jmissao:
So, in case I'm in another custom ROM, in order to go to 2.0.2, I have to:

first flash 1.1.8 full

then incremental 1.1.8 -> 1.5.4

then incremental 1.5.4 -> 1.5.5

then 1.5.5 -> 1.5.6

then finally 1.5.6 -> 2.0.2

is that it?
[Nothing Phone 1] AnotherM1m:
You should

- Download full 1.1.7 EEA or GLOBAL

- Extract boot and vendor_boot from the fw with payload dumper (do not delete the zip file yet)

- Boot the phone into fastboot

- Flash those two .img files

- Boot into recovery and select adb sideload

- adb sideload the full zip previously downloaded

- wipe/format data

You can now boot your phone, if you want to root it remember to BOOT the magisk patched boot, not flash it and then do a direct installation of magisk through the app.

For the other fw versions there could be some otas that jumps through a lot of them that we don't know about.

I would suggest to not root the phone but perform updates through the settings app.
[Nothing Phone 1] AnotherM1m:
ADDED GUIDE to restore NOS after installing a custom rom (otas working after!)
[Nothing Phone 1] vlad9086:
Hello everyone, can anyone help?View attachment 5996515
[Nothing Phone 1] AnotherM1m:
Oh wow this is a new one i think

Rooted? What sw versions are you on? To which are you updating to?

Also check that the sha1 hash of the zip file is equal to its name

If you are downloading the file from a pc, try another usb cable to transfer it to the phone.
[Nothing Phone 1] -RainMaker-:
I have the following problem.

Magisk 26.3 is installed.

I really want to install the 2.0.2 Hotfix update and have followed all the steps. I restored the Magisk Stock.img and then flashed the Stock Boot img 2.0.2 again with Fastboot. After that, I booted with the Patched Magisk Boot img. I loaded the Hotfix Update 2.0.2a into the OTA folder and selected it via the dialer to try to flash it, but it still shows me Error 20, even though the Stock img was flashed. I'm really puzzled about what else I should do.

I also completely removed root and booted with a Stock Boot Img file instead of using the patched version, but even then, it shows me the same error.

The flash-all script to fix it doesn't work because when I start the script, it says 2 files are missing.

Can anyone help me?

If this doesn't belong here and should have been asked in a different section, I apologize.
[Nothing Phone 1] AnotherM1m:
which files are missing?
[Nothing Phone 1] -RainMaker-:
Mdtp.img and qweslicstore.img
[Nothing Phone 1] vlad9086:
нет рут прав, обновилась версия 1.5.6 по воздуху, с кешем и юсб кабелем все в порядке, устанавливал через компьютер
[Nothing Phone 1] AnotherM1m:
Download those here:

mdtp:

File on MEGA

mega.nz

qweslicstore:

File on MEGA

mega.nz

put those in the folder with the fastboot rom and the script and run flash all script again.

you are NOT required to wipe data

Please write in english

Try downloading the ota from HERE directly from your phone, then move it to the ota folder
[Nothing Phone 1] vlad9086:
no root rights, version 1.5.6 was updated over the air, everything is fine with the cache and USB cable, installed via computer

OTA update doesn't work either
[Nothing Phone 1] AnotherM1m:
Try using Hash Checker app from playstore to check that the SHA1 hash of the ota zip file is equal to its name.
[Nothing Phone 1] vlad9086:
checked, everything fits
[Nothing Phone 1] AnotherM1m:
connect the phone to a computer and start and adb logcat before the update process start with the command

adb logcat >file.txt

then start the update with the dialer, when you encounter the error you can stop the adb command

send me privately file.txt
[Nothing Phone 1] vlad9086:
ok, I'll do this as soon as I get home from work
[Nothing Phone 1] DiogoPdC:
Anyone experiencing really bad battery life since nos 2.0?

any tips on how to make it better?
[Nothing Phone 1] muppetz:
nope , I think is better
[Nothing Phone 1] AnotherM1m:
i've analyzed the file, nothing new, what's causing issues is this

09-09 14:36:25.967 1670 1670 E update_engine: [ERROR:utils.cc(232)] rc >= 0 failed: I/O error
09-09 14:36:25.971 1670 1670 E update_engine: [ERROR:extent_reader.cc(85)] utils::ReadAll( fd_, bytes + bytes_read, bytes_to_read, cur_extent_->start_block() * block_size_ + cur_extent_bytes_read_, &out_bytes_read) failed.
09-09 14:36:25.972 1670 1670 E update_engine: [ERROR:file_descriptor_utils.cc(59)] reader.Read(buf.data(), read_blocks * block_size) failed.
09-09 14:36:25.974 1670 1670 E update_engine: [ERROR:partition_writer.cc(261)] source_fd != nullptr failed.
09-09 14:36:25.975 1670 1670 E update_engine: [ERROR:delta_performer.cc(844)] partition_writer_->PerformDiffOperation( operation, error, buffer_.data(), buffer_.size()) failed.
09-09 14:36:25.976 1670 1670 E update_engine: [ERROR:delta_performer.cc(199)] Failed to perform BROTLI_BSDIFF operation 2685, which is the operation 164 in partition "product"
09-09 14:36:25.978 1670 1670 E update_engine: [ERROR:download_action.cc(227)] Error ErrorCode::kDownloadOperationExecutionError (28) in DeltaPerformer's Write method when processing the received payload -- Terminating processing

error 28 seems to be caused by system_a, system_b and userdata partitions' wrong dimensions in the memory.

are your bootloader and critical partitions unlocked?
[Nothing Phone 1] vlad9086:
My unloader is blocked, but my phone was restored via edl, maybe this will affect the memory blocks?
[Nothing Phone 1] AnotherM1m:
It shouldn't... did you get the edl tool from here on xda?

im not sure about what the next steps should be: i think that right now only a reformat with the edl tool here on xda or a flashing through fastboot will fix things

Both unfortunately will require you to lose all your data.

I would try one last time to download the zip file differently to your phone, there may be something damaging the zip

i'm sorry to hear about the soft brick, you did right by not formatting data.

you did get to 2.0.2 (originally, before the brick) by flashing its fastboot rom, right?

did you select auto or a specific slot while flashing?

if you are on stock 2.0.2 updated through ota as long as you root correctly (by booting the magisk patched boot and then doing direct install in magisk) you shouldn't have any issues with updates...

But i guess i've said something similar before i guided you to bricking your phone so it's up to you

(payload dumper wasn't supporting android 13 last time i checked, which added xor compression to partitions.

it should not be used.)

Also, just for curiosity, did you get a single update from 1.1.7 to 2.0.2?
[Nothing Phone 1] vlad9086:
I installed firmware 1.1.7 via unbrick tool edl, now I will try to update via ota
[Nothing Phone 1] vlad9086:
Thank you very much everyone for your help in this investigation, and especially AnotherM1m, after all, I had a problem with memory layout because of this error 28, the solution that helped was installing firmware 1.1.7 via the unbrick tool, and updating to 2.0.2 via ota
[Nothing Phone 1] AnotherM1m:
Glad to hear that, weird that things got messed up in the first place but you were able to solve it.
[Nothing Phone 1] dedors:
I updated via Settings OTA from 1.5.6 to 2.0.2. I had no seperate hotfix update.

Trying to update via dialer mode to hotfix gives me error corde -2, pre-build-incremental is different from ro.build.date.utc. Changing timezone (tried a few) didn't help (this fixed that issue on a earlier version).

My build is Spacewar-T2.0-230901-1652-EEA, I think this is already the hotfix. Can someone confirm please?
[Nothing Phone 1] AnotherM1m:
The build is the hotfix one
[Nothing Phone 1] muppetz:
Did anyone faced "automatic brightness" , "ambient display " or whatever issues ?

Since last 3 updates they ruined this feature . Even last hotfix they said it's fixed but ...bupkis , nada , same bug . I mean brightness it's not really automatic and more than that brightness decrease suddenly , no reason to low levels .

I'm sick of it , no tips please for "device health" or "velis auto.apk or look to AI feature and the phone is learning how to automate the brightness , this is bu...it , I don't see the point ... why on lot of phones this error is present and how can I deal with it ?

This is a major inconvenient to me and it bother me a lot , I can't increase brightness every minutes in low light !!!
[Nothing Phone 1] Adrian312:
i am not able to boot rooted magisk boot file. I tried lates magisk version, 2 versions back, still the same. I never had this problem before. I am on 2.0.2 OS. Any idea where I can find the problem? I want to avoid downloading Magisk boot file from #1. thank you
[Nothing Phone 1] lucy1983:
Download the provided Magisk boot image from this post. It is safe. I also had problems booting with the image patched by me. It wasn't booting.
[Nothing Phone 1] AnotherM1m:
2.0.2 normal or hotfix?
[Nothing Phone 1] Adrian312:
Hotfix
[Nothing Phone 1] AnotherM1m:
Just checked magisk patched boot from the first message, it boots fine, it is provided by me, it's safe.

If your phone still does not boot with that image, one or more modules could be causing issues.
[Nothing Phone 1] Adrian312:
Yes i used that one and its fine. I was just curious why its not booting with mine. I was patching mine since 1.5... Odd. Anyway thank you!
[Nothing Phone 1] lucy1983:
Maybe some changes on the latest 26.3 Magisk side? I also patched with 26.3 and it didn't boot. With what version of Magisk did you patched your image?
[Nothing Phone 1] AnotherM1m:
how are you dumping the boot img to patch? are you doing directly to magisk manager app latest version (26.3)?

26.3 directly from the app

I fastboot booted 2.0.2 (not hotfix) magisk patched boot, opened magisk manager and selected directly install, rebooted, used a script to dump the new boot partition (the one with patched 2.0.2.hotfix)
[Nothing Phone 1] pyry666:
I can confirm that there is something wrong with non patched hotfix boot.img, tried previous one and it bootesd just fine. I also use magisk 26.3. Didnt try patched one though cause i like to patch myself. Maybe non patched hotfix boot.img is corrupted or somethin? Well everything works now anyway as it should..
[Nothing Phone 1] AnotherM1m:
Yes you are right, stock 2.0.2.hotfix boot img was corrupted

The new link is: https://mega.nz/file/j5Rl0bqC#UbfHZDLcJ-jf44jbHD7hH_qysWSz0TETptih9evgsO8