Database Develop

[Q] RUU failed, stuck in RUU Boot, cannot boot recovery

Hi all,
Forgive me if there's a better thread, but I've searched Google and this forum quite deeply but I'm unable to find a method that works to get my phone unbricked.
So I had my (UK, Orange HTC_001) One rooted for a while but I'd like to go back to stock so I can get the latest OTA and troubleshoot some app issues.
No problem I thought, I've done this on other phones. However the RUU failed and now my device constantly boots to the 4 triangles, and everything I try to get it back is failing. I'd really appreciate some help please!
Here's what I've tried:
* fastboot reboot-bootloader ---> launches back to 4 triangles.
* fastboot flash recovery recoverystock.img (recovery downloaded from link in this guide: http://forum.xda-developers.com/showthread.php?t=2281365) ---> Fails to get further than "sending recovery (9562 KB)". Waited at least 10 mins
* unlocked my bootloader using the token from HTC ---> Showed successful but makes no difference.
* fastboot flash zip Guru.zip (recommended Guru_Reset_M7_2.24.401.1.zip for HTC_001 downloaded from http://www.htc1guru.com/2013/09/gurureset-downloads/) ---> Also sits on sending zip, much like trying to flash recovery.
Here's the output from my getvar all:
C:\Utilities\HTCToolkit\One_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33VW904671
(bootloader) imei: 354436050521812
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.095s
Please can I have some advice? I'm getting a little worried at this point!

if you are S-OFF then you can fix it. you can type fastboot oem boot to get phone booted. let me know if you can do that.

igagnidz said:
if you are S-OFF then you can fix it. you can type fastboot oem boot to get phone booted. let me know if you can do that.
Click to expand...
Click to collapse
Brilliant, a different screen at least! It's on the green HTC logo now, but seems to be hung after a couple of minutes sitting like that...I assume because the stock ROM is corrupted due to having failed when loading on RUU.
Do you think it's safe to flash zip now? If so, do you have a recommendation of which exact file?
Thanks!

rhys_himself said:
Brilliant, a different screen at least! It's on the green HTC logo now, but seems to be hung after a couple of minutes sitting like that...I assume because the stock ROM is corrupted due to having failed when loading on RUU.
Do you think it's safe to flash zip now? If so, do you have a recommendation of which exact file?
Thanks!
Click to expand...
Click to collapse
hmm. I was expecting an OS to actually boot. If it didnt boot then you should flash RUU zip again (hopefully one that works):
1) fastboot oem rebootRUU
2) fastboot flash zip RUU_ZIP_FILENAME
3) if on phone it says to flash it again, something like: remote 90 please flash again immediately then repeat step 2 again.
4) you should get htc green progress bar during flash on phone and once its done run fastboot reboot. if you get int ruu boot again then use fastboot oem boot to boot to android.

igagnidz said:
hmm. I was expecting an OS to actually boot. If it didnt boot then you should flash RUU zip again (hopefully one that works):
1) fastboot oem rebootRUU
2) fastboot flash zip RUU_ZIP_FILENAME
3) if on phone it says to flash it again, something like: remote 90 please flash again immediately then repeat step 2 again.
4) you should get htc green progress bar during flash on phone and once its done run fastboot reboot. if you get int ruu boot again then use fastboot oem boot to boot to android.
Click to expand...
Click to collapse
OK after a second go rebooting and attempting to boot OEM it has worked! Thanks my friend.
I think the RUU stock ROM has actually applied as well, which is a nice bonus. Now I'll just see if the OTA update applies. Fingers crossed.
Thanks again buddy.

rhys_himself said:
OK after a second go rebooting and attempting to boot OEM it has worked! Thanks my friend.
I think the RUU stock ROM has actually applied as well, which is a nice bonus. Now I'll just see if the OTA update applies. Fingers crossed.
Thanks again buddy.
Click to expand...
Click to collapse
Actually upon applying update the phone hun on the 4 triangles again.
Is my bootloader borked? If so, how on earth do I fix that!

Can you boot into the bootloader? If so, just boot to that, connect to the PC and then run the 1.28.401.7 RUU. You don't have to piss about with fastboot reboot oemRUU and all that jazz as the RUU deals with it all

EddyOS said:
Can you boot into the bootloader? If so, just boot to that, connect to the PC and then run the 1.28.401.7 RUU. You don't have to piss about with fastboot reboot oemRUU and all that jazz as the RUU deals with it all
Click to expand...
Click to collapse
except that wont solve his problem.
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
rhys_himself said:
Actually upon applying update the phone hun on the 4 triangles again.
Is my bootloader borked? If so, how on earth do I fix that!
Click to expand...
Click to collapse
Are you S-OFF?
Are you rooted?
Are you unlocked?
We need to modify partition 19 to unset force_ruu flag so you dont get into booloader all the time. u need root at least to do it (maybe unlock or s-off too)

igagnidz said:
except that wont solve his problem.
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
Are you S-OFF?
Are you rooted?
Are you unlocked?
We need to modify partition 19 to unset force_ruu flag so you dont get into booloader all the time. u need root at least to do it (maybe unlock or s-off too)
Click to expand...
Click to collapse
Yeah I have root still, luckily. I think I'm also unlocked (what's the easiest way to test? Usually I just check on bootloader screen) but I'm pretty sure I'm not S-off.
Modify partition 19? New territory for me, do show me the way sir!

rhys_himself said:
Yeah I have root still, luckily. I think I'm also unlocked (what's the easiest way to test? Usually I just check on bootloader screen) but I'm pretty sure I'm not S-off.
Modify partition 19? New territory for me, do show me the way sir!
Click to expand...
Click to collapse
So we first need to read your p19 and then hexedit the file.
To read the file (dont use quotes for commands - im using them to show what is the actual command you type):
1) get to adb shell as root - run "adb shell" in terminal while connected and having dev options enabled on the phone. run "su" to obtain root privileges inside adb shell.
2) copy p19 to your sdcard: "dd if=/dev/block/mmcblk0p19 of=/sdcard/p19.orig"
exit adb shell and copy that file from your simcard using "adb pull /sdcard/p19.orig".
if you can attach that file to your reply i can edit for you, or at least tell you what you need to remove from there. that partition does not hold any sensitive data (like imei or serial number) so it should be ok to upload here... Use hex editor and verify just in case - its been some time since i was there last time.

