yashsingh1/xdaforums huggingface dataset:
[Amazon Fire Phone] veti:
thx for the guide.

can you explain why it is better to have SuperSu. What is wrong with kingsu?
[Amazon Fire Phone] russy23:
planning to do this soon, cheers for the guide

so what is safe to remove out of the stock apps
[Amazon Fire Phone] najoor:
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.
[Amazon Fire Phone] rster:
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.
[Amazon Fire Phone] Lianju7:
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.
[Amazon Fire Phone] jdineshk:
Followed the directions and got the root with 0 issues
[Amazon Fire Phone] amf100:
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?
[Amazon Fire Phone] kabloink:
No, it doesn't work. When you run it, the towelroot app pops up a message saying the phone is currently not supported.
[Amazon Fire Phone] amf100:
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
[Amazon Fire Phone] bgroins:
This part is not working for me. Can't seem to remove it with root explorer either. Any tips?
[Amazon Fire Phone] hydromän:
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
[Amazon Fire Phone] mnknight:
first off this worked great! second I have to point out I do not have an unlocked phone and this worked great, no adverse effects yet.
[Amazon Fire Phone] najoor:
Yes.
[Amazon Fire Phone] russy23:
question, what if i need to use mayday, cant they remotely control my phone and see all apps??
[Amazon Fire Phone] najoor:
They can indeed see everything you have in your phone when you connect through Mayday. But I am not sure if rooting voids your warranty or your service.

Honestly, if they REALLY want to know what apps you have they can do it even without the Mayday. Your phone talks to amazon servers and sends data back and forth tens of times every day and it literally takes them one additional line of code to add the list of your apps and your root status to the data that is being exchanged.
[Amazon Fire Phone] hydromän:
Works also on my Kindle Fire HD Soho 7"
[Amazon Fire Phone] PIRATA!:
What does the SuperSU in the root.zip file in first page have different from official SuperSU??

Thank you.
[Amazon Fire Phone] najoor:
Absolutely no difference. You can install your own version of you want.
[Amazon Fire Phone] PIRATA!:
Do you think the method in first page could be applied also to other phones kind, like Samsung?
[Amazon Fire Phone] najoor:
The method can be applied but the script should perhaps change to match the file names if they are different for Samsung
[Amazon Fire Phone] PIRATA!:
Ok, but when you say to use the SuperSU and place it in the adb folder, you refer at the su and busybox files in your zip?

When you say to install the SuperSU on the device, you referee at SuperSU.apk?

Where did you get those three files there? From the official recovery .zip SuperSU file?

Tnx.

---------- Post added at 11:14 AM ---------- Previous post was at 10:33 AM ----------

Ah! Sorry, another thing... In your guide you have:

......

rm /system/etc/install-recovery.sh

rm /system/etc/install-recovery.sh-ku.bak

rm /system/etc/install-recovery.sh

....

Is this a mistake to repeat the rm of the install-recovery.sh file?
[Amazon Fire Phone] najoor:
All the files are from the standard distributions of SuperSU and busybox. As I said before I didn't change them. And the rm was a typo which fortunately didn't affect the functionality of the code but I fixed it anyway. Thanks.
[Amazon Fire Phone] positivehxcgo:
Is it not possible to just install the APK's within the zip file??

All this ADB talk is a little above my competency level - I'm used to clicking and commanding through pre-scripted command prompt files for my previous android devices.. Guessing it's only because this is less than a week old things are still for advanced users.
[Amazon Fire Phone] romario3600:
WORKS!!

Thank you soooo much, just the fact that i was able to root it so easily, i may not really need the SU app as i never really used it other than for granting permissions from its popups so kingroot will work for me.
[Amazon Fire Phone] AbdouRetro:
ADB Problems!!

i couldn't get adb on windows to su.. it just plain refused.. and i was a day away from my linux PC.. but i couldn't wait.. so i copy-pasted the commands into the terminal emulator.. i couldn't make a script and i wasn't bothered to figure it out..

trick is that you have to escalate previliges in the terminal before you do anything and move with the double-tap home-button between apps in order to prevent the phone from closing any important application..

