[SOLVED] Bootloop after installing Magisk.zip - Redmi K20 / Xiaomi Mi 9T Questions & Answers

Hello everyone! I am using Xiaomi Mi9T with OrangeFox recovery.
Today I decided to upgrade from the abandoned PixelExperience ButterySmooth rom to MSM-Xtended. I wiped data, cache, dalvik and system, installed the MSM XR v2.0 and Flame Gapps and everything has been working perfectly fine - I love the ROM so far.
However, I have trouble installing Magisk. I downloaded Magisk21.0.zip, flashed it in recovery, but my phone got stuck on fastboot. I uninstalled Magisk, everything went back to normal and I then tried patching the rom boot.img with Magisk manager and flashing that to the boot partition, once again phone gets stuck to fastboot. I tried the integrated OrangeFox Magisk installer, but it just gets stuck on the MI boot screen where it says "powered by Android".
Could you please help me with how I can fix this and install Magisk on my phone? Am I missing something?
Thank you in advance!

biskitankata said:
Hello everyone! I am using Xiaomi Mi9T with OrangeFox recovery.
Today I decided to upgrade from the abandoned PixelExperience ButterySmooth rom to MSM-Xtended. I wiped data, cache, dalvik and system, installed the MSM XR v2.0 and Flame Gapps and everything has been working perfectly fine - I love the ROM so far.
However, I have trouble installing Magisk. I downloaded Magisk21.0.zip, flashed it in recovery, but my phone got stuck on fastboot. I uninstalled Magisk, everything went back to normal and I then tried patching the rom boot.img with Magisk manager and flashing that to the boot partition, once again phone gets stuck to fastboot. I tried the integrated OrangeFox Magisk installer, but it just gets stuck on the MI boot screen where it says "powered by Android".
Could you please help me with how I can fix this and install Magisk on my phone? Am I missing something?
Thank you in advance!
Click to expand...
Click to collapse
Instead of probably your Stable Magisk v20.4 (six months old), try Canary v21101
Download Magisk Manager Canary v315 ( latest) from Github and patch the boot.img (Recovery option must be unticked) and flash magisk_patched.img by Fastboot to Boot partition

zgfg said:
Instead of probably your Stable Magisk v20.4 (six months old), try Canary v21101
Download Magisk Manager Canary v315 ( latest) from Github and patch the boot.img (Recovery option must be unticked) and flash magisk_patched.img by Fastboot to Boot partition
Click to expand...
Click to collapse
Thank you!
SOLUTION: I reached out to the ROM developers on Telegram and they sent me an old Magisk to flash. I did and it worked successfully and after updating through Magisk manager everything is working perfectly fine now The file can also be found in the ROM thread.

Related

[solved] Stuck on 1+ logo on boot after flashing Magisk, works perfectly without

