yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] NerdFire:
Hi, new user here just confirming that I renamed /system/priv-app/com.amazon.kindle.kso/ to com.amazon.kindle.kso.bak/ and that removed the lockscreen ads for me. I don't know why the folder should make a difference - maybe it just looks for anything named "com.amazon.kindle.kso" in that directory? Whatever it is, I'm glad it's working.

Now if I could just get my Nova launcher to accept widgets (trying to add a widget to a screen invariably takes me to the Settings page) and if I could change the lock screen images (no idea yet if that's possible) I'd be set. Thanks to Rootjunky and Shadow_SD for your work on this!
[Fire Android Development] sd_shadow:
did you move Nova to /system?
[Fire Android Development] NerdFire:
My friend Link2SD said I didn't, so I moved it and rebooted and now the widgets are at least accessible! Thanks!
[Fire Android Development] rzap:
Do you physically have to move or can you use Titanium Backup and make it a system app?
[Fire Android Development] Tomsgt:
titan should work to make it a system app
[Fire Android Development] sd_shadow:
titanium Backup should be fine
[Fire Android Development] rzap:
Thanks, hadn't used Nova because of no widgets, didn't know making system app fixed all that!!

---------- Post added at 04:45 PM ---------- Previous post was at 04:43 PM ----------

Thanks, will make changes when I get home.
[Fire Android Development] jco23:
trying this now on my 5.1.2 device, but kingroot keeps saying unsuccessful. the percentage varies between reboots (mostly 17% before rebooting). After rebooting, should I open kingroot again or do something else? i presume a lockscreen password would not prevent any of these scripts, right?

thanks!
[Fire Android Development] Robo-rooter:
If KingRoot fails to root, retry. (If anyone hasn't used KingRoot before, slide up the 2 blue screens and click "Try It", then click "Root". If if fails a small Retry button will appear at the bottom of the screen.) If it reboots the tablet, open KingRoot again and rerun as many times as necessary (it took one of my Fire 7's 3 reboots and 4 KingRoot tries before it rooted). KingRoot seems to make a little more progress with each try. It will get to a higher percentage before failing. Finally it seems to make a breakthrough and quickly goes to 100% and announces that the device is rooted.

While running KingRoot, don't touch the PC until the tablet is rooted. Once KingRoot says it's rooted, press ENTER on your PC to continue the SuperTool batch file, you don't have to exit KingRoot at that point. The SuperTool script will close KingRoot and remove it from the tablet..
[Fire Android Development] Tomsgt:
can someone with lock screen ads not being disabled please test the new script i just updated it. My device is removing ads just fine but i just edited the script to take a little more extreme measures this time. please report back thanks.
[Fire Android Development] rzap:
No joy!!! Used Titanium Backup to change Nova to system app, rebooted, long pressed home screen to get widgets, pick one to apply and still go to settings!
[Fire Android Development] sd_shadow:
it was reported to work on 5.0.X
[Fire Android Development] Robo-rooter:
Same here. My Fire 7 has firmware version 5.1.2. Just rooted it a couple of days ago with the latest SuperTool. Also installed the Nova launcher.

Bought a fresh copy of Titanium Backup Pro from the Google Play store today and converted Nova launcher to a system app. It still does the same thing. After a widget is dropped on the home screen the tablet goes to the Setup menu instead of popping up a permission window to add the widget.
[Fire Android Development] rzap:
So I've been using Go Launcher and Go widgets. Hate that because I'm limited to their widgets.
[Fire Android Development] drob77777:
So I have been trying out the latest tool to root my 5.1.2 and I get king root installed... the device reboots and finally shows successful root attempts but after hitting spacebar supersu is never installed. I'm wondering if it could be because I ran the auto update on the tool instead of downloading it fresh?

press a key to contine

[*] installing Kingroot app now 5329 KB/s (9087279 bytes in 1.665s)

pkg: /data/local/tmp/Kingroot.apk

Success [*] app installed --------------------------------------------------------------------------------

[*] open kingroot app on the Amazon Fire tablet then try and get root

[*] access. The device may reboot and try a couple times.

[*] If it fails just reboot the device then open kingroot and try again. [*] press and key to remove kingroot and install supersu once

[*] kingroot has working root access.

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

[*] pushing files to the device

cannot stat 'apps\mrw': No such file or directory

[*] please grant root access on your device to ADB shell

sh: /sdcard/mrw/root.sh: No such file or directory

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

[*] once supersu app opens click conitnue

[*] then click normal

[*] and finally click ok

[*] last click no thanks and you have supersu install

[*] close supersu app and uninstall any kingroot or purify apps

[*] left on the device.
[Fire Android Development] Tomsgt:
yeah you need to download again. I had to change something a couple weeks ago to make the option 9 fully work and you didnt get that fix.

a new download form the site will fix that
[Fire Android Development] Robert121571:
I have two questions.

I'm got ting one of these Amazon tablets to mess with and use the super tools on. Here are my questions. Both are after I've rooted the device.

1. If I wanted to do a full reset on the tablet dose it return to like it was from factory? As in it restore back to before rooted and will be a normal Amazon Fire tablet.

2. If I set it all up rooted and all. Is it possible to unregistered it from my account and allow a new user with out re rooting again? O

The reason I'm asking is I got a friend who may want one but he has no access to computer so I would have to set up the root for him which means I would have to activate it on my Amazon account to get it going to root. Then let him play with it to see if he wants one.
[Fire Android Development] DB126:
- the basic reset offered by Amazon does not restore the device to 'fresh out of the box' state; a reload of FireOS via the stock recovery menu is required

- I believe root will survive re-registering the device; do a simple test with your own account to verify
[Fire Android Development] Robert121571:
Ok I'm just trying to figure out best way to do it to avoid making several trips to my my friend after I let him mess with the tablet I'm getting later this week and he says he want one. Didn't know if I can just change owner on the one I let him play with or if I'll need to have him register a fresh one and I take it home do the root and take it back. He can't do the rooting and stuff since he has no computer and not quite as savvy as I ame with messing with that stuff.
[Fire Android Development] Robo-rooter:
Amazon is currently selling some returned/open box Fire 7's for $28 to $30. I bought 3 about 2 weeks ago and they all are in perfect condition and work great. I rooted all 3. They come with firmware version 5.1.1. They come in a plain brown box. Just a shrink wrapped Fire 7 with the data cable and wall charger. No original packaging or printed material is included. There is no 90 day warranty. Amazon would take it back if it doesn't work out of the box. I would not hesitate to buy another one if I needed it. The screens are perfect. The back case may have a slight rub that you can hardly see.

Go to the Amazon main page. Click on TODAY'S DEALS, then click on OPEN BOX & USED.

This will take you to the WAREHOUSE DEALS department where Amazon sells its returns, open and damaged box and one of a kind stuff. The stuff usually comes with a warranty and is eligible for Prime shipping.

In the WAREHOUSE DEALS department search for FIRE 7 TABLET.

There are currently 2 on sale for $28 and $30. More are added all the time, lately.
[Fire Android Development] sandman512:
Ok, trying to flash the latest build of CM via the Supertool and got this error(fwiw, never had an error before).

error: unknown host service

error: unknown host service

Cannot load TWRP.........................IMG

EDIT: Downloaded latest supertool and worked . Thanks!
[Fire Android Development] jco23:
thanks again [MENTION=4246643]Tomsgt[/MENTION], I was able to apply the root using the tool and your video. I also renamed the stock launcher to .bak (making sure that Google Now Launcher was already installed first), rebooted, and then back to good ol' root normal.
[Fire Android Development] rzap:
Ok, just to make sure, you flashed twrp onto your fire hd using the super tool?
[Fire Android Development] sandman512:
[MENTION=4946460]rzap[/MENTION], Yes, I used the supertool to boot into TWRP, then flashed the latest build of CM. Thanks!

EDIT: I had to use the latest version of Supertool, the older one gave me the errors as seen in my previous post.
[Fire Android Development] Sumaech:
Root will not work for 5.1.2, what do I do?

Thanks,
[Fire Android Development] rzap:
ok, thanks, that would be option #4 on the super tool, correct?
[Fire Android Development] bbstucki:
Hi Sumaech, root junky released a new video on rooting 5.1.2. Here is a link:

https://youtu.be/LfxfZkI_l4I

It works.
[Fire Android Development] sandman512:
I believe so, it was the option to boot into TWRP. I'll check and confirm when I get home.
[Fire Android Development] Sumaech:
Thankyou!

---------- Post added at 02:12 PM ---------- Previous post was at 01:33 PM ----------

How do I get xposed on 5.1.2? Does this script work for it?

Thanks,
[Fire Android Development] DB126:
Xposed framework for Lollipop and above must be flashed. Don't know if the script handles it; might have to use a tool like FlashFire.
[Fire Android Development] rzap:
It's option 5 to install xposed on the super tool.
[Fire Android Development] Chewieez:
Couple questions about starting root process on 5.0.1

I just received my replacement Fire 7 and it has 5.0.1 on it right now! (woot) I'm reading up on how to get root and first off, block OTA, then eventually run TWRP and install either SlimLP or Nexus. I have a couple questions and I'd like to wait to start until I have a firm grasp on everything I need to do so I do not accidentally get updated to 5.1.1 or 5.1.2.

I'm on a Mac and would love to use the Super Tool script for Mac if possible. I see it uses KingRoot to gain root and that KingRoot requires me to turn on Wifi. If I connect to wifi to run Kingroot, is there a chance my tablet will update itself to 5.1.2? Is there a better method to gain root with the 5.0.1? I have access to an older Windows XP system, which is what I used to root my first Fire so I can use that if I absolutely have to. I'd prefer not to as it took me quite a while to get the drivers working so it would recognize the tablet with ADB composite and that stuff seems to work better when I use my Mac.

I'm wondering if I could use the Mac script and choose "Block OTA" first, before I choose to Root. Is that an option? Or should I just go to the older thread about rooting 5.0.1 and follow those steps on my Windows XP?

Thanks!!!!!
[Fire Android Development] platypoid:
Root Junky has a video on Youtube how to do the root on different versions . His tool should be able to do the job on 5.0.1 . I wouldn't connect to any wifi until you use the tool and root it , disable the OTA , and whatever else you would like to get done.
[Fire Android Development] m00head:
If you use the Windows version of the SuperTool script (1-Amazon-Fire-5th-gen.bat), you can install the ADB and Fastboot drivers and test them by selecting option 1. It also lets you root version 5.0.1 without using KingRoot by selecting option 6:

https://www.youtube.com/watch?v=sVv1D_LNLTg
[Fire Android Development] koda1789:
I was able to root, blocked OTA updates, install the play store and remove lockscreen ads.

Everything was running fine for a day but then it shut off, rebooted and said optimizing system storage and applications.

It ran through the optimization and now is stuck in a boot loop. Reboots, shows the lockscreen and then goes back to the fire logo.

I didn't install TWRP.

Any ideas?
[Fire Android Development] Tomsgt:
not sure why that happened but you should be able to fix it by ADB sideloading the stock amazon firmware
[Fire Android Development] sd_shadow:
twrp cannot be installed
[Fire Android Development] koda1789:
Was able to get into fastboot and factory reset, seems to be good now.
[Fire Android Development] Chewieez:
Alright I believe I am good to go on my replacement Kindle Fire 7 running 5.0.1 bootloader. I finally got the driver situation worked out again on my XP machine (I never get why it takes me so long to do this. :o\) I rooted and have SU and I ran 3. Block OTA. I was wondering how I could confirm that the Block OTA worked before I turn on Wifi. I went to settings and tapped "System Updates" and it gave me an error stating that "The requested action is not permitted. Check Parental Controls settings and retry." Am I correct to assume that message means that the Block OTA script worked and I'm safe to get on wifi?

Another question, if I load a custom rom such as Nexus or SlimLP, do I have to worry at all about blocking OTA updates? I'm assuming No and I'd only need to worry when I'm running FireOS. Is that correct?

Thank you very much for creating this SuperTool and for everyone providing such great support!
[Fire Android Development] Tomsgt:
you only have to worry about blocking ota updates on Fire OS not on a custom rom. It sounds like you have ota updates blocked on your device correctly. I have a feeling that Amazon has a way to turn back on disabled or hidden apps so that is a little concerning to me. I have changed the latest script to just fully delete the OTA updates on the device. I am hoping that this works better to protect Root access on these devices.

Good luck Rootjunky
[Fire Android Development] Robert121571:
Well got the fire today. Was able to root it on second try but the lock screen ads are still there. I used the tool to change to the nova launcher but how can I say use the google now launcher I download from google play. When I click the app it downloaded it say go to setting home but the fire don't have that in settings. Any help.
[Fire Android Development] bbstucki:
[YOUTUBE]https://youtu.be/ux-2b3X3BlI[/YOUTUBE] used this method on 5.1.1. On 5.1.2 it may cause a boot loop which needs a factory reset. I've also heard that 3rd party apps will switch your default launcher for you, but I had trouble with them even seeing the now launcher.
[Fire Android Development] girron:
This just happened to me too. The battery died, and now it will boot, show the lockscreen, show the fire logo and then every once and awhile will go back and start "Optimizing system storage and applications"
[Fire Android Development] Robert121571:
Just an update I retried that ad removal with the tool and this time ads are gone.
[Fire Android Development] dmbdd72:
Same story here...
[Fire Android Development] DB126:
Indication you may have received an (unwanted) OTA Update from Amazon. Another common cause are changes to system files or folders (delete/rename/permissions/etc). You should be able to restore your device by reloading FireOS from the stock recovery menu.

Info: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
[Fire Android Development] Tomsgt:
thanks for the report :)
[Fire Android Development] Robert121571:
Just a question is there a way possible that you could add an option to the tool so we can have it install a different launcher other than the one you currently have as a replacement. Say like I have the APK for the Google now launcher and there be a menus option to pick one we have.
[Fire Android Development] sd_shadow:
often google now doesn't work right away, takes a couple reboots, or something needs to update

you cannot do much without a working launcher

once stock launcher is gone, other launchers can be easily installed from playstore

a 2nd launcher won't be hard to add to the tool, but I wouldn't add Google Now
[Fire Android Development] Robert121571:
Ok I understand I'm supposed to be able to add another launcher once the I use the tool to install nova. The problem is after I download and install Google now from the play store along with the Google app. And I click on the icon for Google now lion her it tells me to go to settings home to set it. That problem no setting for that.

Oh well at least it something I can play with. I just mainly wanted something to goof with and maybe give to a friend. The 5)8!( is really too small for my bad eyes. The reason I post here from my iPad.
[Fire Android Development] sd_shadow:
exactly why it shouldn't be installed as the only launcher

uninstall the now launcher you have, download/install the oldest now launcher from

Apk mirror

http://www.apkmirror.com/
[Fire Android Development] 1storm976:
Just fyi I ran the script it took it off for a bit then came back... hope it helps I'm a little behind in this thread... ?
[Fire Android Development] ModusTrollens:
My Fire doesn't appear on either my mac or windows machine, I've tried installing drivers on windows to no avail and the tool doesn't find it on my mac either. I've been updated to 5.1.2 and everytime I plug into a computer it just tells me I'm connected to a "low power charger".
[Fire Android Development] wulfie66:
sounds like you haven't enabled developer options and usb debugging
[Fire Android Development] ModusTrollens:
I've done both unfortunately
[Fire Android Development] wulfie66:
use the usb cable that shipped with it, also try different usb ports, not a hub, or even a different pc
[Fire Android Development] ModusTrollens:
On my mac it comes up as low power charger and then the super tool can't find the device. I've tried the same cables/ports with my android phone and it is able to import photos etc.

On my PC it similarly comes up as low power charger but in the device manager it comes up as unverified device. None of my attempts to point it to the drivers included in any of the files have worked.
[Fire Android Development] m00head:
[MENTION=4246643]Tomsgt[/MENTION] I'm seeing the same issue with the website you encountered in your latest video here:

https://www.youtube.com/watch?v=LfxfZkI_l4I&t=2m8s

There is a long pause when using the first link to download the SuperTool, but mirror link starts downloading the SuperTool file instantly.
[Fire Android Development] Tomsgt:
yeah thats a problem with the script that runs the site. I have been meaning to change the hole site over to the mirror link but just havent pulled the trigger yet.
[Fire Android Development] hreffo:
Just want to chime in and I was also able to root my tablet (5.1.2)! Thanks for your app and all the helpful reply in this thread.

Using ggow's Nexus ROM and it's pretty good
[Fire Android Development] x13:
Use the ADB 15 Second Installer as an administrator, then follow the second video embedded there
[Fire Android Development] ModusTrollens:
I think I've used this app before but I'll try it again on my windows machine and try the video - thank a lot.

Is there something similar I need to do on my mac or should that work out the box?
[Fire Android Development] riverstyxxx:
How do I install flashfire 0.31, I cant find a file browser. The supertool only installs 0.30. I put the apk on the root of the internal storage (along with the gapps/cm installer zips). I've also changed it to nova launcher.
[Fire Android Development] Robo-rooter:
Here is how I installed FlashFire-v0.31 to my Fire 7 using Root Junky's SuperTool in Windows 10.

Open the SuperTool folder in Windows 10. Open the "apps" folder within the SuperTool folder.

Look for the "FlashFire-v0.30.apk" file and rename its extension ".bak".

Now copy the "FlashFire-v0.31.apk" file to the SuperTool "apps" folder.

Finally rename "FlashFire-v0.31.apk" file to "FlashFire-v0.30.apk".

When the SuperTool is run and installs FlashFire, it will install now FlashFire-v0.31 onto the Fire 7.
[Fire Android Development] bbstucki:
Flash fire is available in the google play store now. When you download from google play you get version 0.31.
[Fire Android Development] Robert121571:
If I do this. Is it possible to go back? Don't want to try anything that is one way since still not sure I'm going to keep the fire. Also is anything not working?
[Fire Android Development] Y314K:
Is the installation of the latest FlashFire recommended even on the Ford's that have the old FW that still allows TWRP to be booted from this SUPERTOOL or is it only recommended for devices without the TWRP option ?
[Fire Android Development] Robo-rooter:
So far, everything is working for me with the Nexus ROM. I wouldn't consider going back. Yes you can go back to the original Amazon firmware ROM. Don't attempt to go to an earlier Amazon firmware ROM than was originally on your Fire or it will be a permanent brick. (Example: If your Fire has firmware 5.1.2, don't attempt to load 5.1.1 or 5.01. That will cause a permanent bricking.)

---------- Post added at 02:34 PM ---------- Previous post was at 01:55 PM ----------

Personally, I've only worked with my Fire 7 that has firmware 5.1.2, so I don't have an answer to your question. Sorry. Hopefully someone else with more experience can answer your question.
[Fire Android Development] Robert121571:
Can you verify that apps can be put on the SD card. Reading the thread for that rom people say you can't move apps to the SD card at least not the normal way.
[Fire Android Development] Robo-rooter:
On the Fire 7, which has 8gb of internal storage, whether using the Amazon rom or the Nexus rom, there is only about 3.5gb of free storage BEFORE adding any apps. Link2sd basically recovered all of that available internal storage for me.

Link2sd is working on my Fire 7 with the Nexus rom . Link2sd links the apps to the sd card (it won't actually move them and run them from the sd card).

On the Nexus rom, Link2sd moves a portion or all of an app to the sd card and somehow virtually links it back to the internal storage on the android system, running it from there. I only linked apps that I had installed, just to be on the safe side. Link2sd offers to link android system apps to the sd card, but I didn't want to go there, out of an abundance of caution.

Anyway, the end result is before loading LInk2sd I had about 500mb free of internal storage after adding about 100 apps . Now, I have 3.5gb free of internal storage thanks to Link2sd.

My 32gb external sd card is partitioned into 2 partitions. A 14gb fat32 partition and a 14gb ext4 partition. Link2sd uses the ext4 partition for linking the installed apps. The Fire 7 will accept up to a 128gb external sd card. There is about 11gb of the original 14gb free on the ext4 partition of the external sd card. So I can add a couple hundred more apps if desired.

The fat32 partition of the external sd card is for normal use like storing videos, photos, mp3's, e-books, etc. Link2sd sees and uses the ext4 partition of the sd card. The normal android system sees the fat32 partition of the sd card and uses that for normal file storage (videos, photos, mp3's, e-books, etc, etc).

My Dell laptop is set up to dual boot Windows 10 and Linux Mint. Both operating systems have been helpful to root, install the rom and prepare the sd card for the Fire 7. You can download a Windows program to partition the sd card into the fat32 and ext4 partitions. Since I have Linux Mint, I used its Gparted partitioning program to partition the sd card.

The laptop has a normal size sd card slot, which along with an sd adapter allows the micro sd card to be inserted into the laptop for partitioning, formatting, loading files, etc.
[Fire Android Development] Robert121571:
Yea that what I was getting at you have to use and add on for SD SD card instead of using the built in android settings to move an app to SD.