Database Develop

[SOLVED] Please guys, need help to bring my One back working

Hi guys.
Yesterday i decided to s-off via rumrunner.
I was on a GPE ROM (so yes, rooted, twrp recovery and custom rom) so i downloaded and flashed a sense based ROM as suggested, but after repeating 2 times the 8 pouring attempts i was still s-on.
I decided to try another sense base flashing a ruu back to stock to be sure it was compatible, so I relocked the bootloader.
The ruu install went immediately wrong (FAILED signature check verification). The problem now is that when I power it on it immediately goes in fastboot mode (yes fastboot, not bootloader). If I press bootloader and then recovery it goes back to fastboot.
So I tried another thing: unlock again the bootloader to manually flash back a custom recovery to make it work again.
Great idea, so i prepared back the unlocktoken, flash it and BAM: again signature check verification fail.
If I can't unlock and custom recovery again my only hope I guess its an ruu reset.
Now, I know that I can't revert hboot to an older version, and mine is 1.54.0000 so pretty high, but i tried also a 3.x RUU i found inside the RUU collection thread and got the same error msg.
Also smth must be definitely wrong cause I don't think the Unlocktoken should get that error msg, I never got it!
So to summarize:
- tampered, relocked and s-on 1.54.0000 hboot
- FAILED signature check verification if I try to unlock it via htcdev tocken
- RUU zips get same signature check fail error
- same signature check verification error if I try to manually flash just the boot partition (fastboot flash boot)
Guys I had a Desire, a One XL, a Nexus 4 but I think it's the first time I'm stuck with a completely useless slab and really don't know how to recover it.
Really ANY suggestion to make it boot again would be much appreciated...
Thanks

Yorgan said:
Hi guys.
Yesterday i decided to s-off via rumrunner.
I was on a GPE ROM (so yes, rooted, twrp recovery and custom rom) so i downloaded and flashed a sense based ROM as suggested, but after repeating 2 times the 8 pouring attempts i was still s-on.
I decided to try another sense base flashing a ruu back to stock to be sure it was compatible, so I relocked the bootloader.
The ruu install went immediately wrong (FAILED signature check verification). The problem now is that when I power it on it immediately goes in fastboot mode (yes fastboot, not bootloader). If I press bootloader and then recovery it goes back to fastboot.
So I tried another thing: unlock again the bootloader to manually flash back a custom recovery to make it work again.
Great idea, so i prepared back the unlocktoken, flash it and BAM: again signature check verification fail.
If I can't relock my only hope I guess its an ruu reset.
Now, I know that I can't revert hboot to an older version, and mine is 1.54.0000 so pretty high, but i tried also a 3.x RUU i found inside the RUU collection thread and got the same error msg.
Also smth must be definitely wrong cause I don't think the Unlocktoken should get that error msg, I never got it!
So to summarize:
- tampered, relocked and s-on 1.54.0000 hboot
- FAILED signature check verification if I try to unlock it via htcdev tocken
- RUU zips get same signature check fail error
- same signature check verification error if I try to manually flash just the boot partition (fastboot flash boot)
Guys I had a Desire, a One XL, a Nexus 4 but I think it's the first time I'm stuck with a completely useless slab and really don't know how to recover it.
Really ANY suggestion to make it boot again would be much appreciated...
Thanks
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n before posting)

nkk71 said:
can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
Click to expand...
Click to collapse
Sure, here it is:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid:
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 4200mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
Thanks for the quick answer

Yorgan said:
Sure, here it is:
version-bootloader: 1.54.0000
version-main: 2.24.401.1
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0710000
cidnum: HTC__032
Thanks for the quick answer
Click to expand...
Click to collapse
A) Do you still have custom recovery? If yes, can you enter recovery, and on your PC open a shell: "adb shell", does it show $ or #
can you copy/paste the command prompt
B) did you get a new unlocktocken from HTCdev, or are you using your old one?
Hit thanks button if I've helped, though it to soon to tell if I did

