Database Users

Replacement Incredible, unable to write su: Permission denied

I've had an Incredible since launch that had a defective optical trackpad. Long story short, due to Verizon's terrible customer service I did not get my replacement until yesterday. I rooted my original Incredible without problem and backed up everything with Titanium thinking it would be an easy transition over to my replacement phone.
For some reason I am not able to get Superuser to install. Everything goes fine during the root process until I get to this step:
ln -s /system/bin/su /system/xbin/su
I get the following error:
ln: /system/xbin/su: File exists
The root instructions say to run the following command in the event of an error:
rm /system/xbin/su
At this point I get the error:
rm: cannot remove '/system/xbin/su': Permission denied
Obviously running the final command: 'chmod 06755 su' won't work and I just receive a 'Operation not permitted' error.
I've reset to factory settings 3 times with the same result every time I root. I end up with the Superuser icon in my app drawer, but root apps will obviously not work correctly as Superuser was not installed correctly with the correct permissions. If I only do the first 2 lines of the rooting process:
/system/bin/cat /system/bin/sh > /system/bin/su
/system/bin/chmod 4777 /system/bin/su
then reboot, certain apps such as Root Explorer will work, but anything that requires Superuser obviously will not.
Please, for the love of god someone give me some help. I'm so frustrated.

I had the same problem...you will want to follow the official rooting guide, as they have built the superuser into the payloadupdate.zip. Start over following the Unrevoked team: Incredible Root process (sorry, my profile is too new to post links) and you will be good to go.

You were right. I ran the Payload update from recovery, then rebooted without doing anything on the command line. Superuser was in my app drawer on reboot, and I was able to restore with Titanium backup. Thanks for the help!

I was also getting this error. This thread helped me solve my problem. Thanks.
Sent from my ADR6300 using XDA App

Fuzzy_Dunlop said:
I've had an Incredible since launch that had a defective optical trackpad. Long story short, due to Verizon's terrible customer service I did not get my replacement until yesterday. I rooted my original Incredible without problem and backed up everything with Titanium thinking it would be an easy transition over to my replacement phone.
For some reason I am not able to get Superuser to install. Everything goes fine during the root process until I get to this step:
ln -s /system/bin/su /system/xbin/su
I get the following error:
ln: /system/xbin/su: File exists
The root instructions say to run the following command in the event of an error:
rm /system/xbin/su
At this point I get the error:
rm: cannot remove '/system/xbin/su': Permission denied
Obviously running the final command: 'chmod 06755 su' won't work and I just receive a 'Operation not permitted' error.
I've reset to factory settings 3 times with the same result every time I root. I end up with the Superuser icon in my app drawer, but root apps will obviously not work correctly as Superuser was not installed correctly with the correct permissions. If I only do the first 2 lines of the rooting process:
/system/bin/cat /system/bin/sh > /system/bin/su
/system/bin/chmod 4777 /system/bin/su
then reboot, certain apps such as Root Explorer will work, but anything that requires Superuser obviously will not.
Please, for the love of god someone give me some help. I'm so frustrated.
Click to expand...
Click to collapse
I got the su file from below link
http://rapidshare.com/files/422997479/HTC_Magic_Recovery_and_su.zip
but still no result

[Q] After JB update, have partial root; only for existing approved apps [SOLVED]

So I seem to be having odd rooting issues, and I can't find anything that really explains it. Apologies that some of this might be obvious...
I rooted without any issues before the Jelly Bean update. Since then, I did the Voodoo Rootkeeper, updated to Jelly Bean, and have since restored root. Everything that had root before seems to still work, however, I can't provide new root access to any applications (it doesn't even ask), SuperUser can't update the SU binary, Root Checker reports me as not rooted, but I can adb shell and do "su" and that works....and the binary is clearly there with the su bits set. And things like ES File Explorer are clearly getting root access....just not anything new. Seems like I have "partial root". Any ideas on what I need to tweak?
thanks!

You did a good job of explaining the situation. I am in the same position.

Here, more information, below. Again, looks like I have su available (/system/sbin/su), but nothing seems to work...superuser is not granting root....strange. Thoughts?
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2012-11-12 10:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your XT907 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market