I was able to do it at the end..

if now someone can bother making this into a script.. that would be great..
[Amazon Fire Phone] stunvn:
Hey it works :D
[Amazon Fire Phone] hanghuutri:
I make a mistake but success rooting? will anything go wrong?

Hi Najoor, I do steps in your guide until step 7, but I made mistake because of scrolling web-browser, and do the following command:

before the first three these:

after recognize this, I run those first three command in step 7 and continue the rest.

After all, my phone still rooted successful.

Will I get anything go wrong in furture?

Thanks.
[Amazon Fire Phone] najoor:
Have you successfully installed SuperSU and run it? If so, no, you should be fine. Just for peace of mind, go to /system/xbin and delete ku.sud if you see it there.
[Amazon Fire Phone] hanghuutri:
ku.sud is not there anymore, but /system/xbin/supolicy still exists!

Hi friend Najoor, I do some checks:

I see in your guide, there a a command which delete the file "/system/xbin/supolicy", in my case, it's still there after whole rooting process.

Does it happen in your case? Is it ok?

Thanks so much.
[Amazon Fire Phone] najoor:
That is why I asked you if you have installed SuperSU or not, because SuperSU replaces the supolicy from kingroot with its own supolicy so you don't need to remove it. To verify that you can check and see if it has the same time and date as sugote in the same directory.
[Amazon Fire Phone] hanghuutri:
Yes, yes, after installed SuperSU and restart phone, I get SuperSU working right.

I just don't know if I completely remove Kingroot because seeing supolicy appears again and I don't know what that means. (I'm newbie).

Again, thanks so much brother.
[Amazon Fire Phone] cyberdon83:
no SU binary installed?

So I made it all the way to installing SuperSU, but once it loads it gives me a popup "There is no SU binary installed..." I will factory reset the phone again and start over, I was really just wondering if anyone was wiser than I as to what I may have done wrong. Any thoughts are greatly appreciated.
[Amazon Fire Phone] crystalsrt:
Hey guys, i tried several times, but it seems does not work with my device (software version: Fire OS 3.6.8 (128003620)). Does anyone who has rooted the device with software version 3.6.8 and install the android lollipop successfully?
[Amazon Fire Phone] StygiAn TrepidAtioN:
Najoor, does this mean that I have to enable USB debugging before getting on with ur guide?

And does SafinWasi's guide still hold good for Fire OS 4.6.1? If so, can you also guide me to "make sure you have the Android SDK installed,adb and fastboot working" (sic). If, however, it's a different procedure for 4.6.1, let me know.

TIA,

JoEy
[Amazon Fire Phone] najoor:
Yes, you have to enable usb debugging. Judging by the number of the hits that the mentioned guide has I'm confident it is sufficient if you follow it closely. The procedure is that same for all versions of the os.
[Amazon Fire Phone] anameOSF:
hello najoor

thanks for the tutorial. Almost everything works fine for me. But i have a little problem. If i switched to another launcher and afterwards i want to go back to the stock launcher this launcher will not start up. It terminates and start again and again. The only thing i can do is to deinstall the stock launcher and reactivate another launcher at the shell. Any hints?

Thanks for your help.
[Amazon Fire Phone] bradwatson:
This worked for the Razer Forge TV as well. Thanks so much!
[Amazon Fire Phone] dk1keith:
Do you connect to your phone via adb before running kingroot? Or does kingroot connect to your phone through adb? Reason I'm asking is because I would like to try this method on my Fire TV.

Thanks
[Amazon Fire Phone] najoor:
I am not familiar with fire TV but to answer your question you can first install and run kingroot and then connect the phone to computer through USB for adb.
[Amazon Fire Phone] PIRATA!:
I've watched at a method similar to yours in the PingPong thread that uses like you a folder with the busybox, su and SuperSU.apk files.

That version has the same (md5 check) busybox and SuperSU.apk files...but the su file there is different from yours.

I refer to this post from Gunthermic, and related supersu.7z file is in first page, first post attached.

If you know why, can you please tell me?

Thank you.

EDIT:

I have made the md5 also to Mr.W0lf files (Mr.W0lf website with last versions here) and to LilTechPrincess and also those look different. These two are auto scripts to replace KingUser with SuperSU, but they have the same Supersu files to be applied, but differ from yours.

Maybe it depends by the Supersu version that they have adopted in their work?
[Amazon Fire Phone] adix82:
For those who doesn't own a pc or laptop or Mac.

You can also use kingroot to root.

Open the file manager in your device. Make sure it's has root explorer.

Copy and paste the unzip su and busybox to /data/local/tmp

Install Android terminal in your device and type su

From there on, type in everything bro najoor instructed

Install the superuser.apk

Install the binary and it should be successful.

No pc or laptop needed. Every step just by using your Android phone.
[Amazon Fire Phone] PIRATA!:
Why not writing a script to copy in root directory of phone and then execute with SManager or Terminal Emulator?

Would prevent any typo..
[Amazon Fire Phone] hydromän:
Nice idea. :)
[Amazon Fire Phone] PIRATA!:
[MENTION=5769394]najoor[/MENTION] here is what I'm talking about (image in attach)
[Amazon Fire Phone] najoor:
Different versions of binaries have different sizes and checksums. Sorry, but I cannot comment on other people's work. You need to contact them directly to find out what version of what binary they are using.
[Amazon Fire Phone] Viperise152:
Najoor you mention disabling the 4 Amazon services. Question will this block all the incoming updates like Silk, Fire Fly, or the lock screens or just the system updates?
[Amazon Fire Phone] hydromän:
Tried to freeze Amazon Lockscreen with titanium. But its still there
[Amazon Fire Phone] najoor:
For me it blocked every thing.
[Amazon Fire Phone] PIRATA!:
Ok.