nkk71 said:
A) Do you still have custom recovery? If yes, can you enter recovery, and on your PC open a shell: "adb shell", does it show $ or #
can you copy/paste the command prompt
B) did you get a new unlocktocken from HTCdev, or are you using your old one?
Hit thanks button if I've helped, though it to soon to tell if I did
Click to expand...
Click to collapse
yup i forgot to press it =)
no custom recovery as i said, it just goes back to fastboot, i wanted to unlock it to flash twrp again but this stupid signature check is preventing me from doing anything!
i somehow think that my rom is still inside, just not booting, that's why i also tried to manually flash just the boot.img.
nope, i obtained a new one after the old gave me the error, no luck
really i dont know what to think

Yorgan said:
nope, i obtained a new one after the old gave me the error, no luck
really i dont know what to think
Click to expand...
Click to collapse
Okay, this is bad
Yorgan said:
that's why i also tried to manually flash just the boot.img.
Click to expand...
Click to collapse
Won't work with locked/relocked bootloader
Yorgan said:
no custom recovery as i said, it just goes back to fastboot,
Click to expand...
Click to collapse
A) did you at any point flash a stock recovery? (either using a Guru Reset ROM or fastboot flash recovery etc?)
B) have you tried:
fastboot erase cache
fastboot reboot-bootloader
and try to enter RECOVERY (using the volume and power buttons)?

nkk71 said:
Okay, this is bad
Won't work with locked/relocked bootloader
A) did you at any point flash a stock recovery? (either using a Guru Reset ROM or fastboot flash recovery etc?)
B) have you tried:
fastboot erase cache
fastboot reboot-bootloader
and try to enter RECOVERY (using the volume and power buttons)?
Click to expand...
Click to collapse
Nope i never wanted to remove TWRP, but does relocking bootloader not flash back the stock one?
Unluckily it just enters fastboot no matter if i power the phone up with or without volume buttons pressed!
I always thought that "if there's fastboot there's hope", but how to bypass the signature check if i'm s-on?
And why the heck does it fail checking signature of the Unlocktoken?

Yorgan said:
Nope i never wanted to remove TWRP, but does relocking bootloader not flash back the stock one?
Unluckily it just enters fastboot no matter if i power the phone up with or without volume buttons pressed!
I always thought that "if there's fastboot there's hope", but how to bypass the signature check if i'm s-on?
And why the heck does it fail checking signature of the Unlocktoken?
Click to expand...
Click to collapse
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?

nkk71 said:
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?
Click to expand...
Click to collapse
It vibrates, White screen with Htc logo, it writes 'entering recovery' for half a second and then back to fastboot

nkk71 said:
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?
Click to expand...
Click to collapse
OMG the UnlockCode worked!
Just to let you know, i changed absolutely nothing: the command i sent was the same as before and so was the token.
I think that maybe one of the many failed RUU attempts just flashed the partition i was missing, not enough to flash rom but enough to check the signature of the token!
Thx a lot dude, you gave me the hope to try to mess around again =)
Happyyy =))

Yorgan said:
OMG the UnlockCode worked!
Just to let you know, i changed absolutely nothing: the command i sent was the same as before and so was the token.
I think that maybe one of the many failed RUU attempts just flashed the partition i was missing, not enough to flash rom but enough to check the signature of the token!
Thx a lot dude, you gave me the hope to try to mess around again =)
Happyyy =))
Click to expand...
Click to collapse
:good::good::highfive::highfive::highfive::highfive::highfive::highfive::highfive: (I know that looks funny )
So go get yourself S-Off, and never go back S-On. S-Off is your "get out of jail" card!!!
Do not relock, unless S-Off, there's a thread somewhere around here where plenty of people weren't able to get HTCdev to unlock again!!
Any other help needed, let me know.

