Related
Hi all, try to be brief, but not simple:
First, I swear I've read many posts with cases similar to mine and I tried so many commands and tricks without success, so I decide to publish mine.
I have an HTC Inspire 4G, AT&T, rooted, S-off, and running Trickdroid. After a while I decided to return it to the original stock. However, when using the RUU utility, I got an error message and my phone it ruined.
Try to summarize as much as possible the conditions and the current situation:
Environments: Windows XP, Windows 7, Mac OS.
Power not work
Power + Vol Down do not work.
If I connect it to the outlet orante LED turn on, and charging it, but I must not press any buttons at all, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later.
I have access to fastboot commands, but not ADB. I tried to format the partitions, reflash, do recovery, recover partitions, etc, endless commands that do not give me a result.
The information obtained from the achievement of limited screen or fastboot commands is as follows:
ACE PVT HIP S-OFF RL
HBOOT-0.85.0019
MICROP-0438
RADIO-26.06.04.06_M
eMMC-BOOT
Dec 27 2012, 14:47:30
RUU
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0019
(bootloader) version-baseband: 26.06.04.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 2.47.502.7
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-9854d819
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.171s
fastboot oem boot
< waiting for device >
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D08BECC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x27E0E
(bootloader) TAG:hero panel = 0x830012
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(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: HT19VT207144
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =506
(bootloader) active commandline: board_spade.disable_uart2=0 board_spade.
(bootloader) usb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=true androidboot.baseband=26.06.04.06_M androidboot.cid
(bootloader) =CWS__001 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=ATT androidboot.mid=PD9812000 enable_zcharge=1 andro
(bootloader) idboot.keycaps=qwerty androidboot.mode=normal androidboot.se
(bootloader) rialno=HT19VT207144 androidboot.bootloader=0.85.0019 zygote_
(bootloader) oneshot=off kmemleak=off no_console_suspend=1
(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=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) Delay 98712(us) for dpram command before goto AMSS...
(bootloader) jump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:0 msec
FAILED (status read failed (Too many links))
finished. total time: 232.216s
I used the commands, among many others:
Fastboot oem boot
fastboot flash recovery recovery.img (or zip)
fastboot oem resetRUUflag
fastboot reboot -bootloader (this just turn the phone off)
fastboot oem get_identifier_token (answer: (bootloader) [ERR] Command error !!!)
fastboot format userdata
formatting 'userdata' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.020sfastboot format cache
formatting 'cache' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.017s
In many cases the response message in the command line is: remote no allowed
SD card formatted.
I have no access to the SD card from the phone connected.
Please tell me if there is any other way to recover my phone, or if it is just an expensive piece of nothing.
Thanks for everything.
What happened when you tried to flash recovery from fastboot?
bananagranola said:
What happened when you tried to flash recovery from fastboot?
Click to expand...
Click to collapse
./fastboot flash zip PD98IMG.zip
sending 'zip' (3619 KB)...
OKAY [ 0.623s]
writing 'zip'...
No more response, stuck there...
In many other commands (I just don't remember after trying several) I got the message "remote not allowed"
Frogzter said:
./fastboot flash zip PD98IMG.zip
sending 'zip' (3619 KB)...
OKAY [ 0.623s]
writing 'zip'...
No more response, stuck there...
In many other commands (I just don't remember after trying several) I got the message "remote not allowed"
Click to expand...
Click to collapse
That's because you need a recovery.img, not a PD98IMG.zip:
Code:
fastboot flash recovery recovery.img
bananagranola said:
That's because you need a recovery.img, not a PD98IMG.zip:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I got this:
./fastboot flash recovery r.img
sending 'recovery' (4456 KB)...
OKAY [ 0.764s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.771s
Why?
Click to expand...
Click to collapse
Is your phone in fastboot mode?
bananagranola said:
Is your phone in fastboot mode?
Click to expand...
Click to collapse
Yes, it is, or at least I think so, because the command fastboot devices, found my device, besides, the command fastboot getvarr all, also works...
No more responses guys?
Where are you getting the recovery? How are you putting your phone in fastboot? Are you running the command from the folder where the recovery is? Are you sure you are S-Off?
bananagranola said:
Where are you getting the recovery? How are you putting your phone in fastboot? Are you running the command from the folder where the recovery is? Are you sure you are S-Off?
Click to expand...
Click to collapse
Power button not work
Power + Vol Down not work either.
If I connect it to the outlet orange LED turn on, and charges the battery, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later, after this 10 minutes, if I connect via USB the device is responsive to fast boot devices command...
besides the screen shows:
ACE PVT HIP S-OFF RL
I have to command and the recovery file in the same folder
Er, what about the rest of my questions? How are you getting to fastboot with broken buttons? Is there an "adb reboot fastboot"?
Frogzter said:
Power button not work
Power + Vol Down not work either.
If I connect it to the outlet orange LED turn on, and charges the battery, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later, after this 10 minutes, if I connect via USB the device is responsive to fast boot devices command...
besides the screen shows:
ACE PVT HIP S-OFF RL
I have to command and the recovery file in the same folder
Click to expand...
Click to collapse
What RUU did you use?? that sounds like a messed bootloader....
bananagranola said:
Er, what about the rest of my questions? How are you getting to fastboot with broken buttons? Is there an "adb reboot fastboot"?
Click to expand...
Click to collapse
I don't do anything.. I can't... if I plug the usb cable and touch any button nothing happen but if just plug it and let the phone alone, after 20 minutes do to fastboot mode...
"adb devices" don't detect the device.. just "fastboot devices" does
glevitan said:
What RUU did you use?? that sounds like a messed bootloader....
Click to expand...
Click to collapse
Well, now I feel ashamed, I can't remember with one I used... I just google the last version, because I wanted to get back to the original rom...
I formatted the computer with MAC OS, Linux, Win 7 and Win XP, looking for fix it, so I don't have much trace of with one I used.
HTC INSPIRE. att cws_001 bootloader 2.00.0030 s-on
Same thing on mine except my phone never comes on but fastboot is the only thing that recognizes my phone with limited commands. when I do a faceboot devices I get this ☺ ⌠σ fastboot no serial numbers as it use to have. Phone will not turn on at all. while nothing plugged in no light or anything even when trying to power on or get to hboot no sign of life at all. When I plug it in I get solid orange light. Pc sees it as android usb devices - my htc. but stock rom exe dont find phone. this happened to me when I was using xlmultitool 2.1. I was tyring for s 0ff after the option to [5] Flash HBOOT S-OFF Unprotected (via adb) this is when my troubles started. cant flash anything to it. when I try to flash the stock rom I get error file to big. In need of help.......I do have a gold card....
C:\Android>fastboot flash zip PD98IMG_Inspire_S-ON_FactoryRestore_GB_1.07.zip.
sending 'zip' (315734 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 26.09.04.11_M2
(bootloader) version-cpld: ☺
(bootloader) version-microp: ☺
(bootloader) version-main: ♦
(bootloader) serialno: ☺ ⌠σ
(bootloader) imei: 3544550xxxxxxxx ......just sits here tells me nothing more
C:\Android>fastboot flash recover recovery.img
< waiting for device >
sending 'recover' (5532 KB)...
OKAY [ 0.624s]
writing 'recover'...
FAILED (remote: partition does not exist!)
finished. total time: 0.625s
C:\Android>fastboot flash system system.img
sending 'system' (571388 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.002s
C:\Android>fastboot oem boot
...
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.116s]
finished. total time: 0.117s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.008s
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 1.004s]
finished. total time: 1.005s
sorry to double post but its been about a year is there a fix for this please someone help....
wacky_35016 said:
sorry to double post but its been about a year is there a fix for this please someone help....
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.008s
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 1.004s]
finished. total time: 1.005s
Click to expand...
Click to collapse
Sounds like it's still s-on. Where did you get your Unlock_code.bin from? Have you tried using htc dev to get one or a new one?
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
Hi guys, i have been trying to restore my phone in the last ten days. It was stock, until someday it went in a bootloop. I changed the battery because i left it in a drawer for a while. I have tried everything i could find on the net, but nothing worked. At the moment, i don' t remember what i flashed lately, but it' s stuck in the white HTC screen with the green logo.
I tried ruu and now it shows:
Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012
When in fastboot :C:\adb>fastboot getvar all i get this:
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH16WV805444
INFOimei: 358313040178522
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3812mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
It cannot get in recovery.
Any ideas which way should i go? Or should i just give up and move to WP8 with a Nokia ?
Any help will be appreciated.
Jonnyvla said:
Hi guys, i have been trying to restore my phone in the last ten days. It was stock, until someday it went in a bootloop. I changed the battery because i left it in a drawer for a while. I have tried everything i could find on the net, but nothing worked. At the moment, i don' t remember what i flashed lately, but it' s stuck in the white HTC screen with the green logo.
I tried ruu and now it shows:
Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012
C:\adb>fastboot oem unlock
... INFO[ERR] Command error !!!
OKAY [ 0.022s]
finished. total time: 0.022s
C:\adb>m2sd cmdalvik enable
'm2sd' is not recognized as an internal or external command,
operable program or batch file.
When in fastboot :C:\adb>fastboot getvar all i get this:
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH16WV805444
INFOimei: 358313040178522
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 3812mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
C:\adb>
It cannot get in recovery.
Any ideas which way should i go? Or should i just give up and move to WP8 with a Nokia ?
Any help will be appreciated.
Click to expand...
Click to collapse
from bootloader if you choose recovery what does it show you?
Hi rzr86,
thank you for the quick reply. It goes again to the white screen with the green HTC logo. I tried flashing 4ext recovery from a thread in here through adb, but it does the same thing. Shows the white screen HTC and then boots again & again...
Jonnyvla said:
Hi rzr86,
thank you for the quick reply. It goes again to the white screen with the green HTC logo. I tried flashing 4ext recovery from a thread in here through adb, but it does the same thing. Shows the white screen HTC and then boots again & again...
Click to expand...
Click to collapse
try to flash a different recovery such as cwm or twrp
I tried flashing CWM, i got this in adb and when i tried to get in recovery mode i saw again the white screen, just like before.
C:\adb>fastboot flash recovery cwm-4.0.1.4-pyramid.img
sending 'recovery' (4724 KB)... OKAY [ 1.229s]
writing 'recovery'... OKAY [ 5.102s]
finished. total time: 6.334s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.273s]
finished. total time: 3.273s
In Hboot i get this message:
HBOOT
SD Checking...
Loading...[PG58DIAG.zip]
No image!
Loading...[PG58DIAG.nbh]
No image or wrong image!
Loading...[PG58IMG.zip]
No image!
Loading...[PG58IMG.nbh]
No image or wrong image!
Loading...[PG58IMG.tar]
No image!
Loading...[PG58IMG.aes]
No image!
Loading...[PG58IMG.enc]
I flashed Twrp recovery and when i try to get in i go back to the bootloop!
My SDcard is now formated, because i lost the last one and bought a new one 8GB.
Any hint which way i should follow?
Jonnyvla said:
I tried flashing CWM, i got this in adb and when i tried to get in recovery mode i saw again the white screen, just like before.
C:\adb>fastboot flash recovery cwm-4.0.1.4-pyramid.img
sending 'recovery' (4724 KB)... OKAY [ 1.229s]
writing 'recovery'... OKAY [ 5.102s]
finished. total time: 6.334s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.273s]
finished. total time: 3.273s
In Hboot i get this message:
HBOOT
SD Checking...
Loading...[PG58DIAG.zip]
No image!
Loading...[PG58DIAG.nbh]
No image or wrong image!
Loading...[PG58IMG.zip]
No image!
Loading...[PG58IMG.nbh]
No image or wrong image!
Loading...[PG58IMG.tar]
No image!
Loading...[PG58IMG.aes]
No image!
Loading...[PG58IMG.enc]
I flashed Twrp recovery and when i try to get in i go back to the bootloop!
My SDcard is now formated, because i lost the last one and bought a new one 8GB.
Any hint which way i should follow?
Click to expand...
Click to collapse
try to use a ruu.exe
http://fileom.com/v8xia7c0mn02/RUU_....24A.3504.31_M_release_266172_signed.exe.html
see here on how to use it
http://forum.xda-developers.com/showthread.php?t=1672425
don't worry you will remain on S-OFF
Hi, I have a very frustrating problem with my HTC One Mini.
Out of nowhere, my phone won't boot into the OS but goes straight into the bootloader.
This is what my bootloader looks like:
Code:
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2014, 15:21:25 0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can't perform a factory reset and I can't get into recovery either. I tried to unlock the phone so I could flash the recovery and install a ROM from there. So I went to htcdev.com and started the bootloader unlock process. I downloaded the Unlock_code.bin file and tried to flash the unlock token:
Code:
fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s
Nothing happens on the phone after this. I read on the forums I maybe had to run a RUU so I went to the HTC ROM download page and downloaded the RUU and ran it. The phone rebooted but didn't go into RUU mode. After some time, I get a USB Connection error (171).
I tried to get into RUU mode with fastboot but that also doesn't work.
Code:
fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 1.953s]
finished. total time: 1.953s
From here, I don't know what to do next and I hope you can help me.
Thanks in advance.
Welcome to the XDA forums, Vyperz52! I'm currently trying to solve a very similar problem with my HTC One Mini, and I have one suggestion that might help. Have you tried flashing some different form of recovery? Trying to flash TWRP recovery might work, it didn't for me but it's worth a try [https://twrp.me/devices/htconeminigsm.html]. Try the Fastboot install method (reading and accepting the risks that come with trying to install different recovery software).
imapanther said:
Welcome to the XDA forums, Vyperz52! I'm currently trying to solve a very similar problem with my HTC One Mini, and I have one suggestion that might help. Have you tried flashing some different form of recovery? Trying to flash TWRP recovery might work, it didn't for me but it's worth a try. Try the Fastboot install method (reading and accepting the risks that come with trying to install different recovery software).
Click to expand...
Click to collapse
Thank you for your reply.
I tried what you said but unfortunately, it's not working.
Code:
fastboot flash recovery twrp.img
target reported max download size of 800227328 bytes
sending 'recovery' (11460 KB)...
OKAY [ 1.500s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.424s
My phone is still locked so I think that's why flashing the recovery fails.
im also having problem with the bootloader unlock.
i have stuck in the 10th step of htcdev.com
any ideas why i cant see the warning on the phone?
btw the phone doesnt boot. i have access only to bootloader and fastboot on my phone
elessargr said:
im also having problem with the bootloader unlock.
i have stuck in the 10th step of htcdev.com
any ideas why i cant see the warning on the phone?
btw the phone doesnt boot. i have access only to bootloader and fastboot on my phone
Click to expand...
Click to collapse
I contacted HTC about the bootloader unlock issue but they won't help because they don't recommend unlocking the BL because it can cause the phone to crash and become unusable. After which I replied to them that's already the case without doing the unlock.
hi guys i got the same problem as you i m stuck on bootloader menu my phone looks like this
*** UNLOCKED ***
M4_UL PVT SHIP S-OFF RL
CID-HTC__102
HBOOT-2.22.0000
OS-4.09.401.3
eMMC-boot 1024MB
Jun 24 2014, 15:21:25 0
Click to expand...
Click to collapse
this what i got when i tried somes fastboot command
PHP:
C:\Android>fastboot flash zip cm12.zip
sending 'zip' (257726 KB)...
OKAY [ 11.875s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 11.969s
C:\Android>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.031s
C:\Android>fastboot flash recovery recovery14.img
sending 'recovery' (9320 KB)...
OKAY [ 1.234s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.391s
cant boot into recovery and cant flash it via fastboot
can someone help us to solve this issue
hi guys i have a problem the device stuck on bootloop ! i fix before an htc like that so am familiar with the steps but i need som help and files thx i will show the informations below !
**locked***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
OS-3.11.61.10
eMMC-BOOT 1024MB
NOV 7 2013.15:32.31.0
so guys plz what steps and ruu i need!
regards
same problem.
exactly the same and when i do the steps from HTCDEV.com my revice it not recognized.
SOMEONE HELP US??
guys i download RUU that match with my phone but when i enter :
fastboot>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(862): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.155s]
finished. total time: 0.156s
help thanks
benben85 said:
guys i download RUU that match with my phone but when i enter :
fastboot>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(862): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.155s]
finished. total time: 0.156s
help thanks
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
sending 'recovery' (5954 KB)...
OKAY [ 0.815s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.519s
everything is failed even to install recovery
?
As long as you are S-on, you can't flash recovery.
What file ending of the ruu you have, zip or exe?
old.splatterhand said:
As long as you are S-on, you can't flash recovery.
What file ending of the ruu you have, zip or exe?
Click to expand...
Click to collapse
i have this on .exe : RUU_K2_CL_JB422_SENSE50_MR_Sprint_WWE_Boost_3.05.653.4_R_Radio_1.12.50.0516_10.30.42.25_NV_NV_Boost_2.20_150_release_389346_signed
but i think is not what i need and the other is zip file : PL80IMG_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1_Radio__1.18.40a.00.05_10.81a.40.23L_release_338297_signed
so whats the solution please !
benben85 said:
i have this on .exe : RUU_K2_CL_JB422_SENSE50_MR_Sprint_WWE_Boost_3.05.653.4_R_Radio_1.12.50.0516_10.30.42.25_NV_NV_Boost_2.20_150_release_389346_signed
but i think is not what i need and the other is zip file : PL80IMG_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1_Radio__1.18.40a.00.05_10.81a.40.23L_release_338297_signed
so whats the solution please !
Click to expand...
Click to collapse
Both files are are not for your phone and won't flash. You need a Ruu for software number 3.11.61.10.
old.splatterhand said:
Both files are are not for your phone and won't flash. You need a Ruu for software number 3.11.61.10.
Click to expand...
Click to collapse
ok do you have one ruu that match with my phone !
benben85 said:
ok do you have one ruu that match with my phone !
Click to expand...
Click to collapse
i found this is a encrypted zip L80IMG_K2_UL_JB422_SENSE50_MR_Orange_UK_3.11.61.10_Radio_1.18.40a.00.05_10.81a.40.23_release_340236_signed
but when i type fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.198s]
finished. total time: 1.198s
and i dont get it into black htc screen is stuck on logo with white background !
help plz
benben85 said:
i found this is a encrypted zip L80IMG_K2_UL_JB422_SENSE50_MR_Orange_UK_3.11.61.10_Radio_1.18.40a.00.05_10.81a.40.23_release_340236_signed
but when i type fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.198s]
finished. total time: 1.198s
and i dont get it into black htc screen is stuck on logo with white background !
help plz
Click to expand...
Click to collapse
I don't have a Ruu for your phone, but the one you have could work.
Rename the zip file to PL80IMG.zip (make sure it is not named PL80IMG.zip.zip) and copy it in the external sdcard. Boot into the bootloader and let the phone recognize the zip. Confirm to update with vol+ and let it run until its finished.
old.splatterhand said:
I don't have a Ruu for your phone, but the one you have could work.
Rename the zip file to PL80IMG.zip (make sure it is not named PL80IMG.zip.zip) and copy it in the external sdcard. Boot into the bootloader and let the phone recognize the zip. Confirm to update with vol+ and let it run until its finished.
Click to expand...
Click to collapse
i renamed like you said the file but when i upgrading all the steps said 'FAIL-Pu'
eexcept [9] TP -OK
[10]SBL1 -bypass-s
[11] sbl1 -bypass -s
update fail in the end
what i can do
benben85 said:
i renamed like you said the file but when i upgrading all the steps said 'FAIL-Pu'
eexcept [9] TP -OK
[10]SBL1 -bypass-s
[11] sbl1 -bypass -s
update fail in the end
what i can do
Click to expand...
Click to collapse
I don't know. Maybe a bad download, not a full Ruu or something else.
You can try to unlock the bootloader with htcdev.com, flash twrp recovery and a rom.
old.splatterhand said:
I don't know. Maybe a bad download, not a full Ruu or something else.
You can try to unlock the bootloader with htcdev.com, flash twrp recovery and a rom.
Click to expand...
Click to collapse
i try to unlock the bootloader but its failed also ! it can be a bad emmc ?
Then i would say, you are out of luck and you should take a look for another phone.