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

[Q] boot loop cannot get PC to read device

Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?

sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?

sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:

tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?

sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.

tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks

sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard

tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere

sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.

tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111

sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img

tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip

sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.

Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory:

[Q] Reboots no recovery only fastboot

I have a one xl that will reboot after being on for 2 minutes
evita pvt ship s-on rl
hboot-1.14.0002
it is unlocked, but i cant relock it. Every time i try it says fails then reboots. I have also tried flashing twrp and cwm recovery via fastboot, but everytime i try to enter one it hangs on the teamwin screen. I have tried the ruu it reads my phone at first then when it says rebooting to bootloader the phone reboots normaly and get error 107.
Any help would be greatly appreciated.

What method are you using to try to relock the phone? What method are you using to install the mentioned recoveries? Please give as much detailed information as possible.
Sent from my Evita.

To relock i have used fastboot in cmd and typed fastboot oem lock. I have done that 10 times with the same result phone reboots normally and when i reboot back into bootloader it still says unlocked.
To flash recoveries i have used fastboot flash recovery ********.img
fastboot erase cache
fastboot reboot-bootloader
but instead of rebooting to the bootloader it boots normally

What did you do to the phone before all this started happening? Phones don't usually just start doing things like this of their own accord.
Sent from my Evita.

I bought it like this. The last owner said it happend after he installed a rom. I was hopping i could unbrick it with out jtagging it becuase i am still able to fastboot to it.

If you can't get an RUU to work I think jtag might be your only option.
Sent from my Evita.

I've only tried 2.20. I even extracted the system IMG from it but fast boot says it is too large. The only reason ruu won't work is because I can't get my phone to reboot into boot loader. Is there any way I can flash a different boot loader through fast boot.

Just curious, but when you type fastboot devices from the Bootloader, what is the output?
Are you running fastboot oem lock from the bootloader?
Sent from my One X using XDA Premium 4 mobile app

Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices

keithman2567 said:
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
Click to expand...
Click to collapse
If when you type fastboot devices (while in the boot loader) in your computers command prompt, and it doesn't show your HTC device being attached, that means that your computer is not recognizing your phone. Have you installed the HTC drivers? Do you have the newest versions of fastboot and adb installed?
What OS are you running on your computer?
Sent from my One X using XDA Premium 4 mobile app

I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.

keithman2567 said:
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
Click to expand...
Click to collapse
Does your device boot into the ROM at all?
Sent from my One X using XDA Premium 4 mobile app

Yes. But only for 2 mins before it reboots.

keithman2567 said:
Yes. But only for 2 mins before it reboots.
Click to expand...
Click to collapse
If you can connect to Google Play store, download recovery tools, if you have time. From there you could try to install a new recovery for your device. With only 2 minutes you will have to be quick though.
Do you have access to your sdcard from your computer?
Sent from my One X using XDA Premium 4 mobile app

I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.

keithman2567 said:
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
Click to expand...
Click to collapse
Here is the app. Not sure if you'll have time, but you can try
https://www.dropbox.com/s/wa4u565woyrrrlw/de.mkrtchyan.recoverytools-2.apk
Sent from my One X using XDA Premium 4 mobile app

Thank you, but there isn't enough time to even transfer it over

keithman2567 said:
Thank you, but there isn't enough time to even transfer it over
Click to expand...
Click to collapse
Do you have USB debugging enabled in the phone?
Sent from my One X using XDA Premium 4 mobile app
---------- Post added at 10:22 PM ---------- Previous post was at 10:15 PM ----------
Have you tried to flash a new ROM from fastboot? It sounds like your recovery partition might have been corrupted.
Sent from my One X using XDA Premium 4 mobile app

I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.

