yashsingh1/xdaforums huggingface dataset:
[Fire General] DB126:
Naa - 5.1.2.1-5.1.4 has never been successfully rooted with KingRoot (or at least not reported here). Forum ref docs have reflected this for some time.
[Fire General] jorzilin:
Weird. I have managed to successfully root one of them now, after like 10 tries and the newest Kingroot_global. Why did all my other attempts always work on first try on 5.3.1?

Anyway, glad it works. Two more to go. Thanks to Davey for the quick response!
[Fire General] DB126:
KingRoot (and similar titles) are generic rooting tools that don't seem terribly adept at matching make/model/rom to a list of known vulnerabilities and associated exploits. Enter 'trial and error' combined with an unsophisticated (seemingly random) selection algorithm and you have the high variability seen with this tool. Just keep trying; you'll hit paydirt eventually. :)
[Fire General] wu2:
Has anyone succeeded in downgrading from 5.3.2.1 ? Or it is just not possible so far?
[Fire General] DB126:
There is no downgrade path for those on 5.3.2.1; device will brick. Unlikely this will ever change. Best hope is a root exploit becomes available for this release or a subsequent FireOS build. Might be awhile...
[Fire General] amti366:
Thanks Davey126 I was able to downgrade and then Root this tablet. FYI I had one more tablet with same version (5.1.3) to root (what can I say these things make for a nice Christmas present for kids :)) and started the same way as before with installing Kingroot and it worked on first try. so I can confirm Kingroot 4.9.6 did work to root this thing right out of box without downgrade it was just one tablet which did not wanna budge.

Anyways thanks for all your help.

Matt
[Fire General] DB126:
[MENTION=1056340]amti366[/MENTION] - thanks for the update! KingRoot is continuously evolving (for better or worse) and apparently has acquired some new skills...or existing capabilities were never fully exposed. FIreOS 5.1.3 instances are becoming rare but your findings may also apply to 5.1.2.1-5.1.4.0 series.

[MENTION=4267571]sd_shadow[/MENTION]: possible update to forum reference docs. Might also want to note removal issues with KingRoot 5.x per [MENTION=421683]tomst[/MENTION]g (here). Possible but requires manual intervention until SuperTools scripts are updated.
[Fire General] steve8x8:
My new Fire which I had ordered in the Black Fri week arrived today. It's orange (colors - orange, blue, and magenta - became available here only lately), and I was eager to learn about the FW installed. On the back cover it says Model SV98LN (same as my 2015 black one)... Lot M649 (vs. M550).

It's 5.3.1.0 - phew, it's rootable, and there's no need to downgrade.

BTW, on my device it's early morning of Jan 13, 2010 - this means it has been initialized 12 days ago (Dec 2). Apparently 5.3.2(.1) hasn't made its way into the factory yet... YMMV though.
[Fire General] DB126:
- assume you are ok now w/CM 12.1?

- vast majority of CM flash failures are wipe related (missing, wrong partitions selected and/or wrong position in FlashFire queue)

- detail flashing instructions are in the CM 12.1 OP
[Fire General] Super user guy:
I tried to flash I on it's own with gaps etc nothing always failed.

Wish trwp worked for this fw lol
[Fire General] DB126:
See second point in my previous post regarding wipes; high (almost certain) probability that is the source of your problem. Read the CM 12.1 OP for information on which partitions to select and, most importantly, moving the wipe operation to the top of the queue just before hitting 'flash'. BTW - CM flash would also fail in TWRP if wipes were not selected/sequenced correctly.

Note: CM 12.1 OP references FlashFire v0.50. Version 0.53 is preferred (OP is a bit outdated).
[Fire General] Super user guy:
Yeah I've wiped first and followed the instructions, I'm gonna try acip I think or resurrection
[Fire General] DB126:
So what are the symptoms when attempting to flashing CM 12.1? Return to FireOS? Hang on Amazon logo? FlashFire freeze?
[Fire General] Super user guy:
yeah just hangs on Amazon screen so nothing is installed
[Fire General] DB126:
This behavior was reported by another user (which I replicated) with the latest build but appeared to be wipe related. Once the system partition was cleared CM 12.1 went in fine. Sounds like you're pretty confident around the order of operations in FlashFire. Curious why others are not experiencing the same thing. FlashFire 0.53? Not changing any options (eg: mounts), just selecting partitions and zips? Possible the CM zip is corrupt; you can verify that by checking/comparing the MD5 which is posted on the CM download page (LMK if you need tool suggestions).
[Fire General] Super user guy:
Well I wiped first every time and I got the link from xda, I also downloaded it again after first fail just in case got md5 checker.

I'm new to the fire but been rooting since s2 days, found fire to be very temperamental lol
[Fire General] DB126:
Sure are! But a lot has to do with misplaced expectations and the false belief Fire tablets are generic Android ready gadgets just begging for a custom ROM. Reality is Amazon specs hardware to support a captive shopping experience and and has no interest in any form of customization that compromises their walled ecosystem. Device margins are insufficient to justify designing/selling/supporting hardware at the suggested price points without a strong post sales tie-in. A page from Apple's play book...except Amazon is trolling the low end of the market while Apple targets the upper end.
[Fire General] Super user guy:
Your not wrong my nickname is macman , I used to have iphones and make themes for cydia and widgets for iphones but got sick of how Apple nicked my work and others in the community, nowadays I live on my s7e and like to find new ways to mod stuff ,so far im liking this device but yes this device could be great if not for the Apple tactical bull**** lol
[Fire General] chan329234:
After my Fire tablet automatically updated to 5.3.2, Google Play app no longer works. The app loads, but all I see is a white screen. Swiping from the left brings up the Google Play menu (eg Redeem, Settings, etc), but nothing else.

Google Docs app still functions, so Google Services still work, just not Google Play app. How can I solve this or downgrade from 5.3.2?
[Fire General] steve8x8:
It is now.

Security patch level is Oct'16 now (was July'16). Preloader and boot images have been modified (as suspected before).

---------- Post added at 09:52 AM ---------- Previous post was at 09:43 AM ----------

See post #2 in this very thread.

Avoid to get upgraded to 5.3.2.1 by all means - i.e. Flight Mode ON!
[Fire General] kaysond:
I tried downgrading from 5.3.2.1 to 5.3.1. Looks like I bricked it. whatever they changed is preventing the downgrade.
[Fire General] tradedyna:
no need to downgrade, just try go to Settings > App & Games > Manage All Applications > Google Play Store

clear cache and clear data
[Fire General] DB126:
As expected. Always poke around for the latest news before attempting a downgrade/rollback.
[Fire General] kaysond:
Yeah it updated without me noticing. Any idea how to fix it? It was a free tablet so it's not a huge loss, but it would be nice...
[Fire General] falkonn00:
Another 5.3.2.1 failed downgrade

Just thought I'd post yet another (sad) downgrade fail. :crying:

I have two of these tablets, both "kids" versions with Amazon FreeTime. I checked the device OS last night and it was 5.3.2 so I started downloading the 5.3.1 firmware and tools from RootJunky's website (thanks to him for an awesome resource!). Sadly my internet speed is so slow I had to wait overnight for the downloads to complete. I woke up this morning, double checked the device OS version (which I still think was 5.3.2) and started on the downgrade process, and it completed successfully, but only provides me a black screen when trying to boot up.

I then double checked the 2nd (untouched) device, and overnight it had updated to 5.3.2.1 which makes me assume the other device did as well, causing the downgrade to fail. Perhaps I just didn't read the .1 at the end? I guess I'll never know for certain. :eek:

Are there any actions a developer would like me to try before I send in this tablet to get it replaced under the FreeTime unconditional replacement policy? I'll be submitting the replacement ticket tonight and probably have to send it back by the end of next week, but I'll do whatever experimentation I can do to help get 5.3.2.1 rootable. :good:
[Fire General] DB126:
At present there are no known solutions or 'long shot' things to try. Black screen bricks (typically bootloader failures if not a hardware problem) are almost impossible to overcome regardless of device. Sorry for the bleak readout.
[Fire General] DB126:
The public development/support community recently aligned with this device has depended on third party tools for rooting (eg: KingRoot). I don't believe the major players are pursuing root solutions at this time.
[Fire General] SnuggP:
Do you you have root? and how did you do it.....
[Fire General] DB126:
Yep - flashfire would not launch without root. Given other attempted actions (eg: trying to unlock bootloader - lol) individual likely grabbed wrong packages and/or didn't sequence wipes correctly. Been 5+ days since last post. Suspect dude fixed it or moved on.
[Fire General] deivitbcn:
I have got my new device tomorrow and would like doing root but I am reading previous posts and not so sure to it does now...

