Database Users

[Q] Is the Kindle Fire still "hackable"?

Hi!
I have read a few posts about the Kindle fire now being locked from rooting(if I have understood them correctly).
As I have an unopened device at home that I'm givning myself for christmas I have a few questions.
1. Is there an update that makes my untouched Kindle Fire un-rootable?
2. Will this update install automatically when connected to Wi-Fi?
3. Is it the bootloader that is locked or will it be rootable/able to install other ROM's in the future?
Would very much appreciate if someone took some time and answered these questions. I would also appreciate if someone could make some kind of summary. Read a lot on the forum but i am still a bit confused about the current status.
/Masssy
Edit: Read on some more about it and I believe that is is thr 6.2.1 update that screws things up.
Does that make me able to not enable Wi-Fi and then flash CM7 before even using WiFi on the device? That should make it fully hackable with ICS etc in the future, right?

Masssy said:
Hi!
I have read a few posts about the Kindle fire now being locked from rooting(if I have understood them correctly).
As I have an unopened device at home that I'm givning myself for christmas I have a few questions.
1. Is there an update that makes my untouched Kindle Fire un-rootable?
2. Will this update install automatically when connected to Wi-Fi?
3. Is it the bootloader that is locked or will it be rootable/able to install other ROM's in the future?
Would very much appreciate if someone took some time and answered these questions. I would also appreciate if someone could make some kind of summary. Read a lot on the forum but i am still a bit confused about the current status.
/Masssy
Click to expand...
Click to collapse
If it was me i would root it and install titanium using ADB before i connect it to wifi then freeze or uninstall the otasilentinstall app.
---------- Post added at 09:14 AM ---------- Previous post was at 09:09 AM ----------
you could rename or move the OTA certs, and change the hosts file as well if your paranoid about it.
apparantly they are pushing the update even if the device isnt registered with amazon.
Check this thread

6.2.1 breaks root and prevents the only method anybody has used so far. Another method will most likely surface. That said, there is a pre-rooted 6.2.1 ROM, the Fire semi supports android market in Silk in the latest update, and installing CM7 totally gets rid of any Amazon stuff.
You’re best bet is to disable wifi or block the amazon server in your host file.

Winglerw28 said:
6.2.1 breaks root and prevents the only method anybody has used so far. Another method will most likely surface. That said, there is a pre-rooted 6.2.1 ROM, the Fire semi supports android market in Silk in the latest update, and installing CM7 totally gets rid of any Amazon stuff.
You’re best bet is to disable wifi or block the amazon server in your host file.
Click to expand...
Click to collapse
I'm going to open it up when I am away for christmas. Although, I have no use for starting to use WiFi on it that day.
Just keeping WiFi off and then root+CM7 directly when I'm home should be smartest, right?
Edit: I'm not after the Amazon crap anyway since I'm from Sweden.

[info] new ota 6.2.2/6.3 update from amazon and how to prevent

hallo guys
just saw that amazon is pushing the next OTA - 6.2.2
this time i could again verify this method to prevent the OTA:
i deleted /system/etc/security/otacerts.zip - watched the update downloading to the cache folder but did not install - after a reboot the update file was disappeared from the cache folder - i was registered at amazon all the time - and i'm still on 6.2.1
this worked for me - no guarantee
update: worked with 6.3 again !

I assumed the file needs to be permanently removed based your post, but I renamed them to keep them around (I am glad I did)
I did what you recommended and then I rebooted (renamed instead). Once I rebooted though, GMail would crash everytime I tried to use it and the Market said it could not connect. Once I put those files back and reboooted they worked again. So any other ideas would be appreciated.

... but I renamed them to keep them around ...
Once I put those files back and reboooted they worked again
Click to expand...
Click to collapse
yes - as i wrote - i deleted otacerts.zip (only this one) from /system/etc/security/ (renamed and moved to sdcard)
i'm using the android market without any problems
sorry had a typo with the filename !

I only see cacerts.bks and otacerts.zip. Which did you delete?

sorry it is a typo - thank you !!!
it is otacerts.zip !!!
will correct the post - again thanks !

Anyone have any details about the update? What's new?

i think it's too new for detailed information and don't know cause it did not install
but i'm shure detailed information will be availabe in the next days
as well as a pure update version as it was with 6.2.1: http://forum.xda-developers.com/showthread.php?t=1407852

I can't delete the file. I have ES File explorer with su privileges... Voodoo is set so I am rooted... I have read/write checked in settings. Is there something I'm missing?
EDIT: Never mind, I just got it. Sorry! Hopefully this works. Has anybody done this and had it update on them?

