Develop Bugs

[Q] HTC Desire Stuck at Why so serious?

hi i have used evo3 on my htc desire to root and then used alpharev and boht said succussfull. Now phone starts and only shoes joker and written why so serious? doesnt go further at all. any help please
Regards

got a bootloop.. try running an RUU file (this will flash back to stack, get rid of root)
then try to root again, just a different method?
hope this helps!

how to flash with ruu if your phone is stuck not even being detected by PC. any detail please thanks regards

faisal_sherry said:
how to flash with ruu if your phone is stuck not even being detected by PC. any detail please thanks regards
Click to expand...
Click to collapse
First of all: be sure you know what you're doing. The below listed solutions might help but might also end up bricking your phone dead.
If you can enter fastboot (back while powering on the phone) and if you have a nandroid backup, you can try to flash it back using the fastboot flash command.
OR
It's possible to run the RUU update while in fastboot or hboot usb mode (back button while powering on the phone) I had the modified usb drivers installed http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install, not sure if that is needed - but the original drivers didn't work very well with my setup in general: Win7 x64 , also I uninstalled HTC Sync.
OR
If that fails, you can try to extract the rom.zip from the RUU and flash it manually (help on extracting http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html ) JUST DON'T USE THE ROM FROM THAT TUTORIAL, THE LINK IS JUST FOR REFERENCE ON HOW TO EXTRACT THE rom.zip
The offcial RUU are in this thread, just BE SURE TO USE THE CORRECT ONE http://forum.xda-developers.com/showthread.php?t=695667
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom.zip

@quanchi, thanks for your help i'll try and let you know tomorrow thanks again
Regards

hi i have tried the method putting phone in fastboot mode pressing back and power phone was detected and then flashed with this rom 'RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed'' and it was successufll now my phone is not turning on when i press power it vibrates but nothing on the screen but good thing is when i connect the phone with pc it still detects it its not brick yet i think any help
Regards

faisal_sherry said:
hi i have tried the method putting phone in fastboot mode pressing back and power phone was detected and then flashed with this rom 'RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed'' and it was successufll now my phone is not turning on when i press power it vibrates but nothing on the screen but good thing is when i connect the phone with pc it still detects it its not brick yet i think any help
Regards
Click to expand...
Click to collapse
Is your phone SLCD? I reckon you may have flashed an incorrect RUU, in which case you'll need to get a more up-to-date one and flash it again. In case that's the most recent one for T-Mobile, you'll need to make a gold card and then flash a generic RUU. Hope that helps.

hi thanks for your reply i don't know what is slcd? and let me tell you the stat of the phone now
when i press power phone vibrates i can see button lights on the phone but nothing on the lcd screed. Phone is not going in boot mode when i press back and power nothing happens, volume up and power nothing happens. Phone is being recognized in device manager as a usb mass storage and i can see battery light on the top of the screen as well. I dont know what is the real state of my phone and what do you call it but its a t mobile UK phone that's what i know and what should i do now thanks
Regards

SLCD is a type of display present in some Desires, earliest Desires had an AMOLED display. You most probably flashed your SLCD Desire with RUU prepared for an AMOLED Desire, hence the display problems. Search the forum for "SLCD BRICK". Your phone should be able to enter fastboot/hboot, but doesn't display anything because the display handling is screwed up. Before trying to resolve your situation BE SURE TO READ ALL THE INFO ON SLCD UNBRICKING.
I have no experience with SLCD models so can't help you much on the subject, but there are numerous threads on xda detailing dealing with this particular issue.
I don't want to sound rude or holier than thou (as I had my share of bricks and semi bricks) but I did write that you should make sure you get the correct RRU...
best of luck
Sent from my HTC Desire using XDA App

hi thanks for your reply i'll try n post the result here
Regards

So here I will describe what I did to solve the exact same issue.
Remove the battery from the phone
Copy the proper RUU file to the root of my SD card naming it PB99IMG.zip
Insert battery
Power on phone holding the power and the back buttons until the fastboot menu opens
Choose recovery
Then it will go through a bunch of stuff and ask you if you want to flash the file you put on the SD card, I said yes then a few minutes later Bobs your uncle I was back to factory.

faisal_sherry said:
hi thanks for your reply i'll try n post the result here
Regards
Click to expand...
Click to collapse
Faisal, it seems apparent that your device is an SLCD Desire. When you put Alpharev on it, it did S-OFF and your boot got corrupted for some reason and looped. When you ran the RUU (which was incompatible for your SLCD, and actually meant for an AMOLED Desire), you effectively unrooted it, though not restoring it.
Check my thread for a similiar problem.
If you had made a Goldcard earlier, you're in luck. You can restore your device with a generic SLCD RUU available for your device, by either running the RUU or by flashing the rom.zip from the RUU.exe file (Tip. This file gets extracted to %TEMP% folder when you run an RUU)
Things you need to know before you try solving your problem:
Know how to use adb from the command prompt,
Search for the links to shipped-roms site containing the list of Bravo (Desire) ROMS
How to create and use a goldcard
How to navigate to the temporary folder of your Windows PC
How to turn your device on into Recovery mode and Fastboot without seeing the screen
Simple search on XDA can unravel these simple mysteries.
Now, the steps to go about solving your problem:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code which prevents you from flashing a ROM meant for any other brand and also blocks a Generic RUU. If you're from India, it is branded with HTC Asia_India. If you're unbranded, things are looking much easier for you, as generic RUUs for SLCD are easily available.
Check if you have a goldcard (A goldcard is a special microsd card you made while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA)
If you dont have a goldcard, you might try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone gets detected in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
After creating a goldcard, it will allow you to run a generic SLCD RUU. Check my thread for a latest RUU.
If you dont have a goldcard, and adb doesnt show the device in Recovery mode, it means Recovery is corrupted too. In this case, Power off device. Then Poweron by pressing Back key and Power on key. Again try adb devices command. If it shows the device, follow the steps of previous step.
You can also create a goldcard by putting your microsd card into a friend's phone and following the steps needed to create a gold card
If adb doesnt show your device in either Fastboot (previous step) or in Recovery, then you're in trouble. The only way to unbrick your softbricked device is to get a Generic RUU for your device (Check shipped roms site, or search XDA), and flash it. There is also a method if you have the original OTA zip for your device. Check teppic74's posts on XDA for this method.
If you have an Indian Desire, you're done for as I found out. If you dont have a goldcard for an Indian Desire, or the OTA zip, you have no option than to return it to HTC. Dont worry about Warranty being lost if it is a new phone. HTC has to repair it according to their Warranty policy.
Goodluck. I've summarized all methods available to unbrick an SLCD. For more details on any one method, try searching with the appropriate keywords from my post. It's all on XDA.

@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
"switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery."
pc detects the phone but when i run ruu it doesn't find the phone and i have OTA downloaded as well and i have copied to micro sd but i dont know how to use this OTA. i'm sorry for being very basic
Regards

faisal_sherry said:
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
"switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery."
pc detects the phone but when i run ruu it doesn't find the phone and i have OTA downloaded as well and i have copied to micro sd but i dont know how to use this OTA. i'm sorry for being very basic
Regards
Click to expand...
Click to collapse
@Faisal,
No prob. Everyone is a newbie at the beginning!
But, you need to search and find out some things on XDA, and there are a lot of newbie centric guides over here which explain procedures step by step..
You need to do these by yourself though:
1. Install Android SDK. It just involves downloading the setup file, running it, and finding out where in Windows it has been installed. In the main installation folder, there is a Folder called Tools. You need to open a command prompt in that folder and run adb.exe for most of the procedures. Follow this guide to install the SDK.
2. After you have the sdk installed, boot your phone into recovery using the procedure you quoted. As you said, the phone will be detected in Windows. At this point, run the following command from a command prompt in your tools folder.
Code:
adb devices
This will output "List of devices" followed by a code starting with SH. If it does, you're in luck. You can now create a goldcard, and proceed. Follow this guide for this.
3. If the "adb devices" does not show any devices (in recovery/Boot mode), and you dont have a goldcard, you've run out of luck, pal. Honestly, no one on any forum has solved the issue with this combo.
There would still be a solution, if you have the RUU. I dont see why your RUU does not run. Try to run it in one of the following modes.
a. Switch off phone
Switch it on by pressing Back key followed by Back+Power key, then slowly releasing Powerkey while keeping Back key. This is the bootloader mode.
b. Recovery mode. Power off, power on by Vol down + Power key, then slowly release Power key. After 30 sec, press Vol down once, then power key once. Wait 1 min and see if pc detects device. Else press power key once again.
In either of these modes, the RUU you downloaded should down. If it is the incorrect RUU for your location, it will give a customer id error. If it has an incorrect bootloader version, it will show a Bootloader version error. In either of these cases, try the newest generic SLCD RUU from shipped roms. If this still gives one of the above errors, your phone is a branded phone. In this case, you WILL NEED a gold card to work.
Note that if adb devices shows your phone, then you can create a goldcard at this point.
If adb does not show your devices, and the latest generic RUU does not run, and you cant find a correct RUU for your device, then tough luck. I am yet to find a solution to this problem. Return it to HTC.

