Related
Hi all,
I'm trying to run a shell script in sl4a but I'm running into problems. Here's what I want to do: change ADW configuration files in one click (since the app doesn't yet do it natively). There are two files that need to be changed for this to happen:
Code:
/data/data/org.adwfreak.launcher/databases/launcher.db
/data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
I'm trying to delete those files and copy in new files from a stored location on the SD card but I can't get the sl4a script to run the following rm commands:
Code:
rm -rR /data/data/org.adwfreak.launcher/databases/launcher.db
rm -rR /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
I use
Code:
su -c
before the rm commands to run them as root, but the error then is that the /data partition is not mounted (which I find strange since it should be rw anyway...). I've tried using
Code:
mount -o remount,rw /dev/block/userdata /data
and it looks like it runs but then it doesn't work and I can't rm the files anyway.
Am I running into a limitation of sl4a or shell scripts in sl4a? I can rm the files from the terminal, so I'm not sure what the issue is. I'm very new to this (obviously) so any tips would be helpful. Thanks!
Here is my full script currently:
Code:
#!
kill android.process.acore
kill org.adwfreak.launcher
busybox rm -R /data/data/org.adwfreak.launcher/databases/*
busybox rm -R /data/data/org.adwfreak.launcher/files/*
busybox rm -R /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw_ex_launcher.db /sdcard/ADW/Honeycomb/adw_ex_launcher.db
cp /sdcard/adw_ex_settings.xml /sdcard/ADW/Honeycomb/adw_ex_settings.xml
cp /sdcard/ADW/Portrait/adw_ex_launcher.db /sdcard/adw_ex_launcher.db
cp /sdcard/ADW/Portrait/adw_ex_launcher.db /data/data/org.adwfreak.launcher/databases/launcher.db
chmod 664 /data/data/org.adwfreak.launcher/databases/launcher.db
cp /sdcard/ADW/Portrait/adw_ex_settings.xml /sdcard/adw_ex_settings.xml
cp /sdcard/ADW/Portrait/adw_ex_settings.xml /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
chmod 664 /data/data/org.adwfreak.launcher/shared_prefs/adw_ex_preferences.xml
exit
When I test the rm commands in the sl4a shell, they don't remove the files even when the /data partition is mounted. I've tried all that I know. Help please!
Sent from my DROIDX
I don't know what you are trying in your second post, but from your first post I would say:
Code:
su
busybox rm -r /data/data/org.adwfreak.launcher/databases/*
busybox rm -r /data/data/org.adwfreak.launcher/files/*
busybox rm -r /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw/prefs.xml /data/data/org.adwfreak.launcher/shared_prefs/
..
kill org.adwfreak.launcher
If you do "chmod 664" on the files, you also have to do "chown & chgrp" or the launcher won't be able to write into the settings xml's/db's.
And /data ist mounted rw, everything else would be senseless.
Thanks for the response.
I'm trying to change ADW configuration with one click. I'm going to use Tasker to create a widget that, when clicked, runs a script. That script will:
1. delete the current ADW configuration files (launcher.db and adw_ex_preferences.xml)
2. copy the target configuration files to the proper places (and set permissions, owner, group)
3. restart ADW so that the configuration is loaded
OR
3. open the ADW settings page so that I can click "restore desktop" and "restore preferences" and have the configuration loaded in an almost-one-click solution.
The script in the 2nd post is my best effort at that. I have tried the busybox part of the script, but I don't believe it makes a difference. I will try again, though, and report back.
As far as chown and chgrp goes, I'll add in what I think that should be and post that back later, too.
Fr4gg0r said:
I don't know what you are trying in your second post, but from your first post I would say:
Code:
su
busybox rm -r /data/data/org.adwfreak.launcher/databases/*
busybox rm -r /data/data/org.adwfreak.launcher/files/*
busybox rm -r /data/data/org.adwfreak.launcher/shared_prefs/*
cp /sdcard/adw/prefs.xml /data/data/org.adwfreak.launcher/shared_prefs/
..
kill org.adwfreak.launcher
If you do "chmod 664" on the files, you also have to do "chown & chgrp" or the launcher won't be able to write into the settings xml's/db's.
And /data ist mounted rw, everything else would be senseless.
Click to expand...
Click to collapse
Progress update: Success! More or less.
I realized I wouldn't need to remove the files since the ones I was copying in would just overwrite them anyway, so that cleared up that issue.
I did add chown and chgrp (a piece of information I'm sure I'll find useful in the future) so I'm sure that helped. Making sure to get the group and owner right PER YOUR OWN SETUP was key. When I changed ROMs I had to redo it... so check properties with Root Explorer or whatever.
I revised my script a little to add the background wall paper, too.
The true key, however, was using Lua in SL4A and using the 'sush' script in this post here:
http://code.google.com/p/android-scripting/issues/detail?id=184 (comment #9). That allowed me to run my script in the 'sush' format and do what I wanted.
I also had to add a line to kill the launcher process (android.process.acore) so it would restart itself.
I now have a one-click solution to changing between two ADW desktop configurations/settings!
I've attached my script if anyone would like it. Just get SL4A, the Lua interpreter, and put the pieces together! (Use a custom shortcut on the desktop and not a widget and the desktop setup will be preserved; widgets aren't supported in any method...)
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
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?
I was using SwiFTP to upload files, but it seemed to freeze when downloading ...
The reason is that the /system/bin/ls command on S3 returns output which is different from previous Android versions ...
The solution is to replace /system/bin/ls (which points to toolbox) to point to busybox.
Code:
cd /system/bin
mv ls ls.orig
ln -s /system/xbin/busybox ls
Make sure you have busybox installed in /system/xbin and that your /system partition is mounted read/write.
If you don't know what this is doing, please don't attempt to do it
Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
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 &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
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 this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
I have used King's Root to root my phone. My issue is random reboot whenever an app tires to get root access. And titanium backup is not able to backup (it keeps on saying insufficient storage on 20GB free storage area) or delete any app. Plus, I also get random reboot whenever an app having root access is updated over Play Store. And from random reboot it reboots some times and sometimes it doesn't reboot.
So, if anyone having same issue kindly ping back.
(I will post update after reflashing the ftf)
Replace KingUser app with SuperSU
DrXperience said:
I have used King's Root to root my phone. My issue is random reboot whenever an app tires to get root access. And titanium backup is not able to backup (it keeps on saying insufficient storage on 20GB free storage area) or delete any app. Plus, I also get random reboot whenever an app having root access is updated over Play Store. And from random reboot it reboots some times and sometimes it doesn't reboot.
So, if anyone having same issue kindly ping back.
(I will post update after reflashing the ftf)
Click to expand...
Click to collapse
To deal with random reboot issue, I would suggest you to replace KingUser app with SuperSU as described above.
For TitaniumBackup issue, try this:
Open TitaniumBackup, Go to MENU -- Preferences -- Backup folder location.
You will see Storage provider: (Click to change) and you will see multiple option of storage providers. Select second option DocumentProvider Storage and then click on SD Card option and at the bottom of screen you will see select "SD Card". Click on this option. It is important that you do not select any folder inside SD Card, you only have to select the SD Card option. Now select <<Create a new folder>> and then select USE THE CURRENT FOLDER.
To make it more clear, I have attached the snapshots, please go through snapshots one by one and you will be able to fix insufficient free storage error in TB.
SurenderK said:
To deal with random reboot issue, I would suggest you to replace KingUser app with SuperSU as described above.
For TitaniumBackup issue, try this:
Open TitaniumBackup, Go to MENU -- Preferences -- Backup folder location.
You will see Storage provider: (Click to change) and you will see multiple option of storage providers. Select second option DocumentProvider Storage and then click on SD Card option and at the bottom of screen you will see select "SD Card". Click on this option. It is important that you do not select any folder inside SD Card, you only have to select the SD Card option. Now select <<Create a new folder>> and then select USE THE CURRENT FOLDER.
To make it more clear, I have attached the snapshots, please go through snapshots one by one and you will be able to fix insufficient free storage error in TB.
Click to expand...
Click to collapse
Okay I will give it a shot :highfive:
And you have not provided download link. Provide that in your first post.
Download link sent
DrXperience said:
And you have not provided download link. Provide that in your first post.
Click to expand...
Click to collapse
Hey DrXperience,
Check your PM, I have sent the download link through PM....
Try both links, one should be working
can i have download link plz?
SmunksRiley said:
can i have download link plz?
Click to expand...
Click to collapse
Hey SmunksRiley,
Please check your PM. I have sent the link.
Sent from my C6602 using xda Forums PRO
hi sir
sir can i have a link to i need to replace kings app to avoid random reboot
bagsey said:
sir can i have a link to i need to replace kings app to avoid random reboot
Click to expand...
Click to collapse
Hey, please check your PM. I have sent the download link
Sent from my C6602 using xda Forums PRO
SurenderK said:
Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
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 &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
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 this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
Click to expand...
Click to collapse
The following lines in script gives error
busybox chattr -ia /system/xbin/ku.sud
chattr: stat /system/xbin/ku.sud: No such file or directory
busybox chattr -ia /system/bin/.usr/.ku
chattr: stat /system/bin/.usr/.ku: No such file or directory
busybox chattr -ia /system/usr/iku/isu
chattr: stat /system/bin/usr/iku/isu: No such file or directory
DrXperience said:
The following lines in script gives error
busybox chattr -ia /system/xbin/ku.sud
chattr: stat /system/xbin/ku.sud: No such file or directory
busybox chattr -ia /system/bin/.usr/.ku
chattr: stat /system/bin/.usr/.ku: No such file or directory
busybox chattr -ia /system/usr/iku/isu
chattr: stat /system/bin/usr/iku/isu: No such file or directory
Click to expand...
Click to collapse
Hi,
Ignore the error if it says No such file or directory. Proceed to next commands and once completed reboot your device. You will get SuperSU working and KingUser replaced.
Sent from my C6602 using xda Forums PRO
SurenderK said:
Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
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 &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
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 this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
Click to expand...
Click to collapse
Sadly my phone reboots as soon as I get to the point where I mount /system ("mount -o remount,rw /system" ). Probably caused by RIC, any suggestions on how to avoid this?
cruzersteve said:
Sadly my phone reboots as soon as I get to the point where I mount /system ("mount -o remount,rw /system" ). Probably caused by RIC, any suggestions on how to avoid this?
Click to expand...
Click to collapse
Hi,
Please check this xda thread. Might help you out.
http://forum.xda-developers.com/xpe...b-definitive-root-remount-reboot-fix-t2317432
Sent from my C6602 using xda Forums PRO
Anyone tryed on c6603?
hey surrenderk, i did the mistake of following this tutorial and literally copy pasted everything despite not having a sony, but an infinix hot note, just because i wanted to remove kinguser and kingroot and have superuser as the dedfault application for handling root access. any way to reverse everything we just did, coz i cant update via ota?? shell commands to undo everything perhaps that affected the "system" folder or that affected normal working of device??thanks!!
Jokichu said:
hey surrenderk, i did the mistake of following this tutorial and literally copy pasted everything despite not having a sony, but an infinix hot note, just because i wanted to remove kinguser and kingroot and have superuser as the dedfault application for handling root access. any way to reverse everything we just did, coz i cant update via ota?? shell commands to undo everything perhaps that affected the "system" folder or that affected normal working of device??thanks!!
Click to expand...
Click to collapse
Which device and software are you using??
Are you observing any strange behaviour in your device after making changes?
Sent from my C6602 using xda Forums PRO
Hey surrenderk yep, the problem is that somehow, I can't see any Ota update. It's says it's up to date, while I know there's an upgrade. In the steps we did, did we in any way change anything related to that??
I was already rooted, and had kinguser, and used kingroot. Whenever an Ota update came I could just unroot, perform the update then root again, easy.
However since I followed your tutorial steps with the adb shell, I received an Ota update, and did the unroot as usual, but the system found several files failing the root integrity tests, thus failing to update. My questions are
1.all these rm commands we used, did we remove/delete any core essential android file from the system folder? Bin folder? (debuggered /real/64) kroot_*, iku, kr-stock-conf, icusuflag.conf,
2.what do the rt.sh and install-recovery.sh scripts do?
My phone had become unstable, and could not play videos well nor audio files, it kept stuttering like it's buffering from an online Stream. Anyways, I am now unrooted and did a factory reset which fixed the video/audio glitch but still cannot "see" any new update although it's there. I just want want that update.
Sent from my Infinix-X551 using XDA Free mobile app
Question:
Why is the link not available in the OP?
Why is the link only shared thru PM?
Isn't this XDA - a sharing community?
This thread is just a little too weird.