yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] AnotherM1m:
I offer support for sw updates, images and files used and uploaded in this thread. In the first message here

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

Try using them and let me know if you have problem with those.

Which sw are you on?
[Nothing Phone 1] Sonalk:
I'm on 1.5.4. I'll try one of those in a bit
[Nothing Phone 1] Sonalk:
When I'm already on 1.5.4 should i choose

INCREMENTAL 1.5.4 FROM 1.5.3.HOTFIX

or

INCREMENTAL 1.5.4 FROM 1.5.2

Don't rememebr being on the same version being a problem.

When I tried extracting image from the 1.5.3->1.5.4 file I get:

payload.bin: payload.bin

Number of workers: 4

2023/06/01 11:56:35 Payload has not been initialized
[Nothing Phone 1] AnotherM1m:
If you only need the boot.img file scroll down and directly download it.

Payload dumpers right now do not work with nothing os incremental otas.
[Nothing Phone 1] Sonalk:
Thank you! I downlaoded the stock image file, patched it and it worked.

Still don't quite understand why I couldn't extract the image from the payload myself though. I've done that numerous times on different phones included my nothing phone at an earlier software.

Normally I wouldn't care as long as there was boot images to download but I'm actually in the middle of creating a software that extracts payload from zip. image from payload, boots into fastmode and then boots into the image file automatically, but maybe I need to remove that feature.

I was also thinking about making it so I can patch the image with magisk with the software but after some research it seems to be very hard to port the magisk image patcher to pc, if not impossible.
[Nothing Phone 1] AnotherM1m:
Android 13 introduced xor compression for partitions, that could be causing some issues.

Let's end offtopic discussions now tho.
[Nothing Phone 1] Sonalk:
Is TWRP required/recommended for a rooted nothing phone? Want to download lsposed and don't want to risk a boot loop.

What I've seen nothing phone already had a recovery mode, as i guess every phone has. Is that one not as competent or why would you need TWRP?
[Nothing Phone 1] lucy1983:
You don't need twrp to be able to uninstall any modules that causes bootloop. See in this video how to do that without twrp.
[Nothing Phone 1] kekanakan:
Hello guys... Now my nothing phone (code:spacewar) in v1.5.3

Can i root this phone?

Or root only work on version 1.5.2 and previously?

.

.

I try to unlock boot loader, but my PC cannot detect my nothing phone in fastboot mode
[Nothing Phone 1] AnotherM1m:
You can root 153, you just need mglru disabler module to prevent freezes and crashes (bug with 153 fixed with 154)

You are probably missing adb and fastboot drivers.

Install them with the latest version of android sdk platform tools.

If you root 153 could you let me know before updating to a newer version? There are some files needed to solve an issue and you could help for the fix
[Nothing Phone 1] kekanakan:
Can you help me where can i get download adb and fastboot drivers?
[Nothing Phone 1] AnotherM1m:
It's offtopic here, I sent you a private message.
[Nothing Phone 1] Sluzy:
When I use the fastboot boot command the phone doesn't boot, it goes to the charging animation, any help?
[Nothing Phone 1] Cathair2906:
Global Full ROM

1.1.7:

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

1.5.4:

https://android.googleapis.com/packages/ota-api/package/2c17b815911108fdacee1c6124ef67b45538c298.zip
[Nothing Phone 1] AnotherM1m:
Thanks the first link is the full 1.1.7 but the second is an incremental from 1.1.8 to 1.5.4, not a full zip

Still handy tho.
[Nothing Phone 1] Cathair2906:
i thought 1.2GB is a full rom, how do u know that?
[Nothing Phone 1] AnotherM1m:
Download the file, extract it, open folder META-INF/com/android, with a text editor open metadata file and if there are values for pre-build and pre-build-incremental then it's not a full zip but an incremental ota
[Nothing Phone 1] asdfghj1237890:
I have also faced this problem after upgraded to 1.5.4

after booting with the patched img, it stuck at the looping animation.
[Nothing Phone 1] trivjednom:
Can I use one with the attached files? I have project elixir 3.8 and my model is EEA spacevar.
[Nothing Phone 1] AnotherM1m:
@caffeine01 hi, are you still on 153 with error 20? a solution was found:

redownload the fastboot rom, extract it, DO NOT RUN THE FLASH ALL SCRIPT, but open a terminal in that folder and with fastboot flash the broken partition with the img in the fastboot rom folder.

in your case

fastboot flash bluetooth bluetooth.img

Try the ota update again, but beware that another partition could be broken and you will have to flash all the broken partitions back wth fastboot and the fastbootrom folder

