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?

[Q] I cannot get S-Off no matter what I do.

I have SuperCID and rooted. What am I doing wrong?
C:\androidSDK\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\androidSDK\sdk\platform-tools>fastboot getvar cid
< waiting for device >
cid: 11111111
finished. total time: 0.002s
C:\androidSDK\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.082s]
finished. total time: 0.082s
C:\androidSDK\sdk\platform-tools>fastboot flash zip PJ8312000-OneX.zip
sending 'zip' (36064 KB)...
OKAY [ 2.859s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.992s
C:\androidSDK\sdk\platform-tools>fastboot oem boot
< waiting for device >
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F50C4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD0B
(bootloader) TAG:hero panel = 0x4940047
(bootloader) TAG:engineerid = 0x2
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is O2___102
(bootloader) setting->cid:2___102
(bootloader) serial number: HT26KW307917
(bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
(bootloader) .hardware=qcom
(bootloader) command line length =790
(bootloader) active commandline: poweron_status=1 reset_status=0 board_el
(bootloader) ite.disable_uart3=0 diag.enabled=0 board_elite.debug_uart=0
(bootloader) userdata_sel=0 androidboot.emmc=true androidboot.pagesize=20
(bootloader) 48 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.sf=1 td.td=1 td
(bootloader) .ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=69
(bootloader) 4 imc_online_log=0 androidboot.efuse_info=FFSL androidboot.
(bootloader) baseband=1.27a.32.45.28 androidboot.cid=O2___102 androidboot
(bootloader) .devicerev=0 androidboot.batt_poweron=good_battery androidbo
(bootloader) ot.carrier=O2-DE and
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=reserve
(bootloader) aARM_Partion[C].name=radio
(bootloader) aARM_Partion[D].name=adsp
(bootloader) aARM_Partion[E].name=dsps
(bootloader) aARM_Partion[F].name=wcnss
(bootloader) aARM_Partion[10].name=radio_config
(bootloader) aARM_Partion[11].name=modem_st1
(bootloader) aARM_Partion[12].name=modem_st2
(bootloader) aARM_Partion[13].name=reserve
(bootloader) partition number=20
(bootloader) Valid partition num=20
(bootloader) setting_get_bootmode() = 9
(bootloader) ram size = 0
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) Start Verify: 3
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:11787 msec
FAILED (status read failed (Too many links))
finished. total time: 6.224s
C:\androidSDK\sdk\platform-tools>adb push soffbin3 /data/local/tmp/
579 KB/s (4751 bytes in 0.008s)
C:\androidSDK\sdk\platform-tools>adb shell chmod 744 /data/local/tmp/soffbin3
C:\androidSDK\sdk\platform-tools>adb shell su -c "/data/local/tmp/soffbin3"
C:\androidSDK\sdk\platform-tools>adb reboot bootloader
C:\androidSDK\sdk\platform-tools>
Click to expand...
Click to collapse

It all looks like it's going through fine, some people have reported it taking a few tries for it to stick though.
Sent from my Evita

timmaaa said:
It all looks like it's going through fine, some people have reported it taking a few tries for it to stick though.
Sent from my Evita
Click to expand...
Click to collapse
I tried again. Now I'm getting "99 unknown fail"

What I did was to unplug at the black HTC screen after I got the error 99 and power off and started over. That was the only way I could update the firmware.
Sent from my HTC One XL using XDA Premium 4 mobile app

nickfury27 said:
I tried again. Now I'm getting "99 unknown fail"
Click to expand...
Click to collapse
When you get error 99, simulate a battery pull and start again.
Sent from my Evita

nickfury27 said:
I tried again. Now I'm getting "99 unknown fail"
Click to expand...
Click to collapse
When it originally failed did you flash again after it said failed flush image again immediately?
Sent from my HTC One XL using xda app-developers app

nickfury27 said:
I tried again. Now I'm getting "99 unknown fail"
Click to expand...
Click to collapse
I actually got that many times doing it on mine. when that came up i RUUd and tried again. got the first error then pushed it again and got it.

I think this is what happened to me. Read somewhere to wipe the cache a few times. Finally, finally it worked. Maybe for you too.
Sent from my One X using xda app-developers app

I've tried it a million times and I still can't get S-off. What am I suppose to do??

Are your subsequent attempts giving you error 92 or error 99 when flashing the zip?
Sent from my Evita

timmaaa said:
Are your subsequent attempts giving you error 92 or error 99 when flashing the zip?
Sent from my Evita
Click to expand...
Click to collapse
First it gives error 92. And every attempt after that gives error 99. I have to simulate a battery pull to get 92 again.

You've definitely extracted the soffbin zip into your fastboot folder? What ROM are you running while attempting it?
Sent from my Evita

timmaaa said:
You've definitely extracted the soffbin zip into your fastboot folder? What ROM are you running while attempting it?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I extracted soffbin. And I'm using Cyanoges Mod 10.2 Nightly.

You have given root access to adb in developer options?
You could try flashing a Sense ROM purely for this exercise, some people have claimed it works better on Sense. But for the record, I've gotten s-off on two devices, one on Sense and the other on aosp.
Sent from my Evita

timmaaa said:
You have given root access to adb in developer options?
You could try flashing a Sense ROM purely for this exercise, some people have claimed it works better on Sense. But for the record, I've gotten s-off on two devices, one on Sense and the other on aosp.
Sent from my Evita
Click to expand...
Click to collapse
Holy **** it worked! I've given root access to adb and that did it. I've been going crazy over this for a week. Thank you!

Glad to see you got it done.
Sent from my Evita

nickfury27 said:
Holy **** it worked! I've given root access to adb and that did it. I've been going crazy over this for a week. Thank you!
Click to expand...
Click to collapse
Can you write here for me how you did it in detail, please?

Amanbekov said:
Can you write here for me how you did it in detail, please?
Click to expand...
Click to collapse
Here is a detailed guide on how to get S-off. >>> http://forum.xda-developers.com/showthread.php?t=2155071
My problem was that I didn't enable the root access for ADB at developer options so at the last step I didn't grant root access. After enabling root access for ADB it asked for root rights at the last step and that did it.

nickfury27 said:
Here is a detailed guide on how to get S-off. >>> http://forum.xda-developers.com/showthread.php?t=2155071
My problem was that I didn't enable the root access for ADB at developer options so at the last step I didn't grant root access. After enabling root access for ADB it asked for root rights at the last step and that did it.
Click to expand...
Click to collapse
Many thanks to you, my friend! Unfortunately, I was bricked my AT&T HTC One X before I did all of that things and it can't load to Android, but it can load only in bootloader and in TWRP recovery, so I can't to do anything else with my brick =)) So, thank you very mach again and I'm sorry for my English! =)

