Related
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
hi all
So, i rooted my device using KingRoot, i did not unlock the bootloader since i won't be flashing any custom roms or recoveries.
I installed AdAway, the latest stable release, when i try to enable ad blocking with it, i always get this error msg:
Copy failed
Copying of hosts file failed!
Please read Help for more information.
Is there any way to fix this ? and if not, is there any other way to block Ads without the use of AdAway ?
Thanks!
I rooted using SuperSU and AdAway works great . Don't know why isn't it working with you.. Make sure you granted root permission from KingRoot apk
I did, it has root permission
If i have to use SuperSU, that means i need to unlock my BL and flash TWRP correct ?
Some root "programs" are not strong enough.. Like SuperSU x Superuser.. It is possible that your choice is weak i have SuperSU (instaled via TWRP) and adaway works great.
Hello,
i wanna hide root (because of Super Mario Run) and tried to install Magisk, but i get an installation error.
I have no idea if Magisk uses the correct partition, i also tried the boot0/boot1 partition, but no luck.
My P9 lite is running Nougat (VNS-L31C432B370)
Did anyone succeed in installing Magisk on the P9 lite? Or are there any other "hide root" apps i could try?
Thanks!
In my b371 works fine.
I installed magisk from play store and at the first start it asks to install itself in boot partiton.
i can't even install it in recovery, the phone justs reboots during installation.
how did you root? what kernel are you using? i'm using elite-kernel v3 for 370
i assume you're using phh's SuperUser?
well, maybe i give the 371 update a try...
I use elite-kernel. I rooted simply installing phh su from play store. Then I installed magisk from play store and it auto flash itself the zip. It works. Try
Paolo83 said:
I use elite-kernel. I rooted simply installing phh su from play store. Then I installed magisk from play store and it auto flash itself the zip. It works. Try
Click to expand...
Click to collapse
I follow your steps, but it gives me installation error. In which block have you installed mmcblk0p28? What recovery do you use?
Thank you
This recovery https://forum.xda-developers.com/hu...ecovery-twrp-3-0-2-android-nougat-03-t3511937
The partition is autodetected mmcblk0p28
Try to set selinux to permissive
It seems that everything is correct. But it does not hide the root, it does not pass safety net.
Paolo83 said:
Try to set selinux to permissive
Click to expand...
Click to collapse
THIS!
Installation works now, thanks dude!
@gvalro
i get "CTS profile mismatch"
Don't care, Super Mario Run works fine now with root enabled.
edit: naaah, the game crashes at some point, guess there's no perfect solution except unrooting your phone
realCyphox said:
THIS!
Installation works now, thanks dude!
@gvalro
i get "CTS profile mismatch"
Don't care, Super Mario Run works fine now with root enabled.
edit: naaah, the game crashes at some point, guess there's no perfect solution except unrooting your phone
Click to expand...
Click to collapse
try to enable magisk hide in setting
any have boot.img backup with Magisk working? in my case after reboot, Magisk need "reinstall"
simo255 said:
try to enable magisk hide in setting
Click to expand...
Click to collapse
Yes , is enabled
After installing Magisk, fingerprint disappears.
gvalro said:
Yes , is enabled
After installing Magisk, fingerprint disappears.
Click to expand...
Click to collapse
yes it was for me either, when i enable magisk hide, fps disappear :/
BadWolfYe said:
any have boot.img backup with Magisk working? in my case after reboot, Magisk need "reinstall"
Click to expand...
Click to collapse
autoquote for petition.
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.
So, I wanted to use SuperSU as my main root solution(to have the latest magisk, and because it is tested and tried), I attempted rooting with super v2.81 on stock build NPP25.137.72, and to my surprise: it worked!! So now we have SuperSU alongside Magisk as our root solutions
ap4ss3rby said:
So, I wanted to use SuperSU as my main root solution(to have the latest magisk, and because it is tested and tried), I attempted rooting with super v2.81 on stock build NPP25.137.72, and to my surprise: it worked!! So now we have SuperSU alongside Magisk as our root solutions
Click to expand...
Click to collapse
Very cool :good:, could you provide a link and maybe some further informations?
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting sure is recorded by the SuperSU app(and reports granting SU access) we don't have root access
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting SU is recorded by the SuperSU app(and reports granting SU access) we don't have root access
ap4ss3rby said:
Just flash SuperSu v2.82 on top of the aforementioned build, using twrp
however, I would like to note that even though requesting SU is recorded by the SuperSU app(and reports granting SU access) we don't have root access
Click to expand...
Click to collapse
Hello,
I just received my own, and want to be sure:
did Supersu worked yes or no?
can you explain the different steps from a brand new stock g5?
and does fingerprint still works after all?
thank you
daktary said:
Hello,
I just received my own, and want to be sure:
did Supersu worked yes or no?
can you explain the different steps from a brand new stock g5?
and does fingerprint still works after all?
thank you
Click to expand...
Click to collapse
Fingerprint still works, but root access very rarely works, but SuperSu does install, and for installation:
In a nutshell unlock the bootloader, flash twrp, get supersu v2.82 flashable zip on the sdcard, install the latest available app from apkmirror, and you're done