Develop Bugs

Installing Magisk results in bootloop

I'm not new to these things, but this time it seems I'm totally stuck.
What have I done till now?
- unlocked bootloader
- checked Anti-Version -> 4
- followed step 5 in this thread
What have I gained?
- I'm able to boot into TWRP and also to install several ZIPs. But every ZIP I install goes into bootloop. I have to flash the uninstaller-versions and then my phone works totally normal.
- I tried to install Magisk v16.0, v16.3 and v16.7, no success with each of them.
- I patched boot-image through Magisk itself -> also no success, still bootloop
What haven't I done yet?
- used lazyflasher to permanently flash TWRP as recovery
What are my phones creds?
- I'm on MIUI 9.6.3.0
If I'm right I can't flash any MIUI-version below 9.5.19.0 because of Anti 4. How will I be able to install Magisk and have a working phone? I found a thread where several links were included, one of them showing to some kind of ROM-kitchen, where I'd have the choice to create a custom ROM-zip with Magisk included (among other things like wallpapers, ringtones, which ROM-Version) but I can't find the link anymore. Would that be a possibility? Installing a MIUI beta 10?

just try using lazy flasher...

Ok, maybe I identified my problem: I have to booot into TWRP and flash the recovery within TWRP and afterwards I can install Magisk.
Can someone please confirm?

Tischbein said:
Ok, maybe I identified my problem: I have to booot into TWRP and flash the recovery within TWRP and afterwards I can install Magisk.
Can someone please confirm?
Click to expand...
Click to collapse
Yes exactly..

Thanks, worked this way.

Damn Root......

No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,

Don't bother with twrp
Just use magisk.
Download the factory pixel image on your PC , unzip the boot.img file and transfer to your phone.
Open magisk manager and install magisk by patching the boot.img file U just transferred.
Copy that new patched boot img back to your PC.
Use ADB to ADB reboot bootloader
Type: fastboot flash boot patched_boot.img
That's it

mediaman123 said:
No matter what I try I am unable to root my P2XL on Android 10......
The process I am taking is to boot up twrp and flash the latest Magisk zip, however it fails right at the end with the error failed to mound system and vendor.....
I have just tried to do it again but with a clean install of the October update but nothing has changed.......
the October update wasn't without issue either as that too failed and I had to factory reset the September image and update OTA.....
anyway, any thoughts or advice on how to achieve it or what might be wrong.......
is there specific TWRP versions I need to boot from etc,,,,
Click to expand...
Click to collapse
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.

Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.0-0.img; in twrp, flashed 3.3.0-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.

Az Biker said:
[/HIDE]
Since it has been a few months since I messed with my 2 XL, I followed the upgrade 9x guide in my sig to make sure I didn't forget/skip anything.
I just jumped to 10 last night, root, twrp, and cust kernel.
fastboot latest factory image (I left the -w intact for a clean wipe since going form 9 to 10-but have read it is not necessary)
booted back into bootloader and fastboot boot twrp 3.3.3-0.img
once in twrp I install 3.3.3-0
in twrp installed latest EX kernel for 10
rebooted to system
let it boot up fully for a few minutes
booted into twrp
flashed magisk 19.4
rebooted to trwp (superstition for me)
rebooted to system
checked magisk hide in magisk manager
hit systemless hosts in magisk manager
rebooted
Fresh install of android 10, rooted, with cust kernel.
You mentioned the "failed" notice. I've read several places that TWRP will throw the "failed to mount" warning (or something like that) but that it is a false flag. I got this as well and just continued on.
There may be many diff ways to accomplish this, but THIS method worked for me.
Click to expand...
Click to collapse
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx

1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
My safety net passes in magisk, but I don't use any apps that I can verify that with.

jlokos said:
I used a similar method:
I used Duece's Script to flash and format data with April image ( I wanted to able to decrypt with pattern lock); rebooted to system; then rebooted back into bootloader and used Duece's Script to flash but not format data with October image; booted back into bootloader and fastboot boot twrp 3.3.3-0.img; in twrp, flashed 3.3.3-0 zip, rebooted to system, and did initial phone set up; rebooted to twrp, flashed caesium kernel and magisk 19.3 and rebooted to system. Everything worked fine. I did get failed to mount" warning in twrp but both the kerkel and magisk worked fine.
Click to expand...
Click to collapse
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks

docluv01 said:
Hi, for TWRP, are you using 3.3.0.0 or 3.3.3.0
I was only able to find 3.3.0.0
Thanks
Click to expand...
Click to collapse
Sorry; an extra 3; I'm using TWRP 3.3.0.0.
---------- Post added at 07:58 AM ---------- Previous post was at 07:37 AM ----------
1902 said:
Hi, by "checked magisk hide", do you mean that you were able to bypass google's safetynet?
I havn't rooted my P2 XL on A10 since i wasn't sure i will be able to bypass safetynet!
thx
Click to expand...
Click to collapse
I DL magisk hide module and use it for two apps, one for comcast business and the other which regulates my home thermostat.

Wow, thanks guys.....you have all laid out pretty well your processes which I will go through later on....
It's strange, as everything is installed and magisk believes it working it just doesn't pass thee root check..
I'll get back to you with my progress...??

OOS 10.0.11 HD65BA (EU) patched magisk boot image - SIM not detected after flashed

Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater, then I have dumped the payload and grabbed the stock 10.0.11 boot.img from there, patched with Magisk (after the update install) and then flashed the patched image. I have got root access and Magisk is working fine, but after I flash the patched image, the phone can't see the SIM slots. If I re-flash the stock boot.img, it just works fine - but I loose root of course.
I have tried multiple times to patch the stock boot image, but all my attempts was failed, if I've got root access, the phone can't see the SIM card.
I used this method since 10.0.7 to upgrade and until now it just worked fine, without any problem and I don't have any idea what could go wrong.
Any idea, link, etc are welcome.

Had same problem with 10.0.9 EU, have you disabled all magisk modules? For me that was the cause

Hitman478™ said:
Had same problem with 10.0.9 EU, have you disabled all magisk modules? For me that was the cause
Click to expand...
Click to collapse
No, I didn't disable any module before the update. How should I now proceed?
I have tried this:
- flashed patched boot image
- disabled all the modules
- flashed stock boot image
- flashed patched boot image, now this time the modules were disabled
and other one, because this wasn't worked:
- flashed patched boot image
- uninstalled (with restore images) Magisk
- flashed stock boot image
- flashed patched boot image
but my issue still occurs in both cases. If I disable all the modules the SIM is working with the patched boot image, if I enable any of them, the SIM stops working.
So the problem is that I haven't disabled the modules, but now what should I do?

Also same here
I just bought my 7T and i flashed 10.0.9 EU Magisk working fine but i lost sim card and no WIFI
Please any help
Thanks.

Sir Mohd said:
Also same here
I just bought my 7T and i flashed 10.0.9 EU Magisk working fine but i lost sim card and no WIFI
Please any help
Thanks.
Click to expand...
Click to collapse
Well, I did the hard way → flashed a fastboot ROM with full wipe and started clean. Now it's fully working again - but I had to configure everything...
Unfortunately I couldn't find any better solution to make this work.

Th3Scr34m said:
Well, I did the hard way → flashed a fastboot ROM with full wipe and started clean. Now it's fully working again - but I had to configure everything...
Unfortunately I couldn't find any better solution to make this work.
Click to expand...
Click to collapse
Mine as well working now,
I flashed OB1 EU and i reinstall Magisk again and patch it
So SIM, WIFI, Magisk working fine now,
I think there is a problem with latest update with magisk IDK if some1 can confirm by any chance
Thanks.

Th3Scr34m said:
Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater, then I have dumped the payload and grabbed the stock 10.0.11 boot.img from there, patched with Magisk (after the update install) and then flashed the patched image. I have got root access and Magisk is working fine, but after I flash the patched image, the phone can't see the SIM slots. If I re-flash the stock boot.img, it just works fine - but I loose root of course.
I have tried multiple times to patch the stock boot image, but all my attempts was failed, if I've got root access, the phone can't see the SIM card.
I used this method since 10.0.7 to upgrade and until now it just worked fine, without any problem and I don't have any idea what could go wrong.
Any idea, link, etc are welcome.
Click to expand...
Click to collapse
Do you have the OOS native recorder ? Uninstall it and you are good to go. Don't recall if disabling it and rebooting will do the trick

Felheipe said:
Do you have the OOS native recorder ? Uninstall it and you are good to go. Don't recall if disabling it and rebooting will do the trick
Click to expand...
Click to collapse
Yes I had (and have now with the new setup) but I had it before 10.0.9 and didn't cause this kind of issues - actually I did this process 3 times without any problem.

You have to remove call recording module and.than reinstall

Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...

karazz said:
Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...
Click to expand...
Click to collapse
Magisk OTA Upgrade Guides:
https://topjohnwu.github.io/Magisk/ota.html