That's not a brick if you can get to bootloader and recovery. Just flash a ROM.
Sent from my Evita

(SOLVED).......S-OFF_HTC one XL Driver

Hi guys....I'm just wondering if you guys know where I can find good htc one xl driver.....seem like my laptop sometime recognized the usb connection and automatic install the driver and sometime not......especially when I tried to do S-OFF.....right before entering 3 soffbin3 command after Android boot to OS......I always got error device not found after......usb debugging is checked before and unchecked after boot to Android OS.....and I read somewhere on thread that Android 4.2.2 for security purpose htc uncheck USB debugging after boot .....and then I went back to Android 4.0.3 sense 4 and same result....and I'm thinking is the driver might not installed properly......so any link and idea would appreciated......btw using window 7
C:\Android\android-sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android\android-sdk\platform-tools>fastoot oem readcid
'fastoot' is not recognized as an internal or external command,
operable program or batch file.
C:\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Android\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.064s]
finished. total time: 0.065s
C:\Android\android-sdk\platform-tools>fastboot flash zip PJ8312000-OneX.zip
sending 'zip' (36064 KB)...
OKAY [ 2.744s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.841s
C:\Android\android-sdk\platform-tools>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F6C9C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x940047
(bootloader) TAG:engineerid = 0x1
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT24DWXXXXXX
(bootloader) command line length =688
(bootloader) active commandline: poweron_status=32 reset_status=0 board_e
(bootloader) lite.disable_uart3=0 diag.enabled=0 board_elite.debug_uart=0
(bootloader) userdata_sel=0 androidboot.emmc=true androidboot.pagesize=2
(bootloader) 048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.sf=1 t
(bootloader) d.ofs=328 td.prd=1 td.dly=0 td.tmo=300 imc_online_log=0 and
(bootloader) roidboot.efuse_info=FFSL androidboot.baseband=0.18c.32.09.01
(bootloader) androidboot.cid=11111111 androidboot.devicerev=3 androidboo
(bootloader) t.batt_poweron=good_battery androidboot.carrier=ALL androidb
(bootloader) oot.mid=PJ8310000 androidboot.keycaps=qwerty androidboot.dq=
(bootloader) FAIL androidboot.mode=normal androidboot.serialno=HTXXXXXX
(bootloader) 93 androidboot.bootloader=1.09.0000 androidboot.nledhw=0 zyg
(bootloader) ote_oneshot=off kmemleak=off rpm_debug.enable=0
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=radio
(bootloader) aARM_Partion[C].name=adsp
(bootloader) aARM_Partion[D].name=dsps
(bootloader) aARM_Partion[E].name=wcnss
(bootloader) aARM_Partion[F].name=radio_config
(bootloader) aARM_Partion[10].name=modem_st1
(bootloader) aARM_Partion[11].name=modem_st2
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90006000 (phy 90006000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:11377 msec
FAILED (status read failed (Too many links))
finished. total time: 6.387s
C:\Android\android-sdk\platform-tools>adb push soffbin3 /data/local/tmp/
error: device not found
C:\Android\android-sdk\platform-tools>adb push soffbin3 /data/local/tmp/
error: device not found
Swyped From BlueICESense_JBE

The best way to get the latest drivers is to download the latest HTC Sync Manager from the HTC One XL page at HTC.com
Sent from my Evita

timmaaa said:
The best way to get the latest drivers is to download the latest HTC Sync Manager from the HTC One XL page at HTC.com
Sent from my Evita
Click to expand...
Click to collapse
I did that....And updated my htc driver installer from version 3 to version 4 or something.....do I need to keep htc sync manager or uninstall it after that?
Swyped From BlueICESense_JBE

Uninstall Sync Manger but leave drivers installed.
Sent from my Evita

timmaaa said:
Uninstall Sync Manger but leave drivers installed.
Sent from my Evita
Click to expand...
Click to collapse
I did that......same result.....error device not found......I just dunno what else to do.........btw.....I'm fine without S-OFF for now.... since I'm still on older hboot 1.09 and don't have reboot, wifi or signal what so ever on Android 4.2.2 sense 5 base ROM...... but would be awesome with S-OFF to complete mod.......
Swyped From BlueICESense_JBE

Use a different computer
Sent from my VENOMized HoxL

area51avenger said:
Use a different computer
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Did that too....using my wife laptop...my son laptop.....
Swyped From BlueICESense_JBE

Maybe it's a case of needing to download the latest Android SDK to ensure your adb is fully up to date. Or it could be as simple as using the rear usb port on your pc as opposed to the front usb port (may sound silly but it's worked for many people).
Sent from my Evita

timmaaa said:
Maybe it's a case of needing to download the latest Android SDK to ensure your adb is fully up to date. Or it could be as simple as using the rear usb port on your pc as opposed to the front usb port (may sound silly but it's worked for many people).
Sent from my Evita
Click to expand...
Click to collapse
Felt like something easy fix......like u said but I just dunno what else to do and I don't have PC......and i tried all four usb port from my laptop.....might have to use my brother PC but I dunno if he have all the Android sdk tool etc.....but I will try to update adb version via sdk manager tonight......:thumbup: Do you think twrp 2.6.3.0 have to do with it? But it work just fine for me flashing ROM, restoring back up...back and forth sense 4 and sense 5 Rom.....
Swyped From BlueICESense_JBE

