• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Script] Replace KingoRoot with SuperSU

I been loosing root a few times and always get it back w/kingroot (its a pain in the butt ) and every time i switch superuser with bakageta script v1.2 and follow the instructions.
------------------
!! INSTRUCTIONS !!
------------------

!! LINES BEGINNING WITH # SHOULD BE TYPED INTO YOUR SHELL, WITHOUT THE # !!

Fire up your terminal app / adb shell, and gain root access from kingoroot:

# su

Navigate to the folder you extracted this zip into, ie /sdcard/Kingo.to.SuperSU.v1.2

# cd /sdcard/Kingo.to.SuperSU.v1.2

Launch the step0 script, which should copy a SuperSU daemon into /system and
run it in the background.

# ./step0.sh

LEAVE THIS WINDOW OPEN. You need to uninstall kingoroot now, and if you close
your shell, you won't be able to run the next step. Again, you need a shell
with root access to run the next step, and if you close this shell, you won't
be able to get root again without re-rooting your device. LEAVE THIS WINDOW
OPEN! Open the KingUser app, and click the settings icon. Make sure Root
Permission, Smart Authorization, and Backup Root Permission are set to off,
then click Remove Root Permission. The app will uninstall itself. Uninstall the
two other kingo apps.

Go back to your shell, and run the step1 script, which will remove any traces
of kingoroot which cause SuperSU to have problems.

# ./step1.sh

Go to the Play store and install SuperSU. Once installed, run it. If it detects
your su and wants to update, great! Let it update the "normal" method. If it
succeeds, you can now reboot and you're done.
 
chanoc said:
I been loosing root a few times and always get it back w/kingroot (its a pain in the butt ) and every time i switch superuser with bakageta script v1.2 and follow the instructions.
------------------
!! INSTRUCTIONS !!
------------------

!! LINES BEGINNING WITH # SHOULD BE TYPED INTO YOUR SHELL, WITHOUT THE # !!

Fire up your terminal app / adb shell, and gain root access from kingoroot:

# su

Navigate to the folder you extracted this zip into, ie /sdcard/Kingo.to.SuperSU.v1.2

# cd /sdcard/Kingo.to.SuperSU.v1.2

Launch the step0 script, which should copy a SuperSU daemon into /system and
run it in the background.

# ./step0.sh

LEAVE THIS WINDOW OPEN. You need to uninstall kingoroot now, and if you close
your shell, you won't be able to run the next step. Again, you need a shell
with root access to run the next step, and if you close this shell, you won't
be able to get root again without re-rooting your device. LEAVE THIS WINDOW
OPEN! Open the KingUser app, and click the settings icon. Make sure Root
Permission, Smart Authorization, and Backup Root Permission are set to off,
then click Remove Root Permission. The app will uninstall itself. Uninstall the
two other kingo apps.

Go back to your shell, and run the step1 script, which will remove any traces
of kingoroot which cause SuperSU to have problems.

# ./step1.sh

Go to the Play store and install SuperSU. Once installed, run it. If it detects
your su and wants to update, great! Let it update the "normal" method. If it
succeeds, you can now reboot and you're done.
Click to expand...
Is there anything special u did because it always says can't find daemonsu. And I try and mount my file system as R/W but it won't.
 
ITZMERY4N said:
Is there anything special u did because it always says can't find daemonsu. And I try and mount my file system as R/W but it won't.
Click to expand...
Never mind I got it to work I install adb control and started it because it wasn't running then opened terminal and the commands worked.
 
good for you case closed . Now can you guys help me my phone keeps rebooting in to recovery.LOL that's another thread. good luck guys just don't mess to much with your phones or you going to end up like me bricked .
 
Hey,
I've tried running this script many times, and I always get the same error. Well, there's usually a ton of errors, but what it keeps coming down to is that it's trying to copy daemonsu (IIRC) and there's no such file.

I'm on my pc right now, so I can't post a screenshot or a terminal dump, but I'm hoping someone can tell me what I'm doing wrong?
 
