Database Develop

Phone became problematic and asking to decrypt data!

Everything was working great yesterday after I flashed the new 5.0 OOS through TWRP.
But this morning it was like my device suddenly decided to act funny. First it started FCing different apps all the time.
Then it got into a continuous restart loop.
Finally when it settled, I discovered all these problems:
- Home and recent buttons not working
- Developer options were empty
- Factory reset not working
- When I tried to reboot into recovery, I was asked for a password for decrypting data under a Mount title. I entered my pin and continued with some info for updating partition. I reflashed the stock 5.0 rom and the bluespark v.8.54 recovery, wiped cache, but nothing changed.
Any ideas?

Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?

thes3usa said:
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
Click to expand...
Click to collapse
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Everything looks fine now? Because when you said the device couldn't finalise the setup process, it may have been a corrupt flashable package. But since it's fixed now, that doesn't seem like the issue.
Sorry I was misinformed about the TWRP version, I thought there was only one version of TWRP by blu_spark that can be used. Turns out, there is another. Sorry about that.
Cheers!

Yee I hope the clean install did the trick.
Although 2 days ago everything was also running great before the catastrophic behavior.
And the worst part is that I have no clue what caused this. I didn't mess with root settings or new apps, had stock kernel installed and no new apps were installed recently.
Sent from my ONEPLUS A3003 using Tapatalk

Help Please!

Hello. I'm stuck in a bootloop and need help. I have android 7.1.1 with the October security update and the latest franco kernel. Bootloader is unlocked. Here is what happened.
Flashed TWRP and rooted with magisk. Attempted to install xposed SDK25 module through magisk. Restarted phone and xposed did not show up in magisk as installed, all my other modules were also gone.
I'm now thinking that magisk is somehow broken so I attempt to uninstall it through the manager. Phone reboots and is now in a bootloop.
What should I do?

A new install of course.
Press vol down and on/off at the same time.
Go to Recovery.
In TWRP Wipe system/data/cache.
Install your rom and gapps again and reboot system.
See if this solves your boot loop.
If it boot correctly, then install your custom apps.

@ReneZeiss: He doesn't need to wipe data or cache to resolve this. Doing so would be overkill. All he needs to do is reinstall the ROM, because from his description it sounds like his kernel ramdisk became corrupted when Magisk tried restoring the untouched version.
@sandman96: You don't say whether you're running the stable version of Magisk (14.0) or are on the beta channel (14.6). If the problem occurred on the beta channel, switch to the stable channel. If on the stable channel, try the beta channel. Also, after reinstalling your ROM, but before installing Magisk, take a nandroid backup.

Strephon Alkhalikoi said:
@ReneZeiss: He doesn't need to wipe data or cache to resolve this. Doing so would be overkill. All he needs to do is reinstall the ROM, because from his description it sounds like his kernel ramdisk became corrupted when Magisk tried restoring the untouched version.
@sandman96: You don't say whether you're running the stable version of Magisk (14.0) or are on the beta channel (14.6). If the problem occurred on the beta channel, switch to the stable channel. If on the stable channel, try the beta channel. Also, after reinstalling your ROM, but before installing Magisk, take a nandroid backup.
Click to expand...
Click to collapse
Thanks for the replies. I ended up reflashing from a factory image. Was able to restore all my data except for text messages but I'm working on getting those from a twrp backup.
I had the stable version of magisk installed. I'm just not going to try the xposed framework again lol.

I find Xposed to be more trouble than it's worth. I only used it on my Dell Streak as there were some patches for Android 2.3.x that were never integrated into the ROMs I produced for that device. I briefly tried it on my Galaxy S4 and promptly uninstalled it. My N6 never had it.
Xposed fans don't like me much, mostly because I wish it would go die in a fire.

The few times I tried installing Xposed thru the Magisk Repo caused Magisk to screw up for me too. Solution is just install the Xposed app then flash Xposed in TWRP lol. For some reason the Repo install method doesn't seem to work often if at all, least for me lol. Flashing in TWRP like you would if you had SuperSU has worked 100% of the time for me :-/
::Edit:: oh yea lol, if you take anything from the experience take the lesson learned of why TWRP makes it extremely simple to make a complete backup of everything disable compression of backups and that minute or two of extra wait time is worth it when something happens, since it's not a matter of IF, only a matter of WHEN lol.

Galaxy S7 stuck at booting after 14->15 upgrade

