[Kindle Fire Android Development] Hashcode:
Update to this thread:

I posted earlier that if a resolution wasn't found that i would brick my device and work on it from my end. And yesterday (06/07) I did just that.

From my testing yesterday, and examining which partitions had damage on my device, I was able to get a ROM installed on the device by shifting the partitions past the end of the regular cache partition using the instructions laid out earlier in the thread. (this drops about 1.4GB of space from my device).

However, I'm noticing that my Kindle is somewhat unstable. Mostly during writes to the /emmc partition where i was re-setting up files for backups, etc. And when restoring /data from TitaniumBackup I experienced hard lockups.

** So, I don't consider the re-partition fix a solid one -- even tho it may actually be a solution for some users. **

As of now, I'm looking for other methods to "reset" the emmc controller and / or update the firmware. And my sources would be the following:

Investigate the changes Samsung has made to the Note kernels in order to deal with existing damage. It could be that they've added additional checks / IOCTLs for handling bad leveling data.

I've already done some research into the JEDEC eMMC host controller protocol and there may be a flag we can set to avoid error checking, etc during a low level format of the entire device. Experimentation would ensue on my device.

Contact Samsung directly (via the contact in the other threads) and ask for a low level source code solution to format the eMMC AND / OR a way of loading new firmware for our chips.

The low level format binary could be used in a special recovery build (loadable via fastboot) which would allow the user to do the following:

Backup bootpart0, bootpart1, xloader and bootloader to the ramdisk as .img files via dd (or possibly allow for the user to adb push clean .img's of xloader and bootloader in case of corruption)

Remove all of the partitions from the device and perform a low level format using a binary which talks directly to the eMMC host controller and allows for the levelling data to be cleared / reset.

Reset the partition table to stock Amazon spec.

Restore the backed up partitions which would allow the device to be bootable (tho you would still need fastboot to do anything)

format the /emmc as FAT32 and allow for it to be shared via UMS

Once shared the user can place the rest of the larger partition .img files onto the device and restore those as well (from a set directory or something)

^^ Just tossing out ideas for how a full recovery would work.

And to eliminate any doubt: this *IS* the Samsung eMMC corruption issue that we're experiencing. My reasoning as follows:

Those showing "MMC M8G2FA" in parted have Samsung eMMC part #: KLM8G2FEJA (per iFixit and several other sites). And these are the only known devices to have problems.

Those showing "MMC MMC08G" in parted have a Toshiba eMMC controller and no known issues have sprung up with that controller.

In another posting on XDA a user is checking his Galaxy Note's MMC info:

http://i4.photobucket.com/albums/y115/eltigre363/20120519-034653.jpg

You can see hwrev = 0x0, manfid = 0x000015, oemid = 0x0100, date = 09/2011 in the screenshot.

From the M8G2FA chip I show the following values as well:

hwrev = 0x0, manfid = 0x000015, oemid = 0x0100, date = 09/2011

NOTE: We have a different chip than the Galaxy Note, but I'm pointing out how similar the parts are down to the date!