Database Info

[Q] Black Screen / Red triangle after RUU ICS Update

I tried to update my HTC Desire S with ICS update downloaded from HTC and although it appeared to install fine the phone won't boot. It just sits on a black screen, and if I try to enter recovery it shown the red triangle with the exclamation mark! I've tried Factory Reset but that does not work.
I have read that I should NOT have install an official ROM through the RUU while being on S-OFF and that I should have used PG88IMG.zip instead
There was nothing I need on the phone so I did not make a backup and I’m not sure how to access the SD card while in volume down and power mode.
What can I do to fix this issue?
If i press volume down and power:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3831.19.00.110
eMMC-boot
Mar 10 2011, 14:58:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

Your hboot version is not ringing any bells?
Hint: you do not have a custom recovery anymore
Sent from my HTC Desire S

amidabuddha said:
Your hboot version is not ringing any bells?
Hint: you do not have a custom recovery anymore
Sent from my HTC Desire S
Click to expand...
Click to collapse
how do i fix it or is the phone completely dead.

Shabz81 said:
how do i fix it or is the phone completely dead.
Click to expand...
Click to collapse
Don't worry, you didn't brick your phone yet. But your HBOOT (v6.98.1002) doesn't support the /system/lib partition necessary for the ICS RUU. That's why the installation didn't succeed and why your phone can't boot. You should be able to flash a custom recovery again and from this recovery a custom ROM. You also upgraded your radio when you tried to flash the RUU.

yaonos said:
Don't worry, you didn't brick your phone yet. But your HBOOT (v6.98.1002) doesn't support the /system/lib partition necessary for the ICS RUU. That's why the installation didn't succeed and why your phone can't boot. You should be able to flash a custom recovery again and from this recovery a custom ROM. You also upgraded your radio when you tried to flash the RUU.
Click to expand...
Click to collapse
How do I do this? please explain in a simple step-by-step guide as I don’t want to do any more damage.

can anyone help with this issue?

The silence is a small hint for you. It's called "Google it".
People are tired of answering the same questions 3 times a day.
Look at the General section, there's another one like you.

Jack_R1 said:
The silence is a small hint for you. It's called "Google it".
People are tired of answering the same questions 3 times a day.
Look at the General section, there's another one like you.
Click to expand...
Click to collapse
Thanks for nothing Jack
I manage to fixed it by following this link: http://forum.xda-developers.com/showthread.php?t=1679338
I used a second sd card, I formatted it first and only put the file I need at that time on it. I
In step 5 Reboot into bootloade, select recovery wait till you see the screen with the red triangle exclamation mark and press the volume up and power button at the same time.
You will enter the Android system recovery <3e> and see the following options:
reboot system now
apply update from SD card
wipe data/factory reset
wipe cache partition
wipe the cache partition and wipe data/factory reset
Now following step B from this link: http://forum.xda-developers.com/showthread.php?t=1858508
When update is finished - reboot, then configure ICS and delete PG88IMG.zip from sd card.

Congratulations - you actually did what Jack suggested and SEARCHED. We do not exist here as free tech-support for people who are too lazy to bother searching or reading - especially when the same damn question is asked time after time after time.
On another note - insulting very knowledgeable and respected members of the forum is a very, very stupid thing to do. Firstly because it will get his back, and many other peoples' backs, right up. Secondly, because if he was so minded then you could easily find the next response you get to a question is either total silence or advice that would end up bricking your phone totally.
When you rely on people, do not pi$$ them off - that is one of the first things you learn as a soldier and is is equally applicable in everyday life.

SimonTS said:
When you rely on people, do not pi$$ them off - that is one of the first things you learn as a soldier and is is equally applicable in everyday life.
Click to expand...
Click to collapse
So true.

@Jack_R1 and SimonTS. I did not mean to piss anyone off, I was just seeking an answer

#3
please tell me step by step!

Little Sykes said:
please tell me step by step!
Click to expand...
Click to collapse
Search and read - First rule of XDA.

The link for recovery, the pg88img method.
http://forum.xda-developers.com/showthread.php?p=41343637
Sent from my HTC Desire S using XDA Free mobile app

Thats because yer using a stock recovery. If you want to enter it,just press v up and power on warning black screen. Easy.
Sent from my Desire S using XDA Free mobile app

[Q] Bootloop after rebooting

Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??

That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.

