I own a Mi 8 Global Rom on the latest MIUI and my intention was simply to root;
Bootloader is unlocked and I have Android ADB interface recognised under device manager
Successfully flashed "TWRP 3.4.0" via cmd fastboot flash recovery
Successfully went through installation process of "MAGISK 19.3" zip but am now stuck on mi logo bootloop!
I then tried to wipe dalvik cache for fun and reboot again but still bootloop.
Went to download Magisk Uninstaller zip and tried to flash it via TWRP hoping it would stop bootloop but to no avail.
Repeatedly tried to flash the uninstaller zip but i will get RED TEXT ERRORS 1 & 255 in TWRP.
Please help and advice, what did i do wrong, my rooting procedure was clean with latest magisk install but stuck with a bootloop now.
Is this bricked? Thanks for any help in advance!!v
Related
My phone is an Motorola 4G XT1072 Thea. Custom ROM LineageOS 14.1.
I wanted to change SuperSU with Magisk root. I therefore removed SuperSU and rebooted to recovery (TWRP) for flashing Magisk. I got an error code 1 flashing Magisk. I tried to reboot to recovery but I couldn't. It just reboots. It's like my recovery has gone. I can't even do a factory reset. I tried to reinstall TWRP through ADB but it's waiting for device forever. ADB recognizes my device. Anybody got some advice?
I managed to get my recovery back by deleting all moto drivers on windows and reinstalling them, then I could reinstall TWRP through ADB. But I still get error 1 when flashing Magisk. Is that because I need to flash a stock boot.img? If so do I then flash boot.img and thereafter Magisk.zip?
It all depends on what that "error 1" is actually about.
If you didn't restore the stock boot image after removing SuperSU, then that's a likely culprit...
If you want to know for sure you're going to have to share a recovery log with details about the error.
Today I updated my magisk installation from v17.3 to v18.0 using the Magisk Manager app, I rebooted my phone and I'm stuck on the phone logo.
I can get into TWRP, from there I tried to reinstall v17.3 and also uninstall v18.00 but for both cases I get "unable to open boot image" followed by a red "Error 1" in TWRP.
I have a OnePlus Two, running stock MM rom from OnePlus. Never had a problem with Magisk, any tips on how to fix it?
It's not a bootloop, I think boot image is broken.
Thanks for your help
I managed to fix this by downloading the stock rom and flashing the boot.img file inside using TWRP, reflashed Magisk 18.0 without problems.
Hello, everyone!
I hope anyone can help me.
Yesterday I assisted with rooting and flashing a Mi 9 T Pro with Xiaomi.eu firmware.
Here are the steps which were done:
1. Unlocking bootloader via MiFlash Tool.
2. Flashing TWRP (this one: https://androidfilehost.com/?fid=6006931924117906979)
3. First trouble: It only booted once into TWRP with "fastboot boot recovery xxx.img, after formatting data and a restart of TWRP it refused to get access again, neither with a command nor with hardware keys. It was stuck in fastboot.
4. With the MiFlash Tool I reverted to the stock global (this one: http://bigota.d.miui.com/V10.3.1.0....M_20190805.0000.00_9.0_global_135788d537.tgz)
5. After successfully flashing the stock ROM, I downloaded and flashed this TWRP: https://www.androidfilehost.com/?fid=1899786940962577905
6. Flashing this version of TWRP went perfectly fine.
7. In TWRP I formatted data again. I restarted TWRP and copied the following files to storage:
ROM: https://androidfilehost.com/?fid=1899786940962578113
Magisk 19.2.zip
Disable_dm verity_ForceEncrypt
8. I wiped Dalvik, cache, system and data.
9. I flashed ROM - it went through without problems
10. I tried to flash the dm verity, then an error occurred (please see the attached picture).
Can you please tell me what I'm doing wrong? Root is mandatory for me, I definitely need it.
I'm looking forward to your input and your help, it's very appreciated!
try to unmount system then flash it again
SkipperRyujin said:
try to unmount system then flash it again
Click to expand...
Click to collapse
Thanks for your input. I tried that, unfortunately this didn't work.
But I found the solution a few minutes ago:
I downloaded TWRP 3.3.1-13 (one version newer) and flashed it inside of my old TWRP. I rebooted to recovery again and then flashed Magisk without problems.
(The dm verity still refuses to install but the phone is booting and running.)
Well, it always work for me, or simply reboot recovery also work. Try wzsx twrp, it has remove DM verity & forced encryption remover in advanced menu
Hello,
I have been struggling to root my device. I have not wiped and rooted it in some time and now coming back to it again magisk keeps breaking my device.
I have clean flashed the latest android 9.0.0 build. I have flashed TWRP custom recovery 3.3.0 successfully. I have tried to flash magisk 3 times now and afterwards my phone wont boot. I originally used magisk manager to get the latest zip and patch my boot image. I then rebooted to to bootloader and ran fast boot flash boot patched_Magisk.img. This wiped out my twrp recovery and my phone wouldn't boot, i couldn't get back into twrp recovery. I reflashed latest 9.0 build and wiped everything. I flashed twrp again and tried to flash Magisk 20.0 from recovery. It was successful but again i couldn't boot into my phone and it eventually restarted back into recovery which i still had twrp this time. I then tried it again with 19.3 and the same thing happened. can anyone tell me what is going on here? What am I missing? I have been having reflash factory 9.0 build each time just to get it to remove the patched boot image and boot up again.
Was either the TWRP version or the two check boxes it has now to install twrp app as system. Installed 3.2.3-1 and didnt install the twrp app through the recovery check boxes and it worked.
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