Hi! I hope someone can help me, please!. I do not know what I was doing (I am newby in Android).
I rooted my phone (Huawei Y536A1) with Kingo Root, and was OK. I came to this post to try to change the King User with SuperSU, so I applied step0, step1 and installed SuperSU. Everything was as expected, up to when I rebooted the phone.
With Root Chekcer, it says that I have root access but no app, that require rooting, is working (and no app appears in SuperSU App). I made a factory reset, but that has not changed anything.
Tried applying Kingo Root again, and fails. Also after the reset, Root Checker keep saying that I have Root Permisions.
Can someone help me with undoing step0 and step1??? Or with solving this issue?? Thank you very much!
 
sorry but if the script didn't work for you the first time, it's not going to work the second time that's because you already lose root. You should be able to re-root with kingroot, but it's best to get it right the first time. (www.kingroot.net)
P.S. the script was made to switch superusers for Alcatel one touche fierce 2 (7040N-7040t) I don't really know if works for others brands. but if you rooted your phone with kingroot you can give it a try the worst thing can happen is loose root. good luck.
 
no_root said:
Hey,
I've tried running this script many times, and I always get the same error. Well, there's usually a ton of errors, but what it keeps coming down to is that it's trying to copy daemonsu (IIRC) and there's no such file.

I'm on my pc right now, so I can't post a screenshot or a terminal dump, but I'm hoping someone can tell me what I'm doing wrong?
Click to expand...
It could be a number of things, post back when you've got some time and I'll happily try to help.

Pablo S said:
Hi! I hope someone can help me, please!. I do not know what I was doing (I am newby in Android).
I rooted my phone (Huawei Y536A1) with Kingo Root, and was OK. I came to this post to try to change the King User with SuperSU, so I applied step0, step1 and installed SuperSU. Everything was as expected, up to when I rebooted the phone.
With Root Chekcer, it says that I have root access but no app, that require rooting, is working (and no app appears in SuperSU App). I made a factory reset, but that has not changed anything.
Tried applying Kingo Root again, and fails. Also after the reset, Root Checker keep saying that I have Root Permisions.
Can someone help me with undoing step0 and step1??? Or with solving this issue?? Thank you very much!
Click to expand...
You're going to probably need more help than anything these scripts can offer. I think I may have a friend with that model, let me look into it. The easiest fix probably doesn't exist, but if you can get a complete stock signed zip (or whatever recovery tool huawei prefers, like Odin for Samsung), then you can restore the phone to stock and start over. A simple factory reset won't undo changes you've made in /system, which is why backups are important. If you can get a root shell, either through ADB or a terminal emulator, then you can manually finish installing SuperSU so that it'll work properly. If you can't get a root shell, you're going to have a bad time.

chanoc said:
sorry but if the script didn't work for you the first time, it's not going to work the second time that's because you already lose root. You should be able to re-root with kingroot, but it's best to get it right the first time. (www.kingroot.net)
P.S. the script was made to switch superusers for Alcatel one touche fierce 2 (7040N-7040t) I don't really know if works for others brands. but if you rooted your phone with kingroot you can give it a try the worst thing can happen is loose root. good luck.
Click to expand...

As long as you don't close your shell, you don't actually lose root, even with some awful mistakes, and you can fix things without needing to start over with kingroot. However, it's generally a bit more on the advanced side, and starting over will be easiest for most people. I really can't figure out what's causing problems for a few people now, I've unrooted mine several times to play with it and nothing stands out. Maybe one of the models doesn't allow execution from sd, and I need to make a handy installer to toss it in /data/local with the right perms? I wish I had one of the problem phones in front of me, it'd be much faster.

The script's principle is the same for changing from any stubborn root management, by leaving a supersu daemon running and killing everything that tries to interfere, supersu can do it's thing. I picked up one of the Net10 $9 ZTE Midnights at Dollar General yeesterday for a small project, quickly rooted it with kingoroot.net (hey, it turns out they ARE different... whoops), and shifted it over to SuperSU the same way. I'm not sure it's going to work for my project, I knew it was short on internal space but google play is going to have to go entirely it seems. Oh well, it was $9.
 
Alright holmes, im stumped lol ive already done this on my other fierce 2, for some reason after I got root I tryed to run step0 and this is what I keep getting:

u0_a120@Yaris5TMO:/ $ su
root@Yaris5TMO:/ # cd sdcard/download/kingo.to.supersu.v1.3aroot@Yaris5TMO:/sdcard/download/kingo.to.supersu.v1.3a # ./step0.sh
k_shell/10120:5390: ./step0.sh: can't execute: Permission denied
126|root@Yaris5TMO:/sdcard/download/kingo.to.supersu.v1.3a #

