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.
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.
Background:
Went to update Magisk via TWRP, phone now bootloops (and gets really hot when charging).
Before I go ahead with flashing an older firmware, to try and get it running again, I was wondering if there was any way of retrieving data from the phone?
I can still boot into TWRP without issue, although I did notice if i go to Install and select source, Internal Storage shows as empty, while External is fine.
Failing data recovery, any suggestions for unbricking it without wiping anything? I've tried un/reinstalling Magisk via TWRP, wiping data/cache/dalvik, but no luck so far.
Thanks
I know where i ****ed up now. By flashing Magisk directly from TWRP.
Tried reflashing it via the guide on page one:
"Instructions for Root Access"
A) Workaround for flashing Magisk with TWRP – for Advanced Users:
Now getting past the warning screen, but not past the Huawei logo.
Going to try remove Magisk altogether, and see if it boots up. If so, will install Magisk again.
Flashed original ramdisk.img and it now shows the boot animation, but doesn't get past there....progress i guess.
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-
So basicly, I updated the magisk app and it said I have an update available.
I was on a custom rom named Blastui rom: https://forum.xda-developers.com/t/...-1-1-odex-v3-45-aroma-like-a-ferrari.4200153/
at the same time, i had twrp installed on recovery.
So i didn't want to earrase that.
Bec. of that i didnt check the "Install to recovery" option in the magisk app and flashed it.
After the flash, i tried rebooting, which failed on the bootloader loading screen.
Then I tried booting into recovery. didn't work.
Then I tried booting into download mode. didn't work either.
it just keeps rebooting in a period of like 5 minutes and then gets stuck on bootloader.
Pls help its my main phone
I was unlocked and rooted at Indian 12.5.2 ROM for the longest time. Got a notification for 12.5.5 and installed it. That took away root, but that was expected.
Now I've installed official TWRP, but as soon as I install Magisk (either via zip from recovery or patched twrp recovery image via the Magisk app), when I try rebooting to system, phone instead boots back to TWRP with a 'Android Rescue Party Trigger' error.
Happened every single time I've tried above - phone tries booting and then boots to recovery, and only way to boot system again is to install unpatched TWRP recovery, but then there's no root.
What should I do?