Database Users

Can't get ADB to recognize my Galaxy S

Hi All,
I must say first of all Galaxy S is amazing phone and I really love the display.
I'm trying to run lag fix via adb on my Galaxy S but all the time it says "error : device not found".
I've also got Nexus One and adb works fine with it.
I've rooted Galaxy S with BackfireNL instruction and also have latest busybox installed.
Am I doing anything wrong? As adb works with Nexus One but doens't work with Galaxy S.

Before connecting your phone to USB, please make sure that you have the following set correctly (note: translated, I don't have English locale set atm.):
- Settings / Applications / Development: enable (tick) "USB Debugging"
- Settings / About phone / USB settings: select "Mass storage", NOT "Ask" or "Kies"
The last setting in particular appears to be important in my case at least, because when connecting the phone I would get a time-out on my PC before being able to answer the "connect as?" question.
Next time you want to use Kies instead of adb, I would suggest undoing the above settings, to prevent problems connecting to Kies.
Hope this helps.

miki4242 said:
Before connecting your phone to USB, please make sure that you have the following set correctly (note: translated, I don't have English locale set atm.):
- Settings / Applications / Development: enable (tick) "USB Debugging"
- Settings / About phone / USB settings: select "Mass storage", NOT "Ask" or "Kies"
The last setting in particular appears to be important in my case at least, because when connecting the phone I would get a time-out on my PC before being able to answer the "connect as?" question.
Next time you want to use Kies instead of adb, I would suggest undoing the above settings, to prevent problems connecting to Kies.
Hope this helps.
Click to expand...
Click to collapse
I think this setting is in the "wireless and network" > "USB settings" menu.
I haven't gone through the procedure myself. But AFAIK, getting the USB drivers are important, and an often missed step, in this process. Make sure that you connect to Kies in "Kies" mode instead of "Mass Storage" with debugging mode, start Kies, get the drivers installed. Then (maybe, but it should be better than not doing it) restart your computer. Make sure the drivers are all working, some people have had to reinstall.
Alternatively, you can just search for the drivers.

the best way is to set it to set the USB to ASK option every time you connect via the USB
Also you must enable the USB DEBUG mode under Applications Settings

[Q] Samsung Galaxy 3 goes out of adb/mass storage connection occasionally

Hi All,
I have been facing problem of my galaxy 3 I5801 not getting connected through adb/mass storage etc. Following are the symptoms:
* Even if I set USB settings for "Ask on connection", on USB cable insertion, the popup does not come.
* While USB cable is plugged in, I am able to do any change in USB settings (means the USB status is not connected)
* Though debugging is enabled, ADB does not detect the device
* On host side, Device Manager, following drivers are listed.
- USB - Samsung Mobile USB device
- USB - Samsung USB Composite device
- Ports - Samsung Mobile Modem Diagnostic Serial Port
- Modems - Samsung Mobile Modem
- Modems - Samsung Mobile USB modem
* Kies recognizes as I5801, however, contacts etc. are not read from the device
MASTER CLEAR solves this and gets back the device to proper mode and everything works fine. Have done it twice successfully. Again after some time or after installing few apks, I am back to above state. I have installed following apps this time -
aCar, Advanced Task Manager, Facebook, Orkut, Ray Dialer, Skype, To Do List, Twitter and Maps (Brut).
I suspect Maps(Brut) installation, but I need this badly as it is the only turn-by-turn free navigation app that I can use in India and I like that very much. However, uninstalling this app did not recover back the USB.
Any suggestion on how to recover the USB connection by keeping all my apps installed?
Any particular app that is suspect here which I should avoid installing at all?
Any thoughts

Boot into recovery mode and select "wipe cache partition" .

Thanks. I saw few other tips which are in my trial list if the same thing happens next.
I.
1. Dial *#7284# to open PhoneUtil
2. In USB section, switch to Modem, and then switch back to PDA
3. Exit
II.
Boot into recovery mode and reboot again.
III.
Gsam101's suggestion (thanks for that) - Boot into recovery mode and select "wipe cache partition"
Need to see how to boot to recovery mode though. Little confused on the key combinations for Galaxy I5801.

mohankm said:
Need to see how to boot to recovery mode though. Little confused on the key combinations for Galaxy I5801.
Click to expand...
Click to collapse
Use Home+VolUp+VolDown+Power combo You can release all the buttons after initial logo. You'll see recovery screen with 'reboot to the system' or smth option, use it and you'll get your USB back.

Thanks......

I got into the same situation. Tried option 1 and USB is back
Thanks a lot guys.

Option 2 worked for me. Thank you.

Glad that it worked. But, option 1 worked for me all the time. Is it that option 1 did not work for you or you did not try that?

not recognised.. on pc..
mohankm said:
Hi All,
I have been facing problem of my galaxy 3 I5801 not getting connected through adb/mass storage etc. Following are the symptoms:
* Even if I set USB settings for "Ask on connection", on USB cable insertion, the popup does not come.
* While USB cable is plugged in, I am able to do any change in USB settings (means the USB status is not connected)
* Though debugging is enabled, ADB does not detect the device
* On host side, Device Manager, following drivers are listed.
- USB - Samsung Mobile USB device
- USB - Samsung USB Composite device
- Ports - Samsung Mobile Modem Diagnostic Serial Port
- Modems - Samsung Mobile Modem
- Modems - Samsung Mobile USB modem
* Kies recognizes as I5801, however, contacts etc. are not read from the device
MASTER CLEAR solves this and gets back the device to proper mode and everything works fine. Have done it twice successfully. Again after some time or after installing few apks, I am back to above state. I have installed following apps this time -
aCar, Advanced Task Manager, Facebook, Orkut, Ray Dialer, Skype, To Do List, Twitter and Maps (Brut).
I suspect Maps(Brut) installation, but I need this badly as it is the only turn-by-turn free navigation app that I can use in India and I like that very much. However, uninstalling this app did not recover back the USB.
Any suggestion on how to recover the USB connection by keeping all my apps installed?
Any particular app that is suspect here which I should avoid installing at all?
Any thoughts
Click to expand...
Click to collapse
i am facing the same issue.. on my i5801
i m on custom rom indroid 4.1........ dont know wht to do.. tried all the three solutions provided.
kindly help....

Nexus 4 not showing up in my computer as MTP Storage

Hi Guiz, So you all probably have heard this a million times but i have tried every i can to fix this. I have tried many options such as Deleting and re-installing the drivers, trying a different usb port 2.0 and 3.0 I have restored my phone. And my phone only comes up as PTP Camera which is useless since i cant root my N4. This problem occured after i updated to Android 4.3. So my question is how can i make my N4 show up as MTP Storage?
I'm running on Windows 8. Thanks in advance.

Zypent said:
Hi Guiz, So you all probably have heard this a million times but i have tried every i can to fix this. I have tried many options such as Deleting and re-installing the drivers, trying a different usb port 2.0 and 3.0 I have restored my phone. And my phone only comes up as PTP Camera which is useless since i cant root my N4. This problem occured after i updated to Android 4.3. So my question is how can i make my N4 show up as MTP Storage?
I'm running on Windows 8. Thanks in advance.
Click to expand...
Click to collapse
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy

danielms22 said:
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
Click to expand...
Click to collapse
I've been trying to solve this myself, i thank you!!! Finally!!

danielms22 said:
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
Click to expand...
Click to collapse
Thats the problem it doesnt show up.

Zypent said:
Thats the problem it doesnt show up.
Click to expand...
Click to collapse
I also have this problem, my nexus 4 won't show up in device manager (windows 8) it will make the noise and will only show up in my computer if I have usb debugging enabled and select media device, any other combination it won't show up in device manager or in my computer.
What do I do?

foliage said:
I also have this problem, my nexus 4 won't show up in device manager (windows 8) it will make the noise and will only show up in my computer if I have usb debugging enabled and select media device, any other combination it won't show up in device manager or in my computer.
What do I do?
Click to expand...
Click to collapse
Today i've got my new Nexus 4, succesfully unlocked & rooted with this toolkit, but had problems with installing google usb drivers and Universal Adb Driver.
The solution is based on several steps.
I solved my problem this way, hope it will help someone
I have windows 8.1 64-bit, so i had to solve firts the problem with driver signature
1.
How To Disable And Bypass Driver Signature Enforcement In Windows 8
Tutorial link
Tutorial video
If you have problems with driver installations, try this:
2.
Remove hidden existing Nexus 4 or Android Nexus ADB Interface in Device Manager
i had to cleanup the drivers remained after few failed adb driver installations because of the problem in the first step
- (OPTIONAL) Install Nexus Root Toolkit and run it
- (OPTIONAL) click on Full Driver Installation Guide and at step 1
- open Device Manager, click View and select the option Show hidden devices
- now you will see some additional hidden devices (greyed out)
- because i wanted to install the drivers from start i deleted them, that means uninstalled them and added checkmark for deleting local files
- screenshot is attached so you can better understand
Remove the devices that could make problems
3.
- Run Nexus Root Toolkit
- click on Full Driver Installation Guide
- at Step 1 open USBDeview
- in my situation i deleted all the entries with google name
- screenshot in the attach
Final step:
4.
Install drivers for Nexus 4
- Run Nexus Root Toolkit
- click on Full Driver Installation Guide
- at Step 2 i installed Solution #1 - Universal drivers
- maybe you'll need to manually add drivers, if you have an entry in Device Manager that as yellow !
- right click on it - update drivers - browse my computer for drivers - I've added the path to installed Solution #1 - Universal drivers
"C:\Program Files (x86)\ClockworkMod\Universal Adb Driver"
- i repeated it for connection as mtp, ptp and none of that - selection for this is made on nexus: settings - storage - ... in the right upper corner - usb computer connection. so this way the device had installed the needed drivers
- screenshot is added in attach
I've used Wugs Toolkit for installing drivers and after that unlocking and rooting the Nexus 4.
My problem was that there was present HIDDEN ADB Interface under Android Device, after above mentioned steps, my nexus is working properly when connected as MTP device

danielms22 said:
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
Click to expand...
Click to collapse
Brilliant!!!

Not showing up in device manager
danielms22 said:
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
Click to expand...
Click to collapse
I am also facing this issue since flashing 5.0. It doesn't even come up on device manager. Any suggestions?

amj2403 said:
I am also facing this issue since flashing 5.0. It doesn't even come up on device manager. Any suggestions?
Click to expand...
Click to collapse
same here ==

Kogan Agora HDMI Smart TV Quad Core - Root Access

Hi,
So I have had a good experience with the Kogan Agora 7" a couple of years ago. I flashed a new ROM and my 6 year old still idolizes it. It's perfect for games and movies while traveling and cost bugger all.
I was considering getting my kids a console unit for games but came across the new Quad core HDMI Dongle. I though to myself there is the ticket, When traveling i could use it as a smart TV (plug and play is King) Or it may be possible to replace or augment my Media-portal HTPC system.
I bought one and on the face of it it appears to do all that I require from an Android device like web surfing, mail checking and video streaming fine, except when it came to installing the Playstation controller.
I needed Root access and it was a bit of a pain to get it done. BUT I found it!
I used RK3188_ROOT for CX-919 FW0715 MOD by Everal. found here.
1. Turn the device on
2. Make sure USB debugging is enabled
3. Connect the device to Win7
4. Start the file "TPSparkyRoot.bat" as admin
Enjoy.
So if anyone decides to purchase one of these to play with, you will be glad to know that it is a Rockchip RK188. Weather you think that hardware is good or not is irrelevant but it is useful to know as I tried many methods to gain root but once I had this bit of info it became easy.
Those infinity Pocket PC's may be the same although I can't be sure.
I managed to pair a sixaxis controller and am working on getting it running in a game. I will post if i have any more issues and or success.

Raskern said:
1. Turn the device on
2. Make sure USB debugging is enabled
3. Connect the device to Win7
4. Start the file "TPSparkyRoot.bat" as admin
Click to expand...
Click to collapse
Thanks for posting this info. However I'm not able to get this to work. My PC doesn't recognise the device when it's in "USB Debugging" mode. In the device manager it just appears in "Other Devices" as "KHSTVQCDONA". I've tried updating the software, selecting the "usb_drivers" folder containing drivers provided in the downloading Zip file, and also tried downloading the "Google USB Drivers" directly from Google, but Windows doesn't find the drivers for this device.
If I disable "USB Debugging" the device does connect successfully under "Portable Devices", but clearly that's not much use.
I can't seem to figure it out.
Below are the steps I took in trying to get it to work. I was going to write it as a guide for dummies, but I never got it working...
Download the software from the link above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the bit "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC.
Make sure the Micro-USB port of the device is connected to a power source (either your PC or the provided AC adapter). The port doesn't seem to transfer data.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open the Windows "Device Manager".
In the "Device Manager", expand "Other Devices", then right-click on "KHSTVQCDONA" and click on "Update Driver Software".
Click "Browse my computer for driver software".
Navigate to the "usb_drivers" folder of the software you extracted earlier, select it, and click "OK".
Click "OK". THIS DIDN'T WORK, stating that "Windows was unable to install your KHSTVQCDONA" and "Windows could not find driver software for your device".
[*] Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator".
[*]C:
[*]cd RK3188_ROOT
[*]TPSparkyRoot.bat
At this point I see the following:
*---* VonDroid.com N101 II Root Tool based on work by sunnydavid *---*
--- Plug in your device, make sure debugging is enabled in Developer Options
--- This script will now copy files over to your N101 II
error: device not found
error: device not found
error: device not found
--- Reboot 1/3 - Press Space Bar once the device has rebooted
Press any key to continue . . .
error: device not found
error: device not found
error: device not found
--- Reboot 2/3 - Press Space Bar once the device has rebooted
Press any key to continue . . .
error: device not found
--- If the ID shows as 0/root then continue, otherwise CTRL+C to cancel and star
t over
Press any key to continue . . .
Click to expand...
Click to collapse
I terminate at this point
I've also done the following
Un-ticked "Verify apps over USB"
In "Security", ticked "Unkown sources", and un-ticked "Verify apps"
At this point I'm totally at a loss.
I had already started using the device initially, so I did a factory reset, but this hasn't helped at all.
Can you see anything I'm missing, or point me in the right direction?
Many thanks in advance! :good:

Ok So I know i messed around with many drivers installing and uninstalling before it worked. I Thought it was the last set that came with the Root method but I may be wrong.
Also I cant remember exactly now but I am pretty sure if you activate the connect to computer you bypass the ROM and connect to the SD card and the U SD. So that would not help when accessing the root files.
Try re-installing the drivers after connecting without the box checked in settings or try the ones from super oneclick 2.3.3 or even the pocket pC ones. you may also need to uninstall the device then reconnect to get a clean run at it. Windows likes hanging onto what it thinks is the best driver even when they don't work or are completely wrong.
Also I ran the batch file form within windows not in console, Just right clock to run as administrator.
I have just used it for a couple of weeks in Japan get let the Kids watch Aview (iView) and it worked a treat. Also the latest sixaxis updates made the controller even better than before. I can probably have a tool around with it later this week but I am busy before then so wont be able to help any. It can be done!
PM me if you cant find the drivers mentioned above I can email them to you.

Thanks for the quick response.
Can you just confirm that you were connecting using the blue Male-Male USB cable, and not a USB-Micro-USB cable?
When I connect to the Micro-USB port it doesn't see a device at all. It just seems to provide power.
When I connect with the blue Male-Male USB cable, unless I have "Connect to PC" ticked, it also doesn't see a device.
I don't have a micro-SD card installed, but that doesn't matter right?
I'll try those drivers you suggest. Thanks.

I am quite keen to figure out what is different but I cant access it for a couple of days sorry.
I definitely used a full sized USB to Connect, I may have used another one, and powered it from the Micro USB direct to power supply. If you are connecting it to the PC for power it may cause problems.
I know that you cannot access the recovery menu unless you are powering through the Micro USB only. Another thing I meant to mention in my original post. I may have posted it elsewhere.

SUCCESS! After I got the SuperOneClick software to forcibly install the drivers the device was then recognised and I could root the device.
Thanks. I'll write up the full instructions.

Excellent!! Thanks for writing up the guide.

OK, here is a full step-by-step guide for getting this to work:
Download "SuperOneClick" from Download.com (CNET). I can't post external links right now because I'm a new user, but it will appear if you do a Google search.
Extract SuperOneClick to a temporary location ("C:\temp" for the purpose of this installation).
Download the software from the link in the first post above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the big "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC (for the purpose of these instructions "C:\temp").
Make sure the Micro-USB port of the device is connected to a power source (ideally the provided AC adapter). The port doesn't seem to transfer data so don't connect it to your PC, unless you are using your PC as the power source. Basically as long as it's turned on, then continue.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open "SuperOneClick"
In SuperOneClick click the "Advanced" tab, then click "Check Drivers".
When prompted to ask if you would like it to forcefully install drivers, click "Yes".
Click the "Install..." option when prompted by "Windows Security".
You should then hear the device connect, and disconnect, and see an message "Driver installed! Please reconnect your device", so click "OK".
Disconnect the blue USB cable from you PC, and then reconnect it. You should hear that the device has connected successfully (and it now appears as "Android Composite ADB Interface" in you "Device Manager" if you care to check.).
Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator". (I found that running the .bat file directly failed because it didn't find the "adb" application)
C:
cd temp\RK3188_ROOT
TPSparkyRoot.bat
Follow the prompts from here. The application should reboot your device several times (if not something is wrong), after which point you press any ket to continue. From here everything was very straight-forward once the .bat file completed the device was then rooted.
Enjoy

I had to do things differently......
Used rocketchip_batch_tool_1.7 for drivers, superoneclick didnt do anything.
I ran the batch from the folder on my desktop.
For EACH device re-boot i had to RE CHECK connect usb on cx919 settings.
I got a few errors about no more storage on my device when it tried to copy some stuff, although i have the super user and i tried sixaxis controller which requires root and it worked. Not sure what the files were.
update:
Hmm and it seems SSL websites dont work now as well as Netflix or the Store.
ill have to try something else!
Update:
did a factory wipe. all seems ok now.
TeqTeq said:
OK, here is a full step-by-step guide for getting this to work:
Download "SuperOneClick" from Download.com (CNET). I can't post external links right now because I'm a new user, but it will appear if you do a Google search.
Extract SuperOneClick to a temporary location ("C:\temp" for the purpose of this installation).
Download the software from the link in the first post above. On the "Share-Online" page click the small-ish button that says "continue for free", and not the big "DOWNLOAD FILE (regular download)" button in the banner ad (that I feel very silly for clicking several times).
Once the file "RK3188_ROOT for CX-919 FW0715 MOD by Everal.zip" has finished downloading, extract it to a temp location on your PC (for the purpose of these instructions "C:\temp").
Make sure the Micro-USB port of the device is connected to a power source (ideally the provided AC adapter). The port doesn't seem to transfer data so don't connect it to your PC, unless you are using your PC as the power source. Basically as long as it's turned on, then continue.
On the Agora device, go to "Settings", open the "USB" menu, and enable "Connect to PC". Without this the device wasn't recognised by my PC at all.
In "Settings", click on the "Developer options" menu, and tick "USB debugging".
Connect the provided blue Male-Male USB cable to a full-sized USB port on the device, and to a USB port on your PC. At this stage the device connects but is not recognised.
Open "SuperOneClick"
In SuperOneClick click the "Advanced" tab, then click "Check Drivers".
When prompted to ask if you would like it to forcefully install drivers, click "Yes".
Click the "Install..." option when prompted by "Windows Security".
You should then hear the device connect, and disconnect, and see an message "Driver installed! Please reconnect your device", so click "OK".
Disconnect the blue USB cable from you PC, and then reconnect it. You should hear that the device has connected successfully (and it now appears as "Android Composite ADB Interface" in you "Device Manager" if you care to check.).
Open "Command Prompt", by right-clicking on it and clicking "Run as Administrator". (I found that running the .bat file directly failed because it didn't find the "adb" application)
C:
cd temp\RK3188_ROOT
TPSparkyRoot.bat
Follow the prompts from here. The application should reboot your device several times (if not something is wrong), after which point you press any ket to continue. From here everything was very straight-forward once the .bat file completed the device was then rooted.
Enjoy
Click to expand...
Click to collapse

Worked fine since then. All a sudden same prob, no Netflix no store. Wtf?

Just wanted to post an updated root method since i got one of these second hand last week
1. get the universal rockchip drivers, or the latest generic google ones. both worked for me on two different PC's. (including windows 8.1 x64)
2. Enable USB Debug mode in developer options. you know the drill.
3. the kogan device has a "USB" menu in settings, that has a 'connect to PC' setting. turn that on or ADB cuts out shortly after the system boots - turn it off after rooting for it to work normally.
4. connect PC to kogan dongle via the USB port next to the power LED. The other one doesnt work.
5. root with whatever method you want - i used kingo root which rooted it flawlessly first time.
6. have fuuuuun!
3 and 4 stumped me for days til i figured out what was going on. not something i'd ever encountered before, and likely unique to this device and why some people cant figure it out.

Oneplus 5 not recognised in Windows 10

Hi,
I've received a couple of days ago two Onplus 5.
They both work great but when I try to connect them to my desktop, they get detected as "qualcomm hs-usb diagnostics 900e" by windows 10 that states the USB device is not recognised.
The issue is reproduced on a laptop, although it did get picked up once by the laptop, only to fail on a second attempt with the same device name "qualcomm hs-usb diagnostics 900e" after I installed the driver provided by Oneplus.
I read on the forum that "qualcomm hs-usb diagnostics 900e" is normally related to Bricked phone issues, which is not my case and I don't know what to do to resolve this.
I also tried to activate the USB debug mode on the phone, but this didn't change the problem.
My windows are all up to date and my phones as well (running Android 7.1.1, OxygenOS 4.5.2)
Has anyone experienced this issue with that phone or any other?
I would greatly appreciate some help and I thank you in advance for reading this and offering advice.

Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.

dcrnic said:
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
Click to expand...
Click to collapse
Thanks dcrnic, I must have skipped a step with the debugging mode because your procedure did the trick.
Is this a normal process to have to go to Dev mode and Debug mode to be able to connect to a PC?
Thanks again for your help!:good:

Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing

Moderators
Please delete ... Today forum is so slow, and it do double posting for some reason even I press reply just once.
Thank you.

FIXED: Use stock op5 cable. The other cable that gave me issues works just fine for op2.
The phone used to be seen by win10, but since oem unlock and superSU, the computer at work doesn't recognize it. Ran the 4.5.2 update with same results. I noticed that in Developer Options -> Select USB configurations charging is selected and greyed out. Going in selecting anything else returns is to Charing.

Device Manager > Find the phone > Right click > Update drivers (or something like that) > Select driver from Computer > Select "MTP USB Device" Enjoy

I'm having the same issue. If I manage to get it to connect to the PC, then after I unplug and plug it again it gives the same not recognised balloon. It only seems to work with USB Debugging On

I ended up using the original op5 cable and it recognizes the phone right away.The cable that didn't work for op5 is not stock, but worked perfectly fine for op2.

Same issue
Even I'm facing the exact same issue on my op5

dcrnic said:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Click to expand...
Click to collapse
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.

djsubterrain said:
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
Click to expand...
Click to collapse
Yes, they are on the phone, but computer need to recognize device to see it. It does not, so the drivers on the phone are useless in this case.

I compared this to my ZTE Axon 7. If you choose "Charge only" the Axon 7 is recognized as a USB input device. This should also happen for our OP5 but the driver (which btw. is a windows standard driver) does not contain PID 900E and also does not like to have it forced to a USB input device.
The Axon 7's PID is F006.
However, the real issue is when Windows decides to use Qualcomm's HS USB Diagnostic Interface driver which seems to give even more trouble (at least for me). When I tried to switch to MTP this would not work and my Windows 10 hung itself up when rebooting or shuting down. For now I just disabled the "Unknown device" to prevent such things from happening. Charging still works this way and the phone is correctly recognized when changing to MTP.
If you are facing the same issue, disconnect the Oneplus 5 from your PC, reboot the PC and after that launch the device manager. You need to enable hidden devices in the view menu of the device manager to see disconnected devices. Now remove the device "Qualcomm HS USB Device Interface" and also choose to uninstall the driver itself. After that you can connect your device again and it should pop up as "Unknown device". Then simply disable the device.
Regarding the drivers from Oneplus: this package is lacking a driver for the device we are seeing (VID_05C6&PID_900E).

Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"

aa_chow said:
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
Click to expand...
Click to collapse
Worked for me, only remember to Uncheck usb debugging BEFORE the update....

Hmm, didn't work for me, same behavior as before the update...Qualcomm HS-USB as soon as phone is plugged in...USB debug was off.
Sent from my ONEPLUS A5000 using Tapatalk

try changing port (and remember to restart the pc)

Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.

bricky23 said:
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
Click to expand...
Click to collapse
It worked the first time too, but not the second time...at that point connected detected as Qualcomm HS-USB Diagnostic, and computer won't shut down.
And yes I installed it a few time, and it works the first time connecting, but not the second time around.
Sent from my ONEPLUS A5000 using Tapatalk

I don't have my OP5 yet, but I had a very similar and difficult experience with my OP3 when I first received it on Windows 10 Pro. On top of installing the proper drivers, I also had to go into Device Manager and run some steps (I'm going off on memory so they may not be entirely accurate). The root cause is driver signature check enforced in Windows 8+. So by going into Device Manager and seeing "kedacom USB driver", right click and find the oneplus USB driver you installed above and also need to disable the driver signature enforcement (in windows 10 go to advanced startup settings, reboot and choose (I think) #7 then reboot). Then plug in the phone usb go to device mgr right click on kedacom USB driver and choose the oneplus driver.
I don't have all the steps in the right order but it should fix your issue.