yashsingh1/xdaforums huggingface dataset:
[Fire HD 6 and 7 Android Development] Diesen_Dev:
Yes, searched stable machine when it was right here all along. :D The writing of 3 files passed sufficiently fast - in 50 minutes without interruptions, is it normal, why so fast? Fire is pretty warm after that)

Firstly, i installed beta Lollipop (can't remember the build, from September or so). In December i returned it to 4.5.3, installed TWRP and first (and still last) CM11-based custom ROM from TWRP. Used it for 2 months, was unsatisfied that there is no sound in headphones. Installed Fire OS 4.5.3 back and forget to disable updates on air, in 5 minutes my tablet auto updated to 4.5.5.1 (approximately). Then. Brick!

Is here someone who recovered their Fire from that state? Wanna brag. I am. It finally boots! Thank you bibikalka and everyone who was involved in recovery method, tools and process very very much! I really did not thought that my Fire will be alive. It was bricked for 7 months. It was the only device what was gone to hard brick, so it was critical importance for me to recover it. Now it works!

What i may to do now to update to Lollipop without brick? My device is running Fire OS 4.5.5.
[Fire HD 6 and 7 Android Development] bibikalka:
Yes, you should brag !!! :D You did have a weird brick, but happy to hear it's working now! This is great news, since it was not clear if the brick would come alive after writing the 4.5.3 bootloaders as per this post !;)

Your path to Lollipop is here :

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

Install it from TWRP, do factory reset (a must!). Do you recall how you installed Lollipop last time ? Did you try to keep 5.2.0 bootloaders by any chance ? If you don't know, you should probably go for 5.2.2u3 version as to be on the safe side.

[MENTION=5702881]moroxoro[/MENTION], [MENTION=7070888]notorious.dds[/MENTION], @CJD14, @DoLooper, @Gimzie, @kirito9, [MENTION=4267571]sd_shadow[/MENTION], @Drevenu, @kyle12345109876, @Kramar111, [MENTION=3411776]zeroepoch[/MENTION], @hwmod, @jhoutz, [MENTION=4246643]Tomsgt[/MENTION]
[Fire HD 6 and 7 Android Development] Diesen_Dev:
Here we go! Installed last Fire OS version properly, with GApps and root. I chose 5.2.2u3 bootloader, don't want to mess up again this device. Changed Fire launcher to Nova and now it is usable :victory: Thanks again!
[Fire HD 6 and 7 Android Development] spenceboy98:
Okay, so I've bricked my little sister's Fire HD 6 and I was hoping that this method would work for me. Without thinking, I just tried some of the offsets in this thread and now I'm stuck. I've read all the values from the first post now and I am attaching a zip with all of them in it. I hope I haven't screwed it up too much to the point where I will have to buy a new motherboard. Just keep in mind that I have already written files to it with the wrong offset. :eek:
[Fire HD 6 and 7 Android Development] bibikalka:
Well, it would have been way easier the other way around ! :( Is there any reason you started to write images to the semi-random memory addresses ?

You've damaged KB, DKB & MISC partitions. Not sure if it's fatal or not.

These are your read commands :

read_mmc.py 0x0400000 0x4000 00.part
read_mmc.py 0x0408000 0x4000 PRO_INFO.part
read_mmc.py 0x0500000 0x4000 PMT.part
read_mmc.py 0x0900000 0x4000 TEE1.part
read_mmc.py 0x0e00000 0x4000 TEE2.part
read_mmc.py 0x1300000 0x4000 UBOOT.part
read_mmc.py 0x1380000 0x4000 boot.part
read_mmc.py 0x1b80000 0x4000 recovery.part
read_mmc.py 0x2380000 0x4000 KB.part
read_mmc.py 0x2480000 0x4000 DKB.part
read_mmc.py 0x2580000 0x4000 MISC.part
read_mmc.py 0x2600000 0x4000 persisbackup.part

Your write commands :

write_mmc.py 0x0900000 453p_tee1.img
write_mmc.py 0x1300000 453p_uboot.img
write_mmc.py 0x1b80000 453p_twrp.img
write_mmc.py 0x2380000 08_kb.img
write_mmc.py 0x2480000 09_dkb.img
write_mmc.py 0x2580000 10_misc.img

The last 3 partitions are attached to this post as a zip file. Do all of them at once. I would not get my hopes high since KB & DKB seem unique to each device, but let's just try and see how it goes.
[Fire HD 6 and 7 Android Development] spenceboy98:
Alright it looks like it did not work :( (which isn't really too much of a surprise, but I was kinda hoping). I've attached the before and after files here just in case you'd like to see them.
[Fire HD 6 and 7 Android Development] bibikalka:
The partitions look reasonable after flashing.

So how did it not work ? Can you still handshake ? Do you see "Amazon" logo by any chance ? Anything else to report ?

Update: Just to be sure, blast the attached file with zeros to KB & DKB partitions, let's see if we can somehow trigger a reset :

write_mmc.py 0x2380000 zero1M.img
write_mmc.py 0x2480000 zero1M.img
[Fire HD 6 and 7 Android Development] spenceboy98:
Well, it's showing "Amazon," but it's looping and not getting anywhere (which is what it was doing before). It seems like after I disconnect from one usb port, it doesn't let me handshake from the same one again. I'm currently on my last available usb port attempting what you're telling me to do. (Update: I found a way to reset the usb ports on Google using Terminal, and now they work again just fine)

Okay, it just finished, and it's still looping. I'm attaching updated parts (the long one from the first post and also the ones from before/after writing).

EDIT: I just got it to boot into TWRP! :D I guess I'll try flashing stock and see what happens now (if I can determine if it's safe to do so).

EDIT 2: It's working properly now! :D I first booted into cm11 to see if it was working, but now I'm booting to Fire OS. Thanks so much!
[Fire HD 6 and 7 Android Development] bibikalka:
This is pretty amazing! :D Do you think it could have booted into TWRP before you put zeros into KB/DKB ? Did you try that enough to make sure TWRP did not work ? Basically, I am trying to figure out if zeros actually helped, or you just did not try to get into recovery enough times after the last session, and so perhaps just missed it.

Another question, did the tablet loop Amazon logo before as well ? When it was "bricked" ? Before you started using aftv2-tools ?

Can you dump the partitions for me again ? I see only zeros in after-after.zip in KB/DKB. I want to understand if the tablet restored it after you booted Fire OS. This post :

http://xdaforums.com/showpost.php?p=68073948&postcount=72

Otherwise, awesome stuff !!!

Update: Btw, your "before" partitions in this post http://xdaforums.com/showpost.php?p=68089772&postcount=79 looked good for TEE1, UBOOT, recovery (proper 4.5.3 versions + TWRP), so you probably did figure out the addresses after you destroyed KB & DKB the first time :D

[MENTION=7562637]Liz-kawa[/MENTION]
[Fire HD 6 and 7 Android Development] spenceboy98:
I didn't really try to get into twrp before, but it's quite possible that it could have. I'm attaching the new after-after zip. Also, yeah it was doing the "amazon" loop before. When I first started (before I screwed things up), it would get past the "amazon" screen and it would get stuck on the "fire" screen. Thanks again! :D
[Fire HD 6 and 7 Android Development] bibikalka:
Interesting, it does not sound like it was too bricked! Did you try to get into recovery when it was getting stuck on "fire" logo ? Some of such things could be fixed via adb, if you have it authorized beforehand.

Thanks again for the files!!!
[Fire HD 6 and 7 Android Development] spenceboy98:
Well, I tried getting into recovery, but since I had flashed a recovery image that I had built myself that didn't work, it wouldn't boot into it. And I don't think I had root permissions with adb, so I couldn't do anything with that. I could get it into the bootloader, but it said I had no permissions when I tried to flash a working recovery. And you're quite welcome.
[Fire HD 6 and 7 Android Development] bibikalka:
OK, good then ! You did have a full blown brick (with a bootloop), so the efforts were not in vain :D
[Fire HD 6 and 7 Android Development] n3roxda333:
[MENTION=6680544]bibikalka[/MENTION]

Hey :)

I need some help to unbrick my HD6 (rooted 4.5.3).

I plug in my device my pc detect a "mt65xx preloader". Whats to do next to read and flash the repair files?

do i need a fastboot calbe? (PIN 1+4 connected)

I have windows or linux to do it. Is there a step by step guide? i dont understand whats to to^^

regards
[Fire HD 6 and 7 Android Development] bibikalka:
Follow the 2015 guide :

http://xdaforums.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747

Once you handshake, and can read memory, read many blocks as per post #1, zip, and post them here! I need those to figure out the addresses for your Fire HD specifically!
[Fire HD 6 and 7 Android Development] n3roxda333:
AAhhh thx! now i know whats to do :)

i will try it after work in the evening :)
[Fire HD 6 and 7 Android Development] n3roxda333:
i get this error on my linux:

./handshake.py

Traceback (most recent call last):

File "./handshake.py", line 5, in <module>

import serial

ImportError: No module named 'serial'

piserial is installed

solved: need python3

---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------

here is it:

https://www.dropbox.com/s/dswqskfu53y5229/UBOOT_501_backup.part.zip?dl=0

and big one

https://www.dropbox.com/s/akcog81i4lc6jcx/UBOOT_501_backup.part_big.zip?dl=0

and the small files in one zip

https://www.dropbox.com/s/0des9gtwupurv3e/all_small_files.zip?dl=0
[Fire HD 6 and 7 Android Development] bibikalka:
These are your addresses :

read_mmc.py 0x0400000 0x4000 00.part
read_mmc.py 0x0408000 0x4000 PRO_INFO.part
read_mmc.py 0x0500000 0x4000 PMT.part
read_mmc.py 0x0900000 0x4000 TEE1.part
read_mmc.py 0x0e00000 0x4000 TEE2.part
read_mmc.py 0x1300000 0x4000 UBOOT.part
read_mmc.py 0x1380000 0x4000 boot.part
read_mmc.py 0x1b80000 0x4000 recovery.part
read_mmc.py 0x2380000 0x4000 KB.part
read_mmc.py 0x2480000 0x4000 DKB.part
read_mmc.py 0x2580000 0x4000 MISC.part
read_mmc.py 0x2600000 0x4000 persisbackup.part
read_mmc.py 0x3600000 0x4000 system.part
read_mmc.py 0x4e600000 0x4000 cache.part
read_mmc.py 0x85600000 0x4000 userdata.part

