Develop Bugs

[Q] Unrooted Desire Bootloop + Touch panel-fail, help!

Hey,
I have an Unrevoked unrooted HTC Desire with custom rom MIUI XJ A2SD.
Earlier today the phone started randomly rebooting, and the touch
screen would not work for a couple of minutes before working
normally again. Finally it shut down and upon start up it now shows
the HTC logo then goes black, then HTC logo, then black screen and keeps doing that.
I can´t get into recovery so i can´t perform a nandroid backup.
Fastboot works.
When starting the phone pressing volume down it says:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
TOUCH PANEL-fail
RADIO-5.11.05.27
What should i do?

Screens ****ed. Not much you can do really other than send it in for repair.
Swyped...

Meaple said:
Screens ****ed. Not much you can do really other than send it in for repair.
Swyped...
Click to expand...
Click to collapse
Just had the same problem so when i entered recovery i just slam d the phone repeatedly at the desk when loading Recovery and now it works have no idea why tho... but am ahappy!

RaiserTeos said:
Just had the same problem so when i entered recovery i just slam d the phone repeatedly at the desk when loading Recovery and now it works have no idea why tho... but am ahappy!
Click to expand...
Click to collapse
Best fix ever.

abaaaabbbb63 said:
Best fix ever.
Click to expand...
Click to collapse
Sometimes this is best fix...
Sorry for refreshing old topic and my bad english, but i have solution for this problem.
In this model (and other htc like hd mni) touch panel fail not mean definitely hardware crash of touch screen. Sometime after some hit or other crashes touch screen can disconnect little bit from mainboad then phone can't start properly and display touch panel fail error on fastboot. Many times with error appears charging problem and booting problem.
For my working solution is:
1. Disconnect touch screen from mainbord and connect it again
2. Charge battery for minimum 50% on phone when is turned off and orange led working or if not working on external charger or other phone.
3. Put battery, start hboot
4. Reflash by orginal htc Ruu and get beterry out
5. Charging batery to full on turned off phone
6. When green led inform about full battery problem should dissapeard.
Of course your problem can by on broken touch screen but worth try

Can I salvage this dead Desire

Hi,
A friend gave me a broken Desire. It wouldn't turn on at all. I have a Desire myself so tried my battery, still nothing. I also tried his battery in mine and it works perfect, so I don't think its a battery issue.
I put the Desire into the freezer for 15 minutes and it turned on fine. Booted up, I was able to USB tether it and put a ROM zip file on the SD card. I then tried to do a "adb devices" and it rebooted to the "quietly brilliant" logo and made the boot sound.
It then vibrated 7 times and turned off.
Now It won't turn on again.
I've pulled the battery about 5 times and its still not doing anything. No light comes on when I put it on charge.
The phone is well past warranty at this stage. I'm not sure but I think its either a PVT-3 or PVT-4.
If I put it in the freezer again, and flash a new ROM, is there any way it can be usable again, or is the only option to buy a new motherboard off eBay? OR sell the phone for parts?
Thanks.

Try to run a RUU. Search in index thread in development section.
Sent from my HTC Desire using xda app-developers app

Several vibrations at boot indicate to a hardware issue. AFAIK it was something to do with the CPU.
The Desire has a mainboard in 2 parts. The upper and lower board. You could just try to buy the one with the CPU (forgot which one that was, do some digging) and connect it to your phone, and I don't see a reason why it wouldn't work.

OK thanks for the suggestion.
The link is here:
http://forum.xda-developers.com/showthread.php?t=695667
I will just try the first one in the list tonight.

Don't try the first from the list, download 2.3 RUU from htcdev site, you have the instruction in my signature.

thanks,
I tried the download link in your sig, but it said it could not connect to the phone. I think it said USB Connection Error.
Do I need to have a SIM/SD card in it? I just booted it up to the initial welcome screen without the SIM. Does this matter?
PS, its S-ON.
Bravo pvt-3 S-ON
hboot 93.0001
microp-051d
touch panel synt0101
radio 5.11.05.27
aug 10 17:52.18

Another thing i just noticed there.
It was running fine until I did an "adb devices". Then it rebooted and died again, just after I pulled it out of the freezer.
Is it possible I'm getting all this trouble because of a USB brick?

Your device is pvt3 so it's not likely that you have a motherboard overheating issue.
My question is do you have htc sync installed, cause ruu requires it, or at least fastboot and bootloader drivers?
Sent from my HTC Desire using Flashes and Thunders

I have the android SDK installed, so I was using "adb devices" and fastboot from "program files/android/android-sdk/platform-tools".
Do I need the other drivers from HTC Sync? Or will the Android SDK ones do?

Use htc sync drivers, they perfectly do the job.
Sent from my HTC Desire using Flashes and Thunders