I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone, and then it was stuck at the pulsating SAMSUNG logo.
So, next step would be obvious: get into TWRP and install Magisk 14.0.
And so I did, and so it failed. This time I got a bootloop. The "Galaxy S7 powered by Android" thing appears for a few seconds, and then vibrates and starts over. And over, and over, and over.
So then, I "installed" the Magisk Uninstaller. Thinking to get rid of all traces of Magisk that introduced this problem in the first place.
So I did, and now I'm back at the first problem: stuck at booting.
Then installing Magisk 14 AND wiping cache&dalvik: boot loop
Then I installed the uninstaller again, then Magisk 15, and wipe the cache&dalvik. And it's back at being stuck while booting again.
Brilliant. What do I do to fix this?

Are you using a custom ROM, or a port ROM, or a custom kernel?

It's all stock, except for it being rooted.

I'm having the same issue. Canadian S7 W8, Stock ROM with root, Magisk 14, upgraded to 15 using direct install through magisk manager.

Yes, exactly that. No offense, but that's helping neither yourself nor me nor anyone else. Have you been able to figure anything out?
Maybe how to produce some kind of log output?...

Same thing happened to me just now. Never would have thought that upgrading through the Magisk app would cause this. I've tried all of the above and have also tried installing v 12.0 but still no dice.
I even tried a factory reset and still no dice. This is seriously infuriating.
Guess I will have to reflash everything and start fresh. If anyone else has any other ideas I'm all ears.

I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?

thany2 said:
I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone
...
What do I do to fix this?
Click to expand...
Click to collapse
Mate 8 running 7.0 stock except rooted, running Magisk 14, did the same thing and I'm in the same boat. Have also tried removing magisk, reinstalling 14 no dice. Have not factory reset yet (trying everything else before that step) but it looks like it won't help.

thany2 said:
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
Click to expand...
Click to collapse
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.

Ok, I'm still not in that loop... yet.
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.

I'm still not in that loop... yet.
ct1aic said:
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
Click to expand...
Click to collapse
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui

If you can' t solve download Magisk Uninstaller https://forum.xda-developers.com/attachment.php?attachmentid=4370032&d=1514240372
and Magisk 14.0 https://forum.xda-developers.com/attachment.php?attachmentid=4264532&d=1504713887
Then reboot in Twrp (hope you have it) and flash
1 uninstaller
2 14.0

I had the magisk 14.5 and I installed the 15 via twrp on top, and it updated normal. Is there a problem updating this way?

@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.

Same here, updated from v14 to v15 and got a nice bootloop.
Huawei Mate 8 with Nougat (stock) and TWRP.
EDIT:
Solved!
Flashed my stock boot.img backup through TWRP, then booted my phone and downloaded v14, flashed v14 through TWRP, booted my phone again and downloaded v15 with Magisk Manager app and checked "Preserve AVB 2.0/dm-verity" and then tapped "Install" using "Direct Install (recommended)"

thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Because a custom kernel disables dm-verity. There's an issue, mainly on Samsung devices, with the dm-verity detection in Magisk v15.0. It's under investigation...
Meanwhile, flash a dm-verity disabler together with Magisk v15.0 and you should be good to go.

I'm fairly certain you need a custom kernel. I'm also on the S7 and without one I've always boot looped, I think it has to do with dm-verity.
EDIT: I didn't notice there was a second page so I guess I didn't really say anything new, oh well, sorry!

ct1aic said:
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
Click to expand...
Click to collapse
Awesome! Glad it worked. Happy new year.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Hey man. I'm just telling you what worked for me. If you don't want to try it then don't.