Do a control read, then write TEE1, UBOOT, Recovery to the right ones. Can you figure this out ? ;)

Replace with write_mmc, TEE, LK, TWRP respectively!

read_mmc.py 0x0900000 0x4000 TEE1.part
read_mmc.py 0x1300000 0x4000 UBOOT.part
read_mmc.py 0x1b80000 0x4000 recovery.part
[Fire HD 6 and 7 Android Development] n3roxda333:
iam not exactly sure what you mean ^^

1. second read of the listed files - check

2. write the following lines TEE1.part, UBOOT.part, recovery.part - not done at the moment

and then?
[Fire HD 6 and 7 Android Development] bibikalka:
And then write files from post #1 :

write_mmc.py 0x0900000 453p_tee1.img
write_mmc.py 0x1300000 453p_uboot.img
write_mmc.py 0x1b80000 453p_twrp.img

Godspeed ! ;)

After you are done writing, do another control read, and disconnect via "read32.py 0 1". It will hopefully boot up, press "Vol+" during boot to get into TWRP. In TWRP, replace bootloaders with the correct ones (5.3.1 ?), or whatever version you have (post #2 below):

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

This will boot you back into Lollipop - where you screwed up the 1st time.
[Fire HD 6 and 7 Android Development] n3roxda333:
ah okay i will try it. at the moment it hangs on "./read_mmc.py 0x0400000 0x4000 00.part"... is this normal?

arg rebooted and restart and now this:

Waiting for preloader...

Found port = /dev/ttyACM0

Traceback (most recent call last):

File "/home/christoph/.local/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read

'device reports readiness to read but returned no data '

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "./handshake.py", line 90, in <module>

handshake()

File "./handshake.py", line 56, in handshake

c = write8(b'\xa0')

File "./handshake.py", line 48, in write8

in_str = dev.read()

File "/home/christoph/.local/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read

raise SerialException('read failed: {}'.format(e))

serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[Fire HD 6 and 7 Android Development] bibikalka:
This issue has been mentioned previously, you probably need to reboot, or go for a different USB port ...

http://xdaforums.com/showpost.php?p=68105123&postcount=81

If it hangs, it's no so good ... You need it to be stable in order to write things fully. Could it have disconnected while you waited ? Or the battery died ? You may have to find another more stable computer to do this ...
[Fire HD 6 and 7 Android Development] n3roxda333:
okay after reboot it works again.. nuw i did this steps:

sudo ./read_mmc.py 0x0400000 0x4000 00.partXXX

sudo ./read_mmc.py 0x0408000 0x4000 PRO_INFO.partXXX

sudo ./read_mmc.py 0x0500000 0x4000 PMT.partXXX

sudo ./read_mmc.py 0x0900000 0x4000 TEE1.partXXX

sudo ./read_mmc.py 0x0e00000 0x4000 TEE2.partXXX

sudo ./read_mmc.py 0x1300000 0x4000 UBOOT.partXXX

sudo ./read_mmc.py 0x1380000 0x4000 boot.partXXX

sudo ./read_mmc.py 0x1b80000 0x4000 recovery.partXXX

sudo ./read_mmc.py 0x2380000 0x4000 KB.partXXX

sudo ./read_mmc.py 0x2480000 0x4000 DKB.partXXX

sudo ./read_mmc.py 0x2580000 0x4000 MISC.partXXX

sudo ./read_mmc.py 0x2600000 0x4000 persisbackup.partXXX

sudo ./read_mmc.py 0x3600000 0x4000 system.partXXX

sudo ./write_mmc.py 0x0900000 0x4000 TEE1.partXXX

sudo ./write_mmc.py 0x1300000 0x4000 UBOOT.partXXX

sudo ./write_mmc.py 0x1b80000 0x4000 recovery.partXXX

---- dosnt work ---

sudo ./write_mmc.py 0x0900000 453_tee1.imgXXX

sudo ./write_mmc.py 0x1300000 453_uboot.imgXXX

sudo ./write_mmc.py 0x1b80000 453_twrp.imgXXX

sudo ./read32.py 0 1

but my device didnt start :(

i thing i have something done wrong
[Fire HD 6 and 7 Android Development] bibikalka:
You should have used padded images as in post #1 (notice 453p !!!). AFTV2 tools skip the last chunk which is not 256 byte aligned, so TEE1 and UBOOT get messed up.

TWRP is already padded, but you need to redo these 2 :

write_mmc.py 0x0900000 453p_tee1.img
write_mmc.py 0x1300000 453p_uboot.img
[Fire HD 6 and 7 Android Development] n3roxda333:
is see only the tee file without p in the dl section :-/
[Fire HD 6 and 7 Android Development] bibikalka:
What about this zip in post #1 : 453_padded_img.zip

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

If you already did TWRP, you can skip it this time. Only 4Mb to write ...
[Fire HD 6 and 7 Android Development] n3roxda333:
doh!! okay.

now it flashes the right one with this output:

Addr: 0x20a7600

...Already done

Addr: 0x20a7800

...Already done

Addr: 0x20a7a00

...Already done

Addr: 0x20a7c00

...Already done

Addr: 0x20a7e00
[Fire HD 6 and 7 Android Development] bibikalka:
Yeah, delete lastaddr.txt in your AFTV2 tools directory !

And, after you deleted this file, repeat the write_mmc commands !!!
[Fire HD 6 and 7 Android Development] n3roxda333:
it starts!!!! Thx!!!!!! :)
[Fire HD 6 and 7 Android Development] bibikalka:
Can you get into TWRP ???
[Fire HD 6 and 7 Android Development] n3roxda333:
Yes! Now I need the next step to have a actual firmware on the device :)
[Fire HD 6 and 7 Android Development] bibikalka:
Well, you bricked after you installed some FireOS version ?

