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

Question about Unbricking the Sensation instruction.

http://forum.xda-developers.com/showthread.php?t=1522351&highlight=qhsusb
I found the thread to unbrick my phone. I am a little confuse on how the instruction on how to unrbrick the phone.
Under prerequisites, I need to
"a linux box/live cd with automount disabled and without unity"
What is unity?
I have Ubuntu installed on one of my computers but I don't want to continued until I know what I need to do before starting this unbricking process.
And what flavor of Linux can I use? Can I use Ubuntu?

I tried Using ubuntu,
Ubuntu will detect the device using this command
./brickdetect.sh
I unplugged it then plugged it back in, and then use the following command
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
It says waiting for device, then nothing.

F9zSlavik said:
I tried Using ubuntu,
Ubuntu will detect the device using this command
./brickdetect.sh
I unplugged it then plugged it back in, and then use the following command
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
It says waiting for device, then nothing.
Click to expand...
Click to collapse
That is because of automount.
There will, most likely, be a video tutorial that I'll be making soon.
And also, in the command, sdX needs to be replaced with the node that you got from brickdetect. That is, for example: sda, sdi, etc.

i am not an expert in this, but i do know what is Unity
here you go: http://unity.ubuntu.com/

kgs1992 said:
That is because of automount.
There will, most likely, be a video tutorial that I'll be making soon.
And also, in the command, sdX needs to be replaced with the node that you got from brickdetect. That is, for example: sda, sdi, etc.
Click to expand...
Click to collapse
I hate Linux so bad.... Great for certain things but god I just hate it ;/
So I downloaded Ubuntu 12.04 DVD version from Ubuntu website. I went and downloaded the necessary files for the unrbicking process.
I can detect my device, no issues with that.
BUT I had a hard time doing
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
nothing would happen even after I disable automount. I had to time it just right from when I plug the phone back in the USB and hitting enter in terminal to execute the command.
If I time it just RIGHT (took 20 tries), I can get it to back up of HBOOT. I have 1.27.
My isssue is the stupid *&^*%$% auto mounting crap. I have tried (thanks to google)
sudo apt-get install dconf-tools
after installing I then did this
dconf-editor then navigate to org -> gnome -> desktop -> media-handling: disable both automounts
Problem persisted. Nothing happens when I try to flash the hboot (because of automount)
so I tried using this command in Terminal,
gsettings set org.gnome.desktop.media-handling automount false
Same crap. I can't flash the stupid hboot. Nothing happens again when I execute the command.
sudo ./emmc_recover --flash pyrV.VV.nb0 --device /dev/sdX12 --backupafter hboot_f.nb0
I guess if I time it just right after plugging in the phone I might be able to do it.
And yes I am changing the V.VV to the corresponding file and yes I am changing X to whatever letter the phone is assign to.
I tried using the live cd provided by the OP but its even worse then te official one because I see NO WAY of disabling automount. I tried the above ways and nothing worked as far as disabling automount.
How do yo disable automount in the livecd provided by the thread?
This is the Unbricking Project thread
http://forum.xda-developers.com/showthread.php?t=1522351

I got the phone working again. I just had to time it just right.
The phone is completely back to stock with S-ON, reloaded ICS RUU, system still has the wifi issue. ;/

Problem Unbrick

Hello everyone, I have a problem with the method: Downgrade / Unbrick Ville S4. To be noted that I bricked my One s involuntarily. Now if you follow the above method, when I give the code: $ lsusb watch-1 is seen the device correctly, but then when I press the power button for 10 seconds, the device disappears and I get this: Qualcomm, Inc. and continues back to scanning the device. Then do this code: $ ls / dev / sd * and of course the device is not connected. It 's like if I had a problem on the USB ports that do not maintain stable connection with the device, or my One s resets the time. I've used both Ubuntu and Mint13. Do you have any solution? Thank you. Sorry for my English.

