[Q] Problem with Fix Permissions (line 64: UID readonly variable) [WORK AROUND FOUND]

Search This thread

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Latest!! Switch to TWRP 2.1.8 (June 18th 2012)

    Anyone else having a problem Fixing Permisshions? And how did you fix it?

    I noticed it would take 2 seconds to run, so I decided to go to "Show log"

    Here is the log

    I:Checking for extendedcommand, file not found...
    /sbin/fix_permissions: line 64: UID readonly variable
    Done!
    ro.carrier=unknown
    ro.bootloader=unknown
    ro.hardware=qcom
    ro.revision=0
    init.svc.recovery=running
    init.svc.adbd=running


    Tried:
    Running from Rom Manager but it always stalls, never the same place and if I run it multiple times back to back it stalls sooner and sooner
    touch recovery
    re-installing recovery
    clearing download in rom manager and re-installing recovery
    setting rom manager to delete recovery before installing
    Wipe / reset, wipe cache & dalvik, with superwipe 2 times and re-installing

    ClockworkMod Recovery v5.0.2.7

    Running [ROM] [cwm]-BLACKEDITION FOR THE SGS2 4-10-2012-ICS RC6

    A work around has been found! Thanks to RealPariah, so thank him here!
    It is not a fix due to the fact that you still will not be able to fix permissions in CWM or Rom Manager but does get the job done of Fixing Permissions!!


    1st Do you have the Google android installed?
    If not download and install it! http://developer.android.com/sdk/android-4.0.htm
    you might need to install the JDK, if you don't have it already.

    2nd Your path to adb must not be set or is not correct.
    See http://xdaforums.com/show....php?t=1161776

    Now you should be ready to use adb!

    STOP!
    Fixed in this New CWM Recovery or
    GOTO THE DEVELOPMENT THREAD!
    http://xdaforums.com/showthread.php?t=1604581

    Most recent Fix Script / Work Around found here
    http://xdaforums.com/showpost.php?p=25023284&postcount=22


    Boot in to Recovery
    plug USB in to phone and computer
    In Recovery Go in to "mounts and storage" and mount /system and /data
    On computer open a command line window (windows) [click start] then [run] then type "cmd" to get a command prompt or terminal (Linux or OSX)

    Run "ADB devices" and be sure it is not all ? For device number (if it is restart recovery and reseat USB connection and run "adb kill-server" on computer) I had to run terminal as root (admin for best results bit got it to work either way really)

    Now type "adb shell" enter

    Once that opens and you get ~#
    now type cd /sbin
    then type
    sh fix_permissions -l -r

    done correctly, your command prompt should look like the following

    C:\Documents and Settings\family>adb shell
    ~ # cd /sbin
    cd /sbin
    /sbin # sh fix_permissions -l -r
    sh fix_permissions -l -r
    fix_permissions 2.04 started at 04-18-2012 02:28:21
    Processing (1 of 177): com.google.android.location...
    Processing (2 of 177): com.sec.android.app.phoneutil...
    Processing (3 of 177): com.android.defcontainer...
    Processing (4 of 177): com.sec.phone...
    Processing (5 of 177): com.android.contacts...
    Processing (6 of 177): com.android.phone...

    ORIGIONAL

    Fix permissions fix found!
    Alright after testing fix permissions I found a way to make it run!

    Issue: fix permissions won't run from recovery (correctly (it says done in less than 60 secs and stops instantly for me saying completed and while in Android; ROM manager script runs but freezes at random points (same if you open terminal emulator and run it).

    Resolution:
    You have to have adb on a computer for this
    Do you have the Google android installed?
    If not download and install it!
    [/url]http://developer.android.com/sdk/android-4.0.html

    Boot in to Recovery
    plug USB in to phone and computer
    Go in to mounts and storage and mount /system and /data
    On computer open a command line window (windows) or terminal (Linux or OSX)

    Run "ADB devices" and be sure it is not all ? For device number (if it is restart recovery and reseat USB connection and run "adb kill-server" on computer) I had to run terminal as root (admin for best results bit got it to work either way really)

    Now run "adb shell" after mounting /system and /data

    Once that opens and you get ~# run "sh fix_permissions -l -r" just like that (with two separate - don't do -lr or it won't run)

    Of it says not found mount /system

    If it says something about read only variable you forgot the preceding sh (may need to do "cd /sbin" then "sh fix_permissions" if you still have an issue.

    This is only way I can get fix permissions to run (even tried sh fix_permissions -l -r in Android terminal emulator and script manager to no avail)

    After fix permissions ran correctly it really helped iron some small performance issues and notably helped.

    I hoped that helps! :D

    Sent from my SAMSUNG-SGH-I727 using Xparent Green Tapatalk 2
    2
    RealPariah posted a workaround over in the Blackedition ICS thread that worked for me:

    Fix permissions fix found!
    Alright after testing fix permissions I found a way to make it run!

    Issue: fix permissions won't run from recovery (correctly (it says done in less than 60 secs and stops instantly for me saying completed and while in Android; ROM manager script runs but freezes at random points (same if you open terminal emulator and run it).

    Resolution:
    You have to have adb on a computer for this
    Boot in to Recovery
    plug USB in to phone and computer
    Go in to mounts and storage and mount /system and /data
    On computer open a command line window (windows) or terminal (Linux or OSX)

    Run "ADB devices" and be sure it is not all ? For device number (if it is restart recovery and reseat USB connection and run "adb kill-server" on computer) I had to run terminal as root (admin for best results bit got it to work either way really)

    Now run "adb shell" after mounting /system and /data

    Once that opens and you get ~# run "sh fix_permissions -l -r" just like that (with two separate - don't do -lr or it won't run)

    Of it says not found mount /system

    If it says something about read only variable you forgot the preceding sh (may need to do "cd /sbin" then "sh fix_permissions" if you still have an issue.

    This is only way I can get fix permissions to run (even tried sh fix_permissions -l -r in Android terminal emulator and script manager to no avail)

    After fix permissions ran correctly it really helped iron some small performance issues and notably helped.

    I hoped that helps!

    I had to do the "cd /sbin" thing before running "sh fix_permissions -l -r" inside the adb shell, but it actually ran without a hitch!
    1
    i posted a potentially working CWM flashable zip in the dev forum thread.
    1
    Tried it and did not work for me, but this did!
    New CWM Recovery

    yep i helped push that fix into the newest version.

    the issue in rom manager could be fixed via proper symlinking/busybox install probably. it would have no effect on how recovery fix permission works though because its loaded from a ramdisk if im not mistaken.