yashsingh1/xdaforums huggingface dataset:
[Fire HD 6 and 7 Android Development] Killa8:
Strange

I successfully flashed 5.3.1 after unbricking,

Though I couldn't get TWRP,(I read a post explaining why , and how to get it back temporarily)

I'm now on 5.3.1 which I flashed about thrice using TWRP, never got issues

---------- Post added at 06:42 AM ---------- Previous post was at 06:33 AM ----------

All I did was flashing the zip from TWRP

As someone said earlier, it's probably a signature and authorization affair,

Maybe AFTV tools will need and update which can trick the preloader ?

---------- Post added at 06:43 AM ---------- Previous post was at 06:42 AM ----------

Strange

I successfully flashed 5.3.1 after unbricking,

Though I couldn't get TWRP,(I read a post explaining why , and how to get it back temporarily)

I'm now on 5.3.1 which I flashed about thrice using TWRP, never got

All I did was flashing the zip from TWRP

As someone said earlier, it's probably a signature and authorization affair,

Maybe AFTV tools will need and update which can trick the preloader

---------- Post added at 07:15 AM ---------- Previous post was at 06:43 AM ----------

Strange

I successfully flashed 5.3.1 after unbricking,

Though I couldn't get TWRP,(I read a post explaining why , and how to get it back temporarily)

I'm now on 5.3.1 which I flashed about thrice using TWRP, never got

All I did was flashing the zip from TWRP

As someone said earlier, it's probably a signature and authorization affair,

Maybe AFTV tools will need and update which can trick the preloader

Before the brick I had TEE1 from 4.3 and UBOOT 5.2.0, I never tried flashing back stock recovery cause I'm afraid to.brick my device again lol

Hope you can solve it
[Fire HD 6 and 7 Android Development] powerpoint45:
Does recovery also work for you? On my old motherboard I went through the process again this time installed the 5.3.1 rom plus the uboot&recovery5.4.1. Everything works except recovery. Did I flash the wrong recovery or something. Also it seems if I install supersu zip it causes a bootloop. So strange. I've read and re-read your instructions for the root/gapps thing and it seems like it should work. Could just be something wrong with the motherboard I guess but I'm puzzled.
[Fire HD 6 and 7 Android Development] bibikalka:
OK, thanks for the info ! On Fire HD 2014 the preloader is never updated (it seems), so I thought it'd be "permanently enabled." But I guess not ...

Yep, recovery is working. It comes as part of the bootloader package. I have not seen anybody complain about this not working. Also it's weird that you have SuperSu causing a bootloop. Have you done a factory reset before flashing the new rom ? With 5.4.1 BLs you should be able to use AFTV2 tools, get back into TWRP, do a reset, flash SuperSu, etc.
[Fire HD 6 and 7 Android Development] powerpoint45:
yes I did do a factory reset but I also wiped the system partition. maybe that is an issue... Do you have an hd6 or hd7

Edit : Oh I think I need to flash 5.5.2recovery&uboot instead. need to double check

Edit: No that doesn't help. Could be caused by my broken wifi on the actual board. Would be strange but possible that recovery does some sort of check on it.. IDK.
[Fire HD 6 and 7 Android Development] Killa8:
Had the same issue with SuperSU zip, so I just used the Windows Auto root program found on another thread
[Fire HD 6 and 7 Android Development] powerpoint45:
I think I remember now a while back that I had that issue and I found a different supersu zip online like v 2.5 or something
[Fire HD 6 and 7 Android Development] gilweb:
Hi all. Trying to un-boot loop a HD5 using the Linux ISO image. Nice stuff! This is my second time through this.

Ran ./handshake.py and all good

ran ./reader.sh and (apparently) all good

ran ./determinOption.sh and it says Option A

[root@archbang aftv2-tools]# ./determineOption.sh
Option A Evaluation:
00000000: 8816 8858 9099 0e00 5445 4500 0000 0000 ...X....TEE.....
00000000: 8816 8858 943a 0300 4c4b 0000 0000 0000 ...X.:..LK......
00000000: 414e 4452 4f49 4421 b807 4c00 0080 0010 ANDROID!..L.....
OPTION A SHOULD WORK

