10-28-2011 10:42 AM
31 12
tools
  1. Sdude1200's Avatar
    I went to update the SU binary via the superuser app, and it failed once. So I clicked the option to try again, and now it says I do not have root privileges. Any idea what would cause this and how to fix it?

    Sent from my OptiRom v1ed LG Optimus S
    10-23-2011 09:49 AM
  2. mr.longbough's Avatar
    To fix just dirty flash your rom or load a backup
    10-23-2011 09:59 AM
  3. Sdude1200's Avatar
    Ill go ahead and try a dirty. Thanks for your quick reply. Ill post once done how it worked out

    Sent from my OptiRom v1ed LG Optimus S
    10-23-2011 10:01 AM
  4. CuriousNoob's Avatar
    Read last pages 53 and 54 of the IHO kraven thread.
    10-23-2011 10:04 AM
  5. thekraven's Avatar
    Don't update the Superuser or Superuser binary till it gets fixed. Superuser 3.0.6 version and the 3.0.1 Binary are the ones causing problems. Stay with 3.0.4 or 3.0.5.
    epidenimus likes this.
    10-23-2011 10:18 AM
  6. Sdude1200's Avatar
    I found the 3.0.2 binary and flashed that, but still nothing. Do you have a zip of .4 or .5 that I can apply kraven?

    Sent from my OptiRom v1ed LG Optimus S
    10-23-2011 10:27 AM
  7. sfhub's Avatar
    Is it better to just "untie" su from the market? I don't think it is an area that needs major functionality changes all the time and if tied to the market, encourages market updates that could disable it intentionally (in this case it was unintentional)
    epidenimus and memsman like this.
    10-23-2011 10:35 AM
  8. memsman's Avatar
    Is it better to just "untie" su from the market?
    How can you do that?
    10-23-2011 10:41 AM
  9. drewwalton19216801's Avatar
    How can you do that?
    Install it manually vs installing from the Market.
    memsman and epidenimus like this.
    10-23-2011 10:49 AM
  10. thekraven's Avatar
    I attached it below, let me know if it works. Just flash in recovery
    epidenimus and memsman like this.
    10-23-2011 10:51 AM
  11. epidenimus's Avatar
    Superuser appeared in Market and started begging for the update after I cleared the Market cache and data. I will flash manually if it removes it from the nag list. Glad I did not take the update. Thanks for the tip!
    10-23-2011 10:56 AM
  12. punjig's Avatar
    OK, History= got stock EC05, Rooted it using One Click Root Method W/ CWM 3.0.2.5, All was good. Made backups. SU updated itself. Then told me SU Binary was out of date. Reloaded my backup. Su updated agian by itself, This time I saw it updating right at the end of the update, and now same thing. SU Binary out of date, No SU accsess.

    OK, Question= I will reload my back up, no problem. HOW can I stop it from auto updates?? As it seems to me it was manually installed to begin with, w/ the OC Method, or am I confussed?

    Thanks in advanced!
    10-23-2011 12:08 PM
  13. punjig's Avatar
    BTW, Yes this is an EPIC Phone. Just couldn't find any other discussions on the SU problem. Thanks
    10-23-2011 12:31 PM
  14. epidenimus's Avatar
    If it ain't broke.... why bother with it? (And I wonder why relationships are so difficult...)

    So I mimicked the user's problem by flashing your superuser 3.0.4 apk, which gave a newer version of superuser.apk. Cool!

    It then nagged me that the su binary was out of date and courteously offered to update mine from v2.3.1-ef to v3.0.2--which is not one of the troublesome versions cited. So I accepted and it succeeded on the first attempt. It even offered me the option to do it again, just because I might have thought it was cool. It was cool, but I declined and rebooted. That's when the trouble began.

    I ran rootcheck and it said I no longer had root. (At this point, I expect that I was where the OP was.) So I rebooted to Recovery and again flashed the superuser apk linked previously. No luck.

    Output from rootcheck:

    Code:
    Root Access is not properly configured or was not granted.
    
    Superuser.apk - com.noshufou.android.su - version 3.0.4 is installed!
    
    System Environment PATH /sbin /system/sbin /system/bin /system/xbin
    
    The adb binary is set to default shell user access as root
    
    Standard su binary location is: ls -l /system/bin/su:
    -rwsr-sr-x root    root     22172 2011-1023 12:44 su
    
    Standard su binary location is: ls -l /system/xbin/su:
    -rwsr-xr-x root    root     26328 2008-0801 08:00 su
    
    Alternate su binary location is: ls -l /sbin/su:
    /sbin/su: No such file or directoryj
    
    Alternate su type binary location: ls -l /system/xbin/sudo:
    /system/xbin/sudo: No such file or directory
    
    SU binary not found or not operating properly.
    I am sure that I could wipe everything and restore a nandroid, but there must be a less blanketous way of reestablishing root. Is it a file permissions or ownership issue? Two conflicting files?
    10-23-2011 12:34 PM
  15. hamagc's Avatar
    Yep

    Sent from my LS670 using Tapatalk
    10-23-2011 02:40 PM
  16. epidenimus's Avatar
    Alright, now that I recreated the problem, I will proceed with the fix:

    How-To: Root a Custom ROM: A bin named 'su'

    The issue is that the installed su binary is not doing something right and the /system directory is now again read-only.

    We know that the installed Superuser.apk 3.0.4 provided by Kraven, combined with the busybox and previous version of the su binary from the ZVD rooting guide work just fine together. However, we cannot overwrite the faulty su binary with things the way they are.

    So we refer back to Drew's guide to ZVD rooting for instructions and for a copy of the version of su that we know works.

    We need to use adb to push su and gingerbreak only to the device. I am going to presume that you know how to fire up adb, since you already had a rooted a ZVD-based device.

    [BOX="Note"]Even though you may get a # prompt in adb here, you are not running with root permissions and will get an error if you attempt a command that requires them.[/BOX]
    Skip Step 3 in the guide, as you may want to keep some things your custom ROM has there. if If you are curious or cautious, you can use the following command to see what's there:
    Code:
    ls -a /data/local/tmp
    Go right to Step 4 and push only the provided su and gingerbreak to your device's /data/local/tmp directory.
    Code:
    adb push gingerbreak /data/local/tmp/gingerbreak
    adb push su /data/local/tmp/su
    Follow Steps 5 through 10 exactly.

    At Step 11 and Step 12, only cat and set permissions on the su file.
    Code:
    cat su > /system/bin/su
    chmod 4755 /system/bin/su
    Exit as described, reboot and enjoy!
    Superuser may prompt you for permission if you have root apps set to start at boot.

    Finally, this version of Superuser also has a Settings option that stops the nagging about your su binary:
    Superuser --> Settings --> Preferences... scroll to the bottom and untick 'Outdated binary notification'

    Now go use your favorite music app to listen to the Johnny Cash song that is stuck in your head.
    Sdude1200 likes this.
    10-23-2011 02:43 PM
  17. Sdude1200's Avatar
    If it ain't broke.... why bother with it? (And I wonder why relationships are so difficult...)

    So I mimicked the user's problem by flashing your superuser 3.0.4 apk, which gave a newer version of superuser.apk. Cool!

    It then nagged me that the su binary was out of date and courteously offered to update mine from v2.3.1-ef to v3.0.2--which is not one of the troublesome versions cited. So I accepted and it succeeded on the first attempt. It even offered me the option to do it again, just because I might have thought it was cool. It was cool, but I declined and rebooted. That's when the trouble began.

    I ran rootcheck and it said I no longer had root. (At this point, I expect that I was where the OP was.) So I rebooted to Recovery and again flashed the superuser apk linked previously. No luck.

    Output from rootcheck:

    Code:
    Root Access is not properly configured or was not granted.
    
    Superuser.apk - com.noshufou.android.su - version 3.0.4 is installed!
    
    System Environment PATH /sbin /system/sbin /system/bin /system/xbin
    
    The adb binary is set to default shell user access as root
    
    Standard su binary location is: ls -l /system/bin/su:
    -rwsr-sr-x root    root     22172 2011-1023 12:44 su
    
    Standard su binary location is: ls -l /system/xbin/su:
    -rwsr-xr-x root    root     26328 2008-0801 08:00 su
    
    Alternate su binary location is: ls -l /sbin/su:
    /sbin/su: No such file or directoryj
    
    Alternate su type binary location: ls -l /system/xbin/sudo:
    /system/xbin/sudo: No such file or directory
    
    SU binary not found or not operating properly.
    I am sure that I could wipe everything and restore a nandroid, but there must be a less blanketous way of reestablishing root. Is it a file permissions or ownership issue? Two conflicting files?
    Thanks for testing this out. That's exactly what happened to me. I may just do a dirty flash and use the version that is preloaded with optirom because it should work. Or I could try doing a complete wipe and a fresh flash of opti. What do you guys suggest?

    Sent from my OptiRom v1ed LG Optimus S
    10-23-2011 02:44 PM
  18. Sdude1200's Avatar
    Alright, now that I recreated the problem, I will proceed with the fix:

    How-To: Root a Custom ROM: A bin named 'su'

    The issue is that the installed su binary is not doing something right and the /system directory is now again read-only.

    We know that the installed Superuser.apk 3.0.4 provided by Kraven, combined with the busybox and previous version of the su binary from the ZVD rooting guide work just fine together. However, we cannot overwrite the faulty su binary with things the way they are.

    So we refer back to Drew's guide to ZVD rooting for instructions and for a copy of the version of su that we know works.

    We need to use adb to push su and gingerbreak only to the device. I am going to presume that you know how to fire up adb, since you already had a rooted a ZVD-based device.

    [BOX="Note"]Even though you may get a # prompt in adb here, you are not running with root permissions and will get an error if you attempt a command that requires them.[/BOX]
    Skip Step 3 in the guide, as you may want to keep some things your custom ROM has there. if If you are curious or cautious, you can use the following command to see what's there:
    Code:
    ls -a /data/local/tmp
    Go right to Step 4 and push only the provided su and gingerbreak. to your device's /data/local/tmp directory.
    Code:
    adb push gingerbreak /data/local/tmp/gingerbreak
    adb push su /data/local/tmp/su
    Follow Steps 5 through 10 exactly.

    At Step 11 and Step 12, only cat the su file.
    Code:
    cat su > /system/bin/su
    chmod 4755 /system/bin/su
    Exit as described, reboot and enjoy!
    Superuser may prompt you for permission if you have apps that start at boot.

    Go use your favorite music app to listen to the Johnny Cash song that is now stuck in your head.
    Posted just as I did lol. I will try that now! Thanks bro

    Sent from my OptiRom v1ed LG Optimus S
    10-23-2011 02:46 PM
  19. epidenimus's Avatar
    Thanks for testing this out. That's exactly what happened to me. I may just do a dirty flash and use the version that is preloaded with optirom because it should work. Or I could try doing a complete wipe and a fresh flash of opti. What do you guys suggest?

    Sent from my OptiRom v1ed LG Optimus S
    I went by your block that says you were running Drew's CM7, which is ZVD-based. It might be a little different with the ZVH series, but same kinda concept.
    10-23-2011 03:06 PM
  20. Sdude1200's Avatar
    Yeah I Havn't updated that in a while.... Sorry. Im actually now on OptiRom v1.1 on ZVH, thus the sig. How do you think that i could do this defferently on zvh to get it to work?

    Sent from my OptiRom v1ed LG Optimus S
    10-23-2011 03:18 PM
  21. thekraven's Avatar
    It looks like Superuser got the needed update now and is fixed. Superuser 3.0.6 installed and binary 3.0.3 updated.

    I saw some comments where if you cleared data in Settings-applications-Superuser , it should restore your root.
    pergerson6 likes this.
    10-23-2011 03:37 PM
  22. Sdude1200's Avatar
    There we go. I just went through the stephe posted in the How To Root ZVH guide and re rooted my device so i not have the privs again. I hope this can be used by other people experiencing this SuperANNOYINGUser binary update error. Thanks for all your help epidenimus
    epidenimus likes this.
    10-23-2011 03:38 PM
  23. pergerson6's Avatar
    It looks like Superuser got the needed update now and is fixed. Superuser 3.0.6 installed and binary 3.0.3 updated.

    I saw some comments where if you cleared data in Settings-applications-Superuser , it should restore your root.
    Working fine now with no root access issues.

    Sent from my LS670 using Tapatalk
    10-23-2011 04:27 PM
  24. epidenimus's Avatar
    Ok, so v3.0.6 of Superuser.apk and su v3.0.3 works then? I thought you said v3.0.6 was problematic in an earlier post.

    Is there any reason the update thereto would not work on Froyo/VD based ROM's? Has anyone verified it?
    10-23-2011 06:59 PM
  25. pergerson6's Avatar
    Ok, so v3.0.6 of Superuser.apk and su v3.0.3 works then? I thought you said v3.0.6 was problematic in an earlier post.

    Is there any reason the update thereto would not work on Froyo/VD based ROM's? Has anyone verified it?
    I'm using vd with the kravens cm7! Its running fine.

    Sent from my LS670 using Tapatalk
    10-23-2011 07:04 PM
31 12
LINK TO POST COPIED TO CLIPBOARD