Database Info

Htc desire s stuck at Htc logo , even cannot make factory reset

Hi experts
One of my friend brought his Htc stuck at Htc logo even I cannot make factory reset in boot mode.. When I click factory reset nothing happens.. Don't know where to start? Can somebody tech me
I made gold card successfully
Thank you

Give some more info please
1) what is written on the top part of the screen when in boot mode
it should look similar to this:
Code:
---AlphaRev---
SAGA pvt ship S-off RL
HBOOT-6.98.1002
RADIO-3805.04.02.01_M
eMMC-boot
2) can you access RECOVERY from the boot mode menu
if yes make a picture of it and attach it here
Also see here, there are some ways to restore from white screen issue.

SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO - 3805.06.02.03_M
eMMC - boot
and if i press recovery showing recovery symbol and phone get off and vibrating 3 times
And i downloaded this file
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed.exe
when i try to update ..its stuck at rebooting to bootloader

I have a similar problem. But mine is s-off and unrooted, it occurred when I tried updating with the system OTA update (about 230mb in size). It updated, showed the circular green stuff on the black screen, booted a few times then just stuck at the HTC screen on the white background.
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
Please would appreciate your help

sharaz191 said:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO - 3805.06.02.03_M
eMMC - boot
and if i press recovery showing recovery symbol and phone get off and vibrating 3 times
And i downloaded this file
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed.exe
when i try to update ..its stuck at rebooting to bootloader
Click to expand...
Click to collapse
It seems that your problem is complicated. Stock software and no recovery access makes it difficult to give an appropriate advice. Maybe something wrong was flashed on this phone or the worst case - "fried" eMMC chip. You can try to search across the forum for any similar or try various solutions but I cannot advice how to proceed. Sorry
linkin8k said:
I have a similar problem. But mine is s-off and unrooted, it occurred when I tried updating with the system OTA update (about 230mb in size). It updated, showed the circular green stuff on the black screen, booted a few times then just stuck at the HTC screen on the white background.
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
Please would appreciate your help
Click to expand...
Click to collapse
There are at least 10 other threads from the past 2 weeks with exactly the same problem. Do some reading, the solution is simple...

Please just tell me what to do or give me the thread cause I have searched and can't find precisely what will help. Just post something please I beg you.

here you go
Sent from my HTC Desire S using Tapatalk

Can I solve by jtag?

sharaz191 said:
Can I solve by jtag?
Click to expand...
Click to collapse
Surely simpler to return under warranty?
Swyped from my Desire S using XDA Premium

Tried everything in the thread and it won't still work.

I downloaded RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed and used it. It showed successful but got stuck at the htc logo white screen again. When i tried using the ruu again it showed the old version which it supposedly upgraded was still in the phone.
Please help am so frustrated

linkin8k said:
I downloaded RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed and used it. It showed successful but got stuck at the htc logo white screen again. When i tried using the ruu again it showed the old version which it supposedly upgraded was still in the phone.
Please help am so frustrated
Click to expand...
Click to collapse
Hint - flash hboot 0.98.2000
After use the latest RUU 2.10.401.8
Sent from my HTC Desire S using Tapatalk

Thanks for the quick reply. I have already tried flashing hboot_0.98.0000_361a7ba6_0310 onto it using android flasher in "fastboot usb plug" but it reboots and gets stuck at the htc logo again until i remove the battery.
Also here is what androidflasher shows me :
sending "hboot" (1024kb)...
OKAY [0.191s]
writing "hboot"...
(bootloader) image update is bypassed!
OKAY [0.030s]
finished.total time:0.221s
rebooting into bootloader...
OKAY [0.248s]
finished.total time:0.248s
rebooting....
finished. total time: 0.244s

**update**
was able to flash 4ext recovery using android flasher onto my device and tried updating with the ruu again. It still gets stuck at the htc logo white background (so i painfully remove battery again) but when i try running the ruu again from my pc it shows that i have the same version as the ruu.
Still stuck at white screen. Help!!!

