Develop Bugs

Is My Phone Bricked?

Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.

Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.

S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.

Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.

S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...

Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.

If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app

HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.

Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.

3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!

No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app

Phone automatically starts into bootloader and flashing doesnt work

So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help

Hi,
Did you try to reflash your recovery and try to install another rom like ViperOne M8? Or if you want i can send you the stock ROM Android 6.0

Laurens54321 said:
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Click to expand...
Click to collapse
You seem to be going about things rather haphazardly:
1) Not sure exactly what "some OTAs" refers to. But there is typically only one OTA that will properly work. That being the one that is for your CID (carrier version) and for the next software version (can't skip any).
2) Along the same lines, you can't just flash any RUU. It has to be for your CID and MID (Error 130 usually means wrong MID), and equal or greater version number than main version on the phone (no "downgrading" unless you have s-off).
3) "messing around with stuff that didnt work" doesn't tell us anything about how you got to the current condition. You need to be specific and detailed, if you want us to be able to tell what you did, and how to recovery.
4) You can't unroot and OTA, it has to be a stock (never rooted) ROM and stock recovery.
5) boot.img in itself probably won't help your situation. And signature verify fail usually means you tried to flash without the bootloader unlocked (which won't work).

Are you S-OFF? If so, this works;
1) Download 0P6BIMG.zip. You'll have to Google
"dottat @ XDA M8 RUU" to get the file as I haven't
made at least ten posts here and can't post links yet.
2) Place 0P6BIMG.zip on an SD card formatted fat32 ONLY.
3) Boot your phone, allow HBOOT to recognize 0P6BIMG.zip
and follow the prompts.
RESULT: This will land you on STOCK kitkat 1.55.605.2
pre-rooted with stock recovery.
----------------------------------------------------------------
CREDIT: dottat @ XDA

Second replacement M9 won't update to Marshmallow, strange message in recovery

