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!

[Q] HTC One dead!

Guys I have big problems!
I have a htc one with 1.28.401.7 firmware, s-on, unrooted and unlocked bootloader. Hboot version is 1.44
I tried to install ota update which was corrupted. It screwed up the entire device! I could not go into recovery, i could not factory reset
I tried to reflash the RUU but it didnt work.
I tried installing custom recovery but it used to boot for a second and reboot to rom.
I have no idea what to do!
And now the device has gone dead!
Even if i connect it to the charger the notification light doesnt light up...holding power button doesnt help, power button+volume down doesnt help!
I tried rebooting in adb but it says error device offline!
Please please please tell me what i should do!
Thanks in advance!

anibjoshi said:
Guys I have big problems!
I have a htc one with 1.28.401.7 firmware, s-on, unrooted and unlocked bootloader. Hboot version is 1.44
I tried to install ota update which was corrupted. It screwed up the entire device! I could not go into recovery, i could not factory reset
I tried to reflash the RUU but it didnt work.
I tried installing custom recovery but it used to boot for a second and reboot to rom.
I have no idea what to do!
And now the device has gone dead!
Even if i connect it to the charger the notification light doesnt light up...holding power button doesnt help, power button+volume down doesnt help!
I tried rebooting in adb but it says error device offline!
Please please please tell me what i should do!
Thanks in advance!
Click to expand...
Click to collapse
Try this guide here. If you don't understand something, I'll help you!
http://forum.xda-developers.com/showthread.php?t=2632736

LibertyMarine said:
Try this guide here. If you don't understand something, I'll help you!
http://forum.xda-developers.com/showthread.php?t=2632736
Click to expand...
Click to collapse
Okay, so the phone started up again...I have adb and fastboot working.
I had installed twrp and tried to enter it..
But it boots for a second...shows "Entering recovery" but then reboots back to rom..and no matter which recovery i try, it doesnot enter the recovery
what do i do now? Please help
Thanks

anibjoshi said:
Okay, so the phone started up again...I have adb and fastboot working.
I had installed twrp and tried to enter it..
But it boots for a second...shows "Entering recovery" but then reboots back to rom..and no matter which recovery i try, it doesnot enter the recovery
what do i do now? Please help
Thanks
Click to expand...
Click to collapse
install twrp again
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot-bootloader

LibertyMarine said:
Try this guide here. If you don't understand something, I'll help you!
http://forum.xda-developers.com/showthread.php?t=2632736
Click to expand...
Click to collapse
Buddy I need a lot of help!
I will tell u what happened in steps:
1. As written in original post, i tried to install an ota update which got corrupted and it screwed up the entire phone
I couldnt boot into recovery, revone was not working, phone was getting hanged every now and then..
2. I had an unlocked bootloader at that time. I relocked the bootloader to flash the RUU again
3. The RUU failed, and the phone was stuck at the grey HTC screen with 4 exclamation marks on 4 corners
4. I unplugged the device and i got the bootloader screen which showed this message:
Error[152]
Parsing...[downloaded ZIP]
Reset HTC Debug Flag
1 BOOT - OK
2 RECOVERY - OK
3 SYSTEM - OK
4 SPLASH1 - OK
5 USERDATA - OK
6 SBL2 - Fail-PU
7 SBL3 - Fail-PU
8 TRUST_ZONE - Fail-PU
9 RPM - Fail-PU
10 ADSP - OK
11 PG2FS_SPCUSTOM -OK
12 TP - OK
13 SBL1 - Bypass-S
14 SBL1 - Bypass-S
15 SBL1 - Fail-PU
16 RADIO_V2 - OK
17 RADIO_CUST - OK
Partition update fail!
Update Fail!
5. Long press of power, volume up, down nothing works
6. adb doesnt detect the device, but fastboot works
7. I saw your guide and tried to reinstall recovery but it gives this:
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.094s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.109s
What should i do now!
I tried fastboot oem boot but it gives the green htc sign and gets stuck there...nothing moves ahead
What is the state of the device and how do i fix it?
Thanks a lot

