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.

[SOLVED] Soft bricked after manual OTA

Hi,
First, I'm an idiot.
I tried to manually apply the 4.3 OTA by:
fastboot oem rebootRUU
Then flashed the firmware.zip from the OTA:
flash zip firmware.ota
Got a softbrick.
Tried wiping cache and data, wont boot at all.
HBoot updated to 1.55 and firmware rev appears as 3.62.401.1
I'm S-ON with locked bootloader.
Can't apply earlier RUU.
Is there any way you can think of to restore my phone without unlocking it through htcdev.com and flashing a custom recovery?
Thanks,

flash a 4.3 rom through recovery.
i guess you only flashed the firmware.zip and not the whole ota? 4.2.2 roms do not work for me with this firmware.zip
edit: didn't see your locked. i guess there's no way then.

Nemesis_00 said:
Hi,
First, I'm an idiot.
I tried to manually apply the 4.3 OTA by:
fastboot oem rebootRUU
Then flashed the firmware.zip from the OTA:
flash zip firmware.ota
Got a softbrick.
Tried wiping cache and data, wont boot at all.
HBoot updated to 1.55 and firmware rev appears as 3.62.401.1
I'm S-ON with locked bootloader.
Can't apply earlier RUU.
Is there any way you can think of to restore my phone without unlocking it through htcdev.com and flashing a custom recovery?
Thanks,
Click to expand...
Click to collapse
1- Question: why did you manually flash the OTA, if you're still locked and on stock??????????
2- after "fastboot oem rebootRUU", did "fastboot flash zip firmware.zip" TWICE?? you know that usually the first time it reports as "FAILED, push image again immediately" (or something like that).

nkk71 said:
1- Question: why did you manually flash the OTA, if you're still locked and on stock??????????
2- after "fastboot oem rebootRUU", did "fastboot flash zip firmware.zip" TWICE?? you know that usually the first time it reports as "FAILED, push image again immediately" (or something like that).
Click to expand...
Click to collapse
Hi,
1. It's already established I am an IDIOT. It was even the first line of my post
2. Yes, I have flashed it twice. Stuck at black screen after boot. No ADB. Connecting to the PC shows MTP driver as showing up but failing to install.

Nemesis_00 said:
Hi,
1. It's already established I am an IDIOT. It was even the first line of my post
2. Yes, I have flashed it twice. Stuck at black screen after boot. No ADB. Connecting to the PC shows MTP driver as showing up but failing to install.
Click to expand...
Click to collapse
You're not an idiot, take it easy but maybe next time do some more reading before doing something you're not comfortable with.
At least you flashed it twice, so good chance it updated the firmware correctly, but which version of
1- Windows are you on? (hopefully Win 7)
2- and HTC Drivers? (latest are "HTCDriver_4.8.0.002.exe" AFAIK)
3- you on stock or custom recovery?
3b-- if stock, is the OTA file still on your phone?
4- do you have an OTG cable?

nkk71 said:
You're not an idiot, take it easy but maybe next time do some more reading before doing something you're not comfortable with.
At least you flashed it twice, so good chance it updated the firmware correctly, but which version of
1- Windows are you on? (hopefully Win 7)
2- and HTC Drivers? (latest are "HTCDriver_4.8.0.002.exe" AFAIK)
3- you on stock or custom recovery?
3b-- if stock, is the OTA file still on your phone?
4- do you have an OTG cable?
Click to expand...
Click to collapse
Thanks for your help.
Im running Win7 with latest HTC drivers, stock recovery. I bit the bullet and unlocked the bootloader.
The OTA file is not on the phone, but I have an OTG cable.
Fastboot and ADB are installed and working.
P.S.
I have the decrypted 1.29.401.16 zip available.
Tried flashing the zip to the phone, got an error.
Thanks again,

Nemesis_00 said:
Thanks for your help.
Im running Win7 with latest HTC drivers, stock recovery. I bit the bullet and unlocked the bootloader.
The OTA file is not on the phone, but I have an OTG cable.
Fastboot and ADB are installed and working.
P.S.
I have the decrypted 1.29.401.16 zip available.
Tried flashing the zip to the phone, got an error.
Thanks again,
Click to expand...
Click to collapse
OK so fastboot and adb are working :good::good:
Now let's slow down a bit, and let us what your goal is. (ie what ROM do you want to run, ROOT, and anything else of importance).

nkk71 said:
OK so fastboot and adb are working :good::good:
Now let's slow down a bit, and let us what your goal is. (ie what ROM do you want to run, ROOT, and anything else of importance).
Click to expand...
Click to collapse
Obviously there is no ADB since the ROM doesnt boot, but fastboot works fine.
For now, I would like to get back to stock 4.2.2 (2.24.401.8) or even 4.3 (3.62.401.1) if possible.
The MID is PN0710000 and CID is HTC__102
Thanks

you should have manually flashed ota via stock recovery,need to be s-off as well
sent from my s-off 801n M7_UL

Nemesis_00 said:
Obviously there is no ADB since the ROM doesnt boot, but fastboot works fine.
For now, I would like to get back to stock 4.2.2 (2.24.401.8) or even 4.3 (3.62.401.1) if possible.
The MID is PN0710000 and CID is HTC__102
Thanks
Click to expand...
Click to collapse
adb works in recovery too. Are you on stock or custom recovery?
Sent from my HTC One using Tapatalk

Stock recovery.

Ok, I've installed TWRP, now just waiting to download guru reset.

Nemesis_00 said:
Ok, I've installed TWRP, now just waiting to download guru reset.
Click to expand...
Click to collapse
IMHO, if you are comfortably doing it
get http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
then use http://rumrunner.us/ to get s-off (there's a package for 3.62.401.1), then use a full RUU (exe) to go back to stock and get the OTAs.

Thanks, That's exactly what im doing.
Just copied the Guru reset to the usb flash

Nemesis_00 said:
Thanks, That's exactly what im doing.
Just copied the Guru reset to the usb flash
Click to expand...
Click to collapse
Any updates mate?

Sorry, ofcourse.
Flashed Guru Reset boots and works fine.
I didnt manage to S-OFF tho.
Followed all instructions except disabling lockscreen which is impossible with this fw.
Win7 x64 SP1. Firewall and AV disabled.
Stuck with the error message: "FATAL: F**k it" after the second boot into bootloader (test3).
Basically the ROM should be stock and no real reason to re-flash stock via RUU, but it seems somewhat less smooth than 4.2.2, and I have a FC from TuneIn Radio the moment I plug it into the original car dock.
So I thought id start again fresh.
I suppose I'll flash a different Sense based ROM and try to S-OFF again.

Nemesis_00 said:
Sorry, ofcourse.
Flashed Guru Reset boots and works fine.
I didnt manage to S-OFF tho.
Followed all instructions except disabling lockscreen which is impossible with this fw.
Win7 x64 SP1. Firewall and AV disabled.
Stuck with the error message: "FATAL: F**k it" after the second boot into bootloader (test3).
Basically the ROM should be stock and no real reason to re-flash stock via RUU, but it seems somewhat less smooth than 4.2.2, and I have a FC from TuneIn Radio the moment I plug it into the original car dock.
So I thought id start again fresh.
I suppose I'll flash a different Sense based ROM and try to S-OFF again.
Click to expand...
Click to collapse
You'll have to be on a ROM that's compatible with your firmware version (which is now 3.6xxxx). Here are a few things to check
1- Are you on Win7, it could work on Win 8 maybe 8.1 but only haphazardly
2- Did you update drivers to "HTCDriver_4.8.0.002.exe"
3- uninstalled HTC Sync
3- did you update adb sdk to latest
4- disable antivirus & firewall & windows defender, etc.
5- on the phone:
----- disable any lockscreen password, pin, etc (so the password or pin or face recognition, not the actual lockscreen)
----- enable USB debugging
----- disable SETTINGS -> POWER -> Fast boot
copy/paste command prompt of rummrunner for us to see