OK I'll install them now and try it.
BTW, I installed a custom ROM on the phone and its still behaving the same way. Will a RUU make any difference to just reflashing a ROM?

The HTC Sync drivers detected the phone and it then rebooted to some black HTC update screen.
It then started to update, but then vibrated 7 times. The progress bar moved on a slight bit after that but now its stuck on 26%.
Also, on the phone, where the progress bar is, at the end of it, theres a little white triangle with a white exclamation point inside it...
I'm curious should I pull the battery or what?

Wait for some more time, but now I'm definitely sure that you have a HW issue.
Try again with freezer.
Sent from my HTC Desire using Flashes and Thunders

Well I tried with the freezer again.
This time it managed to go to 100%. The RUU said it was successful and that my phone was now ready for use.
It then rebooted to the white HTC screen, and then vibrated 7 times.
I held volume down and power and it booted into the menu, and I saw the HBOOT is now gone from the 0.93.0001 to some 1.00 version, so the phone was definitely updated anyway.
Its back in the freezer again now. lol

After freezer it will probably boot, and then die again after some time.
Sent from my HTC Desire using Flashes and Thunders

Thats my guess too.
I am just turning it on now.
Once it boots, is there any apps I can install that can test the hardware for faults, so I can finally know for sure what the problem is?

Don't know for app like that.
Sent from my HTC Desire using Flashes and Thunders

Well, it booted anyway. Went about half way through the setup wizard, as far as the "Connect to wifi" part, then it rebooted to the white screen, where it vibrated 7 times.
Whats odd this time is that it rebooted after the 7 vibrations, and then booted again to the white screen and vibrated again 7 times. It rebooted like this 3 or 4 times, and now its off again.
I pulled the battery, and turned it on again and now its doing the same. Vibrating 7 times, rebooting, vibrating 7 times, rebooting etc. This time its in a loop and has rebooted 9 times so far, and counting. Each time vibrating 7 times and rebooting...

There should be no doubt that it's hardware issues(and as the freezer works, it is likely some overheating of sorts). Either throw it out or buy a cheap ass desire with a broken screen second hand and replace whatever is broken om the new device with what you have from you friend.
Also stop freezing it, it will likely cause water dammage inside at some point.

[Q] Possibly bricked HTC One X

Befoire you tell me this problem is already listed on the forum, I'd like to tell you I've read through them all and from what I can tell my problem is a little different;
I've had my HOX for about 6 months, I love it and never had a problem with it before (except for the overheat issue).
However, yesterday morning I woke up checked my phone and everything was fine, an hour later however the processor acted like it hung and then rebooted itself. When it booted back up I was greeted with the HOX boot menu:
*** LOCKED ****
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
MICROP-None
RADIO-5.1204.164D.30
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot: enabled
MODEM PATH : OFF
Nov 16 2012, 18:32:39
Battery level is too low to flash
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I have tried all the options and they all seem to loop back into the boot menu, when it first started I was able to power up and get to the bootmenu, however a day later it is giving me nothing unless I plug it into my pc. I have read alot of people accounting this problem to screwing up while trying to install a custom rom, something which has never been done to my phone. The only app I installed recently before the error was touch from the play store, however my contract phone bill is currently late (was cut off on friday, phone locked itself on the saturday), could it be that my carrier (vodafone UK) may have locked my phone for non-payment? Did the app cause my phone to crash? Or is this just random bad luck?
Any advice or help on this subject would be awesome

Seems like random bad luck...
Select hboot and do a factory reset. If that does not work, return the device for warranty repair.

TToivanen said:
Seems like random bad luck...
Select hboot and do a factory reset. If that does not work, return the device for warranty repair.
Click to expand...
Click to collapse
Just tried that, reboots and then loops back into the bootmenu, when selecting hboot I get an error though:
SD Checking...
Failed to open usb master mode
Loading PG46IMG.zip image...
Failed to open usb master mode
(another line here but it moves back to the hboot menu before i can read it)

The error is because you probably had it on the charger. That's normal, we all have that.
But like TT said.....return it for warranty. A full locked bootloader must give you 100% warranty !

yeah i would send it back as well.. shame but hey at least they will replace it for you or repair it