DalekCaan said:
I can't delete the file. I have ES File explorer with su privileges... Voodoo is set so I am rooted... I have read/write checked in settings. Is there something I'm missing?
EDIT: Never mind, I just got it. Sorry! Hopefully this works. Has anybody done this and had it update on them?
Click to expand...
Click to collapse
don't know - sorry - but for me it's the second update i survived

Tried this, will be cheering/complaining loudly, depending on how it goes
Probably a silly question, but I suppose if we get the OTA that knocks out recovery as well?
Edit: Perhaps a sillier question, but does having TWRP prevent the OTA anyway? Usually the OTA is flashed via stock recovery, no?

It should wipe everything.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

podspi said:
Tried this, will be cheering/complaining loudly, depending on how it goes
Probably a silly question, but I suppose if we get the OTA that knocks out recovery as well?
Edit: Perhaps a sillier question, but does having TWRP prevent the OTA anyway? Usually the OTA is flashed via stock recovery, no?
Click to expand...
Click to collapse
The OTA updates thus far typically overwrite the filesystem, so yes it would knock out recovery. You can use a "patched" ROM that will not touch the partition the recovery data is on.
TWRP does not stop OTA amazon updates if you are running the stock amazon ROM, as it operates at a level outside of the operating system. However, you can use TWRP to load an alternate operating system aka ROM, such as CM7 which would not be subject to amazon's OTA updates.

jshaw49 said:
Anyone have any details about the update? What's new?
Click to expand...
Click to collapse
One thing I've noticed is that it mounts a lot faster when attached to my PC via USB. On 6.2.1, it mounted in about 10 seconds. Now it does it in less than 2.

