Database Info

Cant boot into recovery...HTC screen only

I attempted to place a ROM on the phone using CWM recovery and something messed up. Now, I can boot into screen that says fastboot, recovery, etc. However, when I select recovery, nothing happens. Anyone point me in the right direction...im back to using my Blackberry!

From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast

E.Cadro said:
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
This is where I am stuck. Unfortunately, I'm not all that familiar with Fastboot. When connecting the phone to the PC with a USB, I see that the phone says Fatboot USB. From there I'm lost. I've not been able to find a guide that describes how to install a ROM using fastboot. Lots of posts says that it can be done, but none describing how its done. Anyone pointing me in the right direction?

http://forum.xda-developers.com/showthread.php?t=1754018

gunnyman said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?

rpritch said:
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
Click to expand...
Click to collapse
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?

rpritch said:
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
Click to expand...
Click to collapse
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1

veritas2884 said:
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
Click to expand...
Click to collapse
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast

E.Cadro said:
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Our devices will not boot. All we can get is either the white HTC Screen or get into the menu that allows fastboot/recover/ect...

Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app

c5satellite2 said:
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:

Recommended process for fixing strange issues like what you were experiencing. Glad it helped you guys out!
Sent from my HTC One XL using xda app-developers app

veritas2884 said:
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Click to expand...
Click to collapse
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?

rpritch said:
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
Click to expand...
Click to collapse
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!

veritas2884 said:
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
Click to expand...
Click to collapse
I cant seem to find a stock Rogers Ruu...will continue searching. Anyone out there have it?

http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above link is what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!

Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.

Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.

slash178 said:
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
Click to expand...
Click to collapse
What you are doing wrong is flashing the recovery for the wrong phone. Any file with "enveavoru" in it is for the international (Tegra3) version. Our phone is "evita".
Only install things in our Dev forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
To see everything in an organized list, go to my index: http://forum.xda-developers.com/showthread.php?t=1671237
Also, TWRP is recommended. CWM does not officially support our device, and therefore is just a port, and buggy. TWRP officially supports our device.

im getting the same error and im using the recovery ending on evita

{HELP} - This build is for development purposes only - loop

Dear All
I need some help
Got a new HTC One XL today (UK, Everything Everywhere)
Unlocked the bootloader using HTC Dev
Tried to flash recovery (recovery-clockwork-5.8.4.0-endeavoru.img)
Now I get the "This build is for development purposes only ...."
I can sometimes get to the bootloader but the PC does not recognise the phone when it goes into bootloader
When i choose recovery it boots back to the splash screen with "This build is for development purposes only ...." again
I am lost for things to do now and desperately some help
Let me know - thanks
Caolfin

Don't use CWM on this phone, it has issues.

joshuadjohnson22 said:
Don't use CWM on this phone, it has issues.
Click to expand...
Click to collapse
Ok, I've also tried to flash the twrp .img file using the command
fastboot flash recovery ****.img
this did nothing as well
when I choose the recovery option from the bootloader menu it goes immediately to the white htc screen with the "this build is for ...." stuff
Any ideas ?

Is the phone an evita or endevour? (quad core or dual core). If it is an evita, you may have a little bigger problem due to that endeavor cwm flash.

bimmernut318 said:
Is the phone an evita or endevour? (quad core or dual core). If it is an evita, you may have a little bigger problem due to that endeavor cwm flash.
Click to expand...
Click to collapse
Oh no
Its an EVITA
mainver : 2.34.61.2
I've also tried to flash twrp but every time I go to recovery from bootloader I get the white screen with the "development purposes" stuff
What do you think ?

caolfin said:
Oh no
Its an EVITA
mainver : 2.34.61.2
I've also tried to flash twrp but every time I go to recovery from bootloader I get the white screen with the "development purposes" stuff
What do you think ?
Click to expand...
Click to collapse
That development purposes only is normal if you unlock using the super-cid...there is nothing you can do about that...mine has it as well.

mikelebz said:
That development purposes only is normal if you unlock using the super-cid...there is nothing you can do about that...mine has it as well.
Click to expand...
Click to collapse
Hi Mike
I've no problem with the writing on it if I could get it to recovery or to load ICS past this screen I would be very happy
Any ideas as to how I would get past this ? it seems to be in some sort of bootloop or bootcrash

