Related
Hello, i have a very weird problem. My nexus 4 cant connect to pc as mass storage device.. It worked fine like 4 days ago.. I dont know what happened or what else i can try.. Already tried: usb debugging on/off, factory reset, usb settings in storage menu, different usb port, NOTHING HELPED! There are another weird thing that i spoted is that it only charges through usb when i have nothing selected in storage>usb connections menu, as soon as i try to select mtp or camera it stops from charging and nothing happens. Same problem for AC charging it wont charge when theres mtp or camera selected, and only charges as USB... I'm confused.. Are there any ways to get it working again?
I'm having the same problem.. I've just installed Windows 7 64 bit but it sees my Nexus 4 like Unknown Device.. I uninstalling the drivers and re installing them using Nexus Root Toolkit but no result for now..:crying:
Do you have a ROM or anything installed? I know with PA its a problem at the moment at times. A little more info would be nice. I never had a problem with Windows 7. I'm on Windows 8 now and i had an issue at first with it not showing up at times. But it seems to be fine now.
Just go in
Settings,
Dev options (if you not have it go in phone informations and press many times in row the Build Number, this activate Dev options)
and Disable USB Debugging,
then reconnect your phone, and the computer will see it
USB debbuging isnt working. i have no ROMS, stock android 4.3. And yes, now im running WIN 8, previuosly had 7, the problem occured after installing 8 and trying to plug it in. Its not showing in my computer neither in device Manager. I doesnt make any difference with, or without it pluged in, the only difference is that it will start charging, but then again ONLY when i disable everyting in storage>usb connections.
bump
do you have a fast charge app installed? it sounds like it's an issue related to fast charging via USB. if it's enabled you can't access anything on the phone via usb, but i think that requires to at least be rooted.
I'm on last PA 3.99-Rc1 and I just found out that if I go in Setting-Memory the appilcation shutdown .-. Never had this issue before .-.
Matteo Mazzu said:
I'm on last PA 3.99-Rc1 and I just found out that if I go in Setting-Memory the appilcation shutdown .-. Never had this issue before .-.
Click to expand...
Click to collapse
Nothing, just read that it's a issue with PA while using last Franco Kernel nightly XD I'm going back to windows vista 32bit, so I believe the problem connecting my nexus 4 won't be any more an issue (Going back to Vista because for daily use it worked perfectly and every thing worked fine with the drivers, Windows 7 it's better, but too many issues with drivers bla bla bla XD) :laugh:
I have always used the Windows Driver from the Google SDK (Google USB Driver- As of today, Revision 8) for my Windows 7 64 bit computer and have never had a problem. More importantly there is an Update Manager that comes with the SDK, that when you run, notifies you of newer Windows drivers as they are released. That way as Google issues newer OS builds or Windows issues a new OS, I know that not only my driver but my platform tools aka fastboot/adb/etc. (As of today, Revision 18.0.1) will always be compatible. The problem with these toolkits and driver downloads all over the place on these forums is that you have know idea how old the internals are. The other obvious thing to check is a bad or intermittently bad USB cable. Also make sure "MTP" is checked in Settings > Storage >Settings > USB computer connection.
Hey, I'm sorry if it's against etiquette digging up an old post, but this part worked for me:
pjc123 said:
Also make sure "MTP" is checked in Settings > Storage >Settings > USB computer connection.
Click to expand...
Click to collapse
Thank you so much, I had this problem for a long time before I found this thread.
dunni88 said:
Hey, I'm sorry if it's against etiquette digging up an old post, but this part worked for me:
Thank you so much, I had this problem for a long time before I found this thread.
Click to expand...
Click to collapse
Glad I could help. That setting isn't exactly the easiest thing to find.
Fix usb
Go to device manager in windows 7/8/8.1 . Connect your mobile with usb. You will see android device or adb right click on it, select properties, click uninstall driver. NOTE: When you click this a small popup will appear saying remove software driver, tick on it and click uninstall.. there you go ..it will reinstall drivers and your phone will be finally connected.
im having the same problem . My phone shows as Unknown Device on Device Manager. Tried other cables and usb ports. I can tell that the cables and ports are not the problem since my Nexus 7 can connect without problem. Tried usb debuggin on/off, MTP on/off, PTP. Still no luck. Already tried to reinstall drivers but still the same problem. Hoping this is not a hardware issue. I already tried factory reset and flashing other ROMs
hi there,
thanks for the great omniROM, i use it a while now and I was never so happy with my Galaxy Note N7000!
running the latest 4.4.2 (20140329) and have a SDcard in slot working properly.
I upgraded from stock 4.1.2 and it was an better experience than ever before, but there is just one thing that bothers me: USB Connection
when I connect an USBStick via OTG or via USBcable to PC, the only thing that happens is charging. this appeared some while ago still in StockROM after excessive use of USBSticks (all FAT) and keyboards. I was hoping the rooting and upgrading to OmniRom would 'reset' this behaviour, but it didn't tried differend tools, some with SU and nothing worked.
so my questions is: how can I get into the PhoneUtil-menu in omnirom or the UART/USB option?
after researching some more, I found this similar case and (possible?) solution. i'm keeping some hopes in this to get USBtransfer working with USBsticks again:
........ GT-7000 USB Data connection not working
My phone was not detected as MTP by the computer.
My phone didn't detect that it was attached to a PC.
On my PC --It didn't work.
Another PC --It didn't work.
Even another PC --It didn't work.
Mac --It didn't work.
Tried all sorts of things written on many websites. --It didn't work.
There was no MTP option in the status bar. It just always charged using the PC.
THEN... Finally 1 day, when I was looking at the back of my CPU (PC ) I saw my USB 3.0 Ports (the Blue ones). I had never connected anything to them. So,
Tried on a USB 3.0 Port --It WORKED!
My phone was immediately detected as MTP. The option showed up in the status bar. I could transfer files. But then- What about my USB 2.0 Ports?
Then I did the following :
Dialed *#7248# for the PhoneUtil options.
Under 'UART' tap MODEM. Under USB, PDA.
If this is already your setting, choose the another ones (PDA for UART and MODEM for USB) and then tap SAVE and RESET.
Again dial *#7248# for the PhoneUtil options.
Under 'UART' tap MODEM. Under USB, PDA. Finally tap SAVE and RESET.
Your phone will now be detected as MTP with all types of USB Ports now.
thanks and best regards
Hey Folks,
I'm currently on OMNI Rom (Nightly) version 20140326 on my Int Galaxy S2, having this issue of USB Host driver missing.
I don't get a popup when I connect to any USB devices. I'm able to connect to USB flash drive, but unable to connect to my DSLR camera.
I dont have this issue on my Galaxy S i9000 phone which is flashed with 20140314 nightly. When I try to go to Settings>Storage>USB Computer connection, to change the settings, it doesn't allow me to go in
Previously I was on CM10 & had the same issue. I'm attaching the screenshot from the app, 'USB Host Controller' & from Phone status.
I checked with 'DSLR dashboard' app developer & this rom works fine for him. Appreciate your help to have this resolved.
Hey everyone,
for the past few months my Nexus 4 has been unable to connect to the computer through both MTP and PTP (although it's only MTP I'm concerned about). Device Manager gives me the code 10: device unable to start error despite numerous reboots of the devices. I have tried 2 computers, and both have failed to install the MTP Driver, however, on my main machine, the OS (Windows 7 64 Bit) refuses to install the MTP driver for another device of mine also (Optimus 2X). This has lead me to believe it is a computer problem and not a phone one. However, I also believe that something must have happened to both of my machines at the same time for the driver to not be installed on both of them. The driver installs successfully and quickly in safe mode, but not in normal Windows, which I hope might be of help in solving this error. I have tried the online registry tweaks, wiping cache, sfc /scannow, reinstalling windows media player, numerous uninstalls and re-installs of the drivers and countless reboots. I have also tried toggling both MTP and PTP, but they both trigger the MTP driver installation which eventually fails. I usually leave USB debugging on, however, this has not changed the outcome of the driver installation. It should be noted that ADB works without issue and can see the device perfectly. I know this was a lot of text, and I apologize for that. Thanks in advance to anyone that can help.
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.