FORUMS
Remove All Ads from XDA

Root for Fire Phone with SuperSU

643 posts
Thanks Meter: 877
 
By najoor, Senior Member on 11th May 2015, 12:22 PM
Post Reply Email Thread
** 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.
Attached Files
File Type: zip root.zip - [Click for QR Code] (9.61 MB, 37528 views)
The Following 51 Users Say Thank You to najoor For This Useful Post: [ View ] Gift najoor Ad-Free
 
 
11th May 2015, 03:59 PM |#2  
Senior Member
Thanks Meter: 43
 
More
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
12th May 2015, 12:39 AM |#3  
Member
Flag Chicago
Thanks Meter: 14
 
More
Quote:
Originally Posted by najoor

** 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.

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?
The Following 2 Users Say Thank You to Viperise152 For This Useful Post: [ View ] Gift Viperise152 Ad-Free
12th May 2015, 01:08 AM |#4  
OP Senior Member
Los Angeles
Thanks Meter: 877
 
More
Quote:
Originally Posted by Viperise152

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?

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.
The Following User Says Thank You to najoor For This Useful Post: [ View ] Gift najoor Ad-Free
12th May 2015, 03:16 AM |#5  
Member
Flag Chicago
Thanks Meter: 14
 
More
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.
The Following User Says Thank You to Viperise152 For This Useful Post: [ View ] Gift Viperise152 Ad-Free
12th May 2015, 03:49 AM |#6  
OP Senior Member
Los Angeles
Thanks Meter: 877
 
More
Quote:
Originally Posted by Viperise152

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?

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.
The Following User Says Thank You to najoor For This Useful Post: [ View ] Gift najoor Ad-Free
12th May 2015, 04:05 AM |#7  
Member
Flag Chicago
Thanks Meter: 14
 
More
Quote:
Originally Posted by najoor

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.

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.
The Following User Says Thank You to Viperise152 For This Useful Post: [ View ] Gift Viperise152 Ad-Free
12th May 2015, 04:24 AM |#8  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by Viperise152

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.

Thanks for updating with what you were doing wrong. I was having the same issue. Cheers!
The Following User Says Thank You to funkadelik For This Useful Post: [ View ] Gift funkadelik Ad-Free
12th May 2015, 06:10 AM |#9  
Senior Member
Flag Los Angeles, Paris France
Thanks Meter: 13
 
More
Thumbs up
Quote:
Originally Posted by funkadelik

Thanks for updating with what you were doing wrong. I was having the same issue. Cheers!


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
The Following User Says Thank You to guliver365 For This Useful Post: [ View ] Gift guliver365 Ad-Free
12th May 2015, 01:34 PM |#10  
Junior Member
Thanks Meter: 6
 
More
thx for the guide.

can you explain why it is better to have SuperSu. What is wrong with kingsu?
12th May 2015, 01:45 PM |#11  
Senior Member
Thanks Meter: 86
 
More
planning to do this soon, cheers for the guide

so what is safe to remove out of the stock apps
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes