Just thought I'd just have a brief rant. It has taken me days (or actually nights, a fella's gotta work, too) to restore my Win XP system and now I'm having a really big problem with the drivers for my Samsung SCH-I515 VZW GNex. Maybe it's because I let my new install of Win XP go up to SP3? Damn. Why can't we have another Motorola phone on this level?
With the A855, the drivers were simple as all heck. Just one file and done. Not a huge 'trial and error' thing like we have with Samsuck.
I'm running virtual Windows on a Linux box here at work and no about of coaxing has ever gotten the phone to connect to this computer. I connect my iPad and it all works. Bugs me that Apple can do what Samsung and Android cannot.
Well, all of them at first. The last time (and this time) I just want to get the MTP working first.
Used the "SAMSUNG_USB_Driver_for_Mobile_Phones_1.4.8.0.exe" first and got nothing to install, just instant failure whether I select automatic or manually found the directory. Cleaned drivers, reboot.
Then tried the "Naked Samsung 1.7.zip", selected manual location, instant failure. Remembered that they were more for adb and fastboot. Cleaned drivers and reboot Tried Wug's latest "NRT_v1.6.2.sfx.exe" it wouldn't install any thing, no matter how many different methods I used, and yes I cleaned the drivers and rebooted between every try. That's no surprise, last time I used Wug's I had to install the drivers myself anyways.
Finally went to junefabrics myself instead of via Wug's and got the adb drivers to supposedly install.
Gave up and wrote this post before I threw my PC and phone out the window.
Well, as we all know YMMV. Here is my personal victory on my Win XP Pro SP3 box:
After cleaning all previous drivers of course (the readers _might_ be able to use this from scratch), I installed this file first:
Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
I just noticed that the spell checker found that in the above named file there is "Moblie" in it instead of "Mobile". I think just for kicks I will leave it alone, since that is just the way I downloaded it and just in case it would corrupt the file.
which can be found in my 'Samsung i515 files' link in my sig. Once installed, I plugged my phone in and everything went very smoothly and next thing I knew, the XP window popped up to allow me access to my devices 'virtual' sdcard.
But to make sure all else was well, I rebooted my VZW GNex via the OS (I'm on Sourcery) into bootloader mode and plugged it into my PC. Then when prompted for more drivers, I selected the 'let me pick the location' option and pointed it to where I had extracted the 'naked drivers' file(s) to. My PC did the install again. Everything went just fine, at the end it said "unable to start device" so after unplugging from my PC I found I did have to do a battery pull.
But once I put the all the required adb.exe and associated .dll files and fastboot.exe in my c:\android folder, add that folder to my PATH variable, I rebooted my PC. Then I plugged in my phone, canceled the MTP window, open a command prompt and then entered the usual commands, I found out that everything was golden.
The usual commands:
Code:
adb devices
[B]check[/B][I]-gave me a number signifying success[/I]
adb reboot bootloader
[B]check[/B][I]-booted into bootloader/fastboot mode[/I]
fastboot devices
[B]check[/B][I]-again returned a number signifying success[/I]
fastboot reboot
[B]check[/B][I]-rebooted my device just fine[/I]
So, I reckon I will have to edit the title of this thread . . . . . .
So weird... why does windows update not work for anyone else??? That's the only way I could get my phone working on windows xp and now on windows 7. Just plug the phone in via usb and launch windows update... it saw I had a device that needed drivers... MTP/ADB... however, fastboot drivers I needed from the google android sdk manager...
I will add that I may have taken the long way around the barn to get them to work this time. I was prompted with the option to let windows update find my drivers, but for some reason I didn't go that route. I might have saved myself allot of grief.
iirc... i launched windows update to get drivers with the phone connected in several different modes:
1. MTP - with usb debugging on and off
2. PTP - with usb debugging on and off
3. Recovery
4. Fastboot (but I don't think windows had the fastboot driver, that came form google android sdk manager)
I can't remember if usb debugging being on or off made a difference, and I am almost positive that windows update couldn't find the fastboot driver, but I can't remember clearly if there was any driver difference when in recovery mode (I don't think you can push or pull anything to or from the phone in recovery.
Of course, I don't know if already having other drivers installed affects this process.
btw... the dirvers I got form windows update were branded as samsung. I can't get the driver versions right now cuz my phone isn't accessible, but can post them later if anyone is interested...
Edit: Also when rebooting my phone while connected via usb, I get some weird OMAP device recognized but can't install drivers notification in windows. Not sure if there is anything to do there... (I'm windows 7 pro x64, and was windows xp pro before this and used the same driver install process). Also, note... that you have to launch windows update manually, as I don't think going through "let windows update find the drivers" works. And the drivers might be listed under optional updates.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