LibertyMarine said:
Try this guide here. If you don't understand something, I'll help you!
http://forum.xda-developers.com/showthread.php?t=2632736
Click to expand...
Click to collapse
fastboot getvar all shows this...if it is of any use
C:\HTCOneRoot>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: removed by me
(bootloader) imei: removed by me
(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: 3945mV
(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.188s

LibertyMarine said:
Try this guide here. If you don't understand something, I'll help you!
http://forum.xda-developers.com/showthread.php?t=2632736
Click to expand...
Click to collapse
I tried installing recovery again and again..i got different errors each time
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.000s
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
FAILED (status malformed (0 bytes))
finished. total time: 0.000s
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
^C
What on earth is going on! Please help me!
Im panicking here!

anibjoshi said:
I tried installing recovery again and again..i got different errors each time
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.000s
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
FAILED (status malformed (0 bytes))
finished. total time: 0.000s
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
^C
What on earth is going on! Please help me!
Im panicking here!
Click to expand...
Click to collapse
1) Were you in rebootRUU while flashing like this(quoted post)? or in normal fastboot?
2) Have you tried "Case 2" of my guide?
ok, first calm down !!!
Edit.... you are s on.... Damnit this won't work here....
Now try this RUU. This will reset your entire phone.!
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
And flash it in the RUU mode.... I think you are stuck in it...
fastboot flash zip "C:\path\firmware.zip"
It wil first give you an Error message... something like that:
Code:
C:\Android\com>fastboot flash zip "C:\path\firmware.zip"
sending 'zip' (35220 KB)...
OKAY [ 2.839s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) [COLOR="Red"][B]...... Successful[/B][/COLOR]
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.438s
After that INSTANTLY reflash it by using the same command(DON'T REBOOT LONG AS THERE WAS AN ERROR BY FLASHING HBOOT I WOULD INEVITABLY AND INSTANTANEOUSLY BRICK YOUR DEVICE!):
Code:
fastboot flash zip "C:\path\firmware.zip"
Now you get a long output...
Code:
[...]
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 49.443s]
finished. total time: 52.280s
If there's written okay, just reboot....! The bar on the phone won't get to 100%
---------- Post added at 10:10 AM ---------- Previous post was at 10:05 AM ----------
anibjoshi said:
[...]
What on earth is going on! Please help me!
Im panicking here!
Click to expand...
Click to collapse
Tell me where you are with your phone.
BOOTLOADER?
FASTBOOT?
rebootRUU?
so I can provide better help
---------- Post added at 10:22 AM ---------- Previous post was at 10:10 AM ----------
anibjoshi said:
Buddy I need a lot of help!
I will tell u what happened in steps:
1. As written in original post, i tried to install an ota update which got corrupted and it screwed up the entire phone
I couldnt boot into recovery, revone was not working, phone was getting hanged every now and then..
2. I had an unlocked bootloader at that time. I relocked the bootloader to flash the RUU again
3. The RUU failed, and the phone was stuck at the grey HTC screen with 4 exclamation marks on 4 corners
4. I unplugged the device and i got the bootloader screen which showed this message:
Error[152]
Parsing...[downloaded ZIP]
Reset HTC Debug Flag
1 BOOT - OK
2 RECOVERY - OK
3 SYSTEM - OK
4 SPLASH1 - OK
5 USERDATA - OK
6 SBL2 - Fail-PU
7 SBL3 - Fail-PU
8 TRUST_ZONE - Fail-PU
9 RPM - Fail-PU
10 ADSP - OK
11 PG2FS_SPCUSTOM -OK
12 TP - OK
13 SBL1 - Bypass-S
14 SBL1 - Bypass-S
15 SBL1 - Fail-PU
16 RADIO_V2 - OK
17 RADIO_CUST - OK
Partition update fail!
Update Fail!
5. Long press of power, volume up, down nothing works
6. adb doesnt detect the device, but fastboot works
7. I saw your guide and tried to reinstall recovery but it gives this:
C:\HTCOneRoot>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.094s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.109s
What should i do now!
I tried fastboot oem boot but it gives the green htc sign and gets stuck there...nothing moves ahead
What is the state of the device and how do i fix it?
Thanks a lot
Click to expand...
Click to collapse
Ok, are you now still unlocked? Or locked? if you are locked... we can try things,.. but I don't think it will work...
And since you were locked.... there shouldn't be an danger of flashing the RUU... because it doesn't flash the bootloader...

hey @anibjoshi, you'll do better if you just have one thread open on your problems (see also http://forum.xda-developers.com/showthread.php?t=2630333).
stop panicking and start listening to the excellent advice @LibertyMarine is giving you and maybe you'll get your phone working again.

Maybe this will work for you: http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html
Good luck!

re:
I had same problem few days ago, after that famous 4.4.2 update, my phone was screwed. I played a lot around with it, then I came to thingie that my /data partition was gone, so I had to recover it, and what Ronnymes in post before mine said, did help me a lot (link), I got my /data partition back, but you need to be really careful when working with all that...
Now since I read a bit this thread, I'd say you have problem not entering recovery at all (or at least just splashscreen of recovery) and then reboot. Or when you let your phone normal boot into OS, it ends rebooting in infinite loop.
I had same problem, you wouldn't believe what I did.
So to solve this problem I did next, but you must have working drivers on computer, so that it recognizes phone while it is in fastboot:
- Hold Vol - rocker and power button to enter bootloader
- select Fastboot with volume rockers and hit power button to enter it
- connect phone to PC while in Fastboot (it should change from Fastboot to Fastboot USB)
- open Command Prompt on you PC where you have all necessary files for fastboot and adb
- type (without quotes): "fastboot devices" just to be sure that device is attached, it should write down serial no of phone and fastboot after that
- now type: "fastboot oem lock" this will lock your bootloader
- after this do the process of unlocking bootloader by help of htcdev.com
- when you done unlocking bootloader flash whatever custom recovery to phone (I like CWM)
After these steps you should have working bootloader and recovery... now make sure that all your partitions on phone are in tact, be careful when doing that because not every HTC One has same addresses for all partitions, there is command for checking partition table on you device.
Cheers...

