yashsingh1/xdaforums huggingface dataset:
[Fire General] ulises.rodriguez:
Apart of the NEW Alexa, does anyone here has noticed something NEW or any improvements with the latest FireOS 5.3.2 update?
[Fire General] Reuben Talbott:
Can we root it after the update with dirty cow?
[Fire General] DB126:
Hi - this forum is for 5th gen Fire (released fall 2015); you'll want to ask you question here. While 5th and 6th gen devices often run similar builds of FireOS there are some differences attributable to hardware variations and software release cycles. What works on one type of device may or may not on others. Rollbacks can be especially dangerous as bootloaders/kernels generally differ across device types. A failed rollback attempt typically yields a bricked device with no recovery options. In short, I would not generalize across device types.
[Fire General] DB126:
To my knowledge there is no indication Dirty Cow has any meaningful relevance on this device. Although the underlying vulnerability may exist there is no evidence it has been successfully exploited on FireOS.
[Fire General] Reuben Talbott:
OK I thanks
[Fire General] ManWithCamera:
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).
[Fire General] jmara13:
5.3.2 > 5.3.1 downgrade IS possible

Good Afternoon,

I recent purchased a Kindle Fire 7 (11/11/16) and it was upgraded to 5.3.2. I was able to downgrade the OS to 5.3.1 using the ADB sideload method and then root using Kingroot (11/18/16). Be sure to block OTA updates once completed. Have not seen any issues yet and will report if i do.

Good Luck everyone.
[Fire General] Reuben Talbott:
Thanks
[Fire General] subiaco:
Tried to disable lockscreen ads using adb (com.amazon.kindle.kso), but when I touch the special offers icon on lockscreen, I get a window that says Selected Offers. Is there another package that I should be disabling? I'm on Fire OS 5.3.2.
[Fire General] Palux:
Hello, i have the latest Fire 7".

If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?

Onlye root, not recovery modded or other rom.

Thanks

p.s.: not use slang with me, thanks
[Fire General] DB126:
Yes - 5.3.1 can be reloaded again if pure stock is desired. However, this is not generally required for warranty exchanges (the only type of hardware assistance Amazon provides) as they do not perform a detailed inspection of returned devices.
[Fire General] Arret:
Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.

1. Downgraded from 5.3.2 to 5.3.1 -> worked

2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked

3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.

4. Install Google Play Store

5. Install FlashFire from Google Play Store -> was that ok?!

6. Configure it as described in this thread which was linked. CM12 + Gapps Nano

I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.

Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo

Should I reboot it or is it actually flashing right now since hours?

br
[Fire General] DB126:
Something went wrong; the Amazon Logo should display for <30 sec. You will need to reload FireOS 5.3.1 from the stock recovery menu and start over. Guidance here, here. Once recovered post back for further assistance loading CM 12.1.
[Fire General] Arret:
Ok will do.

Should the FlashFire APK included in the "AmazonFire5thGenSuperTool" usually work for this procedure or was there already something wrong in step 3?
[Fire General] DB126:
There is a naming glitch in the script that prevents the FlashFire apk from being installed. However, the Play Store version should have been fine. For the next go-around grab FlashFire from here and skip the Play Store install.

Hard to say what went wrong. FlashFire is an amazing yet touchy tool - especially when coming from FireOS. Best practices:

- don't register your device when prompted when FireOS initializes

- only use apps/tools recommended in the forums or included with well regarded utilities like the 'SuperTool' (you were fine here)

- reboot tablet just prior to launching FlashFire; always use the latest build unless otherwise instructed

- be sure to include a wipe action (system/user/dalvik/cache partitions) when transitioning from/to FireOS

- only use recommended FlashFire options; defaults are typically fine

- make sure wipe action noted above is dragged to TOP of operations sequence before hitting 'Flash' (believe this is what went wrong)
[Fire General] ajayajayaj:
Will downgrading lose all apps/data on the kindle?
[Fire General] Reuben Talbott:
No it just downgrades the system all your apps and settings will stay.

Reuben
[Fire General] ajayajayaj:
Ok that's awesome, the video linked said that it deleted all data so I was worried.
[Fire General] Arret:
Yes I noticed that right after I posted here. "flashfire-0.53.apk" should be renamed in "flashfire-v0.53.apk" in the apps folder and then it works.

