yashsingh1/xdaforums huggingface dataset:
[Fire HD 6 and 7 Android Development] bibikalka:
Same addresses as here :

http://xdaforums.com/showpost.php?p=68222057&postcount=113

Not sure what preloader you had before - but this one looks like the very original 5.2.0 dev preview. If you brick again, repeat the same unbricking !

Good luck !
[Fire HD 6 and 7 Android Development] powerpoint45:
All I needed to do was write TWRP. I read the part files and then I viewed 0x1b80000 in "Bless Hex Editor". It shows that the top of the file started with "ANDROID! L". I then downloaded someone else's part files that you have already told where to write and I viewed their 0x1b80000 part file and found a similar structure with the "ANDROID! L" at the top of the file. I then assumed that the same write command you gave that guy would work for me regarding recovery. Probably not the best way to check if it will work but in my case it should work unless I'm wrong somewhere. Edit: Awesome!!! It worked. My year long bricked motherboard is now fixed!

FYI: In arch linux you can install python serial with "sudo pacman -S python-pyserial"

Hmm... After I fixed it and installed CM12, the wifi was not working. I ripped off the pannels before on the back of the motherboard looking for RX TX ports so I wanted to know if I physically broke the wifi module. So I tried to go back to stock 4.5.3 Rom. I wiped the system & data then flashed 5.2.0_stock_recovery_only.zip so that I could go back to 4.5.3. Unfortunately after that I was unable to boot into recovery. It shows the white amazon logo but never will go into recovery (and obviously wont boot into system because I wiped it). Holding power and volume will usually just end up turning the device off again. It's not a big deal that it's bricked but let me know if you have any idea how to fix it. I re-flashed those images via python write script but they all seemed to have been already written correctly. It's also 4 am here so if I'm not making sense somewhere it's because I'm tired XD

Previous Post before EDIT:

I would like to learn how to find the right addresses but for now I'll post my part files. I believe this is 4.5.3. I messed with the system framework and bricked the thing. since the stock recovery doesn't do much, I can't do anything with it. I guess I only need to write TWRP. Thank you so much for your amazing work.

Edit: nvm don't mind checking the parts. I figured it out
[Fire HD 6 and 7 Android Development] amolloy:
Finally got a chance to do this, and I'm now looking at TWRP... Much better than a completely black screen! :good:

Thanks!
[Fire HD 6 and 7 Android Development] bibikalka:
Indeed, this sounds weird. There was another situation that seems similar to yours :

http://xdaforums.com/showpost.php?p=68223929&postcount=115

http://xdaforums.com/showpost.php?p=68239908&postcount=117

Basically, you can just write stock recovery into both /recovery and /boot partitions. I figure it should boot when the signed recovery sits in /boot partition, so when Fire jumps to boot, it's actually picking a recovery image instead.

Good to hear that you figured out the addresses! They seem to cluster a bit, but different combinations have been observed.
[Fire HD 6 and 7 Android Development] powerpoint45:
You are genius. I didn't think of that. Yesterday after I flashed the recovery via TWRP, and I was having issues, I wrote stock recovery to recovery partition(yesterday) it showed that half of the file was already written basically. For some addresses it was written and then about half way through it wrote wrote other address. The strange thing if I write TWRP back, it seems to show that it is already all written and if I write stock back after that it also shows it is already written. Maybe some of the addressee need to be cleared or something. It confuses me. Edit: I just wrote to the boot partition and it also said that it was already written. Now I thank that it's some issues with the handshake. I'll see what I can do... I don't know. I can't seem to write because it thinks that it is already written... Including the boot partition. I commented out the line in the Python write code where it chicks if already written (testing now).
[Fire HD 6 and 7 Android Development] bibikalka:
Delete lastaddr.txt file in the aftv2-tools folder, this file is why you cannot write again to the same addresses (or the earlier ones) ... Boot comes before recovery, so AFTV2 tools are blocking you from the write operation.
[Fire HD 6 and 7 Android Development] powerpoint45:
Thanks! I wrote to uboot instead of boot. I may be doomed now. Can't get handshake.
[Fire HD 6 and 7 Android Development] bibikalka:
Hmm, interesting ... Technically, with the handshake you are talking to the preloader, so it should not matter if UBOOT has junk or not. Just hold the Pwr button long enough, see if it comes back up. Early on there was a case like this, and I never figured out what happened since that person did not speak much English.

