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).
Related
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.
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
Mine was stucked in boot loop after flashing incorrect ROM (i think)
Right now it can boot into recovery but cannot find any ROM that would install. After searching I think the solution would be flashing the RUU(i think also) but I couldn't find the correct one, here are my details
EVITA PVT SHP S-ON RL
HBOOT-1.14.0002
RADIO-0.19
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jul 11 2012,14:36:28
*********
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 0.19as.32.09.11_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT29VW306913
(bootloader) imei: 359691048837242
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I believe everything was already deleted and no backup.
Please help me fix my HTC.
Thanks in advance.
Your phone is not an HTC One X International. The first line shows EVITA PVT SHP S-ON RL
This HTC One XL or One X (North America)
Do you know which model you have?
If your One x Evita is a AT&T branded phone. Try this RUU.
dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Source: http://www.htc.com/us/support/htc-one-x-att/news/
If it does not work, browse and try any of the RUU here.
http://androidruu.com/?developer=Evita
SÜPERUSER said:
If your One x Evita is a AT&T branded phone. Try this RUU.
Source:
If it does not work, browse and try any of the RUU here.
Click to expand...
Click to collapse
Hi, thank you for your reply, yes I have an AT&T, hopely this works, its been weeks that my phone is not working, BTW what will be the correct process to install this RUU? Do I need to relock my HTC? or just rebootRUU?
Another info that I like to share , "fastboot get version-main" & "adb devices" doesn't display any information, only in "getvar All' where I got some information
modelid: PJ8310000 - This is what I have when I execute fastboot getvar All
Oh my, what happened?
It was in the middle of installing RUU when i thought it will finally repaired.. It shuts down & no longer charging? I tried to wait by keeping it plugged but still no led light, but everytime i plug & unplug it could here that my computer is detecting it?
What happened?
daxjeremy said:
Oh my, what happened?
It was in the middle of installing RUU when i thought it will finally repaired.. It shuts down & no longer charging? I tried to wait by keeping it plugged but still no led light, but everytime i plug & unplug it could here that my computer is detecting it?
What happened?
Click to expand...
Click to collapse
It is recommended that you do "fastboot oem relock" before running the ruu.
Did you make sure that the phone had 100% charge BEFORE you ran the ruu file?
If the phone died...its bricked
Can you boot the phone to Hboot?
SÜPERUSER said:
It is recommended that you do "fastboot oem relock" before running the ruu.
Did you make sure that the phone had 100% charge BEFORE you ran the ruu file?
If the phone died...its bricked
Can you boot the phone to Hboot?
Click to expand...
Click to collapse
Oh my, I don't know its battery capacity before I run the RUU
Yes I had the fastboot oem relocked before RUU
But now, I cannot boot the phone, its not even have led light
Hi, is my phone will be just a paperweight? or there's still hope to unbrick my HTC? Please help.
daxjeremy said:
Hi, is my phone will be just a paperweight? or there's still hope to unbrick my HTC? Please help.
Click to expand...
Click to collapse
Your device is dead. You can unbrick it if you have access to a Riff Jtag tool. This tool cost £191.66 (ex. VAT) to buy new.
http://www.fonefunshop.co.uk/Unlocking/riff_box.htm
You can either solder you own cables to the pinout or buy this ready-made adapter for the PJ8310000
http://multi-com.eu/,details,id_pr,14355,key,jtag-for-htc-one-xl-x-att-pj83120-pj83100.html
http://www.pak-gsm.com/attachments/...3100-repair-boot-sn-cid-htc_one-x-pj83100.jpg
http://www.riffbox.org/jtag-news/riff-jtag-htc-att-unbrick-imei-supercid-repair-supported/
http://www.brickedmyphone.com/hard-bricked-htc-one-x-att-evita-repaired-with-jtag/
https://www.youtube.com/watch?v=4X14NkD9J_o
*Send an email to this guy. He might be able to help you.
http://www.brickedmyphone.com/products/jtag-unbrick-service/
Well, I guess its time to say goodbye to my HTC.
Thanks everyone.
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
xunholyx said:
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
Click to expand...
Click to collapse
I tried that, but it doesn't flash the ROM. Instead it starts flashing and then restarts back into TWRP midway. I tried flashing superuser the same way but to no avail.
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
R3dact said:
I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On
Click to expand...
Click to collapse
Are you sure it was ever s-off? S-off isn't need to flash ROMs, root, or a great many other things.
The only way you could have gotten s-off is with the sunshine app ($25); unless you did s-off with firewater before that method was disabled in Dec 2014.
R3dact said:
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Click to expand...
Click to collapse
There is rarely ever a reason to go into the Advanced section. But if you do, its called "Advanced" for a reason. You shouldn't be wiping any partitions on this device without understanding what it means, and what the results will be.
R3dact said:
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part)
Click to expand...
Click to collapse
If you haven't installed a new TWRP version in a year, there is no way its the "latest".
There is also no reason to guess at this. It says the TWRP version number right on the main screen of TWRP. You're always better of giving the specific number, instead of just saying latest. Folks on here often post they have the "latest" TWRP. But once prompted for the actual version number, I often find its something very old, often 2 years old!
R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Can you plz post fastboot getvar all here without the imei or serial#. We may be able to find you an RUU that may be able to recover your device.
Sent from my Nook HD using XDA Labs
ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
smub said:
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
Click to expand...
Click to collapse
Jesus. 1.54.651.8 OS? That phone has never been updated since forever.
Go to this thread for instructions and links to update your device.
You want the ones that aren't "Harman"
EDIT: You are S-Off, so keep that in mind (security: off from your getvar)
Feel free to send me a PM if you need further instructions.
I wonder I anyone can point me in a right direction ?
After Factory Reset phone went into White HTC Screen and stopped. I'm only able to access Bootloader and Stock Recovery now. There is no OS.
OS.1.21.401.1
HTC___001
HBOOT 3.19.0.0000
S-ON
LOCKED
Software Status: Official
I tried to Unlock bootloader. I used Hasoon's tool. I confirmed YES to unload bootloader. But after restart Bootloader is still locked.
I tried to flash boot.img and recovery.img but all FAILS.
I can access the phone via ADB but anything flashing always fails. Tried sideload via ADB in Phone's recovery. But always Fails.
I can't access SD via Recovery, says E: mount fail. Tried to re-format the SD but no result
To me it seems like bootloader is corrupt and seems that without proper hardware I won't be able to do anything...
I spen many hours now and about to give up. Please let me know if I missed anything before I will, sadly, have to try professionals.
Many thanks to everyone.
Vash
panagath said:
Hello, thanks for the reply. What I see are the following:
LOCKED
HBOOT - 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.61.4
Click to expand...
Click to collapse
Did you find solution/fix pls ?
I seem to have similar problem.
After Factory Reset phone went into White HTC Screen and stopped. I'm only able to access Bootloader and Stock Recovery now. There is no OS.
OS.1.21.401.1
HTC___001
HBOOT 3.19.0.0000
S-ON
LOCKED
Software Status: Official
I tried to Unlock bootloader. I used Hasoon's tool. I confirmed YES to unload bootloader. But after restart Bootloader is still locked.
I tried to flash boot.img and recovery.img but all FAILS.
I can access the phone via ADB but anything flashing always fails. Tried sideload via ADB in Phone's recovery. But always Fails.
I can't access SD via Recovery, says E: mount fail. Tried to re-format the SD but no result
To me it seems like bootloader is corrupt and seems that without proper hardware I won't be able to do anything...
I spent many hours now and about to give up. Please let me know if I missed anything before I will, sadly, have to try professionals.
Vash
vagon1 said:
Did you find solution/fix pls ?
I seem to have similar problem.
After Factory Reset phone went into White HTC Screen and stopped. I'm only able to access Bootloader and Stock Recovery now. There is no OS.
OS.1.21.401.1
HTC___001
HBOOT 3.19.0.0000
S-ON
LOCKED
Software Status: Official
I tried to Unlock bootloader. I used Hasoon's tool. I confirmed YES to unload bootloader. But after restart Bootloader is still locked.
I tried to flash boot.img and recovery.img but all FAILS.
I can access the phone via ADB but anything flashing always fails. Tried sideload via ADB in Phone's recovery. But always Fails.
I can't access SD via Recovery, says E: mount fail. Tried to re-format the SD but no result
To me it seems like bootloader is corrupt and seems that without proper hardware I won't be able to do anything...
I spent many hours now and about to give up. Please let me know if I missed anything before I will, sadly, have to try professionals.
Vash
Click to expand...
Click to collapse
Your device is not regular M8, it's htc M8s.
You can try to RUU - https://forum.xda-developers.com/showpost.php?p=70306458&postcount=2
Anything ask here not in M8 section - https://forum.xda-developers.com/htc-one-m8/one-m8s-general
---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM ----------
panagath said:
Hello, thanks for the reply. What I see are the following:
LOCKED
HBOOT - 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.61.4
Click to expand...
Click to collapse
I can't remember whether there is RUU for your device. I'll check later tonight.
For the time being, try to install stock 6.12.61.4 firmware and see whether this helps or not.
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
ckpv5 said:
Your device is not regular M8, it's htc M8s.
You can try to RUU - https://forum.xda-developers.com/showpost.php?p=70306458&postcount=2
Anything ask here not in M8 section - https://forum.xda-developers.com/htc-one-m8/one-m8s-general
---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM ----------
I can't remember whether there is RUU for your device. I'll check later tonight.
For the time being, try to install stock 6.12.61.4 firmware and see whether this helps or not.
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Click to expand...
Click to collapse
That's interesting ! I will give it a go this evening. Did not think it could be M8s. Thank you !
Vash
---------- Post added at 10:57 AM ---------- Previous post was at 10:56 AM ----------
panagath said:
Hey, thanks for the reply. I haven't managed to do anything neither did I spend a lot of time on this. I was waiting in case someone could help. Such a shame if the phone is bricked. I do not know if it is worth taking to professionals as its value as a used phone is quite low at the moment...
Click to expand...
Click to collapse
Yes you are right. The only way is to keep trying with these phones, until you succeed
---------- Post added at 11:30 AM ---------- Previous post was at 10:57 AM ----------
ckpv5 said:
Your device is not regular M8, it's htc M8s.
You can try to RUU - https://forum.xda-developers.com/showpost.php?p=70306458&postcount=2
Anything ask here not in M8 section - https://forum.xda-developers.com/htc-one-m8/one-m8s-general
---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM
Click to expand...
Click to collapse
How can you say that it is M8s and not M8 please ? I had a problem with another M8 before, seems it could be for the very same reason (could be M8s afterall)
Thank you
Vash
vagon1 said:
How can you say that it is M8s and not M8 please ? I had a problem with another M8 before, seems it could be for the very same reason (could be M8s afterall)
Thank you
Vash
Click to expand...
Click to collapse
Based on the OS no. that you wrote. Regular M8 doesn't have that version, only M8s does.
To really confirm, write here all the details that you see on bootloder because your current one is incomplete.
Better if you give result of fastboot getvar all (without serial & imei no.), this will be truly complete details.
update
ckpv5 said:
Based on the OS no. that you wrote. Regular M8 doesn't have that version, only M8s does.
To really confirm, write here all the details that you see on bootloder because your current one is incomplete.
Better if you give result of fastboot getvar all (without serial & imei no.), this will be truly complete details.
Click to expand...
Click to collapse
Hi Matey
Update. Downloaded the file, placed to SD card and rebooted to bootloader. Update started ok, but soon message popped up : Device halted due to Large Image update fail!
Device rebooted, but now it's blinking orange led but can't start it or anything. Will keep it on charger until tomorrow and see if I can start it again.
My Getvar bellow :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.21.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT554YS01064
(bootloader) imei: 358031060751297
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(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: 7900fbfd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
The attachment below is from someone else, for illustration purposes only. As did not manage to take a photo of mine. But message looks exactly the same..
vagon1 said:
Hi Matey
Update. Downloaded the file, placed to SD card and rebooted to bootloader. Update started ok, but soon message popped up : Device halted due to Large Image update fail!
Device rebooted, but now it's blinking orange led but can't start it or anything. Will keep it on charger until tomorrow and see if I can start it again.
My Getvar bellow :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.21.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT554YS01064
(bootloader) imei: 358031060751297
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(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: 7900fbfd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
The attachment below is from someone else, for illustration purposes only. As did not manage to take a photo of mine. But message looks exactly the same..
Click to expand...
Click to collapse
Seems I managed to brick my M8s. After failed updated and device restart it wont turn back on. Only orange LED is repeatedly flashing when plugged to the charger or PC. PC detects that something is connected by doesn't recognize it. Wont respond to any ADB commands. I also tried VOL UP/DOWN + POWER BUTTONS for 5minutes a number of times, but nothing.
I had similar problem with HTC One Mini 2, had to take phone apart and disconnect the battery for a few minutes. Phone started OK and worked fine after this. But really don't want to take this M8s apart to disconnect the battery. As it's not mine.
Don't know if to keep the phone on charger, or let it rather disconnected and discharge.. ??
Any help would be much appreciated.
Vash
vagon1 said:
My Getvar bellow :
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-main: 1.21.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__001
The attachment below is from someone else, for illustration purposes only. As did not manage to take a photo of mine. But message looks exactly the same..
Click to expand...
Click to collapse
First to answer your earlier question how to know whether your device is M8 or M8s.
As you can see in your getvar result, the product is m8ql_ul which belongs to M8s. M8 is m8_ul for GSM version.
Now your thread already been moved to M8s section. Hoefully someone familiar with M8s can assist here.
I can only assist on general term and idea.
With your getvar result, now we know you have a Lollipop. The RUU is for Marshmallow. To install a Marshmallow RUU (for the case of M8), you need first to install Marshmallow firmware then only can install Marshmallow RUU. That's explained the Large image failure. Unfortunately I don't know whether anyone post any firmware only for 2.10.401.1 so you can install the RUU after.
Getting this Large image failure doesn't brick a device. With S-On it's either the RUU is successfully installed or failed. And usually will only be successfully installed when the problem is firmware & software related. When a hardware problem like corrupted emmc, RUU won't be able to fix it.
As you used Hansoon toolkit earlier which is meant for M8 not M8s, not sure whether that have any effect on your device hardware.
Let's see whether anyone with M8s has any knowledge on how to fix your problem.
ckpv5 said:
First to answer your earlier question how to know whether your device is M8 or M8s.
As you can see in your getvar result, the product is m8ql_ul which belongs to M8s. M8 is m8_ul for GSM version.
Now your thread already been moved to M8s section. Hoefully someone familiar with M8s can assist here.
I can only assist on general term and idea.
With your getvar result, now we know you have a Lollipop. The RUU is for Marshmallow. To install a Marshmallow RUU (for the case of M8), you need first to install Marshmallow firmware then only can install Marshmallow RUU. That's explained the Large image failure. Unfortunately I don't know whether anyone post any firmware only for 2.10.401.1 so you can install the RUU after.
Getting this Large image failure doesn't brick a device. With S-On it's either the RUU is successfully installed or failed. And usually will only be successfully installed when the problem is firmware & software related. When a hardware problem like corrupted emmc, RUU won't be able to fix it.
As you used Hansoon toolkit earlier which is meant for M8 not M8s, not sure whether that have any effect on your device hardware.
Let's see whether anyone with M8s has any knowledge on how to fix your problem.
Click to expand...
Click to collapse
Thank you for the reply, yes there are some seriously valid points. I'm still hoping I'll be able to ressurect the phone. But before I had One Mini 2 with exactly same symptoms and had to take the phone apart, disconnect the battery and when put all back together phone worked again. But really want to avoid doing this... I'll give it a couple of days playing with buttons and charger and if phone doesn't start I will take it apart and do the battery trick.
Once working again will load a Lollipop on it and hopefully phone will work. If emmc is buggered then I think the phone is done...
Will keep everyone posted about results..
Again thank you very much
Vash