faisal_sherry said:
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
Click to expand...
Click to collapse
Yes, you need to have HTC sync installed for the drivers. But the HTC sync main program should not remain in the system tray (bottom right). If it is, close it by rightclicking and Exiting.
The problem with what devin mm said is that an SLCD desire doesnt show anything on screen if bricked. Yet, recovery may be selectable for some, without seeing anything. But if you ran the RUU, then most probably the recovery itself is corrupted and selecting a zip file on memory card wont be possible at this point.
Sorry that I wont be able to follow this thread for the next few days. I'm travelling, and since my Desire is with HTC repair centre, no Net. Hopefully, someone else on XDA can help out with any more qns..

HTC Desire Z feared bricked. (Perhaps stuck in bootloader)

I appoligise if this has been asked before.
I have a HTC Desire Z which I have rooted using the Cyanogen Wiki Method which i believe was successful, I wanted to check whether I was S-Off before loading custom roms.
wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
I read on a forum you should bootload to check, so i held power and VOL up on restart however now i have a black screen with a flashing red led at the top and am unable to get out of this mode does anyone have any advise what I need to do?
Anything would be helpful I'm in the UK military currently deployed on OPS this is my only means of comms to family. Thanks in advance.

Crap, so you're stuck in bootloader huh? Well if you have a PC with you then thats good news. Cause you can just flash something via your bootloader if you have ADB set up.
Wait, you said it has a red led lit right?... the battery might have died on you in all honesty because that's the only time a red/amber led would come on. If this is the case just leave it charging for like 20 minutes before try to turn it on.
Anyways, if that isn't the issue try getting the screen onto that bootloader page. As soon as you get to that you can start fixing it. It should say FASTBOOT_USB or something similar to that. Now on your pc start up your CMD Prompt (Run > 'cmd'). From there try typing Fastboot devices and it should list your device as HT########. If you can get to that then we're doing well.
BEFORE you try this, just note I've never fastboot flashed a ROM and I only posted this because you seem to need it urgently. If you can wait, then post what you've actually done to the phone so I can provide you with a more tailored solution that will work. (post whether the phone is rooted, s-off or superCID or just the guides and where you got stuck)
Now what you need to do is plug your microSD into your laptop and do this:
Aegishua said:
Before you do this please do the following:
1a. Download the RUU I’ve linked (it should be a ~300mb exe file)
1b. Run the setup until you get to the screen with the tick boxes
1c. Goto C:\Users\<your account name>\AppData\local\temp. Then right click and Sort By Date Modified. Look for the most recently created folder which should look like {xxxxxxx-xxxxxx-xxxxxxxx}. Then navigate into it and its parent folder. Look for rom.zip and copy that to your goldcard/memory card.
1d. Rename the rom.zip on your memory card to PC10IMG.zip
1e. Mount your sd card back onto your phone.
Click to expand...
Click to collapse
In this case you want it to be called update.zip. Now you can pop the microSD back into your phone and from there get back into your bootloader and switch to fastboot. Now when it says fastboot_usb you can run this on your PC's CMD Prompt. fastboot update /sdcard/update.zip

did you try something as simple as a battery pull? also, I noted you said power + vol up, you need to do power + vol down to enter bootloader. I seem to remember something similar happening to me back in the day.
chances are it's fine. I'd do a battery pull and boot it normally just to make sure, then power off and enter bootloader to ensure you are s-off by pressing power + vol down.

It is supposed to be volume DOWN + power, I just tried volume up, my phone vibrated 3 times and an orange light flashed continuously, but it was solved by a battery pull, and it was back to normal
Sent from my HTC Desire Z using XDA App

only charge led shows lifesigns.
**moved to new post**

HTC Desire Stuck on HTC logo - Recovery not Working - NOT SOLVED!!

Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30

