Hi, I rooted my G3 after downgrading to KitKat. I downloaded the Chuppa Rom and installed it successfully. I've flashed a recovery successfully too. I've got a SuperUs app but it doesn't seem to work. When I go into Titanium Backup and ES file explorer and when they ask for superuser permissions and I click 'grant', they say that there was an error or that there's no root permissions given.
How do I proceed?
download supersu from the play store.
Had the same problem.
It was solved by flashing the zip version of supersu.
It's in supersu thread (CWM / TWRP / MobileODIN installable ZIP)
Related
I'm at a loss as to what is wrong. I flashed a prerooted stock version of KitKat and I think root was working. But now for some reason it doesn't work. I flashed the supersu zip (v1.80) via TWRP recovery but after rebooting, the SuperSU app doesn't even show up on my device. When I install manually from thr Play Store it's as if I'm not rooted. I've flashed the zip multiple times and I do not want to factory reset and delete all my data (especially since I really can't backup without root atm). Any ideas?
Edit: sorry about the post title typo. *flashing
I am on stock 4.3 and used the CF-autoroot to root my S3. When my phone rebooted it said unfortunately SuperSU has stopped. So, I googled the problem and someone said to download the latest apk and it should work. I did that and SuperSU did work and I installed titanium backup to make sure. However, after I installed Xposed and rebooted, it said that SuperSU has stopped again and I can't go in the app. Will I have to update it every time by downloading the apk when I reboot? When I go in the playstore it just says open and not uninstall or update.
Edit: Ignore the thread. I got it working after flashing the KNOX remover and flashing the latest SuperSU through TWRP.
Hi,
I have the Samsung Galaxy Tab Pro 10.1 (SM-T520) running on Android 4.4.2. Rooting did go well (had to reboot a few times before knox disabled). I tried root checker and its OK.
I then would install TWRP. I downloaded the latest version for my device (2.8.0.0) and tried to flash the IMG with Flashify.
It said complete and rebooted into Stock recovery! Something did go wrong.. I tried TWRP manager (app from app store) to install TWRP, but it wants BusyBox.
I tried to install Busy box but it said it had a problem with installation and said I could try another directory.
I did, and again the same error. I couldnt find the file busybox in system/bin nor system/xbin.
What might the problem be? Should I continue, or is my device unstable and might I brick it?
Edit: Or would Odin do the trick and flash TWRP properly?
This is common and someone should answer already!!
michael64142 said:
Hi,
I have the Samsung Galaxy Tab Pro 10.1 (SM-T520) running on Android 4.4.2. Rooting did go well (had to reboot a few times before knox disabled). I tried root checker and its OK.
I then would install TWRP. I downloaded the latest version for my device (2.8.0.0) and tried to flash the IMG with Flashify.
It said complete and rebooted into Stock recovery! Something did go wrong.. I tried TWRP manager (app from app store) to install TWRP, but it wants BusyBox.
I tried to install Busy box but it said it had a problem with installation and said I could try another directory.
I did, and again the same error. I couldnt find the file busybox in system/bin nor system/xbin.
What might the problem be? Should I continue, or is my device unstable and might I brick it?
Edit: Or would Odin do the trick and flash TWRP properly?
Click to expand...
Click to collapse
Seriously... Do I tell TWRP Manager Root to install Stericson busybox or not?
[FIXED] Unable to replace Kinguser with SuperSU, updating binaries & keeping Root
I'm on KitKat 4.4.2 B510 firmware. After days of struggling to replace Kinguser with SuperSU, updating of binaries failed & keeping Root, I finally solved the issue. Now SuperSU is working perfectly. I tried everything possible, thinking there was an issue with my configuration or compatibility conflicts between SuperSU, Kinguser & Huawei P6 firmware. The problem was with SuperSU. There is an incompatibilty issue with SuperSU 2.46 & earlier versions updating binaries on some P6 phones running KitKat & having rooted their phones with Chinese rooting tools which were installing Kinguser instead of SuperUser as the app of choice. If you wanted to replace the app with SuperSU/SuperUser, you would've encountered many issues. Like
updating binaries, root permissions not given to SuperSU & incorrect root setup.
The SOLUTION is simple.
I found the latest version of SuperSU[2.48] in the test section of the SuperSU thread. SuperSU 2.46 is the latest stable official release & therefore found on Google Play, but since 2.48 is still in beta & being tested, it isnt available on Play or as an apk. You can get SuperSU 2.48 beta here:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It is a zip file & should be installed via a recovery. It is not available as an apk as it is still in testing & still an unofficial release.
I used TWRP to install it.
Boot into recovery, select install or update, find the file you just downloaded from the link & install the zip. Reboot. When your phone is finished booting up, automatically, Kinguser will be replaced with SuperSU 2.48 beta & the binaries will automatically be updated. Kinguser will be deleted, full root permissions will be restored to SuperSU, & no more issues with updating binaries. Solved.
Here is the link for SuperSU 2.48 beta again:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Kingo User was driving me nuts!
adnaanhitman said:
I'm on KitKat 4.4.2 B510 firmware. After days of struggling to replace Kinguser with SuperSU, updating of binaries failed & keeping Root, I finally solved the issue. Now SuperSU is working perfectly. I tried everything possible, thinking there was an issue with my configuration or compatibility conflicts between SuperSU, Kinguser & Huawei P6 firmware. The problem was with SuperSU. There is an incompatibilty issue with SuperSU 2.46 & earlier versions updating binaries on some P6 phones running KitKat & having rooted their phones with Chinese rooting tools which were installing Kinguser instead of SuperUser as the app of choice. If you wanted to replace the app with SuperSU/SuperUser, you would've encountered many issues. Like
updating binaries, root permissions not given to SuperSU & incorrect root setup.
The SOLUTION is simple.
I found the latest version of SuperSU[2.48] in the test section of the SuperSU thread. SuperSU 2.46 is the latest stable official release & therefore found on Google Play, but since 2.48 is still in beta & being tested, it isnt available on Play or as an apk. You can get SuperSU 2.48 beta here:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It is a zip file & should be installed via a recovery. It is not available as an apk as it is still in testing & still an unofficial release.
I used TWRP to install it.
Boot into recovery, select install or update, find the file you just downloaded from the link & install the zip. Reboot. When your phone is finished booting up, automatically, Kinguser will be replaced with SuperSU 2.48 beta & the binaries will automatically be updated. Kinguser will be deleted, full root permissions will be restored to SuperSU, & no more issues with updating binaries. Solved.
Here is the link for SuperSU 2.48 beta again:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Thanks bro. This Kingo User crap was driving me nuts. I just don't trust the Chinese programmers. Kingo seems to have installed a lot more than su binaries. It was constantly going to the internet and uploading/downloading God alone knows what kind of stuff!
KingUser irritated me for a long long time & I struggled to find a solution. The biggest issue was tht my start ups wouldn't stick after restarting my phone. It definitely installed more than just the appropriate binaries. It made it almost impossible to install any other SuperUser app therefore eliminating the competition. Avast also kept reporting it as a threat. Now tht SuperSU is back on my phone, I've had no problems. My smartphone is running smoother & better than ever.
Glad I could be of help bro.
Any solution to devices without recovery? I own a Xperia C3 and there isn´t a recovery for my phone and I wanna try this method
I think all devices have recoveries. They are used by the phone manufacturer or repair service ppl to service & repair our phones. I take it u mean u don't have a custom recovery, but a stock recovery. I haven't tried installing the file via stock recovery as I have TWRP(custom) installed. Last time I checked, it was possible to install or flash zip files via stock recovery. You may have to rename the file to update. zip, then use the install update option to install your zip file. Also Google what button- combination u have to use in order to enter the stock recovery for ur type of phone.
I am running Android 7.0.0 on my P2 rooted with phh Superuser.
However, I want to switch to SuperSU, which as per my understanding (which is very limited in this matter) will happen after I properly uninstall Superuser.
I have researched quite a bit and found out that phh Superuser does not have an inbuilt unroot option unlike SuperSU.
I also flashed the SuperSU .zip file hoping it would delete the current Superuser, but in vain.
I tried to delete su and busybox from /bin and /xbin using Root Explorer but could not find those files in that location.
So I am really helpless now so as what to do in order to have SuperSU installed on my phone.
Try this:
UnSU Script
Flash in Custom Recovery
Videophile said:
Try this:
UnSU Script
Flash in Custom Recovery
Click to expand...
Click to collapse
Thanks for replying.
I flashed the .zip you suggested. It deletes the phh Superuser app but does not unroot.
I can tell this because when I flash the SuperSU .zip and install the app, upon launching it says su binary occupied.
And when I reinstall phh Superuser, it works as it did before.
So I'm afraid, it has not solved my problem.
aeonwiz said:
Thanks for replying.
I flashed the .zip you suggested. It deletes the phh Superuser app but does not unroot.
I can tell this because when I flash the SuperSU .zip and install the app, upon launching it says su binary occupied.
And when I reinstall phh Superuser, it works as it did before.
So I'm afraid, it has not solved my problem.
Click to expand...
Click to collapse
Correct, this will only help with removing Root successfully.
You'll then need to root via SuperSu or Magisk or phhSuperuser.
I've made a post about Magisk rooting here that you can follow, this will use Magisk Manager as your Superuser manager.
In that post I mention flashing your original boot.img which will remove any instances of SU you have previously installed if the zip I provided in my previous post does not work for you.
Thanks, I will try that.