yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] AnotherM1m:
No problem, i really just want a stable phone experience.

Let's wait for updates and hope for the best.

EDIT:

I've updated the first and second posts, please feel free to let me know if i've made any spelling mistake.
[Nothing Phone 1] AnotherM1m:
Hold your finger on android's Home, customization, wallpaper & style, scroll down
[Nothing Phone 1] trax69:
Spacewar-T1.5-230317-2039-EEA Which biuld is 1.5.3 or 1.5.3 hotfix?
[Nothing Phone 1] whamslambam56:
So this only worked for a day or two and then froze again... I have no idea if an app triggers this and I don't really understand the log. But this is what is logged directly before the freeze each time:

View attachment 5870745
[Nothing Phone 1] BuffMcBigHuge:
Yup. Phone freezing entirely on my device too with 1.5.3. Super annoying.

I flashed the stock boot image for now with no root until this problem is fixed.
[Nothing Phone 1] wintermut3:
I got some problems while doing the updates manually. I've just installed the EEA 1.1.7 manually, then I wanted to patch it manually up to (step by step) until 1.5.2.

By patching the 1.1.7hotFix it already gets :45 (kUnsupportedMinorPayloadVersion)

It makes no difference if sideloaded or via *#*#862#*#*

Any ideas why it happens? The buid target is correct.
[Nothing Phone 1] Sluzy:
I'm getting this error when updating to 1.5.3 hotfix, any help?

View attachment 5871549
[Nothing Phone 1] rogerrulez:
Can anyone confirm whether the Nothing OS 1.5.3.hotfix Stable is working yet for root ?

Thanks.
[Nothing Phone 1] The_Overthinker:
As for now, root is neither working in 1.5.3 stable, nor 1.5.3 hotfix stable.

An issue regarding this has been raised here.
[Nothing Phone 1] rogerrulez:
Thanks but, why was it posted ?
[Nothing Phone 1] rogerrulez:
Yeah I know. But I'm just curious that, if it doesn't work than why post the patched boot image. I guess more or less I was thinking the issued was resolved since it is posted.
[Nothing Phone 1] wintermut3:
It could be, that you are mixing Global with EEA. which one are you using? Do you know that?
[Nothing Phone 1] rogerrulez:
Aww, yeah. I do know that very well. I'm using the global version.
[Nothing Phone 1] BertProesmans:
I got the 1.5.3 update notification today (EU spacewar).

If I understand correctly, today it's not recommended to upgrade if root is desired because of not-so-random full system freezes after booting with Magisk root.
[Nothing Phone 1] iamthechickengod:
Yes
[Nothing Phone 1] Sluzy:
I'm using EEA, but isn't now all the same?
[Nothing Phone 1] wintermut3:
I cannot tell you what the exact differences are, but I can tell you, if you look in the meta_inf in metadata, there are different build numbers. Both, pre and post build numbers, so in case of doing update, the software will definetely stop you. For EEA you must use the EEAs updates and for global the same rule.
[Nothing Phone 1] Sluzy:
The new version packages in here are Global or EEA?
[Nothing Phone 1] xtcislove:
There is no global or EEA.

From the second Beta [1.5.1] EEA & Global firmwares are now unified!
[Nothing Phone 1] Enzucuni:
Don't know if anybody asked the same question, but, is this the offline updater on Android 13 or is it a different app? If it is the second case, would you mind telling me which one is it?
[Nothing Phone 1] AnotherM1m:
It's the offline updater used from 1.5.3 (not hotfix) onwards
[Nothing Phone 1] Enzucuni:
Would you be able to send me the apk, please? I know that 99% it won't work, but I don't have a lot of options left.
[Nothing Phone 1] AnotherM1m:
What version are you on right now? If 1.1.7 hotfix you have to go through beta to get 1.5.2
[Nothing Phone 1] Enzucuni:
I have tried multiple times, bricking the first device I had. Everytime I try, I've got a payload error during sideload
[Nothing Phone 1] AnotherM1m:
Sideloading never worked for me, error 20, i always went with the dialer except for ota updates where i did.. the otas.

On 1.1.7hotfix you cannot upgrade to 1.1.8, you have to update to beta and do it one by one.

If you want to root stop at 1.5.2

A safer road would be to download a full fastboot rom and flash it but you'll lose your data.

But the risks of bricking are less likely to happen this way.

Also now users developed tools to unbrick devices in edl mode (which was the hard brick for np1 before) so the context is generally safer right now
[Nothing Phone 1] Enzucuni:
If I have to, screw it. It's much less annoying than relocking the bootloader, send it in RMA and wait who knows how long. Do you have a link for a specific guide regarding fastboot ROM flashing for this device? Hopefully I don't have to wipe it every time a new update comes out. We need a basic custom recovery.
[Nothing Phone 1] AnotherM1m:
First find out which boot slot you have active on your phone with fastboot (get varchar i don't remember the right command) then download the fw you want from the link in this page:

https://xdaforums.com/t/rom-restore...m-boot-img-qfil-rom-edl.4523185/post-87777263

Extract it and run the script of the right boot partition

Edit: but to be honest if i were you i would try to pass through beta first with the dialer method.
[Nothing Phone 1] Enzucuni:
I'll give it a shot this moment, but until now, always gives me error 20, hence why I was curious to try your offline updater apk, just to try before going the wipe route.
[Nothing Phone 1] AnotherM1m:
Remember to restore the original partitions with magisk before updating.
[Nothing Phone 1] Enzucuni:
Could this be why it won't let me update with that error 20?
[Nothing Phone 1] AnotherM1m:
If you try updating with magisk patched boot flashed you will get error 20

If you directly installed magisk, the procedure to do is open magisk, press uninstall and then restore stock images, DO NOT REBOOT, perform the ota update or the dialer update.

If you are doing the ota update from the settings notification wait until it ask to reboot, still do not reboot, open magisk, install it by selecting the ota option, after it finishes return to the settings update menu and restart from there.

When it boots up you are on new fw with patched boot.

Redo all the steps until you are at the version you want.

If you do the dialer update, BEWARE because the phone reboots on its own

Start the dialer update and keep an eye on the phone. When it powers off hold vol down to boot into bootloader and BOOT the magisk patched boot img of the new fw

So the phone has stock boot flashed but patched boot booted, you can perform a new update as soon as you boot it, because the phone has stock partitions on it.

With the dialer always remember vol down at boot and boot the new patched img.

Let us know how it goes.
[Nothing Phone 1] Enzucuni:
I see. If I were to flash back the stock 1.1.7 boot image removing root, update from settings and not from offline OTA, boot in the new rom and THEN flash the magisk patched boot, would there be any problem? Is that an option?
[Nothing Phone 1] AnotherM1m:
You can do that but booting a stock rom on a device with unlocked bootaloder will trigger DRMs which are annoying to fix back.

And to some user, banking apps and netflix are pretty important on their phones.

If you flash stock then boot patched.

If at the time of installing magisk you DID NOT boot patched and directly installed magisk BUT you flashed patched, magisk will return an error when you try to restore to stock.

Boot into bootloader, flash the boot of the fw you have and boot patched, perform the update etc.
[Nothing Phone 1] Enzucuni:
Is everything specified in the guide you linked? And by the way, yesterday I tried flashing the stock boot yesterday and phone was fine. Netflix and Wallet have never worked since day one, but I have all the modules needed that work perfectly on my Pixel 6A, but just in case, how could I restore DRMs?
[Nothing Phone 1] AnotherM1m:
No, that guide is for the fastboot rom, mine is for the zips

Flash safetynet fix, delete data for play services and play store, i think thats it but sometimes it doesn't work
[Nothing Phone 1] Enzucuni:
Oh right, that's easy. So, to wrap up, can you confirm that if I flash stock boot, update either from 1.1.8 onwards from settings or offline update 1.5 Beta 1 onwards, and THEN I flash the magisk boot like for 1.1.7, I should be fine risking no wipe? I'm not holding you accountable, don't worry. I just want to be 100% sure cause I'm at work tomorrow and I need a functioning phone. If it was weekend, I wouldn't care.
[Nothing Phone 1] AnotherM1m:
Boot into bootloader

Fastboot flash boot stock_boot_1.1.7hotfix.img (or how it's called)

Fastboot boot patched_1.1.7.hotfix.img

Now with the dialer method update to 1.5 beta 1, hol vol down

Fastboot boot patched_1.5.beta1.img

And you keep going with dialer and otas.
[Nothing Phone 1] Niecks:
I'm dumb ; when i receive my brand new Nothing Phone i updated to the lastest version (1.5.3) i didn't see this topic before. Now root is not working.

There is a way to downgrade to 1.5.2 without any issue ? Or best option is to wait a fix ?
[Nothing Phone 1] AnotherM1m:
You can downgrade with the link i've previously sent in this conversation but you'll lose all your data
[Nothing Phone 1] dedors:
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.
[Nothing Phone 1] panni:
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.
[Nothing Phone 1] HofaTheRipper:
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.
[Nothing Phone 1] thisjacoob:
how to unbrick the phone when the power up screen says press any key to shutdown?

instead of boot I used flash and now I can't even turn on fastboot mode to do anything

please can it be fixed somehow?
[Nothing Phone 1] AnotherM1m:
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.

But i can update the guide to alert people about this possibility.

Unified means the same zip can be used for both version of the phone to update the software.

For beta users the second beta was unified, for stable user 1.5.3 was the first unified update.
[Nothing Phone 1] AnotherM1m:
https://xdaforums.com/t/unbrick-tool-edl-flash-read-repair-region-change-tool.4552471/post-88133695

Edl mode is the only way
[Nothing Phone 1] thisjacoob:
I don't know what I'm doing wrong, but I can't start the phone in edl mode
[Nothing Phone 1] AnotherM1m:
Sorry, if you need support with the unbrick tool please post your message in that thread, here we offer support for the installation of updates
[Nothing Phone 1] panni:
Great, seems like we're out of luck with our phones on 1.5.3 and root.

Hopefully Nothing removes the new memory management or fixes the underlying issue in the next update. Otherwise this phone is pretty much dead for me.
[Nothing Phone 1] Adrian312:
pff thats pita....if thats the root cause, I am switching to custom rom.
[Nothing Phone 1] NightStrix:
Thank you for the update, I'll stay with the 1.5.3 stock boot image until a stable patch is found.
[Nothing Phone 1] whatsek:
EDIT: Unfortunately I did get a freeze just now, so this seems not a temporary solution!!!

Root on 1.5.3 (temporary) solution:

!! Only try this if you know how to flash and restore an original boot.img !!

As many of you I also encountered freezing problems after flashing the patched boot.img on 1.5.3. So I booted my updated phone with a patched boot.img 1.5.2 and this works without any issues.

(So the optimizations mentioned in the changelog of 1.5.3 are kernel changes in the boot.img)

After a few hours having a working (rooted) phone, I flashed the patched 1.5.2 boot image permanently, and encounterd no issues.

So if you want a rooted 1.5.3, and you are satisfied how 1.5.2 was performing, this can be a temporary solution.

For me it is a better solution then an unrooted 1.5.3.
[Nothing Phone 1] Niecks:
I tried your solution :

I did a "fastboot flash boot magisk_boot_1.5.2.img" on my 1.5.3 device but unable to boot i have to rollback to original 1.5.3 boot.img to boot

I missed something ?
[Nothing Phone 1] whatsek:
I first did: fastboot boot magisk_patched-1.5.2.img to test if it booted, (it did) then I did a: fastboot flash boot magisk_patched-1.5.2.img to make it permanent. I used the patched magisk 1.5.2 boot image from this thread in the first post.
[Nothing Phone 1] AnotherM1m:
I tried that too, unfortunately got a freeze

HEADS UP IF ANYONE WANT TO HELP FIND A SOLUTION FOR THE FREEZES

On github there is a new magisk version which... does not let magisk do its work, creates just a patched img without magisk

It's a starting point to find where the problem could be

Nothing Phone (1) OS 1.5.3 freezes and ramdumps during boot after boot.img is patched · Issue #6780 · topjohnwu/Magisk

With unlocked bootloader and stock boot the phone works ok; with a patched boot img freezes and/or ramdumps during use are common. Sometimes they happen right after boot, other times they can take ...

github.com

If you encounter a freeze with this version please let us know either here in this thread or on github

for me still no freezes but magisk is technically disabled.
[Nothing Phone 1] AnotherM1m:
GitHub - LukeSkyD/NP1-MGLRU-FIX: Magisk module to fix freezes and crashes on NP1 phone

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

github.com

If the culprit of the freezes is the newly implemented MGLRU then this module should fix them.

It's made by me, if you encounter freezes or errors please let me know.
[Nothing Phone 1] dreas74:
Many thanks for your helpful modul. it works as expected, but cold boot is necessary.
[Nothing Phone 1] AnotherM1m:
Yes, thank you, i didn't remembered the right word when i was writing the readme!
[Nothing Phone 1] pyry666:
If this is indeed solution , you found the culprit. And imo magisk by itself sould implement this asap. Thanks for yout hard wotk. Ill try this in a day or two. Atm this is my only working device and I really need it to be reliable and working
[Nothing Phone 1] AnotherM1m:
Thanks let us know if everything works correctly

For fairness this module was made from an idea of aviraxp from github and after many devs tried to look into this issue so it's also thanks to them!

Nothing Phone (1) OS 1.5.3 freezes and ramdumps during boot after boot.img is patched · Issue #6780 · topjohnwu/Magisk

With unlocked bootloader and stock boot the phone works ok; with a patched boot img freezes and/or ramdumps during use are common. Sometimes they happen right after boot, other times they can take ...

github.com
[Nothing Phone 1] NightStrix:
Experiencing freezes and frustration after flashing the v1.5.3 patched image, I followed with great interest on Github the research that led to this Magisk module. So far and after a 2 hours of testing, everything is working fine as SU. Thank you very much for this great job !
[Nothing Phone 1] pyry666:
Sure thing, and of coure i ment that in plural, was just easier to write "you". English is not my native language. And i have kept my eye on that github page.
[Nothing Phone 1] AnotherM1m:
V2 of the module:

Release V2 - Use system.prop · LukeSkyD/NP1-MGLRU-FIX

System.prop is used to change persist.sys.mglru_enable prop post-fs-data deleted because no longer used

github.com
[Nothing Phone 1] iamthechickengod:
Out of curiosity, what does MGLRU do exactly?
[Nothing Phone 1] AnotherM1m:
LRU stands for least-recently-used is a list in the kernel used to manage memory.

Multi-Generational LRU is a new implementation of such list but seems that Nothing's work is flawled somewhere or there is a peculiarity that is blocking magisk to correctly create a boot.img

The module just disables MGLRU and rollsback to the previous kernel.

The best way would be to have LRU and magisk compatible between eachothers but what is causing this issue with lru is still unknown.
[Nothing Phone 1] AnotherM1m:
Has anyone experienced a crash or freeze with the module?
[Nothing Phone 1] Jimnik:
I just installed the update and flashed the magisk boot image. For some reason even after using my phone for about 3 hours i havent encountered any freezes. Anybody knows an effective way to trigger one?
[Nothing Phone 1] AnotherM1m:
When i installed the update for a full day i went without any freeze.

The started getting them every hour.

To me an effective way to trigger crashes is joining a discord voice channel while on bluetooth headset then start opening apps, camera etc
[Nothing Phone 1] Jimnik:
This is kinda weird tbh. I just tried exactly what you said and it didnt overload. I also downloaded a stress test from playstore and it run fine. Is there a chance OP implemented the magisk module fix in the magisk boot image?

Edit: cat /sys/kernel/mm/lru_gen/enabled retruns 0x0000
[Nothing Phone 1] AnotherM1m:
I didn't do anything so you are either a special case or you are able to not touch parts which can trigger crashes and freezes

Looks like you have the module installed if the cat command returns 0x000
[Nothing Phone 1] Jimnik:
I didn't..View attachment 5879689View attachment 5879691
[Nothing Phone 1] Sib64:
Hi everyone,

I'm currently on holiday 🏖️and will be back in two weeks.

I hope Nothing will be out by then and that they will wait for me to come back.😜

Take care everyone and have a good day. 👍😉

There is no need to reply to my post to stay on topic and not have off-topic.

Thanks 👍
[Nothing Phone 1] NightMean:
I see that you mentioned the Full NothingOS update but the OTA is just an incremental update.

As far as I am aware there full OTA wasn't released, right? If it was, the link is incorrect.

Anyway enjoy your holiday!
[Nothing Phone 1] :
Nothing Phone 1 gets minor fixes with Nothing OS 1.1.2

Nothing has released a new update for its Phone 1. The update brings minor bug fixes and enhancements to improve the user experience.

www.xda-developers.com
[Nothing Phone 1] NightMean:
Thanks! Wasn't aware of this.

The link does points to the Incremental OTA instead of the Full OTA. That needs to be adjusted or perhaps a separate expandable area where incremental OTA is listed. Will wait for Sib64 to come from holiday.
[Nothing Phone 1] :
That's full ota it's more than 2gb lol
[Nothing Phone 1] fmotta61:
But it's 1.1.0 not 1.1.2
[Nothing Phone 1] SkandaH:
@fmotta61

The (full) firmware links in the aforementioned XDA Portal article correspond to Nothing OS 1.1.2, not 1.1.0.

In case you have any difficulty following Nothing's OTA rollouts, do take a look at our dedicated Nothing Phone 1 Update Tracker. It contains both full and incremental OTA links.
[Nothing Phone 1] dememted1:
Is there a fastboot "Back to Stock" yet. thanks.
[Nothing Phone 1] JazonX:
Anyone managed to capture the new one ?
[Nothing Phone 1] bariz143:
Anyone with DL link???
[Nothing Phone 1] jjjhitel:
https://android.googleapis.com/packages/ota-api/package/d2e43b858fd93f46d136a424f3756ae2d5decbc3.zip

1.1.3 Incremental OTA update for GLOBAL variant
[Nothing Phone 1] AntoXik72:
Thanks a lot! Can you please share the link for the full update?
[Nothing Phone 1] neilphetamine:
Using local setup wizard (through dialer) and updated!
[Nothing Phone 1] Supermaxness:
How to enter this wizard?
[Nothing Phone 1] neilphetamine:
Phone> open dialer > key *#*#682#*#*
[Nothing Phone 1] Alfr3d0T:
Thanks! Could you post the link for the European version ??
[Nothing Phone 1] q173242:
Not released by now.
[Nothing Phone 1] UserNamist:
Has Nothing said anything about why Europe and the UK aren't receiving the current bugfixes?
[Nothing Phone 1] Pho3nX:
Not purposed on my Nothing EEA for the moment, just wait a little guys.
[Nothing Phone 1] Wabbajackw:
Edit
[Nothing Phone 1] dreas74:
Today, I had a freeze on the cam, but I don't know if it was related to your lovely module.

After reboot everything works again, including the cam.
[Nothing Phone 1] DiogoPdC:
I tried to boot a Magisk patched img and I got this error

usb_read failed with status e00002ed​

Any idea what happened?
[Nothing Phone 1] Adrian312:
Do you mind to provide more details eg:

- did you patch it yourself

- which version

- root etc.
[Nothing Phone 1] gwolfu:
there seems to be some trigger in the system that sets the prop to true again resulting in a crash

I've made a different magisk module that checks for prop status every 30 seconds (because sometimes the crash occurs after a minute, so let's be safe) and resets back to false

feel free to use it guys if interested

https://github.com/gwolf2u/MGLRU-Disabler/releases/tag/4.0
[Nothing Phone 1] DiogoPdC:
Using the same 1.5.3 magisk patched img I used before I boot it and install magisk but the phone freezes so I try to boot again from the img and that message shows up

I found that patched img on here.
[Nothing Phone 1] Adrian312:
FYI right now root is broken on the latest NothingOS version. as you can see above, there is some work around to have it bypassed but its 100% yet. I would recommend to stay away from root for now, unless we have a permanent solution
[Nothing Phone 1] DiogoPdC:
Sure but even if I wanted to root I can't

I just wanna fix the bootloader please
[Nothing Phone 1] JamesGatz3010:
How to disable floating notifications in nothing phone
[Nothing Phone 1] panni:
Can one of the magisk-fix-authors try what was mentioned here? That might be a pretty permanent solution. Magisk won't fix this as it's not their "problem", which is completely true to be honest.

So chmod 444, 555 or 540 I guess. (Not sure how readable that endpoint should be to public/groups).

Let's alert Nothing of the kernel issue, though, as it seems like its implementation of the LRU mechanism is flawed.
[Nothing Phone 1] AnotherM1m:
Give me 1h and i'll try to open an issue on Np's repo

Im not implementing anything that modified system.prop's permissions because some people may have modules that changes it and they would break and it is not a global workaround.

Or maybe is it possible to gain ownership of just that single property?

Anyway, When i have time i would like to implement a script that gets notified everytime system.prop gets changed, checks mglru_enable status and changes it back if it's true

@gwolfu if you are available we can work together on this, so we have just one module.
[Nothing Phone 1] gwolfu:
This is almost what my script does

Checks if value is set and if enabled, it disables it

MGLRU-Disabler/system/etc/mglru-checker-loop.sh at main · gwolf2u/MGLRU-Disabler

Contribute to gwolf2u/MGLRU-Disabler development by creating an account on GitHub.

github.com

Anyway, should also be possible to chown and chmod the read only, just didn't want to as it might break some other stuff
[Nothing Phone 1] AnotherM1m:
Yes but a script running every 30s is a little overkill for me, still a great job obv!

But i would like it to be as less invasive as possible, that's why i also changed my module to not use scripts but props.
[Nothing Phone 1] lucy1983:
Yup same thing just happened to me.
[Nothing Phone 1] gwolfu:
Well might be overkill, however no big load on system

There are lots of system calls that run by minute or so

Using props might be hit and miss also if not ran on timed check
[Nothing Phone 1] mollex:
Yesterday I got an update for my dutch NP1 A13 from:

Spacewar-T1.5-230310-1650-EEA to Spacewar-T1.5-230317-2039-EEA

It feels faster after the update.

Who knows the changes? TiA.
[Nothing Phone 1] AnotherM1m:
1.5.3.hotfix

There is the changelog in the second post of this thread.
[Nothing Phone 1] panni:
Wouldn't that just be chmodding `/sys/kernel/mm/lru_gen/enabled` after setting the prop?