yashsingh1/xdaforums huggingface dataset:
[Fire HD 6 and 7 General] bibikalka:
It is weird ... Is your network on ? Usually 5.1.1 or 5.1.2 roots fine.

If nothing else, downgrade to 4.5.3 and root that one. Block the updates the very first thing, before connecting to Wireless and trying Kingroot.

Blocking updates via adb on OS4:

pm block com.amazon.otaverifier

pm block com.amazon.dcp

http://xdaforums.com/fire-hd/general/how-to-disable-apps-services-includes-t3165348
[Fire HD 6 and 7 General] WaywardOne:
My network is on, for Kingroot, but I always make sure to monitor the notifications in case an update starts downloading. Also, my first move after rooting is always to block the OTA updates.
[Fire HD 6 and 7 General] Yevgen.A:
Just found option for my self to quit from cycle rebooting. You need to wait until device would be turned off for 2-3 sec. before next iteration of boot, then press and hold (vol+ && vol- && power) together for 15 seconds and wait until TWRP would not be loaded. I Just recently discovered that this combination boot Android device to recovery mode.

bibikalka, thank you a lot for post! It would be great if you will put in Red this point:

"9. In TWRP, after you are done with everything, don't forget to flash the 5.x.x bootloaders zip file in order to boot back into Lollipop!"

and result if you will not downgrade bootloader