So what do you recommend, updating firmware to 5.3.2 (for after that does downgroading to 5.3.1) or not and keeping the factory firmware?

If they patched to Oct 2016 I could brick the device, is it ok?
[Fire General] Paul4567:
Sorry for noob questions: Bought a HD7 a week ago, only enabled the WiFi to check it could connect to my AP after which it said OS 5.3.2.0. I have NOT registered it - which limits most icons. Want to install Nexus ROM. I gather need to buy a 'Factory USB cable' to get started ? Question is how to install necessary Apps, eg FlashFire on HD7 without switching on WiFi (i.e forces update to unwanted 5.3.2.1) ?

(I see nowhere in Settings to disable OTA updates)
[Fire General] DB126:
When your device arrives boot but do not let it connect to the network. Report version of FireOS; we'll go from there. Are you interested in a custom ROM or just rooting to tweak FireOS (eg: block ads, install Google Play Store, etc.)?
[Fire General] deivitbcn:
Hi! my device comes with 5.3.1 and manufactered september 2016

I want to do root and after that flashing CM 12.1

so i guess i have lucky and no needing downgrade...

The same thing i did with my first device, so I think I have to go to the same steps (useing supertool and flashire for cm12.1..)

if it helps, this device arrived from Italy to Spain....
[Fire General] deivitbcn:
solved... finally i get to root it (5.3.1)
[Fire General] DB126:
Great! Keep in mind Kinguser (installed by KingRoot) must be replaced by SuperSU before Flashfire will work. The SuperTool handles this for you.
[Fire General] Paul4567:
Sorry for noob question: Bought a HD7 a week ago, only enabled the WiFi to check it could connect to my AP after which it said OS 5.3.2.0. I have NOT registered it - severely limiting usage. Want to install Nexus ROM. Just ordered a 'Factory USB cable'. Gather can use '[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3' to install all necessary PC tools. Question is how to install necessary Apps on HD7 without switching on WiFi (i.e forces update to unwanted 5.3.2.1). Can Kingroot, SuperSU, Flashfire etc, be installed on HD7 from the USB connection ?

(I see nowhere in Settings to disable OTA updates)
[Fire General] DB126:
If you are referring to a 4th gen HD7 this is the wrong forum, ask here: http://xdaforums.com/fire-hd

If you have a 5th gen Fire then everything you are proposing is wrong:

- factory/fastboot cables are useless

- adb/fastboot installs will not work; must use FlashFire for all flashes

- dozens of threads explaining what and how for this device

Figure out what you have (device) and where you need to be (XDA forums).
[Fire General] Paul4567:
As stated, bought it (from Amazon) a week ago I didnt know older HD7's still sold. When I first registered on your Forum over a week ago I gave fuller details of my purchase 'Fire 7 (2015 OS 5.3.2.0)' in the noobs Q&A section asking in which subforum to put my questions, but no response. If you look at my original post you will see, I am preparing to travel overseas and having read in Liliputing 24 Nov it is not difficult to convert Fire 7 - assumed CURRENT version, as they recommended it as a good buy, to Nexus ROM, I bought one, and now just need a newbie guide to doing that. As no reply over a week and only days before I depart, I ended up using Google to search your Forum and found your thread on 'Fire General' which sounded like the right subforum for my post. :(

Can you at least point me to some good noob threads on achieving this ?
[Fire General] DB126:
Assuming you have a 2015 5th gen Fire (and not a HD7) everything you need can be found in the forum index: http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485

In addition, there are many 'tutorials' authored by XDA contributors within these forums, some better than others. You will need to do some reading to find what works best for you as each assumes a different 'tone' and experience level. Good guidance is typically recognized by others (look for that!); errors and omissions are also called out. It is always best to read through a thread before acting. You will also find many step-by-step videos on YouTube. Those produced by 'Root Junky' are especially noteworthy.

If you are unfamiliar with rooting and modifying Amazon devices give consideration to returning the Fire in favor of a Google Nexus 7 which arrives with the desired configuration.

XDA contributors are individuals just like you sharing their personal experiences and expertise with the community.
[Fire General] deivitbcn:
thanks..

by the way,

i have just installed cyanogenmod 12 and after that i deleted super su (doesnt like look so necessary keep it) but maybe i must reinstall it before if i would like to come back to fire OS or flashing another rom ? do you recommend keep on super su at cyanogenmod 12 anyway?
[Fire General] DB126:
CM 12.1 has an integrated root/privacy manager that works well. SuperSU is not needed and in some cases has been known to present issues. That said, SuperSU offers improved granularity, logging and security features that some like. I have SuperSU on some devices and not others. Boils down to personal preference.