keithman2567 said:
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
Click to expand...
Click to collapse
Alright, so I have a few ideas.
1. Try flashing a new rom via fastboot. (the following is based on the assumption that you have adb and fastboot in your path)
Flashing a ROM through Fastboot
So Why Do I Need To Do This?
You don't, normally you would flash a ROM through recovery, but why not have another way? Maybe your recovery partition on your phone is corrupt?
Maybe you just want to say "I learned something new!" whatever your reason here are the simple steps:
To start:
Quote:
Quote:
We need to download the ROM of choice to your computer. Once complete find the folder that rom is in and open terminal/cmd to that directory
(quickest way for windows; just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
2. Boot into Recovery via fastboot.
Plug phone into PC, connect with USB cable and have phone in fastboot mode, now open CMD/Terminal in the same directory as your recovery image
Code:
fastboot boot recovery.img
Of course name image correctly to fit command or vise versa
Now you are in recovery of choice within your device without it being flashed to your recovery partition. There is a time and a place for everything, can you think of ways this may help you? Sure you can!
This doesn't actually flash the recovery.img... it will just allow you to boot into it. Make sure that you have a good TWRP version.
The previous quotes were taken from this guide on XDA-University:
http://forum.xda-developers.com/showthread.php?t=2277112

[Q] htc one sv soft bricked :/

Hi everybody !
I think i'm in the right section to expose you my problem, and no one on this forum had been confronted to such fails ! but i'm new in this forum to write threads (altough i already read many of them)
i'll try to be quick :
a year ago i bought a htc one sv , i unlocked the bootloader and then i stopped because i was with windows 8 and it was boring with usb 3.0 (i can use windows 7 right now..!). then i got some problems with "android.phone", or android.process.media" stopped et i believed my phone dead, but i learned things, installed the TWRP recovery 2.7.0.1 and flashed therom stock odexed jelly bean which allowed me to get back to stock my phone! (the twrp was with the root (or the rom odexed...) so i became rooted! but when i updates the superuser app few months ago, i got problems of binaries so i didn't install the last supersu app update (2/3 weeks ago). unfortunately,2 weeks ago, my phone did a reboot in the night (which awoke me) but in a bootloop...
First i tried factory reset then clean storage du bootloader, but it did nothing.
at the beginning i could not acceed to the recovery, but, lucky i am, a boot in fastboot usb and now from the phone, i can go to my recovery twrp 2.7.0.1 -or 2.8.4.0 by boot fastboot usb) however, TWRP shows "no os installed"it s been 2 weeks that i'm searching, but without results... that's why i'm asking here to the best in android world ^^
the things that i already tried without results:
flash the same zip odexed from recovery and from fastboot usb
flash hboot, but i'm s-on
update recovery ( i only can boot by fastboot usb)
flash rom custom venom with the installer in the rom
find files for sdcard "pl80diag.zip et nbh et pl80img.zip et nbh"
but i'm S-on and can't be S-off, the process with moonshine stopp when the devices has to boot...
i also tried adb sideload and simple adb with the phone in recovery recovery but:
recovery is unable to mount internal storage partitions (unable to mount int-sd, etc............)
my phone shows "tampered" "unlocked" and "s-on" hboot "2.00.000".. ask for more...
from now on, when i boot the phne i don't have any more bootloop, i'm directly in the hboot..!
i tried extract rom.zip from RUU.exe of ICS but i didn't used it...
so i'm wondering if there is a way to unbrick this soft bricked devices 'casue i already tried all of the unbrick things for soft brick but the partitions being unable to mount killed all my tries... i hope i gave you many informations ! all the suggestions and ideas are welcome!
(i can't find nbh files..)
thanks for reading this busy text, i'm a bit bored of using a very old phone in remplacement if i can repair my lover htc..!
i trust you people i'll check and answer suggestions asap!

Well, you are S-on, there is not much you can do.
Flash twrp recovery 2.7.x or 2.8.x and try to flash a rom for your device model.
Don't forget to do a full wipe in twrp and to flash the boot.img of the rom you are using with fastboot.

old.splatterhand said:
Well, you are S-on, there is not much you can do.
Flash twrp recovery 2.7.x or 2.8.x and try to flash a rom for your device model.
Don't forget to do a full wipe in twrp and to flash the boot.img of the rom you are using with fastboot.
Click to expand...
Click to collapse
it that i was thinking... i already try this (i have already twrp without booting in fastboot or flashing) but the fact is : twrp cannot mount any partitions so the step "writing" is impossible.. even the wipe fails..

If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?

old.splatterhand said:
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
Click to expand...
Click to collapse
yep you're right i'v already try it on every partitions but i'll do it again !
i've got the K2_UL (i'm french) and it was on 4.2.2 JB.
by the way, thanks for your answers