nkk71 said:
You'll have to be on a ROM that's compatible with your firmware version (which is now 3.6xxxx). Here are a few things to check
1- Are you on Win7, it could work on Win 8 maybe 8.1 but only haphazardly
2- Did you update drivers to "HTCDriver_4.8.0.002.exe"
3- uninstalled HTC Sync
3- did you update adb sdk to latest
4- disable antivirus & firewall & windows defender, etc.
5- on the phone:
----- disable any lockscreen password, pin, etc (so the password or pin or face recognition, not the actual lockscreen)
----- enable USB debugging
----- disable SETTINGS -> POWER -> Fast boot
copy/paste command prompt of rummrunner for us to see
Click to expand...
Click to collapse
Hi,
1. Win7 Pro x64. Device connected to USB2.0
2. The installed drivers are "HTCDriver_4.8.0.001.exe" Could not find 002 anywhere.
3. I never had HTC Sync
4. Updated Android SDK with SDK Manager to latest version..
5. Antivirus unloaded completely, firewall (Windows) disabled.
6. FW Version reported by fastboot is 3.62.401.1, same as the one reported by the OS itself.
7. Not password/pin/face lock etc.
8. USB Debugging enabled, and Fast Boot disabled.
9. Rumrunner log is as follows:
Code:
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0710000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (25/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: **** it
...................
Thanks,

Nemesis_00 said:
Hi,
1. Win7 Pro x64. Device connected to USB2.0
2. The installed drivers are "HTCDriver_4.8.0.001.exe" Could not find 002 anywhere.
3. I never had HTC Sync
4. Updated Android SDK with SDK Manager to latest version..
5. Antivirus unloaded completely, firewall (Windows) disabled.
6. FW Version reported by fastboot is 3.62.401.1, same as the one reported by the OS itself.
7. Not password/pin/face lock etc.
8. USB Debugging enabled, and Fast Boot disabled.
9. Rumrunner log is as follows:
Code:
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0710000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (25/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: **** it
...................
Thanks,
Click to expand...
Click to collapse
Let me be honest, I have never tried (at least not yet ) rumrunner (I got S-Off with revone), but I did go through rumrunner thread, and the only two things I can think of, seeing your output:
Code:
Waiting for fastboot (7/120)
FATAL: **** it
that would be caused by the fastboot.exe (maybe the latest version is not the best )
Code:
...................
that's usually caused by a firewall or something else interfering with the internet connection.
I can't remember where I got the drivers from, but uploaded them for you:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
or you could, uninstall HTC xxxxxx, then download and install the latest HTC Sync Manager (from HTC web site), and then just uninstall the sync manager and keep drivers.
If all that doesn't work, I would give the Ubuntu Live CD/USB a try.

nkk71 said:
Let me be honest, I have never tried (at least not yet ) rumrunner (I got S-Off with revone), but I did go through rumrunner thread, and the only two things I can think of, seeing your output:
Code:
Waiting for fastboot (7/120)
FATAL: **** it
that would be caused by the fastboot.exe (maybe the latest version is not the best )
Code:
...................
that's usually caused by a firewall or something else interfering with the internet connection.
I can't remember where I got the drivers from, but uploaded them for you:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
or you could, uninstall HTC xxxxxx, then download and install the latest HTC Sync Manager (from HTC web site), and then just uninstall the sync manager and keep drivers.
If all that doesn't work, I would give the Ubuntu Live CD/USB a try.
Click to expand...
Click to collapse
As I've seen rumrunner has it's own fastboot.exe so I doubt it's that. There's also no firewall or anything, fastboot and adb work just fine on their own.
I've also S-OFF using revone, but later the emmc chip died, so I sent it for repair. Got it back with 1.54 hboot.
I'll give the Live CD a try later when I get the chance.

[Q] Stuck in RElocked bootloader cannot unlock

Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!

FURTHER to the above
jaqzilch said:
...
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,

jaqzilch said:
Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
Ok...
First flash a recovery(use Case 2):
No Recovery? No Problem​​
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
​
now you are unlocked and s off... so what we're gonna do depends on what you want to achieve... I didn't really get what you meant in the first post.. you want to be again 100% stock on a Asian ROM ?
with the unlocked bootloader and s off and the custom recovery you are pretty much able to flash the rom you want to the device... how to do this:
http://forum.xda-developers.com/showthread.php?t=2632736
or:
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
jaqzilch said:
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,
Click to expand...
Click to collapse
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs

LibertyMarine said:
Ok...
First flash a recovery(use Case 2):
...
[/INDENT][/INDENT]
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs
Click to expand...
Click to collapse
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
and nothing happens on my phone.
Re: Case two-- I'm one of those poor S-on folks so…
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!

jaqzilch said:
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
Click to expand...
Click to collapse
yeah.. that's because you are locked ....
jaqzilch said:
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
Click to expand...
Click to collapse
hmmm... have you tried redownloading/rerequesting a unlock token ?
try that... try requesting a new one and try flashing this one...
jaqzilch said:
and nothing happens on my phone.
Click to expand...
Click to collapse
haven't had such an issue.. I'll do some research on this topic..
jaqzilch said:
Re: Case two-- I'm one of those poor S-on folks so…
Click to expand...
Click to collapse
I don't know why.. I though you were s off... sorry... I must have commuted you with an other guy
jaqzilch said:
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!
Click to expand...
Click to collapse
Yeah... case 3 needs a custom recovery.. but you won't need that one anyways.. because your data partition seems to be OK

[Q] Htc One Bricked? Not sure...[SOLVED]

Not sure what had gone wrong... I believe the phone may be bricked. I rooted the device and sometime after I attempted to unroot it. Several attempts later with guides from here, htcguru, and many RUU's later it still does not work. It has reached the point where it no longer boots to any sort of rom, rather it will only boot into TRWP's recovery system. previously it would boot to an old rom that was loaded onto it with twrp from htc guru's website. it did nto have any touch compatibility and only the volume and power buttons would work.
I now also cannot access the phone from a computer, the PC (windows) recognizes it in the device manager, but it doesn't show up in windows explorer (maybe because it wont boot anything but the twrp recovery?)
No RUU's can fix it apparently, they will only say they either cannot connect to the phone, or an unknown error occurs and it simply cannot update the phone.
I've tried All-in-one kit, nothing seems to work. I am really at a loss, I spent 14 hours straight trying to unroot it, only progressively making it worse. I also could not get it to accept a mouse input from an otg cable whilst in the no touch input rom, don't know why..
Is this phone now inevitably ****ed beyond repair? I have pretty much given up all hope, I think the last time I asked for help with anything computer related was well over 3 years ago. I finally met my match in the hack and crack world, I read a lot of pages and guides, watched alot of videos, and even the HTC Dev site had me convinced this would be simple, easy, and painless work. Boy was I fooled.
I don't even know where to look anymore for answers, any I have no idea what information to give you guys, please excuse my apparent utter noobness and help me, I will provide as much information as I can, if I can.
Thanks in advance.

zoline411 said:
Not sure what had gone wrong... I believe the phone may be bricked. I rooted the device and sometime after I attempted to unroot it. Several attempts later with guides from here, htcguru, and many RUU's later it still does not work. It has reached the point where it no longer boots to any sort of rom, rather it will only boot into TRWP's recovery system. previously it would boot to an old rom that was loaded onto it with twrp from htc guru's website. it did nto have any touch compatibility and only the volume and power buttons would work.
I now also cannot access the phone from a computer, the PC (windows) recognizes it in the device manager, but it doesn't show up in windows explorer (maybe because it wont boot anything but the twrp recovery?)
No RUU's can fix it apparently, they will only say they either cannot connect to the phone, or an unknown error occurs and it simply cannot update the phone.
I've tried All-in-one kit, nothing seems to work. I am really at a loss, I spent 14 hours straight trying to unroot it, only progressively making it worse. I also could not get it to accept a mouse input from an otg cable whilst in the no touch input rom, don't know why..
Is this phone now inevitably ****ed beyond repair? I have pretty much given up all hope, I think the last time I asked for help with anything computer related was well over 3 years ago. I finally met my match in the hack and crack world, I read a lot of pages and guides, watched alot of videos, and even the HTC Dev site had me convinced this would be simple, easy, and painless work. Boy was I fooled.
I don't even know where to look anymore for answers, any I have no idea what information to give you guys, please excuse my apparent utter noobness and help me, I will provide as much information as I can, if I can.
Thanks in advance.
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' except the IMEI and SERIALNO
btw forget toolkits and work drirectly from your cmd prompt.
and post links of the ruu you tried to flash
what twrp version do you have?

14 hours.. You are stubborn! Better hope the device is recognized in fastboot as asked above
sent from my mobile device

Requested info
alray said:
post the output of ''fastboot getvar all'' except the IMEI and SERIALNO
btw forget toolkits and work drirectly from your cmd prompt.
and post links of the ruu you tried to flash
what twrp version do you have?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(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: 3834mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
RUU 1
http://d-h.st/4VH
found at http://forum.xda-developers.com/showthread.php?t=2427328
RUU 2
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
found at http://forum.xda-developers.com/showthread.php?t=2496074
I am using TWRP v2.6.0.1 So far that is the only thing bootable to, the computer will recognize the phone, so will fastboot, however it seems impossible to drop files onto the phone. Anything will be helpful right now, even if it wipes it clean (only wiped it clean about 70 times over the last 24 hours anyway...)
SaHiLzZ said:
14 hours.. You are stubborn! Better hope the device is recognized in fastboot as asked above
sent from my mobile device
Click to expand...
Click to collapse
Stubborn is one of my middle names, along with 'determined' and 'accident prone'
Thank you both for responding, and any others who try to help, again, I normally don't request or even need help, usually I can solve problems after tinkering for 9-12 hours, this time I decided I would ask because I fear I may be a hop, skip, and jump away from owning a $300 paperweight/bonfire-material...
Additionally, I can 'fastboot oem lock' with command prompt, and 'fastboot flash unlocktoken Unlock_code.bin' done both more times than I can count now, and I can't get the t-mobile startup sound out of my head anymore da-da-duh-duh-da-duh...

zoline411 said:
RUU 1
http://d-h.st/4VH
found at http://forum.xda-developers.com/showthread.php?t=2427328
Click to expand...
Click to collapse
This RUU is a downgrade in version and require S-OFF to be flashed
zoline411 said:
RUU 2
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
found at http://forum.xda-developers.com/showthread.php?t=2496074
Click to expand...
Click to collapse
This RUU is a downgrade in version and require S-OFF to be flashed
Afaik, there is no ruu for your phone version that can be flashed with S-ON
zoline411 said:
I am using TWRP v2.6.0.1 So far that is the only thing bootable to, the computer will recognize the phone, so will fastboot, however it seems impossible to drop files onto the phone. Anything will be helpful right now, even if it wipes it clean (only wiped it clean about 70 times over the last 24 hours anyway...)
Click to expand...
Click to collapse
TWRP 2.6.0.1 is very outdated. You'll need TWRP 2.6.3.3 to be able to flash 4.4+ roms.
zoline411 said:
Additionally, I can 'fastboot oem lock' with command prompt, and 'fastboot flash unlocktoken Unlock_code.bin' done both more times than I can count now, and I can't get the t-mobile startup sound out of my head anymore da-da-duh-duh-da-duh...
Click to expand...
Click to collapse
Woooh! Don't relock your bootloader! Its only needed to flash a RUU with s-on but there is no available for your phone!
Did you made a nandroid backup of your phone? If yes then restore it. if no, your only solution atm is to flash a custom rom (I personnaly recommend ARHD 53)
Is your bootloader still unlocked? If yes then:
Code:
fastboot flash recovery <twrp2.6.3.3>.img
fastboot erase cache [COLOR="Red"]<------ important[/COLOR]
fastboot reboot-bootloader
Download your custom rom and adb push it or adb sideload it from twrp recovery.

Faint light...
alray said:
This RUU is a downgrade in version and require S-OFF to be flashed
This RUU is a downgrade in version and require S-OFF to be flashed
Afaik, there is no ruu for your phone version that can be flashed with S-ON
TWRP 2.6.0.1 is very outdated. You'll need TWRP 2.6.3.3 to be able to flash 4.4+ roms.
Woooh! Don't relock your bootloader! Its only needed to flash a RUU with s-on but there is no available for your phone!
Did you made a nandroid backup of your phone? If yes then restore it. if no, your only solution atm is to flash a custom rom (I personnaly recommend ARHD 53)
Is your bootloader still unlocked? If yes then:
Code:
fastboot flash recovery <twrp2.6.3.3>.img
fastboot erase cache [COLOR="Red"]<------ important[/COLOR]
fastboot reboot-bootloader
Download your custom rom and adb push it or adb sideload it from twrp recovery.
Click to expand...
Click to collapse
I was getting that feeling after about 8 hours of button pressing, t-mobile jingles, and seemingly endless reading of interwebs, that there wasn't any sort of RUU for my phone, thank god. This means I can stop performing Einstein's definition of insanity...
TWRP v2.6.3.3, right... This should be the correct link for me right? (below) Also the line in command prompt should be "<openrecovery-twrp-2.6.3.3-m7>.img" without quotes, should I decide not to rename it, correct? **EDIT** Will not let me post outside links, the link in this page will take you to techerrata, I used the dl link marked 2.6.3.3, also worth noting there is a 2.7.0.0, should I bother with 2.7? or leave it be.
http://forum.xda-developers.com/showthread.php?t=2173870
Bad thing I locked the bootloader? It's currently unlocked for the hundredth time it seems, under your recommendation I will leave it unlocked. Further under your recommendation, the link below should be the version of ARHD 53 needed for my phone also, correct? **DOUBLE EDIT** No link to the outside world aloud, below there is a link to the android rev blogspot, I picked the first dl under HTC One, KitKat 4.4.2.
http://forum.xda-developers.com/showthread.php?t=2183023
As I believe I mentioned earlier, it appears, at the moment, impossible to transfer files over to the phone via usb, it shows up in device manager, but not in windows explorer under "My Computer." If you have an idea around that that would be fantastic, although not particularly needed, the HTC Sync Manager 'drive' that usually also appears also no longer shows up, however the drivers were loaded into this computer already, but the folder in the fake drive containing drivers was not copied (i iz stupidz.)
Also I don't believe I made the nandroid backup, I don't know why, actually I do, it's because I was an idiot and didn't bother to take the normal precautions.
The whole reason I ever wanted to root the device was for s-off, It only turned into a nightmare, I obviously dont even want to do that (well not right now, I'll have to talk to more intelligent types before attempting it,) so since I cannot figure out how to drag and drop (perhaps a way through command prompt?) the files to the phone, can I get a guide or a link to a guide, and please make it into kind-noob-langauge for me, to use abd to push it (ARHD) to the phone, or use it to transfer it to the phone where I can then use TWRP to flash/sideload/not perfectly sure what sideload is, into place.
Sorry for tl;dr; though, I have a feeling you guys are somewhat used to it.
Thanks greatly, I see the faint light on the other end getting brighter, lets hope I'm in a tunnel and not dying.

zoline411 said:
TWRP v2.6.3.3, right... This should be the correct link for me right? (below) Also the line in command prompt should be "<openrecovery-twrp-2.6.3.3-m7>.img" without quotes, should I decide not to rename it, correct? **EDIT** Will not let me post outside links, the link in this page will take you to techerrata, I used the dl link marked 2.6.3.3, also worth noting there is a 2.7.0.0, should I bother with 2.7? or leave it be.
http://forum.xda-developers.com/showthread.php?t=2173870
Click to expand...
Click to collapse
I'll recommend you to use 2.6.3.3 not 2.7 , there is a minor bug with 2.7 which will prevent the screen to turn off when charging the phone when powered off.
Make sure your recovery file and your rom is in the same folder were abd and fastboot are on your computer.
Boot your phone in bootloader mode, select fastboot then connect usb cable
open a cmd prompt from your adb/fastoot folder (hold shift + right click a blank space in the folder, select ''start a commend prompt here'')
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
zoline411 said:
the link below should be the version of ARHD 53 needed for my phone also, correct? **DOUBLE EDIT** No link to the outside world aloud, below there is a link to the android rev blogspot, I picked the first dl under HTC One, KitKat 4.4.2.
http://forum.xda-developers.com/showthread.php?t=2183023
Click to expand...
Click to collapse
Yes this is the correct rom
zoline411 said:
As I believe I mentioned earlier, it appears, at the moment, impossible to transfer files over to the phone via usb, it shows up in device manager, but not in windows explorer under "My Computer." If you have an idea around that that would be fantastic, although not particularly needed, the HTC Sync Manager 'drive' that usually also appears also no longer shows up, however the drivers were loaded into this computer already, but the folder in the fake drive containing drivers was not copied (i iz stupidz.)
Click to expand...
Click to collapse
You will use ADB to transfer files to your phone when booted in TWRP recovery
boot your phone in twrp 2.6.3.3
go in windows device manager and make sure your device is listed as ''android usb device ---> My HTC''. If yes your good to push to rom. If your phone is listed as ''Other Devices ---> One'' you'll need to follow that guide before:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
PUSH THE ROM
Again make sure the rom is in the adb/fasboot folder
open a command prompt from that folder
boot your phone in TWRP main menu
Code:
adb push ''name_of_rom_file''.zip /sdcard/
then in twrp select ''install'' and browse the sdcard folder to find your rom. Select it and swipe to flash.
after it flashed reboot your phone.
If something is not clear/don't work, ask me here and post screenshot of your command prompt

I'm not Dead.
alray said:
I'll recommend you to use 2.6.3.3 not 2.7 , there is a minor bug with 2.7 which will prevent the screen to turn off when charging the phone when powered off.
Make sure your recovery file and your rom is in the same folder were abd and fastboot are on your computer.
Boot your phone in bootloader mode, select fastboot then connect usb cable
open a cmd prompt from your adb/fastoot folder (hold shift + right click a blank space in the folder, select ''start a commend prompt here'')
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Yes this is the correct rom
You will use ADB to transfer files to your phone when booted in TWRP recovery
boot your phone in twrp 2.6.3.3
go in windows device manager and make sure your device is listed as ''android usb device ---> My HTC''. If yes your good to push to rom. If your phone is listed as ''Other Devices ---> One'' you'll need to follow that guide before:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
PUSH THE ROM
Again make sure the rom is in the adb/fasboot folder
open a command prompt from that folder
boot your phone in TWRP main menu
Code:
adb push ''name_of_rom_file''.zip /sdcard/
then in twrp select ''install'' and browse the sdcard folder to find your rom. Select it and swipe to flash.
after it flashed reboot your phone.
If something is not clear/don't work, ask me here and post screenshot of your command prompt
Click to expand...
Click to collapse
<Farnsworth>
Good news everyone!
</Farnsworth>
It worked! Yay. I greatly thank you from the bottom of my heart. Now it's just as good as it was before, and better. Using the sense toolkit, love it, and more importantly, the phone is actually normal now, double love it.
I really do like the area rom, I installed Xposed, and used it to update to the latest sense toolkit. Everything is wonderful. Stayed away from twrp 2.7, and we'll yeah, it's all good.
How do I give you some kind of 'kudos' or something along those lines. It's worth mentioning that this thread question can be marked as solved, not sure how to do it myself on the app. But I will try to hunt it down.
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Wow, just wow, thank you. I nearly turned my phone into a $300 paperweight over the course of 14 or so hours, and you solved the problem in less than 10 posts combined. Epic Android Kudos.
THANK YOU!
Sent from my HTC One using xda app-developers app

zoline411 said:
<Farnsworth>
Good news everyone!
</Farnsworth>
It worked! Yay. I greatly thank you from the bottom of my heart. Now it's just as good as it was before, and better. Using the sense toolkit, love it, and more importantly, the phone is actually normal now, double love it.
I really do like the area rom, I installed Xposed, and used it to update to the latest sense toolkit. Everything is wonderful. Stayed away from twrp 2.7, and we'll yeah, it's all good.
How do I give you some kind of 'kudos' or something along those lines. It's worth mentioning that this thread question can be marked as solved, not sure how to do it myself on the app. But I will try to hunt it down.
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Wow, just wow, thank you. I nearly turned my phone into a $300 paperweight over the course of 14 or so hours, and you solved the problem in less than 10 posts combined. Epic Android Kudos.
THANK YOU!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Congrats
you can mark the thread as solved by editing your first post -> go advanced -> then you can edit the main thread title and include [SOLVED]
you can thank the people who helped you by pressing the little Thanks button, on their posts

zoline411 said:
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Click to expand...
Click to collapse
Guide to return stock from nkk71. There is good informationd in the FAQ.
Guide to push or sideload a rom
There is many more, but those 2 are essential to recover a soft bricked phone
There is also great guides from ARHD blogspot here

@alray
Wonderful, I've been reading and to my understanding my phone in its current state is no longer able to have S-off, is that right? I believe if has to do with an update that occurred not so long ago, and I of course not knowing well enough did opt for the update. Also I have no idea whether any sort of backup would have been helpful or not.
I'm going to spend a great deal of time reading those guides, what I should have done before ever making an attempt at rooting and S-off, so yeah... Time to hit the books.

[Q] Soft-Bricked? HTC One M7 AT&T - Need Help

Hey all, going to try to post as much information as possible I'm a noob with this sort of thing. I had Cyanogenmod 11 on here but had lots of battery issues and stability issues, passing this phone off to a friend before she travels internationally and want to just get stock OS back on it. I've tried to follow several guides but none have really gotten me all the way to due several issues on the way that aren't really covered in those guides so I'm stuck asking for help after a few days of struggling with this.
Phone Info:
For Fastboot info (I can't post outside links yet)...
imgur/dgOIaG6
For hboot info... (I can't post outside links yet)
imgur/7z0Bi6Z
Ideally I'd like to get stock sense back on the phone, or Google Play Edition.
Here are a few instances of it bombing during commands.
D:\Development\AndroidStudio\sdk\platform-tools>fastboot flash recovery twrp.img
sending 'recovery' (9434 KB)...
OKAY [ 1.168s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.575s
D:\Development\AndroidStudio\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[nothing]
All of the RUU's(I tried all of the Cingular ones) just say they're "Sending" and never get to a progress bar. They just leave my phone with an HTC logo and nothing else.
Console Output from HTC One Toolkit
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb shell /data/local/tmp/./revone -s 0 -u
error: device not found
adb shell /data/local/tmp/./revone -s 0 -u
error: device not found
adb push "D:\Development\AndroidStudio\sdk\platform-tools\TWRP.img" "File Destination...Use \ NOT / or // !"
At this point adb doesn't really appear to be working at all, and fastboot is the only response I'll get.
I'm down to actively work on this issue and follow any troubleshooting steps you guys throw at me.
Thanks in advance.

Phaymous said:
Hey all, going to try to post as much information as possible I'm a noob with this sort of thing. I had Cyanogenmod 11 on here but had lots of battery issues and stability issues, passing this phone off to a friend before she travels internationally and want to just get stock OS back on it. I've tried to follow several guides but none have really gotten me all the way to due several issues on the way that aren't really covered in those guides so I'm stuck asking for help after a few days of struggling with this.
Phone Info:
For Fastboot info (I can't post outside links yet)...
imgur/dgOIaG6
For hboot info... (I can't post outside links yet)
imgur/7z0Bi6Z
Ideally I'd like to get stock sense back on the phone, or Google Play Edition.
Here are a few instances of it bombing during commands.
D:\Development\AndroidStudio\sdk\platform-tools>fastboot flash recovery twrp.img
sending 'recovery' (9434 KB)...
OKAY [ 1.168s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.575s
D:\Development\AndroidStudio\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[nothing]
All of the RUU's(I tried all of the Cingular ones) just say they're "Sending" and never get to a progress bar. They just leave my phone with an HTC logo and nothing else.
Console Output from HTC One Toolkit
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb shell /data/local/tmp/./revone -s 0 -u
error: device not found
adb shell /data/local/tmp/./revone -s 0 -u
error: device not found
adb push "D:\Development\AndroidStudio\sdk\platform-tools\TWRP.img" "File Destination...Use \ NOT / or // !"
At this point adb doesn't really appear to be working at all, and fastboot is the only response I'll get.
I'm down to actively work on this issue and follow any troubleshooting steps you guys throw at me.
Thanks in advance.
Click to expand...
Click to collapse
your images arnt working, is your bootloader unlocked ?
adb commands wont work in the bootloader therefore type fastboot devices and see if you get a result, if so type: fastboot getvar all and post the result here, it will help us a lot, be sure to remove your imei and serial number from the output before posting.
if your typing adb devices inside recovery or a booted rom, then you have a driver issue, check device manager and also FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

Seanie280672 said:
your images arnt working, is your bootloader unlocked ?
adb commands wont work in the bootloader therefore type fastboot devices and see if you get a result, if so type: fastboot getvar all and post the result here, it will help us a lot, be sure to remove your imei and serial number from the output before posting.
if your typing adb devices inside recovery or a booted rom, then you have a driver issue, check device manager and also FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
you're correct, bootloader is relocked, here are the images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@nkk71 thanks, how did you get those images up, I couldnt get them to show.
@Phaymous you need too unlock your bootloader to flash recovery, that's why its failing.
but before you do that, here's the RUU that you need to use, however, if you have a driver problem you will have to sort that out first, do not use the toolkits, most of the time they are out of date, once done, put your phone into fastboot USB mode and run the RUU.
http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/
you can try this for drivers and a better version of adb and fastboot: http://forum.xda-developers.com/showthread.php?t=2588979

Seanie280672 said:
@nkk71 thanks, how did you get those images up, I couldnt get them to show.
Click to expand...
Click to collapse
i just added the .com, since he's new here, he can't post links yet so imgur/7z0Bi6Z -> http://imgur.com/7z0Bi6Z
OP, Seanie280672 will guide you through this, remember to thank him :good:
PS: don't bother with revone, you have an ATT patched hboot, you can either use rumrunner, firewater, sunshine, or the att downgrade method

Seanie280672 said:
@Phaymous you need too unlock your bootloader to flash recovery, that's why its failing.
but before you do that, here's the RUU that you need to use, however, if you have a driver problem you will have to sort that out first, do not use the toolkits, most of the time they are out of date, once done, put your phone into fastboot USB mode and run the RUU.
you can try this for drivers and a better version of adb and fastboot: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Seanie,
I unlocked the Bootloader and downloaded the RUU. However, it just fails with a 155 error:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Click to expand...
Click to collapse
I'm trying it again, but all I have is the "HTC" Logo screen on my phone while it's in progress, and on my PC it simply shows that it's "Sending..." indefinitely.
How can I confirm that I am not having driver issues in this mode? This is my driver setup currently: imgur/DqdOr3X (add the http and .com)
Again, fastboot works, but adb devices does not display the device information.
C:\Users\Justin\adb>adb devices
List of devices attached
C:\Users\Justin\adb>fastboot devices
HT38DW903440 fastboot
I've tried to follow the guide that you have listed and I downloaded the 'better version of adb and fastboot', it seems that it is still unsuccessful in running adb commands. While in the bootloader I should be in fastboot selection on phone while trying to run these adb commands correct? The .zip image guide of drivers doesn't exactly play out the same on my PC. I also tried to look for uninstalling the Google USB Driver and re-installing but couldn't find anywhere to uninstall it (it's certainly not in Control Panel), Android Studio/SDK Manager shows that I have the latest version of it installed, however. As for the picture guide that lists him selecting the ADB Driver, I don't have that driver / cannot select it, and it's not anywhere that I can see in his packages so I'm confused by that guide.
Seanie280672 said:
adb commands wont work in the bootloader therefore type fastboot devices and see if you get a result, if so type: fastboot getvar all and post the result here, it will help us a lot, be sure to remove your imei and serial number from the output before posting.
if your typing adb devices inside recovery or a booted rom, then you have a driver issue, check device manager and also FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Now sure how to proceed, RUU's still failing, not sure if ADB Devices are supposed to work while in fastboot on phone.
Thoughts on how to proceed?
Thank you again.

Phaymous said:
Seanie,
I unlocked the Bootloader and downloaded the RUU. However, it just fails with a 155 error:
I'm trying it again, but all I have is the "HTC" Logo screen on my phone while it's in progress, and on my PC it simply shows that it's "Sending..." indefinitely.
How can I confirm that I am not having driver issues in this mode? This is my driver setup currently: imgur/DqdOr3X (add the http and .com)
Again, fastboot works, but adb devices does not display the device information.
C:\Users\Justin\adb>adb devices
List of devices attached
C:\Users\Justin\adb>fastboot devices
HT38DW903440 fastboot
I've tried to follow the guide that you have listed and I downloaded the 'better version of adb and fastboot', it seems that it is still unsuccessful in running adb commands. While in the bootloader I should be in fastboot selection on phone while trying to run these adb commands correct? The .zip image guide of drivers doesn't exactly play out the same on my PC. I also tried to look for uninstalling the Google USB Driver and re-installing but couldn't find anywhere to uninstall it (it's certainly not in Control Panel), Android Studio/SDK Manager shows that I have the latest version of it installed, however. As for the picture guide that lists him selecting the ADB Driver, I don't have that driver / cannot select it, and it's not anywhere that I can see in his packages so I'm confused by that guide.
Now sure how to proceed, RUU's still failing, not sure if ADB Devices are supposed to work while in fastboot on phone.
Thoughts on how to proceed?
Thank you again.
Click to expand...
Click to collapse
you need to have your phone in fastboot USB mode whilst running the ruu, not on the white screen with the green HTC logo
if your having trouble getting to this screen, then hold down the power button and volume down together whilst the lights on the bottom flash 10 to 15 times, when they stop flashing, release the power button, but continue to hold the volume down, it should take you to the bootloader, select fastboot in the list if its not already there and plug into your PC, it should now say fastboot USB on the screen.
your drivers look fine, it says MyHTC, that's fine.
bootloader needs to be locked / relocked for the RUU, or unlocked to flash a custom recovery, according to your output in your picture, that's your RUU.
adb commands will not work in the bootloader full stop, only fastboot commands, adb is only for when in recovery or booted rom.
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
this is your version main: 1.26.502.15 basically the firmware version on your output, and that's the most needed and important number
and this is the RUU: RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
it should work, check the MD5 of the RUU you downloaded to make sure its not corrupt, and also that the file size matches the size on the site you downloaded it from, if your not sure how to check MD5, refer to here: http://forum.xda-developers.com/showthread.php?t=1135620

Okay so it sounds like ADB is nothing I should be concerned about, nor my drivers.
Sorry for the confusion about my fastboot usb screen, I'm aware of how to get there, I was referring to while applying the RUU it just sits at a 'frozen' HTC logo page while it's attempting to deploy the RUU. I attempt the deploy from the fastboot USB screen.
Do I need to re-lock my bootloader? I thought I had to *unlock* my bootloader after the original post.
Now my phone shows:
***TAMPERED***
***UNLOCKED***
From Fastboot USB mode, I should be attempting to apply the RUU at this point, correct?
Thanks

Phaymous said:
Okay so it sounds like ADB is nothing I should be concerned about, nor my drivers.
Sorry for the confusion about my fastboot usb screen, I'm aware of how to get there, I was referring to while applying the RUU it just sits at a 'frozen' HTC logo page while it's attempting to deploy the RUU. I attempt the deploy from the fastboot USB screen.
Do I need to re-lock my bootloader? I thought I had to *unlock* my bootloader after the original post.
Now my phone shows:
***TAMPERED***
***UNLOCKED***
From Fastboot USB mode, I should be attempting to apply the RUU at this point, correct?
Thanks
Click to expand...
Click to collapse
for RUU flashes it needs to be Locked or Relocked
For custom recovery flashes it needs to be unlocked.
sorry about the confusion

How can I proceed to re-lock for RUU? Because originally I thought you guys had me unlock my bootloader?

Phaymous said:
How can I proceed to re-lock for RUU? Because originally I thought you guys had me unlock my bootloader?
Click to expand...
Click to collapse
open a command window in the same folder as your adb and fastboot on your computer, to do that hold control & shift & right mouse click in any white area of that window and select open command window here
plug your phone into the computer and make sure it says fastboot usb on the screen
then type: fastboot oem lock
then type fastboot reboot-bootloader
done.
I said in my 2nd post you need to unlock the bootloader to flash a custom recovery, but before you do that..............

Success! Thank you.

Phaymous said:
Success! Thank you.
Click to expand...
Click to collapse
your welcome, glad its sorted. :good:

Phaymous said:
How can I proceed to re-lock for RUU? Because originally I thought you guys had me unlock my bootloader?
Click to expand...
Click to collapse
To use official RUU relock the bootloader
put yur mobile into fastboot mode
open CMD command
Enter this command fastboot oem relock
official ruu http://www.htc1guru.com/downloads/ruu-file-downloads/

Seanie280672 said:
and this is the RUU: RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Click to expand...
Click to collapse
One last question for you Seanie (thanks again).
Software information shows Android Version 4.1.2, HTC Sense version 5.0, Software Number 1.26.502.15, HTC SDK API level 5.12.
Is there any way to force Google/HTC/AT&T to serve me up the latest version of Android OS? Will it receive 4.4 in time? I believe HTC One M7 came stock with KitKat iirc.
Thanks for your help.