Database Users

{Behold 2 }[How-to] Root for App's working with Persistent root

First off, I want to say thanks to Kam187 & the Creators of asroot
Okay, Below is the Method I used for getting Root working for my app's.
Even though Shell is running as Root, any Call's made to su trigger's the white List Superuser.apk, So don't think your phone is wide open. G1's & MT3G Setup's are the same regard sh.
I'm not sure is the apk is counted as warez or not, if so I hope a Mod will remove the link to the Apk or let me know to Remove it...
Okay, File's Need to complete the Task is....
Try3 Placed in C:\SDK\tools> found here > File's attached below
SU for /system/bin found here > File's attached below
Superuser app control for our App's found Here > File's attached below
Next, Mount the SDCARD and place the SU file in the root of the sdcard like so ( /sdcard ). This is Important!!!
From here we do the Following.. ( Kam187 script the I edited ).
adb push try3 /data/local
adb shell chmod 0755 /data/local/try3
adb shell
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /sdcard/su > /system/bin/su1
cat /sdcard/su > /system/bin/su
chmod 04755 /system/bin/su
su
cat /system/bin/playlogo > /system/bin/playlogo_real
/system/bin/chmod 0755 /system/bin/playlogo_real
echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /system/bin/su1 > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real" > /system/bin/playlogo
Click to expand...
Click to collapse
Once Done, place the Superuser.apk in your SDK tools Directory.
Mine happens to look like this
C:\SDK\tools>
Click to expand...
Click to collapse
Once you have that Copied over, Open a Command prompt and CD to your sdk\tools directory and type the following.
adb install Superuser.apk
Click to expand...
Click to collapse
Once done, do a reboot of the Phone, Once boot up is complete open a Command Prompt ( or app that needs Root ).
For Command Prompt, type:
adb shell
Click to expand...
Click to collapse
su
Click to expand...
Click to collapse
If done correctly you will now see the deny or allow prompt on the Phone, or just open any app that needs root & you will see the same window.
Here's some Picture of it working
SU working with SU apk on Twitpic & SU working with SU apk on Twitpic

installing su complete but nothing! 2.3.3 9023

hello
After unlocking the bootloader then installing the recovery image
then from the recovery image
i install this file from sdcard su-2.3.6.1-ef-signed.zip
everything run smoothly and i get installation completed
but then when i boot to the device, the Rom Manager tells that there is no su into /system/bin
how to install su correctly ?
i'm on ubuntu with Nexus S 9023
thank you

even market enabler app tell "we got a problem Huston" that means no root applied
i've mounted the /system from recovery mode but nothing seem to activate the su
help please

Do you have /system/app/Superuser.apk ? Otherwise I would try to flash the zip again from recovery.

no doing /adb shell ls /system/app/
i can't find the Superuser.apk there
even i tried to flash the zip files 3 times
and removed the superuser then installed it from market
still not su

solved
ok, now i fixed this problem
extract the (su and Superuser.apk) from su-2.3.6.1-ef-signed.zip to /sdcard
Code:
./adb reboot bootloader
then choose recovery mode
then
Code:
./adb shell
Code:
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su
chmod 06755 su

EVO Shift Temp Root for 2.3.3 and HBoot Downgrade

