Develop Bugs

[Q] Failed remote signature verify fail. Phone stops on fastboot

Okay, i have a problem with an old phone, I believe its perm bricked, but wanted to check...
It is currently S-ON, and i have no way to turn off, its has no operating system, and the screen does not turn on. however i can turn the phone on, it does vibrate, and i can use fastboot commands.
Anyone got any idea's or shall i bin it?
C:\and\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: 1.21.405.2
(bootloader) serialno: **************************
(bootloader) imei: ********************
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.006s
C:\and\sdk\platform-tools>

It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before

eddiehk6 said:
It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before
Click to expand...
Click to collapse
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).

mike989e said:
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).
Click to expand...
Click to collapse
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up

eddiehk6 said:
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up
Click to expand...
Click to collapse
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot

mike989e said:
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot
Click to expand...
Click to collapse
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
number 5 on the guide

eddiehk6 said:
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
number 5 on the guide
Click to expand...
Click to collapse
I get a bootloader version error, code 140 when i try to install lol

mike989e said:
I get a bootloader version error, code 140 when i try to install lol
Click to expand...
Click to collapse
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading

eddiehk6 said:
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading
Click to expand...
Click to collapse
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Thanks for your help though, i think it is dead, think i'll just bin it

mike989e said:
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Click to expand...
Click to collapse
no, you don't need to be booted into the OS:
If you dont have a goldcard, you might try to create one at this point. This may work only for some people. Try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone gets detected in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
Click to expand...
Click to collapse
the goldcard is just very useful to have in case you have this kind of situation.
i'm still very surprised the 2.3.3 RUU doesn't work. another thing you could try is to use the 2.3.3 GB RUU again, but use the PB99IMG.zip method, by extracting the rom.zip from the RUU
Thanks for your help though, i think it is dead, think i'll just bin it
Click to expand...
Click to collapse
as long as you can get to a bootloader screen, it's almost certainly not dead. your symptoms are EXACTLY as that guide states. it's your device, might as well get it working again
a real brick is literally nothing, no response, no LED, nothing. most people who think their device is 'bricked' is never actually bricked.

as long as you get to fastboot no problem. just download the pb99img from the latest 2.3 official upgrade then throught fastboot (back+power) enter in to fastboot RUU update mode then flash the zip with the command fastboot flash zip rom.zip . you dont need even an sd card to do that. just wait to procces to finish then fastboot reboot and your done. first boot takes few minutes longer but you wont have problems.

theres a couple of problems i have, 1 i have no screen, even when i fastboot. so i wont know if it fails, secondly my issues is that the image version number is to high on my phone. hence why i am getting the 140 error. as i have installed a number of roms off here the version number is to high.
off the top of my head, i cannot remember the number, however, on 2.3.3 is got a .17. in it, mine instead of that has .27. which means mine cannot install the standard 2.3.3 software, if i knew how to change the image number to higher than mine, and repackage it i could install it. but i don't know how. as i recall there was a thread about this years ago, but not sure if it was ever solved. i did look for it.

Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!

mike989e said:
Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!
Click to expand...
Click to collapse
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.

eddiehk6 said:
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.
Click to expand...
Click to collapse
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.

mike989e said:
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.
Click to expand...
Click to collapse
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...

eddiehk6 said:
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...
Click to expand...
Click to collapse
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!

mike989e said:
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!
Click to expand...
Click to collapse
you shouldnt have a custom recovery installed any more, the RUU should overwrite it to stock recovery. you won't be able to do anything with stock recovery per se, but the guide seems to indicate that you may be able to communicate with the device via adb.
still surprised the 2.3.3 RUU didn't work, I thought it's the highest version number so shouldn't have any problem.
I'm running out of ideas tbh, I'd still recommend posting the issue in the droidzone guide, hopefully he'll reply as he'd most likely know how to solve it.

biggest root fail of all time!

i rooted my phone with no issues, it was unlocked and s off. i uploaded a custom rom that was intended for kitkat 4.4.4 but my phone was 4.4.2. the phone flips to S-ON and says "Tampered". i've tried downloading the right firmware specifically for my phone. ive tried every method known to man just to get the phone back to stock. including sunshine and firewater. looked up the exact firmware for this phone... flashed. nothing. still the same. phone works great with this Venom custom rom but... i have no wifi. also, when the phone reboots, it takes forever. like, a good 15 minutes. i dont know what else to do. i just want to go back stock with S-OFF, update to 4.4.4. then try rooting again. this has been a massive headache. never had issues like this rooting samsung devices. htc is a whole different ballgame!

MPH33 said:
never had issues like this rooting samsung devices. htc is a whole different ballgame!
Click to expand...
Click to collapse
Every phone is different and has its own learning curve. Comparisons to Samsung are pointless.
How did you s-off originally?
My suggestion would be to unlock the bootloader again (if its now relocked) install custom recovery, than nandroid back to stock. Sunshine s-off, then stock recovery and OTA. Once updated, install custom recovery again and root.

