Bricked, got factory cable, and usb device to show. What now?

Search This thread
By:
Advanced…
M

Moronig

Senior Member
Dec 2, 2010
419
206
Curitiba
Okay, so I finally managed to solder a working factory cable, and the ot a response from my Kindle Fire HDX 7" (as far as usb is concerned);
Here is the state my HDX is in: If i hold power for 16 seconds, it will start to boot, show the all grey "kindle fire" logo, then the screen turns off.
If I turn it on with the Volume+ button pressed, I get to stock recovery. No amount of factory reset and rebooting will do any good here.
In both cases above, I will get nothing at all on USB when plugged to a computer. No message about it even being plugged in on dmesg.

When I plug in the factory cable, I get a reponse, but a lot of "new high-speed USB device, device descriptor read/64, error -110".
Now here is the interesting part, when I hold power with the factory cable plugged, the device is recognized! Logs will be at the end.

The problem here is I can't get fastboot to show devices. I tried the following:

fastboot devices
fastboot -i 0x1949 devices
fastboot -i 0x05c6 devices
fastboot -s 0 devices
fastboot -s ttyUSB0 devices
fastboot -s /dev/ttyUSB0 devices

And get nothing. I think I am on the right track to getting it to work again, but I'm at a loss about what to do next.

I'm willing to try anything as long as it doesn't involve screwdrivers and/or snakes!

Here is the log from dmesg:

Code: 
[Ter Dez  3 07:47:10 2013] usb 2-1.2: >new high-speed USB device number 39 using ehci_hcd
[Ter Dez  3 07:47:25 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:47:40 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:47:40 2013] usb 2-1.2: >new high-speed USB device number 40 using ehci_hcd
[Ter Dez  3 07:47:55 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:48:10 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:48:11 2013] usb 2-1.2: >new high-speed USB device number 41 using ehci_hcd
[Ter Dez  3 07:48:21 2013] usb 2-1.2: >device not accepting address 41, error -110
[Ter Dez  3 07:48:21 2013] usb 2-1.2: >new high-speed USB device number 42 using ehci_hcd
[Ter Dez  3 07:48:31 2013] usb 2-1.2: >device not accepting address 42, error -110
[Ter Dez  3 07:48:31 2013] hub 2-1:1.0: >unable to enumerate USB device on port 2
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >new high-speed USB device number 43 using ehci_hcd
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >New USB device found, idVendor=05c6, idProduct=9008
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Product: QHSUSB__BULK
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Manufacturer: Qualcomm CDMA Technologies MSM
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver usbserial
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver usbserial_generic
[Ter Dez  3 07:48:42 2013] USB Serial support registered for generic
[Ter Dez  3 07:48:42 2013] usbserial: USB Serial Driver core
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver qcserial
[Ter Dez  3 07:48:42 2013] USB Serial support registered for Qualcomm USB modem
[Ter Dez  3 07:48:42 2013] qcserial 2-1.2:1.0: >Qualcomm USB modem converter detected
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Qualcomm USB modem converter now attached to ttyUSB0

Here is usb-devices and lsusb output, in case it's needed:

Code: 
T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 43 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=05c6 ProdID=9008 Rev=00.00
S:  Manufacturer=Qualcomm CDMA Technologies MSM
S:  Product=QHSUSB__BULK
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=2mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=qcserial

Code: 
Bus 002 Device 051: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x05c6 Qualcomm, Inc.
  idProduct          0x9008 Gobi Wireless Modem (QDL mode)
  bcdDevice            0.00
  iManufacturer           1 Qualcomm CDMA Technologies MSM
  iProduct                2 QHSUSB__BULK
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Thanks!
 
Last edited:
  • Like
Reactions: ferrouskid
Android Cowboy

Android Cowboy

Senior Member
Jan 17, 2012
307
111
androidcowboy.com
Moronig said:
Okay, so I finally managed to solder a working factory cable, and the ot a response from my Kindle Fire HDX 7" (as far as usb is concerned);
Here is the state my HDX is in: If i hold power for 16 seconds, it will start to boot, show the all grey "kindle fire" logo, then the screen turns off.
If I turn it on with the Volume+ button pressed, I get to stock recovery. No amount of factory reset and rebooting will do any good here.
In both cases above, I will get nothing at all on USB when plugged to a computer. No message about it even being plugged in on dmesg.

When I plug in the factory cable, I get a reponse, but a lot of "new high-speed USB device, device descriptor read/64, error -110".
Now here is the interesting part, when I hold power with the factory cable plugged, the device is recognized! Logs will be at the end.

The problem here is I can't get fastboot to show devices. I tried the following:

fastboot devices
fastboot -i 0x1949 devices
fastboot -i 0x05c6 devices
fastboot -s 0 devices
fastboot -s ttyUSB0 devices
fastboot -s /dev/ttyUSB0 devices

And get nothing. I think I am on the right track to getting it to work again, but I'm at a loss about what to do next.

I'm willing to try anything as long as it doesn't involve screwdrivers and/or snakes!

Here is the log from dmesg:

