hi there, i am new here. recently i bought galaxy s. so far its amazing. since yesterday i cant connect to kies with my galaxy. do not know why. when i tried, its suck on connecting to device please wait screen. on my device it is said "Initialising" . after a long time when i disconnected, i cant browse to my internet sd card and phone memory. it is said unavailable at usb and sd storage. but i can connect to pc after a restart and change the usb settings to mass storage mode. i did not face any mtp error like others. and today my kies updated itself autometically. still i am facing the problem. i connected to kies so many times but from yesterday i have this problem. what should i do now? can anybody please help me?
Same thing happened to me, I had to remove long filename extensions from my sdcard see:
androidforums(DOT)com/samsung-galaxy-s/157617-solution-tutorial-galaxy-s-i9000-mtp-application-crashing.html
elbrendo said:
Same thing happened to me, I had to remove long filename extensions from my sdcard see:
androidforums(DOT)com/samsung-galaxy-s/157617-solution-tutorial-galaxy-s-i9000-mtp-application-crashing.html
Click to expand...
Click to collapse
i tried that before, but funny thing is, i does not even have com.seesmic folder on my internal sd card>android>data> . i set show hidden files from tools>folder options.
welcome to the world of Samsung!!
ok guyz i found out the solution. all you need to download microsoft remote desktop connection manager and its started to working again. i hope if someone have same problem as me, can solve it.
solution for me was click ontop left corner of kies, and choose restore/reinstall phone drivers. I highly doubt the suggest fix above.
kiwijunglist said:
solution for me was click ontop left corner of kies, and choose restore/reinstall phone drivers. I highly doubt the suggest fix above.
Click to expand...
Click to collapse
nah it works for me. i do not know what was the connection between two of them. but i think damn windows cant detect the phone cause of that. you can try also. ..............
but one problem still there. no matter how many times i connect to kies, every time after i disconnect my internet sd and phone storage are unavailable. so i need to go to about phone>usb settings>mass storage mode to fix this every time..................
well you guys want to know what worked for me?
So I heard that the official 2.2 was out, and so just like a lot of you, I tried upgrading my SGS using KIES...
I had firmware 2.1 on my phone and KIES couldn't / wouldn't recognize my SGS... just like the OP, it always stayed on "connecting device please wait bla bla bla" ... so I just went to samfirmware.com or whatever it's called .. and I downloaded the latest firmware 2.2 for my device, which was the I9000XWJPA, and flashed it on my SGS, after that I tried to connect with KIES again, and KIES finally recognized my SGS.. so I flashed the old firmware back onto my SGS(Eclair 2.1) because I wanted to use an official 2.2 firmware, so I was on 2.1 again and I tried to connect my SGS on KIES, and again it got stuck on "connecting device please bla bla bla" ... so I just decided to use the 2.2 firmware I9000XWJPA from samfirmware.com ...
and just now I've tried connecting my SGS on KIES and guess what? KIES recognizes my phone -_-
So long story short:
On firmware 2.1: KIES doesn't recognize my phone
On firmware 2.2: KIES does recognize my phone
all I have to say to that is:
Whatever Samsung!! KIES is one F*[k€d up program you've got there!! I'm not dissatisfied with my SGS or anything, but I do think this will be my last phone from Samsung...
Sigh, I hate Kies, it never works. Just installed it now and my S3 won't connect. Hangs. I rebooted device/phone followed connection settings.. no dice. Phone says connected, but Kies hangs as soon as the phone says connected. It gets unlocked if you hit disconnect on the phone... these guys really can't do software. I miss Nokia software.
Anyways.. uninstalled it.. and now I came across this thread.. should have tried reinstalling the phone drivers.. fudge. Oh well. I'll just do a OTA update of my firmware when the servers are less slammed.
Before you wipe any data or factory reset etc, you may want to try the following.
I know there are many solutions offered around the internet for this horrendous problem - if you are one of those poor people, like me, that get the constant trying to connect message, the MTP error message or if kies can read your phone and you get the 'can't update device' error - then hopefully this solution will help.
I myself have tried everything for many, many months. Downloading the new Kies software, uninstalling, reinstalling it, getting the latest USB drivers (both manually and using Kies), phoning Samsung, going to their Service Centre - all to no avail.
My phone was originally on Orange and I unlocked it to O2. This solution worked for me. And, best of all, you don't have to reboot, factory reset or wipe any data! Joy!
All you need to do is download a very simple utility software developed by one of the wonderful guys over on AndroidForums (I'm unable to post link, due to being a new member, but head over to Android Forums and search 'solution/tutorial galaxy s i9000 mtp application crashing html (will show thread title in bold, click on this) then scroll down a little way and look for the FileSearcherforKiesFix.zip file.
Once you have this utility, connect your SGS to computer via the usb cable, using mass storage mode. Run the utility and find the drive on the computer for the phone - it will search for files with characters of 16 or more. Once you find any go into the computer, find corresponding drive for the phone on the computer and delete this file. Run the application again to double check.
Now I will say that it is a good idea to take out any external memory cards before you run the utility and just have the phone drive to search.
Once you've done this, put phone back into kies mode and run Kies. If it doesn't connect up, do the above again; put phone into mass storage mode and run utility again. Sometimes files show up again after disconnecting and re-connecting. I found a total of four files, that's all! Make sure you definately delete them.
When you have done this, connect to Kies, again in Kies mode, and your phone should be recognised. You will then get offered any firmware updates.
Good luck - hope this works for you. Let me know.
So simple (took me 6 months to find this too!).
I will finish by saying that although my firmware updated, it was to a more recent 2.1 eclair version, as it seems apparently, Orange have not 'officially' released 2.2 for their phones as yet; have heard end of January!! What???!!
So patience patience patience!!
Good luck people.
Any questions please ask.
i have tride this for many times but still not working. i want to smash my phone
Just as a disclaimer up front, I haven't worked with Windows in years, I'm a complete Linux user, so don't assume I know anything. I'm not used to messing around with device drivers or searching for software on the web etc. Where Windows is concerned, I'm your 80 year old Grandmother, ok?
Ok, so with the Gingerbread firmware rolling out, I decided it might be time to try and get my Tab working with Kies. I got access to a windows machine, and went to work. Here's what I did (just in case I messed up somewhere):
Connected the Tab to the windows machine via USB, and selected mass storage device.
Windows mentioned something about needing drivers, which seemed weird (isn't the Tab a normal mass data storage device when told to be one?), but after a few seconds it claimed it was ready to use, so I went ahead and mounted it and could see my files in the Windows file browser. So far so good.
I then disconnected the Tab from windows and went looking for Kies. After some short struggle I was able to download and install it.
Next, I connected the Tab again, this time selecting 'Samsung Kies' mode. Nothing happened, neither on the Tab nor on the Windows machine.
Tried again, this time as 'Media Player'. Nothing happened.
Tried again, in Mass Storage Device mode. Kies tries to connect, then tells me to try again in Kies mode. I do so. Nothing happens.
After some googling, I try with the external SD card unmounted, as that seems to be recommended. No difference.
I told Kies to reinstall the device drivers. No difference.
I've rebooted Tab and PC. No difference.
What am I doing wrong? Can someone who uses his Tab with Windows maybe post a step-by-step howto?
I'm interested in this too as I'm having the exact same problem. If I connect as a mass storage device, I get an error that it needs to be in Kies mode. If I connect in Kies mode, Kies sees the device and shows the status as "connecting" but never actually connects. On the Tab, it says that it's connected though. I've tried this on Win XP and Win 7. Same behavior both times.
Interesting, you're already a step ahead on me. I don't get anything in Kies Mode, no connecting, nothing. I've tried on a 64bit Vista system and a 32Bit Win7 system, but no difference. In Kies mode, I don't even get the 'device plug in' sound in windows.
Care to tell me how you got Kies to at least see the Tab in Kies mode? What version of Kies are you using, etc.?
I'm using a rooted GSM (euro) Tab on Swisscom network and Kies V2.0.0.11014_49_2
I think I've cracked it. Firmware update is installing on my Tab as we speak.
What did I do? Seems really simple. I went to the Connections and Network Settings on the Tab, and in USB Connection Settings, I changed it from 'ask on connection' to 'samsung kies'. Upon plugging it in, it told me that it had to disable Bluetooth to enable the USB connection (never seen that screen before), so I allowed that, and windows immediately scrambled for device drivers and Kies show the connecting sign at the top left.
I'll keep you posted on how it went.
UPDATE: The installation process ran through, and Kies instructed me to disconnect and reboot my Tab. I did. However, it nows hangs during the boot sequence, at the stage where the blue 'SAMSUNG' logo is shown. From time to time, the Tab vibrates like it does when an application force closes, but it doesn't seem to finish booting. I fear I may have bricked my Tab. Trying to go through the recovery menu now.
Ok, factory reset from the recovery menu brought it back to life. No Gingerbread as of yet, but the XXJMF version of Froyo.
Rapax said:
Connected the Tab to the windows machine via USB, and selected mass storage device.
Windows mentioned something about needing drivers, which seemed weird (isn't the Tab a normal mass data storage device when told to be one?)
Click to expand...
Click to collapse
No, unfortunately not.
Back to the overall question - I had similar problems when I bought my Tab in the tail end of last year (Win7 64bit) and had to do some strange combination of attaching the Tab and starting Kies mode on the device before starting Kies on the PC (and dancing a jig while singing the Jingle Bells, you get the picture)
Today I installed the latest version of Kies and it all seems to just work. Therefore it might be worth updating your Kies version (or perhaps I'm just lucky this time through!)
I take it back, same old problem of never connecting unless I plug in the Tab before I start Kies on the PC, sorry for the noise!
I am having no luck whatsoever. I'm rooted if that makes any difference at all. My process has been going like this:
Plug Tab into computer. Wait until I see the screen that says Kies is connected.
Fire up Kies on my computer. Under Connected devices I see "connecting."
That is as far as I get. I never get further than that and I've tried it on Win7 (64 bit) and XP (32 bit) with the exact same results. I've re-installed the driver twice and rebooted both the Tab and the computer multiple times. Kies tells me it's the latest version so that's not an issue. Supposedly there is a Froyo update out there that fixes the screen orientation issue, but I can't get it. Frustrating. This should not be that hard. The fact that there are this many people all having the same issue just proves how half-baked this software is IMO.
Did you try without the SDcard? Seems Kies doesn't play nicely with external SD.
Rapax said:
Did you try without the SDcard? Seems Kies doesn't play nicely with external SD.
Click to expand...
Click to collapse
I didn't. I can't think of why that would make a difference, but I'll try it when I get home. Can't hurt anything.
Rapax said:
Did you try without the SDcard? Seems Kies doesn't play nicely with external SD.
Click to expand...
Click to collapse
Seemed to make no difference at all on the Win 7 machine or the XP machine. Goes to connecting and never actually connects. My Tab says it's connected. Kies never does connect on my Win 7 (64 bit) or on XP (32 bit). Frustrating to know that there is an update available that fixes issues I'm having, but I can't get it.
I've just got this problem too.
My solution: set the usb connect type in your tab to "kies" from "ask when connected". It solved my problem.
Sorry for my english.
[edit] Well, I read the whole thread and realised you found the same slution. Nevermind, at least I tried to help.
sisa7 said:
I've just got this problem too.
My solution: set the usb connect type in your tab to "kies" from "ask when connected". It solved my problem.
Sorry for my english.
[edit] Well, I read the whole thread and realised you found the same slution. Nevermind, at least I tried to help.
Click to expand...
Click to collapse
I tried that, but it didn't work for me.
I have factory reset and unrooted.
Removed the micro-SD card.
Changed to "ask when connected."
Nothing works. Same behavior. Kies says "connecting", but never connects.
I finally got my problem fixed. I had to take a 3rd computer, install Kies, reboot, plug in the Tab, wait for all the drivers to install except for the drive for the MTP device (this wouldn't install). Then I had to have it re-install the drivers, unplug the Tab and reboot it, then plug it in again. The thing finally connected and I was able to sync. Then it displayed a message that the firmware cannot be updated. Not sure if that means cannot be updated at the moment or if that means cannot be updated ever. Seems like a ton of work for nothing.
Update: just noticed that after the mentioned update, all the APN entries were gone. Had to set them up again by hand. No big issue, but annoying. I hadn't noticed until this morning, because I was on Wifi all weekend
I just got my AT&T Galaxy Tab and when I try to connect to Kies I get the message "This device is not supported by Kies 2.0." I checked for updates but it says it is the latest version. Anyone have any ideas?
I know this isn't helpful but KIES is very Flaky. I've never managed to get it working 100%. "Ask for connection type' almost always doesn't work. It's not worth the trouble as it's a completely USELESS app anyway.
For those who don't want to download the ADB drivers separately it's good for that then once the drivers are installed just uninstall and move on
ipit said:
I know this isn't helpful but KIES is very Flaky. I've never managed to get it working 100%. "Ask for connection type' almost always doesn't work. It's not worth the trouble as it's a completely USELESS app anyway.
For those who don't want to download the ADB drivers separately it's good for that then once the drivers are installed just uninstall and move on
Click to expand...
Click to collapse
But how can you install the Gingerbread update without Kies?
ufd108 said:
But how can you install the Gingerbread update without Kies?
Click to expand...
Click to collapse
I don't bother with Samsung provided updates. Just get my ROMS from right here and use ODIN Thanks to the wonderful devs (Ocome) on this site.
PS: Even if you want a stock GB ROM you can get it from here. No need for Kies.
http://forum.xda-developers.com/showthread.php?t=1074759
Me Too
Hi
Just a 'me too' post i'm afraid. I get the GT saying 'connected' in the MTP app, while Kies says 'Connecting....' forever more. Its REALLY anoying.
I am not interested in any non official roms (wasted far too much time on them on my various WinMo phones). I do want to be able to install an official Gingerbread update though.
My tab used to connect to Kies. It stopped connecting right after it installed an update (to FROYO.XYJJ3), and I have never managed to get it to connect since. I think Kies has a bug (one of many!) which means it will not recognise the current rom on my Tab.
I have tried:
- Removing SD card
- USB debug on/off
- USB connection set to Kies/Choose on Connect
- Reset tab to factory default
- Connect tab then start kies
- Start kies then connect tab
- BT On/OFF
- Wifi On/OFF
- Sim card out
- flight mode enabled
- packet data on/off
- Install kies onto 2 other completely fresh PC's Win7X64 and XP
Nothing has worked, says 'Connecting' but never connects. I'm about ready to just ebay the pile of junk and move on!
Kies version: 2.0.0.11014_49
Tab Build No: FROYO.XWJJ3
Kernel 2.6.32.9
Baseband: P1000XXJID
Tab version 3G+Wifi
Firmware Version: 2.2
Model No: GT-P1000
Been onto Samsung tech, but they are ruddy useless - no help what-so-ever (not that I expected then to be). How Samsung ever expects to compete with apple when their software is even worse than ruddy iTunes I just dont know.
Nigel
you have to switch to kies mode in the wireless/usb settings. Then before you connect the tab to usb make sure you on your home screen, else Kies mode will never start up. You can start up kies on the pc before or after you connect the tab doesnt matter. If the kies software never starts up at this point, uninstall, make sure the drivers have been uninstalled as well, reboot, reinstall kies. Start kies before you connect the tab as it may have to install updates, then connect the tab in kies mode. Ive used kies mini and regular kies with this method, works. As a side note, the full version of kies will not work with Stock US roms, it will always say phone not supported, so you have to use Kies mini.
Although I don't think i would rely on Kies to do a firmware update....if at all or successfully.
Ok so I purchased an i9000M that was advertised as broken (got it for cheap) to see if I could get it going for my step daughter. I turn it on.... I get the samsung boot screen and goes black when it should be booting OS.
Windows still recognizes it somewhat. If I look in device manager under "portable devices" It shows a "j" and "k" drive that are identified as i9000 and i9000 sd or something like that. Although Windows sees it.... It wont mount these drives unfortunately.
Things I've tried ( Before someone suggests I use a JIG............. It doesn't and will not work on this phone)
USB JIG (tested and working on my Hercules)
SD Card Partition (EXT4 and FAT32) because I suspect borked internal storage
SD Card Partition (ReiserFS and FAT32) Still nothing......... then I realized the phone probably wasnt rooted
3 button combos ( every single combination) nada
plugging in USB cable while holding volume up and down...
ADB Reboot recovery/download ( not recognized because I cant turn on debugging)
ETC ETC ETC........
I have been searching google for hours for some kind of clue as to what can be done other than JTAG repair and All I come up with (no matter what site im on) is " Use a USB JIG" duhhhh Its getting rather annoying.
Im no stranger to flashing ( no expert) but this one has me stumped. I was considering buying a RIFFbox anyways but I thought maybe some experienced users out there might be able to suggest something.
My hope is that something can be done with the J and K drive that was mentioned. Perhaps I can format and somehow push a rom straight to the internal storage without any assistance from the phone itself...... I know..... wishful thinking. or perhaps boot straight from external SD???? That would be interesting!
More to this.... I realize this question has probably been asked a million times because it seems to be a common issue on this phone but I suppose my long winded question really boils down to my last paragraph which I havent seen suggested yet.
EDIT: I have a Windows 7 AND kubuntu 12.04 dual boot if any suggestions require linux
Any help would be greatly appriciated.
kibosh1981 said:
Any help would be greatly appriciated.
Click to expand...
Click to collapse
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
xsenman said:
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
Click to expand...
Click to collapse
Thanks. i will have a look and experiment tomorrow.
I'll report back my progress
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
taz0697 said:
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
Click to expand...
Click to collapse
As I mentioned.... no download mode, therefore.... No ODIN. Unless someone has some magical way to make it work otherwise. The computer knows its an I9000 at least. Kies says its in the wrong mode and I have no UI so debugging is out of the question.
Also: Xsenmen. I was unable to get any of the tools to connect. In one section you mention that AndroPlatina attempts to connect while booting? I was unable to get this to happen. I even tried the "heat trick" to no avail
I've been running NG3 rooted for 2 years w/ T-Mobile. Due to recent changes on the Tmobile network (they dropped 1900 and switched to b12 = 700a which the 870 can't acquire) I've been forced to move to ATT. When their SIM was loaded I could get 4gLTE so data and text worked, but couldn't make or receive any calls. The signal would drop entirely - no 4gLTE or bars.
I decided I'd try to reload the full NE4. The PC wouldn't recognize the phone via USB (new and old drivers tried). I tried 3 PC's same issue device unknown regardless of Samsung driver age. My wife has the same phone and same issue. Since USB wasn't being recognized (nor on my wifes 870) ODIN was out so I booted and tried loading via the SD card. Well I apparently bricked my phone attempting this. It won't boot beyond the SAMSUNG logo (thereabouts). I can't access the phone via USB. I can however use the bootloader (?) (v-up + pwer + home) and attempt to load from the SD card. I have several stock roms but I receive errors attempting to load these - " footer wrong" and " signature verification failure". I tried Downloading them again but md5 is good on them all
I'm not having fun... . Does anyone know how I can get my phone to load from the boot screen without these errors? I need to get my wife's 870 working too. Her phone can text but no calls (same scenario only I didn't mess here's up just yet). The boot screen on my phone still shows last up date NG3.
I 'm not concerned about being rooted or which version I land on anymore, I'd just to get it working again. Any help is much appreciated - thank you
for what it's worth talking to myself ... the USB cable I've been using for years and has always worked. Tried it on my wife's phone and didn't work but still thinking it's the PC unable to load the USB drivers. Bought 2 new phones. Tried the cable on the new phone - no drivers. Tried the new USB cable that came with the new phone and it worked fine. Used the new USB cable on my soft bricked phone and drivers loaded. I was able to use Odin to upload the OF3 revision to my G870 successfully. Now I'm looking for a way to root it.
any links please?
You can search for "wonder share mobile go" and find how to root with it.
OMG - That was amazing. It rebooted a few times but "SUCCESS". I can't believe all the steps we go through on XDA (and I love XDA) to root a phone but this was 1 click = done. The OF3 can easily be rooted with this software. I uninstalled it (cause I don't trust it) but the root remained and I'm rocking and fat happy.... AND the KNOX = 0
ON THE OTHER HAND - the software soft bricked my Moto G5 Plus. It's not all it's cracked up to be. I contacted the company and it really seemed to me the person responding couldn't read English. Their responses were incoherent and didn't approach the subject at all. Like they were from another country. Yeah.. one of those companies who rely on foreigners to handle their tech support. I'll never use that software again - not trust worthy and the techs are clueless
Thank you very much