Thanks
[Fire HD 6 and 7 General] doe_eyed_gazelle:
Is it possible to downgrade (I'm currently on rooted 5.1.1) back to developers preview for the extra few goodies like your own screen saver and device name, and if so could you point me in the right direction of which version that is.

Thanks.
[Fire HD 6 and 7 General] bibikalka:
The downgrade is very straightforward. Get into TWRP via post #2, then follow post #1, but use your older developer preview zip. When you get to the bootloaders, flash the 5.1.1 bootloaders package (to avoid any trouble). If you use the earliest developer's preview, you may have to use the older Xposed version.
[Fire HD 6 and 7 General] CJD14:
I followed the guide and am successfully on 5.1.2 and pretty much all set. But unfortunately since I went with the lazy method and didn't wipe everything, I am stuck with Kingroot taking the default root here. It is what asks for permission for everything, I have supersu installed as per the guide, but it doesn't seem to be working because of Kingroot. It also states the su binary needs to be updated. Is there a version that is safe to flash over this that will stop this message? And is there a way to remove Kingroot without wiping everything?

I also attempted something mentioned in this thread, a zip called replace_kinguser_with_supersu

But it failed with everything it attempted, plus I don't actually have kinguser its just Kingroot.

Any thoughts folks?

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

Omg I rebooted and apparently that script did screw with kingroot but now supersu isn't working either. So now I'm on 5.1.2 with no root so I can't get back in recovery. So guess I have to start all over..

I'd still like to know which supersu to install this time.
[Fire HD 6 and 7 General] jh1521:
I had rooted my Fire HD 7 (4th gen) with kingroot (4.85) but I had to unroot it to make an app work temporarily. I then tried to root it again with kingroot, but it doesn't work anymore. I'm still on 5.1.2 (not 5.1.2.1) but now no matter how many times I tried, it doesn't root it anymore. I also tried the newer version of kingroot (4.90) but it also doesn't work.
[Fire HD 6 and 7 General] DoLooper:
Are you sure you're running 5.1.2 (February 2016)? 5.1.2.1 shows as 5.1.2 (March 2016) in Device Settings. If it is 5.1.2, FWIW I had 5 reboots and 3 "Failed" yesterday before Kingroot succeeded.
[Fire HD 6 and 7 General] jh1521:
It should be 5.1.2, after unrooting and attempting to root again I ended up in a reboot loop so I sideloaded the 5.1.2 image from the first post of this thread https://kindle-fire-updates.s3.amaz...Wt5/update-kindle-20.5.4.2_user_542169020.bin. The same image which I had rooted with kingroot before.

I tried about 20 times to root again, all failed.
[Fire HD 6 and 7 General] jh1521:
Hmm... there are 2 images for 5.1.2 in the first post.

1.https://kindle-fire-updates.s3.amaz...Wt5/update-kindle-20.5.4.2_user_542169020.bin this one is 5.1.2.1 (March 30, 2016) and cannot be rooted with Kingroot at this time.

2.https://kindle-fire-updates.s3.amaz...HBV/update-kindle-20.5.4.2_user_542168620.bin this one is 5.1.2 (Feb 26, 2016) and can be rooted with kingroot 4.85; however I haven't had any luck rooting with the latest Kingroot 4.90
[Fire HD 6 and 7 General] bibikalka:
Interesting info about the difference in Kingroot versions !!! Thanks for reporting this !
[Fire HD 6 and 7 General] jh1521:
I still have a problem with the Fire HD above.

After reflashing 5.1.2 and rooting, google play has stopped working. It gave me at first an "error retrieve information from the server RH-01". I looked it up, and supposedly it is fixed by logging out of google then logging again. Except on the fire HD you can't do that because settings/accounts only deals with the amazon account, not google.

I tried wiping out app cache and data (for both google play and google services) but it made no difference.

I then made a backup with Ti Backup, uninstalled google play+services, then restored from backup the apps only (no data).

Now google play presents me with a blue screen that says "checking info..." and stays there forever.

(edit) Fixed. I had to uninstall all google apps (not too many), reinstall TWRP as per post #2, then flash back gapps-pico and bootloaders. It works now.
[Fire HD 6 and 7 General] bibikalka:
Happy to hear that TWRP worked for you !!! :D Now that you are no longer scared of TWRP, try Xposed, it's really neat !!!

I believe when GAPPS are flashed in TWRP, the existing GAPPS are first uninstalled, and then the new ones are installed.
[Fire HD 6 and 7 General] jh1521:
I was never scared of TWRP. I used it to do the initial installation, before I had to un-root. It's just that I was unable to fix gapps without reinstalling TWRP temporarily.
[Fire HD 6 and 7 General] DoLooper:
How can DevicesoftwareOTA.apk stay renamed after a major upgrade?

Hi! I Updated OS 4.5.3 to 5.1.2 (February) in TWRP. Did a factory reset and wiped dalvik/cache in TWRP. I'd renamed DeviceSoftwareOTA.apk extension to apk_ while on 4.5.3 and when I ran command to rename after the update, I got "file not found" error. It was still renamed! How can this be? It's in a different dir on OS 5.1.2 and has a February date. Doesn't the entire /system get replaced with the OS4 to OS5 upgrade?

Also, I'm always careful to retain the 520 bootloaders. Why do I want them? :D Thanks!
[Fire HD 6 and 7 General] JUSTINMARMER:
Followed the tutorial to the letter and everything is running fine. Thank you!
[Fire HD 6 and 7 General] Jstame:
Just curious which bin file you used? The one ending in 8620.bin or 9020.bin? Thanks in advance
[Fire HD 6 and 7 General] Jstame:
Followed instructions in OP exactly as it was written and installed 5.1.2.1 update (https://kindle-fire-updates.s3.amazo..._542169020.bin) on my HD 6 that was running Fire OS 4.5.3 with TWRP already installed. My Fire HD 6 (4th Gen) is now running a Rooted Fire OS 5.1.2.1 with a perfectly working Google Playstore!!! Thanks for the great work!!!

SideNote: Next I used DoLooper's Fire HD 6&7 Tools (http://xdaforums.com/fire-hd/general/tools-fire-hd-67-rooting-gapps-t3371242) to change the launcher and block Amazon's OTA, ads, fire launcher, appstore, and Amazon search. Also worked great!
[Fire HD 6 and 7 General] Stoffl_:
Update my rootet Fire HD 7 from 5.0.2u2 to FireOs 5.1.2 according to the OP this week - worked like a charm.

Then I got a SuperSu Update Notifaction by the SuperSu app yesterday, prompted for normal install or flash via twrp / recovery, I chose normal. Update failed - SuperSu App requested a reboot.

Since then I've been stuck in a bootloop. :/

I tried clearing Cache via stock recovery but that didn't help. Haven't tried a factory reset yet but I assume that wouldn't work either.

Any way to recover via ADB or do I have to start from fresh ? :/

*edit*

Had to sidelod 5.1.2 via stock recovery, and then root and flash and setup everything again.

Note to self: Ignore Supersu update requests in the future. ;P
[Fire HD 6 and 7 General] JUSTINMARMER:
I used 3320

http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
[Fire HD 6 and 7 General] :
Thanks dude, this is really worth the upgrade. I just noticed a huge increase in performance on 5.1.2( Feb 26, 2016).
[Fire HD 6 and 7 General] VanillaXtract:
Thanks for the great how-to, I got almost everything working. My Google Play store won't let me download anything. It says "no connection." I have tried clearing data/cache for google play and download manager. I also checked the hosts file and the only entry is 127.0.0.1 localhost. Any ideas how to get it working?
[Fire HD 6 and 7 General] lilcease:
Hi everyone,

I have the Kindle Fire HD 6 4th Gen currently on the developer preview Fire OS 5.0.1..... Is there any way to get this rooted????

I've tried Kingroot v4.90 but no luck....
[Fire HD 6 and 7 General] VanillaXtract:
I just did this yesterday. I followed http://xdaforums.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351

Then I followed this http://xdaforums.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950

However, Google Play Store did not work for me at this point. So I uninstalled Google Play Store, Google Account Manager, Google Play Services, and Google Service Framework. Then I followed this to get Google Play Store working http://xdaforums.com/fire-hd/general/playstore-t3110773

EDIT: Fixed first link
[Fire HD 6 and 7 General] lilcease:
Ok...

What was your original OS before you downgraded?? Were you using the developer preview before you downgraded??
[Fire HD 6 and 7 General] VanillaXtract:
No, I was running 5.1.2. But that guide was written saying to start with the dev preview. I see I accidentally linked to page 15. Fixed for page 1.
[Fire HD 6 and 7 General] lilcease:
Ok thanks.... I got it to work.... Now Im having problems installing the playstore as well Im getting an error stating insufficient space to install Play Services and and Google Play store??
[Fire HD 6 and 7 General] VanillaXtract:
Did you install that make space package v02 package?
[Fire HD 6 and 7 General] WaywardOne:
Hi, I just had to reset my HD 6, and it is now on Fire OS 5.3.1.0. Does anyone know if it's safe to downgrade to 5.1.2 or 5.1.1, or if this version is rootable?

Edit: After a few hours of attempts with the latest Kingroot, both the apk and desktop versions, it appears this version is not yet rootable. I can only hope it's still safe to downgrade...
[Fire HD 6 and 7 General] bibikalka:
I did a rough analysis of the 5.3.1 bootloaders, and I predict that the chance that the downgrade to 5.1.2 will brick is on the lower side (I think I have a bit of a system, but who knows ...). So depending on your risk tolerance and impatience, you could try it.

Another alternative is a laborious approach from this thread (but probably safer):

http://xdaforums.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797

Basically, after setting up drivers, Python, etc, and figuring out that reads and writes are stable, you just write 4.5.3 bootloaders and TWRP into the correct addresses (the addresses need to be figured out as well). Then you hope it boots into TWRP, but I have not updated the flash-able bootloaders for 5.3.1 yet (which for safety you'd have to keep).

I do wish we had a confirmation that the unbricking method works for a downgrade bricked Fire (from the aforementioned thread). But we don't have that yet, so I am not clear if a bricked device can be revived by writing 4.5.3 bootloaders + TWRP, but there seems to be no reason why it should not work.
[Fire HD 6 and 7 General] WaywardOne:
Cool, thanks for the information. I think I'll wait until we get confirmation that downgrading works, just to be on the safe side. I'll keep that other post in mind too though, in case I do happen to get a bit impatient :P
[Fire HD 6 and 7 General] BatteriesIncluded:
Is it possible to install TWRP as recovery and keep it there? And... is there any way to tell what bootloader I am currently running? I am currently running OS 5.1.2 (Feb 26, 2015) rooted.
[Fire HD 6 and 7 General] sd_shadow:
no, locked bootloader prevents that

unless you used twrp to install 5.1.2, & installed 5.0.1 bootloader before rebooting...

the bootloader is 5.1.2 (or at least the bootloader that came with 5.1.2)
[Fire HD 6 and 7 General] WaywardOne:
So, according to this post, it seems downgrading may be a bad idea :( I realize the Fire 7 is a different device, but if it can get bricked, doesn't that mean the Fire HD 6/7 has a greater chance of getting bricked as well?
[Fire HD 6 and 7 General] bkottke3:
The checksums don't appear to match. It says to report to XDA ASAP if they don't match. Running FireOS 4.5.5.1. Also, Ran the adb commands manually from the '1_FIRE_HD_4TH_GEN_TWRP.bat' script since i am running Linux Mint 17.

$ adb shell "su -c 'sh /data/local/tmp/flash_453_stay.sh'"

Checksums before TWRP install:

bc7740e2f83fb22f8d6c5eff2291f45f /dev/block/mmcblk0p3

c99a74c555371a433d121f551d6c6398 /dev/block/mmcblk0p5

2872a5adfc94593a174857c9ca50022b /dev/block/mmcblk0p7

!!!!!!!!!!!!!!!!!

Backing up the current partitions

The backup files are : p3.bin, p5.bin, and p7.bin

64+0 records in

64+0 records out

32768 bytes transferred in 0.001 secs (32768000 bytes/sec)

4+0 records in

4+0 records out

2048 bytes transferred in 0.001 secs (2048000 bytes/sec)

1000+0 records in

1000+0 records out

512000 bytes transferred in 0.020 secs (25600000 bytes/sec)

!!!!!!!!!!!!!!!!!

Flashing the 453 images and TWRP

/dev/block/mmcblk0p3: write error: No space left on device

33+0 records in

32+0 records out

32768 bytes transferred in 0.003 secs (10922666 bytes/sec)

/dev/block/mmcblk0p3: write error: No space left on device

65+0 records in

64+0 records out

32768 bytes transferred in 0.003 secs (10922666 bytes/sec)

/dev/block/mmcblk0p5: write error: No space left on device

3+0 records in

2+0 records out

2048 bytes transferred in 0.001 secs (2048000 bytes/sec)

/dev/block/mmcblk0p5: write error: No space left on device

5+0 records in

4+0 records out

2048 bytes transferred in 0.001 secs (2048000 bytes/sec)

/dev/block/mmcblk0p7: write error: No space left on device

501+0 records in

500+0 records out

512000 bytes transferred in 0.056 secs (9142857 bytes/sec)

/dev/block/mmcblk0p7: write error: No space left on device

1001+0 records in

1000+0 records out

512000 bytes transferred in 0.051 secs (10039215 bytes/sec)

!!!!!!!!!!!!!!!!!

Verify checksums !!!

!!!!!!!!!!!!!!!!!

Required correct checksums as per the XDA guide:

3a1f3cd1ef405eaeec719eaeb41ab791 /dev/block/mmcblk0p3

d605e31a180652c65d6957b58d2d8501 /dev/block/mmcblk0p5

305a5546ff8960b51cd573b59a05cde6 /dev/block/mmcblk0p7

Checksums after TWRP install:

018b8009ff6eff5503adb3ab994b71f1 /dev/block/mmcblk0p3

c8a59ee083082ba05db7781af47dbe3a /dev/block/mmcblk0p5

97366c9f4879a67884095ed6b4d91bed /dev/block/mmcblk0p7

!!!!!!!!!!!!!!!!!

IF THE CHECKSUMS DONT MATCH, KEEP THE FIRE ON AND REPORT TO XDA ASAP

For wrong checksums, restore the partitions from the backups in adb, type:

adb shell

su

cd /data/media/0/gscript

dd of=/dev/block/mmcblk0p3 if=p3.bin

dd of=/dev/block/mmcblk0p5 if=p5.bin

dd of=/dev/block/mmcblk0p7 if=p7.bin

md5 /dev/block/mmcblk0p3

md5 /dev/block/mmcblk0p5

md5 /dev/block/mmcblk0p7
[Fire HD 6 and 7 General] jhoutz:
Just tried to downgrade from OS 5.3.1 and it definitely bricks the device.
[Fire HD 6 and 7 General] WaywardOne:
Hmm, that's too bad :( Thank you for the information, though
[Fire HD 6 and 7 General] bibikalka:
You have the wrong fire !!! Is it still on ???

You must reflash the old stuff back ASAP. It did save the back ups, so you should be fine (if it's still on).
[Fire HD 6 and 7 General] bibikalka:
OK, sorry to hear that, but good to know !

Now, you are a candidate for the unbricking :

http://xdaforums.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797

Are you up for this ?
[Fire HD 6 and 7 General] bkottke3:
It was still on yesterday. Went to bed last night and I think it may have died overnight. I checked it a few hours ago and now nothing. So it's probably bricked. I'm assuming there is no coming back from that one. :/ Thank you for the help though!
[Fire HD 6 and 7 General] bibikalka:
Well, the script did have this text :

IF THE CHECKSUMS DONT MATCH, KEEP THE FIRE ON AND REPORT TO XDA ASAP
For wrong checksums, restore the partitions from the backups in adb, type:
adb shell
su
cd /data/media/0/gscript
dd of=/dev/block/mmcblk0p3 if=p3.bin
dd of=/dev/block/mmcblk0p5 if=p5.bin
dd of=/dev/block/mmcblk0p7 if=p7.bin
md5 /dev/block/mmcblk0p3
md5 /dev/block/mmcblk0p5
md5 /dev/block/mmcblk0p7

So you should have just followed these instructions :(
[Fire HD 6 and 7 General] bibikalka:
You can still root ! Just need to follow this carefully :

http://xdaforums.com/fire-hd/develo...g-lollipop-t3405797/post67483328#post67483328
[Fire HD 6 and 7 General] jhoutz:
Alright so here's where we are at. It's an HD 6 by the way.

Got Python running on Windows. This thing is in a bootloop where the screen is black all the time, when plugged into a computer the USB just connects and disconnects. Pulled the cover off so I can disconnect the battery.

I cannot seem to get the handshake to work though everytime I plug it back in it just goes into the preloader bootloop.

I've been through that thread and tried all the drivers. Kinda hoping it's a Windows issue.

The tablet is at work so I can't get to it to tomorrow, but I'm thinking maybe the next step is to get a computer with Linux up and running.
[Fire HD 6 and 7 General] WaywardOne:
Ok, but just to be sure-- Is this method guaranteed to work? I'm a little nervous about trying this, I can't really afford to lose this device right now. Also, which OS should I use, Linux or Windows?
[Fire HD 6 and 7 General] bibikalka:
Wait a minute, you can just sideload 4.5.3 via the standard recovery, and use Kingroot there! So no need for fancy Python. See this :

http://xdaforums.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
[Fire HD 6 and 7 General] bibikalka:
Awesome to hear that you could get a rooted device without bricking ! :D The first time you have loaded FireOS 5.3.1, but kept the older bootloaders (5.1.2). So the downgrade was fine since it also had 5.1.2 bootloaders, and thus no bricking.

The functions in TWRP do not matter (single zip at a time, or all of them), but indeed, doing things in a single TWRP boot is a must ! You lose TWRP after Lollipop, and thus need to run the script to get back in (requiring root under Lollipop).
[Fire HD 6 and 7 General] n3roxda333:
HELP!

i have just flashed 5.2.0_stock_recovery_uboot.zip and now my tab didnt start.. only black screen :(
[Fire HD 6 and 7 General] bibikalka:
It's a known condition, do proceed to over here :

http://xdaforums.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797

Get set up with Python, read the blocks, I'll tell you the correct addresses for your Fire HD.
[Fire HD 6 and 7 General] n3roxda333:
Thx :) it's a hd 6 with downgrade of 4.5.3
[Fire HD 6 and 7 General] kklops:
Anyone know what the current version of Play Store/ Play Services needs to get installed?
[Fire HD 6 and 7 General] bibikalka:
I don't think there are any current limitations ... With FireOS 5.3.1 all google stuff appears to be functioning normally, with auto-updates to play store/services having no impact on anything. It used to be a bit rough under FireOS 5.1.2, but now all seems good in the newer FireOS.
[Fire HD 6 and 7 General] session030213:
Hi, I just got a Fire HD 6 Gen 4 and I'm trying to puzzle through this. Can this process be followed on 4.5.2 (never connected it to wifi, so it hasn't updated anything yet)? As I understand it, KingRoot should take care of versions < 4.5.3, so I should just block updates, root, and then use the TWRP tool?
[Fire HD 6 and 7 General] bibikalka:
Sure, 4.5.2 will work! Just run the script to get TWRP on it, and off you go.
[Fire HD 6 and 7 General] espeeee:
Hmmm...think I bricked myself - device won't even turn on w/ Power button or Pow & Vol + (yes it should have battery still and is plugged in)

Was stock 5.3.1, downgraded to 4.5.3, then used Kingroot to root and install SU. Confirmed root was working.

Got through the 101 steps, made it fine to TWRP and used the suggested 5.5.2_1534_stock_recovery_uboot.zip (since I was 5.3.1 stock and downgraded to 4.5.3) - success.

Chose to wipe dalvik/cache from the same screen where the bootloader was installed, then chose the reboot option. Now it's just blank, no signs of life or even a blank screen it just appears to be powered off.

Any thoughts on where I went wrong? After getting into TWRP should I have gone through the install steps earlier in the post (flashing to 5.3.1 again, gapps, etc...) then used the bootloader? I was planning to do that using the gscripts method after a successful reboot.
[Fire HD 6 and 7 General] session030213:
Thanks for the guide! Got it to work this morning :)
[Fire HD 6 and 7 General] bibikalka:
It seems that you flashed FireOS 5 bootloaders without having FireOS 5 installed ... You don't flash FireOS 5 bootloaders for FireOS 4, I guess I should add a few words to the guide on this.

Regardless, it should have booted into at least stock recovery, which would let you sideload 4.5.3 again. If you hold "Pwr" button for ~ 2 min, does it do anything ?

If it still looks dead, time to unbrick:

http://xdaforums.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
[Fire HD 6 and 7 General] espeeee:
Thanks for the feedback, I've been flashing rooms for years and thought I understood the directions but see the misstep.

I've been trying 20/30/60/120 second holds of the power button and nothing happens just looks like it's in a powered off state. I also had it plugged into a wall outlet for a couple of hours to make sure it had a charge.

Started down the debricking path but can't seem to get past 1st step - stuck at the handshake screen looking for device.

If I do get the device to magically reboot the steps to follow should be:

Flash 4.5.3

Root it

Sideboard 5.1.2

Install twrp

Install gapps, etc..

Upgrade to 5.3
[Fire HD 6 and 7 General] bibikalka:
Do you hear any USB connection chimes at all ? Is it just the drivers, or is the device genuinely dead ? To handshake you'd need to get the drivers going.

After de-bricking, you'll be in TWRP, so then you just load FireOS 5.3.1, and install the rest as per post #1.
[Fire HD 6 and 7 General] espeeee:
After putting my headphones back on I realized the I do hear the usb connect and disconnect chimes. First connect chime, then 6-8 seconds later the disconnect chimes. Then there's a gap every 10-15 seconds before repeating again. I have a little more hope now, forgot I had my headphone plugged in and couldn't hear any chimes at first.

Still stuck at the "Waiting for preloader...". Thought I installed the signed Mediatek VCom drivers successfully just right clicking on them in Win 10 and saying install - they said they installed correctly, is there another step im missing for the installation of those drivers. Python 3 and pyserial are also working.
[Fire HD 6 and 7 General] bibikalka:
Are you plugging it in in the off state ? Perhaps just delete the drivers via USBDeView, and try to install them again. And listen for the USB connects/disconnects ...
[Fire HD 6 and 7 General] espeeee:
Good suggestion, I'm trying to make sure it's in an off state, but can't tell for sure. I did try USBDeView and uninstall the drivers and reinstalled again. Still hearing the connects and disconnects.

Here's an image of what shows up in USBDeView when I hear the connect chime. Is there any information I can look at in USBDeView to figure out where the driver issue might reside?

I double checked that Python 3 is fine, it's in the PATH, and the Pyserial is up to date.

http://imgur.com/r8FkAoA