Related
I previously rooted my phone without difficulty. Using titanium backup and an number of other apps that required superuser/root acess. I am now trying to flash a Froyo rom. I had upgraded the home PC to a win 7 Pro (64 bit) machine and for some reason I can not get USB drivers to work. I have download drivers from several different threads. SOme fail to load while others seem to install. The Fascinate is recognized but not the modem and I can not get odin to see the device in software download mode.
Any thoughts?
Your best test of whether drivers are installed properly is to install adb and do 'adb devices'. If one shows up in the list you are installed correctly.
You may have an incorrect driver installed. The best place to download these is Samsung directly. If all else fails you can try a different computer and/or heimdall instead of odin.
Swyped w/ XDA App. A clean tie attracts the soup of the day.
get the drivers from samsung, or one of the noob threads, and be sure u mount then first go to setting/applications, make sure unknown sources is checks, and then go to development and make sure usb debugging is checked, then plug it in, and on ur phone u should get an option in notification bar that says transfer files.. click on it.. and then click mount.. n try again.. u should have to do this at least once on every phone to get the drivers properly installed.
I'm having trouble rooting after pulling the oTA this morning. I tried fourdifferent methods, all of which have worked before with leaks as well as with a side loaded install (different Maxx). Put USB debiggin on and tried each of these both as mass storage and MTP:
Matt's Utility 1.7
ROOT-ICS Exploit (can't find the link in dev right now)
Eternity Project's Method: http://forum.xda-developers.com/showthread.php?t=1710871
Doomlord's Method: http://forum.xda-developers.com/showthread.php?t=1341578
In all cases, the daemons just wait for the device - they never see it. In mass storage mode, I'm seeing the drive pops up on Windows so I know I'm connecting using the stock USB cord.
Any suggestions?
I'd be interested in knowing as well...
Sent from my DROID RAZR using xda app-developers app
For the Eternity Project method, you have to enable Mock Locations under developer options (and be in MTP mode), not just USB debugging.
seanzol said:
For the Eternity Project method, you have to enable Mock Locations under developer options (and be in MTP mode), not just USB debugging.
Click to expand...
Click to collapse
Yes, went back and tried that. Thanks. Still no luck though. Can't figure it out. It's like the scripts aren't able to find the phone. I can't imagine that me and soopafly are the only ones dealing with this since the OTA. Are there others out there that haven't been able to re-root?
jeff_roey said:
Yes, went back and tried that. Thanks. Still no luck though. Can't figure it out. It's like the scripts aren't able to find the phone. I can't imagine that me and soopafly are the only ones dealing with this since the OTA. Are there others out there that haven't been able to re-root?
Click to expand...
Click to collapse
Hi!
Take a look on others users problems they faced in eternityproject easyrootics.
You may face problems with other devices drivers like htc sync, kies, motocast... disable those and check you got adb working by typing
Code:
adb devices
I your root folder from windows terminal.
cheers
did you make sure you have the correct drivers installed? Not just plugging it in to USB and windows says drivers are installed.. that's not it. You have to make sure you install the correct 32 or 64 bit drivers (included in "Matt's Utility). Extract them, and double click to run the installation. Then try Matt's utility again.
I have only used M's U, not the other methods on both a 32 bit computer, and a 64 bit puter and haven't had any problems whatsoever. Good luck.
Edit: Just thought of this as I was re-reading the thread, try a different USB port. Some of my other USB stuff only works in the port it was installed in. Also, I'm sure you know, but to find out if you're 32 or 64 bit, go to "start" right click on "my computer", then properties. Install the drivers that are included in the extracted Matt's Utility 1.7 folder. Make sure USB debugging is enabled, USB mass storage on your phone. It'll re-boot 3-4 times during the rooting process.
jeff_roey said:
I'm having trouble rooting after pulling the oTA this morning. I tried fourdifferent methods, all of which have worked before with leaks as well as with a side loaded install (different Maxx). Put USB debiggin on and tried each of these both as mass storage and MTP:
Matt's Utility 1.7
ROOT-ICS Exploit (can't find the link in dev right now)
Eternity Project's Method: http://forum.xda-developers.com/showthread.php?t=1710871
Doomlord's Method: http://forum.xda-developers.com/showthread.php?t=1341578
In all cases, the daemons just wait for the device - they never see it. In mass storage mode, I'm seeing the drive pops up on Windows so I know I'm connecting using the stock USB cord.
Any suggestions?
Click to expand...
Click to collapse
Did you unzip Matt's utility into a new folder?
Go to my thread op and read the instructions
Cheers
Sent from my XT910 using xda premium
I had the same issue when I side loaded. Drivers were updated and all was well. Try plugging the phone in in charge only mode. I was complicating the process by trying to do it in fastboot. I was informed to just plug it in, hit 3 and let Matt's utility do it's thing. And it did.
maybe his link will help.
http://forum.xda-developers.com/showthread.php?t=1589107
newowner said:
maybe his link will help.
http://forum.xda-developers.com/showthread.php?t=1589107
Click to expand...
Click to collapse
Setting my USB mode to connect as a camera (PTP) did it!
I had the Moto Drivers from Matt's Utility 1.7 already installed (driver ver 5.7.0) and based on advice from other posts in this string, I went ahead and uninstalled them and reinstalled them just to be safe. Root attempts after doing that using the methods I discussed in my OP still were unsuccessful.
After seeing newowner's post, I went ahead and chose camera mode for the USB Computer Connection (settings -> storage -> press the menu key and choose Camera (PTP) and windows installed additional devices: USB Composite Device, DROID RAZR, and Mot Composite ADB Interface. I'm guessing the ADB Interface on was the one I was missing before.
Okay, I'm rooted and I'm heading back through this string with my bag O'Thanks to all of you.
Glad to assist.
Thanks for following up with your progress.
ICS is a little different!
nothing worked for me...tried camera mode tried media mode, tried different computers and reinstalling and uninstalling....bah.
I ended up doing a factory reset and everything was fine after. Boo...couldn't TB it beforehand though..
I recently bought the Motorola Droid RAZR and when I powered up the phone, I received a notification to update to System Version 6.16.211.XT912.Verizon.en.US
I agreed and the phone updated. I notice that I am now on Android 4.0.4.
I am trying to root the phone, but when I connect it to my PC, There is no Motorola ADB driver installed. All my drivers are up to date and I have tried this on multiple computers but to no avail. I also have the Android SDK installed.
What I have noticed is that when I connect my phone with USB debugging checked, the USB Networking driver is installed. Typically its the ADB driver that's installed but not in this case, so when I type in ADB devices my phone is not listed.
Anyone else have this problem? Any help would be much appreciated. Please let me know if you need any information and I'll be happy to provide it.
Thank you.
Same here...
I'm seeing the same thing. I've tried all combinations of settings on the phone, PC, Mac, Motocast Drivers, etc. No luck.
New Driver?
I noticed some new Windows drivers were released today on Motorola's dev site. I'm on my Mac today, so I can't give it a try myself.
This forum is blocking me from posting URLs (t00 n00b). developerdotmotoroladotcomslashtoolsslashusb_drivers
No luck...
That didn't work... The problem is that when I switch the phone from Mass Storage to MTP (Media Device), it installs Motorola Networking Drivers... I was expecting it to install the Motorola Composite ADB Interface Drivers....
Maybe an older version of the drivers would help? Not sure...
Fix Found
greatguitartist said:
That didn't work... The problem is that when I switch the phone from Mass Storage to MTP (Media Device), it installs Motorola Networking Drivers... I was expecting it to install the Motorola Composite ADB Interface Drivers....
Maybe an older version of the drivers would help? Not sure...
Click to expand...
Click to collapse
So after all my attempts at installing the ADB Interface failed, I performed the following steps (although a little grudgingly... lol)
1. a factory reset on my phone (currently on ICS 4.0.4).
2. Uninstalled ALL motorola drivers from my PC and installed the one that came with mattlgroff's DroidRazr Utility 1.7
After this, I turned on USB Debugging and connected the phone to my PC and voila! it worked. Even though the USB option was set as Mass Storage, It still installed the ADB Drivers. I set the USB Option to MTP and was able to successfully root my phone using the utility.
Hope this helps.
FYI - If you'd like to take a backup of your text messages then you can get the SMS BackupRestore app from the play store
greatguitartist said:
2. Uninstalled ALL motorola drivers from my PC and installed the one that came with mattlgroff's DroidRazr Utility 1.7
Click to expand...
Click to collapse
I think this is what got it working for you. Windows sometimes won't install USB device drivers if it thinks it's already been attempted.
This is a HUGE problem that I spent the last 12 hours researching how to fix. Instead of typing an essay on how to fix it, I made a blog post that outlines how to fix this problem. The blog post is here: Fix Adb Droid Razr Problems.
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
You are the man! Thanks for posting this!
littlewierdo said:
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Click to expand...
Click to collapse
Didn't work. I get caught in an endless loop where it keeps asking me to uninstall the previous version.
What do you mean "edit the KiesVersion.txt"?
bigmout said:
Didn't work. I get caught in an endless loop where it keeps asking me to uninstall the previous version.
What do you mean "edit the KiesVersion.txt"?
Click to expand...
Click to collapse
Ok, what you need to do is copy and paste the download link into a new tab in your browser. This should automatically give you a download dialog box (no need to browse a website). Download the app, its 90 megabytes and when it is done downloading, run it. Follow the on screen prompts.
This DOES work, I know, I did it on three different machines, all running Vista, XP, and Win7.
Alternatively, you can browse to where Kies is installed (C:\Program Files\SAMSUNG\Kies) and look for a file called KiesVersion.txt. Open this in Notepad and you will see one line at the top. Copy and paste the version number REPLACING whatever version is showing:
2.3.2.12064_9
(So you should have just one line showing the version number above).
Save and exit.
Note, if you choose the KiesVersion.txt method, Kies will not update correctly which is why I strongly recommend doing the first method first.
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
Thanks man. Your method worked for me!:good:
littlewierdo said:
Ok, what you need to do is copy and paste the download link into a new tab in your browser. This should automatically give you a download dialog box (no need to browse a website). Download the app, its 90 megabytes and when it is done downloading, run it. Follow the on screen prompts.
Click to expand...
Click to collapse
Yeah, I did all that. I downloaded the installer and clicked on it. It started installing, then asked me if I wanted to uninstall the old version of Kies. I said yes, and it started uninstalling.
And... that's as far as I can get. After that, it loops back and keeps asking me if I want to uninstall the old version of Kies.
littlewierdo said:
Alternatively, you can browse to where Kies is installed (C:\Program Files\SAMSUNG\Kies) and look for a file called KiesVersion.txt. Open this in Notepad and you will see one line at the top. Copy and paste the version number REPLACING whatever version is showing:
2.3.2.12064_9
(So you should have just one line showing the version number above).
Save and exit.
Note, if you choose the KiesVersion.txt method, Kies will not update correctly which is why I strongly recommend doing the first method first.
Click to expand...
Click to collapse
I'll try this -- thanks.
bigmout said:
Yeah, I did all that. I downloaded the installer and clicked on it. It started installing, then asked me if I wanted to uninstall the old version of Kies. I said yes, and it started uninstalling.
And... that's as far as I can get. After that, it loops back and keeps asking me if I want to uninstall the old version of Kies.
I'll try this -- thanks.
Click to expand...
Click to collapse
Maybe try uninstalling the version you have before you install the one I posted. Might be a version problem (my version that I had installed might be newer/older than yours).
Thx...i finally got it working
Sent from my SAMSUNG-SGH-I717 using xda premium
FINALLY!!!!!! Thank you so much! Downloading the newest version you posted finally got rid of the infinite updating issue plaguing me.
BTW I uninstalled the old version first before installing the new one since im seeing issues with replacing also
Sent from my Galaxy Nexus using Tapatalk 2
29% about 40 mins way to slow to download.
Edit: Received a timeout error damn!!!!!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Thank you for the debugging tip! This worked when I used it regularly. However, as soon as I went into download mode, it started the infinite connecting again! Any idea what is up with that?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
My phone still won't connect
Sent from my SAMSUNG-SGH-I717 using xda premium
whittakerh said:
Thank you for the debugging tip! This worked when I used it regularly. However, as soon as I went into download mode, it started the infinite connecting again! Any idea what is up with that?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
It has to do with the bizarre way Windows handles drivers.
EVERY phone state has to have a different 'driver' installed, although technically, it is using the same driver for each phone state..
The Note actually has five states, Download mode (this is the mode you would put your phone into to 'Odin' anything to it), Recovery mode (Clockwork recovery menu), Debugging mode (turn on USB Debugging) - also known as ADB mode, Mass Storage, and Wifi Direct (useful for connecting to your PC's files or public files on your phone using your PC - requires the PC to have wireless capability). Due to the way plug and play works, any device connected to your PC must put out a 'ping' to tell the OS what it is (a device name). Samsung has opted to really confuse everything by reporting a different device name for all these different states rather than doing what most devices do, a recovery mode and a mass storage mode (two states instead of the 5 Samsung is using).
Installing the samsung note driver via kies is sufficient to cover all the different states (windows just duplicates the driver for each new state it has not detected previously) but in order to cover every state the phone can possibly be in, you have to plug in the phone while the phone is in that state (ie. plugging it in with USB debugging on will install the drivers for ADB mode). One other note, just in case you are getting the brilliant idea to go ahead and -pre-install all of these different states, it has to be done for each USB port (each state) and Windows tends to remove unused drivers after a short period of time (if you havent put your phone in download mode and plugged in to your PC in awhile, chances are, Windows will have to reinstall the driver for this state again). This is why in the instructions I listed, I explain putting the phone into mass storage mode and then back into ADB mode - this forces windows to install the drivers for each state.
For those still having trouble with this, reboot your PC and try the instructions again. Pay very close attention to the system tray (the icons by your clock in the lower right corner - typically unless you moved your start menu).
MAKE SURE that windows FINISHES installing the driver for mass storage BEFORE you switch to ADB mode or you will have problems. BE PATIENT! Put your phone in mass storage and go get a coffee, do a cross word puzzle, take a shower, whatever. It takes anywhere between 30 seconds to 5 minutes to install the driver and if you interrupt the process, things become wonky until you reboot.
There will be an icon by the clock that is animated while the driver is installing (click it and it will tell you it is installing the driver). When it isnt animated, clicking it will tell you that windows finished installing the driver. DONT RELY ON THE ANIMATION! Click the icon and be sure it has installed.
Also, you cannot have Kies running while Windows is installing the driver. If you do, windows will correctly install the driver but Kies will never detect the phone. It is possible that shutting Kies down and restarting it (and repeating the steps I mentioned to get Kies to connect) may correct the issue but most likely, it will require a reboot and then you will have to run thru the steps I outlined again to get it to connect properly.
This is a combination of Windows and Samsung both. Windows could handle this so much better, Samsung could have reported the device as two possibilities instead of 5. But, what can I say, One company is Korean and one is American and they each like to do things their own way.
Thanks, OP - finally able to get the ICS update. This whole process was a complete cluster****. Samsung should work on that.
Edit: Guess I spoke too soon. Kies was able to recognize my Note and began the update process (i.e., asked me if I wanted to update, had to agree to whatever, etc.), but after it downloads the firmware and begins "preparing firmware upgrade components" to install the upgrade it loses the connection with the phone and restarts the whole process again. Kies doesn't say anything about losing the connection - the box that shows the status of the update just closes and Kies doesn't register any connected devices (though it starts the "connecting" process again a few seconds later. Any suggestions?
NickNaylor said:
Thanks, OP - finally able to get the ICS update. This whole process was a complete cluster****. Samsung should work on that.
Edit: Guess I spoke too soon. Kies was able to recognize my Note and began the update process (i.e., asked me if I wanted to update, had to agree to whatever, etc.), but after it downloads the firmware and begins "preparing firmware upgrade components" to install the upgrade it loses the connection with the phone and restarts the whole process again. Kies doesn't say anything about losing the connection - the box that shows the status of the update just closes and Kies doesn't register any connected devices (though it starts the "connecting" process again a few seconds later. Any suggestions?
Click to expand...
Click to collapse
Use the link I provided in the original post to download the updated version and stick it in a folder you can find.
Completely UNINSTALL Kies.
Unplug your Note from the PC.
Reboot your PC.
Reinstall Kies using the new version you downloaded.
After installing, reboot your PC.
After your PC has rebooted, go through the process of installing the Note drivers as I described in the original post (see below). Once you reach the step of putting the phone in USB debugging mode and have plugged it into your PC, wait until AFTER Windows has told you the drivers have been correctly installed. If Windows gives you an error that the drivers did NOT install correctly, reboot and try again. You need to pay attention to the icon in the system tray, click on it to see whether it is currently installing, whether it successfully installed, or whether it failed if you arent seeing the icon animation.
MAKE SURE to watch the icon near the clock, do NOT change the USB mode on the phone until AFTER windows has told you it has installed the driver for that mode.
AFTER you have enabled USB Debugging and plugged it into your PC, wait until AFTER Windows says that it successfully installed the driver, then, WITHOUT unplugging your phone, launch Kies and proceed to update your phone.
littlewierdo said:
Use the link I provided in the original post to download the updated version and stick it in a folder you can find.
Completely UNINSTALL Kies.
Unplug your Note from the PC.
Reboot your PC.
Reinstall Kies using the new version you downloaded.
Click to expand...
Click to collapse
Thanks for all of these suggestions. This makes complete sense but I'm still having a problem (Windows Vista 64):
- I uninstalled using Kies Uninstall tool
- I searched out and deleted all other Kies related files, including program data stored under the user profile
- I rebooted my PC
But... when I try to install Kies from the new .exe file, it goes back to the loop: uninstall / install / uninstall.
Is there something more that needs to be done to "uninstall Kies" completely? e.g. modify a registry?
PS about the "loop" it goes like this:
10 Pop up: Before you install the new version, you need to uninstall the old version of Kies
20 Me: OK
30 (it then uninstalls - allegedly)
40 Pop up: You will now install the new version.
50 Me: OK
60 goto 10
UPDATE (7/17):
I used a registry cleaning utility to wipe out Kies related keys in the registry. I was then able to install the new, downloaded version of Kies and successfully updated my phone. So... I assume the loop was caused by Kies not being able to properly uninstall itself. (Or... it could have just been me...)
There is a possibility of user account control getting in the way. Forgot to mention that before you run the installer, you need to right click on the exe and select the compatibility tab and then select 'run this program as administrator'. For whatever reason, some machines I have noticed that Windows doesnt always automatically detect when a program needs to be run as admin and it needs to in order to access everything it needs to.
Why arent people flashing ICS the way everyone else has been for months? Seems like its causing more problems than anything
Sent from my SAMSUNG-SGH-I717 using xda premium
Newer Version of Kies!
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
This worked great to finally upgrade my Kies to Version 9.7, however there is a newer version 2.3.2.12064.10 available so when trying to update it once again goes into the loop. Any idea as to where to find this newer version?
Cubbump1 said:
This worked great to finally upgrade my Kies to Version 9.7, however there is a newer version 2.3.2.12064.10 available so when trying to update it once again goes into the loop. Any idea as to where to find this newer version?
Click to expand...
Click to collapse
I found this direct link at the German Samung website: downloadcenter.samsung.com/content/SW/201105/20110512115717796/Kies_2.3.2.12064_10_1.exe (Grrr...I am not allowed to post a working link since I am a new user. Sorry for that.).
Worked for me, but I had to remove the old version on my own before installing the latest version with this installer. Otherwise it got stuck in the infinite uninstall loop.
THE PROBLEM HAS BEEN SOLVED!
If you have the MTP usb device driver error (code 10), then scroll down and try what worked for me.
Sparrow245 said:
So, I used Odin to reset my vibrant back to stock 2.1. I then tried to get it to 2.2 using Samsung Kies, but when ever I try to use it, MTP Device fails to install. Anyone know how to get the driver to install / work correctly so that I can use Kies? Thank you in advance.
Click to expand...
Click to collapse
You should really avoid using kies if possible. It is notorious for hard bricking phones, meaning they become paper weights if something goes wrong. You should install clockwork mod recovery and install a custom 2.2 ROM, there are literally tons to choose from and they are pre-rooted. Some of the custom ROMs have odin images so you could actually skip the clockwork recovery step. I'll link you to the 2.2 ROM I'm using or you can search for something different. Here is Axura 2.2, use the odin image in the 3rd post http://forum.xda-developers.com/showthread.php?t=1787267.
EDIT- if you also need drivers for your phone then go here http://forum.xda-developers.com/showthread.php?t=728929
Sent from my SGH-T959 using Tapatalk
If you want 2.2 (Froyo) installed on your Vibrant, like the other poster said, there are literally tons of great builds.
Here is a link to one that I really liked, it had great battery life, and overall good performance. Bionix V - http://forum.xda-developers.com/showthread.php?p=21324042
As stated above, please avoid using the Kies software, it generally creates many more problems than it is worth.
I've used Kies many times, so I know what I'm doing. But apparently this time something about the MTP driver isn't going alright. Could be that I have this fairly new computer? I've already tried installing the vibrant drivers, but for what ever reason I keep getting a code 10 error for the MTP usb device. :/
Well if your not doing so already, try running the program as administrator.
However, not sure why you are so hell bent on running the stock Froyo via Kies, when there are so many other amazing Froyo/GB/ICS/and now JB custom ROMs that work MUCH much better, and have way better support than Samsung could ever provide.
However, to each his own. Good luck to you with your endeavors!
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
I know the thread is for a tablet, not sure which version of windows your running, but maybe something lime this is what you are looking for: http://forum.xda-developers.com/showthread.php?t=1150211
Sparrow245 said:
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
Click to expand...
Click to collapse
Google code 10 error mtp
You should find a link that says fixed code 10 mtp error Samsung galaxy
It is a post on android forums or phandroid??? You should see it and it should fix your error.
sent from my magic box to yours
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Sparrow245 said:
I've used Kies many times, so I know what I'm doing.
Click to expand...
Click to collapse
When kies hard bricks your phone I'll be here to say I told ya so. Its really an unnecessary risk but its your phone, good luck.
Sent from my SGH-T959 using Tapatalk
@sparrow, that's exactly what I read but it was to much to type.
sent from my magic box to yours
Please Help
hey man did you ever get the MTP driver to start? I am still at a loss with this myself.
Sparrow245 said:
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
Click to expand...
Click to collapse
Sparrow245 said:
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Click to expand...
Click to collapse
This is the steps used to fix.
Sent from my SCH-I535 using xda premium
Now is really solved.
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite
Sparrow245 said:
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Click to expand...
Click to collapse
Thanks a ton...saved my day.