If so, just go back to TWRP, restore the correct FireOS bootloaders (right version this time! :D ), and you should end up in FireOS ! No need to redo the prior steps, it's just the 5.x bootloaders that are missing.

See this :

http://xdaforums.com/showpost.php?p=62011228

You just need step 1)-4 [ bootloaders from post #2 ]. Flash 1 zip, and reboot to system.
[Fire HD 6 and 7 Android Development] n3roxda333:
Uff. I have never seen such a hard to flash device xD

What do you mean with #2? the tutorial i a little bit irritating :(

Before i start with my tab i have installed original 5.x.x maybe the newest one. then i have downgraded to 4.5.3 and rooted with twrp.

Now its right to flash 5.2.0_stock_recovery_only.zip?

Its not clear in the tutorial (5.4.1_1133_stock_recovery_uboot.zip, 5.5.2_1534_stock_recovery_uboot.zip,.. What?? xD )

And than the fire os bin and stuff, right? :)

Sorry for double check. I don't want to brick it again
[Fire HD 6 and 7 Android Development] n3roxda333:
i thing i have done it.

flash 5.2

flash 5.5.2_1534_stock_recovery_uboot.zip

...

...

now it start and working.

is it normal, that the twrp is gone after installing?

i have not installed gapps before reboot and now the device starts only in the stock recovery.
[Fire HD 6 and 7 Android Development] bibikalka:
Yes, TWRP disappears because it's not possible to boot TWRP with the 5.x bootloaders. In the old days it was important to replace the non-functional TWRP with the stock recovery in order to be able to fix some issues if they arised.