You flashed the cwm recovery for the endeavor quad-core...........
Download this twrp recovery,
http://db.tt/sXmdepmX
Stick it in your adb/fastboot folder
Boot phone into your bootloader, make sure it says fastboot USB
From cmd prompt type
fastboot devices
Make sure it device serial# shows up
Now type-
fastboot flash recovery twrp.img
Should get-
Sending
Writing
Ok
Now resend the same command by pressing up arrow, then enter.
Should get the same readout
Now on the phone, navigate to the recovery option and select it.....you should have twrp now.........and don't flash endeavor device ANYTHINGS anymore:beer:
Sent from my HTC One XL using Tapatalk 2

yes, i think that is what i have done
now i cant get past the white htc [email protected] screen with the warning message

Edit:nm

18th.abn said:
You flashed the cwm recovery for the endeavor quad-core...........
Download this twrp recovery,
http://db.tt/sXmdepmX
Stick it in your adb/fastboot folder
Boot phone into your bootloader, make sure it says fastboot USB
From cmd prompt type
fastboot devices
Make sure it device serial# shows up
Now type-
fastboot flash recovery twrp.img
Should get-
Sending
Writing
Ok
Now resend the same command by pressing up arrow, then enter.
Should get the same readout
Now on the phone, navigate to the recovery option and select it.....you should have twrp now.........and don't flash endeavor device ANYTHINGS anymore:beer:
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much for that - I now have TWRP working and its great
I still have a problem that the phone will not boot past the HTC screen that has the "this build is for development purposes..."
It reboots and reboots but never goes past this screen
Do I need a ROM as well ?

caolfin said:
Thank you so much for that - I now have TWRP working and its great
I still have a problem that the phone will not boot past the HTC screen that has the "this build is for development purposes..."
It reboots and reboots but never goes past this screen
Do I need a ROM as well ?
Click to expand...
Click to collapse
Yes.. You need a rom.
Dl it on your pc, boot into twrp and mount the sd to transfer it.

qwertyaas
Very much appreciate your responses
ok, I have moved the cm10 evita jellybean ROM over and flashed it - all seemed to go successfully
Used TWRP to factory reset beforehand
Used TWRP to turn the phone off
Pressed the phone button to turn the phone on
Phones boots immediately to white HTC splash screen with the "this build is for development purposes..." and reboots after about 10 seconds, and reboots and reboots
Never gets past this point
Any ideas ?

Your probably on hboot 1.14, so....the cm10 Rom.zip, on your pc, unzip it and you will see a boot.img, put the boot.img in your adb fastboot folder, boot phone into bootloader....cmd prompt type
fastboot flash boot boot.img
Do it a second time for good measure, then type
fastboot reboot
Should be good
Sent from my HTC One XL using Tapatalk 2

18th.abn said:
Your probably on hboot 1.14, so....the cm10 Rom.zip, on your pc, unzip it and you will see a boot.img, put the boot.img in your adb fastboot folder, boot phone into bootloader....cmd prompt type
fastboot flash boot boot.img
Do it a second time for good measure, then type
fastboot reboot
Should be good
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
HAHAHAHAHAHAHAHAH !!!!!!
I dont know what to say !! - Its working - you are an absolute genius - thank you sooooo much for your help
Great stuff - you are a legend
Super stuff :laugh::laugh::laugh:

18th.abn, god of the noobs :cyclops:

finally i made it too. thank you so much!!!

Hey i know this is super mega delayed. but i need that twrp recovery. the link above is no doubt broken now. thanks

Possible Brick

Hey all,
So tonight I attempted to install the Unofficial AOKP Jelly Bean posted here: http://forum.xda-developers.com/showthread.php?t=1862156
Before doing that, I followed the instructions to Unlock, Recovery, and Root my One S here: http://forum.xda-developers.com/showthread.php?t=1583427
After following those instructions, I then followed the instructions for AOKP Jelly Bean however my sdcard couldn't be mounted and the phone was in a boot loop if I didn't boot into fastboot by holding down the volume - and power buttons.
I attempted these instructions below however I couldn't get a stock recovery flashed.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Click to expand...
Click to collapse
Still caught in the reboot loop, I relocked and tried to run an RUU file found here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
I was able to successfully re-lock the phone however every time I try to run the RUU file it comes back with an error about 3-5 minutes into the process.
At this point, my phone boots into fastboot. At the top I have "Tampered, Relocked, Security Warning." My HBOOT is 1.14.0004 and my Radios is 1.08ts.50.02.16
I would appreciate any help if there is a solution. Thank you for your time!
Update: Not sure if this is helpful or not, but whenever I try to do something with The All in one toolkit the cmd window says device not found. Also, when I try to boot into recovery from fastboot, I get a green downward and circular arrows before getting the red triangle and exclamation point.
Update: Running the RUU mentioned above fails at the Signature stage and the cmd prompt when trying to write recovery returns "signature verify fail"

Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app