LibertyMarine said:
1) Were you in rebootRUU while flashing like this(quoted post)? or in normal fastboot?
2) Have you tried "Case 2" of my guide?
ok, first calm down !!!
Edit.... you are s on.... Damnit this won't work here....
Now try this RUU. This will reset your entire phone.!
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
And flash it in the RUU mode.... I think you are stuck in it...
fastboot flash zip "C:\path\firmware.zip"
It wil first give you an Error message... something like that:
Code:
C:\Android\com>fastboot flash zip "C:\path\firmware.zip"
sending 'zip' (35220 KB)...
OKAY [ 2.839s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) [COLOR="Red"][B]...... Successful[/B][/COLOR]
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.438s
After that INSTANTLY reflash it by using the same command(DON'T REBOOT LONG AS THERE WAS AN ERROR BY FLASHING HBOOT I WOULD INEVITABLY AND INSTANTANEOUSLY BRICK YOUR DEVICE!):
Code:
fastboot flash zip "C:\path\firmware.zip"
Now you get a long output...
Code:
[...]
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 49.443s]
finished. total time: 52.280s
If there's written okay, just reboot....! The bar on the phone won't get to 100%
---------- Post added at 10:10 AM ---------- Previous post was at 10:05 AM ----------
Tell me where you are with your phone.
BOOTLOADER?
FASTBOOT?
rebootRUU?
so I can provide better help
---------- Post added at 10:22 AM ---------- Previous post was at 10:10 AM ----------
Ok, are you now still unlocked? Or locked? if you are locked... we can try things,.. but I don't think it will work...
And since you were locked.... there shouldn't be an danger of flashing the RUU... because it doesn't flash the bootloader...
Click to expand...
Click to collapse
Sorry for replying so late...i was travelling to another city..
The device is stuck in rebootRUU
I tried flashing recovery in rebootRUU...was that the reason it failed?
I am relocked now...relocked, s-on
I will flash the zip twice as u instructed...do u have any other specific instructions regarding that flashing?
If the flashing fails for the second time, what do i do? will long press still brick the device?
I am downloading that zip right now...but it will take some time to download..so maybe i will wait for your reply on this before i flash
And i really really appreciate how much you are doing for me...u are a life saver
I just hope the device starts working soon
Thanks

rex1825 said:
I had same problem few days ago, after that famous 4.4.2 update, my phone was screwed. I played a lot around with it, then I came to thingie that my /data partition was gone, so I had to recover it, and what Ronnymes in post before mine said, did help me a lot (link), I got my /data partition back, but you need to be really careful when working with all that...
Now since I read a bit this thread, I'd say you have problem not entering recovery at all (or at least just splashscreen of recovery) and then reboot. Or when you let your phone normal boot into OS, it ends rebooting in infinite loop.
I had same problem, you wouldn't believe what I did.
So to solve this problem I did next, but you must have working drivers on computer, so that it recognizes phone while it is in fastboot:
- Hold Vol - rocker and power button to enter bootloader
- select Fastboot with volume rockers and hit power button to enter it
- connect phone to PC while in Fastboot (it should change from Fastboot to Fastboot USB)
- open Command Prompt on you PC where you have all necessary files for fastboot and adb
- type (without quotes): "fastboot devices" just to be sure that device is attached, it should write down serial no of phone and fastboot after that
- now type: "fastboot oem lock" this will lock your bootloader
- after this do the process of unlocking bootloader by help of htcdev.com
- when you done unlocking bootloader flash whatever custom recovery to phone (I like CWM)
After these steps you should have working bootloader and recovery... now make sure that all your partitions on phone are in tact, be careful when doing that because not every HTC One has same addresses for all partitions, there is command for checking partition table on you device.
Cheers...
Click to expand...
Click to collapse
I cant get inside fastboot or recovery or anything...im stuck at the rebootRUU screen

anibjoshi said:
Sorry for replying so late...i was travelling to another city..
The device is stuck in rebootRUU
I tried flashing recovery in rebootRUU...was that the reason it failed?
I am relocked now...relocked, s-on
I will flash the zip twice as u instructed...do u have any other specific instructions regarding that flashing?
If the flashing fails for the second time, what do i do? will long press still brick the device?
I am downloading that zip right now...but it will take some time to download..so maybe i will wait for your reply on this before i flash
And i really really appreciate how much you are doing for me...u are a life saver
I just hope the device starts working soon
Thanks
Click to expand...
Click to collapse
Hmm, I hope this works... since you are hboot 1.44 I think this RUU should be a working one... I have here quoted what you have to do in case of an error:
Error handling strategies:​IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)​
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successfull firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work with ADB and Fastboot.​
Thanks @Sneakyghost for writing these excellent error handling strat.
here is the original thread: http://forum.xda-developers.com/showthread.php?t=2316726
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
Ronnymes said:
Maybe this will work for you: http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html
Good luck!
Click to expand...
Click to collapse
he is relocked and s on

