Related
Hi Guys,
I've read through tons of posts and tried lots of things but my HTC Desire seems fairly bricked. Earlier I downloaded SPLHexEditor_111006.exe and created a hboot.nb0
I performed a fastboot flash hboot hboot.nb0 and it immediately rebooted to a black screen.
It's very frustrating as I can get into ADBShell and can get into Fastboot and run commands. I've tried flashing various roms and bits and pieces but I keep getting the same error when trying to re-flash a hboot.img:
sending 'hboot' (512 KB)... OKAY [ 0.089s]
writing 'hboot'... FAILED (remote: image update error)
If I perform a fastboot flash zip PB99IMG_stock.zip it runs through as follows
sending 'zip' (207 KB)... OKAY [ 0.045s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
FAILED (remote: 51 partition update fail)
finished. total time: 6.664s
So from what I can see I get a "remote: image update error" and "remote: 51 partition update fail". Before I started messing around I was using an alpharev.nl hboot. I just got 'greedy' thinking I could get better use of space with a custom hboot.
Interestingly if I reflash the hboot.nb0 I created it seems to 'work' in so far as not throwing up errors:
sending 'hboot' (512 KB)... INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
OKAY [ 0.216s]
writing 'hboot'... OKAY [ 0.185s]
finished. total time: 0.402s
...but then I reboot and the screen is still black and I can't 'reflash' either a full rom.zip or any of the hboot.img's from alpharev (which were okay before).
I did a nandroid backup and also have a colleagues Desire available to pull of a partition structure. I'm happy to manually edit the internal phone partitions if someone can advise me how?!
I did have S-Off before playing around trying to fix it - not sure if it is still S-Off or how I can check/ I'm also unsure how to check what the partition structure is at present internally.
Have I killed my phone or does the fact that I can run commands through adb shell and fastboot give me a chance to fix it? I've also got my CID and other relevant info from running a fastboot oem boot:
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
08BCBC
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is T-MOB005
INFOsetting.cid::T-MOB005
INFOserial number: HT09BPL00092
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =382
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFO0.02_2 androidboot.cid=T-MOB005 androidboot.carrier=TMUK and
INFOroidboot.mid=PB9920000 androidboot.keycaps=qwerty androidboo
INFOt.mode=normal androidboot.serialno=HT09BPL00092 androidboot.
INFObootloader=0.35.2017 no_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=crashdata
INFOpartition number=7
INFOValid partition num=7
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
FAILED (status read failed (Too many links))
finished. total time: 9.175s
If anyone can help I'll be hugely grateful!!!
Thanks!
Wrong SPL
I've been able to generate/extract a hboot.bin from my hboot and opening it in a text editor reveals it has a Passion SPL instead of the 8x50 SPL that appear in the hboot.img's of valid ROMs.
I know I've really messed up, but is there any way to fix the hboot issue please?
I have a hboot.bin I extracted from a friends working desire if that helps.
Please Help!
Output from fastboot commander v1.5 if it helps ....
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 7.35.5117.
Radio version: 4.06.00.02_2.
Main software version: 1.21.110.4.
cid: t-mob005.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: eng.
-----------------------------------.
Print of device info SUCCESSFUL.
Folks, This is not a joke anymore
The x920D S-off for your Pan Asia type Phone
I hope you like
This is a valid work
Support equipment x920d
HTC__044
HTC__621
HBOOT version
1.39.0000
1.40.0000
1.41.0000
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
Special thanks Onepagebook to Without him, there is no work
Thanks to the Android4tw.com
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
**If you need to post this article somewhere else, please give the credit as common courtesy
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 )
If you have an error
FAILED (remote: 43 main version check fail)
Use this program
http://forum.xda-developers.com/showpost.php?p=40800799&postcount=9
Click to expand...
Click to collapse
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
XDA S-OFF : original thread
http://forum.xda-developers.com/showthread.php?p=39792659
You must download the above thread the required soffbin3 file into the folder to continue
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..
Please keep in mind, do not stay in the old version of ROM but flash the one you like
Good luck and enjoy.
x920d-HTC__621-S-OFF-Tool
x920d-HTC__044-S-OFF-Tool
If you like this job Buy beer to me
DONATE TO ME
Yay it's back I see you added the HTC_044 as well, hope it works :fingers-crossed:
Interesting, curious to try this but my x920d is a work phone...
If someone else with HTC_044 is successful I will bite the bullet
great you have added HTC__044 support )) downloading now but will try tomorrow i am so tired right now :S and of course i will report back..
not working for me
thank you so much!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
great works
Will test later, tq vm !
? Killx Kernel ?
Code:
C:\android\platform-tools>fastboot flash zip 1.41.firmware.zip
sending 'zip' (37101 KB)...
OKAY [ 2.882s]
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 immediately)
finished. total time: 11.575s
C:\android\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (813093 KB)...
OKAY [ 35.819s]
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) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[COLOR="Red"]FAILED (remote: 43 main version check fail)[/COLOR]
finished. total time: 139.592s
not works
my cid is htc044
Try this
These two into the folder
CWM recovery screen
The execution S-OFF - Error-43.cmd
From the start again, here you will get the error code 90
FAILED (remote: 90 hboot pre-update! Please flush image again immediately)
finished. total time: 11.575s
fastboot flash zip firmware.zip
Fixed
View attachment 1921945
mmcblk0p3
What about S-OFF for X920E , cid HTC_A07 ?
alwayskangel said:
Try this
These two into the folder
CWM recovery screen
The execution S-OFF - Error-43.cmd
From the start again, here you will get the error code 90
FAILED (remote: 90 hboot pre-update! Please flush image again immediately)
finished. total time: 11.575s
fastboot flash zip firmware.zip
View attachment 1918472
mmcblk0p3
Click to expand...
Click to collapse
I jus bought this phone I ain wan brick it don't u have a tool kit for this
Sent from my HTC_Amaze_4G using xda app-developers app
alwayskangel said:
Try this
These two into the folder
CWM recovery screen
The execution S-OFF - Error-43.cmd
From the start again, here you will get the error code 90
FAILED (remote: 90 hboot pre-update! Please flush image again immediately)
finished. total time: 11.575s
fastboot flash zip firmware.zip
View attachment 1918472
mmcblk0p3
Click to expand...
Click to collapse
thx i will try:victory:
aki0306 said:
Code:
C:\android\platform-tools>fastboot flash zip 1.41.firmware.zip
sending 'zip' (37101 KB)...
OKAY [ 2.882s]
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 immediately)
finished. total time: 11.575s
C:\android\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (813093 KB)...
OKAY [ 35.819s]
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) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[COLOR="Red"]FAILED (remote: 43 main version check fail)[/COLOR]
finished. total time: 139.592s
not works
my cid is htc044
Click to expand...
Click to collapse
My phone is HTC_621 and I get the same error
Sent from my HTC_Amaze_4G using xda app-developers app
daorderdillon said:
My phone is HTC_621 and I get the same error
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
The same method as
thank.
It work
aki0306 said:
thx i will try:victory:
Click to expand...
Click to collapse
This is valid for HTC__044 HTC__621
Forum in Taiwan has a lot of people to get S-OFF
alwayskangel said:
This is valid for HTC__044 HTC__621
Forum in Taiwan has a lot of people to get S-OFF
Click to expand...
Click to collapse
1.unlock bootloader
2.flash CWM
3.boot recovery
4.S-OFF Error-43
5.relock bootloader
6.flash 1.41.firmware and firmware
right????
hey, nub question.
Where can you see what HTC version you're on? like HTC_044 or something else.
i tried getvar and i couldn't see it there.
I'm on hboot 1.39.0000
big_me said:
hey, nub question.
Where can you see what HTC version you're on? like HTC_044 or something else.
i tried getvar and i couldn't see it there.
I'm on hboot 1.39.0000
Click to expand...
Click to collapse
Download "cid getter" application from play store. Your cid will be written at the top of the page.
Sent from my HTC Butterfly
i guess u have to have a stock rom
I give up. I have a AT&T HTC ONE X and im rooted unlocked bootloader and superCID 111111111 and I tried to get S-Off but i get a file not found error. I want to change my cid back to the original att cid so i can run a 3.18 ruu. I heard running a 3.18 ruu with s-ON and superCID will Hard Brick your phone. How can i go back to normal before I tampered anything.
----TAMPERED----
----UNLOCKED----
HBOOT 2.14
Version 3.18
S-ON
CID 1111111
Which part of the s-off process gives you the file not found error?
Sent from my Evita
The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app
BloatedDuck404 said:
The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Soffbin has to go in your fastboot/adb folder. That's why it's not found
Sent from my HTC One XL using xda premium
BloatedDuck404 said:
The very end where you put in the chmod command for soffbin3 it says can't chmod file or directory doesn't exsist. But when I use es file explorer to look in /Data/local/tmp the soffbin3 file is there
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Did you extract the zip before putting it into the adb folder?
Sent from my Evita
wrong folder??? I just copied and paste the commands into command prompt. Ill try moving the zip
******EDIT*******There is not fastboot adb folder on the phone.----- Oh the computer. No I did not unzip. Ill try to unzip
You didn't follow the instructions properly then. Read it carefully, and follow the instructions precisely.
Sent from my Evita
BloatedDuck404 said:
wrong folder??? I just copied and paste the commands into command prompt. Ill try moving the zip
******EDIT*******There is not fastboot adb folder on the phone.----- Oh the computer. No I did not unzip. Ill try to unzip
Click to expand...
Click to collapse
Feel like an idiot but now Operation is not permitted.
Can you copy and paste the lines from the command prompt in here? It'll give us a better idea of what's going on.
Sent from my Evita
---------- Post added at 12:00 AM ---------- Previous post was at 12:00 AM ----------
Also, do you have adb debugging enabled in developer options?
Sent from my Evita
http://forum.xda-developers.com/showthread.php?p=33189590
This should help you.
Sent from my HTC One X using xda premium
BTW now error 99 if I retry from scratch
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: device not found
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.093s]
finished. total time: 0.097s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip PJ8312000-One
X.zip
sending 'zip' (36064 KB)...
OKAY [ 2.590s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.858s
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=0xC02F50C4
(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: HT2ACW300425
(bootloader) command line length =719
(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.sf=1 td.td=1 td.ofs=328 td.prd=1
(bootloader) td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=694 imc_online_log=
(bootloader) 0 androidboot.efuse_info=FFSL androidboot.baseband=0.24p.32
(bootloader) .09.06 androidboot.cid=CWS__001 androidboot.devicerev=3 andr
(bootloader) oidboot.batt_poweron=good_battery androidboot.carrier=ATT an
(bootloader) droidboot.mid=PJ8310
(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:635526 msec
FAILED (status read failed (Too many links))
finished. total time: 6.420s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell chmod 744 /data/local/
tmp/soffbin3
Unable to chmod /data/local/tmp/soffbin3: Operation not permitted
Have a look on page 17 (I think) of the s-off thread, there is a fix for the error 99 problem posted by Chongodroid.
Sent from my Evita
kool im downloading viperXL 3.2.7 and ill follow his steps. Htc is so confusing but I love there devices. So risky. I cant thank you enough for taking time out of your day to help me
It's no problem at all. Let us know how it all goes.
Sent from my Evita
No go but I flashed a rom and got over my fear to do that. You know I got error 92 like it was suppose to do but since I did not unzip I couldnt proceed. BUT when I unzipped it and started over I got error 99. I want s-off so I can get rid of that red text (I see now that I flashed a rom),tampered, if I ever need to ruu withe superCID since im on 3.18 and ya know s-off stuff. But I guess my phone doesn't what to s-off. This is my first HTC android phone and Its been a scary ride. Thanks for your help anyway it was greatly appreciated. If ya got anymore suggestions ill try em. I stay with viper rom ATM.
Did you let viper boot after flashing? Or did you boot to the bootloader after flashing?
Sent from my Evita
No I rebooted to the bootloader. Didn't even let viper boot at all.
Sent from my HTC One X using xda app-developers app
And you still got error 99? Another trick to try after getting error 99 is to simulate a battery pull and start again.
To simulate a battery pull on this phone, hold power and volume down keys at the same time, the cap lights will start flashing, when the screen goes blank you can let go of the power key but keep holding volume down until it boots into the bootloader. Then start the s-off process again.
Sent from my Evita
OMFG YOU ARE THE BOMB IT WORKED!!!! Thanks for your help thanks soooooo much.
Awesome :thumbup:
Glad I could help
Sent from my Evita
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
I got in deep trouble.
I got S-on 'ed Relocked and Tampered.
Can get into recovery but fastboot works. Recovery mode will auto reboot once then stuck at HTC logo.
Tried RUU zip got 43 error
ADB not working in all 3 of my pc USB not recognised but fastboot works.
I'm trying to get back to stock but kinda hard to find any thing that works for me.
DELUXE_UB1 PVT SHIP S-ON
Hboot 1.41
Radio 3A.24.306.14
OPENDSP v6.120.274.0114
eMMC-boot
CID___044
anything else I can try?
INFOBoot/Recovery signature checking...
INFOTZ_HTC_SVC_HASH ret = 0
INFOsetup_tag addr=0x80600100 cmdline add=0x00324EB8
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x32E03
INFOTAG:hero panel = 0x940063
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x1
INFODevice CID is not super CID
INFOCID is HTC__044
INFOsetting->cid::HTC__044
INFOserial number: xxxx
INFOcommandline from head: console=ttyHSL0,115200,n8 androidboot
INFO.hardware=dlxub1 user_debug=31
INFOcommand line length =824
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=#000
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.24.306.14 androidboot.cid=HTC
INFO__044 androidboot.devicerev=3 color_ID=RED00 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
INFOStart Verify: 3
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:91034 msec
FAILED (status read failed (Too many links))
finished. total time: 3.063s
antlvk said:
INFOBoot/Recovery signature checking...
INFOTZ_HTC_SVC_HASH ret = 0
INFOsetup_tag addr=0x80600100 cmdline add=0x00324EB8
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x32E03
INFOTAG:hero panel = 0x940063
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x1
INFODevice CID is not super CID
INFOCID is HTC__044
INFOsetting->cid::HTC__044
INFOserial number: xxxx
INFOcommandline from head: console=ttyHSL0,115200,n8 androidboot
INFO.hardware=dlxub1 user_debug=31
INFOcommand line length =824
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=#000
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.24.306.14 androidboot.cid=HTC
INFO__044 androidboot.devicerev=3 color_ID=RED00 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
INFOStart Verify: 3
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:91034 msec
FAILED (status read failed (Too many links))
finished. total time: 3.063s
Click to expand...
Click to collapse
Nithig wrong with the phone jus unlock the boot loader again
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
daorderdillon said:
Nithig wrong with the phone jus unlock the boot loader again
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tried unlock using htcdev i just hangs there.
antlvk said:
tried unlock using htcdev i just hangs there.
Click to expand...
Click to collapse
Look for the pan asia s off process and download it for your cid
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
daorderdillon said:
Look for the pan asia s off process and download it for your cid
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
Click to expand...
Click to collapse
also done
fastboot flash zip 1.41.firmware.zip success
fastboot flash zip firmware.zip (FAILED (remote: 43 main version check fail)) can't find mmcblk0p3 tile to download either
after that all step failed who has mmcblk0p3 file? what is that file does?
anyone?
antlvk said:
anyone?
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=9390288116658475218 use this ruu
Add me to gtalk [email protected]
http://forum.xda-developers.com/showthread.php?t=1672425
[GUIDE]RUU related info (Extracting rom.zip, Restoring stock, going back S-ON, etc.)
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
my x920d is back.... from warranty... wonder how they restore my phone?