Database Users

Superuser?

Does anyone know how to install this on the aria?
http://forum.xda-developers.com/showthread.php?t=682828

It's best to flash your Aria to a Liberated ROM. You can find it within the forums here. Since I can't post links yet. This will root the device and SuperUser will be added.
Not sure about that app. It looks like it does the same thing as the SU that comes in the Liberated ROM by attn1, just without the few extra options.

I tried booting into clockwork and mounting the system partition and doing this:
adb push Superuser.apk /system/app
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb reboot
but when it rebooted the superuser app did nothing at all. No prompt or nothing running apps that needs su. I had usb debugging enabled. So I just restored a nand backup.

Might be a dumb question, but did you do adb remount ?

I used clockwork to mount the system partition. When I tried it with just adb remount it wouldn't mount the system partition. I would always get "Not a directory" error. But when clockwork mounted the partition it wrote the files fine with no error. When I rebooted the superuser icon and version were different than the one that came with the liberated rom.

I'm trying this now, I'll report back when I do it. I'll try a few different apps that require SU

I did the commands it said, I see the new icon, and when I press 'Menu', it shows the prefrences, but when I click it, it freezes the app.

It's probably not compatible with our phone yet.

Could be, but I'm pretty sure it does work, because if I remember correctly, Titanium Backup needs SU permissions, and I haven't encountered any kind of errors with it yet.

I see you posted on the thread for the program itself. Hopefully someone there will have a response.

Yeah, I'm hoping to get a response to it. We will see.

The newer version 2.2.2 works.

Awesome, ill give it a shot a little later.

Tried the newer version, and I get the same issues.

How did you install this one? I booted in to clockwork and selected install from zip file on sd and selected that file on my sd card.

I just did it through adb. I'll give that method a shot.

Looks like after doing your method, it works perfect now. Not sure why using adb doesn't work.

[Q] Superuser permissions not working well

Now I know I'm rooted. I unlocked my bootloader, flashed CWM 3.0 and installed the Superuser (ef) and even installed Rom manager and gave it permission. But for some reason almost every other rooted app I download and try to use it says that my phone isn't rooted?? I'm using a Nexus S. Anybody had similiar issues and resolved it? Thanks for all responses.

Yes the answer has been posted. Go into the recovery from rom manager or by volume and power. Go to mounts and storage and mount / system. You are see it unmount now so mount the system.

You may also need to zap the system with chmod.
You do this by going into Clockwork Recovery's Mounts & Storage. Mount /system. Then in ADB from your computer type in:
1) adb shell
2) cd /system/bin
3) chmod 6775 su
exit and reboot.

semi-success: delayed update to 6.3 and preserved root

This did not go exactly as I had planned but it ended up ok anyway and I learned some.
I am using a rooted stock rom. First, my idea was to prevent the auto update to 6.3. Second, I wanted to see if it was possible to somehow preserve root so that I wouldn't have to re-root after the update, because I am not really thrilled by the idea of installing a new boot loader and so on; I would prefer to make the minimum modifications necessary to do what I need.
The first goal appeared to be well-served by using droidwall. I used whitelist mode and blocked everything that I couldn't tell had an obvious need to access the net. I posted more detail here. From the time the update started going out until today when I had time to actually try my update, I did not receive the update automatically. So that appeared to work.
Next, my idea was to simply make a copy of /system/xbin/su to a place that wouldn't get overwritten by the update.
# mkdir /data/lunchmeat
# cat /system/xbin/su > /data/lunchmeat/salami
# chmod 6755 /data/lunchmeat/salami
The idea being that since it's still setuid root, I'd be able to execute it and become root after the update. (I just picked a silly name in case something looked for su and blew it away).
So, I turned off wifi, disabled droidwall, manually updated (copied the updates into kindleupdates and so on) and after it rebooted, I opened the terminal app and tried to execute my salami binary. I got permission denied, and the superuser app said that superuser permission was denied on the terminal app. Hmmm....
Couldn't figure out why it was behaving that way so I thought I'd try adb root, and whadya know, I had a root shell.
remounted /system read-write, copied su back into /system/xbin, renamed /system/bin/check_rooted to /system/bin/check_rootedx, created an empty executable /system/bin/check_rooted, and rebooted...
...and everything is (rooted) as it was before. I re-enabled droidwall. google play seems to be working.
Why did 'adb root' work for me after the update? That might be a good question to answer, since it could make the re-rooting process much simpler for people! 2 or 3 commands and you're done.
edit: ohhhhh, stupid me! /data is mounted nosuid. / seems to get blown away on every reboot, so even if I remount it read/write and put su there, it gets lost.
And, also, I just remembered that I did what jcase said in this post which is what allowed me to keep adb root working.
So, so far this idea is going nowhere.

Just rooted - unable to backup

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.

Help Rooting N10, Busybox

I just rooted my N10, there is a step to install busybox in the /xbin folder but I accidentally picked /system/bin. Then I hit uninstall and busybox said there is an error. How can I fix this and install it to /xbin without messing anything up?
Thanks!
edit: problem fixed, softbrick, redid everything, working now!