CNexus said:
Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??
Click to expand...
Click to collapse
I've had that happen a couple times but it was because it was something I did/flashed, I agree with prboy, ruu back and format memory card (save your stuff to the computer first)- I've forgotten to save first a couple times

prboy1969 said:
That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.
Click to expand...
Click to collapse
I'll definitely try that, I don't know if this shed anymore light on it but my sdcard doesn't mount through my phone anymore either...happened around the same time as the restarting thing
But I'll tr and see what happens, if not I'll just take it in to sprint, I know it can't be something I flashed, I've been on stock for a while because of my utility
Sent from my PG06100 using xda premium

I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.

prboy1969 said:
I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.
Click to expand...
Click to collapse
Nope, no custom anything. 100% stock 2.2 with temproot, but since I can't reboot its really permroot lol
Sent from my PG06100 using xda premium

Then I would defiantly try what I stated above. See if it can resolve the issue.

prboy1969 said:
Then I would defiantly try what I stated above. See if it can resolve the issue.
Click to expand...
Click to collapse
Will do
Sent from my PG06100 using xda premium

Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot

KiDxNinja said:
Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Click to expand...
Click to collapse
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?

prboy1969 said:
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?
Click to expand...
Click to collapse
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo

KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Have you tried booting it up while connected to a USB cord? That works for me because my phone will otherwise go into a bootloop whenever I restart it
Sent from my PG06100 using xda premium

KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?

prboy1969 said:
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?
Click to expand...
Click to collapse
Yes and Yes, read my first post -_-

KiDxNinja said:
Yes and Yes, read my first post -_-
Click to expand...
Click to collapse
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11

prboy1969 said:
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.

KiDxNinja said:
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.
Click to expand...
Click to collapse
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2

YoungCorruptionV2.0 said:
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I was just about to say that, if the name of the file isn't correct, the bootloader won't pick it up.

Yeah i know, i was just too lazy to type it out. I know what im doing as far as general modding and flashing, and I actually managed to fix it. I'm not positive how but I used the unroot back to stock guide for the stock locked bootloader. After flashing it through hboot I tried the 2.3.4 RUU. Still bootlooped but I was at stock with locked bootloader. I then used htcdev to reunlock the bootloader and I was then able to flash partitions through fastboot. I flashed cwm and was able to adb through it. I basically just reran through the rooting phase and gained temproot. From here I redid the steps to engineer hboot and finally received s-off. After this it booted normally. I might be leaving steps out but if anyone needs specifics, just pm me and maybe I can figure it out again for you.
Sent from my PG06100 using Tapatalk 2

help with boot loop loop loop
hi
someone can help whit phone?
in summer i restart phone and it stuck in loop htc logo in white over and over agen
till batrtery go down and nothing happen when trying to charg only led was flashing
no to long ago i plug to charger ad phone torn back on, sd card was out
I turn it off put sd card back on phone turn back on, try to software update one and second time it go back to loop agen=[
rand battery down agen and it does not torn back on, to hboot
well it does if i play whit it holding power bottom volume down longer time
speed xe ship s-on
hboot-0.99.0001
radio-1.08.01.0111
emmc-boot
can some one give me step by step instruction?

[Q] Help, may have bricked

A little foreshadow. I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install. I was silly and decided to clear the system... Which erased my OS completely.
For a while I was able to get to the TWRT(?) screen where I could mount my sd card, etc. While researching the problem I came across this:
a solution of fastbooting a recovery.img
I ran the fastboot recovery.img. The only problem is the only screen I can now access is the bootloader. I have bootloader 1.14.0002 loaded onto my phone if that helps.
Is there anyway to try to get a operating system or flash a rom onto this phone still or is it bricked for good? Also if I was able to put a rom onto it, what do you sugggest?
When I try to go to Recovery or Factory Reset, I get the HTC screen with the red text underneath it and it never goes any further.
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
That is the information listed in my bootloader as of now. I am not showing it listed as a drive in my computer when connected to USB. Also when I 'power off' I am in a reset cycle that doesn't stop.
I really appreciate any help in advance. This was a big wake up call to myself about how I should be a lot more careful when messing with these things.
Thank you to everyone that answers!

http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
You might be hosed. Can you get into bootloader?
Sent from my One X using xda premium

Read before doing anything. Such a simple task. It's easy to read, it's hard to come back from a brick.
Sent from my One XL using XDA Premium

You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer. http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.0-evita.img
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2

Not only does fastboot erase cache not take long it avoids many stupid little issues. I would say it's a must when flashing a new recovery.
Sent from my One X using xda app-developers app

sinkthehalffoot said:
I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install.
Click to expand...
Click to collapse
The reason it went to recovery is very simple. The OTA needs to have stock recovery in order to install. You don't have stock recovery on your phone anymore, you have custom recovery (TWRP). So the OTA stalled there, when it didn't find stock recovery.
sinkthehalffoot said:
I was silly and decided to clear the system... Which erased my OS completely.
Click to expand...
Click to collapse
Of course it did, what were you expecting to happen? Wiping the OS is the very definition of what happens when you wipe system. If you didn't know what wiping system would do, you shouldn't have done it. For that matter, you shouldn't be doing anything on your phone if you don't know what its for.
A lot of this points to a fundamental lack of reading and understanding:
- Don't know the name of the custom recovery installed on the system
- Wiping things without knowing what they are
- Basic rule (that many folks here seem to ignore, for reasons unknown): Don't install any OTA on a rooted device without first researching what will happen
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
You aren't bricked. With very few exceptions (and this isn't one of those) if the screen turns on, and you can get into hboot, the phone is recoverable. And probably fairly easily so, with the right steps. But you need to do some homework before proceeding.

