[7" Kindle Fire HD Q&A, Help & Troubleshooting] gde061:
I originally posted this question in XDA Assist yesterday. I was directed to this forum, and after reading more here, have added a few more questions/concerns with ***___**** that came after digging through the forum stickies. I know this has become a huge post, so apologies in advance.

I'm having some trouble mounting a Kindle Fire HD 7 Gen2 (Tate) in Fastboot mode on my system which is running Ubuntu 14.04.

I am new to any kind of Android development and have been following the excellent guides here by [MENTION=4422144]kinfauns[/MENTION]. Specifically I have the 5-scecond boot loop problem related to the power draw issue. The solution I'm pursuing is to swap the stock bootloader for FireFireFire. The guide says to do it with fastboot, since the conventional flash recovery method could be interrupted by the shutdown cycle.

******* After reading the Faq here, I am concerned that even if Fastboot were to detect the device, that simply using it to load the FireFireFire bootloader directly onto the device would cause the problem of the wall of fire because of the M-Shield issue. Seems I would have to follow these steps here or here to load FireFireFire as a 2nd bootloader (including downgrading the OS to v7.2.3), is that correct? Also one of those pages says not to use automated tools like FireFireFire... which I thought was a bootloader, so what bootloader should I use to get around the low battery cycle startup problem that FireFireFire specifically addresses with it's startup battery check *******

So now, just when I think I have a solution to my real problem, I get out the fastboot cable, connect the kindle to my PC, and I get an error in Nautilus.

******In one of the pages linked above, it makes a passing reference to some fastboot cables not putting the device in Fastboot. Since I cannot connect to the device in the first place when it is in "fastboot", I cannot use their method to confirm fastboot is working. When bootup with my fastboot cable, the "image" on the device

does

change from orange & flashing "Kinde Fire" to the orange "Kindle Fastboot" pic, so I'd to know if I can rule out the cable as part of my problem... *****

Here is the error from Nautilus: Unable to open MTP device '[usb:001,006]'. Attempting mtpfs at the terminal returns:

Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)

Device 0 (VID=1949 and PID=0007) is a Amazon Kindle Fire (ID1).

Found 1 device(s):

Amazon: Kindle Fire (ID1) (1949:0007) @ bus 1, dev 6

Attempting to connect device

LIBMTP PANIC: Unable to find interface & endpoints of device

Unable to open raw device 0

I found a tutorial on Ubuntu forums for getting MTP to work that involved using lsusb command to get the device id, making entries in /etc/udeb/rules.d and /lib/udev/rules.d, supposedly to allow MTP to access the device with proper credentials. However that didn't work. It seems that in Fastboot I actually might not MTP to handle the device...

OTOH, when the device is NOT in Fastboot mode, it mounts just fine, both in Nautilus and for purposes of checking with the adb devices command....

***** Since yesterday, I back and compared the vendor and product codes reported in lsusb and noticed that they are

the same

regardless of whether I connect the device using a regular cable (when it mounts correctly) and the fastboot cable (when the screen says fastboot, and I get the "raw device" failure to mount. My understanding is that the

hardware ID should be different

if the device is in fastboot mode vs "normal" mode. Is that correct? How do I deal with this behavior if the device is supposed to load different drivers when in different modes?*****

However, it seems to me that what I want is for it to mount in file transfer mode instead of MTP mode when in fastboot. The fix for this exact issue in Windows (as reported on other sites) is to change the driver in Windows Device Manager.

***** The other thing I tried was using the modprobe command to manually start the usb-storage driver as explained here. However the step to confirm the driver was unsuccessful because the /var/log/messages file was not found by the tail command. Even though that is really an ubuntu / linux question, perhaps someone here can help with some guidance on confirming the mass storage driver as well?*****

Can anybody help with this problem please?

Thank you