[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!

HELP! Nasty Brick - No ADB/Recovery/RebootRUU + Borked Fastboot

I hate to add another one of these "help/brick" threads to the pile, but I've been reading around the forums for days, and I'm finally stumped.
My M7 is rooted, unlocked, S-OFF, superCID, with an InsertCoin custom rom and TWRP recovery... all hunky-dorey... Until I decided to return it to stock, so began simply by changing the CID back to original (11111111 - > HTC__622). This worked alright, except then everything suddenly stopped working:
1) Can't boot into OS (hangs on boot screen until eventual auto-reboot)
2) Can't boot into TWRP recovery (hangs on TWRP splash screen until eventual auto-reboot)
3) Can't enter RebootRUU via fastboot (just reboots phone)
4) Can't connect to pc via ADB within hboot/bootloader (no devices present)
5) Can't reboot itself into the bootloader from fastboot (it just resets the phone)
6) CAN enter bootloader manually via power+volume down
7) CAN connect to pc and issue fastboot commands within fastboot, BUT... fastboot is seemingly useless. Fastboot operations either report success (such as writecid and flash recovery giving an "OKAY") without actually writing anything; or they report failure (erase and others giving a "failed - remote: not allowed")
8) Another odd thing... in fastboot, when connecting to the USB, and the red label changes from "FASTBOOT" to "FASTBOOT USB" the label itself is partially 'torn'... that is, the top right corner of the fastboot usb label appears to be only partially drawn/rendered, by varying degrees over time, from completely showing to completely invisible. Weird.
I've tried everything from fastboot-flashing new recoveries (says OK, but nothing changes) to running RUU EXEs (they die when they can't reboot to the bootloader, just as fastboot cannot reboot to bootloader automatically either)
EDIT: I've also tried all of the above on older and newer computers and their different USB ports.
Here's my bootloader/hboot/fastboot status readout and my GETVAR, for those who are interested:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-HTC__622
HBOOT-1.56.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
Nov 29 2013,20:47:04.0
FASTBOOT USB (this is what gets partially rendered!)
------------------------------------------------
GETVAR ALL:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.2
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__622
battery-status: good
battery-voltage: 4317mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
Thanks to all who can offer some help with this... I'm at the end of my rope here......... sigh.
Cheers, guys.

tobin_o said:
I hate to add another one of these "help/brick" threads to the pile, but I've been reading around the forums for days, and I'm finally stumped.
My M7 is rooted, unlocked, S-OFF, superCID, with an InsertCoin custom rom and TWRP recovery... all hunky-dorey... Until I decided to return it to stock, so began simply by changing the CID back to original (11111111 - > HTC__622). This worked alright, except then everything suddenly stopped working:
1) Can't boot into OS (hangs on boot screen until eventual auto-reboot)
2) Can't boot into TWRP recovery (hangs on TWRP splash screen until eventual auto-reboot)
3) Can't enter RebootRUU via fastboot (just reboots phone)
4) Can't connect to pc via ADB within hboot/bootloader (no devices present)
5) Can't reboot itself into the bootloader from fastboot (it just resets the phone)
6) CAN enter bootloader manually via power+volume down
7) CAN connect to pc and issue fastboot commands within fastboot, BUT... fastboot is seemingly useless. Fastboot operations either report success (such as writecid and flash recovery giving an "OKAY") without actually writing anything; or they report failure (erase and others giving a "failed - remote: not allowed")
8) Another odd thing... in fastboot, when connecting to the USB, and the red label changes from "FASTBOOT" to "FASTBOOT USB" the label itself is partially 'torn'... that is, the top right corner of the fastboot usb label appears to be only partially drawn/rendered, by varying degrees over time, from completely showing to completely invisible. Weird.
I've tried everything from fastboot-flashing new recoveries (says OK, but nothing changes) to running RUU EXEs (they die when they can't reboot to the bootloader, just as fastboot cannot reboot to bootloader automatically either)
Here's my bootloader/hboot/fastboot status readout and my GETVAR, for those who are interested:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-HTC__622
HBOOT-1.56.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
Nov 29 2013,20:47:04.0
FASTBOOT USB (this is what gets partially rendered!)
------------------------------------------------
GETVAR ALL:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.2
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__622
battery-status: good
battery-voltage: 4317mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
Thanks to all who can offer some help with this... I'm at the end of my rope here......... sigh.
Cheers, guys.
Click to expand...
Click to collapse
You may want to have a look at my thread. i am having similar problems. On the last post i make a summary of my problems:
http://forum.xda-developers.com/showthread.php?t=2685024&page=3

