Booting to TWRP after flashing - Magisk

Hello. I'm using a Zenfone 2 Z00A with the lastest LOS 14.1 at the time of this post.
I've been trying to install Magisk via flashing the .zip file in TWRP but everytime I flash it the phone doesn't boot to system but to the recovery. It only boots to the system if I flash the Magisk uninstaller
I flashed the su remove, uninstalled Xposed and tried to flash Magisk again but it keeps booting to TWRP. Same thing happening.
How do I solve this ? I just want to play Pokemon GO.
Thanks !

Flash Android Verified Boot Signer after flashing Magisk.
And please make a search in zenfone 2 forum before asking, there're tons of discussion about this problem.

Related

Recovery Bootloop after Installing Magisk

Hi,
I'm using ASUS ZE551ML running latest Lineage OS 14.1 ROM.
The SU addon on the Lineage website doesn't seem to work anymore, so I switched to Magisk.
I tried installing Magisk v14 zip from TWRP, rebooted to system, and it booted back to TWRP.
It's been 2 days and I've done plenty of reading on this forum but haven't found any solutions yet.
Thanks.
Have you tried signing your boot image after flashing Magisk?
Didgeridoohan said:
Have you tried signing your boot image after flashing Magisk?
Click to expand...
Click to collapse
Thanks for the response.
I've visited your link and read it.
So I should flash the Verified Boot Signer after I flashed Magisk?
Edit : Flashing the Verified Boot Signer helps me get out of the loop and my phone is now rooted. Thank you very much.

Stuck in boot loop after installing Magisk

I had SuperSU installed (but I needed to hide the root from some apps), and I installed Magisk with the Direct Install method with succes.
I reboted and now is stuck in a boot loop...
What can I do to fix it?
I'm using a Galaxy Note 3 (Android 5) with stock firmware.
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Edit:
https://didgeridoohan.com/magisk/Magisk#hn_Bootloop
And of course the rest of the guide:
https://didgeridoohan.com/magisk
I didn't know I have to backup my boot.img file
I'm searching for my original boot.img file from the firmware right now, but until the download is complete (15 hours :| ), I'm trying to flash the magisk uninstaller and use it with twrp terminal.
Didgeridoohan said:
Edit:
https://didgeridoohan.com/magisk/Magisk#hn_Bootloop
Click to expand...
Click to collapse
Thank you!
Solved it!
I flashed the Magisk uninstaller (Magisk-uninstaller-20180921.zip from https://github.com/topjohnwu/Magisk/releases) with TWRP, and it worked!

magisk doesn't apply when flashing

Hello guys,
I made an update in TWRP and installed Havoc 2.4 to try it. After 1 hour I restored my backup and changed back to MIUI. I couldn't log in, so I cleaned the keyfiles to set a new pin.
I reflashed new Beta (25.4 MIUI - Xiaomi.eu) ROM and Magisk but root does not apply on my device... What is wrong? Seems that it's not possible to root anymore... Its does not give me any fails when installing the magisk 18.1 zip in TWRP...
thanks in advance
Have you tried a simple reboot? Usually it takes a reboot more to apply.
no it's not that. now its always booting into twrp when I try to flash magisk
makmak001 said:
no it's not that. now its always booting into twrp when I try to flash magisk
Click to expand...
Click to collapse
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
I fixed it by wiping data... now its working
tsongming said:
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
Click to expand...
Click to collapse
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Sent from my Xiaomi MI 8 using XDA Labs
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Here you can see that I have root and latest update
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Click to expand...
Click to collapse
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
slave2007 said:
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
Click to expand...
Click to collapse
I no longer use Viper because my phone has 1 speaker and for me Ainur Sauren works pretty well for all sounds.
For listening to music I have the Pro version of Power amp which has every wanted option such as dynamic compression, dynamic EQ, convolution reverb, limiting , tag editing, visualizations etc, I bought it 5 years ago for $3. Best 3 bucks that I ever spent!
Seriously, I can't recommend Poweramp highly enough, its worth its weight in gold.
Sent from my Xiaomi MI 8 using XDA Labs

K20 Pro China ROM Magisk Bootloop Problem

Read a similar problem from this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
I'm already unlocked and I was gonna stick with the China ROM for now, so I flashed Magisk. After an hour I noticed my root access WAS GONE. So tried restarting it and... bootloop! Magisk uninstaller fixed this BUT I want that Magisk. So I kept retrying... Fastboot, flash TWRP(another issue is TWRP wont stick no matter what it will be replaced by stock recovery), Install magisk, bootloop... Rinse and repeat.
I tried 2 methods installing Magisk. TWRP and the Boot Image Patching using boot.img from latest China ROM miui_RAPHAEL_V10.3.12.0.PFKCNXM_75ea367433_9.0.zip
Im running out of ideas, can anyone here help and share how they fixed it? Thanks!
you should change to Xiaomi EU rom, no issues with Magisk.
Try installing ver 18 or 18.1 magisk i had issues with ver 19 and up on pocof1. Also on pocof1 you had to install dfe (disable force encryption) and them twrp wouldnt be replaced with stock boot recovery. Also any update that comes when twrp is installed will rewrite it to stock recovery.
Wipe userdata/factory reset after installing magisk
I have the same issue and resolve it by install OrangeFox-R10.0_8-Stable & Magisk-v20.1.zip.

MI 9 in bootloop

Hi!
I have pushed my MI 9 into bootloop and need help to get it back working.
The bootloader is unlocked, Magisk and TWRP are installed. I tried to install the latest Universal SafetyNet Fix, but instead of installing it inside Magisk I have "installed" the ZIP with TWRP and wiped the delvik cache. Now the phone is in bootloop.
In the Universal SafetyNet Fix- threat I got the hint to reinstall the stock boot.img, but I am unsure how to do this and which file to use.
Can I just use one of the boot.img linked in this threat, e.g., the one in 10.2.24.0?
[Root images] Boot 10.2.24.0 & 10.2.9.0 & 10.2.26.0
Version 10.2.26.0 Version 10.2.24.0 ------------ > Stock/Root Version 10.2.9.0
forum.xda-developers.com
and install it with fastboot, i.e., "Fastboot flash boot.img" ?
Or is there another solution to my problem, e.g., uninstall the safetynet-fix-v1.1.0.zip ?
Well, I gave it a try, but it doesn't work. Now the phone doesn't even show the MIUI logo anymore. Fortunately, I had made a backup with TWRP before I tried this, and I could reflash the old boot.img with
fastboot flash boot boot.emmc.win
Now at least the MIUI logo appears again, but my original problem is still there, the phone still doesn't boot completely, but resets and goes into twrp.
Problem solved by deleting the safetynet-fix folder. Thanks to Durete for this tip!
How to Uninstall Magisk Modules Using TWRP Recovery
Removing the Magisk module manually causes bootloop. You can easily uninstall Magisk modules using TWRP recovery without resetting your device.
www.droidviews.com
Durete said:
The easy way....
How to Uninstall Magisk Modules Using TWRP Recovery | DroidViews
Click to expand...
Click to collapse

Categories

Resources