yashsingh1/xdaforums huggingface dataset:
[Fire General] psrose:
I turned the tablet on for the first time yesterday and it installed 5.1.1 as part of the first boot-up. Therefore to answer your question I have 5.1.1 from OTA. So, do I need to wait until there is a different version of TWRP available before I can do anything? Is there a way to get back to 5.0.1? I'm guessing doing a factory reset through the settings of the stock operating system is not going to revert the operating software version to 5.0.1, just wipe everything. Had I known this before turning the tablet on for the first time, I wouldn't have entered my wifi password during setup.
[Fire General] DB126:
- no fastboot access (and hence twrp) on 5.1.1 if installed via OTA update

- no rollback option (yet)

- factory reset does touch system partition; only data is removed
[Fire General] Pond-life:
Yeah stuck for now.

Don't try to roll back to 5.0.1 as it bricks it.
[Fire General] 87racer:
This. Can anyone else confirm 5.1.2? Don't think that is out, just checked on my OTA 5.1.1 tablet.
[Fire General] Sid-Shrunk:
Do I unterstand right? You powered up your device and it did update without wifi connection?

Does this mean new devices are actually already shipped with 5.1.1 preinstalled or the updatefiles preinstalled?

Had to return my cybermondaydevice cause of pixelerrors and have to wait for another week till replacement arrives.
[Fire General] psrose:
I don't believe it was shipped with 5.1.1. As part of the first boot-up it asked for my wifi password, and then installed the update before I ever saw the main "desktop". Hopefully, when you get your replacement it will have 5.0.1. When you turn it on for the first time do NOT enter your wifi password.
[Fire General] storkpkp:
Just a rookie question here. Is there no way to make an image that you could load with Odin to roll back to 5.0.1?

I am sure someone can tell me why that is not possible.
[Fire General] 87racer:
Not possible atm, we have the image from amazon. Sideloading results in a brick. Sp flash doesn't work on this device currently either.
[Fire General] storkpkp:
Thanks. Do you know if it is a soft brick or it is unrecoverable?

Anyone have clues as to what causes the brick?
[Fire General] 87racer:
So far, unrecoverable. Screen goes back and loops at preloader. Theoretically we could recover with mtk tools and sp flash but they dont communicate properly for some reason.

Seems to be an incompatibility in preloaders and boot/recovery or something. Maybe one of the devs can chime in but idk if anybody has made progress as they are probably just working towards root/fastboot access for 5.1.1
[Fire General] storkpkp:
Much appreciated. I was able to get a refurb with 5.0.1 so I am up and running after my original unit updated. I have never seen a device just update like that when connected. That is what I get for not checking here first.

I wish I knew more about how these things worked so I could help. Things change quick on Android systems. It is hard to keep up.
[Fire General] guut13:
Thanks for this. Worked without issue, coming from 5.0.1.

FYI - Step 1) 2. flash the update, links to a post which file isn't there. I used the file in post 4, instead. (Had to rename bin to zip, but I didn't have to unpack it first.)
[Fire General] adtamez:
Hi, if I'm already rooted on 5.0.1, can I update using this method and still adb hide Amazon bloatware?

I haven't hide any app yet but I was about to start hiding them. Should I do it prior to updating to 5.1.1 or all the bloatware will unhide anyways? If so, will I be asked to hide then again?
[Fire General] bibikalka:
If you don't do a factory reset, it should remember whatever stuff you blocked from before. If you renamed apk to block stuff (to apk_ or something), then you'll have to do it again.
[Fire General] adtamez:
Thank you. Understood.

But just to clarify further...So once I update to 5.1.1 through this method staying rooted and still with 5.0.1 bootloader there is no option to hide. You can only rename the apk? Hiding doesn't work? Or hide will work since I still will be on boot loader 5.0.1.

Because if hiding doesn't work after updating, I might as well hide all apps now since you are telling me that it should remember whatever stuff i blocked. It's just easier than renaming later.
[Fire General] DB126:
While I understand the disable/hide rational I wouldn't take that chance with the OTA apk. We all know disabled/hidden apps can be coaxed to run which would be highly undesirable with OTAs that can ruin your day. Renaming affords an extra level or protection while retaining easy reversibility. It is not a bullet proof solution as Amazon could find a way to replace/regenerate the file if they really got aggressive about OTAs. Doubt that would happen.

