Jump to content
man.with.a.plan

[Solved] [HELP] Android not recognised on Win 10 (1809)

Recommended Posts

man.with.a.plan

Hello.. I've been having this weird trouble from when I purchased a new HP Notebook. I updated it to the latest build and installed all drivers + ADB drivers + AIO ... But I'm having a hard time connecting my OPPO Realme 1 smartphone to it via USB.. 

When I tried connecting it to my old Laptop (win 10 1803) it connected very well giving me options like Charging, File Transfer, etc.

Whereas on the new one, it only charges.. I tried developer options, usb debugging, latest update from OPPO... No LUCK..:(

Share this post


Link to post
Share on other sites
man.with.a.plan
17 minutes ago, teodz1984 said:

switch usb port 

Tried all 3 ports with two different cables too.. I have an old lenovo phone & it's connecting to that same laptop very well...

Share this post


Link to post
Share on other sites
man.with.a.plan
Just now, teodz1984 said:

Are you on a PC?  or a phone?

PC...

Share this post


Link to post
Share on other sites
man.with.a.plan
1 minute ago, teodz1984 said:

what browser are you using? 

Chrome... But why?? 

The phone isn't even being recognised by Win to update drivers... I'v however installed the ADB...

Share this post


Link to post
Share on other sites
leapinlizards

latest drivers for you phone from their website ?

Share this post


Link to post
Share on other sites
teodz1984

https://www.realme.com/

 

you need third party drivers for specific phones

Quote

;

; Android WinUsb driver installation.

;

[Version]

Signature           = "$Windows NT$"

Class               = AndroidUsbDeviceClass

ClassGuid           = {3F966BD9-FA04-4ec5-991C-D326973B5128}

Provider            = %ProviderName%

DriverVer           = 08/28/2014,11.0.0000.00000

CatalogFile.NTx86   = androidwinusb86.cat

CatalogFile.NTamd64 = androidwinusba64.cat

 

[ClassInstall32]

Addreg = AndroidWinUsbClassReg

 

[AndroidWinUsbClassReg]

HKR,,,0,%ClassName%

HKR,,Icon,,-1

 

 

[Manufacturer]

%ProviderName% = Google, NTx86, NTamd64

 

 

[Google.NTx86]

 

;Google Nexus One

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_0D02

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_0D02&MI_01

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4E11

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E12&MI_01

 

;Google Nexus S

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4E21

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E22&MI_01

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4E23

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E24&MI_01

 

;Google Nexus 7

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E40

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E42&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E44&MI_01

 

;Google Nexus Q

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_2C10

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_2C11

 

;Google Nexus (generic)

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE4&MI_02

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE6&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE7

 

;Google Glass

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_9001

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_9001&MI_01

 

;Project Tango (generic)

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4D00

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4D02&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4D04&MI_02

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4D06&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4D07

 

 

[Google.NTamd64]

 

;Google Nexus One

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_0D02

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_0D02&MI_01

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4E11

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E12&MI_01

 

;Google Nexus S

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4E21

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E22&MI_01

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4E23

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E24&MI_01

 

;Google Nexus 7

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E40

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E42&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E44&MI_01

 

;Google Nexus Q

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_2C10

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_2C11

 

;Google Nexus (generic)

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE2&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE4&MI_02

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE6&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4EE7

 

;Google Glass

%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_9001

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_9001&MI_01

 

;Project Tango (generic)

%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4D00

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4D02&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4D04&MI_02

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4D06&MI_01

%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4D07

 

 

[USB_Install]

Include = winusb.inf

Needs   = WINUSB.NT

 

[USB_Install.Services]

Include     = winusb.inf

AddService  = WinUSB,0x00000002,WinUSB_ServiceInstall

 

[WinUSB_ServiceInstall]

DisplayName     = %WinUSB_SvcDesc%

ServiceType     = 1

StartType       = 3

ErrorControl    = 1

ServiceBinary   = %12%\WinUSB.sys

 

[USB_Install.Wdf]

KmdfService = WINUSB, WinUSB_Install

 

[WinUSB_Install]

KmdfLibraryVersion  = 1.9

 

[USB_Install.HW]

AddReg  = Dev_AddReg

 

[Dev_AddReg]

HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"

 

[USB_Install.CoInstallers]

AddReg    = CoInstallers_AddReg

CopyFiles = CoInstallers_CopyFiles

 

[CoInstallers_AddReg]

HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"

 

[CoInstallers_CopyFiles]

WinUSBCoInstaller2.dll

WdfCoInstaller01009.dll

 

[DestinationDirs]

CoInstallers_CopyFiles=11

 

[SourceDisksNames]

1 = %DISK_NAME%,,,\i386

2 = %DISK_NAME%,,,\amd64

 

[SourceDisksFiles.x86]

WinUSBCoInstaller2.dll  = 1

WdfCoInstaller01009.dll = 1

 

[SourceDisksFiles.amd64]

WinUSBCoInstaller2.dll  = 2

WdfCoInstaller01009.dll = 2

 

[Strings]

ProviderName                = "Google, Inc."

SingleAdbInterface          = "Android ADB Interface"

CompositeAdbInterface       = "Android Composite ADB Interface"

SingleBootLoaderInterface   = "Android Bootloader Interface"

WinUSB_SvcDesc              = "Android USB Driver"

DISK_NAME                   = "Android WinUsb installation disk"

ClassName                   = "Android Device"

 

 

Share this post


Link to post
Share on other sites
man.with.a.plan
8 minutes ago, teodz1984 said:

https://www.realme.com/

 

you need third party drivers for specific phones

 

So... How to install... There's some unexecutalble files in the zip...

Share this post


Link to post
Share on other sites
man.with.a.plan
2 minutes ago, teodz1984 said:

unzip

right-click on android_winusb.inf

select instal

Nah... No Luck... Guess I'm gonna have to reinstall Windows...

I have a eset IS installe with 2 year product key from @Recruit .. Is it possible to save the licence when I format and reinstall???

Share this post


Link to post
Share on other sites
Akaneharuka
2 hours ago, man.with.a.plan said:

Nah... No Luck... Guess I'm gonna have to reinstall Windows...

I have a eset IS installe with 2 year product key from @Recruit .. Is it possible to save the licence when I format and reinstall???

 

Try this method

 

 

Share this post


Link to post
Share on other sites
DKT27

It's really hard to get Android drivers running. Even I do not know how I did it. That's no fault of the OS.

 

Try this. Go in device manager, uninstall all the drivers related to it. How to do it you may ask. First remove the wire from Android device. Now, in device manager, click on View > Show Hidden Devices. Now, in the Android device section of it, uninstall all drivers related to it, including the hidden ones. This part you have to do every time you think the method is not working before trying a new method.

 

Restart the computer while making sure Android device is still not connected.

 

Now, extract those downloaded drivers somewhere. In device manager, click on Actions on top and select Add Hardware > Install the hardware manually - the second option > Show all devices > Have Disk > Browse > Find the extracted file of which you had downloaded, select it > Install it.

 

Make sure developer options and USB debugging is enabled on your Android. Now, try connecting your Android device. It does not matter what device manager shows. Run CMD, type this:

 

Quote

adb devices

 

Sometimes you need to type it two times. A message will appear on your Android device, click on Allow on it. If it shows the device in that list in CMD, means it properly connected there.

Share this post


Link to post
Share on other sites
man.with.a.plan
2 minutes ago, DKT27 said:

It's really hard to get Android drivers running. Even I do not know how I did it. That's no fault of the OS.

 

Try this. Go in device manager, uninstall all the drivers related to it. How to do it you may ask. First remove the wire from Android device. Now, in device manager, click on Show Hidden Devices. Now, in the Android device section of it, uninstall all drivers related to it, including the hidden ones. This part you have to do every time you think the method is not working before trying a new method.

 

Restart the computer while making sure Android device is still not connected.

 

Now, extract those drivers somewhere. Now, click on Actions on top and select Add Hardware > Install the hardware manually - the second option > Show all devices > Have Disk > Browse > Find the extracted file of which you had downloaded, select it > Install it.

 

Make sure developer options and USB debugging is enabled on your Android. Now, try connecting your Android device. It does not matter what device manager shows. Run CMD, type this:

 

 

Sometimes you need to type it two times. If it shows the device in that list, means it properly connected there.

 

I had tried the adb devices command and it didn't show any device nor did it say "no device" , it just gave a blank row..

 

I'm going to try your method..

Share this post


Link to post
Share on other sites
DKT27
1 minute ago, man.with.a.plan said:

 

I had tried the adb devices command and it didn't show any device nor did it say "no device" , it just gave a blank row..

 

I'm going to try your method..

 

Keep us updated on it. Remember, uninstalling hidden Android devices is important, so is restarting the computer after doing it.

Share this post


Link to post
Share on other sites
man.with.a.plan
30 minutes ago, DKT27 said:

 

Keep us updated on it. Remember, uninstalling hidden Android devices is important, so is restarting the computer after doing it.

Now the adb itself doesn't shows anything...

Capture.PNG

Capture (2).PNG

Edited by man.with.a.plan

Share this post


Link to post
Share on other sites
man.with.a.plan

I had installed ADB All-in-One....

Capture (3).PNG

Share this post


Link to post
Share on other sites
man.with.a.plan

@DKT27

Man.... It's still not working... Any suggestions?

I tried :-

Turning on dev mode/USB debugging

MTP selection from dev mode

Insalling adb and related drivers

And method suggested by you... (That just gave nothing)

Reinstalling Win 10 1809

:wut:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×