What method do you follow to flash a Full OS Update?
(Not an OTA)
It would be helpfull for all the members to know where You got it, please.Great, Thanks for your tip I already got the image from another post.
s, though
![]()
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/forum.xda-developers.com
Any way to download it?New update OS 1.1.7
Source: https://www.reddit.com/r/NothingTech/comments/z3j6o0
View attachment 5769129
1.1.7 Global (Spacewar) incremental build.
I need EAA sorry1.1.7 (Spacewar) incremental build.
Oh that's why mine wouldn't work
Someone could explain how to update from 1.1.6 rooted to.1.1.7 without losing root? Thank you
Does anyone know if i can install a global version on my european device from flashing super?
Some time ago I was in brick and since I didn't know the super partition, I tried this and it didn't work, but in bootloader mode, my device name changed from "spacewar" to "lahaina". This is because the global device name is "lahaina" and the European one is "spacewar"?Puede cambiar de versión, pero no se recomienda encarecidamente, puede bloquear su dispositivo, especialmente el día que desea volver a bloquear el gestor de arranque (por ejemplo, para revender, cambiar su dispositivo).
Si es solo para tener una actualización 2 semanas antes de EEA, le aconsejo que no lo haga, hay alguna ventaja para pasar a Global en lugar de EEA.
Some time ago I was in brick and since I didn't know the super partition, I tried this and it didn't work, but in bootloader mode, my device name changed from "spacewar" to "lahaina". This is because the global device name is "lahaina" and the European one is "spacewar"?
And why is it a problem when relocking the bootloader exactly? Wouldn't it just reinstall the European version and relock bootloader?Yes codename are here for recognize model version. Mine is effectivelly "Spacewar" in Fastboot/Bootloader mode, i'm on EEA version.
And why is it a problem when relocking the bootloader exactly? Wouldn't it just reinstall the European version and relock bootloader?
Can you relock it when using custom ROMs? I kind of need safetynet to passYes, if you want, it's advised to put the original version for relock.
@Phon3nX
Reading through this thread (and other threads in this forum), I see a lot of users facing issues updating their devices, especially with root. Even I have faced issues with updating and I try different methods to fix it, but there is still no single method that works 100% of the time. Sometimes local update method works, sometimes sideloading with ADB, etc.
It would be great if you could create a guide for updating their devices with root, possibly with all the different methods and troubleshooting methods. I do not mean unlocking or rooting, but updating NP1 by keeping root access. Sure, there are a lot of individual posts on this topic spread across this forum, as threads and as comments in threads like these, but I think it would be better to have it in one of the reserved sections in the original guide thread.
Thank you and kudos for the great job you do here.![]()
I am making it now.
getprop ro.product.system.name
.\fastboot boot Magisk_Patched_XXX.img
Thanks for the tip! This did the trick, and I'm now happily re-rooted on 1.1.3I was not even aware of the local system update wizard...
.\fastboot boot magisk_patched-2XXXX_XXXXX.img