Database Develop

[Q] my hero can't boot into recovery .. Can anyone help me

my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help

Place this on the root of your sdcard. Boot into hboot (fastboot) and press the down volume key, that's hboot mode. It'll find the HERCIMG.zip, which is just the RUU and after it flashes you're phone will be back to stock.

DoonRoman said:
my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help
Click to expand...
Click to collapse
Im having the same exact error
what i did first is that i accessed the recovery mode without knowing and i did the wipe/factory default settings
it brought me to a black screen with only the top slider while that the recovery mode was working
later i installed the ruu software 2.27.651.6 and downloaded it from htc website , at the end of the installing it showed file error cant open
i thought i was just that software (and i didnt download it right) later i tried installing the 1.27 , 1.56 , 2.27.651.5 and the 2.27.651.6 again and it still gave me the same error
after searching on the net i found the command fastboot oem boot which works only with 2.27.651.5 and the 2.27.651.6 version now i cant open my htc hero sprint without this command ,
is there a way to fix it ? please help

It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...

cytherian said:
It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...
Click to expand...
Click to collapse
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported

mrxuser said:
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported
Click to expand...
Click to collapse
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?

cytherian said:
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?
Click to expand...
Click to collapse
what do u mean by overclocking

mrxuser said:
what do u mean by overclocking
Click to expand...
Click to collapse
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?

ElementalBeatz said:
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?
Click to expand...
Click to collapse
yes never done it before, would the phone be fixed if i did?

No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.

cytherian said:
No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.
Click to expand...
Click to collapse
If u dont mind can u show me how to install earilier bootloaders ?

Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki.
Click to expand...
Click to collapse
I already told u that i can use Adb and fastboot , i cant open my phone unless i use this command fastboot oem boot ,

