[7" Kindle Fire HD Q&A, Help & Troubleshooting] peterpion:
I have a KF2 which I managed to get twrp on, but the partitions seem to be messed up in some way. When I boot to recovery and do an adb shell, ls /dev/block, there are only loop and ram devices shown. The emmc chip seems OK though, since I can transfer a CM rom to it, but I can't write it to become 'working'.

When I try to wipe or factory reset from recovery, I get an error to the effect that none of the partitions can be mounted. IE

unable to mount /data, /cache, /system, /efs, storage, /data/media during gui startup

also:

unable to find partition size for /boot, /recovery, /bootloader

So I should probably describe how I got here. I was sold a KF2 as a KF1 so assumed it was KF1 and hence bricked it (didn't check for the otter2 id). I opened it, soldered to the main board as described in other threads, dd'ed the working otter2-u-boot-prod-10.2.4 file directly to /dev/sdf2 on the emmc from my ubuntu desktop. Then put it back together and used fast boot to get otter2-twrp-2.6.3.1-recovery.img and otter2-freedom-boot-10.4.6.img on it. Then transferred CM rom to /sdcard with adb push. Rebooted and tried to continue the CM install but when I get to the wipe part, it fails with the above errors. Even from 'advanced wipe' it still says the same (unable to mount etc). Factory reset the same too.

So I took it apart again, connected it back to the computer, and used gparted to examine the file system. It seems OK, it had an error at first (primary gpt corrupt or something, using backup - I think gparted fixed that for me) fairly consistent with what the guys in the emmc soldering thread see. Then back to the kindle boot, same thing happening as before. Eventually I reformatted each ext4 partition using gparted (from the desktop) to try to fix it, still no joy.

So reading lots of threads here by soup and hash, I tried several of their solutions, like fastboot oem format (I had to put the device ID in there to make it work). None of them have worked.

So when I do a:

adb shell parted /dev/block/mmcblk0 print all

I get:

Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.

(and /dev/block/mmcblk0 does not exist - the only files in that dir are ram0, ram1 etc, and loop0, loop1 etc)

That seems like the problem to me. Twrp is not seeing the emmc at all it seems - even though its loaded off the emmc AFAIK? Which seems weird. Surely the device is able to see the emmc and the first few partitions if its booting to twrp - but once in twrp, none of the partitions - or even the device mmcblk0 - is showing up at all. But when I connect it back to the PC, gparted is happy with it all - although all the partitions show up as microsoft type which seems odd. But I can mount them and browse them (the ext4 ones).

Anyone throw any light on this? BTW the wiring is unlikely to be causing this problem because I disconnect all the wires from any 'interconnections' when I put the kindle back together. Although the wires are still connected to the main board, there are no bridges between dat0, dat1 etc, as I am using a connector to isolate them.

EDIT: And theres this in dmesg, which seems suspicous:

<4>[ 1.053588] mmc0: host doesn't support card's voltages

<3>[ 1.053588] mmc0: error -22 whilst initialising MMC card

<4>[ 1.067321] wifi_set_power: 1

<4>[ 1.118896] mmc1: card claims to support voltages below the defined range. These will be ignored.

Thanks, Pete