Database Users

The strangest issues...

Hey all!
Those of you monitoring the unofficial LineageOS thread may have seen me talking about this already. I've been having issues with Magisk. I'm running their beta versions for 13.0.
So here's the story...
I have wanted to pass SafetyNet since May, when I got this phone and rooted it. I obviously went to Magisk, and when I realized that 11.6 was not passing SafetyNet, I decided to try the 13 betas. These didn't pass either, but since they were more recent than 11.6, I stuck with them. But when I heard of the Universal SafetyNet Fix Module, I immediately tried it.
Bottom line, these are my issues:
1. Magisk will not install the module. I go to Magisk Manager -> Modules -> + and select the ZIP for the module. Magisk gives me a toast saying "Installation error!" (See screenshot).
2. Okay, so now I want to start fresh and see if it works then. I boot into TWRP, flash the lastest Magisk uninstaller (08 June), and boot. Nope! Stuck on the "device unlocked" screen with ID: bad key.
3. Uhh.. maybe the stock boot image will work? I go to TWRP and flash the stock boot.img taken from the stock firmware. Still ID: bad key and I'm stuck again.
And I can boot successfully if I flash a Magisk 13.0 beta.
So, does anybody have any solutions? I think I may just have to reflash stock firmware.. not my top choice. Thank you for any help and reading through my long post :good: :highfive:

Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )

eskamhl said:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
Click to expand...
Click to collapse
Will give it a shot and update when I see results.
Edit: Nope. I've a feeling that I'll have to start from scratch by flashing stock firmware.

Try flashing the safetynet fix in trwp.

triggerlord said:
Try flashing the safetynet fix in trwp.
Click to expand...
Click to collapse
Tried already. Still no.

Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!

smitharro said:
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
Click to expand...
Click to collapse
Lol, was doing this all on the stock ROM. See my original response to triggerlord's post.
Edit: issues fixed with a clean install of the pure Nexus ROM. I'm assuming this would be the case with a clean install of the stock ROM, but I am definitely not switching anytime soon (this ROM is amazing!)

Root lost after 9.0.13

Hey guys.
Just updated to 9.0.13 last night and today I saw that my root was gone.
I was rooted with Magisk, and did the same as usual. Uninstalled Magisk, downloaded and install the update from System, and after that I Installed Magisk on the second partition (after OTA update) just like in the tutorial..
Any solutions to regain root without wiping the phone ? I already fuc*d it up last month and lost everything .
Regards,
Switiz

In my case it installs magisk after updating and everything worked fine. Reinstall it from the TWRP and it should work.

I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot

Switiz said:
I don't have twrp installed. is there any possibility to install it without pc ?
p.s I don't have a recovery. every time I try to go to recovery, I have a menu with 3 languages ( 2 Chinese and English ) and the only options are Wipe data and cache and reboot
Click to expand...
Click to collapse
How did you get root without flashing magisk inside of twrp? And if you did the update that came thru your phone that's why you lost root.. from what I read it's best to always flash full stock. No partial updates

You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.

Thank you. I will try when I get home.
I update using the tutorial from the page you provided :/.
"Update Process for Rooted Users
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete."
It's not the first time. I don't know why this time it didn't worked..

After booting in twrp and installing Magisk, after reboot, I still don't have root :|
https://imgur.com/a/hjGwQkR

Try this
https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238

OhioYJ said:
You updated incorrectly. So now you have the stock recovery. You will need a PC to fix it. It's not a big deal, you're just starting over. You will need to boot the TWRP image again, flash the TWRP installer. Then flash magisk. BEFORE you do anything, back up all your data.
Follow this guide here. <-- Use this to reinstall TWRP and Magisk.
Use this guide to update from now on. <-- Download update files here. Dirty flash them, follow the TWRP instructions. I don't even uninstall Magisk personally, but go ahead if you want, as the official instructions say to. No data loss. No losing root. Do not use the OTA update (unless you are stock), do not use Magisk to update (Magisk works, it just seems to mess people up), etc.
Click to expand...
Click to collapse
Thanks for this link.

Not sure if you've managed to fix this issue, but I've never used to the uninstaller. I boot into TWRP and flash the full system image and then reboot back into TWRP and flash Magisk onto the active partition. If you don't reboot inbetween then you end up flashing Magisk to the current (old) partition rather than the new upgraded partition.

Bootloop after flashing Magisk on Global ROM

Hi, I need your help. I got a K20 from China with China official ROM.
I linked my Xiaomi account, then unlocked bootloader (had to wait 7 days).
I downloaded fastboot Global ROM 10.3.6.0 and installed it via Xiaomi Flash Tool (making sure to not relock bootloader)
Phone rebooted ok, now it shows as MI 9T and have Google Services installed, but Google Pay is not working...
So I want to root with Magisk to pass CTS SafetyNet test.
Downloaded Magisk 19.2
I installed TWRP (from the post in here) , rebooted to TWRP, installed Magisk zip file. No errors given. Wiped Dalvik/Cache.
But when rebooting to system I got a bootloop and phone goes back to TWRP.
I had to install Magisk uninstaller to get phone working again.
Any help on how to get Magisk working on Global ROM flashed via Fastboot ?
Thanks

After install Magisk, do a factory reset and reboot.

