Database Info

[SOLVED] Infuse wont connect to Ubuntu....

UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.

weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.

Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.

Linux driver should be perfect, before connects to PC the mass storage mode should be selected.

dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/

well I see you fixed it. did you get adb going?

Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk

are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.

Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone

[Q] TF101 usb dosent't get connected to linux and windows...

Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???

joevirus563 said:
Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???
Click to expand...
Click to collapse
Go to Settings - Storage - USB computer connection - tick Media device (MTP)

hapahopi said:
Go to Settings - Storage - USB computer connection - tick Media device (MTP)
Click to expand...
Click to collapse
Its already at MTP...
Any way to root without computer?

I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .

Happydondavid said:
I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .
Click to expand...
Click to collapse
Ok and whant have you done to fix it?
New usb cable?

I've not managed to fix it yet . When i plug my TF into my pc it seems to think its charging but the pc doesn't register it at all , if i get a new usb cable and it works i'll report back .

Well does anyone know if this is a problem with the cable or not ?

Happydondavid said:
Well does anyone know if this is a problem with the cable or not ?
Click to expand...
Click to collapse
I have the same problem. I sent my tf101 to the Asus service center to have it repaired. When it came back it would connect to the PC. After a few months it would not connect. Same problem. It appears to me to be software related somehow. In my case the cable has nothing to do with it. None of the suggestions on this or other forums work. Asus does not respond. Maybe Jelly Bean will fix it. Or maybe not.

are you able to ./adb connect to the asus via usb? if so then that will tell you that the problem is not the cable, it's not the usb version, it's not the device hardware. its likely a driver install issue in windows. i would boot into android and make sure that android debugging is selected in the developer settings menu. then try an adb connection. im not sure about how to install all the stupid drivers in windows because i do everything in linux and its soooooo much simpler.
f it is in fact the hardware cable or port that is not working properly then you can always move files to and from the device over wlan connection, with either adb tcp connection, or using some file manager such as es file explorer. just remember as long as you can get an
./adb connection to your android then anything is fixable. ADB IS YOUR FRIEND. get to know it well.

same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?

qandrav said:
same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?
Click to expand...
Click to collapse
I dont ever connect my devices as mass storage to he computers at all. i just do everything via ./adb usb or ./adb tcp connections over wifi. or i use es file explorer setup as an ftp server on my devices and move files around that way if i need to. but i went ahead and pulled out my windows asus tf101 drivers and sync app and linked them for you at the bottom. my advice really is to lose windows and stick with doing everything on android with linux. soooo much better.
https://www.box.com/s/q2j8n7h8xi5o3ld2bt5z

thank you for your long reply! and obv for the files, I'll give it a try!
I admit that sometimes I used swiftp (over wifi) but every time I have to disconnect pc & tablet from the modem...Sometimes use bluetooth but it's too too slow!!! thank you again!!!

I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk

when I rooted moths ago I used "razorclaw" (and my tf101 is a b70). I use adb with other devices and is very cool but I never need to use with the tf101...

joevirus563 said:
I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk
Click to expand...
Click to collapse
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.

The Real Question when USB does not connect.
haxin said:
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.
Click to expand...
Click to collapse
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.

beware of usb cable
Hi,I personnally own a TF101 sb50.
I had some trouble with usb. Tha cable was ok for charging but didn t register correctly under an usb connection ( it showed up and got kicked out in windows didn t register in lsusb on linux)
If you check the diagram for the cable, it s well endowed there 's resistance inside the cable, and multiple connection.
Depending on your version it doesn t use the same pin, even if it's the same cable.
You can buy a cable on ebay for around 10 euro in europe ( i did it s ok) or buy it cheaper from china(no idea about quality).
to sum it up even if your cable work with another TF, it doesn t mean your cable is not faulty ( i have bounce a nano osci on the faulty cable , and it showed no apparent flaw.) and buying a new one was the solution for me.
good luck for rooting (sb50 :: no need to adb)

The ADB thru WiFi solution worked perfectly for me thankfully, and I am one of the many others who have been having major trouble getting Windows and Linux to recognize the Intercept.
Not sure if this is a duplicate post somewhere, but here's my version using Linux:
1. Go to the Play Store and download the 'ADB over Wifi Widget' app.
2. After installed on your device, the app should be on your home screen. Tap it once to toggle on. You should see an IP address and a port #.
Note the IP address, as this is the address of your device.
3. Open a terminal in Linux.
4. CD to the folder that contains your ADB files. (example: cd /androidsdk/platform-tools)
5. Enter the following code:
chmod 755 ./adb
./adb connect <enter IP address here without brackets of course>
6. You should now be connected to your phone.
Hope this helps...

pm124493 said:
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.
Click to expand...
Click to collapse
ok when you say that the tf101 doesnt connect in either your windows or linux machine, what do you mean exactly? you mean it doesnt show up as a mass storage device or an MTP device? and have you downloaded and installed the android-sdk in linux? and when you connect the tf101 to your linux machine, do yo uhave usb debugging enabled in the developer settings menu, and are you using the "./adb devices" command in the linux terminal from your /android-sdk/platform-tools/ directory?
also you should be able to flash a custom recovery which will enable you to flash custom rom without using the usb cable. theres a couple files that you need to put on your tf101 in the /sdcard/ directory first.
one is the recovery blob and if you want to keep the stock rom and kernel but just root it then youll need the superuser zip i have included both of them at the bottom.
for starters you need to install a terminal emulator app on the tf101 from the play store.
then once you have the recovery blob on your device in /sdcard/ you can continue. (remember /sdcard/ is the internal memory not the micro sd card)
start the terminal emulator on the tf101 and enter these commands.
mv /data/local/tmp /data/local/tmp.bak
exit
(open another terminal window on the tf101 and enter these commands)
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
(now reboot the tf101 when it boots into android start the terminal emulator app again then enter these comands)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
exit
(now you should have a team rogue recovery flashed to your tf101)
reboot your tf101.
now you can hold the vol -down button while you power on the tf101 you will see a message at the top of the screen that says soomething like "Checking for RCK" when you see that press the vol- up button right away, this should boot you into the team rogue recovery where you can flash custom roms or just flash your superuser.zip to get root.
hopefully this makes sense and hopefully it works for you.
remember you have to extract the recoveryblob from the zip folder before you move it to the /sdcard/ on your asus. the superuser.zip can remain zipped though.

I had the same problem:
windows will not notice my transformer (rooted).
( usb debugging is on, android 4.0.3 with Android Revolution HD 3.5.1.)
i know in the past it works.
adb list ( of devices) ist empty also. Same Problem with the two cables i have.
can you give me a help what i can do?
Sorry for my poor english
kind regards
gandalf

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire

The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk

Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S

USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.

It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S

I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.

maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.

No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance

dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...

dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance

Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help

jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.

windows 8 have a issue with ville fastboot... please make you sure you have a fix

zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic

..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...

Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!

Thank you very much bro. HTC One V good working.

[Q] Fastboot USB on windows 8

hi, i face a problem on windows 8 . all drivers is correcly nstalled on windows 8, ADB is located and correctly mounted but when i restart the One s on bootloader to get it in fastboot USB then its not recognize and the computer said USB not recognize ..
any possible idea ??
thank you in advance

Will972 said:
hi, i face a problem on windows 8 . all drivers is correcly nstalled on windows 8, ADB is located and correctly mounted but when i restart the One s on bootloader to get it in fastboot USB then its not recognize and the computer said USB not recognize ..
any possible idea ??
thank you in advance
Click to expand...
Click to collapse
Works fine here.
Look inside the Device Manager while the phone is connected. Is anything not-recognized there?

khan.orak said:
Works fine here.
Look inside the Device Manager while the phone is connected. Is anything not-recognized there?
Click to expand...
Click to collapse
everything is recognized but the fastboot usb is recognized only the restarting of the computer, after that windows 8 start and the fastboot usb mode disappear ..

Will972 said:
everything is recognized but the fastboot usb is recognized only the restarting of the computer, after that windows 8 start and the fastboot usb mode disappear ..
Click to expand...
Click to collapse
Try plugging it into USB 2.0 ports. May not work with USB 3.0.

khan.orak said:
Try plugging it into USB 2.0 ports. May not work with USB 3.0.
Click to expand...
Click to collapse
i'm not using the USB 3.0 i only use USB 2

I got win8 and the fastboot works fine. I did install the htc manager and after I got the drivers, I stop the htm manager from loading at boot. See if the htc manager is loading at boot. That could interfere with fastboot.

beyond fla
i either recommend cheeking windows firewall to be off . latest version of ' htc sync manager' or ' htc sync' softwares . for checking this , you can go to device manager of windows and connect your phone.it must create a new device recognition and add its schematic between current devices .

Software or Hardware issue ? unable to transfer data from PC via type C cable

ASUS ZS551KL(dark blue) failed to transfer data from PC via type C cable but charging works.
ZS551KL did not ask me "allow to transfer from PC" after connecting to type C cable as usual.
same cable works to another ZS551KL(white).
But Type C USB flash driver works well with both.
It occurred one day suddenly. All of those accessories are the same as before(cables、PC).
Could anyone help?
BR
Tom

USB-MTP mode must be enabled on phone to get it working.

jwoegerbauer said:
USB-MTP mode must be enabled on phone to get it working.
Click to expand...
Click to collapse
Thank you
I did but remain same.

If rebooting PC & phone hasn't resolved, one way of testing phone's USB-C port would be trying ADB (e.g. "adb.exe shell ls -l /place/of/interest", "adb.exe pull /place/of/interest/desired*files" following setup like https://wiki.lineageos.org/adb_fastboot_guide.html ). HTH