[Q] Bricked Sensation XE after S-ON - HTC Sensation

Hello guys,
i'm in really big trouble with my new sensation xe.
As mentioned in the title i have bricked it after trying to re s-on my phone, the troubles started with the fact that i did not reflashed with a new stock rom but i hard-resetted the old one (that was still stock). I had successfully reset the CID to HTC__203 (this is the non branded sensation xe europe version right?) and then after a restart in fastboot i did "fastboot oem writesecureflag 3", command that went wrong becouse after a restart my sensation is completely bricked, whatever button i press the display remains black and even if i connect the battery charger the charge status led remains off.
Here are the last commands before the brick:
D:\android>fastboot oem writecid HTC__203
...
(bootloader) Start Verify: 0
(bootloader) erase sector 65504 ~ 65535 (32)
(bootloader) mipi_dsi_cmd_configanel_id=0x940021
(bootloader) width=540 height=960
(bootloader) mipi_dsi_cmd_configanel_id=0x940021
(bootloader) width=540 height=960
OKAY [ 0.183s]
finished. total time: 0.183s
D:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 3.322s]
finished. total time: 3.323s
D:\android>fastboot getvar cid
cid: HTC__203
finished. total time: 0.008s
D:\android>fastboot reboot
rebooting...
finished. total time: 1.674s
D:\android>adb reboot-bootloader
D:\android>fastboot oem writesecureflag 3
...
OKAY [ 0.065s]
finished. total time: 0.065s
D:\android>fastboot oem writesecureflag 3
...
(bootloader) pyramid_init_sd, SD card power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.134s]
finished. total time: 1.135s
D:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 1.789s]
finished. total time: 1.789s
D:\android>fastboot reboot-bootloader
< waiting for device >
Click to expand...
Click to collapse
The phone then was recognized as QHSUSB_DLOAD and after installing QHSUSB_Drivers_(x64) i see it as Qualcomm HS-USB QLDoader 9008 (COM6).
Now i read in various threads that in this state the phone can be managed by using QPST, so i installed it, but i have no idea on how to proceed.
If someone can please guide me we could turn up a very userful thread on how to unbrick phones after failed re s-on, I read several post where several users have experienced the same problem but never know if they have solved or the phone was sent assitance.
Thanks in advance and congratulations for your excellent work

I have the same issue with my sensation 4g,did u get any fox for this.

make a cwm nandroid backup. save file to pc. then flash an ruu and your good.

Oomike said:
make a cwm nandroid backup. save file to pc. then flash an ruu and your good.
Click to expand...
Click to collapse
my phone is not powering on and i'm unable to enter in to boot also.when i connect it to my pc in device manger its showing as "qualcomm hs-usb qdloader 9008"
so how can i go ahead now..

The same thing happen to me
can anyone help me please

the cid number you state is not the designated number for an xe device.
an EU xe device can have numerous cid
(depending on country and branded/unbranded)
htc__203 is an cid for an unbranded french htc device.
you should have chanced the cid number (better rememberd you old one), than flashed a stock rom that supports your cid and then at the end complete the s-on command.
can you get in fastboot? able to flash a ruu??

harish.toy said:
my phone is not powering on and i'm unable to enter in to boot also.when i connect it to my pc in device manger its showing as "qualcomm hs-usb qdloader 9008"
so how can i go ahead now..
Click to expand...
Click to collapse
Man, again I have t be the bearer if bad news...that code means that the phone is essentially bricked. It's a mode that I believe is meant for the factory workers to flash the phone for the first time. Something we cannot do here, yet.
Unless there has been some major advancement, there is nothing you can do short of asking htc to fix it for you. This seems to be the number one cause of bricks here...Going back to S-ON, which isn't all that necessary for warranty work anyways.
Matt

Related

can't change cid

i tried changing my cid to HTC__E11 and it worked but it doesnt show any OTA even after refreshing a lot and waiting a while
now im trying to change it to a diffferent cid but it doesnt change it i think
it says my cid is still HTC__E11
C:\>fastboot oem writecid HTC__001
... INFO pyramid_init_sd, SD card power on
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
INFOStart Verify: 3
INFOerase sector 65504 ~ 65535 (32)
OKAY [ 1.094s]
finished. total time: 1.095s
C:\>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.199s]
finished. total time: 3.199s
C:\>fastboot getvar cid
< waiting for device >
cid: HTC__E11
finished. total time: 0.010s
If you don't get the update after this change, you have done something else to your phone which causes the update to not be able to detect you're eligible for the update. I have changed my CID to HTC__E11 (because I'm Dutch) and I used the stock ROM which can be obtained from here. I also changed the device back to S-ON, but I'm not sure if that is necessary.

[Q] s-off evo3d [solved]

Edit: solved using the juopunutbear's wire-trick.
Hi everybody!
Few months ago I have followed the guide of dryogeshd: http://forum.xda-developers.com/showthread.php?t=1535987
I have unrooted but no s-off.
Now it's time to upgrade the ROM ( actually LeeDrOiD_3D_V5.3.0 ) and I looked to news about s-off.
My device is:
HTC EVO 3D X515m (shooteru-1.49.0012, Android: 2.3.4, ROM version: 1.24.165.1) cid VODAP405
unlocked
shooter_u pvt ship s-on rl
hboot-1.49.0012
eMMc-boot
Aug 4 2011,14:10:29
Click to expand...
Click to collapse
-No way using htcsupertool
-No way using Free 3VO_V2 (just relock the device and add RADIO-10.13.9020.29_M in fastboot, keep cid VODAP405)
-No way changing the file mmcblk0p31.img according with the guide, or following the post of happyhallsy8 forum.xda-developers.com/showthread.php?t=1247392HTC__044
Code:
C:\>cd A
C:\A>fastboot oem readcid
< waiting for device >
...
(bootloader) cid: VODAP405
OKAY [ 0.016s]
finished. total time: 0.016s
C:\A>fastboot getvar cid
cid: VODAP405
finished. total time: 0.000s
C:\A>fastboot oem writecid HTC__001
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) shooter_u_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.125s]
finished. total time: 1.125s
C:\A>fastboot oem readcid
...
(bootloader) cid: VODAP405
OKAY [ 0.000s]
finished. total time: 0.000s
C:\A>
Now I am running Leedroid 5.4 final, but ever s-on. And wifi not working...
Am I too noob or is my version of device invincible? :laugh:
Can I try something other or have to try with the juopunutbear's wire-trick? http://unlimited.io/juopunutbear-public-beta-0-1/instructions/
Tnx in advance
RacketIDE said:
Hi everybody!
Few months ago I have followed the guide of dryogeshd: http://forum.xda-developers.com/showthread.php?t=1535987
I have unrooted but no s-off.
Tnx in advance
Click to expand...
Click to collapse
Hi,
I suppose, your device is not supported yet. You can try the following method.
Copy the PG86IMG to the root of your SD card, just let it flash through boot loader... Then try revolutionary tool.
dryogeshd said:
Hi,
I suppose, your device is not supported yet. You can try the following method.
Copy the PG86IMG to the root of your SD card, just let it flash through boot loader... Then try revolutionary tool.
Click to expand...
Click to collapse
Tnx dryogeshd.
You are right, revolutionary not support my device.
Flashing the pg86img (md5 429663bda14fc353f3ef64c9cab11620 ) don't change
hboot-1.49.0012.
I can't understand why in the old version of leedroid the wifi worked. Bad about the signal distance, but working.
Maybe using Free 3VO_V2 as changed something? (just relock the device and add RADIO-10.13.9020.29_M in fastboot, keep cid VODAP405)
I have now tried also a PG86IMG for 1.20.401.2RUU, find here: http://forum.xda-developers.com/showthread.php?t=1218196
but another hole in the water.
What do you think about the wire trick?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Hi, I have solved using the juopunutbear's wire-trick.
Now I am s-off, hboot-1.49.9999.
Re-installing LeeDroid Final I have found that wifi is working.
Tnx everybody helped me! :highfive:

[Q] Pyramid stuck in fastboot-loop