Any input is appreciated sir lol
 
Download Super-Sume.apk from playstore. Follow directions & u should be Str8 replacing KR with SuperSu
 
BluntBlowin994 said:
A/kingo.to.supersu.v1.3a # ./step0.sh
k_shell/10120:5390: ./step0.sh: can't execute: Permission denied
Click to expand...

Fairly easy fix, your phone doesn't want to run scripts from the SD card. You need to move everything over to /data/local/tmp and run from there. I'm off to bed tonight so I can't give better instructions, but I'll be happy to help tomorrow.
 
i just tryed your method and this is what i got back:

feedback.png



if it helps at all, i dont have an sd inserted and i dont believe that my sd card reader works due to physical defects. i will try to re solder the connections but as far as i know im trying to run all the scripts off internal memory
 
I forgot to mention you'll need to set everything with execute permissions. I'm not sure what the built-in chmod supports, but try one off these two:
Code: 
chmod +x *
cjhmod 755 *
 
Last edited:
bakageta said:
I forgot to mention you'll need to set everything with write permissions. I'm not sure what the built-in chmod supports, but try one off these two:
Code: 
chmod +x *
cjhmod 755 *
Click to expand...

this is what i got back:

Code: 
C:\Users\Cheryl>adb connect 192.168.0.14
connected to 192.168.0.14:5555

C:\Users\Cheryl>adb shell
root@Yaris5TMO:/ $ su
su
root@Yaris5TMO:/ # mount -w -o remount /system
mount -w -o remount /system
root@Yaris5TMO:/ # chmod +x *
chmod +x *
Bad mode
10|root@Yaris5TMO:/ # chmod 755 *
chmod 755 *
Unable to chmod boot.ver: Read-only file system
10|root@Yaris5TMO:/ #

EDIT: Do you think the dd command will get the files into system so i can run them?
 

Attachments

  • upload_2015-6-23_23-22-31.png
    upload_2015-6-23_23-22-31.png
    128.5 KB · Views: 534
Last edited:
You've just pushed everything over to /data/local/tmp, but were still operating in /, which is read-only. After you move the files to /data/local/tmp, tho this:

Code: 
su
cd /data/local/tmp
chmod 755 *
./step0.sh

That should run step0, which will mount /suystem as r/w. Leave this shell open, and continue to run further commands from /data/local/tmp.

Out of curiousity, what carrier / model / build do you have? It seems most of the other build have no problems running files from the sd card;
 
i know its a lot of code but this is what i got:

Code: 
C:\Users\Cheryl>adb shell
shell@Yaris5TMO:/ $ su
su
root@Yaris5TMO:/ # mount -o -w remount /data
mount -o -w remount /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|root@Yaris5TMO:/ # mount -w -o remount /data
mount -w -o remount /data
root@Yaris5TMO:/ # cd /data/local/tmp
cd /data/local/tmp
root@Yaris5TMO:/data/local/tmp # chmod 755 *
chmod 755 *
root@Yaris5TMO:/data/local/tmp # ./step0.sh
./step0.sh
Mounting /system r/w...
Copy SuperSU daemon...
Start SuperSU daemon...
........................................................................
If this finished without errors, uninstall KingRoot and install SuperSU.
root@Yaris5TMO:/data/local/tmp # ./step1.sh
./step1.sh
Restoring SuperSU binary...
cp: /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
./chattr.pie: Read-only file system while setting flags on /system/xbin/ku.sud
./chattr.pie: Read-only file system while setting flags on /system/xbin/supolicy

rm failed for /system/xbin/ku.sud, Read-only file system
rm failed for /system/xbin/supolicy, Read-only file system
rm failed for /system/bin/rt.sh, Read-only file system
rm failed for /system/bin/install-recovery.sh, Read-only file system
rm failed for /system/bin/shipclean, No such file or directory
rm failed for /system/bin/start-ssh, Read-only file system
./chattr.pie: Read-only file system while setting flags on /system/etc/install-r
ecovery.sh
./chattr.pie: Read-only file system while setting flags on /system/etc/install-r
ecovery.sh-ku.bak
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/etc/install-recovery.sh-ku.bak, Read-only file system
rm failed for /system/etc/install_recovery.sh, Read-only file system
rm failed for /system/usr/icu/icusuflag.conf, Read-only file system
./chattr.pie: No such file or directory while trying to stat /system/usr/iku/isu