I don't think the version of TWRP you're running matters, it doesn't come into the s-off process at all.
Sent from my Evita

timmaaa said:
I don't think the version of TWRP you're running matters, it doesn't come into the s-off process at all.
Sent from my Evita
Click to expand...
Click to collapse
Seem to me like.....somewhere inside there a script that somehow killed USB debugging .....after reboot
Swyped From BlueICESense_JBE

You need to check usb debugging in developer settings after the phone boots as I've instructed before, are you doing that?
Sent from my Evita

timmaaa said:
You need to check usb debugging in developer settings after the phone boots as I've instructed before, are you doing that?
Sent from my Evita
Click to expand...
Click to collapse
Yes and keep unchecked everytime after I got failed 92.....before pushing soffbin3 command.....and I did check it again and everytime.....that's y make me think somehow or sometime during booting to Android after failed 92 .....there is a script or command in my phone to uncheck USB debugging......but I doubt it ......just some thought
Swyped From BlueICESense_JBE

I don't that's the case, even if it did disable it on boot you can enable it once the phone boots.
Sent from my Evita

timmaaa said:
I don't that's the case, even if it did disable it on boot you can enable it once the phone boots.
Sent from my Evita
Click to expand...
Click to collapse
I did check it again after booted up.....and then when i enter first command adb push soffbin3 /data/local/tmp/ ........it said error....device not found and then i forced the phone coz im stuck on black htc screen using power button combo....sometime brought me back to bootloader.....and i started with second command from the beginning again .......fastboot oem rebootRUU but when the phone booted up to OS.....i used first command adb reboot bootloader but after that always same error device not found.....