Once I had a partial write to UBOOT, it stopped booting, but did not stop the handshake. Wonder what happened in your case ...
[Fire HD 6 and 7 Android Development] powerpoint45:
interesting.. don't know if it helps but the last address that was written was 0x1affe00 (from 0x1300000). I can't seem to find any life in it. Ive held down power over a min. plus I've even disconnected the battery. I'm planning on looking at the physical jdebugport again and try to handshake it. (I've got an adapter soldered onto my working fire hd6 but I'll never know if it will work on my bricked one because I accidentally ripped the traces off the jdebug port. but if I figure out how to get the handshake via jdebug port then Hard Hard bricked devices might be able to be fixed. Can't be sure though

Edit: JK I got a handshake!! Rewriting uboot now. I think I took out battery plugged in device. pressed both vol up and down and power, reconnected battery
[Fire HD 6 and 7 Android Development] bibikalka:
Cool ! I've seen warnings for MTK phones that in case the flashing is interrupted, some battery data gets clobbered, so the device thinks the battery is dead. Nice to see that there is a way to fix this on Fire HD !

[MENTION=7562637]Liz-kawa[/MENTION] - looks like you should try disconnecting the battery on your dead Fire HD !!!
[Fire HD 6 and 7 Android Development] powerpoint45:
So I was able to flash twrp back on and get to that. But I never could get the 5.2.0 recovery to load. I checked md5 and everything. After i got to TWRP I installed 5.3.1 and flashed the stock_recovery_uboot zip and even after that I cannot boot into the recovery. It tries to load it and the device just shuts down and reboots. I tried adb reboot recovery as well. So now I'm stuck on 5.3.1 and I forgot to root. It's not a big deal but it is strange. I also realized that I actually did break the wlan wifi module after all as it won't work on stock as well.
[Fire HD 6 and 7 Android Development] bibikalka:
So you can boot TWRP recovery, but not the stock 5.2.0 recovery ? I think I checked this recently on a regular tablet, and 5.2.0 worked fine with 4.5.3 BL.

For you unrooted 5.3.1, you can install BL+TWRP via AFTV2 tools, and then install SuperSu via TWRP. Actually, since you are unrooted, your recovery now should have the stock 5.3.1 version which gets updated automatically (unless TWRP disabled that). If anything, this should boot fine.

One of the items I am curious about is if there is any interesting UART output when the tablet goes black screen after the older BLs are flashed on top of the new ones. If you are close to this, could you take a look ? There are partitions that we cannot get to in AFTV2 tools :

dd if=/dev/block/mmcblk0rpmb of=/sdcard/tmp/00_rpmb.img
dd if=/dev/block/mmcblk0boot0 of=/sdcard/tmp/00_boot0.img
dd if=/dev/block/mmcblk0boot1 of=/sdcard/tmp/00_boot1.img

It'd be interesting to read boot1, then update to a newer BL,and then read boot1 again to see if any flags have changed. Then after the screen goes black, one could update to the newer BL, dd the old copy of boot1 back, and see if the older BL works fine again. To me, that's the only place where the newer BLs can set flags that cause bricking.
[Fire HD 6 and 7 Android Development] powerpoint45:
well now that I'm on 5.3.1 I cannot boot TWRP or The stock recovery. The recovery won't update automatically since I can't get wifi lol (unless you are taking about something else). I might be able to get a wifi dongle to work but I need to look into that more. Actually I could put the firmware on the sdcard and then manually update it from settings (but doesn't that depend on a working recovery?) I'm not quite following you there. Also I might or might not be able to get UART from this motherboard because some of the traces are broken. But I still have a fully working motherboard that I can do whatever with. What do you mean by "read boot1"? what is boot1? Also do we have all those uboot(BL) img files to test this. I can take a look at the uart if I can get all the resources. Also which ROM should I be on when I'm getting those logs.
[Fire HD 6 and 7 Android Development] bibikalka:
What I was talking about is a script somewhere in /etc which upon each boot checks the checksum for recovery partition, and if it does not match, it will re-create it from boot.img by using a patch file. So the external ROM update is not involved.

Also remember that you can always boot TWRP if you use AFTV2 tools to write 4.5.3 tee1, uboot, and twrp into the Fire.

These are the commands to read boot partitions :

dd if=/dev/block/mmcblk0rpmb of=/sdcard/tmp/00_rpmb.img
dd if=/dev/block/mmcblk0boot0 of=/sdcard/tmp/00_boot0.img
dd if=/dev/block/mmcblk0boot1 of=/sdcard/tmp/00_boot1.img

But you need a rooted device to do so.

For bricking, the bootloaders are all here :

http://xdaforums.com/showpost.php?p=62011272&postcount=2

Booting the device with 5.2.2u2_stock_recovery_uboot.zip bootloaders once will make it brickable if 5.2.0_stock_recovery_uboot.zip is flashed back after that. The question here if boot1 partition (above) gets some additional flags, that prevent the downgrade and cause the black screen. So I wonder what UART output is when the device is bricked to this black screen state. These days the black screen is fixable via AFTV2 tools, where TWRP + 4.5.3 BLs can be flashed, but before it used to be a major issue. Anyway, it's a bit of laborious exercise, and not really clear how this would help in the future ...
[Fire HD 6 and 7 Android Development] espeeee:
finally got my handshake to work.

here are the read mmc .part files from step 2 - any help is very much appreciated!
[Fire HD 6 and 7 Android Development] bibikalka:
OK, see post #1, Appendix 1, Option B (LK @ 0x1680000). Those are your commands. Good luck !
[Fire HD 6 and 7 Android Development] espeeee:
Got everything sorted out and booting to rooted 5.3.1 - thanks for the help bibikalka!
[Fire HD 6 and 7 Android Development] bibikalka:
OK, glad to see that things have worked out for you !!! :D

Btw, the data blocks have headers of your old TEE1 & UBOOT, and it looks like you flashed the 5.4.1 bootloaders, and not 5.5.2 as claimed ;) That's why it bricked - no mystery there ...
[Fire HD 6 and 7 Android Development] powerpoint45:
Alright I will try to find time soon to check some of this out
[Fire HD 6 and 7 Android Development] PRInCEI7:
Hi

I was the root of the update 4.5.3

the work himself updated to 4.5.4

But after reboot device

device no longer works

When you enter to Recovery This option appears only

Reboot your Fire

Reset to Factory Defaults

Is there a solution to my problem or died device
[Fire HD 6 and 7 Android Development] bibikalka:
Yes, if you follow post #1, you can install TWRP, and will be able to make your Fire work again.
[Fire HD 6 and 7 Android Development] PRInCEI7:
Thank you To answer quickly

Is there an explanation powered Video, photos

Because of my language weak unfortunately

I do not know what to do

If working explain Video will solve the many problems
[Fire HD 6 and 7 Android Development] diskopat:
hello pal.

first of all thanks for making this thread.

i handshaked my bricked device and i didn't understand the next step.

Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
root@ahmet-N61Ja:/home/ahmet# /home/ahmet/Masaüstü/aftv2-tools/read_mmc.py 0x0000000 0x1000 0x0000000.part
Addr: 0x0
Addr: 0x200
Addr: 0x400
Addr: 0x600
Addr: 0x800
Addr: 0xa00
Addr: 0xc00
Addr: 0xe00
[Fire HD 6 and 7 Android Development] bibikalka:
So read a whole bunch of blocks, zip them, and upload them to XDA.
[Fire HD 6 and 7 Android Development] diskopat:
man i didn't understand how to read blocks and zip them like other guys.

sorry for being so noob :D

lol i found the part files on home directory sorry, i am uploading them in 10 minutes..
[Fire HD 6 and 7 Android Development] diskopat:
here my parts
[Fire HD 6 and 7 Android Development] PRInCEI7:
I appreciate this information very much ,, if can work tutorial pictures or videos.

Even if a short video, but we want to explain just the basics

You see now everyone asks

my , respect again.
[Fire HD 6 and 7 Android Development] bibikalka:
Your commands are in post #1, Appendix 1, Option B. (LK @ 0x1680000)

Read first, then write.

Good luck !
[Fire HD 6 and 7 Android Development] bibikalka:
[MENTION=4469251]powerpoint45[/MENTION] was talking about making a video. But, again, there is not much to it, and the steps are somewhat platform dependent. Perhaps, try to follow, and see if you have any questions ?
[Fire HD 6 and 7 Android Development] diskopat:
I able to see twrp recovery thanks for everything bro.
[Fire HD 6 and 7 Android Development] kimphat312:
Unbrick kindle fire 7 5th 5.3 downgrade 5.1

Hi ad! you can help me Unbrick kindle fire 7 5th 5.3 downgrade 5.1, I try to follow your instructions but I do not! I can contact you via Skype, Viber or facebook?
[Fire HD 6 and 7 Android Development] WaywardOne:
Ok, so I finally worked up the courage to try this method, and figured I'd practice the read commands before downgrading. I copied the text in the dropdown on #2 of the instructions and ran them. To my horror, I don't know how, I don't know why, but EVERYTHING under those commands was copied too, resulting in any other commands on that page being run. My device now doesn't start, but I believe the preloader may still be intact, but the handshake keeps giving me this error now: http://paste.ubuntu.com/23137542/

