S-ON, HTC__102, RUU firmware need or help - Desire Q&A, Help & Troubleshooting

Dear XDA-Member!
I have a HTC Desire with this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.93.0001
(bootloader) version-baseband: 5.11.05.27
(bootloader) version-cpld: None
(bootloader) version-microp: 031d
(bootloader) version-main: 2.29.405.14
(bootloader) serialno: HT063PL02868
(bootloader) imei: 3578410370xxxxx
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-365c78d6
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.006s
Click to expand...
Click to collapse
PHONE IS HTC__102 GERMANY
- I try to RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe <- radio ver2 failed
- I have'nt gold card no usb debugging ON ROM not booting
- Rom not booting but flashboot have
What can i do more? How to find I a working rom for this phone? I would like to root and S-OFF.

Try this RUU: http://d-h.st/d44
Use this guide to flash it.
The fact that radio failed, may indicate a radio brick. This is the worst type of brick and there isnt really a known way to recover, other than to keep trying RUU's until one successfully flashes (very low chance). Good luck.

Chromium_ said:
Try this RUU: http://d-h.st/d44
Use this guide to flash it.
The fact that radio failed, may indicate a radio brick. This is the worst type of brick and there isnt really a known way to recover, other than to keep trying RUU's until one successfully flashes (very low chance). Good luck.
Click to expand...
Click to collapse
1. I downloaded and copied to sd card root.
2. Put the card in the phone and starting volume- + power
3. nothing happend: HTC Logo with four corner exclamation icon
Phone is RUU mode???
UPDATE:
1. with this RUU working: http://shipped-roms.com/download.php?&model=Desire&file=RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00.32U_5.11.05.27_release_224699_signed.exe&send_file=yes
But not booting, stop on white screen with HTC LOGO
That was is the original state
UPADTE2:
I'm installing your ROM - failed-PU
UPDATE3:
I try to reinstall RUU ROM, but not working: bootloader - bypass, radio ver2 - failed-PU
UPDATE4:
I installed RUU HTC Desire 2.3 Upgrade.exe from HTCDEV.
Phone not started, stopped HTC logo with white screen, then 1-2 minuten restarting, one more vibrating on start.
HBOOT upgraded to 1.02.0001!!!!! Radio is 5.17.05.23

End of this things. After the freezing, working the phone. Probelem is the motherboard or hardware issue.
Thank you for your help. I going to my Friend he is a hardware specialist.

tomatos said:
End of this things. After the freezing, working the phone. Probelem is the motherboard or hardware issue.
Thank you for your help. I going to my Friend he is a hardware specialist.
Click to expand...
Click to collapse
Well, actually it's a radio brick. A critical component of the software is corrupt, and this can hardly be overcome.
But yeah, changing the motherboard will solve the issue.

abaaaabbbb63 said:
Well, actually it's a radio brick. A critical component of the software is corrupt, and this can hardly be overcome.
But yeah, changing the motherboard will solve the issue.
Click to expand...
Click to collapse
Morning can make I the Gold Card After Freezing (2-3 minute) then working ~ 10 minute. Now working this phone with HTC Desire 2.3.3 RUU Rom.
Have you solution, which components on motherboard is wrong? I wan't change complete motherboard just the wrong hardware component.
Thank you for your help. I push the THANKS button

tomatos said:
Morning can make I the Gold Card After Freezing (2-3 minute) then working ~ 10 minute. Now working this phone with HTC Desire 2.3.3 RUU Rom.
Have you solution, which components on motherboard is wrong? I wan't change complete motherboard just the wrong hardware component.
Thank you for your help. I push the THANKS button
Click to expand...
Click to collapse
Well, I don't really know where the radio is stored, but changing the internal memory chip could probably solve the problem. (I AM NOT SURE AT ALL)
I don't think you can find a separate memory chip, and easily replace it. You can barely find motherboards, so I would recommend either replacing the whole motherboard, or buying a new phone.

Related

How can I reinstall Android?