anibjoshi said:
Guys I have big problems!
I have a htc one with 1.28.401.7 firmware, s-on, unrooted and unlocked bootloader. Hboot version is 1.44
I tried to install ota update which was corrupted. It screwed up the entire device! I could not go into recovery, i could not factory reset
I tried to reflash the RUU but it didnt work.
I tried installing custom recovery but it used to boot for a second and reboot to rom.
I have no idea what to do!
And now the device has gone dead!
Even if i connect it to the charger the notification light doesnt light up...holding power button doesnt help, power button+volume down doesnt help!
I tried rebooting in adb but it says error device offline!
Please please please tell me what i should do!
Thanks in advance!
Click to expand...
Click to collapse
This can be very hard to recover and I dare say it's nearly impossible via a forum, best would be to have the phone in my hands if I was to help here.
However, since you did almost nothing bad except the unlock, I'd try to talk to HTC customer support, then try to get your case elevated so a higher support office can waive off the bills you'd get from the service center.
Arguments:
The device got messed up from an ota, which is a safe process designed to not harm the device. Any mishap there would normally be covered under warranty. Now, you'd admit that you unlocked, be honest, don't lie, but also point out that you did not even root the device. Neither did you touch Security.
So, in this case, there is no reasonable argument to deny you warranty.
Although legally you agreed to losing warranty entitlement when unlocking.
mobile Viper bite

Sneakyghost said:
[...]
Click to expand...
Click to collapse
Is it OK for you that I used your error handling strategies?

LibertyMarine said:
Hmm, I hope this works... since you are hboot 1.44 I think this RUU should be a working one... I have here quoted what you have to do in case of an error:
Error handling strategies:​IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)​
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successfull firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work with ADB and Fastboot.​
Thanks @Sneakyghost for writing these excellent error handling strat.
here is the original thread: http://forum.xda-developers.com/showthread.php?t=2316726
Click to expand...
Click to collapse
When I tried to flash the RUU.exe, it did not work...it gave me the error that I have posted...can you tell me what that error meant?
Cuz i feel i will get the same error when I run the RUU.zip
So if the same thing happens I can be better ready for it

Sneakyghost said:
This can be very hard to recover and I dare say it's nearly impossible via a forum, best would be to have the phone in my hands if I was to help here.
However, since you did almost nothing bad except the unlock, I'd try to talk to HTC customer support, then try to get your case elevated so a higher support office can waive off the bills you'd get from the service center.
Arguments:
The device got messed up from an ota, which is a safe process designed to not harm the device. Any mishap there would normally be covered under warranty. Now, you'd admit that you unlocked, be honest, don't lie, but also point out that you did not even root the device. Neither did you touch Security.
So, in this case, there is no reasonable argument to deny you warranty.
Although legally you agreed to losing warranty entitlement when unlocking.
mobile Viper bite
Click to expand...
Click to collapse
I dont have warranty..lol
Also, the device did boot up later...but still couldnt enter recovery or anything..but still could boot to rom
I was unlocked so i relocked it and ran an ruu.exe
It failed and now the phone is stuck in rebootRUU
adb doesnt work but fastboot does
Does that make my chances better? *hoping

Fastboot reboot
That will get your device out of ruu mode.
Let's us know if it does

SaHiLzZ said:
Fastboot reboot
That will get your device out of ruu mode.
Let's us know if it does
Click to expand...
Click to collapse
I tried that...the device just goes blank and then comes back to the rebootRUU screen
I guess thats all thats left in the device...everything else is gone

[Q] HTC One Bootloop - Cannot unlock bootloader

Hi All,
My phone suddenly started doing a Bootloop, please notice that I haven't messed up with any custom ROMs, flashing, etc... the only thing that I may guess that happened here is that my phone got a little wet a couple of days ago. The screen won't came up so I dry it using a hairdryer and started working normally. Two days later I got an error that Foursquare app was failing and then I got into the Bootloop that I cannot get rid of....
I'm totally new with flashing phones, rooting, unlocking, etc... but I'm a developer, so, I can learn much easily.
I was reading some forums and solutions but I could not get it work.
Here are the details:
1- The phone is a HTC One M7
2- I'm able to enter to "Recovery mode" screen
3- If i scroll down to "Recovery" or "Factory Reset" the phone try to enter to those modes but after a few seconds of black screen I got an image with a phone with a red warning icon inside. So, I cannot enter to recovery nor do a factory reset
4- If I try to use "adb" commands looks like the bootloop is avoiding me to recognize the device. I tried "adb devices" several times while the phone is rebooting and I see the phone appearing in the list in the middle of the reboot but the status is "offline", then, it changed to "unauthorized" and then it disappears. I also tried "adb wait-for-device" but does not worked and sometimes it said that there is more than one device connected (if i tried adb devices again, appear my device a lot of times but always offline).
I also tried a .bat file to wait for the device and do a shell stop to be able to "freeze" where the phone is accessible, but did not worked neither.
I guess that I don't have debugging enable on my device and that is why i cannot use the adb commands of see the phone connected. I saw that adb will work even with debugging disabled in recovery, but like i mentioned before, i cannot enter to recovery.
5- I was able to enter to "fastboot mode" and my phone connected to USB. If i use fastboot devices, my device appears and looks fine.
6- I tried to unlock the bootloader using the htcdev.com. I followed the steps and looks simple, I don't think i messed something there. I was able to get the phone token, submit, get the Unlock_code.bin, flash the code using fastboot, I got the screen to select yes/no to unlock the bootloader, and at this point everything looks great. I selected Yes, and my phone reboot and still on bootloop (as expected), but If i enter again to recovery mode, the phone is still "*** LOCKED ***". I tried the process (get toke, submit, flash bin, etc) lot of times, but with no result, phone is still appears as Locked.
7- My idea on #6 was to flash the recovery img and try to make the recovery to work, but to be able to flash the recovery i need my bootloader to be unlocked. I tried anyways to flash the recovery but as expected if failed :
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.201s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.172s
8- I saw that there is another method to unlock the bootloader but is using adb, which on #4 i explained i cannot use.
Any idea? thoughts?
Thanks in advance,
Juan.

first USB debugging is only for when you are booted into a rom, it doesn't apply to recovery or bootloader.
Red triangle with exclamation mark is normal, that's the stock recovery.
next, you wont beable to adb devices whilst its bootlooping, that's why that's not working, adb is for in a rom or in recovery, fastboot commands are for when your in the bootloader
So reboot your phone to bootloader mode, this is where you saw the list with options to factory reset and reboot and recovery etc, this is the only thing you need to use for now, and only fastboot commands will work there, once plugged into your computer it should say on the screen "fastboot USB"
post your "fastboot getvar all" without quote marks

Seanie280672 said:
first USB debugging is only for when you are booted into a rom, it doesn't apply to recovery or bootloader.
Red triangle with exclamation mark is normal, that's the stock recovery.
next, you wont beable to adb devices whilst its bootlooping, that's why that's not working, adb is for in a rom or in recovery, fastboot commands are for when your in the bootloader
So reboot your phone to bootloader mode, this is where you saw the list with options to factory reset and reboot and recovery etc, this is the only thing you need to use for now, and only fastboot commands will work there, once plugged into your computer it should say on the screen "fastboot USB"
post your "fastboot getvar all" without quote marks
Click to expand...
Click to collapse
Hi Seanie, thanks for the quick response.
Here is the result of fastboot getvar all command:
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3451mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Click to expand...
Click to collapse
J.

first thing is first, remove your serial number and imei from your output, its dangerous to post them.
also get your battery charged up to 50% or more,

Seanie280672 said:
first thing is first, remove your serial number and imei from your output, its dangerous to post them.
also get your battery charged up to 50% or more,
Click to expand...
Click to collapse
Ohh, just removed.
About battery, I cannot turn off my phone (even if trying from fastboot "power off" option), that is why i keep it with low battery so it power off when it's empty.
Do you thing battery level will change my results? If yes, after charging my batter, what i should do?
Thanks,
J.

htc butterfly a 9060 bootloop
I also have something that type of problem what u said ....
By missing i delete some some files from system/bin. And after that my phone boot loop ....nothing is working..... my bootloader is working but is locked .asb not working ..fastboot working ......i have recovery and boot.img.....can can one help ....plzz ..i m crying.....its really big mistake...:crying:

