S-off - Fail


  1. Altaone

    Altaone Well-Known Member

    This is what happened when I tried S-off.

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fas
    tboot devices
    HT24MW403861 fastboot

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fas
    tboot oem rebootRUU
    ...
    (bootloader) Start Verify: 3
    OKAY [ 0.062s]
    finished. total time: 0.062s

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fas
    tboot flash zip PJ4011000-OneS.zip
    < waiting for device >
    sending 'zip' (36215 KB)...
    OKAY [ 2.449s]
    writing 'zip'...
    (bootloader) adopting the signature contained in this image...
    FAILED (remote: 92 supercid! please flush image again immediately)
    finished. total time: 2.558s

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fas
    tboot oem boot
    ...
    (bootloader) Boot/Recovery signature checking...
    (bootloader) Boot/Recovery signature checking...
    (bootloader) setup_tag addr=0x80400100 cmdline add=0xC02E0654
    (bootloader) TAG:Ramdisk OK
    (bootloader) TAG:skuid 0x2ED01
    (bootloader) TAG:hero panel = 0x2940043
    (bootloader) TAG:engineerid = 0x0
    (bootloader) TAG: PS ID = 0x0
    (bootloader) TAG: Gyro ID = 0x0
    (bootloader) Device CID is super CID
    (bootloader) CID is super CID
    (bootloader) Backup CID is empty
    (bootloader) setting->cid::11111111
    (bootloader) serial number: HT24MW403861
    (bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
    (bootloader) .hardware=qcom
    (bootloader) command line length =762
    (bootloader) active commandline: poweron_status=1 reset_status=0 board_vi
    (bootloader) lle.disable_uart3=0 diag.enabled=0 board_ville.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.td=1 td.sf=1 td
    (bootloader) .ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=632 un.ofs=69
    (bootloader) 8 imc_online_log=0 androidboot.efuse_info=FFSL androidboot.
    (bootloader) baseband=1.13.50.05.25 androidboot.cid=11111111 androidboot.
    (bootloader) devicerev=3 androidboot.batt_poweron=good_battery androidboo
    (bootloader) t.carrier=ALL androi
    (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(3751), tags_addr(0x80400100), ker
    (bootloader) nel_addr(0x80408000)
    (bootloader) -------------------hboot boot time:26920 msec
    FAILED (status read failed (Too many links))
    finished. total time: 5.741s

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb
    push soffbin3 /data/local/tmp/
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    failed to copy 'soffbin3' to '/data/local/tmp/': Is a directory

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb
    shell
    ~ # &#8592;[6nls
    ls
    cache init.rc sdcard
    data initlogo.rle supersu
    default.prop internal_sdcard sys
    dev mtdcache system
    devlog proc tmp
    etc res ueventd.goldfish.rc
    fstab.qcom root ueventd.rc
    init sbin
    ~ # &#8592;[6ncd data
    cd data
    /data # &#8592;[6nls
    ls
    data local
    /data # &#8592;[6ncd local
    cd local
    /data/local # &#8592;[6nls
    ls
    tmp
    /data/local # &#8592;[6ncd tmp
    cd tmp
    /data/local/tmp # &#8592;[6nls
    ls
    /data/local/tmp # &#8592;[6nexit
    exit

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb
    push soffbin3 /data/local/tmp/
    4 KB/s (4751 bytes in 1.000s)

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb
    shell
    ~ # &#8592;[6nls
    ls
    cache init.rc sdcard
    data initlogo.rle supersu
    default.prop internal_sdcard sys
    dev mtdcache system
    devlog proc tmp
    etc res ueventd.goldfish.rc
    fstab.qcom root ueventd.rc
    init sbin
    ~ # &#8592;[6ncd data
    cd data
    /data # &#8592;[6nls
    ls
    data local
    /data # &#8592;[6ncd local
    cd local
    /data/local # &#8592;[6nls
    ls
    tmp
    /data/local # &#8592;[6ncd tmp
    cd tmp
    /data/local/tmp # &#8592;[6nls
    ls
    soffbin3
    /data/local/tmp # &#8592;[6nexit
    exit

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb
    shell chmod 744 /data/local/tmp/soffbin3

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb
    shell su -c "/data/local/tmp/soffbin3"
    /sbin/sh: su: not found

    C:\Android\android-sdk\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb
    shell
    ~ # &#8592;[6nls
    ls
    cache init.rc sdcard
    data initlogo.rle supersu
    default.prop internal_sdcard sys
    dev mtdcache system
    devlog proc tmp
    etc res ueventd.goldfish.rc
    fstab.qcom root ueventd.rc
    init sbin
    ~ # &#8592;[6ncd data
    cd data
    /data # &#8592;[6nls
    ls
    data local
    /data # &#8592;[6ncd local
    cd local
    /data/local # &#8592;[6nls
    ls
    tmp
    /data/local # &#8592;[6ncd tmp
    cd tmp
    /data/local/tmp # &#8592;[6nls
    ls
    soffbin3
    /data/local/tmp # &#8592;[6n./soffbin3
    ./soffbin3
    /sbin/sh: ./soffbin3: not found
    /data/local/tmp # &#8592;[6n

    If you notice when I got the not found error I used ADB shell to look and see what the issue was, the first time I ran 'adb push soffbin3 /data/local/tmp/' I got 'failed to copy 'soffbin3' to '/data/local/tmp/': Is a directory'

    So I went and looked - the directory structure was there but the file soffbin3 was not.
    Ran the command again and it copied the file - then the file copied and chmod seemed to work - but running the file did not work - tried running command and going to the directory and running command == ./soffbin3

    still get not found ?? tried multiple times.

    Advertisement
    :
  2. scotty85

    scotty85 Guides Guide

    what rom are you on? also,how how up to date are your adb tools? you can thry with these: miniadb_v1031.zip

    those are from the newest sdk.
    Altaone likes this.
  3. Altaone

    Altaone Well-Known Member

    I am on CM10.1 (nandroid of CM10.1 works great) - currently the only roms I can run are CM 10 and CM10.1 cant go back to old nandroids - tried flashing ICS boot.img and still could not get my old nandroid to run. I Cant make` work, any roms that i have tried - virtous, trick droid, dark jelly and I think one other.

    Trying new ADB tools now.
  4. Altaone

    Altaone Well-Known Member

    still get 'adb shell su -c "/data/local/tmp/soffbin3"
    /sbin/sh: su: not found'

    went to sbin/sh and su is not there.

    However when I go to ADB shell the prompt == # which means I am root right?
  5. scotty85

    scotty85 Guides Guide

    Hmm... maybe we should work on why you can't flash Roms. Cm 10 and 10.1 will likely run on the same kernel... Sounds like for whatever reason you are not actually changing them.

    are you certain there are no errors when flashing the boot images? Maybe you've gotten them mixed up and are installing the same one over and over?

    Maybe describe in as much detail as you can the process you go thru when installing them.
  6. Altaone

    Altaone Well-Known Member

    Ok here is my process this afternoon.

    after trying different roms.
    redownloaded CM10.1 nightly (just to be sure)
    Checked md5
    opened zip and re copied boot.img to working directory
    boot to recovery install zip from sd card
    boot to fastboot -- fastboot flash boot boot.img
    I am willing to try anything at this point - however if there is a chance of a non working phone I would like to wait till monday so if I need to I can go buy another phone.
  7. Altaone

    Altaone Well-Known Member

    Shouldnt I be able to go back to ICS roms if I flash the boot.img?

    Also will CM10 work on stock boot.img stuff? - fastboot flash never gave an error always says writing. do you wnat to see output there?

    I just read your last post on my thread about trying to find the right RUU -- how do I find out what SU I have it is not listed as an app
  8. scotty85

    scotty85 Guides Guide

    Lol you have more questions than I can answer on my phone while doing the weekly grocery shopping ;) I will answer as soon as I get a chance to read everything more closely.

    You might try entering the last cmmand without the "Su" and see if that makes a difference.
  9. Altaone

    Altaone Well-Known Member

    Lol sorry, I will try to mellow.

    My fastboot ==

    C:\Android\New ADB>fastboot flash boot boot.img
    sending 'boot' (5278 KB)...
    OKAY [ 0.889s]
    writing 'boot'...
    OKAY [ 1.326s]
    finished. total time: 2.231s
  10. scotty85

    scotty85 Guides Guide

    thats ok. :) i didnt mean you should stop asking questions,i just didnt want you to think i was ignoring you. that output looks ok. you can try some different usb cables,and double check that nothing is running on the PC that may interfere with the phone. htc sync,pda net,easy tether,even i tunes can sometimes casue issues. ive seen things look fine in the cmd window,but not change the phone- its not real common,but it does happen. if something is comunicating with the phone at the same time,it can affect things.


    that all looks fine. you are wiping data/factory reset,cache,and dalvik cache,correct? if not that could certainly casue issues :eek:
  11. Altaone

    Altaone Well-Known Member

    I knew I needed another pair of eyes!

    I think not having su is the problem, how would I get that back or get the one from Viper?

    As far as using different equipment, I have another computer that I have tried. I also have another USB cable but haven't tried that yet. Is HTC sync the only thing that I should uninstall? I also have HTC driver Installer and HTC BMP USB driver

    Downloaded (from play store) super user app and it force closed :D isnt that cool. leaving that alone till I know more.

    your current rom takes you right to a "#" when you enter adb shell,so maybe the su is confusing it. what i meant above when i said to leave it out is to try it like this:
    adb shell -c "/data/local/tmp/soffbin3"


    right so when I ran that command I got -- not found
    also when I went to the directory where the file soffbin3 was and ran ./soffbin3 it also said not found - so now it makes sense the soffbin3 file is trying to do things that require su as well.

    I dont know why but I was not connecting su with super user
    scotty85 likes this.
  12. Altaone

    Altaone Well-Known Member

    Wiped cache, dalvik, factory reset, system, internal sd. Then fastboot flash TWRP again, and then install from sd super su. reboot and still not found.

    C:\Users\MRC\Downloads>fastboot flash recovery openrecovery-twrp-2.4.4.0-ville.i
    mg
    sending 'recovery' (8292 KB)...
    OKAY [ 0.999s]
    writing 'recovery'...
    OKAY [ 1.982s]
    finished. total time: 2.992s

    C:\Users\MRC\Downloads>adb shell
    ~ # &#8592;[6nsu
    su
    /sbin/sh: su: not found
    ~ # &#8592;[6n
    scotty85 likes this.
  13. Altaone

    Altaone Well-Known Member

    Then when I went to cm10.1, opened terminal emulator and requested SU. I was asked if I wanted to allow terminal SU access, but the icon in the top left corner was not a SU icon but the CM10.1 settins icon. attached photo
    scotty85 likes this.
  14. Altaone

    Altaone Well-Known Member

    this is the attachment

    Attached Files:

  15. razvan06

    razvan06 Well-Known Member


    That is SU[Superuser] only on CM it's built-in the system, try to update the SU version, or install it from market, if that fails try to install ViperOne S ROM and try again, i did S-OFF from ViperOne S and had no issues.
  16. scotty85

    scotty85 Guides Guide

    Did you try on cm10? (Android 4.1)
  17. Altaone

    Altaone Well-Known Member

    I dont know if I will have the time tonight, I will let you know how it goes. Also if there is any kind of log etc. that might help let me know.

    I have been trying to think when I started having issues, I first was using CWM and then saw a post about CWM causing trouble with one-s so I flashed TWRP. -- I think this is when the real issues began. I have no proof though, but I had not attempted a custom rom, after changing my recovery is when I started trying to flash to Viper.
  18. razvan06

    razvan06 Well-Known Member


    You can use CWM as the latest version if good.
    Did you try and format : system/data/cache before installing new ROM [select stock kernel under install in Aroma when asked if you are flashing stock boot.img]? Also, did you manually flash the new boot.img from the Viper ROM ?
  19. agentc13

    agentc13 Daleks Über Alles VIP Member

    I have heard of some people having issues with the latest couple of version of TWRP and the Viper ROM. What version of TWRP are you using?
    scotty85 likes this.
  20. bigt

    bigt Well-Known Member

    By default CM10 only allows root access from Apps not ADB. Go to Settings -> Developer options -> Root access, and change option to "Apps and ADB".
    scotty85 likes this.
  21. scotty85

    scotty85 Guides Guide

    10.1 is still being developed... i run it on my rezound,and there is not a developer options setting yet. im unfamiliar with stock 4.2,so ive no idea if thats a 4.2 change,or cm10.1 not being quite up to speed. my stock phones are still on 4.1.

    there is a system group of settings that has a "superuser" setting, where you can select apps,adb,both,or disable. maybe this is your issue... if you havent checked here,do so,and make sure you have adb allowed.

    edit: i actually cant get an adb shell on my rezound... idk if this is a rezound issue,ora cm10.1 issue.

    i think you should go back to cm10 and try s off again :)
  22. Altaone

    Altaone Well-Known Member

    I am on TWRP V. 2.4.4.0
    I am running CyanogenMod V. 10.1 - 20130312 -nightly-ville.

    Should I change them both?
    Or one at a time?
  23. agentc13

    agentc13 Daleks Über Alles VIP Member

    If you can find a TWRP 2.3.x version that would probably solve the Viper ROM issues. I have read that the newer TWRP updates don't play nicely with Viper.
  24. Altaone

    Altaone Well-Known Member

    What about new version of CWM and is that link on all things root guide?
  25. agentc13

    agentc13 Daleks Über Alles VIP Member

    Personally I prefer TWRP and don't use CWM at all, so I can't tell you.
    Altaone likes this.
Loading...

Share This Page