Sir Mohd said:
Magisk OTA Upgrade Guides:
https://topjohnwu.github.io/Magisk/ota.html
Click to expand...
Click to collapse
Thanks for the link, but I already found that information (and realized my mistake).
But on that page there is no clear answer on my original question. Does the flashing of patched_boot.img make me lose my apps and data?
I tried and found out, the apps and data are still there.
And, more important, magisk is working again!
Copied my oxygenOS-update.zip to my pc and patched my boot.img using these steps starting from step 2.
GoodSoul said:
You can also patch the boot.img yourself.
Here is how:
.) Download latest Stock OOS
.) Extract boot.img using payload.bin dumper (needs python)
.) Install Magisk Manager on your device
.) Copy boot.img to your device
.) Patch boot.img using Magisk Manager
.) Copy patched boot.img to your pc, reboot your phone to fastmode and use 'fastboot boot patched_boot.img' to boot from patches bootimage.
.) Run Magisk Manager, choose direct install
-> Voila, you have a rooted OP7pro.
Click to expand...
Click to collapse

karazz said:
Made the OTA update yesterday, stupid as I am, I rebooted after updating causing me to lose root.
When downloading stock image, patching boot.img and transferring the patched boot.img back using fastboot, will that make me lose my apps and data? Can't find a clear answer unfortunatly...
Click to expand...
Click to collapse
Simply flashing stock or patched boot img would not impact your apps and data, evenprevious magisk modules.

Th3Scr34m said:
Hi there,
Yesterday I have downloaded the full OTA package with Oxygen Updater,
whats the link u downloaded 10.0.11 HD65BA (EU) ota package from?
Click to expand...
Click to collapse

Hi,
OnePlus7T HD1903
I had working root, survived many OTA's, after each OTA I launched Magisk, flash inactive boot bank, it works perfect.
Last time i did the same, but have bootloop.
I downloaded ZIP with OTA, extracted payload, extracted stock boot.img, flash into phone so it boot
Tha same image I'm trying to patch with Magisk Manager 7.5.1 - but everytme i have bootloop.
Force encryption / dm-verify enabled.
Can I have working, patched IMG for my phone?
Or how to resolve my issue?

After trying to root with Magisk...

After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?

If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.

killer23d said:
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
Click to expand...
Click to collapse
already done, if i flash it again will it work? because im still stuck in the bootloop

Nicster205 said:
already done, if i flash it again will it work? because im still stuck in the bootloop
Click to expand...
Click to collapse
if you reflash the factory boot.img then you'll get out of bootloop.

Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse
reflashing the factory boot.img seems useless. you can long-press the power button to force power down. then power up to the fastboot mode,and reflash the full factory image(11 or 10). the nomal methon working on 10 seems dizzy in 11 now.

fwiw, heres the path i used...i hate making it more steps than needed (tranferring boot image to device and back again for magisk patching for example)...
1) flash-all.bat (with wipe enabled - because clean install)
2) Immediately on reboot from 1 and before it gets anywhere near to beginning of setup: fastboot boot twrp-3.4.0-1-taimen.img
3) adb push Magisk-e66b0bf3(20425).zip /tmp
4) adb shell twrp install /tmp/Magisk-e66b0bf3(20425).zip
5) adb reboot
6) after reboot, install canary magisk manager (for whatever reason doesnt install from TWRP flash)
7) open canary magisk manager and enable magiskhide

This is caused by twrp
Use android toolbox, just boot twrp, flash magisk

boot into twrp go to advanced fix bootloop option reboot
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse

Question Bootloop after magisk on 12.5.3.0.RKHEUXM

Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you

suloku said:
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
Click to expand...
Click to collapse
Try flashing the older patched boot.img on the new stock firmware.

On the 12.5.3.0 ill patched boot.img from 12.5.1.0 and all right.

Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended

i have the same issue of auto updated and lost my root access.
Which boot.img I should Magish'd to get the root access again?
Currently installing my twrp
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
if Flash Current TWRP fails, go to Backup > Refresh Sizes and try Flash Current TWRP again
Click to expand...
Click to collapse
Currently at the Resizing stage
Edit 1: failed, I have the error bootctrl error that prevent me from installing after resizing.
I have flashed the twrp3.5.2 directly to boot resulting in bootloop and needed to install the Boot.img from the 12.5.1 from the previous bulit
Edit: actually I can ignore that error.
Magisk installed but safety checked failed even I have the "universal safety check module installed "
Also the app thoax isn't working

I'd try removing all magisk modules, installing stock 12.5.3, then using magisk apk to create patched boot.img and flash it with fastboot (fastboot flash boot magisk_boot_patched.img)
Also, maybe try flashing bot boot_a and boot_b? I had a problem were my active boot partition changed and phone became even more broken.

suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
Might wanna also uncheck Automatic system updates in the Developer settings to be safe.

suloku said:
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
There is a setting in the Xiaomi system updater that had by default checked auto-update. That setting need to be disabled/unchecked as well.
Since you have root with Magisk, can also Force stop or debloat the updater app, so the system will not update itself.

suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
I had the same issue on Redmi Note 9 Pro (joyuse). Based on your tip I've removed some modules from `data/adb/modules` and my device is finally booting normally. Thanks!