Htc butterfly s 9060 bootloop
garyplaton said:
Hi All,
My phone suddenly started doing a Bootloop, please notice that I haven't messed up with any custom ROMs, flashing, etc... the only thing that I may guess that happened here is that my phone got a little wet a couple of days ago. The screen won't came up so I dry it using a hairdryer and started working normally. Two days later I got an error that Foursquare app was failing and then I got into the Bootloop that I cannot get rid of....
I'm totally new with flashing phones, rooting, unlocking, etc... but I'm a developer, so, I can learn much easily.
I was reading some forums and solutions but I could not get it work.
Here are the details:
1- The phone is a HTC One M7
2- I'm able to enter to "Recovery mode" screen
3- If i scroll down to "Recovery" or "Factory Reset" the phone try to enter to those modes but after a few seconds of black screen I got an image with a phone with a red warning icon inside. So, I cannot enter to recovery nor do a factory reset
4- If I try to use "adb" commands looks like the bootloop is avoiding me to recognize the device. I tried "adb devices" several times while the phone is rebooting and I see the phone appearing in the list in the middle of the reboot but the status is "offline", then, it changed to "unauthorized" and then it disappears. I also tried "adb wait-for-device" but does not worked and sometimes it said that there is more than one device connected (if i tried adb devices again, appear my device a lot of times but always offline).
I also tried a .bat file to wait for the device and do a shell stop to be able to "freeze" where the phone is accessible, but did not worked neither.
I guess that I don't have debugging enable on my device and that is why i cannot use the adb commands of see the phone connected. I saw that adb will work even with debugging disabled in recovery, but like i mentioned before, i cannot enter to recovery.
5- I was able to enter to "fastboot mode" and my phone connected to USB. If i use fastboot devices, my device appears and looks fine.
6- I tried to unlock the bootloader using the htcdev.com. I followed the steps and looks simple, I don't think i messed something there. I was able to get the phone token, submit, get the Unlock_code.bin, flash the code using fastboot, I got the screen to select yes/no to unlock the bootloader, and at this point everything looks great. I selected Yes, and my phone reboot and still on bootloop (as expected), but If i enter again to recovery mode, the phone is still "*** LOCKED ***". I tried the process (get toke, submit, flash bin, etc) lot of times, but with no result, phone is still appears as Locked.
7- My idea on #6 was to flash the recovery img and try to make the recovery to work, but to be able to flash the recovery i need my bootloader to be unlocked. I tried anyways to flash the recovery but as expected if failed :
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.201s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.172s
8- I saw that there is another method to unlock the bootloader but is using adb, which on #4 i explained i cannot use.
Any idea? thoughts?
Thanks in advance,
Juan.
Click to expand...
Click to collapse
i also have all these problem what u have with your phone..can u please tell is your problem solved or not if yes so please share with i m crying right now with this..please help

abby1996 said:
i also have all these problem what u have with your phone..can u please tell is your problem solved or not if yes so please share with i m crying right now with this..please help
Click to expand...
Click to collapse
Hi, after trying everything that I found in the forums, google, etc, without been able to work around it, I took my phone to two places where they fix cell phones but both of them told me "it can't be fixed". So, I lost my hope and currently i'm still keeping the broken phone but already got another one

Hello,
My htc butterfly s 9060 bootlooping with locked bootloader was solved.... I unlocked my bootloader by htcdev method... Its working... U also try this again and again bcoz its only method toh unlock the bootloader..... U also search all correct steps for this method....by searching on htc butterfly s unlocked bootloader threats.. And follow all steps... Bcoz i direct use htcdev site to unlock is not working... After that i used these steps for unlock bootloader...
May be help you
Abby
Sent from my HTC 9060 using XDA Free mobile app

I don't buy the 'can't be done' anymore after my issue for the past 24 hours. Your only way forward is to unlock the phone though. When I get back to the pc (using my now working phone!!) I'll put my notes up for you to work through.

I'm going to write this on the assumption that you followed the correct process to get your unlock token from HTC and you now have that.
BEFORE you do any of this, charge your phone. If you're having trouble powering it off, I found that having it connected via usb to my pc and then just holding the power off button or even the power off and volume down button (while it was on) did the trick. The LED should be lit red even if you don't have a visible indicator of what level the battery is at.
In the meantime:
#1 Go to your desktop on your pc. Set up a new folder and call it HTC.
#2 Into this folder extract everything within the attached zip. Don't put it into a further sub directory, just fill the HTC folder with the zip's contents. These are the ADB dll's and HTC's Fastboot programme. On top, I've included version 2.8.6.2 of TWRP.
#3 Put your Unlock_code.bin from the HTC email you received into this same folder.
-The contents of your folder should look like this:
{
"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"
}
#3 When your phone has charged for at least an hour (make it two to be safe) get it onto the bootloader screen and onto the fastboot menu. You should still have the phone connected to the pc and the line should now say 'fastboot usb'
#4 Open up a cmd terminal. Assuming that you know how this is done, make sure that it is reading c:\<path>\HTC (where path is whatever it is where htc is. On mine it was c:\users\username\desktop\HTC
#5 type the following in: fastboot flash unlocktoken Unlock_code.bin (then wait to see what it says.. if successful then proceed to #6)
#6 type the following in: fastboot reboot -bootloader
Tell us how you get on.

abby1996 said:
Hello,
My htc butterfly s 9060 bootlooping with locked bootloader was solved.... I unlocked my bootloader by htcdev method... Its working... U also try this again and again bcoz its only method toh unlock the bootloader..... U also search all correct steps for this method....by searching on htc butterfly s unlocked bootloader threats.. And follow all steps... Bcoz i direct use htcdev site to unlock is not working... After that i used these steps for unlock bootloader...
May be help you
Abby
Click to expand...
Click to collapse
Make sure you don't flash files from this forum (M7), dowload files only from your device forum
Butterfly S forum here: http://forum.xda-developers.com/htc-butterfly-s

[Q] MODs Please close this thread!!!!! Thank you

