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.
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
This started to happen last month..
I tried to flash LikeWise Rom and it was a success and when i tried to update SuperSU in the app it asks me to reboot,i rebooted it and SuperSU is gone and everything is messed up,i tried to install SuperSU in Recovery and it was a success but still no SuperSu, so i went back to my backed up rom(CM11) and it was completely working and it asks me to Update SuperSU in the app it asks me to reboot and it was gone again and i have to flash it again it was a success this time when i was at CM11..
What is actually going on...?
Anyone knows why does this happen..?
Superuser or Supersu is sometimes included in the ROM. Not all custom ROMs are pre-rooted. I know some Nexus 4 ROMs are not pre-rooted. It makes sense that supersu or superuser would be removed and replaced with the superuser/supersu version included with the new ROM.
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.
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.