igagnidz said:
except that wont solve his problem
Click to expand...
Click to collapse
OP says their mainversion is 1.28.401.7 and the CID is HTC__001 so the 1.28.401.7 RUU will solve the issue once you can get it running properly

igagnidz said:
So we first need to read your p19 and then hexedit the file.
To read the file (dont use quotes for commands - im using them to show what is the actual command you type):
1) get to adb shell as root - run "adb shell" in terminal while connected and having dev options enabled on the phone. run "su" to obtain root privileges inside adb shell.
2) copy p19 to your sdcard: "dd if=/dev/block/mmcblk0p19 of=/sdcard/p19.orig"
exit adb shell and copy that file from your simcard using "adb pull /sdcard/p19.orig".
if you can attach that file to your reply i can edit for you, or at least tell you what you need to remove from there. that partition does not hold any sensitive data (like imei or serial number) so it should be ok to upload here... Use hex editor and verify just in case - its been some time since i was there last time.
Click to expand...
Click to collapse
No problem, that's done. Hex does indeed contain nothing sensitive that I can see.
I've renamed it .rar so that the filetype is accepted and with a maximum limit large enough to allow the file.
Thanks for your time on this

EddyOS said:
OP says their mainversion is 1.28.401.7 and the CID is HTC__001 so the 1.28.401.7 RUU will solve the issue once you can get it running properly
Click to expand...
Click to collapse
That's what I'm hoping! The RUU I have is meant to come with an "aroma installer", which I haven't used before...only .zip and RUU .exe files. There are no instructions on how to load it, but the file is a .zip so I just want to make sure it's right to use with the "fastboot flash zip" method?
The contents are as in the screenshot attached, to save downloading the gig file. If you need shots of the subfolders then that's no problem. Can anyone advise if this is correct please? I can't seem to get hold of a stock Nandroid .ZIP so if it looks odd then I would really appreciate a link to a known working one? Most of the sites are either down or the download seems too small or corrupt Thanks in advance!

Ah right! I've not used one of them before, just the official .EXE ones which are all self contained but you'd need to get into the proper fastboot mode first to be able to run it

EddyOS said:
OP says their mainversion is 1.28.401.7 and the CID is HTC__001 so the 1.28.401.7 RUU will solve the issue once you can get it running properly
Click to expand...
Click to collapse
no. RUU will not reset p19 partition. been there, done that.

rhys_himself said:
No problem, that's done. Hex does indeed contain nothing sensitive that I can see.
I've renamed it .rar so that the filetype is accepted and with a maximum limit large enough to allow the file.
Thanks for your time on this
Click to expand...
Click to collapse
I have attached modified p19. It is not rar-ed. You can compare to your original. I removed RUU flag (replace it with 00 in hex - you cant just delete it).
you need to dd it back to partition 19. steps:
1) boot your phone into android, connect to pc in dev mode
2) copy file to your phone: "adb push p19-mod.rar /sdcard/p19.mod" (make sure you are pointing to correct file with correct path - this example assumed file was in same directory that you are running adb commands from)
3) get into adb shell as root: "adb shell" and then inside shell "su"
4) copy modified parition: "dd if=/sdcard/p19.mod of=/dev/block/mmcblk0p19"
5) reboot your phone and profit.

igagnidz said:
I have attached modified p19. It is not rar-ed. You can compare to your original. I removed RUU flag (replace it with 00 in hex - you cant just delete it).
you need to dd it back to partition 19. steps:
1) boot your phone into android, connect to pc in dev mode
2) copy file to your phone: "adb push p19-mod.rar /sdcard/p19.mod" (make sure you are pointing to correct file with correct path - this example assumed file was in same directory that you are running adb commands from)
3) get into adb shell as root: "adb shell" and then inside shell "su"
4) copy modified parition: "dd if=/sdcard/p19.mod of=/dev/block/mmcblk0p19"
5) reboot your phone and profit.
Click to expand...
Click to collapse
lol. Profit.
OK so more progress, which is great. It no longer boots to 4 triangles and will auto-boot into OEM which is great. However I can't power + vol reboot into fastboot...it just does the 3 second countdown then sits on 1 and doesn't actually reboot.
I'd really like to continue to try and get a stock ROM on but to do this I'm going to need bootloader, right? Or do you think there's a method of flashing it that will restore that too?
Thanks again for your time! I'd buy you a beer but, well...internet.

rhys_himself said:
lol. Profit.
OK so more progress, which is great. It no longer boots to 4 triangles and will auto-boot into OEM which is great. However I can't power + vol reboot into fastboot...it just does the 3 second countdown then sits on 1 and doesn't actually reboot.
I'd really like to continue to try and get a stock ROM on but to do this I'm going to need bootloader, right? Or do you think there's a method of flashing it that will restore that too?
Thanks again for your time! I'd buy you a beer but, well...internet.
Click to expand...
Click to collapse
can you get into android OS? what is that countdown? Im little bit confused. can you send screens or more description.
P.S. As for beer, it all good - I dont drink

igagnidz said:
can you get into android OS? what is that countdown? Im little bit confused. can you send screens or more description.
P.S. As for beer, it all good - I dont drink
Click to expand...
Click to collapse
Yeah I can get into the OS now- it boots every time without prompt, thanks to your help. The countdown is when I hold power & vol down to prompt reboot..usually that will show a countdown of 3 seconds then reboot into bootloader. Now it just sticks on1 (until i release the keys, when phone just continues to run as normal) and doesn't reboot. Sorry I can't get a screenshot of this though, coz that'll use the same buttons as I have to press to prompt it.
OK no probs