Hi there.
I've got an unbranded htc sensation device (manufactured for india). lat week i updated to cm9, and accidentally got a 1.29 hboot. after that I tried to flash the stock ICS for my pyramid. so, the situation is:
cid HTC__038
hboot version 1.29.0000
radio 11.24A.3504.31_m
openadsp v05.6.0.2226.00.0418
pyramid pvt ship s-on locked.
working adb, fastboot connection
i've got no working rom on the device, stuck in fastboot-loop.
there is no possibility to use revolutionary s-off because of hboot version 1.29, and because the non-working system (cannot put in debug mode)
i tried to flash the lastest 3.33 firmware, bit it still uses a previous version of hboot. (something messed up with signature check fail)
i cannot flash a non-official rom befause s-on.
do i have any possible steps to make my phone working with ics+sense?
all the answers will be "thanked" & btw sorry for my bad english
palomatE said:
Hi there.
I've got an unbranded htc sensation device (manufactured for india). lat week i updated to cm9, and accidentally got a 1.29 hboot. after that I tried to flash the stock ICS for my pyramid. so, the situation is:
cid HTC__038
hboot version 1.29.0000
radio 11.24A.3504.31_m
openadsp v05.6.0.2226.00.0418
pyramid pvt ship s-on locked.
working adb, fastboot connection
i've got no working rom on the device, stuck in fastboot-loop.
there is no possibility to use revolutionary s-off because of hboot version 1.29, and because the non-working system (cannot put in debug mode)
i tried to flash the lastest 3.33 firmware, bit it still uses a previous version of hboot. (something messed up with signature check fail)
i cannot flash a non-official rom befause s-on.
do i have any possible steps to make my phone working with ics+sense?
all the answers will be "thanked" & btw sorry for my bad english
Click to expand...
Click to collapse
Unlock via htcdev unlock then flash 4EXT recovery and enable smartflash then flash a ROM
flashing issue
Jonny said:
Unlock via htcdev unlock then flash 4EXT recovery and enable smartflash then flash a ROM
Click to expand...
Click to collapse
I've got the Unlock_code.bin, flashed with fastboot (fastboot flash unlocktoken Unlock_code.bin), and nothing happens, i mean no prompt is hiven for me to choose neither yes or no. command line says
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.162s
Click to expand...
Click to collapse
bootloader is still locked.
is it supported for hboot v1.29?
palomatE said:
I've got the Unlock_code.bin, flashed with fastboot (fastboot flash unlocktoken Unlock_code.bin), and nothing happens, i mean no prompt is hiven for me to choose neither yes or no. command line says
bootloader is still locked.
is it supported for hboot v1.29?
Click to expand...
Click to collapse
Hi,
Yes, 1.29 is supported.
Keep trying.
Sometimes ,it takes more than one go to work.
still no success
malybru said:
Hi,
Yes, 1.29 is supported.
Keep trying.
Sometimes ,it takes more than one go to work.
Click to expand...
Click to collapse
after a few attempts, i've got the following four different responses:
Code:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.162s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... FAILED (remote: loading custom splash failed)
finished. total time: 0.001s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.069s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.079s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... OKAY [ 0.008s]
finished. total time: 0.160s
palomatE said:
after a few attempts, i've got the following four different responses:
Code:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.162s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... FAILED (remote: loading custom splash failed)
finished. total time: 0.001s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.069s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.079s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... OKAY [ 0.008s]
finished. total time: 0.160s
Click to expand...
Click to collapse
fastboot reboot-bootloader
and then check the bootloader status
still locked
ganeshp said:
fastboot reboot-bootloader
and then check the bootloader status
Click to expand...
Click to collapse
I actually did this, with the same results. Is it a possible way if modify the partitions by a partitioning software running on pc, and manually edit the partitions' files, changing them to the correct ones, came from the official rom.zip file? I think (dont hit me if i was wrong), this way I can bypass all the s-on and locked bootloader stuff, maybe I can downgrade from hboot 1.29 without wire tricks, and install the stock ICS for pyramid.
what about the PG58IMG stuff? I can modify the removable sd card's files, so i can insert PG58IMG things to root, the phone is actually reads it. what if I somehow inject the Unlock_code.bin into some kind of PG58IMG, and apply this way the unlocking?
could be anything of these upper is working?
palomatE said:
I actually did this, with the same results. Is it a possible way if modify the partitions by a partitioning software running on pc, and manually edit the partitions' files, changing them to the correct ones, came from the official rom.zip file? I think (dont hit me if i was wrong), this way I can bypass all the s-on and locked bootloader stuff, maybe I can downgrade from hboot 1.29 without wire tricks, and install the stock ICS for pyramid.
what about the PG58IMG stuff? I can modify the removable sd card's files, so i can insert PG58IMG things to root, the phone is actually reads it. what if I somehow inject the Unlock_code.bin into some kind of PG58IMG, and apply this way the unlocking?
could be anything of these upper is working?
Click to expand...
Click to collapse
Nope can't/won't work
We could try one thing... Try changing cid
fastboot oem writecid HTC__001
Then ignore errors and reboot
fastboot reboot-bootloader
And check cid again
fastboot getvar cid
If it changed then you can very well flash European unbranded ruu and then boot to a working rom
If it not worked.. Then send a PM to FOOTBALL and ask for Indian ruu.. He might charge some minimal amount based on the scarcity of the ruu.. But if you got proper Indian ruu then you will come out of the boot loop fine
Sent from my Nexus 7 using xda premium
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
You have working adb when in boot loop?
Then you can try my temp-root and then jb SOFF process.. Link in my signature
Have slim chances of working.. But worth a try
Sent from my Nexus 7 using xda premium
ganeshp said:
Nope can't/won't work
We could try one thing... Try changing cid
fastboot oem writecid HTC__001
Then ignore errors and reboot
fastboot reboot-bootloader
And check cid again
fastboot getvar cid
If it changed then you can very well flash European unbranded ruu and then boot to a working rom
If it not worked.. Then send a PM to FOOTBALL and ask for Indian ruu.. He might charge some minimal amount based on the scarcity of the ruu.. But if you got proper Indian ruu then you will come out of the boot loop fine
Sent from my Nexus 7 using xda premium
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
You have working adb when in boot loop?
Then you can try my temp-root and then jb SOFF process.. Link in my signature
Have slim chances of working.. But worth a try
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
cid change is done, now it's HTC_001.
i tried to flash RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed's rom.zip from the temp, renamed to PG58IMG, copied to sdcard's root.
phone said: "lower hboot version"
is there any stock htc ROM with hboot 1.29?
if no, is it a possible way to change the zip to contain a 1.29 hboot version?
edit: i've got no bootloop, but at power-on I'm suddenly passed to fastboot screen without any boot process
but fastboot usb connection is always working, fastboot devices responses are always positive.
palomatE said:
cid change is done, now it's HTC_001.
i tried to flash RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed's rom.zip from the temp, renamed to PG58IMG, copied to sdcard's root.
phone said: "lower hboot version"
is there any stock htc ROM with hboot 1.29?
if no, is it a possible way to change the zip to contain a 1.29 hboot version?
Click to expand...
Click to collapse
Awesome... That will solve our issue now
Do this copy the New PG58IMG zip file to your fastboot folder
And try these commands one by one
fastboot erase cache (if failed ignore it)
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed stop there and don't do any thing else and simply paste back the output here)
fastboot reboot
Done
Edit: if the fail at third step is.. Something like.."Hboot pre update... Please flush the rom immediately again"] then repeat the third step again. (i.e this one fastboot flash zip PG58IMG.zip)
Sent from my Nexus 7 using xda premium
---------- Post added at 10:22 PM ---------- Previous post was at 10:12 PM ----------
palomatE said:
edit: i've got no bootloop, but at power-on I'm suddenly passed to fastboot screen without any boot process
but fastboot usb connection is always working, fastboot devices responses are always positive.
Click to expand...
Click to collapse
Now that we have successful cid change adb change is not required
Sent from my Nexus 7 using xda premium
ganeshp said:
Awesome... That will solve our issue now
Do this copy the New PG58IMG zip file to your fastboot folder
And try these commands one by one
fastboot erase cache (if failed ignore it)
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed stop there and don't do any thing else and simply paste back the output here)
fastboot reboot
Done
Edit: if the fail at third step is.. Something like.."Hboot pre update... Please flush the rom immediately again"] then repeat the third step again. (i.e this one fastboot flash zip PG58IMG.zip)
Sent from my Nexus 7 using xda premium
---------- Post added at 10:22 PM ---------- Previous post was at 10:12 PM ----------
Now that we have successful cid change adb change is not required
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
faced into error again here is the output:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 3.121s]
finished. total time: 3.121s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.267s]
finished. total time: 3.267s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (436283 KB)... OKAY [ 58.448s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 129.037s
C:\Android>fastboot flash zip PG58IMG.zip - here i didn't hit enter
palomatE said:
faced into error again here is the output:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 3.121s]
finished. total time: 3.121s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.267s]
finished. total time: 3.267s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (436283 KB)... OKAY [ 58.448s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 129.037s
C:\Android>fastboot flash zip PG58IMG.zip - here i didn't hit enter
Click to expand...
Click to collapse
hit enter ..if it fails again
reboot to bootloader using this command
fastboot reboot-bootloader
then can you give me the output of this command ?
fastboot getvar all (post everything except IMEI and serial number )
ganeshp said:
hit enter ..if it fails again
reboot to bootloader using this command
fastboot reboot-bootloader
then can you give me the output of this command ?
fastboot getvar all (post everything except IMEI and serial number )
Click to expand...
Click to collapse
i've made several attempts, all of them came out with the same results as I posted previously.
getvar results are the following:
Code:
C:\Android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: *** sent you via PM ***
INFOimei: *** sent you via PM ***
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4064mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.494s
hope this might help :angel:
hmm this has some weird combination (modelid indicates that the phone is normal sensation ..but firmware version says that the phone is xe!!!) ..but lets see
download the XE version of the same RUU you've downloaded earlier (will have LE in its Name) and get the rom.zip and flash the rom.zip manually using the fastboot commands ive given you earlier
ganeshp said:
hmm this has some weird combination (modelid indicates that the phone is normal sensation ..but firmware version says that the phone is xe!!!) ..but lets see
download the XE version of the same RUU you've downloaded earlier (will have LE in its Name) and get the rom.zip and flash the rom.zip manually using the fastboot commands ive given you earlier
Click to expand...
Click to collapse
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
palomatE said:
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
Click to expand...
Click to collapse
To change MID you need S-OFF. The RUU checks MID so if the 3.33.401.153 RUU fails try the 3.33.401.53 one
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
palomatE said:
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
Click to expand...
Click to collapse
Ahh as suspected
What happened is you have somehow flashed sensation xe hboot and rest of them have normal sensation counterparts...
I need you to do something now... Download the universal 3.33 firmware from kohr-ah firmware thread in sensation development section..
Then extract the zip
Open android-info.txt file and replace version-main with 3.33.401.53
And save it
Also you have the rom.zip of the normal sensation 3.33.401.53 right.. Get the hboot.nb0 (the name will be big but the extension remains same) and replace the hboot.nb0 present in the firmware zip with this one..
Then remake the firmware.. PG58IMG.zip
Then try to flash this... Obviously it will fail.. But if that replaces the hboot you are having then all is well
So after the above exercise.. You need to try flashing normal sensation rom.zip again
Hopefully it works
Sent from my HTC Sensation using xda premium
so i had to give back the phone to its owner, if the main htc service fails im goin to do the rest you suggested me. anyway i want to say thanks to all of you guys out there, i'll be back for more info, in case of fail. have a nice day
Sent from my GT-I9000 using xda app-developers app

Stuck in BootLoader & unable to unlock the phone

Hi, I have a very frustrating problem with my HTC One Mini.
Out of nowhere, my phone won't boot into the OS but goes straight into the bootloader.
This is what my bootloader looks like:
Code:
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2014, 15:21:25 0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can't perform a factory reset and I can't get into recovery either. I tried to unlock the phone so I could flash the recovery and install a ROM from there. So I went to htcdev.com and started the bootloader unlock process. I downloaded the Unlock_code.bin file and tried to flash the unlock token:
Code:
fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s
Nothing happens on the phone after this. I read on the forums I maybe had to run a RUU so I went to the HTC ROM download page and downloaded the RUU and ran it. The phone rebooted but didn't go into RUU mode. After some time, I get a USB Connection error (171).
I tried to get into RUU mode with fastboot but that also doesn't work.
Code:
fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 1.953s]
finished. total time: 1.953s
From here, I don't know what to do next and I hope you can help me.
Thanks in advance.
Welcome to the XDA forums, Vyperz52! I'm currently trying to solve a very similar problem with my HTC One Mini, and I have one suggestion that might help. Have you tried flashing some different form of recovery? Trying to flash TWRP recovery might work, it didn't for me but it's worth a try [https://twrp.me/devices/htconeminigsm.html]. Try the Fastboot install method (reading and accepting the risks that come with trying to install different recovery software).
imapanther said:
Welcome to the XDA forums, Vyperz52! I'm currently trying to solve a very similar problem with my HTC One Mini, and I have one suggestion that might help. Have you tried flashing some different form of recovery? Trying to flash TWRP recovery might work, it didn't for me but it's worth a try. Try the Fastboot install method (reading and accepting the risks that come with trying to install different recovery software).
Click to expand...
Click to collapse
Thank you for your reply.
I tried what you said but unfortunately, it's not working.
Code:
fastboot flash recovery twrp.img
target reported max download size of 800227328 bytes
sending 'recovery' (11460 KB)...
OKAY [ 1.500s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.424s
My phone is still locked so I think that's why flashing the recovery fails.
im also having problem with the bootloader unlock.
i have stuck in the 10th step of htcdev.com
any ideas why i cant see the warning on the phone?
btw the phone doesnt boot. i have access only to bootloader and fastboot on my phone
elessargr said:
im also having problem with the bootloader unlock.
i have stuck in the 10th step of htcdev.com
any ideas why i cant see the warning on the phone?
btw the phone doesnt boot. i have access only to bootloader and fastboot on my phone
Click to expand...
Click to collapse
I contacted HTC about the bootloader unlock issue but they won't help because they don't recommend unlocking the BL because it can cause the phone to crash and become unusable. After which I replied to them that's already the case without doing the unlock.
hi guys i got the same problem as you i m stuck on bootloader menu my phone looks like this
*** UNLOCKED ***
M4_UL PVT SHIP S-OFF RL
CID-HTC__102
HBOOT-2.22.0000
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2014, 15:21:25 0
Click to expand...
Click to collapse
this what i got when i tried somes fastboot command
PHP:
C:\Android>fastboot flash zip cm12.zip
sending 'zip' (257726 KB)...
OKAY [ 11.875s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 11.969s
C:\Android>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.031s
C:\Android>fastboot flash recovery recovery14.img
sending 'recovery' (9320 KB)...
OKAY [ 1.234s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.391s
cant boot into recovery and cant flash it via fastboot
can someone help us to solve this issue

Unlocking HTC DESIRE 828 (HELP NEEDED)

I need help with unlocking bootloader of my HTC DESIRE 828. I tried the method as mentioned in the HTC DEV website but i keep encountering this error
fastboot oem get_identifier_token
FAILED (remote: unknown command)
finished. total time: 0.006s​Then with little searching i found this command which i assume is used to lock bootloader ? (not sure) BTW IM NOT GETTING ANY ERROR
fastboot oem lock
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.051s]
finished. total time: 0.052s​BUT WHEN I TRY THIS COMMAND
fastboot oem unlock
(bootloader) [ERR] Command error !!!
OKAY [ 0.004s]
finished. total time: 0.005s​it shows me this error.
ADDITIONAL INFORMATION:
My phone is bricked and im trying to flash the stock rom but for that i need bootloader to be unlocked and download mode is showing "S-ON" idk what it means or does....
weapons9clear said:
I need help with unlocking bootloader of my HTC DESIRE 828. I tried the method as mentioned in the HTC DEV website but i keep encountering this error
fastboot oem get_identifier_token
FAILED (remote: unknown command)
finished. total time: 0.006s​Then with little searching i found this command which i assume is used to lock bootloader ? (not sure) BTW IM NOT GETTING ANY ERROR
fastboot oem lock
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.051s]
finished. total time: 0.052s​BUT WHEN I TRY THIS COMMAND
fastboot oem unlock
(bootloader) [ERR] Command error !!!
OKAY [ 0.004s]
finished. total time: 0.005s​it shows me this error.
ADDITIONAL INFORMATION:
My phone is bricked and im trying to flash the stock rom but for that i need bootloader to be unlocked and download mode is showing "S-ON" idk what it means or does....
Click to expand...
Click to collapse
I shouldn't need to unlock bootloader in order to flash stock rom
go to developer options and check the option - enable oem unlock.then reboot and run the command.
Also how can your phone be bricked with a locked bootloader?It does not make sense .YOu cannot flash ROms on a locked bootloader and if your phone is bricked then that means your bootloader has to be unlocked!!!

Categories

Resources