Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] Root Attempt - Kindle Fire HD not Recognized, in Windows or Linux?

OP Myk Robinson

10th February 2014, 03:17 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: Feb 2014
Morning, all.

A friend of mine bought a Kindle Fire HD 7" and would like to root it so he can install the Google Play store and actually have some useful apps on it. He gave it to me to try that task. I acquired everything I need to be able to install CM11 on the tablet and attempted it initially from a Windows 8.1 machine at my office. Had a heck of a time with the driver, but even with the driver installed, the device just wasn't recognized.

i thought maybe it's the cable, maybe it's the operating system... So I took it home and used a different USB cable and used my Linux laptop, which doesn't need any special drivers and can do adb natively. The tablet is not recognized in Linux either. I tried issuing the lsusb command to see if anything registered as being plugged into the USB bus, and I get the same list with the tablet plugged or unplugged.

Any ideas? Is a proprietary cable required? Is there something I'm missing in the tablet that needs to be turned on? In both cases, the tablet was charging from the USB connection, so I assume the cable may be fine.

Any advice?

Thanks, guys
11th February 2014, 01:54 AM   |  #2  
stunts513's Avatar
Recognized Contributor
Flag New Braunfels, TX
Thanks Meter: 610
 
2,230 posts
Join Date:Joined: Feb 2013
Donate to Me
More
It should be recognized by Linux with lusb as a lab126 device if I remember correctly. Also after you plug it in try running dmesg and see if it detects a usb device that can read the descriptors, if that's the case that's bad.

My spell check butchered this messages computer terms first time round...

Sent from my LG-P769 using xda app-developers app
11th February 2014, 02:38 PM   |  #3  
OP Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: Feb 2014
Exclamation
Quote:
Originally Posted by stunts513

It should be recognized by Linux with lusb as a lab126 device if I remember correctly. Also after you plug it in try running dmesg and see if it detects a usb device that can read the descriptors, if that's the case that's bad.

My spell check butchered this messages computer terms first time round...

Sent from my LG-P769 using xda app-developers app

Hmmm... Here's the output of lsusb and dmesg. The last part of dmesg is interesting.

Code:
myk@AspireV5 ~ $ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0489:e04e Foxconn / Hon Hai 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 064e:e330 Suyin Corp. 
Bus 003 Device 002: ID 04f3:0023 Elan Microelectronics Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
myk@AspireV5 ~ $
and



Code:
--truncated to tail of dmesg

[   36.463231] ehci-pci 0000:00:1a.0: setting latency timer to 64
[   36.464783] init: anacron main process (2862) killed by TERM signal
[   66.745309] usb 3-2: new full-speed USB device number 4 using xhci_hcd
[   66.745419] usb 3-2: Device not responding to set address.
[   66.949337] usb 3-2: Device not responding to set address.
[   67.153197] usb 3-2: device not accepting address 4, error -71
[   67.265148] usb 3-2: new full-speed USB device number 5 using xhci_hcd
[   67.265255] usb 3-2: Device not responding to set address.
[   67.469243] usb 3-2: Device not responding to set address.
[   67.673032] usb 3-2: device not accepting address 5, error -71
[   67.784984] usb 3-2: new full-speed USB device number 6 using xhci_hcd
[   67.785093] usb 3-2: Device not responding to set address.
[   67.989067] usb 3-2: Device not responding to set address.
[   68.192846] usb 3-2: device not accepting address 6, error -71
[   68.304939] usb 3-2: new full-speed USB device number 7 using xhci_hcd
[   68.305078] usb 3-2: Device not responding to set address.
[   68.508931] usb 3-2: Device not responding to set address.
[   68.712692] usb 3-2: device not accepting address 7, error -71
[   68.712727] hub 3-0:1.0: unable to enumerate USB device on port 2
ideas?
11th February 2014, 07:58 PM   |  #4  
stunts513's Avatar
Recognized Contributor
Flag New Braunfels, TX
Thanks Meter: 610
 
2,230 posts
Join Date:Joined: Feb 2013
Donate to Me
More
Weird I was kinda expecting it to say "device descriptor read/64 error" error as well, either way that's not exactly good. This is a USB 2.0 port right? And you said you tried a different cable too?

Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
11th February 2014, 08:46 PM   |  #5  
OP Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: Feb 2014
Question
I get the same result through a USB2 or USB3 port. I am going to try to stop by my friend's and get the original cable that came with the Kindle, but I have been able to duplicate it across two cables.
12th February 2014, 01:16 AM   |  #6  
Junior Member
Thanks Meter: 0
 
24 posts
Join Date:Joined: Aug 2013
Quote:
Originally Posted by Myk Robinson

I get the same result through a USB2 or USB3 port. I am going to try to stop by my friend's and get the original cable that came with the Kindle, but I have been able to duplicate it across two cables.

This is a pretty stupid question but have you installed kindle fire adb drivers? I could send you a link to the ones I used, in case the ones you installed are bad? I had some trouble with this as well. And after Installed them, I rooted my kindle and had omnirom on it haha.
12th February 2014, 01:27 AM   |  #7  
stunts513's Avatar
Recognized Contributor
Flag New Braunfels, TX
Thanks Meter: 610
 
2,230 posts
Join Date:Joined: Feb 2013
Donate to Me
More
He's on Linux so he has no need for drivers. There's some kind of communication problem on the devices end.

Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
12th February 2014, 02:21 AM   |  #8  
OP Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: Feb 2014
Quote:
Originally Posted by luigirocks

This is a pretty stupid question but have you installed kindle fire adb drivers? I could send you a link to the ones I used, in case the ones you installed are bad? I had some trouble with this as well. And after Installed them, I rooted my kindle and had omnirom on it haha.

No worries

I first tried it in Windows 8 using the Kindle ADB drivers. Thinking that either Windows or the software was flaky, I then tried it on my Linux computer.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes