General Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS

Search This thread
By:
Advanced…
1stStep

1stStep

Senior Member
Mar 27, 2012
77
5
Pau
Samsung Galaxy Note 3
Nothing Phone 1
Hi @AnotherM1m
Sorry for late reply.
AnotherM1m said:
@1stStep sorry i linked you the wrong 1.1.8 eea incremental
Click to expand...
Click to collapse
Thanks. Is the quoted link below the one for me too from EEA117noFix?
AnotherM1m said:
@jskeletti sorry try this 1.1.8

Click to expand...
Click to collapse

AnotherM1m said:
....sideloading zip and keeping root is still a little bit clunky but it's doable, you can try searching this thread for guides
Click to expand...
Click to collapse
Is it the guide you refer to? They say to sideload only full updates zip on rooted phones ("Incremental...can be only applied on an untouched base."), but it's nearly 8 months old on NP1 birth days. If I follow this recommendation and your own IIUC, my very first job is to uninstall Magisk, isn't it? Do I do this from within Magisk App with "Uninstall Magisk" option ? Is there anything to do before/after, e.g. reboot and/or relock bootloader so that the phone is back to stock boot? Then why should I sideload an update instead of just applying updates from the NOS main regular popup notification? Sorry for silly questions, surely they show I'm missing major thing but I feel completely puzzled with these tenths of threads.
Then as there isn't full ROM after 1.1.7 according to post1 in this thread every here lost root in the update process :cry:? I hardly figure this :unsure:.
I read the latest posts since my question and see many have huge trouble with 1.5.3, so is your advice for newbs is to stick to 1.5.2?
I didn't try to update from the normal method. Is it at risk for the health of the phone and data (I just copied everything from "Internal shared" storage to a PC but there were files that could not be copied)? Nothing that would prevent other way like sideload?
Many thanks for your advice in post
AnotherM1m said:
.... If you want to follow this guide from 1.1.7 -> 1.1.8 -> 1.5.2 you should do, 1 2 3 4 2 3 4 5
Click to expand...
Click to collapse
I feel it is the definitive ultimate road.
Bye bye
 
Last edited:
A

AnotherM1m

Senior Member
Nov 20, 2016
184
96
1stStep said:
Hmmm, I fell in a trap : no Magisk-Patched_EEA_1.1.8_Boot.img around. I'm stuck at bootloader not knowing what to do now but searching the web
Click to expand...
Click to collapse
Do
Fastboot boot (not flash, boot)
and then use 1.1.7 no fix eea magisk patched boot img

Yes, use the dialer method, and you can use ota zips, not only full ones.

Yes, before any update you open magisk, press uninstall, restore stock images DO NOT REBOOT OR RELOCK THE BOOTLOADER and apply the update while the phone is still running. When it boots up hold vol down for bootloader and boot the magisk patched boot zip of the newer version, then when the phone boots up do not do anything and just apply the other ota update

Do not update to 1.5.3 if you want to use a rooted phone
 
  • Like
Reactions: 1stStep
1stStep

1stStep

Senior Member
Mar 27, 2012
77
5
Pau
Samsung Galaxy Note 3
Nothing Phone 1
Many thanks for quick reply man
Code: 
adb shell
Spacewar:/ $ getprop | grep -e "1\.1\." -e "\[ro..*211.*" -e "\ro..*230.*" -e "\[ro..*166.*" -e "\[ro..*167.*"                                                      
[ro.bootimage.build.date.utc]: [1673529120]
[ro.bootimage.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.build.date.utc]: [1673514747]
[ro.build.description]: [SpacewarEEA-user 12 SKQ1.211230.001 1673511228 release-keys]
[ro.build.display.id]: [Spacewar-S1.1-230112-1613EEA]
[ro.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.build.id]: [SKQ1.211230.001]
[ro.build.version.incremental]: [1673511228]
[ro.nothing.version.id]: [1.1.8]
[ro.odm.build.date.utc]: [1673529120]
[ro.odm.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.odm.build.version.incremental]: [1673511228]
[ro.product.build.date.utc]: [1673514747]
[ro.product.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.product.build.id]: [SKQ1.211230.001]
[ro.product.build.version.incremental]: [1673511228]
[ro.system.build.date.utc]: [1673514747]
[ro.system.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.system.build.id]: [SKQ1.211230.001]
[ro.system.build.version.incremental]: [1673511228]
[ro.system_ext.build.date.utc]: [1673514747]
[ro.system_ext.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.system_ext.build.id]: [SKQ1.211230.001]
[ro.system_ext.build.version.incremental]: [1673511228]
[ro.vendor.build.date.utc]: [1673529120]
[ro.vendor.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.vendor.build.id]: [SKQ1.211230.001]
[ro.vendor.build.version.incremental]: [1673511228]
Spacewar:/ $
This gave me some time to fill up the gasoline tank of the car before riots here in France 🔥🎆🧑‍🚒 prevent me to go to job tomorrow. Now I rebooted fine and I'm pop'd up to upgrade to N.OS 1.5/A13 with no more precision, they only say good things about it beside size:1.25GB... hope this is 1.5.2

BTW, do you advice I build my own Magisk_Patched_EEA_1.5.2_Boot.img ?
 
A

AnotherM1m