Bottom line: disable/hide/uninstall general purpose apps to your hearts content - but take a few extra moments to rename (or otherwise obfuscate) DeviceSoftwareOTA.apk. You be happy you do not have a sad story to tell following some future OTA that hammers privileges or bricks your device.
[Fire General] adtamez:
Excellent explanation. Thank you so much. I will do as advised and rename otas apks!
[Fire General] nEUTRon666:
General question, anyone has the same problem as me?! I have 3 fire's and on all 3 i installed the google play store and entered 3 different accounts (kids) and the play store looks like the play store for work/business. It also say's "My apps for work" if you open it, not the normal way it shows "my apps" and so on ...those 3 accounts are 100% NO apps/work/business accounts, and it's on all 3..
[Fire General] illadelph:
So.. I just flashed fire_boot_53820.zip with flashfire on 5.1.1 without realizing what I did wrong, and now my fire tablet cannot seem to boot up. Please help!:(
[Fire General] DB126:
Likely no recovery from this. As your device is within the 1 year warranty contact Amazon to secure a replacement.
[Fire General] Pond-life:
Just curious as to why you did that. Is there something in the instructions in the OP that don't make it clear enough that it's for 5.0.1 and twrp. In the interests of preventing anyone else doing the same in future it seems pertinent question.

Can you get into stock recovery? Or does it not respond to the power button at all?
[Fire General] solara1973:
Rather interesting. I recently ordered another Kindle 7 three days ago, and was delivered yesterday. It came with the 5.0.1 firmware.
[Fire General] bibikalka:
It's probably their Xmas batch made in Nov/early Dec, so no surprises ...
[Fire General] DoLooper:
This is my favorite thread! I do a lot of testing (and hanging at Fire logo), :D but I've managed to keep my 5.0.1 bootloaders through multiple restores/upgrades/rooting. Finally wrote a couple scripts to automate this and the restores (and the TWRPing!). It's great to always have fastboot and TWRP around. Thanks!
[Fire General] bibikalka:
So what are the highlights of the testing ? The battery now lasts 20 hours, and the speed is 2x of the fastest Samsung tablet ? :D
[Fire General] DoLooper:
HA! Nothing so useful. :D Just getting helpful info from dumpsys to detect bootcomplete, package enabled or disabled, root status, orientation, etc.; checking drivers; converting any launcher to priv-app; one-tap switching between Nova and Firelauncher ;). That sort of thing.

I leave Fire connected to pc all the time, through reboots into all modes, and now wonder if that may be causing regular hanging at Fire screen(?). Finally discovered that clearing cache in stock recovey menu can sometimes fix not booting, but not always, so still must restore and use your method to update.
[Fire General] savvymatthew:
I updated just like it said in the thread, Everything works.... But i cant open setting ? i hit setting, screen goes black for a sec then im back at the launcher ?

i can open open network settings by the pull down bar or whatever thats called, then i hit back i few time to get to the main settings page, but i get same results as if i hit setting from the app icon ?

Not sure what to think, i prefer not to reset the whole thing . So any help would be great.

Thanks
[Fire General] bibikalka:
If you have Root and use Titanium Backup, you should search for "setting", and try to find the exact app that you think is giving you trouble. Then you can click on the app, and it'll give you an option to wipe data. This will be a local reset for Settings. See if it works.
[Fire General] DB126:
Have you tried powering down and restarting?
[Fire General] savvymatthew:
Just tried that, I just discovered alot more problems started to appear after a few reboots, there's no lock screen, my pull down bar is gone, and setting works every other reboot it seems.

So I'm just gonna do a system restore.

My question is will that make me lose the bootloader and TWRP access ? If so what's the best way of restoring without losing that ?

Thanks,
[Fire General] DoLooper:
These are unusual problems, so please be absolutely certain you were running 5.0.1 before you did the update.

Assuming you *were* running 5.0.1, that's what you'll restore and you'll have TWRP access (via fastboot booting TWRP) to do the update to 5.1.1, and then ongoing TWRP access. (On the other hand, if you were originally running 5.1.1 and restore 5.0.1 your tablet will explode.) :D I've done this a half-dozen times so am writing up a few things to keep in mind in case you haven't done it before.

1. Enable firelauncher if you had it blocked: adb -d shell "su -c 'pm enable com.amazon.firelauncher'"

2. Turn off wifi. (Amazon will try to OTA update as soon as 5.0.1 boots)

3. Reboot recovery, go into "adb sideload" and sideload your 5.0.1 bin file (I use the latest 5.0.1, but the earlier is ok too)

4. Factory reset if you want to start with a clean slate (which seems like a good idea)

5. Reboot and block OTA the second you see lockscreen:

. . adb shell pm hide com.amazon.device.software.ota