Edit: ok, somehow, it just came back to life! Crisis averted :P It was lifeless for several minutes though... But at least it's alive. I think I'll paste any other copies into gedit before running them this time... Anyways, the above error is still giving me issues, I thought I read something on one of these pages about "resetting" the usb ports, but I guess I'll have to reboot for now.

Update: Ok, The handshake completes successfully, but unfortunately the first read command seems to hang for me, at least on Linux Mint 18.
[Fire HD 6 and 7 Android Development] diskopat:
after i unbricked my fire, i bricked it again.

i'm doing same things on same computer (everything is same) but it hangs when i write "read_mmc.py 0x0000000 0x1000 0x0000000.part" (the first step)

Did i broke it permanently?
[Fire HD 6 and 7 Android Development] bibikalka:
Unlikely ... You probably need to reboot or something ...

P.S. Once you establish proper communication & stability, you can go straight to the "write_mmc" section. The addresses are the same as last time!
[Fire HD 6 and 7 Android Development] diskopat:
Same here… for lubuntu

İ did it yesterday but bricked again Today.. :rolleyes:
[Fire HD 6 and 7 Android Development] bibikalka:
There was a post on problems like this a while ago - check the thread. I think it got fixed by using a different USB port under Linux, and then there was a more permanent fix.

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

Edit : Btw, the procedure is always the same regardless of how many times you brick - establish handshake, write_mmc the partitions, brick again :D
[Fire HD 6 and 7 Android Development] PRInCEI7:
Hello

I have a problem

When I write it shows me this writing

I have a program Python 3 installed

But this shows me

C:\Users\PRInCEI7\Desktop\aftv2-tools>handshake.py
Traceback (most recent call last):
File "C:\Users\PRInCEI7\Desktop\aftv2-tools\handshake.py", line 5, in <module>
import serial
ImportError: No module named 'serial'

C:\Users\PRInCEI7\Desktop\aftv2-tools>./handshake.py
'.' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\PRInCEI7\Desktop\aftv2-tools>
[Fire HD 6 and 7 Android Development] bibikalka:
Indeed, you are missing the module "serial" in Python3. Look up how to install it, and try again !
[Fire HD 6 and 7 Android Development] bibikalka:
Could you explain how you got the usb ports to work again after the issues you had ? It seems that a few more people are running into similar problems. Thanks!!!
[Fire HD 6 and 7 Android Development] spenceboy98:
Happy to help!

I just looked up how to reset usb ports on Ubuntu and this is what I found:

sudo modprobe -r usbhid && sleep 5 && sudo modprobe usbhid

source

If you guys are having issues on windows or some other os, I'd just have to recommend that you look up how to reset the usb ports on your device.
[Fire HD 6 and 7 Android Development] bibikalka:
Appreciate the tip !!!

[MENTION=4142059]diskopat[/MENTION], [MENTION=6682067]WaywardOne[/MENTION] - try this !
[Fire HD 6 and 7 Android Development] PRInCEI7:
my parts :D
[Fire HD 6 and 7 Android Development] bibikalka:
Good! You've made it this far !!!

Please see post #1, Option A. (LK @ 0x1300000). Those are your commands.

Good luck !
[Fire HD 6 and 7 Android Development] gascomm:
[MENTION=6680544]bibikalka[/MENTION] wow, having just read through this entire thread I thought i'd best start by complimenting you for all the time and support you've offered others. an impressive workload..

