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- NO OS INSTALLED asus ze500kl

hello guys
i accidentally deleted my os. now it says no os found.
bootloader is not unlocked. have twrp working fine.
i have done some research but dont have clear vision.
can i download any version or should i download particular firmware version to which my phone belong.
what is the difference between firmware and OS
i have downloaded my old firmware version but is says "error executing updater binary in zip"
Asus EXPERTS please help me. i am waiting for your reply with 1000 eyes:crying:
PLEASE USE GENERAL WORDS TO MAKE ME UNDERSTAND CLEARLY

Flash to stock recovery and flash to stock rom again

XVenom said:
Flash to stock recovery and flash to stock rom again
Click to expand...
Click to collapse
while i do that i get errors. it says "error executing updater binary in zip"
i didnt unlock bootloader. can we still able to flash?

Try to flash your stock Rom using Odin[PC].You will most likely get your stock Rom in xda itself.
Sent from my Cyanogenmod10.1 Huawei Y210 0100

1) Flash this file with twrp : http://forum.xda-developers.com/attachment.php?attachmentid=3718733&d=1460659898
2) Flash stock recovery with adb
3) Flash stock rom with recovery
sorry for my bad english

XVenom said:
1) Flash this file with twrp : http://forum.xda-developers.com/attachment.php?attachmentid=3718733&d=1460659898
2) Flash stock recovery with adb
3) Flash stock rom with recovery
sorry for my bad english
Click to expand...
Click to collapse
thanks for your interest guys. now i am unable to into fastboot mode too. when i hold power + volume up i only see asus logo but not fastboot mode.

Did you install the software ? Does it work ?

XVenom said:
Did you install the software ? Does it work ?
Click to expand...
Click to collapse
no i flashed the ubu zip file and when i try to flash stock recovery i am unable to get into the fastboot mode

asus ze500kl said:
no i flashed the ubu zip file and when i try to flash stock recovery i am unable to get into the fastboot mode
Click to expand...
Click to collapse
Tried to enter by using adb

XVenom said:
Tried to enter by using adb
Click to expand...
Click to collapse
stock recovery is a img file. Twrp is not detecting the img file.
shell i directly flash the original rom?

asus ze500kl said:
stock recovery is a img file. Twrp is not detecting the img file.
shell i directly flash the original rom?
Click to expand...
Click to collapse
No, you can't flash the stock recovery with twrp and twrp is don' flash the stock rom
You can flash the stock recovery with only adb

XVenom said:
No, you can't flash the stock recovery with twrp and twrp is don' flash the stock rom
You can flash the stock recovery with only adb
Click to expand...
Click to collapse
i am unable to flash through adb. it says cannot read the zip file any other option?

asus ze500kl said:
thanks for your interest guys. now i am unable to into fastboot mode too. when i hold power + volume up i only see asus logo but not fastboot mode.
Click to expand...
Click to collapse
broooooooooooooooooooooooooooooooooooo
FINALLY MY PHONE IS ON NOW SO HAPPY DID DANCE WHEN IT REBOOTED
I WILL EXPLAIN CLEARLY SO THAT IT MAY HELP OTHERS TOO.
i downloaded currunt rom from the official website.
tried to flash the stock rom but it gave me a error like- this is for ww sku your phone is asus zooe
theni extracted the zip file and edited the updater script and reflashed successfully but still stuck at the asus logo with out loading symbol.
i tried to flash stock recovery image with adb but it was saying unable to find the recovery file- not exactly but something like that.
i tot the problem is with adb. then i remembered that i have my phone model root file. to conform that the adb is working properly or not i gave a try to flash the mod_boot.img (asus ze500kl root img file) but unfortunatelly it flashed, rebooted and finally my phone is on.
ANY WAY UR METHOD DIDN'T WORK BUT THANKS A LOT FOR REPLYING TO MY PROBLEM. YOU GAVE ME SO MUCH KNOWLEDGE ABOUT STOCK RECOVERY AND STOCK ROM.
THANKS ALOTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT

XVenom said:
No, you can't flash the stock recovery with twrp and twrp is don' flash the stock rom
You can flash the stock recovery with only adb
Click to expand...
Click to collapse
broooooooooooooooooooooooooooooooooooo
FINALLY MY PHONE IS ON NOW SO HAPPY DID DANCE WHEN IT REBOOTED
I WILL EXPLAIN CLEARLY SO THAT IT MAY HELP OTHERS TOO.
i downloaded currunt rom from the official website.
tried to flash the stock rom but it gave me a error like- this is for ww sku your phone is asus zooe
theni extracted the zip file and edited the updater script and reflashed successfully but still stuck at the asus logo with out loading symbol.
i tried to flash stock recovery image with adb but it was saying unable to find the recovery file- not exactly but something like that.
i tot the problem is with adb. then i remembered that i have my phone model root file. to conform that the adb is working properly or not i gave a try to flash the mod_boot.img (asus ze500kl root img file) but unfortunatelly it flashed, rebooted and finally my phone is on.
ANY WAY UR METHOD DIDN'T WORK BUT THANKS A LOT FOR REPLYING TO MY PROBLEM. YOU GAVE ME SO MUCH KNOWLEDGE ABOUT STOCK RECOVERY AND STOCK ROM.
THANKS ALOTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT

Yeah try ur original rom

[SOLVED] TWRP 3.0.2 bootloop

Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.

After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?

audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.

Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.

audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!

I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.

TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?

I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...

download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck

hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...

kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda

audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.

kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/

Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...

P5100 shows TWRP logo and resets

I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?

light401 said:
I just flashed many different versions of TWRP downloaded from their site(I got only the ones compatible with my P5100). After successfully flashing them all through Odin, I can't boot into recovery. The TWRP logo screen is shown and after 2 seconds the device reboots. I followed many guides, and they were all similar in this particular process. Am I missing something, or could there be anything wrong with my unit?
Click to expand...
Click to collapse
did you also installed a rom??

No. I'm running the stock rom, no root. I just wanted to get the twrp installed because I need to copy my personal files to an sd card. My stock rom is rebooting itself after completing the normal system startup. I can barely open any app. So I need to backup my files and do a factory reset. Any ideas? Thanks!

I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.

Ka-B00M said:
I think you need to get rid of TWRP and root the stock ROM, then flash TWRP using an app running on your tablet. Do not use a PC to flash the recovery. Also, if you are installing a zip, you must do it on the device, not through your PC.
Click to expand...
Click to collapse
That doesn't make sense. Odin exists for the exact purpose of flashing through a PC, in case your recovery or anything gets damaged.

Installed twrp phone reboots to twrp

I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files

cgrimm9 said:
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
Click to expand...
Click to collapse
Did you fastboot boot into TWRP, then flash twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip? Were you stock prior?

Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal

cgrimm9 said:
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
Click to expand...
Click to collapse
Yes, you are not supposed to install twrp, just boot into it. If you install it by mistake, you go back, flash stock boot.img, and do it again.
This is from Dees_Troy's post located here
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.

@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Tulsadiver said:
Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
Click to expand...
Click to collapse
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...

alienjon said:
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
Click to expand...
Click to collapse
Things have changed with 8.1. you have to root with magisk. From slot b you cannot fastboot flash boot_a boot.img?
I believe the instructions now are to boot to TWRP, install TWRP pixel installer zip, then flash Magisk zip
Here is where TWRP files are here
https://dl.twrp.me/sailfish/

Tulsadiver said:
From slot b you cannot fastboot flash boot_a boot.img?
Click to expand...
Click to collapse
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)

alienjon said:
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
Click to expand...
Click to collapse
Yes, the zip file that is located where the flash-all.bat is. Unzip it and flash the boot.img.
I bought a Pixel 2 on swappa. It had different bootloader's on slot a and slot b. I couldn't flash updates when on slot a. I thought I was hosed but from slot b I could flash to slot a so now I'm fine. Slot a had a preview bootloader.