Database Develop

Magisk does not work anymore after update.[v16.0][Xiaomi Mi A1]

Hi, I have been using Magisk for last one month. Everything worked fine. All my root apps worked like a charm. Today I tried to install an OTA update. For which I tried to restore stock boot image with Magisk. After Magisk showed, 'restore successful' message, I tried to install the OTA (April), but I couldn't, it kept on showing installation error.
I then tried to reboot my device but it got stuck in bootloop.
Using MiFlash Tool, I flashed back the stock ROM which restored everything including the bootloader but retained my data (user apps and settings, Magisk and other root apps were also retained.) I then updated my stock ROM with the OTA.
Then with ADB, I unlocked the bootloader and flashed the patched boot image file of April.
After booting up first time after the patch, Initially the Magisk and root checker, both showed me root access, but after a reboot, the root access was gone. The root checker now says - Root access is not properly installed on this device.
Magisk homescreen says, Magisk is Latest Version v16.0 but Magisk is not installed. On clicking the install button, it only shows two options - Download Zip only and Patch boot image file.
What should I do to get back my root access?

You have to reflash Magisk manually after every OTA update.

Magisk bricks my phone

I'm doing a clean install of this rom on my Samsung S4 using the Aroma installer (Note: problem not related to aroma - see edits below).
The installer has an option to use Privacy Guard (for phones with a locked bootloader), SuperSU, or Magisk.
If I install Magisk, the phone is stuck at the Samsung logo indefinitely. If I choose either of the other options, it boots fine.
I've tried a number of different ways around this:
1. Choosing the Magisk option in the Aroma installer.
2. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 afterwards.
3. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 with the updater-script modified (commenting out the two lines) afterwards.
4. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 afterwards.
5. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 with the updater-script modified (commenting out the two lines) afterwards.
All of the above options - every way I can think of - results in bricking the device.
Is there a way to make this work?
Edit:
1. I'm using TWRP 3.1.1.0, if it matters. And yes, my S4 has an unlocked bootloader (MDL).
2. The phone will boot fine if I choose the Aroma SuperSU option, but I discovered that SuperSU is not installing correctly either. It just doesn't brick my phone.
3. I tried running the NON-aroma rom installer. Then I used UnSU to remove the non-functioning SuperSU, and ran the Magisk 16.0 installer (normal one). Bricked.
Rebooted into recovery, ran the Magisk Uninstaller - it failed, saying "Magisk is not installed".
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
4. I added the recovery log. This shows me doing a wipe, installing the rom linked to above, flashing Magisk, then flashing the Magisk uninstaller so you can see it say that Magisk was never installed in the first place.

I've been having zero luck getting this to work. Does anyone have any ideas?

Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.

yung40oz84 said:
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
Click to expand...
Click to collapse
Thank you. However, as I stated above, although I started with the aroma installer, I eventually tried the non-aroma installer and had the exact same problem.
In addition, I also tried the normal versions as well as ones that had been patched as per the instructions on the link you posted.
So whatever is causing this does not appear to be aroma related.

Haphim said:
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
Click to expand...
Click to collapse
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?

Didgeridoohan said:
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Click to expand...
Click to collapse
I tried letting the Manager patch the boot image. I got the boot image by extracting it from the LineageOS rom. However, it would appear that the rom installer Loki's it on the fly, so the extracted rom by itself didn't pass the kernel signature check. This wouldn't be a problem if Magisk Lokied it during the patching process, but apparently it doesn't.
If there's an easy way to get the already lokied boot image off of my phone, I would appreciate being pointed in the right direction and I'll try it again. When installing Magisk, it allegedly backs up the boot image - if so, is there a way for me to recover it?
In any case, I went through the full routine all over again so that I could get the recovery log. I added it to the top post. It shows me doing a wipe, installing the LineageOS rom linked to in the top post, flashing Magisk, then flashing the Magisk Uninstaller immediately afterwards so that you can see it say that Magisk was never installed in the first place.