DesDr0id said:
TWRP does not stop OTA amazon updates if you are running the stock amazon ROM, as it operates at a level outside of the operating system. However, you can use TWRP to load an alternate operating system aka ROM, such as CM7 which would not be subject to amazon's OTA updates.
Click to expand...
Click to collapse
Thanks for this. Exactly what I was looking for (I'm fairly new to rooting).
Sent from my Kindle Fire using xda premium

Just wanted to say that I tried this, and as far as I can tell it worked like a charm. I even tempted fate by hitting 'Sync', but my Kindle refused to update (it wouldn't even attempt to download the update from device settings).
I just flashed the pre-rooted 6.2.2 update and deleted otacerts.zip, so here is hoping they didn't change something to make this not work...

i'm glad that it is working for you too ...

I just wanted to add that I have been blocking the OTA update using Droid Wall. Still running very happy on 6.2.1.
The only down side to this method is having to set permissions initially then updating Droid Wall as I install apps.

Meh. I'm not sweating this update much.
I've still got the Market, still have Swype... Sooooo far as I can tell the only thing I lost is Google Currents, which I wasn't finding much useful since the KF doesn't seem to want to let it sync while I'm not around.
Sooooo sooner or later I'll get the Burrito running again, but I'm in no rush.

FIREMOD replaces BURRITOROOT
http://forum.xda-developers.com/showpost.php?p=21595398&postcount=105

as i am fairly familiar with the rooting process I am okay with amazon pushing update OTA, but some of my friends are complaining and I have to help them root their devices again after OTA update. So if this OTACERTS.ZIP deletion actually works (without other consequences) then I will surely recommend this to my friends

Kingroot not working today?

Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root

positivehxcgo said:
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
Click to expand...
Click to collapse
just try kingroot 4.1 (New Version)
has worked for me
LG Noah

Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?

jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
There is no official download for 4.5.4 yet, did you get it OTA ? If so, it's a big warning for everybody out there to disable the OTA updates!!!
Most likely Amazon fixed the Kingroot exploit, so I'd be actually surprised if 4.5.4 is rootable via the same approach as before.
Fellas, cherish the root that you got, and don't even think about updating !!!

Is there any way to downgrade to 4.5.3 without going through Amazon?

what is the command line to disable auto update ?
and does it auto update ?

alucard_xs said:
what is the command line to disable auto update ?
and does it auto update ?
Click to expand...
Click to collapse
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.

jmz said:
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
Click to expand...
Click to collapse
Thanks so just adb to my device and this command line is enough ?

alucard_xs said:
Thanks so just adb to my device and this command line is enough ?
Click to expand...
Click to collapse
yes. I dunno if it gets reset on boot or not. I think it does.
My tool also does
Code:
mv /system/priv-app/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA.apk.bak

Yeah it was an OTA update. Literally just as is was getting my laptop out to block them

otaverifier stays blocked with boot
jmz said:
yes. I dunno if it gets reset on boot or not. I think it does.
Click to expand...
Click to collapse
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.

DoLooper said:
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
Click to expand...
Click to collapse
Ok. I wasn't sure.

what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?

alucard_xs said:
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
Click to expand...
Click to collapse
Code:
adb shell pm block com.amazon.otaverifier

Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted

CrazyRach said:
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
Click to expand...
Click to collapse
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time

jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?

bibikalka said:
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
Click to expand...
Click to collapse
i actually had my device proxied via burpsuite while contacting support and them conducting the rollback but wasnt able to capture anything
one interesting thing i noticed while having the hd6 proxied is that the silk browser constantly tries to phone home to internal.amazon.com

blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.

CrazyRach said:
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
Click to expand...
Click to collapse
apologies for the delayed response,
ive been dealing with a serious injury over the past few days.
i just went and told them that after updating to 4.5.4 i was having issues with the screen flickering and glitching, and system lags that persisted across factory resets.
if i have the time to try later im gonna see if i can get them to roll back one of my other devices while monitoring my entire network this time vs just proxying the device via burpsuite like i did before, then perhaps this may shed some light on the rollback/upgrade process

[How To] Downgrade to 4.5.3 so you can root device

Step by step instructional video
Help setting up adb for windows: https://www.youtube.com/watch?v=CyJlmTtLsIg
If you are already running Fire OS 4.5.3 and below, all you need to do is follow this video to root: https://youtu.be/KcQ30qcImJc
Steps:
1. Install the Fire OS 5.0 developer preview. EDIT: Do not do this. If you already have a lollypop ROM installed, use that instead of installing dev preview (You could cause a brick)
2. Enable ADB on your device and set up ADB on your computer
3. Download 4.5.3 firmware: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin (Mirror coming soon. This download works for the Fire HD7 and HD6)
4. connect device to computer and run "adb reboot recovery"
5. use volume keys and power button to navigate to "Apply update from ADB"
6. from computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
7. from tablet select "wipe data/factory reset"
8. from tablet select "reboot system"
9. Complete setup (do not connect to a wifi network yet)
10. Download KingRoot: http://www.kingroot.net/
11. Download JmzFireHDTool: http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655
12. install both apps. "adb install KingRoot-4.1.0.249-release-nolog-201505211812_105001.apk" and "adb install JmzFireHDTool_v4.apk"
13. Temporarily disable otaverify via adb "adb shell pm block com.amazon.otaverifier" (spelled wrong in video)
14. Connect to wifi so that KingRoot can work
15. Open KingRoot on your device
16. press "try to root"
17. re-enable otaverifier "adb shell pm unblock com.amazon.otaverifier" (spelled wrong in video)
18. Open JMZ Fire Tools and press "Disable OTA's"
Note: If you ever need to upgrade back to lollypop, you should follow these steps so you do not brick device: http://forum.xda-developers.com/fire-hd/general/tools-fire-hd-67-rooting-gapps-t3371242/page4

Awesome find !!! Here is a direct link to the 5.2.0 update file:
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
After the downgrade, install TWRP, and upgrade to 4.5.4 but this time with root and fully working GAPPS:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
This way one goes directly to SuperSu, and a clean device with no traces of KingRoot.

bibikalka said:
Awesome find !!! Now, can you install TWRP, and try to upgrade to 4.5.4 while keeping root as per this post:
http://forum.xda-developers.com/showpost.php?p=61329063&postcount=4
This way one goes directly to SuperSu, and a clean device with no traces of KingRoot.
Click to expand...
Click to collapse
ah yes good idea. I'm hoping someone with ROM development knowledge will start a build. We've got just about everything setup so that a custom ROM can run
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
ah yes good idea. I'm hoping someone with ROM development knowledge will start a build. We've got just about everything setup so that a custom ROM can run
Click to expand...
Click to collapse
The tricky part is that the unlocked bootloader still needs a signed kernel. Which is pretty constraining. It'd be interesting to replace the boot preloader, but the risks are high.
Upon boot (if connected to PC), the system flashes MT65xx pre-loader. Which seems to indicate that one could start looking into programs such as "Smart Phone Flash Tool" and "MTK Droid Tools" for MTK chipsets.
Another hope is that the 5.0 version would be sufficiently buggy, such that the bootloader can be made to boot unsigned kernels.

bibikalka said:
The tricky part is that the unlocked bootloader still needs a signed kernel. Which is pretty constraining. It'd be interesting to replace the boot preloader, but the risks are high.
Upon boot (if connected to PC), the system flashes MT65xx pre-loader. Which seems to indicate that one could start looking into programs such as "Smart Phone Flash Tool" and "MTK Droid Tools" for MTK chipsets.
Another hope is that the 5.0 version would be sufficiently buggy, such that the bootloader can be made to boot unsigned kernels.
Click to expand...
Click to collapse
Hashcode has gotten around this issue multiple times with something called a bootstrap but I'm not too sure how it works
Sent from my LG-V480 using Tapatalk

Btw, any chance you could post the direct link to 5.0 preview (for non-developers), since it's probably behind some registration page or something ...

i just signed in with my amazon account, you will need to unroot your fire and reset it as 5.0 is a OTA.

bibikalka said:
Btw, any chance you could post the direct link to 5.0 preview (for non-developers), since it's probably behind some registration page or something ...
Click to expand...
Click to collapse
I wish I could find that bin file link... I looked for it but could not find a link to the actual bin file.. If ota's download to the sdcard then It could still be accessed but I don't know where it downloads to. If it downloads to the data dir of the app it would be inaccesable since you need to be on the latest update in order to download the 5.0 version and on the latest version we have no root which means no access to data dir
Sent from my LG-V480 using Tapatalk

this is a great find. but stupid me only have a macbook pro and i cant set up adb. sucks..

edgar.vrgs said:
this is a great find. but stupid me only have a macbook pro and i cant set up adb. sucks..
Click to expand...
Click to collapse
you can set it up on a mac. Just do a little searching. I know it's plausible
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
you can set it up on a mac. Just do a little searching. I know it's plausible
Sent from my LG-V480 using Tapatalk
Click to expand...
Click to collapse
i have tried but i cant figure it out

It worked perfectly. Thanks

Despite really wanting root and the possibility of using my already paid for apps from the Play store, I really like the lollipop version of fire os. I do think it's a bit ridiculous they haven't retained the old kindle skin because it's exactly how every real android tablet looks but at this point they should be forced by law to let people use the Play store as they wish. Sort of like how Verizon was once forced to allow tethering without a subscription.

devicer said:
It worked perfectly. Thanks
Click to expand...
Click to collapse
great to hear it!
Sent from my LG-V480 using Tapatalk

bpeery84 said:
Despite really wanting root and the possibility of using my already paid for apps from the Play store, I really like the lollipop version of fire os. I do think it's a bit ridiculous they haven't retained the old kindle skin because it's exactly how every real android tablet looks but at this point they should be forced by law to let people use the Play store as they wish. Sort of like how Verizon was once forced to allow tethering without a subscription.
Click to expand...
Click to collapse
I hear ya
Sent from my LG-V480 using Tapatalk

so i finally got adb on my mac to work, but now when i am on the last command to install 4.5.3 terminal says it can't read update-kindle-20.4.5.3_user_453011120.bin
has anybody done this on a mac and would like to guide me on what i am doing wrong?

edgar.vrgs said:
so i finally got adb on my mac to work, but now when i am on the last command to install 4.5.3 terminal says it can't read update-kindle-20.4.5.3_user_453011120.bin
has anybody done this on a mac and would like to guide me on what i am doing wrong?
Click to expand...
Click to collapse
does adb devices list your device. Maybe try re-downloading the update in case of corruption
Sent from my LG-V480 using Tapatalk

Perfect timing! Lost root last week and hoped for a way to get back. You the man

I wonder if there is a way to stop the update once it's downloaded, in order to grab the 5.0 update bin from /cache.
This would help to re-pack the update in a way that does not re-write key partitions, then one can have TWRP and root on 5.0
It does sound like 5.0 is a nice update, since it provides stock Android. That's what custom ROMs are usually for, but Amazon will give it away !

bibikalka said:
I wonder if there is a way to stop the update once it's downloaded, in order to grab the 5.0 update bin from /cache.
Click to expand...
Click to collapse
I was wondering the same. Seems like you could rename the otaverifier apk back to (plain) .apk and get the download but by keeping com...otaverifier blocked it wouldn't install. I'm just not sure these developer updates are handled like any other.

Amazon FireOS System Updates from 5.1.4 to 5.3.1.0 released.

Came out on July 14, 2016 10:30 PM. There is no bin file at this time.
Note: Don't try to downgrade from this. Might brick your FireOS. Need a report on it actually works or not first.
Cannot be rooted. Tested with NewKingrootV4.95_C149_B285_en_release_2016_07_15_105203.apk

Comment moved to different post. Sorry new to forum

Tip: If you log in on the Amazon it gonna try to update the system automatic. Don't log in then it gonna ask first after the download.

It wouldn't let me past the splash screen without logging in

Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!

Venio2000 said:
Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!
Click to expand...
Click to collapse
I don't recall that anyone posted anything about the new release. You should just wait until the resident experts chime in with some guidelines.

fmc000 said:
I don't recall that anyone posted anything about the new release. You should just wait until the resident experts chime in with some guidelines.
Click to expand...
Click to collapse
I will - I just wish I would have waited longer with the update, but it was brand new and said: update me now
Thx for any help/ Info

I used the 5.1.2 bin file and installed adb drivers on my windows computer. I used a program called minimal adb and fastboot. I opened minimal adb and fastboot, powered on fire by holding volume down and power until bootloader. Selected apply update from adb. Typed ' adb sideload' and dragged the bin file into the window of minimal adb and fastboot. Hit enter and watched it climb to100%. This was from 5.1.4 and 5.1.3. I do not know if it will work going down from 5.3.1.0. the fire is a piece of crap with the stock amazon installed imo

Venio2000 said:
Anybody knows how I can get 5.1.2 back on my updated 5.3.1.0. Fire?
I tried the Downgrade to Fire OS 5.1.2. Supertool, but all I get is the => Fastboot mode... screen.
When I restart again its still 5.3.1.0.
I am totally new to this, so I may miss something
Thank you for any help!
Click to expand...
Click to collapse
What is the date of your 5.3.1.0 FireOS ?
This thread is your friend :
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
You would try to sideload the 5.1.2 (the last version that's rootable at the moment). There is a chance the downgrade would brick (due to the possible higher version of the newer bootloaders ), so be prepared to send Fire back to Amazon if this fails.
One option is to write the entire new system, but that would take forever since those tools are slow ...

WARNING: Do not downgrade from 5.3.1.0. Brick the device if you do.

so now we're screwed and can't root a device? Has this ever happened before? What are the odds the first device I purposely buy to try my hand at rooting something and it turns out to be unrootable after I brick the first one....

The ROM image for FireOS 5.3.1.0 has now been published on the Fire (5th Generation) Software Updates page. The filename is update-kindle-global-37.5.5.2_user_552153420.bin
http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
Determine your software version
Determine the current software version on your Fire tablet before downloading and installing a software update.
Swipe down from the top of the screen and then tap Settings.
Tap Device Options, and then tap System Updates.
If you have the latest software update, it should look like this: Your device is running Fire OS 5.3.1.
Download Fire (5th Generation) software updates
Click the link below to download the software update to your computer:
Download Software Update 5.3.1
Click to expand...
Click to collapse

fusion01k said:
so now we're screwed and can't root a device? Has this ever happened before? What are the odds the first device I purposely buy to try my hand at rooting something and it turns out to be unrootable after I brick the first one....
Click to expand...
Click to collapse
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.

beezar said:
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.
Click to expand...
Click to collapse
Thanks for the advice. I will check it out when it arrives soon.

beezar said:
You're replacement probably will not have 5.3.1.0 on it, but a lower version. So if I were you, I'd turn off my wifi router to be safe before turning on the device for the first time. Then turn on my new device, skip the wifi login step on the device, and check the version number. If 5.1.4 or below, you should be able to downgrade (if need be) and root. Then shut off OTA updates. Then you can turn on your router/wifi etc.
Click to expand...
Click to collapse
For those without a bricked device, just one on 5.3.1.0 and still want to root is it best to just sit tight then and wait on a work around?

jmorlin said:
For those without a bricked device, just one on 5.3.1.0 and still want to root is it best to just sit tight then and wait on a work around?
Click to expand...
Click to collapse
Well there doesn't seem to be another choice. A "work around" may come tomorrow or never. Seen both scenarios play out.

bibikalka said:
One option is to write the entire new system, but that would take forever since those tools are slow ...
Click to expand...
Click to collapse
@bibikalka what tools are you referencing here? And how to write entire new system?

beautiful3cellar said:
@bibikalka what tools are you referencing here? And how to write entire new system?
Click to expand...
Click to collapse
Sorry, that's not correct It looks like Amazon patched the hole that allowed AFTV2 tools to work. Since these tools don't work with FireOS 5.3.1, even the slow path is not available

bibikalka said:
Sorry, that's not correct It looks like Amazon patched the hole that allowed AFTV2 tools to work. Since these tools don't work with FireOS 5.3.1, even the slow path is not available
Click to expand...
Click to collapse
AFTV2 Tools works below OS 5.3.1 though?

beautiful3cellar said:
AFTV2 Tools works below OS 5.3.1 though?
Click to expand...
Click to collapse
I think the last version was 5.1.1. The tools don't work in 5.1.2 . Amazon replaces the preloader with each update, so they can fix it quite easily.