Database Info

Can't Access TWRP Recovery

Hi guys, I flashed the latest factory image, then flashed the latest TWRP but can access it 1 out of 10 tries.. What am I doing wrong? Is it a faulty replacement phone? Never had this issue with my other nexus 5 (same recovery file but lollipop and not marshmallow) and now I have this problem.. Tried to riflashato the factory image 5 times, boot to recovery without installing but nothing changed.. Thanks in advance!

If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.

beekay201 said:
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
Click to expand...
Click to collapse
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..

carlese said:
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
Click to expand...
Click to collapse
do you finde fix

slavisa037 said:
do you finde fix
Click to expand...
Click to collapse
Downloaded twrp again and used flashify..

carlese said:
Downloaded twrp again and used flashify..
Click to expand...
Click to collapse
This is not really a fix, since to use Flashify one needs to be rooted already.
What I did to work around this was reflash LMY48M. After reflashing that, fastboot correctly boots/flashes twrp.
I've read that the issue arises when trying to boot and/or flash twrp with MRA56K installed, AND the device is connected to USB.

Ok, i got some of problems here, i tryied to root my Nexus 5 with other Android 6 version, it was the first one launched after development version. Now i have MRA58K version.
Problem 1 : I have no stock recovery, i first rooted original version of Marshmallow with CWM and i soft bricked, so no backup, no factory images. Installed MRA58K and there is no stock recovery, thanks god i can use bootloader. I can install TWRP, but i want to install the old recovery, Tell me how to do it.
Problem 2: Actual version of Marshmallow ask me to install a patch, but when installing i got stuck in TWRP, it cant install it (yes, android was rooted, but i installed twrp before root, and the update were before it.)
Thanks.

You can flash a stock ROM using the flash-all file in a command prompt. This will install stock ROM with stock recovery. Make sure the phone has an unlocked bootloader and you should be fine.
Official OTA updates cannot be installed with a custom recovery.

I tryied 3 times to install OS with flash-all. All the problems start after i installed CWM and try to root the phone, but after that, i used a stock rom image that was different build than actually one.
I`m not sure yet who`s fault is.
Any ideas?

I don't recommend using CWM, only TWRP.

After you flash TWRP always boot into it, and since you're flashing a custom recovery I'm going to assume you don't care about OTA's, swipe to allow system to be mounted. TWRP will automatically patch the system to survive android trying to overwrite it. Reboot into TWRP a second time to be safe. TWRP should stick from now on until you flash over it or restore stock system partition.

Yes, now i have TWRP as recovery, but i want to replace it with stock recovery.
Problem is, when i upload stock recovery and try to boot in recovery mode, i got the green dead android with red triangle.
But after TWRP uploading and booting in recovery mode, TWRP is there..
I really don`t know what`s wrong.

Flash stock recovery, select recovery from the fastboot menu, hold the power button and press volume up button.

Help, MMB29Q update wipes TWRP

Hi all,
Recently I updated my Nexus 5 from Lollipop to Marshmallow 6.0.1 (MMB29Q) - latest build.
everything stock works fine but, once I flash a customer recovery, in my case TWRP it stops working...I get either a startup loop or TWRP gets erased by stock recovery.
I tried various steps ...
flashed TWRP 2.8.7.1 - rebooted to boot loader was able to get into TWRP but, once I reboot system, everything works but TWRP is gone/erased and replaced by stock recovery?
Flash TWRP 2.8.7.1, then flash latest TWRP 3.0, reboot to boot loader and can get into TWRP but once i reboot into system, I am stuck on the initial boot loop.
I have to start from scratch of flashing system and boot etc to get past the loop and it still replaces TWRP with stock recovery.
I can always get into Fastboot but when I go to recovery it seems its being replaced by stock recovery.
anyone experiencing this issue? thanks for your help.

I guess I am doing something stupid but, not sure what...and thanks for your help

