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
Related
The latest kies update to version Kies 2.0.2.11071_128 dated 02 August 2011 don't include Samsung Apps.
Has anyone updated his/her kies on pc and observed same missing Samsung Apps Store? Could this be an
error on the part of Samsung? Or maybe the Apps store no longer will show for bada 1.2?
I tested with bada 1.2. Maybe bada 1.2 will no longer be supported (but we still have a long way to reach September )
Anyone with bada 2.0 and who has updated to Kies 2.0.2.11071_128
should please report if the the store show up when WAVE is connected to kies on pc.
It is a bug in kies for sure
i hate Samsung for these awful mistakes
remember the kies version which was able to open Samsung apps but can't install apps
Samsung is not the best software maker
Let's hope for an urgent quick update fixing this
Best Regards
I also noticed that each time that you launch kies,
the option in Memory order is always set to "Use internal memory first"
even though you have previously set it to "Use external memory first"
same here, after the update, Samsung Apps panel is not shown on Kies.
I think it is a bug on this version.
The solution
the solution for this bug is in this link :
http://www.mysamsungwave.com/index.php?topic=10092.50
For me, when my Wave with XPKG6 is connected, it works.
ozeer said:
the solution for this bug in this link :
http://www.mysamsungwave.com/index.php?topic=10092.new#new
Click to expand...
Click to collapse
on the same page i have given another solution, other than simonwill,
the trick is..
1. install the immediate previous version of kies..(previous to kies ver 2.0.2.11071_128) or whatever version u were working on..b4 updating to "2.0.2.11071_128"
2. go to run -> regedit -> HKEY_CURRENT_USER -> software -> samsung -> Kies2.0(select it)
3. in the right hand window, look for Localver, right click on it, click on modify.
4. replace the whole value with this one "2.0.2.11071_128" (without the quotes)
5. open kies again, go to samsungapps normally, it wont ask u to upgrade to newer version so SAMSUNG FOOLED
this works like a charm
can someone upload the "Astore" and "StoreLib"
Kies.Common.StoreManager.dll
files here?
Here you go kadavil : http://www.mediafire.com/?w2ywwtqhymj06pb
The problem with the latest Kies 2.0.2.11071_128 not having the Samsung Apps store is as a result of either a corrupt "AStorePlugin.dll" or a wrong value assigned to this dll. The problem is only with the "AStorePlugin.dll".
To solve this problem, simply install the latest kies (either as a fresh install or an update over existing kies instalation. Restart PC.
1. Now go to Program Files\SAMSUNG\Kies\Plugins\AStore...
(a) inside the AStore folder, replace the "AStorePlugin.dll" with the one from the download link below (or from any previous kies installation)
NOTE: ONLY REPLACE the "AStorePlugin.dll" of size approx 4,014kb.
(Don't replace the small one of size about 4kb).
3. That's all. Now you can enjoy your new Kies 2.0.2.11071_128.
http://www.megaupload.com/?d=0JNX8I3S
Thats the best solution @ spacsk
100% working!!!!!
thanks mylove90 and spacks!
Thanks a lot... Its working...
spacks said:
The problem with the latest Kies 2.0.2.11071_128 not having the Samsung Apps store is as a result of either a corrupt "AStorePlugin.dll" or a wrong value assigned to this dll. The problem is only with the "AStorePlugin.dll".
To solve this problem, simply install the latest kies (either as a fresh install or an update over existing kies instalation. Restart PC.
1. Now go to Program Files\SAMSUNG\Kies\Plugins\AStore...
(a) inside the AStore folder, replace the "AStorePlugin.dll" with the one from the download link below (or from any previous kies installation)
NOTE: ONLY REPLACE the "AStorePlugin.dll" of size approx 4,014kb.
(Don't replace the small one of size about 4kb).
3. That's all. Now you can enjoy your new Kies 2.0.2.11071_128.
http://www.megaupload.com/?d=0JNX8I3S
Click to expand...
Click to collapse
The above method works fine. But it displays the apps store with the old UI.
Another method to use the new kies and have the latest apps store UI is to modify region in registry. Do it this way.
1. From windows command, enter regedit.
2. Expand HKEY_CURRENT_USER => Software => SAMSUNG =>
3. Now double-click folder "Kies2.0" .
4. On right-hand side of window, under Name column, look for "Region" (5th from
bottom)
5. Right-click on "Region" and select "Modify". Change the current region US to yours (or change to) UK.
6. That's all. The new kies will work 100% with the latest samsung apps store UI.
NB: Please see screenshot below for ref.
i cant understand this:
"from windows command, enter regedit" how can i do that with my PC?
Thanks
pao9195 said:
i cant understand this:
"from windows command, enter regedit" how can i do that with my PC?
Thanks
Click to expand...
Click to collapse
If you use Windows 7, just click on "Start" , on the search bar that appears, write "regedit" (without quotes), and press enter. You will be promted to a "Yes" or "No" option. Click Yes to go to the registry editor.
Once the registry opens, then continue from nº 2 of the instructions above.
NB: Please with this registry edit, you don't need to replace any AStore dll. Just install the latest kies, and in registry, change region from "US" to "UK". That's all.
NB!: If you use Windows XP, you will have to enter "cmd" first at Windows Start button, then "regedit", etc. (I hope I'm correct; it's long time now I haven't used an XP machine )
Thanks spacks, that worked like magic !
Thanks spacks...
spacks said:
The above method works fine. But it displays the apps store with the old UI.
Another method to use the new kies and have the latest apps store UI is to modify region in registry. Do it this way.
1. From windows command, enter regedit.
2. Expand HKEY_CURRENT_USER => Software => SAMSUNG =>
3. Now double-click folder "Kies2.0" .
4. On right-hand side of window, under Name column, look for "Region" (5th from
bottom)
5. Right-click on "Region" and select "Modify". Change the current region US to yours (or change to) UK.
6. That's all. The new kies will work 100% with the latest samsung apps store UI.
NB: Please see screenshot below for ref.
Click to expand...
Click to collapse
Right, US has no store xD
Thank you so much
Yes, maybe the corrupt AStore.dll is wrongly installing US as region by default. Let's hope Samsung will correct this error soon to prevent innocent people from messing up their pc registry.
Thanks.
I have installed the connectivity on many machines that others have given up on!
It's EASY! Before you begin, You might also need to open my computer, click on tools, folder options, views and put checks in display contents of system folders
also put a check on show hidden files and folders. Just so that you will be able to see the necessary folders and files.
1) Un-install any other android phone connection software that might be installed on the PC.
2) Use Microsoft Update and get the PC updated to the latest available updates.
3) Install the latest Media Player available to your OS. (XP is only capable of 11) NOTHING LOWER THAN !0 WILL WORK.
The files can be downloaded from the link below.
4) Copy the 2 files in the Toshiba INF folder to your Windows/inf folder (The original ones in your system are mostly the reason for the problem)
5) Install the Kies software, and do not let it update! The newer version won't work.(Don't panic, it takes a few minutes to complete the install)
6) After you're all done, make sure you have the USB Debugging checked on your phone. (Settings/developers options)
Connect the phone to the PC using the USB cable that came with the phone.
It may take a while for the new drivers to install, and also a while to recognize the phone. Just be patient
7) If the system does not work the first time, disconnect the phone and reboot the PC.
8) Open Kies and do the Troubleshoot Connection (it has kept a record of what needs to be fixed when it tried and failed.
9) After it completes, Re connect the phone to the PC, after a while, it will make the connection!
10) After the first time it connects, you will no longer need to run the Kies software to connect to the PC.
Just connect the cable and the PC will recognize the phone..
If for some reason it loses connectivity and cannot connect again, just run the kies again and it will work like it did before.
The files you will need (except the Media Player) can be gotten here:
http://bitshare.com/files/scn15w79/Best-Way.rar.html 3/18/2013
http://www.putlocker.com/file/0D6BDDFFF311EF1C
Link added and checked as of 6/8/13
4) Copy the 2 files in the Toshiba INF folder to your Windows/inf folder (The original ones in your system are mostly the reason for the problem)
what is the windows/inf folder?
im tyring to search it but not getting any hits
thanks
mikey
on ur computer not the phone
bobolinko said:
on ur computer not the phone
Click to expand...
Click to collapse
where are the windows inf files located?
im doing a search and coming up empty
On pc..click start then computer. Now click C drive go to Windows folder open scroll down to INF folder and there you go!
Sent from my SGH-T999 using xda premium
I was advised to check this thread out in regards to my S2 lte having the same issue. That being said it hasn't worked. Can't see what I could be doing wrong. As far as i can tell the only thing that was even slight unclear is whether or not to delete the original files int he INF folder as the two files in the Toshiba folder have the same name as the ones in the INF folder. So I choose copy and replace. Was that incorrect?
AAARGHHHH the issue has now spread to my 10.1 Tablet. Nothing connects now.
bobolinko said:
4) Copy the 2 files in the Toshiba INF folder to your Windows/inf folder (The original ones in your system are mostly the reason for the problem)
Click to expand...
Click to collapse
Where is the Toshiba/inf folder located?
The Round Peg said:
Where is the Toshiba/inf folder located?
Click to expand...
Click to collapse
That would be wherever YOU downloaded it to
when you click on the download link at the end of the list, you will download it. unpack the files. Then you will be able to copy them to the ini file folder in windows.
You might also need to open my computer, click on tools, folder options, views and put checks in display contents of system folders
also put a check on show hidden files and folders.
it's is not that hard to understand if you read the steps carefully. maybe you might want to print the list out, and check off each step as you complete it. Also you would be able to reference the file as you are doing the steps.
if you skip any one of the steps, or jump around, it may not work as the steps in the procedure were deliberately done to facilitate the actions that occurr behind the scenes, and still achieve the expected results.
nurlord said:
I was advised to check this thread out in regards to my S2 lte having the same issue. That being said it hasn't worked. Can't see what I could be doing wrong. As far as i can tell the only thing that was even slight unclear is whether or not to delete the original files int he INF folder as the two files in the Toshiba folder have the same name as the ones in the INF folder. So I choose copy and replace. Was that incorrect?
Click to expand...
Click to collapse
yes
The download link in the original post is no longer valid.
Fixed Links
icelus1 said:
The download link in the original post is no longer valid.
Click to expand...
Click to collapse
Repaired and added another link in case one fails
Links are down. Please someone provide the said files.
This file does not exist, the access to the following file is limited or it has been removed due to infringement of copyright.
kaaniz said:
Links are down. Please someone provide the said files.
This file does not exist, the access to the following file is limited or it has been removed due to infringement of copyright.
Click to expand...
Click to collapse
RE-upped one and verified the other as working. 6/8/2013
this not works on my S4 ... I do all but NOT !! :crying:
Not working 29/12/2016
To establish connectivity, I would download the universal Samsung USB drivers or install Kies/SmartSwitch and use the original Samsung USB cable on a USB 2.0 port.
Can't download the files off that site, as well as I can't access my I535PP at all. I've tried everything, and at one point kies said my device wasn't supported yet it's on the list... Idk what to do...
Edit: Kies specifically says unsupported device when it goes to connect to it, and says to use smart switch but that wouldn't work either.
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.
Hi all,
(Note from OP: Can't change thread title, but if I could I would change "solved" to "proposed solution", because that's what this is: a kind of workaround.)
First, to the best of my knowledge, the Hardware ID problem when connecting the Note II to a PC via microUSB cable isn't yet solved; my apologies if it was.
I got it to work on my Rogers i317M model (like at&t) but I've no reason to think it won't work on other models.
The solution is Kies, but not in the way one might think: yes, Kies provides the solution, but to do this you won't actually be using the Kies software—just gonna borrow it a little while .
First, install Kies on your PC if it isn't already; it wasn't for me as I never use it normally. You can download it from the support pages of Samsung's website (look for a "useful software" link I think), but goo.gl/h6fwMI is a direct download link to the one I used. Note that it takes its sweet time installing, about three full minutes (which feel like 30 or so) . . . do not have your device connected to the PC during installation.
The key feature we're exploiting here is that Kies will hook your PC up with whatever it needs to have the Note II communicate via USB properly with it. Before stumbling on this method, I had the Samsung drivers installed alright, and all I was getting when connecting was the Hardware ID message, like I know many others do. Note that I did not remove the old Samsung drivers before installing Kies . . . not saying it has to be done that way, just saying that's how I did it.
Once installation is complete, close Kies completely; for me that meant popping open the Windows Task Manager (right-click the taskbar or [Ctrl] [Shift] [Esc]) and manually killing two (2) Kies processes, on top of closing the Kies app window itself of course.
Now try connecting your device with the cable . . . you will probably get a Windows AutoPlay popup . . . go into Default Programs > Autoplay Settings and you should see the phone at the very bottom of the list (Figure 1. attachment) . . . configure it to Open device to view files using Windows Explorer as in the figure.
Now when you connect your phone to your PC, Windows Explorer will pop open a file window, which is what we were looking for, and there should be no sign of the Hardware ID problem. The window that will open will look like Figure 2.—take a look, you'll see it doesn't assign the device a drive letter as expected. Instead, it will show up under Computer as its own device, bearing two "drives": Card and Phone (if there's no external SD card in your device you'll just see Phone). Click Phone and you're ready to go! (see Figure 3.).
Two further considerations:
I don't suggest uninstalling the Kies software afterward. I set about doing so (using Revo Uninstaller) to see if I would still be able to connect, and the first popup I got said "Uninstall SAMSUNG USB Driver for Mobile Phones?" That didn't sound encouraging, so I aborted it, and for now I suggest leaving Kies installed, at least until and unless someone tries it and reports back with a verdict.
As a followup to the previous point (a consolation prize, you might say :laugh, you can prevent Kies from starting up every time you boot your computer, so that, even though installed, it will be inactive and out of the way. You need a startup manager of some kind. Windows has its own somewhere—msconfig maybe—but I used the one in the Auslogics® bundle and found no less than four (4) items added by the Kies installer which I had to uncheck (see Figure 4.). I may be keeping Kies installed, but I can at least make sure it's quiet
In short:
1. Install Kies
2. Stop all Kies-related activity:
· the app itself (if running)
· two (2) processes
· four (4) lines in Startup
3. Connect phone to PC with USB cable
4. Configure Windows Autoplay to "view files" when you connect
5. Do the dance of joy
The end result is pretty much that any time you connect your device with your PC via USB cable, a window with the file contents of the device will appear, allowing you to cut/copy/paste/move files at will, at the cost of a piece of inactivated software residing on the PC.
I'd be interested to hear how it goes with others... good luck!
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.