[FIXED] Unable to replace Kinguser with SuperSU, updating binaries & keeping Root - Huawei Ascend P6, Mate

[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.

Related

[Q] SuperSU keeps stopping

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.

[Q] Not rooting, but got Lollipop!

Very strange, all looks good, but still not rooted!
Phone: Samsung Galaxy Mini S4 - GT-I9195
Has recovery image, has:
recovery-clockwork-6.0.5.1-serranoltexx
cm-12-20141127-UNOFFICIAL-serranoltexx
S4Mini_RootKit_v2
Used:
Odin_v3.09
Tried reinstalled S4Mini_RootKit_v2 several times looks fine, but root checker etc say not rooted ;(
Try downloading superSU from play store if you don't have it in app drawer and try again. If it doesn't work change the recovery. I prefer Philz touch over all
No joy with Phiz. Now trying to install SuperSU beta (BETA-SuperSU-v2.42).
Version from Play store does not go in as says can't find files and if upgraded to lollipop need to do it manually.
May later down grade and then upgrade if works in older verion.
Will also try newer version of Lollipop if can get files, currently site timing out.
Rootkit v2 is only for stock ROM its not meant to be used with cm12, download latest supersu zip and flash in recovery
Re-rooted, installed CW 12 and updated SuperSU with latest beta binary and works!
Binary was: BETA-SuperSU-v2.42
Later updated to latest CW 12 (cm-12-20141228-UNOFFICIAL-serranoltexx) and still working.

SuperSU 2.76 fails to install after update to H15

I've updated with the OTA from H14 to H15. I restored the stock recovery beforehand and the update went without Problems.
Before starting the update I tried to "unroot" which also was stated neccessary by SuperSU in two dialogs. But this failed and might be the origin of the problem.
Afterwards SuperSU could not find the su binary so I tried to flash it via TWRP 3.0.2.0 which failed after the line "creating ramdisk backup".
Next I tried to dirty flash the H15 Rom, which also went without problems, but the SuperSU install failed at the same point.
I've attached the logfile of the aroma installer, containing the superSU logfile.
The phone works for the moment, without root / superSU but I would like to have it back
Does anyone have an idea / need more informations / can otherwise help ?
Henry

Pixel XL will not root

Pixel XL running 8.0.0 OPR3.170623.007, developer options and USB Debugging are both on.
I was rooted for a while now, then I tried using one of my root-only apps and it told me it can't get root access.
I looked for SuperSU, which was missing.
I unrooted and rerooted using Skipsoft Unified Android Toolkit.
It flashed SuperSU 2.82 and flashed TWRP 3.1.1.1. The TWRP flashed just fine, but no matter how many times I flash SuperSU, it doesn't show up in my app drawer and the phone is still not rooted. I tried SuperSU 2.82 and the SR5 stable beta, neither worked. I also tried installing it through the Play Store after flashing it, it goes through the install process then just give me the option to install again, never fixes my issue.
Any idea on what I can do next?
edit: I updated to 3.2.0.0 and was able to root. Flashing the most recent beta and non-beta Magisk versions did not work, neither did installing the SuperSU APK. Once I updated to 3.2.0.0 I was able to root with Magisk just fine.
Flash the stock boot.img to both slots and reroot. Use SR5.
I would also advise to start by flashing the stock boot image. I would then boot twrp, flash twrp, then flash latest su.
If that doesn't work I would try going with the latest magisk zip (14.5)
I should have mentioned this, Unified Tool Kit flashed the factory boot image before releasing the latest TWRP and then flashing the most recent SuperSU. I did try flashing SR5 with negative results.
I'll give Magisk a try.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I followed 1,2,3,4,8, zero issues on 8.1.
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
DeviceManagent said:
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
Click to expand...
Click to collapse
Common issue. You can grab the app apk from inside the zip and install it.
I tried flashing both beta and non-beta Magisk versions and installing the SuperSU APK, nothing worked.
I saw that a new TWRP got released, 3.2.0.0. I flashed that and was able to successfully root. Thanks for your help, guys.

Fixing SuperSU

There's a known issue with SuperSU where if you are in superuser mode, you cannot browse the /sdcard path. There's a fix called bueller-fixsusdcard.zip you can apply in TWRP, but the problem seems to come back. Also, there are notifications about updating su that cannot be completed since you cannot seem to actually run the SuperSU app.
You can fix the first problem by flashing the latest SuperSU instead of bueller-fixsusdcard.zip. I used SR5-SuperSU-v2.82-SR5-20171001224502.zip. I have a rooted fully unlocked Fire TV 1 so I extracted the unlocked bootloader and flashed that in TWRP first. I don't know if I needed to actually do that, but I figured that it might be wise to start with a clean boot before flashing the new SuperSU.
The ability to be root and browse /sdcard has been good for a few days now. The other issue of not being able to run the SuperSU app still exists. BTW, I tired to install Magisk 14.0 a while back, but it leaves the FireTV in an unbootable state. I have to flash the boot_unlocked.img file in TWRP and then SuperSU to fix it. I wish someone would troubleshoot why it doesn't work. At least Magisk root can be hidden easier.

Categories

Resources