I got it running now, not sure what went wrong the first time. Thanks all :)
[Fire General] andrewison:
is 5.3.1.0 rootable on the kindle fire.

It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.

Kudos for sacrificing your tablet.

Did you have to do anything special to root it from 5.3.1.0

I didnt think it was possible on that version.

Apologies if this is a noob question.

Just confused. :)
[Fire General] zippy411:
The latest version of the supertool works on 5.3.1.0

Again you'll have to use the version of kingroot as specified instead of the one in the supertool.

http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

You can also reference;

http://xdaforums.com/amazon-fire/general/tut-fire-os-5-3-1-running-cm-12-1-t3482573

When you open the supertool and select the option to root you'll see the option for 5.3.1.0
[Fire General] percy159:
Hey guys,

I'm on 5.3.1 now and rooted the Fire with kingroot.

But i can't get supersu on My Fire how to change the system from kingroot to supersu?

Flashfire doesnt work till now
[Fire General] DB126:
Use the SuperTool to exchange KingUser for SuperSU: http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
[Fire General] percy159:
What item ist have to use in Supertool? I thought it is to change the system from Stock to cm12.1
[Fire General] DB126:
"Root your Amazon Fire 5th gen". Skip over KingRoot if already rooted. Script will then attempt to remove KingUser and install SuperSU.
[Fire General] percy159:
Witch item in Supertool i have to use? Because i look already for it?

Thank You in advance.
[Fire General] DB126:
Previously answered: http://xdaforums.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post69834818
[Fire General] datamosh:
I picked up an HD Fire 8 during the black Friday sale and I absent mindedly let the tablet update when I turned it on for the first time. When trying to revert to 5.3.1.0, my adb sideload fails at 47% every time with an error of "failed to verify whole-file signature". I have downloaded the firmware linked repeatedly (about six times) thinking my files corrupted. I have verified the md5 hash is correct. Are there any other steps I can take to downgrade? I have spent way too much time trying to figure this out, thanks.
[Fire General] percy159:
Thank You! It worked:svetius:
[Fire General] DB126:
Please use the proper forum for your device: http://xdaforums.com/hd8-hd10

Message suggests you may have the wrong file. Also try a different USB cable and/or host as contents may becoming corrupt in route to device.
[Fire General] datamosh:
That's what it was. I wasn't using files for the Fire HD 8, I am now back to 5.3.1. This is my first Fire, I confused it with the different models. Thanks!
[Fire General] hotze999:
Does not start after sideload

I tried the described method in post one. I had version 5.3.2 installed and tried sideload the 5.3.1. The file is correct and the sideload seems to be without any failure. After that i rebooted the device but since then nothing than a black screen.

If I connect it to the PC a device named MT65xx Preloader pops up for 5 seconds in device manager and disapears again, again and again.

Wether pressing power button for 20 or 40 seconds nor pressing power + volume button does anything - the screen remains black.

I tried this unbrick tool without success:

http://xdaforums.com/showthread.php?t=1428428

I believe the fire does not stay connected long enough to let the tool do hie job.

Any suggestions?

Update 1:

Sorry for confusing. I made a mistake choosing the right file for the sideload. I can say now for sure 5.1.2 will brick your device if you have installed 5.3.2.
[Fire General] DB126:
Likely bricked given steps you have already tried. Contact Amazon for a no-questions-asked courtesy exchange if still in warranty.
[Fire General] notinterested2:
Genius! Many thanks for this update mate. Worked like a treat.
[Fire General] kyrtap82:
So, I just got a fire yesterday. It had the prior version of the OS running on it, but without my knowledge it just updated itself to the current version.

As I am quite new to all of this, I would rather not sideload and have my device brick on me. So my question is, in your estimates, how long does it usually take until one-click solutions (such as Kingroot) catch up with OS rollouts?

I am under no pressure to root it, really. The only thing I'd want gone are the deals on the lock screen, but that can wait. They're not very intrusive. But I would still like to have it done - you know how it goes. Root gives you full control over the device you bought, and I guess we all deserve that.