For your case, you need to get back into TWRP via post #2, install GAPPS as in post #1 (did you forget anything else ?), and then flash the 5.x bootloaders back so you boot into Lollipop. An alternative, when you in TWRP, just follow all the steps again from post #1, so you'll have all the things installed :

http://xdaforums.com/fire-hd/genera...root-gapps-t3163950/post62011228#post62011228
[Fire HD 6 and 7 Android Development] n3roxda333:
aaaahhhh now i understand it =)

step one:

dd if=453_tee1.img of=/dev/block/mmcblk0p3

dd if=453_uboot.img of=/dev/block/mmcblk0p5

dd if=453_twrp.img of=/dev/block/mmcblk0p7

reboot in twrp

step two:

back to stock bootloader, right?
[Fire HD 6 and 7 Android Development] bibikalka:
YES ! :D
[Fire HD 6 and 7 Android Development] n3roxda333:
1000 times THX to you :)Now i understand this stuff :)
[Fire HD 6 and 7 Android Development] SmooshMo:
Noob Question

What file(s) do we run for the 2nd step? I've ran patch_mmc.bat but I get an error about changed_blks.py. Do I have to include changed_blks.py in the environment variables?

EDIT: I'm dumb, All I had to do was copy and paste step 2 into cmd. I will post files once it is done and when I have time to do so.

EDIT#2: Here are the files
[Fire HD 6 and 7 Android Development] bibikalka:
Control read :

read_mmc.py 0x0400000 0x4000 00.part
read_mmc.py 0x0408000 0x4000 PRO_INFO.part
read_mmc.py 0x0500000 0x4000 PMT.part
read_mmc.py 0x0900000 0x4000 TEE1.part
read_mmc.py 0x0e00000 0x4000 TEE2.part
read_mmc.py 0x1300000 0x4000 UBOOT.part
read_mmc.py 0x1380000 0x4000 boot.part
read_mmc.py 0x1b80000 0x4000 recovery.part
read_mmc.py 0x2380000 0x4000 KB.part
read_mmc.py 0x2480000 0x4000 DKB.part
read_mmc.py 0x2580000 0x4000 MISC.part
read_mmc.py 0x2600000 0x4000 persisbackup.part

and writing :

write_mmc.py 0x0900000 453p_tee1.img
write_mmc.py 0x1300000 453p_uboot.img
write_mmc.py 0x1b80000 453p_twrp.img

Your bootloader is already 4.5.3, why is it bricked ? Are you just missing TWRP ? Can you boot with "Vol+" pressed to see what you get ?
[Fire HD 6 and 7 Android Development] SmooshMo:
Hey... the reason why it's bricked is because I swapped out an image file in TWRP. I've tried booting with all the basic key inputs but to no avail. It is stuck in a bootloop.

EDIT: The writing part is running!

EDIT#2: It's still stuck in a bootloop :(
[Fire HD 6 and 7 Android Development] bibikalka:
So "Vol+" does not get you into recovery ? Are you sure you are pressing the buttons at the right time ?

Another option is to write the stock recovery (signed !!!) into boot partition, this way the stock recovery should boot automatically. Download 4551_stock_recovery_padded.zip from post #1 , unpack, then write the image into boot :

write_mmc.py 0x1380000 4551_stock_recovery_padded.img