whozilla said:
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure I am S4 (tmobile USA). I am on a windows 7 home build, and the drivers should be installed (at least, I could use HTC sync before all of this). I'll definitely try again tonight. If anyone has any other suggestions they would be much appreciated!

Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app

whozilla said:
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help!
Here are my results:
HTC Sync is not running. Fastboot devices returns a device ID so that seems good. When trying to flash a stock recovery (that I got on this forum somewhere, but can't remember where) it sends it ok but I still get "remote: signature verify fail"
I unlocked the device and flashed TWRP 2.2.2.0 with the all in one tool kit. This put me back into the boot loop mentioned above. Once I manually got back into the bootloader and selected recovery, I was able to get into the TWRP recovery. At this point, I am kind of worried about doing anything. I would like to be able to push AOKP Unofficial JB if at all possible. Any further guidance would be appreciated!

Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville

usaff22 said:
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
It is clear to me that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!

You have to fastboot push the AOKP zip through the bootloader I think.
Sent from my locked, tampered ville

Veritas327 said:
It is clear to fme that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
Click to expand...
Click to collapse
Just like the post above mine says, you have to adb push the file onto the sd card. I'm not to familiar with TWRP (using it actually got me into a bit of a dilemma) so I only know the process for CWM. If TWRP is anything like CWM then you have to be in recovery to adb push and have sdcard and system set to "unmont". It's pretty easy and there's a couple threads explaining how to do it. The command basically is :: adb push romname.zip /sdcard/romname.zip:: Note the space before "/sdcard" I'dpn't know if this ill help you or if you've solved your problem already but this is just my 2 cents, good luck!

Sorry for my late reply; I was rushed to the ER last night in excruciating pain. Looks like I'll be dealing with a kidney stone over the next few days.
So far, I have tried to push AOKP through fastboot. ADB says "no devices found" and when I type adb devices, I get "List of devices attached" and nothing under it. However, when I type fastboot devices, I do get a device ID. As of now, I am downloading the TWRP 2.3 recovery and will try to sideload with adb with that.

Update:
I was able to successfully install TWRP 2.3 and adb sideload the AOKP zip file. The phone then went back into a reboot loop, and I was able to get into recovery to install the .zip. The phone then rebooted, showed the HTC with red text screen very briefly, went to black, showed the HTC with red text screen again, went black, and now the aokp boot animation is repeating over and over. It has been doing so for about 5-7 minutes. I haven't yet installed gapps as mentioned in the AOKP post (I'm honestly not even sure what that is). Where should I go from here?
As a side note, the phone is plugged into power though the LED is not lighting up. It was at 98% when I flashed the .zip, but I obviously don't want it to die on me. Should I turn the phone off or is it still charging?

Veritas327 said:
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Click to expand...
Click to collapse
The newer hboot versions (1.13 and up) don't let you flash boot images in recovery, even if it reports success.
So there is technically no difference, except fastboot always works and recovery depends on hboot version.
Did you fastboot flash the boot image that comes with your rom?
-Jobo
Edit to add: So it seems that following the recipe in your post #1 did in fact make your sdcard mountable again, or did you do something else as well for that?

Fixed!
I ended up flashing the boot.img with fastboot and then going into recovery, factory resetting and then re-installing the rom (and gapps which I now know stands for google apps). I'll be playing around with the ROM but at least I have a working phone again!
I think, in the end, it came down to my sd card not being mounted and my lack of knowledge about how to fix it.

[Q] No OS, can't get to bootloader or recovery

