Database Develop

[Q] lsusb not listing HTC Dream TMobile

Hi All,
I am trying to bypass the google activation. downgraded to RC29 .I typed this in the device with no sim card <enter>setprop persist.service.adb.enable 1<enter>. but when i connect my device using usb port . i see this in the syslogs
usb 1-1.1: new high speed USB device using ehci_hcd and address 29
[ 4611.770659] usb 1-1.1: device descriptor read/64, error -71
[ 4611.958338] usb 1-1.1: device descriptor read/64, error -71
[ 4612.133841] usb 1-1.1: new high speed USB device using ehci_hcd and address 30
[ 4612.217770] usb 1-1.1: device descriptor read/64, error -71
[ 4612.405259] usb 1-1.1: device descriptor read/64, error -71
[ 4612.581176] usb 1-1.1: new high speed USB device using ehci_hcd and address 31
[ 4612.996080] usb 1-1.1: device not accepting address 31, error -71
[ 4613.067744] usb 1-1.1: new high speed USB device using ehci_hcd and address 32
[ 4613.482836] usb 1-1.1: device not accepting address 32, error -71
[ 4613.483094] hub 1-1:1.0: unable to enumerate USB device on port 1
and when i did lsusb htc dream is not listed . please tell me what is wrong with the device. Thanks in Advance.
note: <enter>reboot<enter> worked

do you have adb drivers installed? when did you do lsusb? normally to check you open cmd and go to sdk/platform-tools directory and type 'adb devices'

using ubuntu
ldrifta said:
do you have adb drivers installed? when did you do lsusb? normally to check you open cmd and go to sdk/platform-tools directory and type 'adb devices'
Click to expand...
Click to collapse
Hi
I am using ubuntu 10.10 , so i assumed that usb drivers come with the distro.
adb devices
list nothing even when the device is connected.
Thanks

go here... http://developer.android.com/sdk/index.html
and do some reading... should help you get started

Most likely your phone's vendor and device keys need to be added to the udev rules.
Sent from my Gingerbread on Dream using XDA App

usb cable issue
Sorry guys its my bad, i was using a micro usb cable instead of the usb connector that came with G1. now i am able to connected to the device using adb shell. Sorry again. Thanks to all

so much,but,the next is good

i use a regular micro usb cable and it works fine... but some may be different in some as o cant garuntee anything

USB 3.X xHCI module woes

Hi,
I wanted to try to play around with roms for the P1010 (most are for the P1000, so It's really just me trying to see if I can't do a really bad port), so I downloaded Heimdall, put my P1010 into download mode, and checked to see if Heimdall could find my device. It couldnt, but no wonder it couldn't:
Code:
[ 144.398094] usb 3-3: new high-speed USB device number 7 using xhci_hcd
[ 144.411594] usb 3-3: device descriptor read/8, error -75
[ 144.528102] usb 3-3: device descriptor read/8, error -75
[ 144.790846] usb 3-3: new high-speed USB device number 8 using xhci_hcd
[ 144.804350] usb 3-3: device descriptor read/8, error -75
[ 144.920834] usb 3-3: device descriptor read/8, error -75
[ 145.183559] usb 3-3: new high-speed USB device number 9 using xhci_hcd
[ 145.197101] usb 3-3: device descriptor read/8, error -75
[ 145.313586] usb 3-3: device descriptor read/8, error -75
[ 145.576343] usb 3-3: new high-speed USB device number 10 using xhci_hcd
[ 145.589845] usb 3-3: device descriptor read/8, error -75
[ 145.706346] usb 3-3: device descriptor read/8, error -75
[ 145.809327] hub 3-0:1.0: unable to enumerate USB device on port 3
Well, that makes sense. Heimdall can't detect the device if the kernel has trouble recognising the device. So it looks like the xhci_hcd kernel module is having trouble recognising the device. Doing a little research. I've concluded that all of my USB ports are USBv3 ports because all of my USB ports use the xHCI module. If they were v2, they would use eHCI. Further research suggests that download mode with USBv3.x on linux appears to be buggy at the moment. I found reports of people using Heimdall with USB 3 devices, not working, getting the same error, then plugging it into a USBv2 port and it working.
So I'm sort of stuck at this point. My computer came with all USBv3 ports. Does anyone have experience with USBv3 ports and linux? Have you managed to get it to work with the xHCD module? Is there an alternate module that I can use that works better? Does anyone have any more info on this issue?
Thanks,
Dragos