rhys_himself said:
Yeah I can get into the OS now- it boots every time without prompt, thanks to your help. The countdown is when I hold power & vol down to prompt reboot..usually that will show a countdown of 3 seconds then reboot into bootloader. Now it just sticks on1 (until i release the keys, when phone just continues to run as normal) and doesn't reboot. Sorry I can't get a screenshot of this though, coz that'll use the same buttons as I have to press to prompt it.
OK no probs
Click to expand...
Click to collapse
can you boot to OS and then connect to pc in devmode and reboot using adb: "adb reboot bootloader"
that should get you to bootloader. if it doesnt work than you should downgrade/upgrade your bootloader since booloaders are supposed to be almost last resort for fixing things and not having it working properly is dangerous.

[Q] Bricked after flashing Insertcoin 4.4 ROM (ADB can't find device)

I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.

Caboose127 said:
I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.
Click to expand...
Click to collapse
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.

LibertyMarine said:
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.
Click to expand...
Click to collapse
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.

Caboose127 said:
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.
Click to expand...
Click to collapse
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
fastboot getvar all
Click to expand...
Click to collapse
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?

LibertyMarine said:
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?
Click to expand...
Click to collapse
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.

Caboose127 said:
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.
Click to expand...
Click to collapse
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe

have you tried re flashing a new recovery via fastboot?

LibertyMarine said:
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
Click to expand...
Click to collapse
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN

khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
I would flash a new recovery, but my computer doesn't seem to be recognizing my device. It does for a second during boot into recovery, but once the recovery crashes and the phone resets, the phone disappears from device manager. It doesn't show backup when I'm in FASTBOOT USB.
I'm going to try it on a coworkers computer.

Caboose127 said:
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
this is weird... try another computer. Try different drivers from here:
http://forum.xda-developers.com/showthread.php?t=2191279
TRY EVERYTHING GO GET THE COMPUTER RECOGNIZING YOUR HTC ONE
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
...lol this would be funny.. maybe his recovery partition is corrupt.. hmmm then we'd have to use different error handling strategies...

Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****************
(bootloader) imei: *****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.

If you are still trying for your computer to recognize the adb device and still hasn't then just buy an USB OTG then put an USB to flash a rom from there.
http://www.androidapps4u.com/temp/screenshot_3-usb-otg-cable.jpg

Define crashed? TWRP 2.6.3.0 ? or CWM ? What happens in recovery mode?

Caboose127 said:
Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.
Click to expand...
Click to collapse
adb commands won't work while in fastboot mode/bootloader. fastboot needs to be used while in fastboot mode. While your in fastboot, try
fastboot erase cache
Then fastboot flash your recovery again (fastboot flash recovery nameofrecovery.img), and try to access recovery

Thanks for all of your help guys. I finally got it working.

For everyone else reference, mark your thread [SOLVED] and post a brief description how you fixed it..

Thanks guys for helping me out!

HTC one M7

HTC says this...
*****TAMPERED****
*****Relocked******
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-
eMMc-boot 2048MB
Sept 10 2013, 01:32:23.0
I have tried the HBOOT - Factory reset - no luck
went into fastboot and tried to connect to it - no luck
tried to load the 2.7.img file and rebooted the bootloader and it come back to the same screen..
Can anyone assist in getting the OS put back on?

Wait a minute. Does your phone go to fastboot usb mode when you connect it to your comuter in bootloader mode?

donkeykong1 said:
Wait a minute. Does your phone go to fastboot usb mode when you connect it to your comuter in bootloader mode?
Click to expand...
Click to collapse
Yes... But I can move to HBOOT aslo.. No options work.. always goes to the bootloader screen with the ****tampered**** screen

You need to unlock your bootloader in order to flash custom recovery. You can do that via htcdev site

mehtarajiv1 said:
Yes... But I can move to HBOOT aslo.. No options work.. always goes to the bootloader screen with the ****tampered**** screen
Click to expand...
Click to collapse
donkeykong1 said:
You need to unlock your bootloader in order to flash custom recovery. You can do that via htcdev site
Click to expand...
Click to collapse
unfortunately. I cannot unlock the phone... I have tried using ADB and when I type ADB devices.. I get no devices, yet when I type "Fastboot Devices" it shows my phone..
I loaded the 2.7 xxx.img file from this site and erased cache and rebooted yet unable to get to the recovery menu.

mehtarajiv1 said:
unfortunately. I cannot unlock the phone... I have tried using ADB and when I type ADB devices.. I get no devices, yet when I type "Fastboot Devices" it shows my phone..
I loaded the 2.7 xxx.img file from this site and erased cache and rebooted yet unable to get to the recovery menu.
Click to expand...
Click to collapse
For adb to work yout phone needs to be booted to OS or custom recovery. Since you don't have either of those it won't work. Can you post fastboot getvar all? Just remove your IMEI and serial number.

Go here: htcdev.com/
Follow the steps there to unlock your phone.
You'll need to register a valid email as they will send you a .bin file. You don't need adb for this. Fastboot used.
After unlocking the device, download the stock recovery.img from tmobile (recovery_tmobile.img): dl.dropbox.com/u/50607529/recovery_tmobile.img
Save it to the same spot you have the fastboot.exe file
Then run the following command: fastboot flash recovery recovery_tmobile.img
Then issue a: fastboot reboot-bootloader
Go back into fastboot USB mode, and issue the: fastboot oem lock
Then issue a: fastboot reboot-bootloader
You will then be at the bootloader.
With the device still connected on your PC, switch to fastboot USB again (if not already), and run the RUU found online: htc.com/us/support/htc-one-t-mobile/news/
Do a google search for: HTC One for T-Mobile ROM Update 5.16.2014
Get the download that says "1.49GB". It's an .exe file you just run and it will wipe your phone. Considering the state it is in now, you probably won't mind that it'll wipe the entire phone clean.
This is off the top of my head, so hopefully those steps above are clear.
Any questions, reply to my post.

donkeykong1 said:
For adb to work yout phone needs to be booted to OS or custom recovery. Since you don't have either of those it won't work. Can you post fastboot getvar all? Just remove your IMEI and serial number.
Click to expand...
Click to collapse
C:\ADB>fastboot devices
HT35XW910369 fastboot
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.55.0000
INFOversion-baseband: 4T.20.3218.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 3752mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-2da61e5e88
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.050s
C:\ADB>

Sarting said:
Go here: htcdev.com/
Follow the steps there to unlock your phone.
You'll need to register a valid email as they will send you a .bin file. You don't need adb for this. Fastboot used.
After unlocking the device, download the stock recovery.img from tmobile (recovery_tmobile.img): dl.dropbox.com/u/50607529/recovery_tmobile.img
Save it to the same spot you have the fastboot.exe file
Then run the following command: fastboot flash recovery recovery_tmobile.img
Then issue a: fastboot reboot-bootloader
Go back into fastboot USB mode, and issue the: fastboot oem lock
Then issue a: fastboot reboot-bootloader
You will then be at the bootloader.
With the device still connected on your PC, switch to fastboot USB again (if not already), and run the RUU found online: htc.com/us/support/htc-one-t-mobile/news/
Do a google search for: HTC One for T-Mobile ROM Update 5.16.2014
Get the download that says "1.49GB". It's an .exe file you just run and it will wipe your phone. Considering the state it is in now, you probably won't mind that it'll wipe the entire phone clean.
This is off the top of my head, so hopefully those steps above are clear.
Any questions, reply to my post.
Click to expand...
Click to collapse
That is the problem. I cannot unlock the phone to get to the next step...

OK. You have two options - unlock bootloader and flash custom recovery and then adb sideload a ROM (easier in my oppinion) or run RUU. For RUU you need to match RUU .exe file with your CID and MID.
RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2
This RUU should work for you, but after you flash it you will still need to unlock your bootloader if you want custom recovery and/or custom ROM

donkeykong1 said:
OK. You have two options - unlock bootloader and flash custom recovery and then adb sideload a ROM (easier in my oppinion) or run RUU. For RUU you need to match RUU .exe file with your CID and MID.
RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2
This RUU should work for you, but after you flash it you will still need to unlock your bootloader if you want custom recovery and/or custom ROM
Click to expand...
Click to collapse
I tried the RUU option as well before I sent it to HTC.. Where do I get the RUU file you mentioned in this post?

mehtarajiv1 said:
I tried the RUU option as well before I sent it to HTC.. Where do I get the RUU file you mentioned in this post?
Click to expand...
Click to collapse
Sorry, I didn't post a link. Go to guru reset and download from there

donkeykong1 said:
OK. You have two options - unlock bootloader and flash custom recovery and then adb sideload a ROM (easier in my oppinion) or run RUU. For RUU you need to match RUU .exe file with your CID and MID.
RUU M7 UL K44 SENSE55 MR Cingular US 4.18.502.7 R10 Radio 4T.24.3218.09 10.26.1718.01L Release 356565 Signed 2
This RUU should work for you, but after you flash it you will still need to unlock your bootloader if you want custom recovery and/or custom ROM
Click to expand...
Click to collapse
Running the RUU method, it starts to upload the image to the phone and about 5% through it errors out with error[171] USB connection error. During this process the phone displays a black screen and says HTC in white letters.
The ADB sideloader option states - adb devices not found... Any other options?

Forget about adb for now, it won't work. That black screen is RUU mode and it's fine. Do you have another usb cable to try? Because that error suggests your cable is faulty

donkeykong1 said:
Forget about adb for now, it won't work. That black screen is RUU mode and it's fine. Do you have another usb cable to try? Because that error suggests your cable is faulty
Click to expand...
Click to collapse
I have tried with 3 different usb cables and it dies at the same spot... I think because S-ON is set, I cannot the OS.

Then there's option 2 - unlocking bootloader via htcdev

mehtarajiv1 said:
I have tried with 3 different usb cables and it dies at the same spot... I think because S-ON is set, I cannot the OS.
Click to expand...
Click to collapse
S-ON does not affect flashing with RUU or custom roms (rooted).
If you are having USB issues, please try plugging into a USB 2.0 port. There has been problems reported with using 3.0.
donkeykong1 said:
Then there's option 2 - unlocking bootloader via htcdev
Click to expand...
Click to collapse
+1
mehtarajiv1 said:
The ADB sideloader option states - adb devices not found... Any other options?
Click to expand...
Click to collapse
As stated previously, ADB will not work unless you're in 1.) the OS, or 2.) Recovery mode (TWRP or CWM etc)

mehtarajiv1 said:
Running the RUU method, it starts to upload the image to the phone and about 5% through it errors out with error[171] USB connection error. During this process the phone displays a black screen and says HTC in white letters.
The ADB sideloader option states - adb devices not found... Any other options?
Click to expand...
Click to collapse
sorry for butting in, but your issue, including the 171 usb issue sounds like drivers to me, are you using windows 7 or 8 ?
with your phone plugged into the computer, please check in device manager, under android devices it should say MyHTC, if it says anything else, that's your problem.
download HTC sync manager from the HTC site, install it, then goto add/remove programs and remove HTC sync, this will just leave the drivers behind on your computer, you don't want sync, it interferes, you will see HTC driver installer in add/remove programs just above sync.
---------- Post added at 09:21 PM ---------- Previous post was at 09:15 PM ----------
IT WONT BE your usb leads, ports or the port in the phone, so don't worry about that, its not a hardware fault, if it was then your fastboot getvar wouldn't of worked either.

Sarting said:
S-ON does not affect flashing with RUU or custom roms (rooted).
If you are having USB issues, please try plugging into a USB 2.0 port. There has been problems reported with using 3.0.
+1
As stated previously, ADB will not work unless you're in 1.) the OS, or 2.) Recovery mode (TWRP or CWM etc)
Click to expand...
Click to collapse
I was finally able to get into TWRP recovery mode....
I am on TWRP v2.6.3.0 .. where do I go next?

mehtarajiv1 said:
I was finally able to get into TWRP recovery mode....
I am on TWRP v2.6.3.0 .. where do I go next?
Click to expand...
Click to collapse
you need a working adb and also twrp 2.6.3.3 minimum to push, sideload or flash anything.

[Q] AT&T HTC One M7 soft-bricked. Fastboot works, can't boot to recovery [Concluded]

[Q] AT&T HTC One M7 soft-bricked. Fastboot works, can't boot to recovery [Concluded]
Wondering if I can get somebody to weigh in on this one. Trying to help a friend of a friend out--I don't know the back story of what happened to this, but sounded like a 'bricked his phone doing dangerous things without enough knowledge' kind of situation.
The phone is stuck in a boot loop, just the HTC wordmark on a white background. You can enter the bootloader just fine, and fastboot can read and send commands just fine, flash recovery just fine, etc. The device cannot, however, enter recovery mode. It just says "entering recovery..." at the top, with the same HTC wordmark and white background. It displays for 30 seconds, then the screen goes black for 4-5 seconds, then back to the HTC logo.
Some info about the phone:
AT&T HTC One M7
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: [redacted]
imei: [redacted]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3838mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Things I have tried already:
The first thing I did was I re-locked the bootloader and flashed the RUU exe, thinking that might be the quickest fix. The exe took the expected length of time and said it was successful, and rebooted the phone.
Still looping.
I then got the unlock token, unlocked the bootloader again, erased the cache, and fastboot flashed CWM recovery-clockwork-6.0.4.3-m7att.img - Attempted to reboot to recovery.
Still looping.
Cleared the cache, flashed openrecovery-twrp-2.7.1.1-m7.img - Attempted to reboot to recovery.
Still looping.
What's Next?
So that's about where I am now, I have functional bootloader and fastboot, but something is corrupted and I just absolutely can't get into recovery no matter what I try. I really thought the RUU would be a simple way to fix it, and was surprised when it didn't work.
From the reading I've done it sounds like there's some sort of emmc partition corruption possibly? Am I going in the right direction? I did post the fastboot getvar all results above--perhaps that can tip somebody off? I don't know quite enough to be able to spot trouble there at a glance, unfortunately.
I don't personally have a lot invested in getting this running, its owner already replaced it and I'm just doing it for the fun and challenge of the learning experience. But I may be out of my depth at this point, I've exhausted my barely-passable knowledge when it comes to this stuff.
Thanks for any comments or guidance you can provide!
Thanks to all for your help. I've come to believe the issues were hardware related, and have returned the phone.

matt314159 said:
Wondering if I can get somebody to weigh in on this one. Trying to help a friend of a friend out--I don't know the back story of what happened to this, but sounded like a 'bricked his phone doing dangerous things without enough knowledge' kind of situation.
The phone is stuck in a boot loop, just the HTC wordmark on a white background. You can enter the bootloader just fine, and fastboot can read and send commands just fine, flash recovery just fine, etc. The device cannot, however, enter recovery mode. It just says "entering recovery..." at the top, with the same HTC wordmark and white background. It displays for 30 seconds, then the screen goes black for 4-5 seconds, then back to the HTC logo.
Some info about the phone:
AT&T HTC One M7
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: [redacted]
imei: [redacted]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3838mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Things I have tried already:
The first thing I did was I re-locked the bootloader and flashed the RUU exe, thinking that might be the quickest fix. The exe took the expected length of time and said it was successful, and rebooted the phone.
Still looping.
I then got the unlock token, unlocked the bootloader again, erased the cache, and fastboot flashed CWM recovery-clockwork-6.0.4.3-m7att.img - Attempted to reboot to recovery.
Still looping.
Cleared the cache, flashed openrecovery-twrp-2.7.1.1-m7.img - Attempted to reboot to recovery.
Still looping.
What's Next?
So that's about where I am now, I have functional bootloader and fastboot, but something is corrupted and I just absolutely can't get into recovery no matter what I try. I really thought the RUU would be a simple way to fix it, and was surprised when it didn't work.
From the reading I've done it sounds like there's some sort of emmc partition corruption possibly? Am I going in the right direction? I did post the fastboot getvar all results above--perhaps that can tip somebody off? I don't know quite enough to be able to spot trouble there at a glance, unfortunately.
I don't personally have a lot invested in getting this running, its owner already replaced it and I'm just doing it for the fun and challenge of the learning experience. But I may be out of my depth at this point, I've exhausted my barely-passable knowledge when it comes to this stuff.
Thanks for any comments or guidance you can provide!
Click to expand...
Click to collapse
Try to download TWRP 2.6.3.3 from here http://techerrata.com/browse/twrp2/m7 . When it has downloaded put it in your fastboot folder, plug your phone into your computer, open a command window, and type "fastboot devices" to make sure it recognizes your phone. If it doesn't you will need the drivers, if it does recognize it type "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" . That is the same file and procedure I just used a week ago, hope it helps you.

chuckwago88 said:
Try to download TWRP 2.6.3.3 from here http://techerrata.com/browse/twrp2/m7 . When it has downloaded put it in your fastboot folder, plug your phone into your computer, open a command window, and type "fastboot devices" to make sure it recognizes your phone. If it doesn't you will need the drivers, if it does recognize it type "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" . That is the same file and procedure I just used a week ago, hope it helps you.
Click to expand...
Click to collapse
Thanks for the suggestion, but it's still no joy: TWRP 2.6.3.3 acts the same as TWRP 2.7.1.1 and CWM 6.0.4.3
I'm starting to think this thing is toast.

matt314159 said:
Thanks for the suggestion, but it's still no joy: TWRP 2.6.3.3 acts the same as TWRP 2.7.1.1 and CWM 6.0.4.3
I'm starting to think this thing is toast.
Click to expand...
Click to collapse
I noticed that you have 3.17.502.3 firmware, you might try to flash this RUU 4.18.502.7 it is a higher version and might correct what I suspect is a mismatch between your version and the hboot. If this is successful, you might think about this AT&T 5.12.502.2 Guru Reset. Read the entire OP for both, it might give you some insight.

Hmm... With this RUU, I get as far as "Updating 1/5 Checking headers" at 5% and never any further. Thought I might just need to be more patient, so I left it through three episodes of Trailer Park Boys season 8, and a subsequent afternoon nap before powering off the handset and killing the windows process. Tried it again and it seems to be doing the same thing. The MD5 matched so I don't think it was a bad download, so I wonder if there are any workarounds.
I'm running windows 7 x64, have the proper drivers installed, HTC Sync has been removed, and I've used this PC successfully on another HTC One when I needed to get it back to factory stock to send in for warranty work just a couple of weeks ago. So I'm pretty sure it's nothing to do with my setup...

Can you find the same firmware (or extract from ota) and flash it?

matt314159 said:
Hmm... With this RUU, I get as far as "Updating 1/5 Checking headers" at 5% and never any further. Thought I might just need to be more patient, so I left it through three episodes of Trailer Park Boys season 8, and a subsequent afternoon nap before powering off the handset and killing the windows process. Tried it again and it seems to be doing the same thing. The MD5 matched so I don't think it was a bad download, so I wonder if there are any workarounds.
I'm running windows 7 x64, have the proper drivers installed, HTC Sync has been removed, and I've used this PC successfully on another HTC One when I needed to get it back to factory stock to send in for warranty work just a couple of weeks ago. So I'm pretty sure it's nothing to do with my setup...
Click to expand...
Click to collapse
Those 4.xx.502 RUU are crap...
Are you sure the 3.x.502 RUU completed ? I have never seen a phone bootloop after flashing that RUU.

clsA said:
Are you sure the 3.x.502 RUU completed ? I have never seen a phone bootloop after flashing that RUU.
Click to expand...
Click to collapse
Fairly sure, anyway? It takes the expected length of time (about 10 minutes), the progress bars march through their steps on the computer screen and phone screen, and the RUU exe congratulates me and says it's going to reboot the phone now when it's finished.
Can I try fastboot flashing a zip RUU, or does it require S-Off for that?

matt314159 said:
Fairly sure, anyway? It takes the expected length of time (about 10 minutes), the progress bars march through their steps on the computer screen and phone screen, and the RUU exe congratulates me and says it's going to reboot the phone now when it's finished.
Can I try fastboot flashing a zip RUU, or does it require S-Off for that?
Click to expand...
Click to collapse
it's no different ..if the EXE RUU worked and your still in bootloop you have a corrupt partition and will need expert advice. Maybe @nkk71 will have some time to help you

clsA said:
it's no different ..if the EXE RUU worked and your still in bootloop you have a corrupt partition and will need expert advice. Maybe @nkk71 will have some time to help you
Click to expand...
Click to collapse
Okay, thanks. I'm going to be taking this back to my colleague at work tomorrow, so I probably don't want nkk71 to spend much time on it unless he thinks it's something quick I can do tonight to get it running again.
Just on a lark, I also flashed twrp-recovery-2.7-m7-nobcb.img from This thread.--no change. Although my symptoms were different, it sounded like it might be worth a shot, but no dice.

matt314159 said:
Okay, thanks. I'm going to be taking this back to my colleague at work tomorrow, so I probably don't want nkk71 to spend much time on it unless he thinks it's something quick I can do tonight to get it running again.
Just on a lark, I also flashed twrp-recovery-2.7-m7-nobcb.img from This thread.--no change. Although my symptoms were different, it sounded like it might be worth a shot, but no dice.
Click to expand...
Click to collapse
@clsA is quite right about those 4.xx RUUs, they do work, but are very sensitive (for lack of a better word), about PC configuration, USB ports, etc... no clue what is the defining problem.
though all this sounds strange indeed, usually when the emmc is fried, "fastboot oem rebootRUU" will throw an error.
can you extract the ROM.ZIP from the 3.17.502.3 RUU.EXE and try flashing it using fastboot commands:
run the RUU.EXE, once you're at the welcome screen, it would have extracted all the files into %TEMP%/<weird long numbered folder name> (use sort by date modified to find the newest folders), in it you should find a 1.5GB or so ROM.ZIP <- that's an encrypted/signed ruu.zip) copy it to your fastboot folder, exit the RUU.EXE, and flash the ROM.ZIP (it will give a lot more output):
relock bootloader (since you are S-On):
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice, the first one only does the hboot preupdate
fastboot reboot-bootloader
and copy/paste the command prompt output here, make sure to set the command prompt buffer size to a large enough size (at least 500+ lines)
obviously, if we had some background as to what happened previously, it would/could help too

