Develop Bugs

How to get to recovery if i can't see the screen?

Can you help me, i've made a mistake attempting to downgrade and root an HTC Desire on Voda UK from hboot 0.93. Downgrade seemed to be successful, but the device was stuck in bootloader mode. Since then i have managed to lose my goldcard and flash an uncompatible RUU. And now the screen is dead but if i pop out the battery and put it back in i can hear the start up animation sounds. What can i do to recover my screen? Your advise would be appreciated. Mat

Old versions do not support SLCD (Your Display) hence it turn black (i had hard time, believe me), i personally installed newest official RUU and everithing went OK. But there other solutions, read here http://forum.xda-developers.com/showthread.php?t=748498
wish You luck

Wish i could help you but i don't remember. Been pre-occupied with trying to find a fix and move forward. Can't guarantee that i wouldn't make the same mistake again either. Currently flying blind withthe 'SLCD BRICK FIX Method1' without success.

download ADB to your computer
open up a command prompt/terminal window
cd to your adb/tools directory and type:
adb reboot recovery

Thanks for your reply. I downloaded adb sdk etc but my lack of skill in the command promt is holding me back, not to mention that the Device screen is still black and it isn't recognised by my pc when i plug it in. Don't know what to try next..

With goldcard inserted, started phone in fastboot mode (back key and power button). Flashed back to stock htc rom. Screen is back on and i'm up and running.
Thought i had tried this before but it worked this time (so happy!). Thanks for reading and helping.

Woulda been easier following this guide - as should everyone else currently:
http://forum.xda-developers.com/showthread.php?t=768256

]SK[ said:
Can I ask which method you were using? I see your on Vodafone the same as me. I got my Desire yesterday and want to use OpenDesire however I fear that I will make a mistake and end up in the same situation as yourself.
I was going to follow this http://forum.xda-developers.com/showthread.php?t=768256 guide although I can't as I don't have a SD caddy to plug it into my PC.
*Mods*
Can a mod please fix it so I can post URL's please?
Click to expand...
Click to collapse
URL privileges will be working soon.
And if I come across any new members URL issues I put them in for them.

Bricked!fastboot works in cmd, no adb, recovery/bootloader menus

Would appreciate your help on the following issue (amoled display):
- phone doesnt boot up, it is stuck to a screen showing htc in the middle and 4 small triangles in the corners; if I unplug the pc cable it goes to a RUU menu
- no access to recovery or bootloader menus (by holding power + vol down/back)
- installing stock RUUs dont work; there is a 110 error saying that the RUU is not complete (tried 5-6 RUUs, both 2.1 and 2.2). there is a progress bar on the phone's screen that is normally green, but turns red when the radio is being written (as per the install wizard on the pc) and there is another triangle showing up at the end of the progress bar
- fastboot oem boot restarts the phone, but then it gets stuck to the white screen having htc in the middle (like when you start up the phone and after this quietly brilliant shows under htc, for me it doesnt go beyond this initial point)
- fastboot reboot-bootloader restarts the phone into the same 4triangles screen with htc in the middle
- adb doesnt work as it doesnt show my device
- any power + vol down/back combination brings the phone to the 4triangles screen
- if I run the stock RUU after fastboot oem boot (white screen with htc in the middle) there is a menu showing up on top of the white screen showing up the progress (1-bootloader, 2-radio_v2, 3-radio, then system, recovery, user data, etc.); bootloader is updated ok but then it gets stuck when updating radio_v2 and doesnt move further from that point)
- after the RUU install fails, I plug out the pc cable and see the RUU menu; depending on the RUU that I try to flash the hboot version changes up and even goes down after, but the firmware (what the RUU installer "sees" on the phone) and radio (seen on the RUU menu) remains the same: 1.21.405.1 and 4.06xx; the date on the RUU menu also changes depending on the RUU that I try to flash
Any suggestions to get my desire unbricked?
Bit of a background to the problem:
- rooted (unlockr) and was having Paul's r3 rom (2.1)
- updated the radio to 5.10xx
- got into silly restarts when using gps and thought to reflash a new rom and went for Paul's r8
- restarts were there also when using the phone normally
- thought to re-do all the rooting, wiping out everything from the phone, etc; so having r8 as the rom (pre-baked version) I started the rooting process with creating again the goldcard, etc etc
- error message at some point saying partition update fail (following the steps from theunlockr as I did the first time when rooting) and then the phone got to this triangles screen with htc in the middle
- strange though that this screen is different than the one when I first rooted when there was just one big triangle in the middle
Thanks a ton guys!

