Database Develop

Losing root after a while?!

Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!

Remove magisk manager from greenfy-like apps, close the androidpay app after using anf if possible keep magisk manager opened worked for me

My setup is SuperSU 2.78 SR4, suhide, magisk v9, rootswitch 1.3.3.2 and PoGo and Android Pay works. I used the ramdisk patch. Root is never lost.

gamer765 said:
My setup is SuperSU 2.78 SR4, suhide, magisk v9, rootswitch 1.3.3.2 and PoGo and Android Pay works. I used the ramdisk patch. Root is never lost.
Click to expand...
Click to collapse
Um magisk thosent do anything in that case as supersu is independent from it and su hide is the only thing doing anything in that case

Majesty00 said:
Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!
Click to expand...
Click to collapse
The "losing root" problem with Magisk Hide is known and under investigation. I saw someone claiming that they didn't experience it anymore after doing a complete uninstall of Magisk and starting over. Otherwise, the only solution at the moment is to reboot the device or disable Magisk Hide.

Xmaster24 said:
Um magisk thosent do anything in that case as supersu is independent from it and su hide is the only thing doing anything in that case
Click to expand...
Click to collapse
I'm giving him an alternative that works where he doesn't lose root spontaneously and need to reboot to fix.

gamer765 said:
I'm giving him an alternative that works where he doesn't lose root spontaneously and need to reboot to fix.
Click to expand...
Click to collapse
But magisk in your alternative those nothing it's completely inactive, he would only find magisk useful if he was using another module but not xposed as superSU plus systemless xposed always leads to SN fail