To downgrade your HBOOT to go back to 2.2 visit this link http://forum.xda-developers.com/showthread.php?t=1255474
This will allow you to flash 2.2 to perm root the phone
If you wish to help with perm root status for Android 2.3.3, please visit this thread http://forum.xda-developers.com/showthread.php?t=1218580
Thanks to everyone in this post who has helped get this far. You will need to have the Android SDK installed and working knowledge of ADB and basic file system structure.
Major help from minneyar
TEMP ROOT Instructions:
Download http://tinyw.in/1lI
Unzip if required and put in your ADB folder
Launch command prompt and navigate to your ADB folder
adb push fre3vo /data/local/tmp/
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF (if this doesn't work, try rebooting phone)
Download these 2 files here and put them in your ADB directory: http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
exit back to command prompt if you aren't there already
adb push Superuser3-beta1.apk /data/app/
adb push su-3.0-alpha7 /data/local/tmp
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
You now have temp root. Disregard any notification about outdated SU binary. Root will go away if you reboot. If you reboot your phone you can obtain root again by just running the following
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
I haven't found a way to re-root after rebooting without connecting to a PC

Type su and see if it gives you root permissions
Sent from my MiuiSpeedy

says su: not found.

You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.

Stuke00 said:
See screenshot. Doesn't the # mean temp rooted? Tho I cannot install SU and Root Explorer isn't working. Anything else I need to do first or something?
Click to expand...
Click to collapse
Looks hopeful!

tokuzumi said:
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Click to expand...
Click to collapse
Okay let me clarify
I can install SU but it wouldn't install the binaries. I did all of the above. Says su: not found.
I then tried something else.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /system/bin/sh > /system/bin/su
# chmod 4755 /system/bin/su
I was then able to get the SU binaries to install but Titanium Backup says:
"Busybox works but the "su" command does not elevate to root: "whoami" reports "app_135" instead of root/uid 0.
then su from the command prompt was saying "link_image[1935]: 3160 missing essential tablesCANNOT LINK EXECUTABLE" and now back to su: not found again....

I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.

tokuzumi said:
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
Click to expand...
Click to collapse
Yeah I tweeted him with what I could provide with 160 characters. Just waiting now.

Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App

crump84 said:
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Yeah he posted that right after I gave him the memory address for the exploit. Just means that I did it the manual way through debugging. At least I think so... hopefully soon!

Good news, everybody! I have successfully acquired temp root on my Shift!
First, fre3vo has to be pointed at the right address. After copying it over to my phone, I did "adb shell" and then ran it like so:
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
That printed out a message that it found an exploit and kicked me out of the shell. After doing "adb shell" again, I got a command prompt. I tried installing the 2.3.6.3 version of Superuser, but it complained about being unable to install "su"; I tried to find a separate su binary and copy it over manually, but it didn't work due to a linker error.
After searching around, I found a beta version of Superuser 3:
http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
First I uninstalled the old version of Superuser and then used adb to install the new one from that thread. I ran it and it said it was unable to install su, so I downloaded the version of su provided there and installed it manually. The process went something like:
Code:
adb push su-3.0-alpha7 /data/local/tmp
adb shell
# cd /data/local/tmp
# chmod 4755 su-3.0-alpha7
# ./su-3.0-alpha7
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /system
# cat su-3.0-alpha7 > /system/bin/su
# chmod 4755 /system/bin/su
I don't know if explicitly running "./su-3.0-alpha7" is necessary, it just seemed like a good idea at the time. I don't know if everybody's block device will be named "mmcblk0p26", I used "mount" to figure out what was mounted at /system.
Anyway, after all that was done, I ran Superuser again and it didn't complain. To test it out, I started up Wireless Tether. It asked me for superuser permissions, which I granted it, and it's working fine.
Root successful!

Good job!!
Sent from my Speedy HTC EVO shift on XDA Premium app

I followed those steps exactly and got what I would call a partial root. Some of the 'you need root' errors are gone but "su" still results in 'not found' even though "mkdir su" results in 'file exists.'
mmcblk0p26 exists on this unit.
The weirdest part is that Adfree will accept the device as rooted and with superuser but says it can't find a partition to modify. And after a reboot root is definitely gone.
I think you're on to it but it isn't quite there yet.

It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.

I caught something like that.
I think there should be a chmod 777 su-3.0-alpha7 after cd /data/local/tmp

minneyar said:
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
Click to expand...
Click to collapse
YES! I have root! I was able to install a screenshot app and test it this is amazing progress! Thanks for that.
So now when I reboot, you have to do the entire thing again? SU and all?

Stuke00 said:
So now when I reboot, you have to do the entire thing again? SU and all?
Click to expand...
Click to collapse
Yes, every time you reboot you'll have to redo the whole process, including running fre3vo and then copying su into /system/bin. Hopefully somebody will figure out a permanent root soon.

Wow those SU binaries are disappearing before I even reboot! Already gone and I haven't rebooted the phone

I think I had that issue too. I just couldn't believe the files just disappeared and thought I did something wrong somewhere.

Would a logcat help anyone at all? Anything I should look for?

[TUTORIAL]How to manual root official 2.3

I always have problems to root official 2.3 with automatic ways, and found that this caused from some adb miscommunication.
So this is how to do it manual, in case automatic ways stacked.
First install adb-sdk and add its path to system variables, so to don't have to go to adb' s path before you can run it.
Then download doomlord' s rooting tool and extract it to drive C:\DoomLordRoot.v3.
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Preparation steps on device:
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) uncheck fast boot from settings -> applications
Click to expand...
Click to collapse
Open windows command prompt window and do the above:
Code:
adb push c:\DoomLordRoot.v3\files\zergRush /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
chmod 777 /data/local/tmp/zergRush
./data/local/tmp/zergRush
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\busybox /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox mount -o remount,rw /system
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
rm -r /data/local/tmp/busybox
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit again from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\su /system/bin/su
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit once more from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\Superuser.apk /system/app/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
cd /data/local/tmp/
rm *
reboot
This is basic what the runme.bat file does, just some paths corrected to point to the right locations.

