Database Info

HTC Magic keeps rebooting, unlike other posts, PLEASE HELP, thanks in advance! :):)

Hello All,
I've tried my hardest to search all over the forums but I still can't figure this out. I'm highlighting all I've tried to eliminate all that junk.
I have a 32A magic and I tried updating the ROM via this post.
I actually installed the radio 6.35.08.29 a little bit lower on the post using recovery mode while it was on my SD.
My device is rooted via theunlockr.com's one click rooting.
I think this was the problem because I was supposed to install the radio 6.35.10.18 because as soon as it was finished installing and rebooting, it keeps rebooting and doesn't even get past the splash screen
Here's where the issues start making me want to pull my hair out.
The good news (from what I'm hearing) is that I can still boot into fastboot and HBoot modes, but I can't get to restore mode at all
I'm getting better with the sdk so I'm understanding fastboot etc now but the main problem I believe is that it won't recognize my device.
I am on windows 7, but yes I've installed the latest drivers and device manager is recognizing it but when I try in cmnd to type adb devices it shows "List of devices attached" and it's emtpy.
I try to type something like adb bugreport and it comes back "error: device not found"
So clearly it doesn't seem to be recognizing the device.
What I was trying to do what push another radio to the device or something but at this point I have no idea what I am to do, especially since I can't get to restore!! Grr!
Any ideas?

p.s.
I thought I'd mention that I think this may be because I didn't (and cannot) select USB debugging from the menu as I can't load the device...
May be bricked... Oh well lol

update
It's only going into fastboot mode when plugged in now.

kob123 said:
It's only going into fastboot mode when plugged in now.
Click to expand...
Click to collapse
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
make sure those files are in your tools folder

Thanks,
The files recovery-RA-hero-v1.5.2, Radio_HTC_PVT_32A_6.35.10.18, as well as hboot-1.76.2007 are all in the tools folder.
For fastboot flash radio:
I keep getting:
sending 'radio' ... okay
writing 'radio' ... INFOsignature checking...
FAILED (remote: signature verify fail)
Same thing happens for flashing hboot and recovery as well...
fastboot erase system -w
fastboot reboot-bootloader
both work fine.
Like I said, thanks HUGE so far, but still not working...

im also having the very same problem i cant even flash the sappimg or anything i dont even get the recovery
sapphier pvt 32b ship s-on h
hboot-1.33.0009 (sapp30000)
cpld-10
radio-3.22.20.17
thats all i get please help
ok i got it check it this is what i did i put the engineering-spl-hboot 1.33.2005on to sdcard and rename to update...
then turn on to recovery holding home n power...
then when the triangle picture pops up press home & end call buttons again just press it no need to hold....
once done updating place sappimg.zip on to sdcard...
power on to hboot ...
phonewill load zip file.....
let it do its thing again after done reboot and you got it!!!!!!
i had a card adapter sou will need on let me know if it helped you out....also i formatted my sdcard before i started because phone had problems mounting card when in recovery

http://forum.xda-developers.com/showthread.php?t=530527
download the update.zip
fastboot boot recovery-RA-sapphire-v1.5.2.img
(make sure you use sapphire unless you have the hero radio and spl installed otherwise the hero recovery is needed if you have the cursorsense radio which effectivly makes the magic a hero)
apply the update.zip
then you should be able to fastboot the prev instructions

just fyi make sure u check your radio on the fastboot screen before using the hero or sapphire recovery - make sure you use the proper one!

update
Hey all my problem was also with the spl as well for some reason. I also loaded the newest rogers update instead which the combination did the trick...

kob123 said:
Hey all my problem was also with the spl as well for some reason. I also loaded the newest rogers update instead which the combination did the trick...
Click to expand...
Click to collapse
yeaaa the spl is what my above tricck woulda fixed but if you loaded the latest rogers update you got no root access for now which kinda sucks

[Q] Can someone help me with this boot loop?

Good day ...
im having a problem with my desire s, i bought it 2 days ago with the same problem when i bought it, its already with the problem when i bought it..
it is priced low so i bought it from a guy being tempted thinking i could fix it or its just a software problem, but unfortunately i got no luck fixing it,
i can get it to bootloader (power+volume down) but i cant seem to enter the recovery from the menu and it is not charging. Tried flashing new recovery but still no luck tried installing RUU but i get an error 155 rom update utility cannot update your android phone.... The weird thing is when i try to charge the phone on wall, it enters CWM and i tried to format cache, do factory reset but theres an error unable to mount sd something like that... And my phone cant be detected using adb cause i think usb debugging is not enabled before it got bootloop, but with fastboot it can be detected...
Here is the detail of my phone:
UNLOCKED
SAGA PVT SHIP S-ON RL
HBOOT-2.00.002
RADIO-3822.10.08.04_M
eMMC-Boot
Aug 22 2011, 15:22:13
more details
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.405.6
(bootloader) serialno: SH14PTJ06464
(bootloader) imei: ******************
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3634mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Can someone tell me what RUU should i use..
THANKS IN ADVANCE GUYS :crying:

To run RUU you need to relock your bootloader.
Google and INDEX thread can tell you everything else.
(well, they could have saved me this post too, if you'd run a simple search for "error 155").

Jack_R1 said:
To run RUU you need to relock your bootloader.
Google and INDEX thread can tell you everything else.
(well, they could have saved me this post too, if you'd run a simple search for "error 155").
Click to expand...
Click to collapse
i have manage to install the ICS RUU, but sad to say still having a boot loop and still unable to go to recovery...
now i think the problem is with fired emmc chip? i hope its not :crying:
i cant seem to follow this guide http://forum.xda-developers.com/showthread.php?t=1284196 due to not able to detect my phone in adb commands.. is there a way for my phone to be detected in adb?? whenever i typed in adb shell i get an error:device not found
another noob question and im sorry for it, if i have a fried emmc chip, will i still be able to boot it in bootloader???

Patutz said:
but theres an error unable to mount sd something like that...
Click to expand...
Click to collapse
Sure you already tried another SD Card!?

Jericoacoara said:
Sure you already tried another SD Card!?
Click to expand...
Click to collapse
i dont think it pertains to the external sd, i think its on internal... well can u tell me how can my computer detect my device via adb??.. im thinking about the fried emmc.. but cant seem to know if its with the emmc issue since my device cant be detected via adb...

Patutz said:
i dont think it pertains to the external sd, i think its on internal... well can u tell me how can my computer detect my device via adb??.. im thinking about the fried emmc.. but cant seem to know if its with the emmc issue since my device cant be detected via adb...
Click to expand...
Click to collapse
If you are stuck into boot loop you can follow this guide http://forum.xda-developers.com/showpost.php?p=21569470&postcount=957 to get logcat information...

TheLegendGZ said:
If you are stuck into boot loop you can follow this guide http://forum.xda-developers.com/showpost.php?p=21569470&postcount=957 to get logcat information...
Click to expand...
Click to collapse
the problem is whenever i type adb devices i get an error no device =(

Patutz said:
the problem is whenever i type adb devices i get an error no device =(
Click to expand...
Click to collapse
First you made a mistake to flash the ICS RUU, because you could have easily check the eMMC from CWM via adb. Now you cannot.
At your current state you can go into the Recovery by choosing it from the bootloader menu, pressing Volume UP + Power when you see a black screen with an exclamation mark. But there is nothing you can do there...
And finally - since your RUU flash was successful and you still cannot boot to the OS the conclusion is obvious - you have wasted your money. Sorry about that

amidabuddha said:
First you made a mistake to flash the ICS RUU, because you could have easily check the eMMC from CWM via adb. Now you cannot.
At your current state you can go into the Recovery by choosing it from the bootloader menu, pressing Volume UP + Power when you see a black screen with an exclamation mark. But there is nothing you can do there...
And finally - since your RUU flash was successful and you still cannot boot to the OS the conclusion is obvious - you have wasted your money. Sorry about that
Click to expand...
Click to collapse
i cant enter recovery from the very beginning, i tried volume up + power but i cant see a black screen with exclamation mark..cant i flash gingerbread RUU anymore to downgrade it?
so i do have fried eMMc? :crying:

You might not have ADB drivers properly installed. If you managed to install RUU, it means your USB port is working and eMMC is likely functional.
Enter the bootloader (Power+VolDown).
Select "RECOVERY" by VolDown/VolUp and press Power.
This should get you to recovery.

Jack_R1 said:
You might not have ADB drivers properly installed. If you managed to install RUU, it means your USB port is working and eMMC is likely functional.
Enter the bootloader (Power+VolDown).
Select "RECOVERY" by VolDown/VolUp and press Power.
This should get you to recovery.
Click to expand...
Click to collapse
i cant enter recovery i tried power+voldown then i select RECOVERY.
but it just go to HTC logo colored green and white background, then after that it shut off, it doesnt go to recovery...and regarding the adb, i try in cmd to type adb then i get all the menu of adb, so i think the adb is installed properly?? by the way, are adb drivers the one included on this link? http://forum.xda-developers.com/showthread.php?t=1272595 i just put the extracted zip file on C drive and i didnt do "setx path /m "%PATH%;C:\android-tools" this command i just type in cmd cd C:\android-tools am i doin it wrong?

Patutz said:
i cant enter recovery i tried power+voldown then i select RECOVERY.
but it just go to HTC logo colored green and white background, then after that it shut off, it doesnt go to recovery...and regarding the adb, i try in cmd to type adb then i get all the menu of adb, so i think the adb is installed properly?? by the way, are adb drivers the one included on this link? http://forum.xda-developers.com/showthread.php?t=1272595 i just put the extracted zip file on C drive and i didnt do "setx path /m "%PATH%;C:\android-tools" this command i just type in cmd cd C:\android-tools am i doin it wrong?
Click to expand...
Click to collapse
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.

amidabuddha said:
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.
Click to expand...
Click to collapse
i tried installing the 4ext recovery and i flashed it ok but still cant get to recovery...i cant access adb since it wont be detected by the computer and i cant s-off my phone since i need to adb push...
yeah im sure that it went smooth, no errors at all, after the installation on RUU its says congratulation upgrade complete you can now use your device something like that haha not sure whats the exact words used there haha wait im goin to RUU again just to be sure that theres no error :fingers-crossed:
Here's the exact thing written on RUU... Congratulations! Your ROM update has been completed. Your Android phone is now ready for use..
hmm do you think even with that notice i can still get error during the update??? and by the way is it normal around 17% during the RUU installation after the "updating radio" around 17% it reboots then on the RUU it says waiting for device, is it normal?

amidabuddha said:
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.
Click to expand...
Click to collapse
i have a great news for me hehe i hope so, i made some new findings on my device,
1st of all i made it to the recovery but the wierd thing is i can only go to recovery when i plugged my phone on the computer, now adb can detect my phone
2nd by following this guide http://forum.xda-developers.com/showthread.php?t=1284196&nocache=1 for the checking of Fried eMMc, i was able to get this result:
<3>[ 7.996978] mmc0: No card detect facilities available
<6>[ 7.997589] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.997741] mmc0: Platform slot type: MMC
<6>[ 7.997985] mmc0: 4 bit data mode disabled
<6>[ 7.998107] mmc0: 8 bit data mode enabled
<6>[ 7.998260] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.998504] mmc0: Slot eject status = 0
<6>[ 7.998626] mmc0: Power save feature enable = 1
<6>[ 7.998870] mmc0: DM non-cached buffer at ff817000, dma_addr 0x29be3000
<6>[ 7.998992] mmc0: DM cmd busaddr 0x29be3000, cmdptr busaddr 0x29be3300
<6>[ 8.151794] mmc0: new high speed MMC card at address 0001
<6>[ 8.152832] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
from the result up there i dont think i got a fried emmc? or maybe i maybe wrong? please enlighten me guys i think its a good find? maybe again im wrong? so what do you think is the problem here that my htc got boot looped??

Patutz said:
i
from the result up there i dont think i got a fried emmc? or maybe i maybe wrong? please enlighten me guys i think its a good find? maybe again im wrong? so what do you think is the problem here that my htc got boot looped??
Click to expand...
Click to collapse
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?

Charge/change your battery, see if anything changes.
amidabuddha said:
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?
Click to expand...
Click to collapse
His RUU flash obviously didn't work. Not even sure what he's flashing.

amidabuddha said:
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?
Click to expand...
Click to collapse
i flashed this one http://forum.xda-developers.com/showthread.php?t=1484753 thats how i get the recovery , sorry for the explanations im just being excited hoping id still get a chance to fix this phone
Jack_R1 said:
Charge/change your battery, see if anything changes.
His RUU flash obviously didn't work. Not even sure what he's flashing.
Click to expand...
Click to collapse
im flashing this RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed got it from htcdev... ican i downgrade to gingerbread? can u tell me which RUU should i use?

I'm not as knowledgeable as people helping you here, but if it was me is start from scratch and i mean from scratch. Fresh install of everything, drivers etc. I'd then flash a custom rom and seeing as your not s-off. Flash the kernel. Then if its ok is maybe try a fresh download of the ruu and run that.
"Do, or do not. There is no 'try'."
- Yoda

Patutz said:
im flashing this RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed got it from htcdev... ican i downgrade to gingerbread? can u tell me which RUU should i use?
Click to expand...
Click to collapse
You can downgrade, but not by a simple RUU flash.
RUU flash doesn't work when bootloader is unlocked.
I'm tired. Read instead of asking.

jugg1es said:
I'm not as knowledgeable as people helping you here, but if it was me is start from scratch and i mean from scratch. Fresh install of everything, drivers etc. I'd then flash a custom rom and seeing as your not s-off. Flash the kernel. Then if its ok is maybe try a fresh download of the ruu and run that.
"Do, or do not. There is no 'try'."
- Yoda
Click to expand...
Click to collapse
can i use any ics kernel??... the bad news is that not whenever i try the same method yesterday when i can enter recovery by putting my phone on pc, now it just loop on recovery when i plugged it in computer, it just enter recovery then shut it self then enter recovery again..
Jack_R1 said:
You can downgrade, but not by a simple RUU flash.
RUU flash doesn't work when bootloader is unlocked.
I'm tired. Read instead of asking.
Click to expand...
Click to collapse
i relocked my bootloader whenever i flash RUU but i get error that its not the right RUU, the only one that i got success in flashing RUU was the one iposted abaove... thats why im asking you guys if you know any compatible RUU for my device cause ive tried alot and still get incompatability

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.

[Q] HTC ONE S no rom no adb no sd card

Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.

dominolapin said:
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4

Flashalot said:
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !

dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed

dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed

dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
"STOCK" recovery. I think you have tried with CUSTOM recovery.
Here is the link for stock recovery. The second download link is the stock recovery image
Flash stock recovery, then relock boot loader and then follow the above procedure :good:

Actually I did flash the stock recovery I just typed custom by mistake. Sorry about that. The one I flashed even came from the same link .

I searched on the forums and I might not have flashed the right ruu.
But i can't seam to find the right one, because strangely "fastboot getvar version-main" gives a blank result.
Hboot 1.14.0002
radio 1.08es.50.02.16
CID HTC_247

[Q] HTC One S Bootloop; S-On - Can't flash RUU recovery.img

Phone Details
HTC One S TMobile
****Tampered****
****Unlocked*****
VLE PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Cidnum: T-MOB010
My phone sustained water damage (unfortunate accident of a leaking wall aircondition unit while on vacation). Anyways- once things dried out- everything turns on and seems to work, but I'm stuck in a boot loop. It bootloops through the cyanogenmod loading screen then over again. I can still get to bootloader and TWRP 2.5.0.0.
I have tried the following.
-reinstall the CM10 ROM from TWRP and flash the boot.img in fastboot but same bootloop occurs.
-re-lock the bootloader to use a RUU.exe but everytime I use the 'fastboot oem lock' command the screen turns off. When I reboot into bootloader, I'm still unlocked. I've copied the command window below-
.5\data>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.946s
-ADB Sideload a new ROM- but in TWRP the drivers fail to install and my computer doesn't recognize any devices for adb commands. I've tried re-flashing TWRP and the drivers using Hasoon's Toolkit in hopes that it would
-I have also looked for a way to get my phone S-off since I think that is one of the problems preventing these other steps. But I can't seem to find any steps for that.
Anyways, hopefully I was at least on the right track with one of those steps. I am definitely a noob- but I've tried looking through forums and tutorials and videos for hours. I'm hoping someone can give me a good step by step solution to try. Thanks in advance for any help.

Let's Tackle This..
Alright, First step. Let's get the drivers.
(If you have HTC Sync on your PC, remove it now)
Install this for the drivers on your PC
Restart both your PC and phone, and if you dont have adb (Or want to use the newest one)
Install this for the minimal adb and fastboot program. It's a lot more convenient then seperate files.
Tell me if you're able to do ADB commands after this .

Mozziliac said:
Alright, First step. Let's get the drivers.
(If you have HTC Sync on your PC, remove it now)
Install this for the drivers on your PC
Restart both your PC and phone, and if you dont have adb (Or want to use the newest one)
Install this for the minimal adb and fastboot program. It's a lot more convenient then seperate files.
Tell me if you're able to do ADB commands after this .
Click to expand...
Click to collapse
I'm not as familiar with ADB commands in general. But I did what you said and tried "adb devices" in TWRP, TWRP while adb sideload scrip was trying to run on my phone, in hboot, and in fastboot and none of them seemed to work. Fastboot commands still work in fastboot mode. I sort of predicted that when the device drivers failed to load again when I entered recovery mode.

drpaul85 said:
I'm not as familiar with ADB commands in general. But I did what you said and tried "adb devices" in TWRP, TWRP while adb sideload scrip was trying to run on my phone, in hboot, and in fastboot and none of them seemed to work. Fastboot commands still work in fastboot mode. I sort of predicted that when the device drivers failed to load again when I entered recovery mode.
Click to expand...
Click to collapse
Looks like your on a old enough firmware for you to mount your SD in recovery so just download stock ROM and flash it
Also you got the error from not flashing stock recovery

ville
why my one s usually have some reboot????????
---------- Post added at 07:06 PM ---------- Previous post was at 06:27 PM ----------
why my one s usually have some reboot????????