nkk71 said:
@clsA is quite right about those 4.xx RUUs, they do work, but are very sensitive (for lack of a better word), about PC configuration, USB ports, etc... no clue what is the defining problem.
though all this sounds strange indeed, usually when the emmc is fried, "fastboot oem rebootRUU" will throw an error.
can you extract the ROM.ZIP from the 3.17.502.3 RUU.EXE and try flashing it using fastboot commands:
run the RUU.EXE, once you're at the welcome screen, it would have extracted all the files into %TEMP%/<weird long numbered folder name> (use sort by date modified to find the newest folders), in it you should find a 1.5GB or so ROM.ZIP <- that's an encrypted/signed ruu.zip) copy it to your fastboot folder, exit the RUU.EXE, and flash the ROM.ZIP (it will give a lot more output):
relock bootloader (since you are S-On):
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice, the first one only does the hboot preupdate
fastboot reboot-bootloader
and copy/paste the command prompt output here, make sure to set the command prompt buffer size to a large enough size (at least 500+ lines)
obviously, if we had some background as to what happened previously, it would/could help too
Click to expand...
Click to collapse
Thank you for the clear instructions. I followed them over my lunch hour. My only problem was getting the command prompt buffer to stick, I changed it to 999 but it kept truncating the output anyhow. So I ran the commands a second time and snagged the output a few times throughout the process and cobbled it back together.
Here's the output at pastebin: http://pastebin.com/dNKaKKtd (note that it does not show the lock command as this was the second iteration that I captured)
presently, the phone is still looping.
I still have the phone for another night, so I'll keep going with this if you have more suggestions or instructions.
Many Thanks!

