Database Info

[Q] Finally i bricked my HTC SENSATION !!!!

hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: (removed by me because it's not important)
(bootloader) imei: (removed by me because it's not important)
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s

specter16 said:
hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s
Click to expand...
Click to collapse
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC

DennisBold said:
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC
Click to expand...
Click to collapse
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting

specter16 said:
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting
Click to expand...
Click to collapse
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC

DennisBold said:
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC
Click to expand...
Click to collapse
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working

specter16 said:
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working
Click to expand...
Click to collapse
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC

DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
okay i'll try
please stay connected, i really need you

specter16 said:
okay i'll try
please stay connected, i really need you
Click to expand...
Click to collapse
Sure. If the fastboot commands work I've got something you can try.
Sent from my HTC

DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s

specter16 said:
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC

DennisBold said:
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC
Click to expand...
Click to collapse
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s

specter16 said:
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC

DennisBold said:
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC
Click to expand...
Click to collapse
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green

specter16 said:
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green
Click to expand...
Click to collapse
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC

DennisBold said:
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC
Click to expand...
Click to collapse
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot

specter16 said:
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot
Click to expand...
Click to collapse
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC

DennisBold said:
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC
Click to expand...
Click to collapse
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s

specter16 said:
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s
Click to expand...
Click to collapse
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC

Fail-PU errors generally correspond to firmware corruption
Which is pretty hard to solve
If Op can exactly tell flashing what caused this issue
Maybe we can have a chance
Btw can the phone go to recovery?
Also how did the patched hboot flash went?
Sent from my HTC Sensation 4G using xda premium

DennisBold said:
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC
Click to expand...
Click to collapse
- Fail-PU next to the bootloader line
i found this command
Code:
fastboot oem writesecureflag 3
i think this will return me back to s-on
but can i s-off my phone from hboot ??? if i want
or it's useless this command for me ?

(SOLVED).......S-OFF_HTC one XL Driver

Hi guys....I'm just wondering if you guys know where I can find good htc one xl driver.....seem like my laptop sometime recognized the usb connection and automatic install the driver and sometime not......especially when I tried to do S-OFF.....right before entering 3 soffbin3 command after Android boot to OS......I always got error device not found after......usb debugging is checked before and unchecked after boot to Android OS.....and I read somewhere on thread that Android 4.2.2 for security purpose htc uncheck USB debugging after boot .....and then I went back to Android 4.0.3 sense 4 and same result....and I'm thinking is the driver might not installed properly......so any link and idea would appreciated......btw using window 7
C:\Android\android-sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android\android-sdk\platform-tools>fastoot oem readcid
'fastoot' is not recognized as an internal or external command,
operable program or batch file.
C:\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.064s]
finished. total time: 0.065s
C:\Android\android-sdk\platform-tools>fastboot flash zip PJ8312000-OneX.zip
sending 'zip' (36064 KB)...
OKAY [ 2.744s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.841s
C:\Android\android-sdk\platform-tools>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F6C9C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x940047
(bootloader) TAG:engineerid = 0x1
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT24DWXXXXXX
(bootloader) command line length =688
(bootloader) active commandline: poweron_status=32 reset_status=0 board_e
(bootloader) lite.disable_uart3=0 diag.enabled=0 board_elite.debug_uart=0
(bootloader) userdata_sel=0 androidboot.emmc=true androidboot.pagesize=2
(bootloader) 048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.sf=1 t
(bootloader) d.ofs=328 td.prd=1 td.dly=0 td.tmo=300 imc_online_log=0 and
(bootloader) roidboot.efuse_info=FFSL androidboot.baseband=0.18c.32.09.01
(bootloader) androidboot.cid=11111111 androidboot.devicerev=3 androidboo
(bootloader) t.batt_poweron=good_battery androidboot.carrier=ALL androidb
(bootloader) oot.mid=PJ8310000 androidboot.keycaps=qwerty androidboot.dq=
(bootloader) FAIL androidboot.mode=normal androidboot.serialno=HTXXXXXX
(bootloader) 93 androidboot.bootloader=1.09.0000 androidboot.nledhw=0 zyg
(bootloader) ote_oneshot=off kmemleak=off rpm_debug.enable=0
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=radio
(bootloader) aARM_Partion[C].name=adsp
(bootloader) aARM_Partion[D].name=dsps
(bootloader) aARM_Partion[E].name=wcnss
(bootloader) aARM_Partion[F].name=radio_config
(bootloader) aARM_Partion[10].name=modem_st1
(bootloader) aARM_Partion[11].name=modem_st2
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90006000 (phy 90006000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:11377 msec
FAILED (status read failed (Too many links))
finished. total time: 6.387s
C:\Android\android-sdk\platform-tools>adb push soffbin3 /data/local/tmp/
error: device not found
C:\Android\android-sdk\platform-tools>adb push soffbin3 /data/local/tmp/
error: device not found
Swyped From BlueICESense_JBE

The best way to get the latest drivers is to download the latest HTC Sync Manager from the HTC One XL page at HTC.com
Sent from my Evita

timmaaa said:
The best way to get the latest drivers is to download the latest HTC Sync Manager from the HTC One XL page at HTC.com
Sent from my Evita
Click to expand...
Click to collapse
I did that....And updated my htc driver installer from version 3 to version 4 or something.....do I need to keep htc sync manager or uninstall it after that?
Swyped From BlueICESense_JBE

Uninstall Sync Manger but leave drivers installed.
Sent from my Evita

timmaaa said:
Uninstall Sync Manger but leave drivers installed.
Sent from my Evita
Click to expand...
Click to collapse
I did that......same result.....error device not found......I just dunno what else to do.........btw.....I'm fine without S-OFF for now.... since I'm still on older hboot 1.09 and don't have reboot, wifi or signal what so ever on Android 4.2.2 sense 5 base ROM...... but would be awesome with S-OFF to complete mod.......
Swyped From BlueICESense_JBE

Use a different computer
Sent from my VENOMized HoxL

area51avenger said:
Use a different computer
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Did that too....using my wife laptop...my son laptop.....
Swyped From BlueICESense_JBE

Maybe it's a case of needing to download the latest Android SDK to ensure your adb is fully up to date. Or it could be as simple as using the rear usb port on your pc as opposed to the front usb port (may sound silly but it's worked for many people).
Sent from my Evita

timmaaa said:
Maybe it's a case of needing to download the latest Android SDK to ensure your adb is fully up to date. Or it could be as simple as using the rear usb port on your pc as opposed to the front usb port (may sound silly but it's worked for many people).
Sent from my Evita
Click to expand...
Click to collapse
Felt like something easy fix......like u said but I just dunno what else to do and I don't have PC......and i tried all four usb port from my laptop.....might have to use my brother PC but I dunno if he have all the Android sdk tool etc.....but I will try to update adb version via sdk manager tonight......:thumbup: Do you think twrp 2.6.3.0 have to do with it? But it work just fine for me flashing ROM, restoring back up...back and forth sense 4 and sense 5 Rom.....
Swyped From BlueICESense_JBE

I don't think the version of TWRP you're running matters, it doesn't come into the s-off process at all.
Sent from my Evita

timmaaa said:
I don't think the version of TWRP you're running matters, it doesn't come into the s-off process at all.
Sent from my Evita
Click to expand...
Click to collapse
Seem to me like.....somewhere inside there a script that somehow killed USB debugging .....after reboot
Swyped From BlueICESense_JBE

You need to check usb debugging in developer settings after the phone boots as I've instructed before, are you doing that?
Sent from my Evita

timmaaa said:
You need to check usb debugging in developer settings after the phone boots as I've instructed before, are you doing that?
Sent from my Evita
Click to expand...
Click to collapse
Yes and keep unchecked everytime after I got failed 92.....before pushing soffbin3 command.....and I did check it again and everytime.....that's y make me think somehow or sometime during booting to Android after failed 92 .....there is a script or command in my phone to uncheck USB debugging......but I doubt it ......just some thought
Swyped From BlueICESense_JBE

I don't that's the case, even if it did disable it on boot you can enable it once the phone boots.
Sent from my Evita

timmaaa said:
I don't that's the case, even if it did disable it on boot you can enable it once the phone boots.
Sent from my Evita
Click to expand...
Click to collapse
I did check it again after booted up.....and then when i enter first command adb push soffbin3 /data/local/tmp/ ........it said error....device not found and then i forced the phone coz im stuck on black htc screen using power button combo....sometime brought me back to bootloader.....and i started with second command from the beginning again .......fastboot oem rebootRUU but when the phone booted up to OS.....i used first command adb reboot bootloader but after that always same error device not found.....

Maybe you need to try another ROM.
Sent from my Evita

Solved.....s-off now
timmaaa said:
Maybe you need to try another ROM.
Sent from my Evita
Click to expand...
Click to collapse
SOLVED.....awesome....i figured it out.....:
1. Make sure to use android ICS ROM base coz JELLY BEAN base rom has a security feature that killed usb debugging during or after booting.
2. Check your android ADB version make sure 1.0.31 from cmd prompt navigate to your adb folder by pressing shift+right click and open cdm
3. Make sure u have all the htc driver install by installing htc sync manager ...it will update your htc driver installer and make sure to uninstall htc sync manager after that....just leave htc driver installer on your computer.
AWESOME....VERY APPRECIATED TIME AND HELP U GUYS GIVEN
Myrder said:
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Click to expand...
Click to collapse

Hmm, that's interesting. I've gotten s-off on two devices while on Jellybean. But at least you finally got it working.
Sent from my Evita

timmaaa said:
Hmm, that's interesting. I've gotten s-off on two devices while on Jellybean. But at least you finally got it working.
Sent from my Evita
Click to expand...
Click to collapse
Weird huh.....but like people said every phone is different...that's just what i did to my phone incase this might be useful for other xda member.....Just do alot of reading....and u might cross path with other people problem........READ....READ....AND READ.....:good: BTW TIM.....very appreciated for ur time.....i'm all out thanks....for today....more come to u tomorrow and other that help me.....
Myrder said:
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Click to expand...
Click to collapse

No problems mate, I'm just glad it finally worked for you.
Sent from my Evita

Sensation bootloop only hboot

Hello, i have a big Problem!
My sister have a HTC Sensation 4G she have plugin to Battery Load and the next morning have it bootloop.
When i will flash a RUU than come error 132 Signature Error
When i Flash manual it come 132 Signature Error
I dont come in the Recovery and not in the System
the CID is HTC__102
**** RELOCKED ****
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012, 17:33:34
C:\1>fastboot oem check_emmc
... INFOThis eMMC is not made from Micron.MID=144.
INFOeMMC should not be Micron's
OKAY
C:\1>fastboot flash zip PG58IMG.zip
sending 'zip' (420233 KB)... OKAY
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
Click to expand...
Click to collapse
C:\1>fastboot oem boot
... INFOmipi_dsi_cmd_configanel_id=0x940021
INFOwidth=540 height=960
INFOsetup_tag addr=0x48000100 cmdline add=0x801DA920
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x28002
INFOTAG:hero panel = 0x940021
INFOTAG:engineerid = 0x7
INFOTAG: PS ID = 0x2
INFODevice CID is not super CID
INFOCID is HTC__102
INFOsetting->cid::HTC__102
INFOserial number: HT227V810835
INFOcommandline from head: console=ttyHSL0 androidboot.hardware=
INFOpyramid no_console_suspend=1
INFOcommand line length =571
INFOactive commandline: poweron_status=1 board_pyramid.disable_u
INFOart3=0 diag.enabled=0 board_pyramid.debug_uart=0 userdata_se
INFOl=0 androidboot.emmc=true androidboot.pagesize=2048 android
INFOboot.lb=1 androidboot.baseband=11.24A.3504.31_M androidboot
INFO.cid=HTC__102 androidboot.batt_poweron=good_battery androidb
INFOoot.carrier=HTC-GER androidboot.mid=PG5813000 androidboot.ke
INFOycaps=qwerty androidboot.dq=FAIL androidboot.mode=normal and
INFOroidboot.serialno=HT227V810835 androidboot.bootloader=1.27.0
INFO000 zygote_oneshot=off msm_watchdog.enable=1 console=ttyHSL0
INFO androidboot.hardware=pyramid no_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOaARM_Partion[7].name=pdata
INFOaARM_Partion[8].name=extra
INFOaARM_Partion[9].name=radio
INFOaARM_Partion[A].name=adsp
INFOaARM_Partion.name=radio_config
INFOaARM_Partion[C].name=modem_st1
INFOaARM_Partion[D].name=modem_st2
INFOpartition number=14
INFOValid partition num=14
INFOTZ_HTC_SVC_SET_DDR_MPU ret = 0
INFOsmem 50005000 (phy 50005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_LOG_OPERATOR ret = 0
INFOTZ_HTC_SVC_MEMPROT ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 73523200 (0x461E000)
INFOjump_to_kernel: machine_id(3133), tags_addr(0x48000100), ker
INFOnel_addr(0x48008000)
INFO-------------------hboot boot time:118565 msec
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
i come only in HBoot and Fastboot and RUU bootloader more not.
please help!

post your firmware version
fastboot getvar version-main
have you seen this?
http://forum.xda-developers.com/showthread.php?t=1672425

version is 3.33.401.6
i cant Flash RUU but i can flash the firmware.zip what in the OTA now it is not finish and reboot
no realy change.....
Bootloop only HBoot... no Recovery come in Bootloop
your link dosnt work i have it make not change...
i dont come in the S-OFF it doesnt a Firmeware on the HTC or is a Firmware and cant boot...

AeroxTobi said:
version is 3.33.401.6
i cant Flash RUU but i can flash the firmware.zip what in the OTA now it is not finish and reboot
no realy change.....
Bootloop only HBoot... no Recovery come in Bootloop
your link dosnt work i have it make not change...
i dont come in the S-OFF it doesnt a Firmeware on the HTC or is a Firmware and cant boot...
Click to expand...
Click to collapse
use these ruu.exe
http://fileom.com/m9b0o83qmnpv/RUU_....24A.3504.31_M_release_266171_signed.exe.html
http://fileom.com/gjssrzfjd7c6/RUU_....24A.3504.31_M_release_280871_signed.exe.html
connect your device to the pc in fastboot mode and run the ruu.exe from pc

It come 132 Signature Error by all roms from you

AeroxTobi said:
It come 132 Signature Error by all roms from you
Click to expand...
Click to collapse
eroor 132 means different model
probably you need a specific ruu for sensation 4G
edit: by the way is your device branded?

Device isn´t brandig
Model number is 58130 i mean it is a normerly Sensation not 4g
I have more RUU flashed always Signature Error...

AeroxTobi said:
Device isn´t brandig
Model number is 58130 i mean it is a normerly Sensation not 4g
I have more RUU flashed always Signature Error...
Click to expand...
Click to collapse
i don't know mate what to tell you
i am out of ideas
post the out from this command
fastboot getvar all
remove your imei and s/n

version: 0.5
version-bootloader: 1.27.0000
version-baseband: 11.24A.3504.31_M
version-cpld: None
version-microp: None
version-main: 3.33.401.6
serialno: SERIAL
imei: IMEI
product: pyramid
platform: HBOOT-8260
modelid: PG5813000
cidnum: HTC__102
battery-status: very good
battery-voltage: 3837mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 617f0a98
hbootpreupdate: 11
gencheckpt: 0
all: Done!
That is in getvar all...

AeroxTobi said:
version: 0.5
version-bootloader: 1.27.0000
version-baseband: 11.24A.3504.31_M
version-cpld: None
version-microp: None
version-main: 3.33.401.6
serialno: SERIAL
imei: IMEI
product: pyramid
platform: HBOOT-8260
modelid: PG5813000
cidnum: HTC__102
battery-status: very good
battery-voltage: 3837mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 617f0a98
hbootpreupdate: 11
gencheckpt: 0
all: Done!
That is in getvar all...
Click to expand...
Click to collapse
everything seems to be fine
i really don't know mate
try several ruu.exe and see which one will work

I have try all RUU what i have Found min. 20 RUU and by all come Signature Error.
When i come in Recovery than can i Repair the HTC but i dont come in Recovery and not Boot only HBoot
it is exasperating

AeroxTobi said:
I have try all RUU what i have Found min. 20 RUU and by all come Signature Error.
When i come in Recovery than can i Repair the HTC but i dont come in Recovery and not Boot only HBoot
it is exasperating
Click to expand...
Click to collapse
unlock the bootloader again
then you can have access to the recovery

rzr86 said:
unlock the bootloader again
then you can have access to the recovery
Click to expand...
Click to collapse
I habe it but when i Boot in recovery it is bootloop or he Boot in hboot back

AeroxTobi said:
I habe it but when i Boot in recovery it is bootloop or he Boot in hboot back
Click to expand...
Click to collapse
i am out of ideas mate
try to reflash recovery with fastboot command

What about extracting the rom.zip file from the ruu, put it into the root directory of your sdcard and name it PG58IMG.zip.
Then turn on your phone by holding the volume down button to go into bootloader. There, the bootloader should look for some particular files including the mentioned file on your sdcard. You will be asked, if you want to install. Select yes with volume buttons and confirm by pressing the power button.
If this will not work, take the img file from a custom recovery. Take the file
android-info.txt from ruu or somewhere here from xda. Keep the structure inside the file, but check, that your phone's cid and mid are listed.
Compress both files to the file name above. Place the new file on your sdcard (remove or overwrite the old one) and retry.
Maybe with this you can achieve a custom recovery, which allows you to do some more experiments.
Sent from my HTC Sensation z710a

Stock AT&T XL won't boot after factory reset

I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.

He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)

Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img

I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon

Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?

Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.

I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.

Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon

Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.

Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382

HTC one mini - stuck in fastboot / unlock without victory

Hello ladies and gentlemen,
i got a problem with an (no surprise) HTC One Mini.
I try to fix it for a friend - but so far without victory.
problem description
The phone is constantly in Fastboot-Mode when turned on.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
OS-4.09.206.4
eMMc-boot 1024MB
Aug 13 2015, 23:05:25.0
FASTBOOT [USB]*
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
*when connected to the pc
The Bootloader Menu (Recovery, Factory Reset, Clear Storage) are without any function - just sending me back to fastboot.
Image CRC output:
Code:
rpm: 0x0
sbl1: 0x0
sbl2: 0x0
sbl3: 0x0
tz: 0x0
radio: 0x0
hboot: 0x0
boot: 0x0
recovery: 0x0
system: 0x0
Tries to unlock the device via htcdev did not work up to now [the popup on the screen never pops up ]
Here some Code Snippets:
*fastboot getvar all - output:
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.22.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.206.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37W*******
(bootloader) imei: 3558********
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4237mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
*fastboot flash unlocktoken Unlock_code.bin - output:
Code:
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.169s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.182s
Used tools:
PC - Windows 10
15 seconds ADB Installer v1.3
Samsung Galaxy S6 - Data/Power-Cable
Feel Free to ask for more information - ill try to provide.
Thank you in advance!
Edit: No Ideas?

got exactly the same problem here, also an HTC One Mini from O2...

I have the same problem and you cannot flash as I get error 171 anyone got any idea on how to get these phones flashed?

HTC mini one stopped working. Won't turn on or off and screen even looks like it's come away from the sides...help please

Temporary fix for the FastBoot loop problem: Search the HTC One X forums for "SOLVED: Stuck in fastboot with low battery. Use this BATCH file! by floepie" - all credit to floepie
https://forum.xda-developers.com/showthread.php?p=26212322
The script continually reboots your phone, which allows it to slowly charge (plug it directly into the motherboard, good USB cable, and non-essential USB peripherals unplugged for max amperage). Eventually it will boot normally, though in my experience, it's taken hours. Not sure if it's actually the battery charging or just random luck with the number of reboots. 80% battery and 4.1-4.2V might be the magic numbers. This probably won't work if you had a bad flash or other preexisting condition.
This ridiculous problem now happens to me every time my phone dies or I have to reboot it. I have the recommended TWRP, s-off, unlocked, no tampered message, etc but pressing recovery just reboots it into fastboot again. I'll probably try re-flashing stuff or just use this method until it's completely dead. Bought it in 2014 when it was >$200 unlocked but I excessively baby my devices; 3 years is good in cell phone years, but I was expecting more.
I really like this phone, but it's getting hard to love between this, the pink camera issues, and speakerphone problem with the older InsertCoin (my preference). Good size, snappy Sense interface, and decent battery life when used with a nice, slim kernel and rom.
Windows - Put the following into a .bat file in your adb directory:
Code:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
Linux/Mac - Put the following into a .sh file in your adb directory (untested):
Code:
#!/bin/sh
while true
do
./fastboot getvar battery-voltage
./fastboot reboot-bootloader
sleep 5
Edit: Latest numbers are 2 hours of rebooting to get to 4110mV / 82% reported battery (started sub 4V after a phone freeze/reboot)