I can flash a new recovery or update the recovery through flashify or TWRP Manager however I cannot actually get into twrp it just hangs there forever. Anyway to fix this?
Related
I cant install TWRP Recovery through TWRP Manager. When I try to, I get this error:
Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred.”
I think this because i installed CWM and it may have blocked TWRP from installing. But I really dont know, I'm just speculating.
I can still go into TWRP Recovery through Rashr. But I want to go into it rhrough TWRP Mangaer. How do I get into TWRP Recovery through TWRP Manager?
use one of the toolkits to use ADB to manage things ! You'll be much happier
My I747 has been running ok with twrp 2.8.7. and cm 12(latest). After I used twrp manager to install twrp 3.0.1, twrp will boot loop whenever recovery is booted. if I reboot at this point (no buttons except pwr) the system goes to recovery again. I am then able to boot back to download mode via buttons and then continue to rom. I have also tried 3.0,2 and 2.8.7, all the same. I have installed the same set of twrps with flashify, same problem. I then restored a philz bckup from flashify which boots ok. I then installed cwm recovery (newest version) from flashify which boots ok. Basic issue is no recent twrp version will install without going into loop. Any help/thoughts appreciated!!!
i believe an older bootloader can cause this issue. which bootloader/modem are you on ?
"err on the side of kindness"
Im on CM13. So I was trying to install the updated recovery from Official TWRP App and though it said success, when I select go to recovery it goes to Fastboot.
What did I do wrong? How do I install recovery now?
after flashing twrp recovery i can reboot to recovery and fastboot. if i reboot system next time i try recovery i get the stock recovery. How to make the twrp to remain?
I used the latest official TWRP twrp-3.5.0_9-0-albus, when recovery flashes the first reboot recovery starts in TWRP but next reboot back to custom recovery, please any solution?