yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] glorifyday:
Hi everybody ;).

Big thanks for this great tool, Tomsgt :good:.

My device was bought in the end of 2015 and now shows the firmware revision 5.1.2, but I suspect that it might be 5.1.2.1, actually.

I am going to use the SuperTool, but before I start, I would like to ask a few questions.

A. Are all changes made by the SuperTool easy to reverse and return to stock look and behaviour?

B. Is there a way to ensure which firmware version I have (5.1.2 or 5.1.2.1) before I start?

C. Which points from the quoted list work with the 5.1.2.1 firmware?

D. If I downgrade do 5.1.2, is there any preferred method of blocking OTA in the meantime before and while using the SuperTool? WiFi off / WiFi set up skipped / airplane mode?

I am interested mainly in points 1, 2, 3, 7, 8 and 9. I might live without the root access.

If I happen to have 5.1.2.1, can I go on without downgrading to 5.1.2?

Thanks in advance for all your help.

Glorifyday.
[Fire Android Development] glorifyday:
Thanks a lot for this info, Fahrenheit17:good:.

I will have to think it over how to block the OTA servers inside my LAN, then.
[Fire Android Development] DB126:
Unlikely OTA update will stream in during the brief period a network connection is enabled while Kingroot is active. If one starts a reboot will delete the partially downloaded file. No need to over think procedure.
[Fire Android Development] fmc000:
Exactly. In my case I left the Wi-Fi always on and simply did not register the Fire with my wlan during the first boot. Just a few seconds before starting Kingroot I configured the network and all went fine.
[Fire Android Development] glorifyday:
Thanks guys, I might give it a try this way.
[Fire Android Development] ripteh1337:
Ok, so i think i have 5.1.2.1 installed, gets to 30 and errors out. Saw video on how to sideload a previous install but whenever using adb sideload command it states 'adb' is not recognized as an internal or external command operable program or batch file.
[Fire Android Development] m00head:
Are you using the SuperTool to install the ADB drivers? It will take care of installing them for you if you select option 1 and follow the instructions on screen.

If it still doesn't work then try this tool and choose 'y' when prompted 'Install ADB system-wide? (Y/N)':

[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3

http://xdaforums.com/showthread.php?p=48915118
[Fire Android Development] ripteh1337:
I did use the SuperTool to install the ADB drivers and ran the test and it did display my device. Then followed his video for sideload and typing in adb sideload update-kindle-global-37.5.4.2_user_542168620.bin in CMD Prompt C:\adb which is where the file is.

Installed the 15 second adb installer as well getting same message
[Fire Android Development] Tomsgt:
you have to install the drivers again while the device is in adb sideload mode
[Fire Android Development] ripteh1337:
Ok, tried that but still showing 'adb' is not recognized as an internal or external command, operable program or batch file.

If it helps it shows as Universal Series Bus Devices : Fire in Device Manager. When clicking update driver then browsing locally it just states the best driver is already installed
[Fire Android Development] fmc000:
You have to be sure that not only the drivers but also the "adb" program is installed on your PC. It's usually included with every tool that needs it, though.
[Fire Android Development] DB126:
- note which device entry(s) show up when Fire is connected

- uninstall those devices then disconnect Fire

- reboot both devices

- put Fire in desired mode

- open Device Manager in Windows

- teether device (direct; no hubs) and see what gets added

- above should provide some clues to help resolve the problem
[Fire Android Development] digthemlows:
I'm only looking to add the play store so I can use Google Music. So, I used this and added the store but I get an error when signing in to google saying "There was a problem communiating with Google servers. Try again later" and it doesn't seem like it's ever going to work? Any ideas? Brand new Fire, so it has the latest "amazon" android.......
[Fire Android Development] DB126:
- reboot; try again

- if problem persists consider a custom ROM

- Play Services (Store) on FireOS is always a sketchy proposition; good choice for those who enjoy troubleshooting and redos

Edit: Also see potential workaround posted by [MENTION=3092090]popoyaya[/MENTION] immediately following.
[Fire Android Development] popoyaya:
Can't sign in problem?

"turn on 2-step authentication. after doing that i happily came across the error “couldn’t sign in: to access your account you must sign in on the web. touch next to start browser sign in.” which i knew would work. case solved for my issue. hope this helps others."
[Fire Android Development] saiftheboss7:
I'm having error signing into Google Play. I successfully Installed Google Play from the script but when I try to log in, it says There was a problem communicating with Google servers, try again later

What to do?

thanks [MENTION=3092090]popoyaya[/MENTION] It worked!
[Fire Android Development] DB126:
Deleted (duplicate post).
[Fire Android Development] therock11:
I trying to root on Fire OS 5.1.2 and after it installs KingRoot I run and it fails at 30%. I've rebooted several times and it still fails.
[Fire Android Development] DB126:
This issue is well documented; a quick search would have revealed the answer:

- reload 5.1.2 via stock recovery menu

- on restart do not register device with Amazon

- retry kingroot; sometimes takes a few attempts
[Fire Android Development] therock11:
Do I need to actually reinstall the stock rom or can I just format the data/cache in recovery mode?
[Fire Android Development] DB126:
Must reinstall FireOS. See first few posts in this thread for guidance.
[Fire Android Development] alego500:
Just to be completely clear: I'm running 5.12 and have just gained root access.

Now, if I wanna flash a rom or backup the stock rom, then the only way to do it is through flashfire right? I can't just flash twrp even though it doesn't "stick" to the device and boot into recovery through fastboot every time I need it or what?

Thanks for the incredibly easy root process either way!
[Fire Android Development] DB126:
- twrp is not an option

- FlashFire must be used for most flash operations; recommend v0.32

- if root was obtained via Kingroot recommend swapping out Kinguser for SuperSU as the former can cause problems with FlashFire
[Fire Android Development] sd_shadow:
only option for Fires on 5.1.X to install a custom rom is FlashFire

twrp only works with Fires on 5.0.X
[Fire Android Development] popoyaya:
Can xposed be installed with flashfire?
[Fire Android Development] BRANDENDEUCE:
Yes
[Fire Android Development] popoyaya:
Xposed works ok on stock 5.1.2 rom rooted?
[Fire Android Development] DB126:
Xposed Framework - yes. Modules that mess with UI elements will be less successful.
[Fire Android Development] microbar:
Can my amazon fire 7 with firmware version 5.1.3 be rooted thanks.
[Fire Android Development] DB126:
Must rollback to 5.1.2. See below, third post.

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485/page12
[Fire Android Development] Signor Rossi:
The post you linked to, only shows how to unbrick, not how to downgrade.

As far as I saw it, you can't downgrade at all (apart from 5.1.2.x to 5.1.2) if you try to go from 5.1.3 to 5.1.2 you will surely brick your device

Gesendet von meinem OnePlus One

Edit :

LoL people should learn to link correctly. If you want to guide someone to the 3rd post, God damn link the God damn 3rd post lol.

Anyway this is the first time I see someone saying you can do this. So far I only read that if you do this, it will brick your device. But hey, I can be wrong [emoji41]
[Fire Android Development] fmc000:
Wrong. I downgraded from 5.1.3 to 5.1.2 and subsequently rooted and flashed the Nexus ROM without issues.
[Fire Android Development] Signor Rossi:
Good, first time I read about this here.

Is it just to sideload the stock 5.1.2 then?

Gesendet von meinem OnePlus One
[Fire Android Development] sd_shadow:
Unbrick, restoring, downgrade are all done with same steps

---------- Post added at 01:29 PM ---------- Previous post was at 01:28 PM ----------

pretty hard to go to first page and read
[Fire Android Development] Signor Rossi:
Thanks for the Info.

Btw. First Page does not say anything about 5.1.3 downgrades.

I'm following this thread since a while now and, as said, so far everyone said, if you're on 5.1.3 you're f****d.

Anyway this is cleared now, so nuff said. [emoji484]

Gesendet von meinem OnePlus One
[Fire Android Development] sd_shadow:
I've been saying for at least a month 5.1.3 can be downgraded
[Fire Android Development] DB126:
I intentionally linked the index thread (while referencing the relevant post addressing your specific question) as it was evident you were uninformed and might benefit from some of the other information in the index which you will likely need. Happy reading.
[Fire Android Development] Signor Rossi:
LoL, why is everyone so offended / offending here at XDA [emoji213]

Calm down everyone [emoji317]

Gesendet von meinem OnePlus One
[Fire Android Development] glorifyday:
:crying:

I had no time to sit down and do the procedure... and...

Surprise!

5.1.4 has arrived :(

Any idea what to do with the new OS?
[Fire Android Development] sd_shadow:
just more security updates, downgrade to 5.1.2, if you want to root
[Fire Android Development] glorifyday:
No risk to brick the device? Is that confirmed?

Thanks for the good news:good:.
[Fire Android Development] sd_shadow:
there has been at least 2 reports that it's safe to downgrade 5.1.4 to 5.1.2
[Fire Android Development] glorifyday:
Thanks again.

Hope I will find time before the next update ;).
[Fire Android Development] jubango:
I'm not totally sure this is the correct place, but I can't find any resources elsewhere. I was able to successfully root and install flashfire, but whenever I try to open flashfire, it crashes immediately. Does anyone have any suggestions?
[Fire Android Development] Signor Rossi:
Use the latest FlashFire, 0.30 is outdated. 0.50 is the actual version. Check the Playstore

Gesendet von meinem OnePlus One
[Fire Android Development] Tomsgt:
Looks like Amazon just released Fire OS 5.1.4 firmware and looks like the bootloader has been updated again this means that downgrades from fire os 5.1.4 will probably cause a hard brick with dead screen. Do not downgrade. also I have downgraded fire OS 5.1.3 and 5.1.2.1 to Fire OS 5.1.2 without any problems since the bootloader hasnt changed across these firmwares.
[Fire Android Development] sd_shadow:
there has been a few reports of successfully downgrading from 5.1.4 to 5.1.2, without issue
[Fire Android Development] Tomsgt:
good to know. I will have to test this out some time soon :)

just tested downgrading from 5.1.4 to 5.1.2 and the device is booting up now. glad that Amazon hasn't blocked this downgrade.
[Fire Android Development] m00nshake:
Last evening, I was able to downgrade from 5.1.4 to 5.1.2 successfully following the video and file link on the first page of this thread. Then I was able to root, install/update SuperSU, uninstall Kingroot, install ChainFire, use SuperTools to block OTA updates, and finally install Cyanogenmod. When I downgraded, I made sure to skip setup and only turn on WiFi when Kingroot needed it until it was rooted. I primarily used this guide after downgrading: http://xdaforums.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300
[Fire Android Development] Beeg Boy:
Does anyone know what version new orders are being shipped with? What version are they running right out of the box?
[Fire Android Development] DB126:
Variable. Latest is 5.1.4 but receiving an older build is not uncommon. Shouldn't matter as same abilities are available on all builds in the 5.1.x series (prep work may vary by version). Highly unlikely you would receive a 5.0.x build which is the sweetest of them all.
[Fire Android Development] Beeg Boy:
Cool.

I ordered one back in April and it had 5.1.1 on it.

I used the SuperTool and Flashfire to get Nexus Rom on it.

I was thinking of ordering another one, just not sure yet.
[Fire Android Development] Tomsgt:
then run the root script again
[Fire Android Development] killa78:
I've tried it twice now, rather than rooting, it goes to the TWRP screen.

Before I switch off the tablet leaving the TWRP, it says install Root and I swipe across to allow it.

Is there another way? Or what should be happening.
[Fire Android Development] dhm282:
Can someone confirm that, with option 3 the OTA is in fact blocked on 5.1.1?

The only reason I ask is that when I choose option 4, it says unblocked and then when I choose option 3 it says blocked.

[IMG="menu"]http://i64.tinypic.com/2lvb9k1.png[/IMG]

[IMG="Option 3"]http://i65.tinypic.com/sbj6t0.png[/IMG]

[IMG="Option 4"]http://i67.tinypic.com/2z8zpxv.png[/IMG]
[Fire Android Development] Tomsgt:
yeah sorry that was a typo its been fixed in new version that is on the site now, download it and check it out
[Fire Android Development] dhm282:
Great thanks! Also, do you think Ad removal for the 5.1.1 can be included now? See this thread: http://xdaforums.com/amazon-fire/general/removing-ads-5-1-1-t3272714
[Fire Android Development] Pond-life:
If in doubt turn wifi off and try to get the system update to do anything. If it won't let you into the systems update page or returns "check for update failed" on the check now button then it's done.
[Fire Android Development] hobojester:
/moved to appropriate thread/
[Fire Android Development] Tomsgt:
great point and that is how i tested it also
[Fire Android Development] Tomsgt:
option 9 added to supertool enjoy you will have to download it again :)
[Fire Android Development] jbraney:
You sir, are awesome...
[Fire Android Development] jbraney:
New possible method of obtaining boot

Hey, I may be speaking complete garbage here, in which case please stop me, but I remember the devs running into this same problem of a locked bootloader and horribly locked down OS with the amazon fire phone. It took months to figure everything out, but they finally got everything from root to CM11 working. They used safestrap to get everything working... I don't remember how exactly they did it, but I remember they had to use kingroot, then use safestrap in a method similar to TWRP, then flash, and get rid of kingroot and put on SuperSU...

That probably makes very little sense, but either way, just check out the fire phone forums, and read up on what they did there. Same OS, just an earlier version, and they had the same problems we are having now. Maybe we can get some ideas!
[Fire Android Development] blueberry.sky:
Yes, we could use safestrap for 5.1.1 devices with their crippled fastboot, but we need kexec for safestrap. Someone is working on kexec, see the kexec thread (in dev subforum).
[Fire Android Development] theusualuser:
Hi, this isn't usually my wheelhouse but I got one of these for my daughter for Christmas and I've read through the thread. I think I managed to get the ADB drivers to update correctly. It now seems to recognize my device as unauthorized. What is the next step I would want to take? I'd like to totally replace Amazon's stuff with Nova if that's possible, and I want the play store on there and I want the device rooted so I can get an adblocker like adaway up and working (3 year old daughter loves to click on everything). What's the order I want to go about this?
[Fire Android Development] Pond-life:
Think you've not enabled adb on the Fire.

From the batch file.

Before continuing, ensure USB debugging is enabled

in your Amazon fire 5th gen settings

go to device options then click on serial number 7 times to enable

developer options then in developer options turn on Enable adb option.
[Fire Android Development] klsystem1:
worked perfect yesterday on 3 devices. The only thing I recognized was that I had to make a factory reset before... pre installed google playstore can't cope with the script.

my questions so far: Why should I block OTA Updates ? I only want to use Nova Launcher and playstore. Is there a OTA blocking necessary ?

Nova and Firelauncher for choose would be great, but at the moment only Nova Launcher is present. (After factory set too!).

Thank so much for that supertool ! christmas is saved for 3 young boys.
[Fire Android Development] redbandana:
okay, while running script I keep getting "ADB server is out of date". I followed the update drivers instructions and all seems to be up to date. I restarted computer and device several times. I had no difficulties rooting the earlier firmware. What exactly am I doing incorrectly?
[Fire Android Development] pappasmurfsharem:
What does device manager show when you have the device on and plugged in?
[Fire Android Development] redbandana:
Under portable devices:

It now shows "Fire" it used to display "MTP USB Device", I believe.

Now have a section for Fire Devices, which displays:

Android Composite ADB interface

---------- Post added at 02:30 AM ---------- Previous post was at 02:26 AM ----------

Think I should uninstall both and try again?

---------- Post added at 02:39 AM ---------- Previous post was at 02:30 AM ----------

deleting both devices from device manager and htc sync manager allowed device to go into root process. wow, i'm becoming an idiot at my old age.
[Fire Android Development] Butcher98:
I'm getting the device to show up in ADB on the driver check, but when it goes into fastboot it doesn't show up. Using Windows 7 btw. Any ideas?
[Fire Android Development] Dr.TheMaster:
The earlier version of the SuperTool (before 5.1.1 options ) had no problem with me on 5.1.1 at all.. I installed Google apps and it worked like a charm.. but the latest version (December 17th 2015) I open the .bat file.. is shows adb devices attached.. it shows my device as usual and then it just turns off.. it does not show the 9 options that I should get.. I tried to run it as administrator and had no luck with it.. can you please explain to me what i can do? BTW I still have the older version and it is still working.. anyway thanks for helping us out :)
[Fire Android Development] Aiadi:
Unlikely a fault of flashfire but after completing all the processes and installing cyanogenmod I cannot use 'Developer Options' at all. I mean, I can bring them up but turning on USB Debugging does not stick at all. Also when I switch of developer options they completely disappear off the face of the settings menu. Very strange and cannot find any similar reported searching on google. Has anyone on here experienced a similar issue?
[Fire Android Development] Chillmann:
QVC Germany still got 5.0.1 devices. They even replaced mine after i got ota'd to 5.1.2 and hard bricked it :laugh::svetius:
[Fire Android Development] fmc000:
My second arrived a couple of weeks ago and it had 5.1.3 on.
[Fire Android Development] flamanar:
I have version 5.1.4. Am I S.O.L. with just using SuperTool to install Google Play store and disable ads?
[Fire Android Development] 45Wheelgun:
I just successfully downgraded 5.14>5.12, and successfully used almost every every feature of this Supertool. Thank OP for making it so easy.
[Fire Android Development] Tomsgt:
glad you like my work :)
[Fire Android Development] ipfreelytech:
I'm stumped. Can't get Kingroot going on my 2nd Fire. Both shipped with 5.1.3. The first one was no problem. Downgrade to 5.12, kingroot just worked.

this 2nd tablet just doesn't want to run Kingroot. I've sideload downgraded it several times to 5.1.2. I've wiped /data and /cache after donwgrading. It's not registered to my amazon account.

Kingroot crashes at about 17% and the device reboots. Using the latest kingroot apk, also tried using the kingroot apk in the super tool.

I get this in the log:

E/ContextImpl( 547): Implicit intents with startService are not safe: Intent { act=com.tencent.qqpimsecure.TMS_LITE_SERVICE (has extras) } android.content.ContextWrapper.bindService:564 com.kingroot.kinguser.aem.run:86 java.lang.Thread.run:818

W/ActivityManager( 453): Unable to start service Intent { act=com.tencent.qqpimsecure.TMS_LITE_SERVICE (has extras) } U=0: not found

It's definitely downgraded:

[ro.build.date]: [Sat Feb 27 02:18:24 UTC 2016]

[ro.build.description]: [full_ford-user 5.1.1 LMY47O 37.5.4.2_user_542168620 release-keys]

[ro.build.display.id]: [LMY47O]

[ro.build.fingerprint]: [Amazon/full_ford/ford:5.1.1/LMY47O/37.5.4.2_user_542168620:user/release-keys]
[Fire Android Development] fmc000:
My Fire had 5.1.3 on it too, I downgraded it to 5.1.2 and rooted with Kingroot v4.92. The first couple of tries it didn't work. The third try it ran until 20-something % and it reboot failing to root. I re-run the app a couple of times without rebooting and then the tablet rebooted by itself, finally acquiring the root privileges.

I enabled wi-fi only after having launched the app, immediately before it started looking on the net for data.

Hope it helps.
[Fire Android Development] BlazingOwnager:
I just managed to get my Fire rooted, but I'm having trouble finding one of the two possible options:

A) I want to install the APKs for Live Wallpaper and Voice Typing; both are showing uninstalled at the moment

but ideally:

B) I'd like to find a replacement ROM for Kitkat or Lollipop to replace FireOS with.

The tablet has successfully been rooted and really only two features are non-functional thus far (the links I found to the solutions on the net were from 2 years back and expired), but other than that it's ready. I have the supertool in and Flashfire is installed.

Can anyone point me to where to grab a replacement OS? Thanks!
[Fire Android Development] DB126:
http://xdaforums.com/kindle-fire-hdx/general/index-kindle-fire-hdx-7-8-9-t3206703
[Fire Android Development] tul9033:
I used SuperTool to install Nova and still can't get widgets working. With original Fire OS 5.1.2 I can't add widgets. It just goes to the Fire OS settings screen instead of popping up a confirmation window to add the widget within the Nova launcher.

Any other suggestions or tips? Didn't realize how much I took for granted the widgets until they were gone.
[Fire Android Development] greencat2:
Just got the Fire tablet yesterday and was getting ready to root when I saw it was at 5.1.1. It has a December build date.

Supertool here I come. The recent sale is probably clearing out the stock.
[Fire Android Development] tul9033:
I ordered 2. The black one was 5.1.1 and the Tangerine was 5.1.4. 5.1.1 was much easier to root.
[Fire Android Development] DoLooper:
I assume you're rooted. First look for NovaLauncher_4.2.0.apk at bottom of /system/priv-app. If it's there, use file explorer to change permissions to rw- r-- r--. (Long press apk to select it and choose properties to change perms.) If it's not in priv-app, see if it's still in /data/local/tmp/. If not, use file explorer to search for it. When found, move to /priv-app and change perms.

If you're certain it's not on device, look for com.teslacoilsw.launcher folder in /data/app. It will have a base.apk file in it. Move base.apk to /system/priv-app and change permissions as above. Please post which apk you find and where it was. Thanks.

EDIT [MENTION=7537930]tul9033[/MENTION]: Oh, yeah, reboot after changing perms :)
[Fire Android Development] tul9033:
Yes I am rooted. I have 2 of these Fire tablets. After the widget issue I loaded the Fire Nexus ROM on one. It's promising, but several apps aren't giving the option to install. I may fall back to the Fire ROM if I can get this widget issue sorted out.

I will go through what you have outlined on the other Fire that is still Fire ROM'd tonight and report back.

Thanks!