Maybe you need to try another ROM.
Sent from my Evita

Solved.....s-off now
timmaaa said:
Maybe you need to try another ROM.
Sent from my Evita
Click to expand...
Click to collapse
SOLVED.....awesome....i figured it out.....:
1. Make sure to use android ICS ROM base coz JELLY BEAN base rom has a security feature that killed usb debugging during or after booting.
2. Check your android ADB version make sure 1.0.31 from cmd prompt navigate to your adb folder by pressing shift+right click and open cdm
3. Make sure u have all the htc driver install by installing htc sync manager ...it will update your htc driver installer and make sure to uninstall htc sync manager after that....just leave htc driver installer on your computer.
AWESOME....VERY APPRECIATED TIME AND HELP U GUYS GIVEN
Myrder said:
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Click to expand...
Click to collapse

Hmm, that's interesting. I've gotten s-off on two devices while on Jellybean. But at least you finally got it working.
Sent from my Evita

timmaaa said:
Hmm, that's interesting. I've gotten s-off on two devices while on Jellybean. But at least you finally got it working.
Sent from my Evita
Click to expand...
Click to collapse
Weird huh.....but like people said every phone is different...that's just what i did to my phone incase this might be useful for other xda member.....Just do alot of reading....and u might cross path with other people problem........READ....READ....AND READ.....:good: BTW TIM.....very appreciated for ur time.....i'm all out thanks....for today....more come to u tomorrow and other that help me.....
Myrder said:
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Click to expand...
Click to collapse

No problems mate, I'm just glad it finally worked for you.
Sent from my Evita

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

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

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

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

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

Thanks i will try it now!

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

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

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

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

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

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

