Hi,
I used root_de_la_vega script to replace the existing su with SuperSU. It puts SuperSu.apk in system folder. Then I was able to update SuperSU via Market.
It seems that SuperSU is actually quite smart. It will detect existing su and remove it.
Does this mean you can simply install SuperSU to replace existing SU?
Thanks
Related
I'm running cm7 Barebones on my KF and I've read that SuperSu is supposed to be "better" than regular SuperUser. First, can anyone confirm/deny this? Second, Is it ok to have both installed simultaneously? I can't seem to find a way to uninstall SuperUser. It isn't listed in Titanium backup(SuperSu is) and Settings-->Applications-->Manage Apps only allows me to force stop but not uninstall. Any help/input/comments would be appreciated. Thanks in advance.
Hi, you can remove superuser by deleting /system/app/superuser.apk (I'm assuming SuperSU overwrites /system/bin/su and busybox) and then rebooting. You may use ADB, Root Explorer, ES File Explorer with Root permissions mounting /system as writeable...
As for whether SuperSU is better, that's up to each individual's circumstances. It's best if you read a bit more about the features SuperSU has and then decide on your own: http://forum.xda-developers.com/showthread.php?t=1538053
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.
I have a nvidia shield tv with full android 6.
adb root and and adb remount is working, so I have root access on shell level.
Also I have /system/xbin/su which goes into root if I do not use "adb root".
But root for apps does not work. No app gets root access, RootChecker says "no".
I installed Superuser.apk but this did not help.
What is missing?
I see that this:
java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
Caused by: java.io.IOException: Permission denied
I saw that RootChecker tells me "SELinux enforcing", is this the problem?
I do not want to download any ready-made root miracle and flash the whole device.
Since I have adb root, I can adb push everything.
Just flash su.zip and all will be fine.
I don't need SuperSU. I want to root my device i.e. that apps can execute su.
I have /system/xbin/su but it seems that apps cannot use it.
SuperSU is required to give root access to apps, even with full Android. You will need to flash the zip file from TWRP recovery.
How does SuperSU work?
As far as I understand, there is a /system/xbin/su which is called by apps wanting root access.
This su binary then starts the app to verify access. Right?
Not sure, but I think that su is just for adb and maybe system apps.
On my system I have "adb root" access. But apps do not have root access, I do not have supersu or su.
I am trying to root my huawei P8 lite but WITHOUT using the propriatery SuperSu binary therefore I managed to install the Superuser. But now I am missing the su binary as far I searched I found this su binary https://download.lineageos.org/extras . After that I rebooter to system and typed in my console (with usb debugging enabled):
Code:
adb shell
In the phone's console I typed:
Code:
su
But I get the following error:
Code:
Permission denied
DO you think that SeLinux block me to run su and how I will ovveride this restriction? If not do you have any idea why I cannot execute the su binary?
pc_magas said:
I am trying to root my huawei P8 lite but WITHOUT using the propriatery SuperSu binary therefore I managed to install the Superuser. But now I am missing the su binary as far I searched I found this su binary https://download.lineageos.org/extras . After that I rebooter to system and typed in my console (with usb debugging enabled):
Code:
adb shell
In the phone's console I typed:
Code:
su
But I get the following error:
Code:
Permission denied
DO you think that SeLinux block me to run su and how I will ovveride this restriction? If not do you have any idea why I cannot execute the su binary?
Click to expand...
Click to collapse
You have to flash superSu or magisk or something similiar. There shouldn't be any work around for this. SeLinux has nothing to do with this(I think).
keikari said:
You have to flash superSu or magisk or something similiar. There shouldn't be any work around for this. SeLinux has nothing to do with this(I think).
Click to expand...
Click to collapse
But all these tools need to install somehow the su binary in order to work. What I am trying is to do is ti install it by hand. On GNU/Linux systems that Android is based on use this binary in order to provide su access.
pc_magas said:
But all these tools need to install somehow the su binary in order to work. What I am trying is to do is ti install it by hand. On GNU/Linux systems that Android is based on use this binary in order to provide su access.
Click to expand...
Click to collapse
But that's been purposely prevented. You need to install TWRP recovery then you flash one of them and now you can use "su" command.
I don't know much(read anything) about how linux system works, so I don't understand why you want to get "su" stuff work other than normal way to do it. Meaning is there some specific reason why you don't want to flash SuperSu?
keikari said:
But that's been purposely prevented. You need to install TWRP recovery then you flash one of them and now you can use "su" command.
I don't know much(read anything) about how linux system works, so I don't understand why you want to get "su" stuff work other than normal way to do it. Meaning is there some specific reason why you don't want to flash SuperSu?
Click to expand...
Click to collapse
Because SuperSu is a propriatery software.
pc_magas said:
Because SuperSu is a propriatery software.
Click to expand...
Click to collapse
I think magisk is open source https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 maybe you want to give it a try.
ps. Is open source opposite of propriatery? if not pls ignore this post
I love you you're awesome!!!!!
So I have rooted my Nexus 6p with Magisk v13. Confirmed it worked as I have several apps with SU authority. I'm trying to install V4A. In order to get it to work I need to rename audio_effects.conf in /Vendor/Etc. I'm getting permission issue. How do I mount to get permission? Tried several ways: downloading remount app, using terminal emulator, using adb shell. Not sure what I'm doing wrong. I used to be have permission when I used old systemless root + SuperSU for root.
synnyster said:
So I have rooted my Nexus 6p with Magisk v13. Confirmed it worked as I have several apps with SU authority. I'm trying to install V4A. In order to get it to work I need to rename audio_effects.conf in /Vendor/Etc. I'm getting permission issue. How do I mount to get permission? Tried several ways: downloading remount app, using terminal emulator, using adb shell. Not sure what I'm doing wrong. I used to be have permission when I used old systemless root + SuperSU for root.
Click to expand...
Click to collapse
Just use this and the add ons like JamesDSP. The sound is much better than viper in my opinion.
https://forum.xda-developers.com/android/software/soundmod-ainur-audio-t3450516
Never had this issue with magisk, may you do a clean install, maybe it's magisk, maybe the rom, maybe your Explorer. Anyway, if you only want to rename the file, do it with twrp, boot twrp, mount system, vendor whatever you want to and rename the file with the twrpfilemanager, this will always work.