If you give more detail on the steps you are taking it will be easier for someone to help. Also, have you tried doing a factory reset when it bootloops?

thanks for the response..here are the details..
I had Lollipop with TWRP 2.8.7.1
yesterday, I downloaded latest build from android site...extracted all files....booted into bootloader and flashed all files..
rebooted - Marshmallow works perfectly...offcourse it not rooted yet or its locedback due to this flash
Scenario:1
So downloaded TWRP 2.8.7.1 and flashed it as recovery, no errors nothing...i rebooted to bootloader and went to recovery to confirm TWRP is there
I rebooted the system - TWRP gives option to root which I said yes so its rooted. I reboot system, this goes into bootloop - I wait for say 5-10 min in this loop mode and I see that adb can recognize the device but nothing else....its stuck in loop
when I force shut down by holding power button for few sec - and go back bootloader/recovery - TWRP is still there
***note*** I did factory wipe in TWRP but that did not fix above condition.
Scenario2:
exact same steps but after I flashed twrp2.8.7.1, I rebooted bootloader and flashed twrp 3.0 as well confirmed twrp 3.0 is flashed and rebooted system - phone start normally no issues - when I restart to bootloader - no TWRP exists, its replaced by stock recovery
Scenario 2, I tried couple of other ways and still the same thing happens - twrp 3.0 get erased.
not sure what I am doing wrong but TWRP doesn't stick
since this is my active device - i flash system.img and boot.img to get the phone to working condition
thanks for your help

Try flashing the latest supersu to get root.

audit13 said:
Try flashing the latest supersu to get root.
Click to expand...
Click to collapse
That did the trick.....thank you very much. I was using older version of supersu thinking it was latest.....I downloaded V2.65 and installed it and that fixed all my troubles..
muchas gracias

Need help with recovery please...

I bought this phone so I can get access to a lot of different roms... I'm trying to install twrp as my recovery or cmw but when I flash it after unlocking the boot loader with cmw it doesn't stay installed and revert back to the original request and the twrp I get an error message in twrp about original recovery and then the phone goes into a boot loop. It has the latest OS version running with April Security fixes... please help

Flash twrp as it is a more versatile and widely supported recovery.
Flash twrp in fastboot mode. After flashing, use the power and volume buttons to boot directly to twrp, do not reboot the phone until after you have entered recovery.

audit13 said:
Flash twrp as it is a more versatile and widely supported recovery.
Flash twrp in fastboot mode. After flashing, use the power and volume buttons to boot directly to twrp, do not reboot the phone until after you have entered recovery.
Click to expand...
Click to collapse
did exactly what you said and im getting thr error / system to prevent the stock rom from replacing twrp...
whats happening

I recommend flashing the latest stock rom to make sure the phone boots properly.Then, I would flash twrp again.

audit13 said:
I recommend flashing the latest stock rom to make sure the phone boots properly.Then, I would flash twrp again.
Click to expand...
Click to collapse
Did that and flashed twrp and I'm still getting the error...
I unlocked boot loader
Flashed twrp
With USB still plugged in I selected recovery from the fastboot menu...
Boots to recovery and still get that error message
Am I doing something wrong

You're flashing 2.8.7 for the hammerhead?

audit13 said:
You're flashing 2.8.7 for the hammerhead?
Click to expand...
Click to collapse
No I'm flashing the latest 3.0.2 version is that the problem?

I would try 2.8.7

[Solved][C2105]Can't install custom recovery with anything contanining FOTAKernel way

Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?

qqzzxxcc said:
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
Click to expand...
Click to collapse
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety

Kungfu73 said:
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Click to expand...
Click to collapse
Thanks, that helped me so much!

Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.

qqzzxxcc said:
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
Click to expand...
Click to collapse
Glad that it worked for you and you finally could get latest one!
I forgot to mention that in first method, after installing LP ROM, install recovery installer app and flash TWRP v2.8.7.2 and use that to install latest one !!! and LoL very long way
I just wanted to say that it is possible!