Have you tried a different computer or just a different USB on your own machine?. Try a USB 2.0 to send fastboot commands, erase cache, flash recovery again (try both CWM as well as TWRP) after that fastboot erase cache again
Then reboot back into boot loader and from there into recovery.
Hope you get it sorted
Sent from my HTC One using XDA Premium HD app

Darksnoopy, thank you *very* much for the link to your own issue... it sounds very much like the same problem. Sadly, this means I'm probably SOL.
Did you ever look into how much HTC would want to charge you for fixing this nastiness? The irony is that I was changing mine back to stock only because I wanted to get the infamous purple-haze camera replaced while the warranty was still good... now I would have to pay for the internal memory fix myself, and probably the camera replacement, too. What are the chances this would end up being more than the value of the phone...
darksnoopy said:
You may want to have a look at my thread. i am having similar problems. On the last post i make a summary of my problems:
http://forum.xda-developers.com/showthread.php?t=2685024&page=3
Click to expand...
Click to collapse

hardstuffmuc said:
Have you tried a different computer or just a different USB on your own machine?. Try a USB 2.0 to send fastboot commands, erase cache, flash recovery again (try both CWM as well as TWRP) after that fastboot erase cache again
Then reboot back into boot loader and from there into recovery.
Click to expand...
Click to collapse
Good suggestion, Hardstuff... I did in fact try two very different (in age) computers and all of their USB ports, all with the same result, unfortunately. I forgot to mention that fact in the OP.
Thanks, anyway!

I can only add that do not lock the bootloader or s-on

SaHiLzZ said:
I can only add that do not lock the bootloader or s-on
Click to expand...
Click to collapse
Thanks for the reminder... at desperate times like this, we might be driven to try something crazy

What windows version do you have?
Just to make sure the steps:
Fastboot USB is detected? (that graphic glitch is nothing to worry about...I had that in the past)
And you have latest HTC drivers installed? If not, delete all HTC Sybc stuff including drivers, reboot computer, download latest HTC Syncmanager and install it, reboot computer again, de-install SyncManager, but leave drivers, and another reboot of computer!
Please download TWRP 2.6.3.3 file, put it into your adb/fastboot folder (it has to be named inside the folder WITHOUT the .img at the end) see attached pic
Please download a Sense 5.5 custom ROM, also put it into your adb/fastboot folder
Connect One using USB 2.0 to computer
fastboot erase cache
fastboot flash recovery openrecovery-twrp.2.6.3.3-m7ul.img (name exactly as the file is named inside adb/fastboot folder...see attached pic)
fastboot erase cache
Please post output to these commands with screenshot
Try to boot into recovery
If it works, back to bootloader, connect the One in Fastboot USB mode
adb devices (see attached pic)
adb push xxx.zip sdcard/
here in the cmd window not a lot happening as a Sense ROM has 1GB which takes a while to transfer, like 5 minutes, be patient
Once done, back into recovery and flash the .zip from there
Please report back if this solves the problem!
greets