Hey everyone, I just went through the process of rooting my phone using the Hasoon200 tool (http://forum.xda-developers.com/showthread.php?t=1952426). Everything worked fine; I unlocked the bootloader, flashed the TWRP recovery, and installed CM10. However I couldn't get past the CM10 loading screen so I went back to recovery and wiped everything I could (cache, dalvik, system, factory restore) then rebooted. After that I can't get past the white HTC "Quietly Brilliant" splash screen. No bootloader or recovery. Hasoon2000's tool can't reach the phone to do anything. Holding Down Volume and Power buttons just reboots to the splash screen. When I plug the USB into my computer it must be recognized somehow because it connection notification sound plays but I don't see the drive. What can I do now?

Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
Than select recovery
And once in bootloader check if you have hboot 1.14
---------- Post added at 03:37 AM ---------- Previous post was at 03:36 AM ----------
When you get back into recovery do the same wipe process than flash the Rom...if you have hboot 1.14 you have to flash the boot.img manually

Yea what box of kittens says ^^^^^^^
http://forum.xda-developers.com/showthread.php?p=33303798
(This thread might help as well.= if your 1.14 hboot) And make sure your thanks button isn't broken at least for the member above who took time to help. :thumbup:
Sent from my HOX w/CM10.1

a box of kittens said:
Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
Than select recovery
And once in bootloader check if you have hboot 1.14
---------- Post added at 03:37 AM ---------- Previous post was at 03:36 AM ----------
When you get back into recovery do the same wipe process than flash the Rom...if you have hboot 1.14 you have to flash the boot.img manually
Click to expand...
Click to collapse
Thanks for the response. I'm able to reach the bootloader now, but when I select recovery it freezes once again on the white HTC splash (but this time with the HTC Dev red text below). And I do have hboot 1.14

subarudroid said:
Yea what box of kittens says ^^^^^^^
http://forum.xda-developers.com/showthread.php?p=33303798
(This thread might help as well.= if your 1.14 hboot) And make sure your thanks button isn't broken at least for the member above who took time to help. :thumbup:
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Thanks [email protected] reflash your recovery so fastboot flash recovery recovery.img(whatever you have it named but has to end with .img)

Reflash your recovery image. Then try again
Sent from my DROID RAZR using Tapatalk 2

Thanks everyone, I'm back to recovery! Hopefully I can figure it out from here.

If you need anything else just post here.
Sent from my HTC One X using Tapatalk 2

ltjska04 said:
Thanks everyone, I'm back to recovery! Hopefully I can figure it out from here.
Click to expand...
Click to collapse
Easy peasy...
Flash rom,
boot into boot loader,
drop the boot.img inside your adb/fastboot folder,
Right click on you adb/fastboot folder and choose open command prompt here. The type
Fastboot flash boot boot.img
Reboot that beast and enjoy the profits
Sent from my HTC One XL using Tapatalk 2

New to this phone and was a little overeager. I unlocked bootloader, rooted, installed TWRP and flashed CM but didn't flash the boot img before flashing CM so it boots forever, of course (I'm so dumb...)
I can get back to the bootloader where I try to flash my CM boot img but adb won't detect the device (presumably because usb debugging isn't selected since I can't boot into the rom). How can I either 1) get adb to detect so that I can flash the boot img with adb or 2) flash the boot img without adb?
Stumped. Thanks in advance for any/all that can help with this.

_atlien_ said:
New to this phone and was a little overeager. I unlocked bootloader, rooted, installed TWRP and flashed CM but didn't flash the boot img before flashing CM so it boots forever, of course (I'm so dumb...)
I can get back to the bootloader where I try to flash my CM boot img but adb won't detect the device (presumably because usb debugging isn't selected since I can't boot into the rom). How can I either 1) get adb to detect so that I can flash the boot img with adb or 2) flash the boot img without adb?
Stumped. Thanks in advance for any/all that can help with this.
Click to expand...
Click to collapse
Sigh you flash boot img through fastboot

Get phone into bootloader. (White screen, 3 skating droids)- make sure it says "fastboot USB" in red
Right click on your adb/fastboot folder, choose "open command prompt here"
Type--> fastboot devices
See if anything shows up.
Sent from my One X using Tapatalk 2

a box of kittens said:
Sigh you flash boot img through fastboot
Click to expand...
Click to collapse
Hey! Thanks for replying. I'm stuck here. Fastboot flash of the boot img requires the phone to be usb detected, yes? I go to fastboot but when I type 'adb devices' I gets nothing back.
I don't think I was clear in my earlier post. I have CM and gapps flashed but it won't boot into the OS because I didn't flash the boot img first but now I can't get the phone to be detected by adb so I don't know how else to flash the boot img. Thanks for taking the time to reply to me. I realize you didn't have to.

Thanks to all! My phone rides again!

_atlien_ said:
Thanks to all! My phone rides again!
Click to expand...
Click to collapse
Lol what did to do to be able to fastboot flash
Sent from my One X using Tapatalk 2

Hey,
I was stuck too... Managed to get the recovery working but the fastboot flash boot boot.img thing is not working can anyone guide me through this?
I did try the forum ways but still isn't solving the problem...

strommer666 said:
Hey,
I was stuck too... Managed to get the recovery working but the fastboot flash boot boot.img thing is not working can anyone guide me through this?
I did try the forum ways but still isn't solving the problem...
Click to expand...
Click to collapse
Drop the boot.img INSIDE of your adb/fastboot folder.
Boot into bootloader
Right click on your adb/fastboot folder. Choose "open command prompt here" type --> fastboot flash boot boot.img
Sent from my One X using Tapatalk 2

Stuck in bootloader loop
Folks, I was stuck in similar situation as well; I had missed copying the boot.img step initially and after i did a factory reset on the boot loader i got stuck in HTC logo screen with red lines warning.
I followed the directions provided on this thread and am now able to get into TWRP recovery screen. What would be the steps for me now to flash a rom onto the device again. I had flashed the ViperXL rom prior to me stupidly doing the factory reset.
Per directions on another thread, I was trying to first have the rom and boot.img loaded using the mount from TWRP. However when i do the the step of 'Mount USB storage', I get the warning that on my computer that i need to 'Format Disk drive'. Not sure why would i need to do it.
Please help!
Thanks

singh.bobby said:
Folks, I was stuck in similar situation as well; I had missed copying the boot.img step initially and after i did a factory reset on the boot loader i got stuck in HTC logo screen with red lines warning.
I followed the directions provided on this thread and am now able to get into TWRP recovery screen. What would be the steps for me now to flash a rom onto the device again. I had flashed the ViperXL rom prior to me stupidly doing the factory reset.
Per directions on another thread, I was trying to first have the rom and boot.img loaded using the mount from TWRP. However when i do the the step of 'Mount USB storage', I get the warning that on my computer that i need to 'Format Disk drive'. Not sure why would i need to do it.
Please help!
Thanks
Click to expand...
Click to collapse
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app

exad said:
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I did the reformat for my SDCard; how do i proceed now? should i move the zip file for the rom to the sd card and try installing it ?What would be the next steps i would need to do to get back to the ViperXL rom i have downloaded; or is there a way for me to go back to the original HTC sense rom i had prior to flashing
Thanks
---------- Post added at 11:44 PM ---------- Previous post was at 11:18 PM ----------
exad said:
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
singh.bobby said:
I did the reformat for my SDCard; how do i proceed now? should i move the zip file for the rom to the sd card and try installing it ?What would be the next steps i would need to do to get back to the ViperXL rom i have downloaded; or is there a way for me to go back to the original HTC sense rom i had prior to flashing
Thanks
Click to expand...
Click to collapse
I was able to flash ViperXL rom again; I placed the zip file for the rom in the TWRP folder after i mounted the device. Thereafter i was able to install the rom from the recovery. All good for now . Although all my data from Sd card got wiped :crying:

Nexus 5 "No SU binary installed and SuperSU? cannot Install it

So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?

am3606 said:
So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?
Click to expand...
Click to collapse
are you sure that you "rooted" it, or did you just unlock the bootloader? thgat open android with the red sign is the stock recovery btw. what you need to do is flash a custom recovery via fastboot, either twrp or cwm, then flash the latest supersu via your new custom recovery. thats all that you need to do.
latest supersu http://download.chainfire.eu/supersu

Well I rooted it but due to some problems had to reset the whole thing. Before I reseted it, I had SuperSU installed and it said that the device was rooted.
I can't access the bootloader is the problem, when I go to recovery mode I go to the "stock recovery" with the android with the red sign saying no command. So am I suppose to place the zip file using android file transfer?

am3606 said:
Well I rooted it but due to some problems had to reset the whole thing. Before I reseted it, I had SuperSU installed and it said that the device was rooted.
I can't access the bootloader is the problem, when I go to recovery mode I go to the "stock recovery" with the android with the red sign saying no command. So am I suppose to place the zip file using android file transfer?
Click to expand...
Click to collapse
to access the bootloader, power off first. then power on holding the volume down button and the power button. that is the bootloader. thats what gives you the options to go into recovery, reboot bootloader, boot up, or power off. in order for you to be able to flash the latest supersu, you need to flash a custom recovery first.

