Database Info

[Q] Help with Boot/Recovery Problems?

Hello, I have a T-Mobile HTC Sensation 4G, and I've ran into some problems recently. I'm a basic-intermediate user when it comes to Android, but I can't find a solution specifically for this. It started with a small problem but got worse and worse until I couldn't even boot correctly.
I started out installing a small custom battery mod, but that led to a few problems with the notification bar (not a big deal).
Then I tried to revert to the stock battery to fix the problem, format cache and dalvik cache in recovery, and reset. Then I was put into an infinite boot loop with the HTC splash, but going into cwm recovery was still possible.
Then, in recovery, I could not access my sd card for some reason, so I shut off, reinserted the sd card, and remounted it, then I reset again.
Now, it's impossible to boot to android at all, and I am completely stuck at HBOOT/FASTBOOT, and cannot access recovery OR perform a hard reset.
If I try to reinstall cwm recovery, I get a partition update fail as well...
I have full root, s-off, etc.
ROM- InsertCoin 3.3.1
Kernel- Stock
Hboot- 1.17.1011
Clockwork version- 5.0.0.8
Any suggestions? Am I bricked? I can give more details if needed.

I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium

neoissuperman said:
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Alright, thanks, I'll try that soon and see if it works.
Update: Unfortunately, I don't think I can flash anything, it just comes up with a partition update fail...

Anyone else know what I could try? I also tried to flash the 1.45 RUU, but it can't continue past the search for the bootloader.

If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device

joshndroid said:
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
Click to expand...
Click to collapse
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...

have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas

joshndroid said:
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
Click to expand...
Click to collapse
Nope, still nothing, I even tried different sd cards and usb cables, with no difference...
So has my phone been reduced to a paperweight?

APmoss13 said:
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
Click to expand...
Click to collapse
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.

Divine flaw said:
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Click to expand...
Click to collapse
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.

APmoss13 said:
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
Click to expand...
Click to collapse
ok.... i was just askin cause did the exact same thing (well almost, i tried to change the notification icons which resulted in my notification bar completely gone) you did and got into that infinite boot loop. and couldnt boot into android. and couldnt figure it out. the only thing i did was just install the ruu while i was in the fastboot screen and it worked. i wasnt aware that there was a 1.45 ruu for tmous but i dont think that should matter since you are scid anyways. now im just wonderin if you tried any other ruu's besides that one. for me i flashed the 1.29 ruu for tmous and that got me up and running...... sorry i couldnt help

[Q] HTC sensation Boot loader stuck

Hi
I update my phone to ICS by RUU and I couldn't open it. The boot animation is stuck in the green HTC logo. "Quietly brilliant" doesn't even come on.
So i tried to flash the RUU again but it said Error 155. So i tried to superwipe. But when I go into the bootloader and into Recovery, the screen just flashed and went black. And showed the phone icon with a red cross. Seems like I can't get into recovery to install zip from card.
My bootloader says -
UNLOCKED
PYRAMID PVT SHIP S-0N RL
HBOOT - 1.27.0000
eMMC - BOOT
Jan 13 2012, 17:33:34
Please help me.

Since you are using RUU I wonder it will been fine even you are on custom ROM.
I guest maybe you are using wrong version of RUU make sure you are using the right ROM.
If would you like to try you may would like to revert back the Recovery if your are using custom recovery with this guide [GUIDE] Get Stock Recovery/Install OTA Updates without losing data.

zarhayda said:
Hi
I update my phone to ICS by RUU and I couldn't open it. The boot animation is stuck in the green HTC logo. "Quietly brilliant" doesn't even come on.
So i tried to flash the RUU again but it said Error 155. So i tried to superwipe. But when I go into the bootloader and into Recovery, the screen just flashed and went black. And showed the phone icon with a red cross. Seems like I can't get into recovery to install zip from card.
My bootloader says -
UNLOCKED
PYRAMID PVT SHIP S-0N RL
HBOOT - 1.27.0000
eMMC - BOOT
Jan 13 2012, 17:33:34
Please help me.
Click to expand...
Click to collapse
the error you have represents connection issues
you need to run the RUU from fastboot mode in device (your device should read "fastboot usb")
Also you got stuck after running RUU ?? weird ...did the RUU ran first time completely ?
Also for safe RUN ...relock the boot loader and run the RUU...by keeping the phone in fastboot mode (device reads "fastboot usb")

