Hi,
I'm trying to install magisk and keep getting into a boot loop.
I've installed RETEU 29.98-111-9 and then twrp-3.3.1-0-lake and the system boots without any problem.
When installing Magisk-v20.3.zip from TWRP the log is fine, without any errors, but after a dalvik wipe and reboot to system I get a never ending boot loop.
I can exit it only by installing Magisk-uninstaller-20200110.zip
I also tried the manually way of patching the boot.img and flashing it in fastboot, but this also gets me into a boot loop (exiting only by flashing the original boot.img)
Any idea on this?
Which way works for you?
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.
My Nexus 6 has the last Pure Nexus rom, TWRP, and Magisk.
I updated the Magisk app earlier and it went fine. Then I tried updating the boot image or whatever it is that you also update after the main app updates. But it would not do that update. It just didn't do anything when I hit install. So I rebooted. Now it goes straight to recovery mode and says boot up failed: invalid boot image header.
Is there a way around this or do I need to flash the rom and whatnot? I tried wiping the cache, and that didn't seem to change anything.
Finding a workaround is going to be harder than reflashing.
Flash the same rom as you already have, including gapps and anything else you might have flashed. You won't need to wipe data.
Flashing just the boot image (followed by the Magisk installer if you want to keep root) should be enough. You likely experienced a bug where several Magisk flashing activities ran at the same time and this destroyed the boot image. Get a fresh image installed and you should be up and running again.
That worked! Thanks.
-posting from N6-
Hi Guys
I tried an update to Mirza's ROM but after it caused more issues, I tried restoring from full Orangefox backup in recovery; only to find the phone stuck at Fastboot mode. It appeared strange, so I tried it again to end up with same fate. I tried installing Xiaomi.EU ROM, but after installation it got into a boot loop alternating between Recovery logo and MIUI startup logo. I got into fastboot again and flashed TWRP trying the same, but without joy. Tried another recovery and multiple versions of Xioami.EU ROM all with same fate. Finally got hold of an old fastboot ROM from Xioami.EU and flashed with MiFlash tool and it flashed successfully without issues. Assuming all was well, I tried flashing ROM via recovery which either gets stuck at MIUI logo or recovery. Boot loader in unlocked and decrypted. I tried flashing SHRP recovery, Magisk, wiping data etc as well to rule out any issues, but the problems remain.
Any ideas as to what's happening?
If I understood right, recovery ofox is working.
So reboot to it
Format data with yes
Reboot ofox
Flash ROM
Flash magisk recommend
Format data again with yes
Reboot system and give time to boot, could be more than some minutes but I think not more than 20
For those who might face similar issues.
According to Orangefox website, 'note that you should not restore a backup of the persist image, unless it proves absolutely necessary'. I may have checked it in recovery during restoration which probably destroyed the partition.
Fix:Installed TWRP via flashboot, formatted all data(not wiped) and installed ROM then formatted again and it booted.
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Blackdragonbird said:
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Click to expand...
Click to collapse
Reflash the stock unrooted boot.img of your room in bootloader. Use adb
Fastboot flash boot boot.img
Similar problem here...
I tried reflashing stock recovery and stock boot.img - now whenever I reboot it just boots into recovery! I don't seem to be able to boot into system any more...
Any ideas?
I'm running AOSIP on a Xiami Mix Mi 3 - I hadn't updated to the latest Magisk in quite some time (since before the app could do it automatically). I have to use the recovery method.
Steps I took are:
Get recovery.zip from my ROM, patched it through the app, then flashed through fastboot. I rebooted while holding down the up arrow to reboot into recovery, then released for the phone to boot.
I got an error after booting that said "there's an internal error with your device" - and it was super buggy, couldn't tap the screen, super slow to load stuff, etc.... I figured it was a magisk issue, so tried to reflash recovery and boot... Not I'm stuck booting into recovery!
Help.
Edit: so - I think it turns out I have one of those RARE xiaomi devices that DOES have ramdisk even though the app doesn't detect it... Go figure. A clean install of the ROM, followed by patching the BOOT image rather than the recovery image - and we're up and running.
Hi,
I have C11 RMX2185, unlocked bootloader, installed TWRP and then some roms (pixel experience, next stock android 11, next CipherOS-2.0-KNIGHT)
everything worked fine and I was preparing to try some other ROMS
But now I am unable to enter TWRP (I was, I flashed roms with TWRP before)
In fastboot I do fastboot reboot recovery and TWRP started to load (blue TWRP logo), and it blink and logo, blink - logo,.... forever
I tried to flash boot.img, flash TWRP again, tried another release of TWRP for RMX2185, flashing vbmeta, format userdata, ..... all kind of posibilities without any error but stil unable to run TWRP
I can boot into system (CipherOS-2.0), I can do things in fastboot, when it loops in starting TWRP it is able to react to adb reboot
I run out of ideas.
Thanks in advance for some kicks in the back