Database Develop

[Q] Nexus One bricked, help?

So my phone just died. It doesn't power on, and doesn't turn on the charging LED. At first I thought the battery was completely dead, and I read that the Nexus One won't charge the battery if it's completely drained, but after checking with a known good battery from a friend's HTC Desire it's still exhibiting the same symptoms. Also, my battery is apparently fine and 100% full, so the phone is still capable of charging at least.
I've tried multiple chargers, connecting by USB to a computer, pressing buttons in strange orders, holding the power button with the battery removed, removing SD card and SIM card, you name it. Phone doesn't do anything.
The annoying part is that I didn't do anything to it this time... It ran out of battery, so I hooked it up to a charger and turned it back on. It booted, vibrated a few times, then turned itself off (It sometimes does this if I turn it on right after connecting to a wall charger, because the battery is still too empty). So I left it off and connected to a wall charger. When I came back it was like this.
When connecting it to a Linux computer, it recognizes that it's a USB device, but gets a protocol error (looked up what -71 means) like this:
Code:
[320548.660641] usb 6-2: new full speed USB device using uhci_hcd and address 38
[320548.790023] usb 6-2: device descriptor read/64, error -71
[320549.030014] usb 6-2: device descriptor read/64, error -71
[320549.260016] usb 6-2: new full speed USB device using uhci_hcd and address 39
[320549.390015] usb 6-2: device descriptor read/64, error -71
[320549.630609] usb 6-2: device descriptor read/64, error -71
[320549.860015] usb 6-2: new full speed USB device using uhci_hcd and address 40
[320550.280638] usb 6-2: device not accepting address 40, error -71
[320550.400639] usb 6-2: new full speed USB device using uhci_hcd and address 41
[320550.820012] usb 6-2: device not accepting address 41, error -71
[320550.820022] hub 6-0:1.0: unable to enumerate USB device on port 2
This isn't good news, I think
The phone isn't new, it's out of warranty and even if it were still in warranty, I've voided it. It's rooted, and I replaced a broken screen last month. Worked fine since the repair, though...
So, anyone seen something like this before? Anything I can try?

Did you solve this problem? What is the solution?

Put it in the freezer for a couple of hours.

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

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

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

stunts513 said:
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
Click to expand...
Click to collapse
Hmmm... Here's the output of lsusb and dmesg. The last part of dmesg is interesting.
Code:
[email protected] ~ $ 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
[email protected] ~ $
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?

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

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.

Myk Robinson said:
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.
Click to expand...
Click to collapse
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.

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

luigirocks said:
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.
Click to expand...
Click to collapse
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.

Fixing IP address on USB to Ethernet device

We have a device that added a driver to the AOSP kernel build. It pops up an ethernet interface when you plug it into the usb port. DHCP is started on the port, but we want to make it a fixed address. Is there a way to set a fixed address on a USB/Ethernet device plugged into Android?
Thx
Y-

USB cable not detected

Hello.
My Zenfone 4 (ZE554KL) is updated at WW_ZE554KL_15.0405.1803.99 and Android 8.0. My usb cable is not being detected by any Windows 7 computers. I've tried with 3 different computers, no "Unknown devices" at devices manager, it's only charging.
Any ideas what this can be?
Thanks.

sprint note 5 computer descriptor error but otg fine

Title says my problem, I can access a flash drive through other just fine but if I plug my phone into my computer I get a descriptor error. I have tried 3 cables and two computers and nothing has helped

Well, now when I plug it in windows can see it fine and otg still works. I have no idea what was wrong because it is the same USB port and same cable