Option B Evaluation:

Option C Evaluation:

Result:
OPTION A SHOULD WORK

ran ./readerSpecialOptionA.sh and (apparently) all good

ran. ./unbrickSpecialOptionA.sh

...
Addr: 0x91fe00
...Already done
Addr: 0x920000
Traceback (most recent call last):
File "./write_mmc.py", line 375, in <module>
word = struct.unpack('@I', input.read(4))[0]
OSError: [Errno 5] Input/output error
writing 453p_uboot.img to 0x1300000
This will take some time...
Addr: 0x1300000
Traceback (most recent call last):
File "./write_mmc.py", line 375, in <module>
word = struct.unpack('@I', input.read(4))[0]
OSError: [Errno 5] Input/output error
writing 453p_twrp.img to 0x1b80000
This will take some time...
Addr: 0x1b80000
Traceback (most recent call last):
File "./write_mmc.py", line 375, in <module>
word = struct.unpack('@I', input.read(4))[0]
OSError: [Errno 5] Input/output error
Your device should now be fixed! Boot into TWRP and flash a ROM
[root@archbang aftv2-tools]#

What's my next move? :)

Thanks!
[Fire HD 6 and 7 Android Development] Killa8:
Boot into TWRP and flash the ROM for your device !

If you don't know which one to flash just go to the link in OP on how to get back FireOS
[Fire HD 6 and 7 Android Development] gascomm:
i'm holding out for the walkthrough for the [MENTION=4469251]powerpoint45[/MENTION] iso image method. hours spent going in circles trying to fathom that flavour of Linux - I couldn't even figure if I had pyserial available & got nowhere near a handshake.

the hd6 is now in bubble-wrap whilst I play with my bargain 9" nook hd+ find.
[Fire HD 6 and 7 Android Development] powerpoint45:
I've already got the walkthrough done here & yes it has pyserial. you may need to try the handshake a few times to get it to work: http://xdaforums.com/fire-hd/development/video-linux-iso-unbrick-fire-hd6-hd7-t3474999/page1
[Fire HD 6 and 7 Android Development] gilweb:
Thanks for the reply. Unfortunately I'm not sure how to do that on this one, although I've done it before on a different device. On this one, when the device reboots, the amazon logo appears briefly and then I get the Fire System Recovery screen with two choices: Reboot or Reset. Holding the Vol+ button doesn't seem to help change where it boots into. Any thoughts?
[Fire HD 6 and 7 Android Development] Killa8:
Ow, then you didn't write the TWRP image,

What exactly did you have as brick ?

Black screen brick ?

With cache error?
[Fire HD 6 and 7 Android Development] gilweb:
"Reset loop" actually. Amazon logo, then Fire Recovery screen. I did the Reset, but that doesn't help. I think it happened when I did the 4.5.3 downgrade ( as per http://xdaforums.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950. I can't remember for sure since it was one of two I'm having issues with.) I thought maybe the unbricking process would help, but I get the messages in my OP and the device does the same behavior.
[Fire HD 6 and 7 Android Development] Killa8:
Just flash 4.5.3 image and all should be fine , and sideload it :)
[Fire HD 6 and 7 Android Development] bibikalka:
Not much to do, other then to try to unbrick via TWRP. Use the latest instructions, it should be quite easy !
[Fire HD 6 and 7 Android Development] gilweb:
I really appreciate you guys responding, and I'm sorry for being so dense. But I'm not sure how to do this. The only choices on the system recovery screen are "reboot" and "reset". Sideload isn't a option. And when I try any "adb" command, like "adb devices" I get nothing, even after I get a handshake.

And after searching around, for unbricking via TWRP, I can't seem to find anything that stands out.
[Fire HD 6 and 7 Android Development] powerpoint45:
the log you posted a while back looks like it had some errors. You may need to re-run the unbrick script. You should have TWRP installed but it seems you still have stock 4.x recovery instead which you can't do anything with.
[Fire HD 6 and 7 Android Development] polys248:
Which option

Hello,

I've followed the instructions and my data dump is attached. Please tell me which option to use.

Thanks.
[Fire HD 6 and 7 Android Development] bibikalka:
Something is really weird ... I don't see the correct partitions at all. The addresses are totally off. How did you brick it ?

