I am constantly having issues with the built in superuser app in most 4.3 roms (in settings) and /system and "sdcard" storage... is there any way to update the built in su binary?
Right now I'm stuck installing supersu instead to get things to work right. I'd prefer to use the built in superuser though to avoid conflicts
On a side note, why do most roms include the most incompatible superuser app for 4.3 anyway? (I've found supersu works best, followed by superuser from the market with only a few issues, and the built in one does not work well at all with 4.3)
metalspring said:
I am constantly having issues with the built in superuser app in most 4.3 roms (in settings) and /system and "sdcard" storage... is there any way to update the built in su binary?
Right now I'm stuck installing supersu instead to get things to work right. I'd prefer to use the built in superuser though to avoid conflicts
On a side note, why do most roms include the most incompatible superuser app for 4.3 anyway? (I've found supersu works best, followed by superuser from the market with only a few issues, and the built in one does not work well at all with 4.3)
Click to expand...
Click to collapse
I dont know if you can change anything about superuser.. But you could have a look at developer settings. There are some settings regarding root access..
They use superuser because its open source. Supersu isnt (as far as I know)
Sent from my Galaxy Nexus using XDA Premium HD app
Related
I use the stock 4.0.3 rom, rooted by flashing the su binary to system.
Now I updated to the latest superuser market app, and it sees that there's a new version of su binary.
But when I try to update to this new su binary, everything else goes fine, but when it reaches the last step "Making sure new su works...", it says "Fail!".
What's going on?
Problem
I HAVE THIS PROBLEM Too i contacted chainfire but he doesnt answer me back.
Same issue here as well. It still grants all my apps superuser privileges though. I wonder if it matters?
Sent from my SGH-T989D using xda app-developers app
Should I make a flashable zip with the latest su? That would work.
Sent from a sexy turtle.
Same, lost root after cm10 flash, su fail.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
yes I'm having the same issue after flashing new ROM...but Tit Backup won't gain Root! ^^
Same issue.. The newest SU update is a fail. It's a total shock because it's always been solid in the past. We wouldn't be doing half the things we do on our phone without it
Sent from my SGH-T989 using xda premium
I also noted this when trying to update the binary on my GTab 7510. Only things I can suggest are choosing a ROM that has the latest Superuser + binary included, re-rooting with a newer root package, or uninstalling the update (although you constantly get the update notification which is annoying).
Same thing used to happen to me whenever I would try switching from SuperSU to Super User. Seems like SU anything from the market doesn't play nice with our phones.
i just reflash a root zip or superuser zip and that usually fixes it for me. no idea why its happening though.
I am running AOKP JB B1, just like suddenly, some of my Apps like DX tool box and DX power booster can't gain root access anymore, but other apps like root explorer work fine, I tried to update supersu and binary, no good.
Then I thought maybe I screw up the system because lots kernel flashed, so I just reflash AOKP JB B1 with full wipe , but still no good...
Could it be application compatibility problem or something wrong at my end?
Sent from my Galaxy Nexus using xda premium
qtwrk said:
I am running AOKP JB B1, just like suddenly, some of my Apps like DX tool box and DX power booster can't gain root access anymore, but other apps like root explorer work fine, I tried to update supersu and binary, no good.
Then I thought maybe I screw up the system because lots kernel flashed, so I just reflash AOKP JB B1 with full wipe , but still no good...
Could it be application compatibility problem or something wrong at my end?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
3rdstring said:
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
Click to expand...
Click to collapse
No good, I tried installed superuser
Sent from my Galaxy Nexus using xda premium
3rdstring said:
Just a guess but some apps look for Superuser.apk to confirm root access. If your ROM has SuperSU.apk as SuperSU.apk that could be the issue. When I flash a ROM with SuperSU I always change the name to Superuser.apk.
HTH
Click to expand...
Click to collapse
the supersu apk is named Superuser.apk as well for compatibily purpose
@OP flash in recovery SuperSU.zip solve all ur problems
andQlimax said:
the supersu apk is named Superuser.apk as well for compatibily purpose
@OP flash in recovery SuperSU.zip solve all ur problems
Click to expand...
Click to collapse
still no good , DX tool box still says "Root not allowed, the operation is denied"
i also tried in CodenaAndroid and XeonHD , doesn't work on both of them , it should be applications compatibly preblem.
qtwrk said:
still no good , DX tool box still says "Root not allowed, the operation is denied"
i also tried in CodenaAndroid and XeonHD , doesn't work on both of them , it should be applications compatibly preblem.
Click to expand...
Click to collapse
a. update your busybox, use stericsons busybox updater from the play market. open the app, update busybox.
b. open your superuser or supersu app and make sure that your binaries are updated and that root is enabled. superuser has known issues with jelly bean.
c. if aokp has an optional root or no choice, enable root.
simms22 said:
a. update your busybox, use stericsons busybox updater from the play market. open the app, update busybox.
b. open your superuser or supersu app and make sure that your binaries are updated and that root is enabled. superuser has known issues with jelly bean.
c. if aokp has an optional root or no choice, enable root.
Click to expand...
Click to collapse
unfortunately , still can't , busybox is updated. SuperSu has updated the binaries as well and i even set to gain permission without asking, still can't
all other apps like ROOT EXPLORER , TRITIUM BACK UP, FRANCO KERNEL UPDATER, PGM2 and something more were able to gain access to root , only these 2 can't
this is the app that can not gain access ...
qtwrk said:
unfortunately , still can't , busybox is updated. SuperSu has updated the binaries as well and i even set to gain permission without asking, still can't
all other apps like ROOT EXPLORER , TRITIUM BACK UP, FRANCO KERNEL UPDATER, PGM2 and something more were able to gain access to root , only these 2 can't
this is the app that can not gain access ...
Click to expand...
Click to collapse
its the app. and on top of it, it doesnt want to close, it wants to run itself and download/send data. i uninstalled it really quick.
simms22 said:
its the app. and on top of it, it doesnt want to close, it wants to run itself and download/send data. i uninstalled it really quick.
Click to expand...
Click to collapse
It's app for system optimization or something like firewall, kill auto run apps, process management...
Ok... were you able to get root access?
Sent from my Galaxy Nexus using xda premium
Im currently running JMT which uses SuperSU. I would like to use Superuser. Ive tried just flashing Superuser, but how to remove SuperSU?
I posted this in the ROM's thread, but never got an answer so hoping someone here will know
Delete the Superuser.apk in the ROM (it's really SuperSU) and pull the "real" Superuser.apk from somewhere else.
Sent from my Nexus 4 using xda premium
android88 said:
Delete the Superuser.apk in the ROM (it's really SuperSU) and pull the "real" Superuser.apk from somewhere else.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
blackangst said:
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
Click to expand...
Click to collapse
I'm curious, but would it just be a matter of updating the binaries with Superuser?
treefrog321 said:
I'm curious, but would it just be a matter of updating the binaries with Superuser?
Click to expand...
Click to collapse
Well, I downloaded a fresh copy from the market, and when I open it it doesn't update. Just shows no apps are assigned to it..
Sent from my SGH-T989 using xda app-developers app
blackangst said:
I did so (system-->app), installed superuser, rebooted, cleared dalvik and fixed permissions...still getting the supersu shell message with apps, and still showing up on installed programs...what did I miss?
Click to expand...
Click to collapse
There are some /bin and /xbin files too.
Sent from my Nexus 4 using xda premium
blackangst said:
Im currently running JMT which uses SuperSU. I would like to use Superuser. Ive tried just flashing Superuser, but how to remove SuperSU?
I posted this in the ROM's thread, but never got an answer so hoping someone here will know
Click to expand...
Click to collapse
Um, even easier...
Download SuperUser recovery flash zip and while still inside Android on device go to file manager open /system/apps and delete the SuperSU.apk
Now restart to recovery clear the cache and dalvick cache
choose install from SDCard
Find where you downloaded SuperUser.zip and flash
Restart
SuperSU is WAY better at handling Super User requests [for instance, it has a wait state on the pop-up where it does not go quite as fast so some apps that take a min to request super user and another min to display the pop you aren't already at 1 - 2 seconds] and for instance for quite some time Super User was known to seg fault [basically an error happens and it doesn't work to grant access right when that happens] whereas SuperSU was created later to kinda address that and some other issues in SuperUser [not saying SuperUser is bad it is updated and does it's job, it's just SuperSU does it better].
Just if any guide says use SuperUser just replace SuperUser with SuperSU when doing something and in app drawer just look under SuperSU for it's app and not SuperUser.
Thanks for the help and input guys
blackangst said:
Thanks for the help and input guys
Click to expand...
Click to collapse
Did you get it working the way you wanted?
RealPariah said:
Did you get it working the way you wanted?
Click to expand...
Click to collapse
Im gonna follow the advice that supersu is better and use it for awhile
RealPariah said:
Um, even easier...
Download SuperUser recovery flash zip and while still inside Android on device go to file manager open /system/apps and delete the SuperSU.apk
Now restart to recovery clear the cache and dalvick cache
choose install from SDCard
Find where you downloaded SuperUser.zip and flash
Restart
SuperSU is WAY better at handling Super User requests [for instance, it has a wait state on the pop-up where it does not go quite as fast so some apps that take a min to request super user and another min to display the pop you aren't already at 1 - 2 seconds] and for instance for quite some time Super User was known to seg fault [basically an error happens and it doesn't work to grant access right when that happens] whereas SuperSU was created later to kinda address that and some other issues in SuperUser [not saying SuperUser is bad it is updated and does it's job, it's just SuperSU does it better].
Just if any guide says use SuperUser just replace SuperUser with SuperSU when doing something and in app drawer just look under SuperSU for it's app and not SuperUser.
Click to expand...
Click to collapse
Can I do this with replacing Superuser with SuperSU (I'm running Avatar ROM & I miss using SuperSU)?
Guys/Gals,
I am running the newest version of PACman ROM by klin1344 on KToonsez Ktweaker kernel.
Cleanly installed, with newest Gapps
What I need help on:
I have an in settings superuser app (the new opensource settings integrated one from Koush) and I also have the standard SuperSU.
I was able to remove SuperSU, but wasn't getting prompted for any root requests afterwards. I also then went into the in-settings SU app to update the binary but wasn't prompted at all. I am wondering if I SHOULD be seeing a binary update prompt from the in-settings SU app? (this might be the extent of my issue) or if more steps need to be taken to migrate from 2 separate apps to one.
Any help is greatly appreciated!
Links to info I looked at: http://www.droiddog.com/android-blo...s-the-play-store-brings-open-source-goodness/
http://www.droiddog.com/android-blog/2013/03/cyanogenmod-integrates-cwm-superuser-into-settings/
http://forum.xda-developers.com/showthread.php?p=38760467
Edit:
turns out, after removing SuperSU and rebooting I still retained access to root but I am no longer getting prompted for it nor do any of the apps requesting the permission get logged in the in-settings Superuser app.
You need to install the superSU app
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Gotcha and that handles which apps get access correct?
Is there anyway to boil it down to the single in-settings app? Or do u think supersu is the only way, currently, to handle su requests?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have aTMO M919 SGS4 rooted and running the latest CM10.2 nighties. I have tried following instructions to enable wallet by installing xposed. I keep getting an error like xposed framework not installed with a number of write errors pointing to /data/data. Using root explore to make /system writable did not help. Does anyone have any idea how to get xposed working on our device running cm10.2? Or another workaround four wallet? Thanks very much.
omgdz said:
I have aTMO M919 SGS4 rooted and running the latest CM10.2 nighties. I have tried following instructions to enable wallet by installing xposed. I keep getting an error like xposed framework not installed with a number of write errors pointing to /data/data. Using root explore to make /system writable did not help. Does anyone have any idea how to get xposed working on our device running cm10.2? Or another workaround four wallet? Thanks very much.
Click to expand...
Click to collapse
I believe xposed is for touch wiz based Roms only
Sent from my SGH-M919 using XDA Premium 4 mobile app
omgdz said:
I have aTMO M919 SGS4 rooted and running the latest CM10.2 nighties. I have tried following instructions to enable wallet by installing xposed. I keep getting an error like xposed framework not installed with a number of write errors pointing to /data/data. Using root explore to make /system writable did not help. Does anyone have any idea how to get xposed working on our device running cm10.2? Or another workaround four wallet? Thanks very much.
Click to expand...
Click to collapse
There are a few more steps you need to follow in addition to just using xposed. This is what I did to get it working on mine.
First you need to modify the build.prop to the Sprint version:
ro.product.model=SPH-L720
ro.product.name=jfltespr
ro.product.device=jfltespr
Second you need to install SuperSU with the 1.51 binary (install from recovery)
http://forum.xda-developers.com/showthread.php?t=1538053
xposed will not work with CM's Superuser, you need SuperSU
After you install xposed 2.14 and restart you should be able to setup Wallet
Once Wallet is setup you can edit the build.prop back to TMO
ro.product.model=SGH-M919
ro.product.name=jfltetmo
ro.product.device=jfltetmo
**Each time you flash a new nightly you will need to re-install the SuperSU binary and the xposed binary from inside the app.
Thank you so much! Worked perfectly.
Well, almost... I couldn't download the zip file properly with cm10.2 and Chrome... the downloaded file was to small/corrupted. I downloaded from my PC, transferred the file to my phone, then proceeded and now I have wallet!
Thanks again, I[E!
No problem, Chrome seems to have issues downloading from some sites. Regular browser usually works though.
Glad it worked out for you.
Sent from my SGH-M919 using Tapatalk 4