Ok. So I relock my bootloader and I tried to install it. It said Error 140 - Bootloader version error. It's in fastboot USB mode. The installer get up to the Updating signature stage but then it gave error. I have SUPERcid. help?

zarhayda said:
Ok. So I relock my bootloader and I tried to install it. It said Error 140 - Bootloader version error. It's in fastboot USB mode. The installer get up to the Updating signature stage but then it gave error. I have SUPERcid. help?
Click to expand...
Click to collapse
as you are S-ON currently ..you cant run RUU having lower bootloader versions....(thats why you are getting bootloader errors)
right now you can only run ICS RUU's...
as you are superCID you can get any ICS RUU..
to RUN the RUU
1.make sure your bootloader is locked/relocked
2.keep the device in fastboot usb (i.e. connect it to pc when in fastboot )
3.run the RUU from PC
(only if RUU runs completely and gives you congats message --then only RUU is successful)
if you got any errors even after doing this...please post the error in this thread

ganeshp said:
as you are S-ON currently ..you cant run RUU having lower bootloader versions....(thats why you are getting bootloader errors)
right now you can only run ICS RUU's...
as you are superCID you can get any ICS RUU..
to RUN the RUU
1.make sure your bootloader is locked/relocked
2.keep the device in fastboot usb (i.e. connect it to pc when in fastboot )
3.run the RUU from PC
(only if RUU runs completely and gives you congats message --then only RUU is successful)
if you got any errors even after doing this...please post the error in this thread
Click to expand...
Click to collapse
Hi there.
I have the exact same problem as the original poster! (Coincidentally the same info in the bootloader too!) I'm trying run a RUU which I downloaded and have had an
'ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
The error may be because my bootloader is unlocked? But when I try to re-lock it it shows the "security warning" below "re-locked"
and then the RUU gives me ERROR [140]: BOOTLOADER VERSION ERROR
The RUU I'm trying to use is called RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198358_signed
Please help! I've been trying to Install MIUI all day and it is turning into a nightmare.. I don't want to lose this phone D:

Shunun said:
Hi there.
I have the exact same problem as the original poster! (Coincidentally the same info in the bootloader too!) I'm trying run a RUU which I downloaded and have had an
'ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
The error may be because my bootloader is unlocked? But when I try to re-lock it it shows the "security warning" below "re-locked"
and then the RUU gives me ERROR [140]: BOOTLOADER VERSION ERROR
The RUU I'm trying to use is called RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198358_signed
Please help! I've been trying to Install MIUI all day and it is turning into a nightmare.. I don't want to lose this phone D:
Click to expand...
Click to collapse
I just got my phone back. Flash clockwordmod or 4ext from adb. And then use it to wipe everything in your phone. And then flash a ROM.zip and it will work like charm

zarhayda said:
I just got my phone back. Flash clockwordmod or 4ext from adb. And then use it to wipe everything in your phone. And then flash a ROM.zip and it will work like charm
Click to expand...
Click to collapse
Do i need to rename into PG58IMG.zip ? thnx for your help.

[Q] bricked evo design (kingdom)

well i recently came across a evo design (codename: kingdom), or hero-s as its called in other markets.
long story short, i flashed it to a local carrier revol (similar to metro/cricket).
and during that process i foolishly flashed some non-vol items to it and it is now bricked.
it only boots to the white htc splash and restarts in a loop
i can only access hboot and fastboot. i cant even get into recovery.
the only good things i have going for me are that i have my Unlock_code.bin so i can unlock/relock my bootloader (no s-off on this device)
and that i got a copy of my non-vol items from CDMA Workshop from before i borked it, and a copy of what broke it (from whiterabbit.org)
...im just not sure if thats enough
sucks cause it would be an easy fix if i could just use adb :/
any help is appreciated...tia
-d

a little more info on what ive tried so far
ive installed new recoveries, cwm and twrp, via fastboot PH44IMG.zip...they install fine but will not boot into the recovery.
ive installed the same recoveries via fastboot usb and RUU (flashboot flash recovery recovery.img)...they install fine but will not boot into the recovery.
ive tried the 'downgrade ruu' (RUU_Kingdom_S_Sprint_WWE_2.12.651.5_Radio_1.11.00.1228_NV_SPCS_2.97_removeCIQ_release_234636_signed.exe)...it flashes fine but still a boot loop (phone was 2.12.651.8 originally i believe).
ive tried ics ruu's but all ive found are for boost so i get a cid error...when i changed the cid to sprint i got another error that i cant recall.
i got my hands on sprints newest OTA update (OTA_Kingdom_ICS_35_S_Sprint_WWE_3.14.651.0-2.12.651.8_release_27047061zjyiwl2kn4vskn.zip)....but its a 'scripted update' so it will not install via hboot or fastboot.
i extracted the above OTA update, and retrieved the firmware.zip (contains boot, hboot, radio and recovery) and installed that fine...but no recovery still even after cwm/twrp reinstall.
even though my phone is unlocked its still s-on, so the only things i can manage to install manually with "Fastboot flash" are signed binaries (boot_signed.img and recovery_signed.img) anything else i get "FAILED (remote: 12 signature verify fail)"
anyone know if i can flash the rest of the update without error?
i still have dzdata.img, splash1.nb0,NV_MFG_eMMC_SPCS_2.97_1206_PRL51082.nb, ramdisk.img, rcdata_2.97.img and tp_atmel224_20aa.img maybe one of those will overwrite the spot i fudged up...idk

[Q] HTC One X unable to mount /data, can't RUU