Schnedi said:
After install Magisk, do a factory reset and reboot.
Click to expand...
Click to collapse
I will try that, thanks for the suggestion.
Is it safe to remove xiaomi account from the phone before doing factory reset ?
I am asking cause last time after I flashed fastboot ROM first thing I had to do was insert xiaomi account pwd, but I would prefer to have a phone with no account linked to it after a factory reset.
Cheers,

seblog said:
I will try that, thanks for the suggestion.
Is it safe to remove xiaomi account from the phone before doing factory reset ?
I am asking cause last time after I flashed fastboot ROM first thing I had to do was insert xiaomi account pwd, but I would prefer to have a phone with no account linked to it after a factory reset.
Cheers,
Click to expand...
Click to collapse
You can remove it, yes.

Schnedi said:
You can remove it, yes.
Click to expand...
Click to collapse
Thanks a lot!
After a factory reset finally I got it working!
I am a bit concerned cause I have then updated via Recovery ROM to 10.3.7 Global (so global to global) but I lost root !
Should I have done it via TRWP ? Cause I did it via the Updater of MIUI.
I reinstalled Magisk via TWRP but got bootloop again, so I had to factory reset once again !
Is that normal ? What will be the best way to update without loosing everything ?
Cheers

are you able to make google pay working?
For me after installing magisk and formating data, when I open magisk it shows additional setup is required. If I say yes, it reboots and again goes back to revocvery bootloop.

seblog said:
Thanks a lot!
After a factory reset finally I got it working!
I am a bit concerned cause I have then updated via Recovery ROM to 10.3.7 Global (so global to global) but I lost root !
Should I have done it via TRWP ? Cause I did it via the Updater of MIUI.
I reinstalled Magisk via TWRP but got bootloop again, so I had to factory reset once again !
Is that normal ? What will be the best way to update without loosing everything ?
Cheers
Click to expand...
Click to collapse
As far as I know you should never do any updates through MIUI when you have custom recovery. I was on EEA 10.3.7 and flashed twrp and magisk. Then updated to EEA 10.3.12 by wiping data, sys, catch and installing 10.3.12 recovery rom through twrp and then magisk and its working fine

Direct installing newest Magisk update wiped out my entire system & forces fastboot

Direct installing newest Magisk update wiped out my entire system & forces fastboot
I just want to make it clear that I've rooted this phone since a year or 2 ago and the updates for Magisk have been working fine until recently. Saw that there was a 20.2 Magisk update, direct installed it per recommendation, and it forces me into Fastboot mode loop. The only way for me to even get out of it was to go to download mode where TWRP saved my ass cause it didn't show up when trying to boot into recovery using normal methods (i.e. pressing power + vol down and fastboot commands). While on TWRP, I've noticed it said 0mb so I tried doing the "Change into EX2 and back into EX4" method. It worked but my data was wiped (however Internal shouldn't be wiped). I reflashed stock Oreo rom + root and tried to direct install Magisk update again to see if that's really the culprit and fair enough, it did the same thing. There goes my data & everything else that was in there for years.
Tl;dr
DO NOT DIRECT UPDATE MAGISK 20.2 BC IT WIPES YOUR SYSTEM

D00pie said:
I just want to make it clear that I've rooted this phone since a year or 2 ago and the updates for Magisk have been working fine until recently. Saw that there was a 20.2 Magisk update, direct installed it per recommendation, and it forces me into Fastboot mode loop. The only way for me to even get out of it was to go to download mode where TWRP saved my ass cause it didn't show up when trying to boot into recovery using normal methods (i.e. pressing power + vol down and fastboot commands). While on TWRP, I've noticed it said 0mb so I tried doing the "Change into EX2 and back into EX4" method. It worked but my data was wiped (however Internal shouldn't be wiped). I reflashed stock Oreo rom + root and tried to direct install Magisk update again to see if that's really the culprit and fair enough, it did the same thing. There goes my data & everything else that was in there for years.
Tl;dr
DO NOT DIRECT UPDATE MAGISK 20.2 BC IT WIPES YOUR SYSTEM
Click to expand...
Click to collapse
I did the same to me and I did my install from twrp. Can you give me an idea of what to do? I appreciate it, johnm Thanks I found another thread here, gonna try it, will report back

jmacie said:
I did the same to me and I did my install from twrp. Can you give me an idea of what to do? I appreciate it, johnm Thanks I found another thread here, gonna try it, will report back
Click to expand...
Click to collapse
Your data is pretty much done for if you do this update. You have to flash a new rom from TWRP.

D00pie said:
Your data is pretty much done for if you do this update. You have to flash a new rom from TWRP.
Click to expand...
Click to collapse
There's another thread that explains to get the rom boot .img and re-flash that, clear dalvik and reflash magisk 20.1. It worked for me no data loss

jmacie said:
There's another thread that explains to get the rom boot .img and re-flash that, clear dalvik and reflash magisk 20.1. It worked for me no data loss
Click to expand...
Click to collapse
Ah okay. Disregard that then. I was a bit salty that I lost my data without finding this out lol. Thank you for the solution!

Here is the ultimate solution https://forum.xda-developers.com/showpost.php?p=81378123&postcount=13 Don't panic!

Phone stuck in bootloop after updating Magisk

I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?

Dirty flash ROM or if 1st step doesn't work factory reset and install everything

Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!

I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.

[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.

en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen

Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.

i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.

I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.

I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system

flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.

flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.