redpoint73 said:
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
Click to expand...
Click to collapse
+1000
This is exactly the kind of situation that occurs when people get in over their heads and start blundering around.
http://forum.xda-developers.com/showthread.php?t=2232141

InflatedTitan said:
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer.
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In case anyone ends up stumbling here with a similar issue, this solution worked to a 'T'. Thank you again InflatedTitan.
To everyone else, yes I know, I should of read more than I had. I saw the jellybean update and have been wanting it for a while and acted with haste. I learned a valuable lesson from it all.

Lol this "solution" was around before you posted. You just didn't read or search enough.
Sent from my One X using xda app-developers app

F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium

Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol :beer:
Sent from my HTC One X using xda app-developers app

Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2

InflatedTitan said:
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I thought I was the only one. In fact I just rooted a nook tablet and installed twrp. Slides to flash... And I could swear I was on cloud 9.
But bravo on the explanation sir. Love a good write up. Even though i already know it, feels good to read it.
Sent from my Carbon-ize Evita using xda-developers app

[HELP] Not sure if bricked or hardware issue?
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28

pharrjw said:
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?

exad said:
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
Click to expand...
Click to collapse
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?

If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Sent from my HTC One X using xda app-developers app

pharrjw said:
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
Click to expand...
Click to collapse
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.

Thanks again for the replies guys.
31ken31 said:
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Click to expand...
Click to collapse
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
exad said:
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Click to expand...
Click to collapse
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.

pharrjw said:
Thanks again for the replies guys.
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
Click to expand...
Click to collapse
factory reset in bootloader corrupts the SD card. We wont worry about that just yet as there's nothing we can do about it until we can get recovery on there.
You're going to have to be very careful because it sounds like your EMMC partitions might have some issues. if you can get it to bootlaoder KEEP IT AT THAT SCREEN. don't power it off or anything, leave it there. Because one wrong move could be a perma brick. If we can get a rom on there to S-OFF with, we can RUU to restore your emmc partitions.

[SOLVED] Flashing light, no screen...Help appreciated!

Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again

What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita

timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated

So does it power on at all?
Sent from my Evita

timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!

Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.

It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita

Hi from Canada!... I just wanted to be part of the greetings.. :laugh:

exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)

I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.

My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita

timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:

Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated

Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita

timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated

Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita

timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now

Stuck on hboot and recovery, internal/external storage not readable. Help!!!!

Here is my problem.
I have an HTC M8 with Verizon, was doing an upgrade in HTC Sync Manager
during the upgrade/update, it stopped. I was on android 4.4.3 I believe
I have never had this phone rooted, it is S-ON, Locked, bootloader is locked, HTC Dev does not let me get the token to unlock it. still shows official software in the HBOOT screen. never flashed anything to it.
when i first turn it on, goes to white screen with HTC logo. I can get to HBOOT, and recovery. Odd thing it, the recovery Doesn't read anything on the ext SD card or the internal storage. Already tried formatting the SD card multiple times, so i can't do anything from the recovery but wipe and factory reset.
when i plug the phone to a PC, HTC sync manager picks up the phone, but with no android verision, no Sense version, nothing, just the phone itself. In terminal, ADB does not recognize the device being attached, so can't do anything from ADB.
After researching, I am lead to believe it has something to do with the storage partition, not being partitioned properly or something along those lines. I can't write anything to the storage, my PC usb only picks the phone up as a CD Drive, so i can't add or remove anything from it.
I am willing to pay someone that can fix this for me PLEASE!!!
Again, I can get to HBOOT, Fastboot, and recovery,
recovery does not read the internal or external storage