What version of binary do you use?
[Amazon Fire Phone] najoor:
2.46 supersu and 1.18 busybox.
[Amazon Fire Phone] markwebb:
I could not get my pc to recognize device....actually on any pc.

So what I did was:

1.Copy and paste the unzip su and busybox to /data/local/tmp on the phone.

2.Copy and paste the 2 scripts in the instructions into a text file.

3. Installed terminal emulator on phone.

4. Copied and pasted the contents of script file into terminal emulator and followed instructions. VOILA!

5. Rooted in 5 minutes.

Didn't need to worry about typing errors.

Didn't need a PC. I don't trust this kingroot app and always prefer SuperSU.
[Amazon Fire Phone] PIRATA!:
Well...how did you manage to root only with SuperSU?

I thought that rooting is something you must achieve with other ways, like CF-Root or KingRoot out iRoot, and that SuperSU is only something extra.

You just did this that is in first page and ended up with a rooted phone??

You say two scripts...

You mean that one it's to be applied before uninstalling KingUser and the second part to be applied afterwards, right? Not all together, but with the uninstallation of KingUser in the middle as it's explained in the procedure, right?

What device do you have?
[Amazon Fire Phone] gcbxda:
just tried the mount command without root just to make sure I'm not crazy :) . obviously it failed without previous root. i share the incredulity.

also, i will never use kingroot until i figure out/get time to look inside. :(
[Amazon Fire Phone] PIRATA!:
And about the su file version? still 2.46?

I see a lot of different su files in the SuperSU original flashable .zip file, all of them placed in different folders. Which one have you choose for your replacement method?

Why did't you managed to install even the other files included in the folder from where you have extracted the su file?

Thank you so much.
[Amazon Fire Phone] rtnmich:
thank you!

Your information was very helpful! I successfully changed kinguser to super su.
[Amazon Fire Phone] russy23:
ok getting somewhere, but adb doesnt see a device

it seems to be a driver issue, where do i get the latest driver from

Got there in the end..:)
[Amazon Fire Phone] PIRATA!:
It appear that last KingRoot (file KingRoot-4.1.0.249-release-nolog-201505211812_105241.apk) rooted my Samsung S5 Prime SM-G906K with Qualcomm Snapdragon 805 cpu, and replacing like you say will result in keeping root, BUT after reboot the device looses its root!!!
[Amazon Fire Phone] najoor:
The instruction in this thread is only designed for Fire phone, not Samsung s5.
[Amazon Fire Phone] PIRATA!:
But the files are those...
[Amazon Fire Phone] O.a.T.:
Like you, and others, I never could get adb to see my device. As markwebb suggested, I then decided to go the ES Explorer & Terminal Emulator route, along with making a .txt file with the listed commands. Very seriously, it took about 5 minutes to root, excluding the time to update the su binaries and the time to reboot. Even if you do get adb to recognize your device, I'd suggest this method for ease and expediency!
[Amazon Fire Phone] O.a.T.:
Has anyone tried this method on the 4th Generation Kindle Fire HDX 7"?
[Amazon Fire Phone] Bryanrd05:
Thank you

