Database Info

HTC Inspire 4g AT&T useless

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.020s​fastboot 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?

It's not a dream for x920D to get S-off even @ hboot 1.41

Folks, This is not a joke anymore
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
Thanks to the Android4tw.com
**If you need to post this article somewhere else, please give the credit as common courtesy
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
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 )
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
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..
Good luck and enjoy.
x920d-HTC__621-S-OFF-Tool
If you like this job
Buy beer to my brother
DONATE Onepagebook

r0x!
Thank bro

now you guys will be happy for sure,
Nice one bro..be sure you guys all get this done lol

Onepagebook said:
now you guys will be happy for sure,
Nice one bro..be sure you guys all get this done lol
Click to expand...
Click to collapse
You should sleep ........

It has more "failed" than "successful". Are you sure it is working?
Sent from my HTC Butterfly

Deadly Sto(R)m said:
It has more "failed" than "successful". Are you sure it is working?
Sent from my HTC Butterfly
Click to expand...
Click to collapse
i found cidnum: HTC__621
1.41.firmware/android-info.txt
i don't think i can flash this..

it2007me said:
i found cidnum: HTC__621
1.41.firmware/android-info.txt
i don't think i can flash this..
Click to expand...
Click to collapse
What does it mean?
Sent from my HTC Butterfly

it2007me said:
i found cidnum: HTC__621
1.41.firmware/android-info.txt
i don't think i can flash this..
Click to expand...
Click to collapse
Is the only work in HTC__621
If your device is not it certainly does not work

alwayskangel said:
Is the only work in HTC__621
If your device is not it certainly does not work
Click to expand...
Click to collapse
So wait and see...
Sent from my HTC Butterfly

alwayskangel said:
Is the only work in HTC__621
If your device is not it certainly does not work
Click to expand...
Click to collapse
Ok, let the hacking begin
Edit:
stuck at : FAILED (remote: 42 custom id check fail)

I will try it.
[Edit] I can't, my CID is HTC__044

I think, this is S-Off for TW, we need supercid for hboot 1.40 or 1.41 ..

Is this not working for anyone else?
Sent from my HTC Butterfly using xda premium

my cid is htc044
need a sbl2 non protect rom
---------- Post added at 08:27 PM ---------- Previous post was at 08:14 PM ----------
it2007me said:
I think, this is S-Off for TW, we need supercid for hboot 1.40 or 1.41 ..
Click to expand...
Click to collapse
flashed firmware.zip is for htc_asia_tw rom
if we get the sbl2 non protected rom
i think we get the s-off!

Mine is htc__621,will try it later, outside now
Sent from my HTC Butterfly using Tapatalk 2

Deadly Sto(R)m said:
It has more "failed" than "successful". Are you sure it is working?
Sent from my HTC Butterfly
Click to expand...
Click to collapse
so ? tons of folks in our country tried and it works
if you doubt it then just don't try it.
so many failed message means that's the way to prove the process is way correct
if you don't see that failed message , emans you're screwed.

it2007me said:
I think, this is S-Off for TW, we need supercid for hboot 1.40 or 1.41 ..
Click to expand...
Click to collapse
I come from Taiwan
Of course, making TW device priority
I will try to make equipment to WWE
I'm not sure but I will try to

alwayskangel said:
I come from Taiwan
Of course, making TW device priority
I will try to make equipment to WWE
I'm not sure but I will try to
Click to expand...
Click to collapse
that true bro, thanks for your hard work, really appreciate it :good: :good:

it2007me said:
Ok, let the hacking begin
Edit:
stuck at : FAILED (remote: 42 custom id check fail)
Click to expand...
Click to collapse
i am having the same issue so what is next.?

Awesome, I will try and report it, thanks for you great job

[Q] help needed : no network then auto restart.

Hi Senior,
My butterfly is facing no network then auto restart problem.
1 day could happen 3-4 times.
i try to flash lastest asia RUU.zip provided in this section but failed.
Results :
sending 'zip' (824265 KB)...
OKAY [ 38.386s]
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) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 142.123s
My butterly is unlocked and TWRP installed. Flashed BOA 8.2
But i have relock my bootloader b 4 i flash the RUU. yet still facing the fails.
Any help is appreciated.
Thank you in advance.

htc one sv bootloop help plz !

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.

why nobody helping me i need help

i flashed my a9 with SenseO V0,4 my firmware is 1.10 and the rom need 1.56
now my phone is only works with cm roms like mokee
i need a solution i tried to relock bootloader and flash stock ruu zips with the same cid not work
the names of the ruu i tried
2PQ9IMG_HIA[email protected]51002.3_29.05_F_release_454007_combined_signed
2PQ9IMG_HIA_AER[email protected]60122.4_43.05_F_release_469200_signed
i get the same error
C:\adb>fastboot flash zip rom.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (126573 KB)...
OKAY [ 8.751s]
writing 'zip'...
(bootloader) HOSD CL#635503
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 9.765s
my cid information
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) imei: 352636073422391
(bootloader) version-main: 1.10.401.7
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: HTC__J15
all:
finished. total time: 0.021s
please help i want to flash SenseO V0,4 or stock rom i hated stuck on cm roms

please try first: rename 2PQ9IMG_HIA_AERO_UHL_M60_SENSE7GP_MR_HTC_Europe_1. [email protected]_43.05_F_relea se_469200_signed
to 2PQ9IMG.img and put it to an SD-Card (first level, not into a folder) - plug in this sd-card.
If you boot into download-mode you will be asked if you want to flash this RUU. Volume up to start flashing.
Please report (do not write just error)

JochenP said:
please try first: rename 2PQ9IMG_HIA_AERO_UHL_M60_SENSE7GP_MR_HTC_Europe_1. [email protected]_43.05_F_relea se_469200_signed
to 2PQ9IMG.img and put it to an SD-Card (first level, not into a folder) - plug in this sd-card.
If you boot into download-mode you will be asked if you want to flash this RUU. Volume up to start flashing.
Please report (do not write just error)
Click to expand...
Click to collapse
thanks pro solved
i was flashing 2PQ9IMG.zip in relocked bootlader i try flashed after reunlock bootloader and its work now thanks for helping