OnePlus one does not go into recovery after updating it

Hello everyone, I'll tell you what happened
First I was in CM13.1, then I flashed to oxygen OS 3.1.4 custom
(When I flash the ROM, without warning me the recovery was updated to the version TWRP 3.0.3-2TugaPower, previously being in a version inferior to 2.8)
After logging in to the new recovery, I noticed that the recovery version was not on the TWRP page, so I decided to flash the most recent version of TWRP (twrp-3.1.1-0-bacon.img), flashe it through Android sdk (Fastboot), everything went well the pc recognized me the OPO in fastboot Mode and flashe the recovery without problems, the problem came when I try to enter the new recovery the OPO does not enter the recovery stays in the OnePlus Logo.
(Before updating the recovery I tried to restate the backup of my previous rom CM13.1 but when I was going to restart it it stays in the OnePlus logo, and when I go to recovery I fixed that in the section of "Mount" system is not checked , Active but still the same, and when I return to recovery is removed.)
I ask you if you can give me ideas to be able to have recovery again and revive my OPO plz.

Molex69 said:
Hello everyone, I'll tell you what happened
First I was in CM13.1, then I flashed to oxygen OS 3.1.4 custom
(When I flash the ROM, without warning me the recovery was updated to the version TWRP 3.0.3-2TugaPower, previously being in a version inferior to 2.8)
After logging in to the new recovery, I noticed that the recovery version was not on the TWRP page, so I decided to flash the most recent version of TWRP (twrp-3.1.1-0-bacon.img), flashe it through Android sdk (Fastboot), everything went well the pc recognized me the OPO in fastboot Mode and flashe the recovery without problems, the problem came when I try to enter the new recovery the OPO does not enter the recovery stays in the OnePlus Logo.
(Before updating the recovery I tried to restate the backup of my previous rom CM13.1 but when I was going to restart it it stays in the OnePlus logo, and when I go to recovery I fixed that in the section of "Mount" system is not checked , Active but still the same, and when I return to recovery is removed.)
I ask you if you can give me ideas to be able to have recovery again and revive my OPO plz.
Click to expand...
Click to collapse
I guess you didn't read the OP of Oxygen Os correctly,he clearly mentioned that this 'Tuga Power Recovery' is patched to work with Oxygen Os's firmware and one should not flash any other recovery.Now,what you can do is this,
https://drive.google.com/file/d/0B-ikULjZZlloNHpOdVBrTzQxZzQ/view?usp=drive_web
> Download This file, install it somewhere and run Revert-2-CM.exe. Make sure you have fastboot drivers installed or it wont work.Avoid using any Antivirus program while doing this as they might give false alarms.After this you'll be restored to TWRP then you can flash any rom you want.The reason due to which you weren't able to find 'TugaPower Recovery' on TWRP page is because this is an Unofficial Recovery.

Question
What does the program do with the OPO?

If you are familiar with fastboot commands, this method should work. Had my OnePlus in the same situation last night messing around with Efidroid. Phone was bootlooping. Efidroid boot menu as well as recovery mode were both inaccessible. I had tried several other things but none worked for me. *CAUTION: this method did ERASE my userdata.* I downloaded a fastboot-able stock full firmware zip, then manually reflashed device. My beloved OnePlus is no longer my daily driver but still my fave device to experiment with so I just used COS 13.1 file. After full reboot, I downloaded and flashed official TWRP. Device is fully functional again, but without OOS installed.

Molex69 said:
What does the program do with the OPO?
Click to expand...
Click to collapse
It'll change your firmware and alter your recovery to a functional TWRP.You'll lose Oxygen Os after doing this.Though you can use this anytime when not being able to flash TWRP.

What should i do
Thanks a lot thanks to the method you told me my OPO has recovery again really thanks, but I have a question, I still in the TugaPower recovery, should I flash the stock recovery or the newest version of TWRP?
Because I do not know if flashing again the TWRP will happen the same