Related
Kies synced with windows 7
Anyone had success with this?
Nope. No suck luck
I had the issue yesterday. If you change the USB setting on the phone to select on connect it should work a lot better.
These are the drivers that i found, kies works perfect now.
http://db.tt/ErGVyE
BuddyLee said:
These are the drivers that i found, kies works perfect now.
http://db.tt/ErGVyE
Click to expand...
Click to collapse
Thanks for those, I will try them when I get my phone on monday (if Kies doesn't work with Windows 7 32 bit)
but what is the point of Kies though? lol to update firmware?? because on my HTC Magic Android I only use the mass storage for everything.
Archius said:
Thanks for those, I will try them when I get my phone on monday (if Kies doesn't work with Windows 7 32 bit)
but what is the point of Kies though? lol to update firmware?? because on my HTC Magic Android I only use the mass storage for everything.
Click to expand...
Click to collapse
Honestly its kinda useless. It only has a video converter app built in for the galaxy s. But you dont even have to have the phone connected to use it
~.~
btw im on win7 64bit and confirm it works.
BuddyLee said:
These are the drivers that i found, kies works perfect now.
http://db.tt/ErGVyE
Click to expand...
Click to collapse
Thanks, that worked a treat, can see the inbuilt ROM and SD card now.
tough luck..
man.. i am still having this issue for 2 days straight now..
uninstalled.. safe mode, reinstalled.. super admin.. device manager.. ccleaner..
nothing works for me.. my windows 7 ultimate 64bit is still not detecting my phone.. even using 2 version of Kies..
Any other suggestion(s)?
m3keni said:
man.. i am still having this issue for 2 days straight now..
uninstalled.. safe mode, reinstalled.. super admin.. device manager.. ccleaner..
nothing works for me.. my windows 7 ultimate 64bit is still not detecting my phone.. even using 2 version of Kies..
Any other suggestion(s)?
Click to expand...
Click to collapse
Install the file I linked
Galaxy S MTP detection issue resolved!
got it working finally after toying with the application and the phone itself..
honestly, i did all the suggestions here including BuddyLee's suggestion but nothing worked including all my research from other forums.. what a waste of my time.
anyways, I finally got it working by doing "Format" for the internal memory.. unmount then format.. and yes, reset to "Factory Default".
after the phone restarted, I connected it to my Windows 7 Ultimate x64bit computer and success.. device manager finally shows GT-I9000, Kies shows it as GT-I9000 and My Computer as well.
Hope this helps anyone out there with the same issue where countless uninstall/reinstall, device manager troubleshooting, Kies Driver Recovery and Reset Phone to Factory Defaults didn't work at all.
m3keni said:
got it working finally after toying with the application and the phone itself..
honestly, i did all the suggestions here including BuddyLee's suggestion but nothing worked including all my research from other forums.. what a waste of my time.
anyways, I finally got it working by doing "Format" for the internal memory.. unmount then format.. and yes, reset to "Factory Default".
after the phone restarted, I connected it to my Windows 7 Ultimate x64bit computer and success.. device manager finally shows GT-I9000, Kies shows it as GT-I9000 and My Computer as well.
Hope this helps anyone out there with the same issue where countless uninstall/reinstall, device manager troubleshooting, Kies Driver Recovery and Reset Phone to Factory Defaults didn't work at all.
Click to expand...
Click to collapse
For me it was enough to unmount/mount internal memory. And after plugging USB it immediately was detected by Kies
BuddyLee said:
These are the drivers that i found, kies works perfect now.
http://db.tt/ErGVyE
Click to expand...
Click to collapse
I can´t download the file... can someone upload a mirror?
Link: jump.fm/UURUE (new user, so can't post urls yet)
And I can confirm it works on Win7-64.
suggestion.. can't provide links yet.. (restriction)
Steili said:
I can´t download the file... can someone upload a mirror?
Click to expand...
Click to collapse
try this one.. go to google and seach "samsung kies download".. the first or second result should take you to the samsung download site for the Kies application.
hope this helps.
I had the exact same problem i tried everything nothing worked so i rebooted the phone and BAM it worked
So reboot your phone then try again...
which driver version is this? MTP
can some one post the file please
I don't understand why this file is so difficult to download. I have the file now finally!
I was able to get the sync to work via Outlook.
Sometimes it say that mtp device is installed, but kies not see it, but recognise it as mass storage...
how can i solve this problem?
when i connect the phone as Samsung kies on the screen it say initializing but is not lock on this screen...
sorry 4 my bad english
ilbulgaro89 said:
Sometimes it say that mtp device is installed, but kies not see it, but recognise it as mass storage...
how can i solve this problem?
when i connect the phone as Samsung kies on the screen it say initializing but is not lock on this screen...
sorry 4 my bad english
Click to expand...
Click to collapse
What system are you using? Windows XP, Vista, 7?
TMW597 said:
What system are you using? Windows XP, Vista, 7?
Click to expand...
Click to collapse
Same problem here, using XP
I flashed my Nexus S with CM7 RC 4. Accidentally my original nandroid backup got deleted. I want to flash my device with the factory android 2.3.3 image. Please let me know the link to download the Android 2.3.3 for SNS 9023 GRI54.
You find it on:
http://forum.xda-developers.com/showthread.php?t=973534
I have already downloaded the rom files and the odin but the odin don't recognise my NS.
Can you tell me how to do a fastboot flash ?
If you want odin to recognize your nexus you have to install the samsung usb drivers .. You can find them here: http://forum.xda-developers.com/showthread.php?t=728929
I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.
I do not have a fastboot image for you ..btw the google drivers are not the same as the samsung drivers ..for odin you will need the samsung ones ...
To go into downloadmode :
turn on you phone, plug your phone into a sb port ( as if you wanted to put something on the phone) then while your phone is still connected to your pc , switch you phone off and keep holding vol up + vol down ..you will see that if you keep holding them phone will go into download mode after you phone is switched off
jaivinder said:
I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.
Click to expand...
Click to collapse
You installed the samsung drivers, make sure that your phone is power on,disable the usb debugging, ceheck that microsoft.net framework is installed on your pc. When you connect your phone (on your device manager) you must have "android phone" and below that "nexus s" with out any question symbols.If so then select to update your driver and give the path you installed the samsung drivers (eg c:\program files\samsung ....).
Power off you phone, open Odin and follow the pdf file from samfirmware to load the files (bootloader,pda,modem,csc). Hold your phone from the middle of volume buttons(between vol up and vol down) and immediately connect your phone to your pc with the usb cable .you are going to see the yellow triangle with the android.
Try it
Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.
hamajiro said:
Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.
Click to expand...
Click to collapse
What kind of error?on Odin or on your phone?
afilopou said:
What kind of error?on Odin or on your phone?
Click to expand...
Click to collapse
On Odin. The error message is in Korean so I don't know what it says, but it says something about the PDA tar. Please see the attached image.
Thanks
If I do it without PDA, I don't get an error...
hamajiro said:
If I do it without PDA, I don't get an error...
Click to expand...
Click to collapse
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522
afilopou said:
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522
Click to expand...
Click to collapse
Thank you so much for your help.
I don't have a windows PC, but I'll install Windows 7 to my MBP using bootcamp and see how that goes.
I'll check the md5 check sum as well.
Sent from my Nexus S using XDA Premium App
Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App
hamajiro said:
Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Looks like that the virtual machine (vm fusion) on macosx generates problems.As far as i remember only parallels worked ok.I have imac as well but i have bootcamp win7 in order to avoid all these problems. Hope to help
Sent from my Desire HD using Tapatalk
Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...
hamajiro said:
Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...
Click to expand...
Click to collapse
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk
thanks, really needed this link
afilopou said:
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
No, I don't remember the initial values...
I'll check them at a Vodafone store when I get a chance.
Sent from my Nexus S using XDA Premium App
OK, so I had a chance to go into a local Vodafone Australia store.
The Baseband version under 'About phone' from the settings was I9023XXXKB1.
Under fastbootmode, the bootloader and baseband versions were I9020XXXKA3 and I9020XXXKB1.
However, CARRIER INFO is 'XSE' for Vodafone Australia, where as the CARRIER INFO from the Samfirmware.com ROM is 'EUR'.
Almost back to factory stock condition! Is it possible to change the carrier info? Does anyone know where I can get the stock Australian ROM for Nexus S?
I have the stock rom (2.1). Kies connected to my phone one time only ! Now It never connect. Can someone help me to fix it ?
Thanx
i face the same problem ,during 1 st attempt of update unknown error occur and after that the it is not connecting again ,takes forever any one please help
the word going around is to uninstall all the previously installed phone drivers, download latest version of kies and install it again..
hope it works..
It has never connected to my phone. I don't miss it.
I have the same problem..
19.nvv.11 said:
the word going around is to uninstall all the previously installed phone drivers, download latest version of kies and install it again..
hope it works..
Click to expand...
Click to collapse
does not work even after uninstall i fix all the registry using c cleaner and restart and the use the latest version of kies
Hi... I hope this can help you...
Try to do this
try that but no improvement ,i also put in aeroplane mode but same problem.....
So I found how to fix this problem on the I9000 forum and It works
Follow this link :
http://forum.xda-developers.com/showthread.php?t=758212
E-mail samsung about it, they'll send you a tutorial.
There are other programs for manage your samsung mobile.Kies dont work for much people included for me.
Just connect ur phone without sd card and then try, it worked for me.
Sent from my GT-I5801 using XDA App
I've installed Kies but it won't run on my xp pro 64 bit. It did work before I updated to Gingerbread but since then ,nothing. Kies won't run,either with the phone connected or not. Think it's more a problem of the pc but can't find a solution online. I have tried uninstalling,rebooting and re installing both Kies and the USB drivers to no avail. Attached file of error when trying to run Kies. Kies did connect ok when I could get it running but now I can't even get it to run.
have you tried running as administrator ?? also what about running in compatibility mode ?
I have the same problem after rooting with the Fug-Mod method. Maybe it is the same reason for your problem.
Custom-ROMs are not supported by Kies.
Try to run Kies in compability mode. Then reinstall the drivers. After that it work without issues. Or just reinstall Kies.
Just tryed to start it via XP SP3 mode and, like every time i execute Kies, it works.
Device: Galaxy S @ Simply Honey 2.3.3 (JVB)
PC OS: Win7 x64 SP1
stepping said:
I have the same problem after rooting with the Fug-Mod method. Maybe it is the same reason for your problem.
Click to expand...
Click to collapse
Other people had this problem too. Reflash with stock firmware and use cf-root instead. Worked for me, even after flashing supercurio's kernel afterwards.
Sent from my GT-I9000 using XDA App
Kies does not like Win 7 x64 .
Latest version Kies only one i ever got to work .
jje
Liam Good said:
I've installed Kies but it won't run on my xp pro 64 bit. It did work before I updated to Gingerbread but since then ,nothing. Kies won't run,either with the phone connected or not. Think it's more a problem of the pc but can't find a solution online. I have tried uninstalling,rebooting and re installing both Kies and the USB drivers to no avail. Attached file of error when trying to run Kies. Kies did connect ok when I could get it running but now I can't even get it to run.
Click to expand...
Click to collapse
Thanks to Jjegan your solution is here> http://forum.xda-developers.com/showthread.php?p=13166133#post13166133
Update
I uninstalled all usb drivers,uninstalled Kies. Then I reinstalled Kies without connecting any cable or phone but I am still getting the exact same error message. Kies can't know I have my phone rooted or even which Rom I am using as I have not connected the phone but it still won't run. Any other suggestions welcome.
Hello all
Wondering if anyone can help me with this. I have rooted my S ii and now when I connect it to the KIES software and try to check for updates, it says device not recognized. I can still use other functions of the software but I cannot try to check for updates. Does this mean when Samsung releases an update or pushes out a new version of Android, I will not be able to update my phone? If so, is there any way to change that?
Thanks for your answers.
search the forums, answers already out there...
in short, when you know that there is some latest firmware available in KIES...flash with the previous KIES update (not the latest) thru odin (the stock firmwares are available in dev section) and you must be knowing all this when you rooted your phone...
thereafter you are all ready for KIES updates...KIES will recognize your phone
SndChsr said:
Hello all
Wondering if anyone can help me with this. I have rooted my S ii and now when I connect it to the KIES software and try to check for updates, it says device not recognized. I can still use other functions of the software but I cannot try to check for updates. Does this mean when Samsung releases an update or pushes out a new version of Android, I will not be able to update my phone? If so, is there any way to change that?
Thanks for your answers.
Click to expand...
Click to collapse
If you are running windows 7 make sure you run kies as an administrator if you don't then it will always say device not recognised.
Root has nothing to do with Kies, as long as you stay on Stock ROM Kies will show update.
Sent from my GT-I9100 using XDA App
Turn off USB debugging.
Sent from my GT-I9100 using Tapatalk
Thanks all for the help. Greatly appreciated. I will run it as administrator and see if that does the trick.
SndChsr said:
Thanks all for the help. Greatly appreciated. I will run it as administrator and see if that does the trick.
Click to expand...
Click to collapse
do what chrisjcks told you instead.
Windows wont recognize the phone nor would kies as long as the usb debugging mode is active on your phone. In my case it shows to virtual drives flash drives, i cant access when usb debug is active on my phone on windows 7.
When USB debugging is not active, windows 7 shows me a phone icon with I9100 below it, that is fully accessible, at that point even kies recognizes it instantly.
OK, so now the phone is being recognized in Win7 but this is the message I see in Kies:
"This version of the device cannot be updated.
Current Firmware Version: PDA:KG2/PHONE:KG2/CSC:KG2 (VMC)"
Any thoughts why? I know that I rooted my phone in order to unlock it, but I'm not sure if rooting also altered the ROM. Sorry guys, I'm a total noob to Android. I rooted with the method posted here on the forums.
I should mention that I rooted using SuperOneClick and Odin method.
SndChsr said:
OK, so now the phone is being recognized in Win7 but this is the message I see in Kies:
"This version of the device cannot be updated.
Current Firmware Version: PDA:KG2/PHONE:KG2/CSC:KG2 (VMC)"
Any thoughts why? I know that I rooted my phone in order to unlock it, but I'm not sure if rooting also altered the ROM. Sorry guys, I'm a total noob to Android. I rooted with the method posted here on the forums.
I should mention that I rooted using SuperOneClick and Odin method.
Click to expand...
Click to collapse
Just means that there is no update for your phone at the moment. It will say that it either cannot be updated or you have the latest firmware. Same thing.
If you use a mixture of a CSC, modem, and rom/kernel from different stock firmwares KIES wont detect it.
So you need to flash to the same kernel, modem and CSC as your stock firmware, if you used superoneclick you must have flashed a insecure kernel, did you flash your stock one back?
veyka said:
If you use a mixture of a CSC, modem, and rom/kernel from different stock firmwares KIES wont detect it.
So you need to flash to the same kernel, modem and CSC as your stock firmware, if you used superoneclick you must have flashed a insecure kernel, did you flash your stock one back?
Click to expand...
Click to collapse
No, I did not flash it back. I flashed with superoneclick, unlocked the phone and left it as it is. However, I would like to flash it back. Is the stock ROM available somewhere? And if so, instructions on flashing it back to stock ROM would be beyond words of appreciation.
Do you need to change anything in kies registry.
Coming from sgs1, I remember you need to change HID value or something in kies registry.
[email protected] said:
Do you need to change anything in kies registry.
Coming from sgs1, I remember you need to change HID value or something in kies registry.
Click to expand...
Click to collapse
I'm not sure. You mean if the phone is rooted?
Well..I've connected my phone again and suddenly everything works as expected. Kies says everything is up to date. Thanks for the help chumps Greatly appreciated!
Sent from my Transformer TF101 using xda premium