MODs please delete this thread
Hi all,
I've been wrecking my brains out, can anyone help.
My M7ul is stuck in recovery loop, doesn't matter what rom I push using adb and flash it keeps on going booting into recovery. I cannot change the recovery from TWRP even tho using adb it says I have tried to flash new recovery twrp and cwm it still reverts back to twrp 2.6.3.3.
I have also used the method http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html to wipe the data partition, it shows that it has wiped it but as it reboots all the files that were suppose to be wiped is still there.
I have tried to load stock rom but as soon as it restarts to load the bootloader the phone boots into recovery and the pc doesn't pick up the phone and the process stops. I have tried to relock the bootloader and it doesn't lock.
Any ideas and help would be appreciated.

touchplus said:
Hi all,
I've been wrecking my brains out, can anyone help.
My M7ul is stuck in recovery loop, doesn't matter what rom I push using adb and flash it keeps on going booting into recovery. I cannot change the recovery from TWRP even tho using adb it says I have tried to flash new recovery twrp and cwm it still reverts back to twrp 2.6.3.3.
I have also used the method http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html to wipe the data partition, it shows that it has wiped it but as it reboots all the files that were suppose to be wiped is still there.
I have tried to load stock rom but as soon as it restarts to load the bootloader the phone boots into recovery and the pc doesn't pick up the phone and the process stops. I have tried to relock the bootloader and it doesn't lock.
Any ideas and help would be appreciated.
Click to expand...
Click to collapse
Try to flash a boot.img from you rom. You might have wiped it out.

Thank you, I'll try that and let you know.
Update;
no luck, it still reverts into the recovery loop.

touchplus said:
Thank you, I'll try that and let you know.
Update;
no luck, it still reverts into the recovery loop.
Click to expand...
Click to collapse
When you flashed the new recovery did you use the following commands:
In bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
If you don't erase the cache after you flash the recovery it does take properly.
You might give this new version of TWRP a try.

Hi Majmoz
I am grateful for your time in helping me, but I am not having any luck.
I have followed your instruction but to no avail, for some reason it will not flash a new recovery, the adb process shows its writing but it defaults back to the twrp 2.6.3.3. I have tried flashing the new one you linked and CWM but keeps on reverting back. The phone goes into the htc logo for about 10 sec and restarts again into old recovery.

touchplus said:
Hi Majmoz
I am grateful for your time in helping me, but I am not having any luck.
I have followed your instruction but to no avail, for some reason it will not flash a new recovery, the adb process shows its writing but it defaults back to the twrp 2.6.3.3. I have tried flashing the new one you linked and CWM but keeps on reverting back. The phone goes into the htc logo for about 10 sec and restarts again into old recovery.
Click to expand...
Click to collapse
@alray or @nkk71 Can you help with this.
touchplus: Can you post a fastboot getvar all with the imei and serialno removed? I think you will need a RUU to put all the pieces back together.

touchplus said:
Hi all,
I've been wrecking my brains out, can anyone help.
My M7ul is stuck in recovery loop, doesn't matter what rom I push using adb and flash it keeps on going booting into recovery. I cannot change the recovery from TWRP even tho using adb it says I have tried to flash new recovery twrp and cwm it still reverts back to twrp 2.6.3.3.
I have also used the method http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html to wipe the data partition, it shows that it has wiped it but as it reboots all the files that were suppose to be wiped is still there.
I have tried to load stock rom but as soon as it restarts to load the bootloader the phone boots into recovery and the pc doesn't pick up the phone and the process stops. I have tried to relock the bootloader and it doesn't lock.
Any ideas and help would be appreciated.
Click to expand...
Click to collapse
I hate to be the bearer of bad news, but this sounds like a hardware problem. I've seen one or two other people whose phones were "stuck in time", the ROM would boot up fine, but upon every reboot it would revert back to a previous state, even files (eg pictures) that were added or deleted would revert back.
TWRP 2.6.3.3 should be good for any ROM.
So first make sure you bootloader is UNLOCKED, then copy/paste command prompt output of everything you do, please check the Frequently Asked Question sticky page 3
and do all the steps mentioned there, in particular step D which will truly format everything (like the fix-data-htc-one article).
copy/paste your output back here, maybe we can spot something
best of luck