Senior Member
Nov 20, 2016
184
96
1stStep said:
Many thanks for quick reply man
Code: 
adb shell
Spacewar:/ $ getprop | grep -e "1\.1\." -e "\[ro..*211.*" -e "\ro..*230.*" -e "\[ro..*166.*" -e "\[ro..*167.*"                                                     
[ro.bootimage.build.date.utc]: [1673529120]
[ro.bootimage.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.build.date.utc]: [1673514747]
[ro.build.description]: [SpacewarEEA-user 12 SKQ1.211230.001 1673511228 release-keys]
[ro.build.display.id]: [Spacewar-S1.1-230112-1613EEA]
[ro.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.build.id]: [SKQ1.211230.001]
[ro.build.version.incremental]: [1673511228]
[ro.nothing.version.id]: [1.1.8]
[ro.odm.build.date.utc]: [1673529120]
[ro.odm.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.odm.build.version.incremental]: [1673511228]
[ro.product.build.date.utc]: [1673514747]
[ro.product.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.product.build.id]: [SKQ1.211230.001]
[ro.product.build.version.incremental]: [1673511228]
[ro.system.build.date.utc]: [1673514747]
[ro.system.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.system.build.id]: [SKQ1.211230.001]
[ro.system.build.version.incremental]: [1673511228]
[ro.system_ext.build.date.utc]: [1673514747]
[ro.system_ext.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.system_ext.build.id]: [SKQ1.211230.001]
[ro.system_ext.build.version.incremental]: [1673511228]
[ro.vendor.build.date.utc]: [1673529120]
[ro.vendor.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:12/SKQ1.211230.001/1673511228:user/release-keys]
[ro.vendor.build.id]: [SKQ1.211230.001]
[ro.vendor.build.version.incremental]: [1673511228]
Spacewar:/ $
This gave me some time to fill up the gasoline tank of the car before riots here in France 🔥🎆🧑‍🚒 prevent me to go to job tomorrow. Now I rebooted fine and I'm pop'd up to upgrade to N.OS 1.5/A13 with no more precision, they only say good things about it beside size:1.25GB... hope this is 1.5.2

BTW, do you advice I build my own Magisk_Patched_EEA_1.5.2_Boot.img ?
Click to expand...
Click to collapse
For sure it's 1.5.2

You can use this one, made it myself and tested by multiple users.

magisk_patched-25200_TrVLh.img

drive.google.com drive.google.com
 
1stStep

1stStep

Senior Member
Mar 27, 2012
77
5
Pau
Samsung Galaxy Note 3
Nothing Phone 1
It was huge! Weak network here. Now I got the update installed, System optimization stage done, ready to reboot, but didn't reboot yet.
Is it mandatory to immediately reboot to recovery then from PC "adb fastboot boot patched.img" or can I reboot now the normal way and postpone the patched boot/root for later ? Your magisk_patched-25200_TrVLh.img and the Magisk-Patched_1.5.2_Boot.img one from post #2 has not the same sha1sum hash. I wanted to have a look at my Magisk app but the icon has changed (since uninstalled from within?-didn't notice at the time) and says "An upgrade of Magisk Manager to full version is required to complete installation. Do you wish...?"
In the lap time I grabbed the ota.zip from "logcat|grep zip" => ... https://android.googleapis.com/packages/ota-api/package/6718db370773ad0191b970df545f54c4163a014e.zi ... *
Someone said it is better to build the patched-boot.img from our own original payload.bin because phones may have hardware differences. Any chance I could extract this 1.5.2-stock-boot.img from the payload.bin in the incremental ota zip?

* silly: it was available here at the NP1 tracker 😵‍💫
 
Last edited:
A

AnotherM1m

Senior Member
Nov 20, 2016
184
96
1stStep said:
It was huge! Weak network here. Now I got the update installed, System optimization stage done, ready to reboot, but didn't reboot yet.
Is it mandatory to immediately reboot to recovery then from PC "adb fastboot boot patched.img" or can I reboot now the normal way and postpone the patched boot/root for later ? Your magisk_patched-25200_TrVLh.img and the Magisk-Patched_1.5.2_Boot.img one from post #2 has not the same sha1sum hash. I wanted to have a look at my Magisk app but the icon has changed (since uninstalled from within?-didn't notice at the time) and says "An upgrade of Magisk Manager to full version is required to complete installation. Do you wish...?"
In the lap time I grabbed the ota.zip from "logcat|grep zip" => ... https://android.googleapis.com/packages/ota-api/package/6718db370773ad0191b970df545f54c4163a014e.zip ... *
Someone said it is better to build the patched-boot.img from our own original payload.bin because phones may have hardware differences. Any chance I could extract this 1.5.2-stock-boot.img from the payload.bin in the incremental ota zip?

* silly: it was available here at the NP1 tracker 😵‍💫
Click to expand...
Click to collapse
It's not mandatory but booting unrooted with an unlocked bootloader can trigger the device certifications (widevine L3 for netflix) to be revoked which is kind of an hussle to deal with

The one in the main page does not work and the mantainer has abandoned its job

The one i linked is the one i made because others' were not working and it works for many.

Update magisk manager
 
  • Like
Reactions: 1stStep
1stStep

1stStep

Senior Member
Mar 27, 2012
77
5
Pau
Samsung Galaxy Note 3
Nothing Phone 1
Done :cool:
:coffee:
I rebooted right after the ota update 118->152, did fastboot boot your-patched-1.5.2-Boot.img, self reboot, went to remaining Magisk (Manager, brown icon) app, updated it to full, then choose "Update" and selected the middle option direct (recommended)... from memory ;-)

