Database Info

Cannot enter Recovery mode

Hi... i tried to flash CWM and enter recovery mode a couple of times and not once am i successful. I keep getting a white HTC screen with red text "This build is for development purposes only, not to be distributed.. etc etc"
No matter which CWM i tried it just would not work... i noticed some people have this problem but no solution? Does the latest One S have some kind of block or something that does not let us run these images?

Wrong section !!!
Anyway, Are you flashing the CWM recovery image in fastboot ? Do you have unlocked bootloader ? Have you tried a different recovery image ?

First person I have heard of not being able to flash recovery. Unlock bootloader. Then go to appstore and download goomanager. Download and flash TWRP thru goomanager.....done
Sent from my HTC VLE_U using XDA Premium HD app

Moved To Q&A​
Please post questions in the Q&A section​

azzledazzle said:
Wrong section !!!
Anyway, Are you flashing the CWM recovery image in fastboot ? Do you have unlocked bootloader ? Have you tried a different recovery image ?
Click to expand...
Click to collapse
I can flash it...Yes flashing in fastboot, yes tried a few img...official, Paul and twcm... I can click the option too...but all still bring me to that screen. I cannot use goomanager because without cwm I can't root,
Am I missing something? My bootloader does show unlocked ... so it means my boot loader is successfully unlocked right

onlinechi said:
I can flash it...Yes flashing in fastboot, yes tried a few img...official, Paul and twcm... I can click the option too...but all still bring me to that screen. I cannot use goomanager because without cwm I can't root,
Am I missing something? My bootloader does show unlocked ... so it means my boot loader is successfully unlocked right
Click to expand...
Click to collapse
Yes, If it says unlocked then it is unlocked did YOU unlock it ?
Are the recovery images flashing successfully ? without any errors ? you could try and use adb to reboot in to recovery.
If that fails, You could try and fastboot boot recovery, You can flash almost anything this way

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I get.... yes I did unlock it. Yes I did successfully flash. Its just when I reboot and enter bootloader and choose recovery... I keep getting that despite trying multiple images ... what is the meaning of that screen anyway... if we know what it does perhaps we can know what is wrong

--duplicate post--

That writing you see is normal, It happens as soon as you put non official software on the device. I cant figure out why it wont boot into recovery.
You could try to flash stock recovery,
Then fastboot erase cache.
Then reflash CWM and hope for the best.
Dont give up, Ill have a look around for some kinda fix for you !
EDIT: Also try Hasoons All In One Tool until i figure this out

when I click recovery in the bootloader... it shows that and just stays there.... may I know where the link is to a stock recovery as I did not back up mine...

https://dl.dropbox.com/u/69014495/stock recovery.zip
Does the phone boot ?
Did you try fastboot erase cache ?

Hi.. i tried flashing the stock recovery with Hasoons tool... I still get to the screen which shows... "this build is for development purposes only. Do not distribute.. etc etc..." Thats so strange. Logically it should should just show that for awhile then go on to the recovery isnt it? Why does it just stay there?
By the way.. how do i erase cache? Is it possible to be done without entering recovery?

