FINALLY achieved root, but now Supersu-me just stops at Kingroot removal - Verizon Galaxy S 5 General

Am using pro version. Finally get root, and am now stuck. AGAIN!

Flash stock, factory reset, and try again...

kotuamoalt said:
Am using pro version. Finally get root, and am now stuck. AGAIN!
Click to expand...
Click to collapse
Yeah...... been there, done that. Solution.

Just use super sume 6.7 apk. Always works

1) Kingroot root
2) UPDATE-SuperSU-v2.46.zip
https://download.chainfire.eu/696/supersu/
3) extract
UPDATE-SuperSU-v2.46.zip armv7/su
root explorer ->su replace /system/bin : key point!
4) http://spapa1004.tistory.com/259
Banking_SpapaSU-v2.52b_20151011(by_spapa).zip
5) extract SpapaSU.apk install
6) reboot
7) Superuser.apk su update
8) App. Mananger remove Kingroot

Related

[Help]Superuser v3.0.7(41) Su binary vnull lost root

Please help, I updated my superuser and now I think my phone is unrooted
Phone: Motorola Fire xt (xt531)
Rooted
I have done the following but the problem is still there:
1. Searched for fix and applied the following:
1.1. superuser update fix (market)​1.2. superuser flashable zip files. (flashed it through stock recovery (hold volume up and down and power) (gives an error that the zip file is not signed/corrupted)​2. Update su binary (failed)
3. Tried unrooting then rooting.
4. Checked my root using rootchecker (sorry, this device does not have proper root access)

[Q] SuperSU problem in GT-P3110

I installed my SuperSU via flashing in this way
1st: Via CF Root (only working one in 4.1.1), which Had no Busybox package/ or CWM,
2nd: so I used P3110_CWM_RECOVERY-6.0.1.1_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5 from one of the threads here (idk the name) just for the busybox package,
3rd: but once I booted up, My SuperSU Icon, even in system-> apps->all disappeared, leaving only "eu.chainfire" which had less than 1 mb
Please help, I tried reflashing the CF root, with no avail... Tried deleting Superuser.apk and su binary from System, but it won't delete
I do not know what to do next... TIA.

[CWM]Replace KingUser with SuperSu, Install CWM on KingRoot rooted Device

How-To: Installing CWM on Phone, rooted with KingRoot
If you want to get CWM on a Phone, rooted with KingRoot, for example to get rid of KingUser with SuperSu and it doesn't work for you to only flash CWM with Odin and later SuperSu.zip with CWM, try this:
What you need:
-Your Phone
-PC running Linux with ADB installed
-CWM for your Phone
-Supersu.zip
Downloads: SuperSu.zip • http://download.chainfire.eu/supersu
ATTENTION: WITH FLASHING CWM YOUR WARRANTY IS NOW LOST !I'M NOT RESPONSIBLE FOR BRICKED PHONES! YOU DO THIS ALL ON YOUR OWN RESPONSIBILITY!
Tested System: Galaxy Ace 3, running Android 4.2.2 Stock Rom
Let's go:
1. Backup all your data !
2. Start your Phone and enable USB-Debugging in the Developer-Options
3. Connect your Phone to the PC
4. Download the needed Files
5. Copy the Supersu.zip on your SdCard and Copy CWM in the Binary where you've installed ADB
6. Open an ADB-Shell-Terminal (type: "adb shell")and Tip following Code:
su
Click to expand...
Click to collapse
and Accept the USB-Debugging-Dialogue
7.
lsattr install-recovery.sh
Click to expand...
Click to collapse
8.
cp/install/etc/install-recovery.sh/system/etc/install-recovery.sh.STOCK
Click to expand...
Click to collapse
9.
chattr -ia/system/etc/install-recovery.sh
Click to expand...
Click to collapse
10.
rm /system/etc/install-recovery.sh
Click to expand...
Click to collapse
11. Now Shut-Down your Phone and enter into Download-Mode
12. Now open Odin (or Jodin...) and flash the Recovery-File (Now Warranty is Void)
13. Now Resart your Phone and boot into CWM-Recovery and Flash SuperSu.zip from SD-Card
Don't forget to hit the Thanks-Button !
Sunbucks

Systemless root info

There seems to be a lot of issues regarding the systemless root method. Here is some help/basic info.
Prerequisite:
1. Bootloader must be unlocked
2. Must have TWRP recovery installed
How to systemless root:
1. Download SuperSU v2.61 or SuperSU v2.62-3. Both work, I use the v2.62-3.
2. Flash either in TWRP recovery. Reboot to system. You now have systemless root.
Problems/Fixes:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
2. One of your favorite root apps doesn't see that your rooted? Do THIS.
I update super su from the playstore without issues.
kadopt said:
I update super su from the playstore without issues.
Click to expand...
Click to collapse
Could you explain your process? I tried updating from the 2.61 and had issues.
gokart2 said:
Could you explain your process? I tried updating from the 2.61 and had issues.
Click to expand...
Click to collapse
Well, to get root (systemless) you flash super su 2.62-3 with twrp, then go to playstore and update super su app, open Super su and a pop up will indicate that your binaries need updating, press OK and wait until it's complete, then just reboot your device.
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
gokart2 said:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
Click to expand...
Click to collapse
Where can one find this magical "How to systemless root" list of safe-to-flash systemless SuperSU?
And I assume only the BETA versions are systemless? I have tried flashing the latest STABLE v2.76 and it just stuck on boot.
The SuperSU v2.62-3 that you mentioned does work but just want to find the latest version to flash.
jason2678 said:
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
Click to expand...
Click to collapse
Adding the single line text file to /data worked for me to root stock 1575 18-4 with the latest Supersu 2.76 stable.
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
The systemless file contains the following:
SYSTEMLESS=true
BINDSYSTEMXBIN=false
Click to expand...
Click to collapse
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
Click to expand...
Click to collapse
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
csrow said:
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
Click to expand...
Click to collapse
Yeah I'm hoping this will make it easier for those who are flashing SuperSU and ending up with an un-bootable phone due to the installer defaulting to system root in newer versions.
I've removed the permission script since I had no idea 2.76 now applies it. Thanks for the heads up!
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
Click to expand...
Click to collapse
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Edvin73 said:
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Click to expand...
Click to collapse
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Spasticdroid said:
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Click to expand...
Click to collapse
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Ijspegel said:
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, I have updated the zip to fix this and it will now find and flash it.
Spasticdroid said:
Yes, I have updated the zip to fix this and it will now find and flash it.
Click to expand...
Click to collapse
Thank you for your work on this one, it is very helpfull!?
Sent from my XT1572 using XDA-Developers mobile app
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
Thanks man, your script was the only thing that worked for me, but now wifi isn't working. what can I do?
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
OMG THANK YOU
I had accidentally installed the wrong SU and i thought I would have to wipe my entire device after hours of trying different methods. Yours was the only one that worked and my phone booted back on. Thank you so much.
Taking a risk of sounding stupid, will your SystemLess Root work for Android 7.0 Nougat?
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
phillyguy /northeast said:
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
Click to expand...
Click to collapse
Didn't we fix this in another thread?!?!

Can't install busybox on 32.3.A.0.378, patched stock kernel and phh's superuser.

Hi!
Today I have updated my E6653 from 32.2.A.5.11 (with Chainfire's SuperSU) to the newest version 32.3.A.0.378 (with phh's superuser) using the "Customized NOBA" package, downloaded via XPeriFirm.
Everything seems to work fine and I have root access. I can create new files in "/system/xbin" by using the RootExplorer, but I cannot install busyboy (pro).
Every time I try to install it to "/system/bin" or "/system/xbin" it fails, telling me I have to chose another location. And if I try to install it to "/su/bin" it tells me that systemless root is not installed.
What I did to upgrade my phone:
1) Downloaded 32.3.A.0.378 via XPeriFirm
2) Removed build.xml and created a new bundle
3) Extracted the kernel and patched it by using "rootkernel v5.23"
3a) Disabled: RIC and dm-verity
3b) No superuser, no busybox
4) Flashed the custom bundle (wiped everything, except user data)
5) Flashed patched kernel
6) Installed phh's Superuser app.
Everything worked as expected.
But after I was not able to install BusyBox I rebuild the kernel and this time I installed superuser.zip to it.
3b) phh's superuser with unmodified config.txt => installed permissive
But the BusyBox installer is still not working.
How can I install BusyBox on my system?
Thank you very much!
Ikarisan said:
Hi!
Today I have updated my E6653 from 32.2.A.5.11 (with Chainfire's SuperSU) to the newest version 32.3.A.0.378 (with phh's superuser) using the "Customized NOBA" package, downloaded via XPeriFirm.
Everything seems to work fine and I have root access. I can create new files in "/system/xbin" by using the RootExplorer, but I cannot install busyboy (pro).
Every time I try to install it to "/system/bin" or "/system/xbin" it fails, telling me I have to chose another location. And if I try to install it to "/su/bin" it tells me that systemless root is not installed.
What I did to upgrade my phone:
1) Downloaded 32.3.A.0.378 via XPeriFirm
2) Removed build.xml and created a new bundle
3) Extracted the kernel and patched it by using "rootkernel v5.23"
3a) Disabled: RIC and dm-verity
3b) No superuser, no busybox
4) Flashed the custom bundle (wiped everything, except user data)
5) Flashed patched kernel
6) Installed phh's Superuser app.
Everything worked as expected.
But after I was not able to install BusyBox I rebuild the kernel and this time I installed superuser.zip to it.
3b) phh's superuser with unmodified config.txt => installed permissive
But the BusyBox installer is still not working.
How can I install BusyBox on my system?
Thank you very much!
Click to expand...
Click to collapse
Try with supersu, that way you can tell the source of the problem.
Hi!
A few seconds ago I managed the installation by using the custom installation path "/vendor/bin".
This is the location where the su binary is installed, too.
L33Tgod said:
Try with supersu, that way you can tell the source of the problem.
Click to expand...
Click to collapse
Ikarisan said:
Hi!
A few seconds ago I managed the installation by using the custom installation path "/vendor/bin".
This is the location where the su binary is installed, too.
Click to expand...
Click to collapse
Install via rootkernel..

Categories

Resources