Phone stopped being detected by Windows 10 - Redmi K20 / Xiaomi Mi 9T Questions & Answers

Hi guys. Everything was fine yesterday. Ran Windows disc cleaner today and now when I plug in my phone into PC, the charging starts but Windows does not detect it/nor there is menu "file transfer/etc" popping on the phone.
- tried different cables (charges starts on all of them)
- Enabled USB debugging in Dev settings
- reinstalled ADB adb-setup-1.4.3.exe - and chose "Yes" on the prompt to install drivers. Install was successful, but no changes.
- Phone is not detected in Fastboot either.
Adb devices - device is not listed.
EDIT:
It just came back and working normally for now, without me doing anything else, just another re plug. Worrisome...

Related

Can't get windows to recognise my DHD...

Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
wakers said:
Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
Click to expand...
Click to collapse
Have you got Android SDK installed on your PC, Im sure the driver is in there...android .1.0 driver I think..
Without Android SDK you cant use fastboot flash for clockwork image..
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Did you install and launched HTC sync? It should install all the necessary drivers.
f.
Sent from The Galactic Empire using the Dark Side of The Force
wakers said:
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Click to expand...
Click to collapse
Ok try this.... shut phone down, boot (volume down and power button) selected fastboot so it turns red, put the files into android-sdk-windows\tools. i-e the clockwork image and fastboot files
Plug usb cable in.
In "windows search program files" type cmd
now type cd c:\android-sdk-windows (unless you placed the android sdk somewhere else!!)
type cd tools
Type fastboot-windows flash recovery recovery-clockwork-2.5.1.2-ace-modaco-r2.img
When done type fastboot-windows reboot
You should now have CWM.
Now I know you may have tried this but It would help to find out what happens if you haven't already do so.
EDIT ...I also ask this because my laptop doesn't do anything either when I plug in usb cable in fastboot mode..im on windows 7....
Just trying to help...
Really appreciate the reply.
I got a "cannot load" Error.
I think its down to a driver for my phone when in the fastboot mode.
Whats might shed some light on something for someone with a bit more windows/android knowledge than myself is
When the phone is in Fastboot USB mode in Device manager the phone is listed as Android Bootloader interface but when i type into cmd "adb devices" nothing is listed.
When the phone is switched on normally and syncing with HTC sync in device manager the phone is listed as "my htc" and when i type adb devices in cmd, the message adb server is out of date killing...
then daemon is started and the device shows in my list ?
But HTC sync stops working ?
And the internet on my laptop stops working bizarrly.
I'm really scratching my head now lol
I'm thinking it must be something to do with not having the correct driver for Fastboot USB mode ?
Finally sorted it, had to remove the phone from device manager and delete the driver.
Then went into programs and features and removed everything to do with HTC.
Re-Installed HTC Sync
which also reinstalled HTC drivers
Plugged the phone in let windows select the driver and instead of showing in device manager as Android Bootloader Interface it showed as My HTC Sync and worked first time, not sure what happened but sure glad thats finally sorted..
Rixsta really appreciate the advice...
Cheers

[Q] USB Issues with Windows 8.1

put in a new SSD and got Windows 8.1, did a fresh install on a new hard-drive, everything's been working great, My nexus 4 has worked with with ADB./Fastboot and I've been able to transfer files to and from it in MTP mode. Been like that for about 4 days until about 3 hours ago, I had Windows Explorer crash, had to run Task Manager, end the process, and then manually restart explorer.exe My device was plugged in when this happened, and afterwards, I noticed that I could no longer see my Nexus 4 under the Devices & Drives section of "This Computer" (My Computer had a better ring to it lol) First I tried rebooting both my laptop and my Nexus 4, then I tried uninstalled the drivers, rebooting, re-installing, and then rebooting again. Did that like 4 times now, each time re-downloading the drivers, and doing an MD5 hash to create a Checksum, and checking them each time. Also to no avail. ADB shows my device serial number when i enter : ADB Devices, but says it's unauthorized, so if I try anything like: ADB Reboot Bootloader, it says Device is not authorized.
So ! I don't understand wtf is going on. Was working fine before. The drivers are up to date, I just flashed the Official OTA image, and was on the leaked image prior to that. Then earlier this evening I switched to the newest version of the Nexus 5 Port, and everything was still working fine, hadn't made any changes in a couple hours before this happened. When I install the drivers, It acts like it worked. Instead of saying "NEXUS 4" under Other Devices in my Device Manager, it says Composite ADB Interface under Android Devices and MTP under Portable Devices. Sometimes tho the MTP entry will still show the Yellow Exclamation Point. But goes away. Don't know whats up with that either.
Also, it wont let me install drivers unless I am in MTP mode, which Usually you can install them regardless (tho I never tried in Camera mode, I am just assuming about that one) Usually I install drivers without MTP or Camera modes checked, but now if I try it, it says that Windows Cant find the Drivers, even tho I am obviously browsing for them myself and selecting them. And just now I tried updating instead of re-installing them, and it keeps saying that Windows has determined they are the most up to date.
So I am out of I ideas. I even updated windows media player cause that's what fixed my issue on Day 1 of running Windows 8.1 when it wouldn't recognize it at all. So I don't know. Sorry for the long post but I wanted to make sure I got everything in there so hopefully someone can narrow down what the issue is. Cause I've been at it for 3 hours, haven't slept yet, my Nexus 5 gets here today, and I need to get this fixed before I sell it to my buddy. Its brand new, only 15 days old.*
Any thoughts ?*
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
ADB Devices, but says it's unauthorized
Click to expand...
Click to collapse
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
eksasol said:
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
Click to expand...
Click to collapse
ok I am gonna try that now. And as far as the part about my phone being unauthorized. I already knew about the notification that pops up, i was waiting for it to happen. Never did tho. Maybe it will happen after I do the rest of what you said. thanks, i will post my results in a min
no matter what i do, i cant get MTP working. When i uninstall the ADB entry in Device Manager it gives me the check-box option for removing drivers as well, but not on MTP. And now it wont even give me the option to uninstall, update, or anything at all, even tho I uninstalled it already so it should at least give me the option to install drivers. Even tho it's showing up in Device Manager as a Portable device, if I look in Printers and Devices, it shows up as unspecified device. Disabled USB Debugging, and all that. it says its working but it wont show up in My Computer>Devices and Drives still. For some reason ever once in awhile it will pop up with the Yellow Exclamation Point tho, only for a brief second tho. other then that, its shows it like it's running correctly. Also, nothing pops up saying that windows is installing drivers when i plug it in. Which in Win 7, XP, etc, it always did. Does this not happen in Windows 8.1 ?
Also, under Driver Details, which is the only option it lets me click on MTP, it says the drivers are from 2006 lol
Update - Just reinstalled the drivers for ADB and enabled USB Debugging, and everything is still saying its working even tho its not. But when I take my phone out of MTP mode it shows up in device manager under "Other Devices" as Nexus4, with a Yellow Exclamation, and it gives me the option to update drivers, so i tried, but it says Windows Can't find my driver. This is very frustrating.
Had this problem aswell, which was caused by the N version of Windows 8 versions.
These versions dont have Windows Media Player istalled, which is needed for MTP to work.
So to fix your problem you need to download that latest Windows Media Player (WMP) from microsoft and install that.
I dont have the N version, I have WMP installed, i mentioend your fix in the OP. Had to update it, and it worked. It was working fine for the last few days, then it stopped working suddenly
double post, sorry. dont know why that happened.
Vouch. Since I use win8.1 (no n version) Mtp doesnt work. I tried all known drivers, disabled driver signature and so on. The only working combination for me is Usb Debugging + PTP. Then I use file manager to cut the files. Airdroid would be an alternative as well.
update - SOLVED * Kind of.....I say kind of cause I still don't know what caused it but apparently Flashing to the Nexus 5 Port fixed the issue lol. I am assuming something pertaining to the way USB connectivity is controlled by Android got corrupted, and a fresh install was in order. Whatever it was, it worked and i am back in business. thanks to all those who attempted to help.
Sent From My Nexus 4 via XDA Premium 4

If MTP, PTP does not work (If you can't acces phone storage with PC)

My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
4K2K said:
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
Click to expand...
Click to collapse
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Alternative solution is to use KDE Connect app over Wifi. Bonus is that once set up, it is possible to push files from the phone to the PC without any interaction on the PC side - e.g. useful if the PC doubles as a file server.
losteagle said:
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Click to expand...
Click to collapse
Both of my home & works computer (Win10 14959) failed to detect it as MTP or PTP drive. Might have been due to those having previous phone's drivers.
But I faced same problem with fresh out of the box Win8 laptop.
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
ksj0823 said:
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
Click to expand...
Click to collapse
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Citroon said:
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Click to expand...
Click to collapse
Wanted to add my voice here too that I did the same - I had to clean up previous drivers I had installed over time for varios phones and different ADB versions like the one from clockworkmod - once I cleaned that out and installed google drivers from SDK PTP worked and I was able to do Helium restores
I had issue on my Win10 PC, but I found that after I disabled USB debugging, it would work as MTP/PTP, but not for ADB of course. So apparently, I have to toggle USB debugging ON/OFF to switch back and forth from MTP and ADB.
Small pain in the butt.
Solution.
I had the same issue. Drove me NUTS for about an hour. In the end, simply unchecked the USB DEBUGING in developer settings. This will make it pop up immediately.
Update:
I clearly should have read the post above mine first.

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.

Fix for anyone that has ADB connectivity issues.

Not sure If I missed it with searching or if anyone has made a post about this, sorry for repeating.
I just recently bought the Essential phone and for some reason had issues getting the USB debugging authorization to show up. Nothing seemed to fix it, tried numerous cables, usb ports, removed and reinstalled drivers, still nothing.
I realized that there is a file located in C:\Users\Current User Name(whatever the current user is)\.android called adb_usb.ini. It list device IDs of other android devices and for some reason my phone wasn't listed. After adding my device ID (the file just opens in notepad) and saving, I went back to terminal and sure enough my phone got the allow usb debugging rsa key prompt and my phone finally showed up when typing ADB devices.
The device ID is 0x2e17
Also, even though I downloaded the lasted platform tools from google, in order to issue commands in fastboot I need to type fastboot -i 0x2e17
So for example in order to unlock the bootloader I needed to type fastboot -i 0x2e17 flashing unlock. I modified Essentials flashall.sh file and added the device id to all commands in order to get DP4 installed.
Didn't work for me...however windows just gives me an error when i even connect my phone to the PC.
Update: switching usb-c cables DEFINITELY works.
Try another computer will sure fix this, or just install another system like windows 10 or Ubuntu something like that.
I was having problems when i connected my essential phone to the pc and nothing was showing up. After a lot of frustration i decided to plug my usb cable to a usb 2 port instead of a usb 3.0 and that made everything work.
So if you're having problems connecting to the pc try using a regular usb port and not a 3.0 port.

Categories

Resources