So...i purchased a HOX on Sunday and it was all working fine on straight talk not long after i got home with it. I was sick of the bloatware so i went to load a custom ROM (i've rooted/rom'd the Fascinate and RAZR before, i'm not totally clueless) and made the awful mistake of flashing an endeavoru ROM on my evita phone (at&t) along with an incorrect recovery. I didn't realize my mistake at the time and wiped cache/dalvik/factoryreset/ and system to try and install a different ROM. After failing to load that i tried other ROMs and somehow my sd card became corrupted. I tried to read many many threads (worked around 7 hours on this) to fix the sd card issue including:
http://forum.xda-developers.com/showthread.php?t=2092721
http://forum.xda-developers.com/showthread.php?t=1936198
http://forum.xda-developers.com/showthread.php?t=1942519
http://forum.xda-developers.com/showthread.php?t=1630459 post #8
I have tried to relock the bootloader, cmd shows:
C:\fastboot>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.940s
After doing that however it still says RELOCKED in fastboot, although under that is has Security Warning so apparently it still worked. Then i tried running "htc_one_x_RUU_2.20.502.7_att_us_08022012", Version is 1.0.6.2012 on the 'HTC Android Phone ROM Update Utility', it says my current image version is 2.20.502.7. After hitting 'Update' on that it says it will update to image version: http://i.imgur.com/IwD2nIQ.png. The program runs into ERROR [132]: SIGNATURE ERROR which i also can't seem to fix (it says to get the correct ROM Update Utility and try again but i'm pretty sure i have the correct one..). Here is the fastboot version and CID along with a failed recovery: http://i.imgur.com/wmg93YT.png
Once i realized my first mistake i put the correct recovery back on my phone. I even tried to sideload a rom onto the phone but it got stuck in CMD on 6% nearly instantly. I also have formatted the sd storage at least 3 times in windows.
So the current situation is:
- No OS installed. Phone gets stuck at HTC screen with red writing upon normal boot.
- Bootloader is accessible.
- TWRP 2.3.3.0 is installed and accessible through recovery.
- Can't install any ROM because the unable to mount /data error. When wiping dalvik i also get "E:Unable to mount 'cache' "
- Tried to format at least 3 times, no error in windows from formatting; sd card has no files on it in windows currently
- I've tried to push the TWRP recovery onto the device again, it works but nothing is fixed.
- Using Windows 7 64bit, HTC One X AIO Kit v2.0,fastboot tool
- Phone can be unlocked/relocked, however with an error in cmd (see above).
- Every program has been run 'as administrator', no change in result.
- Phone is recognized as 'My HTC' under 'Android USB Devices' in windows, so drivers should be correctly installed (not that i haven't tried uninstalling those twice already..)
Bootloader info:
*** TAMPERED ***
*** UNLOCKED ***
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
Any help is greatly appreciated. Hopefully i've not made any noob mistakes (nice registration video btw..) since i have searched already for this problem, although it is most likely something i missed.
**Update**
Ran through the Nocturnal guide for corrupted sd card and it seems to have worked. Was able to install the cm10 nightly ROM but it failed from a symlink error. Installed evita Avatar ROM instead and it has been booting up for the last 4 minutes, will update on whether or not that works.

http://dl3.htc.com/application/htc_o...s_08022012.exe download this ruu, if it doesnt load then the download link is in post 9 of the second link below,i think you are using the wrong ruu. You have to have the same ruu for the phone version...2.20 ruu for 2.20 firmware.
http://forum.xda-developers.com/showthread.php?t=1956258&page=2
if that doesnt work read through that thread, i had the same problem as you when i first started, your phone is fine...as long as you can get into bootloader and recovery, your phone is ok..
Relock your phone again by the way (fastboot oem lock) from fastboot, if it says relocked..then it is locked again. run the ruu in fastboot as well, if that does not work try running the ruu in bootloader.
Ruu should work if you do it right...If it doesnt work.
Alternative, wipe your phone data,cache, dalvik and THEN flash boot img of a rom and LASTLY install a rom,

WhatTheAndroid? said:
http://dl3.htc.com/application/htc_o...s_08022012.exe download this ruu, if it doesnt load then the download link is in post 9 of the second link below,i think you are using the wrong ruu. You have to have the same ruu for the phone version...2.20 ruu for 2.20 firmware.
http://forum.xda-developers.com/showthread.php?t=1956258&page=2
if that doesnt work read through that thread, i had the same problem as you when i first started, your phone is fine...as long as you can get into bootloader and recovery, your phone is ok..
Relock your phone again by the way (fastboot oem lock) from fastboot, if it says relocked..then it is locked again. run the ruu in fastboot as well, if that does not work try running the ruu in bootloader.
Click to expand...
Click to collapse
OK thanks. The RUU you linked is giving me a 404 error. I've got Avatar working on it now but....sorry to the developer...its hideous, so i need to find another .

spectrum8 said:
OK thanks. The RUU you linked is giving me a 404 error. I've got Avatar working on it now but....sorry to the developer...its hideous, so i need to find another .
Click to expand...
Click to collapse
What is the Nocturnal guide for corrupted sd card ?

[Q] [Help] My HTC One S not booting on after rooting

Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak

deepak_raja20 said:
Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak
Click to expand...
Click to collapse
Well i got S-OFF with Rumrummer but i got it till my 7th try. you should keep trying with it

Stuck in sending recovery/sending zip flash
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak

deepak_raja20 said:
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak
Click to expand...
Click to collapse
I suggest you get the OTG USB cable. Load the ROM on a Flash USB and then use TWRP to install the ROM (Remember to mount the OTG in TWRP) Check Amazon, it only cost less than $3. I've never push the ROM to the phone. Saves a lot of time when you have multiple phones.