yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] CamiloMed:
I make it!

Hi /bros i can root easy and fast.. It's true kingroot first and dont try supersume because don't work, hide access to su or freeze the process, you only need root with kingroot first (i make it 2 try), restart and make click to the first search (sorry i can't put external links)... Follow the instructions

Google it : Kingroot su

And select first option, you need install terminal and download the zip....

Restart after install and enjoy super su and say goodbye to kingroot...

Unistall first su if you have it before!
[Fire Android Development] BTSchuster:
This morning, lock screen ads came back on my Fire running 5.1.2.. I reran the SuperTool and chose remove lock screen ads. It looked like everything went as intended, but once my Fire rebooted, there were lock screen ads again.

---------- Post added at 08:43 PM ---------- Previous post was at 07:48 PM ----------

The instructions here http://xdaforums.com/showpost.php?p=66062233&postcount=555 worked great! Thanks CamiloMed!
[Fire Android Development] zerozed99:
I have run Kingroot at least 6 times and continually get "ROOT FAIL." Is anyone actually able to root with this method?

EDIT: I have got it rooted. LINK to details.
[Fire Android Development] DB126:
Local or desktop version? Later is said to be more robust but requires usb tether.
[Fire Android Development] zerozed99:
I've run both. I'm still running them. I'm convinced that it is an urban legend that this method works.

EDIT: I have got it rooted. LINK to details.
[Fire Android Development] DB126:
Possible, but there have been enough success stories to suggest it works for some. See here.
[Fire Android Development] Stonebot:
You should go to Aldi's. They have a really nice budget tablet with better specs. Standard Android.
[Fire Android Development] BTSchuster:
I have successfully rooted my Fire running 5.1.2 using KingRoot. Here are the steps I followed:

1) Run Windows version of KingRoot from http://www.kingroot.net. Tool said root successful, but rootchecker said root did not exist on device.

2) Install and run KingRoot apk from here http://xdaforums.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461. Root showed as successful and verified by rootchecker.

3) Follow steps here http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html to remove KingRoot and install SuperSu.

It does seem that ymmv, but this may help those who are trying to figure out how to root their Fire with 5.1.2.
[Fire Android Development] DB126:
I snagged a couple of those (MEDION LIFETAB® P7332) over the holidays. Excited at first as specs seemed better....and some were (resolution, weight, etc). Reality was a different story. Screen did not render colors well. Atom processor lagged on all but simple tasks. Battery life was unimpressive. Wanted to make them work but in the end I returned both in favor of 2015 Fire which I was testing concurrently. Ability to root and install custom ROMs sealed the deal.
[Fire Android Development] Stonebot:
Interesting, most of the reviews were positive over the fire, accept for battery.
[Fire Android Development] GladOSkar:
As I posted yesterday, for me it worked with KingRoot app version 4.5.0, and on one tablet it only worked on about the 10th try. Keep trying! And please report back :)

-Oskar
[Fire Android Development] GladOSkar:
Apparently, when I tried Super-SUme I broke my Kingroot installation.

I can neither open it nor can other apps request root access, though KingRoot does still appear in the App list. When I reinstall it the "open" button is greyed out and KingRoot won't show up in any app drawer.

So the solution that you found now probably won't work for me.

After installing SuperSU manually it tries to update its binaries for like forever.

Also, since trying Super-SUme, a weird error message shows up irregularily (maybe whenever something tries to do something rooty in the background?)

Translated it says something like "The requested action is not permitted. Check your child protection settings and try again".
[Fire Android Development] zerozed99:
I got it to work. Thank you. I tried it again this morning and was able to achieve root the first time. I uninstalled the versions of King Root I had been using last night and replaced them with ones from BTSchuster's links. I believe the download link for the android app from XDA is what made the difference, as I had downloaded the app from King Root's website previously. I first ran the Windows app (which is in Chinese) and (like last night) it rebooted my tablet at ~18%--beyond that I don't know whether it claimed to be rooted or not (the text was green but in Chinese). RootChecker said it was NOT rooted after running the Windows version of King Root. I then ran the android app that [MENTION=775320]BTSchuster[/MENTION] links to (and which is in English) and that after that completed it said I was rooted. I ran RootChecker and it validated that I was. I then downloaded the files from the W0lfdroid link, copied the MRW folder over to my tablet, and ran the Terminal commands (from the tablet) and it worked. Running the script deletes King Root and installs SuperSu. After you run the script it prompts you to update the SuperSu binaries and reboot, which I did. After this, I ran RootChecker again and it failed. I then went and opened SuperSu and was automatically prompted to grant permissions for Root Checker--once I did this, Root Checker validated my root status.

The only other thing different between my attempts last night and this morning was that my tablet had ~50% battery last night and was fully charged this morning. I can't think of a reason why this might have made a difference, but I'm throwing it out there.

TLDR: This method seems to work, however be sure you grab the files from [MENTION=775320]BTSchuster[/MENTION]'s links and not from other sources.
[Fire Android Development] zerbey:
Rooting with KingRoot worked with the Windows version, no need to use the APK at all it just worked. The SuperSU step broke the root so I had to redo it with KingRoot. So, I have root but not SuperSU.
[Fire Android Development] richiec427:
Great stuff. you explain things perfectly. easy to follow.

I am having an issue, I have a Amazon Fire 7 . I watched your videos, and the first time I tried, I was able to get the message on the fire , that I was connected to pc, media mode.. I was unable to root device, becuase of drivers, and not finding the device.

So I removed everything from pc, and factory restarted fire 7. Now I cant get the device to show connected ,no message on fire, and cant get it show in device manager .

Im using windows 7, usb 3.0 connection and factory cable that cam with device, I have adb de-bugging turned on .

any ideas?

thanks for your info.
[Fire Android Development] platypoid:
Try going to Device Manager in Windows , plug in your Fire, and look for it in the lists to make sure the correct drivers are installed. You may have to uninstall whatever driver is in there and reinstall the correct one. Windows can be a bit of pain sometimes and keep trying to automatically re-install a different driver other than the one you want.
[Fire Android Development] bbstucki:
I was able to use Kingroot apk. I found a comment where the user said he had used Kingroot 4.5 apk and rooted two fire tabs on 5.1.2. He said one took 2 tries to root, the other took 10. I was skeptical that a repeated effort would do the trick. But I installed the lastest version 4.8.x and after the 3rd retry, I got root back. I like chainfire supersu better, but in the mean time, I was able to use my file browser (with root privileges) to re-delete the lockscreen ads and remove fire launcher to use Now launcher again. To manually remove those, go to:

system> priv-app

remove the two folders entitled:

com.amazon.kindle.kso (kindle special offers)

com.amazon.firelauncher

I copied these folders to my sd card as a backup first. Also, be sure you have an alternate launcher like Google Now or Nova launcher before removing the firelauncher folder.

If you want to use Google Now, it has to be the only launcher available and it will make itself the default. Reboot your fire 5th gen and you will have the new launcher as your default and the ads will be gone.

Also, do yourself a favor and download the "Disable Service" app from Google play. Give it root access and you can turn off system updates to prevent further fiascoes. I did this on my kids fire tab and they are still on fire 5.1.1 with root, google play and all the other goodies on the supertool.
[Fire Android Development] zerozed99:
Just FYI--I run Google Now along side the Fire Launcher. You are correct that in that (as far as I've been able to determine) it is impossible to set it as the default as long as Fire Launcher is installed, however I just use a Launcher switcher app that allows me to jump back and forth between the two--so you can (technically speaking) run Google Now Launcher even if you use Fire Launcher--you just can't set it as default. I actually prefer this setup as I like using Fire Launcher when I want to do Amazon-specific stuff, but switch over to Google Now when I'm doing "normal" Android stuff. Obviously this isn't an ideal setup IF you don't want to ever use Fire Launcher, but for me it works great.
[Fire Android Development] fguzmant:
Thanks, for me it worked on the 7th try in 5.1.2.

I have an issue, after all the process I'm not able to add widgets to Nova Launcher, it always take me to te configuration screen; anyone knows what could it be?.

Another question, using "Disable Service" app, what system service should I block? (I found Dynamic Updation Service).

Thanks
[Fire Android Development] XmanORE:
Is there a version in English?
[Fire Android Development] rzap:
The only launcher I found to use widgets is Go launcher but you can only use go widgets. All other launchers just send you to settings.
[Fire Android Development] zerozed99:
Google Now Launcher handles widgets on the Fire tablet with no problem.
[Fire Android Development] rzap:
Great!! Will have to try it, thanks
[Fire Android Development] DB126:
Great app, as is "My Android Tools" by the same author. Be aware disabled and/or hidden services can easily be reenabled. Amazon properties are notorious for this behavior but are far from the only guilty party. Pretty easy for an app to look for a disabled service and reenable it. Best defense (historically) is to rename the apks responsible for administering the OTA update process.
[Fire Android Development] bbstucki:
That's what I disabled on my kids fire tab and it hasn't updated.
[Fire Android Development] zerbey:
No, but it's pretty easy to follow. It'll prompt you to root after it detects the phone.
[Fire Android Development] pappasmurfsharem:
I can't seem to get any PM commands to output anything

pm list packages
pm list users

etc...

EDIT: If I adb shell and don't switch to root I can list the packages fine... That's interesting...

If I goto

Settings > Apps & Games

then clear the default I get prompted for my Google Now Launcher and ADW Ex again.

Can't seem to "enable" or "unhide" the firelauncher though
[Fire Android Development] jbraney:
Hold on... After my third reboot, taking the SD card out and putting it back in, and waiting about 10 minutes, everything showed up... I don't know what it was, but it's fine now. Now I just need to find out if Xposed will work.
[Fire Android Development] Tomsgt:
awesome good news thanks. SuperTool updated to block ota update on 5.1.1 option 4 now
[Fire Android Development] jbraney:
Cool.

Hey man, as a personal favor, could you look into my Xposed question from the previous page. And if Xposed can't be installed atm, is there a way with root to set app, video, musice, etc. downloads to go to the SD card by DEFAULT, so that I'm not running out of storage space every time an app updates and I have to move everything back to the SD card? Very annoying, and I can't begin to describe how thankful I would be if you could find a way to fix that!
[Fire Android Development] DoLooper:
Not usually pushy, so this is strictly FWIW. :)

What I did to in my script to get Nova going without deleting firelauncher:

Echo. &Echo Starting custom launcher and disabling stock . . .

adb shell am start -n /com.android.launcher2.Launcher
adb shell pm disable com.amazon.firelauncher

(needs a reboot)

EDIT: Sorry, but this was for OS 5.0.1 so of course it couldn't work, as kindly confirmed by [MENTION=834366]pappasmurfsharem[/MENTION].
[Fire Android Development] Tomsgt:
I will look into it if i have some time but i would guess that you could use flash fire to install it
[Fire Android Development] pappasmurfsharem:
See if you can re-enable the launcher...

It wont let me for whatever reason.

running as shell comes out as

C:\Users\<REDACTED>\Downloads\Amazon-Fire-5th-Gen-SuperTool>adb shell pm enable com.amazon.firelauncher
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9079, uid=2000, package uid=32061

Running as root just hangs.
[Fire Android Development] revdirty:
Ok after trying the block OTA on this 5.1.1 i got this:

[*] grant root access on your device to adb shell

Package com.amazon.otaverifier new state: disabled

Package com.amazon.device.software.ota new state: disabled

Package com.amazon.settings.systemupdates new state: disabled

--------------------------------------------------------------------------------

[*] OTA update have now been unblocked

[*] and amazon can now auto update your device.

--------------------------------------------------------------------------------

Press any key to continue . . .

This seems weird.. IF they are disabled , why does it say its now "unblocked"?
[Fire Android Development] pappasmurfsharem:
Thats just a TYPO in the script

It looks like thats where he used to have UNBLOCK OTA as that option doesn't exist in the "latest" script

Its "echoing" a static text string, so until he edits it will always say that.

You should be good though.

echo.--------------------------------------------------------------------------------
echo [*] OTA update have now been unblocked
echo [*] and amazon can now auto update your device.
echo.--------------------------------------------------------------------------------
[Fire Android Development] revdirty:
Thats what i thought, but i figured id double check and maybe bring that to light on his next revision, assuming he will anyway
[Fire Android Development] jbraney:
Thanks man... That's all I ask! I haven't used flash fire before... is it safe on 5.1.1?
[Fire Android Development] pappasmurfsharem:
I don't think anyones tried.

I'm a bit scared myself, was thinking about trying to flash CM12.1 and seeing how it worked out.

But I don't really want to have to go through the return process.
[Fire Android Development] DoLooper:
Sorry, I can't test yet. I think this might do it if you'd kindly give it a try:

adb -d shell "su -c 'pm disable com.amazon.firelauncher'"
adb -d shell "su -c 'am start -n /com.android.launcher2.Launcher'"

(reboot)

If that works, switch back to Amazon UI with this:

adb -d shell "su -c 'pm enable com.amazon.firelauncher'"
adb -d shell "su -c 'am start -n com.amazon.firelauncher/.Launcher'"
[Fire Android Development] revdirty:
What is Flash Fire, i couldn't find any info on this?
[Fire Android Development] pappasmurfsharem:
It appears to hang as normal, so if someone else can verify that it's not something specific to my setup, that would probably be best.
[Fire Android Development] Tomsgt:
yeah just a typo lol will fix it soon
[Fire Android Development] Tomsgt:
I will do it i have used flash fire on other devices and it works great :)
[Fire Android Development] pappasmurfsharem:
Keep me posted. I want dat CM12.1 WOOOOOO
[Fire Android Development] jbraney:
Yeah, CM 12.1 is the biggest thing I want, equal to Xposed. With one of you guys working on each, that is most effective. Be careful though, none of us want bricked tablets! And I hate seeing our hard working devs have that sort of pain... :P
[Fire Android Development] Tomsgt:
just tried flashfire and it failed to install cm12 it say there was a problem with the cm12.zip I will have to see if i can get a log. the device is rebooting now. looks like the Gapp and supersu.zip i flashed worked.
[Fire Android Development] jonathanmoneill:
When I tried to access the Windows version of Kingroot I got the message "You do not have permission to access this page". Any alternative links / suggestions would be much appreciated :)

