Related
Whenever I try to flash HadSPL Windows pops up saying it's installing some driver and then says it has finished installing and the hardware is ready to be used, but then the progress bar just sits at 0%, I believe this has to do with the driver on my system for when my Kaiser is in flash mode, can anyone point me to the correct driver?
HyoImowano said:
Whenever I try to flash HadSPL Windows pops up saying it's installing some driver and then says it has finished installing and the hardware is ready to be used, but then the progress bar just sits at 0%, I believe this has to do with the driver on my system for when my Kaiser is in flash mode, can anyone point me to the correct driver?
Click to expand...
Click to collapse
As long as the correct version of ActiveSync/WMDC (depending on your OS) is installed, Windows will have the required drivers for "HTC USB SYNC" or however it shows up in device manager.
I have ActiveSync 4.5 installed on Windows XP, I've tried uninstalling, re-installing, re-starting, uninstalling drivers, re-booting, the whole shebang, but my device still just sits at 0% when flashing.
HyoImowano said:
I have ActiveSync 4.5 installed on Windows XP, I've tried uninstalling, re-installing, re-starting, uninstalling drivers, re-booting, the whole shebang, but my device still just sits at 0% when flashing.
Click to expand...
Click to collapse
Which version of JumpSPL/SSPL are you using? Also, try a different USB port.
Did you perform step 6 in the instructions on the second post
6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
http://forum.xda-developers.com/showthread.php?t=396922
I exactly know the problem and the solution
While flashing remove all other USB devices(e.g. external harddrive, flashdrive) remove all USB devices other than your kaiser.
Hope that helps,
Regards
this might help in some cases if it was power issue..but in the case descibed in this thread i will agree that our friend must try different usb (the one at the back of your notebook/pc) not at side or front, use the one fed from motherboard...
also try to
uninstall and reinstall active sync
put your device on bootloader and plug usb (install the driver)
perform hardspl
perform flashing
best luck
hardik119 said:
I exactly know the problem and the solution
While flashing remove all other USB devices(e.g. external harddrive, flashdrive) remove all USB devices other than your kaiser.
Hope that helps,
Regards
Click to expand...
Click to collapse
Got it to work, thank you all very very very much for your help, it's greatly appreciated!
For those of you who have had trouble with getting the drivers for the Infuse, download this:
[Im new so cant post a link, but goto softpedia.com and search kies. The only kies program available will appear, and download and install that]
It wont recognize your phone, but after you install the program, the appropriate drivers will be present, and the root with SuperOneClick will work immediately.
*remember, the program wont recognize your phone if its plugged in, but that doesn't matter. It will just install the appropriate Samsung_Android drivers your PC needs to recognize the phone in SuperOneClick.
Hope this helps!
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
pvillasuso said:
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
Click to expand...
Click to collapse
404 Page Not Found
The page you requested was not found.
http://forum.xda-developers.com/showpost.php?p=13895587&postcount=7
posted here.
Phone doesn't exist on my PC.
Nope. Bought the infuse on day one. Installed Kies 2.0.0.11044_11_3. Phone not recognized, installed drivers, learned the truth about Kies. Phone would not be recognized but at least installing Kies made the phone visible to the PC, so I knew I could root if I so desired, read up about rooting and thought I was ready. The phone had other plans.
Decided the other day that I was ready to root. Plugged in the phone but it no longer showed up in Windows. Something about the phones compatibility with my system changed. Tried to install this Kies 2.2.1.11053_99_3 yesterday, reinstalled drivers, activated USB debugging, plugged the phone in started up SuperOneClick and . . . still nothing happened. So I deactivated USB debugging and started over. Followed all the directions in the root posts and and SuperOneClick threads . . .
But somehow between day one and today my Windows 7 64 bit system does not know that the phone is plugged into it.
When I plug the phone into USB the phone asks me how I want to interact with the computer, Kies (Firmware Update); Media player: Mass storage. But the computer shows nothing. Device Manager doesn't list the phone, Windows Explorer doesn't show the phone, Devices and Printers window shows everything that's connected but NOT the phone, it's as if I plugged nothing into the computer. The phone is charging so I know that it's plugged in, but it doesn't seem to be communicating with the PC. I've re-booted, re-installed, reviewed, rewired and re-alized that I have no clue what happened. (Tried different cables, different USB ports different times of the day)
It worked once upon a time, I tried rolling back restore points and disabling my kaspersky 2011, I've followed all rooting instructions in these threads to no avail.
I am now ready to hurl my phone out into traffic to see if that will help, but before I do I'm hoping someone here may have the answer I need.
. . . please . . .
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
For me, one of the SuperOneClick packages included Windows drivers.
Which is great since SOC is the only reason I needed Windows drivers. (SOC never works in Linux for me for whatever reason...)
All android phones are supported in linux natively.......jus t saying
Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Well yeah - I've never had to install any drivers for ADB or anything else.
However, for whatever reason, superoneclick and Linux don't get along for me. So the only time I ever have to install drivers is when SOC rooting from Windows.
superweapons said:
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
Click to expand...
Click to collapse
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
menzoom said:
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
Click to expand...
Click to collapse
I've tried just about everything too, and nothing works to get my 64 bit Windows 7 PC to recognize the Infuse. Finally resorted to AndroidSync for file transfers, which worked fine, but it just makes me angry that I can't make the darn thing connect via USB.
http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT
And select SOFTWARE
Tried that last week. Didn't work for me. The PC does see the device, but never finds any files on it.
Drivers in that link
I was having the same issue mentioned yesterday after loading the Samsung Infuse drivers, where my PC still couldn't see the data on my phone. (I'm also running 64-bit Windows 7 OS.)
Once I loaded the drivers and plugged in my phone, I got the happy little "device drivers installed properly" message and thought I was good to go. Nope. No drives mounted and visible in Explorer.
Under Devices and Printers, I could see SAMSUNG_Android with the unhappy yellow exclamation point. The troubleshooting report just says "Problems with PnP devices."
So I dug into into Device Manager. Under Portable Devices, there were 2 new WPD FileSystem Volume Drivers. Both had the same yellow exclamation points and showed a Device Status of "This device cannot start. (Code 10)."
It turns out Windows 7 wasn't assigning drive letters to the new Android volumes. It creates two disk drives (one with pictures, videos, and ringtones and the other with music, external SD, and media). If you right-click on the drives and choose "Change Drive Letter and Paths," click Add, and assign it an unused drive mapping, it will then appear in Explorer.
Incidentally, the SAMSUNG_Android still shows up with its unhappy yellow exclamation point in Devices and Printers. So I imagine there's supposed to be a more user-friendly way that doesn't expose the true internal file structure when it's all working properly. But in the meantime, I can at least access my phone data via USB.
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Dude look at the date
neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Hey there..
View attachment 876861
thanks
Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Yep...
Ubuntu / Linux FTW!
Hmmm, native on Linux you say? Don't have to battle with windows composite USB hub bullcrap you say? I shall try this.
Sent from my SAMSUNG-SGH-I997 using xda premium
HI all, I seem to have a problem getting my laptop (ubuntu 12.04) to recognize my phone as storage when connected via USB. Here's what happened. I have already enabled USB debugging and USB debugging notify. When I plugged the phone to my laptop I got the usual message on the screen of my phone an when I clicked on it there were 2 tick boxes: one to recognize the phone as camera (that by the way worked) and the other one that recognized the phone as storage: when ticked nothing happened on my laptop, so I unticked both and now that bloody message is not coming up anymore on my phone, I only got one which says "USB debugging connected". ANy idea?
thanks
Disable the USB debugging... It's not needed for storage connection.
Sent from my One using XDA Premium 4 mobile app
HI thanks, ok fair enough but somehow I seem to have messed up with it and I would like to fix it if I can: I can't get the usb debugging mode message up when I connect the phone and the laptop doesn't recognize it as storage, not only ubuntu but even windows! could it be a matter of drivers? If so where can I get them from?
thanks
Menu>Storage>*menu on the upper right corner*>USB computer connection>*check box MTP/PTP*
happygolucky919 said:
Menu>Storage>*menu on the upper right corner*>USB computer connection>*check box MTP/PTP*
Click to expand...
Click to collapse
Thanks. When I connect the device as PTP it gets connected but when I do it as MTP , computer shows the error that drivers are not installed.
I'm having a similar problem on my phone, there is no option to change USB computer connection, so phone not regonised when plugged into PC? Any ideas?
MTP is a proprietary and modern protocol, older or open source OS's will not support it out of the box. You will need the relevant drivers, not sure how to do it on older version of Ubuntu, may be worth looking in their forums (support is included in new version in the proprietary driver bundle). There are no drivers for Windows XP, but you can get them for Windows 7, I'll dig out the guide I have bookmarked somewhere.
IIIIkoolaidIIII said:
MTP is a proprietary and modern protocol, older or open source OS's will not support it out of the box. You will need the relevant drivers, not sure how to do it on older version of Ubuntu, may be worth looking in their forums (support is included in new version in the proprietary driver bundle). There are no drivers for Windows XP, but you can get them for Windows 7, I'll dig out the guide I have bookmarked somewhere.
Click to expand...
Click to collapse
Thanks. That would be of great help.
Dush123 said:
Thanks. That would be of great help.
Click to expand...
Click to collapse
Here are the three guides I have bookmarked relating to MTP, I think the first from Tom's Hardware should fix (download is in 3rd post).
http://www.tomshardware.co.uk/forum/50119-63-devices-working
http://forum.xda-developers.com/showthread.php?t=2390296
http://forum.xda-developers.com/showthread.php?t=2391236
Hope these help.
B
---------- Post added at 09:22 AM ---------- Previous post was at 09:21 AM ----------
Oh yeah the other thing I didn't mention is MTP honors your phones security, so if you have a secure lock it won't show up initially until screen is on and device is unlocked.
Same issue, no options under USB computer connection !
boringfrog said:
I'm having a similar problem on my phone, there is no option to change USB computer connection, so phone not regonised when plugged into PC? Any ideas?
Click to expand...
Click to collapse
Hi, boringfrog,
were you able to get the issue resolved ?
After the phone upgraded from 12.0-YNG1TAS17L to 12.0-YNG1TAS2I3, i am seeing the similar issue, my phone will only charge on a Laptop, i tried different cables, 2 laptops, uninstalled and re-installed drivers, nothing works, i did a dirty flash back to 12.0-YNG1TAS17L the issue still exists, i tried enabling and disabling ADB debugging etc...
Under storage options , under the three dots on the right i see the USB computer connection, upon hitting it , nothing happens, the storage page just refreshes... no options to mount as MTP....
Please help need to copy the data from phone to PC...
mkhanemkay said:
Hi, boringfrog,
were you able to get the issue resolved ?
After the phone upgraded from 12.0-YNG1TAS17L to 12.0-YNG1TAS2I3, i am seeing the similar issue, my phone will only charge on a Laptop, i tried different cables, 2 laptops, uninstalled and re-installed drivers, nothing works, i did a dirty flash back to 12.0-YNG1TAS17L the issue still exists, i tried enabling and disabling ADB debugging etc...
Under storage options , under the three dots on the right i see the USB computer connection, upon hitting it , nothing happens, the storage page just refreshes... no options to mount as MTP....
Please help need to copy the data from phone to PC...
Click to expand...
Click to collapse
Sorry it was a friends phone so I just returned it to him after try a few attempts. Can you not put your data into the cloud then you can access it on your PC? Good luck.
PC not recognizing OnePlus 2 after update to Oxigen 3.0.1
What seems to solve the problem is to pull down the notifications bar, which shows one notification which gives you multiple options for the USB. Please choose the file download option(usually the second option). Your OPT will show up on the PC.
Thanks and regards to all.
When I connect my Asus Transformer to my computer, the message "USB Device Not Recognized" appears. I'm working with Window 7, and in the Device Manager it appears as "Unknown Device".
I tried using different computers and cables, so I'm assuming the problem can't be there. I reflashed the firmware lately (had to because the device was stuck), but I'm not sure if it's related (it used to connect properly to my computer, but it's been a while since I tried connecting it).
What could cause this issue? And what can I do about it?
amitb83 said:
When I connect my Asus Transformer to my computer, the message "USB Device Not Recognized" appears. I'm working with Window 7, and in the Device Manager it appears as "Unknown Device".
I tried using different computers and cables, so I'm assuming the problem can't be there. I reflashed the firmware lately (had to because the device was stuck), but I'm not sure if it's related (it used to connect properly to my computer, but it's been a while since I tried connecting it).
What could cause this issue? And what can I do about it?
Click to expand...
Click to collapse
You might want to read this thread, because the guy (at the last 4 or 5 posts) has same problem.
I tried the Linux Live CD suggested there, but couldn't get it to boot. Could I be missing anything?
Other than that, the situation there does seems similar, except I do see an exclamation mark in the Device Manager next to the "Unknown Device".
And when trying to select a folder for updating a driver, I'm getting the message "Windows has determined the driver software for your device is up to date".
amitb83 said:
I tried the Linux Live CD suggested there, but couldn't get it to boot. Could I be missing anything?
Click to expand...
Click to collapse
Well, did you set your BIOS to boot from CD or USB stick before booting from HDD?
Other than that, the situation there does seems similar, except I do see an exclamation mark in the Device Manager next to the "Unknown Device".
And when trying to select a folder for updating a driver, I'm getting the message "Windows has determined the driver software for your device is up to date".
Click to expand...
Click to collapse
You are letting Windows "search for drivers", right? Bad idea. You have to manually install them.
Download the driver pack from here: http://forum.xda-developers.com/showthread.php?t=2646279, then click "Have disk" and point Windows towards the (unzipped) folder. That should install the necessary device drivers.
berndblb said:
Well, did you set your BIOS to boot from CD or USB stick before booting from HDD?
Click to expand...
Click to collapse
I burnt the iso file to a CD and selected booting from the CD when starting the computer (actually tried it on two computers), but it seemed to ignore that and start Window anyway.
Maybe I got the wrong file? Its name is sulu2-528.007-android.iso
berndblb said:
You are letting Windows "search for drivers", right? Bad idea. You have to manually install them.
Download the driver pack from here: http://forum.xda-developers.com/showthread.php?t=2646279, then click "Have disk" and point Windows towards the (unzipped) folder. That should install the necessary device drivers.
Click to expand...
Click to collapse
I tried it manually and selected the folder, but it didn't recognize the drivers.
Maybe it's the wrong ones again? I unzipped the file in the "WINDOWS DRIVERS DOWNLOAD" in your link.
amitb83 said:
I burnt the iso file to a CD and selected booting from the CD when starting the computer (actually tried it on two computers), but it seemed to ignore that and start Window anyway.
Maybe I got the wrong file? Its name is sulu2-528.007-android.iso
I tried it manually and selected the folder, but it didn't recognize the drivers.
Maybe it's the wrong ones again? I unzipped the file in the "WINDOWS DRIVERS DOWNLOAD" in your link.
Click to expand...
Click to collapse
The iso file is correct. Don't know what's going on there....
What Windows version are you running? You are logged in as administrator? Does your Windows version have the driver verification thing? You may have to turn that off.
amitb83 said:
When I connect my Asus Transformer to my computer, the message "USB Device Not Recognized" appears. I'm working with Window 7, and in the Device Manager it appears as "Unknown Device".
I tried using different computers and cables, so I'm assuming the problem can't be there. I reflashed the firmware lately (had to because the device was stuck), but I'm not sure if it's related (it used to connect properly to my computer, but it's been a while since I tried connecting it).
What could cause this issue? And what can I do about it?
Click to expand...
Click to collapse
Yep, looks like we are in the same boat (with the exception of the yellow triangle).
Just curious, you didn't just place the ISO file on the CD, but you actually burnt the image, right?
If you aren't sure, check this link: http://windows.microsoft.com/en-us/windows7/burn-a-cd-or-dvd-from-an-iso-file
Sorry about the late reply.
I managed to boot from the CD (not sure what went wrong in the previous attempts), but when connecting the tablet I couldn't see any indications it worked.
However, the same goes for when I connected my phone (Samsung Galaxy 5), so I'm suspecting I'm still missing something.
Where can I see my connected devices there?
amitb83 said:
Sorry about the late reply.
I managed to boot from the CD (not sure what went wrong in the previous attempts), but when connecting the tablet I couldn't see any indications it worked.
However, the same goes for when I connected my phone (Samsung Galaxy 5), so I'm suspecting I'm still missing something.
Where can I see my connected devices there?
Click to expand...
Click to collapse
If you open a console and type: adb devices - what do you get?
Should have asked earlier what you are trying to do... Just transfer files to your tablet? MTP is lousy for that anyway. I assumed you were trying to get adb/fastboot access...
if you are just after file transfer, Superbeam, Airdroid or a LAN connection in ES File Explorer are much better than a wired connection..
berndblb said:
If you open a console and type: adb devices - what do you get?
Should have asked earlier what you are trying to do... Just transfer files to your tablet? MTP is lousy for that anyway. I assumed you were trying to get adb/fastboot access...
if you are just after file transfer, Superbeam, Airdroid or a LAN connection in ES File Explorer are much better than a wired connection..
Click to expand...
Click to collapse
Not to forget Total Commander with it's plug-ins. IMHO the best file manager on market and absolutely free.
BTW: command 'devices' whether in adb nor in fastboot environment showed me ever any result on pc. Nevertheless fasboot is working, but adb not. Never needed it anyway.
berndblb said:
Should have asked earlier what you are trying to do... Just transfer files to your tablet? MTP is lousy for that anyway. I assumed you were trying to get adb/fastboot access...
if you are just after file transfer, Superbeam, Airdroid or a LAN connection in ES File Explorer are much better than a wired connection..
Click to expand...
Click to collapse
Yes, I was just trying to transfer files, and now it's a bit awkward to admit I didn't think of a wireless transfer
I'll try one of the apps, thanks for the help!
A couple days ago my mobile data just stopped working. I had a couple updates I had been ignoring because it would remove the root. I finally gave in and ran the updates. Data returned. Root gone. I connected to my home computer to begin the root process, but my phone would not be recognized by the PC and would not show anything related except that it was charging. It's a new cable, barely used. I tried on my work computer with a different cable and still nothing except "charging". To the best of my knowledge, it connected to my computer just fine prior to the updates.
I've checked Developer Options for anything that says "USB". Toggled USB debugging, revoked authorizations, etc. "Select USB Configuration" is a weird one, all I have are: "Charging", "MTP", "PTP", RNDIS (USB Eathernet)", and "MIDI". But in "Default USB Configuration" I have: "No data transfer", "File transfer / Android Auto", "MIDI", "PTP", "USB tethering". I've selected every option, but (again) no reaction from my phone or PC.
My final options are wipe and reset, or take it to a store; I'm wanting to avoid both of these if possible. Does anyone have an idea of what else I can try?
Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?
IamTheBRAVE said:
Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?
Click to expand...
Click to collapse
I'll take a look at that tonight.
To answer your questions, phone boots and everything else seems to operate just fine. Just checked and boot screen says "Orange State Your device has been unlocked and can no longer be trusted", then like 30 seconds later it boots. It no longer has root after the updates and the only way I know to do it is through adb and fastboot commands. But also I backup my photos to my home PC when it gets pretty full. Also, also I occasionally do mobile development at home and test things on my phone.
The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.
IamTheBRAVE said:
The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.
Click to expand...
Click to collapse
Ya, I wasn't too worried about the bootloader message, just being thorough. I'll try the android folder at home also, but for what it's worth I don't have anything android-related on my work computer and it doesn't connect either.
Both are Win10
In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?
IamTheBRAVE said:
In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?
Click to expand...
Click to collapse
Phone doesn't show anywhere in Device Manager, and no yellow triangles. IIRC, drivers were installed by my phone when I plugged it in at home. I actually don't remember the last time I plugged into my pc at work before now.
Then look for your brand's android drivers and install them. I think that's the issue. Plugging the phone alone would install generic android drivers not your specific ones.
Short version: Nothing worked.
I had already tried searching for "oneplus 9 drivers". The main site doesn't offer anything, so there are a couple search results that really feel like scam sites. But they're the top results, so maybe I'm wrong. I installed the results from the search, and also searched xda and the one result I found.
I downloaded the ISO for mAid. Ran it in a VM. I couldn't really figure out what to do in it to troubleshoot. I was also discouraged because if my computer won't recognize the device, then why would the device show up in a VM?
I found and removed adbkey and adbkey.pub from "Users\<me>\.android\".
I had a brief bit of hope. I doubt the drivers caused it, so I'll probably remove those again. I got the device to appear in Device Manager but with a yellow triangle. It only seemed to happen when switching between "No data transfer" and "File transfer / Android Auto". The device was displayed as "Unknown USB Device (Device Descriptor Request Failed)". I doubt that provides much help though.
Have you tried clearing out the dust bunny's in the usb port on phone?
Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com
MrSteelX said:
Have you tried clearing out the dust bunny's in the usb port on phone?
Click to expand...
Click to collapse
Yup. Folded some paper after the previous stuff. A little bit came out, but not so much that I'd think it's the issue. I have a floss stick thing, but it was a bit thicker and was moving the piece inside the slot.
IamTheBRAVE said:
Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com
Click to expand...
Click to collapse
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds
tconn said:
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds
Click to expand...
Click to collapse
Took a look on OP9 forum, doesn't look like there is one. We have that on OP9Pro. Here's a link to the drivers, should work for you i think.
10.26 MB file on MEGA
mega.nz
You can use this thread as tutorial for root (you don't need all parts of it)
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
"Device Descriptor request failed" tells you that the very first step of USB enumeration failed.
So you're talking about flakey cable, bad connection, interference OR the device was not initialized properly.
So try different ports, different computers, something different.
The first step is getting it to the point where it connects solidly (even if it can't/won't find a driver).
Unfortunately you can't tell Windows to use common sense and install a WinUSB driver. That's why we have Zadig: https://zadig.akeo.ie/
Unfortunately (again), adb.exe expects the correct DeviceInterfaceGUID. Ok, you can patch adb.exe or you can use Zadig with a custom .cfg file to specify the DIGUID.
Here is an example .cfg file. You'll have to fill in the VID/PID/MI if you ever get your phone to connect solidly and you can see that info in the DeviceManager.
So, go to Zadig, select Device > Load Preset File, select Options > List all devices, find your device and hit install.
Code:
[device]
Description="Standard Google Device"
VID=0x18d1
PID=0x4ee7
MI=0x00
GUID="{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}"
Good luck.
Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!
tconn said:
Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!
Click to expand...
Click to collapse
Try using a toothpick. Just try not to bend port too much.