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

[ted77usa]

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

 

[Heisenberg]

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

 

[ted77usa]

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

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

 

[Heisenberg]

Uninstall Sync Manger but leave drivers installed.

Sent from my Evita

 

[ted77usa]

Uninstall Sync Manger but leave drivers installed.

Sent from my Evita

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

 

[area51avenger]

Use a different computer

Sent from my VENOMized HoxL

 

[ted77usa]

Use a different computer

Sent from my VENOMized HoxL

Did that too....using my wife laptop...my son laptop.....

Swyped From BlueICESense_JBE

 

[Heisenberg]

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

 

[ted77usa]

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

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

 

[Heisenberg]

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

 

[ted77usa]

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

Seem to me like.....somewhere inside there a script that somehow killed USB debugging .....after reboot

Swyped From BlueICESense_JBE

 

[Heisenberg]

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

 

[ted77usa]

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

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

 

[Heisenberg]

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

 

[ted77usa]

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

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.....

 

[Heisenberg]

Maybe you need to try another ROM.

Sent from my Evita

 

[ted77usa]

Solved.....s-off now

Maybe you need to try another ROM.

Sent from my Evita

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

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.

 

[Heisenberg]

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

 

[ted77usa]

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

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.....

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.

 

[Heisenberg]

No problems mate, I'm just glad it finally worked for you.

Sent from my Evita