matt314159 said:
Thank you for the clear instructions. I followed them over my lunch hour. My only problem was getting the command prompt buffer to stick, I changed it to 999 but it kept truncating the output anyhow. So I ran the commands a second time and snagged the output a few times throughout the process and cobbled it back together.
Here's the output at pastebin: http://pastebin.com/dNKaKKtd (note that it does not show the lock command as this was the second iteration that I captured)
presently, the phone is still looping.
I still have the phone for another night, so I'll keep going with this if you have more suggestions or instructions.
Many Thanks!
Click to expand...
Click to collapse
Well that output looks just fine, the ruu is successfully flashed, and has put everything back to stock. So unfortunately i can't really think of anything else, my only two guesses would be:
1- hardware problem
2- if he did flash something into p19 (the active cmdline overflow error), then maybe try the older cwm 6.0.2.8 recovery which seems to sometimes work for s-on users
you should first try to find out from your friend if this was the result of him flashing something, or if it happened by itself (in the latter case, it would be a hardware problem for sure)

nkk71 said:
Well that output looks just fine, the ruu is successfully flashed, and has put everything back to stock. So unfortunately i can't really think of anything else, my only two guesses would be:
1- hardware problem
2- if he did flash something into p19 (the active cmdline overflow error), then maybe try the older cwm 6.0.2.8 recovery which seems to sometimes work for s-on users
you should first try to find out from your friend if this was the result of him flashing something, or if it happened by itself (in the latter case, it would be a hardware problem for sure)
Click to expand...
Click to collapse
Thanks so much for your help! Nothing ended up working, so I gave the phone back. My colleague wasn't sure the history of it, but I'm willing to bet hardware issue. I appreciate your guidance, though! This was good learning experience for me. I feel a lot more at home with a lot of the basic fastboot commands and that kind of thing, so it wasn't a total loss on my part. I'm usually having to look up tutorials just to remember basic syntax!
Anyway thanks to all who chimed in. If mods want, they can close this thread, otherwise I'll just let it sink to its grave.