Well good luck with that...

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.
Click to expand...
Click to collapse
here is the problem while flashing using fastboot
fastboot flash radio radio1.img
sending 'radio' (21376 KB)...
OKAY [ 24.089s]
writing 'radio'...
FAILED (remote: image type not support)
finished. total time: 24.108s
or here when i use flash the zip
fastboot flash zip update.zip
sending 'zip' (118067 KB)...
OKAY [129.171s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 132.015s
why does the (remote: image type not support) or the (remote: 24 parsing android-info fail) appear

Have you tried what I posted yet?

Shelnutt2 said:
Have you tried what I posted yet?
Click to expand...
Click to collapse
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!

mrxuser said:
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!
Click to expand...
Click to collapse
so there's nothing to help

Guys , Arent there anything to do to my program ,,, if somebody knows ,,,, please tell me

[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] Stuck in RElocked bootloader cannot unlock

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

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

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

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

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

[URGENT] Phone Stuck in Fastboot !!! Can't Reboot !!! Can't RUU

I was running my rom fine an hour ago, until I decided to try and reboot into recovery to make a backup. Instead of recovery, I ended up in bootloader. I then tried to enter recovery through the menu. It rebooted into bootloader and flashed the "3 Skating Androids" in the middle of the screen. I then tried to simply restart, and it did the same. All buttons did this. I then tried to run the RUU, and lock the bootloader from command prompt. I entered "fastboot oem lock", and it returned the following:
Code:
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(117):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(169):
(bootloader) htc_pg_hdr_get failed
(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 (No such file or directory))
finished. total time: 1.094s
I am unable to relock the bootloader, therefore I am unable to return to stock. I can't boot, and I have no way of recovering. I am sick and tired of these situations with my phone. What on earth could I possibly do to fix this ****?!

Your bootloader is unlocked correct? Do you have S-off? You can flash the RUU without re locking the bootloader if you have S-off.

chuckwago88 said:
Your bootloader is unlocked correct? Do you have S-off? You can flash the RUU without re locking the bootloader if you have S-off.
Click to expand...
Click to collapse
Unfortunately I don't have S-OFF, and I was unable to get it. I was running ViperOne 6.2.1 with Elemental X 14.12.
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
OS-4.19.661.8
eMMC-boot 2048MB

HTC1V said:
Unfortunately I don't have S-OFF, and I was unable to get it. I was running ViperOne 6.2.1 with Elemental X 14.12.
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
OS-4.19.661.8
eMMC-boot 2048MB
Click to expand...
Click to collapse
Try reading through this http://forum.xda-developers.com/showthread.php?t=2633276 . And you can find more instructions and information here http://forum.xda-developers.com/showthread.php?t=2632351 . I had a hard time getting it done, I was HBOOT 1.57, but firewater is what got it done for me.

chuckwago88 said:
Try reading through this http://forum.xda-developers.com/showthread.php?t=2633276 . And you can find more instructions and information here http://forum.xda-developers.com/showthread.php?t=2632351 . I had a hard time getting it done, I was HBOOT 1.57, but firewater is what got it done for me.
Click to expand...
Click to collapse
Thanks for trying to help. But my device appears to softbricked. I don't have access to my operating system, so S-OFF is not even remotely possible. Anyone else have any possible solutions?

I am pretty sure the term soft bricked means you can still boot into your bootloader. Hold down the power and volume down buttons until it gets there, mine took 20+ seconds when I was soft bricked. From your bootloader you can flash a recovery and then you should be able to get S-off. If you can't get into recovery or the bootloader I don't know what else to tell you.

chuckwago88 said:
I am pretty sure the term soft bricked means you can still boot into your bootloader. Hold down the power and volume down buttons until it gets there, mine took 20+ seconds when I was soft bricked. From your bootloader you can flash a recovery and then you should be able to get S-off. If you can't get into recovery or the bootloader I don't know what else to tell you.
Click to expand...
Click to collapse
Unfortunately I cannot boot into recovery. Every time I hit an option, the bootloader restarts. I will try leaving my phone turned off for the next day, to see if draining the circuits does anything.

HTC1V said:
Unfortunately I cannot boot into recovery. Every time I hit an option, the bootloader restarts. I will try leaving my phone turned off for the next day, to see if draining the circuits does anything.
Click to expand...
Click to collapse
If you can get into the bootloader you should be good to flash a recovery through fastboot. Try looking at this link, get all the correct files for your phone and computer, and look towards the end of the page where it talks about download via fastboot, this is what you need to do. http://teamw.in/project/twrp2/164 . After you get the TWRP installed, you will be able to sideload a rom from there.

chuckwago88 said:
If you can get into the bootloader you should be good to flash a recovery through fastboot. Try looking at this link, get all the correct files for your phone and computer, and look towards the end of the page where it talks about download via fastboot, this is what you need to do. http://teamw.in/project/twrp2/164 . After you get the TWRP installed, you will be able to sideload a rom from there.
Click to expand...
Click to collapse
As I said earlier, I am unable to boot into recovery. I've tried CWM, TWRP, and stock. Every time I try to use a command, I get an error. I get "FAILED (remote: image update error)" every time I try to flash a recovery. It's like my fastboot mode is broken. I also tried booting directly into recovery with "fastboot boot twrp.img" but this didn't work, and just froze the device.

HTC1V said:
As I said earlier, I am unable to boot into recovery. I've tried CWM, TWRP, and stock. Every time I try to use a command, I get an error. I get "FAILED (remote: image update error)" every time I try to flash a recovery. It's like my fastboot mode is broken. I also tried booting directly into recovery with "fastboot boot twrp.img" but this didn't work, and just froze the device.
Click to expand...
Click to collapse
What stock recovery are you using ?
Here's the steps I would take
from bootloader choose shut down
wait about 5 min reboot to the bootloader fastboot USB
then fastboot erase cache
fastboot reboot-bootloader
now flash Stock recovery
fastboot flash recovery stock_recovery.img
fastboot erase cache
fastboot reboot-bootloader
now enter stock recovery (power + volume up after you choose it in the bootloader)
when you see the menu choose factory reset
now start over with the custom recovery
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
What stock recovery are you using ?
Here's the steps I would take
from bootloader choose shut down
wait about 5 min reboot to the bootloader fastboot USB
then fastboot erase cache
fastboot reboot-bootloader
now flash Stock recovery
fastboot flash recovery stock_recovery.img
fastboot erase cache
fastboot reboot-bootloader
now enter stock recovery (power + volume up after you choose it in the bootloader)
when you see the menu choose factory reset
now start over with the custom recovery
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
I'm using the telus stock recovery from here: http://forum.xda-developers.com/showthread.php?t=2545227 and unfortunately, I get an error every time I try to wipe the cache. I get:
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.015s
I also get errors when I flash the stock recovery, I can't access anything it seems. My cord is fine, it's worked for me forever.
There must be a way to fix this!

HTC1V said:
I'm using the telus stock recovery from here: http://forum.xda-developers.com/showthread.php?t=2545227 and unfortunately, I get an error every time I try to wipe the cache. I get:
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.015s
I also get errors when I flash the stock recovery, I can't access anything it seems. My cord is fine, it's worked for me forever.
There must be a way to fix this!
Click to expand...
Click to collapse
sounds like your bootloader is locked

clsA said:
sounds like your bootloader is locked
Click to expand...
Click to collapse
:silly: No my bootloader is not locked. It says *** UNLOCKED *** right on the screen. Just because I'm a junior member doesn't mean I'm a noob. I have tried many commands, including "fastboot oem lock" but nothing works. Read my first post again. Let me clarify for everyone! My bootloader is not fully fuctional. I am able to check barcode, and shutdown. Any fastboot commands don't seem to really work (with exception of "fastboot devices," and "fastboot oem unlock_token token.bin"). I've been trying to relock my device, so I can run the RUU.exe, but I this gives me an error. I tried unlocking my device for a second time, and it says unlock successful, but I don't get the warranty, and prompt on screen. I've only had this phone for about 4 months, and I'd like to get a little more life out of it before turning to ebay to find another.

HTC1V said:
:silly: No my bootloader is not locked. It says *** UNLOCKED *** right on the screen. Just because I'm a junior member doesn't mean I'm a noob. I have tried many commands, including "fastboot oem lock" but nothing works. Read my first post again. Let me clarify for everyone! My bootloader is not fully fuctional. I am able to check barcode, and shutdown. Any fastboot commands don't seem to really work (with exception of "fastboot devices," and "fastboot oem unlock_token token.bin"). I've been trying to relock my device, so I can run the RUU.exe, but I this gives me an error. I tried unlocking my device for a second time, and it says unlock successful, but I don't get the warranty, and prompt on screen. I've only had this phone for about 4 months, and I'd like to get a little more life out of it before turning to ebay to find another.
Click to expand...
Click to collapse
I wasn't implying your were dumb ..i was pointing out that your phone acts the same as one with a locked bootloader.
the bootloader partition seems corrupt, fixing it is out of my league. Maybe @nkk71 or @alray has some advice

clsA said:
I wasn't implying your were dumb ..i was pointing out that your phone acts the same as one with a locked bootloader.
the bootloader partition seems corrupt, fixing it is out of my league. Maybe @nkk71 or @alray has some advice
Click to expand...
Click to collapse
Sorry. Thank you very much for the help dude. I'll see what I can do about getting it fixed, I hope there's nothing wrong on the hardware side.

HTC1V said:
Sorry. Thank you very much for the help dude. I'll see what I can do about getting it fixed, I hope there's nothing wrong on the hardware side.
Click to expand...
Click to collapse
like cIsA said, it looks like your eMMC is corrupted, at least the partition where your bootloader is. Ive never seen that kind of error before (SD_HW_ERR] read data fail in CMD18) so I don't have any idea how to help you. Probably re-flashing the firmware or a complete ruu will fix it but its not possible with a non-relockable bootloader + S-ON.
sorry