i'm obviously suffering from a bricked fire hd6 (v4) which i'd rolled back to 4.5.3 (using powerpoint45's walkthrough) but hit trouble trying to install TWRP. now i'm getting a bootloop which repeats after the amazon logo appears & no option for adb in the hopeless stock recovery.

[IMG="screengrab"]http://i.imgur.com/H5xWzNA.jpg[/IMG]

I've installed python3, pyserial, usbderial & numerous versions of the mtk drivers with no success. I can't seem to get it to handshake & move forward. i'm using a surface pro 3 which has only the one usb3 port so i'm going to try setting up on a win7 desktop to see if that works.
[Fire HD 6 and 7 Android Development] PRInCEI7:
Thank you've entered into TWRP :D:D:D:D:D:D:D:D:D:D:D

Now I want the official installing the system FireOS 5.3.1

what should I do :confused:
[Fire HD 6 and 7 Android Development] diskopat:
Download rom

Change .bin to .zip

Connect tablet, send zip to tablet and flash with twrp

Or you can use adb sideload

---------- Post added at 12:56 PM ---------- Previous post was at 12:37 PM ----------

After i have bricked my fire second time i'm able to handshake but it hangs when i write read.py or write.py codes. Be careful because I think it is a permanent brick now. Maybe an hardware situation here. Before the brick i couldnt send any file to tablet when it has connection with twrp recovery. it was connected but when i clicked ariel (device name was like that) it was just an empty folder. (normally you can access tablet's sdcard when twrp is on) and i couldnt install rom from adb sideload too. because it stucked at %47 or somewhere else while sending rom. Is there any chance to wake up again? I was trying upgrade from 4.5.3 to 5.1.2 with twrp :(

for summary: while trying room update twrp couldnt mount data. I resetted tablet and didnt open anymore :D

And no more write or read commands working after handshake(handshake is ok!).
[Fire HD 6 and 7 Android Development] bibikalka:
Yeah, you just need to find a computer that will work and remain stable. Keep persisting, if Windows is a no go, try a USB stick Linux distro. Sorry that I cannot be any more helpful :(

There is a whole thread, just for you :

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

Have you tried a different computer ? If you can handshake, I cannot see why you should not be able to revive it again. Also, if you tablet got stuck, it should still have TWRP on it. How did you TWRP flash end ? Or did you overwrite recovery in the process ? Did you try to reset the USB ports as per suggestion a few posts back ???
[Fire HD 6 and 7 Android Development] diskopat:
[MENTION=6680544]bibikalka[/MENTION] yes i did it usb reset thing but still no action.

I will try hard today again. I formatted ubuntu and installed win10 32 bit

Before the brick I couldnt flash any rom so i think recovery is still twrp.
[Fire HD 6 and 7 Android Development] PRInCEI7:
[MENTION=6680544]bibikalka[/MENTION]

Thank you

I have worked my device 100%

Now the machine is fully functional

Thank you once again
[Fire HD 6 and 7 Android Development] bibikalka:
So could not you just boot into TWRP ? Or you don't see Amazon logo at all ? What's the deal?
[Fire HD 6 and 7 Android Development] BASHEER7:
Hello

this my files
[Fire HD 6 and 7 Android Development] gascomm:
hey, no worries. I've now tried it on my surface pro 3, a thinkpad and desktop running win7 - all failing to recognise the hd6 for handshake.

unfortunately, I've never understood Linux as I've always favoured windows & dos before that. out of desperation I will try a Ubuntu distro but I haven't really the time or inclination to learn a command line OS. frankly, Linux baffles me.

I fear my hd6 is looking at a future in the cupboard out of sight & mind. pity. I love the form of it - shame they stuck such a cr***y OS on it. ;-/
[Fire HD 6 and 7 Android Development] bibikalka:
Follow instructions Option B. LK @ 0x1680000 in post #1 . You can write TWRP only, the rest of your stuff seems to already be 4.5.3 ...
[Android Q&A, Help & Troubleshooting] Icarusu:
Hello!

I'm having a problem, the thing is i have a tablet which is not a good one honestly but I only use it to watch videos and download large files, then one day I inserted a new sd card for some file transfer and it turned off, I didn't know at first but it only turned on when I removed the SD card and found out it only worked without it, specifically that SD not my other one, once again I inserted it while it was on but it turned off again but this time it got in a bootloop, I aleadry have gone through this but forgot some of this restore process so I searched abit and it said to re install the ROM with a program (I forgot to mention but I think the SD card reader isn't reading and can't put files in a SD card I have since the notebook I have don't have a adaptator SD and I don't have those USB adaptadors for SD cards either) so I used the tutorial that teaches using a program which installs a firmware again, which would help, I went and downloaded the ROM that said it was for my tablet ( M7s Dual Core ML01 and the chip is called rockchip 3026 or rk3026, in kitkat 4.4 , its made in Brazil by a poor company called Multilaser, so i think the tablet has some kind of chinese origins, anyways, the post helping had the same specifications said by me so I went and installed using the program for it called rockbatch or something like that, but the tablet got a greyscreen over most parts of the brick, its still working as it can go to the recovery screen too but I can't really see it, so I'm wondering what I'm doing wrong or where to find the correct firmware, I tried similar to the name firmwares but same results, now I'm back to the normal one with grey screen and im kinda need of urgent help.
[XDA Assist] mommy2310:
The Question is how it works fine on my phone, they said it would happen if I rooted my phone but I don't know how to root...?

Font changer, etc I'd try them all(application) on my phone but fortunately they said that your phone must be rooted first... confused about how to root, does anyone else can teach me how to get root?

please, I'm begging you...???