why does oneos rom got bootlooped when your are rooting it with magisk or patching it? after several reboots, it will not boot up and going through fastboot logo can is there any issues with twrp or magisk? can i have the proper installation of twrp and magisk to avoid bootloop? @DeathStroke47 am sure you can help me hehehe
Related
I recently installed RR in Asus ze551ml, and just discovered that magisk manager is not working. I badly needed Magisk manager, to use NFC in the various payment apps, but it's not working. It is saying that Magisk has not been installed. I tried flashing Magisk v14.0 manually, through recovery mode, but it went into recovery loop. That's just unexpected. Same thing happened when I tried to install Magisk in CM 14.1, which I was previously using. Please help me to find a solution.
Stuck on recovery loop
How did you manage to pass through recovery loop. I have some data on my phone memory that i need so i can't fully flash it with stock. Please suggest me something
Solution
After flash magisk you need to flash VerifiedBootSigner.
I resolved by this way
PS Sorry for my english
When flashing Magisk in ZE551ML, you must sign up Magisk before flashing. Or, you can flash Magisk then flash the script here
rex_agamidae said:
How did you manage to pass through recovery loop. I have some data on my phone memory that i need so i can't fully flash it with stock. Please suggest me something
Click to expand...
Click to collapse
I simply flashed the RR rom over it without wiping anything. It worked.
I recently updated my device(OP3) to Android 8.0(Open Beta ).
The issue arises when I try to boot my device after flashing Magisk Successfully via TWRP Recovery.
The Magisk process is successful in the recovery but due to some reason the device doesn't boot.
Any suggestions?
you need to install magisk v14.3 beta for oreo
I'm on oxygenos 5.0.5 and had Magisk 16.0 installed , I downloaded Magisk 17.0 and installed through twrp but phone went into boot loop , so I had to use Magisk uninstaller to get phone to start,
Now I dont have Magisk how go about installing it again
flash the v17 again .
i had the same problem , i downloaded the latest from github and flashed. everything is back to normal
Ok got magisk installed again , what caused the boot loop ? I thought flash through twrp was the safest option
I have OP3 and Lineage 14.1. I uninstalled magisk and reinstalled. Now I have root but no wifi. Do you have wifi?
Yes wifi is ok , but I just did a dirty flash of the rom , then installed twrp and magisk again
I'm try to magisk 17.1 no problem boot loop.
17.0 has bootloop bug on some phones it's fixed in 17.1
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Sumit Sikder said:
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Click to expand...
Click to collapse
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
I tried the latest v22.1. It worked in Android 11 evolution X ROM but not in realme UI 1! The only reason I installed my Android 10 was because Magisk modules weren't working in Android 11!
oxbowlarry said:
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
Click to expand...
Click to collapse
I have seen another rooting method with ADB and the patched boot image BUT that method first flashes vbmeta.img before flashing the patched boot.img.
Perhaps that is why my boot partition was corrupted because I just flashed the patched boot.img.
Has anyone had success with this rooting method on a Realme 6 pro ?
hello
I have rooted my device with magisk patch boot image and it work .my device is rooted.
but when I restart my device root has lost.
I have try 3-4 time this process but each time after device restart root has lost.
pls help...
miui version- miui global 14.0.3
magisk version - 26.1
wakram001 said:
hello
I have rooted my device with magisk patch boot image and it work .my device is rooted.
but when I restart my device root has lost.
I have try 3-4 time this process but each time after device restart root has lost.
pls help...
miui version- miui global 14.0.3
magisk version - 26.1
Click to expand...
Click to collapse
I suggest you install the latest Orang fox recovery if you don't have it or if you don't have custom recovery. Ive had issues with magisk "sticking" bc of the installed recovery. Flash Magisk zip via recovery then reboot to system and make sure it's still there. Make a copy of magisk zip and rename it "uninstall.zip" Then reboot to recovery and flash uninstall.zip. Then reboot to system then again to recovery and reflash Magisk zip. You can also try installing magisk alpha
Aserar said:
I suggest you install the latest Orang fox recovery if you don't have it or if you don't have custom recovery. Ive had issues with magisk "sticking" bc of the installed recovery. Flash Magisk zip via recovery then reboot to system and make sure it's still there. Make a copy of magisk zip and rename it "uninstall.zip" Then reboot to recovery and flash uninstall.zip. Then reboot to system then again to recovery and reflash Magisk zip. You can also try installing magisk alpha
Click to expand...
Click to collapse
i don't want to install custom recovery.[ bcz of ota update].
is there any way to fix this issue?
Flash Magisk zip
wakram001 said:
i don't want to install custom recovery.[ bcz of ota update].
is there any way to fix this issue?
Click to expand...
Click to collapse
Most people will have minimum to no experience regarding your situation honestly since its rare to root without the safty of a custom recovery. I think you should ask in the main magisk XDA thread or consider a custom recovery. Its hard to pinpoint the reason in this situation
Aserar said:
Most people will have minimum to no experience regarding your situation honestly since its rare to root without the safty of a custom recovery. I think you should ask in the main magisk XDA thread or consider a custom recovery. Its hard to pinpoint the reason in this situation
Click to expand...
Click to collapse
ok now I will consider custom recovery.( twrp ).