Related
I am booting from SD Card for the NC. I am trying to install busybox so I can can get the full version of Titanium Backup to work properly.
The error message I'm getting is /system/xbin/ could not be mounted as RW, the install will fail.
If I click on install it just hangs there until I finally press and hold the power button to perform a reboot.
Is there something that I'm missing on this?
Thanks,
Dubg
It sounds as if you don't have SU. Head to Market and update/install the SuperUser app. Also, try letting Titanium Backup install its own BusyBox (it'll prompt for it if it doesn't detect one).
You can also try getting BusyBox off the market, look for BusyBox Installer or some such.
Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.
cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer
cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again
I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.
cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.
Hello,
My S4 is rooted, es3 cannot delete, move or change permission.
With a terminal under su, chmod or rm - Rf gives Access Denied.
The directory is a clockworkmod created by backup, named backup.
Suggestions ?
Hi there,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
[email protected] said:
Hello,
My S4 is rooted, es3 cannot delete, move or change permission.
With a terminal under su, chmod or rm - Rf gives Access Denied.
The directory is a clockworkmod created by backup, named backup.
Suggestions ?
Click to expand...
Click to collapse
I am on cm12 nightly.
On modern versions of CWM, you should always use the delete function within the backup and restore menu to remove nandroid backups. This is because CWM by default automatically does incremental backups whenever you make a nandroid. Manually deleting nandroid backups when CWM is set up for incremental backups is a really bad idea, as it screws up every single nandroid backup you have, including the master backup. Thus CWM protects the nandroid backup directory.
So, to recap, enter CWM, go to "backup and restore", then delete your nandroid backup from there. After that, go to "free unused backup data" and select it to have CWM restore access to the now freed space.
Thanks for the explanation.
Rom Manager is not installed at present. I am using TRWP manager instead.
I installed CWM Backup manager from Guimberg .
I could pull the backup to a new folder, but delete the original clockworkmod folder did not work.
Would I need to have a cwm recovery installed in order to delete cwm backups ?
You didn't mention you had replaced CWM with TWRP. So, before putting CWM back on to the S4 and using it to wipe away the directory, did you change permissions in ES File Explorer or execute a chmod 777 command in Terminal? Since permissions is the issue here you have to change them.
Being in su I used chmod 777 and rm -rf as well as trying with es3 to change permission but always got "access denied".
I also try with twrp recovery file manager.
I have busy box and sudo installed.
The directory is at /mnt/shell/emulated/
In a nutshell I cannot change permission.
Replace TWRP with CWM, delete the nandroid backups and free the space. Then restore TWRP and you should be good to go. If that doesn't work, your only other alternative is to reset.
I replaced and try, but the only change I could do is the rename of the bu and a zip. Delete was denied.
It is a minor isue since the file is only 255MB. I guess that their are some bits corrupted somewhere and therefore as you suggested a format will fix it.
I will wait for a better reason to do that and live with the bu files happily.
Thanks for your advises.
Didn't find the thanks button. I didn't not understood near the quote as the location for doing it?
Thanks button is on the left, at the bottom of each post under the user information.
Done
After doing a restore with CWM of 4.4.4 backup, I'm unable to save files to user storage. Owner is 0 root, GID is 1028 sdcard_r, permissions drwxrwx--x, same as on my N7 '13.
Drive can export a file to ./Downloads though. ?:| Other files can save to that folder.
Have tried with Nova Launcher backup (can save backup file to ./Download, but no other), ES File manager ("EACCES (Permission Denied)"), Total Commander file manager. Helium backup can't backup locally either.
Noticed yesterday that I couldn't delete folders or move files from folders (Alarms, Notifications, Pictures), so did it in Recovery with ADB shell. Think that's just another symptom.
Never encountered this before. Anyone ever see this, fixed this?
Oh, one note. During my 5.1.1 order, I did a fresh wiped boot of 4.4.4, set up accounts and basic apps, and did a CWM backup. Moved it off with adb (adb pull /sdcard/ ./sdcard/).
After flashing 4.4.4 completely, I used CWM and adb push to move the entire backed up /sdcard/ back to the device so I could do a restore (adb push /sdcard/ ./sdcard/). Restored in CWM.
Could this have been an issue? /sdcard/ created by adb ?
Solved. Did a CWM backup and was readying to pull that off, and checked on a hunch. After mounting /data/, I shelled in (adb shell) and checked permissions (ls -ald /sdcard/0/ ) and lo and behold -- many (not all) of the folders were owned by root:root, not media_rw:media_rw. /sdcard/0/Download/ was not.
Changed ownership of all under /sdcard/0 (chown -R media_rw:media:rw * ) rebooted, and can save in those folders again. Hopefully that didn't bork something else up.
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?