pasquill75 said:
Hello everyone, I have a problem with the method: Downgrade / Unbrick Ville S4. To be noted that I bricked my One s involuntarily. Now if you follow the above method, when I give the code: $ lsusb watch-1 is seen the device correctly, but then when I press the power button for 10 seconds, the device disappears and I get this: Qualcomm, Inc. and continues back to scanning the device. Then do this code: $ ls / dev / sd * and of course the device is not connected. It 's like if I had a problem on the USB ports that do not maintain stable connection with the device, or my One s resets the time. I've used both Ubuntu and Mint13. Do you have any solution? Thank you. Sorry for my English.
Click to expand...
Click to collapse
Best off posting in the downgrade thread but if you think usb is the issue they try another pc.

You have to do the $ ls dev/sd* command multiple times by doing up enter up enter so that it will appear at least once. If you do the command once or twice, it won't work. You need to be really quick.

Darknites said:
Best off posting in the downgrade thread but if you think usb is the issue they try another pc.
Click to expand...
Click to collapse
I can not post in this thread because I do not have privileges. I've tried three PCs. Thank you.

pasquill75 said:
I can not post in this thread because I do not have privileges. I've tried three PCs. Thank you.
Click to expand...
Click to collapse
Oh ya dumb me sorry but what usaff22 said is right I had to do that 3 or 4 times.

usaff22 said:
You have to do the $ ls dev/sd* command multiple times by doing up enter up enter so that it will appear at least once. If you do the command once or twice, it won't work. You need to be really quick.
Click to expand...
Click to collapse
First of all, thank you. You think it's a speed problem? In fact sometimes comes too: Qualcomm. Inc. Gobi Wireless Modem (QDL mode), but then when I go to press the power button, the display disappears and this begins to look for the device Qualcomm, Inc. 001, 002, 003 etc.. I can not continue with the procedure because after telling me Connect device. One more thing: why when I enter the command $ tells me that is not valid? Which linux distro do you recommend?

pasquill75 said:
First of all, thank you. You think it's a speed problem? In fact sometimes comes too: Qualcomm. Inc. Gobi Wireless Modem (QDL mode), but then when I go to press the power button, the display disappears and this begins to look for the device Qualcomm, Inc. 001, 002, 003 etc.. I can not continue with the procedure because after telling me Connect device. One more thing: why when I enter the command $ tells me that is not valid? Which linux distro do you recommend?
Click to expand...
Click to collapse
I used Ubuntu 12.10 64-bit.

Darknites said:
I used Ubuntu 12.10 64-bit.
Click to expand...
Click to collapse
To you has the same problem?
I mean, why it makes me see the device and as soon as I press the power button to start the search again?

pasquill75 said:
To you has the same problem?
I mean, why it makes me see the device and as soon as I press the power button to start the search again?
Click to expand...
Click to collapse
I did the downgrade first try but like usaff22 says you need to spam $ ls dev/sd* when you reboot using the Up button and then hit enter in till it pops up.

pasquill75 said:
Then do this code: $ ls / dev / sd *
Click to expand...
Click to collapse
Disregard this if it's obvious, but the command you should use is:
ls /dev/sd*
(So you dont type the '$'-sign (that's your prompt) and there is only one space between 'ls' and '/dev/sd*' and no other spaces.)
usaff22 said:
..by doing up enter up enter... You need to be really quick.
Click to expand...
Click to collapse
You could do something like:
while [[ 1 ]] ; do ls /dev/sd* ; sleep 1 ; echo "Again..." ; done
-Jobo

touch of jobo said:
You could do something like:
while [[ 1 ]] ; do ls /dev/sd* ; sleep 1 ; echo "Again..." ; done
-Jobo
Click to expand...
Click to collapse
This is not I get it, you can be more basic? Thank you.

pasquill75 said:
This is not I get it, you can be more basic? Thank you.
Click to expand...
Click to collapse
Instead of the 'up .. enter .. up .. enter ..'-thing, this just runs it once per second in a loop.
It was in reply to usaff222 who explained that you have to run it multiple times. This is a lazy way to do it multiple times.
The first bit about the dollar sign and spaces was in reply to your original post.
Sorry for any confusion.
-Jobo

HI!
i'm new on the forum but i've found help in this site many times.
i'm in the same problema of pasquill75..when i do the command I have back everytime the same yellow line without sd*4 / 12..
I've tried many times and everytime faster but nothing changes
ps:I'm running ubuntu 12.10 fully installed on a hdd (not live cd or fully installed on my pc I mean)
can this be the problem? sorry for my bad english

[Completed] New Guide for rooting LG Volt(LGLS740)

This guide is for a brand new Boost Mobile LG Volt (LGLS740.) 4/4/2015
I had an LG Realm that I rooted in less than 5 minutes with Kingo Root. Cracked the screen, didn't have time to fix it so I went and bought the LG Volt from Boost Mobile. I've spent around 7 months trying to root the stupid thing with one-click utilities and other tricks and gave up.
Finally I found a guide that got me on the right path and made it happen. Now keep in mind I didn't have to flash back to earlier versions of firmware for anything you can do this on ZV5.
First download the attachment (LG_Root.zip) and unzip it too your desktop or wherever you wish.
make sure you have the LG_unified drivers installed(I did all this in Windows 7 but it shouldn't matter.)
And now I pass you off to this brilliant man's guide: http://forum.xda-developers.com/and...lg-devices-t3049772/post59309508#post59309508
It took me all of two minutes to root the phone. Don't be afraid. To sum it all up:
1. Install drivers, extract LG_root.
2. Make sure the usual is done(Enable USB debugging, allow untrusted vendors)
3. Hold shift and left click in the window to open command line in the proper directory
4. type adb.exe devices in the command window or just paste it from here, and make sure your device shows up.
5. copy and paste this to the command prompt: adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp which pushes the supersu utility to your phone.
6. a: Power off your device
b:When the device is powered off, hold volume up and insert a USB cable connected to the PC
c:Wait for the drivers to install
7. Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port, mine was com4, com3 didn't even show up in mine so no worries.)
8. Go back to your command prompt window(close the Ports.bat window if you want.) and paste: Send_Command.exe \\.\COM4 (This opens the channel to send commands to the diag port.)
9. Paste this final command to your command prompt when the channel is open: sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
10. Once it's done you can pull the battery.
FYI: I had trouble a couple of times while in firmware mode and had to restart once or twice before I did it all correctly. Also, I know I'm just basically copying Unjustified_Dev's post but it took me around 7 or 8 months to find a way that worked with this phone so I just want it to be easier for people to find and confirm that it works for the LG Volt(LGLS740) when you try to find a way to root it. And NONE of the one click utilities worked for me.
Thanks everyone and especially Unjustified Dev, I hope this helps and brings some attention to this phone model. I remember I had a certain version of the Motorola Razr(V3XX) or something and I could barely ever get anything hacked with it, it was frustrating as hell!

PlasticCogLiquid said:
This guide is for a brand new Boost Mobile LG Volt (LGLS740.) 4/4/2015
I had an LG Realm that I rooted in less than 5 minutes with Kingo Root. Cracked the screen, didn't have time to fix it so I went and bought the LG Volt from Boost Mobile. I've spent around 7 months trying to root the stupid thing with one-click utilities and other tricks and gave up.
Finally I found a guide that got me on the right path and made it happen. Now keep in mind I didn't have to flash back to earlier versions of firmware for anything you can do this on ZV5.
First download the attachment (LG_Root.zip) and unzip it too your desktop or wherever you wish.
make sure you have the LG_unified drivers installed(I did all this in Windows 7 but it shouldn't matter.)
And now I pass you off to this brilliant man's guide: http://forum.xda-developers.com/and...lg-devices-t3049772/post59309508#post59309508
It took me all of two minutes to root the phone. Don't be afraid. To sum it all up:
1. Install drivers, extract LG_root.
2. Make sure the usual is done(Enable USB debugging, allow untrusted vendors)
3. Hold shift and left click in the window to open command line in the proper directory
4. type adb.exe devices in the command window or just paste it from here, and make sure your device shows up.
5. copy and paste this to the command prompt: adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp which pushes the supersu utility to your phone.
6. a: Power off your device
b:When the device is powered off, hold volume up and insert a USB cable connected to the PC
c:Wait for the drivers to install
7. Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port, mine was com4, com3 didn't even show up in mine so no worries.)
8. Go back to your command prompt window(close the Ports.bat window if you want.) and paste: Send_Command.exe \\.\COM4 (This opens the channel to send commands to the diag port.)
9. Paste this final command to your command prompt when the channel is open: sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
10. Once it's done you can pull the battery.
FYI: I had trouble a couple of times while in firmware mode and had to restart once or twice before I did it all correctly. Also, I know I'm just basically copying Unjustified_Dev's post but it took me around 7 or 8 months to find a way that worked with this phone so I just want it to be easier for people to find and confirm that it works for the LG Volt(LGLS740) when you try to find a way to root it. And NONE of the one click utilities worked for me.
Thanks everyone and especially Unjustified Dev, I hope this helps and brings some attention to this phone model. I remember I had a certain version of the Motorola Razr(V3XX) or something and I could barely ever get anything hacked with it, it was frustrating as hell!
Click to expand...
Click to collapse
Because there is not a specific forum for your device, you can start your own thread here General Upgrading, Modifying and Unlocking

No reply, thread will be closed.

[FIX] Unknown USB device (Device Descriptor Request Failed) Fastboot Windows 10

First of all, I have a HTC Droid DNA. I was searching for about a year. Finally I got a solution for my problem and I know some of you are still out there with no solution.
The Fail Code is: Unknown USB device (Device Descriptor Request Failed)
Windows has stopped this device because it has reported problems. (Code 43)
So I found a German solution where you have to go to regedit.
Step 1: You need to install the HTC drivers (Google, Samsung etc...) in the normal mode your PC will find your phone, but when you turn into Fastboot you get that error "Unknown USB device (Device Descriptor Request Failed) "
Step 2: Make sure you see that error in your Device Manager under USB - Controller
Step 3: Open "regedit"
Step 4: Navigate to : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
Step 5: Create a new Key called
0BB40FF00100
Step 6: In that Key you create a Binary Value
Name: SkipBOSDescriptorQuery
Value: 01 00 00 00 (ignore the "0000" at the beginning)
Step 7: Reconnect the Phone and enjoy your FIX
I hope I helped you. I can just tell you that it worked for me. I m not sure if it works on all HTC devices.

tried it with a S7 right now, didnt work. thanks for your post tho!

Had the solution for windows 8.1, from a blog on microsoft MSDN. (Sorry can't link to it. Since I'm new @ xda)
But as it turned out the Datatype for SkipBOSDescriptorQuery has changed from windows 8.1 to 10. Instead of a DWORD Value in Windows 8.1 it should be a Binary Value in Windows 10 .
So thanks :good: Now I can connect via fastboot to my HTC Incredible S.
Ps. Google this:
why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43
And blogpost will show as top result

Thank you very much the regedit method worked for sure..
I spent 5 hours on my computer and laptop different usb cables different ports installing uninstalling drivers and ADB nothing
Thanks BoBo Rich:good:

Thnx!!

Didn't work for HTC Explorer (Pico)

Worked with the HTC Aria on Win10 x64!
Thanks a ton.
edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100

Has anyone else gotten this to work?
My Pixel XL isn't recognized at all when plugged in while in system, but it shows up as unrecognized when plugged in while in fastboot. But despite installing the drivers, Windows still refuses to recognize the phone. I tried the various solutions in this thread, but none of them worked. Perhaps it's because my Pixel's fastboot hardware ID is different, but I can't seem to find out what it is.

work perfectly for htc one xl (evita). Thanks !!

Thanks
After 48 Hours of searching!! thanks man! HTC ONE S (Ville)

Thanks! I have this problem with my Shield TV Pro, will try this after work.
Here's some PowerShell code for doing the registry editing, if anyone is interested.
Code:
#Requires -RunAsAdministrator
[string] $Path = 'HKLM:\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100'
[string] $Name = 'SkipBOSDescriptorQuery'
if ($false) {
# Create the path if not exist
if (-not(Test-Path -Path $Path)){New-Item -Path $Path -ItemType 'Directory'}
# Set "SkipBOSDescriptorQuery" to $true
Set-ItemProperty -Path $Path -Name $Name -Value 1 -Type 'DWord'
# Set "SkipBOSDescriptorQuery" to $false
Set-ItemProperty -Path $Path -Name $Name -Value 0 -Type 'DWord'
# Remove item
Remove-ItemProperty -Path $Path -Name $Name
# Remove path and item(s)
Remove-Item -Path $Path -Recurse -Force
}
Edit: This did not work for my Shield TV 2015 Pro unfortunately..

The error changes to "Port Reset failed". Error code remains the same 43. In my case I am trying to connect an LG G3 D858HK. I have tried many different cabels but no solution.

Unknown usb device error Motorola

Doesn't work on lg v20... Haven't been able to fix this issue for a while now..

Thanks for the info mate !
The registry key worked just great in my Windows 10 x64 computer at home and at my work laptop.
I have a Huawei P9 mobile Device.
Had this issue and nothing i tried seemed to work.
Your key did.
Thanks again !!!:good::good:

V20 Method prior to attempt....
@texas### whos still having trouble with a V20 stuck in the firmware screen ( like me) and I have a theory so I'm posting this prior to attempting it but someone please let me know if I have this wrong.
I read this post on the first page of the thread by someone whos name I've forgotten now (sorry) but they wrote....
--------------- edit: Hrm. Seems to have cropped up again. Time to continue the battle *sigh*
edit 2: Got it! Thankfully I had a Win7 laptop that I was able to fire up. The HTC Aria's fastboot hardware ID is "USB\VID_0BB4&PID_0FFF&REV_0100" which means the vvvvpppprrrr is 0BB40FFF0100. So follow the instructions above but using the key of 0BB40FFF0100 -----------------------
and based on this --- my V20 hardware ID reads "USB\VID_0000&PID_0002\5&2BF451F8&0&2" or rather the instance path does and using this I should be able to correct the value of the binary string to fit this corresponding ID for the VVVVPPPPRRRR correct? so value will be "0000000252BF451f02" ????
Im making the key and binary value now and I'll repost results later
I'm so invested in this phone both in time and sheer ignorance of what else I can do to get this damn thing out of the firmware screen.
* I've tried loading the "LG drivers from both LG composite device and VZW versions" to no avail.
*On a side note, tapping the power button brings up a "download mode" sub screen where is searches for wifi connections and after finding mine I went ahead and tried to connect 1- normally 2- removing my wifi password 3- using the WPS button to connect, all of which ended in "connection failed" so can someone explain the actual purpose of this option if there is no way to connect? or am I finding the wrong signal so to speak>?
Thanks
I'll gladly post all of my results or screen shots, (all failed so far) using ADB, uppercut, LGUP, odin, placing TOT files on the SD card, plus a few absolutely embarrassing methods but had to try something.
Please tell me someone knows a way out of this

Otherwise start a *.bat file containing
Code:
REG ADD HKLM\SYSTEM\CurrentControlSet\Control\UsbFlags\0BB40FF00100 /v SkipBOSDescriptorQuery /t REG_BINARY /d 01000000 /f
or use this in the Run window that you can call by pressing the Windows button and R, Win+R.

DEAD
Hi
Hope there's still anyone here that could help. I got the same error {The Fail Code is: Unknown USB device (Device Descriptor Request Failed) Windows has stopped this device because it has reported problems. (Code 43)} that appears on windows when watch is connected and i press the red button. I tried to get the identifier via device manager and microsoft message analyzer but it is not detected. What else can i do?
Thanks!

didnt work for the V40. anyone got any ideas?

SuperMike393 said:
didnt work for the V40. anyone got any ideas?
Click to expand...
Click to collapse
Have you tried going to device manager > universal bus controllers, right click USB Root Hub and unintall. Restart the PPC/Laptop and reconnect the device. It works on both Xiaomi and other brands as well.