timmaaa said:
The 2.20 root exploit should give you SuperCID in order to unlock the bootloader. What does it say when you give the following command?
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
it says 1111111
I have installed the SuperSU and repeated the procedure. This time around i was able to finish the procedure but i still have S-ON. Please help me get the S-OFF
Here is my cmd prompt
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
HT28SW301846 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip PJ8312000-One
X.zip
sending 'zip' (36064 KB)...
OKAY [ 2.652s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.753s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem boot
...
(bootloader) Boot/Recovery signature checking...
(bootloader) Boot/Recovery signature checking...
(bootloader) setup_tag addr=0x80400100 cmdline add=0xC02F9E3C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x2FD04
(bootloader) TAG:hero panel = 0x4940047
(bootloader) TAG:engineerid = 0x1
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT28SW301846
(bootloader) commandline from head: console=ttyHSL0,115200,n8
(bootloader) command line length =699
(bootloader) active commandline: reset_status=0 board_elite.disable_uart3
(bootloader) =0 diag.enabled=0 board_elite.debug_uart=0 userdata_sel=0 an
(bootloader) droidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20
(bootloader) ats=0 androidboot.lb=1 td.td=1 td.sf=1 td.ofs=328 td.prd=1
(bootloader) td.dly=0 td.tmo=300 imc_online_log=0 androidboot.efuse_inf
(bootloader) o=FFSL androidboot.baseband=0.19as.32.09.11_2 androidboot.ci
(bootloader) d=CWS__001 androidboot.devicerev=3 androidboot.batt_poweron=
(bootloader) good_battery androidboot.carrier=ATT androidboot.mid=PJ83100
(bootloader) 00 androidboot.keyca
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=fat
(bootloader) aARM_Partion[A].name=extra
(bootloader) aARM_Partion.name=radio
(bootloader) aARM_Partion[C].name=adsp
(bootloader) aARM_Partion[D].name=dsps
(bootloader) aARM_Partion[E].name=wcnss
(bootloader) aARM_Partion[F].name=radio_config
(bootloader) aARM_Partion[10].name=modem_st1
(bootloader) aARM_Partion[11].name=modem_st2
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) TZ_HTC_SVC_SET_DDR_MPU ret = 0
(bootloader) smem 90005000 (phy 90005000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_LOG_OPERATOR ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
(bootloader) jump_to_kernel: machine_id(3766), tags_addr(0x80400100), ker
(bootloader) nel_addr(0x80408000)
(bootloader) -------------------hboot boot time:15253 msec
FAILED (status read failed (Too many links))
finished. total time: 7.362s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push soffbin3 /data/local/tm
p/
356 KB/s (4751 bytes in 0.012s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell chmod 744 /data/local/
tmp/soffbin3
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell su -c "/data/local/tmp
/soffbin3"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>

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

[Q] Unable to re-lock bootloader, need help to flash RUU

Hello, I actually have a T-Mobile version of the HTC One m8 but that community seems dead and I haven't been able to find help to my problem. I am kind of getting desperate so I will tell you what I know. I have done my best to search for solutions and I feel as though I have exhausted almost every possible work around so that is why I look to you guys for help.
***Software status: Modified ***
***UNLOCKED***
MS_UL PVT SHIP S-ON
RADIO-1.22.213311491.08G
version-bootloader: 3.19.0.0000
version-main: (blank)
product: m8_ul
modelide: 0P6B13000
cidnum: T-MOB010
The issue is that the phone is in a boot loop status with an unresponsive operating system. Essentially, I cannot successfully maneuver around the file system and adjust/change settings because it is laggy/slow/unresponsive. Someone suggested to me that I flash an RUU but all attempts have failed. I cannot "re-lock" my bootloader either. When I try to do so I get the following error:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.232s
I could care less about loss of data (in fact I have everything backed up) but I just want my phone to work again either rooted/unrooted, locked/unlocked, or otherwise. Any willingness to help would be reciprocated with immense gratitude. Thank you for the time and consideration.

Pretty sure I can help you. Send me a pm I'll help u.

Look here:::> http://forum.xda-developers.com/showthread.php?t=3078889
Sent from my One M8 using XDA Premium 4 mobile app