Develop Bugs

[Q] i think my Desire HD bricked ! please help !

Hi,
I was trying to root my phone with the guide that is on this forum, but then when i restarted my phone, it was stuck on the white "HTC" boot screen. Then i tried to do a "Factory Reset" in hboot and rebooted, and still stuck on the boot screen. I tried to put a PD98IMG.zip as it was prompted in hboot as "no image or wrong file", so i loaded PD98IMG.zip onto my SD card, and still not working. any suggestions ?
my phone is S-ON.

I guess your phone is branded ? If that's the case, you need to follow the tutorial for a goldcard.
Also, if your rom is 1.7x or 1.8x, you can't root it. You have to follow the downgrade tutorial 1st

Mine took 30 mins to boot once. You could try the ruu look in dev section, you just flash it from Windows, then start again. Was your she branded?
Sent from my Desire HD using XDA App

Howling Wolf said:
I guess your phone is branded ? If that's the case, you need to follow the tutorial for a goldcard.
Also, if your rom is 1.7x or 1.8x, you can't root it. You have to follow the downgrade tutorial 1st
Click to expand...
Click to collapse
<-- This
I was in the same situation, downgraded ROM and clockwork mod and did a restore and it works fine now

@Howling Wolf - I cannot get the CID for the SD card, because
in the 'adb shell' command, my command prompt says "error: device not found". But i want to know, can i still get the CID through another HTC desire phone ? and can i still update a stock rom with S-ON ? and how do i know if my phone is branded ?
I got my phone from Taiwan, a friend brought it over for me, and when i last checked it was on software version 1.37.921.1 .
@turbo_d - ill try that thnx

did you try installing the htc sync software then do adb devices

ye i did, i installed HTC sync to get the HTC drivers, but from what i noticed is that your phone needs to be "running" instead of being stuck on the white HTC boot screen or even the hboot doesnt pick up the device aswell >.<

Totoro_tw said:
ye i did, i installed HTC sync to get the HTC drivers, but from what i noticed is that your phone needs to be "running" instead of being stuck on the white HTC boot screen or even the hboot doesnt pick up the device aswell >.<
Click to expand...
Click to collapse
Try going into bootloader, and then run adb from pc..

@SAPPH1RE - i tried that but thanks for the help !
ok i acquired my CID through linux, but now its telling me
main version is older !
update fail.
any suggiestions ? my current software version of the phone is 1.37, which stock RUU should i be using ?

If you are on 1.37 you should be fine to continue with getting s-off and such. You don't need to upgrade or downgrade your ROM until you achieve s-off. And then you should upgrade to a custom ROM such as LeeDroid.
Sent from my Desire HD using XDA App

did you get it working ?

I fixed mine a few weeks back by doing a full wipe and then loading a fresh ROM

Thing is, i cant get my phone to start up, so i need to flash a stock rom, so that i can get my phone started and then do S-OFF. But it keeps telling me "Main Version is older!"
ive tried 2 roms already, 1.32 and 1.72 RUU. What could be the problem ?

thnx problem solved, the gold card wasnt done properly, so i re did everything.
thnx for the help guys !

paulcoop007 said:
I fixed mine a few weeks back by doing a full wipe and then loading a fresh ROM
Click to expand...
Click to collapse
@paulcoop007 i have same problem with you, same version with your phone and S-ON. and my phone at black screen with htc. how can i fix it. can you explain how did you fix your phone?

[Q] HTC One X stuck on bootloader screen!!!

Hey everyone!
I recently unlocked the bootloader and installed the latest ClockWork Mod Recovery 5.8.3.1 on my HTC One X. I was trying to install the Android Revolution HD theme on my phone, it didn't install and when I restarted my phone - it got stuck on 'HTC quietly brilliant screen'.
I have tried a lot of the tutorials but I am having no luck and am very sad and frustrated with my phone now.
I updated my phone to software version 1.28 before doing all the above. Right now my phone is unlocked and the CWM is installed and works.
I downloaded the RUU for my phone which is:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed
Whenever, I try to run the RUU there is some kind of problem. At first it was battery below 30%, now it was get the correct version.
I tried flashing boot.img and system.img via command prompt but the system.img flash does not work for some reason.
I know that in order to run the RUU, I need lock the bootloader and I think I need a stock recovery.
But I am confused, the RUU is 1.26, but my phone software was 1.28 - so what do I do?
Anyone please help. Thank you very much.

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

OTA Update fails to install on HTC one M9. Help!

I recently bought an Unlocked HTC one M9 from eBay. It was on Android 5.0.2 (1.32.617.6) and I received an update notification for 1.32.617.30. When I clicked to install it, it fails saying error in cache with error 7. I think since it's a used phone the device software has been tampered before therefore the OTA update fails. I don't know the device history.This is what I found in bootloader mode.
Software status: Official
S-OFF
Bootloader:Locked
It is super CID (11111111)
And it has stock recovery.
I have tried flashing 1.32.617.6 stock ROM from stock recovery after I found it on XDA. It also failed saying signature verification failed. I searched this forum and found that someone had the same issue and they had to flash 1.32.617.6 using a SD card formatted to FAT32. I don't have a SD card so I couldn't try it.
I also tried HTC's latest RUU. EXE for Unlocked/Developer edition but it doesn't run well. It starts and shuts down after it asks me to agree to terms and conditions. I have latest HTC sync manager and it recognizes my phone. I will be trying this again on some other computer.
I really want to update my device to the latest version of OS. Please help me! I don't know what else to try.

You cannot flash an ruu because the device is modified. The easiest option is to flash an unsigned update. Unlock your bootloader and enable usb debugging first though.
Beamed in by telepathy.

I don't understand in what way the device is modified because it says bootloader Locked not relocked and everyrhing is stock. I thought it might have been restored to stock after rooting or what not. If that is the case shouldn't I be able to install OTA update?
Anyways I wanted to know if there is some way where I don't need to unlock bootloader or root it. I want to stay on stock OS.

Update: used RUU.EXE on Windows 7 computer and it worked. For some reason Windows 8/10 is not good with running external exe files.

Have I messed up my HTC10

I have a HTC 10 Verizon which is s-off and on 2.41.605.12
Like this
https://photos.app.goo.gl/SaDih6PLt1NyMa2A9
https://photos.app.goo.gl/o5WFVxVDxQH8NFf17
And I want to update it with LeeDrOiD
I first flashed the Verizon Oreo firmware with no boot IMG and with Twrp and Flashing the room . It ends up the phone showed the boot logo and heats up. Then I head to the download mode and see this
https://photos.app.goo.gl/NUjhm4zTpa6V6dX8A
The CPU is unknown.
What should I do ?
I am also afraid that the s-off is gone and I can't root my phone.

Flash the 2.41.605 RUU. Via the SD card method.