Been unlocked and rooted since day one. Have the latest TWRP, Magisk 19.5, Smurf kernel, and the latest stock PIE installed. Suddenly I cannot boot to recovery. When I try, it boots to fastboot.
I went to Magisk manager and ran the TWRP installer. It said it installed to both slots. Still can't get to recovery. I haven't done or installed anything differently. The only thing I can think of is
updating to Magisk 19.5 through the Magisk manager. I don't recall if I have booted to recovery since then. I do have the option to install Magisk to the inactive slot, but then the phone will boot to
that slot. I don't want to try that without some feedback from here, as I won't be able to boot back to the current slot without being able to boot to recovery. Everything on the phone is
perfect, all the root apps work, etc. I simply can't get into TWRP. The TWRP folder shows up in root explorer. Any suggestions would be greatly appreciated!
Related
Please bear with me.
I was about to upgrade from Magisk 19.4 to 20 and I tapped on "Install to inactive slot (after OTA)" instead of the recommended option "Direct install), then clicked yes without reading because I though I tapped the correct option... and after that, without rebooting, I tapped the Direct install option and rebooted. (Yup, I effed up that whole part.)
Then, when booting up the phone got stuck in fastboot.
I followed @Arden144's steps to install twrp and I was able to boot into twrp and flash magisk.
If I go to power options and tap on reboot to OS, it boots fine and I have Magisk 20. My modules are still there and everything seems fine. Wi-Fi, fingerprint sensor and SafetyNet are fine.
BUT! Now, for my actual problem:
Whenever I use advanced reboot to go to the recovery, go to recovery through Magisk Manager, press Volume Down + Power to boot into recovery or even select "Recovery" in TWRP's power menu, the phone just goes to fasboot and I can't enter the recovery unless I "fastboot flash" a recovery.
Thankfully if I select "Start", the phone starts fine. Previously it just looped back to the fastboot but seems that reflashing twrp at least fixed that.
But yeah, I can't enter TWRP without a computer to fastboot, which sucks.
What can I do? Flashing twrp doesn't seem to stick.
Thank you for any advice you can give me!
Deses said:
Please bear with me.
I was about to upgrade from Magisk 19.4 to 20 and I tapped on "Install to inactive slot (after OTA)" instead of the recommended option "Direct install), then clicked yes without reading because I though I tapped the correct option... and after that, without rebooting, I tapped the Direct install option and rebooted. (Yup, I effed up that whole part.)
Then, when booting up the phone got stuck in fastboot.
I followed @Arden144's steps to install twrp and I was able to boot into twrp and flash magisk.
If I go to power options and tap on reboot to OS, it boots fine and I have Magisk 20. My modules are still there and everything seems fine. Wi-Fi, fingerprint sensor and SafetyNet are fine.
BUT! Now, for my actual problem:
Whenever I use advanced reboot to go to the recovery, go to recovery through Magisk Manager, press Volume Down + Power to boot into recovery or even select "Recovery" in TWRP's power menu, the phone just goes to fasboot and I can't enter the recovery unless I "fastboot flash" a recovery.
Thankfully if I select "Start", the phone starts fine. Previously it just looped back to the fastboot but seems that reflashing twrp at least fixed that.
But yeah, I can't enter TWRP without a computer to fastboot, which sucks.
What can I do? Flashing twrp doesn't seem to stick.
Thank you for any advice you can give me!
Click to expand...
Click to collapse
There's a known issue with Magisk 20 that makes TWRP not stay installed. Downgrade to 19.4 or hold tight without TWRP
Arden144 said:
There's a known issue with Magisk 20 that makes TWRP not stay installed. Downgrade to 19.4 or hold tight without TWRP
Click to expand...
Click to collapse
Oooh. What an awful moment to have this problem, then.
Unfortunately, I reflashed Magisk, (Manager now shows 19.4) but TWRP doesn't stay installed... What worries me is that not even the stock recovery is available to use, just fastboot.
Deses said:
Oooh. What an awful moment to have this problem, then.
Unfortunately, I reflashed Magisk, (Manager now shows 19.4) but TWRP doesn't stay installed... What worries me is that not even the stock recovery is available to use, just fastboot.
Click to expand...
Click to collapse
You can try using the Magisk Canary Uninstaller to completely clean up the Magisk install, or dirty flash the stock ROM
Magisk 20.1 works for me with latest TWRP.
have you tried installing TWRP as a magisk module?
Try this..
To solve the prroblem
1. Reflash the latest rom.you have using system.update...
2. Install magisk to inactive slot
3. Reboot
4. Goto magisk and flash twrp installer v70..
5. Install magisk again as recommended..
Reboot...
when that happened to me i grabbed magisk uninstaller and fadtboot booted twrp flash magisk uninstaller then twrp zip reflashed magisk 20. whatever new version of magisk is
Deses said:
What can I do? Flashing twrp doesn't seem to stick.
Click to expand...
Click to collapse
Flash twrp to ramdisk. It should stick. I have it installed to ramdisk. Also updated from 19.3 to 20 with twrp still there.
Same happened to me. No recovery partition it seems. Lol going to try ecompton's suggestion later.
aNGERY said:
have you tried installing TWRP as a magisk module?
Click to expand...
Click to collapse
Makes no difference. Also, the TWRP issues are pretty random. I have no issues on ob3 with Magisk 20 and TWRP 70
TheKnux said:
Magisk 20.1 works for me with latest TWRP.
Click to expand...
Click to collapse
Me too.
OK, so only way I restored access to my recovery was to flash the OTA update and the stock recovery was there... after that I reflashed TWRP and I can access it just fine.
Please help me i have mistacke i unstall magisk now i went to restore root
I have TWRP installed but any time I try to Flash magisk, the boot image seems to corrupt and leaves me on the 'Bootloader unlocked' screen. I have to boot back into bootloader and use the 'repair recovery boot loop' option just to get back into my phone which then doesn't have Magisk available and root has not taken. Does anyone have any advice? Is there a boot image I need to flash after Magisk maybe? I'm fairly new to all this.
Isadorian said:
I have TWRP installed but any time I try to Flash magisk, the boot image seems to corrupt and leaves me on the 'Bootloader unlocked' screen. I have to boot back into bootloader and use the 'repair recovery boot loop' option just to get back into my phone which then doesn't have Magisk available and root has not taken. Does anyone have any advice? Is there a boot image I need to flash after Magisk maybe? I'm fairly new to all this.
Click to expand...
Click to collapse
Hello, would love to know because I have same issue here …
In fact I could effectively have root and magisk installed once, then I installed viper which didn't work... I removed viper module from Magisk Manager, then reboot, then got into the issue you describe. The 'repair recovery boot loop' allows booting but magisk is removed. And if I flash magisk again from TWRP, then the phone won't boot.
I tried reinstall TWRP/Magisk without success, tried lock/unlock bootloader (don't do that ! I could get out of it but no more success with magisk), also tried to remove the viper module with TWRP file manager (I could but it did not solve the issue), not sure what to do now.
What versions TWRP and Magisk?
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Goooober said:
I decided to root my Oneplus 6 (10.30.1) yesterday and everything went fine using TWRP 3.3.1.17 mauronofrio and Magisk 20.3.
Today I wanted to installed EdXposed which I did by going in to Magisk Manager, install Riru, reboot, install EdXposed and then reboot.
However, after installing EdXposed my phone would not boot, it would just hang on the loading screen.
I forced a reboot in to TWRP recovery and proceeded to restore my nandroid backup. This only made things worse.
When i try to boot I get the unlocked bootloader warning, it tries to boot in to the OS for about one second, then back to the bootloader warning screen and so on and so on.
I can still boot in to TWRP with Vol down + Power and i've tried wiping data and i've tried 'fix recovery bootloop' in the advanced settings but neither has worked.
Could someone kindly help fix this? I dont mind if i have to reinstall a stock Rom and lose root etc. I just want my phone back
Thanks
Click to expand...
Click to collapse
Use the msm tool to recover your device...
Try booting into the mauronofrio twrp recovery from fastboot. Then wipe the system partition and reinstall your rom.
Then boot mauronofrio twrp again from fastboot and install the zip, and reboot to recovery.
Install custom kernel, Magisk.
Uninstall edexposed
People reply here with no clue and advise to just restore stock. How is this a solution and how did not OP think of it themselves?
This is too little too late, but maybe it helps someone else:
Unofficial TWRP for Android 10 is glitchy. E.g. nanodroid backups are not restoring properly. Given current A/B mess this is not at all surprising.
Solution: wipe everything, reinstall *same* lineageOS version as before, flash same gapps as you had, and if you took the nanodroid backup after magisk, install it as well.
Don't boot yet!
Restore the backup *partially*, e.g. only the data partition.
This should work.
Or, emh, it did for me with some minor glitches. But even Google Authenticator didn't notice spoofing (otherwise RIP my accounts). So, i definitely recommend trying this workaround.
Hi all,
Yesterday I was messing around with V4A and following the final installation steps my phone got stuck in fastboot. To fix it I did the following:
1. I extracted the stock boot.img from my current OS version (10.3.12) and flashed it to boot_a and boot_b using fastboot. This restored the phone's ability to boot.
2. I booted the phone and went into the Magisk app to disable/unhide as much as possible and uninstalled the V4A app.
3. Rebooted into fastboot and booted into TWRP to remove Magisk, V4A and Vanced stuff from data/adb with the file manager.
4. Booted and flashed various combinations of TWRP versions (Mauronofrio, Bluspark) and Magisk (from 19.4 to 23.0). TWRP flashes fine and allows system to boot, but as soon as Magisk is flashed and a reboot is tried into system, it gets stuck on bootloader again and I have to repeat step 1.
(5. Tried patching stock boot.img file with the Magisk app. Same results as step 4.)
Does anyone here know what might be wrong? Is there another method I can try to regain Magisk without losing data?
Thanks in advance!
EDIT: really at a loss here. Idk why but as soon as magisk is flashed, the system refuses to boot. Without flashing magisk, system boots fine – am typing from it now. I figured at first that it had to do with remnants of AML, V4A and other Magisk modules not being properly removed, but I've removed those through TWRP file manager.
Really hoping one of you can point out something I've missed or think of something else I can try.
EDIT: solved! See update below.
UPDATE: solved it by forcing a local upgrade of the full OTA through phone settings (same version as mentioned above), causing it to switch slots. On the other slot, the system managed to boot after flashing TWRP and Magisk (latest versions).
Hello,
So my phone was in a recovery boot loop and had to rebuild the boot partition in twrp. So I'm back in my phone now and everything is the same but have lost root. Still have access to twrp. It's been a while since I rooted it and don't have any of the files anymore. What do I need to flash to get root back? Do I need to back up all my data or will it be safe?
I am still running android 9 and oos 9.0.7 and I assume bootloader is still unlocked. Orignally rooted with magisk.
thanks
kaotik123 said:
Hello,
So my phone was in a recovery boot loop and had to rebuild the boot partition in twrp. So I'm back in my phone now and everything is the same but have lost root. Still have access to twrp. It's been a while since I rooted it and don't have any of the files anymore. What do I need to flash to get root back? Do I need to back up all my data or will it be safe?
I am still running android 9 and oos 9.0.7 and I assume bootloader is still unlocked. Orignally rooted with magisk.
thanks
Click to expand...
Click to collapse
Damn it, so I booted into twrp and then flashed latest magisk v23 zip but when it finished it said failed to mount partition in red and now the phone just boots to fastboot mode.. I can get back into twrp.. and all my files are still there in file manager.. but it won't boot into my phone.. only fastboot mode. Any advice?
First, boot into TWRP and delete all Magisk Module files and folders:
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
I had the same and it seems a module was causing fastboot mode. If that doesn't work try downloading and flashing the stock boot image for your OOS version in TWRP (remember to flash TWRP again before reboot). At least then you will have your phone back.