After half an hour trying I have just found a working solution how to connect your SGS in Kies. Here is the deal:
Start Kies, put phone's USB settings in Kies mode. Connect your phone to the PC. Wait until MTP App show "Connected". Go to your PC's Device manager, find Portable Devices and select Disable on GT-I9000. Do not wait for the disabling process to be completed, just disconnect the USB cable. Now connect the USB cable again, wait the MTP App on the phone to show you the message "Connected" and choose Enable on GT-I9000 in Device Manager. After a few seconds your phone should be ready in Kies
I tried this both on x86 and x64 Windows 7 and it works for me.
I hope this will help! And I hope there isn't another thread with this solution. If there is - I'm sorry
i cant wait to get home and try this... another 10h to go
but if this helps ur a geniues
celeronix said:
After half an hour trying I have just found a working solution how to connect your SGS in Kies. Here is the deal:
Start Kies, put phone's USB settings in Kies mode , go to your PC's Device manager, find Portable Devices and select Disable on GT-I9000. Do not wait for the disabling process to be completed, just disconnect the USB cable. Now connect the USB cable again and choose Enable on GT-I9000 in Device Manager. After a few seconds your phone should be ready in Kies
I hope this will help! And I hope there isn't another thread with this solution. If there is - I'm sorry
Click to expand...
Click to collapse
Will put this in the FAQ if we have some confirmations for its effectiveness
when i first bought my phone it worked with kies, but after flashing it to a different firmware there was nothing i could do to get it to connect. i had deleted drivers, re-installed, etc etc but nothing worked. what ended up working was putting the phone in download mode, plugging in the usb to both phone and pc, then putting the phone into recovery mode, and as soon as the recovery menu popped up my device was recognized and the correct drivers were reinstalled and all was fine again
hondaguy said:
when i first bought my phone it worked with kies, but after flashing it to a different firmware there was nothing i could do to get it to connect. i had deleted drivers, re-installed, etc etc but nothing worked. what ended up working was putting the phone in download mode, plugging in the usb to both phone and pc, then putting the phone into recovery mode, and as soon as the recovery menu popped up my device was recognized and the correct drivers were reinstalled and all was fine again
Click to expand...
Click to collapse
If you still have this problem, please try my method and tell me if it works
I had issues and I also tried this method. But it didn't help
Last thing I tried was to format the internal SD. That did the trick for me....
The biggest problem with getting the phone to connect to Kies is two fold:
1) MTP application will ONLY launch from the home screen (touchwiz screen). NOT from any app. drawer / launcher screen
2) If USB mode on the phone is set to Ask on Connection, MTP won't launch due to the USB app. being open (see 1) above)
If you set USB to Kies mode and then ensure you are on the home screen of the phone with nothing else running, Kies WILL connect
Also remember the 16+ size extension bug.
So a full wipe on ur I internal sd card is a good solution just make sure u back it up tour hdd
I also did a "Driver recovery" from Kies and it worked after that. Although MTP driver failed to install for me in this case.
Make sure to update to the latest version of Kies ( Now 1.5.1.0074.45 ) as this version seems far more reliable when connecting the phone
I recently discovered that the culprit of Kies continuously trying to connect to phone was caused by wrong MTP driver selected.
Under WinXP
After phone connected in Kies Mode..Go to Device Manager/Portable device..
If you see a device labeled as "MTP xxx or Portable device.." ,wrong MTP driver or older driver has been used..For my case, a Microsoft 2004 MTP driver was selected.
To fix it.
1) Do a manual driver update..for my case ,i let the driver wizard to search automatically..this round, another newer Microsoft driver was found..in fact 2 of them.. after installing the drivers(Microsoft 2006 MTP driver,2 are listed..). .Now Device Manager/Portable device listed "GT-i9000" ,Kies immediately found my phone.
Driver name that worked are "wpdusb.sys" and "wudfrd.sys" found under \windows\System32\drivers\..
celeronix said:
If you still have this problem, please try my method and tell me if it works
Click to expand...
Click to collapse
You must not understand English. The entire reason I posted a comment was to share how I overcame this issue, so that would mean I no longer have this issue
Probable Fix for Kies
Friends,
I have also faced the same problem (while connecting my SGS via Kies MTP was crashing). It used to work earlier so I started to remove Applications and data in the reverse order of Installation. After I removed "Dolphin Browser HD" and all saved bookmarks it started working.
This may be a probable solution if you also have Installed Dolphin Browser.
~Gaurav
India.
2 different issues.
MTP crashing on phone is independent from Kies on PC cant detect phone.
i couldnt use kies either but i wasnt worried as i hardly have free time now..
this was a simple fix and now it workes perfectly for me.
sorry about the late replay.
thanks
I'm glad that it works for you
try this
try #9 on
http://forum.xda-developers.com/showthread.php?p=8046872#post8046872
You might be interested in my little APK (SGS Toolbox). I first created it to have it read the product code from the nv_data file to allow you to check whether it has been modified after a firmware update. But now I added some extra options, of which one is the option to check whether there are new firmware updates available in KIES by issuing the same request KIES does when checking for new firmware. This way you don't have to connect your phone to your computer all the time to check for new updates in KIES. Note: It sends JM1 as the current firmware version to find the latest. I might send the actual phone's firmware version once I figured out how to find it. See: http://forum.xda-developers.com/showthread.php?t=778244
Thanks, I'll give it a try
Deleted. Wrong thread.
Trying to enable AWS on Unlocked Rogers i337M.
Tried every possible thing but QPST does not see it on COM Ports. Phone was on NE1, I Odin Flashed it to NC1 but no use.
Tried different phones and all are recognized the second they are plugged in except this one.
A week ago I enabled AWS on the other i337M from rogers that was doing the same thing (Not being recognized by QPST) but can't remember what I did, that QPST started to recognize the phone and still does when I plug that phone in.
I would appreciate if someone could let me know how to make QPST recognize it. I've tried different computers, installed reinstalled Samsung drivers, factory reset phone, enabled disabled apps but no use.
Had same problem here...
BigBigBoss said:
Trying to enable AWS on Unlocked Rogers i337M.
Tried every possible thing but QPST does not see it on COM Ports. Phone was on NE1, I Odin Flashed it to NC1 but no use.
Tried different phones and all are recognized the second they are plugged in except this one.
A week ago I enabled AWS on the other i337M from rogers that was doing the same thing (Not being recognized by QPST) but can't remember what I did, that QPST started to recognize the phone and still does when I plug that phone in.
I would appreciate if someone could let me know how to make QPST recognize it. I've tried different computers, installed reinstalled Samsung drivers, factory reset phone, enabled disabled apps but no use.
Click to expand...
Click to collapse
Just type *#9090# and switch back to DM/DUN over HSIC... You probably switched it to DM/DUN over HS-USB when doing the unlock and forgot to switch back...
Cheers!
I am new to posting, but I have followed XDA for a long time and used it to install custom ROM's on other phones. However, I now have a problem with my wife's Samsung Galaxy GT-S5360L. I have searched for hours, but can not find a solution.
The phone is stuck in a boot loop. I can enter stock recovery mode. When I try to perform a factory reset, I get the following message:
E:format folume: rfs format failed on /dev/stl11
formatting /cache
Data wipe complete
After wiping the cache partition, the phone continues to be stuck in the same boot loop after reboot (Samsung logo appears on screen, followed by animation, back to Samsung logo).
The phone will not enter into download mode. When I press power+volume down+home, I see a white screen, followed by a black sreen, followed by another white screen. the suggested method of removing the battery, SIM, and SD card, and plugging into the computer while holding both volume buttons does not work. Odin will not recognize that the phone is connected.
I tried to connect the phone to two different computers. One runs Linux mint with Windows XP on a VM. This computer has always worked for flashing ROM's to other phones. Odin would not recognize the phone, and I received messages that the device was not properly installed.
I then tried to connect the phone to another computer with Windows Vista. This PC has Kies installed and Samsung drivers. Kies would not connect to the phone, and I also received messages that the device was not properly installed. Odin would not recognize the phone. I should note that the phone has interfaced with this computer sucessfully before.
This phone has never had a custom recovery or ROMs installed. It only has the original stock ROM. Is the phone's hardware defective, or can it somehow be fixed? Please post any links to threads that I may have missed. Thanks.
Download mode is only effected by a change in bootloader normally by Flashing incompatible firmware or a hardware fault
For flashing via odin kies is not required - its useless as it's not compaitable with the galaxy y for this purpose
You just need the Samsung USB drivers available from my firmware thread (links in signature)
It maybe possible to still flash the device
Once USB drivers installed
Enter download mode
Connect USB to pc
When the white screen appears push Vol up
Wait a few seconds
Open odin
Put the 3 firmware files in their places & flash
If it doesn't flash you will either need to flash a new bootloader via a jtag (repair shop) Or replace the motherboard - either way unless you can get it done very cheap it's more economical to buy a new phone
Thank you marcussmith2626 for your sound advice. The phone is working again. I will share the problems I solved in order to flash the stock ROM. Hopefully this will help anyone else that may have a similar problem.
The Samsung USB drivers had been previously installed on my PC running windows vista. I installed the drivers so that I did not have to use the bloated Kies software. However, when I tried to connect the corrupted phone to the PC via USB, it was not recognized, even though the correct drivers were installed. Below is the procedure I had to follow in order to connect the phone:
1. I connected the phone to the computer via USB. The phone had the battery installed and was powered off. After connecting to the computer, the phone started charging (battery icon on screen). Connecting in download mode at this point did not work. The phone must be powered off.
2. When the "found new hardware" notification box appeared, I had to make a note of each device that had been discovered.
3. I then had to open Device Manager from the control panel and find each device (the name in Device Manager matched the name in the new hardware notification).
4. I right clicked on each unknown device and selected "update driver software"
5. In the next menu, I selected "Browse my computer for driver software"
6. In the following menu, I selected "Let me pick from a list of drivers on my computer"
7. This brought up a list currently installed drivers. I selected the Samsung phone driver.
8. The driver then installed for the selected device..
9. Steps 2 through 9 were repeated for each new device discovered by Windows (each device listed in the "found new hardware" dialog).
10. I started the phone in boot mode (power+home+volume down, phone still connected to PC). I saw only a white screen. However, when I pressed the volume up button, the phone connected to the PC. Odin recoginized the phone and the stock ROM was flashed.
So, even if you only see a white screen, download mode can still be active. In my case, the drivers on the PC were not working correctly, probably due to the corruption of the original stock ROM. The drivers can only be added on my PC using the above method. The option to choose from a list of currently installed drivers was not available from the found new hardware wizzard.
Also, I will also say for reference that in the USA, the stock ROM from Brazil is the one that should be used so that the phone broadcasts on the proper GSM frequencies.
Hi,
I have an AT&T Galaxy S4. There was a water issue and for a time we thought it was completely dead. We tried the bag with the rice and sure enough, it was able to charge and turns on. For while, it was in a loop until I wiped the cache through the recovery menu. My phone is stock and using Android 5.01 and the model is the SGH-i337. If I plug in the cable tot he computer, it charges the phone, but it will not recognize it as a mobilde device. I have tried different USB cables, tried using KIES to reinstall the driver software, etc.. I did finally notice that my Devices have a Qualcom Modem installed and since my computer doesn't have a modem, I figured that must be it.
Reading other posts about dial screen codes, I've plaid around with changing some of the USB settings, but there is apparently a way to change from modem to PDA. Can't find a way to access that menu.
Is there anything else I can do? I also tried manually installing the Samsung USB driver manually, but it will not recognize the phone. I realize the water might have done more damage that what appears on the surface, but if it connects, charges and identifies it as a modem, I figured what better place to ask, but here with the experts!
Thank you in advance.
Guys could anyone help me?
My phone is Samsung A8 variant A800i non-rooted and already 6.0.1.
Eversince I upgraded to MM thru ODIN I am encountering an error in my OTG as in it won't read any disk... the only resort to make the otg work again is to reflash my phone. However during the most recent otg failure, a "USBsettings has stopped" was shown. I factory reset my phone but still this notification appears everytime I start my phone. So when I decided to reflash my phone, I was shocked that my laptop only charges my phone. It can't even detect my files thru mtp connection.
I tried the following and my laptop still can't detect my phone:
1. At the Developers Option I tried to switch the USB Configuration from MTP to Charging to MTP and various other switching, while connected and unconnected to laptop.
2. Dialled *#0808# to reset USBsettings but I am only getting "USBsettings" has stopped.
3. I reinstalled the USBsettings.apk from the system folder (via total commander).
4. I have installed USBsettings.apk taken from another phone.
By the way before I tried the above methods I have already eliminated the cable and pc problems since using the same cable and laptop, I can connect my other samsung phone thru mtp and is detected by odin. I have also tried various other desktop on Windows 7 and 10 but still the same problem: these only charges my phone.
Moreover, there is no abnormality in my charging time eversince this happened.
Hope someone could help me make this work again.
Thank You.