rm failed for /system/kroot_*, No such file or directory
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.
root@Yaris5TMO:/data/local/tmp # mount -w -o remount /system
mount -w -o remount /system
root@Yaris5TMO:/data/local/tmp # ./step1.sh
./step1.sh
Restoring SuperSU binary...
cp: /system/xbin/su: Permission denied
Unable to chmod /system/xbin/su: Operation not permitted
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
rm failed for /system/bin/shipclean, No such file or directory
./chattr.pie: No such file or directory while trying to stat /system/usr/iku/isu

rm failed for /system/kroot_*, No such file or directory
rm failed for /sdcard/kr-stock-conf, No such file or directory
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.
root@Yaris5TMO:/data/local/tmp # ./step0.sh
./step0.sh
Mounting /system r/w...
Copy SuperSU daemon...
cp: /system/xbin/daemonsu: Text file busy
Start SuperSU daemon...
........................................................................
If this finished without errors, uninstall KingRoot and install SuperSU.
root@Yaris5TMO:/data/local/tmp # ./manualsucopy.sh
./manualsucopy.sh
Attempting to manually install SuperSU, this will only work on KitKat.
cp: /system/xbin/su: Operation not permitted
mkdir failed for /system/bin/.ext, File exists
Unable to chmod /system/xbin/su: Operation not permitted
cp: /system/etc/install-recovery.sh: Operation not permitted
Unable to chmod /system/etc/install-recovery.sh: Operation not permitted
link failed File exists
root@Yaris5TMO:/data/local/tmp #

and i have metro but i switched the network over to att to try to get service so i could activate it but its not picking up any bars.
 
Last edited:
And there's that damned magical mount that doesn't like to work. Do you happen to have busybox installed? If so, type this:
Code: 
busybox mount -o rw,remount /system

That should properly mount system, and you can start from step0 again. Everything else looks fairly good, once system is writeable you should be all set.

If you don't have busyboxy, grab this file, push it over to /data/local/tmp, chmo 755 busybxo, and then type this in, from /data/local/tmp

Code: 
./busybox mount -o rw,remount /system

If one of those won't get system writeable, we've really screwed up.
 
bakageta said:
And there's that damned magical mount that doesn't like to work. Do you happen to have busybox installed? If so, type this:
Code: 
busybox mount -o rw,remount /system

That should properly mount system, and you can start from step0 again. Everything else looks fairly good, once system is writeable you should be all set.

If you don't have busyboxy, grab this file, push it over to /data/local/tmp, chmo 755 busybxo, and then type this in, from /data/local/tmp

Code: 
./busybox mount -o rw,remount /system

If one of those won't get system writeable, we've really screwed up.
Click to expand...
this is what i got back:

Code: 
C:\Users\Cheryl>adb connect 192.168.0.14
connected to 192.168.0.14:5555

C:\Users\Cheryl>adb shell
root@Yaris5TMO:/ $ cd ha
cd ha
/system/bin/sh: cd: /ha: No such file or directory
2|root@Yaris5TMO:/ $ su
su
root@Yaris5TMO:/ # cd ha
cd ha
k_shell/2000:26409: cd: /ha: No such file or directory
2|root@Yaris5TMO:/ # cd /data/local/tmp
cd /data/local/tmp
root@Yaris5TMO:/data/local/tmp # mount -w -o remount /data
mount -w -o remount /data
root@Yaris5TMO:/data/local/tmp # cd /Kingo.to.SuperSU.v1.3a
cd /Kingo.to.SuperSU.v1.3a
k_shell/2000:26409: cd: /Kingo.to.SuperSU.v1.3a: No such file or directory
2|root@Yaris5TMO:/data/local/tmp # ls
ls
README.TXT
chattr.pie
glsl_shader_log.txt
install-recovery.sh
libsupol.so
manualsucopy.sh
step0.sh
step1.sh
su
supolicy
root@Yaris5TMO:/data/local/tmp # busybox mount -o rw,remount /system
busybox mount -o rw,remount /system
root@Yaris5TMO:/data/local/tmp # ./step0.sh
./step0.sh
k_shell/2000:26409: ./step0.sh: can't execute: Permission denied
126|root@Yaris5TMO:/data/local/tmp # chmod 755 *
chmod 755 *
root@Yaris5TMO:/data/local/tmp # ./step0.sh
./step0.sh
Mounting /system r/w...
Copy SuperSU daemon...
Start SuperSU daemon...
........................................................................
If this finished without errors, uninstall KingRoot and install SuperSU.
root@Yaris5TMO:/data/local/tmp # ./step1.sh
./step1.sh
Restoring SuperSU binary...
cp: /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
./chattr.pie: Read-only file system while setting flags on /system/xbin/ku.sud
./chattr.pie: Read-only file system while setting flags on /system/xbin/supolicy

