Root adb/emulator help needed.??

[1iwilly]

hello
i went back to the sense rom from joneidy. when i go on terminal and type su enter then fix_permissions. i get the error=command not found the same error also when i use adb. any help or guidance is needed. thanks.

 

[AndyOpie150]

Did you look to see if there is Busybox in the /system/bin or /system/xbin. If it is installed you will see the first two folders with [ and [[ for names.

The code is fix_permissions not fix_permission
Fix permissions - CyanogenMod Wiki

 

[1iwilly]

Did you look to see if there is Busybox in the /system/bin or /system/xbin. If it is installed you will see the first two folders with [ and [[ for names.

The code is fix_permissions not fix_permission
Fix permissions - CyanogenMod Wiki

thanks yes i know that is the code.typo error when i wrote this. yes those 2= [ and [[ for names.are in the system/xbin only when i check it with root explorer.are they suppose to be in system/bin also.??? the only thing i saw in that folder was busybox no [ and [[ for names in that folder.???

 

[AndyOpie150]

Busybox just has to be in one of them. Either the bin or the xbin. Most times the xbin is where it will be because there is not enough room in the bin for a complete install.

This is something I just learned from a member over at another Optimus phones forum here.
If you get an error, try: type exit then hit the enter key. back out of the app and try again.
Don't know how many times you would need to try it if errors again.

 

[1iwilly]

well just for the hell of it .i went back to the backside rom. found no issues what so ever running fix_permissions. now i'm back on the sense rom again.after hours of googling this is what i found that works 100%.hope it helps others when all else fails.
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...
when it finish type reboot and your done.