syllamonster said:
Here is my problem.
I have an HTC M8 with Verizon, was doing an upgrade in HTC Sync Manager
during the upgrade/update, it stopped. I was on android 4.4.3 I believe
I have never had this phone rooted, it is S-ON, Locked, bootloader is locked, HTC Dev does not let me get the token to unlock it. still shows official software in the HBOOT screen. never flashed anything to it.
when i first turn it on, goes to white screen with HTC logo. I can get to HBOOT, and recovery. Odd thing it, the recovery Doesn't read anything on the ext SD card or the internal storage. Already tried formatting the SD card multiple times, so i can't do anything from the recovery but wipe and factory reset.
when i plug the phone to a PC, HTC sync manager picks up the phone, but with no android verision, no Sense version, nothing, just the phone itself. In terminal, ADB does not recognize the device being attached, so can't do anything from ADB.
After researching, I am lead to believe it has something to do with the storage partition, not being partitioned properly or something along those lines. I can't write anything to the storage, my PC usb only picks the phone up as a CD Drive, so i can't add or remove anything from it.
I am willing to pay someone that can fix this for me PLEASE!!!
Again, I can get to HBOOT, Fastboot, and recovery,
recovery does not read the internal or external storage
Click to expand...
Click to collapse
Does hboot read sdcard?
You want to run RUU through hboot (not recovery), either using sdcard or fastboot method.
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

andybones said:
Does hboot read sdcard?
You want to run RUU through hboot (not recovery), either using sdcard or fastboot method.
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
I thought you had to be S-Off to do that?
to run RUU, you naming it for hboot to reading when it first boots?

syllamonster said:
I thought you had to be S-Off to do that?
to run RUU, you naming it for hboot to reading when it first boots?
Click to expand...
Click to collapse
You can RUU with s-on. Wouldn't have suggest it otherwise.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473

andybones said:
You can RUU with s-on. Wouldn't have suggest it otherwise.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Click to expand...
Click to collapse
OK downloading it right now. Thank you for helping so fast, I'll keep you posted

syllamonster said:
OK downloading it right now. Thank you for helping so fast, I'll keep you posted
Click to expand...
Click to collapse
Very welcome, my friend.

andybones said:
Very welcome, my friend.
Click to expand...
Click to collapse
You are Freakin Awesome!!! I almost have tears in my eyes, you saved my butt. Sending appreciation

syllamonster said:
You are Freakin Awesome!!! I almost have tears in my eyes, you saved my butt. Sending appreciation
Click to expand...
Click to collapse
More than welcome glad I could help. Very much appreciate the donation!

syllamonster said:
OK downloading it right now. Thank you for helping so fast, I'll keep you posted
Click to expand...
Click to collapse
Best part is the s-on ones don't wipe /data. They can be flashed by both s-on and s-off devices.
The s-off ones do and are also pre-rooted and can only be flashed while s-off.
Sent from my Nexus 6 using Tapatalk

Good to know it won't wipe data, unfortunately I had already tried so much crap, even HTC support had me wipe, factory reset,all with no resolution. I was screwed.
I was only trying to upgrade from 4.4 android to 5, using HTC own sync manager, and it failed.
I don't think I will be messing with anything software, Rom, firmware, recovery, RUU, adb and fastboot related any time soon. I shouldnt even know half this stuff, and I didn't until last night when my phone went to hell and back.

syllamonster said:
Good to know it won't wipe data, unfortunately I had already tried so much crap, even HTC support had me wipe, factory reset,all with no resolution. I was screwed.
I was only trying to upgrade from 4.4 android to 5, using HTC own sync manager, and it failed.
I don't think I will be messing with anything software, Rom, firmware, recovery, RUU, adb and fastboot related any time soon. I shouldnt even know half this stuff, and I didn't until last night when my phone went to hell and back.
Click to expand...
Click to collapse
Ah...well seek out help sooner next time. These ruu make it easier. I have even packed some of these new ones up as exes to make it sorta hands free.
Sent from my Nexus 6 using Tapatalk