Just to be sure, have you tried the automatic script :

http://xdaforums.com/fire-hd/development/video-linux-iso-unbrick-fire-hd6-hd7-t3474999
[Fire HD 6 and 7 Android Development] derfington:
Trying to just install an android OS on an old kindle fire i have laying around. Found some guides online and i will walk you through the steps i took. Maybe someone can point me in a direction to get it unbricked.

Device was 5.1.2.1

sideloaded 5.3.1

When Kingroot still did not work, Side loaded 4.5.3

Rooted with Kingroot

Installed TWRP

Installed 5.4.1 Bootloaders per tutorial in TWRP

Rebooted device, now a black screen and i can hear the USB chime connecting and disconnecting when it is plugged into my PC.

Trying to Use AFTV 2 tools but it shows waiting for preloader, and in devices and printers i can see a MT65XX appearing and disappearing with the usb chimes. Installed the Mediatek drivers as well as a MTKUsbALL driver.
[Fire HD 6 and 7 Android Development] gilweb:
Worked like a charm once it ran without errors. Thanks and sorry for the delay.. on to Fire #2...
[Fire HD 6 and 7 Android Development] gilweb:
So fire #2 has the same problem as some previous posters: Black screen, handshakes ok but then reader.sh hangs on different PCs and different cables. Before I give up on it, are there any new developments that I might not know of? :) Unfortunately it's been two months and I don't remember specifically what I did to brick it. It was trying to put lollipop on it and I think it was loading TWRP that I messed up somehow.
[Fire HD 6 and 7 Android Development] Drevenu:
Is anybody willing to help me? :|

So I managed to brick my Kindle Fire HD7 (8 Gb) 4th Gen 2014 couple of months ago by playing around with TWRP and not fully knowing what I was doing. This thread gave me the hope that maybe it can be fixed but after reading the whole thread it is clear that although I know my way around the computer this is beyond me.

Initial read STEP 2 .part files : https://1drv.ms/f/s!AizqtwflbfAkgijV-0PIIVydsneR

Also did and attached:

read_mmc.py 0x400000 0x1000 00.part

read_mmc.py 0x408000 0x1000 PRO_INFO.part

read_mmc.py 0x500000 0x1000 PMT.part

read_mmc.py 0x900000 0x1000 TEE1.part

read_mmc.py 0xe00000 0x1000 TEE2.part

read_mmc.py 0x1300000 0x1000 UBOOT.part

read_mmc.py 0x1380000 0x1000 boot.part

read_mmc.py 0x1b80000 0x1000 recovery.part

read_mmc.py 0x2380000 0x1000 KB.part

read_mmc.py 0x2480000 0x1000 DKB.part

read_mmc.py 0x2580000 0x1000 MISC.part

read_mmc.py 0x2600000 0x1000 persisbackup.part

read_mmc.py 0x3600000 0x1000 system.part

read_mmc.py 0x4e600000 0x1000 cache.part

read_mmc.py 0x85600000 0x1000 userdata.part

What is the next step?

Thank you in advance :)
[Fire HD 6 and 7 Android Development] bibikalka:
Well, it seems that by chance you've stumbled upon the correct addresses. So as per instructions in post #1, continue with this :

write_mmc.py 0x0900000 453p_tee1.img

write_mmc.py 0x1300000 453p_uboot.img

write_mmc.py 0x1b80000 453p_twrp.img
[Fire HD 6 and 7 Android Development] Drevenu:
Hey,

I managed to get it up am running!

After posting here, i saw /powerpoint45 thread with the Linux iso, gave it a go and it worked !!!

My old files were even there !!!

Thank you so much for your reply in June, and pointing me to your post. I only now had the proper time to give it a go.

You guys rock!

Cheers!
[Fire HD 6 and 7 Android Development] Oleg-vbz:
Hello!

I have Black sreen on my HD6:(

This happened after I did some mistakes when try to upgrade FireOS using this topic.

1) I have booted to TWRP the wrong version of GAPPS (mini) and get error during flash

2) Then I have push Reboot -> System (instead Reboot -> Recovery)

