yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 1] rogerrulez:
I have tried the "getprop ro.product.system.name" on my phone but the results are nowhere what is explained in the first thread. What I get is "qssi". Anyone know what that means ?
[Nothing Phone 1] rogerrulez:
Never mind. Found the answer. Have to leave out the word system. So it's "getprop ro.product.name".
[Nothing Phone 1] jskeletti:
Is there no "Full update package" for 1.1.8 and 1.5.2 in order to update rooted phones? (Havn't found any anywhere)
[Nothing Phone 1] burkett375:
1.5.3 incoming...

https://www.reddit.com/r/NothingTech/comments/11r85p7
[Nothing Phone 1] AnotherM1m:
1.5.3 Incremental zip from 1.5.2

https://android.googleapis.com/packages/ota-api/package/68158669e0fc6d6eee95e2612c2e84ed840faeec.zip

I've checked the metadata, should work both on global and eea
[Nothing Phone 1] AnotherM1m:
There are still no links for 1.5 full zip

You have to update with ota zips. It is still possible to keep root with them

There is a 1.1.8 EEA

First you update with the incremental ota to 1.1.8 and then to 1.5.2.

Even if rooted you can receive ota updates and install them, magisk got updated to support this.

https://android.googleapis.com/packages/ota-api/package/5a8a872c8fa2071424af6272bd78806f55d4aeda.zip

sideloading zip and keeping root is still a little bit clunky but it's doable, you can try searching this thread for guides
[Nothing Phone 1] jskeletti:
I've tried. Keep on getting Error 20.
[Nothing Phone 1] HofaTheRipper:
1.5.3 incremental over 1.5.2:

https://android.googleapis.com/packages/ota-api/package/68158669e0fc6d6eee95e2612c2e84ed840faeec.zip

1.5.3 stock boot:

96 MB file on MEGA

mega.nz

1.5.3 magisk patched boot:

96 MB file on MEGA

mega.nz

DONT ROOT ATM.... SYSTEM FREEZES CONSTANTLY AFTER ROOTING 1.5.3!!! DONT KNOW WHY!
[Nothing Phone 1] AnotherM1m:
Do you have an eea or a global device?

1.5.2

If EEA

https://android.googleapis.com/packages/ota-api/package/6718db370773ad0191b970df545f54c4163a014e.zip

if Global

https://android.googleapis.com/packages/ota-api/package/ae6c43b3022f2d554bd7a15e3dffb363e6b89000.zip

1 ) go to magisk, uninstall, restore to stock

2 ) put the ota file in the ota folder, dial *#*#682#*#* and select the right file

3) Keep an eye on the phone, when it powers off hold vol down button and keep it until it loads fastboot-bootloader

4) on a pc open a terminal and boot the magisk patched boot for your new sw

