Kedacom driver possible permanent fix - OnePlus 3 Questions & Answers

I've posted this as a new thread to separate fastboot and kedacom driver from the other W10 issues AND IT IS AT YOUR OWN RISK.
Apologies if I've reinvented the wheel - I haven't found any related posts
I updated the Kedacom usb driver in Device Manager by manual selection of the OnePlus Android Bootloader Interface and fastboot access worked. However a PC boot later and "kedacom" was back and a manual update required.
I made the changes below and 2 reboots later no sign of "kedacom" and reboots of the OP3 to bootloader cause W!0 to load the OnePlus Android Bootloader Interface device.
1) Find the "kedacom" driver.
There is a command line utility in Windows "pnputil.exe" ( see full syntax and use at https://msdn.microsoft.com/en-gb/library/windows/hardware/ff550423(v=vs.85).aspx )
that lists all non-core Windows drivers that are installed. The command can be run from any location so running from R:\junk\> this "pnputil /e >drivers.txt" will create a text file in R:\junk called drivers.txt.
A search of the file for "kedacom" finds this entry:
Published name : oem39.inf
Driver package provider : Google, Inc.
Class : Kedacom USB Device
Driver date and version : 08/28/2016 11.0.0.0
Signer name : Microsoft Windows Hardware Compatibility Publisher
I DON'T KNOW IF "oem39.inf" IS A FILE NAME UNIQUE TO MY PC SO CHECK!!!!!
In the same file I located the "fastboot" driver (you can find the inf file used from Device Manager: device> properties> details tab > in "property name" box select "inf name")
Published name : oem36.inf
Driver package provider : OnePlus, Inc.
Class : Android Phone
Driver date and version : 05/24/2012 6.0.0.0
Signer name : Unknown
Note it is not WHQL signed. ( Unsigned drivers and Windows 10 and W10 Pro needs a full page. Depending on your W10 version and when it was installed (see https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/) then "out of the box" W10 will only use WHQL certified drivers (hence some of the Anniversary edition problems and the also the recent spate of op3 problems????). I now run Windows in "test mode" with no issues. Random google link https://www.linkedin.com/pulse/enable-test-mode-windows-10-ajibola-okubanjo.
I now deleted the "kedcom" driver with the command "pnputil /d oem36.inf " .
Note: pnputil with /d will not delete an inf file for any "working" device that is connected to the PC - so you can't delete an active driver inf file by accident. Look at the syntax link above to force a delete.
I believe that the kedacom version number (Driver date and version : 08/28/2016 11.0.0.0) may indicate that it is part of Google's WinUSB android driver set. Could it be installed when you attempt to download the OP3 drivers from the phone "CD drive" ? I've got other Google android devices and have had no issues following the "deletion". In fact I cleaned out a stack of oemxx.inf files that had accumulated through the use of various devices, one click driver installations, Google v9 drivers etc.

Related

Some help with USB and XDA II

Hi,
Maybe someone here knows a solutions to this one:
When you go to bootloader on the XDA II you can use a serial cable to talk to it. However you can also dock your device in the cradle again and it will allow a USB connection to the bootloader prompt. However, with Windows it will start the wceusbsh.sys driver for active sync. In Linux it loads the generic serial USB driver, which allows you to connect to the bootloader with a terminal program.
Question is: does anyone know how to prevent the wceusbsh.sys driver to load, but instead load the serial usb driver (so you can use hyperterminal for example) OR how you can programmatically talk to the device through the wceusbsh.sys driver without any actuall active sync on the side of the device (that is running the bootloader and presenting a USB> prompt)
If I'm not clear let me know.
Thanks,
(not really sure) but maybe this may help: http://www.lvr.com/usbfaq.htm
What I tried so far is edit the INF file for the wireless modem with the vendor and equipment IDs for the bootloader mode. Then remove the active sync driver from the Device manager and try to add the INF manually. That doesn't work without the device connected. And once you connect the device it immediately installs the windows driver again.
ys, that is what I encountered too.
maybe completely remove everything from \windows\inf that has some relation to active sync?
maybe the trick is to set the correct vendor/product id:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/modem/hh/modem/modem6_0ox3.asp
( trying now, requires reboot .. maybe a good sign )
Code:
[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%XDADEV%
LayoutFile=layout.inf
DriverVer=10/15/1999,5.0.2153.1
[Manufacturer]
%XDADEV%=XDADEV
[XDADEV]
%XDAUSBSER%=Reader, USB\VID_0BB4&PID_00CE
[Reader_Install.NTx86]
;Windows2000
[DestinationDirs]
DefaultDestDir=12
Reader.NT.Copy=12
[Reader.NT]
CopyFiles=Reader.NT.Copy
AddReg=Reader.NT.AddReg
[Reader.NT.Copy]
usbser.sys
[Reader.NT.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,usbser.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
[Reader.NT.Services]
AddService = usbser, 0x00000002, Service_Inst
[Service_Inst]
DisplayName = %Serial.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\usbser.sys
LoadOrderGroup = Base
[Strings]
XDADEV = "XDA Developers"
XDAUSBSER = "XDA Serial over USB"
Serial.SvcDesc = "XDA USB Serial emulation driver"
one step further, now activesync no longer works, and I do see a broken 'COM3'.
got it to work programmatically - see http://www.xs4all.nl/~itsme/projects/xda/xda-ii.html - the xda2dmp tool.
allows you to dump either windows ce, or gsm memory, via serial port or usb

[SOLVED] USB Tethering - Missing RNDIS Driver

Problem: I'm trying to USB tether my phone using a Wi-Fi connection (3G is not available atm). I connect my phone to my PC. I go into menu -> settings -> Wireless & network settings -> tethering & portable hotspot, and check USB tethering. Device manager says an RNDIS driver is missing.
Setup: Rooted (using unRevoked) HTC Incredible running CyanogenMod 7.03, not overclocked atm. USB debugging is enabled. I am running Windows 7 64-bit on my PC. Everything is running smoothly.
What I've tried:
I've searched everywhere and cannot find this driver. Of course, Windows 7 cannot find it online.
I can't install ActiveSync because I am running Windows 7.
I've installed Windows Mobile Device Center 6.1, but it still can't find the driver.
The Google OEM USB drivers out of the Android SDK don't work.
Without HTC Sync installed, I simply do not have the RNDIS driver. With HTC sync installed, this is what happens: The RNDIS driver gets installed, but when I check the USB tethering box on my phone, it goes on for a second, and then immediately goes off again.
Please help, this is one of the most frustrating problems I've ever dealt with, and it seems to be a simple driver issue.
Jackson
*EDIT* This solved it.
Good learning, thanks for sharing!
Sent from my ADR6300 using XDA Premium App
jacksonwalters said:
Problem: I'm trying to USB tether my phone using a Wi-Fi connection (3G is not available atm). I connect my phone to my PC. I go into menu -> settings -> Wireless & network settings -> tethering & portable hotspot, and check USB tethering. Device manager says an RNDIS driver is missing.
Setup: Rooted (using unRevoked) HTC Incredible running CyanogenMod 7.03, not overclocked atm. USB debugging is enabled. I am running Windows 7 64-bit on my PC. Everything is running smoothly.
What I've tried:
I've searched everywhere and cannot find this driver. Of course, Windows 7 cannot find it online.
I can't install ActiveSync because I am running Windows 7.
I've installed Windows Mobile Device Center 6.1, but it still can't find the driver.
The Google OEM USB drivers out of the Android SDK don't work.
Without HTC Sync installed, I simply do not have the RNDIS driver. With HTC sync installed, this is what happens: The RNDIS driver gets installed, but when I check the USB tethering box on my phone, it goes on for a second, and then immediately goes off again.
Please help, this is one of the most frustrating problems I've ever dealt with, and it seems to be a simple driver issue.
Jackson
*EDIT* This solved it.
Click to expand...
Click to collapse
Thank you for the Thanks. haha. =oD
Thanks a lot!
Thanks for this and posting the fix
Just to save some people some heavy head scratching: If you get error 10 for the RNDIS device in the device manager and USB-tethering does not work, disable USB-debugging for the time being.
Missing RNDIS driver (karbonn A12) windows 8
This works for all operating systems(hopefully) , and i have tried it for windows 8 to connect karbonn A12 via tethering
can you tell me the password for that zip file
gokullal said:
This works for all operating systems(hopefully) , and i have tried it for windows 8 to connect karbonn A12 via tethering
Click to expand...
Click to collapse
sir i need a password
password
vetri789vel said:
sir i need a password
Click to expand...
Click to collapse
priceandspecification.in
gokullal said:
priceandspecification.in
Click to expand...
Click to collapse
password not work
Worked for me...
thanks its works for me I downloaded that 8 Mb File and followed the steps mentioned in .txt file,,,, ")
thanks gokullal for the ultimate solution
gokullal said:
priceandspecification.in
Click to expand...
Click to collapse
password not work
Thank You!
Thank You for posting this! It really solved my alcatel single rndis problem! Thank You soooo much!
need help
gokullal said:
This works for all operating systems(hopefully) , and i have tried it for windows 8 to connect karbonn A12 via tethering
Click to expand...
Click to collapse
i have followed your procedure but i get "the specified folder does not contain information about your hardware".how should i solve this..i use android one mobile an my pc's operating system is xp
RNDIS_Driver_Windows7_8
I had same problem. My asus zenfone 6 was not able to usb tethering on my windows 8.1 computer.
I got help frım this topic but it was not clear. So clear how to is shown below.
First download the driver and unrar it.
1. Connect your phone, open usb tethering
2. go to your device manager.
3. Find the Device with the little ? and then maybe a yellow !. (RDNIS)
4. Right click that device and select Update Driver.
5. When the window pops up, select, Browse My Computer for driver software, then on the next screen, click on the bottom that says, LET ME PICK.
6. Then it will ask you the device type, go down select Network Adapters.
7. Select microsoft as manufacturer and select Microsoft Corporation.
8. Then, select Remote NDIS based Internet Sharing Device.
9. Hit next, it will say it's not safe, etc etc, proceed to install it.
confirm password please... what is password for this file please help...???
darmanto3001 said:
password not work
Click to expand...
Click to collapse
its working
Select the rndis in device manager then click on update then select manually then search for Microsoft then click on rndis based Internet sharing then install. .. u all done enjoy. .. For more details contact [email protected]
Tethering With XP-64 Pro And Remote NDIS Install
It took me about a day to figure this out and yes, some of us still use XP. (I use it for mechanical CAD work, because I can't afford to buy all new CAD proggies, which would be required, if I upgraded Windows.) Tethering now works great and I can even share the connection further using MS Internet sharing on XP, which provides the tethered Internet to machines on my wired network and wifi router without having to connect them to my Moto G4 Plus. This means I can also place whatever firewall I choose in the path and extend the wifi range (my Netgear wifi signal is more powerful than my Moto G4 Plus).
I tried two .inf files. The only one that worked was produced by cutting and pasting to an .inf file from here:
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/remote-ndis-inf-template#rndis-inf-template-for-ndis-60-windows-7-and-later
Then I had to explicitly add my Moto G4 Plus ID, as described here (remembering to enable USB tethering on my Moto G4 phone AFTER plugging it into my Windows computer):
http://karceh.blogspot.com/2012/05/how-to-usb-tether-android-phones-with.html
The rest of the install was nearly as described here in this xda-dev thread. Browse directly to the .inf file when given the chance to select the driver.
Here is my .inf file with my Moto G4 ID (you'll need to replace it with your phone's ID in the right spot, of course). Search for "Moto G4" to see where I placed my G4's ID:
Code:
; Remote NDIS template device setup file
; Copyright (c) Microsoft Corporation
;
; This is the template for the INF installation script
; for the RNDIS-over-USB host driver.
; This INF works for Windows XP SP2, Windows XP x64,
; Windows Server 2003 SP1 x86, x64, and ia64, and
; Windows Vista x86 and x64.
; This INF will work with Windows XP, Windows XP SP1,
; and Windows 2003 after applying specific hotfixes.
[Version]
Signature = "$Windows NT$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %Microsoft%
DriverVer =06/21/2006,6.0.6000.16384
;CatalogFile = device.cat
[Manufacturer]
%Microsoft% = RndisDevices,NTx86,NTamd64,NTia64
; Decoration for x86 architecture
[RndisDevices.NTx86]
%RndisDevice% = RNDIS.NT.5.1, USB\VID_xxxx&PID_yyyy
; Decoration for x64 architecture
[RndisDevices.NTamd64]
%RndisDevice% = RNDIS.NT.5.1, USB\VID_xxxx&PID_yyyy
; My Moto G4
%RndisDevice% = RNDIS.NT.5.1, USB\VID_22B8&PID_2E24
; Decoration for ia64 architecture
[RndisDevices.NTia64]
%RndisDevice% = RNDIS.NT.5.1, USB\VID_xxxx&PID_yyyy
;@@@ This is the common setting for setup
[ControlFlags]
ExcludeFromSelect=*
; DDInstall section
; References the in-build Netrndis.inf
[RNDIS.NT.5.1]
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI
BusType = 15
; NEVER REMOVE THE FOLLOWING REFERENCE FOR NETRNDIS.INF
include = netrndis.inf
needs = Usb_Rndis.ndi
AddReg = Rndis_AddReg_Vista
; DDInstal.Services section
[RNDIS.NT.5.1.Services]
include = netrndis.inf
needs = Usb_Rndis.ndi.Services
; Optional registry settings. You can modify as needed.
[RNDIS_AddReg_Vista]
HKR, NDI\params\VistaProperty, ParamDesc, 0, %Vista_Property%
HKR, NDI\params\VistaProperty, type, 0, "edit"
HKR, NDI\params\VistaProperty, LimitText, 0, "12"
HKR, NDI\params\VistaProperty, UpperCase, 0, "1"
HKR, NDI\params\VistaProperty, default, 0, " "
HKR, NDI\params\VistaProperty, optional, 0, "1"
; No sys copyfiles - the sys files are already in-build
; (part of the operating system).
; Modify these strings for your device as needed.
[Strings]
Microsoft = "Microsoft Corporation"
RndisDevice = "Remote NDIS based Device"
Vista_Property = "Optional Vista Property"
I am still getting error as the device cannot start 10..please help

Minimum pollution USB driver installation

For USB driver only installation I normally recommend the thread by SamHaLeKe. However the download link is offline again due to... that would be an endless story.
I know the USB drivers have been uploaded to other sites but I do not know how good and frequently these are maintained.
Anyway: I just decided to write this little list of instructions so everybody will be able to extract the USB drivers from the official Samsung Kies download himself as long as Samsung does not provide a download link (yes Samsung, even Intel provides “driver only downloads” ). These are the steps to follow:
0. Make sure Kies is not installed. If it is you don't need this guide
1. Download Kies from Samsung
2. Double click it to start the installation but do not go any further when you see the first dialog box looking like the first screenshot attached. Don't close the dialog box for now!
3. Use the file explorer to search for a file named “*kies*.msi” starting at or below this location: “C:\Documents and Settings\your_name\Local Settings”. I found a file named “Samsung Kies.msi” which is roughly 90 MB in size at some temporary directory. Your file may be named different or it might be located at some other place. I will call the file “Samsung Kies.msi” for the rest of this description.
4. Copy “Samsung Kies.msi” to some safe place, say “c:\kies-installer\Samsung Kies.msi”
5. Now press the cancel button in the dialog of step 2, not the next button.
6. Open a console in “c:\kies-installer” and type this: 'msiexec /a "Samsung Kies.msi" /qb TARGETDIR="c:\kies-installer\extracted"'. Don't worry, this will not really install Kies, it will perform an administrative installation which basically extracts and copies files from the installation package for later installation. You will also see a somewhat strange looking dialog similar to the one in the second attachment. This too is nothing to be worried about. The dialog will close itself.
7. The installer has copied the files to the newly created sub directory "c:\kies-installer\extracted". This directory contains a sub directory named “program files\Samsung\Kies\USB Driver” in which you will finally find a file named “SAMSUNG_USB_Driver_for_Mobile_Phones.exe”, the USB driver installation package.
8. Copy this file to a safe place and delete the entire “c:\kies-installer” directory. Again note: these files have not been 'installed' only copied to this location, so it is safe to just delete them.
9. That's it, the file “SAMSUNG_USB_Driver_for_Mobile_Phones.exe” is the USB driver installer we were looking for
I have tested the steps above on a Windows XP system for the following Kies (USB driver) versions:
2.2.0.12014 (USB driver version V1.4.103.0)
2.3.2.12054 (USB driver version V1.5.5.0)
2.3.2.12064 (USB driver version V1.5.6.0)
2.3.2.12074 (USB driver version V1.5.6.0, not changed)
2.3.2.12085 (USB driver version V1.5.9.0)
2.5.0.12094 (USB driver version V1.5.15.0)
2.5.0.12104 (USB driver version V1.5.16.0)
2.5.3.13043 (USB driver version V1.5.23.0)
2.6.1 (USB driver version V1.5.29.0)
For Windows 7 and other versions of Kies things might differ a little bit.
Hi there,
very nice Info!
Have tested this on Windows7 Prof. x64
You will find the "Samsung Kies.msi" in: C:\Users\your_name\AppData\Local\Downloaded Installations\... or in C:\Users\TobiAdmin\AppData\Local\Temp\... for me, both are the same files!
Everything else works absolutely the same way!
Thanks for your work
Thanks for the guide, was helpful in getting me started.
FYI, after step 3, you can also open Samsung Kies.msi with something like 7-Zip, extract samsung_usb_driver_for_mobil and then rename it to samsung_usb_driver_for_mobile.exe.
Likewise if you actually install Kies the USB driver .exe is in the Kies program folder .
jje

[GUIDE] Crash Course in ADB/Unlocking on WINDOWS

Just wanted to try and put together something helpful for those who are unlocking their devices who might be doing this for the first time or just are having issues.
THIS GUIDE ONLY WORKS FOR WINDOWS FOLK, SORRY! IF YOU HAPPEN TO BREAK YOUR DEVICE OR DO ANYTHING TO IT THAT PREVENTS YOU FROM USING, I AM NOT RESPONSIBLE, CAVETE LIBERUM OPUS.
ADB
Download ADB from here: http://developer.android.com/sdk/index.html
Make sure you install it where ever you are comfortable with, I tend to keep mine in my main installation (C: )
HTC Sync
Download HTC Sync here - http://www.htc.com/www/software/htc-sync-manager/
Why download HTC Sync? For the drivers. After the installation is complete you can remove HTC Sync, just not the drivers.
Appropriate Drivers
In your Program Files (x86) folder, there should be an HTC Folder, with the drivers in it.
What you are going to need to do is make sure that your device has the HTC drivers installed.
You'll need to open Control Panel ----> Hardware and Sound ----> Device Manager
Your HTC One should be under portable device or android phone, or something similar to that. If it is telling you the current drivers are up to date, you may need to disable driver signature enforcement, and that method is different between Windows 7 and 8.
You'll want to update the driver software by right clicking ----> Update Driver Software ----> Browse my computer for driver software ----> Browse...; then select the HTC Driver folder from within the HTC folder (you'll have to navigate to it)
If you need to disable driver signature:
Windows 7 - http://bit.ly/1bE0jZT
Windows 8 - http://bit.ly/1bE0mF7
Trouble Shooting ADB and Rumrunner
I am, in no way, saying that I am an expert in running rumrunner. If you can use irc and contact beaups please do. However, just in general, here are tips I think might work -
Go to "System and Security" from Control Panel and click "Allow an app through Windows Firewall." Click "Change Settings" at the top and then click "Allow another app...". Navigate to your extracted rumrunner file and select the soju.exe to be allowed through. Why do this? Because I personally rather not take down my entire firewall to allow this program to run. No offense to beaups, just doesn't seem terribly practical to me.
In your ADB installation folder, go into SDK -----> platform tools ----> Hold down left shift and right click -----> Open command window here
type in adb devices; if you are not seeing
List of devices attached
XXXXXXXXXXXXXXXXXX device (read the X's as a string of numbers which are your device)
then it isn't ready to be use rumrunner. You'll have to go into Settings -----> About Phone -----> Software Information -----> Then click 7 times on Build Number to unlock developer options. Go into "Developer Options" and enable USB Debugging.
As mentioned in Rumrunner, please run soju.exe AS ADMINISTRATOR, to avoid permission issues on computer-side.
OEM Cables are also ideal in this situation. Also make sure you downloaded the right file (.8 version versus .10)
Last but not least, IT TAKES A WHILE FOR SOJU TO RUN. BE PATIENT Your phone will reboot A LOT during the entire process. It'll take awhile, but if you run into the (.........) problems or an error because your drivers aren't installed correctly be patient.
The guide isn't perfect, but hopefully it helps. I'll add advice if it comes in.
Great guide!
Make sure to remember to do a fastboot devices check too. that is my problem adb works great fastboot is another story
Sent from my HTC6500LVW using xda app-developers app
It also hates USB3
It also hates USB 3.0, had to use my fiances laptop todo it, but very straightforward.

Access to device launched in fastboot mode connected to the USB in Windows 8.1 64-bit

Windows 8.1 64-bit can not tolerate some USB devices.
Helpful in solving this problem is an entry
Why does my USB device work on Windows 8.0 but fail on Windows 8.1 with code 43?
In brief.
In the described method, you must diagnose the USB port using the Microsoft Message Analyzer and create an entry in the registry for the device.
I made this diagnosis for HTC Desire aka A8181 aka Bravo.
Below the registry, which can merge or be used for self-creation of the registry binary value.
Code:
[FONT="Courier New"]Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\[COLOR="Red"][B]0BB4[/B][/COLOR][COLOR="YellowGreen"][B]0FFF[/B][/COLOR][COLOR="Orange"][B]0100[/B][/COLOR]]
"SkipBOSDescriptorQuery"=hex:01,00,00,00[/FONT]
Code:
[COLOR="red"][B]0BB4[/B][/COLOR] -> Vendor ID -> HTC (High Tech Computer Corp.)
[COLOR="yellowgreen"][B]0FFF[/B][/COLOR] -> Product ID -> Android Fastboot Bootloader
[COLOR="orange"][B]0100[/B][/COLOR] -> Revision Number
Source: [URL="http://www.linux-usb.org/usb.ids"]List of USB ID's[/URL]

Categories

Resources