After that device became a brick :(

I have tryed unbrick device using 1 message of this topic, but it ends in step "Waiting for preloader..."

Maybe someone knows a way to unbrick it?
[Fire HD 6 and 7 Android Development] Drevenu:
Use this : https://www.youtube.com/watch?v=BC0L6Up5opQ

Follow the instructions in the description.

It the preloader stuff works better with the bootable linux usb than under windows.

The whole thing should take about an hour.
[Fire HD 6 and 7 Android Development] Oleg-vbz:
Thank you for good advice :good:

I have done all steps untill step 12. But during holding volume up and running ./complete.sh I received this message on the screen (look attach)
[Fire HD 6 and 7 Android Development] Drevenu:
Did you try the process more than once and got the same error?

Did your battery die? Did you move the tablet to much to cause the plug to move and disconnect?

Try a different cable / usb port.

Did you run the linux of a usb or in a virtual machine? I got an error like that when i tried to run it from a virtual machine.

I don't know what to say other than that because it just worked for me.

Try and do the steps in post #1 and maybe /bibikalka can help you further.

Best of luck!

:)
[Fire HD 6 and 7 Android Development] Oleg-vbz:
I have did yesterday and today it more than once.

I run linux from usb (not VM).

The battery was full until my dance with brick (5 days ago). I each time get "handshake complete" after running "./handshake.py".

I have tried use different cables, but some of that does not work, some have given me same result :(

I think to solder a special cable tomorow, maybe it help me.
[Fire HD 6 and 7 Android Development] Liz-kawa:
Dear bibikalka

it will send the necessary files.

Thank you!
[Fire HD 6 and 7 Android Development] bibikalka:
Well, I cannot figure out any of your addresses ... They are different than my Fire HD 7.

You have Fire HD 6 2014 version, correct ? What's the product version ?

You can read every 1 or 0.5 Mb, zip it, and post it here :

read_mmc.py 0x1500000 0x1000 15.part

read_mmc.py 0x1600000 0x1000 16.part

read_mmc.py 0x1700000 0x1000 17.part

read_mmc.py 0x1800000 0x1000 18.part

read_mmc.py 0x1900000 0x1000 19.part

read_mmc.py 0x1A00000 0x1000 1A.part

read_mmc.py 0x1B00000 0x1000 1B.part

read_mmc.py 0x1C00000 0x1000 1C.part

read_mmc.py 0x1D00000 0x1000 1D.part

read_mmc.py 0x1E00000 0x1000 1E.part

read_mmc.py 0x1F00000 0x1000 1F.part
[Fire HD 6 and 7 Android Development] Liz-kawa:
Dear bibikalka

it will send the necessary files.

My HD6 is 2014(4thGen)

Thank you!
[Fire HD 6 and 7 Android Development] bibikalka:
Please read this one and upload a zip file :

read_mmc.py 0x1D80000 0x1000 1D8.part
[Fire HD 6 and 7 Android Development] Liz-kawa:
Dear bibikalka

it will send the necessary files.

Thank you！
[Fire HD 6 and 7 Android Development] bibikalka:
Please do a few more :

read_mmc.py 0x1D10000 0x1000 1D1.part

read_mmc.py 0x1D20000 0x1000 1D2.part

read_mmc.py 0x1D30000 0x1000 1D3.part

read_mmc.py 0x1D40000 0x1000 1D4.part

read_mmc.py 0x1D50000 0x1000 1D5.part

read_mmc.py 0x1D60000 0x1000 1D6.part

read_mmc.py 0x1D70000 0x1000 1D7.part
[Fire HD 6 and 7 Android Development] Liz-kawa:
Dear bibikalka

I attached your request.

Thank you!
[Fire HD 6 and 7 Android Development] bibikalka:
This is tough ... The address is hard to guess, please run this and post the zip here :

read_mmc.py 0x1D70000 0x10000 1D7full.part
[Fire HD 6 and 7 Android Development] bibikalka:
And this one :

read_mmc.py 0x1D70000 0x20000 1D7full2.part
[Fire HD 6 and 7 Android Development] Liz-kawa:
Dear bibikalka

I attached your request.

I will thank you for your effort.
[Fire HD 6 and 7 Android Development] bibikalka:
OK, good ! Try this :

read_mmc.py 0x400000 0x1000 00.part
read_mmc.py 0x408000 0x1000 PRO_INFO.part
read_mmc.py 0x500000 0x1000 PMT.part
read_mmc.py 0x900000 0x1000 TEE1.part
read_mmc.py 0xe00000 0x1000 TEE2.part
read_mmc.py 0x1300000 0x1000 UBOOT.part
read_mmc.py 0x1380000 0x1000 boot.part
read_mmc.py 0x1b80000 0x1000 recovery.part
read_mmc.py 0x2380000 0x1000 KB.part
read_mmc.py 0x2480000 0x1000 DKB.part
read_mmc.py 0x2580000 0x1000 MISC.part
read_mmc.py 0x2600000 0x1000 persisbackup.part
read_mmc.py 0x3600000 0x1000 system.part
read_mmc.py 0x4e600000 0x1000 cache.part
read_mmc.py 0x85600000 0x1000 userdata.part
[Fire HD 6 and 7 Android Development] bibikalka:
Now try this (we will attempt to write partitions to the proper addresses) :

write_mmc.py 0x900000 453_tee1.img

write_mmc.py 0x1300000 453_uboot.img

write_mmc.py 0x1b80000 453_twrp.img

After you do this, disconnect. And see what you get.
[Fire HD 6 and 7 Android Development] Liz-kawa:
Unfortunately unbrick is unsuccessful. Let alone HD6 became unresponsive...:crying:
[Fire HD 6 and 7 Android Development] bibikalka:
Hold the power button for about 60-90 sec or so. At least you should be able to get pre-loader back !!!

Update: once it's talking again via the preloader, please re-run this again, and post the files :

http://xdaforums.com/showpost.php?p=67663563&postcount=34
[Fire HD 6 and 7 Android Development] Liz-kawa:
I tried several times.But pre-loader is'nt back... PC does not recognize the HD6. Ican't send files for you.
[Fire HD 6 and 7 Android Development] bibikalka:
Try this. First, hold the Pwr for 60-90 sec, and release. Then, start the handshake on the PC, and plug in the Fire into the USB port. It should power up the Fire, and handshake with the preloader immediately.

I don't believe we could have overwritten the preloader !!! I think the unbricking is actually working, since the behavior has changed, but we need to fix a few more partitions.

Keep trying, and you should get the preloader back!!!

Update : here is what you do, start the handshake, plug in Fire to the USB port, hold the power button. About 30-40 seconds later it should go into preloader.
[Fire HD 6 and 7 Android Development] Killa8:
"Device disconnected or multiple ports??"

Try powering the device by holding the power button for about a min

Then start back the process and watch.
[Fire HD 6 and 7 Android Development] Oleg-vbz:
Thank you for your answer.

One week ago I have tried use the "factory cable" and after that my device has been become invisible from pc (win and linux) ((( Full brick(
[Fire HD 6 and 7 Android Development] Killa8:
Well, fastboot cable is pointless with this model of Fire.

If you definitely weren't able to unbrick you can still ship it to a volunteer developer for him to do researches, and maybe unbrick it for you ?? ;)

Or just buy a motherboard from eBay , they're pretty cheap there
[Fire HD 6 and 7 Android Development] my2k2zx2:
I had an HD6 stuck in a boot loop. I've went through the unbrick process with the linux iso, but after running ./complete.sh the display is no longer working. I can still handshake and run the other commands, but the screen never turns back on. Is there any fix for this?

Edit: was able to recover the device using 5.5.2_1534_stock_recovery_uboot.zip.
[Fire HD 6 and 7 Android Development] Killa8:
Hi, I just bricked my Fire (again) trying to install Xposed(again). So I can handshake, and i went right to the part where I've got to write the files to the tab. Last time i did it from kali, but now i'm on window's, and my connection is too slow to download Powerpoint's (extraordinary) already packed distro. So my option last time was Option A, could this change ? For when I run any write command e.g write_mmc.py 0x1b80000 453p_twrp.img i get "Usage: write_mmc.py addr file"

Is there something wrong? Handshake is ok and device is still present

Hope you can help :)
[Fire HD 6 and 7 Android Development] bibikalka:
The opton will stay the same for you (A). Not sure why you get the error, is there a space missing somewhere ? ;) You can debug Python yourself, just google for print line, and print the number of input arguments, see how many it sees! Perhaps, the Python version is too new/too old ?
[Fire HD 6 and 7 Android Development] Killa8:
Hi

Was once rooted with everything fine, until I tried to install Xposed, bricked my device upon installing wrong bootloader(third time), unbricked it, got root, TWRP, flashed Xposed, and fire OS, with our flashing any bootloader and super SU. Device boots Xposed works, but no root, no way to get to TWRP and root nor any recovery. Has happened to me multiple times( Fire OS 5.3.1) but I was able to get back root after multiple reboots and kingroot tries. But this time around nothing, Even tried writing TWRP and 4.5.3 bootloader directly to memory, but it just hangs when I select my option, handshake is fine but no response.

Any help is welcome
[Fire HD 6 and 7 Android Development] AmpCo:
brick classic

downgraded to 4.5 for root etc. success. was upgrading 5.x as per here. all good until twrp. wrong flash i guess. fire hd 6 4th gen. locked in the preloader. have handshake and a few .parts at this point. my question is how many do u need i guess. will post few i have. thanks for everything
[Fire HD 6 and 7 Android Development] AmpCo:
more .part

more .part thanks again
[Fire HD 6 and 7 Android Development] AmpCo:
unbricked!

wow
[Fire HD 6 and 7 Android Development] Tangoviktor:
I have a problem with my HD7 4th gen. It is in a boot loop, but it only loops to the amazon logo, it will not show the kindle logo. I tried the linux version, and the ./determineOption.sh said that there was no option available. Should I post the part files here?
[Fire HD 6 and 7 Android Development] zeroepoch:
You need to change to the directory where the reader.sh script is located.
[Fire HD 6 and 7 Android Development] Tangoviktor:
So, i was unable to do it. Copied the part files and made them into a zip. Can someone take a look?
[Fire HD 6 and 7 Android Development] kdlego:
I asked some question here but i solved it myself, so i edit my post.
[Fire HD 6 and 7 Android Development] Tonymontana655:
I found the correct hex part to edit, thanks though.
[Fire HD 6 and 7 Android Development] leehiyong:
How can I solve this problem?

I have a bricked kindle fire HD 7. I tried to recovery it, but not succeed.

[IMG="bricked kindle fire HD 7 recovery menu"]https://goo.gl/ZCeZH1[/IMG]

I tried to enter system recovery mode, kindle said "E:fail to mount /cache (Invalid argument)"

When run "wipe cache partition" and "wipe data/factory reset" kindle reply same message.

I tried "apply update from ADB", I connected with cable and I tried "adb sideload update-kindle-20.5.7.9_user_579225620.bin" but writing to kindle dosen't work.

kindle said "E:fail to mount /cache (Invalid argument)"

Next time I tried run "reboot to bootloader" to enter fastmode. and I connected with cable.

i typed "fastboot getvar product" kindle replied "product: ARIEL"

I tried to "fastboot oem unlock" command after connected, but it doesn't work. kindle replied "FAILED (remote: the command you input is restricted on locked hw)"

I tried again with normal cable and factory cable. but I couldn't break H/W lock.

Finally I tried "AFTV2 tools" on Archbang Linux, "handshake.py" works well. but "./reader.sh" command doesn't show any reply.

Then I found message in this thread, "Notice that in FireOS 5.3.1 this functionality has been disabled, so nothing happens as people try to read/write memory"

I really want to unbrick my kindle fire HD 7. How can I do?

Thanks.
[Fire HD 6 and 7 Android Development] Drunkpilot:
I had a similar issues with a previous Kindle, and completely bricking due to downgrading to 5.3.1 with the 5.5.2 bootloader. Have you tried to adb sideload 4.5.3? You can downgrade to that bootloader without bricking your device and hopefully get your Kindle working again. Then you can try upgrading to the OS you we using and flashing a new recovery/uboot which could possibly be corrupted on your device. I don't know, just a thought. He's the link to the 4.5.3 update: https://xdaforums.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351