5) open magisk, install, direct installation and reboot when it tells you

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
[Nothing Phone 1] jskeletti:
Thanks for the guide. I try to update from 1.1.7 (fix? don't know how to find out). I've uninstalled Magisk (full uninstall, device rebooted) but when I try to start 1.1.8 update from "local system update" I still get Error 20.
[Nothing Phone 1] AnotherM1m:
Can you post a screenshot from software information where we can see the build number?
[Nothing Phone 1] jskeletti:
Of course.View attachment 5862715
[Nothing Phone 1] jskeletti:
I've flashed the stock boot.img of 1.1.7 and flashed ota package to 1.1.7fix and it worked. Now the build numer ist Spacewar-S1.1-221129-1525EEA. But when I try to flash 1.1.8 there is error 20 again.
[Nothing Phone 1] AnotherM1m:
@1stStep sorry i linked you the wrong 1.1.8 eea incremental

@jskeletti sorry try this 1.1.8

https://android.googleapis.com/packages/ota-api/package/c4313bd73c334c10db148217d3b9edffc2725077.zip
[Nothing Phone 1] jskeletti:
Still error 20.
[Nothing Phone 1] AnotherM1m:
1.1.7hotfix can only go to beta and then to 1.5.2 stable. You can try that.

Otherwise here's the full 1.1.7 (non hotfix) eea zip to downgrade.

https://android.googleapis.com/packages/ota-api/package/0e6855d19dbcdf328449e4d06386a6257bb1aadd.zip

the stable road for eea devices is 1.1.7 (not hotfix), 1.1.8, 1.5.2
[Nothing Phone 1] jskeletti:
Can I downgrade it with "local system update" or sideload?
[Nothing Phone 1] AnotherM1m:
No, you'll have to download the full zip, download payload_dumper and use it to have all the partitions' images

flash each ones with fastboot. i don't know if there is something that when flashed wipes your userdata
[Nothing Phone 1] jskeletti:
Thanks for the advice! I first tried the path through the beta. I updated from 1.1.7fix to 1.5.0 with the zip file, that worked. Now I update via Nothings OTA. After updating all versions I will install magisk again.
[Nothing Phone 1] jskeletti:
Worked perfect!
[Nothing Phone 1] zedroprom:
how did you get these images, is there no falla full ota ?
[Nothing Phone 1] jskeletti:
Now I've got an other problem with 1.5.3: the phone freezes completely when I start any app. I can't do anything, even not turn off to standy by. After a long while the phone restarts itself and shoes this on display before it reboots. Any ideas?

Edit: It not only freezes after startig an app. It also freezes after booting and entering the pin.

View attachment 5863179
[Nothing Phone 1] gwolfu:
rooted?
[Nothing Phone 1] HofaTheRipper:
yeah same for me... only solution for now was unroot... dont know why this happens
[Nothing Phone 1] pyry666:
Whitch magisk version are you using? I havent updated yet and if something is this borked now I am not even gonna do it. And does this happen even with no mudules or zygisk installed/enabled?
[Nothing Phone 1] HofaTheRipper:
tried with different versions, canary, magisk delta .... all the same
[Nothing Phone 1] gwolfu:
happened to me on magisk stable (25.2) even with no modules installed

thinking has something to do with Zygisk, but yet to confirm
[Nothing Phone 1] pyry666:
Oh, thats a real bummer then. Hopefully there is some sort of solution soon. But after reading about this i am not gonna update. Imo latest update brakes something then and needs hotfix asap
[Nothing Phone 1] pyry666:
If its zygisk, thats an absolute no go then! I really need it for some apks
[Nothing Phone 1] HofaTheRipper:
its not zygisk... deactivated it and same issue
[Nothing Phone 1] AnotherM1m:
What version of safetynet fix do you have? The latest is v2.4.0
[Nothing Phone 1] HofaTheRipper:
disabled all modules and zygisk.... system still freezes
[Nothing Phone 1] gwolfu:
As soon as I get home will have a test by flashing older 1.5.2 boot.img and not patching running 1.5.3

so basically run with 1.5.2
[Nothing Phone 1] HofaTheRipper:
i tried.... 1.5.2 boot.img doesnt boot.... stuck at nothing logo
[Nothing Phone 1] gwolfu:
yeah just read that they changed the security patch level, so the idea dropped right after reading
[Nothing Phone 1] jskeletti:
For now it helped to flash the 1.5.3 unpatched boot.img
[Nothing Phone 1] froz3nbug:
Did you get 1.5.3 OTA??
[Nothing Phone 1] aleqa:
Hello, i have the same problem. Hope someone find the solution.
[Nothing Phone 1] pyry666:
That dont explain that weird freezing right? Unless they messed up something kernel side

Edit: and that update is what 92mb, whole boot image is larger
[Nothing Phone 1] jskeletti:
That from #626 and the boot.img from #629
[Nothing Phone 1] gwolfu:
Update size doesn't matter as incremental packages just patch what's needed.

However the size of the boot partition will always be the same no matter what.

Anyway, the update is not the issue since using stock boot, won't have issues.

Something from magisk is cause.
[Nothing Phone 1] AnotherM1m:
Did you all flashed the magisk patched boot image or you just booted it and did magisk's direct installation?
[Nothing Phone 1] HofaTheRipper:
just booted and then direct install...
[Nothing Phone 1] ot_inc:
v1.5.3 boot.img

https://github.com/reindex-ot/reindex-ot.github.io/blob/main/boot_img/lahaina_boot_v1.5.3.zip?raw=true
[Nothing Phone 1] HofaTheRipper:
tried also your file but freezing issue is still there....
[Nothing Phone 1] gwolfu:
tried with magisk delta ?
[Nothing Phone 1] HofaTheRipper:
yepp 🤷‍♂️
[Nothing Phone 1] pyry666:
Yeah, i know but this just seems strange. Amd if every other manufacturer would be in this situation. Id talk to johnwu but this first..
[Nothing Phone 1] Adrian312:
same here, I tried stock image and it works fine, as soon as i patch it with magisk I am getting random freezes. i've tried removing all modules - no luck, only time when its not freezing its stock image = no root, now I am trying patched image from another thread and so far looks fine. I will wait and see

EDIT: i just fastboot boot that patched image, I have root for now - unless rebooting. my guess - its related to magisk itself in some way, I am pretty positive that if I flash it OR direct install from Magisk, I am going to see that freezing again.
[Nothing Phone 1] HofaTheRipper:
I am done with root for now and relocked my bl 🙈. In a Telegram group someone rooted, and did a factory reset after that. He said since that he has no freezing issue 🤷‍♂️. Good luck to all 👍.
[Nothing Phone 1] Adrian312:
well I hope there will be a better solution, I am too lazy to start from scratch! :) GL man
[Nothing Phone 1] pyry666:
Delete
[Nothing Phone 1] pyry666:
That telegram solution was posted already, i just hadnt refreshed this page
[Nothing Phone 1] warludo:
what is the solution ? thank
[Nothing Phone 1] pyry666:
First root, then factory reset. But apparently its not working 100% either..
[Nothing Phone 1] warludo:
it is better to wait.....
[Nothing Phone 1] pyry666:
Yes, and if rumors are true, nothing has stopped rollout for 1.5.3 due bugs anyway for now
[Nothing Phone 1] warludo:
thanks for your help anyway ;-)
[Nothing Phone 1] 1stStep:
Hi @AnotherM1m

