Develop Bugs

[Q] Desire HD almost dead (only boots to fastboot). Any way to S-ON?

I had a Desire HD for a year. I just started rooting and using custom roms three months ago.
A few days ago, when I got the phone from charging, I found it frozen. I restarted it to get a looping "force close" for almost all processes. I restarted it again to the same result; the third time I restarted the phone emited 7 short vibrations just after powering it, and after some time in the initial HTC logo it froze in a black screen.
I tried to reflash my last custom rom I used, so I booted to ClockworkMod recovery and tried to reinstall the last ZIP file I kept on my SD card from last time, it installed ok, but then I got the exact same scenario: 7 vibrations, HTC logo, black screen of death.
Later, I tried to flash another custom rom, but now I can't boot to recovery. It does the exact same thing as trying to do a standard boot.
So now I'm stuck in Fastboot. I tried flashing a stock rom (downloaded the lastest official RUU), but while it seems to flash it ok, it still hangs the same. I also tried to flash copying the ROM.ZIP file from the RUU to the root of the SDCARD as PD98IMG.ZIP, but while it also seems to flash the ROM ok, it still fails to boot.
This is what I discovered (Googling):
-The 7 vibrations means bad CPU. What I don't understand is why fastboot works perfectly without any hang but can't boot even in recovery mode.
-I can't use my warranty while the phone is ENG S-OFF.
I think I succeeded to flash a stock ROM, so now the only thing that keeps me to carry my phone to fix is the ENG S-OFF. Is there a way to set ENG S-ON while in fastboot?

spyd77 said:
I had a Desire HD for a year. I just started rooting and using custom roms three months ago.
A few days ago, when I got the phone from charging, I found it frozen. I restarted it to get a looping "force close" for almost all processes. I restarted it again to the same result; the third time I restarted the phone emited 7 short vibrations just after powering it, and after some time in the initial HTC logo it froze in a black screen.
I tried to reflash my last custom rom I used, so I booted to ClockworkMod recovery and tried to reinstall the last ZIP file I kept on my SD card from last time, it installed ok, but then I got the exact same scenario: 7 vibrations, HTC logo, black screen of death.
Later, I tried to flash another custom rom, but now I can't boot to recovery. It does the exact same thing as trying to do a standard boot.
So now I'm stuck in Fastboot. I tried flashing a stock rom (downloaded the lastest official RUU), but while it seems to flash it ok, it still hangs the same. I also tried to flash copying the ROM.ZIP file from the RUU to the root of the SDCARD as PD98IMG.ZIP, but while it also seems to flash the ROM ok, it still fails to boot.
This is what I discovered (Googling):
-The 7 vibrations means bad CPU. What I don't understand is why fastboot works perfectly without any hang but can't boot even in recovery mode.
-I can't use my warranty while the phone is ENG S-OFF.
I think I succeeded to flash a stock ROM, so now the only thing that keeps me to carry my phone to fix is the ENG S-OFF. Is there a way to set ENG S-ON while in fastboot?
Click to expand...
Click to collapse
Ive had multiple vibrations thats when i was deving on something (unreleased)
Take out battery for 30mins then put it back n try recovery mode again, make sure you install a custom rom again after full wiping
EDIT: flashing stock ruu should s-on, then redo s-off that should fix it afaik
Sent from my Desire HD using Tapatalk

shaky156 said:
Ive had multiple vibrations thats when i was deving on something (unreleased)
Take out battery for 30mins then put it back n try recovery mode again, make sure you install a custom rom again after full wiping
Click to expand...
Click to collapse
I already did this (not intentionally). It doesn't change anything.
shaky156 said:
EDIT: flashing stock ruu should s-on, then redo s-off that should fix it afaik
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
If flashing stock RUU should s-on, then the flashes I tried didn't complete. I guess the flash finishes after the first boot, but as the phone hangs before booting, no flash is done?
Anyway, if this helps somehow, this is what shows my fastboot:
ACE PVT ENG S-OFF
HBOOT-0.85.2007 (PD9810000)
MICROP-0438
RADIO-26.13.04.19_M
eMMC-boot
Oct 11 2010,12:44:14
Click to expand...
Click to collapse

Phone restarts and won't turn on

