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
Related
Has anyone been able to run adb in a linux virtualbox vm under windows? For the life of me I can't get the galaxy s to show up in lsusb or adb recognizing the galaxy s. Virtualbox sees it though, and it shows up if I mouseover the little usb plug icon at the bottom right of the vm window.
Some more info:
Code:
May 23 20:16:25 VirtualBox kernel: [ 181.004130] usb 1-1: new high speed USB device using ehci_hcd and address 13
May 23 20:16:25 VirtualBox kernel: [ 181.060566] usb 1-1: device descriptor read/8, error -32
May 23 20:16:25 VirtualBox kernel: [ 181.204698] usb 1-1: device descriptor read/8, error -32
May 23 20:16:26 VirtualBox kernel: [ 181.309023] hub 1-0:1.0: unable to enumerate USB device on port 1
I have tried everything to get my SGS to run ADB in an Ubuntu VM, but I couldn't find a way... In Virtualbox forums there are more people complaining about the same, and there is a bug filled in their bug-tracker about this issue..
After hours of frustration around Virtualbox, I have decided to give a chance to VMware Player, and it worked right away...
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
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
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?
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1467879144.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,127))
and this is my dmesg log:
Code:
[ 3440.213018] usb 1-1.2: new high-speed USB device number 55 using ehci-pci
[ 3440.307101] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3440.307104] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3440.307105] usb 1-1.2: Product: MT65xx Preloader
[ 3440.307106] usb 1-1.2: Manufacturer: MediaTek
[ 3440.369300] cdc_acm 1-1.2:1.1: ttyACM1: USB ACM device
[ 3443.146921] usb 1-1.2: USB disconnect, device number 55
[ 3560.113932] usb 1-1.2: new high-speed USB device number 56 using ehci-pci
[ 3560.209002] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3560.209005] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3560.209007] usb 1-1.2: Product: MT65xx Preloader
[ 3560.209008] usb 1-1.2: Manufacturer: MediaTek
[ 3560.271453] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3563.563312] usb 1-1.2: USB disconnect, device number 56.
.
.
.
[ 3589.764652] usb 1-1.2: new high-speed USB device number 62 using ehci-pci
[ 3589.859355] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3589.859359] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3589.859361] usb 1-1.2: Product: MT65xx Preloader
[ 3589.859363] usb 1-1.2: Manufacturer: MediaTek
[ 3589.921646] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3590.138898] usb 1-1.2: USB disconnect, device number 62
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
So… Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
danialbehzadi said:
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
and this is my dmesg log:
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
Soâ?¦ Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
Click to expand...
Click to collapse
Do adb recognize your phone?!
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
danialbehzadi said:
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
Click to expand...
Click to collapse
Ahhh too bad :/
The same thing happened to my Samsung , i overcharged it via an unstable source, and the power IC was damaged, if i slid the battery in it would just keep vibrating and flash light turned on, it costed me PKR Rs.1200(USD.12$) to repair it......
Try SP Flashtool again, but with your battery in. Flashing recovery might be your best bet
Fixed your device?
hassanjavaid8181 said:
Fixed your device?
Click to expand...
Click to collapse
No. Threw it away!
danialbehzadi said:
No. Threw it away!
Click to expand...
Click to collapse
thats another way to fix issue