linkin8k said:
**update**
was able to flash 4ext recovery using android flasher onto my device and tried updating with the ruu again. It still gets stuck at the htc logo white background (so i painfully remove battery again) but when i try running the ruu again from my pc it shows that i have the same version as the ruu.
Still stuck at white screen. Help!!!
Click to expand...
Click to collapse
see the version of the bootloader
if it is still 6.98.xxxx this is you problem. Flash 0.98.2000 with PG88IMG.zip from the SDcard or try 2.00.2002 - you can find this in the forums also

linkin8k
I have the same problem and I have not found the solution up here.

can anybody tell me can i solve this by JAG?i can do jtag my self

thanks for the replies sorry i couldn't post yesterday was trying to be in a festive mood.
**my progress**
I have tried all i can to update the bootloader, from putting the pg88img file in through root of sd to update through 4ext recovery to tryin to use android flasher to put the 0.98.2000 it won't just update.
please what else can i do?? is there a hboot installer for windows for me to try??
please help AmidaBuddha u have done a lot but i still need a little help. thanks

As much as i know would be the last possible solution to replace the bootloader with dd command inside adb shell or try to flash it with fastboot (to make this the htc drivers [if you are using windows] and the android sdk with the given android plattform-tools must be installed, if some parts are not present look at the index thread)
Walkthrough:
fastboot:
reboot your device to bootloader and put it in fastboot mode
open commanline at your pc
attach device to pc
cd to the directory where the hboot.img is ( extract it from the pg88img.zip file)
Code:
fastboot devices
(your device should show up as some letters and digits at the right of it should stand recovery, also the adb daemon is started if it wasn't running before)
fastboot flash hboot hboot.img
this replaces your current hboot with the hboot.img file, don't interrupt the process or pull the usb cable, this can brick your device, i'm not responsible if something goes wrong.
dd:
put the needed .img file of the bootloader at the root of your sd (extract it from the pg88img.zip file) and rename it to hboot.img
reboot to recovery
Open commandline at your pc
attach device to pc
Code:
adb devices
(your device should show up as some letters and digits at the right of it should stand recovery, also the adb daemon is started if it wasn't running before)
adb shell
(this opens the adb command shell, from where you can execute shell commands right at your device)
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
(this backups your current bootloader partition to the backup.img file)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
(this replaces your bootloader partition with the boot.img)
exit
(exits adb shell)
adb reboot bootloader
(reboots your device to bootloader)
this backups your current bootloader to /sdcard/backup.img and replaces it with the boot.img, but beware this is hard stuff and be carefull, don't stop the execution of the any dd command and never pull the usb-cable while it writes your bootloader, this definitly can brick your device, i'm not responsible if something goes wrong, good luck.

Tectas thanks, see what i get using fastboot:
on command line:
c:\users>fastboot devices
SH14HTJ05*** fastboot
c:users> cd c:\temp
c:\temp>fastboot flash hboot hboot.img
sending `hboot` <1024 kb>... OKAY
writing `hboot`... INFOimage update is bypassed!
OKAY
on phone under bootloader menu:
Can not roll back hboot version
........
will try dd option now.

[Q] Bricked? By trying to get s-on

Dear xda-community,
as said in the title i dont know if i bricked my device by trying to get s-on again.
At first i read some threads here about getting s-on again and revert to stock.
I was s-off by revelutionary and flashed the ENG-hboot a few days ago (0.98.2000). After that i flashed the stock 1.47 rom and was trying to get s-on and stock again with the 1.47 RUU. I read that if i have the ENG-hboot i can run the RUU and then i get back to stock and s-on. But after i was running the RUU, i get to the bootloader again (on the phone). In the header stands now "*** Security Warning ***" and i'm s-on again like i want it with hboot 0.98.0002.
But the problem is that i cant get out of the bootloader, i can only acsses fastboot and the bootloader. If i click 'recovery', 'reboot' or anything else it only restarts the bootloader. I cant even turn the phone off, only with pulling the battery :/
So i'm stucked in the hboot 0.98.0002 with s-on and i dont know what i can do now or if i bricked my desire s permanently
Can anyone help me please?

are you sure that you have used the right RUU?

amidabuddha said:
are you sure that you have used the right RUU?
Click to expand...
Click to collapse
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?

Jahai said:
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?
Click to expand...
Click to collapse
It should be if you bought it in Europe. What happens when you try the RUU again? You should do this when "FASTBOOT USB" is written on your phone screen.

amidabuddha said:
It should be if you bought it in Europe. What happens when you try the RUU again?
Click to expand...
Click to collapse
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S

Jahai said:
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S
Click to expand...
Click to collapse
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit

amidabuddha said:
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit
Click to expand...
Click to collapse
thank you for your help!
i will try that and report back in a few minutes

hm
i cant get it to work in this way :/
if i write fastboot flash system C:\android-tools\system.img
it tells me:
"sending 'system' (571388 KB)...
OKAY [93.130s]
writing 'system'...
(bootloader) signature cheking...
FAILED (remote: signature verify fail)
finished. total time: 166.095s"
its the same with boot_signed.img and recovery_signed.img

if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?

So you problem maybe sounds the same, but it is not.
Try
Code:
fastboot oem rebootRUU
Your phone will reboot to a black screen with silver HTC logo. Then run the RUU.
Other options is to go to the repair centre and tell them that this happened during OTA update.
Sent from my HTC Desire S using Tapatalk

Jahai said:
if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?
Click to expand...
Click to collapse
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk

amidabuddha said:
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
will try it with that. since now i tried it until 2.10.401.4
Edit: it took me ages to download that ruu from filefacrtory :/

i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever

Jahai said:
i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever
Click to expand...
Click to collapse
Go to repair center and say that the OTA update did this (it is the same as RUU) They should repair it for free
Sent from my HTC Desire S using Tapatalk

maybe there is any way to get s-off from fastboot or bootloader?

got to new hboot with this instruction: http://forum.xda-developers.com/showpost.php?p=20850548&postcount=22
managed to get the unlocktoken from htcdev but if i flash it everything themes fine, but i cant choose the option yes (unlock bootloader).
if i choose "no" and press the power button it reboots like it should but if i choose "yes" and press the power button nothing happens. i can still choose between the options but nothing happens :/
anyone know how i can get it working to unlock this bootloader and flash a custom recovery?

HTC One XL hboot 2.15.0000 can't unbrick

My HTC One XL went on low battery and i plugged it on charge. Power outages meant the phone couldn't charge and when power came back on, I plugged it again on charge for about two hours. I tried booting the phone and the phone couldn't start, but the red light kept blinking even though it was unplugged from the charger. I pressed and held the power button for a while and turned it on again. It came on, but could not boot pass the "HTC quietly brilliant" screen, it kept restarting from that screen after it stays on for some seconds.
Next thing i did was to boot into bootloader. The bootloader was initially "Unlocked" but when the bootloader came up, it showed "LOCKED", which means the bootloader has gone back to locked all by itself. I tried unlocking the bootloader again, but when the unlocking warning screen shows up and i select "YES", it restarts and the "HTC quietly brilliant" screen keeps restarting. I tried factory reset from bootloader but the htc screen comes up and restarts from there.
The next thing i did was to look for an RUU. I couldn't find any, as most of the links were down. So i downloaded "RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radi o_0.19as.32.09.11_2_10.105.32.25L_release_271865_s igned" and I tried flashing from there, but the RUU loader could not load on the phone, could not even restart into the bootloader, as the HTC screen keeps restarting. RUU could not also be loaded from fastboot commands. I tried flashing a new kernel, but the phone doesn't allow the command to push the "boot" image file.
The phone was running on the official T-Mobile 4.2.2 Sense 5 which I updated OTA before unlocking the bootloader, and everything was working just fine, until the phones battery run low and the bootloader went back to locked by itself. Please help, as it seems all options have been exhausted. I have attached a copy of an image of my bootloader. But the details are as follows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OpenDSP-v33.1.0.45.1128
eMMC-boot
Aug 14 2013, 16:02:22:-1
Please help :'(

Running an older RUU (older hboot version) is not possible with S-on.
You also can't run another carrier's RUU unless you are SuperCID.
Also, you can't flash a kernel with a locked bootloader and S-on.
Don't know how your phone got screwed up the way it is. But since you are hboot 2.15 and s-on, you are somewhat stuck (no current RUU, no way to run an older RUU).

redpoint73 said:
Running an older RUU (older hboot version) is not possible with S-on.
You also can't run another carrier's RUU unless you are SuperCID.
Also, you can't flash a kernel with a locked bootloader and S-on.
Don't know how your phone got screwed up the way it is. But since you are hboot 2.15 and s-on, you are somewhat stuck (no current RUU, no way to run an older RUU).
Click to expand...
Click to collapse
Thank you very much. At least, you replied. I don't even know how this is possible. I have tried "fastboot flash unlocktoken Unlock_code.bin" over a million times, still, the bootloader shows "*** LOCKED ***"
I have almost exhausted every option out here. I've spend so many days trying everything possible, but all i get is this locked bootloader.

Economistaterry said:
Thank you very much. At least, you replied. I don't even know how this is possible. I have tried "fastboot flash unlocktoken Unlock_code.bin" over a million times, still, the bootloader shows "*** LOCKED ***"
I have almost exhausted every option out here. I've spend so many days trying everything possible, but all i get is this locked bootloader.
Click to expand...
Click to collapse
Its very odd that it says "LOCKED", as its not supposed to say that after being UNLOCKED, only RELOCKED. Its also not supposed to go back to LOCKED by itself. No technical evidence to think so (just a hunch), but it makes me think that the bootloader has been damaged or corrupted.

redpoint73 said:
Its very odd that it says "LOCKED", as its not supposed to say that after being UNLOCKED, only RELOCKED. Its also not supposed to go back to LOCKED by itself. No technical evidence to think so (just a hunch), but it makes me think that the bootloader has been damaged or corrupted.
Click to expand...
Click to collapse
so can the bootloader be repaired? if yes, how?

Economistaterry said:
so can the bootloader be repaired? if yes, how?
Click to expand...
Click to collapse
Possibly. But since you are s-on, your only option (that I can think of) is an appropriate RUU (equal or higher hboot version). But since no RUU with hboot 2.15 or higher is available, you will have to wait for one to be released.
Don't know what else can be done. You might be stuck.

Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.

redpoint73 said:
Possibly. But since you are s-on, your only option (that I can think of) is an appropriate RUU (equal or higher hboot version). But since no RUU with hboot 2.15 or higher is available, you will have to wait for one to be released.
Don't know what else can be done. You might be stuck.
Click to expand...
Click to collapse
The red light which shows that the battery is charging never turns green. I have left it on charge over night so many times, but green never shows. Then the red light also stays solid for like 6seconds, goes off for like 2 or 3 seconds and comes back on. It never turns solid like it does when it's fully working, even when I leave it on charge for a long time.

twistedddx said:
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
Click to expand...
Click to collapse
When ever I give the rebootRUU command, the phone restarts, the black HTC screen never shows.

Have you tried
fastboot erase cache
and then try rebootRUU?

twistedddx said:
Have you tried
fastboot erase cache
and then try rebootRUU?
Click to expand...
Click to collapse
Yes please, I just did that a couple of times. It only reboots the HTC white screen, same problem.

From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?

twistedddx said:
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
Click to expand...
Click to collapse
I gave the "fastboot flash recovery recovery.img" command and all i get is "sending 'recovery' (9060 kb) . . ." and nothing happens. The green bar which will show on the bootloader shows, but doesn't load. I have done this a couple of times, same results

twistedddx said:
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
Click to expand...
Click to collapse
Its a good idea, and certainly worth a try.
Although it must be remembered that not all the hboot modules were deployed with the 5.08 OTA. Just one of the three modules, I forget.

So to recap(these are more questions then statements):
-phone was upgraded to T-Mobile 5.08 and therefore has all 5.08 firmwares
-your phone can not boot into a ROM.
-your phone can not boot into recovery?
-fastboot works? You tried: fastboot oem readcid and get a response? What response?
-you cleared cache with fastboot erase cache
-flashing recovery fails?
-relock the phone, power cycle then do fastboot oem lock. Even though the phones says locked it might help to reset the lock state manually.
-Unlock token fails? Did you try to get a new token from HTCDev. Old tokens become invalid if your CID changes etc, go get a new one and try again
-RUU fails? You tried 2.20 I know but why not try 3.18 just for fun.
-rebootRUU mode fails? note it is cAsE sEnSiTiVe.
You are quickly running out of options, sending to HTC or independent jtag repair are probably the only way forwards.
If timmaaa and redpoint73 are out of ideas your problems are beyond repair by "XDA Q&A helpdesk support"

twistedddx said:
So to recap(these are more questions then statements):
-phone was upgraded to T-Mobile 5.08 and therefore has all 5.08 firmwares
-your phone can not boot into a ROM.
-your phone can not boot into recovery?
-fastboot works? You tried: fastboot oem readcid and get a response? What response?
-you cleared cache with fastboot erase cache
-flashing recovery fails?
-relock the phone, power cycle then do fastboot oem lock. Even though the phones says locked it might help to reset the lock state manually.
-Unlock token fails? Did you try to get a new token from HTCDev. Old tokens become invalid if your CID changes etc, go get a new one and try again
-RUU fails? You tried 2.20 I know but why not try 3.18 just for fun.
-rebootRUU mode fails? note it is cAsE sEnSiTiVe.
You are quickly running out of options, sending to HTC or independent jtag repair are probably the only way forwards.
If timmaaa and redpoint73 are out of ideas your problems are beyond repair by "XDA Q&A helpdesk support"
Click to expand...
Click to collapse
-yes, 5.08 OTA
-yes, can not boot into a ROM
-yes, can not boot into recovery
-yes, INFOcid: T-MOB101
-yes, can clear cache with fastboot
-yes, flash recovery fails
-fastboot oem lock comes "INFODevice is already locked!"
-yes, unlocktoken fails. Got millions of new tokens from htcdev, all can't unlock, but will try again
-yes, RUU fails, will try the version u mentioned
-yes, rebootRUU fails, and i know its case sensitive
Thanks a lot for your support. Am in Ghana, no htc servive center here, no jtag repair center too.

Another observation I've made.
The red light which shows the battery is charging, never turns green. I left it on charge for almost 24hours. Then the red light which shows a charge also does not stay solid for more than 5 seconds. It goes off, and comes on again, never stays solid red to indicate a charge, like it normally does when it was was fully working. I run fastboot getvar all and the battery status shows good, but sometimes too low.
Again, if I unplug the charger, the red light continues to show, like its still on charge, shows for like 5 seconds, and goes off, and comes back on, never stops.
Can it be that the battery is damaged? And if the battery is damaged, can it be the cause of all these issues?

Economistaterry said:
Another observation I've made.
The red light which shows the battery is charging, never turns green. I left it on charge for almost 24hours. Then the red light which shows a charge also does not stay solid for more than 5 seconds. It goes off, and comes on again, never stays solid red to indicate a charge, like it normally does when it was was fully working. I run fastboot getvar all and the battery status shows good, but sometimes too low.
Again, if I unplug the charger, the red light continues to show, like its still on charge, shows for like 5 seconds, and goes off, and comes back on, never stops.
Can it be that the battery is damaged? And if the battery is damaged, can it be the cause of all these issues?
Click to expand...
Click to collapse
It could be a hardware issue.. But I doubt a hardware issue would mess up your hboot to the point you cant do anything.
You won't be able to flash anything with a locked bootloader. Keep trying to unlock the bootloader. Use the same unlock token, you do not need to re-request new ones everytime. if/when it fails to unlock, press and hold power until the phone shuts off, let go of power, press and hold volume down to go back into bootloader then try again with the same unlockcode bin file. Repeat until it unlocks. It may take many many tries. Press and hold power to hard power off the phone between tries every time.
When you finally do get it to unlock post here and we will fix your hboot issues.

redpoint73 said:
Its a good idea, and certainly worth a try.
Although it must be remembered that not all the hboot modules were deployed with the 5.08 OTA. Just one of the three modules, I forget.
Click to expand...
Click to collapse
twistedddx said:
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
Click to expand...
Click to collapse
guys, there has been some slight improvement. Initially, "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img" wasn't giving any reply, but today, i get this from flashing the boot and recovery image in the OTA 5.08 ...
C:\Users\user\Desktop\Fastboot>fastboot flash boot boot.img
sending 'boot' (6052 KB)... OKAY [ 1.182s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.836s
C:\Users\user\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9060 KB)... OKAY [ 1.512s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.490s
Does it mean anything? Does it mean flashing a different boot.img or recovery.img may work?

Economistaterry said:
guys, there has been some slight improvement. Initially, "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img" wasn't giving any reply, but today, i get this from flashing the boot and recovery image in the OTA 5.08 ...
C:\Users\user\Desktop\Fastboot>fastboot flash boot boot.img
sending 'boot' (6052 KB)... OKAY [ 1.182s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.836s
C:\Users\user\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9060 KB)... OKAY [ 1.512s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.490s
Does it mean anything? Does it mean flashing a different boot.img or recovery.img may work?
Click to expand...
Click to collapse
absolutely nothing will flash with a locked bootloader. Nothing nothing nothing.

Stuck in bootloader--no recovery or system [Help?]

Hello Guys, I need your help.
I got this INSPIRE 4G from a friend. When he gave it to me, he said it needed to be flashed.
The thing is, When you press the power button, it boots straight up into Fastboot.
Here Is my Hboot Info
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
Emmc-boot
Apr 12 2011,00:55:45
In Fastboot, i can move around with the volume buttons and power buttons(so that means the phone booting straight into Fastboot isnt a result of one of the volume buttons being stuck.)
When i try to access recovery from the Bootloader, It vibrates 6 to 8 times then the screen becomes black,it stays that way until i do a battery pull.
When i select factory reset from the bootloader, it does nothing.
WHen i select Image CRC from the Bootloader,These is what is printed on the screen.
OSBL: 0xC2C4DD79
AMSS: 0x6CC260EB
HBOOT: 0xF9E06F63
BOOT: 0x0
RECOVERY: 0x0
SYSTEM: 0x0
As the digit are displayed, the first three look okay,but the last three which are BOOT RECOVERY and SYSTEM seem to have no digits, Which kinda looks like its empty.
THESE ARE THE SOLUTIONS I HAVE TRIED.
1. I tried flashing a recovery from Fastboot, but it gives an error like this:
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
HT0BFRX06133 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (3704 KB)...
OKAY [ 0.664s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.672s
I get the same errors when i try to flash,erase or format the rest of the partitions(BOOT,SYSTEM).
2. I have also tried the HTC RUU, it finds the device and then gets stuck when it tries to boot into Android.
I have also tried the HTC RUU Hboot update but it also fails like the RUU ROm update.
3. I have also tried to flash the STock rom as PD98IMG.zip via bootloader, but when it finds the file, it asks me to press volume up to start update, when i press volume up, it loads the file and when its suppose to flash it, it sort of skips it and move to the next. It does that until its done the asks me to press power to reboot. Since it skips the files it stays the same after reboot.
3.I have Also tried flashing Eng-Hboot as PD98IMG.zip, But it skips that also.
4. I also tried to use this command Fastboot oem boot
And this is what i get:
C:\Program Files\Minimal ADB and Fastboot>Fastboot oem boot
...
(bootloader) Error status=0x400008
(bootloader) [SD_HW_ERR] SD: read fail ..
(bootloader) DATA_TIMEOUT
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 13
(bootloader) [ERR] boot image does not exist!!!
OKAY [ 1.418s]
finished. total time: 1.418s
I am begining to think that some how the partitions are corrupt or something.
PLEASE HELP ME OUT!!

@krook6023 The reason why i posted there also was because i wasnt sure what device it is wether its a DHD or INSPIRE 4G since it doesnt boot up and is stuck in bootloader,thats why i posted there also.Hope you understand and open the other thread incase someone over there has the answer to my problem.

You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.

spokanite said:
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
Click to expand...
Click to collapse
Thanks for your reply.But i tried 2. and made sure android-info.txt was appropriate, it just wouldnt flash. Looked like the partitions were corrupt thats why it wouldnt flash.
This is how it usually acts.
It finds the file, Loads the file on the upper right side of the bootloader with a green loading bar, after that, when its time for it to flash, normally shows up in red loading bar. It just moves as if it was flashing a 1kilobyte file. Then asks me to reboot.
After reboot nothing happens. Stays the same way.
But Right now, its even worse. After installing QHSUSB_DLOAD drivers, its refused to boot into bootloader ever since. but shows up as QHSUSB_DLOAD when connected to my pc.

Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?

bananagranola said:
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
Click to expand...
Click to collapse
I tried flashing CWM,TWRP,STOCK.... but non of them worked.
But as i said, after installing some drivers i found for QHSUSB_DLOAD, it no longer boots into bootloader.
But when i connect the device to a computer it only shows up as QHSUSB_DLOAD.
Any Help On that?

Nope, no idea. What drivers? From where?

bananagranola said:
Nope, no idea. What drivers? From where?
Click to expand...
Click to collapse
I found it on one of the threads.
at first, when the phone is connected to the pc, the charge light turns on and shows up as QHSUSB_DLOAD, but now no light or bootloader, just QHSUSB_DLOAD

Was it a DHD thread?

bananagranola said:
Was it a DHD thread?
Click to expand...
Click to collapse
Yea i guess so.
After the driver stopped the device from booting into bootloader, i read the README file that came with the driver and found out that it was for Some sort of Qualcomm Modem Device.
I guess thats why it bricked the device.

What thread?

bananagranola said:
What thread?
Click to expand...
Click to collapse
I cant seem to remember what thread it is. Cause I downloaded lost of the drivers from different threads. So I cant tell which one is from which thread.

Yeah, I don't think I can help you then.

Is it actually fully bricked yet? What exactly happen when you power on the device unplugged usb?

[Q] Likely hard bricked, is there any hope?

Hi all,
I have(had) a AT&T HTC One X (evita) that was running CM10.2.1, hboot 2.14, S-OFF, CID 11111111
My story: I wanted to update to CM11 so according to the CyanogenMod website (sorry can't post a link as a new user) I updated from my previous hboot 2.14 to 2.18 by updating to firmware 5.18.502.1, so far so good all went fine. Then I noticed that I should have at least TWRP 2.7.0.8 but I had 2.6.something so I went ahead and wanted to update the twrp recovery. That's were I made the stupid mistake. I went to the TWRP manager app, selected recovery update and by mistake (now as I'm tinking back about that) I selected HTC One X+ ATT i.e. the "evitareul" instead of "evita" and flashed that. Now the phone is dead, the screen is black, when put on charger the red LED doesn't come on, power+volume down doesn't do anything (no flashing, vibration, nothing). When I connect it to windows machine it recognizes some android device. Under linux, ADB doesn't see any device, though fastboot does, but instead of serial number there are just some non sense characters. I can run some bastboot commands like "fastboot oem readcid" and that works, but I can't flash (now correct) twrp recovery, all flash attempts end with FAILED (remote: not allowed). I tried applying RUU from windows but the phone can't boot into bootloader so it fails.
Please, is there any way I can fix this on my own? Or is it permanently bricked and I should start looking into getting a new phone :crying:
Many thanks for any advise!!

Does fastboot reboot bootloader do anything?

Hi, I tried to reboot to bootloader, the command was sent but the phone didn't do a thing, no visible reaction
Code:
$ sudo fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.113s]
finished. total time: 0.113s

You've borked your partition table. You can either have the motherboard replaced by HTC (~$200) or have a jtag repair done (~$50).

Thanks, I'll try to find somebody to get the jtag repair done.