need help
i deinstall supersu by mistake..
so i run auto-root again but supersu said su-file is not installed.
What can i do???
Thanks for help!
If you had root and all you did was uninstalled SuperSU, you should just be able to reinstall SuperSU from Google Play Store. You don't lose root by uninstalling the app. You would loose root if you say unrooted through the app w/o backing up your root.
Xdad_0001 said:
If you had root and all you did was uninstalled SuperSU, you should just be able to reinstall SuperSU from Google Play Store. You don't lose root by uninstalling the app. You would loose root if you say unrooted through the app w/o backing up your root.
Click to expand...
Click to collapse
Thanks for answer.
First how can i backup?
And when i uninstall in supersu - how can i get root back?
After about 16 hours supersu work again. I just rebootet 15 times - but everytime supersu said: su-file not installed and now it worked.
I thougt i will hopeless - im just begann to flash...
Related
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
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!
Hi all, I just want to share this. Regarding to Kinguser cant be replace by SuperSU, I just solve this issue. But, I want to make it clear,
I FOUND THIS METHOD ACCIDENTALLY(by experimenting).
I just got Samsung Galaxy Grand Duos I9082, with home button not functioning. So I cant root it by custom recovery, which made me use Iroot(known as Vroot), 1 click rooting app. It will root using Kinguser binary. Which will give problem to replace it with SuperSU. Then install busybox.
So I reroot my phone using KingO root which will install SuperSU v2.02. I guest this is the point where SuperSU bin get hook in device(I tried installing various ver of SuperSU without success,"Installing Failed". And KingUser give perm to SuperSU using KingO root method.
So I go into SuperSU, install as system, reboot, install custom recovery, install SuperSU.zip thru recovery, reboot, uninstall KingUser(it will warn this will unroot your device back to normal, i just ignore and proceed), and this will erase SuperSU app too, but I guest it leave the binary installed. And again I reinstall SuperSu in normal way, with success.
And again, I'm not telling the best solution, just want to share what I've done. Hope this will help someone.
Good Day
I try to replace King User with the Terminal Emulator Method, and King User gone, but it unroot mi device
I have a Samsung i8200L.
After, I re-root my device (now with Kingo Root, thanks for mention it in your thread), and everything is ok, with SuperSU
Naimlaaa said:
Hi all, I just want to share this. Regarding to Kinguser cant be replace by SuperSU, I just solve this issue. But, I want to make it clear,
I FOUND THIS METHOD ACCIDENTALLY(by experimenting).
I just got Samsung Galaxy Grand Duos I9082, with home button not functioning. So I cant root it by custom recovery, which made me use Iroot(known as Vroot), 1 click rooting app. It will root using Kinguser binary. Which will give problem to replace it with SuperSU. Then install busybox.
So I reroot my phone using KingO root which will install SuperSU v2.02. I guest this is the point where SuperSU bin get hook in device(I tried installing various ver of SuperSU without success,"Installing Failed". And KingUser give perm to SuperSU using KingO root method.
So I go into SuperSU, install as system, reboot, install custom recovery, install SuperSU.zip thru recovery, reboot, uninstall KingUser(it will warn this will unroot your device back to normal, i just ignore and proceed), and this will erase SuperSU app too, but I guest it leave the binary installed. And again I reinstall SuperSu in normal way, with success.
And again, I'm not telling the best solution, just want to share what I've done. Hope this will help someone.
Good Day
Click to expand...
Click to collapse
Easiest method that worked for me!
Use es file explorer
change permision to /system/bin to rw, tick all
run updated supersu, it will ask to update su binary, use the normal option
Kinguser will ask permission from SuperSu, DENY!
Then you can successfully remove kinguser
Newyork! said:
Easiest method that worked for me!
Use es file explorer
change permision to /system/bin to rw, tick all
run updated supersu, it will ask to update su binary, use the normal option
Kinguser will ask permission from SuperSu, DENY!
Then you can successfully remove kinguser
Click to expand...
Click to collapse
I'm assuming you used SSU 2.49? As Chainfire said, he made this mostly for lollipop comparability, also for Kinguser replacements issues.
And thanks for sharing the workaround you've figured.:thumbup:
Sent from here to there
Naimlaaa said:
I'm assuming you used SSU 2.49? As Chainfire said, he made this mostly for lollipop comparability, also for Kinguser replacements issues.
And thanks for sharing the workaround you've figured.:thumbup:
Sent from here to there
Click to expand...
Click to collapse
I didn't figure it out. it just worked for me!
Newyork! said:
I didn't figure it out. it just worked for me!
Click to expand...
Click to collapse
Maybe someone will need it later, lucky them found an easy and more practical way.:thumbup:
Sent from here to there
Hope this will work
Worked on Galaxy S3 NEO ( GT-I9300I ) Android 4.4.4
The Steps that worked for me are as follows:
Start from HERE
1. Same steps untill SuperSu installed
2. When SuperSu launched itself (or you can launch it manually ) , it
will ask to update SU Binary, Click Normal.
3. Wait until SuperSu says other user management app detected (in my
case) and will ask you to remove it. Click cancel ( very important ).
4. When you Click Cancel, it will say Binary updated Successfully. And
will ask you to Reboot or OK. Click OK ( very important ) and not to
Reboot.
5. Now SuperSu will open normally but KingUser app will still be present
( in my case).
6. Now go to Settings in SuperSu App and Go to Clean Up options and
there you will find an option to remove other User Managemnt apps, just
click the option and Boom SuperSu will remove it completely from your
System.
Hope this will work for someone else also.
2nd Method:
Just simply install SuperSu from Play Store and follow the above steps
from Number 2 onwards. (Confirm if it works for you)
Credit to : Chainfire and MrW0lf
SuperSU updated yesterday like normal, required updating binaries and I used TRWP. I updated the app with my Titanium Backup. Another app updated today but when I tried to back it up Titanium had lost root. Opened SuperSU and got SU Binaries occupied. Later today, I powered up again, SuperSU and Titanium both had new updates. I thought the problem was reported and fixed but it still does the same thing! :crying: Anybody??
EDIT: A known issue, https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
I am also having the same problem...
Now what to do...?
ashesall said:
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
Click to expand...
Click to collapse
I have staright talk stylo 2 lgl82vl 5.1.1 lollipop think thats issue? I cant really find info on my stylo 2 version.. Rooted phone with kingroot 4.6 and reboots itself and losses root within minutes of completing root. Any help for this rookie tech. Guy...thanks
ashesall said:
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
Click to expand...
Click to collapse
No... It doesnt work... Failed to update binaries... And asks to update the app...
yashasvi.malik said:
No... It doesnt work... Failed to update binaries... And asks to update the app...
Click to expand...
Click to collapse
The last SuperSU version I had before updating to 2.82 was 2.79. I was lucky I turned off automatic updates because the next SuperSU versions after 2.79 were buggy based on reviews. I updated to 2.82 because I thought bugs were already ironed out. It was a bad decision because I started having "SU Binaries occupied" error popping up. I solved this by reinstalling the 2.79 apk I had as backup.
Maybe you updated from a different SuperSU version that's why it didn't work. Make sure that you reinstalled the SuperSU apk version you were using before you upgraded to 2.82.
I've been reading the reviews and the most common reply by support is to flash the SuperSU binaries that corresponds to version 2.82. You can try that. Visit the XDA thread of SuperSU for the flashable zip.
If all things fail with SuperSU, you can try phh's Superuser as an alternative.
---------- Post added at 05:55 PM ---------- Previous post was at 05:32 PM ----------
JGene1983 said:
I have staright talk stylo 2 lgl82vl 5.1.1 lollipop think thats issue? I cant really find info on my stylo 2 version.. Rooted phone with kingroot 4.6 and reboots itself and losses root within minutes of completing root. Any help for this rookie tech. Guy...thanks
Click to expand...
Click to collapse
Sorry, I'm not an expert with these kinds of things. However, you can try visiting the XDA thread of SuperSU and ask for help there.
And also, I'll stay away from Kingroot if I were you. Search for "Kingroot malware/adware" on XDA for more information.
You can try 'phh's Superuser' as an alternative. You can also ask help there.
Install SuperSU 2.65 and update binary, then reboot, and update from Play Store, then update binary again (using "normal" option).
evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
lucasgabmoreno said:
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
Click to expand...
Click to collapse
this solved for me, thanks a lot!
For me root works, but SuperSU SU Binaries are still "occupied" Device: Huawei y540
for me it helped to:
* install version 2.79
* run it and follow instructions
* update to 2.82
* reboot
* 2.82 works!
delete this please
super su binaries occupied
wptski said:
SuperSU updated yesterday like normal, required updating binaries and I used TRWP. I updated the app with my Titanium Backup. Another app updated today but when I tried to back it up Titanium had lost root. Opened SuperSU and got SU Binaries occupied. Later today, I powered up again, SuperSU and Titanium both had new updates. I thought the problem was reported and fixed but it still does the same thing! :crying: Anybody??
EDIT: A known issue, https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
Click to expand...
Click to collapse
this worked for me. https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1. I installed the update zip from the sd card
lucasgabmoreno said:
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
Click to expand...
Click to collapse
do we need to unroot the device for this first?????
akshayrrrb said:
do we need to unroot the device for this first?????
Click to expand...
Click to collapse
No.
You need to root your mobile first. Kingroot works for me.