-
Hi, I recently bought a Nothing Phone (3). Everything worked fine at first – I connected and rooted the phone (initially using APatch, then switched to Magisk) and successfully installed the OTA package. After performing a factory reset, I couldn’t reinstall the OTA – the phone kept prompting me to install it, but the installation would always fail with an error. Is there anything else I can try, or should I wait for a full OTA package to be released? Thanks again for your support and for all the work you’re doing here! Logs: |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
@Widmo, from your logs, I can see that you used the wrong script for flashing. Note that Correct link: flash_all.bat (Windows) |
Beta Was this translation helpful? Give feedback.
-
Refer to this. The device won't allow you to OTA update if the partitions are not stock or have been modified in any way. In such cases, flashing the stock images for the modified partitions will help. Simply performing factory resets won't help in this regard to the best of my knowledge. As always, please go through the documentation in the future. Cheers! |
Beta Was this translation helpful? Give feedback.
-
Thank you so much – the phone is back to life! I definitely feel lucky… or maybe Nothing is just a very forgiving brand 😉 Maybe it would be helpful to add a quick prompt like Thanks again for the help and the amazing work you're doing! -- Just to clarify – the OTA was applied on stock images.
and flashed, and re-flashed by original boot.img. Hope that helps clarify. Appreciate the guidance! |
Beta Was this translation helpful? Give feedback.
@Widmo, from your logs, I can see that you used the wrong script for flashing. Note that
spacewar
= Nothing Phone (1) &metroid
= Nothing Phone (3). Please refer to the correct script and always make sure to go through the readme in the future. In this case, you are fortunate that it did not get bricked. The device got stuck in a bootloop because some of the partitions were not flashed which is obvious in this case for the wrong script usage and the partition layouts being different for the respective models.Correct link: flash_all.bat (Windows)