[Q] Kindle fire HD 7" not recognised as an MTP device anymore

---

I have a Kinde fire HD 7" that I rooted for a neighbours son which he managed to brick within 20 Mins of getting it back, I think the battery died on him when he was installing something. Now when I plug the Kindle into my system which runs Linux I get the following in the logs.

Feb 13 15:01:05 kernel: [ 161.419037] usb 1-5: new high speed USB device using ehci_hcd and address 5
Feb 13 15:01:05 kernel: [ 161.533760] usb 1-5: New USB device found, idVendor=0451, idProduct=d010
Feb 13 15:01:05 kernel: [ 161.533767] usb 1-5: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 13 15:01:05 kernel: [ 161.533772] usb 1-5: Product: OMAP4440
Feb 13 15:01:05 kernel: [ 161.533775] usb 1-5: Manufacturer: Texas Instruments
Feb 13 15:01:05 mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Feb 13 15:01:05 mtp-probe: bus: 1, device: 5 was not an MTP device
Feb 13 15:01:08 kernel: [ 164.534204] usb 1-5: USB disconnect, address 5
Feb 13 15:01:08 kernel: [ 165.305041] usb 1-5: new high speed USB device using ehci_hcd and address 6
Feb 13 15:01:09 kernel: [ 165.419856] usb 1-5: New USB device found, idVendor=0451, idProduct=d010
Feb 13 15:01:09 kernel: [ 165.419863] usb 1-5: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 13 15:01:09 kernel: [ 165.419868] usb 1-5: Product: OMAP4440
Feb 13 15:01:09 kernel: [ 165.419871] usb 1-5: Manufacturer: Texas Instruments
Feb 13 15:01:09 mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Feb 13 15:01:09 mtp-probe: bus: 1, device: 6 was not an MTP device
Feb 13 15:01:12 kernel: [ 168.420300] usb 1-5: USB disconnect, address 6`

This repeats ad infinitum, well at least 30 times I unplugged it after that.

My question is this, will I be able to to restore the Kindle using the Factory cable from SkOrPn or is this a case where I need to send it back to Amazon ??

Any help would be much appreciated.

Originally Posted by JBDegriz

I have a Kinde fire HD 7" that I rooted for a neighbours son which he managed to brick within 20 Mins of getting it back, I think the battery died on him when he was installing something. Now when I plug the Kindle into my system which runs Linux I get the following in the logs.

This repeats ad infinitum, well at least 30 times I unplugged it after that.

My question is this, will I be able to to restore the Kindle using the Factory cable from SkOrPn or is this a case where I need to send it back to Amazon ??

Any help would be much appreciated.

Is the device still able to comunicate with ADB? If it can then you do not need a fastboot cable. If it does not then yes you will need one to restore it..

Originally Posted by lacoursiere18

Is the device still able to comunicate with ADB? If it can then you do not need a fastboot cable. If it does not then yes you will need one to restore it..

No ADB never sees the device any more as the USB just keeps reconnecting and disconnecting. The same thing happens in windows where I keep getting the sound when you connect a usb device over and over again and windows looks for a device driver for an OMAP4440, which I believe is the CPU in the Kindle.

So I need to know that in a situation like this that the Factory cable would actually help, I'm sure I read somewhere that fastboot mode needs a working bootloader and I'm not sure that this kindles bootloader is still there.

Thanks

Originally Posted by JBDegriz

No ADB never sees the device any more as the USB just keeps reconnecting and disconnecting. The same thing happens in windows where I keep getting the sound when you connect a usb device over and over again and windows looks for a device driver for an OMAP4440, which I believe is the CPU in the Kindle.

So I need to know that in a situation like this that the Factory cable would actually help, I'm sure I read somewhere that fastboot mode needs a working bootloader and I'm not sure that this kindles bootloader is still there.

Thanks

Yea it doesn't sound like it's in working order, so yes, a fastboot cable would be need to get the device back in action..