As you can see below the phone is now 1.5.2. You guess I didn't yet explore the new things and if everything works as intended. Is it normal we still see references to EEA? I though Global|EEA were unified from now... maybe only the boot?
Code: 
Spacewar:/ $ getprop | grep -e "1\.[15]\." -e "\[ro..*16[67].*" -e "\ro..*211.*" -e "\[ro..*213.*" -e "\[ro..*230.*" -i -e eea               [ro.boot.hardware.sku]: [EEA]
[ro.boot.product.hardware.sku]: [EEA]
[ro.bootimage.build.date.utc]: [1676299311]
[ro.bootimage.build.fingerprint]: [Nothing/Spacewar/Spacewar:11/RKQ1.211222.001/2302132131:user/release-keys]
[ro.build.date.utc]: [1676295119]
[ro.build.description]: [SpacewarEEA-user 13 TKQ1.220915.002 2302132131 release-keys]
[ro.build.display.id]: [T1.5-230213-2131]
[ro.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:13/TKQ1.220915.002/2302132131:user/release-keys]
[ro.build.nothing.feature.diff.product.SpacewarEEA]: [0x0]
[ro.build.version.incremental]: [2302132131]
[ro.nothing.version.id]: [1.5.2]
[ro.odm.build.date.utc]: [1676299311]
[ro.odm.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:11/RKQ1.211222.001/2302132131:user/release-keys]
[ro.odm.build.version.incremental]: [2302132131]
[ro.oem.key1]: [EEA]
[ro.product.build.date.utc]: [1676295119]
[ro.product.build.fingerprint]: [Nothing/qssi/qssi:13/TKQ1.220915.002/2302132131:user/release-keys]
[ro.product.build.version.incremental]: [2302132131]
[ro.product.name]: [SpacewarEEA]
[ro.product.odm.name]: [SpacewarEEA]
[ro.product.vendor.name]: [SpacewarEEA]
[ro.system.build.date.utc]: [1676295119]
[ro.system.build.fingerprint]: [Nothing/qssi/qssi:13/TKQ1.220915.002/2302132131:user/release-keys]
[ro.system.build.version.incremental]: [2302132131]
[ro.system_ext.build.date.utc]: [1676295119]
[ro.system_ext.build.fingerprint]: [Nothing/qssi/qssi:13/TKQ1.220915.002/2302132131:user/release-keys]
[ro.system_ext.build.version.incremental]: [2302132131]
[ro.vendor.build.date.utc]: [1676299311]
[ro.vendor.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:11/RKQ1.211222.001/2302132131:user/release-keys]
[ro.vendor.build.id]: [RKQ1.211222.001]
[ro.vendor.build.version.incremental]: [2302132131]
Spacewar:/ $

Many thanks for kind and quick support
 
A

AnotherM1m

Senior Member
Nov 20, 2016
184
96
1stStep said:
Done :cool:
:coffee:
I rebooted right after the ota update 118->152, did fastboot boot your-patched-1.5.2-Boot.img, self reboot, went to remaining Magisk (Manager, brown icon) app, updated it to full, then choose "Update" and selected the middle option direct (recommended)... from memory ;-)

As you can see below the phone is now 1.5.2. You guess I didn't yet explore the new things and if everything works as intended. Is it normal we still see references to EEA? I though Global|EEA were unified from now... maybe only the boot?
Code: 
Spacewar:/ $ getprop | grep -e "1\.[15]\." -e "\[ro..*16[67].*" -e "\ro..*211.*" -e "\[ro..*213.*" -e "\[ro..*230.*" -i -e eea               [ro.boot.hardware.sku]: [EEA]
[ro.boot.product.hardware.sku]: [EEA]
[ro.bootimage.build.date.utc]: [1676299311]
[ro.bootimage.build.fingerprint]: [Nothing/Spacewar/Spacewar:11/RKQ1.211222.001/2302132131:user/release-keys]
[ro.build.date.utc]: [1676295119]
[ro.build.description]: [SpacewarEEA-user 13 TKQ1.220915.002 2302132131 release-keys]
[ro.build.display.id]: [T1.5-230213-2131]
[ro.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:13/TKQ1.220915.002/2302132131:user/release-keys]
[ro.build.nothing.feature.diff.product.SpacewarEEA]: [0x0]
[ro.build.version.incremental]: [2302132131]
[ro.nothing.version.id]: [1.5.2]
[ro.odm.build.date.utc]: [1676299311]
[ro.odm.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:11/RKQ1.211222.001/2302132131:user/release-keys]
[ro.odm.build.version.incremental]: [2302132131]
[ro.oem.key1]: [EEA]
[ro.product.build.date.utc]: [1676295119]
[ro.product.build.fingerprint]: [Nothing/qssi/qssi:13/TKQ1.220915.002/2302132131:user/release-keys]
[ro.product.build.version.incremental]: [2302132131]
[ro.product.name]: [SpacewarEEA]
[ro.product.odm.name]: [SpacewarEEA]
[ro.product.vendor.name]: [SpacewarEEA]
[ro.system.build.date.utc]: [1676295119]
[ro.system.build.fingerprint]: [Nothing/qssi/qssi:13/TKQ1.220915.002/2302132131:user/release-keys]
[ro.system.build.version.incremental]: [2302132131]
[ro.system_ext.build.date.utc]: [1676295119]
[ro.system_ext.build.fingerprint]: [Nothing/qssi/qssi:13/TKQ1.220915.002/2302132131:user/release-keys]
[ro.system_ext.build.version.incremental]: [2302132131]
[ro.vendor.build.date.utc]: [1676299311]
[ro.vendor.build.fingerprint]: [Nothing/SpacewarEEA/Spacewar:11/RKQ1.211222.001/2302132131:user/release-keys]
[ro.vendor.build.id]: [RKQ1.211222.001]
[ro.vendor.build.version.incremental]: [2302132131]
Spacewar:/ $

Many thanks for kind and quick support
Click to expand...
Click to collapse
No problem.

It's the update process that got unified, there is still the separation between devices and on how they treat your data.

So you'll always see spacewareea
 
Pepousek67

Pepousek67

Senior Member
Mar 13, 2012
408
166
Karlovy Vary
Samsung Galaxy Watch 4
Another update.... Hotfix

Information is from Facebook!

Ps: I haven't received the 1.5.3 update yet! Czech Republic EU

336693406_196004813129753_965419137943256010_n.jpg
 
Last edited:
  • Like
Reactions: neilphetamine and aleqa
A

AnotherM1m

Senior Member
Nov 20, 2016
184
96
Pepousek67 said:
Další aktualizace.... Hotfix
Informace jsou z Facebooku!
Ps: Ještě jsem neobdržel aktualizaci 1.5.3! Česká republika EU
336693406_196004813129753_965419137943256010_n.jpg
Click to expand...
Click to collapse
English please but thanks for the heads up

1.5.3 HOTFIX just released
I COULD NOT update and keep root. I did magisk ota installation but at reboot i was bootlooping.

So i did the update as stock with unlocked bootloader and at reboot i held vol down to boot into bootloader, booted NOT FLASHED, BOOTED the old 153 (not hotfix) magisk patched boot and did direct installation

Everything seems to be working fine, i'll let you know if i encounter any freeze.
 
  • Like
Reactions: Pepousek67, aleqa and gmx2pt
W

whamslambam56

New member
Mar 21, 2023
3
0
Guys, I may have found the fix to 1.5.3 with root. (Will update if freeze comes back. however its been an hr with no freeze so that's better than before where it freezes seconds after boot)

Many are not going to like this(including me) but, you will lose internal storage data so make sure to get a usb c flash drive or backup to pc.

What I have done is:
  1. Factory Data Reset.
  2. Wait for first reboot to reach erasing data screen. (Watch carefully this screen basically just flashes by. Pic is attached)
  3. Immediately after screen goes black from erasing data screen hold only volume down button until fastboot shows.
  4. Flash Magisk patched boot for 1.5.3 or 1.5.3 hotfix, depending on which you are on.
    • For Pwrshell: "./fastboot flash boot Magisk Patched 1.5.3.fix.img"
    • For cmd: "fastboot flash boot Magisk Patched 1.5.3.fix.img"
  5. System should boot, then proceed through setup.
  6. Open Magisk and click ok to reboot.
  7. Then system should boot without any freezes.
 

Attachments

  • image_2023-03-20_234609058.png
    image_2023-03-20_234609058.png
    22.7 KB · Views: 50
Last edited:
kumar akarsh

kumar akarsh

Senior Member
Dec 21, 2012
491
300
whamslambam56 said:
Guys, I may have found the fix to 1.5.3 with root. (Will update if freeze comes back. however its been an hr with no freeze so that's better than before where it freezes seconds after boot)

Many are not going to like this(including me) but, you will lose internal storage data so make sure to get a usb c flash drive or backup to pc.

What I have done is:
  1. Factory Data Reset.
  2. Wait for first reboot to reach erasing data screen. (Watch carefully this screen basically just flashes by. Pic is attached)
  3. Immediately after screen goes black from erasing data screen hold only volume down button until fastboot shows.
  4. Flash Magisk patched boot for 1.5.3 or 1.5.3 hotfix, depending on which you are on.
    • For Pwrshell: "./fastboot flash boot Magisk Patched 1.5.3.fix.img"
    • For cmd: "fastboot flash boot Magisk Patched 1.5.3.fix.img"
  5. System should boot, then proceed through setup.
  6. Open Magisk and click ok to reboot.
  7. Then system should boot without any freezes.
Click to expand...
Click to collapse
observe for longer. It will come back. Connect charger. let it charge for 30-40mins. Then start opening heavy apps. camera, social media apps, games if u have them. And then observe freeze.
 
W

whamslambam56

New member
Mar 21, 2023
3
0
kumar akarsh said:
observe for longer. It will come back. Connect charger. let it charge for 30-40mins. Then start opening heavy apps. camera, social media apps, games if u have them. And then observe freeze.
Click to expand...
Click to collapse
Well.. it's been 10 hours. I have all apps logged in and reinstalled my modules. I don't get any freeze. But i'll let you guys know after a week how it goes.
 
Adrian312

Adrian312

Senior Member
Jan 12, 2009
352
73
Bratislava
whamslambam56 said:
Guys, I may have found the fix to 1.5.3 with root. (Will update if freeze comes back. however its been an hr with no freeze so that's better than before where it freezes seconds after boot)

Many are not going to like this(including me) but, you will lose internal storage data so make sure to get a usb c flash drive or backup to pc.

What I have done is:
  1. Factory Data Reset.
  2. Wait for first reboot to reach erasing data screen. (Watch carefully this screen basically just flashes by. Pic is attached)
  3. Immediately after screen goes black from erasing data screen hold only volume down button until fastboot shows.
  4. Flash Magisk patched boot for 1.5.3 or 1.5.3 hotfix, depending on which you are on.
    • For Pwrshell: "./fastboot flash boot Magisk Patched 1.5.3.fix.img"
    • For cmd: "fastboot flash boot Magisk Patched 1.5.3.fix.img"
  5. System should boot, then proceed through setup.
  6. Open Magisk and click ok to reboot.
  7. Then system should boot without any freezes.
Click to expand...
Click to collapse
so basically that's like a telegram "workaround" which I (and I guess many others) would like to avoid = factory reset.... Anyway - if that works for you - good for you ;)
 
You must log in or register to reply here.

Similar threads

herna
Development Paranoid Android Topaz 2 - Nothing phone (1)
Replies
307
Views
48K
nontheoretical
nontheoretical
A
Question Gcam for Nothing phone 1
Replies
47
Views
31K
S
samflynn777
Pho3nX
How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1)
Replies
237
Views
31K
C
cibai7181
Sib64
  • Sticky
Question [HELP THREAD][Nothing Phone (1)] Ask Any Question, Noob Friendly
Replies
348
Views
28K
wolfLzoro
wolfLzoro
ot_inc
General [ROM][Restore][Unbrick] Nothing OS v1.5.4 Global/EEA Fastboot ROM(Full ROM) & boot.img & QFIL ROM (EDL)
Replies
146
Views
19K
A
AnotherM1m

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 3
    ferretmc
    ferretmc
    panni said:
    Yep, worked.

    tl;dr, if you're getting error 20 or can't update to 1.5.4 (worked for me, might not actually be MGLRU Disabler's fault; rather a borked boot image):
    - disable MGLRU Disabler V3
    - adb reboot bootloader
    - fastboot flash stock 1.5.3 hotfix boot
    - fastboot boot patched 1.5.3 hotfix boot
    - install OTA
    - install magisk into inactive slot/OTA; reboot via magisk

    profit.

    Thanks @AnotherM1m as always!

    Edit: No issues; root works; no MGLRU fixes necessary. They've actually listened. Baffling.
    Click to expand...
    Click to collapse

    Thank you so much for pointing out the solution.
    For me it actually worked with my SpacewarEEA coming from 1.5.3 hotfix with magisk in this order:
    1. set Timezone to China/Shanghai
    2. disable MGLRU v3
    3. adb reboot bootloader
    4. fastboot flash boot <stock 1.5.3 fix boot>.img
    5. boot to system
    6. dial *#*#682#*#* and select the 1.5.4. OTA Image
    7. ...wait for it to finish (~10 mins)
    8. adb reboot bootloader
    9. fastboot boot <magisk_1.5.4>.img
    10. install magisk through the app
    cheers
    View
    3
    A
    AnotherM1m
    nothing.tech/blogs/news/android-14-beta

    Two things: Download server is really slow on eu west, ota_diff_20230428_222944_20230428_201717.zip the rollback file could be 154 full, i'll look into it tomorrow

    Update: it's a rollback zip to 154 from UpsideDownCake, i don't know which nos version is this beta.

    Upsate2: This beta has no Nothing OS version set. The easter egg's still A13's. Android's version set to UpsideDownCake.
    View
    3
    C
    Chaotick
    Got 1.5.4 update in EU Poland :)
    View
    2
    A
    AnotherM1m
    Hello!

    For everyone having problems updating with offline ota updater because of error 20, I've made a script that easily copies logs from the phone into the sdcard.

    GitHub - LukeSkyD/NP1-OtaTxtExtractor: Bash script that searches for ota.txt and copies it to /sdcard, only tested on NP1

    Bash script that searches for ota.txt and...
    github.com github.com

    You need root to run this script.

    The logs can be then copied here to find out why things are not working.

    @Ostry10
    View
    1
    A
    AnotherM1m
    svaethier said:
    Yes I am on 154 fastboot rom currently
    Click to expand...
    Click to collapse
    I wrote to you privately

    EDIT: user reported flashing my uefisecapp and being able to update! It's the right direction to fix fastboot roms not updating.
    Now we need uefisecapp for 152 and bluetooth (and maybe other partitions) for 153
    View
  • 26
    A
    AnotherM1m

    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 the Phone(1), you can post in     this open topic​

    The Nothing Phone(1) was officially unveiled on July 12th and we know a good part of the specifications of the smartphone.

    • Phone(1) - Model : A063
    • Initial Code Name : Abra / Global Name : Lahaina / EEA Name = Spacewar
    • Android 12

    Platform =>OS - Android 12 - Nothing OS
    Chipset => Qualcomm SM7325-AE Snapdragon 778G+ 5G (6 nm)
    1. CPU => Octa-core (1x2.5 GHz Cortex-A78 & 3x2.4 GHz Cortex-A78 & 4x1.8 GHz Cortex-A55)
    2. GPU => Adreno 642L
    Memory => 8Go & 12Go
    Storage => 128Go & 256Go - UFS 3.1 - no card slot
    Sim => Dual SIM (Nano-SIM, dual stand-by)

    Network Technology => GSM / HSPA / LTE / 5G
    1. 2G Bands => GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2
    2. 3G Bands => HSDPA 800 / 850 / 900 / 1700(AWS) / 1900 / 2100
    3. 4G Bands => 1, 2, 3, 4, 5, 7, 8, 12, 17, 18, 19, 20, 26, 28, 32, 34, 38, 39, 40, 41, 66
    4. 5G Bands => 1, 3, 5, 7, 8, 20, 28, 38, 40, 41, 77, 78 SA/NSA
    5. Speed => HSPA 42.2/5.76 Mbps, LTE-A, 5G

    Comms => WLAN => Wi-Fi 802.11 a/b/g/n/ac/6, dual-band, hotspot
    1. Bluetooth => 5.2, A2DP, LE
    2. GPS => Yes, with A-GPS. Up to dual-band: GLONASS (1), BDS (2), GALILEO (1), QZSS (1)
    3. NFC => Yes
    4. Radio => Unspecified
    5. USB => USB Type-C 2.0, USB On-The-Go
    Dimensions => 159.2 x 75.8 x 8.3 mm - 6.27 x 2.98 x 0.33 in
    Weight => 193.5 g - 6.84 oz
    Build => Glass front (Gorilla Glass 5), glass back (Gorilla Glass 5), aluminum frame

    Dispaly => OLED, 1B colors, 120Hz, HDR10+, 500 nits (typ), 1200 nits (peak)
    Size => 6.55 inches = 103.6 cm2 (~85.8% screen-to-body ratio)
    Resolution => 1080 x 2400 pixels, 20:9 ratio (~402 ppi density)

    Battery => Li-Po 4500 mAh, non-removable
    => CHARGING => Fast charging 33W, 50% in 30 min, 100% in 70 min (advertised)
    => Wireless charging 15W
    => Reverse wireless charging 5W
    => Power Delivery 3.0
    => Quick Charge 4.0

    Protection => Corning Gorilla Glass 5

    Camera => 50 MP Main Camera, Dual
    => 50 MP, f/1.9, 24mm (wide-angle), 1/1.56", 1.0µm, PDAF, OIS
    => 50 MP, f/2.2, 114˚ (ultra wide angle), 1/2.76", 0.64µm
    => LED flash, panorama, HDR features
    => Video recording [email protected], [email protected]/60fps, gyro-EIS, live HDR
    => Front Camera, Selfie 16 MP, Single
    => Features -16 MP, f/2.5, (wide-angle), 1/3.1", 1.0µm
    => Video recording [email protected]

    Others =>
    1. Multiple LED lights on the back (notifications, charging progress, camera fill light)
    2. Blinking red light on the back (video recording indicator)
    3. IP53 - splash, water and dust resistant
    4. 3.5mm jack => No
    5. Loudspeaker => Yes, with stereo speakers
    6. Sensors => Fingerprint (under display, optical), accelerometer, proximity, gyro, compass

    Android_14_1200x675_a45ea069-8c30-4396-bd9c-050ae4443dfb.jpg


    LATEST NEWS (dd/mm notation is used)

    Nothing just published this blog post:

    nothing.tech/blogs/news/android-14-beta

    It's really early in development, read carefully the post if you want to try Android 14 on Nothing Phone (1)
    Code: 
    error code -2: pre-build-incremental is different from ro.build.date.utc
    This is what many people are reporting while trying to update to 1.5.3.HOTFIX or 1.5.4

    Go to Settings, System, Date and Time, remove automatic time zone and set it manually to China, Shangai was the only option working for me.
    Now reopen the offline updater and try starting the update once again

    Don't forget to set automatic time zone again after you are done!
    The cause of the instability of rooted system with 1.5.3(/hotfix) is the implementation of MGLRU, a new way to handle processes and memory while the phone is under pressure.
    This module should fix the issue:

    GitHub - LukeSkyD/NP1-MGLRU-FIX: Magisk module to fix freezes and crashes on NP1 phone

    Magisk module to fix freezes and crashes on...
    github.com github.com

    If you encounter freezes or crashes user @gwolfu made this module which script runs every 30s to force MGLRU to stay disabled:

    GitHub - gwolf2u/MGLRU-Disabler

    Contribute to gwolf2u/MGLRU-Disabler...
    github.com github.com

    ​
    NOTHING OS ZIP - DOWNLOAD OTA/FULL ZIP UPDATE FILES

    Special thanks to HofaTheRipper,AVB Delenda Est & neilphetamine for shared their firmwares & boot files links !!
    ​
    ​
    ​
    ​
    ​








    ​
    ​







    (DO NOT PERFORM THE 1.1.7.HOTFIX UPDATE IF YOU WANT TO UPDATE TO 1.1.8)

    ​
    ​

    From BETA.2 onwards the update zips are unified meaning that the same zip can be used for both Global and EEA versions!

    ​
    ​
    From 1.5.2 onwards the update zips are unified meaning that the same zip can be used for both Global and EEA versions!


    ​

    NOTHING OS IMG - DOWNLOAD BOOT IMAGES

    /!\ IT'S HIGHLY RECOMMANDED /!\
    to always using fastboot "boot" command installation
    instead directly "flash" a patched boot.img file to avoid any risk of brick

    Code: 
    .\fastboot boot Magisk_Patched_XXX.img
    ​

    By the way if Magisk patched boot file is good, device will boot temporary with root and install Magisk, you must simply install/apply root on the boot definitively :
    - Open Magisk > Install > Install Directly (Recommanded) > Reboot... Voila !

    If the Magisk patched boot file don't boot, just do a hard reboot/shutdown by pressing ON/OFF button +5 seconds, device reboot directly with your stock boot without problems.

    ​














    • Stock 1.1.8
    • Magisk Patched 1.1.8

    From BETA.2 onwards Boot Images are unified meaning that the same img can be used for both Global and EEA versions!

    From 1.5.2 onwards Boot Images are unified meaning that the same img can be used for both Global and EEA versions!






    What are the regional variants of Nothing OS ?

    Nothing offers two distinct regional variants of Nothing OS.
    • Intended for European countries is the "EEA" version, as it meets the requirements of the European Privacy Directive and the General Data Protection Regulation (GDPR).
    • The other version, the so-called "Global Version" is intended for Asian and Australian devices.
    You can easily control the regional setting of your Phone(1) by going to your Shell terminal or Android emulator (e.g. Fuss, Termux) and executing the following command if on Nothing OS >= 1.5:
    Code: 
    getprop ro.product.name

    If Nothing OS <1.5
    Code: 
    getprop ro.product.system.name
    • These commands will return "SpacewarEEA" if the device is delivered with the European firmware.
    • For International models, the result should be "Spacewar" only.

    Don't forget to read this post which tries to gather your problems, but especially solutions brought by members

    [HELP THREADING] Nothing Phone 1 Common Issues and Problems​

    View
    19
    A
    AnotherM1m
    Old News
    Both 1.5.3 and 1.5.3.hotfix versions of NOTHING OS are currently unstable if the device is rooted and booting a magisk patched boot img.
    An issue has been opened on magisk github.
    For now if you want root and a stable device stick to 1.5.2, do not update until the cause of freezes is found.

    HEADS UP WHILE UPDATING TO A13
    [STABLE] UPDATING TO NOS 1.5.2
    Prerequisites:
    Global & EEA device with NOS 1.1.8
    The OTA Update file from 1.1.8 to 1.5.2. The link is down below: Global and EEA are not unified.

    Global users will have no problem performing the update with the necessary precautions.
    An EEA user on 1.1.7 no hotfix should update to 1.1.8.
    Updating to 1.1.7.hotfix will prevent you from updating to 1.1.8.
    They will need to perform beta updates.

    [BETA] UPDATING TO NOS 1.5.2
    Prerequisites:
    Global device with NOS 1.1.7
    OR
    EEA device with NOS 1.1.7.hotfix
    The OTA Update file from 1.1.7(/hotfix) to 1.5.0. The link is down below.

    Then from 1.5.0 to 1.5.2 perform all the needed beta updates

    NOTHING OS - Changelog

    Nothing OS 1.1.0 Changelog:
    Here’s the complete changelog for the Nothing OS 1.1.0 update for the Phone 1
    • New features
      • Introduced experimental Tesla control feature.
      • Introduced experimental NFT Gallery widget.
      • We heard your feedback on the Beta Launcher – the Search Bar on the home screen is now optional.
    • Camera improvements
      • Glyph fill light is now available in Portrait Mode.
      • Improved clarity and reduced noise when taking photos in low light environments.
      • Improved dynamic range when taking photos in low light environments.
      • Improved photo clarity when using the ultra-wide camera.
      • Improved colour consistency across the main and ultra-wide sensors.
    • Bug fixes & Performance optimisations
      • Updated Android security patch to July 2022.
      • Fixed a lock screen bug that would sometimes hide the fingerprint icon.
      • Improved the reliability of the Glyph Interface.
      • Battery life optimisations when device is on standby.
      • Improved Face Unlock performance.
      • General bug fixes.
    Nothing OS 1.1.2 Changelog:
    The complete changelog for the European Nothing OS 1.1.2 update​
    • New features
      • Added a toggle for showing the fingerprint icon when screen is off.
      • Always on display will now be turned off during the night by default.
    • Bug fixes & Performance optimizations
      • Improved charging performance and compatibility with 3rd party chargers.
      • Resolved Bluetooth codec issue.
      • Optimized minor UI details.
      • General bug fixes and stability improvement.
    Nothing OS 1.1.3 Changelog:
    The complete changelog for the European & Global Full Nothing OS 1.1.3 update​
    • New features
      • Added option to turn on Google’s Adaptive Battery to intelligently optimise battery life.
      • Redesigned fingerprint verification UI for 3rd party apps.
    • Camera improvements
      • When using Glyph lighting, images are automatically adjusted to optimal colour and brightness.
      • Impoved photo clarity when using the front camera.
      • Faster Night Mode and HDR photo processing time.
      • Richer colour saturation when using the ultra-wide camera.
      • Reduced noise and increased sharpness when using zoom.
      • Added reminder to clean the camera lenses.
    • Bug fixes and performance optimisations
      • Resolved an issue that caused stuttering in some apps like Twitter, Play Store etc.
      • Resolved an issue that prevented mobile hotspot from working properly.
      • Fixed ussye that caused the lock screen to crash after tapping on a notification and then trying to use finger unlock.
      • Polished minor UI details.
      • General bug fixes.
    Nothing OS 1.1.4 features the following changes:
    • New features
      • New option to flip the 3-button navigation bar.
      • All Ear (1) app features are now integrated into Nothing OS. Customize gesture controls and switch Noise Cancellation modes and more in Quick Settings and Settings.
      • Now supports LHDC high-def audio.
    • Camera improvements
      • New option to add a Nothing themed watermark to the camera app.
      • Improved ultra-wide camera colour calibration and increased colour consistency between main and ultra-wide sensors.
      • New motion detection algorithm added for improved stability when shooting moving objects.
      • Increased shooting speed when using HDR in ultra-wide mode.
    • System improvements
      • September Security Patch.
      • Reduced battery consumption for Always On Display and other use cases.
      • Improved thermal performance.
      • New UI for system updates.
    • Bug fixes & Performance optimizations
      • Fixed network issues for certain carriers.
      • Fixed an issue causing incoming calls to show up as Unknown Contact.
      • Fixed HDFC Bank app fingerprint issue.
      • General bug fixes.
    Nothing OS 1.1.6 features the following changes:
    • New features
      • Now supports Google AR Core.
      • Indian users covered by Reliance Jio can now access 5G.
    • Camera
      • Sharper videos with improved stability.
      • Recording light indicator is now always-on by default.
    • Improvements
      • Optimised, more fluid Launcher experience.
      • More accurate battery status.
      • Increased maximum brightness when displaying HDR content.
      • Updated, more reactive Flip to Glyph animation.
      • Glyph charging light now synced to sound effect.
      • Updated NFC sound effect.
      • General bug fixes.
    Nothing OS 1.1.7 features the following changes:
    • New features
      • Now supports battery percentage display for AirPods. You can enable it in Settings - Experimental features.
    • Improvements
      • Updated to October/November Security Patch.
      • Improved OS fluidity and reduced stutters.
      • Adjusted the thermal threshold to better balance performance and temperature.
      • Improved audio quality when recording videos.
      • More accurate battery status.
    • Bug fixes
      • Resolved an issue causing Whatsapp notifications to be unresponsive in lockscreen.
      • General bug fixes.
    Nothing OS 1.1.8 features the following changes:

    • The full Nothing X app will now be available in Nothing OS.
    • Fixed an issue causing the system to shutter in some scenarios.
    • General bug fixes.
    Nothing OS 1.5 Open Beta features the following changes:

    This is the first version of many to come and the priority is to ensure the stability of migrating to Android 13.
    • Android 13 Highlights:
      • More colour schemes are availables from the wallpaper selector
      • All apps must now have your permission before sending notifications
      • Added a QR code scanner shortcut in Quick Settings
      • Added support for setting per-app language preference
      • Added the Live Caption feature which detects speech from audio output to automatically generate captions.
      • Added a clipboard preview after copying text allowing the content to be edited directly from the clipboard
      • Better privacy protection such as Photo picker, Nearby WiFi devices Permission, Types of media permission, etc.
    • Nothing OS Improvements:
      • Improved the user interaction of Network and Connectivity tiles in Quick Settings
      • Reduced the wait time when loading apps
      • Implemented a new self-repair feature to periodically delete unused system dumps and cache
      • Optimised the smoothness of many animations throughout the whole system
      • Improved the volume setting panel, allowing granular volume controls without unlocking the device
      • Improved the game mode light notification and added the Google game dashboard
    • Weather app beta release!
      • Take an initial look at Nothing's in-house Weather app
      • Tapping a weather widget on the homescreen now directly opens the corresponding city in Weather instead of opening a link
      • Air Quality Index and more animations will be added in later stages
    • This is the first version of the Nothing OS
      1.5 Open Beta, so there are still many more features in development and you should also expect to run into some bugs and with the following      :

      - Google Pay and Netflix cannot be used normally.
      - Pop-up view feature will not be available.
    Nothing OS 1.5.1 Beta features the following changes:

    A warm welcome back to the second round of the Nothing OS 1.5 beta programme! Below are some additional features that we will bring to the NothingOS 1.5 update. Additionally, congratulations to those of you have been newly selected to participate!
    • Weather app beta release!
      • New Nothing weather app
      • Tapping a weather widget on the homescreen now directly opens the corresponding city in Weather instead of opening a link
    • Weather app beta release!
      • Take an initial look at Nothing's in-house Weather app
      • Tapping a weather widget on the homescreen now directly opens the corresponding city in Weather instead of opening a link
      • Air Quality Index and more animations will be added in later stages

        Thanks for your ongoing support and contributions to our efforts in improving the Nothing OS Experience. Let's continue building Nothing together.
    Nothing OS 1.5.2 Stable features the following changes:

    It's finally here. Our Nothing OS 1.5 official release. As a thank you for taking part in our Open Beta, we want you to experience it first.

    Experience Nothing OS 1.5, powered by Android 13. Our most significant update yet. With all new features and improvements.
    • Weather app
      • New Nothing weather app
      • Tapping a weather widget on the homescreen now directly opens the corresponding city in Weather instead of opening a link
    • Customisation
      • All new Glyth soundpack for more ringtone and notification sounds.
      • More colour schemes available from the walpaper selector.
      • New collection of minimalist wallpapers.
      • Icons can match your background colour to make your home screen look more consistent.
      • Lockscreen shortcut customisations. Create shortcuts for camera, torch, device controls, and wallet.
    • Improved experience
      • Easily switch data usage when using dual SIM with the improved network Quick Settings panel.
      • Automaticallyshow the current network and display how much mobile data you have used in Quick Settings.
      • Directly scan a QR code in the Camera app. Scanner also appears as a shortcut in Quick Settings.
      • Select language preferences for different apps.
    • Visual improvement
      • A New look for Media Control. Puts album artwork on full display with a wider set of music controls.
      • Improved volume settings panel. Allows granular volume control without unlocking the device.
      • Improved Game mode light notifications. So there is less distraction when you are playing.
      • Smoother animations when transitioning the display between on and off.
      • More refined Camera app interface.
    • Privacy and safety
      • Get an alert when an app accesses your clipboard. Cleared history after a period of time to prevent unwanted access.
      • Added Personal Safety app.
      • Better privacy protection including Photo Picker, nearby Wi-Fi devices permission, and select media permission.
    • System performance
      • Fingerprint unlock accuracy has improved by up to 12%.
      • App startup speed has increased by up to 71%.
      • Standby power consumption has improved by up to 50%.
      • Implemented a new self-repair feature to periodically delete unused system dumps and cache.
      • Increased system stability.
      • General bug fixes.
    Nothing OS 1.5.3 features the following changes:
    • What’s New
      • New support for manually adding games to Game Mode (games not installed from Play Store will not be able to be used with the Game Dashboard).
      • Smoother animations for pop-up view.
      • Improved fingerprint transition between the lock screen and AOD.
      • New wallpapers.
      • Added support for Ear (2).
      • New memory management algorithm that reduces app restart times by over 35% and lowers CPU consumption to improve overall battery life. Improved system stability.
    • Bug fixes:
      • Fixed abnormal appearance of Night Light mode in certain scenarios.
      • Fixed the flashing charging prompt on the AOD interface.
      • Fixed issue where Glyph lights did not show for incoming WhatsApp calls.
      • Fixed freeze issues during YouTube video playback.
      • Fixed issue where weather data did not show in the Quick Look widget.
      • Other general bug fixes.
      • Update size: 91.79 MB
    Nothing OS 1.5.3.hotfix features the following changes:
    • Fixed an issue causing notifications to not appear when Quick Settings is active.
    • Fixed an issue preventing the NFC toggle to function as intended
    1683219274383.png
    View
    7
    A
    AnotherM1m
    KERNEL FOR PHONE(1) - 17-07-2022

    If you're a developer looking to create something around the Phone(1), here's something to get you started with the release of the Kernel and device tree.

    Nothing Phone 1 : Kernel Source || Device Tree
    View
    7
    A
    AnotherM1m
    UPDATE: set the time zone to China, Shangai to use the offline updater
    View
    7
    TheHappyBuddhist
    TheHappyBuddhist
    @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. :)
    View

New posts