Database Info

The x920D S-off for your Pan Asia type Phone

Folks, This is not a joke anymore ​​
The x920D S-off for your Pan Asia type Phone
I hope you like
This is a valid work
Support equipment x920d
HTC__044
HTC__621
HBOOT version
1.39.0000
1.40.0000
1.41.0000​
​​I would like to give all the credits for my friends who have been helping me for all this process​
Onepagebook: For making the needed files
Nenebear: For supporting his idea and the order of process
Boa: for his Technical support
We are the A4tw Team
Special thanks Onepagebook to Without him, there is no work
Thanks to the Android4tw.com
I would like to thank XDA beaups’s S-OFF way
XDA S-OFF : original thread
http://forum.xda-developers.com/showthread.php?p=39792659
**If you need to post this article somewhere else, please give the credit as common courtesy
For beginning, please do nand back up first to the ext_SD, do NOT back up to internal SD
The process of s-off will definitely erase your data in internal sd
Now, get start and be ready for info
**before we start: There is nothing to do with s-off for hboot , by using the beaups’s way,
For getting s-off you need to be able to mod the superCID; however, the only version of firmware of X920D is based on the 1.04.709.5 (for moding mmcblk0p4)..
And what I did is downgrade the base to 1.03.709.1 and get to the S-off.
Now First step:
Please relock your x920D, and get into your fastboot tools:
Type:
Code:
fastboot oem rebootRUU
you will see the black background HTC screen and then type
Code:
fastboot flash zip 1.41.firmware.zip
after this, you will see:
sending 'zip' (33259 KB)...
OKAY [ 2.620s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check.
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again i
finished. total time: 9.372s
the key thing will be as followed you will see this
FAILED (remote: 90 hboot pre-update! please flush image again )
If you have an error
FAILED (remote: 43 main version check fail)
Use this program
http://forum.xda-developers.com/showpost.php?p=40800799&postcount=9
Click to expand...
Click to collapse
then type again:
Code:
fastboot flash zip firmware.zip
it takes time because send the ruu fromm computer to phone
it’s not the freeze..
now it will back to fastboot but still is S-ON
and you won;’t see the -TAMPERED again
Now go ahead and do unlock then flash the cwm recovery
Code:
fastboot flash recovery cwm-6027-touch-recovery.img
Under recovery use install zip from sideload
From your computer,
Code:
adb sideload Superuser3.2.zip
Now it will flash the superuser, after that please stay put, and back to your desktop for the
Supercid.cmd
If you see the screen , means you got the superCID changed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For making sure we have Super CID changed, type this
Code:
fastboot getvar all
Now pull you usb and then insert it again
NOW DO THE FOLLLOWING AGIN
Code:
fastboot oem rebootRUU
Check if screen get into the black HTC screen like beginning? If so then type
Code:
fastboot flash zip 1.41.firmware.zip
make sure you see the following:
c:\adb>fastboot flash zip firmware.zip
sending 'zip' (33259 KB)...
OKAY [ 2.591s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.666s
Again, this is very important if you do see this:
FAILED (remote: 92 supercid! please flush image again immediately)
It will show 92 error code because you got superCID already
So go on and type
Code:
fastboot oem boot
and you will see this:
C:\adb>Fastboot oem boot
... INFOpm8921_vreg_disable function, vreg_id = 14
INFOBoot/Recovery signature checking...
INFOTZ_HTC_SVC_HASH ret = 0
INFOsetup_tag addr=0x80600100 cmdline add=0x00324BE8
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x32E03
INFOTAG:hero panel = 0x940063
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x1
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is empty
INFOsetting->cid::11111111
INFOserial number: FA2CMPNXXXXX
INFOcommandline from head: console=ttyHSL0,115200,n8 androidboot
INFO.hardware=dlxub1 user_debug=31
INFOcommand line length =811
INFOactive commandline: poweron_status=1 reset_status=0 board_de
INFOluxe_ub1.disable_uart3=0 diag.enabled=0 board_deluxe_ub1.deb
INFOug_uart=0 userdata_sel=0 androidboot.emmc=true androidboot.p
INFOagesize=2048 skuid=0 ddt=20 ats=0 androidboot.lb=1 uif=S2iM
INFO td.sf=1 td.td=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlo
INFOg.ofs=628 un.ofs=694 imc_online_log=0 androidboot.efuse_inf
INFOo=FNSL androidboot.baseband=3A.21.306.10 androidboot.cid=111
INFO11111 androidboot.devicerev=3 color_ID=BLK00 androidboot.bat
INFOt_poweron=good_batte
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=local
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOaARM_Partion[7].name=devlog
INFOaARM_Partion[8].name=pdata
INFOaARM_Partion[9].name=extra
INFOaARM_Partion[A].name=radio
INFOaARM_Partion.name=adsp
INFOaARM_Partion[C].name=dsps
INFOaARM_Partion[D].name=radio_config
INFOaARM_Partion[E].name=modem_st1
INFOaARM_Partion[F].name=modem_st2
INFOaARM_Partion[10].name=cdma_record
INFOaARM_Partion[11].name=reserve
INFOpartition number=18
INFOValid partition num=18
INFOsetting_get_bootmode() = 9
INFOsmem 8CF04000 (phy 8CF04000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
INFOStart Verify: 3
INFOjump_to_kernel: machine_id(4372), tags_addr(0x80600100), ker
INFOnel_addr(0x80608000)
INFO-------------------hboot boot time:25563 msec
FAILED (status read failed (Too many links))
Ok then phone will reboot
Then we wait for it get in system, you will need to make sure your DEV usb debugging option is checked
XDA S-OFF : original thread
http://forum.xda-developers.com/showthread.php?p=39792659
You must download the above thread the required soffbin3 file into the folder to continue
Then type
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb wait-for-device shell su -c "/data/local/tmp/soffbin3"
then key in twice:
Code:
exit
exit
and then
Code:
adb reboot bootloader
now go under bootloader…check if you got s-off
But we are not done yet…type
Code:
fastboot oem rebootRUU
go upgrade your firmware and stuff
Code:
fastboot flash zip 1.41.firmware.zip
it still got error but will turn to 90
FAILED (remote: 90 hboot pre-update! please flush image again )
And do this again:
Code:
fastboot flash zip 1.41.firmware.zip
so now it will start flashing 1.18 firmware
Code:
fastboot reboot
so now you have to reflash the cwm again to do whatever you want..
Please keep in mind, do not stay in the old version of ROM but flash the one you like
Good luck and enjoy.
x920d-HTC__621-S-OFF-Tool
x920d-HTC__044-S-OFF-Tool
If you like this job Buy beer to me​
DONATE TO ME

Yay it's back I see you added the HTC_044 as well, hope it works :fingers-crossed:

Interesting, curious to try this but my x920d is a work phone...
If someone else with HTC_044 is successful I will bite the bullet

great you have added HTC__044 support )) downloading now but will try tomorrow i am so tired right now :S and of course i will report back..

not working for me

thank you so much!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
great works

Will test later, tq vm !
? Killx Kernel ?

Code:
C:\android\platform-tools>fastboot flash zip 1.41.firmware.zip
sending 'zip' (37101 KB)...
OKAY [ 2.882s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 11.575s
C:\android\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (813093 KB)...
OKAY [ 35.819s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[COLOR="Red"]FAILED (remote: 43 main version check fail)[/COLOR]
finished. total time: 139.592s
not works
my cid is htc044

Try this
These two into the folder
CWM recovery screen
The execution S-OFF - Error-43.cmd
From the start again, here you will get the error code 90
FAILED (remote: 90 hboot pre-update! Please flush image again immediately)
finished. total time: 11.575s
fastboot flash zip firmware.zip
Fixed
View attachment 1921945
mmcblk0p3

What about S-OFF for X920E , cid HTC_A07 ?

alwayskangel said:
Try this
These two into the folder
CWM recovery screen
The execution S-OFF - Error-43.cmd
From the start again, here you will get the error code 90
FAILED (remote: 90 hboot pre-update! Please flush image again immediately)
finished. total time: 11.575s
fastboot flash zip firmware.zip
View attachment 1918472
mmcblk0p3
Click to expand...
Click to collapse
I jus bought this phone I ain wan brick it don't u have a tool kit for this
Sent from my HTC_Amaze_4G using xda app-developers app

alwayskangel said:
Try this
These two into the folder
CWM recovery screen
The execution S-OFF - Error-43.cmd
From the start again, here you will get the error code 90
FAILED (remote: 90 hboot pre-update! Please flush image again immediately)
finished. total time: 11.575s
fastboot flash zip firmware.zip
View attachment 1918472
mmcblk0p3
Click to expand...
Click to collapse
thx i will try:victory:

aki0306 said:
Code:
C:\android\platform-tools>fastboot flash zip 1.41.firmware.zip
sending 'zip' (37101 KB)...
OKAY [ 2.882s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 11.575s
C:\android\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (813093 KB)...
OKAY [ 35.819s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[COLOR="Red"]FAILED (remote: 43 main version check fail)[/COLOR]
finished. total time: 139.592s
not works
my cid is htc044
Click to expand...
Click to collapse
My phone is HTC_621 and I get the same error
Sent from my HTC_Amaze_4G using xda app-developers app

daorderdillon said:
My phone is HTC_621 and I get the same error
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
The same method as

thank.
It work

aki0306 said:
thx i will try:victory:
Click to expand...
Click to collapse
This is valid for HTC__044 HTC__621
Forum in Taiwan has a lot of people to get S-OFF

alwayskangel said:
This is valid for HTC__044 HTC__621
Forum in Taiwan has a lot of people to get S-OFF
Click to expand...
Click to collapse
1.unlock bootloader
2.flash CWM
3.boot recovery
4.S-OFF Error-43
5.relock bootloader
6.flash 1.41.firmware and firmware
right????

hey, nub question.
Where can you see what HTC version you're on? like HTC_044 or something else.
i tried getvar and i couldn't see it there.
I'm on hboot 1.39.0000

big_me said:
hey, nub question.
Where can you see what HTC version you're on? like HTC_044 or something else.
i tried getvar and i couldn't see it there.
I'm on hboot 1.39.0000
Click to expand...
Click to collapse
Download "cid getter" application from play store. Your cid will be written at the top of the page.
Sent from my HTC Butterfly

i guess u have to have a stock rom

[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] First timer HTC User

I give up. I have a AT&T HTC ONE X and im rooted unlocked bootloader and superCID 111111111 and I tried to get S-Off but i get a file not found error. I want to change my cid back to the original att cid so i can run a 3.18 ruu. I heard running a 3.18 ruu with s-ON and superCID will Hard Brick your phone. How can i go back to normal before I tampered anything.
----TAMPERED----
----UNLOCKED----
HBOOT 2.14
Version 3.18
S-ON
CID 1111111

Which part of the s-off process gives you the file not found error?
Sent from my Evita

The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app

BloatedDuck404 said:
The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Soffbin has to go in your fastboot/adb folder. That's why it's not found
Sent from my HTC One XL using xda premium

BloatedDuck404 said:
The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Did you extract the zip before putting it into the adb folder?
Sent from my Evita

wrong folder??? I just copied and paste the commands into command prompt. Ill try moving the zip
******EDIT*******There is not fastboot adb folder on the phone.----- Oh the computer. No I did not unzip. Ill try to unzip

You didn't follow the instructions properly then. Read it carefully, and follow the instructions precisely.
Sent from my Evita

BloatedDuck404 said:
wrong folder??? I just copied and paste the commands into command prompt. Ill try moving the zip
******EDIT*******There is not fastboot adb folder on the phone.----- Oh the computer. No I did not unzip. Ill try to unzip
Click to expand...
Click to collapse
Feel like an idiot but now Operation is not permitted.

Can you copy and paste the lines from the command prompt in here? It'll give us a better idea of what's going on.
Sent from my Evita
---------- Post added at 12:00 AM ---------- Previous post was at 12:00 AM ----------
Also, do you have adb debugging enabled in developer options?
Sent from my Evita

http://forum.xda-developers.com/showthread.php?p=33189590
This should help you.
Sent from my HTC One X using xda premium

BTW now error 99 if I retry from scratch
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.093s]
finished. total time: 0.097s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip PJ8312000-One
X.zip
sending 'zip' (36064 KB)...
OKAY [ 2.590s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.858s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F50C4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x4940047
(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 CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT2ACW300425
(bootloader) command line length =719
(bootloader) active commandline: reset_status=0 board_elite.disable_uart3
(bootloader) =0 diag.enabled=0 board_elite.debug_uart=0 userdata_sel=0 an
(bootloader) droidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20
(bootloader) ats=0 androidboot.lb=1 td.sf=1 td.td=1 td.ofs=328 td.prd=1
(bootloader) td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=694 imc_online_log=
(bootloader) 0 androidboot.efuse_info=FFSL androidboot.baseband=0.24p.32
(bootloader) .09.06 androidboot.cid=CWS__001 androidboot.devicerev=3 andr
(bootloader) oidboot.batt_poweron=good_battery androidboot.carrier=ATT an
(bootloader) droidboot.mid=PJ8310
(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=reserve
(bootloader) aARM_Partion[C].name=radio
(bootloader) aARM_Partion[D].name=adsp
(bootloader) aARM_Partion[E].name=dsps
(bootloader) aARM_Partion[F].name=wcnss
(bootloader) aARM_Partion[10].name=radio_config
(bootloader) aARM_Partion[11].name=modem_st1
(bootloader) aARM_Partion[12].name=modem_st2
(bootloader) aARM_Partion[13].name=reserve
(bootloader) partition number=20
(bootloader) Valid partition num=20
(bootloader) setting_get_bootmode() = 9
(bootloader) ram size = 0
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): 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) Start Verify: 3
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:635526 msec
FAILED (status read failed (Too many links))
finished. total time: 6.420s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell chmod 744 /data/local/
tmp/soffbin3
Unable to chmod /data/local/tmp/soffbin3: Operation not permitted

Have a look on page 17 (I think) of the s-off thread, there is a fix for the error 99 problem posted by Chongodroid.
Sent from my Evita

kool im downloading viperXL 3.2.7 and ill follow his steps. Htc is so confusing but I love there devices. So risky. I cant thank you enough for taking time out of your day to help me

It's no problem at all. Let us know how it all goes.
Sent from my Evita

No go but I flashed a rom and got over my fear to do that. You know I got error 92 like it was suppose to do but since I did not unzip I couldnt proceed. BUT when I unzipped it and started over I got error 99. I want s-off so I can get rid of that red text (I see now that I flashed a rom),tampered, if I ever need to ruu withe superCID since im on 3.18 and ya know s-off stuff. But I guess my phone doesn't what to s-off. This is my first HTC android phone and Its been a scary ride. Thanks for your help anyway it was greatly appreciated. If ya got anymore suggestions ill try em. I stay with viper rom ATM.

Did you let viper boot after flashing? Or did you boot to the bootloader after flashing?
Sent from my Evita

No I rebooted to the bootloader. Didn't even let viper boot at all.
Sent from my HTC One X using xda app-developers app

And you still got error 99? Another trick to try after getting error 99 is to simulate a battery pull and start again.
To simulate a battery pull on this phone, hold power and volume down keys at the same time, the cap lights will start flashing, when the screen goes blank you can let go of the power key but keep holding volume down until it boots into the bootloader. Then start the s-off process again.
Sent from my Evita

OMFG YOU ARE THE BOMB IT WORKED!!!! Thanks for your help thanks soooooo much.

Awesome :thumbup:
Glad I could help
Sent from my Evita

[Q] Want to install Cyanogenmod 10.1 on my AT&T ONE X

I am new to this HTC version of rooting and installing custom recovery on phones. I previously did this to my Galaxy S3 and it all worked fine. I wanted to make sure i am following the correct instructions to root and be able to install cyanogenmod on my one x. I currently have the android version 4.0.4. Please let me know if all the links i have are correct. Really appreciate the help guys!!
1. Root the HTC one X
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit link
2. Install SuperCID
[TOOL] OneClick SuperCID for Unlocking Bootloader link
3. S-OFF
[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA link
4. Install TWRP http://forum.xda-developers.com/showthread.php?t=1677447
5. Follow the ROM installation procedure
Thanks...

hari04415 said:
I am new to this HTC version of rooting and installing custom recovery on phones. I previously did this to my Galaxy S3 and it all worked fine. I wanted to make sure i am following the correct instructions to root and be able to install cyanogenmod on my one x. I currently have the android version 4.0.4. Please let me know if all the links i have are correct. Really appreciate the help guys!!
1. Root the HTC one X
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit link
2. Install SuperCID
[TOOL] OneClick SuperCID for Unlocking Bootloader link
3. S-OFF
[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA link
4. Install TWRP http://forum.xda-developers.com/showthread.php?t=1677447
5. Follow the ROM installation procedure
Thanks...
Click to expand...
Click to collapse
Good steps but after s-off you should run the 3.18 ruu. Then flash twrp and your choosen rom.

DvineLord said:
Good steps but after s-off you should run the 3.18 ruu. Then flash twrp and your choosen rom.
Click to expand...
Click to collapse
Could you tell me how to install 3.18 RUU...any link would be much appreciated..thanks

Just download the 3.18 RUU, connect your phone to the PC in fastboot mode and run the RUU exe program. Just make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver/hibernation is turned off. You must have s-off before you run the RUU though.
Sent from my Evita

Thanks i will try it now!

Would I have to relock the boot loader before running the ruu? Fastboot OEM lock??
Sent from my HTC One XL using XDA Premium 4 mobile app

No, as long as you get s-off first you don't need to relock the bootloader.
Sent from my Evita

timmaaa said:
No, as long as you get s-off first you don't need to relock the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa, I am using a mac and i am in processing of finishing root method from the step 1 i posted earlier. I got the unlock_code.bin from htcdev but not sure what to do now. Do i go to terminal and use the fastboot from there or do i have to use the super CID link to unlock the bootloader?

You just need to follow the instructions at the htcdev, it's outlined pretty specifically.
Sent from my Evita

timmaaa said:
You just need to follow the instructions at the htcdev, it's outlined pretty specifically.
Sent from my Evita
Click to expand...
Click to collapse
I followed the step 1 correctly. Now in bootloader it says unlocked but when i try to run SuperCID it doesnt work. Tried both on mac and windows.

The 2.20 root exploit should give you SuperCID in order to unlock the bootloader. What does it say when you give the following command?
Code:
fastboot oem readcid
Sent from my Evita

timmaaa said:
The 2.20 root exploit should give you SuperCID in order to unlock the bootloader. What does it say when you give the following command?
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
it says 1111111
I have installed the SuperSU and repeated the procedure. This time around i was able to finish the procedure but i still have S-ON. Please help me get the S-OFF
Here is my cmd prompt
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
HT28SW301846 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip PJ8312000-One
X.zip
sending 'zip' (36064 KB)...
OKAY [ 2.652s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.753s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F9E3C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x4940047
(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 CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT28SW301846
(bootloader) commandline from head: console=ttyHSL0,115200,n8
(bootloader) command line length =699
(bootloader) active commandline: reset_status=0 board_elite.disable_uart3
(bootloader) =0 diag.enabled=0 board_elite.debug_uart=0 userdata_sel=0 an
(bootloader) droidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20
(bootloader) ats=0 androidboot.lb=1 td.td=1 td.sf=1 td.ofs=328 td.prd=1
(bootloader) td.dly=0 td.tmo=300 imc_online_log=0 androidboot.efuse_inf
(bootloader) o=FFSL androidboot.baseband=0.19as.32.09.11_2 androidboot.ci
(bootloader) d=CWS__001 androidboot.devicerev=3 androidboot.batt_poweron=
(bootloader) good_battery androidboot.carrier=ATT androidboot.mid=PJ83100
(bootloader) 00 androidboot.keyca
(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 90005000 (phy 90005000): 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:15253 msec
FAILED (status read failed (Too many links))
finished. total time: 7.362s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push soffbin3 /data/local/tm
p/
356 KB/s (4751 bytes in 0.012s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell chmod 744 /data/local/
tmp/soffbin3
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell su -c "/data/local/tmp
/soffbin3"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>

You need to stop posting the same thing in multiple places, duplicating posts is against the rules. I've answered you in the other thread.
Sent from my Evita

Stuck while flashing RUU [HTC logo with 4 triangles in corner]

Hello ,
Today I want test new rom but I get error in TWRP recovery can't mount system cache data I tried other recovery (4ext) same problem , wipe data system .... not succeed
I tried to flush a RUU (I flush this RUU version always in my phone with succeed ) after relock bootload S-ON I stuck in 39% I think it's stop in dzdata
know my phone stuck in black screen and HTC logo with 4 triangles in corner
Hboot just have RUU in yellow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
Thank for help .

popo020 said:
Hello ,
Today I want test new rom but I get error in TWRP recovery can't mount system cache data I tried other recovery (4ext) same problem , wipe data system .... not succeed
I tried to flush a RUU (I flush this RUU version always in my phone with succeed ) after relock bootload S-ON I stuck in 39% I think it's stop in dzdata
know my phone stuck in black screen and HTC logo with 4 triangles in corner
Hboot just have RUU in yellow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
Thank for help .
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588

Thank you for reply
but I have different problem in Hboot I don't have any option like fastboot/recovery/rest ...
I have only RUU with yellow color like in this image
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
please help

popo020 said:
Thank you for reply
but I have different problem in Hboot I don't have any option like fastboot/recovery/rest ...
I have only RUU with yellow color like in this image
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
please help
Click to expand...
Click to collapse
post it again
i can't see it
but i think you have stuck in ruu mode

This what I have in my HBOOT
=================================
*** 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
RUU
=================================
like in this picture
#remove space from link
Code:
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg

If I want flash anything by fastboot i get
Code:
FAILED (remote: 12 signature verify fail)

popo020 said:
If I want flash anything by fastboot i get
Code:
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
since you are relocked you are limited to fastboot commands
try this one
fastboot reboot bootloader
edit: by the way did you use any wipe option from TWRP ?

rzr86 said:
since you are relocked you are limited to fastboot commands
try this one
fastboot reboot bootloader
edit: by the way did you use any wipe option from TWRP ?
Click to expand...
Click to collapse
yep this is it start with this problem I use wipe from TWRP but didn't work so I decide go back to stock RUU and have this problem
Code:
fastboot reboot bootloader
back to same black screen with htc logo and 4 triangle

popo020 said:
yep this is it start with this problem I use wipe from TWRP but didn't work so I decide go back to stock RUU and have this problem
Code:
fastboot reboot bootloader
back to same black screen with htc logo and 4 triangle
Click to expand...
Click to collapse
you shouldn't use any wipe option from twrp
your system and data partitoin are corrupted probably
also you are stuck in ruu mode
try to flash the ruu manually
see how it goes
otherwise your only option is the thread i gave you in my previous post

Thank you again
but Bootloader can't find PG58IMG.zip in my SD card how can I flash the RUU manually
phone stuck in 39% when start system flashing

popo020 said:
Thank you again
but Bootloader can't find PG58IMG.zip in my SD card how can I flash the RUU manually
phone stuck in 39% when start system flashing
Click to expand...
Click to collapse
try with fastboot flash zip pg58img.zip

rzr86 said:
try with fastboot flash zip pg58img.zip
Click to expand...
Click to collapse
I got this error :crying:
Code:
FAILED (remote: 12 signature verify fail)

any help bro ?

At first you said you have relocked your bootloader in order to flash the RUU.You have not S-OFF so you are forbidden to use the recovery right now and probably you are stuck in RUU mode.
As long as you have "relocked" status you could unlock your bootloader again by using the command
Code:
fastboot oem unlock
or by flashing the Unlock_code.bin again
Code:
fastboot flash unlocktoken Unlock_code.bin
After those steps you should have access to bootloader again and you should be able to use recovery to correct (the possibly corrupted) partitions by using the guide that gave you rzr86.
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
It's a painful proccess but it is the only solution I can think right now.
---------- Post added at 03:53 AM ---------- Previous post was at 03:35 AM ----------
You could also check this guide out how to reformat a partition from recovery.(This guide is for HTC One and the /data partition number is probably not the same with the sensation /data partition number but I think it's a good start to read this solution)
---------- Post added at 04:06 AM ---------- Previous post was at 03:53 AM ----------
If you have access to recovery you can use adb shell to give the command
Code:
cat /proc/emmc
so you can see the numbers for every partition in your device.
You can also check this guide out.

for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work

popo020 said:
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
Click to expand...
Click to collapse
The first command doesn't always work but the unlocktoken should unlock your bootloader again.
If you use the command
Code:
fastboot reboot bootloader
after the flash of unlocktoken you should be able to see the bootloader on the next reboot.(If you can't just try to remove the battery for some time ,put it back in and press (power) + (vol-) to get the phone in bootloader mode.
Adb commands doesn't work on fastboot or RUU modes.You can only use adb by using a recovery with that capability or with a working rom.
Anyway...If nothing of them can help you you could try (by relocking your bootloader at first) to flash an extracted system.img from an RUU by using fastboot
Code:
fastboot flash system system.img
You should better try to erase data and cache partitions before you reboot and see if you have a working ROM.
Code:
fastboot erase userdata
fastboot erase cache
fastboot reboot

Thank you for reply , I have only the tow screens displayed exactly like the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And [VOL -] +[ POWER BUT ] give the black screen
I think unlocktoken need ROM installed for choosing between unlock or not
and all flash commands failed
Code:
FAILED (remote: 12 signature verify fail)
:crying:

popo020 said:
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
Click to expand...
Click to collapse
popo020 said:
Thank you for reply , I have only the tow screens displayed exactly like the image
And [VOL -] +[ POWER BUT ] give the black screen
I think unlocktoken need ROM installed for choosing between unlock or not
and all flash commands failed
Code:
FAILED (remote: 12 signature verify fail)
:crying:
Click to expand...
Click to collapse
As I saw in your first post here you are saying you have hboot 1.27 (probably from a command you gave in RUU mode)
Code:
fastboot getvar all
Now as I can see in the image your bootloader status seems to be 0.85 for the model ACE (HTC DESIRE HD).If this is an enginering HBOOT and you reverted to S-ON you probably breaked your device.I just don't get it!
HTC Desire HD HBOOT
HTC Sensation HBOOT
The sensation phones are PYRAMID models!
If it has to do with wrong flash you could try this guide.
But before you try anything give the command
Code:
fastboot getvar all
one more time and copy-paste everything here.

the image not from my phone I found it in the net , just to show you what look like
This what I have in my HBOOT
=================================
*** 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
RUU
=================================
and getVar All
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

If you cannot unlock your device from relocked status and you cannot flash anything to it I don't think I can help you further.You can always use varius tools like riffbox to repartition emmc chip or maybe to s-off your device (Too).
Are you apsolutely sure you tried to flash a signed system.img with relocked bootloader and it didn't flash??