The script does not flash all files, so some partitions are skipped and not flashed resulting in old, not stock partitions for the new fw.
[Nothing Phone 1] neilphetamine:
NothingOS 1.5.5 is now live!

Incremental: https://android.googleapis.com/packages/ota-api/package/b0d72e21232dfd4392c6eaaeb651dcfd163007f3.zip
[Nothing Phone 1] AnotherM1m:
Added to the front page with stock and magisk patched boot images!
[Nothing Phone 1] Pepousek67:
View attachment 5941521
[Nothing Phone 1] Ma3str0:
Thanks, is Desktop Mode still locked?
[Nothing Phone 1] Sluzy:
When trying to update to the 1.5.5 version, the OfflineOtaUpdate gives me the error DOWNLOAD_STATE_INITIALIZATION/20 even when I change the region to China/Xangai, can someone help me?
[Nothing Phone 1] AnotherM1m:
Some partitions are broken, please take a look at this post

https://xdaforums.com/t/nothing-phone-1-rom-ota-nothing-os-repo-of-nothing-os.4464039/post-87101175
[Nothing Phone 1] Sluzy:
Yes, I saw it, but I wasn't finding what partition was broken, so I loaded the original boot.img and it worked
[Nothing Phone 1] Sluzy:
By the way, my bluetooth keeps crashing when I use the AirPods gestures to skip to the next song, can it be the Bluetooth partition broken?
[Nothing Phone 1] AnotherM1m:
If it was broken you would not have been able to update your phone

I don't know much about airpods integration, you could try asking in the official support thread mentioned at the start of the first message here
[Nothing Phone 1] dexlemaffo:
Did you try CAPOD from F-Droid ? That app manages Airpods on Android (but no firmware uptade feature imolented becaise it's Apple property)
[Nothing Phone 1] evase:
just a question: Why aren't there anymore full ota updates for download? I have my Np1 only a month now so I don't know everything yet and I saw that the full otas just stop sometime in the update list
[Nothing Phone 1] AnotherM1m:
Nothing prefers releasing different incrementals rather than full zips.

If you need a full zip rom because you've bricked your phone you can use these (beware that critical partitions are not flashed by the script so must done manually, phone will boot normally but updates will be broken):

https://xdaforums.com/t/rom-restore...t-rom-full-rom-boot-img-qfil-rom-edl.4523185/

Installing an update via adb sideloading doesn't work, the only way to update your phone is with the dialer and offlineotaupdater
[Nothing Phone 1] evase:
That's what I already tried but I'm having issues with my device being rooted. When restoring boot.img via magisk uninstall it says no original boot.img is saved that's why I flashed the original boot.img and deleted everything root-related. Root checker said device is not rooted but update still couldn't be loaded via settings and the dialer offline updater didn't do anything(does recognize the file but never starts update) (for reference netflix app also still detects root after flashing original boot.img)
[Nothing Phone 1] AnotherM1m:
Netflix apps has a lot of checks like the bootloader state, if it reads unlocked it blocks.

Have you updated your phone with a fastboot rom?

From and To which fw version did you update?

If you did you'll need an unlocked bootloader and flash all the critical partitions with fastboot command.

To restore a stock boot img with magisk you need a phone with a stock boot flashed, and then boot a magisk patched boot img with fastboot (see that i wrote boot and not flash?)

fastboot boot *patched boot img here*

When the phone boots up open magisk, select install and then direct install.

Next time you get an ota update you open magisk, select uninstall and the restore stock images, open the ota update, update but before rebooting your phone open magisk, select install and then ota update installation, reboot when magisk tells you to.
[Nothing Phone 1] evase:
I have stock rom 1.5.4 flashed through Fastboot because of a bootloop before

I think magisk couldn't save the original boot.img because booted patched boot.img but then flashed it afterwards manually through Fastboot instead of the app. I think I'll just wait for Android 14 update and do a clean rom install to do everything right.

Thank you for making everything clear
[Nothing Phone 1] lucy1983:
If you use the edl method to install the 1.1.7 firmware then all the partitions will be flashed correctly and you'll have no problems updating your phone by OTA (online or offline method, doesn't matter) AND keeping root at the same time. Unlike the fastboot method of going back to stock, witch doesn't properly flash some partitions and you'll have to find them and flash them manually, witch is more complicated and not necessary considering that flashing stock with EDL method does everything correctly witch just two clicks.

I just updated to latest 1.5.5 from 1.5.4 using the OFFLINE method and it worked flawlessly.
[Nothing Phone 1] evase:
so offline updater doesn't care about root? And doesn't the online update block when it detects root?