I've seen a few posts about this screen with the 4 triangles, but never seen the result of any potential fixes, or if it was ever actually fixed.
Just an idea, but it was maybe a bad radio flash if you are saying it started playing up after that? Unfortunately a bad radio flash is fairly terminal so I hope that's not your problem.
Good luck with this one and if you get it fixed then post the result here if you don't mind!

Will definitely post the solution when found; so far though nobody has any thoughts around what might be the reason behind this problem and how to get around it. I dropped a few PMs to the people that had this problem in the past and contacted Paul at Modaco, but so far no replies...

You can fix this with an RUU, I've had the same issue when I unplugged too early after flashing, but you are asking for help in the wrong section.

thought that the dev's section is where the best knowledge exists...
about the RUU process, I am trying to flash stock RUU.exe files, but there is a problem when the radio is being written and then I get a 110 error from the RUU install wizard saying that the RUU is incomplete.
for you the RUU install worked smoothly?

If you get a write error during an RUU flash (i.e. while the flashing is taking place, not before) it probably means there's a hardware fault.

Could be hardware, but I find it hard to believe as the phone is new and it is network locked, hence I didnt even use it for real, apart from some wifi and gps activities. Besides, the phone worked very well when I first rooted with Paul's r3 and the whole mess with restarts when using gps started after I upgraded the radio to 5.10xx having a 2.1 OS.
I feel that the problem started when I tried to root the phone being on Paul's r8 2.2 OS (tried to root with a 2.1 system and then it got messed up in the process).
I am not saying that it is not hardware as it is a possibility, but still think that it might be a messy software aspect, as if the radio is messed up from a hardware perspective, then at least the system should boot up and then wifi, gps, gsm and the things that are controlled by the radio shouldnt work...but somehow the OS should start-up.
Basically I dont get a write error, it's just that the error comes up when the radio is being written, hence I think that there is something wrong with the radio set-up that I have now on the phone...
Maybe somebody knows how to flash the system from scratch using only fastboot in cmd (having the right zip or img files properly signed), or maybe just the radio to start with.

This is not a Development question and thus should not be posted in the Development forum.
Thread reported.

have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.

acolwill said:
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
Click to expand...
Click to collapse
Well, I thought that as various solutions to root the phone, to get past different restrictions in the OS, etc. were discussed here, it might be a good thing to develop a way to bring back to life a OS being in this situation like mine...come on...

mariosraptor said:
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
Click to expand...
Click to collapse
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days

I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.

but to get adb you need to download and install android sdk. look here http://developer.android.com/sdk/index.html system dependands download.
install it here are instructions on how to use if you aren't familiar with.
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
for anything else just use google.
i'm pretty sure that your device is fixable and you can fix it without any service center. cheers and post what ever happens.
popepope said:
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
Click to expand...
Click to collapse

I know how to use adb commands...pretty new to android and everything, but lately I roamed a lot through various things about it and learned a lot.
The problem is that adb doesnt list my phone when I run adb devices, it shows only when I run fastboot devices, I am sure you know what I mean...hence I cannot push any files to the phone, etc., at least not using adb in cmd.
That's actually the problem, that I cannot get adb to work, I only have fastboot commands. At least the way I see it now the question is how can I work with the phone to fix it just by having fastboot access in cmd.
I searched quite a lot various forums, etc, but I never came across a solution that will get things going just by having fastboot in cmd (without adb working). Maybe somebody here will come up with some magic trick...

Nerten said:
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
Click to expand...
Click to collapse
How did you end up having this problem, just like that or after some update, flash, etc?
Thanks!

