Ok, so here is what puzzles me:
I have a MT3G, SuperOneClick rooted, with RA 1.7.0, busybox 1.18.4, all apps requiring superuser permissions are working flawlessly (Titanium, SetCPU, Root Explorer, Droid Wall, etc). Fix_permissions works with RA (other/fix uid mismatches) and ROM Manager, but when I open the emulator and type $su #fix_permissions, it gives me
bash: fix_permissions: command not found
In adb shell fix_permissions, permission is denied. All useful ideas how to solve this are much appreciated, thanks...
Anyone?
Sent through XDA App
Ok, I don't want to open a new topic, but really need some advice here! I just used Root Check in advanced mode, before it ran it asked for and received superuser permissions, then the detailed results were:
Congratulations! You have root access!
Alternate su bin location:
/sbin/su: Permission denied
Root user id:
uid=0(root)
Root group id:
gid=0(root)
Click to expand...
Click to collapse
Seriously, guys, please help, I dont have a clue whether I have a permanent root or not. I forgot to mention I'm using the T-Mobile OTA Froyo 2.2.1 FRG83D. I've rooted this same ROM once, 5-6 months ago, when it was pushed out, I had no problems, fix_permissions were working. Then I nandroid backed it up, so I can restore it if I don't like the other ROMs I used later (which were Ginger Yoshi RC7 -a great ROM, but the launcher was constantly restarting, and then back to Super D - most stable one, but lots of the good apps are not for 1.6 anymore). However, when I tried to restore Froyo, it didnt work, so I had to start over, using the following steps to get the OTA and root it. Please, let me know if I missed something or did it wrong:
1. I flashed sappimg.nbh with hboot to get to unrooted Cupcake
2. Flashed DRC92 and DMD64 Donut updates with stock recovery <3e>
3. Got the OTA Froyo from T-Mobile (*#*#checkin*#*#)
4. Used SuperOneClick to root, then restarted the phone
5. Using Droid Explorer, I installed a terminal emulator, then I uninstalled Superuser (have read in several threads people saying they had problems with it when it comes with SuperOneClick), using
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/app/Superuser.apk
# pm uninstall com.noshufou.android.su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
$ exit
and reinstalled it from the market.
6. Installed the latest busybox with Busybox Installer.
7. Pasted flash_image and recovery.img (Amon RA 1.7.0) to the sdcard, then installed recovery:
$ su
# mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
# rm /system/etc/install-recovery.sh
# cd sdcard
# mount -o remount,exec /dev/block//vold/179:1 /sdcard
# ./flash_image recovery /sdcard/recovery.img
# exit
$ exit
8. And finally I started removing the unnecessary system apps (Amazon, MyFaves, etc) with the emulator, using the same method I did to remove Superuser in step 5
Click to expand...
Click to collapse
Now, as I mentioned before, I cannot run fix_permissions through the emulator, but it runs through ROM Manager and RA (fix package uid mismatches).
Why is that? Is it the ROM, which causes the problem?
I'm clueless, please help!
Related
I have a rooted ASUS Transformer running Revolver 2.1.1 (Android 3.2).
I am a programmer and want a simple programming environment for my Transformer. I purchased an app called c4droid the other day and have had issues compiling c++ code using the g++ compiler.
When I try to compile/run code, I get the messages below:
C4droid has been granted superuser permissions
Click to expand...
Click to collapse
Then....
sh: /sdcard/Android/data/com.n0n3m4.droidc/files/gcc/compile-g++.sh: Permission Denied
Click to expand...
Click to collapse
How can I get this to work? Did I root wrong?
If you face these issues, click on the link below -
http://forum.xda-developers.com/showpost.php?p=16604606&postcount=6
What about trying this:
$su
#chmod 755 /sdcard/Android/data/com.n0n3m4.droidc/files/gcc/compile-g++.sh
I'm not sure what type of FS /sdcard is on the TF, so I don't know if those permissions will a) be allowed to be set, and b) work, but I doubt if any shell script will give anything but a permissions error without having +x permissions.
By the way:: If you can't do a chmod and that is due also to a permissions error, then I'm guessing you're not really rooted or not correctly rooted.
Good luck.
hachamacha said:
What about trying this:
$su
#chmod 755 /sdcard/Android/data/com.n0n3m4.droidc/files/gcc/compile-g++.sh
I'm not sure what type of FS /sdcard is on the TF, so I don't know if those permissions will a) be allowed to be set, and b) work, but I doubt if any shell script will give anything but a permissions error without having +x permissions.
By the way:: If you can't do a chmod and that is due also to a permissions error, then I'm guessing you're not really rooted or not correctly rooted.
Good luck.
Click to expand...
Click to collapse
did.......
su then chmod 755 /sdcard/Android/data/com.n0n3m4.droidc/files/gcc/compile-g++.sh and it had no such error but if I ran both on the same line I got a "Permission Denied" error. Either way, it still provided me with the permission denied error through c4droid.
Also, I've used root checker to verify that it's rooted.
So is it a sure thing that the .sh file you're getting the error on is actually the problem or could it be something inside it that is also having a permissions error?
I guess you could easily test that by writing a single line test.sh script that does an ls or a ps command.
Code:
example:
--start of test.sh--
#!/system/bin/sh #or whatever the path is for your case
ls > /sdcard/ls.txt
-- end of file ---
# cd {pathoftestfile}
# chmod 755 test.sh
# ./test.sh
# more ls.txt # or cat ls.txt, etc.
If that doesn't give an error then something in your 'real' shell script is.
One other thing worth a shot, which I "think" I've noticed on droids in the past is to just test the script inside the /system FS and see if it does any better there. At least we know that scripts have no problems in for example, /system/xbin or /system/bin, so mount /system rw (mount -o remount,rw /system) and move the test.sh over there , fix permissions, (mount -o remount,ro /system) and cd to /system/*bin/ and ./test.sh.
You've probably tried all this already, but if not.
NOTE: Never mind: I just tested my stuff ^^ myself, and it just doesn't work in the /sdcard tree. I moved it to /system/xbin after mounting rw and it works fine without any change.
There might be some way past this, but I can't recall ever getting a shell script working while on the /sdcard share.
I tried making the shell script but I had no luck actually running it. I chmodded it without error and ran it without error but it didn't produce a .txt file so I guess it failed to run or didn't have permissions to create a file.
The app developer/creator specifies that the compiler I'm using should work fine on rooted phones. I don't have an android phone to test it. I've tried working out problems with the developer but he couldn't figure it out either.
Okay, the creator helped me out and we resolved it. Here are the steps I took to do it, for other users.-
Pre-requisites: You must have BusyBox, SuperUser, C4droid, GCC for C4droid, and a Terminal Emulator installed. You also need a rooted device.
1. Open Terminal emulator and type "su" and press enter. A superuser screen will pop up and you need to click allow.
2. Type the following lines into the terminal (one by one):
cd /Removable/MicroSD/
mkdir Android
mkdir Android/data
cp -r /sdcard/Android/data/com.n0n3m4.droidc/ /Removable/MicroSD/Android/data/
su
mount -o remount,rw,exec -t vfat /dev/block/vold/179:9 /Removable/MicroSD
/system/xbin/mount -o bind /Removable/MicroSD/Android/data/com.n0n3m4.droidc/ /sdcard/Android/data/com.n0n3m4.droidc/
3. Change the default compiler in C4droid to G++ + bionic (Root required)
4. Done
Congratulations!
I guess it was mainly the 'noexec' switch of the mount -o {} that kept things from being executable.
I didn't notice that and am glad you posted the solution and I also wasn't really aware of the use of the "mount -o bind" for dual-pathing as well.
-- Thanks.
Hi, I'm enter on my transformer by :
adb shell
and I want do that :
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
cd /data/app
rm com.mhuang.overclock*
cd /data/data
rm com.mhuang.overclock*
cd /data/dalvik-cache
rm *mhuang.overclock*
exit
But when I execute su, it don't work :
/data/app # su
Segmentation fault
Can you help me ?
Thanks
Just reflash your rom without wiping data unless your trying to flash a rom that is overclocked by default
If it's in your data partition, then it's not a system file. Try this:
adb uninstall com.mhuang.overclocking (use the full package name)
EDIT: saw your other thread about borking your TF. follow badfrog's trick and flash a rom with a non-overclocking kernel, which will limit setcpu.
If adb uninstall don't work, which rom with overclock by default propose me ? Révolution HD ?
Sorry for my english, i'm french ?
Prime has a stock kernel as default
http://forum.xda-developers.com/showthread.php?t=1251044
i am trying to mount /system as rw, but keep running into errors. my tab is rooted and i have superuser elite installed. i have tried from a terminal app from the su prompt (#mount -o remount,rw /system and variations of), from adb shell, and using adb remount, but always get an error. (permission denied, are you root?)
any suggestions?
secondly, i messed up my permissions on both /system and /etc, as i had a similar issue with permissions when i was trying to get root, but forgot to note what they were previous so that i could set them back. i set them both to 755 for now, but if someone could tell me what they are suppose to be that would be appreciated.
Rusty_Gunn said:
i am trying to mount /system as rw, but keep running into errors. my tab is rooted and i have superuser elite installed. i have tried from a terminal app from the su prompt (#mount -o remount,rw /system and variations of), from adb shell, and using adb remount, but always get an error. (permission denied, are you root?)
any suggestions?
secondly, i messed up my permissions on both /system and /etc, as i had a similar issue with permissions when i was trying to get root, but forgot to note what they were previous so that i could set them back. i set them both to 755 for now, but if someone could tell me what they are suppose to be that would be appreciated.
Click to expand...
Click to collapse
Hi,
Try :
adb shell
su
mount -o rw, remount /system
It work fine for me on adb shell and terminal emulator
The command adb shell remount doesn't mount /system as rw
thanks, that put me on the write track. turns out i was getting rw the whole time, but i didnt have write permissions. did chmod 777 /system and it worked, and when i was done i put it back to chmod 755 /system
if anyone has a similar problem, the command 'mount | grep /system' is a great way to check to see if you actually have it mount as rw or not.
before this i tried a couple of the remount apps, as well as the mount as 'rw' option in es file explorer and they always fail to mount, presumably they aren't failing to mount but are running into the same permission issue and can't write
Hi,
I'm getting the following output while trying to flash custom recovery:
# su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
link_image[1934]: 4368 missing essential tablesCANNOT LINK EXECUTABLE
Setup:
Android 2.2.3.
Stock GB ROM rooted.
Stock Kernel.
I haven't even flashed a single ROM yet...I am getting this same error no matter which custom recovery I try to flash. Any ideas please? :crying:
mugenishere said:
Hi,
I'm getting the following output while trying to flash custom recovery:
# su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
flash_image recovery /sdcard/recovery-RA-thunderg-2.2.1-GNM.img
link_image[1934]: 4368 missing essential tablesCANNOT LINK EXECUTABLE
Setup:
Android 2.2.3.
Stock GB ROM rooted.
Stock Kernel.
I haven't even flashed a single ROM yet...I am getting this same error no matter which custom recovery I try to flash. Any ideas please? :crying:
Click to expand...
Click to collapse
What phone are you using? Are you sure that the recoveries are for your phone? Also, are you sure you're rooted?
upconvert said:
What phone are you using? Are you sure that the recoveries are for your phone? Also, are you sure you're rooted?
Click to expand...
Click to collapse
I'm using LG Optimus One P500. Setup is as follows:
ROM: Stock GB 2.2.3 (rooted)
Kernel: Stock (everything else is stock, untouched)
Recovery: thunderg 2.2.1
I'm quite sure the phone is rooted. I just shifted from SuperUser to SuperSU. Root privileges are being granted fine. But the problem is still there in recovery mode. Root checker, Titanium Backup, SuperSU, adb shell ("SU") are all working fine with no errors...
You could try the flash image gui. It's on the play store, and I think it supports the P500.
upconvert said:
You could try the flash image gui. It's on the play store, and I think it supports the P500.
Click to expand...
Click to collapse
"flash image gui" from the play store works just fine to flash a new custom recovery. Thanks a lot for your suggestion.
I was just wondering whether there is something wrong with my setup that in the adb shell - the last step is consistently failing for every recovery I try.
I don't know. Glad it worked out, though.
Sent from my LG-VM670 using xda app-developers app
Hi,all, I just get start with Nexus 5. can anybody tell me what the problem? follow with the command I input in windows shell.
K:\N5\ROOT>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount system /system
mount -o remount system /system
mount: Permission denied
255|[email protected]:/ #
Anyone on this?
Cheers!
su
mount -o remount,rw /system
However this only works if you have a custom "insecure" kernel that allows adb to do root things.
Sent from my Nexus 5 using Tapatalk
Thanks for the reply!
So, I will write my story here, hopefully to help some other guy in the future!
Basically I was on debug build from AOSP for the N5! And I installed all proprietary files from Google, LG, Qualcomm etc! But camera was faulty! So I decided to flash the stock images from Google! Then I 've lost
Code:
adb root
So I flashed the boot image from the debug build I had previously!
adb root works like charm!
to flash it, I used: fastboot flash boot boot.img