. . adb shell pm hide com.amazon.otaverifier

6. Make sure wifi is still off (May have to say continue, then "complete setup later" at setup screen)

7. Follow the OP to update, keeping 5.0.1 bootloaders, and get root and gapps.
[Fire General] savvymatthew:
As long as there wasn't an update in between 5.0.1 to 5.1.1 ( there wasn't a 5.1.0 was there ? ) I figured there isn't one cause a custom recovery only works on 5.0.1 right ?

So I can't just hit the system restore botton in the settings ? Or will I lose the bootloader ?

A yeah I had the fire launcher completely deleted before I even attempted to update to 5.1.1 using the method in the thread ? Could that be why things got messed up?

I don't understand why the fire launcher has to be enabled when I flash back to 5.0.1 ? I didn't disable it after I updated to 5.1.1 but before like I said I deleted it on whatever firmware I was on ( assumeing 5.0.1 ) prior to attempting to upgrade.

Thanks so much for that step by step guide, that's gonna be very helpful if/when I have to flash everything back.

Just to be clear a system restore is not possible ? Or am I really gonna have to backtrack everything I did ?
[Fire General] DoLooper:
What I describe is a restore. [Edit] I've not done a reset with 5.1.1 loaded, so can't say what outcome will be. Perhaps I misunderstood what you wanted to accomplish. You only need to redo all you did If you want a guaranteed properly working system. :D
[Fire General] savvymatthew:
I ended up trying a system restore on the fire tablet itself cause well you said you haven't tried it so thought i would :) . It seemed to have fixed most of my problems, Google play was still there and SuperSU with root survived the restore. :)

There are ads again on the lock screen, but at-least theirs a lock screen now !!! lol

Oh and it didnt write over the boot-loader, so I am still on a 5.0.1 Bootloader with 5.1.1 firmware, ( can confirm, Still but up a custom recover )

Im just gonna go ahead and try to change to a different launcher and disable updates, Hopefully that doesn't break anything to much :)

Thanks for you help
[Fire General] DB126:
Amazon's native system restore wipes the cache, dalvik and data partitions. It does not 'refresh' the system partition (pros/cons) or mess with the bootloader. Although the system partition is largely untouched a factory reset can render the device unbootable due to missing, changed or 'corrupt' (including permissions) components.

Glad it worked for [MENTION=4412194]savvymatthew[/MENTION]; others should consider the potential consequences before rushing to reset. Best try other options first, at least for now.
[Fire General] fuzzynco2:
method question

Can I:

transfer the 3 zips to the microsd card with MTP

then use Supertool to boot to TWRP

1) flash update-kindle-full_ford-37.5.4.1_user_541112720.zip

2) flash fire_boot_53820.zip

3) flash SuperSU-v2.46.zip

and then reboot to the updated, rooted 5.1.1

then run supertool to block OTA updates,

and reinstall google play store?

We figure the ROM changing requires redoing

whatever package manger changes were done for 5.0.1?

the fire_boot_53820 put back the 5.0.1 pre boot loader and bootloader,

so telling supertool its 5.0.1 should work.
[Fire General] DB126:
IDK - and don't want to spend time thinking though it including potential problems/perils. Suggest following guidance in OP as it is quick, easy and proven.
[Fire General] bibikalka:
Added a comment on 5.1.2 . See the top of post #1.
[Fire General] rameses:
Just to add my experience to this, I've followed the OP and upgraded from 5.0.1 to 5.1.2 without any issues. All is good, I'm currently playing with the blue light filter. :)
[Fire General] scoggy:
I've currently got an unrooted Fire Tablet on 5.1.2. If I've understood the first post correctly I can follow those instructions to downgrade to 5.0.1, and can then root etc. Is that right?

I've read elsewhere on XDA of others bricking their tablets when trying to rollback the firmware from 5.1.2, and haven't seen anyone manage to do it successfully.
[Fire General] DB126:
Any attempt to rollback will result in a brick. Instructions in the OP are for devices that started with FireOS 5.0.1. This version had unique capabilities (twrp access) relative to later releases. Some users wanted to upgrade FireOS while retaining earlier capabilities. The end result is a hybrid of the two versions (somewhat simplified explanation).
[Fire General] scoggy:
Thanks for clearing that up - glad I checked!
[Fire General] realsnet:
I just got the device with 5.1.2 on it brand new. Is there anything at all I can do with it or have to wait?
[Fire General] DB126:
Best wait until the dust settles. Still uncertain what can/can't be done without root on 5.1.2.
[Fire General] SteveBozz:
Tried it but doesnt work

My tablet is already 5.1.2 and I've tried that method but there is a problem. When I try to install TWRP on my tablet this shows up:

downloading 'boot.img'...

OKAY [ 0.266s]

booting...

FAILED (remote: unknown command)

finished. total time: 0.281s

and on the tablet:

USB Transferring...

USB Transmission OK Time: 249ms Vel: 31764KB/s
[Fire General] DB126:
What method? You didn't quote a post. Regardless, you can't "install" twrp on this device as the bootloader remains locked. Twrp can be booted on devices if the bootloader version is 5.0.1 or lower.
[Fire General] SteveBozz:
How do I know the version of the bootloader? The devices got OS 5.1.2 and i have full access to the bootloader. I have tried to boot TWRP with an ADB/fastboot kit, I think it is listed at the beginning of the thread (http://xdaforums.com/showpost.php?p=63635664&postcount=9).

Many thanks in advance!
[Fire General] DB126:
If you are on FireOS 5.1.2 and took no special precautions to preserve an older version of the bootloader then you can not use TWRP. There is no mechanism to query the bootloader version directly nor can you rollback to an earlier version (instant brick). Although 5.1.2 can be rooted the procedure remains a work in progress with further challenges if you want to use FlashFire to install a custom rom. In your shoes I would wait a bit until the dust settles. Monitor other forum threads for updates; this thread holds no further benefit unless you acquire another device with an older bootloader.
[Fire General] gdroid666:
why would anyone want to update to 5.1.2 if they are running a custom rom? what is the benefit ?

is there any benefit to update if you are using a custom rom? or in 5.1.2 fire OS?
[Fire General] DB126:
FireOS version is largely irrelevant when running a different ROM. However, every ROM has direct/indirect dependencies on the bootloader and kernel which can only be updated by installing the complete FireOS package on this device as the bootloader remains locked. At present there is no benefit updating these components to 5.1.2 or whatever and several disadvantages. But there may come a time when that changes.
[Fire General] Bobboman:
here is a weird one, i turned off updates, but for some reason i have 5.1.2 and have working gapps (installed gapps before it randomly updated to 5.1.2)

is there any way to install CM12.1 or am i SOL because my fire tab has a mind of its own
[Fire General] DB126:
Several scripts and user posts used a flawed method for blocking updates. Fixed in latest versions but that doesn't help you now.

You likely lost root which may eventually impact GAaps functionality on FireOS depending on method of installation. Latest SuperTool supports rooting 5.1.2 which is the first step on the path to installing CM12.1.
[Fire General] Kirakat:
Supertool

Hi,

I used Rootjunkys supertool and guides to root my fire 5.1.1.

As far as I am aware I followed the instructions to block updates but it still updated to 5.1.2.

If I use the latest supertool abd root 5.1.2 and reapply the update block will the updates be blocked this time or can Amazon still update my tablet.

If I install another os such as slimrom will this stop amazon screwing around with my tablet or could they still screw it up by modifying the boot loader.

Finally (sorry this such a long list) I want to use an app such as Link2SD so that the tablet uses the SD card as internal memory. I can't install Link2SD properly as the bootloader is locked. Is there another way of getting LInk2SD working fully. Would I need to load a different os to get it to work.

Many thanks

Kirakat
[Fire General] DB126:
Early versions of the SuperTool (and other utilities) used a OTA blocming technique that was vulnerable to reversal. That has been rectified in recent updates. Reapply the block using the latest SuperTool - should stick.

Amazon cannot update your device once a custom rom has been installed. Guarenteed!

Link2SD works fine on this device and you don't need (nor ever needed) an unlocked BL to install. Just use the Playstore version. See related post below. While I only tested on Nexus and CM I see no reason why it shouldn't work with other custom roms. I believe FireOS has some native capability in this area so there may be conflicts with another SD migration/management. Can't hurt to try.

http://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/post66208155
[Fire General] Kirakat:
upertool and Supersu

Hi Davey,

Thanks for the info,

I've given the latest supertool from Rootjunkys website a go but I'm finding that SuperSu will not install the binaries.

The instructions work as per video (https://www.youtube.com/watch?v=LfxfZkI_l4I) up to where supersu installs, but as soon as supersu is installed and opens, it says 'There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you have just upgraded ro Android 5.0, you need to manually re-root -consult the relevant forums for your device'

I've tried uninstalling Kingroot and SuperSu and restarting the process from scratch. I've also tried reinstalling supersu from google play (the tablet had been previously rooted using Rootjunky's Supertool when it was running on 5.1.1)

Any thoughts?

Best regards

Kirakat
[Fire General] DB126:
Failure to update binaries usually (not always) indicates a rooting problem. As you may know Kingroot uses a trial/error approach which means the technique selected to root your device may be different than others. You might want to try rerooting and then using Supersu-me to switch over to SuperSU (vid links below). Verify root access at each stage using one of the many free root checker apps. Worse case you may have to reload FireOS (same version; don't attempt a downgrade!) and start fresh. Ugh.

https://m.youtube.com/watch?v=3O3DcpeS_Ic

https://m.youtube.com/watch?v=WevWdErXWy4
[Fire General] Dunard:
Fire OS 5.1.2 (542169020)﻿ update came out the other day. Even though there no patch to download on this version at the website. They still have the old patch there. Anyway I wasn't enabled to stop the update after rooted.

KingRoot need the full 5.1.2 support. KingRoot 5.1.1 doesn't work anymore after the 2nd Fire OS 5.1.2 patch came out.
[Fire General] DB126:
FireOS 5.1.2 arrived several weeks ago and can rooted w/Kingroot. FireOS 5.1.2.1 (note the trailing digit) appeared a few days ago. The effectiveness of Kingroot on this release has not been determined.

Which version of FireOS do you have?
[Fire General] Dunard:
Fire OS 5.1.2 (542169020) 2nd patch released. Bugs fixes. Downloaded onto the Fire OS 5.1.2 only.

The one that the website have is the update-kindle-global-37.5.4.2_user_542168620.bin > Fire OS 5.1.2 (542168620)
[Fire General] DB126:
[MENTION=7041923]Dunard[/MENTION] - thank you for the legwork on recent 5.1.2/5.1.2.1 builds a surfacing a path to root devices that received the latter via OTA. Well done, mate. :)
[Fire General] Dunard:
OK I did it. I turn off the updates on the 5.1.2 after I restore it by using the update-kindle-global-37.5.4.2_user_542168620.bin.

I use the Apps2SD to disabled the com.amazon.otaverifier, com.amazon.settings.systemupdates and com.amazon.device.software.ota. After the re-rooted. :)
[Fire General] DoLooper:
How did you restore 5.1.2 v.1 (542168620). Was this with adb sideload? Thanks!
[Fire General] Dunard:
To get rid of the 5.1.2.1 update.

//Commands.

cd "C:\Users\(Name of the account)\Downloads\AmazonFire5thgenSuperTool\files"

adb devices

adb.exe sideload "C:\Users\(Name of the account)\Downloads\update-kindle-global-37.5.4.2_user_542168620.bin"

pause

cd "C:\Users\(Name of the account)\Downloads\AmazonFire5thgenSuperTool\files"

adb devices

adb install "C:\Users\(Name of the account)\Downloads\(Name of the installer).apk"

pause

//Downloads.

http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool < Download the tools.

Apps2SD download from here. https://apkpure.com/apps2sd-all-in-one-tool-root/in.co.pricealert.apps2sd

//Read here.

Do a reset to default settings. Let it erase. Hold Vol left and Power after that. Let go the Power after the menu come up. Pick sideload. Load up the cmd and then put in those command. Wait until it is finish re-installing. Don't sign into your account. Don't turn on the WiFi yet. Install KingRoot and then turn on the WiFi. Let it root your devise. Take some time. Even when it fail. Keep trying. After KingRoot rooted your devise. Install the SuperSU next. Now the SuperSU gonna ask you to install the update. Install the update. After the reboot turn off the WiFi. Download any of the Apps2SD free version. Install it using the adb. Go to Link apps to SD card on the Apps2SD. Find these.

com.amazon.otaverifier

com.amazon.settings.systemupdates

com.amazon.device.software.ota

Disabled those. This will turn off the updates. Now those have different names. You click on each app to see what the apk name is. After all three is disabled then turn on the WiFi. Reboot afterward. :)

Forgot to say this. All it does is put the 5.1.2.1 back to 5.1.2. Do not use this on any version below 5.1.2 at all. Will brick your devise. Don’t even try this above 5.1.2.1. Still might brick your devise.
[Fire General] K5LK:
I just received my Fire which came with Fire OS 5.1.2 dated March 30,2016. If it is 5.1.2.1 would it say that? Will this method described work to get it prepared for rooting? I have tried the Supertool method with no luck so far.

Thanks very much.
[Fire General] sd_shadow:
if it is 5.1.2.1 it will say 5.1.2.1