I just tried using TWRP 3.1.0.0 instead of 3.1.1.0 - no change.
Is there an easy way to extract the current boot.img (not the one from the rom installer, since that hasn't been Loki patched)? If so, I can try the patching through the app again.
Otherwise, if there are any other ideas, I would love to hear them.
Otherwise, I may have no choice but to buy a new phone if this one can no longer be rooted.

Can't root my Mi8 with Magisk v18.0 with working TWRP 3.2.3-1208

Hi,
I need some help
Today I successfully installed the newest stable Xiaomi.eu-ROM on my finally unlocked Mi8, using TWRP from here: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-1110-t3869729
TWRP is working flawlessly, but I didn't succeed in making root with Magisk to work.
What I did:
- I booted into TWRP
- formatted data
- rebooted back into TWRP
- flashed DM-verity disabler from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- flashed Magisk v18.0 right after from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- wiped dalvik cache
- rebooted the phone
But everytime I did it, I didn't had root access (checked with Root Checker app) when the phone finally booted up to MIUI 10.1.2.0 (PEACNFI).
I even didn't have Magisk Manager showed up.
Can you tell me what I did wrong? I don't have a clue
Thanks a lot and best regards
Mischa

what does magisk manager tell you about your magisk installation status?

Strange thing...
After I rebooted the phone, there was no Magisk Manager nor the phone was rooted, what I checked with Root Checker app.
Then I used it a couple minutes before it became really laggy. My chosen theme disappeared back to stock theme, scrolling was nearly impossible and the screen went black.
I was not able to wake up the display again, so I held down the power button a couple seconds until the phone rebooted.
Now I saw that the Magisk Manager was installed, without me doing anything else than rebooting after the phone got unusable.
Weird, right? I read that there might be lags after installing Magisk, but that it's going to be like that was surprising.
Anyway, I have root now, TWRP works, Magisk v18 is installed. Now I only have to find some must-have-modules, e.g. like stereo-mod.
BTW, could it be that Netflix isn't working on rooted phones? I always get error 14 saying that the Netflix-service is not reachable even though I have internet connection.

hey dude i know this isnt a guide
but i followed your kind of direction after spending the whole afternoon and few hours in the evening to figure how to root this phone and finally it worked (so far)
thanks a lot my man
and i didnt even format after flashing twrp i hope it didnt **** up my phone

Keep root after update with Magisk and no TWRP

If you already have root with Magisk, and don't have TWRP on your otherwise stock ROM, it is easy to retain root after upgrade. I have done this the past 4 updates.
1) Install the update through system updates. Don't reboot.
2) Open Magisk Manager and select "Install to Inactive Slot (After OTA)." Press Magisk Reboot button to reboot.
If for some reason you don't get the choice in Magisk to install to inactive slot the first time, then do this:
1) Install the update through system updates. Don't reboot.
2) Open Magisk Manager and install Magisk. Don't reboot
3) Open Magisk Manager again and this time select "Install to Inactive Slot (After OTA)." Press Reboot button to reboot.

don't you have to restore first the stock boot image in Magisk, before downloading/installing the OTA?
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
I haven"t done the procedure yet, but I"m gonna have to update soon before Q drops, I wanna stay in Pie

Nope. I just updated to android 10 (A6013_41_191214) using the same method, so that makes 5 updates. I am really glad I found this method that is so simple since I always used to dread updating and regaining root. Now it adds about 10 seconds to the process.
I did have to use the three-step process since I had not updated Magisk in a while and it wants to be on the latest version before it allows you to install to inactive slot. Unlike previous updates, I had to re-choose Nova as the default launcher.

This helped me after I hard bricked my phone trying to root android 10. Thanks!

H10N3 said:
This helped me after I hard bricked my phone trying to root android 10. Thanks!
Click to expand...
Click to collapse
No problem. When I said "I used to dread updating and regaining root" it was because i had bricked my phone trying to re-root after an update, too, so I was always on edge when doing it until I found this easy method.

It works for me from 10 oos to oos10.3

I did that, I'm now stuck on Bootloader warning screen, even after rebooting :/
Phone can't boot in fastboot, PC can't detect device anymore.
Edit: Managed to boot in fastboot mode (vol +/-/power), had to use MsmDownloadTool to unbrick.

Hi can anybody give me a hint how to procede?
- I was on 8.1 Oreo with my 1043 PL2
- did select System Update --> Android 10 (V4.16B)
- in magisk I selected "Install to Inactive Slot (After OTA)." + reboot
I just got a loop of white android one screens,
every third cycle "Android Recovery" is offering a selection of "Try again" or "Factory data reset".
Did I lose unlocked Boot loader?
Would some more retries help?
If I use "factory data reset" do I keep magisk - or would it be non rooted system?
Any hint to go to an android 10 rooted device is apreciated (preferrably with my data).
I id a TWRP BU of 8.1 system before update.
Would also a switch back to other "sltot" with 8.1 be possible?
cheers
lino
EDIT (29mar21):
since no answer,
- I selected "delete Data partition"
- Phone deleted all my data I had no BU (pictures, Download folder)
- installed MagiskManager, and at least I stayed rooted.
- now I have to setup may phone from scratch :'(
EDIT2: and I did not even realise that I that I stumbled in wrong thread (I was searching for Nokia 6.1 ... anyway)

woo that was close.
ok so, sorry, reviving from the future, hello!
for some reason, I followed this on a Nord. Bootloop.
A/B partitions!
fastboot --set-active=a