guess who's back
old.splatterhand said:
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
Click to expand...
Click to collapse
hey guys, it's been a while but i was searching during all this time. I've experienced some things with adb shell and what i saw :
my partitions are messed up, not annihilated, but messed up. 2 reasons : partitions can't be mounted in the last recovery of TWRP, and when i use Fdisk -l /dev/block/mmcblk0 and the partition table of mmcblk0 and what I see is that my partitions table are not in disk order. My partitions are overlapping.. Perhaps it will help. I tried some ext2fd and mkfs.ext4 but it as not worked properly... maybe you have ideas... because it's been about months that my phone is useless and a paperweight.
by the way on my computer under windows 10, my phone used to be in qhsus_dload..! perhaps there are issues with that!
Thanks.

colton49 said:
hey guys, it's been a while but i was searching during all this time. I've experienced some things with adb shell and what i saw :
my partitions are messed up, not annihilated, but messed up. 2 reasons : partitions can't be mounted in the last recovery of TWRP, and when i use Fdisk -l /dev/block/mmcblk0 and the partition table of mmcblk0 and what I see is that my partitions table are not in disk order. My partitions are overlapping.. Perhaps it will help. I tried some ext2fd and mkfs.ext4 but it as not worked properly... maybe you have ideas... because it's been about months that my phone is useless and a paperweight.
by the way on my computer under windows 10, my phone used to be in qhsus_dload..! perhaps there are issues with that!
Thanks.
Click to expand...
Click to collapse
Which K2 variant do you have?
Sent from my C525c using Tapatalk

SHM said:
Which K2 variant do you have?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
K2_UL, but I am at a point that each try worths it.. even with other K2!
moreover I've got a full stock backup of K2_UL but it didn't work with TWRP when I tried
. from now on i have no more ideas.. ^^

colton49 said:
K2_UL, but I am at a point that each try worths it.. even with other K2!
moreover I've got a full stock backup of K2_UL but it didn't work with TWRP when I tried
. from now on i have no more ideas.. ^^
Click to expand...
Click to collapse
You need an RUU to fix you up.
http://androidruu.com/getdownload.p...0.14_2_10.49.40.11L_release_301902_signed.exe
Sent from my C525c using Tapatalk

SHM said:
You need an RUU to fix you up.
http://androidruu.com/getdownload.p...0.14_2_10.49.40.11L_release_301902_signed.exe
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
ha
I've already tried but when it as to be detected, nothing occured, but i'll try again.. do you think that could be restore my phone ( ave you read my first explanation message,)

colton49 said:
ha
I've already tried but when it as to be detected, nothing occured, but i'll try again.. do you think that could be restore my phone ( ave you read my first explanation message,)
Click to expand...
Click to collapse
Well if you can extract the RUU from the .exe program then you can boot to your hboot then select fastboot from the screen. Plug device to your pc then enter:
Confirm pc reads phone and displays serial number before proceeding...
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU.zip
If terminal shows it has completed successfully then reboot:
Code:
fastboot reboot
If terminal shows it didn't complete successfully then do not reboot but try again:
Code:
fastboot flash zip RUU.zip
I went through this last weekend for my K2CL because I was converting my device to f2fs and messed up in the process.
Sent from my C525c using Tapatalk