alray said:
like cIsA said, it looks like your eMMC is corrupted, at least the partition where your bootloader is. Ive never seen that kind of error before (SD_HW_ERR] read data fail in CMD18) so I don't have any idea how to help you. Probably re-flashing the firmware or a complete ruu will fix it but its not possible with a non-relockable bootloader + S-ON.
sorry
Click to expand...
Click to collapse
So it's time for a new phone?

HTC1V said:
So it's time for a new phone?
Click to expand...
Click to collapse
You should wait to see what nkk71 think about your situation.
Code:
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [[COLOR="Red"]SD_HW_ERR[/COLOR]] [COLOR="red"]read data fail in CMD18[/COLOR]
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
only speculating here but I think that CMD is a master/slave protocol used to send commands to the eMMC chip (I might be wrong, I'm not an expert in this matter) So this could mean you have a defective or corrupted eMMC. that would explain why you got these error codes and that you are not able to do anything useful from the bootloader.
Maybe a jtag/riffbox flash could fix this....

HTC1V said:
So it's time for a new phone?
Click to expand...
Click to collapse
Sorry for the late reply, but yep, i think it's time for a new phone.
from what i've seen (and/or):
* "image update error"
* unable to relock bootloader
* "fastboot oem rebootRUU" doesn't actually go to RUU mode (gives some kind of CMDxx / SD error)
== fried phone
sorry to be the bearer of bad news

nkk71 said:
Sorry for the late reply, but yep, i think it's time for a new phone.
from what i've seen (and/or):
* "image update error"
* unable to relock bootloader
* "fastboot oem rebootRUU" doesn't actually go to RUU mode (gives some kind of CMDxx / SD error)
== fried phone
sorry to be the bearer of bad news
Click to expand...
Click to collapse
Thank you nkk71
There's no way I can repair it? Jtag is jot an option?

Stuck in fastboot - No running ROM, recovery , ADB

Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Some more info:
- ADB does not work currently. I tried Win and OSX , so I believe its the phone rejecting it.
- With stock recovery, reading in the 0P8BIMG.zip RUU file containing a 2.19.401.2 or 2.18.401.3 system fails.
- Flashing recovery TWRP 2.8.5.0 / 2.8.1.0 works, but the phone will not start it.
Code:
C:\Users\USER>fastboot flash recovery "Z:\Installs\HTC Mini 2\recovery-twrp-2.8.5.0.img"
sending 'recovery' (11796 KB)...
OKAY [ 1.393s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 1.790s
- My bootloader is ***Unlocked*** according to the fastboot screen. However, I cannot lock it :
Code:
C:\Users\USER>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 8
(bootloader) [INFO] Reset reason in IMEM is 0x77665501
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.056s
- Output of getvar all :
Code:
C:\Users\USER>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please let me know if I missed to provide important information.
Is there any way for me to start over on a lower level ? Or is a mobile shop / HTC my only solution left?
Thanks a lot for any feedback!
Greetings,
faiv

faiv said:
Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Click to expand...
Click to collapse
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.

kativiti said:
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.
Click to expand...
Click to collapse
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.

faiv said:
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.
Click to expand...
Click to collapse
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?

kativiti said:
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?
Click to expand...
Click to collapse
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?

faiv said:
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?
Click to expand...
Click to collapse
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.

kativiti said:
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.
Click to expand...
Click to collapse
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !

blu3sm4n said:
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !
Click to expand...
Click to collapse
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.

kativiti said:
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.
Click to expand...
Click to collapse
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks

blu3sm4n said:
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks
Click to expand...
Click to collapse
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.

kativiti said:
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.
Click to expand...
Click to collapse
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)

blu3sm4n said:
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)
Click to expand...
Click to collapse
thx for the picture.
you hboot shows that nothing has been done to the phone. so it was NEVER unlocked as stated in original post.
At this point im gonna suggest get your self an original usb cable because the one you using its no good. its giving you wrong info and it seems some get to the phone but corrupted and thats why unlock fails.
im trying to create a new updated RUU but might take some time.
please get OTA cable and try to unlock

You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

blu3sm4n said:
You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know

Ok I'll try and let you know
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

kativiti said:
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know
Click to expand...
Click to collapse
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).

blu3sm4n said:
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).
Click to expand...
Click to collapse
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.

kativiti said:
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
Click to expand...
Click to collapse
in hboot when I try to enter recovery, red warning comes and pressing power+vol up, it says "device cw install:cant mount/data" and then black screen.
I tried second step and added your file into sdcard and update. it says press power button. After that white htc screen is coming. It is waiting since 15 minutes but still nothing and still white screen [emoji21]
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

Sorry but it seems I'm unable to help you.
The picture shows green letters behind the red ones. It means the flashing fail, maybe it rejected the recovery or because its locked.
Either way your problem is, your system and recovery are corrupted.
My advice is contact HTC and send for repair. They usually don't charge you.

Ok dude thanks a lot. I'll contact HTC, i hope they can help ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi