Hello, i just installed an TWRP 3.0.0.0 Zip file and after that i rebooted the recovery and it keeps bootlooping, is there any ways to fix it? My current android version is MinimalOS 5.1.1.
Thanks.
Zelion said:
Hello, i just installed an TWRP 3.0.0.0 Zip file and after that i rebooted the recovery and it keeps bootlooping, is there any ways to fix it? My current android version is MinimalOS 5.1.1.
Thanks.
Click to expand...
Click to collapse
What else did you do, did you flash anything else or wiped anything?
TWRP won't work on a non-isorec compatible rom, but it shouldn't bootloop either, explain in details.
Related
Hello. So I was on AllianceROM build 25 on 4.3 until today. I decided to go try out the 4.4.4 LiquidSmooth ROM, so I flashed the ND7 modem and the rom. Things were alright, but after I installed GApps, I got force closes over and over to where it was unusable. So I booted back into recovery and now TWRP fails every time at "restoring system" from my backup .
I believe I backed up my working ROM with TWRP 2.5.0.1, I flashed LS ROM with CWM to see if it would help with force closing. It didn't so I reflashed TWRP 2.5.0.1 as recovery and tried restoring it from there, and haven't had any luck.
Anyone have any pointers? Suggestions? Have you had a similar situation?
falkon114 said:
Hello. So I was on AllianceROM build 25 on 4.3 until today. I decided to go try out the 4.4.4 LiquidSmooth ROM, so I flashed the ND7 modem and the rom. Things were alright, but after I installed GApps, I got force closes over and over to where it was unusable. So I booted back into recovery and now TWRP fails every time at "restoring system" from my backup .
I believe I backed up my working ROM with TWRP 2.5.0.1, I flashed LS ROM with CWM to see if it would help with force closing. It didn't so I reflashed TWRP 2.5.0.1 as recovery and tried restoring it from there, and haven't had any luck.
Anyone have any pointers? Suggestions? Have you had a similar situation?
Click to expand...
Click to collapse
Not sure if the recovery version has anything to do with it but twrp 2.5.0.1 is old. Current version is 2.7.2.1.
BluGuy said:
Not sure if the recovery version has anything to do with it but twrp 2.5.0.1 is old. Current version is 2.7.2.1.
Click to expand...
Click to collapse
Only reason I'm on a deprecated version is because, in the past, I've made a backup and tried restoring it on a newer version of TWRP and it failed and failed for days, then I reverted to the version I did the backup on and it worked. The issue here could be that I don't know specifically that 2.5.0.1 was the TWRP i was using before... I could try an updated one though. Is it ok to just flash a newer version of TWRP through TWRP itself?
falkon114 said:
Only reason I'm on a deprecated version is because, in the past, I've made a backup and tried restoring it on a newer version of TWRP and it failed and failed for days, then I reverted to the version I did the backup on and it worked. The issue here could be that I don't know specifically that 2.5.0.1 was the TWRP i was using before... I could try an updated one though. Is it ok to just flash a newer version of TWRP through TWRP itself?
Click to expand...
Click to collapse
Yes, you can flash twrp with twrp. As about the rest, like I said I was just making a guess. It could just also be that the backup was bad. I have had that happen once or twice.
BluGuy said:
Yes, you can flash twrp with twrp. As about the rest, like I said I was just making a guess. It could just also be that the backup was bad. I have had that happen once or twice.
Click to expand...
Click to collapse
Flashing it with the newest TWRP fixed everything.. We're good.
Thank you!
falkon114 said:
Flashing it with the newest TWRP fixed everything.. We're good.
Thank you!
Click to expand...
Click to collapse
Glad to hear.
HI, so I'm on MDK, rooted, and running GPE 5.0 LP, and I was recently attempt to update my recovery. I used Jrummy's ROM installer to install the TWRP 2.8.3. I rebooted, and now when i load into recovery, it says "kernel secure fail" and won't let me do anything. Is there a way to fix this? Any help would be appreciated.
Update: After attempting to reboot it a few times, I am able to boot to ROM, but still unable to boot to recovery.
clarinetboy said:
HI, so I'm on MDK, rooted, and running GPE 5.0 LP, and I was recently attempt to update my recovery. I used Jrummy's ROM installer to install the TWRP 2.8.3. I rebooted, and now when i load into recovery, it says "kernel secure fail" and won't let me do anything. Is there a way to fix this? Any help would be appreciated.
Update: After attempting to reboot it a few times, I am able to boot to ROM, but still unable to boot to recovery.
Click to expand...
Click to collapse
Boot to the ROM and install Flashify from the Google Play store. Use it to install the latest TWRP. That should clear everything up.
MehStrongBadMeh said:
Boot to the ROM and install Flashify from the Google Play store. Use it to install the latest TWRP. That should clear everything up.
Click to expand...
Click to collapse
Hmm. Ok so I installed TWRP 2.8.3 via Flashify, and successfully rebooted to recovery. I then flashed JFLTE-GPE 5.0 (jan. 2nd version). Now can't boot to either recovery or ROM, both of which are saying "secure fail: kernel." I did not loki doki. Ahh help!
Update: After rebooting multiple times, I can now reboot to recovery, but not to ROM.
Update: I used the 12/24 loki doki and now it seems like the ROM is working.
clarinetboy said:
Update: I used the 12/24 loki doki and now it seems like the ROM is working.
Click to expand...
Click to collapse
I ran into a similar problem, and had to completely restore to stock via Odin.
What were your steps here? Also I had trouble getting loki to install, which steps did you use?
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Drake9897 said:
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Click to expand...
Click to collapse
Bump, would really like some help :/
Back to stock
Drake9897 said:
Bump, would really like some help :/
Click to expand...
Click to collapse
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
I'll try that! Thanks! (sorry for late reply)
just flashed stock and got twrp back, tried to flash my RLS 19 backup and it completes at 3gb out of 1.2gb and 170% out of 100%. ugh :/ also twrp won't install via goo manager, have to use twrp manager .
TheSt33v said:
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
Click to expand...
Click to collapse
z
Also I'm running danvdh's lollipop GPE as well. It's actually the reason i updated twrp and started to get this issue. i'm running the same version of twrp as you and still no hyperdrive backup can restore. ):
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.
My phone is Galaxy S4 Mini (i9195i). I've installed TWRP 3.3.1 and flashed using this ROM ( https://forum.xda-developers.com/galaxy-s4-mini/development/rom-aospextended-rom-v7-2-t4107397 ).
The ROM works fine but whenever I try to install GApps (open_gapps-arm64-10.0-pico-20200715) it fails with "Error 64".
I've tried wiping the caches after installing the ROM, rebooting into recovery after installing the ROM, mounting /system before I try to install GApps, downgrading the recovery to TWRP 3.0.2, downgrading the GApps to earlier versions and I've just rooted. The only thing that let me install GApps was installing an arm version instead of arm64. My device is 100% arm64. This resulted in the OS not booting. I left it with a spinning wheel for over 2.5hrs. Reflashed without the arm GApps and it booted in 90s.
Please can someone help me!?
Thank you!
DevaVictrix said:
My phone is Galaxy S4 Mini (i9195i). I've installed TWRP 3.3.1 and flashed using this ROM ( https://forum.xda-developers.com/galaxy-s4-mini/development/rom-aospextended-rom-v7-2-t4107397 ).
...
Please can someone help me!?
Thank you!
Click to expand...
Click to collapse
Hi, apparently from what I read here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
And here:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-562900489
This is a TWRP issue that can be solved by updating TWRP to its latest version or by using a non official build that have been patched. So I advice you to contact the dev who built TWRP for your device, or keep installing arm Gapps to your phone (if it works).
Have a good day
Also, you can try that : https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-531326172
Or you can try boot TWRP from fastboot :
https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/