Thanks in advance I'll definitely try this to get correct partitions.
[Nothing Phone 1] lucy1983:
No. It "cares" about root. You must respect the procedure to install magisk on the empty slot. I was saying that by flashing the stock 1.1.7 rom with the EDL method you are absolutely sure that ALL the partitions are flashed properly. Unlike the fastboot method, witch lets some partitions not flashed properly and you have to struggle to find witch they are and flashed them manually after that.
[Nothing Phone 1] 1stStep:
Hi all

It's a long while since I postponed upgrade from NOS1.5.2 to 1.5.3 as we were aware that rooting would drive in error. Now I'm prompted by NOS to upgrade to 1.5.4. My NP is rooted. Magisk currently installed release is 26101 and advises to update the App to 26103 (Only Ramdisk is enabled, no Zygisk, no extension/plugin). Should I update this first of all ?

Then Uninstall Magisk to restore unpatched partitions ?

Then relock bootloader for successful upgrade to 1.5.4 ?

Last time AnotherM1m gave a link to grab patched partitions. Is the process the same now or is there a way to make these ourselves (will require the full target release official ROM isn't it ?)

Many thanks for lights
[Nothing Phone 1] AnotherM1m:
Update Magisk.

To proceed with ota updates you don't need to lock the bootloader, it is not something i would suggest in general.

Just uninstall magisk by selecting restore to stock, proceed with nothing os update but before rebooting open magisk, select install and then ota update installation. Reboot when magisk asks you to.

Uninstalling Magisk while restoring stock images is possible only if magisk patched boot was NOT flashed with fastboot (only booted).
[Nothing Phone 1] Ma3str0:
Could someone check the following two 3 things on 1.5.5:

- Are we still getting system freezes with the app [Speedify] (formerly also known as connectify)

- Now that Bluetooth has been changed; does the app [Sleep as Android] (aka "Sleep") still keep a consistent connection with wearables for use with smart alarm (for waking up in lite sleep state

- Is USB video out still not working ("locked")? (Desktop Mode in dev options)
[Nothing Phone 1] 1stStep:
Hi Another M1m

It seemed straightforward, unfortunately it seems that it didn't work:

I updated Magisk so that all 3 indications show 26103 (Latest and Installed for both Magisk and Application). I had to reboot for this IIRC.

Then I Uninstalled Magisk with the large red button choosing "Restore stock" or something like that (no need to reboot IIRC).

Then I updated NOS from the notification message, Download step was fast (144Mo), Install step was a bit longer, then Optimisation step was somewhat longer. In the end I didn't reboot: instead I went back to Magisk and I choose Install and selected the last bottom available option, the one dedicated to post-OTA update. Here I got a warning stating my data may ~become encrypted if they not yet~, what I validated. A short log displayed

target slot _a ....
...onto the other slot"

and in the end I hit the reboot button.

No error until now.

Now the phone rebooted twice (IIRC) and started fine.

I went to Settings to check the process success, but it is still 1.5.2. Also, Magisk shows as not installed (Install button beside both Magisk & Application).

It seems like the phone failed to boot the good slot and choose to boot the slot I updated from isn't it ?

Please what should I do now?
[Nothing Phone 1] AnotherM1m:
Update failed, happened to me with 1.5.2 and root.

Open Magisk, select install, you should only have one option, right? it's because you are not rooted anymore.

Then, proceed as it follows:

- Download with your pc magisk patched 1.5.4 boot img from here

- On your phone, open settings and restart the update procedure again

- When it asks you to reboot your phone, accept it and when it powers down, PRESS AND HOLD volume down until the phone boots up in bootloader

- Connect the phone to your pc

- Launch the command

fastboot boot *magisk patched boot image downloaded before*

- Wait for your phone to boot, after unlocking it you will see a notification about finishing the update, let it finish.

- Open magisk, select install then direct install, reboot when prompted

Done, let us know how it goes.
[Nothing Phone 1] 1stStep:
Right, as Method I only have option to "Select patch target file".

Just a question here to make me less ignorant: instead of following your step above (fastboot boot...), why should I not download Magisk-Patched_1.5.4_Boot.img with the phone (or upload from PC if yet DL'd) once OTA updated/rebooted, then Magisk install "Select patch target file" ? If I understand this I'll be less ignorant about the whole process.

Thanks for being there and quick answers man :cool:.
[Nothing Phone 1] AnotherM1m:
Select patch target file needs a stock boot img as input then creates the magisk patched boot img that will need to be booted with fastboot (it does not flash anything automatically).

Directly downloading the magisk patched boot skips this step.

I mean, if you want to create your own magisk patched boot you can no problem, the already patched boot img is just a comodity.
[Nothing Phone 1] 1stStep:
Right, I'll learn how to create my own Magisk patched boot later.

As for now, when I hit Settings/About the phone/Software informations(Nothing OS 1.5.2)/Nothing OS (1) (1.5.2) I get the screen that states "System update available" like it was at the end of the update process before, I mean directly with the reboot button I didn't hit before. I guess the update is already done here (seen from the booted slot), so I hit "Reboot" isn't it, and I go to bootloader, right ?
[Nothing Phone 1] AnotherM1m:
yes, remember to hold vol down when it's powering off until the bootloader boots
[Nothing Phone 1] 1stStep:
Hit reboot => "A problem happened when preparing reboot. Do retry later"

What's new:...

...

Reset the update
[Nothing Phone 1] AnotherM1m:
try again
[Nothing Phone 1] 1stStep:
Hitting "Reset the update"? The Reboot button isn't there anymore :confused:
[Nothing Phone 1] AnotherM1m:
yes
[Nothing Phone 1] 1stStep:
I didn't need: coming back for the 3rd time to the "System update available", now the button "Download and install" is there again.

...Downloading and installing the update

... Optimizing device (may be long)
[Nothing Phone 1] 1stStep:
"Reboot now" ? To bootloader (Vol Down held) ?
[Nothing Phone 1] AnotherM1m:
yes to both
[Nothing Phone 1] 1stStep:
Hit "Reboot now" => "Installing update of the system"... after a while self reboot, held VolDown until menu shows, select FastBoot Mode

fastboot boot Magisk-Patched_1.5.4_Boot.img

Self reboot

"Updating...

can take some minutes"

_____________________________________

Start OK... Settings : 1.5.4

Thanks so much AnotherM1m

But

Magisk :

"Additional installation is required

Your device requires to reinstall Magisk to work properly.

Thank you to reinstall Magisk from Application as the restore mode cannot work"

Screen faded while typing here, then when tapped on touch screen the message wasn't here. Instead I see:

Magisk Update

Installed 26.1 (26100)

Zygist No

Ramdisk Yes

Application Install

Last release ac4a33e (26103)

Installed release ac4a33e (26103)

Pakage com.topjohnwu.magisk

Uninstall Magisk​

So what? Update ?
[Nothing Phone 1] 1stStep:
Method:

* Select patch target file

* Direct install (recommanded)

* Install in unused space (after OTA update)

?
[Nothing Phone 1] AnotherM1m:
Direct install
[Nothing Phone 1] 1stStep:
(y) All fine.

How do we understand all this magic to be able to do it by ourselves ? I don't believe in magics, so I guess there is something to understand here behind.
[Nothing Phone 1] AnotherM1m:
Reading online, searching can help, mostly support thread are useful for providing infos.

Also readme and source code on github helps a lot.

Like incremental updates as the name suggest are features/lines of code that get added on your phone to already existing data

The phone checks that the data where the update is getting applied is valid at the start of the updating procedure.

If modified is not valid, so that's why restore to stock is always needed.

Now if you want to update to 1.5.5 the procedure is the same, open magisk, uninstall, restore stock images, proceed with the 1.5.5 update, when the reboot message comes on screen, press the home button, open magisk, install, select install on inactive slot (after ota update), reboot with magisk when asked.
[Nothing Phone 1] Sonalk:
[Deleted]
[Nothing Phone 1] AnotherM1m:
If the update fails you will boot with stock boot image, this will prevent any kind of magisk installation.

So you will be with the fw before the update without root, you can either update, then boot with fastboot magisk patched boot of the new fw and do direct install from magisk's app or boot into fastboot, boot the magisk patched boot img of the old fw, proceed with the update then open magisk and select install on inactive slot and reboot with magisk.
[Nothing Phone 1] 1stStep:
Did it, but same behaviour as on 152>154 upgrade: double reboot then find 154 still here and single install option in Magisk. Is it time I learn to build my own 155 patched ?
[Nothing Phone 1] AnotherM1m:
building your own patched boot img won't solve this issue.

next time try with the offline ota updater, not through the Settings' app.

just one question, when the message asking you to reboot the phone appears, do you press okay, cancel or the home button and then open magisk?
[Nothing Phone 1] 1stStep:
None: I don't remember there is any of "OK" or "Cancel" on the OTA update screen when finished (only a "Reboot now" button) and the NP1 has no home button, so I sweep the bottom blank bar upwards, then I go to Magisk.

The offline updater is *#*#682#*#* from dialer, isn't it?
[Nothing Phone 1] AnotherM1m:
That's correct

Yes
[Nothing Phone 1] 1stStep:
View attachment 5948205
[Nothing Phone 1] AnotherM1m:
yes, next time try with this.
[Nothing Phone 1] 1stStep:
Do I DL both stock and patched 1.5.5 from page 1?
[Nothing Phone 1] AnotherM1m:
you can go with just the patched one.
[Nothing Phone 1] 1stStep:
Okay, I put it in /sdcard/ota folder. Then I select "DIRECTLY APPLY OTA FROM SELECT" within Offline updater ?

Something I don't understand: this is only boot partition image. Then how is the phone OS updated ?

Or do I "Reboot now" from online updater then hold VolDown to bootloader and fastboot boot Magisk-Patched_1.5.5_Boot.img ?
[Nothing Phone 1] Ma3str0:
If someone could please check on these that would make everyones day.

If Bluetooth polling has changed in a way that is regressive then we may skip this update
[Nothing Phone 1] dav1234444:
can someone explain to me how to update from 1.5.4 to 1.5.5 (rooted)
[Nothing Phone 1] AnotherM1m:
To restore to stock boot image you have to open magisk, select uninstall then restore to stock

Then you do the procedure with offlineotaupdater which will update your phone.

When it asks for reboot do not select anything, go back to the home, open magisk, install, install on inactive slot.

The fastboot boot command is only if you are unrooted or lost root in the process if something goes wrong.

Im not using that app, im not using wearable, the force desktop mode can be activated,

cannot test if it works on usb tho.
[Nothing Phone 1] AnotherM1m:
Follow the procedure mentioned in message before this one.
[Nothing Phone 1] Ma3str0:
Thanks for the reply. The speedify and all connectify Inc bonding apps have been completely freezing the OS. I was also getting ever so slight but tolerable lag with other vpn bonding apps.

The desktop mode video out over USB c was working for a moment with some previous versions and then shuts off according to what I've read.

Some people are also reporting that slide quick app switching is broke and crashes the OS when invoked.

But REALLY need someone to confirm these things!

Edit: one last thing. Tap to lock in launcher seems to be non existent as well.
[Nothing Phone 1] dav1234444:
hi, i uninstalled magisk, tried to ota update error 20
[Nothing Phone 1] AnotherM1m:
Do not turn off or reboot your phone or you will lose root.

Have you installed a fastboot rom?
[Nothing Phone 1] dav1234444:
yeah about that i did it like 3 times already lol

i am doing it right now. I have to guess which partition is broken and flash the fastboot rom?
[Nothing Phone 1] 1stStep:
Am I wrong saying I have to fastboot after update failed with double reboot after Magisk reinstall+reboot?

I'm in the same case as after 1.5.2>1.5.4 when after double reboot the phone was still 1.5.2 and Magisk had a single install option. Root is lost ATM.
[Nothing Phone 1] AnotherM1m:
what are you flashing right now?

You don't need to flash the whole rom, just the broken partitions, you need root (so with fastboot boot a magisk patched image) and use the script talked about here:

https://xdaforums.com/t/nothing-phone-1-rom-ota-nothing-os-repo-of-nothing-os.4464039/#post-87101175

yes, if the updates fails in order to reobtain root you will have to use fastboot to launch a modified boot image
[Nothing Phone 1] dav1234444:
so yeah it was not a good idea i just bricked it.
[Nothing Phone 1] AnotherM1m:
bootloop? nothing logo with press any key to shutdown?
[Nothing Phone 1] dav1234444:
i fixed it by using the flash slot a idk if it was good what i did but it works.
[Nothing Phone 1] dav1234444:
also it seems like it fixed the error 20.

after the ota is done i flash the magisk boot to get my root back?
[Nothing Phone 1] AnotherM1m:
don't flash it, boot it

fastboot boot *magisk patched img*

Once the phone boots up, open magisk, select install then direct installation.

This lets magisk backup your stock boot and flash patched.

You can do ota updates without the need of a pc from now on.
[Nothing Phone 1] 1stStep:
Done :cowboy:. All updated now! Many thanks for huge support @AnotherM1m

Have a good [k]night and a long lazy week-end 🍻
[Nothing Phone 1] AnotherM1m:
No problem, thanks, you too
[Nothing Phone 1] caffeine01:
Okay, will report back with results
[Nothing Phone 1] dzjin:
Is there any way to extract the payload from A13 incremental and flash through Fastboot without NOS installed from the beginning?