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!
Related
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.
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
whoiam55 said:
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
Click to expand...
Click to collapse
You can remove a module via recovery (mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img to disable magisk then you can remove the module from the manager itself.
Sent from my MI 5 using Tapatalk
teddy0209 said:
(mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img
Click to expand...
Click to collapse
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
whoiam55 said:
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
Click to expand...
Click to collapse
You can find the latter in the download section, the first on the compilation of modules... Your unpatched boot.img/stock boot.img, you can find it inside your room zip, from your twrp backup if you did backup prior to installing magisk. Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Sent from my MI 5 using Tapatalk
teddy0209 said:
Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Click to expand...
Click to collapse
So your are saying that if it stuck on boot then I can go back to TWRP, select /data/boot.img and flash it to boot partition?
One more think suppose I install *X* module and it succeed, then I install *Y* module and it failed to boot. Now I flashed boot.img as written above will it contain *X* module or just a fresh boot.img?
Thanks again for the reply.
Hi all, as the title implies, I'm a newbie to all this. I tried to root my phone using an online guide on how to root xiaomi mi 9 using TWRP and Magisk. I faced some problems but eventually everything was done as the tutorial said.
Here are the exact steps I've done...
- unlocked the phone via Mi unlocking tool
- started fastboot and installed TWRP 3.3.1-0 ( I installed a version first that didn't start when I pressed both power and volume up, then installed the 331-0 version that worked)
- inside TWRP i installed Magisk 20.4
- The phone restarted but never reach the system. It hangs for sometime on android screen then restarts again and then brings me again to TWRP
I spent quiet sometimes reading online solutions but nothing worked for me...
I tried installing Magisk uninstaller.zip nothing changed. tried wiping cache. Tried installing magisk 20 and 20.3
some solutions recommended installing Magisk 19 0r 17 but they both ended up with error for me.
Please help. I'm on Android 10 with MIUI 11
Never had any problems with magisk What TWRP version have you used?
The steps are the same:
-Unlocked phone.
-TWRP.
-Flash magisk zip (you can install magisk manager, then download latest official magisk zip from it and then flash downloaded zip from TWRP).
-reboot.
Anyway you can fix your system by:
-wipe cache/dalvik.
-FORMAT data (with yes).
I don't think you need this 2 first steps for flashing fastboot ROM but it won't hurt.
-Flash official fastboot ROM in fastboot mod, using mi flash tool or included batch/bash scripts (don't lock your device if you don't want to, choose the right option when you flash, with or without "lock").
Mi 9 Fastboot V11.0.5.0.QFAMIXM Global
Mi 9 Fastboot V11.0.8.0.QFAEUXM EEA
You will loose all your data, apps and settings.
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
F.Ashour said:
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
Click to expand...
Click to collapse
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
antonio52 said:
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
F.Ashour said:
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
Click to expand...
Click to collapse
I would try flash latest fastboot ROM as i said before it will reflash almost everything And then flash magisk by installing magisk manager and download latest magisk zip through it and flash it with twrp-3.3.1-62-cepheus-mauronofrio TWRP
Sometimes first flash of TWRP don't work, just flash it ones more by fastboot flash twrp twrp-3.3.1-62-cepheus-mauronofrio.img from your pc.
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
I just patched boot.img using latest ver of magisk and flashed to device Samsung m01 core (android 10(Q) go edition)
Magisk simply showing all done!
But after flashing magisk_patched_boot
Application is not detecting root i ve repeated steps but no use still it showing device not rooted
Can anyone help me.
I ve tried same procedure on other devices it worked perfectly but i don't know what happened this time...
Problem solved. The hidden magisk just renamed it to magisk...
What?
Renaming magisk solves problem?
Did u mean rename apk file
My problem is magisk not detecting rooted boot.img or recovery.img that i ve flashed to my device
Wait, what.. I thought I replied to another post. Sorry
MasterGmind said:
I just patched boot.img using latest ver of magisk and flashed to device Samsung m01 core (android 10(Q) go edition)
Magisk simply showing all done!
But after flashing magisk_patched_boot
Application is not detecting root i ve repeated steps but no use still it showing device not rooted
Can anyone help me.
I ve tried same procedure on other devices it worked perfectly but i don't know what happened this time...
Click to expand...
Click to collapse
Which magisk version?
Selvam_2568 said:
Which magisk version?
Click to expand...
Click to collapse
Here is the solution...(It will work for all magisk versions)
1.Uninstall magisk manager.
2.Reboot to twrp recovery. Then Advanced > File manager > /data/adb/
3.Delete the "adb" folder which present inside the /data.
4.Restore stock boot.img
5.Now flash magisk via recovery...it will work now.