have a look here mate http://forum.androidcentral.com/htc...9-bricked-my-evo-but-there-away-un-brick.html

same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!

sorry idf i don't underdstand, but if you have fastboot working in your device and sdcard also then you should be able to push files to device via fastboot making as clean installs as possible.so if your device is picked up by command line type fastboot to see command list. i'am a bit comfused. pretty sure you should fix it through fastboot though.
popepope said:
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
Click to expand...
Click to collapse

right, I can run 2 things with fastboot in cmd: (name of the files just an example)
1. fastboot update update.zip
here I get that the archive doesnt contain android-info.txt or android-product.txt
2. fastboot flash update.img
here i get signature verify fail
for example, fastboot erase radio says FAILED, remote: not allowed
there are some fastboot commands related to the kernel and some others, but dont know how to make use of them for my problem.
sd card is accesible for sure and it is a goldcard.
I saw some linux/ubuntu methods to simulate adb usage in cmd, but I dont think it will work...will try to find an ubuntu image and mount it under windows, but dont have time now...
anyways, thanks to everybody for the suggestions and interest, maybe we'll crack it some day

You need to use an official RUU zip image - i.e. a PB99IMG.zip. Not an update.zip.

[TUTORIAL][S-OFF] Virgin Mobile CDMA S-OFF Without XTC-Clip Confirmed Working!

Ok so I spent hours reading post after post and thread after thread trying to figure out how I could get S-OFF on my Virgin Mobile Wildfire S without having to use an XTC clip. I was told by another user (thehumble1) that I was able to do it without the use of an XTC Clip and it seems to only work with CDMA versions of the Wildfire S. So after hours of trial and error and frustration I finally was able to get S-OFF without the use of an XTC Clip. I decided to write a tutorial specifically to the Virgin Mobile Wildfire S users so that they don't have to do all the searching that I did.
*I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MAY BE DONE TO YOUR PHONE WHILE FOLLOWING THIS TUTORIAL*
*READ AND FOLLOW THESE DIRECTIONS EXACTLY OR YOU "WILL" RUN INTO PROBLEMS*
CREATING A GOLD CARD
Ok first we need to modify an sd card to make something called a gold card. Don't ask me what it is because honestly I have no idea I just know it is a necessary process in getting S-OFF.
1. Backup all files on your SD card as we will be formatting the card and you will lose all of your data.
2. Plug your phone into your computer and make sure hard disk mode is chosen. (Make sure USB debugging is turned on also)
3.Extract SimpleGoldCard_v1.zip to your desktop and start SimpleGoldCard.exe.
4. Select your SD card's drive letter in the drop down menu under "Step 1 - Format SD Card" and then select Format. If your drive letter is not showing up try pressing the refresh button next to the drop down menu.
5. Select ok when it says Format Complete then turn your phones USB Connection option to Charge Only instead of Disk Drive.
6. Next under "Step 3" select the MMC1 radio button and then click on GetCID. (It will produce a long list of jumbled numbers and letters this is your SD card ID)
7. Then select the link under "Step 4 - Request for IMG file". Copy the long ID from "Step 3" and paste it into the CID space on the web page you just opened and then fill out the captcha form and click Download to download your goldcard.img file (Save to your desktop)(the goldcard.img files are specific to individual SD Cards)
8. Close the page once you have downloaded your file and then bring back the Simple Gold Card application. Under "Step 5 - Load IMG File And Patch" select Load IMG and locate the goldcard.img file that you just downloaded and select it.
9. Put your phone back into Disk Drive mode and then click Patch MMC. Once everything is complete you should have a working gold card. (To make sure, remove your SD card and reinsert it and make sure that it still functions normally.
After your gold card has been made you need to download and unrar the DIAG Files.rar file I have uploaded. Extract the of the folder to the root of the new Gold Card you have just made. There should be two files and it should look like this when you are complete.
F:/PG76DIAG.nbh
F:/PG76DIAG.zip
*F being the letter of your removable drive whatever that may be
Before we move on to the next step we need to make sure that Fast Boot is turned off. So to do that you need to go to Settings/Power and then make sure Fast Boot is not selected.
INSTALLING THE DIAG FILES
1. Once that has been done power off your phone and pull the battery for a good 5 seconds just to make sure it's completely off.
2. Boot into HBOOT by holding Volume down while pressing the power button (you do not need to hold the power button, only hold the volume down button) The HBOOT screen will boot up and then you can let go of the Volume down button.
3. The phone will automatically scan the SD card for the files we just put on the root of the SD card and will start the update process.
4. A screen will appear that says Clean s58. Press the power button once to select clean s58 and the phone will start doing it's thing and should take about a good 20 seconds until it's finished.
5. Once the process is complete then pull the battery to turn the phone off.
6. Once the phone is off remove the SD card so that the phone doesn't install the DIAG files when we boot into HBOOT to check if we now have S-OFF.
7. Boot into HBOOT again by holding Volume down and quickly pressing the power button. The phone should boot into HBOOT and at the top of the screen it should now say S-OFF. Congratulations you now have Security off on your Virgin Mobile Wildfire S!
Now all that is left to do is restart your phone, reformat the SD card to remove the files we don't need anymore and restore your backed up files and your all set. You may now root your phone and do whatever it is that you wanted S-OFF for.
If you have any questions feel free to ask. Comments are welcome. Any corrections or things that need to be changed as well let me know. This is my very first tutorial ever on XDA Forums so I hope that I was able to help some people out. All feedback is welcome and if this tutorial helped please give me a thanks.

Well done pal.. That's great news!
So this is only for US mobile phones?

arkatis said:
Well done pal.. That's great news!
So this is only for Virgin mobile phones?
Click to expand...
Click to collapse
Well I don't want to say that it's ONLY for Virgin Mobile phones persay, but that is what I have and what I used for this tutorial. I'm sure it's mainly because the Virgin Mobile Wildfire S has a different version of HBOOT and is also CDMA so who knows if that plays a part or not.

It wouldn't hurt for anyone to go ahead and try this procedure. And as for just US mobile phones I couldn't tell ya.
Here is my HBOOT info if anyone cares to know it.
MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
MICROP-0354
RADIO-0.94.00.0824

My HBOOT version is 0.90.0000 so i do not think it should work.. but i will give it a try! If i do not respond to this topic that means that my wife killed me! lol

arkatis said:
My HBOOT version is 0.90.0000 so i do not think it should work.. but i will give it a try! If i do not respond to this topic that means that my wife killed me! lol
Click to expand...
Click to collapse
Hahaha well good luck with your phone and your wife!

arkatis said:
Well done pal.. That's great news!
So this is only for US mobile phones?
Click to expand...
Click to collapse
This method works only for CDMA phones (many GSM users have tried and failed to get S-Off).
Also, probably only for US phones as hboot version is different. Have you had any luck?

sk8tr5955 said:
Here is my HBOOT info if anyone cares to know it.
MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
MICROP-0354
RADIO-0.94.00.0824
Click to expand...
Click to collapse
I have the exact same phone and I can confirm that I am now S-OFF!!!!!!
Thank you so much for the tutorial! Now I have to read up on how to root an S-OFF phone !
UPDATE: The phone is now fully rooted. This is amazing! I thought I was doomed to never have root due to Virgin Mobile not having sim cards, and being incompatible with XTC clips. It's amazing this was all done in software.

Awesome man I'm glad that I could help out! I'm extremely happy to know that it is working for other users out there as well. The most I ask out of you is to just give me some good feedback and thank me!
billclay1988 said:
I have the exact same phone and I can confirm that I am now S-OFF!!!!!!
Thank you so much for the tutorial! Now I have to read up on how to root an S-OFF phone !
UPDATE: The phone is now fully rooted. This is amazing! I thought I was doomed to never have root due to Virgin Mobile not having sim cards, and being incompatible with XTC clips. It's amazing this was all done in software.
Click to expand...
Click to collapse

Hey guys! Yes i am alive!!!!!
No not any luck with my GSM WFS. Hope can someone modify the diag files to work as i am not able to open them nor extract them...Any help appreciated.

May I ask you, what is difference between "Virgin Mobile CDMA HTC Wildfire S" and normal HTC Wildfire S ?
WildFire I'm speaking about :
Code:
HBOOT 1.03.0000
MICROP-451
RADIO-7.46.35.08
Jun 02 2011, 16:17"50

Nevermind ignore this.

arkatis said:
I don't know if I'm correct but if you know the differences between CDMA and GSM then the answer is in front of you..
Each company have different versions of the firmware which is locked on their services.
So far we got 3 different hboot versions [0.90, 1.06, 1.03] with 3 different radios
0.90 is for GSM phones as i got one.
1.06 and 1.03 are for CDMA i suppose
Click to expand...
Click to collapse
Our Europe Wildfire s (Austria) was shipped with the Hboot 1.03

Schnello said:
Our Europe Wildfire s (Austria) was shipped with the Hboot 1.03
Click to expand...
Click to collapse
Alright that's why i told you guys to ignore my comment..
Seriously I am lost with this phone, it's a pain in the a$$!
Thanks God i got my Desire HD to play with.. lol

shaarky said:
May I ask you, what is difference between "Virgin Mobile CDMA HTC Wildfire S" and normal HTC Wildfire S ?
WildFire I'm speaking about :
Code:
HBOOT 1.03.0000
MICROP-451
RADIO-7.46.35.08
Jun 02 2011, 16:17"50
Click to expand...
Click to collapse
I have the same Wildfire.
Code:
MARVEL PVT SHIP S-ON RL
HBOOT-1.03.0000
MICROP-0451
RADIO-7.46.35.08
Jun 2 2011, 16:17:50
I thought that CDMA phones don't have sim card?

too bad, no good for HBOOT-0.90

No.12 said:
I have the same Wildfire.
Code:
MARVEL PVT SHIP S-ON RL
HBOOT-1.03.0000
MICROP-0451
RADIO-7.46.35.08
Jun 2 2011, 16:17:50
I thought that CDMA phones don't have sim card?
Click to expand...
Click to collapse
Yes, the cdma phones don't have sim so when makig s58 there is no error because the phone not need the sim card. In the gsm after makig s58 phone reboots because not detect the flex cable conected to the xtc clip.

honorable mention?
sk8tr5955 said:
Ok so I spent hours reading post after post and thread after thread trying to figure out how I could get S-OFF on my Virgin Mobile Wildfire S without having to use an XTC clip. I was told by another user (thehumble1) that I was able to do it without the use of an XTC Clip and it seems to only work with CDMA versions of the Wildfire S. So after hours of trial and error and frustration I finally was able to get S-OFF without the use of an XTC Clip. I decided to write a tutorial specifically to the Virgin Mobile Wildfire S users so that they don't have to do all the searching that I did.
*I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MAY BE DONE TO YOUR PHONE WHILE FOLLOWING THIS TUTORIAL*
*READ AND FOLLOW THESE DIRECTIONS EXACTLY OR YOU "WILL" RUN INTO PROBLEMS*
CREATING A GOLD CARD
Ok first we need to modify an sd card to make something called a gold card. Don't ask me what it is because honestly I have no idea I just know it is a necessary process in getting S-OFF.
1. Backup all files on your SD card as we will be formatting the card and you will lose all of your data.
2. Plug your phone into your computer and make sure hard disk mode is chosen. (Make sure USB debugging is turned on also)
3.Extract SimpleGoldCard_v1.zip to your desktop and start SimpleGoldCard.exe.
4. Select your SD card's drive letter in the drop down menu under "Step 1 - Format SD Card" and then select Format. If your drive letter is not showing up try pressing the refresh button next to the drop down menu.
5. Select ok when it says Format Complete then turn your phones USB Connection option to Charge Only instead of Disk Drive.
6. Next under "Step 3" select the MMC1 radio button and then click on GetCID. (It will produce a long list of jumbled numbers and letters this is your SD card ID)
7. Then select the link under "Step 4 - Request for IMG file". Copy the long ID from "Step 3" and paste it into the CID space on the web page you just opened and then fill out the captcha form and click Download to download your goldcard.img file (Save to your desktop)(the goldcard.img files are specific to individual SD Cards)
8. Close the page once you have downloaded your file and then bring back the Simple Gold Card application. Under "Step 5 - Load IMG File And Patch" select Load IMG and locate the goldcard.img file that you just downloaded and select it.
9. Put your phone back into Disk Drive mode and then click Patch MMC. Once everything is complete you should have a working gold card. (To make sure, remove your SD card and reinsert it and make sure that it still functions normally.
After your gold card has been made you need to download and unrar the DIAG Files.rar file I have uploaded. Extract the of the folder to the root of the new Gold Card you have just made. There should be two files and it should look like this when you are complete.
F:/PG76DIAG.nbh
F:/PG76DIAG.zip
*F being the letter of your removable drive whatever that may be
Before we move on to the next step we need to make sure that Fast Boot is turned off. So to do that you need to go to Settings/Power and then make sure Fast Boot is not selected.
INSTALLING THE DIAG FILES
1. Once that has been done power off your phone and pull the battery for a good 5 seconds just to make sure it's completely off.
2. Boot into HBOOT by holding Volume down while pressing the power button (you do not need to hold the power button, only hold the volume down button) The HBOOT screen will boot up and then you can let go of the Volume down button.
3. The phone will automatically scan the SD card for the files we just put on the root of the SD card and will start the update process.
4. A screen will appear that says Clean s58. Press the power button once to select clean s58 and the phone will start doing it's thing and should take about a good 20 seconds until it's finished.
5. Once the process is complete then pull the battery to turn the phone off.
6. Once the phone is off remove the SD card so that the phone doesn't install the DIAG files when we boot into HBOOT to check if we now have S-OFF.
7. Boot into HBOOT again by holding Volume down and quickly pressing the power button. The phone should boot into HBOOT and at the top of the screen it should now say S-OFF. Congratulations you now have Security off on your Virgin Mobile Wildfire S!
Now all that is left to do is restart your phone, reformat the SD card to remove the files we don't need anymore and restore your backed up files and your all set. You may now root your phone and do whatever it is that you wanted S-OFF for.
If you have any questions feel free to ask. Comments are welcome. Any corrections or things that need to be changed as well let me know. This is my very first tutorial ever on XDA Forums so I hope that I was able to help some people out. All feedback is welcome and if this tutorial helped please give me a thanks.
Click to expand...
Click to collapse
Very clean, well-made guide, and it got moved to the dev thread. I would only like to mention the thread that was searched for hours was most likely http://forum.xda-developers.com/showthread.php?t=1343094 . I believe GotsOJ was the first I saw report sucess then mentioned the process he used. I tested and documented here http://forum.xda-developers.com/showpost.php?p=19302575&postcount=121 . I think these efforts bear mention and also perhaps a thanks; alas, I still only have 4 ::shrug::
Also, of course I would thank that thread's OP daxiaamu and eoghan2t7 for pioneering work and the chinese development that made it possible. Perhaps a moment of appreciation in the time it takes to click a thanks button is due to these.
Also I would add a cursory warning to the effect s-off=yes, root=yes... STOP DO NOT attempt to flash a custom rom at this time. It happened to GotsOJ [and I'm sure others] phone locks into qualcom diagnostic mode and is down until you read up [or make a guide for] how to get out of that pickle. But I digress.
Again thank you for the well put-together tutorial.
Rob

insink71 said:
STOP DO NOT attempt to flash a custom rom at this time. It happened to GotsOJ [and I'm sure others] phone locks into qualcom diagnostic mode and is down until you read up [or make a guide for] how to get out of that pickle.
Click to expand...
Click to collapse
GotsOJ mentioned that he successfully flashed a first rom, then bricked when he tried to flash a second one. I'd be interested in finding out which rom he tried first that actually worked.

does it work with a gsm phone?

HTC Desire -- Stuck at HBOOT after RUU

Hopefully I'm just being blind here -- and I have tried a number of guides to fix this -- but I'm pretty stuck.
Couple of days ago the volume down button started playing up, then the menu and search keys stopped working. At the time I had rooted the phone with unrevoked and installed CM7.3 (iirc), and taken the S-OFF with Alpharev 1.8. I figured it was probably a software issue and for some reason decided to go back to run an RUU (rather than just running a different ROM, don't really know why on earth I did that). Kind of having a feeling that I was very dense and ran the wrong RUU, as now the phone is simply stuck at HBOOT.
When I say stuck, I mean as soon as I turn on the phone it goes directly into the stock HBOOT (FASTBOOT -- RECOVERY -- CLEAR STORAGE -- SIMLOCK) yet NONE of the buttons work (so I cannot navigate it at all). Perhaps it is actually a hardware issue, which would make sense as it boots straight into HBOOT, no HTC screen or anything. When it runs the SD check it comes back with wrong / image missing in all the checks.
Tried running ADB, couldn't find the phone. Other RUU's return error 170 as though they can't find the phone. Phone does register "HBOOT USB PLUG" when plugged in though, and my Windows 7 machine does recognise it, but as there's a new RUU on there USB debugging is not enabled and I cannot access the SD card through the phone.
The full info on the HBOOT screen is --
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
Any help would be much appreciated... Later on today I'll pick up a card reader, figure my only option now is to try and get through to it that way?

Hmmmm!
I'm not sure but it actually could sound like a hardware issue. You have the STOCK HBOOT and then ran the RUU for the HTC Desire? If u did so I cant see it as a software brick. PM me if you need some more help. I had a Desire for some month ago that i bricked A LOT more than yours, and i got it fixed (by myself... took some nights thought :/

Yeah I thought that as well, but before I flashed the RUU, although the phone was powering directly into HBOOT, I could use the buttons to navigate the menu. Now, I simply can't.
I should maybe add that when it checks the SD it returns with wrong / missing image (can't remember the exact wording -- pops up then goes pretty quickly).
Also this afternoon I opened up the desire and checked and reseated the buttons, all seem to be working as normal. Seeing as it's stuck at HBOOT, I think I'll just need to buy a new SD card and put whatever the image it's looking for is on it?
Edit: I was thinking that reformatting the SD card (through a PC USB reader) as FAT32, then placing the PB99IMG.zip from the latest 2.3 HTC WWE RUU might work? I can't see any reason why not -- think the Desire is unbranded so no goldcard required.
Edit2: Still waiting on a new adapter, but was wondering why the RUU failed -- the file was RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed.exe from shipped-roms. Don't see any reason why flashing it would have ended up leaving me in this position -- even if it was a hardware issue underlying it.

Sorry to double post...
Tried putting the PB99img from the RUU (and tried the 2.3 update PB99img) to no avail on both the SD card that I'd been using recently and the one that had originally come with the phone -- no luck; once HBOOT detects the img and runs through it, it gets stuck at the "parsing... [1] [2] [3]" etc page.
Any help would be massively appreciated, would be appalled if I have managed to brick this in my enthusiasm for fixing a volume button problem -.-

Already checked bortak's troubleshooting guide?

Yep and anything else I could find really. Starting to think this little droid is doomed.

HTC one m8 in a boot loop

Hi all.
I suspect this question has been asked before and I have found loads on how to do's, but I can't seem to achive what is needed, so any help, however small is greatly appriciated.... he goes.
Customer has brought in an HTC One M8. Details I can give from the Fastboot screen is:-=
***Software Status: Official***
***LOCKED***
M8_UL_CA PVT SHIP S-OFF
CID-111111111 (<---- 8X1'S)
HBOOT-3.10.0.0000
RADIO-1.29.214500021.12G
OpenDSP-V51.2.2-00593-M8974_FO.1015
OS-6.12.401.1
eMMC-boot 2048MB
Dec 17 2015,14:15:48.3
It is stuck in a boot loop that alsways shows the HTC boot screen, reboots to the HTC screen and promptly then to the Android recovery screen:-
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power
Reboot system now
Reboot to bootloader
Apply update from ABD
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
_________________________________
Supported API:3
handle_cota_install: install cwpkg to /cache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop tp /cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip cw installation
Sorry to have to type this in as I cant seam to get images to upload.
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Thanks in advance.
Marc

PC1staid said:
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Click to expand...
Click to collapse
Try another USB cable, and another port on the PC.
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
PC1staid said:
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Click to expand...
Click to collapse
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?

redpoint73 said:
Try another USB cable, and another port on the PC.
Attempted this with 2 PC's, 1 Laptop all running Windows 7 Pro with SP1 64 bit and a Mac. Tried the cable that came with my Samsung S5 ( Not the USB 3 cable) plus 2 other cables that I use in the workshop and the original cable suppled by the customer. Phone not detected in device manager on any of the PC's, however the plugged in and unplugged sounds do play. Mac sit's idoly twiddleing its thumbs...
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
Went into bootloader and fastboot. only option I have to locate the S/N is via show barcodes. the S/N is:- HT444WM04348
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I dont think it would be under warranty as customer reckons it is over 12 months old.
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?
Click to expand...
Click to collapse
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.

PC1staid said:
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.
Click to expand...
Click to collapse
Now that you mention that, I think there may be an Australian variant (OP6B110) which also has the product ID (M8_UL_CA) indicated on the bootloader screen.
Either way, its not the Euro variant; and its been modified by a previous owner (as mentioned).
Any luck getting USB fastboot working? Once you do, do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can verify the MID and make sure you are running the right RUU.

exactly the same problem
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India

sonalgirdhar said:
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India
Click to expand...
Click to collapse
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.

redpoint73 said:
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.
Click to expand...
Click to collapse
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.

sonalgirdhar said:
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.
Click to expand...
Click to collapse
"completely conked off" (your previous words) is not a good description of the above. Misleading, really.
Hold the vol down button during the bootloop cycle. Don't let go until you are on the bootloader screen. Then try to connect with fastboot.

My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..

tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..
Click to expand...
Click to collapse
Hi.. Did u find any solution to the problem. The service center here also refused to take a phone bought outside india.

Hi..
Please find attached the result of 'fastboot getvar all'. i had also shared the same with HTCDev team and the reply is as below:
"Hello Sonal
I sincerely thank you for sending us the information that was requested . According to the information you have provided, I was able to identify the reason why the device can not receive updates at this time. For your device to without any problem , it must have all the original software or settings and STOCK.
To begin , let me explain how our devices are distributed to security S -ON to protect your settings and to ensure proper operation. Security on your device has been disabled ( S -OFF) which has allowed the following parameters change at this time prevent the upgrade is installed
cidnum : 11111111 < ---- this parameter will not get your device updates
Here are the options for you:
Option 1 - Return all device settings to their original settings or STOCK. - First you must change the parameters specified as these were originally. Once this is done, now again to contact STOCK install the operating system.At this time, HTC doesn't officially support obtaining S-Off on our devices. Having said that, I'll be happy to take a look at what's going on and at least point you in the right direction. I know this may cause some limitations in the assistance I am able to provide to you but I am more than happy to do what I can to assist you through your issue . We are happy if you contact us about any problems you might, in any part of their development process. .To begin with, the following websites are some examples where we recommend you start your research on S-Off. http://forums.xda-developers.com http://www.androidcommunity.com http://androidforums.com Please note the above web sites are not operated by HTC. We can not validate or guarantee the information contained therein.
Do not hesitate to reach out to us if you have any questions. You can contact us back via email, using the second link listed below (The one at the end of the sentence "To send a reply to this message, please click here"). "
Can you please help with the next steps to get the phone working again.

sonalgirdhar said:
Please find attached the result of 'fastboot getvar all'.
Click to expand...
Click to collapse
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
sonalgirdhar said:
i had also shared the same with HTCDev team and the reply is as below:
Click to expand...
Click to collapse
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc..
Click to expand...
Click to collapse
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.

redpoint73 said:
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.
Click to expand...
Click to collapse
@redpoint73 Thank you so much, have been able to update the RUU. Updating apps now