Working with Kindle Fire HD 2013 KFSOWI. Thanks for the guide :)
[Amazon Fire Phone] :
W0lfdroid updated his 'replace Kingroot / KingUser with SuperSU" script:

www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Script works well.

KingUser got updated to version 4.0.5 this month and it's still a "PUPpy" in the eyes of some AV tools.

www.virustotal.com/de/file/227db637...5dba0b4971069f88af9279a8dd17e9d98bb/analysis/
[Amazon Fire Phone] PIRATA!:
Check Mr.W0lf thread for my experience. Last posts.

You'll find it here on XDA.
[Amazon Fire Phone] Viperise152:
http://www.xda-developers.com/kindle-fire-hd-6-and-7-receive-bootloader-unlock-and-twrp/

Will this help us Fire Phone users?
[Amazon Fire Phone] Eiermann78:
I already tried this and CuberHDX.py, too but it fails with Unlock Code is NOT correct

Maybe the Steps would be right, but i don´t know how to figure out the correct code for the fire phone.

Tested at Fire OS 3.5 and 4.6.1
[Amazon Fire Phone] :
@ Viperise152 & Eggmän78 Sadly: No, it won't help. The unlock for the 6" and 7" is based on the HDX bootloader unlock method. This vuln. was already fixed for the FirePhone by Amazon.
[Amazon Fire Phone] JowyOMac:
:D Thanks
[Amazon Fire Phone] odizeuz:
Fire Phone Black Screen of Death

Hello all,

I've managed to put my device into coma in a very creative way. First I've successfully rooted my Amazon Fire Phone using the instructions on this thread, then changed to superSu. I've granted permissions to ES File Explorer and some days later I made some modifications to the build.prop file. Nothing went wrong there, just that I wanted to go back to the original version, so I copied my backup back to /system BUT I forgot to change permissions (644) back on the file, so when I rebooted... BSOD

Now here is what I've tried: connected with adb shell and then su but it doesn't give me root, as I haven't approve that with superSu, so I got a background job waiting forever. Tried to go recovery mode but no adb there, choose adb sideload from the menu, but when I try to sideload a simple zip with a updater-script that change the permission. It fails with :

E: Footer is wrong

E. Signature Verification Failed

Installation aborted.

I'm stuck. I've been thinking about programmatically accept su request from superSu or try to remount /system partition from ES Explorer using adb somehow.

Any help would be greatly appreciated. I'm attaching my update.zip file just in case.
[Amazon Fire Phone] :
@ odizeuz AFAIK, ADB on Fire Phone only allows sideloading, so you're out of luck and options, it seems. :/ (edit: darn, I see you only tested a ZIP, not the BIN)

Whenever I make changes to build.prop, I use a tool like "Kernel Adiutor", since I only change 3 or 4 values. No need for replacing the whole file... but I guess I stop talking before you strangle me with the powercord. ^^
[Amazon Fire Phone] odizeuz:
Thank you very much. I managed to save the day by sideloading the bin upgrade http://xdaforums.com/fire-phone/general/unlocked-fire-phone-4-6-1-bin-file-t3100538

I'll try to be more careful from now on :cowboy:
[Amazon Fire Phone] WillyJo:
Ousting KingUser