redpoint73 said:
Every phone is different and has its own learning curve. Comparisons to Samsung are pointless.
How did you s-off originally?
My suggestion would be to unlock the bootloader again (if its now relocked) install custom recovery, than nandroid back to stock. Sunshine s-off, then stock recovery and OTA. Once updated, install custom recovery again and root.
Click to expand...
Click to collapse
now my phone is stuck in htc boot. how can i flash a recovery back to the phone with adb? cmd doesnt see device. just stuck in htc boot(white screen with " this build is for development purposes only" in bright red)

Bootloader always works as long as the screen comes on.
Hold down power + vol up until the phone reboots. The moment the screen goes dark to restart, let go of those buttons and just hold vol down. This will get you into bootloader. If it doesn't work, you just did the button combo wrong (either didn't press vol down soon enough, or let go too early). Just try again until you are in bootloader. From there, go into fastboot mode and erase cache and flash recovery.

just find and flash the latest firmware for your m8 from RUU mode. if you can let us know the variant maybe someone here can help.
Also, I am pretty sure Viper ROM's OP says to update to latest firmware else wifi wont work and also warns about long boot times.

im able to go in to recovery, now i need to flash a rom to get the phone going. can this be done through cmd? im unable to access phone storage through fastboot usb in recovery. i was trying to place stock rom on phone but have zero access

MPH33 said:
im unable to access phone storage through fastboot usb in recovery.
Click to expand...
Click to collapse
I think you mean fastboot mode, which is different from recovery. If on a Windows PC, try to uninstall HTC Sync and drivers. Then when the phone connects, go to Device Manager, find the device. Select the option to manually select drivers, and pick the Generic MTP Android device drivers.
MPH33 said:
now i need to flash a rom to get the phone going. can this be done through cmd?
Click to expand...
Click to collapse
Sure, use adb push.
Or put a ROM on your SD card using a USB card reader connected to your computer.

redpoint73 said:
I think you mean fastboot mode, which is different from recovery. If on a Windows PC, try to uninstall HTC Sync and drivers. Then when the phone connects, go to Device Manager, find the device. Select the option to manually select drivers, and pick the Generic MTP Android device drivers.
Sure, use adb push.
Or put a ROM on your SD card using a USB card reader connected to your computer.
Click to expand...
Click to collapse
i want to push "stock 1.12.502.18 - TWRP - CWS__001." through cmd. how do i do this? im not an expert on cmd language. i just want to put any rom on this phone so i can get it working. i have a newborn baby. phone is a must

MPH33 said:
i want to push "stock 1.12.502.18 - TWRP - CWS__001." through cmd. how do i do this? im not an expert on cmd language. i just want to put any rom on this phone so i can get it working. i have a newborn baby. phone is a must
Click to expand...
Click to collapse
I'm assuming you are using a Windows PC (otherwise I can't really help):
1) Put the file in the same folder that contains adb.exe
2) With phone connected, open command prompt. Change directory to your adb folder.
3) Enter command: adb push ROM.zip /data/media/0/
Where ROM.zip is the name of the file. You can actually rename the file ROM.zip if you like (to make it shorter to type). But make sure in Windows that you do not have the option selected to hide file extensions (based on the file you stated, you might in fact have this selected, a ROM file should have extension .zip), otherwise you may accidentally name the file ROM.zip.zip and not know it (common mistake).

finally get the rom on my phone and it failed to install through philz clockwork. im freaking pissed! i cant believe how tough this is! i dont know what else to do! i converted the rar file to zip. still didnt work.

MPH33 said:
finally get the rom on my phone and it failed to install through philz clockwork. im freaking pissed! i cant believe how tough this is! i dont know what else to do! i converted the rar file to zip. still didnt work.
Click to expand...
Click to collapse
A ROM should be a ZIP, not a RAR. What are you trying to flash?
Also, I can't tell if my suggestions are helping or not. You don't indicate whether you have tried the suggestions/steps I gave you; or if they didn't work, or if got here some other way.

redpoint73 said:
A ROM should be a ZIP, not a RAR. What are you trying to flash?
Also, I can't tell if my suggestions are helping or not. You don't indicate whether you have tried the suggestions/steps I gave you; or if they didn't work, or if got here some other way.
Click to expand...
Click to collapse
finally! i found android revolution hd 21.1 in my recovery. sux that i dont have wifi but atleast i have a phone. i sure wish i could go back to stock to start over again. even when i went back to 4.4.2, it never would let me update to 4.4.4. i use an at&t phone with cricket wireless. maybe that has something to do with it. my phone never update even before i rooted

MPH33 said:
finally! i found android revolution hd 21.1 in my recovery. sux that i dont have wifi but atleast i have a phone. i sure wish i could go back to stock to start over again. even when i went back to 4.4.2, it never would let me update to 4.4.4. i use an at&t phone with cricket wireless. maybe that has something to do with it. my phone never update even before i rooted
Click to expand...
Click to collapse
Which firmware version have you got installed now?? U can check it under settings/info/software info

OmniSlyfer said:
Which firmware version have you got installed now?? U can check it under settings/info/software info
Click to expand...
Click to collapse
This is wrong. settings/info/software info shows just the base the ROM is built on, not the actual firmware. his software info will show 3.28.401.7 which is clearly wrong since he doesn't have a working Wifi which shows that he is on older firmware.
The only reliable way to find the firmware is
fastboot getvar all

From what you've said you've a AT&T branded handset, so download the following:
http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
Put your phone into fastboot mode, but powering down and then holding volume down + power until you get to the hboot screen, press power again to enter fastboot mode.
Connect your phone via usb to your pc, (ensuring you've removed htc sync and have the relevant fastboot drivers), run the downloaded .exe file and let the process run until completion.
This should restore your phone to stock rom, your bootloader should still be unlocked and if s-off (if applied) still active.
I've been struggling to follow what it is you had done to put yourself into this problem, I recommend reading through all the guides available development forum before rooting and flashing again.
Many new roms will require a firmware update, or you'll find that wifi won't work.
Let us know how you get along.

OmniSlyfer said:
Which firmware version have you got installed now?? U can check it under settings/info/software info
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXXX
imei: 3587180508XXXXXXXXX
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0

downbringer said:
From what you've said you've a AT&T branded handset, so download the following:
http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
Put your phone into fastboot mode, but powering down and then holding volume down + power until you get to the hboot screen, press power again to enter fastboot mode.
Connect your phone via usb to your pc, (ensuring you've removed htc sync and have the relevant fastboot drivers), run the downloaded .exe file and let the process run until completion.
This should restore your phone to stock rom, your bootloader should still be unlocked and if s-off (if applied) still active.
I've been struggling to follow what it is you had done to put yourself into this problem, I recommend reading through all the guides available development forum before rooting and flashing again.
Many new roms will require a firmware update, or you'll find that wifi won't work.
Let us know how you get along.
Click to expand...
Click to collapse
just tried this. i got an error message about usb. cant read phone. odd. maybe it was my spyware running in the background. this sux. i really wanted this to work. looked very promising

Not likely to be spyware, more likely to be the fact that you don't have the right fastboot drivers installed on your pc.
Download the application from this thread and follow the instructions to set up fastboot.
http://forum.xda-developers.com/showthread.php?t=2588979
After completing that - reboot your pc and then attempt the install of the RUU again following my original instructions.

MPH33 said:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXXX
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Why do you take out your serial number but leave the more important IMEI number there? Take it out of your post.
Also your HBOOT version is still old 3.16, ARHD runs on the 3.28 firmware with HBOOT 3.19. You need to update your firmware in order to run a newer version of ARHD.

downbringer said:
Not likely to be spyware, more likely to be the fact that you don't have the right fastboot drivers installed on your pc.
Download the application from this thread and follow the instructions to set up fastboot.
http://forum.xda-developers.com/showthread.php?t=2588979
After completing that - reboot your pc and then attempt the install of the RUU again following my original instructions.
Click to expand...
Click to collapse
failed ruu. said chose different firmware to update. disappointed. thought for sure this would work
thanx for trying though

HTC one M8 stuck in bootloop

Hi Everyone.
Recently I factory reset my HTC One M8 and now It hangs on logo screen when powered on. sometimes after a hard reset using vol+ and power it loads past logo screen to android starting, optimizing app, but hangs after optimizing apps.
cant get access to recovery mode phone wont load bootloader.

ThomasHoey said:
cant get access to recovery mode phone wont load bootloader.
Click to expand...
Click to collapse
Hold vol up and power on, until the screen goes dark (may take a minute or so). While the screen is dark, and before the white logo screen comes on, let go of the buttons and only hold vol down. Don't let go of vol down, until the bootloader screen appears.
This virtually always works. So if you can't get into bootloader, try again. Failure to get into bootloader this way, is usually due to not pressing vol down fast enough, or letting go too early.
From there, if you need more help, do fastboot getvar all, and post the results (delete IMEI and serial number) so we can get more info about the device.

Thank you for the reply, will try this and get back to you.
thanks again

redpoint73 said:
Hold vol up and power on, until the screen goes dark (may take a minute or so). While the screen is dark, and before the white logo screen comes on, let go of the buttons and only hold vol down. Don't let go of vol down, until the bootloader screen appears.
This virtually always works. So if you can't get into bootloader, try again. Failure to get into bootloader this way, is usually due to not pressing vol down fast enough, or letting go too early.
From there, if you need more help, do fastboot getvar all, and post the results (delete IMEI and serial number) so we can get more info about the device.
Click to expand...
Click to collapse
I have a question regarding this method
do I hold vol+ and power and immediately let go when screen goes black?
if i hold them for a few seconds longer then the phone vibrates

ThomasHoey said:
I have a question regarding this method
do I hold vol+ and power and immediately let go when screen goes black?
if i hold them for a few seconds longer then the phone vibrates
Click to expand...
Click to collapse
You have about 3 seconds while the screen is dark to let go of vol up, and start holding vol down. If you the white HTC logo screen appears, its too late to start pressing vol down. If you had a working OS, pressing vol down "too late" during the logo screen initiates safe mode. But in your case, since you can't boot OS, nothing happens and it stays on the logo screen.
Really, its only sliding your finger down from vol up, to vol down, that matters. It actually doesn't matter if you continue to hold the power button or not.

redpoint73 said:
Hold vol up and power on, until the screen goes dark (may take a minute or so). While the screen is dark, and before the white logo screen comes on, let go of the buttons and only hold vol down. Don't let go of vol down, until the bootloader screen appears.
This virtually always works. So if you can't get into bootloader, try again. Failure to get into bootloader this way, is usually due to not pressing vol down fast enough, or letting go too early.
From there, if you need more help, do fastboot getvar all, and post the results (delete IMEI and serial number) so we can get more info about the device.[/QUOTE
redpoint73 said:
You have about 3 seconds while the screen is dark to let go of vol up, and start holding vol down. If you the white HTC logo screen appears, its too late to start pressing vol down. If you had a working OS, pressing vol down "too late" during the logo screen initiates safe mode. But in your case, since you can't boot OS, nothing happens and it stays on the logo screen.
Really, its only sliding your finger down from vol up, to vol down, that matters. It actually doesn't matter if you continue to hold the power button or not.
Click to expand...
Click to collapse
still no luck getting bootloader to load
Click to expand...
Click to collapse

ThomasHoey said:
redpoint73 said:
Hold vol up and power on, until the screen goes dark (may take a minute or so). While the screen is dark, and before the white logo screen comes on, let go of the buttons and only hold vol down. Don't let go of vol down, until the bootloader screen appears.
This virtually always works. So if you can't get into bootloader, try again. Failure to get into bootloader this way, is usually due to not pressing vol down fast enough, or letting go too early.
From there, if you need more help, do fastboot getvar all, and post the results (delete IMEI and serial number) so we can get more info about the device.[/QUOTE
still no luck getting bootloader to load
Click to expand...
Click to collapse
So I have managed to find the problem. When the phone loads the bootloader/fastboot mode I cannot see it as the screen is blank but I am able to use the vol keys to highlight and power to select an option problem being I dont know what I'm selecting or if im even in bootloader or Fastboot mode.
Click to expand...
Click to collapse

ThomasHoey said:
ThomasHoey said:
So I have managed to find the problem. When the phone loads the bootloader/fastboot mode I cannot see it as the screen is blank but I am able to use the vol keys to highlight and power to select an option
Click to expand...
Click to collapse
Gotcha, I've seen this problem (black screen in bootloader) reported here once or twice. But its pretty rare (which is one reason I said the button combo "virtually" always works).
ThomasHoey said:
problem being I dont know what I'm selecting or if im even in bootloader or Fastboot mode.
Click to expand...
Click to collapse
I haven't seen any solution for this, aside from just guessing, and trial and error.
If you M8 version has the RUU in zip format, you can rename it to 0P6BIMG.zip then put it on an SD card, and boot into bootloader, and it should install automatically. Although an RUU won't install if the bootloader is unlocked and phone is s-on.
Click to expand...
Click to collapse

redpoint73 said:
ThomasHoey said:
Gotcha, I've seen this problem (black screen in bootloader) reported here once or twice. But its pretty rare (which is one reason I said the button combo "virtually" always works).
I haven't seen any solution for this, aside from just guessing, and trial and error.
Yeah thats what I have been doing. I managed to get it to go into recovery, cleared cache and then cleared data and factory reset, still stuck in bootloop.
If you M8 version has the RUU in zip format, you can rename it to 0P6BIMG.zip then put it on an SD card, and boot into bootloader, and it should install automatically. Although an RUU won't install if the bootloader is unlocked and phone is s-on.
Click to expand...
Click to collapse
Do you know where I can get a Stock ROM to do RUU. I haven't modded my phone at all so would the bootloader not be locked and S-off by default.
again thanks for taking time to reply.
Click to expand...
Click to collapse

ThomasHoey said:
Do you know where I can get a Stock ROM to do RUU. I haven't modded my phone at all so would the bootloader not be locked and S-off by default.
Click to expand...
Click to collapse
If the phone is not modded, it would be bootloader locked, which is what you want in order to RUU. Probably also s-on (although s-off from the factory is rare, but we have seen it). But s-on or s-off doesn't affect your ability to RUU (as long as the bootloader is locked).
Which RUU depends on the version (CID) of your phone. If you don't know the CID, you'll need to try to get into fastboot, and do fastboot getvar all, and post the results here (delete IMEI and serial number before posting).

redpoint73 said:
ThomasHoey said:
Which RUU depends on the version (CID) of your phone. If you don't know the CID, you'll need to try to get into fastboot, and do fastboot getvar all, and post the results here (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
I dont know the CID, How would I get into fastboot if I cant see the screen. I take it I would yous the CMD on my laptop to run the command.
I have already got ADB and Fastboot on my laptop.
Click to expand...
Click to collapse

ThomasHoey said:
How would I get into fastboot if I cant see the screen.
Click to expand...
Click to collapse
Yes, I realize that. That is why I typed: try to get into fastboot
With no OS, you'll need fastboot to determine the needed info.
Your other option is to read the model number off the back of the phone. But this isn't always reliable (better to verify with fastboot getvar) as we've seen a lot of M8 phones with the back cover swapped to remove carrier branding.
But if you obtained the phone from a reputable source, such as your carrier, it likely won't have had its back cover changed. But you haven't told us anything about the phone. Is it carrier branded, what version you think it is, where you bought it from, etc.
ThomasHoey said:
I take it I would yous the CMD on my laptop to run the command.
I have already got ADB and Fastboot on my laptop.
Click to expand...
Click to collapse
That is correct, in CMD window, change directory to whatever folder you have fastboot.exe located. Windows shortcut here is to find fastboot.exe, open that folder, then hover your cursor inside that folder, press Shift+right mouse, and select "Open command window here" from the popup menu.
Then in command, simply type: fastboot getvar all
Or you can check the phone is properly in fastboot mode with the command: fastboot devices
The phone's serial number should be returned, if the phone is properly in fastboot mode. No serial number (no devices listed) or device indicated as "offline" means you don't have a proper fastboot connection. If everything else is okay (drivers, cable, etc.), but phone is not in fastboot mode, the likely result is the phone's serial number, but shown as "offline".
Again, don't post your IMEI or serial number to the forums.

redpoint73 said:
Yes, I realize that. That is why I typed: try to get into fastboot]
But if you obtained the phone from a reputable source, such as your carrier, it likely won't have had its back cover changed. But you haven't told us anything about the phone. Is it carrier branded, what version you think it is, where you bought it from, etc.
The phone is on contract to 02, purchased fro the 02 store.
That is correct, in CMD window, change directory to whatever folder you have fastboot.exe located. Windows shortcut here is to find fastboot.exe, open that folder, then hover your cursor inside that folder, press Shift+right mouse, and select "Open command window here" from the popup menu.
Then in command, simply type: fastboot getvar all
Or you can check the phone is properly in fastboot mode with the command: fastboot devices
The phone's serial number should be returned, if the phone is properly in fastboot mode. No serial number (no devices listed) or device indicated as "offline" means you don't have a proper fastboot connection. If everything else is okay (drivers, cable, etc.), but phone is not in fastboot mode, the likely result is the phone's serial number, but shown as "offline".
I have tried all the modes in bootloader.
1 when in bootloader if I just press power button to select first option all the phone does is stay in a continual loop of vibrates with a 2 sec pause in-between each vibrate.
2 Press vol- down then power then I see another screen with a small phone logo with a green circle going round with an green arrow pointing down. if i press vol+ power or vol- power the I get power icon with a red line through it.
3 press vol- 2 times then it takes me to screen with red exclamation mark and circle, then a press vol+ and power takes me to recovery.
in recovery it gives me the option to update via ADB would this be an option. if so could you instruct me on how to do so if you know
Thank you so much for taking the time to reply
Click to expand...
Click to collapse

ThomasHoey said:
I have tried all the modes in bootloader.
1 when in bootloader if I just press power button to select first option all the phone does is stay in a continual loop of vibrates with a 2 sec pause in-between each vibrate.
2 Press vol- down then power then I see another screen with a small phone logo with a green circle going round with an green arrow pointing down. if i press vol+ power or vol- power the I get power icon with a red line through it.
3 press vol- 2 times then it takes me to screen with red exclamation mark and circle, then a press vol+ and power takes me to recovery.
Click to expand...
Click to collapse
What if you go into bootloader, and press nothing (any response to fastboot devices)? Fastboot mode is often the default bootloader mode, if a USB cable is connected.

redpoint73 said:
What if you go into bootloader, and press nothing (any response to fastboot devices)? Fastboot mode is often the default bootloader mode, if a USB cable is connected.
Click to expand...
Click to collapse
I never thought of that. will try that and give it a go. will get back to you.
thanks again

redpoint73 said:
What if you go into bootloader, and press nothing (any response to fastboot devices)? Fastboot mode is often the default bootloader mode, if a USB cable is connected.
Click to expand...
Click to collapse
ok so I managed to get it into fastboot with your last instructions here is the info from fastboot getvar all
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\T.Hoey>fastboot devices
SH43MWM12276 fastboot
C:\Users\T.Hoey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH43MWM12276
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.139s

You'll find the RUU for your version here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Plus instructions on that link on how to flash using htc_fastboot. Note, that you need to use the htc_fastboot.exe provided in that thread, the RUU probably won't run with the "generic" fastboot you are presently using.
Or you can rename the RUU file to 0P6BIMG.zip (first character is a zero, not the letter "O"), put it on an SD card, insert into the phone, and reboot into bootloader, and it will install automatically.
The RUU will install a completely new factory stock image, which will hopefully get you booted into Android OS, and fix the black screen on hboot issue.

redpoint73 said:
You'll find the RUU for your version here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Plus instructions on that link on how to flash using htc_fastboot. Note, that you need to use the htc_fastboot.exe provided in that thread, the RUU probably won't run with the "generic" fastboot you are presently using.
Or you can rename the RUU file to 0P6BIMG.zip (first character is a zero, not the letter "O"), put it on an SD card, insert into the phone, and reboot into bootloader, and it will install automatically.
The RUU will install a completely new factory stock image, which will hopefully get you booted into Android OS, and fix the black screen on hboot issue.
Click to expand...
Click to collapse
Thamk you so much for ll your help. will give this a go and get back to you. here is hoping

View attachment 3726366
ThomasHoey said:
Thank you so much for ll your help. will give this a go and get back to you. here is hoping
Click to expand...
Click to collapse
So I have tried this option but when I enter the third command had to change it from htc_fastboot flash zip RUU.zip to htc_fastboot.exe flash zip 0P6BIMG.zip for it to run.
got an failed mesage. (pic attached)
now its hung on sending zip
pic attached

ThomasHoey said:
So I have tried this option but when I enter the third command had to change it from htc_fastboot flash zip RUU.zip to htc_fastboot.exe flash zip 0P6BIMG.zip for it to run.
Click to expand...
Click to collapse
It clearly says in the instructions for this method: Rename the RUU zip to RUU.zip
In any case, what you did also works, of course. The point is you are telling fastboot to flash the zip named in the command. You can rename the zip file whatever you want, and still flash it:
htc_fastboot flash zip whatever.zip
The file name 0P6BIMG.zip is only required if you use the SD card install method.
If the RUU stopped at the "flush image again immediately" error, just flash it again (this is a common and normal result).

Soft-Bricked HTC One M9, no recovery or download mode, need help with factory reload

Hey all. First of all, let me thank you in advance for any and all help. Here's the low-down.
I bought this phone today on craigslist (I know, I know). I confirmed, however, that the phone was not reported lost or stolen and that the IMEI was not blacklisted. The guy I bought it from said he was having issues after an attempted update, but after spending the last 6+ hours combing through forum posts, trying every software combination I can find, etc. I think my issues may be bigger.
Here's what I'm experiencing. When turning the phone on, I see the following:
***Software status: Official ***
*** LOCKED ***
*** S-ON ***
Click to expand...
Click to collapse
I have 5 options at that point:
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
Click to expand...
Click to collapse
If I select Reboot, the phone reboots and the message at the top changes slightly to show:
***Software status: Modified***
*** LOCKED ***
*** S-ON ***
*** Security Warning ***
Click to expand...
Click to collapse
If I select reboot to bootloader, it goes back to "Software status: Official"
If I try to boot to download mode, I get
Failed to boot to download mode
Press volume up or down to back to menu
Click to expand...
Click to collapse
followed then by the HTC Logo and the following text
This build is for development purposes only
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action.
Click to expand...
Click to collapse
If I boot to recovery mode I get the same thing as download mode, with the text saying "Failed to boot to recovery mode" and all of the rest matching.
I have tried signing up for an HTC dev account and going in to get the Identifier token, but because I can't boot the phone into download mode I can't get the token. When I try running the
fastboot oem get_identifier_token.
Click to expand...
Click to collapse
command it just tells me
FAILED: unknown remote command.
Click to expand...
Click to collapse
I've also tried using the HTC One M9 toolkit found here on the forums (though maybe there's some functionality I missed, I tried to be thorough).
I've also tried using the HTC sync software and downloading the RUU but after running the RUU executable nothing happens. I then dug into trying to make sure the MID and CID are correct but again, the command
fastboot oem getvar al
Click to expand...
Click to collapse
returns the "unknown remote command" message.
I'm really hoping someone else has run into something like this. Again- thanks for your time and any help you can give.

I Have the Same issue as you describe, brought Mine Back to the retailer to get it replaced ><

Failed root attempt. Most likely to be a corrupt emmc. When you get to that menu with the mode options, what happens when you immediately select "download mode", does it reboot or go to download mode?.
Beamed in by telepathy.

I have the same issue I can't get to download mode or recovery mode, when I boot to download mode I get the message "Failed to boot to download mode". Please anyone can help with this??

Redfox511 said:
I have the same issue I can't get to download mode or recovery mode, when I boot to download mode I get the message "Failed to boot to download mode". Please anyone can help with this??
Click to expand...
Click to collapse
What model do you have exactly?
OPJA100 or wich?
Android 6.0 or 5.1 ?
Firmware running ?
need some information....

shivasrage said:
What model do you have exactly?
OPJA100 or wich?
Android 6.0 or 5.1 ?
Firmware running ?
need some information....
Click to expand...
Click to collapse
I have OPJA100 before the device crashes I as on android 6.0 now I think there is no firmware on the device as it just boots to bootloader, the thing started with a reboot loop then I did a hard factory reset but it didn't work out so I tried to install a new firmware but I couldn't as S-On after multiple tries I ended up can't boot to download or recovery mode with the message "failed to boot to download/recovery mode". That's everything

I had same problem last week.
I don't have warranty on my device, so I look forward for a user solution.

throcker said:
I had same problem last week.
I don't have warranty on my device, so I look forward for a user solution.
Click to expand...
Click to collapse
same problem

guys, there are so many threads about self-bricking devices...I never saw anything since this month...what's happening?!

throcker said:
guys, there are so many threads about self-bricking devices...I never saw anything since this month...what's happening?!
Click to expand...
Click to collapse
Like the Nexus 5X and Nexus 6P, the M9 has reached the age (~1.5 years old) where hardware issues begin to show.

computerslayer said:
Like the Nexus 5X and Nexus 6P, the M9 has reached the age (~1.5 years old) where hardware issues begin to show.
Click to expand...
Click to collapse
after m9 died I switched to nexus 5x. wrong move ahahah
at least I have warranty on this

I purchased two Nexus 5X phones days before the problems started getting reported. My folks are using them. Ah well. They're great devices and I'll just have to hope that these two don't have the problems they some others do. So far, so good.

socrates23 said:
I've also tried using the HTC One M9 toolkit found here on the forums (though maybe there's some functionality I missed, I tried to be thorough).
I've also tried using the HTC sync software and downloading the RUU but after running the RUU executable nothing happens. I then dug into trying to make sure the MID and CID are correct but again, the command returns the "unknown remote command" message.
Click to expand...
Click to collapse
Hey there, the command is not fastboot oem getvar al, you should try:
Code:
fastboot getvar all
or you can return specific thing like:
Code:
fastboot getvar cidnum
And wow...I'm finding my self reading this topic, because i have the exact same issue with one of my customers phones that brought me his soft bricked M9 device.
You described the problem perfectly and this is the exact troubleshooting results i get too.
I was never a fan of HTC replacing the classic fastboot bootloader with the damn download mode, which bring us to such a situation where we get to dead end when no download mode and no recovery mode with locked bootloader.
If we could just unlock the bootloader, then we could flash easily a recovery and then flash the stock rom or custom rom, but what makes things more complicated is when we are not even able to get there due to that new download mode thingy in htc.
My only solution and work around i can give you regarding this, is finding the exact RUU specific to your model since the current state of the device will ONLY be able to accept the stock RUU firmware since it is S-ON.
Finding the stock RUU for your device can be quiet challenging, since you have to know the cidnum with the command:
Code:
fastboot getvar cidnum
That will basically help you know the right RUU for your device.
But in my case, it didn't display the cidnum since i guess the guy before me tried to flash a wrong software or run some fastboot commands that removed the data partition.
And he can't even tell me to what company it was belongs too, because the whole idea of figuring out what the cidnum is, helps you know the cellular provider that responsible on that device which will basically help you at the end of point finding the right RUU to make the device accepting it.
There are 2 methods flashing RUU's:
1. Downloading the exe file and running as admin and hoping for good.
2. Downloading the zip file and renaming it to the matching name and putting it in the sd-card and letting the device recognize it while you starting download mode(even though it doesn't load download mode).
It would basically flash the whole thing including recovery, download mode, software, firmware and put it into factory setting.
So yea, that's pretty much my direction regarding this problem. I would also really appreciate some of the proffis here to give us a hand here which would be a great help!
Let me know in the comments if you solved it somehow.
That's my getvar all status atm:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54MYJ03126
all:
finished. total time: 0.141s

reichrepairs said:
And wow...I'm finding my self reading this topic, because i have the exact same issue with one of my customers phones that brought me his soft bricked M9 device.
You described the problem perfectly and this is the exact troubleshooting results i get too.
I was never a fan of HTC replacing the classic fastboot bootloader with the damn download mode, which bring us to such a situation where we get to dead end when no download mode and no recovery mode with locked bootloader.
If we could just unlock the bootloader, then we could flash easily a recovery and then flash the stock rom or custom rom, but what makes things more complicated is when we are not even able to get there due to that new download mode thingy in htc.
Click to expand...
Click to collapse
Try to flash the hosd.img (fastboot flash hosd hosd.img) that corresponds to the current firmware of the phone while it's booted to bootloader. If that doesn't work try to flash it as soon as it reaches the error while booting to download mode. If the flash was sucessful, shut off the device and reboot to download mode and flash the RUU that corresponds to the current firmware. (According to this post the whole procedure needs S-OFF but I got told that it's possible with S-ON, as well, some days ago.)
reichrepairs said:
My only solution and work around i can give you regarding this, is finding the exact RUU specific to your model since the current state of the device will ONLY be able to accept the stock RUU firmware since it is S-ON.
Finding the stock RUU for your device can be quiet challenging, since you have to know the cidnum with the command:
Code:
fastboot getvar cidnum
That will basically help you know the right RUU for your device.
But in my case, it didn't display the cidnum since i guess the guy before me tried to flash a wrong software or run some fastboot commands that removed the data partition.
Click to expand...
Click to collapse
There are better ways. If you look at the firmware version (version-main in the getvar output or stated in the line with "OS" at the beginning while the phone is booted to download mode) you know exactly which RUU version you need to look for. This way you don't need to guess the correct RUU from the CID.
reichrepairs said:
And he can't even tell me to what company it was belongs too, because the whole idea of figuring out what the cidnum is, helps you know the cellular provider that responsible on that device which will basically help you at the end of point finding the right RUU to make the device accepting it.
Click to expand...
Click to collapse
This actually is a problem. Unfortunately, I don't have a solution, sorry.
reichrepairs said:
There are 2 methods flashing RUU's:
1. Downloading the exe file and running as admin and hoping for good.
2. Downloading the zip file and renaming it to the matching name and putting it in the sd-card and letting the device recognize it while you starting download mode(even though it doesn't load download mode).
It would basically flash the whole thing including recovery, download mode, software, firmware and put it into factory setting.
So yea, that's pretty much my direction regarding this problem. I would also really appreciate some of the proffis here to give us a hand here which would be a great help!
Click to expand...
Click to collapse
Step by step instructions are already posted several times here on xda. One example can be found here.
reichrepairs said:
Let me know in the comments if you solved it somehow.
That's my getvar all status atm:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54MYJ03126
all:
finished. total time: 0.141s
Click to expand...
Click to collapse
You can't get a proper getvar outputs while the phone is booted to the bootloader. It needs to be in download mode. However, I'm not sure whether the command will give you a proper output if the download mode is broken.

Yeah, there are many, many reports in the last weeks about this "downloadmode" issue
and dying emmc´s
I don´t know if it´s true but I heared somewhere that it´s
happenig to M9 with emmc´s produced by hynix.
Do you think this rumour coud be true?

Appreciate your very detailed reply @Flippy498! Thanks for that.
Long story short, in that case the only solution would be getting one of these JTags tools like XTC 2 Clip and do the S-OFF and only that way we can basically flash any software or RUU.
I was doing some re-search and sadly i had one of those clips 4-5 years ago and too bad i didn't keep it with me. But the price for that xtc2clip is ridiculously expensive that it's better finding someone who owns it and pay for his service just for the S-OFF part.
I found someone in Berlin who actually does that and hopefully he'll help me out.
Because without finding the right RUU, there is no way solving this problem. But the thing is, no matter in what mode i type the getvar all command, i don't get the cidnum number or main version since there is no download mode or recovery which disabling me from finding the right RUU for that specific m9 phone.

Hey everyone, kinda new to the forum. I pop back on every time I funk up a phone lol, started with a windows pocket PC ages ago.....ANYWAYS
Same problem.
Lost the phone for months and booted it up to the *software status modified*locked*s-on*security warning*
as soon as it has power it goes to this screen. reboot to download or recovery end in errors. Powerdown if it has juice just boots it back to the white reboot screen.
I never tried to even unlock the bootloader, flash or root anything, I got this phone for my wife.
Good news, though. I've been working with a 3rd tier HTC tech...whatever that means, and we have been working through everything step by step, soon enough I'll have an answer and I've saved all our logs, so I can share it here. We might even find out what causes this to happen. Stay tuned.

Repair was the only solution
I had the same issue as srqgeek. Worked through some options with HTC tech support and the ended up sending the handset away. Now I have it back it appears that it may have been a software issue as no parts are listed as replaced. I have noticed I have a different version of the ROM installed with the HTC standard global ROM as opposed to the carrier updated version (EE-UK in my case). I've had no issues since the re-image.
srqgeek said:
Hey everyone, kinda new to the forum. I pop back on every time I funk up a phone lol, started with a windows pocket PC ages ago.....ANYWAYS
Same problem.
Lost the phone for months and booted it up to the *software status modified*locked*s-on*security warning*
as soon as it has power it goes to this screen. reboot to download or recovery end in errors. Powerdown if it has juice just boots it back to the white reboot screen.
I never tried to even unlock the bootloader, flash or root anything, I got this phone for my wife.
Good news, though. I've been working with a 3rd tier HTC tech...whatever that means, and we have been working through everything step by step, soon enough I'll have an answer and I've saved all our logs, so I can share it here. We might even find out what causes this to happen. Stay tuned.
Click to expand...
Click to collapse

M9 boot loop

Hello, I have a weird problem with my vanilla M9.
A week ago, after a playstore update and a required reboot, it got stuck to the white htc logo. With some help, I managed to flash the stock RUU on it and checked the Unlock OEM option right away (I found out about that after the issue, so I made sure I won't encounter it again). All went well until yesterday, when I started getting crash messages from background services (send/don't send dialogs). Today I've decided to restart the phone, hoping it will get rid of these issues, but it started a boot loop - rebooting every few seconds. I've tried wiping the cache, and got mounting errors. I've wiped the data, and that seemed to work, with the mounting errors from the cache partition. I've tried unlocking the bootloader, now that I have the unlock option checked. But after selecting Yes, the phone shows the black htc logo, and after like 3 seconds it reboots again and again. I have also tried flashing the RUU zip using Flippy498's sd card method, but when selecting the flash option (volume up), I get the same 3 second boot loop. Basically, it cannot enter download mode by itself (I can only enter it via the Vol up + Vol dn + Power menu).
On top of that, after the data wipe, I now have the same neverending white htc logo. So, I am now at a loss of ideas. Can it be saved in any way?
my fastboot getvar all output is something like this, if relevant:
Code:
kernel: lk
product: htc_himauhl
version: 1.0
imei: <redacted>
version-main: 3.36.709.3
boot-mode: download
version-baseband: 01.01_U11440792_97.00.51203G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: HTC__621
Thank you in advance!

Well, as an update for people with the same problem: I'm sorry. I just sent the phone to the service, as it's still in warranty.

Download this and put it on outside of your sdcard
https://www.androidfilehost.com/?fid=24591000424948715
Click to expand...
Click to collapse
Connect your phone to charger and make sure you have enough battery to flash it
boot download mode (power+vol down) and flash it, wait -10min to finish do not force shutdown or your phone will never wakeup anymore
if you can't boot to download mode or bootloader it impossible to fix it