Database Info

[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

[Q] bad CID - stuck in bootloader

In my quest to upgrade the hboot of my HTC One XL (evita), I accidentally used a tool intended for the the HTC One X (JFW Tool), and overwrote my CID to HTC__621. Now I'm stuck in the bootloader. Any help would be much appreciated (especially with the steps, I'm still a bit fuzzy on SuperCID, S-Off, bootloaders, roms and recovery). I think I was previously unlocked, running an unofficial CyanogenMod (because updates stopped coming around), and then I wanted to get on the OTA CM train, but needed to update hboot, which got me in my current situation:
Here's what my bootloader screen says:
Code:
*** TAMPERED ***
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
FASTBOOT (or FASTBOOT USB)
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
And here's what I've tried:
tried setting CID to 11111111
tried flashing recovery (my TWRP recovery is not present anymore)
tried flashing hboot
tried running X-Factor exploits
ran the all-in-one tool to try and exploit and unlock
I cannot seem to get anything to work. Flashing anything generates a remote signature fail id error.
Please help me to get my phone back up again!
Thanks,
Dave

You tried all those things without knowing what you're doing? You must love to live life dangerously!
Your bootloader is locked.

In bootloader, use volume down to scroll to reboot and hit power button to select it. Then read forums on how to unlock bootloader.
Sent from my HTC One X using xda premium

Venomtester said:
In bootloader, use volume down to scroll to reboot and hit power button to select it. Then read forums on how to unlock bootloader.
Click to expand...
Click to collapse
Perfect, that's what I needed (I didn't know bootloaders could become "relocked".
So, I'm now back to where I was before, with a phone I cannot update to the latest CM10, because my hboot is too old (=1.09)
I've tried to follow all the instructions on these forums for updating hboot to 2.14, without any success:
Using Hassoon2000's all-in-one kit for the HTC One X (evita) and also from the command line, I've tried to directly install:
hboot 2.14
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k (which contains 2.14)
It fails on signature or hangs. I tried this with bootloader locked and unlocked (thanks to Venomtester, I can now do this without difficulty), and from the bootloader, fastboot and htc screens (gold htc logo).
So any hints on how to get hboot 2.14 installed on this device? Failing that, (or perhaps instead of) I could even go back to a factory ROM and settings, if I could get some hints on this.
Thanks again,
Dave
PS: I have a feeling it may be malfunctioning due to that CID change I did. I tried to change CID back using the regular tool, and then used the instructions for hex editing the CID, all without success (adb shell doesn't work)

boulder_dave said:
Perfect, that's what I needed (I didn't know bootloaders could become "relocked".
So, I'm now back to where I was before, with a phone I cannot update to the latest CM10, because my hboot is too old (=1.09)
I've tried to follow all the instructions on these forums for updating hboot to 2.14, without any success:
Using Hassoon2000's all-in-one kit for the HTC One X (evita) and also from the command line, I've tried to directly install:
hboot 2.14
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k (which contains 2.14)
It fails on signature or hangs. I tried this with bootloader locked and unlocked (thanks to Venomtester, I can now do this without difficulty), and from the bootloader, fastboot and htc screens (gold htc logo).
So any hints on how to get hboot 2.14 installed on this device? Failing that, (or perhaps instead of) I could even go back to a factory ROM and settings, if I could get some hints on this.
Thanks again,
Dave
PS: I have a feeling it may be malfunctioning due to that CID change I did. I tried to change CID back using the regular tool, and then used the instructions for hex editing the CID, all without success (adb shell doesn't work)
Click to expand...
Click to collapse
What is your CID right now still the same?
use fastboot oem readcid to find out if you're not sure.

exad said:
What is your CID right now still the same?
use fastboot oem readcid to find out if you're not sure.
Click to expand...
Click to collapse
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT249W300070
(bootloader) imei: 359691042133556
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s

boulder_dave said:
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT249W300070
(bootloader) imei: 359691042133556
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Click to expand...
Click to collapse
Okie dokie, so, your bootloader is unlocked at this point right?
If so, flash twrp 2.6: fastboot flash recovery recoveryfilename.img
Your CID shouldn't matter for right now, you should at least be able to flash a Rom at this point (obv. not cm10.1 3.4 kernel). Then we can work on SuperCID and S-OFF.

exad said:
Okie dokie, so, your bootloader is unlocked at this point right?
If so, flash twrp 2.6: fastboot flash recovery recoveryfilename.img
Your CID shouldn't matter for right now, you should at least be able to flash a Rom at this point (obv. not cm10.1 3.4 kernel). Then we can work on SuperCID and S-OFF.
Click to expand...
Click to collapse
Thanks for all the help!
2.6 TWRP installed and working. Still running (extremely poorly, all kinds of flakiness: loses cellular data connection constantly) the 10.1 CM I was running before I embarked upon this upgrade.
What should I do next?
Cheers,
Dave

If I'm not wrong, you're gonna need to s-off to get to the newest cm nightlies because of RUU. So first you're gonna need SuperCID. Someone correct me of I'm wrong but I'm gonna say you need to
fastboot oem writecid 11111111
and then head over to the S-Off thread. I wouldn't do this just yet, because I'm not 100% sure, but if someone could confirm that'd be wonderful.

RollTribe said:
If I'm not wrong, you're gonna need to s-off to get to the newest cm nightlies because of RUU. So first you're gonna need SuperCID. Someone correct me of I'm wrong but I'm gonna say you need to
fastboot oem writecid 11111111
and then head over to the S-Off thread. I wouldn't do this just yet, because I'm not 100% sure, but if someone could confirm that'd be wonderful.
Click to expand...
Click to collapse
That command may or may not work.
The good news is, if it doesn't, since you have root and aren't on a 2.14 hboot it's still super easy
If that command doesn't work, boot to the rom you're using, make sure usb debugging is enabled. If you're using CyanogenMod, you'll also have to give ADB root access in developer settings.
Open command prompt in the folder you have ADB and do
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
then you should have superCID and should be able to S-OFF using the sticky in original android dev. section
when you type the su command, it may prompt you on your phone to allow su through adb so keep that in mind.

exad said:
That command may or may not work.
The good news is, if it doesn't, since you have root and aren't on a 2.14 hboot it's still super easy
If that command doesn't work, boot to the rom you're using, make sure usb debugging is enabled. If you're using CyanogenMod, you'll also have to give ADB root access in developer settings.
Open command prompt in the folder you have ADB and do
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
then you should have superCID and should be able to S-OFF using the sticky in original android dev. section
when you type the su command, it may prompt you on your phone to allow su through adb so keep that in mind.
Click to expand...
Click to collapse
Excellent, you guys are the best! So, I have CID = 11111111, S-OFF.
What's the next step to getting back on the CM10 bandwagon? Or updating hboot? Or whatever I need to do next?
Cheers,
Dave

Run your carrier 3.17/3.18 ruu
Then flash twrp then flash cm10.1
Sent from my One X using xda app-developers app

exad said:
Run your carrier 3.17/3.18 ruu
Then flash twrp then flash cm10.1
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Here's how I tried to flash the RUU (failing):
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.945s
This booted me into CM unexpectedly
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>adb reboot-bootloader
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.062s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.835s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.936s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
For some reason, if I didn't reissue the below command, subsequent flashes would fail, even though I was still in the black screen with HTC logo mode
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.060s]
finished. total time: 0.063s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.421s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.514s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.024s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.060s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.132s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.234s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.063s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.144s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.232s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.065s]
finished. total time: 0.070s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>
So I'm not sure what to do next. Flashing RUU doesn't seem to work. bootloader says I'm still S-OFF (whatever that means), now "RELOCKED", CID still 11111111, and hboot still 1.09.
Thanks again for taking me through this,
Dave