rm failed for /system/xbin/ku.sud, Read-only file system
rm failed for /system/xbin/supolicy, Read-only file system
rm failed for /system/bin/rt.sh, Read-only file system
rm failed for /system/bin/install-recovery.sh, Read-only file system
rm failed for /system/bin/shipclean, No such file or directory
rm failed for /system/bin/start-ssh, No such file or directory
./chattr.pie: Read-only file system while setting flags on /system/etc/install-r
ecovery.sh
./chattr.pie: No such file or directory while trying to stat /system/etc/install
-recovery.sh-ku.bak
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/etc/install-recovery.sh-ku.bak, No such file or directory
rm failed for /system/etc/install_recovery.sh, No such file or directory
rm failed for /system/usr/icu/icusuflag.conf, Read-only file system
./chattr.pie: No such file or directory while trying to stat /system/usr/iku/isu

rm failed for /system/kroot_*, No such file or directory
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.
root@Yaris5TMO:/data/local/tmp # busybox mount -o rw,remount /system
busybox mount -o rw,remount /system
root@Yaris5TMO:/data/local/tmp # ./step1.sh
./step1.sh
Restoring SuperSU binary...
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
rm failed for /system/bin/shipclean, No such file or directory
rm failed for /system/bin/start-ssh, No such file or directory
./chattr.pie: No such file or directory while trying to stat /system/etc/install
-recovery.sh-ku.bak
rm failed for /system/etc/install-recovery.sh-ku.bak, No such file or directory
rm failed for /system/etc/install_recovery.sh, No such file or directory
./chattr.pie: No such file or directory while trying to stat /system/usr/iku/isu

rm failed for /system/kroot_*, No such file or directory
rm failed for /sdcard/kr-stock-conf, No such file or directory
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.
root@Yaris5TMO:/data/local/tmp # cd ..
cd ..
root@Yaris5TMO:/data/local # cd ..
cd ..
root@Yaris5TMO:/data # cd ..
cd ..
root@Yaris5TMO:/ # cd /system
cd /system
root@Yaris5TMO:/system # chmod 755 *
chmod 755 *
Unable to chmod build.prop: Read-only file system
10|root@Yaris5TMO:/system # cd ..
cd ..
root@Yaris5TMO:/ # cd /data/local/tmp
cd /data/local/tmp
root@Yaris5TMO:/data/local/tmp # ./busybox mount -o rw,remount /system
./busybox mount -o rw,remount /system
k_shell/2000:26409: ./busybox: can't execute: Permission denied
126|root@Yaris5TMO:/data/local/tmp # chmod 755 *
chmod 755 *
root@Yaris5TMO:/data/local/tmp # ./busybox mount -o rw,remount /system
./busybox mount -o rw,remount /system
root@Yaris5TMO:/data/local/tmp # ./step1.sh
./step1.sh
Restoring SuperSU binary...
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
./chattr.pie: No such file or directory while trying to stat /system/xbin/supoli
cy
rm failed for /system/xbin/supolicy, No such file or directory
rm failed for /system/bin/rt.sh, No such file or directory
rm failed for /system/bin/install-recovery.sh, No such file or directory
rm failed for /system/bin/shipclean, No such file or directory
rm failed for /system/bin/start-ssh, No such file or directory
./chattr.pie: No such file or directory while trying to stat /system/etc/install
-recovery.sh-ku.bak
rm failed for /system/etc/install-recovery.sh-ku.bak, No such file or directory
rm failed for /system/etc/install_recovery.sh, No such file or directory
./chattr.pie: No such file or directory while trying to stat /system/usr/iku/isu