I agree good job explaining. But I think a lot of us are in this situation right now. I miss the root! But also love jb (;
Sent from my XT907 using Tapatalk 2

FIXED!
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.

RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Nice,
I am going to try using SU and Superuser.apk from that site and rooting JB with those files replaced in motofail2go run.bat Think I'd still have to change permissions that way?

Not sure....I don't think so. Good luck!

RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Any chance you could provide step-by-step details starting from where you pushed the files into data/local/temp?
I'm not a total novice with android but rooting is something I prefer to be very careful with! Sorry to bug you.

I had the same issue. Wiping Cache, Factory Reset, and re-root with JB exploits solved it.

I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!

RoboCuz said:
I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!
Click to expand...
Click to collapse
This fixed the "half-root" on my Razr Maxx HD, thanks!

[Solved] [Stock .27] ADB only work in recovery mode

Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Bounty : I'll send Russian chocolat and candies to the one that will find how to fix this !

Magissia said:
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Click to expand...
Click to collapse
Go to the play store, download & install Goomanager, install TWRP. CWM seems to have a few issues with teh TF101's.

Hello, i have a CWM flashable TWRP recovery, i even tested it, but wasn't able to work with it, it was very slow and didn't found files i was looking for, i will regive it a try.
Edit : I have the exact same problem when flashing SuperSU from TeamWin recovery, everything act as i don't have SU, i can grant rights to anything i want it will still act as i don't have root, and SuperSU is unable to update it own binary at startup

Magissia said:
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Bounty : I'll send Russian chocolat and candies to the one that will find how to fix this !
Click to expand...
Click to collapse
Hi, your busybox installation seems corrupt (ie busybox binary is missing). You can reinstall busybox to /system/bin (do make sure that /system is mounted) from inside CWM and everything shall be fine. Your root su also seems to exist and should be fine.
If you can't do it in CWM then you can try and connect to the tablet in normal use mode and then run /system/bin/su and you should be root. Then you can install busybox manually ( you'll need to upload the busybox binary to /data/local/tmp or something) and run:
/system/bin/toolbox chmod 755 /data/local/tmp/busybox ( or if you're in CWM make sure /data is also mounted and then run: /sbin/chmod 755 /data/local/tmp/busybox )
/data/local/tmp/busybox --install /system/bin ( Please verify syntax ).
Good luck!
Sent from my Transformer TF101G using xda app-developers app

idcrisis said:
Hi, your busybox installation seems corrupt (ie busybox binary is missing). You can reinstall busybox to /system/bin (do make sure that /system is mounted) from inside CWM and everything shall be fine. Your root su also seems to exist and should be fine.
If you can't do it in CWM then you can try and connect to the tablet in normal use mode and then run /system/bin/su and you should be root. Then you can install busybox manually ( you'll need to upload the busybox binary to /data/local/tmp or something) and run:
/system/bin/toolbox chmod 755 /data/local/tmp/busybox ( or if you're in CWM make sure /data is also mounted and then run: /sbin/chmod 755 /data/local/tmp/busybox )
/data/local/tmp/busybox --install /system/bin ( Please verify syntax ).
Good luck!
Sent from my Transformer TF101G using xda app-developers app
Click to expand...
Click to collapse
Hello, i cannot do anything if not under CWM (even ls gives a "not found" if not in CWM)
I tried /system/xbin/su and got a
"sh: /system/etc/mkshrc[8]: id: not found"
Rebooted in CWM and tried to install Busybox
i mounted /system /data and /sdcard
i created the folder /data/local/temp
cp /sdcard/busybox /data/local/temp
applied /sbin/chmod 755 to /data/local/temp/busybox
ran /data/local/temp/busybox --install /system/bin and got a "Invalid cross-device link" error on every commands busybox tried to install
http://pastebin.com/g3DMHbJz
Tried to install it on /system/xbin too, but same error
Note : When i use /system/xbin/su in CWM, it change name to [email protected] from ~# while it doesn't in normal mode
Edit : Titanium backup rework :
In CWM, i copied busybox to /system/bin, and i installed it to /system/bin from /system/bin
cp /data/local/temp/busybox /system/bin
/system/bin/busybox --install /system/bin
I'm now checking if only Titanium backup works or if everything else too
Thanks for your help, i don't know if it's done yet, but i made a progress using your information !
Edit 2 : Seems everything works, please send me a private message to talk about candies and chocolat

Magissia said:
Edit 2 : Seems everything works, please send me a private message to talk about candies and chocolat
Click to expand...
Click to collapse
Good to see everything works. Give the candy to some children in the neighborhood mate, I'm watching the calories
Cheers!
Sent from my Transformer TF101G using xda app-developers app

Better way ???

What is better way to unroot you S4 on MF3 Odin back to stock MF3 or by SU full unroot?

It'll somewhat depend on why you want to remove root. But I've always used odin. You will lose all your apps this easy though. I've never tried using unroot inside super su and don't know if it leaves somethings behind.

Personally, I like to make sure everything is completely gone by doing the following:
First remove Safestrap via ADB:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Then, remove SU & Busybox via Root Explorer:
1. Navigate to /system/xbin
2. Delete busybox and SU
3. Naviate to /system/bin
4. Delete SU
5. Uninstall Superuser from the Applications Menu
Finally, nuke the entire thing by ODINing back to MF3 stock with this:
http://forum.xda-developers.com/showthread.php?t=2502003
You really only need to do the last step, but I always like to be extra safe.

jd1639 said:
It'll somewhat depend on why you want to remove root. But I've always used odin. You will lose all your apps this easy though. I've never tried using unroot inside super su and don't know if it leaves somethings behind.
Click to expand...
Click to collapse
One of my friends want to get back to stock with out root so he can push last update tru ADB. He is not using anything what required root but he rooted his phone..Also he want to keep his settings on phone.

jdisco1 said:
Personally, I like to make sure everything is completely gone by doing the following:
First remove Safestrap via ADB:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Then, remove SU & Busybox via Root Explorer:
1. Navigate to /system/xbin
2. Delete busybox and SU
3. Naviate to /system/bin
4. Delete SU
5. Uninstall Superuser from the Applications Menu
Finally, nuke the entire thing by ODINing back to MF3 stock with this:
http://forum.xda-developers.com/showthread.php?t=2502003
You really only need to do the last step, but I always like to be extra safe.
Click to expand...
Click to collapse
Friend of mine don't have SafeStrip on his phone. BTW you can remove last version of SS with appication manager.

2nd step will remove will remove root and leave the rest of the OS intact. I think SU full unroot leaves busybox behind, and you cant delete it without root.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

jdisco1 said:
2nd step will remove will remove root and leave the rest of the OS intact. I think SU full unroot leaves busybox behind, and you cant delete it without root.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cool thanks..

Lost root on Titanium Backup

I have the Verizon VS995 LG20 and rooted via DirtySanta a couple weeks ago. I recently have lost root privilege with Titanium Backup. Root on other apps is fine. The issue may be related to changes I made a week ago in trying to get root access for Secure Settings plugin for Tasker. Secure Settings doesn't work with systemless root. I have tried uninstalling and reinstalling both the su app and Titanium Backup, but I keep getting the same error:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I would appreciate any suggestions in how I can fix this. I would like to make a backup before trying some new roms.

I just ran into this same exact problem. I removed the su files I created in order to get Secure Settings working and Titanium Backup now works. But why did Titanium Backup start having a problem with this all of a sudden and what is the true solution?
Here's what I did to fix Secure Settings from adb shell:
su
mount -o rw,remount /system
touch /system/bin/su /system/xbin/su
mount -o ro,remount /system
So I fixed the problem by just removing the su files. However I want both Secure Settings and Titanium Backup working!!!

TheShanMan said:
I just ran into this same exact problem. I removed the su files I created in order to get Secure Settings working and Titanium Backup now works. But why did Titanium Backup start having a problem with this all of a sudden and what is the true solution?
Here's what I did to fix Secure Settings from adb shell:
su
mount -o rw,remount /system
touch /system/bin/su /system/xbin/su
mount -o ro,remount /system
So I fixed the problem by just removing the su files. However I want both Secure Settings and Titanium Backup working!!!
Click to expand...
Click to collapse
I had a similar issue - TB stopped obtaining root after a kernel change - don't know why. I solved it by changing the su 'dummy' file in /system/bin/su (TB was trying to use this) to a symbolic link pointing at the real su:
Code:
[email protected]:/su # rm /system/bin/su
[email protected]:/su # ln -s /su/bin/su /system/bin/su
Rebooted and TB and SecureSettings can now use root.

Not having this problem but TB does force close alot on me. It started when rom toolbox pro deactivated app manager. Maybe TB has something to do with the dev?