Some ROMs recommend SuperSU or have it built in (eg: Nexus). Be sure to review requirements before flashing a different ROM. Returning to FireOS entails a fresh start; you will have to root again and can decide whether to keep Kinguser, go with SuperSU or install another root manager.
[Fire General] DB126:
Quick note on XDA protocol: No need to say 'thanks' as a separate post. Simply used the 'thanks' button built into whatever tool you are using to access XDA. Also no need to do that on every exchange...just those posts that, well, deserve a 'thanks'! :) :)
[Fire General] Paul4567:
Thanks for correcting my wrong path, I didnt realise there are so many different Fire models, also which are 'Kindles', which are not.

The link you sent me is top of a pyramid of links to many articles/threads. I spent a while on your link to see if I could find a thread similar to your 5.3.2.0 thread where I read all 13 pages of it thinking it applied to my Fire 7 (2015), before making yesterdays post in it. Had I got answer to my initial post asking where is the subforum for questions on the 'Fire HD7 (2015 OS 5.3.2.0 )' when I registered 9 days ago I would have gone to 'where I need to be' and hopefully found a noobs guide to converting the OS to Nexus ROM, but that pyramid appears too vast to restart my search with only days left before I depart for Brazil.

From sound of your reply, you know enough of '2015 5th gen Fire 7 ' model to give me an assurance its OS can be converted to 'Nexus ROM ', and a noobs guide exists somewhere in that pyramid to show me how. Can you assure me that is true now before I depart ?

I will then be happy keeping the Fire and searching your link for a noob guide in January at the other end.

Re. your mention of Nexus 7. I have a Nexus 5 for use about the apartment, and as a 3G modem/AP for laptop to access internet. To date not had time to explore Android deeper. Reason I didn't buy a N7 for Brazil is I wanted something cheap for the beach (N7 cost x6 more than a F7.). Too risky taking a N5 or N7 to a Brazilian beach. Bit niffed Google not making a Nougat OTA for my N5 stuck at Android 6. As F7 has 64bit CPU maybe it will advance to Android7.
[Fire General] DB126:
- if FireOS remains at version 5.3.2 or below is possible to install Nexus ROM

- if FireOS has advanced to 5.3.2.1 or above Nexus is not an option at present

- the work effort to achieve Nexus Nirvana ranges from modest to somewhat difficult depending on FireOS version and experience level; "noob" guides can only take you so far

- there are no assurances; any flash can result in a non-recoverable brick

- unlikely Android 6/7 will come to this device; no business case
[Fire General] freaky2xd:
how to root 5.3.2.1?

how did you root 5.3.2.1 ?!?!

I was only able to install the playstore :(

rooting with kingroot was no success

this is my first amazon device, so I had no idea that it would be more difficult
[Fire General] DB126:
No root exploit (yet) for FireOS 5.3.2.1. Most likely will appear in KingRoot first. Run every few weeks or check the forums for updates.

Amazon tablets are not your typical Android gizmo. Special procedures and caveats abound starting with no custom recovery (booted/flashed) even if rooted. All partition updates, including flashing custom ROMs, must be done via Flashfire. Stock recovery only permits restoring FireOS.
[Fire General] BeeWall:
The link you put does not work. You included an extra URL tag.
[Fire General] DB126:
Link works fine from XDA labs app where the post was created. The extraneous URL tag is either being introduced by the XDA labs app (unlikely), XDA site engine or represents a rendering error by the app or browser being using to access the thread.
[Fire General] fuzzynco:
Amazon says I need to upgrade OS to 5.3.2.1 to fix networking issue?

I have bootloaders/boot from 5.1.2 and OS from 5.3.2.0 via the flashfire method of new OS the reflash bootloaders and boot from 5.1.2.

Amazon says 5.3.2.1 will fix the networkng issue of time zone keeps trying to change to Central Tine when I and my ISP's router are in Eastern Time.

If I redo the process (backup sdcard (internal storage) with flashfire), flash (new bin, old bootloaders / boot bin, supersu.zip, google (pico),

xposed.zip), reboot, restore internal sdcard, restore apps from titanium); will I need to redo the prevent updates and stop advs again?
[Fire General] steve8x8:
Did I get this right that you're running a rooted 5.3.2.0 userland on top of 5.1.2 bootloader? *drops jaw* - so this is apparently possible. (Using FlashFire to install stock ROMs has never been encouraged IIRC, but it seems to work...)

Now that we have a tool to retrieve the preloader version, can you verify it's indeed 5.1.2 = 20160120-094719? See https://drive.google.com/drive/folders/0B214JJmar6j-VllGSWNXTS1mSU0?usp=sharing

If FF'ing stock ROMs *and* unsigned other stuff works, then we should be able to flash anything: excise bootloader stuff from the stock ROM (no need for signatures anymore), remove OTA, pre-root... If not everybody is already doing this, something must be fishy - but what? (You've got to "dirty flash" /system to preserve root, right? You're supposed never to touch any of the lower-level partitions. If one of the flash steps fails, you're finished...)

This still doesn't provide a means to root 5.3.2.1 - as a rooted system is required to install stock ROM and SuperSU. (This would have been too easy.)

Noting that your final Q hasn't been answered yet: as OTA and ad blocking (RJ style) works by removing the corresponding components: Installing a newer stock ROM would make them available again, so the A is yes...

A final edit, now that I read the 20 pages of the "Tut: FlashFire" thread - must have slipped my attention while reading a thousand other pages to get back in sync. It seems that [MENTION=4551511]Vlasp[/MENTION] had suggested to build a stripped, pre-rooted ROM but never came back - and this path is open only for people who decided early to keep their old bootloaders (i.e. not me :-/). Apologies for ignoring that part of the forum. Off to read even more now.
[Fire General] BeeWall:
It does work from Labs. However, it does not work on Chrome or Chrome on Mobile. When using the Xda Legacy app on the Play Store, it displays

I'm guessing that browser, Labs, and Legacy all deal with links differently for some reason. Although it seems the link worked for other people, so maybe it is Chrome.
[Fire General] fuzzynco:
whichpl says the bootloader is ...

./whichpl
build stamp: 20160120-094719
fireOS-5.1.2 secure

I'm guessing since the process a the whole new FireOS and its bootloaders then loads a tailored install that only replaces

the old bootloaders and boot partition; it should all work. I'm guessing that since 5.3.1 is rootable and 5.3.2.x isn't Amazon

changed something in the bootloaders or boot. Since it appears that 5.1.2 kernel works with the 5.3.2 /system (even

Alexa [long press home to get an Alexa prompt, like Fire TV] works). The approach is to flash a whole fireOS .bin from

Amazon, then flash a tailored one that only replaces the bootloaders and boot, then flash supersu.zip, google &

xposed framework all from the same 'job' so no boots happen before everything is updated & installed.
[Fire General] Marsu42:
I understand Amazon is pushing these devices as a delivery system for their content, but I somehow doubt that annoying the dev community with trying to lock everything out serves them in the long run. They probab don't have a huge profit margin on the devices, but I doubt they put money *into* them so the price is b/c of the large volume produced.

My personal guess would be that not too many people exchange their roms, even with nice yt vids it takes some courage and experience handling embedded devices - if a lot of people would go for custom roms, all these locked phones wouldn't sell as they do? The only valid reason for Amazon's behavior proab would be if some people mod tablets for a living and re-sell them with a profit.

Anyway, I'd like to recommend the Fire7 to a friend of mine, but since you cannot know if you get one with downgrade'able rom I'd rather skip the "it doesn't work as you said it would" complaints :-o
[Fire General] Arhcangel:
If you want a low end tablet with a near stock Android then the B&N Nook 7" is probably a better bet. Of course you'll want to make sure you update to a non-malware version of the firmware. :fingers-crossed:

I grabbed the Fire 7 because I thought it would be a good companion to my Echo. Sadly I don't even see it as worth the $49 I paid for it. I'm hoping for a root to 5.3.2.1 ASAP otherwise it will sit in a drawer until I clean the drawer.
[Fire General] DB126:
Return that one and snag a refurb on Amazon Warehouse for half the cost which will almost certainly arrive with older firmware that can be rooted. Refurbish is somewhat of a misnomer for Amazon products - most are indistinguishable from new aside from the box it arrives in.
[Fire General] Marsu42:
Sadly, in old Europe we're limited to fewer choices than in t he center of the unverse :) ... but the B&N somehow looks identical to the Fire anyway? Imho on black friday the Fire7 was a steal - but ony if you happen to get a root'able version :-\