rm failed for /system/kroot_*, No such file or directory
rm failed for /sdcard/kr-stock-conf, No such file or directory
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.
root@Yaris5TMO:/data/local/tmp #


EDIT: I'm seriously considering removing the root and starting from square one again but as far as kinguser goes i have no idea how to get rid of it besides titanium backup
 
No, really, it's fine. It's that you don't have busybox installed. Take that busybox.zip file I linked and extract it, and put it in /data/local/tmp too. Then do these:
Code: 
cd /data/local/tmp
chmod 755 busybox
./busybox mount -w -o remount /system

The ./busybox in front of the mount is important, it means we want to use busybox's standard mount instead of the horribly crappy one installed in your system.
 
bakageta said:
No, really, it's fine. It's that you don't have busybox installed. Take that busybox.zip file I linked and extract it, and put it in /data/local/tmp too. Then do these:
Code: 
cd /data/local/tmp
chmod 755 busybox
./busybox mount -w -o remount /system

The ./busybox in front of the mount is important, it means we want to use busybox's standard mount instead of the horribly crappy one installed in your system.
Click to expand...


This is what i got back:

Code: 
u0_a120@Yaris5TMO:/ $ su
root@Yaris5TMO:/ # cd /data/local/tmp/Kingo.to.SuperSU.v1.3ak_shell/10120:30598: cd: /data/local/tmp/Kingo.to.SuperSU..v1.3a: No such file or directory
2|root@Yaris5TMO:/ # cd data
root@Yaris5TMO:/data # mount -w -o remount data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|root@Yaris5TMO:/data # mount -w -o remount /data
root@Yaris5TMO:/data # mount -w -o remount /data            root@Yaris5TMO:/data # mount -w -o remount data             root@Yaris5TMO:/data # cd data                              root@Yaris5TMO:/data # cd /data/local/tmp/Kingo.to.SuperSU..
root@Yaris5TMO:/data # cd local
root@Yaris5TMO:/data/local # cd tmp/Kingo..
k_shell/10120:30598: cd: /data/local/tmp/Kingo..: No such file or directory
2|root@Yaris5TMO:/data/local # cd tmp
root@Yaris5TMO:/data/local/tmp # cd Kingo.to.SuperSU.v1.3a
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # ./bu
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # chmod 755 busybox
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # ./buount -w -o                                                  remount /system   <
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # ./step0.sh
Mounting /system r/w...
Copy SuperSU daemon...
Start SuperSU daemon...
........................................................................
If this finished without errors, uninstall KingRoot and install SuperSU.
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # ./step1.sh
Restoring SuperSU binary...
cp: /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
./chattr.pie: Read-only file system while setting flags on /system/xbin/ku.sud
./chattr.pie: Read-only file system while setting flags on /system/xbin/supolicy
rm failed for /system/xbin/ku.sud, Read-only file system
rm failed for /system/xbin/supolicy, Read-only file system
rm failed for /system/bin/rt.sh, Read-only file system
rm failed for /system/bin/install-recovery.sh, Read-only file system
rm failed for /system/bin/shipclean, No such file or directory
rm failed for /system/bin/start-ssh, Read-only file system
./chattr.pie: Read-only file system while setting flags on /system/etc/install-recovery.sh
./chattr.pie: No such file or directory while trying to stat /system/etc/install-recovery.sh-ku.bak
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/etc/install-recovery.sh-ku.bak, No such file or directory
rm failed for /system/etc/install_recovery.sh, No such file or directory
rm failed for /system/usr/icu/icusuflag.conf, Read-only file system
./chattr.pie: No such file or directory while trying to stat /system/usr/iku/isu
rm failed for /system/kroot_*, No such file or directory
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # ./buount -rw,re                                                 mount /system     <
mount: invalid option -- ,
BusyBox v1.23.1-Stericson (2015-02-06 13:50:32 EST) multi-call binary.

Usage: mount [OPTIONS] [-o OPTS] DEVICE NODE

Mount a filesystem. Filesystem autodetection requires /proc.
        -a              Mount all filesystems in fstab
        -f              Dry run
        -i              Don't run mount helper
        -v              Verbose
        -r              Read-only mount
        -w              Read-write mount (default)
        -t FSTYPE[,...] Filesystem type(s)
        -O OPT          Mount only filesystems with option OPT (-a only)