For the past several months my phone would restart randomly when I used 3G, GPS or sometime just from heavy usage. It would turn off, boot to the white HTC screen but then the screen went black and it would vibrate 3 times and a led would blink. At that point the only way to turn it back on was to pull the battery and power on (although that usually didn't work until after a few tries or letting it sit for a while).
It has done this with both CM7.1 and decks 1.3 and with the Tiamat 3.3.7 & 4.1 kernels. I flashed Mason .14 on Tuesday hoping it might fix the problem. It did at first but after 24 hours it was back to restarting randomly, only this time it was worse. I was also getting a lot of force closes and it would restart even it was sitting unused. It would take hours until I could get it to successfully boot again. I attempted to do a full wipe and install CM7.2 yesterday only to find out I can not boot into recovery, attempting to do so causes the phone to turn off (I tried both through holding the power button and selecting recovery and through the bootloader).
As of right now my phone will not turn back on at all (going on 4 hours), I've had it successfully boot twice only to immediately turn off, other times it gets stuck on the white HTC screen.
I am still able to access the bootloader so I'm thinking my best option may be to place a PC36IMG.zip on my sdcard and see if I can't flash back to stock and then load CM7.2. My concerns are a) not sure if that will even work b) if the phone were to turn off in the middle of that would it completely brick my phone?
Sorry for the long post but I just wanted to provide as much info as possible. Any thoughts/suggestions would be greatly appreciated.

Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium

scottspa74 said:
Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Unfortunately that doesn't work. Flashes the recovery just fine but I still can't access it. I did manage to get my phone to boot into android after trying, not sure if that's a coincidence or not.
So I'm left with my original option, flashing a stock PC36IMG.zip. Also this might be a dumb question but can I rename anything PC36IMG.zip and flash? If so I could just rename Calkulin's format all, flash that and then repeat the process with CM7.2. Anyone know if this will work?
Edit: Should probably also ask if anyone knows what is causing this, is it a kernel issue?

Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium

imheroldman said:
Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I was able to flash back to stock and it is still having similar problems. Turns off during any sort of data usage both 3g and Wifi. The fact that it has happened on multiple ROMs, multiple kernels, and multiple radios makes me think it is something hardware related. I guess I will talk to sprint and see what they can do.
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.

mcotter said:
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.
Click to expand...
Click to collapse
Well after going back to stock but still being S-Off I decided to try reflashing Amon_RA and I eventually got it to boot into recovery. It was similar to booting into the OS, I just had to pull the battery and wait 30+ mins before trying and then boot into bootloader and select recovery. It was a PITA since I needed flash a couple things but it worked. Got it back to S-On and took it to Sprint. Of course they didn't bother checking for any of that haha but I was able to get a replacement EVO.

Phone not booting

Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.

Why don't you try flashing the latest version of ICJ (3.4) with a full wipe and see whether the problem persists? Can you enter recovery now??
However, there's always a possibility of a hardware failure... and your situation with the random reboots / recovery reboots suggests somethings wrong!

ViktorN said:
Hi, I have a very strange issue. My One X just randomly stopped working. It started to randomly turn itself off (not the usual random reboots, it would simply stay off). It started about 2 days ago and the problem continued to appear more and more often. Today it turned itself off and didn't want to boot again. When I tried to boot it, it got to the HTC quietly brilliant screen and just turned off. The battery shouldn't be the problem because I charged it and it won't boot when it's connected to the PC either. When this problem appeared, I wiped cache and dalvik cache in recovery, hoping it would fix it. After that, the phone started to turn off after spending a few seconds in recovery. Now I can't access the recovery anymore. I flashed CWM again just to be sure and it still won't boot into recovery. I also tried with fastboot erase cache and reflashing the boot.img, but no luck. I am running ICJ 3.2.1 I think (not sure about the exact version and there is no way to check it) and hboot version 1.39. S-ON, bootloader unlocked ofcourse. Booting to bootloader works and the phone stays in there without turning off. I deeply apologize if there was a similar thread to mine, but I am very, very busy because I'm writing my final exam tomorrow and I really need my phone.
EDIT: I just tried to boot it and it worked for some reason. I can't even begin to explain this problem, it is really, really weird. tried booting it a minute ago and it didn't work. I literally just wanted to enter bootloader but I guess I didn't press the volume down button hard enough and it just booted normally. It turned off again after a few seconds and now it won't boot again. When I leave it connected to the PC when it's turned off, the PC starts to make USB connect/disconnect noises quite randomly.
Click to expand...
Click to collapse
Sounds alot like a issue I had on ICJ quite a while ago.
If you select recovery at the bootloader, do you see the recovery for a split second and after that it reboots? I did flash multiple recoveries but it all didn't help. The luck I had is that fastboot was still working
I tried everything to get it to work, but nothing seemed to help. The only luck I had was that fastboot worked, and with that I managed to flash a RUU. What actually happend I don't know, but it worked again.