Let's see if this works. The FireOS 4.x recovery sucks in terms of features, but we could later replace everything with versions from FireOS 5.x. The recovery there has a lot more features, so we could sideload the OS.
[Fire HD 6 and 7 Android Development] SmooshMo:
Just got home... the image is running as I type.

EDIT#2: It worked it worked!!!!
[Fire HD 6 and 7 Android Development] bibikalka:
OK, now flash the stock 5.x recovery into boot & recovery, grab it here :

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

( 5.2.0_stock_recovery_only.zip , it's in /images folder)

write_mmc.py 0x1380000 recovery.img
write_mmc.py 0x1b80000 recovery.img

In 5.x stock recovery, you could try to sideload stock FireOS 4.5.3 . I'd flash the recovery into both partitions, since I am not sure how sideloading will work when recovery is run from /boot partition.

Instead of messing around with Kingroot, a fun (but longer!) thing to try to do is to type "adb reboot recovery", and as it's rebooting, do a handshake, and write TWRP into recovery using AFTV2 tools:

write_mmc.py 0x1b80000 453p_twrp.img
read32.py 0 1

(I've just tested it, it will reboot into recovery after a detour caused by AFTV2 tools!)

As Fire reboots after AFTV2 tools, you'll get into the freshly written TWRP, where you immediately install SuperSu (save a zip to Fire's /sdcard while 4.5.3 is still unrooted). This will prevent 4.5.3 from putting stock recovery into Fire.

Anyway, it's a long way to get around "Vol+" during boot [which does not seem to be working for you :( ]
[Fire HD 6 and 7 Android Development] SmooshMo:
Hey… the vol+ button works now thanks to your previous reply!! Also I already had TWRP installed prior to bricking my Fire HD 6.
[Fire HD 6 and 7 Android Development] bibikalka:
Well, you've replaced whatever recovery you had with TWRP again in this post : http://xdaforums.com/showpost.php?p=68222255&postcount=114

So you do have plenty of TWRPs to go around :D
[Fire HD 6 and 7 Android Development] SmooshMo:
How would I flash it using TWRP instead?

EDIT#2: Wait nvm.
[Fire HD 6 and 7 Android Development] carlyman:
Any hints on getting this working with Windows 10? I've tried 3 different machines, but all have the same issue of hanging on Step 2 (read_mmc.py). I have a successful handshake (COM7) and have installed the Mediatek drivers (tried both the "MediaTek DA USB VCOM (Android)" and "MediaTek PreLoader USB VCOM (Android)" from the driver options). Also tried different USB ports as well as USB2.0 and USB3.0.

Unfortunately don'y have any Linux or Mac machines around...

-JC
[Fire HD 6 and 7 Android Development] bibikalka:
How about running Linux off a USB drive ? There are tons of distros out there like this.
[Fire HD 6 and 7 Android Development] carlyman:
Obvious suggestion...that I hadn't even thought of, geesh :)

However...I can't get a successful handshake; it just hangs ("Waiting for preloader..."). I've installed libusb-dev as well as able to communicate via ADB and FASTBOOT. Tried following several how-tos (link), but still no handshake. Using latest ubuntu off a thumbdrive.

Edit: Also tried running as python, python3, and just "./handbrake.py" -- as well as ensuring pyserial version 3.0.1

Thanks again,

JC
[Fire HD 6 and 7 Android Development] powerpoint45:
Amazing job man. Will check this out soon. Got a bricked motherboard lying around. May make a video over this .
[Fire HD 6 and 7 Android Development] zeroepoch:
You might want to try running as root (if you haven't already) because maybe it doesn't have permission to open or write to the serial device.
[Fire HD 6 and 7 Android Development] SmooshMo:
Hey man make sure that you reboot windows 10 with advanced options and choose skip digital drivers signatures (Or something along those lines).

After reinstall the drivers and change your environment variables to have python included in the "path". If you need anymore help just ask.
[Fire HD 6 and 7 Android Development] amolloy:
Unbricking HD 6

Hi, it appears I have bricked my Kindle Fire HD 6. As described in step #2 I've assembled a zip of the *.part files retrieved using read_mmc.py and attached it to this message. Reading all of the part files appears to have gone smoothly so I think I'm pretty set for a computer to perform the unbricking from. Thanks in advance for the help, I appreciate it!