heimdall problem with xhci-hcd module
i have exactly the same problem (and dmesg-logging) with my GT-P5110 tablet on my asus laptop R704A, with ubuntu 12.10 installed.
heimdall does not detect this tablet.
the xhci-hcd module is in kernel embedded, so i can't blacklist that module.
instead i tried to unbind :
conform: ref: ubuntuforums.org/showthread.php?p=9180298#post9180298
echo -n "XXXX:XX:XX.X" | tee /sys/bus/pci/drivers/xhci_hcd/unbind
but without success.
the mentioned problem does not occur with heimdall on the same laptop with my I9300-smartphone connected.
with ADB i don't have any detect problem with the GT-P5110 and I9300-phone.
--
my GT-5110 and I9300 are working perfectly with heimdall on a laptop with the same ubuntu release, but without a usb3.0 interface.

Just found this thread after searching for exactly the same problem. I'm trying to connect a GT-P5110 to Ubuntu (12.10 as well as 13.04) just like you seem to try. Does anyone know if it works on other systems?

I am having this issue too..
[ 37.151513] usb 1-2: new high-speed USB device number 2 using xhci_hcd
[ 37.167861] usb 1-2: device descriptor read/8, error -75
[ 37.287940] usb 1-2: device descriptor read/8, error -75
[ 37.503921] usb 1-2: new high-speed USB device number 3 using xhci_hcd
[ 37.520265] usb 1-2: device descriptor read/8, error -75
[ 37.640343] usb 1-2: device descriptor read/8, error -75
[ 37.856292] usb 1-2: new high-speed USB device number 4 using xhci_hcd
[ 37.872608] usb 1-2: device descriptor read/8, error -75
[ 37.992803] usb 1-2: device descriptor read/8, error -75
[ 38.208755] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 38.225032] usb 1-2: device descriptor read/8, error -75
[ 38.345139] usb 1-2: device descriptor read/8, error -75
[ 38.449017] hub 1-0:1.0: unable to enumerate USB device on port 2
Click to expand...
Click to collapse

I am having the exact same issue trying to root a Galaxy Tab 2 7.0, I too have only v3 USB ports, were you able to figure out a way around this?

[Q] Probably broke the bootloader

Greetings,
I am in search for help to restore my GT-P1000 (p1); I do not have any SD in it.
Here what it happened:
I upgraded it from cm-10.1-20131117-NIGHTLY-p1.zip to cm-11-20131207-NIGHTLY-p1.zip
After the update it was really blazingly fast, more than with CM 10.x; everything worked: bluetooth, camera, radio, wifi, flash, gps, etc.
Then I upgraded gapps, installing those of CM11.
And rebooted.
Then I noticed I forgot to Clear the cache and Dalvik cache and rebooted in maintainance mode and there I misclicked and formatted /system.
I tried to reinstall stock 2.3.3 android and then reinstall CM-11, but Odin fails to recognize the device.
From my limited knowledge of Android, apart from removing everything I think I broke the bootloader. In fact:
* Odin does not recognize the Tab when in Download mode (POWEL + VOL DOWN) (I tried with Windows XP, 7, 8; connecting the tab after and before starting Odin, etc); the strange fact is that Heimdall recognizes the device;
* When the Tab is plugged to recharge, it boots in Maintainance mode (like POWER + VOL UP).
Can anybody help me to get Odin work again with my tab?

You can use heimdall.
If you need to use odin, reinstall the windows USB driver for Samsung.
you probably never tried with odin after you had heimdall while the tab was still ok.
You can't damage a bootloader with just flashing and playing with recovery.
Sent from my GT-N7100 using xda app-developers app

priyana said:
You can use heimdall.
If you need to use odin, reinstall the windows USB driver for Samsung.
you probably never tried with odin after you had heimdall while the tab was still ok.
Click to expand...
Click to collapse
Yes, I did.
From different PCs, with windows XP, 7 and 8.
With Kies or just the Samsung drivers - http://forum.xda-developers.com/showthread.php?t=961956 - and every time Odin does not recognize the Galaxy Tab. Windows detects a "Gadget Serial" device attached to the USB port, but it does not associate a driver to it. Manually doing so doesn't change the final result: the device is not recognized.
I'll try again with Odin. If there will be no results again I'll resign myself to use Heimdall after reading a guide (I never used it).
On Linux, here is the dmesg output when the tab is plugged to the usb port:
Dec 9 09:29:07 triskelion kernel: [ 1405.595278] usb 2-1.2: new high-speed USB device number 6 using ehci-pci
Dec 9 09:29:08 triskelion kernel: [ 1405.757946] usb 2-1.2: New USB device found, idVendor=04e8, idProduct=6601
Dec 9 09:29:08 triskelion kernel: [ 1405.757956] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 9 09:29:08 triskelion kernel: [ 1405.757962] usb 2-1.2: Product: Gadget Serial
Dec 9 09:29:08 triskelion kernel: [ 1405.757967] usb 2-1.2: Manufacturer: SAMSUNG
Dec 9 09:29:08 triskelion kernel: [ 1405.758474] cdc_acm 2-1.2:2.0: This device cannot do calls on its own. It is not a modem.
Dec 9 09:29:08 triskelion kernel: [ 1405.758575] cdc_acm 2-1.2:2.0: ttyACM0: USB ACM device
Dec 9 09:29:08 triskelion mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
Dec 9 09:29:08 triskelion mtp-probe: bus: 2, device: 6 was not an MTP device
Dec 9 09:29:08 triskelion modem-manager[1288]: <info> (ttyACM0) opening serial port...
Dec 9 09:29:20 triskelion modem-manager[1288]: <info> (ttyACM0) closing serial port...
Dec 9 09:29:20 triskelion modem-manager[1288]: <info> (ttyACM0) serial port closed
Dec 9 09:29:20 triskelion modem-manager[1288]: <info> (ttyACM0) opening serial port...
Dec 9 09:29:26 triskelion modem-manager[1288]: <info> (ttyACM0) closing serial port...
Dec 9 09:29:26 triskelion modem-manager[1288]: <info> (ttyACM0) serial port closed
Dec 9 09:29:26 triskelion modem-manager[1288]: <info> (ttyACM0) opening serial port...
...
Dec 9 09:29:51 triskelion kernel: [ 1449.626220] usb 2-1.2: USB disconnect, device number 6
The device is currently detected by Heimdall but not by Odin.
One last question: do you know why the device starts in recovery mode when I plug it to the wall to recharge the battery?

lt30p - can't get into bootloader

hey there,
i'm trying to unlock the lt30p's bootloader, want to install a custom recovery and cyanogenmod.
in every tutorial i'm reading about "power the phone off, push the volume-up button until you plug in the usb-cable".
if i do this, the phone begins to charge (i see the charging-icon), then the display turns off. on windows (hardwaremanager) or linux (lsusb) there is no fastboot device, rebooting into fastboot via adbwon't work too.
its a james bond-branded phone from a1 (an austrian carrier).
is there anyone who experiences this issue too and could give me some tips? that would be very nice.
thanks in advance,
toaster

I dual boot my laptop windows 7 and linux mint 17.1, I tried for 4-5 hours to unlock my bootloader through the sony website with windows 7. Had the same issues as you, hold volume up, plug in usb, phone shows blue light(entering fastboot) then started charging. I finally decided to try it in linux and after installing fastboot "apt-get install android-tools-adb android-tools-fastboot", I was done in about 5 minutes. I was glad it was finally done but I was pissed it took so long. Yet another reason I love linux and hate windows, wish I would have tried linux sooner. Hope this helps.

i never get a blue light, only red, when i plug the cable in. dmesg meant, that the phone only connects as mass storage device...
Code:
[ 684.005774] usb 2-1.5: new high-speed USB device number 5 using ehci-pci
[ 684.099613] usb 2-1.5: New USB device found, idVendor=0fce, idProduct=e182
[ 684.099622] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 684.099627] usb 2-1.5: Product: Android
[ 684.099631] usb 2-1.5: Manufacturer: Android
[ 684.099636] usb 2-1.5: SerialNumber: CB51234S76
[ 684.102505] usb-storage 2-1.5:1.0: USB Mass Storage device detected
[ 684.102677] scsi host7: usb-storage 2-1.5:1.0
[ 685.102449] scsi 7:0:0:0: Direct-Access SONY Mass Storage 0100 PQ: 0 ANSI: 4
[ 685.102947] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 688.117277] sd 7:0:0:0: [sdb] Attached SCSI removable disk
it runs with sony android 4.3.

-> http://forum.xda-developers.com/showthread.php?t=2798411
helped for me.

Can't connect to PC for adb/fastboot/flashing

I'm a bit late to the party, am I?
Recently I've been experimenting with my RM1G which I bought years ago. I came to a point where I would like to connect it to a PC to sideload APKs, root it etc. and I got stuck.
I've made the cable (actually three of them) and nothing seems to be working. On Windows I get the unhelpful "USB device malfunctioned" popup. On Linux in journalctl I get this:
Code:
kernel: usb2-1.3: new low-speed USB device number 4 using ehci-pci
kernel: usb2-1.3: device descriptor read/64, error -32
kernel: usb2-1.3: device descriptor read/64, error -32
kernel: usb2-1.3: new low-speed USB device number 5 using ehci-pci
kernel: usb2-1.3: device descriptor read/64, error -32
kernel: usb2-1.3: device descriptor read/64, error -32
kernel: usb2-1-port3: attempt power cycle
kernel: usb2-1.3: new low-speed USB device number 6 using ehci-pci
kernel: usb2-1.3: device descriptor read/64, error -32
kernel: usb2-1.3: device descriptor read/64, error -32
kernel: usb2-1.3: new low-speed USB device number 7 using ehci-pci
kernel: usb2-1.3: device descriptor read/64, error -32
kernel: usb2-1.3: device descriptor read/64, error -32
kernel: usb2-1-port3: unable to enumerate USB device
This is happening both with the device powered on and in fastboot mode. ADB and USB host are enabled, the cable is plugged into the top port. Disabling USB host stops the errors, but also nothing is working (as expected). The other port isn't responding at all no matter the settings.
This is with cables wired like this (data lines crossed):
Code:
Vbus ↔ Vbus
D- ↔ D+
D+ ↔ D-
GND ↔ GND
With straight data lines I didn't get any communication whatsoever. I didn't try to reverse power lines because shorting two voltage sources like that sounds like a terrible idea. Googling suggests this error could be overcurrent protection kicking in, but that seems weird and I'd rather not do anything risky without first making sure it makes sense. I really don't want to let the magic smoke out.
Does anybody know what could be going on here? Could someone post wiring of a known-good USB cable?

Problem solved.
While working on some other project I've discovered that I own a factory-made male to male cable with straight connections (so D+ to D+, D- to D-) and I've decided to give it a go - and it worked. I don't know why my own straight cable didn't cause any reaction - probably some connection was loose.
Windows didn't recognize the fastboot device. Tinkering with the drivers would probably help, but it was quicker to boot into Linux and there it worked from the get go. I'm now a happy owner of a rooted Remix Mini. Next: soldering in the serial header