Anyway, hope you guys are having a great day.
[Fire General] DB126:
To borrow a common investing phrase: past performance is not an indication of future results. A vulnerability in Android needs to be discovered which may or may not be exploitable. Then the same code needs to be present in FireOS. Highly doubt anyone is working on root exploits specific to Amazon devices or ROMs. FireOS 5.3.2 and it's successors may never be rootable on this device. No working root exploits have been found for the recently released (6th gen) HD 8 despite sharing common FireOS versions. Time will tell.
[Fire General] kyrtap82:
Appreciate the reply.

I guess all I can do is wait... or, if/when I get desperate for root, attempt to side-load. But as said before, I have no pressing need for root. All I want this little machine for is reading books and comics, and that I can do, thanks to being able to install the Google Play store.

Only the ads are a slight annoyane, but not enough for me to attempt to flash an older Firmware just yet.

Either way, thanks again, and I will be waiting/scanning this forum/thread for news.
[Fire General] DB126:
Contact Amazon and tell them some of the ads are inappropriate for young children. They will likely remove them for free. Otherwise $15 USD does the trick.
[Fire General] zzzk:
Downgrade from 5.3.2 to 5.3.1 and root Fire HD 8 6th Gen?

Hello,

Will this procedure work with a downgrade from 5.3.2 to 5.3.1 and root Fire HD 8 6th Gen? With the same firmware, tools, above? Thank you.
[Fire General] DB126:
- please post HD 8 questions in appropriate forum: http://xdaforums.com/hd8-hd10

- as of now (16-Dec-01) HD 8 can not be rooted or downgraded
[Fire General] DB126:
Thanks for your post. Rolling back to FireOS 5.3.1 is a well known technique to secure root on 5th gen devices running FireOS 5.3.2. A catalog of stock FireOS images (including 5.3.1) along with instructions for applying it (including a step-by-step video) can be found in the forum index here and here.
[Fire General] zzzk:
Thank you marcus_hogan81 and Davey126. Was this done on the new Fire hd 8, 6th generation? ( I have gone to the hd 8 forum, but they seem to be answering my question.)
[Fire General] DB126:
At present 6th gen HD 8 can not be rooted or downgraded. However, the Google Play Store and associated services

can

be installed. See here, here or here. Same info/procedure, slightly different presentations. Enjoy.
[Fire General] RedsonRising:
Read through the thread, this question has been asked 2x and answered.
[Fire General] BobCat78:
Morning gents,

Just wondering if anyone knows if its possible for the custom launcher and no lockscreen adverts mods to work without the downgrade and root?

Ta very much
[Fire General] DB126:
- custom launcher yes (Nova only)

- lockscreen ads no (return after a few days)
[Fire General] BobCat78:
1 outta 2 is better than none!

So just use the same sideload adb mods as posted elsewhere in the sub forum?
[Fire General] BobCat78:
You are a scholar and a gent, sir

Many thanks
[Fire General] DB126:
Not sure about the former; never made it to Darwin's waiting room...rejected at the door. :)
[Fire General] 3ch01c:
Not sure if anybody else is banging their head on this, but I kept trying to launch Kingroot from the search bar and it would crash during the "Checking" step. When I finally launched from Home screen, it detected device and attempted to root. Downgrade worked fine. Now just need root to succeed...

UPDATE: Failed root twice with Supertool Kingroot, then tried with Kingroot 4.9.6_151, failed, clicked request research, clicked retry, and success!
[Fire General] Strawberry-27:
When i open supersu after rooting it says it needs to update binary... should i cancel or continue with update ?
[Fire General] DB126:
Continue with update. Select 'normal' method if prompted.
[Fire General] my2k2zx2:
Thank you, tried about 15 times without success with the supertool version, saw your post and tried the 4.9.6_151 version and it worked on the first try.
[Fire General] pietro_spina:
Success following post #2 an #6

Thanks all!

I had success following the comments in post #2 and #6 (my device had arrived recently and sat for a day and updated to 5.3.2 OTA.)

When it came to installing flashfire, instead of using the one that came with supertool I chose to install it from the play store (after using supertool to install the store)
[Fire General] ieatabiscuit:
Ok, I've followed the video, and things said on here precisely, and I get error: device '(null)' not found every time I go to sideload. I only get this when in recovery, and in ADB sideload option from that menu. I have ADB control while the tablet is on, but not once I enter recovery, and beyond. Am I just not holding it right, should I sing to it? What'd I miss here?

