[Q] facepalm s-off problem

rootntootn

Senior Member
Dec 28, 2011
125
21
0
I believe I did all the steps correctly but it did not seem to work. May have not done the 'immediate' step quickly enough (fastboot oem boot)? Anyway, i tried it a few more times again without success. I seemed to not be able to write the 3 files equired at the end specifically #2 + 3. Now it says it can't find my fastboot flash zip (I renamed mine soff.zip) but it is there...Thought I would give it and me space for a while before I try again. Anyone with any suggestions?
 

rootntootn

Senior Member
Dec 28, 2011
125
21
0
Pretty sure I extracted that but will double check, thanks..
Posting command file here as it did not work again...... I put the zip file and extracted in my working directory not the phone,is that correct? just occured to me that it may need to be on phone sd card anyway below is what got spit out, any help appreciated.




C:\adt-bundle-windows-x86\sdk\platform-tools>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *

C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.049s

C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot flash zip soff.zip
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
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: 3.595s

C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem boot
...
(bootloader) monarudo_vibrate_device_time(): vibrate 200(ms)...
(bootloader) Boot/Recovery signature checking...
(bootloader) TZ_HTC_SVC_HASH ret = 0
(bootloader) setup_tag addr=0x80600100 cmdline add=0x003147C8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x32401
(bootloader) TAG:hero panel = 0x94005B
(bootloader) TAG:engineerid = 0x0
(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::22222222
(bootloader) serial number: FA2BAS504674
(bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
(bootloader) .hardware=dlx user_debug=31
(bootloader) command line length =796
(bootloader) active commandline: poweron_status=1 reset_status=0 board_mo
(bootloader) narudo.disable_uart3=0 diag.enabled=0 board_monarudo.debug_u
(bootloader) art=0 userdata_sel=0 androidboot.emmc=true androidboot.pages
(bootloader) ize=2048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.s
(bootloader) f=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.
(bootloader) ofs=694 imc_online_log=0 androidboot.efuse_info=SNSL androi
(bootloader) dboot.baseband=1.00.00.1023_3 androidboot.cid=22222222 andro
(bootloader) idboot.devicerev=3 androidboot.batt_poweron=good_battery and
(bootloader) roidboot.carrier=COM
(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=extra
(bootloader) aARM_Partion[A].name=radio
(bootloader) aARM_Partion.name=adsp
(bootloader) aARM_Partion[C].name=dsps
(bootloader) aARM_Partion[D].name=radio_config
(bootloader) aARM_Partion[E].name=modem_st1
(bootloader) aARM_Partion[F].name=modem_st2
(bootloader) aARM_Partion[10].name=cdma_record
(bootloader) aARM_Partion[11].name=reserve
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) setting_get_bootmode() = 9
(bootloader) smem 8CF04000 (phy 8CF04000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
(bootloader) jump_to_kernel: machine_id(4060), tags_addr(0x80600100), ker
(bootloader) nel_addr(0x80608000)
(bootloader) -------------------hboot boot time:156503 msec
FAILED (status read failed (Too many links))
finished. total time: 2.904s

C:\adt-bundle-windows-x86\sdk\platform-tools>
 

rootntootn

Senior Member
Dec 28, 2011
125
21
0
I already see what's wrong..

When you

fastboot flash zip P8300000-DNA.ZIP

you flash that not the soffbin3 file the soffbin3 is for later

Sent from my HTC6435LVW using XDA Premium HD app
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
 

.torrented

Senior Member
Mar 7, 2011
2,789
1,484
0
29
www.cyanfox-rom.com
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in :) (i dont know the exact name so if i were you i would look it up)

if that doesnt work do a data factory reset in recovery and wipe both caches
 
  • Like
Reactions: rootntootn

rootntootn

Senior Member
Dec 28, 2011
125
21
0
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in :) (i dont know the exact name so if i were you i would look it up)

if that doesnt work do a data factory reset in recovery and wipe both caches
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below

sending 'zip' (36905 KB)...
OKAY [ 3.370s]
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: 3.595s


Is it possible I need stock kernal first?
 

CharliesTheMan

Senior Member
May 4, 2009
3,951
2,729
0
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below

sending 'zip' (36905 KB)...
OKAY [ 3.370s]
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: 3.595s


Is it possible I need stock kernal first?
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.

Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.

So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.

But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
 
  • Like
Reactions: rootntootn

rootntootn

Senior Member
Dec 28, 2011
125
21
0
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.

Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.

So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.

But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...