Code: 
[Ter Dez  3 07:47:10 2013] usb 2-1.2: >new high-speed USB device number 39 using ehci_hcd
[Ter Dez  3 07:47:25 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:47:40 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:47:40 2013] usb 2-1.2: >new high-speed USB device number 40 using ehci_hcd
[Ter Dez  3 07:47:55 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:48:10 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:48:11 2013] usb 2-1.2: >new high-speed USB device number 41 using ehci_hcd
[Ter Dez  3 07:48:21 2013] usb 2-1.2: >device not accepting address 41, error -110
[Ter Dez  3 07:48:21 2013] usb 2-1.2: >new high-speed USB device number 42 using ehci_hcd
[Ter Dez  3 07:48:31 2013] usb 2-1.2: >device not accepting address 42, error -110
[Ter Dez  3 07:48:31 2013] hub 2-1:1.0: >unable to enumerate USB device on port 2
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >new high-speed USB device number 43 using ehci_hcd
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >New USB device found, idVendor=05c6, idProduct=9008
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Product: QHSUSB__BULK
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Manufacturer: Qualcomm CDMA Technologies MSM
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver usbserial
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver usbserial_generic
[Ter Dez  3 07:48:42 2013] USB Serial support registered for generic
[Ter Dez  3 07:48:42 2013] usbserial: USB Serial Driver core
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver qcserial
[Ter Dez  3 07:48:42 2013] USB Serial support registered for Qualcomm USB modem
[Ter Dez  3 07:48:42 2013] qcserial 2-1.2:1.0: >Qualcomm USB modem converter detected
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Qualcomm USB modem converter now attached to ttyUSB0

Here is usb-devices and lsusb output, in case it's needed:

Code: 
T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 43 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=05c6 ProdID=9008 Rev=00.00
S:  Manufacturer=Qualcomm CDMA Technologies MSM
S:  Product=QHSUSB__BULK
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=2mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=qcserial

Code: 
Bus 002 Device 051: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x05c6 Qualcomm, Inc.
  idProduct          0x9008 Gobi Wireless Modem (QDL mode)
  bcdDevice            0.00
  iManufacturer           1 Qualcomm CDMA Technologies MSM
  iProduct                2 QHSUSB__BULK
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Thanks!
Click to expand...
Click to collapse

How about adb devices. Is that working. If so that could help. My brick Kindle went totally dead on me. Won't power on at all even plugged in. Not even the grey Kindle shows up.

Sent from my Nexus 5 using Tapatalk
 
M

Moronig

Senior Member
Dec 2, 2010
419
206
Curitiba
Android Cowboy said:
How about adb devices. Is that working. If so that could help. My brick Kindle went totally dead on me. Won't power on at all even plugged in. Not even the grey Kindle shows up.

Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

Nope, nothing on adb devices either. And my Kindle stopped responding completely. I'm afraid the factory cable burned something, but if yours is dead as well, that could be the battery going dead. Maybe the bootloader won't boot far enought to let the battery charge. Did your stop showing the grey kindle by itself?
 
Android Cowboy

Android Cowboy

Senior Member
Jan 17, 2012
307
111
androidcowboy.com
Moronig said:
Nope, nothing on adb devices either. And my Kindle stopped responding completely. I'm afraid the factory cable burned something, but if yours is dead as well, that could be the battery going dead. Maybe the bootloader won't boot far enought to let the battery charge. Did your stop showing the grey kindle by itself?
Click to expand...
Click to collapse

Plugged it for 30min and it's turning on again. Being recognized by pc now with fastboot cable.. Testing at the moment.

Sent from my Nexus 5 using Tapatalk
 
  • Like
Reactions: davekaz and Spec-Chum
donharden2002

donharden2002

Senior Member
Nov 25, 2010
1,932
144
Pittsburgh
I'm able to get adb recognized but not fastboot. Been searching for fastboot drivers with no luck.
Mine acts like it wants to boot up but then I get fooled and try to unlock it real quick with no luck.
It's teasing me.

Sent from my LG-D800 using XDA Premium 4 mobile app
 
D

doggyxxx

Member
Apr 4, 2008
16
0
Android Cowboy said:
I was not able to recover. But there is another thread in the forum that does show how to get the device to be properly recognized and possible recovery.
Click to expand...
Click to collapse


Do you have idea of what make your kindle become un-recoverable? I've done factory reset after my kindle is bricked. Do you think this would make the recover hopeless?
 
F

ferrouskid

Senior Member
Mar 12, 2014
105
26
Android Cowboy said:
I was not able to recover. But there is another thread in the forum that does show how to get the device to be properly recognized and possible recovery.
Click to expand...
Click to collapse

Hello
I have been following android cowboy for a long time, got root, custom rom and etc on kindle fire hdx, but now its bricked, can you Please give a link to that thread,

Thanks a LOT.
 
You must log in or register to reply here.

Similar threads

C
Need Help on How to Download Torrents on Kindle Fire HDX
Replies
4
Views
56K
tl3
tl3
hth2813
USB OTG on Kindle Fire HDX
Replies
10
Views
33K
shabbypenguin
shabbypenguin
sd_shadow
  • Sticky