Majesty00 said:
Hello folks!
I have a weird problem with my rooted OPX 3.1.3. I'm still using this version because Xposed is not yet officially supported with the november patch (last time I checked, it was being tested).
I haven't been able to successfully hide supersu and Xposed with Chainfire's SuperSU (even tough I think it's very good!). So, instead, I'm using PHH's SuperSU 266-2 with Magisk v9 (and Xposed 86.6). As expected, I can use Android Pay (by hiding it with Magisk Hide functionality), but after a while, I lose the root access... I don't know what to do to cause the problem, I just know it happens. So, I can't give you a step-by-step to reproduce it, which makes it more difficult to diagnose.
A reboot "fix" this, but it's kind of annoying. As this happened to someone else? What could cause this kind of problem?
Thanks and let me know if you need more info!
Click to expand...
Click to collapse
+1
I have same issue. I randomly loose root and I have no idea why. I hope someone can help.
I also will try to disable the magisk hide and see if it helps.

FlintStoned- said:
+1
I have same issue. I randomly loose root and I have no idea why. I hope someone can help.
I also will try to disable the magisk hide and see if it helps.
Click to expand...
Click to collapse
I am having the same problem, but am not using the Magisk hide feature. Have to reboot to restore root - very annoying!

I disabled battery optimization on magisk and super user so we'll see if these fixes it or not.
Edit: as long as magisk hide is on this doesn't seem to help. It's a bug with magisk hide apparently.

I have noticed this twice, and it seems to be related to having the phone die from low battery? This is the only common condition I can recognize with the last two times it has happened.

Revenge282 said:
I have noticed this twice, and it seems to be related to having the phone die from low battery? This is the only common condition I can recognize with the last two times it has happened.
Click to expand...
Click to collapse
This happens to my phone and it's not died from having low battery.

Link_of_Hyrule said:
This happens to my phone and it's not died from having low battery.
Click to expand...
Click to collapse
Yeah, I let it die last night with Magisk Hide off, so that certainly seems to be the issue. I kept root and other modules after I turned it back on.
But even with Magisk Hide on, I never experienced any issues unless the phone died. I had rebooted it a ton of times and never lost any modules. I'm convinced that it has something to do with a "ungraceful" reboot situation and how Magisk Hide must unload itself.

Maybe that's an issue as well but my phone if I pick it up after it's been sitting there and charging or a good amount of battery and try to use root it says there isn't root unless I restart.

The same issue with Magisk hide on Xiaomi Redmi Note 3 Pro
Sent from my Xiaomi Redmi Note 3 using XDA Labs

Started experiencing this on Nexus 6p stock NMF26F. Predominantly happening overnight.

tzortst said:
Started experiencing this on Nexus 6p stock NMF26F. Predominantly happening overnight.
Click to expand...
Click to collapse
Also facing this problem on Nexus 6 (nougat 7.0.1).
In addition to this, when ROOT is lost, Magisk Log is empty.
It happens whatever the day/hour... it just seems to happen after a few hours without using the phone.
- Phone never dead due to battery empty
- android pay DISABLED
- PokemonGO not installed
- Android installed from a Factory Image (november patch NBD91P)
- Magisk V9 + phh_root_r266-2 (the only module)
- magisk hide ENABLED + magisk busybox DISABLED + systemless hosts ENABLED
- greenify installed, but neither Magisk Manager nor SuperSU in the greenified applications

lebaud07 said:
Also facing this problem on Nexus 6 (nougat 7.0.1).
In addition to this, when ROOT is lost, Magisk Log is empty.
It happens whatever the day/hour... it just seems to happen after a few hours without using the phone.
- Phone never dead due to battery empty
- android pay DISABLED
- PokemonGO not installed
- Android installed from a Factory Image (november patch NBD91P)
- Magisk V9 + phh_root_r266-2 (the only module)
- magisk hide ENABLED + magisk busybox DISABLED + systemless hosts ENABLED
- greenify installed, but neither Magisk Manager nor SuperSU in the greenified applications
Click to expand...
Click to collapse
Magisk log is empty because the Magisk Manager can't access the cache folder where it's located (no root, remember ).
It's a known bug, probably due to Magisk Hide being a little too aggressive.

I've noticed that I lose root every time I open Magisk Manager, so I've decided to hide it from to app drawer & have Greenified it in an attempt to stop it from running at all after initial boot - will report back if it works or not.
Edit: so I rebooted and haven't opened the Magisk Manager app since last boot and haven't lost root yet, so, so far so good. (15hrs 30m uptime) - will update if I do.
Edit2: haven't lost root in 2 days now, so looks like a temporary fix?

enabling Magiskhide caused me to lose root

Advisory : Safetynet seems. to have been updated

EDIT: TOPJOHNWU IS WORKING ON A FIX RIGHT NOW, WAIT FOR MAGISK 13 RELEASE OR ENABLE CORE ONLY MODE AS A TEMP FIX.
Posting this from my phone so sorry for any errors here.
Google seems to have updated safetynet within the last few hours, on 2 devices. That previously passed with magisk. There is an easy way to fix it, that I don't really want to post here as Google probably read the forums. Let's just say it's easy to fix, but you not using modules any more. Hoping for an update soon if that's possible and I can provide any logs or details to the dev if needed.

manor7777 said:
Posting this from my phone so sorry for any errors here.
Google seems to have updated safetynet within the last few hours, on 2 devices. That previously passed with magisk. There is an easy way to fix it, that I don't really want to post here as Google probably read the forums. Let's just say it's easy to fix, but you not using modules any more. Hoping for an update soon if that's possible and I can provide any logs or details to the dev if needed.
Click to expand...
Click to collapse
Yeah, it seems like Google has updated SafetyNet, now I can't pass the check
Sent from my Pixel using Tapatalk

Same here.

Using Galaxy s6, same here.

Thanks it works

Glad to know I'm not the only one. They will probably patch what I've done later on but at least I can still use my phone with root. Can back to stock as I'm on a OP3T but I don't want to lol

So i need to uninstall my youtube ad free module?

bam099 said:
Same here.
Click to expand...
Click to collapse
Yep... may not be related, but noticed random "unable to parse data" toast messages earlier today. Later caught google play downloading. Killed download, then ran safetynet check. Failed CTS profile mismatch. Again, any of those symptoms could be unrelated. Just reporting anomalies.
bummer

Nexus 6 running Pure Nexus 7.1.2 on Magisk v12.0
SafetyNet Failed: CTS profile mismatched
Yeah, looks like another swing from Google.

how can i pass safteynet i cant get to hide my root to log into snapchat

Same here it definitely updated. Haven't done anything with my phone in a while. Suddenly failing the check

I thought i was the only one

If you can live without modules, enable 'Magisk Core Only Mode' in Settings and you'll pass SafetyNet again.

Works but..
blk_jack said:
If you can live without modules, enable 'Magisk Core Only Mode' in Settings and you'll pass SafetyNet again.
Click to expand...
Click to collapse
I have a problem with Mario run, safetynet pass And magisk hide is enabled but Mario run always give me the 804-5100 error code

Btw, it seems not all modules trigger SafetyNet. My suggestion to people is to test each module one at a time and see which are affected.
To do this:
- Disable all modules
- Enable the first module
- Reboot
- Check if SafetyNet passes
- Disable the first module and enable the second
- Reboot
- Check if SafetyNet passes
- Repeat.......

angelus_kun said:
I have a problem with Mario run, safetynet pass And magisk hide is enabled but Mario run always give me the 804-5100 error code
Click to expand...
Click to collapse
Maybe try clearing data in the game. You might have tripped a flag and the game is remembering that your device has failed.

blk_jack said:
Maybe try clearing data in the game. You might have tripped a flag and the game is remembering that your device has failed.
Click to expand...
Click to collapse
Nope, i tried that before And dosen't work, irñts very strange because on my moto G4 with magisk hide And safetynet pass i was able to play without issues until now, And i don't know why because i have the same modules like before, And i have the same issue on my galaxy Tab A6 t280 with the same modules, safetynet pass etc :\
---------- Post added at 03:10 AM ---------- Previous post was at 02:42 AM ----------
andybfmv96 said:
Same here it definitely updated. Haven't done anything with my phone in a while. Suddenly failing the check
Click to expand...
Click to collapse
Mario run work again i solved the issue deleting all modules enable magisk core And systemless host (for adaway at least) magisk hide with Mario run selected, clear Mario run data And reboot oh Well :/ bye bye to ad away OGyoutube module

angelus_kun said:
Nope, i tried that before And dosen't work, irñts very strange because on my moto G4 with magisk hide And safetynet pass i was able to play without issues until now, And i don't know why because i have the same modules like before, And i have the same issue on my galaxy Tab A6 t280 with the same modules, safetynet pass etc :\
---------- Post added at 03:10 AM ---------- Previous post was at 02:42 AM ----------
Mario run work again i solved the issue deleting all modules enable magisk core And systemless host (for adaway at least) magisk hide with Mario run selected, clear Mario run data And reboot oh Well :/ bye bye to ad away OGyoutube module
Click to expand...
Click to collapse
Did you even read OP's post? Google updated a security patch and now most of us can't pass SafetyNet.

MiuKing said:
Did you even read OP's post? Google updated a security patch and now most of us can't pass SafetyNet.
Click to expand...
Click to collapse
Yes And the solution is don't use modules anymore that work for me And you And everyone Even if you pass safetynet you need to enable magisk core to use broken apps like Mario run

I can confirm that enabling "Core Only Mode" in Magisk Settings does pass SafetyNet.
(Sigh), now magisk modules break SafetyNet. Now what do we do?

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.

Use Magisk I guess? Use it to hide root from that app.

Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?

ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.

Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?

ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?

First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?

ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.

ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs

Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?

After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?

ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?

I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).

ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...

Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).

ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?

After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...

probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.

Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

"ctsProfile: false" in Magisk Manager after August update

I know other folks had issues with earlier updates, but this is the first time I've seen this. I skipped the last few updates. Does the Magisk patch method no longer work for rooting the Pixel 4 XL? Or is there some way to fix this?

The "hardware off" module from Displax might help you.
Sent from my Google Pixel 4 XL using XDA Labs

It's hardware based so nothing you can do about it

Patching your boot image with Magisk still works. With the recent implementation of hardware attestation, apps can now recognize if your bootloader is unlocked and safetynet checks result in ctsProfile failing. Magisk Hide still works and you can still hide root from most apps but cannot hide that your bootloader is unlocked unless you use either the hardwareoff mod or the Magisk Props mod.

Lughnasadh said:
Patching your boot image with Magisk still works. With the recent implementation of hardware attestation, apps can now recognize if your bootloader is unlocked and safetynet checks result in ctsProfile failing. Magisk Hide still works and you can still hide root from most apps but cannot hide that your bootloader is unlocked unless you use either the hardwareoff mod or the Magisk Props mod.
Click to expand...
Click to collapse
I tried MagiskHide Props Config but that didn't work - unless I need to do more than just replace the fingerprint. Replacing the fingerprint did not fix the problem. It's likely the Pixel 4 XL uses hardware backed key attestation to check the bootloader state, which I think means MagiskHide Props Config won't solve the problem.
I did find and install the hardwareoff mod and that fixed the problem. Thanks everyone who mentioned that. It was not available for download in Magisk but I found it buried deep in a 4000+ post thread on XDA.
https://forum.xda-developers.com/ap...systemless-t3432382/post83028387#post83028387

fuarkgl3 said:
It's hardware based so nothing you can do about it
Click to expand...
Click to collapse
Eventually you will be right, once Google makes hardware backed key attestation permanent. But for now the hardwareoff mod works.

No work for me
Basic integrity and CTS profile remains false.

madmartian said:
I tried MagiskHide Props Config but that didn't work - unless I need to do more than just replace the fingerprint.
Click to expand...
Click to collapse
Just for clarification: you would also have had to use the "Force BASIC attestation" option. It basically does the same thing as the hardware off mod, so you're good to go already...

So I have the same problem basic integrity but the cts profile fails. Iam in the January update.
I've done anything to fix it but 0 for me. And the problem is that it just happened from nowhere it was everything ok I was passing the safety net and in a moment the gpay made me a warning about contactless payments and the problem started.

Escribis said:
So I have the same problem basic integrity but the cts profile fails. Iam in the January update.
I've done anything to fix it but 0 for me. And the problem is that it just happened from nowhere it was everything ok I was passing the safety net and in a moment the gpay made me a warning about contactless payments and the problem started.
Click to expand...
Click to collapse
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..

Lughnasadh said:
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..
Click to expand...
Click to collapse
Can you give me the link my friend?

Lughnasadh said:
Go over to the Magisk thread. It's discussed there in detail and there has been a Magisk Mod released to fix it..
Click to expand...
Click to collapse
Found it, thank you very much sir.

Can you share the link please?
I also woke up to Google Pay warning, an update, than lost Magisk. I've re-installed it but now failing safetynet. Been attempting to fix it for 2 hours now

mushtafa said:
Can you share the link please?
I also woke up to Google Pay warning, an update, than lost Magisk. I've re-installed it but now failing safetynet. Been attempting to fix it for 2 hours now
Click to expand...
Click to collapse
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com

Found the link. It works, just need to setup Google Pay again https://github.com/kdrag0n/safetynet-fix

Question [issue] GrapheneOS, Magisk and June update [SOLVED]

The latest OTA update made my phone bootloop if i re-flash magisk patched init_boot image...
After I asked Stock users, it looks like it's a GrapheneOS june update + Magisk specific issue.
Do someone else also have this issue?
Phone boots normally, then reboot to recovery instead of reaching lock screen.
For now, I re-flashed panther-factory-2023061402 init_boot.

Have you tried Magisk canary version? or maybe GrapheneOS doesn't like june update and newest Magisk and you need to either go back down to stable Magisk or an older version of Magisk?
Actually, after re-reading your OP, a module might be the cause of the bootloop -- I've recently seen similar behavior from other members where device bootloops or crashes during/right-after loading & starting up -- if you were on the stock ROM I would suggest you loading up in Safe Mode to see if it is a module issue; I don't know anything about GrapheneOS so I don't know if it offers anything similar. I wonder if the adb command to remove modules at boot would work....

mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/

Albirew said:
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Click to expand...
Click to collapse
knew it....
glad I helped get you there!