All you need to do is run the RUU as was intended. It's an exe file. Plug in your phone and start the program.

Use RUU not OTA, it is easier.
OTA would require stock recovery to complete and much more care with how stock things are.

RollTribe said:
All you need to do is run the RUU as was intended. It's an exe file. Plug in your phone and start the program.
Click to expand...
Click to collapse
Thanks everyone! I'm back on the CM10.1 bandwagon (with OTA updates!) and this HTC One X is working better than ever.
For other folks, here were my mistakes and stumbling blocks:
Don't use utilities intended for the HTC One X (Tegra 3) on the HTC One XL (evita). This is how I accidentally changed my CID. This might seem obvious, but when you're checking around these forums, you can frequently end up in the wrong forum.
ADB commands work when the phone is in its OS.
If the setcid command line doesn't work, use the line from exad.
Don't try and use the RUU flashing procedure (with the OTA .zip file) to flash the firmware, use the .exe file, and just execute it.
I did not (and still don't really) understand the difference and utility of RUUs, S-On/S-Off, unlocking the bootloader, hboot, ROMs, SuperCID, radios, ADB and fastboot commands.
Back to using my now very functional HTC One X (it was on the verge of a tragic high-velocity intentional disassembly).
Cheers,
Dave

boulder_dave said:
[*]I did not (and still don't really) understand the difference and utility of RUUs, S-On/S-Off, unlocking the bootloader, hboot, ROMs, SuperCID, radios, ADB and fastboot commands.
Click to expand...
Click to collapse
There's a link in my signature that I took time to write up just for explaining these.

Fixed

And how will his hboot go to 2.14?
Sent from my HTC One XL using xda app-developers app
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
Cause I'm confused to where you got the exe file from? Thanks
Sent from my HTC One XL using xda app-developers app

ZayedQamer.zq said:
And how will his hboot go to 2.14?
Sent from my HTC One XL using xda app-developers app
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
Cause I'm confused to where you got the exe file from? Thanks
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
by running the RUU :silly: http://forum.xda-developers.com/showthread.php?t=1671237

[Q] CM11 and Hboot 2.13

Will I be able to flash CM11 or any other KK ROM with Hboot 2.13? I have searched around without much luck, when I updated my Hboot, I got stuck with this strange version of it.
Thanks

gooner98 said:
Will I be able to flash CM11 or any other KK ROM with Hboot 2.13? I have searched around without much luck, when I updated my Hboot, I got stuck with this strange version of it.
Thanks
Click to expand...
Click to collapse
Try upgrade your hboot to 2.15:
1. Download here
2. Move the file to the location of fastboot on your computer
3. Windows: Open fastboot folder and hold shift and right click, then select Open Command Window Here.
Mac: Open a terminal window and your fastboot folder alongside each other. drag fastboot from folder to terminal window
4. Get into fastboot mode and type the following commands
fastboot oem rebootRUU
fastboot flash zip orig_hboot_2.15.0000.zip
fastboot reboot-bootloader
5. You should see Hboot 2.15.0000. If you had s-off with hboot 2.13 you will have it with 2.15
6. You should be able to flash cm11 nightlies now

Thanks for that, I'll give it a go.

OK, I got a fail
C:\fastboot>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.280s]
finished. total time: 0.280s
C:\fastboot>fastboot flash zip orig_hboot_2.15.0000.zip
sending 'zip' (400 KB)... OKAY [ 0.238s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 1.928s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.383s]
finished. total time: 0.383s

Do the command again, when you flash your firmware.zip with fastboot, this first try fail but the second is good. I don't know it may be some kind of security
Envoyé de mon One S en utilisant Tapatalk

Hi Guys
Any confirmation with this one? Did it work?
I do also have similat HBoot 2.13.
Have a phone from "3" / Three UK network with this HBOOT.
I was able to do the S-OFF.
Previous CID: CID: H3G__001 (H3G_01)
Current state:
CID: 11111111
Bootloader (HBOOT) 2.13 version
Baseband is 1.11.50.05.28
TWRM 2.6.0.0
Model: PJ4010000
I have checked the zip file from this thread and found txt file with details:
modelid: PJ4010000
cidnum: HTC__001
mainver: 3.16.401.8
btype:1
aareport:1
hbootpreupdate:1
...
Should I change CID before proceeding with HBOOT upgrade?
I am really afraid cause flashing HBOOT causes most of the bricks?

You guys are either not reading much or dont know how to search. The assert check in updater-script for any ROM allows flashing for the following hboots: 2.13.0000, 2.15.4444 and 2.15.0000
It is like this from the beginning and it was stated several times. So you don't need to update any hboot if you're on 2.13.
Sent from nowhere over the air...

Thanks Rapier. and I am sorry for taking your time. can I just clarify? you're saying that I can flash my phone with even kitkat (4.4) when I am on HBOOT 2.13? even when all threads are mentioning HBOOT in version 2.15/2.16?
really confusing for me. like I have missed something really basic over the last 3-4 weeks of reading this forum ?

[Completed] [Q] Flashing a non flashable boot image - HTC One (M7)

Hello,
Can anyone help me here please... i'm trying to flash the digital rain blue boot image which isnt flashable but i dont know how to make it flashable or how to instal it
Ive tried ADB sideloading it with no joy, fastboot oem rebootRUU then fastboot flash zip 'filename.zip' and get this message:
D:\FASTBOOT ADB>fastboot flash zip BootAnim_Digital_Rain_Blue_QuietlyBrilliant.zip
sending 'zip' (19066 KB)...
OKAY [ 2.205s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 3.154s
I'm totally new to all this as you can tell.. if anyone can point me in the right direction it would be very much appreciated !!
Thank you,
Craig
HTC One (M7)
Rooted (SuperSU)
S-Off
Unlocked
4.4.3 - Sense 6.0

Iv'e managed to do this now case closed

[Completed] HTC One M9 Bootloop Help

Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate

Hi !
I see that you have fixed your issue https://forum.xda-developers.com/showpost.php?p=71188370&postcount=1372 so I close this down
Cheers !