yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] ulises.rodriguez:
So, there is a new FireOS 5.1.2 update, for all Amazon's Fire Tablets... Great news!

Does Anyone knows what's new and when has been released?

I really hope that Amazon finally have corrected some errors that caused some programs to run very slowly, and have also optimized some functions, so that we can use the FireOS5 much faster!
[Fire Android Development] asmad:
Not necessarily a good thing. After 5.0 Amazon used 5.1.1 to lock the bootloader. Who knows what obstacles 5.1.2 will bring. After all, Amazon don't really wants rooting our budget tablets. The only way they can make money from them is by users downloading and buying Amazon products.
[Fire Android Development] :
I made the update by mistake (now I don't dare try rooting it in case it causes a brick) the only thing the changelog indicates is "general performance improvements" so there are no big new features, but if you found 5.1.1 slow you might enjoy this update. :)

I don't know when it has been released but it's really new. I got my tablet yesterday, and it didn't install it automatically, it only updated when I checked manually for updates.
[Fire Android Development] DB126:
- attempting to root poses little risk of bricking (may or may not work)

- attempts to rollback are another matter; not recommended

- roms, scripts, etc prepared for 5.0.1/5.1.1 may or may not work with 5.1.2

- I would not expect 5.1.2 to perform significantly better than previous versions

- FireOS performance issues are largely rooted in the number of concurrent processes associated with Amazon's bloated ecosystem; launch one and several are dragged into memory. Lots of background tasks and swapping. Clear them out and they come right back. As such any performance 'improvements' will be highly incremental.
[Fire Android Development] sd_shadow:
the bootloader was always lock, amazon stopped allowing booting unsigned recovery.img
[Fire Android Development] ulises.rodriguez:
Elvenstar, thanks for your quick reply!

My New Amazon Fire HD 8 is still on the FireOS 5.1.1 (Build Date: December 2, 2015), and has not updated automatically or manually... Does the new 5.1.1 has also been released for Fire HD8 (5th Generation)??

I am asking because I have searched in the Fire HD 8 (5th Generation) Software Update on Amazon, and Curiously this 5.1.2 is not mentioned nowhere:

Fire HD 8 (5th Generation) Software Updates

https://www.amazon.com/gp/help/customer/display.html?nodeId=201830200
[Fire Android Development] DB126:
Off topic - look here.
[Fire Android Development] Tomsgt:
ok fixed the mac script it works now please download and try again
[Fire Android Development] CoreOxide:
Any word on that 5.1.2 update support?
[Fire Android Development] Tomsgt:
I still havent seen that software need to get it on my device to test it out.
[Fire Android Development] drob77777:
Well, I have 2 fire tablets for my kids. I just changed the launcher and installed google the other day using Tomsgt's tool and I didn't root the tablets. Unfortunately, last night one tablet updated to 5.1.2 It put back the old launcher but ads are still blocked. On another note, I'm rooting and blocking ota right now on my other daughters tablet to save it from this disaster of an amazon lock screen. Thanks Tomsgt for the tool. Works great! Here's hoping you get the software for 5.1.2
[Fire Android Development] Tomsgt:
I wonder if 5.1.2 is downgradable to 5.1.1 if so then root is easy. if not then we will have to see what they changed in the bootloader to stop our current root method.
[Fire Android Development] DB126:
- obvious brick risk rolling back 5.1.2 - > 5.1.1 (TBD)

- unlikely bootloader is involved with 5.1.1 root exploit(s) no longer working; Amazon probably closed a vulnerability in FireOS itself
[Fire Android Development] Tomsgt:
yeah totally agree with both statements for sure. I am restoring one of my tablets to 5.1.1 so that i can take the ota update and test out this tool on it and see what we can still do.

if anyone see the stock 5.1.2 firmware please link it here thanks
[Fire Android Development] Tomsgt:
my device isnt getting a ota update to 5.1.2 and amazon isnt listing that firmware on there site yet either so i am not sure what you guys are talking about with this 5.1.2 firmware
[Fire Android Development] DB126:
Rollouts are typically staged with initial distributions throttled in case issues arise that were not detected during testing. No surprise some devices are receiving updates while others are not. Amazon has yet to post 5.1.2 download so it may be early in life cycle.
[Fire Android Development] CoreOxide:
That's strange. I'm in Israel and already got updated.

Usually North America are first, then the rest of the world - then Israel.

Still waiting for my Marshmallow update for SGS 6 :(

Can I somehow dump it to an image for you?
[Fire Android Development] Mlokz:
just downloaded it and tried it same error no matter what i try... the windows one works flawlessly though. not sure why it won't work on the mac. I have adb and everything else setup correctly so I'm stumped.. thanks though!
[Fire Android Development] snark.shark:
I've ONLY used the Supertool to install ADB and then the Google Play store on my Fire 5th Gen. No root. No fooling with the launcher.

As soon as anyone knows for sure if 5.1.2 breaks just that minimal level of system alteration, please post so. My main concern is losing access to all of those important non-Amazon certified apps.
[Fire Android Development] Tomsgt:
really i just got a mac and have tested it a couple times and it work s fine on my end
[Fire Android Development] Tomsgt:
I am pretty sure that the fastboot.exe oem append-cmdline has been removed from the bootloader and that means we have lost root on 5.1.2 I really hope amazon post the firmware so that i can check for sure. I also want to check if we can downgrade, which i am guessing we cant but still worth a look.
[Fire Android Development] ndg_2000:
Hi just a quick message

believe I have root on my kindle fire 7inch 5.1.2 using king root 4.5.0

Checked with Rootchecker pro 1.5.8

Anyone else managed with this
[Fire Android Development] bbstucki:
Update for 5.1.2

This is by far the best tool I have used to root a device. Thanks for the awesome work on this supertool.

I neglected to turn of the OTA updates and lost root and nova launcher. Can you update the supertool so I can re-root my device for Fire OS 5.1.2.

Thanks!

:good:

---------- Post added at 10:16 PM ---------- Previous post was at 10:04 PM ----------

I see this is a known issue. I will begin searching for alternative solutions. Thanks
[Fire Android Development] DB126:
As of this writing no root possible on 5.1.2.
[Fire Android Development] KnappyRoot:
I have yet to open my Fire 5th gen (got on sale and put back for kid's birthday). I should be OK to turn it on, not connect to a network so it does not update to 5.1.2, and run this tool to root and load slim, correct?
[Fire Android Development] asmad:
Yes that will work no problem. Just check if it's running 5.0 or 5.1.1 before running the tool so you can select the correct option in the tool. If it's older stock it may still be on the earlier rom.
[Fire Android Development] JadeStarr:
I followed your guide, and running 5.1.1 but when rooting the tablet, I'm stuck at the deamon runs successfully part in the script.

I've checked that I DO have ADB and Fastboot working, so can you please help me out?
[Fire Android Development] Tomsgt:
well guys its official..... oem append-cmdline has been removed from the bootloader on Fire OS 5.1.2 and our root method for 5.1.1 will not work on 5.1.2. we will need to check into something new.
[Fire Android Development] snowman46919:
Any chance at downgrading? I had rooted 2 of my 3 kindles and now I have one stuck on 5.1.2 that I would much rather have android on.
[Fire Android Development] DB126:
There is no evidence 5.1.2 can be safely downgraded...nor is their evidence that it can not. No one has reported success or failure. We do know that any attempt to rollback 5.1.1 resulted in a hard brick.

Edit: Thanks to [MENTION=4246643]Tomsgt[/MENTION] (a.k.a. Root Junky) we now know attempting to downgrade 5.1.2 -> 5.1.1 via adb sideload results in a hard brick. See here.
[Fire Android Development] BTSchuster:
Did you use the app or desktop version of KingRoot?

Has anyone else been able to verify this works?
[Fire Android Development] Dave414:
I'm pretty much a complete worthless noob with this stuff, but I did manage to use RootJunkie's supertool to install Google Play and switch to Nova launcher(Thank you RJ). Not to hijack this awesome thread, but I have a quick question. I changed the background picture on Nova launcher. Before I got the OTA updates blocked, it installed 5.1.2. :( The tablet is back to the Amazon launcher, but it still has the ugly background pic I had set in Nova. Anyone know of a way to change the background pic in the Amazon launcher.....or is it just stuck until someone (much smarter than me) comes up with these same tools for 5.1.2??
[Fire Android Development] snark.shark:
{okay never mind. I had a whole huge post here talking about how I thought the 5.11 --> 5.12 update had ruined my Google Play store functionality--literally the ONLY Fire customization I have turned on--but it's not true. Instead I had one corrupt app install that was causing the whole store to break and I misdiagnosed that as being the fault of the OS upgrade. If the Play store is the only customization you have it DOES seem to still work (I found that out after I zapped my corrupted app)--although I can't say if the Supertool could reinstall this stuff if I ever lost it off my Fire now that I'm on 5.12.}
[Fire Android Development] ndg_2000:
Did you use the app or desktop version of KingRoot? App

Has anyone else been able to verify this works? Haven't had any replies stating yes or no.

I would proceed with caution as I had root and tried to switch to super Su using a switching program and hard bricked my device so king root is as far as it goes at the moment
[Fire Android Development] Tomsgt:
did you try to use supersume app?
[Fire Android Development] Tomsgt:
yeah I just tried to downgrade from fire os 5.1.2 to 5.1.1 just for the hell of it and it hard bricked one of my devices. so do not try and adb sideload to downgrade... it will end badly. The more you know :)
[Fire Android Development] BTSchuster:
Any luck figuring out a root method?

KingRoot + Super-SuMe?

Other options?
[Fire Android Development] CamiloMed:
Kingroot says 5.1.1 not root (the apk don't detect the new version 5.1.2) and don't root... I try many times but didn't work... I don't know but after unistall the kingroot apk i see some issues whit wifi connection, no big deal but it's annoying. I hope some miracle for ours kindle fire.
[Fire Android Development] ndg_2000:
Yes and soft bricked my device

then downloaded the latest firmware from amazon website which afterwards i realised was 5.1.1 and hard bricked it

rang Amazon.co.uk and have a shiny refurbished one after saying screen did not work/ wouldn't switch on and going through "fault finding steps"......... its on 5.0.1 not connected it to wifi as yet for it to update
[Fire Android Development] tim.ton:
I can't seem to find the directions for Mac installation... am I missing something?
[Fire Android Development] ndg_2000:
Hi

Big thank you to R. J. For the super tool it worked a treat now have an ad free , rooted, gapps, kindle. Mmm now what next ? might have to look into the ROM's that are available
[Fire Android Development] duckmandm:
5.1.2 Super Tool plans for the future?

So I used the super tool on my 5.1.1 tablet and everything was great... until the OTA update that I thought was blocked was applied. I have seen the posts on using other alternative methods for re-rooting the tablet, I was just wondering if you intended to update the Super Tool for 5.1.2? Thanks in advance for all you do for the scene!

-D-
[Fire Android Development] wulfie66:
there is no known exploit for 5.12 atm afaik
[Fire Android Development] BTSchuster:
FWIW, my previously rooted Fire updated to 5.1.2 this morning. Lost root as expected, but Play Store still works and no ads. I did have to do a reinstall of a few apps because of some quirky Amazon App permission issues, but device seems to be working fine. Anxiously awaiting someone with much more Android knowledge than I have to figure out how to root again.
[Fire Android Development] duckmandm:
Thanks for the heads up, I've seen some discussion on this with some bricks reported, so I'm holding off for now. Hoping for a quick exploit to be discovered.
[Fire Android Development] DB126:
Bricks are from rollback attempts.
[Fire Android Development] xulia10:
Same happened to me. Though I had deactivated the auto update, but apparently i didn't, so it updated to 5.1.2. However, i still have no ads and both my google play and nova launcher are working. However, the launcher is working as an app, not as the default launcher.

Update: I had just posted this and the ads are back. -_-
[Fire Android Development] DB126:
Yep - the most common OTA block used a technique that is vulnerable to being overridden/reversed. The best approach (based on track record with other amazon devices) is to rename the files that control OTA operations. Some delete them; bad idea and you want a way to reenable OTA if/when needed.

I no longer have FireOS installed on any of my devices so I am loath to post specific instructions without validating the files exist on 5.1.1 which is the version most people have installed. It goes without saying that root is required to effectively block OTA. Those who have 5.1.2 will continue to receive OTA updates until (if/when) and method of rooting 5.1.2 is found.
[Fire Android Development] bbstucki:
Wugfresh toolkit?

I know wugfresh Nexus toolkit is more geared to the Nexus line, but I have used the advanced options to sideload stuff on my fire. I was able to use it to boot into fastboot and recovery mode and sideload Gapps. It has options like TWRP recovery. You can wipe and format the drive. I'm not sure what the end result would be. I was thinking wipe everything and then flash slimrom or cm. If anyone tries it would be great to hear about the results. Might be the answer to all this 5.1.12 nonsense. Cheers
[Fire Android Development] x13:
Hey

I woke up this morning to find my Fire had updated to 5.1.2, even after blocking OTA updates with the tool, so I'm guessing blocking on 5.1.1 isn't working too well!

I'm now re-rooting and blocking OTA once again, hopefully my apps will have kept the config files

---------- Post added at 08:31 AM ---------- Previous post was at 08:29 AM ----------

This and Wugfresh Nexus Root Toolkit are very similar, in that they just pipe commands to ADB, so there's in theory nothing one can do that the other can't
[Fire Android Development] DB126:
Yep - at least one of the widely published methods to 'block' OTA updates was flawed (hiding components). The only multi-device time-proven way to prevent updates is to rename the system files involved with the OTA process.

As you probably discovered 5.1.2 can not be rooted (nor future updates blocked). Hopefully a root method will be found shortly. For now those on 5.1.2 are on a forced march to whatever Amazon releases next.
[Fire Android Development] x13:
I've contacted Amazon, and they've said it is possible to downgrade, but it has to be triggered from their end. I'm going to keep trying to get that downgrade, and if I can then I'll have to look into a more permanent method of blocking OTA updates.

Does anyone have the OTA packages to attempt flashing a lower Version?
[Fire Android Development] DB126:
If you are successful in obtaining a downgrade you should attempt to capture the associated .bin file that Amazon will push to your device. It will be located in 'internal storage' (root of sdcard folder). Saving the file will allow others to rollback to 5.1.1 or whatever version Amazon pushes to your device.

Typically Amazon rollback pushes arrives within 48 hours. You will see it downloading then receive a reboot prompt to start/complete the installation. This is when you want to snag a

copy

of the file. Rename it to something benign and transfer a copy to another device (or resident sdcard) before rebooting. Do not mess with the original as you'll want this to execute on reboot. It will automatically erase itself after the install completes.
[Fire Android Development] x13:
If they agree to it I will probably airgap the tablet, set up a monitored wifi network with wireshark or something, and capture the TCP data just to be sure
[Fire Android Development] DB126:
Yep - I have lost track of how OTAs are delivered on newer devices. Previously arrived as one big file but possible Amazon is now breaking in pieces. Hopefully it's complete and not just an incremental which can prove challenging to reapply. Could also be tied to a specific MAC address or other unique identifier although I have not see Amazon use this technique. Easy enough to work around unless the package is signed. That would be a killer ...
[Fire Android Development] x13:
I've requested that they supply me with a fastboot/adb flashable package, as apparently they can't OTA-down this device; I've also requested they supply me with the necessary to re-sign the package if required, and, seeing as their English isn't great, am half expecting that to accidentally net me the key
[Fire Android Development] DB126:
Hope it works out. Typical life-cycle of similar requests is a quick (and often silent) death once it goes beyond L1 support. In my limited experience their L3 (or whatever you want to call it) capability is competent. You'll need a good explanation why 5.1.2 is not meeting your needs within the framework of FireOS and the services expected of this device type. Can't root probably won't cut it (lol).
[Fire Android Development] x13:
It's nothing to do with root, 5.1.2 broke other apps, and I want 5.1.1 back.

The L1 support agent was very nice, and has passed my email along to the "technical team" (L3 I guess?) who are going to contact me with a solution
[Fire Android Development] DB126:
What apps did 5.1.2 break? Might help others who are experiencing similar issues regardless of how they arrived on 5.1.2.
[Fire Android Development] x13:
All gApps, everything that even slightly looked at root, also it unflashed XPosed, which is a pain in the ****
[Fire Android Development] DB126:
Thank you. None of those are part of Amazon's walled-in ecosystem or benefit its business objectives. You are likely facing an uphill battle. That said, stranger things have happened; perhaps Amazon will oblige. Looking forward to seeing how this plays out. :)
[Fire Android Development] x13:
It broke a couple of apps I downloaded from the Amazon appstore as well, so we'll have to wait and see
[Fire Android Development] momonjava:
Help please...super tool not working for me

deleted
[Fire Android Development] purokogi:
Thank you.. I'm glad I blocked updates after 5.1.1 .... the supertool worked great and I'm rooted and running nova launcher. :D
[Fire Android Development] goremasta:
Nice

Have been watching this thread for a while

I'm gonna give it a shot!

thanks
[Fire Android Development] asmad:
If you're still on 5.1.1 it's simple and so worthwhile. I had to run the block updates twice. 2nd time it worked. Been ad and update free since December.
[Fire Android Development] goremasta:
thanks! I'm not sure which version that I have right now

I'm gonna find out later
[Fire Android Development] purokogi:
Not sure what happened but my changes all reverted back after some hours being left alone. I confirmed it did not auto update to 5.1.2 though so I'm redoing everything....

edit: I don't know.. the auto root is not working now.

---------- Post added at 03:53 PM ---------- Previous post was at 03:28 PM ----------

Well... I guess the OTA block didn't work when I ran it twice. My tablet is now on 5.1.2... ****
[Fire Android Development] jonathanmoneill:
Hi, is there any word on root for 5.1.2 ?
[Fire Android Development] DB126:
No progress.
[Fire Android Development] solestia:
Super Tool Upgrade?

Recently Kindle fire has been updated to 5.1.2, since then current SupperTool doesn't work.

It doesn't root to kindle fire 5th Gen anymore.

Do you have an update for the SuperTool?
[Fire Android Development] wulfie66:
there is no known root for 5.1.2 at this point in time
[Fire Android Development] solestia:
Thanks!

Is there a way to downgrade the Kindle to 5.1.1 so I can root onto it?
[Fire Android Development] sd_shadow:
no, but looks like RootKing windows version may root 5.1.2 now
[Fire Android Development] solestia:
Tried the RootKing version 3.2. No luck, it couldn't root.
[Fire Android Development] sd_shadow:
Using Version 3.2.0 Build 1128 ?
[Fire Android Development] solestia:
Yes, it looks like Kingroot has managed to root, but when I run the FlashFire, it thinks device is not rooted. I am confused.
[Fire Android Development] sd_shadow:
kingroot root doesn't play nice with chainfire apps

try supersume app

---------- Post added at 11:03 PM ---------- Previous post was at 11:01 PM ----------

rootjunky's supersume video

https://www.youtube.com/watch?v=3O3DcpeS_Ic
[Fire Android Development] zerozed99:
Is there a downside to using RootKing?
[Fire Android Development] sd_shadow:
rootking may cause some apps to force close (fc)

also rootking is kind of bloated

After rooting I suggest switching to supersu via supersume

Rootking thread

then see rootjunky's supersume video

[url]https://www.youtube.com/watch?v=3O3DcpeS_Ic
[Fire Android Development] GladOSkar:
Soo... I followed this thread for a while and wanted to share my observations, this is my first post on the forum.

I bought 2 fires for the non-profit organisation I work at, the plan was to install CM12.

Shortly after unpacking them, they started upgrading to 5.1.2, so the SuperTool doesn't work any more.

As suggested earlier in this thread, i used the KingRoot App Version 4.5.0.

On fire 1, the exploit worked on the 2nd try,

on fire 2, it worked on about the 10th try.

Just tried Super-SUme 6.0, that uninstalled KingRoot successfully, but I cannot find SuperSU afterwards. Not even in the settings app list.

Also, if I try to reinstall KingRoot, it does not reappear on the home screen, though it does appear in the settings app list.

Also, after uninstalling some preinstalled apps (that should not be needed by the system) on one of the fires, then logged into my Amazon-account and then factory resetting; Nothing works any more.

It boots to the home screen, but shows no apps at all, I can not even enter the settings or anything. I will probably be able to get it replaced by Amazon by playing dumb.

Anyway: I hope somebody has a tip for me; or I helped somebody with this.

Maybe somebody can find out what exploit used by KingRoot was successful?

Sorry for English errors, I am German :)

-Oskar
[Fire Android Development] wulfie66:
as others have posted, do NOT set up your tablet until AFTER it's been rooted. The second you connect it to wifi or any other network, it reaches out for the update
[Fire Android Development] GladOSkar:
Yeah, I guess I should have read around a little more before getting all excited and setting it up -.-
[Fire Android Development] DB126:
Good translation; would never know English wasn't your primary language :)

As noted by another poster set-up sequence is important. I would look to return both devices for a one time courtesy exchange as the foundation is now uncertain. You'll probably get a pair of refurbs with 5.1.1 (or possibly 5.0.1; sweet reward).

Other thoughts:

- only a matter of time before the nondurable OTA block used by SuperTool is circumvented; OP should update method or eliminate OTA block option

- 5.1.2 root exploit is new; not much community experience. Hopefully will be better understood by the time your replacements arrive.