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.
Related
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Have you loaded an insecure kernel using Odin?
SusieGalaxy880 said:
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Click to expand...
Click to collapse
The easiest way to gain root would be to flash a ROM that has root already. Such as this stock ROM: http://forum.xda-developers.com/showthread.php?t=1512331
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
These kinda more difficul steps,, and i dont wanna mess any of those because if any step goes wrong, I duno how to fix it. Aren't most people use the easy way to superoneclick to root and successful? I just want to know which step I did wrong for my fail root. I dont wanna mess with any deeper or more diffiuclt stuff.
SusieGalaxy880 said:
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
Click to expand...
Click to collapse
You shouldn't have connected mass storage.
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
SusieGalaxy880 said:
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
Click to expand...
Click to collapse
From my experience just have Windows 7 doesn't ensure have framework 4+ so check for a download on that.
If your USB debugging mode is ON then you shouldn't get the "connect mass storage" option on the device at all, so double check that (uncheck and recheck it if necessary.
Personally I choose to skip Kies entirely and just download the drivers only, but the first time you plug the player in with Debugging on windows should do it driver search thing down by the clock and it installs (i think 3) different drivers for the player (different then the mass storage driver) if you jumped in to superoneclick before that finished that may have been part of the problem, if you didn't get those to install then sounds like a driver issue.
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
SusieGalaxy880 said:
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
Click to expand...
Click to collapse
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
I didnt restart my device before rooting.
I got the superoneclick from XDA main page the offical one with 500+ page of posts and reply. "Superoneclickv2.2 -shortfuse.zip"
Try using doomlords rooting toolkit, it worked for me.
http://forum.xda-developers.com/showthread.php?p=18805532
thanks for info, but I duno how to use the DooMLoRD's Easy Rooting Toolkit. Any instruction? I have no idea why my device is so diffiuclt to root, as other people rooted very easy
I used version 2.3.3 to root mine.
Got to shortfuse.org and scroll down to the 2.3.3 download link.
I tired the 3rd time today, failed again, same outcome. This time I follow each step carefully, and I used superoneclick v2.3.3 Before ROOT, I make sure all the "READY TO USE" check mark on. But still hang at Shell Rooting device step #5. I patient waited for 20mins, still hang at this step.
I shoulda try root when I got it first day. Is there possible some mess up app might cause this? I never heard anyone have any diffiuclty Rooting their galaxy player 4.0 YP-G1 US version with superoneclick after so many tried. I officially give up. I only have this device for 1 week..............
Kernal Version 2.6.35.7-G1UEKI8-CL562400 [email protected] #2
Build # Gingerbread.UEKI8
Firmware V2.3.5
Model Number: YP-G1
I found a very important issue might cause this failed. When I check the unzip folder, the Expoits folder IS NO FILE, EMPTY, but when I check the original zip file, it has 3 important files "GingerBreak,psneuter, zergRush" files (on the v2.2) I try unzip on desktop, pull out this Exploit folder, pull out the file, none work. I even uninstall winRAR and restall the newer version. These 3 files on the exploit folder in superoneclick v2.2 seem CANNOT pull out of the zip file no matter what I try. I think on shell Rooting device step #3 started the problem cuz cannot locate these few important exploit files. I just found out the unzip folder have no those file (psneuter,zergRush), while the original zip file has, and I cannoot pull out those file out of the zip folder NO MATTER WHAT I TRIED. Both superoneclick v2.2 and v2.3.3 exploit folder, i cannot get those file out of the zip folder.
Got rooted successful the 4th tired. Problem is my antiviurs always remove the psneuter & zergRush files in exploit folder when I extract everytime. And I didnt notice this problem. So I was rooting without these 2 important files in superoneclick folder. Now I disable antivirus, so i can extract those file and start rooting, after done rooting, i turn antivirus back on.
another problem
daniel644 said:
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
Click to expand...
Click to collapse
can someone help me i have the ``firmware uprade encountered....``
i can go to the the warning but
-if i press up to continue it return to firmware....
-if i press down the same thing
thanks.
Hi
For some reason I am now getting a Driver Installation Failure error for my S3 when I plug it in to USB on Windows 7. The driver is SAMSUNG Mobile MTP Device, which fails after a long (3 minute or so) install attempt.
This means I can't access the Phone via USB for file tranfers etc, either Windows Explorer or Keis. Though I can use ODIN to Flash if I put the Phone in Debug Mode.
I have tried all sorts. Un-installing the Samsung Drivers, rebooting and reinstalling, and getting Kies to try a driver repair.
It wasn't like this when I started with the phone. Something changed - after I rooted it. I am currently on the Omega ROM 6.0 with standard kernel. For a while I was on 5.1 with Syloa 1.1 and then 1.26. I realized it was wrong when I couldn't copy Omega 6.0 ROM ZIP over to Flash.
I have searched and searched. This seems to have happened to other phones as well but be intermittent. A few other phone on XDA have reported this in the last couple of weeks (so maybe a Microsoft change to Windows 7?)
As a weird related issue sometimes when I plug the Phone into WIndows now I get two removable drives showing, which are "Samsung USB Gadgets" using a 2006 Microsoft Driver... They show as removable drives with no drive in them. Again all my tricks of disabling uninstalling, re-installing etc these seem to make no difference.
Anyway - any ideas / fixes help appreciated!!!
Cheers
So here is the cure. First connect your phone to your pc. Now right click my computer and select manage. Go to device manager and expand the universal serial bus controllers tab. Now you should see something like unknown device with a yellow exclamation mark. Right click it and select uninstall. Now reconnect your phone and try it.
Now again check in device manager after installation. It should look like the one in the attachment.
I've got the same issue; can't get the MTP drivers to work on my Win 7 machine or my work XP box. Both had the Galaxy nexus drivers on them previously (I think, came from ICS Captivate).
Are you sure USB debbuging is unchecked in settings?
If that's not the problem, you could try a different pc or os (a live ubunt cd for instance) to see whether it's the phone or the computer thats messed up.
Fresh windows 7 install and still nothing. Could the phone be messed up?
Have you tried a different USB port?
Yeah tried all the ports/cables I've got lying around. In safe mode it will install everything okay but Kies still won't connect. :/
Geoff.Costello said:
Hi
It wasn't like this when I started with the phone. Something changed - after I rooted it. I am currently on the Omega ROM 6.0 with standard kernel.
Click to expand...
Click to collapse
Same here!
I also have Omega ROM 6.0 but the problem started BEFORE Omega ROM.
Did you also back up your efs folder using SGS Toolkit 2.0?
I seem to have had the problem after flashing the "insecure image" which one has to do using the SGS Toolkit in order to backup efs.
Ive also uninstalled and reinstalled pretty much EVERYTHING, drivers, Kies, SGSToolkit etc...
I have 5 pc's at home. ALL of them cannot connect to my SGS3, and ALL could connect to my SGS2 a couple of days ago!
tx
Mark.
---------- Post added at 03:12 PM ---------- Previous post was at 03:06 PM ----------
rohan999 said:
So here is the cure. First connect your phone to your pc. Now right click my computer and select manage. Go to device manager and expand the universal serial bus controllers tab. Now you should see something like unknown device with a yellow exclamation mark. Right click it and select uninstall. Now reconnect your phone and try it.
Click to expand...
Click to collapse
Thanks, but process does not work in this case. Not on 5 PC's in my house.
BTW Kies by WIFI seems to work, but it is obviously very limited...
Try this
This worked for me follow link
tomshardware.com/forum/242140-44-device-refuses-installed-please
rjnolberto83 said:
This worked for me follow link
tomshardware.com/forum/242140-44-device-refuses-installed-please[/url]
Click to expand...
Click to collapse
hi link does not work
it takes me to toms home page...
To fix the problem, follow the next steps:*1) Go to http://www.microsoft.com/en-us/download/details.aspx?id=19153
2) Press the*Continue*button (Near the validation required button)*
3) Press the*Download*button (Near the genuine Microsoft software)*
4) In case that the download hasn't started automatically within 30 seconds, press the*Start Download*button.*
5) Save the file.*
6) Execute the file (Double click on the mouse's left button).*
7) Next -> Repair -> Repair -> Finish -> Choose "Yes" so the system restarts itself.*
That's it, now the MTP devices should work correctly.*
Sent from my SPH-D710 using xda premium
rjnolberto83 said:
To fix the problem, follow the next steps:*1) Go to microsoft.com/downloads/details.aspx?FamilyId=A2E73160-E862-4F19-BB26-C0CAFE798955&displaylang=en
2) Press the*Continue*button (Near the validation required button)*
3) Press the*Download*button (Near the genuine Microsoft software)*
4) In case that the download hasn't started automatically within 30 seconds, press the*Start Download*button.*
5) Save the file.*
6) Execute the file (Double click on the mouse's left button).*
7) Next -> Repair -> Repair -> Finish -> Choose "Yes" so the system restarts itself.*
That's it, now the MTP devices should work correctly.*
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I've got the same issue and this did not work.
Reinstalling windows fixed my problem.
cure is to wipe phone, dalvik, re-flash rom
rjnolberto83 said:
To fix the problem, follow the next steps:*1) Go to microsoft.com/downloads/details.aspx?FamilyId=A2E73160-E862-4F19-BB26-C0CAFE798955&displaylang=en
2) Press the*Continue*button (Near the validation required button)*
3) Press the*Download*button (Near the genuine Microsoft software)*
4) In case that the download hasn't started automatically within 30 seconds, press the*Start Download*button.*
5) Save the file.*
6) Execute the file (Double click on the mouse's left button).*
7) Next -> Repair -> Repair -> Finish -> Choose "Yes" so the system restarts itself.*
That's it, now the MTP devices should work correctly.*
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Hi there
This may work in other situations, but I have found out what caused my MTP to start working again, and it is NOT the computer, it is the phone for 100% sure.
I had this issue on 5 PCs in my home, ALL of which worked fine with my SGS2.
I did a factory wipe, wiped dalvik, and re-installed Omega v6 rom, and it now works on all 5 computers.
I do not know why it started, but the thing I did before the problems started was to use SGSToolkit v2 to flash an "insecure image" so I could backup efs folder. I have a feeling it is related to this, but I do not know for sure, and the maker of that software says 20000 people have used his software without this issue, so it cannot be his software.
Anyhow, by reflashing omega, and wiping the phone, it now works.
Mark.
Worked for me too.. It was the phone.
Mark,
Thanks. I too had Omega 5.2.
I wanted to upgrade modems but found I couldn't connect via PC as I had lost Root.
I too downloaded Version 2.0 of the tool kit and downloaded the insecure kernel and flashed it.
After that I could not get any PC to recognise the phone.
I got Omega 6.0 on wirelessly
But connection problem remained.
So your full wipe worked. The phone is now behaving and connecting to any PC I try.
Thanks
Geoff
Possibly the USB cable?
I ran into this issue as well. When I connected my phone to my (Win7Prof64) computer, the OS recognized and downloaded the drivers and my phone's directory came right up. When I tried the same the next day - I received the "unknown device" message. After about an hour of troubleshooting I learned something interesting - I was using a different USB cable than the one I received with my phone. I connected the USB cable I got with the phone and everything automagically worked again. The USB cable must use another wire that "regular" USB cables don't? Here's a chat with Samsung support regarding the cable:
Gavin: Yes, the USB cable supplied with the device is Samsung recommend and is the Original. So, we request you to use the USB which is supplied with the device.
Doug: will i damage the device at all if i use a different cable to simply charge the device?
Gavin: No, it will not damage the device while charging.
Gavin: But, it can face some issues in connecting in mass storage mode.
Hope this helps!
Here's what I found about about my problem.
Samsung Galaxy S3 does not like USB 3.0 ports on my laptop.
Plugged the phone into the USB 2.0 port and it worked perfect.
Hope this helps out some of you!
The same device on Win7 OK, on XP not.
4 me it happen after Android upgrade to ICS 4.0.4 but only on XP PC. Win7 found new drivers online automatically.
May be XP is to old 4 ICS
One solution I found here: http://androidforums.com/4819200-post7.html however don't want to hard reset my device
Some body can try driver pack 4 all phones here: http://www.mobiledit.com/downloads.htm?show=14
I had this happen on occasion in the past and just now (moved to new laptop). What I have done that works for me is that you open up the details (where it says that it's installing your device click here for more details) and let it find/install all the drivers. Eventually it will fail with the MTP driver, KEEP that window open. Now unplug the usb cable FROM YOUR PC (don't ask me why but this works 100% from the phone side not always) and then plug in again. You'll see the MTP driver search start again and this time it should install.
FIX
1. Download and install the s3 Toolkit here: http://forum.xda-developers.com/showthread.php?t=1703488
2. Don't run it but browse to \Samsung Galaxy S3 ToolKit\drivers
3. Run USBDeview and uninstall everything with Samsung or i9300 in the description (right-mouse)
4. uninstall Kies and USB drivers.
5. Disconnect phone
6. Install \Samsung Galaxy S3 ToolKit\drivers\Samsung_USB_Driver.exe
7. Connect phone.
Tadah!
Solution
Here is the only solution that could resolve the problem for me after days and days of trials and errors.
Just go to device manager and manually install the driver after selecting it from the already available drivers.
over and done.
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.
People!, I'm about to pull all my hair out on this one
Vibrant is soft bricked in a boot loop after a incomplete flash, I am able to get it into download mode but both my windows machines say USB device isnot recognized, and thus, I cant use ODIN to return to stock. When I try to manually point windows to the samsung drivers I get nothing…
So far I have tried drivers from:
-Bay_wolf's AIO Vibrant Toolbox 2.5
-USB drivers for vibrant from samsung support site
-Drivers from samsung keyes
Side notes that might help: I was perviously using a Hellybean Rom. My device displays "Galaxy S gt-9000" on boot... not sure when that came to be but maybe some rom changed some important recognition stuff??...
I found this thread http://forum.xda-developers.com/showthread.php?t=1008383 but no help...
Any help would be greatly appreciated!!
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Toast6977 said:
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Click to expand...
Click to collapse
Thanks a ton for reply but, sadly, no dice.
Tried connecting the phone, getting the "unrecognized device" prompt, finding "unknown device" in device manager, right clicking to uninstall. rebooting my machine, using various install methods to re-install drivers, re-connecting, and nothing.. same issue...
I lost the original cable a while back, but can't accept that NONE of the other 5 cables used are all broke... specially if the computer recognizes something going on... is it worth buying a new one?
Losing hope here, been like this for 4 days now, think it's time to go get a new phone. :crying:
Even so, it would have been nice to get what was a perfectly working phone back if only to keep it as a mp3 payer.
If anybody in New York, NY has a working odin set up that can do this for me, I have a 6 pack of your favorite beer with your name on it.
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
For what its worth, the gt i9000 screen appears after your on a custom GB boot loader and Odin back to stock (or probably Odin flashing any other ROM) you can change it by flashing the GB boot loader again. My phone says its a i9000 too, but I'm just about lazy enough to not bother changing it, lol.
So that's unrelated.
eksasol said:
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
Click to expand...
Click to collapse
Ok, faith momentarily restored. But I have questions:
-What do you mean when you say "check the option to also delete USB driver and uninstall any drivers"? I dont get such a prompt from right clicking on "unknown device" and selecting uninstall? Is there another method to uninstalling drivers?
-In the link attached, I can only find "Device(Install),USB Driver (Software) (ver.1.0)" not the 1.5.3 version mentioned. What am i doing wrong here? currently searching google for the 1.5.3 but finding nothing.
I get into download mode by holding volume- up + power. Have 2 PCs ( win xp and win 7) and a mac running mountain lion (but never ever have been able to get Heimdall to work, so devoting time to odin.)
Thank you for the time + help, guys, I really do appreciate it in the time of utter un-nerdness.
If the device is already installed it will have a check box that said "Delete the driver software for this device." If its unknown then obviously not. By "uninstall any driver", I mean uninstall any Android drivers you current have installed and reboot before you reinstall the new driver.
Although I doubt it will make a difference than the one I linked above, you can try the Samsung driver version 1.5.3: http://www.mediafire.com/?r0uc3h413qcy80z
If you did manage to get into download mode and see this: http://images.google.com/search?num=10&hl=en&site=&tbm=isch&source=hp&q=download+mode
Then it mean there is a very good chance you can restore the phone, if you can find a computer to recognize it and Odin to see a COM port.
I definitely think it would be worth the money to go buy an OEM USB cord. I can't tell you how many times I have seen this and a new USB is the fix.
sent from the depths of helly bean
OK guys...
My friend, who also owns a Vibrant, let me borrow the cable that came with the phone for the last 2 days.
Tried to make ODIN work on both PCs at home, gave Heimdall a shot on my mac, even hijacked a computer at work for the better part of the morning and freshly installed USB drivers 1.5.3 before connecting. All for nothing... “Unknown device” across the board....
At first I felt that with being able to get into download and have SOME kind of a reaction from connecting to PC had to be a good sign. Almost completely convinced that there is some unknown, unworkable hardware problem present. Definitely, officially, unremarkably out of ideas here.
Nothing is beautiful and everything hurts.
Last thoughts? Options at this point?
Also, tried One-click Unbrick tool on mac. I got a "is your phone plugged in, is it on download mode?" error, but anyone reading this down the line with a similar problem should check it out.
http://forum.xda-developers.com/showthread.php?p=15330252
Hey guys,
So I posted on here awhile back ago with a problem of a boot loop on my SGH-i777 and I never got around to repairing it till now, I went down to Best Buy and got a new phone maybe 2-3 days after I got the boot loop.
I ran into the "Deleting Cryption Meta Data" problem and was told to follow this thread. But I'm having a hard time understanding it, so I went around searching a bit more and found someone with the same problem (here's that thread).
I read that he was having a hard time understanding what's supposed to be done, so I thought someone would explain it to him a bit more.
creepyncrawly said:
Assuming your laptop runs Windows...
Refer back to this post again, and...
For 1. follow the instructions in step 2a) of this guide, except use this file: I777UCKH7-CL503881 FULL Odin3 One-click Downloader (See Download Repository, link in sig) which contains the bootloaders and param.lfs.
Click to expand...
Click to collapse
So I go to that post, start to follow the instructions thinking I'm finally gonna get this thing to work. Well, no..
I downloaded the latest version of Odin, I downloaded the "I777UCKH7-CL503881-Full.exe", then like the thread said. I unzipped, ran the .exe and put my SGH-i777 into download mode. But when it's in download mode, supposedly in Odin "the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]"
and mine doesn't do anything.. my computer recognizes something is plugged in, so it plays the noise. But nothing else happens.
Am I supposed to put something in the "Bootloader", "PDA", "PHONE" or the "CSC" box's? I don't really need this phone, but I still don't want to brick it and ruin it. I'm starting Application Development in school this year, so I was hoping to use my S2 for tests and what not, instead of my S3.
zZSleepyZz said:
...So I go to that post, start to follow the instructions thinking I'm finally gonna get this thing to work. Well, no..
I downloaded the latest version of Odin, I downloaded the "I777UCKH7-CL503881-Full.exe", then like the thread said. I unzipped, ran the .exe and put my SGH-i777 into download mode. But when it's in download mode, supposedly in Odin "the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]"
and mine doesn't do anything.. my computer recognizes something is plugged in, so it plays the noise. But nothing else happens.
Am I supposed to put something in the "Bootloader", "PDA", "PHONE" or the "CSC" box's? I don't really need this phone, but I still don't want to brick it and ruin it. I'm starting Application Development in school this year, so I was hoping to use my S2 for tests and what not, instead of my S3.
Click to expand...
Click to collapse
First, the file you were directed to download is a "one-click downloader."
I777UCKH7-CL503881 FULL Odin3 One-click Downloader: I777UCKH7-CL503881-Full.7z (Contains I777UCKH7-CL503881-Full.exe.)
This means that the executable file contains both Odin, and the firmware package compiled into one. You therefore do not need a stand alone Odin package to use this. The One-click downloader interface does not have the slots, "Bootloader", "PDA", "PHONE" or the "CSC" where you can insert files. Maybe that will clear up some confusion.
Secondly, the way you describe your problem, it sounds like you do not have the correct USB driver installed on your computer. Please go to the Windows dialog for "Add Remove Programs" or in Windows 7 "Uninstall a program." Look for SAMSUNG USB Driver for Mobile Phones. If that is not present, then you must install the driver. You could get it directly from Samsung, or perhaps download it from this thread. If that is present, and you still can't get Odin to add the phone, then you should uninstall the driver, reboot windows, reinstall the latest driver, and reboot windows again, and then retry Odin.
creepyncrawly said:
Please go to the Windows dialog for "Add Remove Programs" or in Windows 7 "Uninstall a program." Look for SAMSUNG USB Driver for Mobile Phones. If that is not present, then you must install the driver. You could get it directly from Samsung, or perhaps download it from this thread. If that is present, and you still can't get Odin to add the phone, then you should uninstall the driver, reboot windows, reinstall the latest driver, and reboot windows again, and then retry Odin.
Click to expand...
Click to collapse
I'll be sure to do that, I did an install right before plugging in my SGH and the last time I was having issue's my PC would do the same thing (I've recently formatted my laptop and reinstalled Windows 7). Kind of makes me think it could be something wrong with my phone's USB Port. But I'll try one more time and report back.
zZSleepyZz said:
I'll be sure to do that, I did an install right before plugging in my SGH and the last time I was having issue's my PC would do the same thing (I've recently formatted my laptop and reinstalled Windows 7). Kind of makes me think it could be something wrong with my phone's USB Port. But I'll try one more time and report back.
Click to expand...
Click to collapse
If the USB driver is installed and working correctly, then the problem is most likely in the connection between the phone and the computer. Yes, possibly the usb port on the phone, but it could be the cable, or the usb port on the computer as well.