Spoiler: Culprit was App Systemizer.
I've had Magisk on my OP5 (128) for some time, and had the most common modules installed (can't get the list currently), but when I rebooted the phone this morning to install AllStream (dlna streaming app), the phone got stuck on the 1+ logo screen, that shows before the boot animation. I let it run for around 15 minutes but it was still stuck.
I rebooted into fastboot (recovery didn't work) and did
Code:
fastboot boot twrp-cheeseburger.img
to get into TWRP, and I reflashed the zip of the latest OOS (4.5.8) (of course, wiped caches beforehand). I rebooted and it worked (no root, of course).
So I rebooted into TWRP and flashed a freshly downloaded Magisk 13.3 zip, rebooted, and then it got stuck on the 1+ logo again. Flashed OOS zip, and it worked again (writing from the phone right now).
TL;DR: OP5 128 with Magisk & TWRP works perfectly. And then one day, book, stuck on logo at boot
Flashed latest OOS zip, works. Flash Magisk zip, stuck at boot again. Flashed OOS again, works.
In case of a Magisk module is responsible for that, how can I remove modules without actually installing Magisk?
I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5
Try just installing the magisk manager apk but without installing magisk root. Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.
Wechy77 said:
I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5
Click to expand...
Click to collapse
You don't need to flash the twrp image on every update.
As I said, Magisk has been working perfectly for weeks, it's just that when I random rebooted my phone it didn't boot correctly.
Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.
Click to expand...
Click to collapse
If Magisk is not installed, Magisk Manager doesn't have the Modules tab.
You don't need to flash the twrp image on every update.
Click to expand...
Click to collapse
I do. Stock recovery is restored every time I flash an update.
I am quite sure the problem comes from a module and not from Magisk itself, since it was working before. But I can only remove modules if Magisk is installed.
Quote from my reply on the other thread
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse
I'm having the same problem, look here: https://forum.xda-developers.com/oneplus-5/help/magisk-modules-t3651558
I suppose the magisk's modules stay installed in the background and when we flash it again, the phone bootloops.
I had to use SuperSU for now until I understand what's happening.

Need help getting back root/magisk

I updated to 9.0.12 today and went to magisk app to reinstall and wasnt able to. So i rebooted and when it was all booted back up i didn't have magisk or root. I decided it was time for a permanent twrp so i loaded twrp. Img and installed the twrp installer. Booted back into twrp and flashed magisk 18.1.zip and rebooted. When it was back up i still didn't have magisk or root so i tried to install magisk apk and it fails to install.
I dont know what else to do to be rooted again. Any help would be great.
That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root
did you "fastboot boot twrp img name" then install the Twrp installer to both slots ?
AndyBury said:
did you "fastboot boot twrp img name" then install the Twrp installer to both slots ?
Click to expand...
Click to collapse
That's what I did and have no issues.
BittahWarlock said:
That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root
Click to expand...
Click to collapse
I had this issue yesterday too, where I loaded 9.0.12 and TWRP, rebooted to recovery, loaded Magisk and then the phone would automagically shutdown after boot.
TL;DR; an issue with a magisk module misbehaving.
After some research, this is what worked for me:
Download the latest version of Magisk and the Magisk uninstaller from the Magisk thread. Reboot to recovery, and then zip install Magisk, but don't reboot. Immediately after, run the Magisk uninstaller. This should clear any offending modules. After that, you can reboot back into recovery and install Magisk normally. You'll need to reload your modules, though.
psychen6 said:
I had this issue yesterday too, where I loaded 9.0.12 and TWRP, rebooted to recovery, loaded Magisk and then the phone would automagically shutdown after boot.
TL;DR; an issue with a magisk module misbehaving.
After some research, this is what worked for me:
Download the latest version of Magisk and the Magisk uninstaller from the Magisk thread. Reboot to recovery, and then zip install Magisk, but don't reboot. Immediately after, run the Magisk uninstaller. This should clear any offending modules. After that, you can reboot back into recovery and install Magisk normally. You'll need to reload your modules, though.
Click to expand...
Click to collapse
thanks, that worked
BittahWarlock said:
That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root
Click to expand...
Click to collapse
The best way to take the update is download the full ROM and let the factory installer do the update via local install.
You lose root and TWRP, but that happens anyway.
I typically install, reboot, install.
This forces the OS to be the same in both a and b.
Then I go through the process of TWRP, etc.
after what i mostly do:
in fastboot boot to twrp,
install full rom,
install twrp,
reboot to twrp,
install magisk,
reboot to system
aaand it shut down on me ;(
in twrp i had to:
uninstall magisk (with the magisk uninstaller)
install magisk
almost done (reboot to system)
reinstall your magisk modules (they will be gone thanks to the unistaller, so know what you have magisked)
luckily it was that simple
So to avoid it al together:
take note of your magisk modules
fastboot to twrp,
install full rom,
install twrp,
reboot to twrp,
uninstall magisk,
install magisk,
reboot,
done!

[FIX] Flashlight and Camera not working after updating rooted 5T to OOS 10.0.0

After updating my 5t from OOS 9.0.10, it was rooted with magisk (20.4) plus some magisk modules and EdXposed framework then i did a dirty update like this:
- installed the OOS 10.0.0 firmware zip through TWRP (without first uninstalling magisk with magisk uninstaller zip)
- then i flashed magisk zip
- wiped cache/delvik and restarted, after what seems like eternity (long boot), the phone booted with Android 10 but flash and camera stopped working.
After looking for some solution online i didn't find anything helpful so i did this:
- Reboot to TWRP recovery and uninstall magisk with magisk uninstaller zip then i wipe cache/delvik and reboot to system (you loose twrp on this one cuz uninstalling magisk restores stock boot image which replaces TWRP with stock recovery)
- When the phone boots up normally everything (flash, camera) should start to work fine
- Now reboot to fastboot and flash TWRP recovery (you need pc)
- After it finishes flashing don't start the phone instead do this press volume key until the above title says recovery and press power button to boot to recovery
- When you are on TWRP install magisk zip and clear cache/delvik then reboot to system
- Now flash and camera will work and you can reinstall your previous magisk modules
- Reboot so your modules get activated
- Done! That's all
Sent from my ONEPLUS A5010 using Tapatalk
nadiration said:
After updating my 5t from OOS 9.0.10, it was rooted with magisk (20.4) plus some magisk modules and EdXposed framework then i did a dirty update like this:
- installed the OOS 10.0.0 firmware zip through TWRP (without first uninstalling magisk with magisk uninstaller zip)
- then i flashed magisk zip
- wiped cache/delvik and restarted, after what seems like eternity (long boot), the phone booted with Android 10 but flash and camera stopped working.
After looking for some solution online i didn't find anything helpful so i did this:
- Reboot to TWRP recovery and uninstall magisk with magisk uninstaller zip then i wipe cache/delvik and reboot to system (you loose twrp on this one cuz uninstalling magisk restores stock boot image which replaces TWRP with stock recovery)
- When the phone boots up normally everything (flash, camera) should start to work fine
- Now reboot to fastboot and flash TWRP recovery (you need pc)
- After it finishes flashing don't start the phone instead do this press volume key until the above title says recovery and press power button to boot to recovery
- When you are on TWRP install magisk zip and clear cache/delvik then reboot to system
- Now flash and camera will work and you can reinstall your previous magisk modules
- Reboot so your modules get activated
- Done! That's all
Click to expand...
Click to collapse
Can I give link for the ROM you flash?
zhukry said:
Can I give link for the ROM you flash?
Click to expand...
Click to collapse
[emoji1428] https://otafsg1.h2os.com/patch/amaz...ygen_43_OTA_067_all_2005130057_6b923fb89f.zip
Sent from my ONEPLUS A5010 using Tapatalk
Thanks for this! The same thing happened to me. You saved me hours of troubleshooting!
Thanks VoltaGe86 - been driving me mad for a week now and your advice has solved all my camera & flashlight problems AND YouTube and Tasker not connecting.
Appreciate your post!
i know i am late but
if anyone else is facing this problem then try installing open camera and try going to stock rom(old one) do rom update with stock recovery
I've been experiencing the same loss of camera and torch/flashlight after upgraded my Oneplus 5T to the latest firmware (10.0.0/10.0.1).
It was not solved by using magisk uninstaller and downgrading.
Additionally, the phone will not auto upgrade to new releases, whatever rom I install it always insists 'Your system is up to date'.
After wasting far too many hours I've found that the camera works on stock roms up to Oxygen 5.1.7 (Android 8 Oreo), but stops working when flashing the next update: Oxygen 9.0.0 (Android 9 Pie).
I've addtionally tried unbricking the phone using dumpling_43_O.36_180613_unlocked.7z and have attempted to upgrade with OEM Unlocking turned off.
Any ideas as to what might be the cause would be super welcome!
I'm wondering if the underlying paritioning could be damaged in some way?

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.

Mi9T stucks on kali boot logo after flashing nethunter

I do have orangefox recovery flashed into my phone. Wiped data, system, cache... and format data
First of all, I installed MIUI (the latest version from mi website "miui_DAVINCIGlobal_V12.1.4.0.RFJMIXM_e0ac13ed89_11.0.zip"). If I reboot into the system, it works fine.
Then flash magisk(v24.3) and 'disable DM-Verity_ForceEncrypt', and reboot into recovery
When I flash nethunter (nethunter-2022.2-davinci-miui-ten-kalifs-full.zip), which I downloaded from offensive security webpage., it does install well (at least it doesn't show any error messages).
After flashing nethunter, I rebooted into system. When nethunter logo did pop up, it got stuck into that fire animation. I can still access fastboot and recovery menu.
Any idea of what's happening? Why doesn't it boot?
Xylonity said:
I do have orangefox recovery flashed into my phone. Wiped data, system, cache... and format data
First of all, I installed MIUI (the latest version from mi website "miui_DAVINCIGlobal_V12.1.4.0.RFJMIXM_e0ac13ed89_11.0.zip"). If I reboot into the system, it works fine.
Then flash magisk(v24.3) and 'disable DM-Verity_ForceEncrypt', and reboot into recovery
When I flash nethunter (nethunter-2022.2-davinci-miui-ten-kalifs-full.zip), which I downloaded from offensive security webpage., it does install well (at least it doesn't show any error messages).
After flashing nethunter, I rebooted into system. When nethunter logo did pop up, it got stuck into that fire animation. I can still access fastboot and recovery menu.
Any idea of what's happening? Why doesn't it boot?
Click to expand...
Click to collapse
For Magisk you ABSOLUTELY don't need Verity and so
Simply, extract boot.img from the firmware zip and by using Magisk APP take install, Select and Patch to patch your extracted boot.img
Do not enable Recovery option while patching
Then flash from Fastboot the patched boot img to Boot
That's it - the proper way to install Magisk to your Xiaomi ( I used and still use on my Mi 9T from MIUI 10 till now with MIUI 12.5)
For Nethunter I cannot help you. It's been more than two years since I used Kali and at that time it installed flawlessly.
However, then I had MIUI 11 and Kali required MIUI 11 - don't know how is it now...
And btw, I always use the latest TWRP.me version - currently 3.6.1_9-0
zgfg said:
For Magisk you ABSOLUTELY don't need Verity and so
Simply, extract boot.img from the firmware zip and by using Magisk APP take install, Select and Patch to patch your extracted boot.img
Do not enable Recovery option while patching
Then flash from Fastboot the patched boot img to Boot
That's it - the proper way to install Magisk to your Xiaomi ( I used and still use on my Mi 9T from MIUI 10 till now with MIUI 12.5)
For Nethunter I cannot help you. It's been more than two years since I used Kali and at that time it installed flawlessly.
However, then I had MIUI 11 and Kali required MIUI 11 - don't know how is it now...
And btw, I always use the latest TWRP.me version - currently 3.6.1_9-0
Click to expand...
Click to collapse
Thanks for replying

Categories

Resources