Hi,
My phone stopped working after installing an app that might have contained some malicious code. I cannot get the phone into recover mode as when I boot up pressing the down or up volume button I cannot select anything.
When I connect to my computer using USB, I can use the fastbook command from the Android development kit, and reboot the phone normally. When I do this, all I can see on the screen is HTC is big writing. I can never access the SD card directly either.
During a normal boot, the phone says it cannot find a few files and hangs in the boot menu.
Anybody got any advise?
Thanks in advise.
martindublin said:
Hi,
My phone stopped working after installing an app that might have contained some malicious code. I cannot get the phone into recover mode as when I boot up pressing the down or up volume button I cannot select anything.
When I connect to my computer using USB, I can use the fastbook command from the Android development kit, and reboot the phone normally. When I do this, all I can see on the screen is HTC is big writing. I can never access the SD card directly either.
During a normal boot, the phone says it cannot find a few files and hangs in the boot menu.
Anybody got any advise?
Thanks in advise.
Click to expand...
Click to collapse
Try to install RUU from PC
card natelate
EdikNeznanov said:
Try to install RUU from PC
Click to expand...
Click to collapse
Thanks, tried that and it appears to have upgraded it to 1.02.0000, but the problem is still exactly the same.
martindublin said:
Thanks, tried that and it appears to have upgraded it to 1.02.0000, but the problem is still exactly the same.
Click to expand...
Click to collapse
can you post here what is your device information: hboot ver., radio, marvel/c/ct and other information which will help?
P.S. you don't need to write thanks, there is a button under my avatar
I had the same thing happen a few days ago... it was a PAIN to get my phone back to life!!
I was installing some fonts when it froze... then no matter what i did, it got stuck on the boot screen.
So... what worked for me was... turn phone off (which for me the only way was to take the battery out), take SD card out, put battery back, restart phone to bootloader (vol down+power). I had previously installed clockworkmod on it, so with that i could revive the phone.... BUT could not put the stock rom back on it, have tried different versions... so i'm using a custom rom (WildChild Sense) now... which BTW is much better!!
Oh and if your phone flashes this screen for a sec or two (see attachment) you don't need to worry about it, it has nothing to do with anything.... mine is working fine now and still get that message.
Good luck!
EdikNeznanov said:
can you post here what is your device information: hboot ver., radio, marvel/c/ct and other information which will help?
P.S. you don't need to write thanks, there is a button under my avatar
Click to expand...
Click to collapse
Sorry for the delay in replying, have been trying to fix the issue.
When I boot the phone, using the arrow down key, I get this information
Buzz pvt ship s-on
hboot-1.02.0000
microp-0611
touch panel-atmelc03_16ac
Radio-3.35.20.10
Dec 12 2011, 12:08:54
I have tried many different RUU downloads and they all fail.
Is there a recommended version for me to try?
Thanks
When I do a "fastboot getvar all" I get this
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0000
(bootloader) version-baseband: 3.35.20.10
(bootloader) version-cpld: None
(bootloader) version-microp: 0622
(bootloader) version-main: 2.46.0.0
(bootloader) serialno: HT0C9PY13830
(bootloader) imei: 355797040378558
(bootloader) product: buzz
(bootloader) platform: HBOOT-7225
(bootloader) modelid: PC4910000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4223mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 42e5cc47
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
martindublin said:
Sorry for the delay in replying, have been trying to fix the issue.
When I boot the phone, using the arrow down key, I get this information
Buzz pvt ship s-on
hboot-1.02.0000
microp-0611
touch panel-atmelc03_16ac
Radio-3.35.20.10
Dec 12 2011, 12:08:54
I have tried many different RUU downloads and they all fail.
Is there a recommended version for me to try?
Thanks
Click to expand...
Click to collapse
You have a Wildfire, NOT a Wildfire S. You should be asking in the Wildfire forums here: http://forum.xda-developers.com/forumdisplay.php?f=678

[Q] Factory Unlock HTC One M8 Softbrick HELP!

HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
fgarcia10 said:
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Have you flashed a custom recovery on the device? If yes, just try to restore a nandroid back from @Mr Hofs thread and your phone will be fine
Problem is, I don't think there is any nandroid backups available for his device LRA__001. First time I've seen that CID mentioned. Going by MID doesn't help much either, I think the Verizon has the same MID. Going by the "product: m8_wlv" it also indicates Verizon. I do see that he's on AT&T on his profile though but...
Being stuck on bootloader screen for 10minutes or more won't be surprising at all if he flashed a 2.xx.xxx.x firmware based custom ROM instead of a 1.xx.xxx.x version. Need to upgrade firmware in order to do that.
You don't happen to recall what version software your device ran?
Hi, I had the 2.7 TWRP recovery but found the 2.8.0.6 works better. I was able to flash PA ROM and it is working now. Plus now is rooted and S-off and super CID.
The phone has no branding and bought from amazon as unlock from factory. But is funny you mention Verizon has similar IDs because when I plug the phone to HTC sync the first splash screen shows Verizon wireless assistant and then go to the normal HTC one.
I tried the latest HD ROM and it was force closing a lot so I think the firmware is 1.... Something. I want to upgrade but don't know which one to get. Maybe I should look on the Verizon forum, thanks for letting me know that.
I spoke with developer support at HTC and they told me they will help restore to stock and escalated the call. I will let you know if they do help.
Thanks for the replies.
fgarcia10 said:
Hi, I had the 2.7 TWRP recovery but found the 2.8.0.6 works better. I was able to flash PA ROM and it is working now. Plus now is rooted and S-off and super CID.
The phone has no branding and bought from amazon as unlock from factory. But is funny you mention Verizon has similar IDs because when I plug the phone to HTC sync the first splash screen shows Verizon wireless assistant and then go to the normal HTC one.
I tried the latest HD ROM and it was force closing a lot so I think the firmware is 1.... Something. I want to upgrade but don't know which one to get. Maybe I should look on the Verizon forum, thanks for letting me know that.
I spoke with developer support at HTC and they told me they will help restore to stock and escalated the call. I will let you know if they do help.
Thanks for the replies.
Click to expand...
Click to collapse
Honestly if its that much of a hassle, you should stick with something safe, Change the MID and CID to a Dev Edition/Europe, to do a full convert and you wont have to worry about the LRA_001. If you do those 2 steps the the OTA will be automatic as follows.
Else just flash a custom recovery, wipe data/cache and so and restore with one of the TWRP backups posted around here and you'll be good to go :good:
Cool I will try that. I did not know that.
fgarcia10 said:
Cool I will try that. I did not know that.
Click to expand...
Click to collapse
Don't forget though, best steps as follow, change MID, CID, restore via TWRP backup. If youre in Europe then change the MID to EUR, but the CID change it to super CID. Youve gotten past the hardest part which is the SOFF so everything is a breeze from there on out.
You won't lose your internal data if you do any of the following steps but dumping them on your SD card would be safe too.
I had an SG manufactured one, and the OTA came out pretty weird, was an unbranded one too. changed it to Dev/Unlocked MID and the super CID, downloaded the B_US002 TWRP dump thats posted here and restored that. Might want to download the OTA too aswell would save massive time after the first 159MB ota.
Awesome. Thanks!
was any one here ever able to get things working?
i am on LRA__001 and got my radio to stop working, no phone signals
contacted HTC dev and they provided me a zip, flashing that didn't help much, still no signals and can't boot into stock recovery.
seems like i've flashed the wrong hboot or something that's causing everything to be flashed on wrong partition addresses.
any help ?
fgarcia10 said:
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
hey
were you able to get it working ?
do you still have that phone?
i need some help
genious_t said:
hey
were you able to get it working ?
do you still have that phone?
i need some help
Click to expand...
Click to collapse
This isn't the same issue as the OP. You flashed the wrong firmware which is much more serious. This thread isn't relevant to your issue, in addition to being over a year old (which also most likely won't help your issue).
redpoint73 said:
This isn't the same issue as the OP. You flashed the wrong firmware which is much more serious. This thread isn't relevant to your issue, in addition to being over a year old (which also most likely won't help your issue).
Click to expand...
Click to collapse
I am just trying to trace ppl with the same variant so I can request them to dump couple of partitions for me. and there is no relevant thread for this particular variant, some says it s bluegrass some says its verizon variant, but according to HTCDev its actually rural area variant.
genious_t said:
I am just trying to trace ppl with the same variant so I can request them to dump couple of partitions for me. and there is no relevant thread for this particular variant, some says it s bluegrass some says its verizon variant, but according to HTCDev its actually rural area variant.
Click to expand...
Click to collapse
The LRA version is the LRA version. there's no question there. Its based on Verizon, but its not Verizon.
Sounds like you are trying to make up solutions. What you need is LRA firmware or RUU (RUU may not exist).
redpoint73 said:
The LRA version is the LRA version. there's no question there. Its based on Verizon, but its not Verizon.
Sounds like you are trying to make up solutions. What you need is LRA firmware or RUU (RUU may not exist).
Click to expand...
Click to collapse
i've got complete RUU from HTCDev to flash via hboot, did flash that but lost the IMEI and baseband version under settings > about, however the getvar all is still showing that information. so just trying to figure out what went wrong. either something is missing in what they have provided. or the hboot version is mismatching.
read bout the boot process and got to know that hboot reads IMEI and baseband while booting up and holds into some shared memory variables which later read by kernel.
just trying to figure out things and also looking for somebody who can provide dumps so i can try flashing them.
genious_t said:
i've got complete RUU from HTCDev to flash via hboot, did flash that but lost the IMEI and baseband version under settings > about, however the getvar all is still showing that information. so just trying to figure out what went wrong. either something is missing in what they have provided. or the hboot version is mismatching.
Click to expand...
Click to collapse
You flashed a hacked Verizon RUU. Its not the LRA RUU, and its also not an official RUU.
redpoint73 said:
You flashed a hacked Verizon RUU. Its not the LRA RUU, and its also not an official RUU.
Click to expand...
Click to collapse
No I explained them my case and they asked to couple of days time and then they provided a zip file to flash via hboot. They claimed that they have prepared this file especially for me. I flashed that file. It was 5.0.1 with almost all the images.
One thing that I doubt is that the hboot is not updated since the android-info.txt says hbootpreupdate=12 and my getvar says 11 so just wondering whether it was updated or not.
Also I dumped mmcblk0p3 (board-info) and I can see my IMEI there too.
Just don't know where to nock my head
genious_t said:
hey
were you able to get it working ?
do you still have that phone?
i need some help
Click to expand...
Click to collapse
I did get it to work again, HTC help me to get it back to stock. I still have the phone. They send me the files to restore it.
genious_t said:
No I explained them my case and they asked to couple of days time and then they provided a zip file to flash via hboot. They claimed that they have prepared this file especially for me. I flashed that file. It was 5.0.1 with almost all the images.
One thing that I doubt is that the hboot is not updated since the android-info.txt says hbootpreupdate=12 and my getvar says 11 so just wondering whether it was updated or not.
Also I dumped mmcblk0p3 (board-info) and I can see my IMEI there too.
Just don't know where to nock my head
Click to expand...
Click to collapse
they send me the wrong files a couple of times. But they did get me the right one at the end. it seems you have the same problem I did. I still the hboot file and the system image. The hboot zip should be installed on download mode and the system image should be rename to OP6BIMG.zip and put in the sd card and re-start the phone in bootloader and let the zip install itself. It takes a long time but it worked. I have the files in my google drive I don't mind sharing it.
fgarcia10 said:
they send me the wrong files a couple of times. But they did get me the right one at the end. it seems you have the same problem I did. I still the hboot file and the system image. The hboot zip should be installed on download mode and the system image should be rename to OP6BIMG.zip and put in the sd card and re-start the phone in bootloader and let the zip install itself. It takes a long time but it worked. I have the files in my google drive I don't mind sharing it.
Click to expand...
Click to collapse
In my case they gave up, the guy said it can still be fixed but I don't know what to do.
Would you be able to share the stuff that worked for you ?
genious_t said:
In my case they gave up, the guy said it can still be fixed but I don't know what to do.
Would you be able to share the stuff that worked for you ?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0Bw_sCYzL1RITbGkzRExWTmU1d1U/view?usp=sharing
https://drive.google.com/file/d/0Bw_sCYzL1RITN0ttSVBZZ3VUYkk/view?usp=sharing

HELP, m8 stuck in bootloop at "starting apps."

hi i've got a huge problem with my htc m8. it wont boot anymore and always keeps on beeing stuck on "android is starting... starting apps." after an optimization of 167 apps. have been pulling an all nighter and im at the end of the rope unfortunatly =(.
i alrdy hard reset it several times. through bootloader factory reset, as well as recovery and wipe data/fac reset. i only can stop the bootloop by pressing power+volume up and switching into bootloader. it also takes forever to optimize the 167 apps....
after having read a few threads here and elsewhere i also did 2 recoverys with 0P6BIMG.zip with an miniSD card through bootloader/fastboot and once through htc_fastboot with RUU.zip through the CMD in win10. in all 5 cases the phone tells me it successfully "recovered"/reset its system but it still always starts again with optimizing 167 apps and then beeing stuck on "starting apps...".
the m8 is ***locked*** and S-ON with software status official. OS- 6.12.401.4. i never customized the android os and bought it brand new.
(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:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s
im grasping for straws here guys (desperately). appreciate all the help i can get. there are a lot of people here who seem to be experts in this. i am totally new to this and really hoping for guidance. thanks in advance!
I`ve had a similar issue today, while trying to revert my phone from an update to GPE Rom.
I was able to reboot my phone, and get back to the bootloader, and from there I flashed to a stock rom.
What I did was, volume up + power, and just when the phone turned black, I pushed the volume down button, and it entered the bootloader instantly.
Sorry if it didn`t help you out much, but I was stuck in the updating apps, and was able to get off rebooting loop only like that, I was stuck for about an hour on that!
Good luck!
Chubbiebr said:
I`ve had a similar issue today, while trying to revert my phone from an update to GPE Rom.
Click to expand...
Click to collapse
The OP has a stock device, so the situation is really not similar, nor have the same solution.
In addition, what the OP neglected to post here (but posted in another thread) is that his issue was caused by dropping the phone, and going major physical damage. No amount of software fixes is going to help the OP:
http://forum.xda-developers.com/showpost.php?p=67417831&postcount=1761
Chubbiebr said:
I was able to reboot my phone, and get back to the bootloader, and from there I flashed to a stock rom.
What I did was, volume up + power, and just when the phone turned black, I pushed the volume down button, and it entered the bootloader instantly.
Sorry if it didn`t help you out much, but I was stuck in the updating apps, and was able to get off rebooting loop only like that, I was stuck for about an hour on that!
Click to expand...
Click to collapse
What exactly did you try to flash (file name) and flash it how (TWRP, fastboot, etc.).?
What was the original condition? "revert from an update to GPE Rom" really isn't specific enough.
Were you on a GPE ROM, or did you fully convert to GPE using RUU (2 very different things)/ Bootloader screen is black or white?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
In addition, what the OP neglected to post here (but posted in another thread) is that his issue was caused by dropping the phone, and going major physical damage. No amount of software fixes is going to help the OP:
http://forum.xda-developers.com/showpost.php?p=67417831&postcount=1761
Click to expand...
Click to collapse
i didnt drop the phone. a 2.5 kg plate dropped on it. and i also dont think its interior is broken because of that. only the display glass is broken. the phone was working fine for hours until i tried to use the front camera and the camera app froze up. up to that point all functions were normal apart from the visuals of the broken display glass. even the touchpad/digitizer and colours of the display are working at 100%.
because of that frozen camera app i rebooted the phone. thats when it started to bootloop. the bootloader is also working fine. dislay is still working fine. it just wont boot beyond optimizing apps....
the only hardware problem that could be is: if the front camera is mailfuntioning. can it stop the android os from booting? thats the only explanation it could have for a bootloop hardware wise. if thats not the case its purely a software problem
HTC M8 Logo loop issue
Hi There
Were u able to find a fix for the below issue. Am also having the same problem with M8.
nithinrv said:
Hi There
Were u able to find a fix for the below issue. Am also having the same problem with M8.
Click to expand...
Click to collapse
You dropped a 2.5 kg plate on your M8, and caused physical damage also, like the OP? You tried to flash the RUU through htc_fastboot and SD card methods?
Please don't just post you have the "same problem" without giving any details. My experience, that these issues are never exactly the same (simply too many variables: different CIDs, version numbers, causes for the issue) and if you don't give any details, nobody can provide the proper help.
At a minimum, describe what events led to the current condition (and what that condition is), what you've tried (specific steps, file names, etc.) and the specific outcomes (error messages, other outcomes). Also do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
even i had the same prob..i fixed it by wiping the cache partition..
get into bootloader menu ..go to recovery..and then after the red exclamatory sign appears..keep pressing power button and hold and release volume up button..you will get the wipe cache partition option.
do dat and ur phone will reboot
power and volume up press.
roker22 said:
power and volume up press.
Click to expand...
Click to collapse
Is this a question or a statement? The last post already says power + vol up.
Do you realize you responded to a thread that hasn't been active for over 2 years (August 2016)? Worthwhile contribution is always appreciated. But you decided to make this your first post to xda?

Out of options, phone fails to work.

Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
boomboxie said:
Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
Click to expand...
Click to collapse
UPDATE: Seems like it`s mostly happening when installing new apps, or recovering them. Tried to remove sdcard , did`t help.
boomboxie said:
H
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
Click to expand...
Click to collapse
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
redpoint73 said:
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
Click to expand...
Click to collapse
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Will try to convert to stock GPE with RUU and update on results.
boomboxie said:
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Click to expand...
Click to collapse
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
boomboxie said:
Will try to convert to stock GPE with RUU and update on results.
Click to expand...
Click to collapse
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
redpoint73 said:
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
Click to expand...
Click to collapse
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
Click to expand...
Click to collapse
Be careful with your terminology there, to avoid confusion. From your previous post, you stated you just flashed a GPE ROM.
This isn't the same as "converting" to GPE with RUU, which puts you on GPE firmware, GPE partitioning, etc.
boomboxie said:
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
I don't know what that means, if you don't give details on what you did, and the specific results. But I'm assuming you know how to use command prompt to issue adb/fastboot commands, entered the command, and get no response (or device offline)?
If so, check that you are in bootloader-fastboot mode, have HTC drivers installed, or try different cable or USB port.
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
bombo_b said:
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
Click to expand...
Click to collapse
I tend to agree that its a hardware problem. But its always a good idea to return to full stock by RUU, to eliminate the possibility its a software issue, before concluding its a hardware problem.
boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
1) at first go to bootloader
2) connect device via usb cable into pc
3) confirm you are in fastboot mode
4) install drivers through htc sync manager
5) download the following zip
6) at first create a new folder in desktop. then copy zip into that folder & extract.
7) while press ''shift'' right clik on the new folder & select ''open command window here''
8) on the command prompt type fastboot getvar all
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Disregard this post.Sorry
boomboxie said:
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Click to expand...
Click to collapse
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
umesh.lk said:
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
Click to expand...
Click to collapse
What would be the best way to do that ?
boomboxie said:
What would be the best way to do that ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
boomboxie said:
I have newest TWRP installed.
Yes firmware is up to date.
Click to expand...
Click to collapse
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
redpoint73 said:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
Click to expand...
Click to collapse
Thanks, will update on outcome.
EDIT: I thought i was "up to date" i guess i wasn`t lol, my bad.
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failure.
(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:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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.049s
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
boomboxie said:
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failur
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
Click to expand...
Click to collapse
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
umesh.lk said:
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
Click to expand...
Click to collapse
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
boomboxie said:
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
Click to expand...
Click to collapse
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
umesh.lk said:
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
Click to expand...
Click to collapse
By that you mean: Connecting phone to PC and flashing Newer recovery or OS ?

HTC One M8 bootloop after RUU

Hi, I just got HTC One M8 stuck on black HTC logo with four triangles. To solve this I flashed official RUU but phone was still on bootloop. Now It's on white htc screen, I can boot recovery and bootloader. Flashed firmware and RUU - nothing changes.
BOOTLOADER : LOCKED
S-ON
I add my getvar :
(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) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(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
Could it be hardware issue? Thanks in advance!
What RUU did you flash (full file name) and did it run to completion, and were there any error messages?
I flashed RUU : 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
There was no errors, only FAIL90 hboot pre-update! please flush image again immediately. Please help me to find solution. Thanks in advance!
clocklock said:
There was no errors, only FAIL90 hboot pre-update! please flush image again immediately. Please help me to find solution. Thanks in advance!
Click to expand...
Click to collapse
This is common, and means you should flash the RUU again (pretty sure its supposed to say "flash image again immediately" - even though it says "flush"). Did you try to do so?
After that error it flashes image again by itself. After 8-10 min it says that everything is ok. Then i restart and get same bootloop. Maybe I'm using wrong RUU? My HTC is European version
clocklock said:
After that error it flashes image again by itself. After 8-10 min it says that everything is ok. Then i restart and get same bootloop. Maybe I'm using wrong RUU? My HTC is European version
Click to expand...
Click to collapse
It should be the right RUU. You're using htc_fastboot to flash? Maybe try downloading the RUU again, and flash again.
I flashed with htc_fastboot and used image from : https://www.androidfilehost.com/?fid=24369303960687057. Tried two times, same results. Don't know what to do next.
clocklock said:
Hi, I just got HTC One M8 stuck on black HTC logo with four triangles.
Click to expand...
Click to collapse
How exactly did this happen, where you doing something at the time? Was there any significant type of update to the phone recently? Or you just picked up the phone and it was stuck this way?
I bought it with the note that motherboard is faulty. But I thought that It's only bricked somehow. Previous owner said that he saw an error and phone shut down itself. No water damage or etc. Maybe really It is faulty logic board?
clocklock said:
I bought it with the note that motherboard is faulty. But I thought that It's only bricked somehow. Previous owner said that he saw an error and phone shut down itself. No water damage or etc. Maybe really It is faulty logic board?
Click to expand...
Click to collapse
Its the correct RUU, and I don't see any other reason why the RUU wouldn't work. Correct RUU not getting a stock device to run is a good indication that its a hardware failure. Especially since it seems the previous owner was just using the phone (assuming no recent updates or other major changes), and it shut down, and hasn't worked since; again that to me would point to hardware failure.
If you've got nothing to lose, you can try to unlock the bootloader, install TWRP and flash a ROM, and see if the condition improves at all. But my guess would be no.
How to unlock bootloader with developer options disabled? I tried to do it but it still shows that bootloader is locked. I used htcdev webpage. Any other solutions?
clocklock said:
How to unlock bootloader with developer options disabled? I tried to do it but it still shows that bootloader is locked. I used htcdev webpage. Any other solutions?
Click to expand...
Click to collapse
You don't need developer's options (debugging) enabled to unlock the bootloader. Its done by fastboot, which doesn't require debugging.
If you went through the full process at HTCDev.com with obtaining an unlock bin token, and flashed the token with fastboot per the instructions, and its still locked; then its another indication that you are looking at a hardware failure (like bad emmc).

Categories

Resources