Update: Clearly I was not holding it right. I have it working now, and I think it was a crap USB cable after all.
[Fire General] DB126:
Yep - sketchy cables are a common culprit. Glad you got it sorted (and didn't have to sing).
[Fire General] kyrtap82:
[MENTION=5338410]macmandarrell1[/MENTION] That video was quite good. With it, I was able to downgrade and root my device. Had to restart Kingroot 4 times, then it worked. So if anyone else is doing this: Just try over and over again, sooner or later it works.

I now have #SU, no ads, Nova launcher as default, Play Store installed, and OTA-updates disabled. Woohoo.

Thank you very much.

P.S. I was going to quote your post, but as a new user I cannot post links yet. :p
[Fire General] BSH1969:
Here's where I'm getting stuck: when I enter the "apply update from ADB" step, where the Kindle goes into adb sideload mode. At that point, the device is not recognized on my computer. I tried updating drivers every which way, and it will not show up in ADB. Instead of seeing the Fire Android device under the device manager, when it goes to sideload, I get KFFOWI under "other devices" and still can't apply a driver that gets the device accessible.

I'm on Windows 8.1 Enterprise, and I've had the worst time getting the Kindle to show up on the computer in any way.
[Fire General] BSH1969:
Finally got it sorted out, thanks to sd_shadow's driver instructions here.
[Fire General] srohang1:
Thank you for this as well as RootJunky and SuperUser on youtube for their videos. Successfully rooted, no ads, NovaLauncher, flashfire, better in every way possible.
[Fire General] MugiBoy:
I have tried to install CM12.1 and Unofficial SlimLP 0.15 (20160321) without much luck.

Downgraded from 5.3.2 to v5.3.1 and rooted (after a few tries) with KingRoot 4.96, installed SuperSU and FlashFire.

However when I try to flash the device I received the message "Can't install this package on top of incompatible data. Please try another package or run a factory reset". After that message mini_gapps are installed without any issues.

I ensured "Wipe" option was selected.

Have anyone experienced this?

Thanks! =)
[Fire General] DB126:
Yep - pay attending to flashing instructions in rom thread OP, specifically wipe operation. Must be moved to top of operations sequence just prior to flashing. Can't install a custom ROM over FireOS without clearing system partition first.
[Fire General] MugiBoy:
Thanks a lot Davey126!! It worked =)

I thought about that before but didn't manage to change the order until now (I had to RTFM) :silly:
[Fire General] Samson Lau:
5.3.2.0 is possible downgrade back to 5.3.1.0 by adb sideload.

5.3.2.1 arrived as well. This cannot root by Kingroot & cannot downgrade.
[Fire General] Stuckagain:
My fire tablet updated to 5.3.2.1 :crying: have you tried downgrading from 5.3.2.1 Samson Lau ?

If so can you tell what happened please
[Fire General] steve8x8:
That's bad news, but there's no hint of 5.3.2.1 on the firmware download page yet? (I had ordered a fire back on Black Fri which just got packed and shipped today... this may become a photo-finish... will make sure it won't see any open wifi.)
[Fire General] toyotajon93:
Hey everyone, ok I admit I forgot I had automatically received the 5.3.2.1 update. I proceeded to try and downgrade it to 5.3.1. Everything seemed to work fine no errors with anything. When I went to reboot after downgrade nothing happens. I can hear the USB turn on if my pc volume is up but nothing comes on screen and nothing happens. I cannot get to recovery or anything. Is it time to order a new kindle?
[Fire General] DB126:
Although it is possible the downgrade failure was a fluke more likely Amazon introduced a bootloader change, intentional or not, that effectively invalidates rollbacks. Amazon will exchange it if still within warranty.
[Fire General] toyotajon93:
Yep, been rooting since androids first came out haha never bricked anything until now. Does that loop where not even recovery loads means it is dead? Luckily it is only a week old so I can easily return. Hopefully get a version I can root right away.
[Fire General] DB126:
Likely (albeit unproven) a bootloader incompatibility which comes into play early in the boot sequence. If true there is no recovery short of more dramatic steps such as board replacement. Typically not worth the time/effort/expense on a low-end device. BTW - fastboot/factory cables have also proven to be ineffective.
[Fire General] toyotajon93:
Good to know, I will start the return process :) thanks and definitely avoid the downgrade for now.
[Fire General] Samson Lau:
Yes, I tried. It totally brick. Cannot power up anymore:crying:
[Fire General] winners_club:
I was able to root mine. I have superuser, flashfire and I was able to remove ads, and etc...