tobin_o said:
Darksnoopy, thank you *very* much for the link to your own issue... it sounds very much like the same problem. Sadly, this means I'm probably SOL.
Did you ever look into how much HTC would want to charge you for fixing this nastiness? The irony is that I was changing mine back to stock only because I wanted to get the infamous purple-haze camera replaced while the warranty was still good... now I would have to pay for the internal memory fix myself, and probably the camera replacement, too. What are the chances this would end up being more than the value of the phone...
Click to expand...
Click to collapse
No not really, i know they are asking a lot of money for simple repairs, i am not going to ask for a new motherboard! And i cant find any motherboards on the internet to try to fix it myself
hardstuffmuc said:
What windows version do you have?
Just to make sure the steps:
Fastboot USB is detected? (that graphic glitch is nothing to worry about...I had that in the past)
And you have latest HTC drivers installed? If not, delete all HTC Sybc stuff including drivers, reboot computer, download latest HTC Syncmanager and install it, reboot computer again, de-install SyncManager, but leave drivers, and another reboot of computer!
Please download TWRP 2.6.3.3 file, put it into your adb/fastboot folder (it has to be named inside the folder WITHOUT the .img at the end) see attached pic
Please download a Sense 5.5 custom ROM, also put it into your adb/fastboot folder
Connect One using USB 2.0 to computer
fastboot erase cache
fastboot flash recovery openrecovery-twrp.2.6.3.3-m7ul.img (name exactly as the file is named inside adb/fastboot folder...see attached pic)
fastboot erase cache
Please post output to these commands with screenshot
Try to boot into recovery
If it works, back to bootloader, connect the One in Fastboot USB mode
adb devices (see attached pic)
adb push xxx.zip sdcard/
here in the cmd window not a lot happening as a Sense ROM has 1GB which takes a while to transfer, like 5 minutes, be patient
Once done, back into recovery and flash the .zip from there
Please report back if this solves the problem!
greets
Click to expand...
Click to collapse
I really hope it is not a eMMC failure, because if it is, none of the above will work. I lost one week of my life trying to fix my phone!

Hi Hardstuff, thanks for the thorough list of suggestions!
First, I'm running Win7-32bit on one computer, and Win7-64bit on the other.
Second, yeah, Fastboot USB is detected no problem, but that's about the only thing going for me.
I did as you said-- wiped every trace of the old drivers, and reinstalled the HTC drivers by way of HTC Sync install/uninstall, with reboots in between each step.
Sadly, everything with the cache erase and recovery flash went as always-- fastboot seems to indicate success on each command, but TWRP still freezes on the TWRP splash screen until it finally does a reboot by itself. I'm pretty sure this isn't a new install of TWRP that's freezing, as I tried flashing a CWM recovery the other day too, with a success message on the flash, then still came up freezing on a TWRP screen.
I did a screencap of the fastboot commands, as well as the driver install window, showing the collection of driver installs attempted as the phone went from power off, to bootloader, to fastboot, to attempting recovery, and so on. Windows also kept complaining that it was connected to a USB device that it couldn't recognize.
This entire series of steps and results was the same on each USB port on both computers - no variation.
Not sure if there's anything left to try at this point... I've never been this screwed with a phone before, and it was all just from a weenie little CID change - this sucks.
Anyway, thanks again Hardstuff!
hardstuffmuc said:
What windows version do you have?
Just to make sure the steps:
Fastboot USB is detected? (that graphic glitch is nothing to worry about...I had that in the past)
And you have latest HTC drivers installed? If not, delete all HTC Sybc stuff including drivers, reboot computer, download latest HTC Syncmanager and install it, reboot computer again, de-install SyncManager, but leave drivers, and another reboot of computer!
Please download TWRP 2.6.3.3 file, put it into your adb/fastboot folder (it has to be named inside the folder WITHOUT the .img at the end) see attached pic
Please download a Sense 5.5 custom ROM, also put it into your adb/fastboot folder
Connect One using USB 2.0 to computer
fastboot erase cache
fastboot flash recovery openrecovery-twrp.2.6.3.3-m7ul.img (name exactly as the file is named inside adb/fastboot folder...see attached pic)
fastboot erase cache
Please post output to these commands with screenshot
Try to boot into recovery
Click to expand...
Click to collapse

darksnoopy said:
No not really, i know they are asking a lot of money for simple repairs, i am not going to ask for a new motherboard! And i cant find any motherboards on the internet to try to fix it myself
I really hope it is not a eMMC failure, because if it is, none of the above will work. I lost one week of my life trying to fix my phone!
Click to expand...
Click to collapse
Yeah, and even if you could find a replacement mobo online, I've heard that the One is one of the worst phones ever for taking apart and reassembling.
What really burns me is that I've likely lost a fairly expensive phone without making any mistake that I could at least blame myself for. It sounds like your One also went south on you without any mistake on your part. My next question would be-- is this more likely to happen with the One? With all HTCs? Or all handsets equally? My backup Xperia Play has put on a lot of crazy mileage in terms of flashing, along with a Galaxy S2 that I sold some time ago. On the other hand, my One was virtually untouched by comparison...

tobin_o said:
Yeah, and even if you could find a replacement mobo online, I've heard that the One is one of the worst phones ever for taking apart and reassembling.
What really burns me is that I've likely lost a fairly expensive phone without making any mistake that I could at least blame myself for. It sounds like your One also went south on you without any mistake on your part. My next question would be-- is this more likely to happen with the One? With all HTCs? Or all handsets equally? My backup Xperia Play has put on a lot of crazy mileage in terms of flashing, along with a Galaxy S2 that I sold some time ago. On the other hand, my One was virtually untouched by comparison...
Click to expand...
Click to collapse
Yeah if you search for "emmc write protected" or "emmc lockout" you will find many threads about lots of different brands. Well if u consider how many htc ones have been sold, this problem is not quite common

Have you tried to get back to supercid?

SaHiLzZ said:
Have you tried to get back to supercid?
Click to expand...
Click to collapse
Yep. Same deal as the other fastboot write commands: It carries out the write operation as if it were successful, but then nothing has changed.

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.

Can't go to stock rom HTC One M7m need stock rom

Hello.
In the first time, sorry for my english.
I have a HTC One M7 with this:
Tampered
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35-3218.16
OpenDSP-v35.120.274.0718
OS-
eMMC-boot 2048MB
Nov 16 2015,20:23:35.28773
In this moment, I use other ROM, I need install original stock rom.
A few months ago I try to made this (using some instructions and files of the htc1guru) but I was have problem, install fine (with android 4.x) and in the sewcond or third update of the system by HTC, when restart, not start the phone, try this operation 3 or 4 times, and always the same result, after this upgrade, when restart phone, not start, enter in bucle mode in the start.
For this reasson, now I have other rom, but need the original stock rom.
Thanks in advanced!!

wonder_skydive said:
Hello.
In the first time, sorry for my english.
I have a HTC One M7 with this:
Tampered
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35-3218.16
OpenDSP-v35.120.274.0718
OS-
eMMC-boot 2048MB
Nov 16 2015,20:23:35.28773
In this moment, I use other ROM, I need install original stock rom.
A few months ago I try to made this (using some instructions and files of the htc1guru) but I was have problem, install fine (with android 4.x) and in the sewcond or third update of the system by HTC, when restart, not start the phone, try this operation 3 or 4 times, and always the same result, after this upgrade, when restart phone, not start, enter in bucle mode in the start.
For this reasson, now I have other rom, but need the original stock rom.
Thanks in advanced!!
Click to expand...
Click to collapse
Please post your "fastboot getvar all" output (don't post your imei/serialno)

Thank you!
alray said:
Please post your "fastboot getvar all" output (don't post your imei/serialno)
Click to expand...
Click to collapse
This is the info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3931mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
Again, thank you!

Please, somebody can help me?
I search info, but I don't view and when I was try, I have a error that I indicate above
Thanks in advance :good:

wonder_skydive said:
Please, somebody can help me?
I search info, but I don't view and when I was try, I have a error that I indicate above
Thanks in advance :good:
Click to expand...
Click to collapse
flash the 7.19.401.51 RUU
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

alray said:
flash the 7.19.401.51 RUU
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
I need block the bootloader for install this ruu?
Thank you very much!

wonder_skydive said:
I need block the bootloader for install this ruu?
Thank you very much!
Click to expand...
Click to collapse
Yes you must relock the bootloader to flash a RUU when your phone is S-ON
Code:
fastboot oem lock

alray said:
Yes you must relock the bootloader to flash a RUU when your phone is S-ON
Code:
fastboot oem lock
Click to expand...
Click to collapse
Ok, thanks
I have doubt about install, my apologies for this doubt, I feel a little absurd...
I need a stock recovery? If its yes, I don't have and I don't know how to flash.
At the moment, never flash my phone with a RUU, I search info about flash, and view that, its possible I need stock recovery ( I don't have) and in all posts, indicate a .exe "auto install".
This ruu is a .zip and I don't know how to flash...
I work in linux but also I have windows.
Again, my apologies, I feel a little embarrassed.
Thanks in advenced.

wonder_skydive said:
I need a stock recovery? If its yes, I don't have and I don't know how to flash.
Click to expand...
Click to collapse
You don't need to flash the stock recovery back before flashing the ruu. The stock recovery is included in the RUU and will be flashed automatically at the same time.
This ruu is a .zip and I don't know how to flash...
I work in linux but also I have windows.
Click to expand...
Click to collapse
To flash a ruu.zip you need to have fastboot installed on your computer. Newer RUU (starting with 7.xx.xxx.x) requires to use a fastboot.exe version distributed by HTC (often referred as htc_fastboot.exe), The regular fastboot.exe you'll find in the android sdk tool will not work for these ruu. You can download htc_fastboot from here (just save it in the same folder where you already have your regular fastboot.exe and adb.exe). Btw make sure the RUU file is in the same folder.
Reboot your phone in bootloader mode and make sure you can see "FASTBOOT USB" in red
Start a command windows from your adb/fastboot folder
To relock your bootloader, type:
Code:
fastboot oem lock
Then hit Enter. Your phone will reboot automatically
Reboot it again in bootloader mode and again make sure "FASTBOOT USB" in showing in red characters
Type:
Code:
fastboot oem rebootRUU
and hit Enter (note that fastboot commands are case sensitive so don't forget "RUU" are capital letters). Your phone will reboot in RUU mode (a black screen with a silver HTC logo). At this point your phone is ready to flash the RUU and waiting for the flash command, type:
Code:
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
The flash process will start. Don't touch anything until it's completed: your phone should reboot twice during the process 1st time in the middle of the flash and it will go back in ruu mode by itself and continue the flashing process. The 2nd time should make your phone reboot in the rom at the welcome/setup screen. Do not disconnect or play with your phone or computer until it's rebooted at the welcome screen.

alray said:
You don't need to flash the stock recovery back before flashing the ruu. The stock recovery is included in the RUU and will be flashed automatically at the same time.
To flash a ruu.zip you need to have fastboot installed on your computer. Newer RUU (starting with 7.xx.xxx.x) requires to use a fastboot.exe version distributed by HTC (often referred as htc_fastboot.exe), The regular fastboot.exe you'll find in the android sdk tool will not work for these ruu. You can download htc_fastboot from here (just save it in the same folder where you already have your regular fastboot.exe and adb.exe). Btw make sure the RUU file is in the same folder.
Reboot your phone in bootloader mode and make sure you can see "FASTBOOT USB" in red
Start a command windows from your adb/fastboot folder
To relock your bootloader, type:
Code:
fastboot oem lock
Then hit Enter. Your phone will reboot automatically
Reboot it again in bootloader mode and again make sure "FASTBOOT USB" in showing in red characters
Type:
Code:
fastboot oem rebootRUU
and hit Enter (note that fastboot commands are case sensitive so don't forget "RUU" are capital letters). Your phone will reboot in RUU mode (a black screen with a silver HTC logo). At this point your phone is ready to flash the RUU and waiting for the flash command, type:
Code:
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
The flash process will start. Don't touch anything until it's completed: your phone should reboot twice during the process 1st time in the middle of the flash and it will go back in ruu mode by itself and continue the flashing process. The 2nd time should make your phone reboot in the rom at the welcome/setup screen. Do not disconnect or play with your phone or computer until it's rebooted at the welcome screen.
Click to expand...
Click to collapse
In the first time, thank you very much for your help and explanation.
Your directions have been very helpful and have helped me to learn a lot. Thank you.
I made all steps like you indicate, in the last step, on you indicate this:
alray said:
The flash process will start. Don't touch anything until it's completed: your phone should reboot twice during the process 1st time in the middle of the flash and it will go back in ruu mode by itself and continue the flashing process. The 2nd time should make your phone reboot in the rom at the welcome/setup screen. Do not disconnect or play with your phone or computer until it's rebooted at the welcome screen.
Click to expand...
Click to collapse
I wait to finish all, in terminal windows, appears that, htc_fastboot was finished (with any error), all ok, but the phone appears a progress bar stop at 80 or 90%.
I wai for a 10-20 or 30 minutes, and the progress bar was continue stoped.
I try in terminal windows type: htc_fastboot reboot (I view this in the past in some post) and then the phone was reboot.
And yes, the phone are flashed and start all fine!!
And a doubt: this ruu contain the last rom? I question this because, after config the phone, I view that, not have any system update, and for example, in menu, the colour of screen in menu are black, and I remember that, in some update this colour screen menu, was changed to blue.
Again, thank you very much for your details and help!!!
It's a pleasure, few people help / teach so well.
Regards!

wonder_skydive said:
You don't need to flash the stock recovery back before flashing the ruu. The stock recovery is included in the RUU and will be flashed automatically at the same time.
To flash a ruu.zip you need to have fastboot installed on your computer. Newer RUU (starting with 7.xx.xxx.x) requires to use a fastboot.exe version distributed by HTC (often referred as htc_fastboot.exe), The regular fastboot.exe you'll find in the android sdk tool will not work for these ruu. You can download htc_fastboot from here (just save it in the same folder where you already have your regular fastboot.exe and adb.exe). Btw make sure the RUU file is in the same folder.
Reboot your phone in bootloader mode and make sure you can see "FASTBOOT USB" in red
Start a command windows from your adb/fastboot folder
To relock your bootloader, type:
Then hit Enter. Your phone will reboot automatically
Reboot it again in bootloader mode and again make sure "FASTBOOT USB" in showing in red characters
Type:
and hit Enter (note that fastboot commands are case sensitive so don't forget "RUU" are capital letters). Your phone will reboot in RUU mode (a black screen with a silver HTC logo). At this point your phone is ready to flash the RUU and waiting for the flash command, type:
In the first time, thank you very much for your help and explanation.
Your directions have been very helpful and have helped me to learn a lot. Thank you.
I made all steps like you indicate, in the last step, on you indicate this:
I wait to finish all, in terminal windows, appears that, htc_fastboot was finished (with any error), all ok, but the phone appears a progress bar stop at 80 or 90%.
I wai for a 10-20 or 30 minutes, and the progress bar was continue stoped.
I try in terminal windows type: htc_fastboot reboot (I view this in the past in some post) and then the phone was reboot.
And yes, the phone are flashed and start all fine!!
And a doubt: this ruu contain the last rom? I question this because, after config the phone, I view that, not have any system update, and for example, in menu, the colour of screen in menu are black, and I remember that, in some update this colour screen menu, was changed to blue.
Again, thank you very much for your details and help!!!
It's a pleasure, few people help / teach so well.
Regards!
Click to expand...
Click to collapse
Yes this is the latest version. You're welcome