details
majmoz said:
@alray or @nkk71 Can you help with this.
touchplus: Can you post a fastboot getvar all with the imei and serialno removed? I think you will need a RUU to put all the pieces back together.
Click to expand...
Click to collapse
Hi Majmoz,
Here are the details, thanks again
c:\mini>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH38**********
(bootloader) imei: 357****************
(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: 3717mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I have downloaded the RUU from htcguru for HTC_001 but can't seem to load it on the phone, the ruu process goes to the first stage and reboots the phone and says waiting for bootloader but the phone boots up and goes straight into the htc logo and then restarts again and enters into recovery. I have tried to force the phone into bootloader mode after restart but it won't recognise the phone and installation process timeouts
Thank you again

nkk71 said:
I hate to be the bearer of bad news, but this sounds like a hardware problem. I've seen one or two other people whose phones were "stuck in time", the ROM would boot up fine, but upon every reboot it would revert back to a previous state, even files (eg pictures) that were added or deleted would revert back.
TWRP 2.6.3.3 should be good for any ROM.
So first make sure you bootloader is UNLOCKED, then copy/paste command prompt output of everything you do, please check the Frequently Asked Question sticky page 3
and do all the steps mentioned there, in particular step D which will truly format everything (like the fix-data-htc-one article).
copy/paste your output back here, maybe we can spot something
best of luck
Click to expand...
Click to collapse
Hi nkk71,
Thank you for getting involved in helping me, I have followed all steps from A -G
A- Please see attached image
B- I am able to get to into the bootloader- the bootloader is unlocked and has the word tampered written on top
C-
c:\mini>adb version
Android Debug Bridge version 1.0.31
c:\mini>fastboot devices
SH38XXXXXXXX fastboot
c:\mini>fastboot flash recovery twrp-2.7.1.2-m7.img (the recovery didn't update to 2.7.1.2 as you can see in the picture it reverted back)
sending 'recovery' (9940 KB)... OKAY
writing 'recovery'... OKAY
c:\mini>fastboot erase cache
erasing 'cache'... OKAY
c:\mini>fastboot reboot-bootloader
rebooting into bootloader... OKAY
D- See attached pictures
E- I have pushed the rom into the phone and installed it, it goes through the installation process without errors and reboots into htc logo for about 10 sec and then reboots again and goes back into recovery
F- Windows recognizes the phone
G- doesn't go through the bootup cycle instead phone starts and hangs at HTC logo for about 10 sec and restarts into recovery.
H- I have added an additional picture as I did a imgcrc in the bootloader menu just incase there is information that may help.
Thank you again.

found an error
Hi Guys,
I did another check using this command /sbin/e2fsck -n -f /dev/block/mmcblk0p37 listed on http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html. There is an error that showed up could this be the problem and if so how can I fix this, I have already tried the process from the link about 3 times but that error isn't fixed.
c:\mini>adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (1914292, counted=976600).
Fix? no
Free inodes count wrong (1677448, counted=1677418).
Fix? no
/dev/block/mmcblk0p37: ********** WARNING: Filesystem still has errors *********
*
/dev/block/mmcblk0p37: 26488/1703936 files (3.4% non-contiguous), 4901452/681574
4 blocks

touchplus said:
Hi nkk71,
Thank you for getting involved in helping me, I have followed all steps from A -G
H- I have added an additional picture as I did a imgcrc in the bootloader menu just incase there is information that may help.
Thank you again.
Click to expand...
Click to collapse
I think it's a hardware problem
the part where the rpm crc checksum is only 7 characters is not a good sign, and if you're flashing 2.1.7.2 properly, but it's still stuck with 2.6.3.3 would lead me to say it's a hardware issue.
you can still try running the 4.19.401.9 ruu: http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
you'll need to relock bootloader since you are S-ON, using "fastboot oem lock" for the RUU to be able to install
Best of luck
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
touchplus said:
Hi Guys,
I did another check using this command /sbin/e2fsck -n -f /dev/block/mmcblk0p37 listed on http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html. There is an error that showed up could this be the problem and if so how can I fix this, I have already tried the process from the link about 3 times but that error isn't fixed.
c:\mini>adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (1914292, counted=976600).
Fix? no
Free inodes count wrong (1677448, counted=1677418).
Fix? no
/dev/block/mmcblk0p37: ********** WARNING: Filesystem still has errors *********
*
/dev/block/mmcblk0p37: 26488/1703936 files (3.4% non-contiguous), 4901452/681574
4 blocks
Click to expand...
Click to collapse
yep, looks bad, you've already done two full formats (one using the original mk2fs and one using twrp), and the error comes back -> bad chip, needs a motherboard replacement
sorry

nkk71 said:
I think it's a hardware problem
the part where the rpm crc checksum is only 7 characters is not a good sign, and if you're flashing 2.1.7.2 properly, but it's still stuck with 2.6.3.3 would lead me to say it's a hardware issue.
you can still try running the 4.19.401.9 ruu: http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
you'll need to relock bootloader since you are S-ON, using "fastboot oem lock" for the RUU to be able to install
Best of luck
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
yep, looks bad, you've already done two full formats (one using the original mk2fs and one using twrp), and the error comes back -> bad chip, needs a motherboard replacement
sorry
Click to expand...
Click to collapse
Hi nkk71 and Majmoz,
Thank you very much for all your help. I guess its a dead end then :crying:,
I just wanted to try one last thing before I give up, but having a slight problem, I want force it load an RUU but I can't lock the bootloader, the phone restarts after the adb command but doesn't lock the bootloader, if I could somehow lock the bootloader then maybe I can try and load the RUU. If you have any ideas on how else I can lock the bootloader that would be a great.
this what I get from adb
c:\mini>fastboot oem lock
... (bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
When I attempt to put the phone in ruu mode using adb command the phone restarts and goes back into recovery- so this options doesn't work any other options you may have would be great
c:\mini>fastboot oem rebootRUU
< waiting for device >
... (bootloader) Start Verify: 3
OKAY