Edit: I got this to work just installing directly on the Kindle but wondered what's the rationale for removing Kingroot and installing SuperSU?
[Fire Android Development] DB126:
Kingroot installs its own access manager (along with a few other goodies) which allows/denies root access to individual apps. Some people prefer SuperSU which has a long track record and respected developer. If you intend to flash a custom rom FlashFire and Kingroot do not play well together. FlashFire and SuperSU are written/supported by the same developer.
[Fire Android Development] jonathanmoneill:
That's helpful thank you :o Just to confirm though if I were to use SuperSu would that mean granting root access to all apps? I know that's less secure but it's certainly what I'd prefer at this stage.
[Fire Android Development] DB126:
By default SuperSU prompts for access the first time an app needs root access. It remembers you choice and only reprompts if the app is significantly changed. All this can be configured within the app. I would advise against granting all apps blanket root access. Not so much for security (although that's a concern for some) but the mayhem that can be created by a misbehaving apps w/root access. Akin to giving a Glock to a monkey.

Manually switching from Kinguser to SuperSU is not for the faint of heart. Suggest investing in Super-Sume with automates the process. You'll find it in the Play Store.
[Fire Android Development] jonathanmoneill:
I was going to try the manual switch outlined here but I wimped out and bout Super-Sume Pro, worked spot on and all looking good at my end. Thanks again for the advice :D
[Fire Android Development] zerozed99:
Although you purchased Super-Sume, I'd just like the larger crowd to know that the manual method of switching over to SuperSu really is easy. All you do is download a zipped file, unzip it (it has a folder with a few files inside), copy it to your Fire, and run a simple command from the Terminal Emulator app on your device. It is extremely easy and will save you the 3 or 4 bucks that Super-Sume costs. Which isn't to say that Super-Sume isn't good--but if you're savvy enough to root your device, etc., there's really no reason you can't use the free method.
[Fire Android Development] DB126:
Yup - good to have choices! Probably both methods should be included in the 5.1.2 root thread or referenced on one of [MENTION=4267571]sd_shadow[/MENTION]'s excellent guides.
[Fire Android Development] Tomsgt:
supertool has been updated to Fire OS 5.1.2 all options work again and i have taken further steps to stop ota updates. to get the latest files run the update option 9 twice or just download the new Supertool from the link in the OP
[Fire Android Development] rzap:
Thank you very much for the update!!! Time to go root the fire hd!!
[Fire Android Development] ytsejam1138:
Awesome news on the 5.1.2 Supertool update. So I'm currently on 5.1.1, rooted, OTA updates blocked, ads blocked, etc. via this Supertool. How would I go about unblocking the OTA updates so I can upgrade to 5.1.2 and then use the Supertool to root and reblock updates?
[Fire Android Development] ndg_2000:
Sorry to ask a dum question but does this mean that TWRP can be accessed via the tool after 5.1.2 update mine currently has cm12 on it but I would like to have the ability to go back to stock & if possible to switch back and forth thanks
[Fire Android Development] sd_shadow:
no twrp only is compatible with system versions 5.0.x
[Fire Android Development] ndg_2000:
mmm ok thanks will stay as I am then
[Fire Android Development] tigerbenzin01:
I 'd be interested in an answer to that question as well...
[Fire Android Development] bbstucki:
This may be a dumb question, but why can't we install TWRP or CM Recovery on 5.1.1 and up? I've read that if you have TWRP on 5.0.1, you can update to 5.1.2 and keep the custom recovery. What prevents me from booting a custom recovery on the updated OS?
[Fire Android Development] spydermahn:
Unfortunately site appears to be down.....any chance of an alternative link?
[Fire Android Development] sd_shadow:
downloads fine for me
[Fire Android Development] spydermahn:
Yeah has worked now.... Was going to cloud fare since last night.
[Fire Android Development] Tomsgt:
if you ever need it you can always download HERE also
[Fire Android Development] Tomsgt:
on Fire OS 5.1.1 and up the bootloader has changed and the feature that let us boot twrp and CWM recovery has been removed by Amazon. I have seen a process that you can update to 5.1.2 without updating the bootloader and keep the boot to recovery feature working but i havent researched it myself.
[Fire Android Development] Tomsgt:
just update tool again this time adding Xposed framework install to option 5 check it out.
[Fire Android Development] Oez58:
First of all thanks for your efforts, awesome tool.

With the latest version I can't start flashfire.

Tool is installing it but as soon as I start it close immediately
[Fire Android Development] duckmandm:
New Supertool for 5.1.2

Root Junky does it again! Time to fix the kindle, Thanks again for all you do RJ!
[Fire Android Development] kgirlx:
Can anyone answer this, I'm in the same situation as this. Thanks
[Fire Android Development] girron:
On 5.1.2 and I have updated SuperTool twice, but the removal of ads isn't working for me.
[Fire Android Development] bbstucki:
You can manually remove ads with root. Use ES file explorer or similar rooted file browser and navigate to /system/priv-aps/ and delete the folder called com.Amazon.Kindle.kso (kso=Kindle special offers) then reboot.
[Fire Android Development] Tomsgt:
yeah sorry about that seems to be a problem with the older flashfire app and the script. I update flash fire to .3.0 and it should be working now just update the Supertool
[Fire Android Development] Tomsgt:
the supertool removes ads by renaming /system/priv-aps/com.Amazon.Kindle.kso/com.Amazon.Kindle.kso.apk to com.Amazon.Kindle.kso.bak I has work 100% in my testing
[Fire Android Development] DB126:
There's a more elegant, reversible and safer way to accomplish this simple task: rename a single apk. Deleting stuff is just asking for trouble if you make a mistake. Many a brick has started with the 'delete key. Look back a few posts for details.

Edit: Might have to rename a folder too; see here
[Fire Android Development] girron:
This is what I get

When I use ES and navigate to the directory, the apk has been successfully renamed, but I am still seeing ads on the lockscreen.

EDIT: I just renamed the folder and added .bak as well and rebooted. Seems to have solved my issue.
[Fire Android Development] Tomsgt:
interesting the folder shouldnt have to be renamed but maybe more people can report on this one.

I can always have the script rename the holder to .bak also thats simple enough
[Fire Android Development] OnlySomeDood:
Great app, it works perfectly. I noticed a couple minor spelling errors that quite frankly bugged the crap out of me so I fixed them. I didn't see a source posted so I created a gist HERE

In one spot it said debice instead of device and in another it said mornal instead of normal.
[Fire Android Development] platypoid:
Should this line say ANY instead of AND ?

echo "[*] press and key to remove kingroot and install supersu once"
[Fire Android Development] OnlySomeDood:
and updated
[Fire Android Development] Tomsgt:
o **** LOL those are some bad ones LOL

edit ok I fixed those spelling problems