simms22 said:
to access the bootloader, power off first. then power on holding the volume down button and the power button. that is the bootloader. thats what gives you the options to go into recovery, reboot bootloader, boot up, or power off. in order for you to be able to flash the latest supersu, you need to flash a custom recovery first.
Click to expand...
Click to collapse
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?

am3606 said:
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?
Click to expand...
Click to collapse
you need to flash it via fastboot while your phone is in the bootloader(there are instruction here). follow the "installing a custom recovery" part http://forum.xda-developers.com/showthread.php?t=2507905

am3606 said:
Oh I know about the bootloader I did it before its just that I can't access the recover, when I go to it in the bootloader I go to the android with the red sign.
How do I flash a custom recovery?
Click to expand...
Click to collapse
You must have flashed a custom recovery before to flash root.
If you're confused at this moment , its a good idea to put your phone down and get a cup of tea.
Then, read the how to unlock your bootloader / root thread stuck at the top of general.
Read through it. To have been rooted, you must have done all that stuff before. It has instructions for each step. But importantly, read don't do until you're familiar with it all
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
If you're confused at this moment , its a good idea to put your phone down and get a cup of tea.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
thats one of the best pieces of advice ive read!
sometimes, just taking a step back, a breather, a time out, opens your eyes to things right in front of you that you dont see. plus gives you a chance to read up and make yourself better prepared.

rootSU said:
...its a good idea to put your phone down and get a cup of tea...
Click to expand...
Click to collapse
You're so damn civilized across the pond. It's enviable.

You can also download the app "Goo Manager", in the settings menu there is an option to install the latest TWRP recovery. ☺
Sent from my Nexus 5

you can use nexus root toolkit to unlock bootloader and flash supersu:

am3606 said:
So I rooted my nexus 5 but when I check to see if it is rooted, I get this message. When I go to the bootloader and try to go to the recovery mode, I get the opened android with red sign saying "no command".
I read that I have to flash the latest SuperSU......any ideas how I am supposed to do that?
Click to expand...
Click to collapse
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
iburtondroid said:
you can use nexus root toolkit to unlock bootloader and flash supersu:
Click to expand...
Click to collapse
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed

lichti1901 said:
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed
Click to expand...
Click to collapse
agree, I have just proposed him, if he is not sure what he was doing wrong, also, correct me if I am wrong, but maybe he didn't enable developer options (not sure if this is a must for other steps he needs to take)

Developer Options are only applicable when Android is booted, has no bearing on things when in fastboot. They also have no bearing on root.
If the OP doesn't know what they're doing then they should read up on everything and LEARN the adb/fastoot commands. It takes all of 10 minutes reading to know the basics and will hold you in good stead for future Android handsets

PhilipTD said:
You're so damn civilized across the pond.
Click to expand...
Click to collapse
Well I couldn't say shoot up and rob a granny now could I?
</poor taste>

rootSU said:
Well I couldn't say shoot up and rob a granny now could I?
</poor taste>
Click to expand...
Click to collapse
LMAO

lichti1901 said:
We have to know all the setps you´ve done to get root.
1. download SuperSU.zip to your sdcard
2. Unlock bootloader - reboot afterwards done?
3. download a recovery.img, CWM or TWRP
4. Back to bootloader and flash recovery: fastboot flash recovery nameofrecovery.img
5. in bootloader boot now to recovery and select install/SuperSU.zip
6. Reboot and and you are ready to go
All-in-One-Thread here is a link which should help you to get started :good:
Pls report back if you get it sorted :highfive:
---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------
Sure, roottoolkit works, but you dont learn something with using toolkits. You dont know what they are doing.
There are easy fastboot commands
fastboot oem unlock
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
........
so nothing special, no toolkits needed
Click to expand...
Click to collapse
mysd card? I thought all I needed is the usb...
I was in class much of yesterday and of today so forgive me for the update.
Downloading the SDK and just downloaded the twrp recovery.img.

TCWadey said:
You can also download the app "Goo Manager", in the settings menu there is an option to install the latest TWRP recovery. ☺
Sent from my Nexus 5
Click to expand...
Click to collapse
you can, but you need root for it to work. the name of this thread is.. "Nexus 5 "No SU binary installed and SuperSU? cannot Install it".

@PhilipTD @rootSU, Sorry to bump this thread, but I had to lol :laugh::laugh::laugh: