Database Develop

Problem with ROM UPGRADE under VMWARE /no connection after the Boot Loader menu/

I have a trouble flashing my Diamond ROM with HardSPL or anything else, including the original shipped ROMs. First of all I'm running the WinXP as a guest OS under VMWare and my host is linux. Once the Diamond restart and enter the boot loader (the colorful screen) the XP can't recognize it with the standart message "USB Device Not Recognized"...
The info I receive in dmesg is as follows:
usb 3-2: new full speed USB device using uhci_hcd and address 10
usb 3-2: new full speed USB device using uhci_hcd and address 11
usb 3-2: new device found, idVendor=0bb4, idProduct=0a15
usb 3-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2: Product: Qualcomm CDMA Technologies MSM
usb 3-2: Manufacturer: HTC
usb 3-2: configuration #1 chosen from 1 choice
Also, of course I have allowed and redirected the "High Qualcomm CDMA Technologies MSM" into VMWare.
Any ideas??
Cheers!!

i have the same prolem..did u manage to sole this problem?

[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

[Q] TouchPad doesnt boot - very very tricky - how to solve?

Hi,
my TouchPad seems to be in a boot loop, or bootloader is corrupt, dunno.
I am using linux, btw.
This happend:
I did install CM7 since after the first alpha release and upgraded each release without a hassle. I had both OS parallel for a long time dual booting regulary, but using Android more and more often.
Since Christmas then I havent even been in WebOs.
Two weeks ago, I started WebOS again, and got a message to update my software.
I clicked yes.
Then it took an hour or so and the Pad rebooted ..... and got stuck - never came up again since then.
It just stays a bit where the round HP sign comes up, and reboot after a minute or so.
here is the dmesg:
Code:
[37240.196350] usb 2-1.3: new high-speed USB device number 8 using ehci_hcd
[37240.317306] usb 2-1.3: New USB device found, idVendor=0830, idProduct=8070
[37240.317318] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37240.317325] usb 2-1.3: Product: Palm
[37240.317330] usb 2-1.3: Manufacturer: bootie
[37522.496211] usb 2-1.3: USB disconnect, device number 8
[37552.413914] usb 2-1.3: new high-speed USB device number 9 using ehci_hcd
[37552.534865] usb 2-1.3: New USB device found, idVendor=0830, idProduct=8070
[37552.534877] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37552.534884] usb 2-1.3: Product: Palm
[37552.534889] usb 2-1.3: Manufacturer: bootie
[37579.309737] usb 2-1.3: USB disconnect, device number 9
I tried a hard reset, and same same happens again:
It resets, the hp logo shows up, then after a minute it reboots again.
So after this I tried to use memboot. but I can't get even into usb mode!
Holding Volume up + Power does exactly nothing! Novacom doesn't recognize my TouchPad.
Holding Volume down + Home + Power does nothing as well - despite throwing this into dmesg:
Code:
[37197.120415] usb 2-1.3: new high-speed USB device number 7 using ehci_hcd
[37197.240971] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9008
[37197.240977] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37197.240981] usb 2-1.3: Product: QHSUSB_DLOAD
[37197.240984] usb 2-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[37197.241877] qcserial 2-1.3:1.0: Qualcomm USB modem converter detected
[37197.242395] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB0
[37238.172562] usb 2-1.3: USB disconnect, device number 7
[37238.173155] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[37238.173359] qcserial 2-1.3:1.0: device disconnected
btw, webdoctor certainly doesnt recognize my device, neither in linux nor in windows 7 - nonetheless it shows up in explorer as palm device without device drivers installed (yes I did install novacom drivers in Windows as well as in linux).
What to do now? Any hints?

Do the reset again then when it starts to reset hold volume up only.
hopefully that should be you in webos recovery.
Then you can try to flash moboot again because the update does break moboot.

thanks....
had to do it three times, then it worked out!! maybe my vol key is lose?
Anyway, you made my week!! :-D

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?

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.