[Help Thread]Kindle Fire HDX 7" & 8.9" (3rd Gen/2013) Ask Any Question, Noob Friendly
Replies
731
Views
56K
wavvy01
wavvy01
T
install Google play on Kindle Fire HDX 7 (3rd Generation) os 4.5.5.1
Replies
2
Views
32K
J
jolo100
R
root kindle fire hdx 7" 3rd generation
Replies
7
Views
27K
DB126
DB126

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 2
    Android Cowboy
    Android Cowboy
    Moronig said:
    Nope, nothing on adb devices either. And my Kindle stopped responding completely. I'm afraid the factory cable burned something, but if yours is dead as well, that could be the battery going dead. Maybe the bootloader won't boot far enought to let the battery charge. Did your stop showing the grey kindle by itself?
    Click to expand...
    Click to collapse

    Plugged it for 30min and it's turning on again. Being recognized by pc now with fastboot cable.. Testing at the moment.

    Sent from my Nexus 5 using Tapatalk
    View
    1
    M
    Moronig
    Okay, so I finally managed to solder a working factory cable, and the ot a response from my Kindle Fire HDX 7" (as far as usb is concerned);
    Here is the state my HDX is in: If i hold power for 16 seconds, it will start to boot, show the all grey "kindle fire" logo, then the screen turns off.
    If I turn it on with the Volume+ button pressed, I get to stock recovery. No amount of factory reset and rebooting will do any good here.
    In both cases above, I will get nothing at all on USB when plugged to a computer. No message about it even being plugged in on dmesg.

    When I plug in the factory cable, I get a reponse, but a lot of "new high-speed USB device, device descriptor read/64, error -110".
    Now here is the interesting part, when I hold power with the factory cable plugged, the device is recognized! Logs will be at the end.

    The problem here is I can't get fastboot to show devices. I tried the following:

    fastboot devices
    fastboot -i 0x1949 devices
    fastboot -i 0x05c6 devices
    fastboot -s 0 devices
    fastboot -s ttyUSB0 devices
    fastboot -s /dev/ttyUSB0 devices

    And get nothing. I think I am on the right track to getting it to work again, but I'm at a loss about what to do next.

    I'm willing to try anything as long as it doesn't involve screwdrivers and/or snakes!

    Here is the log from dmesg:

    Code: 
    [Ter Dez  3 07:47:10 2013] usb 2-1.2: >new high-speed USB device number 39 using ehci_hcd
[Ter Dez  3 07:47:25 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:47:40 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:47:40 2013] usb 2-1.2: >new high-speed USB device number 40 using ehci_hcd
[Ter Dez  3 07:47:55 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:48:10 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez  3 07:48:11 2013] usb 2-1.2: >new high-speed USB device number 41 using ehci_hcd
[Ter Dez  3 07:48:21 2013] usb 2-1.2: >device not accepting address 41, error -110
[Ter Dez  3 07:48:21 2013] usb 2-1.2: >new high-speed USB device number 42 using ehci_hcd
[Ter Dez  3 07:48:31 2013] usb 2-1.2: >device not accepting address 42, error -110
[Ter Dez  3 07:48:31 2013] hub 2-1:1.0: >unable to enumerate USB device on port 2
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >new high-speed USB device number 43 using ehci_hcd
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >New USB device found, idVendor=05c6, idProduct=9008
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Product: QHSUSB__BULK
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Manufacturer: Qualcomm CDMA Technologies MSM
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver usbserial
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver usbserial_generic
[Ter Dez  3 07:48:42 2013] USB Serial support registered for generic
[Ter Dez  3 07:48:42 2013] usbserial: USB Serial Driver core
[Ter Dez  3 07:48:42 2013] usbcore: registered new interface driver qcserial
[Ter Dez  3 07:48:42 2013] USB Serial support registered for Qualcomm USB modem
[Ter Dez  3 07:48:42 2013] qcserial 2-1.2:1.0: >Qualcomm USB modem converter detected
[Ter Dez  3 07:48:42 2013] usb 2-1.2: >Qualcomm USB modem converter now attached to ttyUSB0

    Here is usb-devices and lsusb output, in case it's needed:

    Code: 
    T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 43 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=05c6 ProdID=9008 Rev=00.00
S:  Manufacturer=Qualcomm CDMA Technologies MSM
S:  Product=QHSUSB__BULK
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=2mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=qcserial

    Code: 
    Bus 002 Device 051: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x05c6 Qualcomm, Inc.
  idProduct          0x9008 Gobi Wireless Modem (QDL mode)
  bcdDevice            0.00
  iManufacturer           1 Qualcomm CDMA Technologies MSM
  iProduct                2 QHSUSB__BULK
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

    Thanks!
    View
    1
    F
    ferrouskid
    Android Cowboy said:
    xdaforums.com/showthread.php?t=2588608

    Sent from my Nexus 5 using Tapatalk
    Click to expand...
    Click to collapse


    Thanks so much man.
    View

New posts