Related
Hi, well, as the title says i just updated magisk to v9 and my cellphone got stuck at the recovery mode.
I had magisk v8 installed, so i went to the magisk manager to update it but it said i had to do it manually and that the file was saved at MagiskManager, so i enter to TWRP and flashed the zip to update to magisk v9, and after that i turned on the cellphone and it appears a screen with two errors
Func 10 boot image
Error 2 load failed
I dont know what to do, i tried to uninstall magisk and re install it but it wont work.
I flashed a boot img from b317 (i think i used that update.app) and flashed the stock recovery using the Huawei Update Extractor, but now i got a bootloop or a blackscreen.
I need your help, i dont want to do a factory reset, THANKS.
Santiago2812 said:
Hi, well, as the title says i just updated magisk to v9 and my cellphone got stuck at the recovery mode.
I had magisk v8 installed, so i went to the magisk manager to update it but it said i had to do it manually and that the file was saved at MagiskManager, so i enter to TWRP and flashed the zip to update to magisk v9, and after that i turned on the cellphone and it appears a screen with two errors
Func 10 boot image
Error 2 load failed
I dont know what to do, i tried to uninstall magisk and re install it but it wont work.
I flashed a boot img from b317 (i think i used that update.app) and flashed the stock recovery using the Huawei Update Extractor, but now i got a bootloop or a blackscreen.
I need your help, i dont want to do a factory reset, THANKS.
Click to expand...
Click to collapse
Did you uninstalled v8 before flashing v9?
Sent from my SM-G935F using Tapatalk
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
ssteward said:
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
Click to expand...
Click to collapse
Try flashing magisk 15.3 + no verity stuff as suggested on that thread...
Sent from my MI 5 using Tapatalk
ssteward said:
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
Click to expand...
Click to collapse
Dont flash unpatched boot images using twrp
flash unpatched boot image or v14 boot image(that you made earlier) using pc ODIN/ any other prefered tool. Just flash the boot.img nothing else or you can use fastboot to only flash boot.img, it works 100% all times,after flashing it should boot normal
then make a new patched boot image for v15.3 from magisk app just as you made for v14 and flash using pc,then it should boot normally
many phones seem to show stuck at boot logo after moving from v14 to v15(especially v15.1 and v15.2) and also some some devices with f2fs storage seems working weirdly with audio mods.
teddy0209 said:
Try flashing magisk 15.3 + no verity stuff as suggested on that thread...
Click to expand...
Click to collapse
I'm pretty sure that's one of the permutations I tried before but having just flashed those two zips again, after making sure any previous Magisk installations had been removed, I get the same result - stuck at the pulsating Samsung logo.
If someone can tell me what parts of the system the problematic in-app upgrade from v14.0 to v15.0 would have affected then I could perhaps have a better idea of what I need to fix to get my phone starting up again.
ssteward said:
I'm pretty sure that's one of the permutations I tried before but having just flashed those two zips again, after making sure any previous Magisk installations had been removed, I get the same result - stuck at the pulsating Samsung logo.
If someone can tell me what parts of the system the problematic in-app upgrade from v14.0 to v15.0 would have affected then I could perhaps have a better idea of what I need to fix to get my phone starting up again.
Click to expand...
Click to collapse
Have you tried flashing your stock boot image or even dirty flashing your entire system with ODIN (as suggested above)? Magisk only edits the boot image, nothing else.
Supreme Genius said:
Dont flash unpatched boot images using twrp
Click to expand...
Click to collapse
Sorry, my mistake. I did flash boot.img via Odin. It was the original boot.img file that I fed into Magisk v14.0 so it could create patched_boot.img.tar that originally worked. I'm going to try that again now.
Didgeridoohan said:
Have you tried flashing your stock boot image or even dirty flashing your entire system with ODIN (as suggested above)? Magisk only edits the boot image, nothing else.
Click to expand...
Click to collapse
That's good to know, thanks. I do have the full system from sammobile from which I extracted boot.img, so could try that if the 'lighter touch' approaches fail.
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
ssteward said:
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
Click to expand...
Click to collapse
Probably try that... Hope it's not a corrupt boot partition...
Sent from my MI 5 using Tapatalk
ssteward said:
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
Click to expand...
Click to collapse
did you flash the previous v14 patched boot image again using ODIN? this should work
same boot loop problem prevailed on my s7 active and lenevo k8 and flashing the v14 patched boot image and then making new v15.3 boot image gave a perfectly working magisk, although my redmi 3 was showing same boot loop problem and i have to flash the stock rom ( used twrp to restore nandroid backup but boot loop was not solved )
It seems your lots of permutations and combinations have damaged post_fs config of the kernel so you have only option left is to dirty flash the ROM.
teddy0209 said:
Probably try that... Hope it's not a corrupt boot partition...
Click to expand...
Click to collapse
Sounds ominous. How would I recognise this and fix it?
Supreme Genius said:
did you flash the previous v14 patched boot image again using ODIN? this should work.
Click to expand...
Click to collapse
I don't seem to be able to find the patched_boot.img.tar that I used originally with Odin. I've checked a few different machines and on various SD cards but I only have the unpatched boot.img.
ssteward said:
Sounds ominous. How would I recognise this and fix it?
I don't seem to be able to find the patched_boot.img.tar that I used originally with Odin. I've checked a few different machines and on various SD cards but I only have the unpatched boot.img.
Click to expand...
Click to collapse
Then you need to flash the ROM , if you got another device then you can make a patched v15.3 image and flash it
I used another phone to created a patched_boot.img.tar for v15.3 and flashed that with Odin but that gave me a boot loop. Trying this again but flashing no-verity-opt-encrypt-6.0 afterwards allowed me to get to the pulsating Samsung logo. So giving up on this approach, I dirty flashed my stock ROM and this worked but I was left looking at a pulsating Samsung logo for a nerve-racking 5 mins or more.
Thank you everyone for your help. I have my phone booting up again!
Now I need to work out install the latest Magisk successfully. If I try using the patched_boot.img.tar method with v15.3 then I'm back to the pulsating Samsung logo. Again. Using TWRP to flash the v15.3 zip gives the pulsating Samsung logo. I did select 'Preserve AVB 2.0/dm-verity. I also tried again with a clean stock ROM install and flashed the v15.3 zip and no-verity-opt-encrypt-6.0, as suggested by someone who'd successfully installed v15.3. I'm at a bit of a loss.
One clue, TWRP couldn't see the internal SD card data (iow /data). I wasn't able to check this option in the 'Mount' menu in TWRP either. I think this points to /data being encrypted. TWRP could see it yesterday, so perhaps I've inadvertently encrypted this. I was careful to uncheck 'Preserve force encryption' in Magisk Manager. I guess now that I've unbricked my phone, I should start another thread for this magisk install issue but any help or pointers to relevant threads that I may have missed would be great.
Thanks again for all your help.
I've tried to install Magisk and I had no problems at first. I downloaded Magisk Module and tried to install some modules, I rebooted my phone and it was stuck on a bootloop. Luckily I had the rom availabe so installed it using hrupdater.zip. Everything was back to normal without magisk installed, I assume a module is causing the bootloop, so I did some investigating and found the unimod module, I tried too flash it from twrp and it keeps ending with error 1. The same thing happens with magisk uninstaller and mount magisk. I'm also unable to wipe cache but I dont know if that's a seperate issue
Please post the recovery log showing those errors. Impossible to definitely say what's wrong otherwise.
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
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.