Cyanoid said:
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Click to expand...
Click to collapse
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.

Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it says "Android Bootloader Interface" in Windows Device Manager, that it says "HBOOT USB PLUG" on the HBOOT screen when connected via USB, and that I am able to issue FASTBOOT commands from the PC. But I can't issue adb commands, so it appears I can only "partially" communicate with the phone from the PC.
Should I try CLEAR STORAGE, or could that fully brick my phone?
On the HBOOT screen, these are the status messages that load:
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nbh]
No Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99DIMG.nbh]
No Image or wrong image!
waynestir said:
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Click to expand...
Click to collapse

USB Brick
For me, it sounds like a typical usb brick :/ I hope you still have rooted ROM. Search through this forum for unbricking guide.

Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.

HTC Desire Stuck on HTC logo - Recovery not Working - SOLVED!!
madcr0w said:
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
Click to expand...
Click to collapse
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.

sorry for delayed responce. I'm sure you had already found a solution by now but in the off chance you didn't.
you have to load fastboot not hboot.
from a power off state hold back button and power on phone. this will load fastboot and ruu will find device when run.
Cyanoid said:
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it o Image!
Click to expand...
Click to collapse

Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.

expza said:
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
Click to expand...
Click to collapse
+1 There is a good guide to fastboot commands on the android wiki:
http://android-dls.com/wiki/index.php?title=Fastboot
Should be a case of wiping system, data, cache, then flashing recovery image. Then boot into that and restore a backup or flash a rom.

Cyanoid said:
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
Click to expand...
Click to collapse
can u plz help me frm with post u solved ur probs....i m stuck too

1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional

Does your phone get hot and overheated during the htc logo? It did so to me and it turned out to that my CPU had melted and overheated. Take it to your retailer and they will fix it for free because it's not your fault, it's the phone that overheated.

Try this:
-download this with ur pc and rename it a PB99IMG.zip (not PB99IMG.zip.zip ok?)
-then put it on the root of ur sdcard (not in some folder) through an sd card reader
-ensure the battery is charged much than 30%..better more
-with the phone off (remove battery and put again) press and HOLD the volume down key and press (still holding the volume down key) and hold the power button..hold both and wait to enter in the hboot
-there wait a bit, and it will ask to u if u want apply the update, select yes with the volume keys and confirm with power button

awayra said:
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Click to expand...
Click to collapse
Just go to my troubleshooting guide, you'll probably find an answer there.

Send it back for warranty repair.
Sent from my Motorola Startac running Atari 2600 software!

@nhrsak - you save me, thanks very much!!

Did you try getting s-off with Revolutionary?
I had problems when i was s-on, but when i s-offed, everything went fine.

Have you tried flashing recovery.img via AndroidFlasher(from XDA)?

[Q] One x touch screen fail

Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.

bump

thebarran said:
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
Click to expand...
Click to collapse
Did you try RUU?

Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.

thebarran said:
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1859714
No need to root / unlock bootloader
EDIT: follow option 2

following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked

thebarran said:
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
Click to expand...
Click to collapse
Can you try running fastboot on a different OS? Windows XP/7, Ubuntu? Something else?
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?

davidk-il said:
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
Click to expand...
Click to collapse
not doing this what do you mean?

thebarran said:
not doing this what do you mean?
Click to expand...
Click to collapse
Navigate on your PC to the fastboot folder lets say "c:\fastboot".
Shift+right click on any blank place and choose open command window here(or something like that my OS is not in english now).
Try using fastboot commands .

ah nice works, thanks. stay with me in case i get stuck again.

thebarran said:
ah nice works, thanks. stay with me in case i get stuck again.
Click to expand...
Click to collapse
Sorry,
Gotta get some sleep =)
If after running RUU nothing changes take the phone to service.

more problems
Ran and installed the ruu but got an
error[152]:image update error
The ROM update utility cannot update your android phone.
Please get the correct ROM update utility and try again
But i have the correct version already 3.14.401.31 it just wont install and now my phone is stuck on a black screen with htc in centre and nothing else.

Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode

Mr Hofs said:
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Click to expand...
Click to collapse
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle

thebarran said:
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
Click to expand...
Click to collapse
Phone for sure in fastboot usb mode?

davidk-il said:
Phone for sure in fastboot usb mode?
Click to expand...
Click to collapse
it was when i first did it biut cannot check no more

Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights

Mr Hofs said:
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Click to expand...
Click to collapse
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.

