Database Users

For those who can't connect with Kies

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.

No usb connectivity in any mode after flashing stock rom

Hello all,
I have a Samsung galaxy S II purchased in Israel from Cellcom.
In my ill advised attempt to unbrand, and thus accelerate, improve memory and battery consumption, I flashed a stock ROM which I believed to be the latest.
The phone works great, with one exception. There seems to be no way to connect it to PC, be it WIN7 32bit or ubuntu 32bit. original usb cable or other cable, my stationary workstation or my laptop, be it USB Storage mode, USB Debugging, that stupid Kies mode, and most importantly because i'd like to flush it back, no Odin Mode. (in win32 - any mode gets "unknown device" status like the device doesn't publish it's name correctly or similar.)
moments before the flash the phone connected in all modes.
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
SO some info - and what I have already researched.
from http://forum.xda-developers.com/showthread.php?t=1113928, I gather that the PDA on my Cellcome bought SGS2 is either JIKG3 or JIKJ1. and that it's a GT19100T and I gather that denotes some kind of hardware specification.
the ROM I've flushed to my phone has this name:
GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5
everything seems wrong about this ROM in hindsight but, the worst is that it has no T, and probably isn't very hardware compatible. (though the telephony, wifi, camera, sensors and anything I tried works).
The phone is not rooted as after flushing I have lost any USB connectivity. I therefore cannot try and manipulate system files, to try to recover that way.
I have tried to root with the exploit apk. to no effect. I gather it's a statistically challenged way of rooting so I'll try my luck a lot more during the wait for your answer, and report any success.
**Edited**
the "Easy Rooting Toolkit" on http://forum.xda-developers.com/showthread.php?t=1319653
I'll try to run it as best I can, with the shell emulator, instead of on adb, but with debugging enabled.. although it's not a very East Toolkit, when I use it this way..
I'll still report any progress..
**/Edited**
I have seen no one on the internet with this problem. it's really a very stupid problem to have. but a problem nevertheless.
Any insight as to the moves I can try next will be greatly appreciated.
Any information I can add with my limited usb connectivity will be gladly shared. (my "Kies air" works so I can upload to storage that way.. plus i have a shell emulator installed..)
Regards,
Alex.

In ur Device Manager dose it show several unknown devices when connected?

teenvista said:
In ur Device Manager dose it show several unknown devices when connected?
Click to expand...
Click to collapse
just the single one.

There is absolutely nothing wrong with the ROM itself as I have been using it on my phone for a couple weeks now.
The problem exists between your phone and your PC, the PC is stating that it's an unknown device after all.
What I would try is to un-install the device in Device Manager, unplug the device and restart the PC and then plug the phone in again, if that does not work, I would throw in a factory reset of the device itself while repeating the above steps

I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
Click to expand...
Click to collapse
What do you mean by that? The nexus drivers have nothing to do with the galaxy drivers. Only if you run an AOSP rom you will need those drivers. Not if you run a stock rom.
Am I right that your pc sees the phone, but does not recognize it? Did you try reinstalling kies? And then from within kies tried to reinstall the phone drivers?

your PC may not recognize the device after the radio or kernel is changed. what I did was uninstall every single usb device from device manager and reboot, fixed.

Reply to all
jamesyb0i said:
your PC may not recognize the device after the radio or kernel is changed. what I did was uninstall every single usb device from device manager and reboot, fixed.
Click to expand...
Click to collapse
jamesyb0i - I saw that some people have been successful after uninstalling all usb devices, I'm challenged in this task as my keyboard and mouse are USB. I will try it on my laptop as soon as I'll get access to it, though because of the wide range of computer and OS I've tried I'm pretty sure the effort will be ultimately futile.
Lennyz1988 said:
What do you mean by that? The nexus drivers have nothing to do with the galaxy drivers. Only if you run an AOSP rom you will need those drivers. Not if you run a stock rom.
Am I right that your pc sees the phone, but does not recognize it? Did you try reinstalling kies? And then from within kies tried to reinstall the phone drivers?
Click to expand...
Click to collapse
Lennyz1988 - I see your point about the ADB Driver for the Nexus S, but as for the other advice.
As I said, I extensively tried to run it on multiple PC's multiple OS's.
I did try to uninstall / reinstall kies, and kies drivers.
after that didn't help. I got an SGS2 from a friend, just to try it on my computer.
it worked just fine.
achillies400 said:
There is absolutely nothing wrong with the ROM itself as I have been using it on my phone for a couple weeks now.
The problem exists between your phone and your PC, the PC is stating that it's an unknown device after all.
What I would try is to un-install the device in Device Manager, unplug the device and restart the PC and then plug the phone in again, if that does not work, I would throw in a factory reset of the device itself while repeating the above steps
Click to expand...
Click to collapse
The problem I believe is specifically because of the GTI9100/GTI19100T differences
I'm sure as achillies400 said that there is nothing wrong with the ROM itself. BUT the problem is not with my PC's it is more likely the different hardware, and the hardware driver on the phone itself that makes my phone become an "unknown device".
Regards,
Alex.