I tried flashing the stock recovery. Locking the bootloader... then unlocking it all over again. Then flashing the CWM recovery... then boot to recovery.. still.... the same. :-(

so the phone does never boot ??
If i was you i'd run an RUU and start all over again

Oh no... the phone is perfectly fine.. its just the Recovery in to which its stuck. The normal operation of the phone is totally OK. I read something.. if i had flashed a recovery image... it should show my phone as "tampered" in the bootloader. Mine does not show that.. it just shows "Unlocked".. Is there something i missed?

Btw... i do not know if it matters.. but my phone is from Singapore.

it will only show tampered when you replace the stock recovery. Your phone believes it still has this.. which indicates that CWM didnt flash, even tho adb said it did
I came across a post where someone said erasing cache helped. So perhaps you could try this, It wont reset your phone, Just erases the cache, Boot into fastboot and type: fastboot erase cache
then try to get into recovery, if not try the command again and flash cwm recovery without rebooting.

I had the same problem. I did not know how to fix it directly.
Installing it using the app Rom Manager got CWM installed properly, though.

jayelbird said:
I had the same problem. I did not know how to fix it directly.
Installing it using the app Rom Manager got CWM installed properly, though.
Click to expand...
Click to collapse
How did you use Rom Manager when you dont have root?

azzledazzle said:
it will only show tampered when you replace the stock recovery. Your phone believes it still has this.. which indicates that CWM didnt flash, even tho adb said it did
I came across a post where someone said erasing cache helped. So perhaps you could try this, It wont reset your phone, Just erases the cache, Boot into fastboot and type: fastboot erase cache
then try to get into recovery, if not try the command again and flash cwm recovery without rebooting.
Click to expand...
Click to collapse
MMM.... Does not work.. I tried this
Boot into boot loader.. did the erase cache. Was ok. Did a reboot.
Reboot in to bootloader.. install recovery.. reboot
Reboot then attempted enter recovery.. still the same... Stuck at the red text
I then tried this
Boot into boot loader... did the erase cache.. was ok.. no reboot
Flash the recovery.. no reboot
Enter recovery.. still the same.. stuck at red text
Reboot.. enter recovery.. also the same.. stuck at red text...
:-( I have had HTCs.. Samsungs... and rooted all of em.. this is the first time i have been unsucessful.. heck i even rooted a China Device before....

Boot Loop without Recovery. OS gone.

Ill keep this short and sweet.
I have a HOXL 1.85 evita
Used this to get superuser and busybox. Tested positive for root with root checker.
Used this to get to unlock screen and restored my partitions to what it was previously. Rebooted into OS after to make sure phone was still rooted.
Boot into fastboot and used this to start pushing JB gapps/tg endeavoru ota 30/CWM touch to phone. Everything "successful" (no failures or permission denials). Flashed the boot.img and cleared cache
Go back into bootloader and select recovery. Recovery won't load. Stuck in bootloop with the "only for development purposes" message.
Currently trying to download the 1.85 RUU, fastboot oem lock, and then restart the whole process over. Just wanted to know if anyone could offer any advice on how to fix this before i revert everything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

When I had a boot loop like that I did a fast boot erase cache and it reverted me back to the kernel I had from the room flash. It fixed my boot loop and allowed me to boot into recovery. I don't know if that will help with your case but flashing boot.img is what caused my boot loop.
Sent from my HTC One X using xda app-developers app

davep1982 said:
When I had a boot loop like that I did a fast boot erase cache and it reverted me back to the kernel I had from the room flash. It fixed my boot loop and allowed me to boot into recovery. I don't know if that will help with your case but flashing boot.img is what caused my boot loop.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
i fastboot erase cache and it still goes into boot loop
EDIT--------
just flashed twrp recovery and at least i have recovery working now.
no usb mount storage though. im using twrp 2.2.0. win7 keeps asking me to format the disk

Is this what you flashed?
http://forum.xda-developers.com/showthread.php?t=1763240
You realize this is an International One X ROM? It won't work on this phone.

What amuses me is that you know you have an Evita, yet you tried to flash something that has Endeavor in the file name.
These threads never get old.
Sent from my HTC One X using xda premium

_MetalHead_ said:
What amuses me is that you know you have an Evita, yet you tried to flash something that has Endeavor in the file name.
These threads never get old.
Click to expand...
Click to collapse
At least it looks like he didn't accidentally overwrite hboot like this guy did.

wow. noob moment. for some reason i ignored it stupidly hoping it would work. anyway...sorted everything out. sd card mounts now...just had to format it on win7

theledman said:
wow. noob moment. for some reason i ignored it stupidly hoping it would work.
Click to expand...
Click to collapse
You're lucky; people have hard-bricked their phones doing that.

iElvis said:
You're lucky; people have hard-bricked their phones doing that.
Click to expand...
Click to collapse
I accidentally flashed recovery to boot portion. ie
HTML:
fastboot flash boot twrp.img
instead of
HTML:
fastboot flash recovery twrp.img
.
Then I also flashed recovery to recovery portion thinking that I can boot into recovery.
But now my phone boots and stays at twrp logo.
Even when I try to boot into recovery the same twrp logo nothing happens.
please help.
Hboot: 1.12.0000
Radio : 2.1204.135.20
HTC__001

Nexus 5 stuck in bootloop with no access to E:

My phone (2nd nexus5, not my daily driver nexus) is stuck in a bootloop (stuck at the booting animation) after updating via the OTA updtes, never rooted or touched any setting in the dev options in the setting menu.
The phone stays like that for hours, doesn't even reboot on its own, just keeps playing the bootanimation for hours and hours until the battery dies.
I have access to the bootloader, and default(stock) recovery.
tried oem unlock, but it doesn't work, and shows no errors.
Tried hard reset from the stock recovery and got numerous E: Failed to mount ..... errors. (check attached photo)
All attempts to wipe or format anypart of the phone fail with the same error,
ADB side load of a custom recovery ( TWRP ) also failed with the same error.
Please help me out, data loss is not an issue as i had no imp data and used it mainly for calls and emails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom

pranavmali said:
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
Click to expand...
Click to collapse
It shows an error
FAILED (remote: not supported in locked device)
Like I said, oem unlock doesn't work.
As soon as i give the oem unlock command, it will ask for conformation, after hitting yes,
it will even show LOCK STATE - unlocked.
But as soon as the phone reboots or re-enters bootloader, the phone is back to a locked bootloader.
On unlocking bootloader, flashing TWRP via fastboot, when i enter recovery mode, i am still taken back to the stock recovery.

Try Wug fresh's tool kit! To unlock bootloader

Does the give give an error message when issuing the fastboot oem unlock command?

pranavmali said:
Try Wug fresh's tool kit! To unlock bootloader
Click to expand...
Click to collapse
No effect, still stuck the same way.
below is the live log from the NRT toolkit
Live log initiated [2016-05-19]:
Analyzing factory image; please be patient...
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
Checking ADB/FASTBOOT Connectivity
adb devices
03670030215d290e device
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
fastboot oem unlock
Rebooting your device...
and then suck at bootanimation loop

audit13 said:
Does the give give an error message when issuing the fastboot oem unlock command?
Click to expand...
Click to collapse
when i give the fast boot oem unlock command, it will get executed, my phone will ask for me to manually go to the yes key, hit power button to conform,
I am taken back to the bootloader screen, it shows lock state- unlocked
and the word "erasing..." flashes under it for less than 1 second and thats it...no other change what so ever, as soon as i reboot to bootloader or reboot the phone or do anything, the phone is back to the locked bootloader state.

The emmc is damaged or defective and can only be fixed with a motherboard replacement.

audit13 said:
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
Click to expand...
Click to collapse
is there a sure-shot way of determining that my emmc is damaged ..?
the state that my phone is in now, it would make more sense to just buy a new device rather than replace the motherboard.
or
another option i can consider is the thread - http://forum.xda-developers.com/google-nexus-5/help/nexus-5-64gb-t3350533 for getting a new emmc and replacing, but before i take any actions i would like to know that there is no other option left.

Since you now appear to have nothing to lose, try installing the full N5 OTA image:
https://developers.google.com/android/nexus/ota#hammerhead-for-nexus-5-mobile
The instructions are on the page, or NRT has an OTA option (Advanced utilities/Sideload OTA update).
It may not work if your bootloader is genuinely locked or if the EMMC is really fried, but worst case you can't do any more damage, right?

HELP!!! Recovery and system wont boot

I just received my Pixel (not XL and not verizon version) that I bought from the Google Store and I tried loading TWRP on it. Fastboot works and I can fastboot into a TWRP recovery, however, whenever I try to flash another recovery with that recovery, the the message warning me to lock the bootloader pops up, then the phone very briefly goes to white screen with the google logo and instantly shuts off. Then it automatically repeats that process.. Am not sure what I did wrong (for example if I accidentally flashed the wrong variant to begin with?) but I also don't know how to fix it. I have tried all of the TWRP variants and nothing has worked. I also think the I was on 7.1.2.
I spent all night searching through all of the threads and could not find anyone who had a similar situation so any help is greatly appreciated and desperately needed.
Thank you in advance

SponsOne said:
I just received my Pixel (not XL and not verizon version) that I bought from the Google Store and I tried loading TWRP on it. Fastboot works and I can fastboot into a TWRP recovery, however, whenever I try to flash another recovery with that recovery, the the message warning me to lock the bootloader pops up, then the phone very briefly goes to white screen with the google logo and instantly shuts off. Then it automatically repeats that process.. Am not sure what I did wrong (for example if I accidentally flashed the wrong variant to begin with?) but I also don't know how to fix it. I have tried all of the TWRP variants and nothing has worked. I also think the I was on 7.1.2.
I spent all night searching through all of the threads and could not find anyone who had a similar situation so any help is greatly appreciated and desperately needed.
Thank you in advance
Click to expand...
Click to collapse
Try fastboot flashing 7.1.2 boot.img, then fastboot boot into TWRP, flash the attached twrp pixel installer, reboot to recovery from recovery , then flash supersu, then reboot. It will reboot a time or two if that is normal.

Tulsadiver said:
Try fastboot flashing 7.1.2 boot.img, then fastboot boot into TWRP, flash the attached twrp pixel installer, reboot to recovery from recovery , then flash supersu, then reboot. It will reboot a time or two if that is normal.
Click to expand...
Click to collapse
Thank you so much for your quick response.
Is this the version I use? I want to make sure I download the correct one: 7 .1.2 (N2G47O, May 2017)

SponsOne said:
Thank you so much for your quick response.
Is this the version I use? I want to make sure I download the correct one: 7 .1.2 (N2G47O, May 2017)
Click to expand...
Click to collapse
That should work though there should be June update.

p
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
Tulsadiver said:
That should work though there should be June update.
Click to expand...
Click to collapse
Thank you again for your help. I put the June version on instead of the previous and everything seems to be working. My only question is at the end of fastbooting the factory img, it said, "FAILED (remote: Partition table doesn't exist). Is that normal or something to be concerned about?
Here is a photo I took of it:

[/IMG]

SponsOne said:
[/IMG]
Click to expand...
Click to collapse
I don't know why the image doesn't seem to be uploading so here is a link to it:
https://drive.google.com/open?id=0B3fIceeoMIn8NC1XTUVTODNBT1k

[solved + how i solved it] the current image(boot/recovery) have been destroyed

so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?

update: now i can use bootloader

update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!

Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking it

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo

Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery

And how do you enter that mode without the application?

enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work

in case you get the same error for the recovery you have to unlock the bootloader again

Can I send you a private message?

yes

Did you solve it? I'm facing the same issue.

Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do