[Solved]
whats the meaning of the code? this is my second M9, after my old s-off M9 got replaced with a new one. but I am beginning tp suspect that the second new one is a dud also. So
this new device is LOCKED, S-On, Original firmware, stock recovery, not rooted.
So updated to 2.9.710.5 all ok
but problem : won't update to 2.10.710.x
it always fails. (It want take ota's to Marshmallow)
I tried flash Official OTAs via stock recovery via phone and sdcard both failed and got this strange error each time (image below)
tried official 0PJAIMG. zip via sd card method (so that I could try do all updates again) and got same/similar error messages.
anyone know what it means?
Any solution to get official OTA.
also If I S-off this phone and flash another firmware will it solve?
note- if i reboot, it just reboots back into 2.9.xxx.xx firmware and rom seems fine, just not able to update..

I had similar issues. Try RUU.EXE from HTC's website. Try it on Windows 7 computer. For some reason it didn't work my laptop with windows 8

mferoz said:
I had similar issues. Try RUU.EXE from HTC's website. Try it on Windows 7 computer. For some reason it didn't work my laptop with windows 8
Click to expand...
Click to collapse
there is no rru. exe for this firmware.
my question is do you know the meaning of the code in my screenshot? i trued run rru 0PJAIMG zip file same issie.

Sorry I don't know what that error means

(Solved) I used this (thanks to @Flippy498) google spreadsheet found the correct 0PJAIMG for this same rom/firmware (couldn't find it before) here https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml# renamed it 0PJAIMG.zip, put into external SD card , then powerdown and re-booted into bootloader mode , then clicked vol up button to agree "OK" flash firmware/rom. (I think the original firmware software was a bit corrupted so device could not take stock updates nor manual ota's automatically...and the mistake I made was I used an older 0PJAIMG.zip version the first time because I had correct region/cid but was not able to locate exact software version to reinstall 0PAGIMG file .....but i still dont know the exact meaning of the code in my initial screenshot).
TL: DR
Anyhow on 2.10.xxx.x now so continueing to marshmallow hopefully.

Help Please... Phone bricked while Manually updating to 6.0.0 with RUU

I have an HTC One M9 and tried to install an RUU with 6.0.0... Think is bricked... after digging a lot... the problem is I never closed or unnistalled the HTC sync manager and tried to update the software with it running, I got the advice: Get the right software for your phone, I downloaded the RUU from the official HTC page and the AT&T section, I live outside the US so OTA wasn't an option, the first attempt I got 11%, restarted phone, everthing OK, tried again, now it got till 22% but now phone is stuck in the service mode mode, the menu where I can choose: Reboot, Reboot to bootloader, etc. the phone won't boot to OS, I'm downloading this RUU http://forum.xda-developers.com/att-one-m9/general/official-att-htc-one-m9-t3380821 but since now I Can't get into the OS I don't know if the RUU will recognize the phone to update, please help me how to restore my phone or how to install the RUU from download mode or whatever.
My phone is stock, S-on, Locked, don't know why the software status now shows: Modified*** Bootloader is lock, have never done nothing to the phone, I was running Lollipop.
Thanks in advance.

It says modified because someone borked the process when trying to root it so now the phone thinks it's rooted so the update wont take. Stynk manager might be able to reflash it but if not you'll need the original ruu.exe for the version you were at or later.
Beamed in by telepathy.

[Solved] HTC M9 bricked during update

Solved.
I flashed the 3.35.401.12 RUU according to Flippy498's guide
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698 (Thread #5)
All the Phone data was wiped during the process.
shivadow and computerslayer thanks again for your help
Hello,
My friend's HTC M9 got bricked during the new Nougat update (was turned off during update).
Ever since it is bootlooping, in can put it in Bootloader and Download mode but can't load it to recovery mode.
Tried to flash the stock recovery via download mode but the phone is S-ON and locked.
What are my options in getting the phone back to life (gave up on saving any of the data on the device)?
Any help will be appreciated.
P.S.
First time handeling HTC but have a lot of experience with nexus devices
Device info:
HTC M9 himauhl
S-ON,
Locked,
OS - 3.35.401.32

You need to run the ruu.exe but I don't know if one exists for your version. You can flash any 3.35.401.xx ruu but those that aren't "xx" must match. Not sure you can flash a signed zip in s-on state..
If the ruu.exe doesn't exist then you'll either have to wait for it to be released or rtm for repair.
There is no actual way to know exactly how buggered the phone is because it died in the middle of a flash process. It is very possible it died just as it was flashing recovery, explaining why there isn't one, but I wouldn't like to bet money on it, or it being recoverable at all.
Beamed in by telepathy.

shimshi said:
Hello,
My friend's HTC M9 got bricked during the new Nougat update (was turned off during update).
Ever since it is bootlooping, in can put it in Bootloader and Download mode but can't load it to recovery mode.
Tried to flash the stock recovery via download mode but the phone is S-ON and locked.
What are my options in getting the phone back to life (gave up on saving any of the data on the device)?
Any help will be appreciated.
P.S.
First time handeling HTC but have a lot of experience with nexus devices
Device info:
HTC M9 himauhl
S-ON,
Locked,
OS - 3.35.401.32
Click to expand...
Click to collapse
You've access to download mode, so you should be able to use the SD card method of applying the matching RUU. Check out the readme thread for instructions and the necessary file.

Thanks for your help shivadow and computerslayer,
I will look at the RUU method and try to learn more about it and replay if it worked or not.

I have the same problem and have tried everything but it's still bricked. If I send it in for repair will they charge me? My phone is out of warranty (it's 1.5 years old). Since their update caused this problem you would think they wouldn't make me pay. Thoughts?

jewels76 said:
I have the same problem and have tried everything but it's still bricked. If I send it in for repair will they charge me? My phone is out of warranty (it's 1.5 years old). Since their update caused this problem you would think they wouldn't make me pay. Thoughts?
Click to expand...
Click to collapse
If you unlocked bootloader, the warranty is void anyway.
Try flashing the stock rom which doesn´t need a unlocked bootloader via htc_fastboot.exe. Place the stock rom in your sd-card. Then in bootloader it will say directly "Do you want to flash xxx.img".

albaniax said:
Try flashing the stock rom which doesn´t need a unlocked bootloader via htc_fastboot.exe. Place the stock rom in your sd-card. Then in bootloader it will say directly "Do you want to flash xxx.img".
Click to expand...
Click to collapse
Those are two different methods: The SD card method and the htc_fastboot method (which requires a PC).
And it's actually the other way round. The htc_fastboot method requires a locked or at least re-locked bootloader whereas the SD card method can be used with an unlocked bootloader, as well.