fattyspecial said:
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Click to expand...
Click to collapse
Hello,
Here is the problem I personnaly had (solved now !) :
Initially, my wife had a G930F (samsung galaxy S7) and a Custom 7.0 rom (i think it was the "AlexNDR.G930FXXU2DRAG" rom...but I'm not sure at all because it was installed several months ago or even years) with TWRP as recovery and Magisk as root.
I saw that Magisk not working (since when ? I don't know because it was not my phone). So, I tried to update it via the Magisk application (the initial goal was to use then Titanium Backup).
Logically, the phone then rebooted to install the Magisk update... except that a Boot Loop appeared.
I then tried many things :
1° Downgrade or Upgrade the TWRP recovery to 3.0.0.0; to 3.2.2.0 and to 3.5.2.9.0 (thes recovery .img files are here: https://eu.dl.twrp.me/herolte/)
=> It didn't work, and the bootloop continued (but, at the end, i keep the TWRP v.3.5.2.9.0)
2° I tried to uninstall and reinstall Magisk
(cf. the "Custom Recovery" tuto here : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
=> Failure. Still the BootLoop... (either with the .zip v19.1 or the .zip v23)
nb: I even tried to donwload other magisk files but still the same bootloop (cf.https://forum.xda-developers.com/t/collection-of-magisk-modules-v2.3575758/page-13#post-72542167)
4° I tried to change the kernel by using TGPKernel (https://forum.xda-developers.com/t/...2-30-tgpkernel-v6-15-5-3-18-140-esd2.3462897/)
=> Failure, the bootloop remained...
5° Finally, I found a solution :
a° I downloaded the rom "G930FXXU2DRAG_DevBase_v4.6.zip" (via the following tutorial here : https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/)
, more exactly at the following location : https://androidfilehost.com/?fid=818070582850489124
b° Then, as indicated in the tuto (https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/), I renamed the .zip downloaded on my PC to "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" (ps: so, i add "..._rescue.zip)
c° After that, I copied the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" on my micro SD.
d° In the recovery I finally installed the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" and the phone restarted after a long time (or maybe 5 minutes, I didn't watch).
=> End of the bootloop and all data was preserved!!!

Flashing Magisk modules crashes phone

Any time I flash a new module in Magisk, when the phone reboots everything crashes (i.e. Google has stopped working, system UI has stopped working, clock has stopped working, etc etc)
Everything will crash and then my phone will constantly reboot. I don't know how I fixed it but I got Viper and YouTube Vanced to work, but anytime I try flashing a new module, it will break Viper and start crashing and restarting again until I hard reset or just wait it out.
Any suggestions? I know that I flashed whatever TWRP is in the 11g root tutorial but there was a new TWRP made for the LG G6. Maybe if I flashed that one or does that not have anything to do with this?
Any suggestions would be appreciated
Magisk is up to date.

roger.hernandez91 said:
Any time I flash a new module in Magisk, when the phone reboots everything crashes (i.e. Google has stopped working, system UI has stopped working, clock has stopped working, etc etc)
Everything will crash and then my phone will constantly reboot. I don't know how I fixed it but I got Viper and YouTube Vanced to work, but anytime I try flashing a new module, it will break Viper and start crashing and restarting again until I hard reset or just wait it out.
Any suggestions? I know that I flashed whatever TWRP is in the 11g root tutorial but there was a new TWRP made for the LG G6. Maybe if I flashed that one or does that not have anything to do with this?
Any suggestions would be appreciated
Magisk is up to date.
Click to expand...
Click to collapse
What modules are you using? I've had it happen quite a bit for me but I figured out what the issue was.

beany23 said:
What modules are you using? I've had it happen quite a bit for me but I figured out what the issue was.
Click to expand...
Click to collapse
It happens with any module, but I've successfully got several installed and working such as viper, Greenify, YouTube vanced, Emoji one, Google product sans font, and Magisk Google DNS
What was the issue and how'd you fix it?

roger.hernandez91 said:
It happens with any module, but I've successfully got several installed and working such as viper, Greenify, YouTube vanced, Emoji one, Google product sans font, and Magisk Google DNS
What was the issue and how'd you fix it?
Click to expand...
Click to collapse
Easy. Uninstall magisk wipe cache 3 times then reboot recovery again then flash magisk 16.4 beta should fix your issue. Remember to download magisk 16.4 first then follow the above steps.

beany23 said:
Easy. Uninstall magisk wipe cache 3 times then reboot recovery again then flash magisk 16.4 beta should fix your issue. Remember to download magisk 16.4 first then follow the above steps.
Click to expand...
Click to collapse
When you say wipe cache 3 times, what do you mean by that? Go into recovery and wipe and keep rebooting three times?
Also, what method did you use to get into recovery each time and to flash Magisk?

roger.hernandez91 said:
When you say wipe cache 3 times, what do you mean by that? Go into recovery and wipe and keep rebooting three times?
Also, what method did you use to get into recovery each time and to flash Magisk?
Click to expand...
Click to collapse
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.

​
Metabolic12 said:
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Click to expand...
Click to collapse
Yes quick question, did you use Magisk uninstaller package from thread or just uninstall Magisk directly from the app?

Confused on how to uninstall Magisk without encrypting my device or loosing my boot or messing anything like that up

Also, wipe Dalvik cache and cache or just cache only?

Okay I guess I'm going to:
Boot into laf TWRP recovery
Flash Magisk uninstall zip
Wipe cache three times
Reboot into recovery
Flash Magisk v16.4 beta
Reboot system
Profit.... hopefully

Metabolic12 said:
No, you just need to go into recovery and wipe cache 3 times back to back to back. You can use the file manager in TWRP to check the cache after wiping to see if its clear. If it is, reboot to recovery and flash Magisk. If you have anymore issues let me know.
Click to expand...
Click to collapse
Great well I can't uninstall Magisk from recovery
Still getting error that TWRP can't mount /system
Can anybody help?

roger.hernandez91 said:
Great well I can't uninstall Magisk from recovery
Still getting error that TWRP can't mount /system
Can anybody help?
Click to expand...
Click to collapse
Sure you can. Magisk doesn't root the system so all of the files you need to discard are in /data and /cache. You need a copy of the stock kernel in image format, if Magisk didn't make a back up. I gotta say bro, I haven't uninstalled Magisk or tried, so I don't know what's going to happen when you do this.
If your phone force encrypts after flashing the kernel, you may be screwed and have to format data and lose everything. This could possibly also brick your device beyond help. Since you can't mount your system in TWRP, if for some reason it fails encryption or DM-Verify into a bootloop, from the LAF or recocery modification, it won't boot. At least, not until you find a way to mount the system, which I think will be near impossible.
With that being said, if you decide to move forward you can either wipe data and cache or remove the files one by one. Your choice.

Well I gotta say, I've had a hell of a day fixing this thing. System partition got wiped somehow and had to fight to get my backup restored, thankfully I had one. Basically came back from the dead. Ended up wiping my entire internal storage to get TWRP to shut the hell up about decrypting, flashed new recovery again, flashed Magisk v16.4 beta, and now I'm good to go. Didn't have any of the issues mentioned above. And now I'm not having /system mounting problems or the force quits upon flashing a new mod. Everything seems good.
Appreciate y'all. You guys are awesome for taking the time to help.

roger.hernandez91 said:
Okay I guess I'm going to:
Boot into laf TWRP recovery
Flash Magisk uninstall zip
Wipe cache three times
Reboot into recovery
Flash Magisk v16.4 beta
Reboot system
Profit.... hopefully
Click to expand...
Click to collapse
Don't do it from laf twrp flash the latest h872 recovery and do the steps u posted

beany23 said:
Don't do it from laf twrp flash the latest h872 recovery and do the steps u posted
Click to expand...
Click to collapse
Nah man I actually did have to do it from laf recovery because it wasn't working from regular recovery. Had to flash it from both and also formatted data and I was good to go. I got it all figured out.

OnePlus 6T shutting down right after startup after installing Magisk 18.1

Hello!
I have a weird problem after I updated Magisk to 18.1 on my OnePlus 6T. It installed properly and the phone will also properly boot. But just when it arrives at the lockscreen, the phone will show right away the message "Shutting down phone" - and then the phone will restart to the recovery. Why is it doing this and how can I fix it? Is there somehow a restart command in the autostart of my phone?
I tried already reflashing the system image. This made it possible to start the phone again. But after installing Magisk again, it will do the reboots again.
Thanks for any help!

I was able to fix my problem!
Was doing it the following way (in case sb else has this problem as well):
- Boot twrp from fastboot (the official twrp - with bluspark it didn't work because it doens't decrypt the data partition)
- Run the Magisk uninstaller zip
- Run the Magisk installer zip
- Phone will boot normally again
Just reflashing the factory image wasn't enough in my case. There must have been some files left from Magisk somewhere. Removing them with the Magisk uninstaller fixed the problem.

Thanx a bundle, works...

thanks for sharing this solutions!

---------- Post added at 10:28 PM ---------- Previous post was at 10:18 PM ----------
1651321 said:
I was able to fix my problem!
Was doing it the following way (in case sb else has this problem as well):
- Boot twrp from fastboot (the official twrp - with bluspark it didn't work because it doens't decrypt the data partition)
- Run the Magisk uninstaller zip
- Run the Magisk installer zip
- Phone will boot normally again
Just reflashing the factory image wasn't enough in my case. There must have been some files left from Magisk somewhere. Removing them with the Magisk uninstaller fixed the problem.
Click to expand...
Click to collapse
It worked on the OnePlus6 after updating the new OOS and reinstalling twrp and magisk. you saved my life !!

tnx dude, it worked.

oos beta 13 and magisk 19.4 and still works, you just saved me hours of troubleshooting. thanks.

thanks
i was facing the same issue on OP 5T, it works fine

Worked for me too!

Man oh man! You saved my beautiful sunday.

Just came here to confirm it worked perfectly in my OP5T after applying 9.0.9.
Same procedure to the letter thanks!

1651321 said:
i was able to fix my problem!
Was doing it the following way (in case sb else has this problem as well):
- boot twrp from fastboot (the official twrp - with bluspark it didn't work because it doens't decrypt the data partition)
- run the magisk uninstaller zip
- run the magisk installer zip
- phone will boot normally again
just reflashing the factory image wasn't enough in my case. There must have been some files left from magisk somewhere. Removing them with the magisk uninstaller fixed the problem.
Click to expand...
Click to collapse
thank you, thank you so much