Related
Thanks go to goroh_kun, ayati and DoomLord. All the usual warnings about attempting to root a phone apply. This works on a phone with build number V16R24C, which is current as of this writing. I can't speak for any later updates.
You will need the following:
Java SDK (required for android dev kit – get the JDK): http://www.oracle.com/technetwork/java/javase/downloads/index.html
ADK: http://developer.android.com/sdk/index.html
ADB driver: http://spf.fmworld.net/oss/usb_driver/f-05d/index.html
F-05D rooting files: http://ayati.cocolog-nifty.com/blog/files/F05Droot.zip
zergRush files (tested with v4): http://forum.xda-developers.com/showthread.php?t=1319653
Optional:
- a terminal application of your choice
- busybox installer from the market
- English versions of the .bat files (remove the .txt extension): http://pastebin.com/RBCWvzES and http://pastebin.com/EQfjpDAM
Part 1, installing the ADB driver:
1. Install the JDK
2. Install the ADK
3. Go to C:\Users\YourUsername\.android and edit the adb_usb.ini file.
4. Add 0x04C5 on a separate line at the bottom. Save and close the file.
5. Reboot the computer or restart adb
6. On the phone, press home, settings, applications – toggle Unknown sources to On.
7. Same place, press development and toggle USB debugging to On.
8. Connect the phone to the PC, and when prompted, navigate to the location where you extracted the ADB driver.
Part 2, rooting the phone:
1. Extract the zergRush and rooting files to the same folder. (put the English versions in the same spot if want to use them instead).
2. With the phone connected and in debug mode, run the f05dsu.bat file (DO NOT RIGHT CLICK AND SELECT RUN AS ADMIN).
3. You first will get asked to go to Settings, Setting my body, Step/activity counter app, Pedometer use, is turned On. Press space after doing that.
4. You will then get asked to toggle the same setting OFF once, then back to ON. After doing that, press space and the phone will reboot
5. Wait for the phone to reboot and connect over USB properly. Press space when ready.
6. Files will be transferred over and the phone rooted. If you don't get any errors, press space and wait for the phone to reboot again.
7. The phone should now be rebooted, and you can install Busybox and Superuser from the market.
I had trouble getting the Busybox installers to work properly at first – the stericson one would wipe su and require re-running the f05dsu.bat, and the jrummy one would simply not start properly. I suggest trying the jrummy16 installer first just to see if it runs. In the end I had to do things manually to get it installed, but once that was done both installers worked fine.
Part 3, optional, installing Busybox manually:
1. If superuser has been lost, re-root the phone.
2. Open up your favorite terminal application and enter the following manually:
Code:
su
soff
mount -o rw,remount /system /system
dd if=/data/local/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
dd if=/data/local/su of=/system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
echo insmod /data/local/lsm_disabler.ko > /system/xbin/soff
chmod 755 /system/xbin/soff
At this point you should be able to do a "which su" and get /system/xbin/su as a response. If you don't get any response, Busybox is not properly installed (start over). Doing a "ls -ls /system/xbin/su" should also NOT return a symbolic link to Busybox – if it does, you'll need to copy over su from /data/local again. The same goes for soff. Once this is done, start up jrummy's Busybox installer to confirm the installed version of Busybox, and upgrade it if you want.
Thanks very much, worked well but sadly I managed to boot loop my phone after rooting it.
Now I need to SIM unlock the phone as the factory unlock code is gone.
F05D rooting
Hi there i have successfully rooted my Fujitsu F05D have root access but I can't seem to loads busy box, I have permission through superuser and it goes through the motions but at the end it says " install unsuccessful".
The files are in the system/bin folder but something is wrong. if I use busy box installer jrimmy16 it just say installing and keeps going and never stops if I got to to scripts and click fix file permissions
" run script" it too just spins round and round..
hmm any hints guys.
Don't do a forced install or whatever it's called, that's how I bootlooped and later SIM locked mine, still yet to send it back haha.
Hello, is this working?? I want to root my Docomo Fujitsu Arrows X F-10.. And also my phone keeps on rebooting Please help.. Any ideas why?
does it work on Fujitsu T-02D?
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
skyraven83 said:
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
Click to expand...
Click to collapse
it seems in the end that it was all in xprivacy problem....
solved and now it is functional
skyraven83 said:
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
Click to expand...
Click to collapse
Just so you know
The reason you probably did not get responses to this is because you posted it in Galaxy Nexus section and not Nexus 4 forums
** 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 **** This method is designed for Amazon fire phone. Do not use it on other devices unless you are familiar with Android file system and are able to apply proper modifications. **
This has been tested with the unlocked US version running 4.6.1.
This procedure installs superSU root binaries and busybox on your system.
Requirements
Make sure your PC can communicate with your fire phone 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 permission when the phone 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 phone, 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 will self-uninstall.
6- Uninstall the other two Kingroot programs that are still on your phone (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
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/shipclean
rm /system/bin/start-ssh
busybox chattr -ia /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install_recovery.sh
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 phone.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the phone. After about 5 minutes your root is ready.
Hint: It is a good idea to disable Amazon device client platform, DCP platform contracts, and two apps called System Updates in Amazon settings. They are responsible for regular updates, constant chatter with Amazon servers, and possible patching of your root exploit. Also disable Kinesis service which is responsible for major battery drain and heating. You will find it under settings, display, configure motion and gesture settings. Disable all.
Troubleshooting
1- Most of the problems that I noticed people have encountered is due to not reading the instructions fully. So make sure you read the OP word by word.
2- If you miss a step or mess up something go back to installing Kingroot and start over from the beginning.
3- If instant video or some other Amazon app doesn't work it is because you should run them at least once prior to rooting the phone.
4- Finally, I noticed that with an AT&T sim card in the phone Kingroot fails (why am I not surprised?) Either a reboot occurs in the middle of rooting or it completes the cycle without accomplishing root. If that occurs, my best advice is to change your phone company. If that fails, you may need to factory reset your phone or even install the firmware from scratch and try again without the sim card.
Okay. Working. I tried it 2 Times because i get in troubles with the SuperSu App.
After First Time i Cant open it anymore after adb shell.
Second Time i installed SuperSu, but after adbshell the app was gone (!?) - but i installed it again with adb shell before reboot. Now SuperSu is Working.
And now tell me how to change the FireOS to a Android Status Bar with Notifications, and youre my Hero ;D
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 **
This has been tested with the unlocked US version running 4.6.1.
Requirements
Make sure your PC can communicate with your fire phone 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 permission when the phone 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 phone, open the Kinguser app, open settings, Root authorization setting, and Remove Root permission .
6- Uninstall the other two Kingroot programs that are still on your phone (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
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh-ku.bak
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
Again, leave the adb terminal window running and go to your phone.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the phone. After about 5 minutes your root is ready.
Hint: It is a good idea to disable Amazon device client platform, DCP platform contracts, and two apps called System Updates in Amazon settings.
Click to expand...
Click to collapse
Not sure what I'm doing wrong but everything works till I get to rm stage of step 7. Im getting 255 read only file system error. Any ideas what I did wrong. since it didnt work to I have reinstall Kingroot and start over or do I start over from the adb shell part?
Viperise152 said:
Not sure what I'm doing wrong but everything works till I get to rm stage of step 7. Im getting 255 read only file system error. Any ideas what I did wrong. since it didnt work to I have reinstall Kingroot and start over or do I start over from the adb shell part?
Click to expand...
Click to collapse
Do you close the adb window between steps 4 and 7? Step 7 should be continued in the window that you left open in step 4.
Do you get any error message after you type each command in part 4?
To redo the process you should install the Kingroot again and stay overt from the beginning.
I did not get any errors for part 4 just when I get to the first rm command in part 7, I'm getting (rm failed for /system/xbin/ku.sud, Read-only file system). Is that normal?
FIXED!!!
Ok i was not following this step properly "open the Kinguser app, open settings, Root authorization setting, and Remove Root permission ." I was not doing through that Root authorization setting which was a few slots down.
Viperise152 said:
Not sure what I'm doing wrong but everything works till I get to rm stage of step 7. Im getting 255 read only file system error. Any ideas what I did wrong. since it didnt work to I have reinstall Kingroot and start over or do I start over from the adb shell part?
Click to expand...
Click to collapse
Please copy and paste the entire content of the adb terminal up to the point that you get the error message and send it to me via pm so I can debug it.
najoor said:
Please copy and paste the entire content of the adb terminal up to the point that you get the error message and send it to me via pm so I can debug it.
Click to expand...
Click to collapse
I still had this page open while I was giving it another go. I figured out what i was doing wrong. The " open the Kinguser app,open settings, Root authorization setting, and remove root permission." part I was just opening Kinguser settings and hitting the big center button turning it off. Did'nt realize i had to go down a few slots to the Root Authorization Setting then hit the Remove Root Permission. After i did it right Kinguser disappeared unistalled the other 2 apps. Everything after that work fine then. Thanks for trying to help me out. Maybe my confusion will help others.
Viperise152 said:
I still had this page open while I was giving it another go. I figured out what i was doing wrong. The " open the Kinguser app,open settings, Root authorization setting, and remove root permission." part I was just opening Kinguser settings and hitting the big center button turning it off. Did'nt realize i had to go down a few slots to the Root Authorization Setting then hit the Remove Root Permission. After i did it right Kinguser disappeared unistalled the other 2 apps. Everything after that work fine then. Thanks for trying to help me out. Maybe my confusion will help others.
Click to expand...
Click to collapse
Thanks for updating with what you were doing wrong. I was having the same issue. Cheers!
funkadelik said:
Thanks for updating with what you were doing wrong. I was having the same issue. Cheers!
Click to expand...
Click to collapse
And me too I should have read your post instead of bugging najoor who has been a great help to resolve my SuperSU
installation
Great thread :good::good:
thx for the guide.
can you explain why it is better to have SuperSu. What is wrong with kingsu?
planning to do this soon, cheers for the guide
so what is safe to remove out of the stock apps
veti said:
thx for the guide.
can you explain why it is better to have SuperSu. What is wrong with kingsu?
Click to expand...
Click to collapse
King user might even be a better SU than superSU, who knows? The problem is that we don't know kinguser. We don't know who wrote it, we don't know what kind of information it gathers, we don't know if it puts a backdoor exploit in your OS, etc. Super SU is a tool that we have used for years. We know exactly what supersu does and who wrote it. We can even communicate with him on xda. Chainfire, the author of SuperSU even has a weblog that he often uses to talk about the intricacies of designing a tool like superSU. There is almost nothing unknown or suspicious about superSU.
On the contrary kingroot/kinguser seems to be intrusive and sneaky. The first thing it does after rooting your phone is to install some random app on it that has nothing to do with rooting and at best I can describe it as bloat. It saves files and folders all over your phone for no apparent reason. Then, it does everything it can to prevent you from removing it. In effect, the only straightforward way to remove it is to give up root, and even then it very suspiciously leaves some executable files behind that God knows if they are sleeper cells or what. To devise the procedure in the OP I had to go through an extensive search to find every little carp that king user has planted into the system and truth be told I will not be surprised if I discover more hidden gems left behind.
The corrected op guide worked great. I had to tap a blue rectangle at two different times to get kingroot to finish (get to a screen that had 100% on it), but other than that, everything worked.
najoor said:
King user might even be a better SU than superSU, who knows? The problem is that we don't know kinguser. We don't know who wrote it, we don't know what kind of information it gathers, we don't know if it puts a backdoor exploit in your OS, etc. Super SU is a tool that we have used for years. We know exactly what supersu does and who wrote it. We can even communicate with him on xda. Chainfire, the author of SuperSU even has a weblog that he often uses to talk about the intricacies of designing a tool like superSU. There is almost nothing unknown or suspicious about superSU.
On the contrary kingroot/kinguser seems to be intrusive and sneaky. The first thing it does after rooting your phone is to install some random app on it that has nothing to do with rooting and at best I can describe it as bloat. It saves files and folders all over your phone for no apparent reason. Then, it does everything it can to prevent you from removing it. In effect, the only straightforward way to remove it is to give up root, and even then it very suspiciously leaves some executable files behind that God knows if they are sleeper cells or what. To devise the procedure in the OP I had to go through an extensive search to find every little carp that king user has planted into the system and truth be told I will not be surprised if I discover more hidden gems left behind.
Click to expand...
Click to collapse
Thank you _so_ much for your effort. I was doing some research too in advance prior to installing kingroot, but didn't get near as much useful information. Sniffing the network connection for any suspicious behaviour via wireshark and my router wasn't successful at all, as they use https.
I came up with the idea that they could have patched some of the system-apps to load an payload even after you tried to "delete everything"(tm). I am currently checking the MD5 and SHA-1 checksum of a identical, second Firephone without root.
---------- Post added at 09:09 PM ---------- Previous post was at 09:05 PM ----------
Also the Mods should pin your post. I totally agree that KingRoot uses intrusive behaviour - as it seems mostly for statistics, but anyway - and should be replaced with the method described in the OP.
EDIT: The MD5 checksum of an unrooted firephone is identical. The System apps might not have been replaced or touched at all. I didn't got a easy chance to check all apps with the SHA-1 checksum though.
Followed the directions and got the root with 0 issues
Just saw this article saying root is now achievable w/ SuperSU via Towelroot: http://dottech.org/180812/how-to-root-amazon-fire-phone-on-android-4-4-kitkat-guide/
Can anyone verify?
amf100 said:
Just saw this article saying root is now achievable w/ SuperSU via Towelroot: http://dottech.org/180812/how-to-root-amazon-fire-phone-on-android-4-4-kitkat-guide/
Can anyone verify?
Click to expand...
Click to collapse
No, it doesn't work. When you run it, the towelroot app pops up a message saying the phone is currently not supported.
Hmph! That's too bad. I wasn't with my fire phone to check for myself. The internet is so weird lol. Why make a whole page with instructions for nothing? Ugh lol
rm /system/bin/rt.sh
Click to expand...
Click to collapse
This part is not working for me. Can't seem to remove it with root explorer either. Any tips?
Im on 4.6.1 with SuperSu. If im Sideload 4.6.1 again and do an Factory Reset. Is root gone? Because Amazon send me New One Because Hardware issues
AT&T D850
Stock, rooted, Bump'd TWRP recovery installed
I noticed today that when viewing a files' properties in Solidexplorer, the Change Permissions button was missing.
I made sure the latest busybox was installed and noticed there that "chmod", "chown", and "chcon "are NOT re-linked to "busybox" but left linked to "toolbox". I didn't want to change the symlink without explicitly trying the chmod command (via toolbox and busybox) first to see if it worked.
I opened Terminial Emulator, su'd to root, then navigated to an mp3 file I have on my external sdcard, and issued both
Code:
chmod 777 "file"
busybox chmod 777 "file"
and nothing happened.
No error, but no change in the permission either (it is 770).
Anyone have a clue as to what's wrong?
UPDATE:
The problem appears to be caused by me not being thorough, not SELinux.
In summary, the SDcard is formatted as exFat which doesn't retain Linux file permissions, therefore, issuing a chmod yields no result, but no error. Solidexplorer is "smart enough" to know that fact and so there is not button to change permissions available.
After dabbling around in some murky waters trying to achieve root, and going trough some 2010 stuff I did, I did discover a method I devised back then works to some extent, strangely.
Using fastboot (boot) to a TWRP recovery image (TWRP_v2.8.6.0_honami-f2fs_from_cm12.1_150423.img), mounting /system, and pushing a version of busybox, bash and using the supersu su binary already in the TWRP recovery image.
boot-new.img.bz2.zip (rename to boot-new.img.bz2 before extracting -.Just TWRP_v2.8.6.0_honami, with a different kernel and dt image included to boot from fastboot)
bash and busybox i compiled from git and debian sources yesterday/today
Basically this; (use only for reference.)
Code:
# Magically push all files in place here.
# Optionally, move /system/bin/sh out of the way and link /system/bin/sh to bash
./"$ADB" shell "chmod 755 /system/bin/bash && chown 0.0 /system/bin/bash"
./"$ADB" shell "chmod 4755 /system/bin/busybox && chown 0.0 /system/bin/busybox"
# TWRP
#./"$ADB" shell "cp /supersu/su /system/bin/_su"
./"$ADB" shell "cp /supersu/su /system/bin/su"
./"$ADB" shell "cp /supersu/supolicy /supersu/su /system/xbin"
./"$ADB" shell "cp /supersu/libsupol.so /system/lib/"
./"$ADB" shell "chmod 0644 /system/lib/libsupol.so && chown 0.0 /system/lib/libsupol.so"
./"$ADB" shell "cp -r /supersu /system/app/SuperSU"
./"$ADB" shell "chmod 0755 /system/app/SuperSU && chown 0.0 /system/app/SuperSU && chmod 0644 /system/app/SuperSU/SuperSU.apk"
#
#./"$ADB" shell "chmod 4755 /system/bin/_su && chown 0.0 /system/bin/_su"
#./"$ADB" shell "echo "busybox su -c "_su"" > /system/bin/su" # or busybox su -c "_su -c /system/bin/sh-org"
./"$ADB" shell "chmod 4755 /system/bin/su /system/xbin/su* && chown 0.0 /system/bin/su system/xbin/su*"
# Quite dangerous - Suggest moving passwd when in normal use
./"$ADB" shell "echo "root::0:0:0:/root:/system/bin/sh" > /system/etc/passwd"
./"$ADB" shell "chmod 0644 /system/etc/passwd"
Next step, to remount /system with write permissions from a normal boot, I think, would be to modify boot.img/default.prop and set "ro.secure=0"
Thought I had done this prior, I run with touch disabled as I cracked my screen (impressively massive drop of at least 30 cm! - onto object.. ) ... I could not remount system when I first tried.
Notes:
If i adb in early i can use supersu/su to gain root, when system is loaded busybox su -c ""supersu/"su" works. - NO AUTH
Hm, updated SuperSU via google play and suddenly it realized it was rooted . = ) Still keeping the supersu/su intact in /system/*bin
Thankfully I've been unsuccessful in grabbing root from /data/local/tmp this way as of now. Seems the permissions are reset. Though getting root without any auth is a serious matter no matter how you flip the coin. At least it's not as easy as pushing an archive to /data/local/tmp and running busybox su -c su. Also with a modified busybox you could easily skip the part where I write a /etc/passwd with no password.. Incredibly handy if you need root without Android running, say with setprop ctl.stop zygote, media and bootanim. But incredibly dangerous!
Fastboot to attached TWRP and install [STABLE][2016.02.02] SuperSU v2.65 - http://forum.xda-developers.com/showthread.php?t=1538053 - drop the zip to somewhere on the device and use the install function, i installed supersu via google play first. Attached is the kernel image i'm using. On a side-note, the script above failed .
Apart from this, the attached gnu-tools i will have to update... Got a neon flags optimized for out cpu and all, but that's for a different day.
Cheers, have a good one mates
Noob question: what is the difference between using this method for root and kingroot method? Which is better to use?
I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image
threader said:
I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image
Click to expand...
Click to collapse
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric
Noticed my boot img was rebooting sometimes, went off and updated my compiler toolchain and had a look at the kernel and recent developments.
Had a look at X-Honami v6 and ported some parts of that effort to the latter Sony kernel used in 14.6.a.1.216.
* Messed around with memutils and implemented ARM_PLD_64BYTE and USE_LDRDSTRD_OVER_LDMSTM atop memutils from the Xperia-dev unified kernel. - this needs some testing but appears to be stable at least with the options turned on.
* Slight overclock of GPU to 533 mhz, and underclock to 27 mhz on idle.
* Has kexec hardboot
I cannot busybox su -c su with this kernel. Which is only useful for developers anyway. You'd be wise in running some benchmarks before and after the flash.
Kernel needs to be flashed via fastboot.
Source:
https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/
DectonX said:
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric
Click to expand...
Click to collapse
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
Ok i have done step #1 by manually updating supersu and it deleted the kingroot by itself. Now i need answer for #2 only, Which recovery should i install in stock based rom ?
VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped
DectonX said:
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped
Click to expand...
Click to collapse
Thanks a lot..
I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
VikasG09 said:
Thanks a lot..
Click to expand...
Click to collapse
threader said:
I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
Click to expand...
Click to collapse
I just used kingroot, unlocked bootloader, flashed dual recovery, flashed prerooted Rom. That's it. Easy as pie.
Sent from my D5503 using Tapatalk