Is there a update guide for Magisk using LOS 19.1? This method does not work for LOS, only for OOS. It will give you a bootloop. I have been flashing Magisk's zip file under LOS recovery, but there should be another way to update Magisk without all that hassle. Magisk's direct install will not work.

Stuck in Download mode bootloop after updating from v20.x to v21.x

Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just restarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the download mode problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.

n00btuber said:
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just resarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the downloading problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
Click to expand...
Click to collapse
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there

Lord Sithek said:
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Click to expand...
Click to collapse
Looked like my device forum is pretty dead, which is why I asked the question here again. Thanks for the fast respone
Its probably not possible to just install a Magisk version again and overwrite the current one, probably need to uninstall first and then install it again?
There is a Magisk Module Uninstaller and a Magisk Uninstaller. Are those different things or just the same?
How to Uninstall Magisk Module Using TWRP Recovery | MagiskRoot
Uninstall Magisk Module using TWRP Recovery or Offline whenever you stuck into bootloop. Magisk Module Uninstaller and Magisk Manager for Recovery methods.
magiskroot.net
How to Uninstall Magisk From Android [2 Easiest Method]
Are you facing issues with Magisk? You can uninstall magisk from your phone with these simple and easy steps.
magiskmanager.com
Because the 2nd guide says in the end
Keep in Mind – Whenever you use TWRP as a method to uninstall Magisk, it is imperative to flash the Magisk Module Uninstaller Zip onto your device.
Does this mean I need to do the magisk module one first?

@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk

If you need to uninstall Magisk use the uninstall zips from the above linked Github repo, and if you need to uninstall modules (but those will also be removed by the Magisk uninstaller) you can do that directly from TWRP:
https://www.didgeridoohan.com/magisk/Magisk#hn_Uninstalldeletedisable_modules_from_recovery
A lot of times you can just flash another Magisk version over your installed one, but there are times where you do need to uninstall first. Since you have TWRP it can't really hurt to just try flashing whatever Magisk zip you want and it it doesn't work you can just use the uninstaller first.
One other thing to try would be the Canary release, mainly to see if you're affected by any bugs that is present in the current stable release but has been fixed upstream. You'll find the Canary app in the same Github link above.

Didgeridoohan said:
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Ok.
Was trying to use the uninstaller from his GitHub.
Trying to flash it leads to
"Updater process ended with ERROR:1
Error installing Zip file .....
Updating partition details"
So what to do now?
Trying to just flash any Magisk version to overwrite the current one leads to the same result.

I think it says Unsupported/Unknown image format

Your TWRP might be bugged/incompatible. I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).

Didgeridoohan said:
Your TWRP might be bugged/incompatible.
Click to expand...
Click to collapse
But TWRP worked fine when installing magisk the first time, I even tried the same zip folder I used to install it back then, but it wont work anymore.
Didgeridoohan said:
I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Click to expand...
Click to collapse
However, whats my stock boot image and how to reflash it? Cant find a guide for that on GitHub.
Would a Factory Reset wipe all Magisk stuff and my TWRP Partition as well?

Does anyone know what is going on between Magisk and Google? It seems Google has removed Magisk Manager from the Play Store AGAIN! What's more, I downloaded and installed the apk but when I try to use it to install the latest Magisk the install fails. Tried installing the Magisk zip via TWRP, and while it doesn't show any errors, I still don't have root.

Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you

n00btuber said:
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
Click to expand...
Click to collapse
Sounds to me like you need to reflash your ROM, not TWRP. According to your OP, you're running Android 7, but it doesn't say if it is stock or a custom ROM.. If it is stock, then use Frija.exe to download the ROM and then flash th AP, BL and HOME_CSC md5 files with Odin. If it is a custom ROM, use TWRP to flash the ROM and gapps. DO NOT try to flash Magisk. Right now there seems to be a problem with Google disabling Magisk. Wait till it is resolved before attempting to get root.

@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...

Didgeridoohan said:
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Click to expand...
Click to collapse
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.

lewmur said:
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
Click to expand...
Click to collapse
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".

Didgeridoohan said:
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Click to expand...
Click to collapse
That 's my mistake. Play Store would put up a lot of "Magisk Manager" stuff, but I never really tried any of it because flashing Magisk would give me the Manager. But even that "stuff" no longer shows up.
Butt Magisk Manager still won't install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.

lewmur said:
Then why won't Magisk Manager install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
Click to expand...
Click to collapse
That will be an incompatibility between Magisk and your device and has nothing to do with Google (blame your OEM for doing weird stuff instead).

Thanks for the help guys, had to flash the ROM, now its working again.