bootloader refuses to unlock

I've tried to unlock the boot loader of my HTC one m7 to no avail.
I tried unlocking it via htcdev but after wiping my phone, my boot loader still remained locked.
is there any alternative way of unlocking the boot loader without htcdev?
I saw one that involved typing some commands in fastboot but I'm afraid that might wreck the phone.
PS, I'm a newbie so please make any suggestions as plain as possible

gravity02 said:
I've tried to unlock the boot loader of my HTC one m7 to no avail.
I tried unlocking it via htcdev but after wiping my phone, my boot loader still remained locked.
is there any alternative way of unlocking the boot loader without htcdev?
I saw one that involved typing some commands in fastboot but I'm afraid that might wreck the phone.
PS, I'm a newbie so please make any suggestions as plain as possible
Click to expand...
Click to collapse
So is your device ***LOCKED*** or ***RELOCKED*** by which I mean has it ever been unlocked before or this is the first time?
Normally the course of action for bootloader unlocking issues is to flash a matching firmware package and request a new Unlock_code.bin. But let's see what variant of M7 you have first not all M7s can be unlocked via HTCdev.
Could you post the out put of
Code:
fastboot getvar all
Please remove your IMEI and Serial numbers before posting for security purposes
If you can't use HTCdev and your device is s-on then the only option is Sunshine App but it costs $25 so let's see what you've got and go from there :good:

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3721mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))

gravity02 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3721mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Ok your s-off That's good you have a couple of options here. You can flash a firmware package and request a new Unlock_code.bin as I mentioned above. :good: I'll see if I can find a firmware zip for you and post the link here
EDIT: -You can download a matching firmware here http://d-h.st/NPJ. Do you know how to flash firmware.zips with fastboot?
Or you can boot a custom recovery and unlock it yourself using "adb shell"
With the recovery image file in your fastboot folder. Connect fastboot usb and in the command window type
Code:
[B]fastboot boot recovery "name-of-recovery".img[/B]
[B]adb shell[/B]
[B]su[/B] (if needed to get a*#*prompt)
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/B]
(i would very strongly recomend you copy/paste this)
[B]exit[/B]
(exit a second time if you need to to get back to a normal > prompt)
[B]adb reboot bootloader[/B]
verify you are now unlocked
The above method is taken from this thread http://forum.xda-developers.com/showthread.php?t=2475914 Thanks should go to the OP :good:

thanks for the quick replies. I already have twrp installed. should I now run the command?
will it erase my files?

gravity02 said:
thanks for the quick replies. I already have twrp installed. should I now run the command?
will it erase my files?
Click to expand...
Click to collapse
HTCdev method will wipe your DATA and SDCARD
Recovery command method will not wipe anything :good:
Quoted from the Main Thread in above link
piterk said:
Could you tell me if this method to lock/unlock bootloader wipes phone data like the method via htcdev?
Click to expand...
Click to collapse
scotty1223 said:
no,it does not erase data.
the flashing of unlock code,and relock command initiate hboot to factory reset. this is only changing the flag that hboot checks.
Click to expand...
Click to collapse