Goku80 said:
yeah i would send it back as well.. shame but hey at least they will replace it for you or repair it
Click to expand...
Click to collapse
Hi i think im having a similar problem, HOX running cyanogenmod 10.1 beta 7, i was playing with my phone last night and went a bit mad uninstalling apps (CM Updater was one :silly, i set the cpu to performance (which i hadnt really done before, not sure if has any effect) but i noticed after i tried setting it back to on demand none of the frequencies would lower i just ignored this turned my screen off and then it wouldnt turn back on so i turned it off by holding the power button and put it on charge and fell asleep and completely forgot about it until i woke up about 15 minutes ago, FANTASTIC.
It was on charge but the charge indicator was just flashing Then when i tried turning it on it only got to the cyanogenmod bootscreen. So i rebooted into bootloader where it tells me the battery is too low to flash anything, even though its been on charge all night? I then proceeded to do a factory wipe and restore my backup which succeeded but now i get as far the "htc one x with beats audio" boot screen.
I have heard that it could be from using the wrong charger which could be as i wasnt using the stock charger but as soon as i changed to that it charges(????) with a solid red indicator. Still stuck on the boot screen. I fear for the worst unless anyone can shed any light :crying::crying::crying:

Did you also flashed the boot.img from the backup and performed a full wipe before restoring ??? Otherwise it will never boot.
You cant flash anything......try this !?
Enter the recovery if you can and wipe the batt stats, then put the phone in the bootloader and execute this script from inside the fastboot folder.
http://db.tt/aLqeTpPO
Or when you have a custom recovery where you can charge inside....leave it in the recovery and try charging from there.

Mr Hofs said:
Did you also flashed the boot.img from the backup and performed a full wipe before restoring ??? Otherwise it will never boot.
You cant flash anything......try this !?
Enter the recovery if you can and wipe the batt stats, then put the phone in the bootloader and execute this script from inside the fastboot folder.
http://db.tt/aLqeTpPO
Or when you have a custom recovery where you can charge inside....leave it in the recovery and try charging from there.
Click to expand...
Click to collapse
I did a full wipe but did not flash the boot.img! Do i do this with fastboot or can i do that from the recovery?

Boot.img must be flashes with fastboot.....
Fastboot flash boot boot.img

Mr Hofs said:
Boot.img must be flashes with fastboot.....
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Ok cheers! The boot.img in the backup folder yes? Not the rom one? Also I left my phone on charge for a bit after i powered down from the bootloader and now theres no low battery warning so i guess that must be a good sign?!

Yep and if you restore the backup then yes you must flash the boot.img from that backup. And yes its in the backup folder
Don't forget to do this right after flashing the boot.img
Fastboot erase cache
It prevents from having problems booting into the recovery

yessssssssss!!!!!! thank you so much you are an actual hero!!!!!! second problem ive had and both times youve helped me fix it!!! next time i wont get high before i start messing with system files and stuff lmao

Haha good thing its sorted.....again :
CASE CLOSED !

Sense Home errors. Restarted. Hang on HTC screen. Factory reset. Rinse repeat. Help!

Hey guys
I have an annoying problem and I'm stuck what to do now. First the history. So I converted my phone to developers edition to get the Marshmallow update. That all went fine and my phone has been fine for awhile, running MM just fine.
Last few days my phone started playing up. I think I recall updating Sense Home through the Play Store. Since then things like entering settings would crash and an error pop up. So I'd restart the phone, however it never makes the restart. It basically gets to the HTC logo and hangs on that. The only thing it allows me to do is I can press and hold power and volume up to restart it, then power and volume down to enter fastboot\hboot and through to recovery. It doesn't matter how many times I reboot system, wipe cache from recovery, it'll hang on HTC logo screen again.
The only option I have is to use the factory reset option from the fastboot\hboot screen. This restarts the phone and boots through to new phone setup.
Great!
No.
I start going through the setup and repeatedly I get an error pop up "Sense Home unexpected error reported to HTC". I dismiss it, few seconds later back again. I can finish the setup and get to Home screen. The error still persists until I go in to the Play Store and update Sense Home. So I do that. It all seems fine. Then HTC lockscreen updates and asks me to restart. I restart and...BOOM. I'm back to square one and stuck on HTC logo screen.
I can only assume my phone has corrupt software, which a factory reset does nothing for. Can anyone advise what I can do? Here are some details:
Software status: Modified
UNLOCKED
M8_UL PVT SHIP S-OFF
CID-BS_US001
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.1540.4
eMMC-boot 2048MB
Nov 27 2015, 01:21:29.0
I've also attached a shot of messages I get when changing from HBOOT to FASTBOOT if its of any cause of concern?
Cheers for the help guys!

So I've just downloaded and ran the RUU from HTC. Currently at "Android is starting... Optimizing app X of XXX" where I've been before...lets see how it progresses beyond that.

Happy to report, this solved my problem.

Soft Brick from bad cable?

So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.

Lohboh said:
So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Click to expand...
Click to collapse
So you can't even get to download mode by holding power+vol down for several seconds?

Tarima said:
So you can't even get to download mode by holding power+vol down for several seconds?
Click to expand...
Click to collapse
No, it just brings up the same issue of it getting stuck on the monochrome HTC logo.

no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?

ffuser1 said:
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
Click to expand...
Click to collapse
I've tried that, and I have the latest TWRP.