Develop Bugs

Help! USB driver needed (for Win98)

Maybe somebody would be able to to send to me driver usb for win98 (for my SPV M2000 if this matters). Only ActiveSync does not working, my windows still needs "drivers for usb" (but I don't have CD).
My addres is simply: (nick) + @gmail.com (if somebody will send packed file must change the end on ".zi_" or something like this).

Nobody can help me ?

Try this website
http://www.usb-drivers.com/

What are you trying to do?
Active Sync?
If you want to use it as an USB Mass Storage device look here: Generic w98 mass storage device driver
Cheers

Yes i tray to run Active Sync.
When i connect PDA to PC (with Win98) i have information "new device found, drivers needed", but i must press "Cancel" because i don't have this driver :-(
When i run Active Sync - i have information "No device found on: Com 1-8, IR, USB. Check communication cable"
www.usb-drivers.com - i don't found there drivers for XDA, MDA, SPV, Qtek etc.
Generic w98 mass storage device driver - I don't have English version Windows 98, and this driver can't run.
Maybe somenoe send me this Win98 driver form CD ??? It should be no bigger file than 500K.

Active Sync installs the driver from wceusbsh.inf
In there you find
[Win9xWDMFiles]
;wceusbsh.sys
Click to expand...
Click to collapse
Perhaps remove the ; from that line?
Do you know your usb pnp id?
[HTC]
%USB\Vid_0BB4&Pid_00CE.DeviceDesc% = Host_Inst, USB\Vid_0BB4&Pid_00CE
%USB\Vid_0BB4&Pid_0A01.DeviceDesc% = Host_Inst, USB\Vid_0BB4&Pid_0A01
Click to expand...
Click to collapse
If you know your usb pnp id you can add a modified line from that section
to the wceusbsh.inf file.
You can also comment out (; at the start of the line) this line
[ControlFlags]
ExcludeFromSelect = *
becomes
[ControlFlags]
;ExcludeFromSelect = *
and then manualy select a HTC device.
Cheers

BIG THX
i have only remove ";" (comment sign) from this sction:
[Win9xWDMFiles]
;wceusbsh.sys
Click to expand...
Click to collapse
...and ewerything works
(in [HTC] section i already have had some about 50 devices)

What we have tried and where to go from here

Ok, so we haven't had quite as much luck yet as we would have liked, but I think as we continue to try out different approaches we will have some luck. I think it might be beneficial for us to have a an overview of what has been tried and what has been attempted thus far. So here is a list of things people have tried (please feel free to add anything that I may have left out or accidentally overlooked).
Registry Edit to access Zune storage
I believe this was the first approach that people took to gaining access to the KIN, and this link provides a great walkthrough.​
Bitpim
This is a pretty good overview of what has been attempted through Bitpim. Recently some have even tried using some other software, namely CDMA Workshop, (Look at the last post of the page.) I would suggest that we also try a couple more:
RevSkills
UniCDMA​
Nvidia Tegra Flash
I forgot this when I first posted.​
OpenZDK
This was another potential since much of the hardware, namely the processor is the same on both the kin and zune.​
Looking for clues in the log files
To put it simply in the hidden menu there is an option to have system log s emailed to you. I tried reading through some and noticed some of the events and files that the KIN uses, but have not had any luck yet.​
FTP
This link is the same as the link for the Log Files above.​
Export/Import in hidden Menu
Once again, the linked used here is the same one for Log Files and FTP.​
Please add anything that I may have left out, either different approaches or links to helpful information. I haven't had a chance to tinker with RevSkills too much yet, but it looks real promising.

Ah, we mods like these threads. Keep it up. Stickied.

The hidden import feature becomes active if you create a contact while using
qpst. It imports but I don't know where it put that info.
Interesting to note is that None of my phone entered contacts show up in qpst.
It is like that directory is mapped to some other place.
I was able to create directories and added txt files using qpst that remain even after power cycling the phone. I haven't found any of this using the phone yet.

I am getting the same results as you when I use the EFS manager and service programming. I can create files and make changes and they last after reboot.
I find it odd that when I export contacts from the hidden menu the file is visible in windows explorer if I have edited the registry as noted in the first post. I find this odd because everything else that is visible on the device using this method is related to the Zune, i.e. photos, music, and videos.

I have started looking back at some of the log files that I had the phone email me through the hidden menu and I have found some AT commands for the phone along with some other information. Here is a little bit of one file that I just started sorting through. The formatting isn't perfect because the log files have a lot of unreadable characters, but I have bolded files and commands. I also left everything in the case (upper and lower) as I found it in the file. The name of this file is:
MICROSOFT-PMX-DEBUGSTRINGPROVIDER-CHANNEL.02.clg
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_PRE_UPDATE
MPM_BB_USB_DRIVER_LOAD_UPDATE_EVENT, dwWaitTime: -1
MPM_Util:USB Client 1 has been Loaded
MPM_Util:USB Client 2 has been !UnLoaded!
CDMA Radio Updeate: Text stored version : v0.4.727
CDMA Radio Update:Registry Key version: v0.4.727
CDMA Radio Update: Current Modem version: v0.4.727
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_PRE_UPDATE
MPM_MainsSmThread
MPM_BB_UPDATE_REQ_EVENT - No modem update is needed
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_END_RSTISR_REQ_EVENT, dwWaitTime: -1
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_END_RSTISR_REQ_EVENT MODEM RESET ISR Init Completed.
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_POWER_ON_REQ_EVENT, dwWaitTime: -1
RILNDIS: GetPacketInterface Initialize = c117d634
Shutdown = c117c4e4
RILDrv : i : Accumulated response (1) : <cr><lf>
IOPTMODE: 6 <cr><lf>
RILDrv : i : Sending cmd: ATV0E0X3 <cr>
RILDrv : t : LoadEriData : Opening file
\RoamingIndicator\eri.bin
RILDrv : i : Accumulated response (1) : ATV0E0X3 <cr> 0 <cr>
RILDrv : t : LoadEriData:
\RoamingIndicator\eri.bin not exist. Err 0x00000002
RILDrv : i : Sending cmd:
AT+cstt=0, 1, 75, 85, 95, 100 <cr>
RILDrv : t : LoadEriData: Opening file
\Windows\eri.bin
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv : i : Sending cmd :
AT+CSTT=1,1,18,22,26,30 <cr>
PMIC Boot cookie: rb7262h
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv : i : Sending cmd :
AT+CSQT=1<cr>
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv:i: Sending cmd:
AT+GMI; +GMM; +GMR; +CKEYPAD?25<cr>
RILDrv:i: Accumulated response: +CKEYPAD:25
RILDrv:i: Accumulated response (2): equesting :
IUSBON, USBST, New PLMST, timestamp, 10, 2,2944 <cr><lf>
RILDrv:i:Accumulated response(1): +IQMIREADY <cr><lf>
+IUSBON<cr><lf>+IECHO: Requesting:IUSBON, USBST,
New PLMST, timestamp, 10, 2, 2944 <cr><lf>
RILDrv:i: ParseNotificationOEM: +IQMIREADY: SetEvent for QMI Init
RILDrv:i: Accumulated response(1): +IUSBON<cr><lf> +IECHO:
Requesting: IUSBON, USBST, New PLMST, timestamp, 10, 2, 2944<cr><lf>
RILDrv:i: Accumulated response(1): +IECHO:
Requesting: IUSBON, USBST, New PLMST, timestamp, 10, 2, 2944<cr><lf>
RilDrv:arseGetEquipmentInfo Modem Version: 727

I found out one more thing, if you use the s+l+power comination when the phone is powered off and connected to the computer another USB device is found. I just found this thanks to conflipper's early work We will have to come up with some sort of driver for this now.
Here is the name of the device and the hardware IDs
Microsoft Pink Bootstrap
USB\VID_045E&PID_2345&REV_0000
USB\VID_045E&PID_2345

I also just found this hardware id when having the computer turned off and plugged into the pc. When I hold down u+s+b+power Windows finds another device with the following name and hardware IDs (According to what I have found online this VID is Nvidia.) So this might be where we can use the tegra chipset stuff.
APX
USB\VID_0955&PID_7416&REV_0103
USB\VID_0955&PID_7416

Thought I would also add that my phone is currently unusable, but on the positive side, I wouldn't found those other two usb hardware IDs if this hadn't happened. Sidenote, I was using QPST Configuration program, and I right clicked on the my phone in the active phones tab. I then clicked on "Configure service to port mapping..." and added one property (unforturnately, I can no longer go back to the window because the program doesn't recognize my phone now). At this point, my phone rebooted and is now stuck trying to boot up.
I don't think it is completely bricked, but I fear that until we pull a rom it is probably useless because it is stuck in a constant cycle trying to reboot. The only way to stop this is to remove the battery. I have since tried using the various key combinations provided by conflipper and have found that the bootstrapper combination (s+l+power) would probably work if we had a rom. I then tried the hard reset combination (c+b+power) which initially looks like it might work but then it gets stuck in the cycle of rebooting.
I am going to continue working on it, hoping that somehow now that I might have some extra sort of access to hardware, but I am afraid my contributions may be limited until we are able to pull a rom.

Sorry to hear that. There has to be a way of getting it out of the loop.

RevSkills Hardware Log.
Diag Port Supported Command List.
7E - TRS FRM MSG supported.
5A - CHECK AKEY supported.
59 - EFS CMD supported.
58 - GET IS95B supported.
57 - SET MAX SUP CH supported.
56 - SUP WALSH CODES supported.
55 - FER INFO supported.
51 - GET FEATURES supported.
49 - READ PRL supported.
47 - UNKNOWN unknown response:
45 - GET CDMA RSSI unknown response:
44 - CHANGE SERIAL MODE unknown response:
43 - GET PARAMETER unknown response:
42 - UNKNOWN unknown response:
40 - SET PILOTS unknown response:
3F - GET STATE unknown response:
3E - UNKNOWN unknown response:
3D - CONF SLEEP unknown response:
3C - GET PACKET SEQNO unknown response:
22 - DISPLAY EMU supported.
04 - PEEK DWORD supported.
03 - PEEK WORD supported.
02 - PEEK BYTE supported.
01 - Show ESN supported.
00 - Version Info supported.
Click to expand...
Click to collapse
(the phone rebooted many times while doing this test, hence the unknown responses).
I tested more of the options provided by the free version of Revskills and it was kind of funny to see how the keyboard emulator worked, but only for numbers.
After all the reboots and so, i got some hex descriptions for errors in a new folder, called Err. Uploaded a new screenshot from that folder contents.
Easy CDMA just lets you browse the filesystem we already know.... not so much fun.
Little update.
You seem to be able to enter the recovery mode holding the U S B + power option but, as i tried right now, also using "Volume -" + power as stated for other tegra devices. Can't check if that loads ok on the computer, as i dont have the usb cable here right now.

OOPS I made a mistake. I am not seeing anything using windows 7 using u+S+B and power up. Should I disable zune, change registry for zune back to normal etc??

You shouldn't have to because the device has a different hardware id, so the drivers installed for the zune portion aren't applicable. Try turning your phone off, plugging in the usb cable and then using the key combinations. If the new hardware message box doesn't appear, you should still see an unkown device in device manager.
Also you have to hold the u+s+b+power for a few seconds before it will be recognized. When I have done this the screen stays blank on my phone and the only way I know it is working is through Windows.

Using Windows 7 OS. I had to uninstall the zune driver located in portable devices in the device manager then it found new APX device and i was able to point to the NVIDIA driver. Tried ruining the phone (Flashing android to it) as in another thread but it also got stuck on the flashing prompt. Restarted phone normally and the windows found another device and loaded the zune drivers back.
Incidently, holding the volume down and power on does the same as the U+S+B+Power and is easier on the fingers.
Thanks and keep up the great work.

I again may have spoken to soon. I cannot duplicate the above scenario anymore.
I also can no longer transfer pictures taken with my phone on to my pc. I can add pictures to the phone from pc and back but not the ones taken with the camera. Originally I could with zune software. The folders for uploaded pictures are different then the ones taken with the phone. I really think that I screwed something in the phone up by playing with qpst and others.

I'm not sure about what you did there, but in my testing & curiosity purposes trials, i wasnt able to alter the device (do a write to memory), so i doubt that qpst or the others did it for you.
Also, according to coinflipper notes, the kin has several layers, including the SBL that is the one operating with the os directly (the "Ms Pink bootstrap" device), not the recovery mode, which basically put us handling a modem....
I'm trying some things, but no results yet... gonna take some time....

I have changed the USB password and added contacts (somewhere) while writing to the device using qpst. I changed the password to 000001. Is this a different part of memory I am fooling with?
Thanks

I am not sure. I have no previous experience with any phone deving nor Qualcomm tools. Just pointed what coinflipper said.
I said "basically a modem", cause you got diag(nostics) mode within a com port, and some users (in other posts) showed logs with AT commands.
I'm working with some tools to connect to the device, but using the driver we all got (zune software). Not promising anything, just peeking around some tests.
@mcdietz
Here I pasted a public output of the linux command "lsusb -vv" (ultraverbose) where Kin (factory default settings) values are.
http://pastebin.com/rZscb9wz
Is useful for usb access to the kin. Use at will.

I have been testing usb connections to the kin devices (the ones we used in this forum) and i checked this:
Kin mode (normal Zune mode):
- Using MTP protocol:
-- You can browse files/folders/track related to Zune values using the lib-mtp tools in the system you like.
-- You can format the device (zune related folders) & delete zune files using the lib-mtp tools.
-- You can't download files from the device using the lib-mtp tools (kin doesn't allow you to)
-- You can't upload files to the device using the lib-mtp tools (kin doesn't allow you to)
- Using raw USB:
-- You can Write & Read values to the device (Kin VID 0x045e, PID 0x0641). Protocol allowed: MTP
Click to expand...
Click to collapse
Of course, Zune software does use this mode and is allowed to write to the filesystem. But that's because before doing so, it uses MTP protocol values to send and receive crypto values based on JANUS from Microsoft (Microsoft DRM for Mobile Devices) and after crypto relationships, the usb commands enable the "Connected" window at the Kin.
Capturing and replaying this values over usb does not work (ever) and does not work for the kin (had to try), so no go-go from here. Also, we cannot know if it would be able (dreaming after bypassing the DRM) to go outside the pictures/music/etc folders.
On the other hand, MTP tools reports that our little friend is able to reproduce the following files:
Firmware file
MediaCard
Abstract Playlist file
Abstract Album file
JPEG file
Microsoft Windows Media Video
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
MPEG-4 Part 14 Container Format (Audio Emphasis)
Microsoft Advanced Systems Format
Microsoft Windows Media Audio
ISO MPEG-1 Audio Layer 3
Click to expand...
Click to collapse
Where firmware is strange and good but the question is... how to upload the firmwares files (you can get zune firmwares from the net) to the zune software on the device (and run them)?.
It's more interesting when you notice that firmwares contain "Zboot.bin" which is "Tegra device bootloader" but, sadly, doesnt work with nvflash because of what I said below. Those updates are WinCE updates too...
APX mode (nvidia "flashing" mode), with or without Nvidia driver.
- Using nvflash
-- You can't start flashing due to writing to usb error
-- Following attemps block the nvflash and device access.
- Using raw USB:
-- You can't Write or Read values to the device (APX VID 0x0955, PID 0x7416). Protocol allowed: None
Click to expand...
Click to collapse
This matches the post where coinflipper told us that you cannot dump the rom image.
Microsoft Pink Bootstrap (No driver):
- Using raw USB:
-- You can Write & Read values to the device (Kin VID 0x045e, PID 0x2345). Protocol allowed: Unknown
-- Phone answers "01" to all the write requests i did (from "00" to "FF").
Click to expand...
Click to collapse

markspace. com/kin/
Here's some software that was developed for it, but I'm guessing it is only client end?
I'm not allowed to link, so assemble the spaces yourself please

The link for the download (direct) , being for Mac(only) is:
http://www.markspace.com/kin/download.php
But you must register to get an activation code from the main page (posted by shlhu). It will need internet access to activate the software during installation and reboot after it.
Requires Itunes (for audio sync), Iphoto (for image, also have started it once), and Quicktime (for video).
I tested it with a fresh installed Snow Leopard and i can say that it works. I dunno how it does (without zune installed), but it works.
Unfortunately, i wasnt able to analyze the usb transmission there, so i cant compare with the windows one. If it can skip the JANUS drm, then we may have a chance. If it is the same process as windows... we are done... lol.

[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

ADB drivers for ARC [solved]

hey guys I can't seem to get adb working on my arc, I think it is a driver issue but after reinstalling them adb still shows device not found, can anyone tell me wich drivers are working correct.
These is my driver at the moment :
==================================================
Device Name : Port_#0001.Hub_#0005
Description : Sony Ericsson sa0102 ADB Interface Driver
Device Type : Vendor Specific
Connected : No
Safe To Unplug : No
Disabled : No
USB Hub : No
Drive Letter :
Serial Number : CB5A1E72ER&ZLP
Created Date : 19-6-2011 22:41:52
Last Plug/Unplug Date: 20-6-2011 17:51:18
VendorID : 0fce
ProductID : 0dde
Firmware Revision : 1.00
USB Class : ff
USB SubClass : 42
USB Protocol : 03
Hub / Port :
Computer Name :
Vendor Name :
Product Name :
ParentId Prefix :
Service Name : WinUSB
Service Description: Sony Ericsson sa0102 ADB Interface
Driver Filename : WinUsb.sys
Device Class : sa0102AdbDeviceClass
Device Mfg : @oem27.inf,%providername%;Sony Ericsson
Power :
Driver Description: Sony Ericsson sa0102 ADB Interface Driver
Driver Version : 2.0.10.20010
Instance ID : USB\VID_0FCE&PID_0DDE\CB5A1E72ER&ZLP
==================================================
thanks in advance

I wouldn't bother debugging.
Just install both PC Companion (http://www.sonyericsson.com/cws/support/softwaredownloads/detailed/pccompanion/xperiaarc?cc=gb&lc=en) and Update Service (http://www.sonyericsson.com/cws/sup.../detailed/updateservice/xperiaarc?cc=gb&lc=en).

I have them installed and then I get this driver but no luck at all, I also tried reinstalling ADB but no luck either

These are the drivers i used (win7/32 bit) and they work well. Honestly, i got no clue where i got them from, SE site?
You could give them a try.
Hope it works out for you
edit: just saw they are probably the same as you already have, not much help i guess, sorry!

tried them but no luck indeed, thanks anyway

Too bad, you could try installing droid explorer and let it set up the sdk for you
Sent from my Arc

I try with:
in cmd, type
Code:
shutdown -o -r -t 0
and when the pc reboot, choose "disable driver signing". Then try to install the driver from Flashtool-drivers.exe file and magically it works!

Kedacom driver possible permanent fix

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.