You could try this exploit.
http://forum.xda-developers.com/showthread.php?t=1296916
Don't know if it will work for you but it's worth a try.
Extract the .zip to /data/local/ on your phone and run the commands.

alex.feigin said:
Hello all,
I have a Samsung galaxy S II purchased in Israel from Cellcom.
In my ill advised attempt to unbrand, and thus accelerate, improve memory and battery consumption, I flashed a stock ROM which I believed to be the latest.
The phone works great, with one exception. There seems to be no way to connect it to PC, be it WIN7 32bit or ubuntu 32bit. original usb cable or other cable, my stationary workstation or my laptop, be it USB Storage mode, USB Debugging, that stupid Kies mode, and most importantly because i'd like to flush it back, no Odin Mode. (in win32 - any mode gets "unknown device" status like the device doesn't publish it's name correctly or similar.)
moments before the flash the phone connected in all modes.
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
SO some info - and what I have already researched.
from http://forum.xda-developers.com/showthread.php?t=1113928, I gather that the PDA on my Cellcome bought SGS2 is either JIKG3 or JIKJ1. and that it's a GT19100T and I gather that denotes some kind of hardware specification.
the ROM I've flushed to my phone has this name:
GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5
everything seems wrong about this ROM in hindsight but, the worst is that it has no T, and probably isn't very hardware compatible. (though the telephony, wifi, camera, sensors and anything I tried works).
The phone is not rooted as after flushing I have lost any USB connectivity. I therefore cannot try and manipulate system files, to try to recover that way.
I have tried to root with the exploit apk. to no effect. I gather it's a statistically challenged way of rooting so I'll try my luck a lot more during the wait for your answer, and report any success.
**Edited**
the "Easy Rooting Toolkit" on http://forum.xda-developers.com/showthread.php?t=1319653
I'll try to run it as best I can, with the shell emulator, instead of on adb, but with debugging enabled.. although it's not a very East Toolkit, when I use it this way..
I'll still report any progress..
**/Edited**
I have seen no one on the internet with this problem. it's really a very stupid problem to have. but a problem nevertheless.
Any insight as to the moves I can try next will be greatly appreciated.
Any information I can add with my limited usb connectivity will be gladly shared. (my "Kies air" works so I can upload to storage that way.. plus i have a shell emulator installed..)
Regards,
Alex.
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!
I have the same problem, and I couldn't find anyone else w/ it or with answers either.
almost all the same scenario except I have an SGSII AT&T I777 that started out as UCKJ1 and is now UCKH7
My phone started coming up as unknown device. I can not find any remedy to the solution.
Here's my scenario: http://forum.xda-developers.com/showthread.php?t=1372171
My guess is I might try to uninstall "new" programs that I added to the phone and PC, uninstall kies etc. and drivers, and maybe try and do a restore or refresh or something on my phone and see if I can get to "scratch" and re-start from there.
I installed winamp on phone and reinstalled it on PC for wifi, and it kept mounting/unmounting my SD card from phone to computer each time I plugged it in (I think that messed with my card possibly giving it "unknown")
Or also when I changed my Kernel may have made the phone unknown. Those are the only 2 changes I can assume did this to my phone =/

any update on your phone?
UPD: My kernel was causing all my problems. Restored to an earlier backup and it had older kernel. All problems were relieved.

N4 not showing up at all on PC

I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!

Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.

Make sure for windows media player to be updated to the latest, for the windows mtp driver.

duraeas said:
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Click to expand...
Click to collapse
There are a few things you can try. Have you tried uninstalling the drivers completely then reinstalling from the toolkit? In the past, I've had issues where the phone wouldn't be accessible in some way on one computer but would be fine on another, so maybe try a different computer to try to narrow down the problem as to whether it's an issue with the phone or the computer? Also, this may sound a bit ridiculous, but simply switching USB cables and / or ports has fixed detection issues for me in the past as well--something to consider.
Sent via Morse code from my Nexus 4

Remove any existing drivers (while phone is connected), do the same for other android devices if you have any, then reboot and install Universal Naked Drivers. Have always had success with this driver pack.

Rizy7 said:
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Click to expand...
Click to collapse
100% sure on both counts.

I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.

I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.

YeledKaki said:
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
Click to expand...
Click to collapse
Thats not the problem, it doesn't give any option. It doesn't show up on the computer at all and only charges. It's the same for every computer.

yuriorkis said:
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
Click to expand...
Click to collapse
I'm thinking we've screwed something up with the phone's side of the MTP protocol - mine is totally independent of the cord/computer used. All the correct drivers installed.
Have you tried Factory Resetting? I'm really hoping this is a workable option.

If you have a recovery back up the current Rom and flash stock and see if it's working
Sent from my KFTT using xda premium

if the phone is locked with a pin/password/pattern unlock it.

I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD

my screen is cracked and phone is useless now (replacement coming tomorrow) can i connect it and wipe it back to factory before i have to send it out?

K0v4L said:
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.

yuriorkis said:
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
Click to expand...
Click to collapse
Is yours able to connect during Bootloader/Recovery? Fastboot/ADB have no trouble recognizing my device.
It's really odd that if these things work, meaning your USB connection is fine, replacing the all of software fixed nothing... unless MTP occurs at a much lower level of the OS (maybe kernel is corrupted?)

I've got a similar problem that others have posted - PCs not detecting my N4. I got it last Friday (2/1) from Google and after the registering process and updating to 4.2.1, I connected it to my Win7 laptop and it showed on the PC as a drive. But since I couldn't copy/paste Office docs to that drive and had to do that through Dropbox, I didn't bother trying to reconnect until Monday, at which time the PC didn't detect it. Neither will one other Win7 nor two XP (both with WMP10) PCs. Have tried multiple cables, all of which work with other Android devices (pre 3.0). I've seen several suggestions on this and other threads, but one major issue I'm having is that some of the fixes require enabling USB Debugging. For the life of me I can't find that option in the N4's Settings. Unlike my other phones, there is no Applications subcategory under Settings on my N4 (4.2.1, Build JOP40D). Can anyone help me find that option? TIA.
Edit - Found answer. Click on Build in About Phone setting 7 times. That activated Developer options. Now to try the fixes which require USB Debugging mode turned on.

[Q] Computer not recognizing phone when in USB Debugging Mode

I am trying to install the ADB drivers but my phone is not appearing in the device manager at all for some reason. I have USB Debugging mode turned on but all that pops up when I plug my phone in is the auto play that asks me if I want to open the device to view files. I have no android device listed in my device manager to install drivers to. I have tried on two different computers and my phone is not recognized.
I have the google edition on 4.3

have you tried a different usb cable?

jedinegotiator said:
I am trying to install the ADB drivers but my phone is not appearing in the device manager at all for some reason. I have USB Debugging mode turned on but all that pops up when I plug my phone in is the auto play that asks me if I want to open the device to view files. I have no android device listed in my device manager to install drivers to. I have tried on two different computers and my phone is not recognized.
I have the google edition on 4.3
Click to expand...
Click to collapse
Uninstall and then reinstall Kies and try again bro, that should work bro.

Try a different cable. Had an issue was GNex where it charged fine, connected to the computer okay, but couldn't get adb or use odin. Spent hours trying to figure it out, uninstslling, reinstalling, and rebooting everything under the sun. Then thought maybe, just maybe it might be the cable. Swapped it out, and it worked like a charm.
Sent from my SCH-I545 using Tapatalk 4

[Q] Cannot connect in MTP mode anymore. Tried a lot, still no solution...

Hello everyone.
I don't know since when or how, since it has been always working for me on my win7 desktop, but when I tried to connect my phone to a new Latptop (with win8) during the holidays at home, it wouldn't detect it as an MTP device.
Well, it doesn't recognise it at all, unless I put it in debug mode, then it's under unknown devices as "Nexus 4" with a failed driver installation.
But I need to get MTP working to back some things up.
I'm running AOKP's Milestone for 4.3 and franco's kernel 193.
I checked if fastcharge was enabled: No
Switched it on and back off: Nothing
Reflashed the Kernel: Nothing
Reflashed AOKP (including the stock Kernel): Still not recognised
Of course several reboots included. Tried all slots and different cables. The cables tested all work for my N7 on Kitkat.
I had issues before with franco's kernel not really disabling fastcharge when I clicked it but I managed to fix that by rebooting or switching it back on and off again. Also this doesn't really give me any clues as I reflashed AOKP which comes with a different kernel that doesn't even support fast charge..
I'm kind of clueless now, I urgently need to back up things from my phone which I now did via Airdroid, but I also need to get MTP back working for bigger files.
Thank you very much for your help!
It would be nice if someone had a suggestion before I try going back to stock.

turn off driver signature verification(ask google how to do)
install universal naked drivers.
there you go

Will it then only be recognised in debug mode? Or normal as well? Since it doesn't even appear in device manager right now when in regular USB mode
Gesendet von meinem Nexus 4 mit Tapatalk

Try the way @opssemnik said, maybe your driver isnt work

andredn8 said:
Try the way @opssemnik said, maybe your driver isnt work
Click to expand...
Click to collapse
I had this problem. Try deleting all android drivers and MTP drivers from your PC using USBDeview (google it). Also try connecting to a different PC to see if the phone can connect at all. Finally, you may need to unlock the lock screen before attaching. After that it connects no problems!

jimbo34 said:
I had this problem. Try deleting all android drivers and MTP drivers from your PC using USBDeview (google it). Also try connecting to a different PC to see if the phone can connect at all. Finally, you may need to unlock the lock screen before attaching. After that it connects no problems!
Click to expand...
Click to collapse
USBDeview did the trick. Thanks a lot.