Hello guys,
i'm in really big trouble with my new sensation xe.
As mentioned in the title i have bricked it after trying to re s-on my phone, the troubles started with the fact that i did not reflashed with a new stock rom but i hard-resetted the old one (that was still stock). I had successfully reset the CID to HTC__203 (this is the non branded sensation xe europe version right?) and then after a restart in fastboot i did "fastboot oem writesecureflag 3", command that went wrong becouse after a restart my sensation is completely bricked, whatever button i press the display remains black and even if i connect the battery charger the charge status led remains off.
Here are the last commands before the brick:
D:\android>fastboot oem writecid HTC__203
...
(bootloader) Start Verify: 0
(bootloader) erase sector 65504 ~ 65535 (32)
(bootloader) mipi_dsi_cmd_configanel_id=0x940021
(bootloader) width=540 height=960
(bootloader) mipi_dsi_cmd_configanel_id=0x940021
(bootloader) width=540 height=960
OKAY [ 0.183s]
finished. total time: 0.183s
D:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 3.322s]
finished. total time: 3.323s
D:\android>fastboot getvar cid
cid: HTC__203
finished. total time: 0.008s
D:\android>fastboot reboot
rebooting...
finished. total time: 1.674s
D:\android>adb reboot-bootloader
D:\android>fastboot oem writesecureflag 3
...
OKAY [ 0.065s]
finished. total time: 0.065s
D:\android>fastboot oem writesecureflag 3
...
(bootloader) pyramid_init_sd, SD card power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.134s]
finished. total time: 1.135s
D:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 1.789s]
finished. total time: 1.789s
D:\android>fastboot reboot-bootloader
< waiting for device >
Click to expand...
Click to collapse
The phone then was recognized as QHSUSB_DLOAD and after installing QHSUSB_Drivers_(x64) i see it as Qualcomm HS-USB QLDoader 9008 (COM6).
Now i read in various threads that in this state the phone can be managed by using QPST, so i installed it, but i have no idea on how to proceed.
If someone can please guide me we could turn up a very userful thread on how to unbrick phones after failed re s-on, I read several post where several users have experienced the same problem but never know if they have solved or the phone was sent assitance.
Thanks in advance and congratulations for your excellent work
I have the same issue with my sensation 4g,did u get any fox for this.
make a cwm nandroid backup. save file to pc. then flash an ruu and your good.
Oomike said:
make a cwm nandroid backup. save file to pc. then flash an ruu and your good.
Click to expand...
Click to collapse
my phone is not powering on and i'm unable to enter in to boot also.when i connect it to my pc in device manger its showing as "qualcomm hs-usb qdloader 9008"
so how can i go ahead now..
The same thing happen to me
can anyone help me please
the cid number you state is not the designated number for an xe device.
an EU xe device can have numerous cid
(depending on country and branded/unbranded)
htc__203 is an cid for an unbranded french htc device.
you should have chanced the cid number (better rememberd you old one), than flashed a stock rom that supports your cid and then at the end complete the s-on command.
can you get in fastboot? able to flash a ruu??
harish.toy said:
my phone is not powering on and i'm unable to enter in to boot also.when i connect it to my pc in device manger its showing as "qualcomm hs-usb qdloader 9008"
so how can i go ahead now..
Click to expand...
Click to collapse
Man, again I have t be the bearer if bad news...that code means that the phone is essentially bricked. It's a mode that I believe is meant for the factory workers to flash the phone for the first time. Something we cannot do here, yet.
Unless there has been some major advancement, there is nothing you can do short of asking htc to fix it for you. This seems to be the number one cause of bricks here...Going back to S-ON, which isn't all that necessary for warranty work anyways.
Matt
hello can someone help if i follow CID on http://forum.xda-developers.com/showthread.php?t=1192300
it don't work i get:
c:\abd>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.081s]
finished. total time: 1.081s
and this is what i get afther:
c:\abd>fastboot getvar cid
cid: T-MOB003
finished. total time: 0.002s
can someone help me plz ?
tnx
djwesleyman said:
hello can someone help if i follow CID on http://forum.xda-developers.com/showthread.php?t=1192300
it don't work i get:
c:\abd>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.081s]
finished. total time: 1.081s
and this is what i get afther:
c:\abd>fastboot getvar cid
cid: T-MOB003
finished. total time: 0.002s
can someone help me plz ?
tnx
Click to expand...
Click to collapse
Plz refer to this: http://forum.xda-developers.com/showthread.php?t=1459767
You just find what's your CID and d/load the compatible firmware......
djwesleyman said:
hello can someone help if i follow CID on http://forum.xda-developers.com/showthread.php?t=1192300
it don't work i get:
c:\abd>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.081s]
finished. total time: 1.081s
and this is what i get afther:
c:\abd>fastboot getvar cid
cid: T-MOB003
finished. total time: 0.002s
can someone help me plz ?
tnx
Click to expand...
Click to collapse
You have alot of guts posting this here. But nevertheless.
Did you follow the guide here(step 5) properly?
Cheers, Eager to help
my phone is already unlocked by HTC self ?
is that a problem ?
djwesleyman said:
hello can someone help if i follow CID on http://forum.xda-developers.com/showthread.php?t=1192300
it don't work i get:
c:\abd>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.081s]
finished. total time: 1.081s
and this is what i get afther:
c:\abd>fastboot getvar cid
cid: T-MOB003
finished. total time: 0.002s
can someone help me plz ?
tnx
Click to expand...
Click to collapse
after you write your CID to 11111111 you need to give the command fastboot reboot-bootloader then fastboot getvar cid and it should show the proper CID
casper200519 said:
after you write your CID to 11111111 you need to give the command fastboot reboot-bootloader then fastboot getvar cid and it should show the proper CID
Click to expand...
Click to collapse
then is still get this.
c:\abd>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.082s]
finished. total time: 1.082s
c:\abd>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.341s]
finished. total time: 3.342s
c:\abd>fastboot getvar cid
cid: T-MOB003
finished. total time: 0.002s
c:\abd>
Hi, First off this is posted in the wrong place. It should be in Q&A but they will move it for you (the moderators)
Second, it looks like your phone isn't even S-OFF. That command won't work unless it is.
HTC Unlocked isn't the same as Rooted S-OFF
djwesleyman said:
then is still get this.
c:\abd>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.082s]
finished. total time: 1.082s
c:\abd>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.341s]
finished. total time: 3.342s
c:\abd>fastboot getvar cid
cid: T-MOB003
finished. total time: 0.002s
c:\abd>
Click to expand...
Click to collapse
I know this might sound like a stupid question, but I must ask.... Do you have S-Off? It looks as it the bootloader is still S-ON which will stop you from being able to do anything in bootloader.
Didn't see the other post before I replied....
casper200519 said:
I know this might sound like a stupid question, but I must ask.... Do you have S-Off? It looks as it the bootloader is still S-ON which will stop you from being able to do anything in bootloader.
Didn't see the other post before I replied....
Click to expand...
Click to collapse
maybe a stupid qeustion but what is s-on or s-off ?
i am a noob in sensation but HD2 i know most of it xD
djwesleyman said:
maybe a stupid qeustion but what is s-on or s-off ?
i am a noob in sensation but HD2 i know most of it xD
Click to expand...
Click to collapse
HERE!
Follow the link and go step by step
I tried to change my cid from HTC__044 to 11111111.
But when I did the command fastboot oem writecid 11111111
It says:... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.109s]
finished. total time: 1.109s
But when I do fastboot getvar cid
It still says cid: HTC__044
What am I doing wrong or can somebody correct me? Thanks
htcsensationxeuser said:
I tried to change my cid from HTC__044 to 11111111.
But when I did the command fastboot oem writecid 11111111
It says:... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.109s]
finished. total time: 1.109s
But when I do fastboot getvar cid
It still says cid: HTC__044
What am I doing wrong or can somebody correct me? Thanks
Click to expand...
Click to collapse
Hi,
Were you in fastboot bootloader when you did this?
Also ,it may be worth trying again.
It does not always work first time.
htcsensationxeuser said:
I tried to change my cid from HTC__044 to 11111111.
But when I did the command fastboot oem writecid 11111111
It says:... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.109s]
finished. total time: 1.109s
But when I do fastboot getvar cid
It still says cid: HTC__044
What am I doing wrong or can somebody correct me? Thanks
Click to expand...
Click to collapse
Pop in the sdcard and try again... Also you should be soff for this
Edit: Ohh you have sdcard plugged in..
So that failure is because you don't have SOFF
Sent from my HTC Sensation 4G using xda premium
I do have S-OFF...
Edit: Just want to ask.. Why do we need sdcard to do SuperCID?
Sent from my Sensation using xda app-developers app
htcsensationxeuser said:
I do have S-OFF...
Edit: Just want to ask.. Why do we need sdcard to do SuperCID?
Sent from my Sensation using xda app-developers app
Click to expand...
Click to collapse
idk why sdcard is required ..but the process checks for it ..see this line in your output SD card power on ok
you have soff? and supercid failed?
can you post the complete output of this command (except IMEI)
fastboot getvar all
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
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 ?