thebarran said:
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
Click to expand...
Click to collapse
Try shutting of the phone, powering on when holding power button+volume down for about 8s.
You will get a hboot, choose fastboot connect usb cable and try ruu with admin permissions

finally did get to hboot screen by letting the phone shutdown itself but couldnt ruu as battery power to low so i powered down and recharged battery but back to square one where i cannot get to boot screen just constant black htc screen and cant power down again.
So ill let my battery run down again to power off completely open boot screen then stay on that til i power up enough to try ruu again.
Il let you know what happens when this is done later.

[Q] Stuck on HTC Logo, can't get into bootloader after root attempt

Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
7.If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
•Fastboot oem lock
Then type:
•fastboot oem rebootRUU
•fastboot flash zip firmware.zip
•fastboot reboot-bootloader
unlock the bootloader again using the Unlock_code.bin you got from HTC:
•fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).

konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
stuck in the same place... before unlocking bootloader pc would recognise the phone. now it doesn't... i think were stuck unless a developer helps us

Hmm, remove and reinsert the battery, and plug it into a computer, don't power the phone on, wait and see if the computer detects it, if it does, try "adb devices" to see if it shows up.
Sent from my Desire HD using Tapatalk 4 Beta

humzaahmed155 said:
Hmm, remove and reinsert the battery, and plug it into a computer, don't power the phone on, wait and see if the computer detects it, if it does, try "adb devices" to see if it shows up.
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Windows detects an "Android Phone" in Devices but "adb devices" is still empty.

konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
i had the same problem but fixed now. The way i did this was to actually take out the hardware for the volume rocker and check if the contacts are all in place. i then booted into bootloader by connecting my phone to a power source (computer or ac) and pressed the volume down button so that it registered. For some reason it seems to register you clicking the button better when its out of the key. Sorry if you don't understand this, I really don't know how to explain the rocker and the keys separately 0_o

Some times guys the firmware.zip file once flash does get stuck on the HTC White screen during the exploit just run ADB and continue with the unlocking of your radio. Its safe.

IBeKay said:
i had the same problem but fixed now. The way i did this was to actually take out the hardware for the volume rocker and check if the contacts are all in place. i then booted into bootloader by connecting my phone to a power source (computer or ac) and pressed the volume down button so that it registered. For some reason it seems to register you clicking the button better when its out of the key. Sorry if you don't understand this, I really don't know how to explain the rocker and the keys separately 0_o
Click to expand...
Click to collapse
Wooh!!! It worked !!! Thank you very much!!!
For future reference, this is how what I did to complete the root process:
1. Pull off the battery cover, take out the battery.
2. Rip off the label with IMEI and S/N and then use a toothpick or plastic tweezers to pull out the ribbon cable from the volume rocker (see video here: youtube[dotcom]/watch?v=JfatoeWbMRk&feature=player_detailpage&t=143)
3. Press the volume down button on the cable a few times to make sure it clicks then clean the inside of the volume rocker a bit, put the cable back in, and press volume down a few times to test it.
4. Put the battery back in, connect the USB to your computer, hold volume down and press the power button so that it goes into the bootloader.
5. Go into fastboot and continue the rest of the steps from the guide.
Note: if adb doesn't detect your phone then reboot it and enable USB debugging again in Settings > Applications > Development and then reboot into the bootloader.
Thanks to everyone that helped ! :good:

konungr said:
Wooh!!! It worked !!! Thank you very much!!!
For future reference, this is how what I did to complete the root process:
1. Pull off the battery cover, take out the battery.
2. Rip off the label with IMEI and S/N and then use a toothpick or plastic tweezers to pull out the ribbon cable from the volume rocker (see video here: youtube[dotcom]/watch?v=JfatoeWbMRk&feature=player_detailpage&t=143)
3. Press the volume down button on the cable a few times to make sure it clicks then clean the inside of the volume rocker a bit, put the cable back in, and press volume down a few times to test it.
4. Put the battery back in, connect the USB to your computer, hold volume down and press the power button so that it goes into the bootloader.
5. Go into fastboot and continue the rest of the steps from the guide.
Note: if adb doesn't detect your phone then reboot it and enable USB debugging again in Settings > Applications > Development and then reboot into the bootloader.
Thanks to everyone that helped ! :good:
Click to expand...
Click to collapse
glad I helped

konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
Hi
I have followed your all steps perfectly... after done i have reboot my desire hd it shows htc screen and goes to qualcom mode...plz tell what should i've to do now