[Q] Is this an error of emmc chip?

Hi, everyone
I got promblem with my HTC DHD, it appeared the notice to "force close" many app all time so I cant do anything on my phone. I tried to re-up rom by sd card, everything was in normal process during flashing rom until i reboot the system after finishing flashing, it was stuck on logo screen althought i take time to wait, it was still stuck. I dont know how to shut it down or restart so i took the battery out for a while and put it back then power on again. The strange thing is it didnt show the rom i've just flashed, it worked with everything same like before flashing rom (require pass to unlock device, home screen, apps... Speicially is the error "force close" still same) . I wiped data, cache and everything before flashing. I tried to restart many times but same problem, sometimes stuck on logo screen, sometimes boot to old rom.
Then I decided to up the ship rom by laptop, after running RUU...exe file, it aks me to update the rom version for device without other option. I click update and wait, It appear the error (#171) and ask me to check the cable connection but 100% nothing wrong with the cable or connection. I tried to redo this several times as well but still same. My friend said the emmc chip is damaged and need to replace.
Could anyone help me? I still can go to recovery, hboot/fastboot screen. If emmc chip damaged, i think we still can fix it by software because it not dead.

thanhbom83 said:
Hi, everyone
I got promblem with my HTC DHD, it appeared the notice to "force close" many app all time so I cant do anything on my phone. I tried to re-up rom by sd card, everything was in normal process during flashing rom until i reboot the system after finishing flashing, it was stuck on logo screen althought i take time to wait, it was still stuck. I dont know how to shut it down or restart so i took the battery out for a while and put it back then power on again. The strange thing is it didnt show the rom i've just flashed, it worked with everything same like before flashing rom (require pass to unlock device, home screen, apps... Speicially is the error "force close" still same) . I wiped data, cache and everything before flashing. I tried to restart many times but same problem, sometimes stuck on logo screen, sometimes boot to old rom.
Then I decided to up the ship rom by laptop, after running RUU...exe file, it aks me to update the rom version for device without other option. I click update and wait, It appear the error (#171) and ask me to check the cable connection but 100% nothing wrong with the cable or connection. I tried to redo this several times as well but still same. My friend said the emmc chip is damaged and need to replace.
Could anyone help me? I still can go to recovery, hboot/fastboot screen. If emmc chip damaged, i think we still can fix it by software because it not dead.
Click to expand...
Click to collapse
Same problem here with one desire hd. Force closing many apps and wipe/flashing new rom doesn't help at all. Guess it's the emmc chip, indeed.

ONE M9 Bootloop but booting after a time

Hello
I have problem with my M9
Its normally working, no overheating no lags. Comepletly fine.
But when I turn it off and on it keeps bootlooping and after 10-30 mins it booting normally.
Is there any way to prevent that bootloops before normal boot? It freezes at first frame of boot animation and reboots.
I've tried bootloader unlock, root, install another room, factory reset, wipe data and cache and nothing.

m1ko8 said:
Hello
I have problem with my M9
Its normally working, no overheating no lags. Comepletly fine.
But when I turn it off and on it keeps bootlooping and after 10-30 mins it booting normally.
Is there any way to prevent that bootloops before normal boot? It freezes at first frame of boot animation and reboots.
I've tried bootloader unlock, root, install another room, factory reset, wipe data and cache and nothing.
Click to expand...
Click to collapse
There might be a hardware issue involved. How many stock roms have you tried?

Hovatek said:
There might be a hardware issue involved. How many stock roms have you tried?
Click to expand...
Click to collapse
I've tried 3-4 roms. But I can't install RUU cause I can't find ORANGB10 RUU with android 7 or above.
So I think the one solution is S-OFF and SuperCID , am I right?