So ParanoidAndroid comes with SuperSU out of the box which I don't really like as Superuser seems much cleaner to me. However, I can't seem to figure out how to replace SuperSU with Superuser. Flashing the .zip from http://androidsu.com/superuser/ only adds Superuser with SuperSU remaining on the device as well.
Does anyone know how I should go about replacing SuperSU on ParanoidAndroid with traditional Superuser? It's been difficult looking for a tutorial as most people prefer SuperSU over Superuser.
I believe you can just install Superuser (I think it's in Play Store?), then SuperSU will prompt for SU rights for Superuser. Then once this is done, uninstall SuperSU. I could be wrong though
In any case, I also hear SuperSU actually works better.
espionage724 said:
I believe you can just install Superuser (I think it's in Play Store?), then SuperSU will prompt for SU rights for Superuser. Then once this is done, uninstall SuperSU. I could be wrong though
In any case, I also hear SuperSU actually works better.
Click to expand...
Click to collapse
When installing from the Play Store, it is installed as a regular app and can be uninstalled easily as it is not a system app.
Iunno, I just prefer Superuser as it seems more refined, in my opinion. To each their own though.
Install superuser, reboot, uninstall supersu using titanium backup or another app thst will le you uninstall system apps then reboot.
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
Install superuser, reboot, uninstall supersu using titanium backup or another app thst will le you uninstall system apps then reboot.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Titanium backup actually hides Super User apps so you would have to use a root explorer to go to system/apps and remove SuperSU
Related
I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..
Hi
I have been using clockworkmod superuser on stock 4.3 with no problems. However I have just flashed a new kernel and am now getting the message that the SU binaries are out of date. I have tried re-flshing the superuser.zip with CWM but still have the same message and of course no root. Is it possible to replace superuser with the latest supersu and see if that gets my root back. If so how I do it and will I then be able to unistall the clockwork superuser app once supersu is up and running.
Thanks
Andy.
g1dtf said:
Hi
I have been using clockworkmod superuser on stock 4.3 with no problems. However I have just flashed a new kernel and am now getting the message that the SU binaries are out of date. I have tried re-flshing the superuser.zip with CWM but still have the same message and of course no root. Is it possible to replace superuser with the latest supersu and see if that gets my root back. If so how I do it and will I then be able to unistall the clockwork superuser app once supersu is up and running.
Thanks
Andy.
Click to expand...
Click to collapse
just flash the latest supersu flashable. search google for supersu, youll find it asap. its better than the latest superuser.
simms22 said:
just flash the latest supersu flashable. search google for supersu, youll find it asap. its better than the latest superuser.
Click to expand...
Click to collapse
cool wikll give it a try once flashed will it replace the current superuser app or will i have to uninstall remove it manually?
g1dtf said:
cool wikll give it a try once flashed will it replace the current superuser app or will i have to uninstall remove it manually?
Click to expand...
Click to collapse
itll add the supersu app
simms22 said:
itll add the supersu app
Click to expand...
Click to collapse
By that do you mean it replaces the superuser that is currently installed or adds it as an additional app. Sorry for the confusion but still a little confused with the various methods of obtaining root with the various superusers etc.
g1dtf said:
By that do you mean it replaces the superuser that is currently installed or adds it as an additional app. Sorry for the confusion but still a little confused with the various methods of obtaining root with the various superusers etc.
Click to expand...
Click to collapse
itll add the supersu app, youll probably have to uninstall the superuser app by yourself.
simms22 said:
itll add the supersu app, youll probably have to uninstall the superuser app by yourself.
Click to expand...
Click to collapse
Thanks for the help and will let you know how I get on once I get it downloaded and installed.
Installed the zip and everything is now working ok and I have root back. The supersu app replaced the origional superuser app so nothing to uninstall/delete.
Thanks Again
Andy.
g1dtf said:
Installed the zip and everything is now working ok and I have root back. The supersu app replaced the origional superuser app so nothing to uninstall/delete.
Thanks Again
Andy.
Click to expand...
Click to collapse
sweet
Hi guys,
I have rooted my phone with ioroot method. It came with SuperUser Apk, now I want to change it with SuperSU.
Can I just install SuperSU then uninstall SuperUser without losing root access?
That's what I did. SuperSU works fine for me. You can always install SuperSU, make sure it works (it should), then uninstall Superuser.
Uninstalling SuperUser does not remove root access and you can do that. However if you don't turnaround and install a superuser type of app (ex: SuperSU) shortly and then try to access an app that requires root (ex: Titanium Backup), then you will not be able to use the app. It is best practice to install a superuser app as soon as you install another one to ensure there are no issues.
Hello all,
I've been running into some issues with Superuser and SuperSU while running the CM11 nightlies. I restore all of my apps using the built-in Superuser from CM11, and then I go into SuperSU to update the binary (I want to use SuperSU as my main Root app) and update the binary successfully. All is well, but then it seems that Superuser will then take over as my main root app and then I need to continuously update the SuperSU binary.
Does anybody have any idea why SuperSU is not sticking as my root app, or how to "disable" Superuser?
skadude66 said:
Hello all,
I've been running into some issues with Superuser and SuperSU while running the CM11 nightlies. I restore all of my apps using the built-in Superuser from CM11, and then I go into SuperSU to update the binary (I want to use SuperSU as my main Root app) and update the binary successfully. All is well, but then it seems that Superuser will then take over as my main root app and then I need to continuously update the SuperSU binary.
Does anybody have any idea why SuperSU is not sticking as my root app, or how to "disable" Superuser?
Click to expand...
Click to collapse
i think you can only have one or the other not both running
jaythenut said:
i think you can only have one or the other not both running
Click to expand...
Click to collapse
I can't find a way to disable Superuser without completing removing Root Access for my phone.. :/ Do you know how to disable Superuser?
skadude66 said:
I can't find a way to disable Superuser without completing removing Root Access for my phone.. :/ Do you know how to disable Superuser?
Click to expand...
Click to collapse
on cm dont think you can ask on your rom thread
jaythenut said:
on cm dont think you can ask on your rom thread
Click to expand...
Click to collapse
Thanks, I'll try that out!
I did a semi search on how to get busybox working on Oreo, found chatter of using this app for busybox but for a different phone. I figured it wouldn't hurt to try. I needed BusyBox for Cerberus app to work and block the status bar access.
I downloaded this app https://play.google.com/store/apps/details?id=ru.meefik.busybox
Go to it's settings and change your install path *if your using supersu like I am path is:
/sbin
After you set your path, install. Then reboot.
After boot the BusyBox app used states that busybox wasn't installed but when I used a BusyBox checker app it's installed and working. My Cerberus app works too and blocks the status bar from locked screen. Busybox has been working after reboots. It sticks
Anyways, busybox is working on Oreo ver.11
Question: Now that you've installed that, can you still boot TWRP on your device and have it still ask to decrypt your file system? I've attempted 3 times with different types of busybox install locations, and each time I install it to anywhere in /system/, TWRP no longer prompts for the decryption key or password to access the file system.
ToolB0x said:
Question: Now that you've installed that, can you still boot TWRP on your device and have it still ask to decrypt your file system? I've attempted 3 times with different types of busybox install locations, and each time I install it to anywhere in /system/, TWRP no longer prompts for the decryption key or password to access the file system.
Click to expand...
Click to collapse
I boot to TWRP using fastboot boot TWRP.img it works for me. I still get the decryption prompt. I didn't install in system/
I installed in /sbin
Please look at pic
Rooted?
Sent from my Pixel XL using Tapatalk
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
I mean do you have root after boot? What version of su are you using?
Sent from my Pixel XL using Tapatalk
Does this Busybox/method make V4A work on Oreo? Anyone with any success?
I think this is the best busybox. It does not break Root. Flash in recovery.
Tulsadiver said:
I think this is the best busybox. It does not break Root. Flash in recovery.
Click to expand...
Click to collapse
Full thread?
sliding_billy said:
Full thread?
Click to expand...
Click to collapse
This is where it came from but I wouldn't flash the latest. Stick with this one for now.
https://forum.xda-developers.com/and...archs-t3348543
Tulsadiver said:
This is where it came from but I wouldn't flash the latest. Stick with this one for now.
https://forum.xda-developers.com/and...archs-t3348543
Click to expand...
Click to collapse
That link doesn't work.
sliding_billy said:
That link doesn't work.
Click to expand...
Click to collapse
Try this one.
https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
That worked. Thanks.
Thanks, this thing worked, just make sure to mount system first before flashing=)
Stericson Busybox has been updated and is in the Play Store. Installs to the default location. All works after install and after reboot including root (I am using SuperSU 2.82 SR4), suhide and Adaway. Patience pays off in this case. I have always had the best luck with this dev's work.
sliding_billy said:
Stericson Busybox has been updated and is in the Play Store. Installs to the default location. All works after install and after reboot including root (I am using SuperSU 2.82 SR4), suhide and Adaway. Patience pays off in this case. I have always had the best luck with this dev's work.
Click to expand...
Click to collapse
Been waiting for this. Thanks for the update cuz it made my day... And if all my Fantasy teams and the Vikings win...that will really make my day. Lol
Sent from my Pixel XL using Tapatalk
I just updated to Stericson Busybox. I Installed to /sbin/supersu/xbin and all functioning as expected. Even after re-boot.
Deleted: nevermind, good to go now
Did this, lost root. Re-Flashing Su does not work (no root no su app) Cannot uninstall busybox due to lack of root.
Any suggestions on how to fix this?
I've had success installing busybox via the Magisk Manager as they have it as a module you can install. It was as easy as installing Magisk, choosing their BusyBox module, and restarting my phone. Now I can use Lucky Patcher / any other app that requires it without a problem, Systemless-ly rooted, no custom recovery or kernels.
Any update!??
Its called osm0sis BusyBox for ndk