Sorry for late reply.

Thanks. Is the quoted link below the one for me too from EEA117noFix?

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

I feel it is the definitive ultimate road.

Bye bye
[Nothing Phone 1] 1stStep:
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
[Nothing Phone 1] AnotherM1m:
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
[Nothing Phone 1] 1stStep:
Many thanks for quick reply man

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 ?
[Nothing Phone 1] AnotherM1m:
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
[Nothing Phone 1] 1stStep:
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 😵‍💫
[Nothing Phone 1] AnotherM1m:
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
[Nothing Phone 1] 1stStep:
Before I adb fastboot boot ?

[EDIT]... I have to re-read the process of "fastboot boot patched.img" and install Magisk to understand this.
[Nothing Phone 1] 1stStep:
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?

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
[Nothing Phone 1] AnotherM1m:
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
[Nothing Phone 1] Pepousek67:
Another update.... Hotfix

Information is from Facebook!

Ps: I haven't received the 1.5.3 update yet! Czech Republic EU
[Nothing Phone 1] AnotherM1m:
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.
[Nothing Phone 1] aleqa:
Hope this one support root. Will wait for the file to try!
[Nothing Phone 1] AnotherM1m:
Freezes are not fixed

Im on 153 hotfix and root and just froze two times

Proceed at your own risk
[Nothing Phone 1] AnotherM1m:
Stock 1.5.3.fix

MD5: 5ab2cd46f2953b394a78cec9ed130c04

File on MEGA

mega.nz

Magisk Patched 1.5.3.fix

MD5: 72c972807c2db953bff3d399f19ea390

File on MEGA

mega.nz
[Nothing Phone 1] whamslambam56:
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:

Factory Data Reset.

Wait for first reboot to reach erasing data screen. (Watch carefully this screen basically just flashes by. Pic is attached)

Immediately after screen goes black from erasing data screen hold only volume down button until fastboot shows.

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"

System should boot, then proceed through setup.

Open Magisk and click ok to reboot.

Then system should boot without any freezes.
[Nothing Phone 1] kumar akarsh:
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.
[Nothing Phone 1] whamslambam56:
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.
[Nothing Phone 1] Pepousek67:
I couldn't resist and installed the 1.5.3 update manually. Immediately after the update, the hot fix update came via OTA! Everything is OK!

View attachment 5868701
[Nothing Phone 1] Adrian312:
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 ;)
[Nothing Phone 1] AnotherM1m:
Im trying to do some tests to try and find out why the phone crashes with a modified boot img

Im a noob in the android environment so my reasons can seem naive.

Since we are getting ramdumps at crash i thought the problem was the ramdisk in the boot.img

So i've created a boot img with 1.5.3.fix kernel and boot and 1.5.2 ramdisk, but the device still crashes

If it's not a corrupted boot.img problem, maybe it's the system checking if everything's fine and noticing a modified environment throws a crash.

So it's the system's fault.

Does anyone know a way to check what background services there are and if one of them is the culprit? How can we check what makes the phone crash?

Also what if the problem is magisk itself? if factory resets seems to fix the issue for many, maybe updating from .2 to .3 brings magisk to keep some old keys and values that when used/accessed crash the phone

I do not know if anyone tested this, but totally uninstalling magisk and deleting all data of it and installing it brand new could fix the issue...?
[Nothing Phone 1] Oswald Boelcke:
Moderator Announcement

Ownership of this thread has been transferred from @Pho3nX to @AnotherM1m!

Regards

Oswald Boelcke

Senior Moderator
[Nothing Phone 1] Chaotick:
Just got 1.5.3 in Poland EU. Size 91.76 MB :)
[Nothing Phone 1] TheNewHEROBRINE:
I don't have a Nothing phone but I have some suggestions:

Did anyone try using latest bleeding-edge build of Magisk from: https://github.com/topjohnwu/Magisk/actions ?

If it still has issues I suggest opening an issue on the repo to notify topjohnwu.
[Nothing Phone 1] muppetz:
You should receive soon 1.5.3 Hotfix . I got it few days ago
[Nothing Phone 1] AnotherM1m:
Downloading artifacts and installing the apk should be the right way to go, right? Because after installing apks from actions magisk manager app crashes.

In the afternoon i'll also try to logcat the device

EDIT: Magisk implements a signature check to block malicious clones, to move from official to action you should first install the debug apk found on magisk's main page, do direct install and then install the actions apks...

15:26, im trying

Force ramdisk format to lz4_legacy for v4 #2878

Action, i'll let you know if i get any crash or what

UPDATE

15:42 the device crashed with the latest action build
[Nothing Phone 1] Chaotick:
What does HFchange/add?
[Nothing Phone 1] TheNewHEROBRINE:
Thank you for trying out the latest build. Can you open an issue on the repo reporting this crash problem?

Edit: someone already did so https://github.com/topjohnwu/Magisk/issues/6780
[Nothing Phone 1] muppetz:
The update is 16.61 MB in size. In essence, this update resolved a problem that prevented the NFC toggle from working as intended, and that led to alerts showing up when the Quick option was enabled.