SHM said:
Well if you can extract the RUU from the .exe program then you can boot to your hboot then select fastboot from the screen. Plug device to your pc then enter:
Confirm pc reads phone and displays serial number before proceeding...
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU.zip
If terminal shows it has completed successfully then reboot:
Code:
fastboot reboot
If terminal shows it didn't complete successfully then do not reboot but try again:
Code:
fastboot flash zip RUU.zip
I went through this last weekend for my K2CL because I was converting my device to f2fs and messed up in the process.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
OK well i'll use my computer under windows 7, but i know that when i extract the ruu from the .exe (using the folder temp, you know) the file can't be flash with recovery but i'll give a try with fastboot (fastboot devices always work) if this can work you'll be my heroe haha because i've tried so many things with the adb shell the recoveries, the flash with fastboot (which taught me some things about android) but nothing worked!

colton49 said:
OK well i'll use my computer under windows 7, but i know that when i extract the ruu from the .exe (using the folder temp, you know) the file can't be flash with recovery but i'll give a try with fastboot (fastboot devices always work) if this can work you'll be my heroe haha because i've tried so many things with the adb shell the recoveries, the flash with fastboot (which taught me some things about android) but nothing worked!
Click to expand...
Click to collapse
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk

SHM said:
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
okay thanks i'm gonna try this again and again if it does not work at the first shot! yes i'm S-ON and Unlocked.. ! okay you give me hope !!
i'll tell you if i succeed

SHM said:
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
to decrypt the RUU You use smthing on Ubuntu right ? or you tried something else because i guess it's better when decrypted

colton49 said:
to decrypt the RUU You use smthing on Ubuntu right ? or you tried something else because i guess it's better when decrypted
Click to expand...
Click to collapse
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk

SHM said:
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
ok i'll try with the encrypted and if it doesn't work after many tries i'll try to decrypt it! i'm gonna try all of this right now ! just have to remember where extract the ruu

SHM said:
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I've got a huge pb, it seems that i can't relock my bootloader and well i'm s-on...
because fastboot oem lockfail
even htc bootloader unlock fails when i put the phone in a recovery to be recognized.. ****.. but if i can lock it it'll work..

colton49 said:
I've got a huge pb, it seems that i can't relock my bootloader and well i'm s-on...
because fastboot oem lockfail
even htc bootloader unlock fails when i put the phone in a recovery to be recognized.. ****.. but if i can lock it it'll work..
Click to expand...
Click to collapse
What do you mean by putting the phone in "recovery"? You shouldn't be in your recovery when using fastboot. You should be in your bootloader. Power off device, then press and hold the volume down key and the power key. Release when you see your hboot appear. Using your volume keys to move up and down you want to highlight the option, fastboot. Hit the power button to select fastboot. You are now in fastboot mode. You will see fastboot in red text. Plug your device into your pc and you should now see, fastboot usb, in red text. Using the terminal on your pc proceed to lock your bootloader using fastboot. Then proceed with my instructions in the other post.
Sent from my C525c using Tapatalk

SHM said:
What do you mean by putting the phone in "recovery"? You shouldn't be in your recovery when using fastboot. You should be in your bootloader. Power off device, then press and hold the volume down key and the power key. Release when you see your hboot appear. Using your volume keys to move up and down you want to highlight the option, fastboot. Hit the power button to select fastboot. You are now in fastboot mode. You will see fastboot in red text. Plug your device into your pc and you should now see, fastboot usb, in red text. Using the terminal on your pc proceed to lock your bootloader using fastboot. Then proceed with my instructions in the other post.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yeah of course i did it. Being in the recovery was just a try with a toolkit which is used to relock.
i know how fastboot works but i've got error messages with fastboot oem lock and by flashing the ruu the last thing after the signature checking fails because of my bootloader unlocked i guess.