yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] gwolfu:
The idea was

chown /sys/kernel/mm/lru_gen/enabled

Set flag to disabled

chmod to read only file

Am not big fan of this, since some system calls may want to write that file and who knows, maybe make system crash

My way was just simple call to check if flag is set and unset in case it is

In case some system call changes it, will simply fail back to disable

Anyway feel free to use and develop any other magisk module or so, but imo my way works (proof as I didn't had any issues since two days now)

Also in case some asks, RAM usage is same and my battery is also same

Nothing out of the ordinary

Now am not gonna participate to this specific discussion anymore as all has been written
[Nothing Phone 1] gmx2pt:
Thank to all the knowledgeable people that helped diagnostic this magisk issue, it's really appreciated by a silent majority !
[Nothing Phone 1] BuffMcBigHuge:
I want to thank LukeSkyD for solving the root issue. Fingers crossed my device doesn't freeze!

Great work!
[Nothing Phone 1] lucy1983:
I also installed the fix this morning. No freeze until now.
[Nothing Phone 1] AnotherM1m:
Thanks!

The device could still freeze. If it happens too frequently you may try this other module by Gwolfu

GitHub - gwolf2u/MGLRU-Disabler

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

github.com
[Nothing Phone 1] aleqa:
Hello I am getting this error, while trying to update from 1.5.3 to 1.5.3 hotfix. Anyone knows what I should do, to get the hotfix?View attachment 5881595
[Nothing Phone 1] panni:
Works flawlessly. Thank you!
[Nothing Phone 1] panni:
Same issue in Germany with EEA.
[Nothing Phone 1] pyry666:
I faced this also. But after asking from tg about it I actually already have hotfix cause I waited so long to update it (via ota).

Spacewar-T1.5-230317-2039-EEA is hotfix built in update
[Nothing Phone 1] paper88:
Hello together

Im om V 1.5.2 and just wondering if I can install the same Version again over sideload to reinstall it? Will this delete my data? Will it even work?
[Nothing Phone 1] aleqa:
I always made all the updates from the offline update tool. but the hot fix i am getting error.

I dont get the updates from OTA. Already tried.

Also tried with adb sidload and i am getting errors as well.
[Nothing Phone 1] pyry666:
Hmm weird, afaik your build number isnt the latest. Maybe try asking from tg if some one there knows better. And in my case manual updates has never worked..Error 20 etc
[Nothing Phone 1] aleqa:
My version is this one.
[Nothing Phone 1] pyry666:
Yeah, it shows from your previous screen shot also. Mine is mentioned also at couple posts up
[Nothing Phone 1] aleqa:
Did you find the solution for this error?
[Nothing Phone 1] aleqa:
If i try to update again to 1.5.3 (override) should i get any problem?
[Nothing Phone 1] AnotherM1m:
the phone shouldn't allow it giving you an error.

have you tried with a vpn searching for updates from settings? i think they broke the offline updater with the 153 update.

remember if you are rooted to restore partitions before starting the update.
[Nothing Phone 1] aleqa:
Already tried different vpn apps, different country's, say always that i don't have updates.

I am running out of options.
[Nothing Phone 1] AnotherM1m:
Wait for the ota rollout or use the edl tool to flash 1.5.3.hotfix but you will lose your data

https://xdaforums.com/t/rom-restore...t-rom-full-rom-boot-img-qfil-rom-edl.4523185/

tbh if you really don't have the necessities of what hotfix brings (look at the changelog) wait for the ota.
[Nothing Phone 1] aleqa:
I never got any update from OTA, doesn't know if it is some problem or not. Always updated from dialer.

I am from Portugal, and i know other people here that already got the 1.5.3 hotfix.

So i don't understand why i don't receive, or can't update from dialer.

I can try EDL, but my afraid is if need to do it always there is a new update.
[Nothing Phone 1] AnotherM1m:
153 FREEZE FIX

To anyone whose persist.sys.mglru_enable was resetting to true after unlocking the phone, can you please try this module and check if it's happening again? remember to cold boot after install and if you have it disable mglru disabler by gwolfu

Thanks!

Edit:

Added V3b2 that changes a string
[Nothing Phone 1] aleqa:
I also noticed that last update check was on 8/9/2022.

What could be the reason for this?
[Nothing Phone 1] lucy1983:
If we do not have problems with resetting to "true" we can keep the old fix, right?
[Nothing Phone 1] AnotherM1m:
Yes
[Nothing Phone 1] panni:
Did anyone test this vs the one from gwolfu?

Thanks!
[Nothing Phone 1] AnotherM1m:
v3b and b2 do not work

I'm doing tests with chmod to check the system stability rn but the results are not encouraging, at least on my part
[Nothing Phone 1] AnotherM1m:
New day, new beta, let me know how it goes, it's a beta but it should not break anything

Edit: a user on github reported that the flag persist.sys.mglru_enable still gets set to true.

No crashes were reported even in such situation.
[Nothing Phone 1] gwolfu:
since I've created (for a week now) and installed it, no issues

https://github.com/gwolf2u/MGLRU-Disabler/releases/download/4.0/mglru-disabler-v4.zip
[Nothing Phone 1] lucy1983:
Same here. No freezes.
[Nothing Phone 1] panni:
Yep I know, I'm using it successfully as well. I was just interested in the other "fix-type" and whether it works.
[Nothing Phone 1] AnotherM1m:
1.5.3(/hotfix) issue with root is being investigated:

MGLRU implementation crashes the phone when Magisk is used · Issue #7 · NothingOSS/android_kernel_msm-5.4_nothing_sm7325

Nothing's implementation of the MGLRU kernel causes modified boot images to crash the phone. Freezes and ramdumps are common if the device is rooted. MGLRU implementations from other vendors do not...

github.com
[Nothing Phone 1] gwolfu:
to be honest I have low expectations

we kind of complain that tampering with the system causes issues

they can simply say, "don't root"

however fingers crossed for a fix
[Nothing Phone 1] AnotherM1m:
I think they will fix it but it will take some time

Fingers crossed
[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

V3 released, now mglru should does not re enable itself and cold boot after installation is no longer needed.

persist.sys.mglru_enable stays true on this version.

This update is recommended for those with a previous version.

If you find yourself comfortable with gwolfu's module a swap is not needed.
[Nothing Phone 1] panni:
Seems like memory creep issues aren't fully solved with the available fixes (probably not fixable?); I was running gwolfu's fix for a week and today no app remained in-memory (was killed immediately after tabbing out), and the GBoard closed itself constantly after 2 seconds.

The issue is gone after a reboot.
[Nothing Phone 1] AnotherM1m:
I've noticed it too before but the ram usage shown in developer settings does not get higher than 4GB, i don't know how apps are choked by the system.

The function which is probably called to deal with this has been moved to the newer mglru implementation and with it disabled this side effect is shown.

I will try to look into this but i cannot give any garantees. Nothing will probably issue a fix before i'll update the module.

Edit: Franco kernel Manager shows 75% of memory used, dev options less than 50%.
[Nothing Phone 1] paper88:
Hi Guys

I currently struggeling with my magisk installation. (Thread) Since I updated to 1.5.2 I can boot the patched img and have root, but in magisk I just have the option to patch a boot.img and cannot directly install. I cannot install modules or access zygisk options. The installed modules before, like iOS Emoji, just work. I think it happened because I installed Magisk over "after OTA-Option" and then rebooted phone on OTA Menu. My Phone rebooted but switched back to V1.1.8. After that I uninstalled Magisk completly, updated it over OTA and booted the patched img. I think that now already some magisk is installed on the second boot slot so it detects somehow root.

What is the actual state of the 1.5.3 Freeze Problem? If boot now the stock img and upgrade over OTA I need to boot the patched img again. Do I have time to install the Module or is it freezing immediately? Can I maybe downgrade to 1.1.8 and install 1.5.2 again so it clean the boot slot? Will I loose any data at downgrade?

Logfile after boot patched img: https://drive.google.com/file/d/1yqodJxhT9l6ERyJjcRtSEiqUUB1QXovh/view?usp=drivesdk

Thanks for help!View attachment 5887595
[Nothing Phone 1] AnotherM1m:
Directly flashing this img does not work right?

https://xdaforums.com/t/magisk-direct-install-not-visible.4556733/post-88197735

With

Fastboot flash boot magisk_patched-25200_TrVLh.img

1.5.3 freezes without modules, but you have time to install any of them.

Downgrading or reinstalling via fastboot roms will factory reset the phone.

About the logs i wouldn't know but

---Magisk Logs---

26.1 (-1)

The Magisk daemon is not starting, but im not an expert on this.

What does

fastboot getvar current-slot

Return?
[Nothing Phone 1] paper88:
No, also flashing the img directly was not working.

Im currently on slot a. Maybe I switch back to stock img, update to 1.5.3, patch and directly install the module?
[Nothing Phone 1] AnotherM1m:
flash to stock and update, just to be sure

then boot patched, direct install, install the module, reboot.

hopefully magisk will install on your phone on 1.5.3
[Nothing Phone 1] paper88:
I will, im sure if I update and switch back to slot b and update again go back to slot a, it will overwrite the wrong magisk config.

I just wasn't sure about the freezing problem, because I cannot install the MGLRU Module before updating
[Nothing Phone 1] AnotherM1m:
Don't do anything with the slots.

If it's possible just perform the ota update.

After it finishes, go back to fastboot to simply boot the patched img
[Nothing Phone 1] paper88:
Of course, but it will switch the boot slot on Updates everytime or am I wrong?
[Nothing Phone 1] AnotherM1m:
Not with full zips but in case of otas yes
[Nothing Phone 1] DarkNeogen:
Sorry guys, but I have been reading and following this topic ever since I upgraded to 1.5.3 and learned that root will freeze.

What is the full and best working procedure to get 1.5.3. rooted again that's stable enough for a daily driver?
[Nothing Phone 1] AnotherM1m:
Boot patched img, directly install magisk and then install one of the two modules talked in the news section of the main page of this thread.

Gwolfu's module runs every 30s to disable mglru in case it gets reactivated.

Mine disables mglru from the start and removes permissions to restart it again.
[Nothing Phone 1] DarkNeogen:
Thanks for the quick reply, what module would be the safest or with the lowest impact?
[Nothing Phone 1] AnotherM1m:
Counting on the fact that I'm NOT impartial, i would think mine (the V3 version) gets the job done better that the other.

Because the other doesn't block mglru from restarting and i think (im still not 100% sure, 75% yes) just mglru starting creates problems the more you use the phone (facial recognition gets slower and keyboard starts closing on its own).

But both are really valid, you can hear people from both parts praising both modules.

If you have problem with one, use the other. try them out.

@gwolfu don't kill me pls after stealing the name of the module im also stealing userbase x.x

sorry! :^*

if im able to find a fix i'll rollback the name of mine
[Nothing Phone 1] gwolfu:
My module is good enough for my needs and while maybe name is similar (how many other ways to name it though), our ways of doing it is different

My module simply checks from time to time the value of prop and makes sure if any system call changed it, to put it back proper prop, that way not having any system call issues

No battery issues or anything as confirmed by others also not just me

Your way if different and imo no need to chmod as previously discussed

This is not a steal of anything and I care less how many users use my module as long as all don't have issues (having other things to care for)
[Nothing Phone 1] dreas74:
I have both modules installed. no impact to messure.

Thanks to both developers.
[Nothing Phone 1] DarkNeogen:
Good to hear, I just re-rooted after weeks of feeling 'naked'. I installed the V3 one. I'll try it out for some weeks.

Thanks for your efforts!
[Nothing Phone 1] usernametaken53:
I am so confused by this.

Is there a Full Stock ROM for 1.5.3 ? I am on a custom A13 ROM and wanna revert back to stock, can't seem to find the file for it. Do i need to go back 1.18 and install the incremental OTAs from there ?
[Nothing Phone 1] lucy1983:
From what I know there isn't a full stock 1.5.3 rom.

For going back to NOS I always use the EDL method posted here on XDA witch takes me back to 1.1.7 and from there I update by OTA like ussual.

In that way I make sure that all the partitions are flashed properly and on the right slot.
[Nothing Phone 1] TheHappyBuddhist:
You can straight away flash the fastboot ROM from here. Instructions are given in this too. I believe the maintainer of this also has an open thread in this subforum. Do note that you need a clean flash when coming to stock from a custom ROM, so make a backup first.
[Nothing Phone 1] lucy1983:
Those fastboot roms are for the Global variant of NP1. I don't think it is recommended to flash them into an EEA device.
[Nothing Phone 1] TheHappyBuddhist:
AFAIK, Global and EEA are merged from 1.5.1 and up, so it shouldn't be a problem. But do check with the maintainer before flashing - just to be safe.
[Nothing Phone 1] lucy1983:
It seems that there are problems with those fastboot roms. So I think the safest way to go back to stock it's the EDL one since it doesn't depend on variants of the phone or slots flashed or malfunction of the adb and fastboot programs.
[Nothing Phone 1] lucy1983:
Besides that, the fastboot method requires the use of "fastboot flashing unlock_critical" command, as the OP stated.
[Nothing Phone 1] TheHappyBuddhist:
I don't have the critical partition unlocked (it's not mandatory to unlock that) and I have used the fastboot ROM files to come back from custom ROM to stock NOS. No issues faced and it was a simple process. But if EDL process is the best option for you, then go ahead with that.
[Nothing Phone 1] lucy1983:
Weird. On that XDA post it says that you must have unlock critical to flash fastboot roms.

And how did you do it? With "fastboot update" command followed by drag and drop the zip file or by unzipping the file and executing the "flash" script inside it?
[Nothing Phone 1] TheHappyBuddhist:
X

Unlocking the critical partition is not mandatory. Only the bootloader needs to be unlocked. Make sure you have all the drivers installed and check if your device is detected as fastboot in your PC. You can either use the fastboot command or click on the .bat file to flash it (both does the same thing anyway).
[Nothing Phone 1] lucy1983:
Trying right now to apply the fastboot method. I'm a little bit scared since it says "flashing is not allowed for critical partitions".

We'll see how it goes ...
[Nothing Phone 1] lucy1983:
Did not went well. Bootloping to fastboot mode after flashing is done. That's why I was sceptical when you said "unlock critical" is not necessary.
[Nothing Phone 1] TheHappyBuddhist:
I get the same error, since critical is not unlocked. Did you get any error at the end? Else, try to flash again. I faced it once like this - had to flash again to fix it. But I usually flash fastboot ROMs and never had this issue again.
[Nothing Phone 1] lucy1983:
Didn't get any errors at the end, it just rebooted into bootloader by itself.

Although at the beginning of the proces, after I run the .bat file it sets active slot to "b" even if my active slot was "a" (i checked it before starting the flash).

If you din the flash twice it means the first time it is flashing incorrect, on the inactive slot. The second time did you change the name of the slot in the .bat file or did you flashed the same slot?

Because I checked the active slot, it was "a" and after that I edited the .bat file by replacing the "b" in it (came like this with the rom) with my current slot, witch was "a".
[Nothing Phone 1] TheHappyBuddhist:
I used the commands, but didn't specify any slots; just the fastboot flash command.
[Nothing Phone 1] rogerrulez:
In order for some files to get flashed, you have to unlock the critical partitions. It will not work if you don't.
[Nothing Phone 1] panni:
Your fix might actually be better than the other one. I'm running yours for six days now and haven't experienced the memory creep from before. I'll report back.
[Nothing Phone 1] BertProesmans:
Also checking in to say that LukeSkyD's magisk mod V3 to disable MGLRU is stable enough for my active daily use. 72 hours+ uptime without issues.

gwolfu is also 100% right in this thinking, btw. Us few testing access block on the lru flags is at this point in time nothing more than a lucky shot.

Good enough for me 👍
[Nothing Phone 1] lucy1983:
Both modules work perfectly. They only take action in different ways.
[Nothing Phone 1] Giunta._:
Hi guys i've update to 1.5.3 and i've read that a13 freeze if rooted. to avoid it what i have to do?
[Nothing Phone 1] AnotherM1m:
https://xdaforums.com/t/nothing-phone-1-rom-ota-nothing-os-repo-of-nothing-os.4464039/post-87101173

First message, news section at the start, mglru disabler.
[Nothing Phone 1] Giunta._:
Thank you man. So i follow the classic steps and at the first boot after installing magisk patched boot i install one of the two modules is that right?
[Nothing Phone 1] pyry666:
Yes
[Nothing Phone 1] neilphetamine:
Get ready peeps. A14 Upside-down Cake is coming to Nothing.
[Nothing Phone 1] Sonalk:
I lost my root a while back due to a failed OTA , and I was about to re-root it on 1.5.3. Is this MGLRU disabler something temporary or will it always be necessary moving forward?
[Nothing Phone 1] xtcislove:
Thats nothing we know, only Nothing knows.
[Nothing Phone 1] neilphetamine:
NothingOS 1.5.4 is now live! Let's go

https://android.googleapis.com/packages/ota-api/package/da75a517b2ab113621a45c01fad5f8867caea71c.zip
[Nothing Phone 1] dallathebest:
Hi Neil,

I tried to use the zip file attached, but during the manual update It gives me the error code 2, do you know why?

I'm currently on the last firmware
[Nothing Phone 1] NightMean:
Is the MGLRU disabler still required or was it fixed as Nothing stated on their Github?
[Nothing Phone 1] SkandaH:
The pre-build value (TKQ1.220915.002/2303172039) of the incremental OTA mentioned in the post is different from the publicly released 1.5.3 software's build tag (TKQ1.220915.002/2303101650). This is the reason many people couldn't sideload the new release.

It could be possible that someone running an internal release captured the package, or there was an intermediary 1.5.3 hotfix release that we missed(?).
[Nothing Phone 1] RZ(One):
039 is the current hotfix 1.5.3

650 is release 1.5.3

so all good on that part
[Nothing Phone 1] AnotherM1m:
.3Hotfix has 2303172039 has the build value.

Judging from the error the offline updater is failing because it's checking ro.build.date.utc (THE DATE) with the pre-build-incremental... they are obviously not matching

Trying to update from hotfix to .4 right now...
[Nothing Phone 1] dallathebest:
It's strange because i'm pretty sure that the hotfix update Is already installed (ora update)

If i try to install the 1.5.3 hotfix It gives me the same error
[Nothing Phone 1] AnotherM1m:
the offline updater is bugged since .3 not hotfix

that's not usable rn to update.
[Nothing Phone 1] SkandaH:
I stand corrected. Somehow forgot about the 1.5.3 hotfix.

Nonetheless, the error about ro.build.date.utc is interesting. Can you guys dump the value of this particular prop variable so that we can track it down?
[Nothing Phone 1] dallathebest:
So do you say that i can only wait that the update comes from ota?
[Nothing Phone 1] AnotherM1m:
1679056747 on my device.

I tried to made a module to set that value and the phone didn't liked it.

trying to change it with resetprop won't work.

either that or maybe loading the old updater, or waiting for someone to release one.
[Nothing Phone 1] AnotherM1m:
UPDATE: set the time zone to China, Shangai to use the offline updater
[Nothing Phone 1] mollex:
Thanks, that does it. MvG.
[Nothing Phone 1] AnotherM1m:
Added stock and magisk patched 1.5.4 boot images.

I'll now add how to solve the -2 error on the offline updater.

Running without mglru disabler, still no crash but i will report if anything happens.

EDIT: now on rooted 1.5.4

cat /sys/kernel/mm/lru_gen/enabled

returns 1

Which is different from 3 of 1.5.3(/hotfix)

Im curious to know if stock 1.5.4 also has lru_gen/enabled set to 1 and not 3
[Nothing Phone 1] warludo:
Root ok in 1.5.4?
[Nothing Phone 1] bariz143:
Life saver. Worked like a charm ✌️
[Nothing Phone 1] Pepousek67:
Manual update all OK thank you!

View attachment 5903909
[Nothing Phone 1] burkett375:
This worked. Don't forget to switch it back, though. My notification sounds were broken until I figured it out! :)
[Nothing Phone 1] AnotherM1m:
I don't wanna jinx it but for now no problems found.

I tried the usual routine for freezes (bluetooth, discord, music, opening apps fast) and the device is still ok.

If someone has a crash let us know thanks.
[Nothing Phone 1] dallathebest:
Worked for me. Thank you!
[Nothing Phone 1] RZ(One):
I tried it here and it get stuck at Nothing logo and reboot after a minute
[Nothing Phone 1] AnotherM1m:
I didn't have this problem nor other people i chatted with.

You sure you don't have something else that's causing bootloops? Disabling MGLRU DISABLER shouldn't cause bootloops.

Edit: sorry maybe you meant a problem while updating
[Nothing Phone 1] RZ(One):
1.5.4 is installed but wouldn't boot with the patched magisk boot, installing the "original" boot back let it boot
[Nothing Phone 1] AnotherM1m:
You either have one or more modules that are causing bootloops or a corrupted magisk patched boot.

Did you use the one in the first page?
[Nothing Phone 1] RZ(One):
No modules, and yes the one from main page
[Nothing Phone 1] AnotherM1m:
You may be right, I've updated the links, try downloading and booting magisk patched 154 again

Im on slot b and dumped slot a, sorry!
[Nothing Phone 1] RZ(One):
it's working, thanks
[Nothing Phone 1] paper88:
im very confused. I just flashed the stock 1.5.3 img to update to 1.5.4 but after fastboot boot img I still see the IOS emojis from magisk module.. anyone has ideas why this happen? Should I fastboot flash the img?

What happens if I install the 1.5.3 hotfix and 1.5.4 update over sideload manually while root is still installed?
[Nothing Phone 1] AnotherM1m:
You cannot install ota updates if modified boot images are present on the phone.

If you flash stock boot, but boot magisk patched boot images then you have root until reboot, but since you have flashed stock images you can update
[Nothing Phone 1] paper88:
I flashed the stock img. Now I need to unbrick my phone :) try to flash again the patched img but after 1min nothing boot logo the phone is restarting.

EDIT: It seems the button method to EDL Mode doesn't work.. I shut down the device. wait 1 minute. Press Volume Up + Down for few seconds, plugin nothing cable and release buttons. But it will boot into fastboot
[Nothing Phone 1] AnotherM1m:
https://xdaforums.com/t/how-to-disa...agisk-and-twrp-recovery.4394991/post-86333733

To remove magisk modules

Check that you are trying to boot the correct magisk patched boot.
[Nothing Phone 1] paper88:
How can I run adb commands when i just can access bootloader?

EDIT: It worked now!!! Thanks a lot!
[Nothing Phone 1] AnotherM1m:
It just works™
[Nothing Phone 1] panni:
Huh, I'm getting this now:

View attachment 5904677

Any ideas?

Edit: restored images in Magisk beforehand, as always; set timezone to china as suggested.