But somehow I can't install CM 12.1. I tried it with flashfire and it will wipe out the data BUT won't install anything after that. FlashFire with redbar will show but nothing installs.

GAPPS tries to install but it says not enough storage even though I have enough storage. I tried pico, nano and micro and all same results.

I tried TWRP method, but I can't even install TWRP. It says flashing not allowed when I tried installing at bootloader. adb unlock bootloader doesn't work.

I tried it for 3 hours and I'm about to give up now. Anyone can help me out on this one?
[Fire General] Stuckagain:
Sorry to hear that mate, thanks 4 the head up, otherwise I would have done the same as you. I think we should send these 5.3.2.1 ( dusty bins) back to amazon. Get 5.1.3 hopefully and try again, this time with no WiFi :)
[Fire General] DB126:
Follow flashing instructions in the CM 12.1 OP (here). Likely failed to move wipe action to top of operations sequence before flashing. Note: FF 0.53 is fine and preferred.

TWRP is a no-no on all but the earliest builds of this device. Recommend GAaps nano to insure sufficient space in system partition for silent updates to Google components.
[Fire General] amti366:
Hi,

I need some help with a new Fire tablet that I have just purchased and trying to root. I have used the supertool in the past to root another fire tablet with this same build without much problems (just a couple of reboot during root or couple of tries if it does not root the first time). But this tablet is being exceptionally harder.

here are the details of the tablet:

Your device is running Fire OS 5.1.3 (Build date: March 30, 2016)

Fire OS 5.1.4 (544271020) is ready to install

I tried using Kingroot 4.9.6 and 4.9.2 that came with the supertool. both versions keep failing. both versions start the root process and then restart at around 16%. After reboot I go back into Kingroot by opening the app and it continues from where it had restarted (for example 16%) it then restarts again at around 30% and on launching app again tries till 40% then gives root failed.

here is what Kingroot shows me when it starts:

KFFOWI

5.1.1

I would really appreciate any help as right now i am trying to make sure not to enable wifi except when kingroot asks for it while trying to root. really worried of automatic update making the tablet unrootable.

Thanks,

Matt
[Fire General] jorzilin:
Same here unfortunately. Rooted 2 earlier ones without any problems, the new colored ones that arrived this week (one blue, two orange) just won't work with KingRoot. I have noticed that they had stock 5.3.1 installed, but a later build from September 22, 2016. Something must have been done by Amazon...
[Fire General] DB126:
Unlikely Amazon has 'done something'. FireOS 5.3.1 does not always root easy. Keys to success:

- perform a 'factory reset' from the stock recovery menu

- if you have attempted a prior root reload FireOS 5.3.1 via adb sideload (optional but sometimes helpful)

- on initial reboot do not register device with Amazon

- try various Kingroot builds obtainable from APKMirror: 4.85, 4.92, 4.96 (avoid 5.x series)

- make sure device is actually connecting to AP (enable WiFi and do a quick web search)

- if failure repeatedly occurs at the exact same location try desktop build of Kingroot

Patience and a little creativity are virtues. Sep 22 '16 FireOS build has been successfully rooted by others. Good luck!
[Fire General] amti366:
When you say 5.3.1 you actually mean 5.1.3? that was the version mine showed out of the box it still says 5.1.3 and ready to upgrade to 5.1.4
[Fire General] DB126:
Sorry for the oversight (not your fault; working through my 7th year of Literacy 101). FireOS 5.1.3 can not be rooted. You must rollback to 5.1.2 or update to 5.3.1; both of those can be successfully rooted. See this thread and included video for FireOS rollback/sideload guidance. Please note: you can not downgrade below version 5.1.2; device will brick.
[Fire General] amti366:
That's weird I am pretty sure I rooted atleast two other tablets on 5.1.3 using the kingroot. I will downgrade and report back. Thanks