Exodusnick
Senior Member
I would, but I can't. My device is not rooted.
I can't give you the boot.img from here either.
Just wait until you get it via OTA it will be distributed step by step to all.
I would, but I can't. My device is not rooted.
Hello, which country? Thanks
Germany
How can I know if mine is global or European being in Paranoid Android?There is no EU full package for 1.1.4.
You are sure you did not changed your device to global?
Please check via ADB Shel or Terminal:
getprop ro.product.system.name
This will return “SpacewarEEA” if the device comes with the European firmware. On global models, the output should be "Spacewar" only.
I guess this means you are on paranoid.How can I know if mine is global or European being in Paranoid Android?
With that command it return me "aospa_phone1"
I think it's possible. I bought a EEA Nothing, when I bricked my phone and restored it like I wrote it in the Unbrick thread, my phone switched to global. Plus, all the custom roms doesn't care about being EEA or global. So we can pretty much assume this is not importantIt's still not clear to me if it's possible to switch from EEA to Global.
From my understanding, EEA is missing call recording features.
Is it possible to sideload 1.1.6 Global over 1.1.4 EEA for instance?
Thank you everything works OK!
It's works fine! Thanks!
You can contact me by PM only.
- The member(s) must be active on the threads,
- Have a minimum of knowledge about Android 12, or even 13.
- You need to be available and regular. Not necessarily every day, but at least once a week, ideally 2 to 3 times a week.
Can you get it from here - it seems they have a full version of 1.1.6 Global:
Great, Thanks for your tips, though I already got the image from another post.Can you get it from here - it seems they have a full version of 1.1.6 Global:
![]()
Nothing Phone 1 update tracker: Here are all the official Nothing OS builds to download and install
We tracked down the updates so you don't have towww.xda-developers.com
unified means, that both variants are in 1 Update/FW Package... so the Update is the same and installs the files according your device variant. Thats why you (as me) see EEA in the build number.That does not seem to be the case. I am on 1.5.2 EEA (Spacewar-T1.5-230213-2131-EEA).
View attachment 5875097
I think it only unified when flashing beta firmware.
@AnotherM1m maybe OP needs an update regarding this, but please double check first.
I've always restarted from magisk but from .3 to .3.hotfix i've encountered a bootloop so that's the reason im talking about restarting with the settings app.Can't confirm. I always reboot from the magisk interface after using OTA installation method. It doesn't make much sense, but I've had cases where using the settings update menu's reboot option somehow lead to magisk not being installed.
Unified means the same zip can be used for both version of the phone to update the software.That does not seem to be the case. I am on 1.5.2 EEA (Spacewar-T1.5-230213-2131-EEA).
View attachment 5875097
I think it only unified when flashing beta firmware.
@AnotherM1m maybe OP needs an update regarding this, but please double check first.
Sorry, if you need support with the unbrick tool please post your message in that thread, here we offer support for the installation of updatesI don't know what I'm doing wrong, but I can't start the phone in edl mode
English please but thanks for the heads upDalší aktualizace.... Hotfix
Informace jsou z Facebooku!
Ps: Ještě jsem neobdržel aktualizaci 1.5.3! Česká republika EU
![]()
Downloading artifacts and installing the apk should be the right way to go, right? Because after installing apks from actions magisk manager app crashes.I don't have a Nothing phone but I have some suggestions:
Did anyone try using latest bleeding-edge build of Magisk from: https://github.com/topjohnwu/Magisk/actions ?
If it still has issues I suggest opening an issue on the repo to notify topjohnwu.
No problem, i really just want a stable phone experience.Thank you for trying out the latest build. Can you open an issue on the repo reporting this crash problem?
Edit: someone already did so https://github.com/topjohnwu/Magisk/issues/6780
getprop ro.product.name
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