-o OPT:
        loop            Ignored (loop devices are autodetected)
        [a]sync         Writes are [a]synchronous
        [no]atime       Disable/enable updates to inode access times
        [no]diratime    Disable/enable atime updates to directories
        [no]relatime    Disable/enable atime updates relative to modification time
        [no]dev         (Dis)allow use of special device files
        [no]exec        (Dis)allow use of executable files
        [no]suid        (Dis)allow set-user-id-root programs        [r]shared       Convert [recursively] to a shared subtree
        [r]slave        Convert [recursively] to a slave subtree
        [r]private      Convert [recursively] to a private subtree
        [un]bindable    Make mount point [un]able to be bind mounted
        [r]bind         Bind a file or directory [recursively] to another location
        move            Relocate an existing mount point
        remount         Remount a mounted filesystem, changing flags
        ro/rw           Same as -r/-w

There are filesystem-specific -o flags.

1|root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # ./mount -w -                                                  o remount /system <
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # ./step1.sh
Restoring SuperSU binary...
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
Cleaning up KingRoot leftovers that prevent SuperSU from updating...
rm failed for /system/bin/shipclean, No such file or directory
./chattr.pie: No such file or directory while trying to stat /system/etc/install-recovery.sh-ku.bak
rm failed for /system/etc/install-recovery.sh-ku.bak, No such file or directory
rm failed for /system/etc/install_recovery.sh, No such file or directory
./chattr.pie: No such file or directory while trying to stat /system/usr/iku/isu
rm failed for /system/kroot_*, No such file or directory
rm failed for /sdcard/kr-stock-conf, No such file or directory
.............................................................................
1-2 errors are ok, 10+ are not. Run SuperSU and update binary normally if ok.
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a #
 
Code: 
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # chmod 755 busybox
root@Yaris5TMO:/data/local/tmp/Kingo.to.SuperSU.v1.3a # ./buount -w -o
I'm going to assume you've made a script for mounting here, as I'm not familiar with a buount command and it does seem to set your system to r/w for the step0.sh. This is fine.

It seems something is putting system back to r/o before you run the step1.sh. You did make sure you uninstall the kingroot app through the settings in itself, and uninstall the other two apps before trying to run step1.sh, right? If not, it will attempt to stop you with things like this.

Also, I noticed you're doing a few commands to set data as r/w at the beginning:
Code: 
1|root@Yaris5TMO:/data # mount -w -o remount /data
root@Yaris5TMO:/data # mount -w -o remount /data
etc. These should not be needed, data is already r/w, and even normal users have write permission to /data/local/tmp. You can freely adb push files to /data/local/tmp, just make sure that once you push them, you chmod them correctly (chmod 755 * and chown root.root * are good examples).

You're executing scripts now, and you have r/w access to system (or you'd have errors in step0.sh), so now it's just a matter of doing it all in exactly the right order. If you've uninstalled all of KingRoot and it's STILL setting system back to r/o before step1.sh, you may have some protection app installed. You can remount system as r/w just before running step1.sh if you don't feel comfortable removing something like that temporarily, but I suspect the problem is from KingRoot, not another app.

I'm sorry it's taken me so long to get back to you, I know that can be inconvenient when you need to leave a root window open. If you want to try and catch for near real-time help, drop me a google talk (or hangouts or whatever the hell they call it now) message, my username @gmail.com. If I'm around I'll be happy to help and with quick responses this should get solved much faster.
 
This worked great Bakageta, you did great work, the only thing I did different was I typed cd /sdcard/Kingo.to.SuperSU.v1.3a instead of the one in the readme file, naturally because the folder is named differently, but other than that, I followed your instructions and everything works great, I finally have the more preferred and better functioning SuperSU, thanks.
 
Ever look back at something you've done, and wonder what the hell you were thinking at the time? Definitely one of those days. Why on earth wouldn't I just use packagemanager to uninstall/install things automatically? Why would I expect people to manually do it at specific points?

I guess not just making a one-click solution actually left a rooted shell available to fix mistakes, but it's certainly not the most user-friendly way to do it. New script incoming that should just work, or at least fail a bit more elegantly.
 
You must log in or register to reply here.
Back
Top Bottom