tried this but it didn't work. the boot loader remained locked.
the phone was once bricked and I had it fixed via a JTAG. could this be a reason for this?

gravity02 said:
tried this but it didn't work. the boot loader remained locked.
the phone was once bricked and I had it fixed via a JTAG. could this be a reason for this?
Click to expand...
Click to collapse
Mmmm that's strange try again but this time use CWM https://www.dropbox.com/s/82kt3edku0j2sup/cwm.img?dl=0 you don't need to flash it just boot it with
Code:
fastboot boot cwm.img
Failing that did you try the firmware method?

I haven't tried the firmware method. can you walk me through it?

gravity02 said:
I haven't tried the firmware method. can you walk me through it?
Click to expand...
Click to collapse
Download the firmware package linked in my previous post. Put the zip in your fastboot folder and rename it "firmware.zip"
Boot your phone to the bootloader and connect fastbootusb, Now in the fastboot command line type
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now go to htcdev and complete the Unlock my bootloader procedure to get a new Unlock_code.bin :fingers-crossed:
FYI :- Flashing the firmware will restore the Stock Recovery so after the Unlock you will need to flash your Custom recovery again

I followed the steps but my phone is now stuck in the htc logo. I can't even switch it off

done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:

gravity02 said:
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
Click to expand...
Click to collapse
Hold down the power button and the volume down together, the capacitive buttons will flash, don't worry just let them flash and just keep holding down those 2 buttons, when they stop flashing which is about 12 to 15 times, release the power button, but continue to hold down the volume down the phone should now boot to the bootloader.

Seanie280672 said:
Hold down the power button and the volume down together, the capacitive buttons will flash, don't worry just let them flash and just keep holding down those 2 buttons, when they stop flashing which is about 12 to 15 times, release the power button, but continue to hold down the volume down the phone should now boot to the bootloader.
Click to expand...
Click to collapse
Don't forget it needs to be in a bright lighted room (really!)

gravity02 said:
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
Click to expand...
Click to collapse
Your Stuck on the HTC logo because you flashed the firmware and you have a custom rom. The Firmware restored your Stock Recovery and boot.img. Were you able to unlock the bootloader? You need to do that before you try flash anything. It was the Custom recovery and boot.img that caused the problem with unlocking the bootloader.
To make your phone boot to your rom again open the zip file of the rom installed on the phone and extract the boot.img to your fastboot folder. Then flash it with fastboot
Code:
fastboot flash boot boot.img
or just flash your rom again or any compatible rom :good:
P.S for the record when you post you should be quoting my last post or mention me like this @Danny201281 Then I will get a notification and you will get a faster response :good:

i'm currently in fastboot and there doesn't seem to be any change even after flashing the firmware.
i'm still s-off.
tried unlocking the bootloader again and it still remains locked. should i retry flashing the firmware?

gravity02 said:
i'm currently in fastboot and there doesn't seem to be any change even after flashing the firmware.
i'm still s-off.
tried unlocking the bootloader again and it still remains locked. should i retry flashing the firmware?
Click to expand...
Click to collapse
That is weird, are there any files on the device you need to keep? I'm running out of ideas here but you could try factory reset from the stock recovery but i'm not sure it will help. After that the only other thing I can suggest is flashing a full RUU.
Stock recovery factory reset instructions
Select recovery from the bootloader menu. The screen will turn black for a while and then display an image of a phone with red exclamation. Don't worry that's normal. Hold Volume up and press the power button to reveal the stock recovery menu. You will also see some errors about failed to mount sdcard that's also normal in Stock Recovery.
Select Factory Reset from the recovery menu. :good:
In the mean time i'll check out your options for RUU
---------- Post added at 10:44 AM ---------- Previous post was at 10:30 AM ----------
Danny201281 said:
That is weird, are there any files on the device you need to keep? I'm running out of ideas here but you could try factory reset from the stock recovery but i'm not sure it will help. After that the only other thing I can suggest is flashing a full RUU.
Stock recovery factory reset instructions
Select recovery from the bootloader menu. The screen will turn black for a while and then display an image of a phone with red exclamation. Don't worry that's normal. Hold Volume up and press the power button to reveal the stock recovery menu. You will also see some errors about failed to mount sdcard that's also normal in Stock Recovery.
Select Factory Reset from the recovery menu. :good:
In the mean time i'll check out your options for RUU
Click to expand...
Click to collapse
Ok it seems your in luck. There's plenty of RUU's for your T-Mobile device. Look here http://forum.xda-developers.com/showthread.php?t=2375223 and download this T-Mobile HTC One RUU 1.27.531.11
Simple to use just connect fastboot usb in the bootloader and launch the ruu on your pc. This will also wipe your device and return you to Stock.

@Danny201281, i'll download the RUU but will it be possible to flash twrp recovery and restore a backup of the ROM I made so?
won't that bring the phone back to life?

gravity02 said:
@Danny201281, i'll download the RUU but will it be possible to flash twrp recovery and restore a backup of the ROM I made so?
won't that bring the phone back to life?
Click to expand...
Click to collapse
You can't flash recovery while the bootloader is locked not even with s-off.
You could open the firmware zip you flashed and replace the recovery and boot.img with twrp and the boot.img of your Rom. Then flash the firmware zip. The phone should then boot up no problem. And you'll have the custom recovery back. If you want you can send me the boot.img or a link to the Rom on your phone and I can make the zip for you
Can I ask why you locked it in the first place? There's really no need to lock or relock when the device is s-off.
It's starting to look more like a hardware problem though. As I say normally it's some customization in the firmware that causes the problem. But with non of the methods working even with stock firmware it seems like the bootloader is not excepting any unlock instruction.

@ Danny201281, I replaced the stock recovery in the firmware.zip with twrp and flashed the firmware and was able to boot into twrp. I then copied a nandroid backup I made previously into the phone and restored it and the phone booted up properly.
how do I extract the boot.IMG from the nandroid?
thanks for your help so far