I rooted my tablet with Kingo ROOT which said it would install SuperuserSU but when the root was successfully done I found KingUser installed instead of SuperuserSU. My tablet is rooted and I have not made any changes in the internal. Still running stock Kitkat 4.4..2. If I simply do a factory reset wouldn't that get rid of root and put my tablet back to original state? Then I could just start over and root by another method, right?
[Amazon Fire Phone] najoor:
This is a thread for Fire phone, which is a phone. Your question is about a tablet and should therefore be posted in your tablet's corresponding forum.

Having said that, a factory reset does not remove the root and will not bring your tablet back to the original state. You will need to search the xda forum for your tablet to see how you can flash a firmware and return the tablet to the original settings.

And one last thing, since you are a new member of the xda: when you want to ask a question about a post please only quote the relevant part of the post. Quoting all of a long OP just makes the thread messy and unreadable.
[Amazon Fire Phone] Eiermann78:
With KingRoot 4.1 i have some more files in /data/data-lib.

I wasn´t able to install KingRoot 4.0 anymore after a new reinstall of 4.6.1
[Amazon Fire Phone] najoor:
1- If the data-lib folder doesn't disappear after a reboot you can manually delete it. The presence or absence of it will not affect the operation of your system.

2- After a fresh install you should do a factory reset (wipe data and cache) in the recovery. If you still can't root with kingroot try it with the sim card removed and use WiFi.
[Amazon Fire Phone] Eiermann78:
Sorry for the misunderstanding i´ve caused. I was able to root it with KingRoot but not with Version 4.0, i had to use KingRoot 4.1 now instead.

I couldn´t even install V4.0 anymore. Before i always rooted it with KingRoot 4.0. I will test it with another Fire Phone at the end of the week again.

I´m pretty sure i made a full factory reset, but who knows :)
[Amazon Fire Phone] najoor:
It is pretty strange that you couldn't even install the apk. What error message did you get? Did you use the one that is attached to the op? This morning I tested that on another device and it worked.

Keep in mind that sometimes malwares masquerade themselves as legit apks and when you try to install them it fails because the file is corrupt or incompatible.
[Amazon Fire Phone] Eiermann78:
The Error Message was: INSTALL_FAILED_DEXOPT

I tried it with the file, that is attached in the first thread and it worked with 4 other Phones before without any Problems.

Even downloaded it again, but there were no changes. I guesss, i didn´t really clean cache or made a full factory reset or something.

I will test it with the next phone again.
[Amazon Fire Phone] mazay2:
On 4 step:

user unallowed: Operation not permitted

What is problem?
[Amazon Fire Phone] najoor:
After you type su in the adb window look at your phone and you will see that kinguser is prompting you to allow root access for the adb shell. If you miss that and you don't grant access, it will time out and the commands that follow will not execute. This has been mentioned in the OP.
[Amazon Fire Phone] mazay2:
Thank you very much!
[Amazon Fire Phone] TheMightyFid:
4.6.1 UK - Not appearing to work

Couldnt get this method to work on the UK version of the OS - Kingroot installs (along with its other rubbish), daemonsu', and I tell it to remove root. Kinguser removed and the other two gone, I can busybox "busybox chattr -ia /system/xbin/ku.sud" and "busybox chattr -ia /system/xbin/supolicy", but it then fails while trying to remove one or the other. rm attempts it but reports back the error "Operation not Allowed".

Any attempts to further install SuperSU end in failure with SuperSU unable to update its binaries.

I have also attempted Wolfdroid's script from both the adb and on phone terminal, with no success. (factory reset each time to prevent Kingroot from staying installed)
[Amazon Fire Phone] najoor:
When the system reports "Operation not allowed" it means that the "chattr" commands did not run successfully, and that in turn means that at the time you ran them you did not have root privileges. So most likely, when you ran daemonsu it did not start or it prematurely stopped. Check your procedure there.
[Amazon Fire Phone] TheMightyFid:
Note - Just tested this with the US unlocked version, and this worked just fine. But trying again on the O2 UK version and it failed.