I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?

Oneclickroot v2. 2 did the work for me or something like this
Sent from my U8800

SS said:
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Click to expand...
Click to collapse
This probably means that rooting failed.
What messages you get when you run zergrush?

dancer_69 said:
This probably means that rooting failed.
What messages you get when you run zergrush?
Click to expand...
Click to collapse
I got messages for sending 149, then 189 zerglings, then messages about not being able to mount, find or write to directories.
It seems like it wasn't able to get root access to be able to run its process.
In any case, I just downgraded to the previous release and then used ZergRush, which worked perfectly

don't work.

try this, it works for my B528 rom!
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7

Root Lollipop for Xperia tablet Z & add SuperSU without downgrading to Kitkat + ftf

Root Lollipop for Xperia tablet Z & add SuperSU without downgrading to Kitkat + ftf
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
You don't need to have root to apply this procedure. Your bootloader doesn't have to be unlocked.
This has been tested with SGP311, 10.6.A.0.454, Lollipop 5.0.2, Customized TW version, but it should work fine on any other customization of 10.6.A.0.454.
This procedure installs superSU root binaries and busybox on your system.
Requirements
1- Upgrade to Lollipop 5.0.2. Either flash an ftf using flashtool or if you are in a region where the update is available take the OTA. You can get the unmodified Customized TW version from here.
2- Make sure your PC can communicate with your tablet via adb.
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the access permission when the tablet prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your tablet, open the Kinguser app, open settings (the wheel at the top right corner of the screen), Root authorization setting, and Remove Root permission. The app may self-uninstall.
6- In any case, after this is done, uninstall the two or three remaining Kingroot apps that are still on your tablet (Kinguser, KingRoot, and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
mv /system/bin/debuggerd_real /system/bin/debuggerd
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
rm -rf /data/data-lib/com.kingroot.RushRoot
rm -rf /data/data-lib/com.kingroot.kinguser
rm -rf /data/data-lib/king
Again, leave the adb terminal window running and go to your tablet.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the tablet. After about 5 minutes your root is ready.
Troubleshooting
If you get this error: "can't stat /system/bin/debuggerd no such file or directory" the solution is here: http://forum.xda-developers.com/showpost.php?p=61386604&postcount=31
Download link
http://forum.xda-developers.com/attachment.php?attachmentid=3307248&d=1431343293

najoor said:
When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work.
Click to expand...
Click to collapse
KingRoot is China's most popular one-click Android root tool, now translated in English and ready to serve you.
XDA Forum: KINGROOT: The One-Click Root Tool for Almost All Devices

Upgraded last night & was waiting for someone to post a guide. Thanks for the hard work! So happy to uninstall all of the built-in sony bloatware!

If I remember correctly after rooting the device all you have to do is install supersu and open it. It will prompt you to remove the Chinese root app and everything will be done automatically. Please correct me if this is not the case.

Thanks so much! Very easy to follow

botsaris said:
If I remember correctly after rooting the device all you have to do is install supersu and open it. It will prompt you to remove the Chinese root app and everything will be done automatically. Please correct me if this is not the case.
Click to expand...
Click to collapse
Yes, I guess this method will work. I'd used kingroot before and SuperSU get rid of it. I haven't tried it in lollipop but i guess it will work.

botsaris said:
If I remember correctly after rooting the device all you have to do is install supersu and open it. It will prompt you to remove the Chinese root app and everything will be done automatically. Please correct me if this is not the case.
Click to expand...
Click to collapse
donedos said:
Yes, I guess this method will work. I'd used kingroot before and SuperSU get rid of it. I haven't tried it in lollipop but i guess it will work.
Click to expand...
Click to collapse
King root 4 does not let you or supersu or anyone else remove or touch it unless you relinquish root privilege. Otherwise what would be the point of such a long post like this?!

najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
You don't need to have root to apply this procedure. Your bootloader doesn't have to be unlocked.
This has been tested with SGP311, 10.6.A.0.454, Lollipop 5.0.2, Customized TW version, but it should work fine on any other customization of 10.6.A.0.454.
This procedure installs superSU root binaries and busybox on your system.
Requirements
1- Upgrade to Lollipop 5.0.2. Either flash an ftf using flashtool or if you are in a region where the update is available take the OTA. You can get the unmodified Customized TW version from here.
2- Make sure your PC can communicate with your tablet via adb.
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the access permission when the tablet prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your tablet, open the Kinguser app, open settings (the wheel at the top right corner of the screen), Root authorization setting, and Remove Root permission. The app may self-uninstall.
6- In any case, after this is done, uninstall the two or three remaining Kingroot apps hat are still on your tablet (Kinguser, KingRoot, and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again, leave the adb terminal window running and go to your tablet.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the tablet. After about 5 minutes your root is ready.
Download link
http://forum.xda-developers.com/attachment.php?attachmentid=3307248&d=1431343293
Click to expand...
Click to collapse
thank you for your hard work .
but it has a problem .
at first type "adb push su /data/local/tmp" ,the KingRoot was allow "root", and then conlose was promot "error: device unauthorized. Please check the confirmation dialog on your device."
need retype "adb push su /data/local/tmp" .
and goon.
中文看这里:
http://bbs.gfan.com/android-7970307-1-1.html

@najoor :
Thanks - worked fine for me :good:

Thank you very much, works perfectly

Thanks a million bro.. works like a charm on Xperia Z 5.0.2!!

Wow , thats bro. Still expecting the lollipop for my c6603

What's wrong with just using King Root for root access instead of SuperSU?

Not working for me... tablet reboots on remount system as rw

Does this method work with SGP321?

Thank you for the tutorial. SuperSU works flawless on my SGP311.
Total time: 10 minutes :good:

I managed to root my Xperia Z (C6602) by following these instructions
najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
You don't need to have root to apply this procedure. Your bootloader doesn't have to be unlocked.
This has been tested with SGP311, 10.6.A.0.454, Lollipop 5.0.2, Customized TW version, but it should work fine on any other customization of 10.6.A.0.454.
This procedure installs superSU root binaries and busybox on your system.
Requirements
1- Upgrade to Lollipop 5.0.2. Either flash an ftf using flashtool or if you are in a region where the update is available take the OTA. You can get the unmodified Customized TW version from here.
2- Make sure your PC can communicate with your tablet via adb.
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the access permission when the tablet prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your tablet, open the Kinguser app, open settings (the wheel at the top right corner of the screen), Root authorization setting, and Remove Root permission. The app may self-uninstall.
6- In any case, after this is done, uninstall the two or three remaining Kingroot apps hat are still on your tablet (Kinguser, KingRoot, and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again, leave the adb terminal window running and go to your tablet.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the tablet. After about 5 minutes your root is ready.
Download link
http://forum.xda-developers.com/attachment.php?attachmentid=3307248&d=1431343293
Click to expand...
Click to collapse
I managed to ROOT & replace the KingRoot with my favorite root manager app SuperSU in my Xperia Z (C6602) running Android 5.0.2 (10.6.A.0.454) by following the above instructions. You are awesome man..
Thanks a lot.

I swapped Kingroot for superSU with your instructions, thank you.
But I have the same question, especially when there is an eglish version of Kingroot.
SickBeast said:
What's wrong with just using King Root for root access instead of SuperSU?
Click to expand...
Click to collapse

JulianK87 said:
I swapped Kingroot for superSU with your instructions, thank you.
But I have the same question, especially when there is an eglish version of Kingroot.
Click to expand...
Click to collapse
I heard many people facing random reeboot issue while any app requests su access and superSU works fine for them as a replacement.
Sent from my C6602 using xda Forums PRO

TiBckUp does not work well with KR
Sent from my VGN-NS10J_S using Tapatalk