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.
Related
So I had my phone rooted, and removed some of the ATT apps using instructions from here: http://androidforums.com/samsung-captivate/124736-t-bloatware-getting-your-way-delete-some.html
After doing all this, the phone still worked fine, but as of today I can't seem to connect via USB. ADB doesn't see the phone, and even if I disable USB debugging and attempt to just connect as mass storage, the drives don't show up in my computer like they used to.
I attempted a windows rollback to just before I installed the drivers, then reconnected the phone, but I did not get any message about unknown devices, and the phone doesn't seem to be in my device manager.
Can anyone help me out here?
Edit: Running Windows 7 x64
you erased something you werent supposed to. dl the dump posted here & move it to an Micro SD. Put it in your phone and use a program to move it from external to internal memory then load back all the apps you deleted.
If I had deleted something, shouldn't USB connectivity have died right after I did that, and not after a night of doing nothing with the phone?
Either way, How exactly would I go about restoring from that stock dump that was posted?
Mine is doing the same thing. Had a hard time with the windows 7 drivers to begin with though.
I am going back to XP when I get home. Will see if it will recognize it then.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hm, an update on my situation: 3g watchdog died on me a couple times (gave me the popup, asked me to force close), so I decided to reboot the phone, and now everything works like it used to. I had also restarted my PC since the last time I tried (and failed) to connect over USB.
So if anyone else is having similar problems, I guess try rebooting both the phone and your computer.
I'm going to be keeping a copy of that "Rooted Stock System Restore" update.zip on my phone from now on, just in case.
The first Captivate I got from AT&T did the exact same thing right out of the box. I actually had to return it for another unit. Hopefully that was just a freak thing though.
I had a similar issue with windows 7 when I was first trying to connect via usb. Not sure if this will work for you, but I had to plug it into my rear port, the front ones didn't work just for the captivate.
Sent from my SAMSUNG-SGH-I897 using XDA App
it seems im having the same probs too i removed the att stock apps that were in one of the posts, im downloading samsung kies atm to see if that will help...
Edit, it did...windows and ADB redetected it.
I also rooted my Captivate and removed all of the AT&T crap. USB connection is still working fine under Windows 7 x64. Didn't install Kies or drivers either.
Halleleujah!
I had the same problem. Got this file from Samsung, and it worked on my Win7Ultimate 64 bit machine.
Try making sure you are back to touch wiz and see if it works... Worked for me.
I had some issues trying to get my phone to connect also ...
Windows Vista64 Ult.
Initially the MTP driver would hang when the phone was connected, and then eventually it would indicate that the installation was successful, then it would re-install itself after about 5 minutes. This was an endless loop which was severely draining of my system resources causing other applications to hang as well. I removed the drivers and ...
I downloaded the USB drivers from Samsung and installed them, when I connected the phone the computer did not recognize it, nor did the display on the phone indicate that it was plugged in. I tried several different USB ports.
I then changed the mode to mass storage and the phone was recognized, but both the internal and my secondary memory cards displayed 0 bytes free of 0 bytes available.
I downloaded the UK version of Kies, this was an utter waste of time. The Kies utility was not able to connect to the phone at all. I mass storage mode Kies displays an alert that it is not compatible, and the same goes for media player mode. If left in Kies mode the phone displays "connected", but the Kies utility just displays "connecting" and never progresses. Uninstalled Kies, and re-installed the Samsung driver ...
Connected the phone in Media Player mode, which is allowing me to access both memory locations without difficulty. Though windows pisses me off every time I connect the phone because it wants to sync windows media center with the phone ... though this is easily ignored.
Has anyone gotten the Kies utility to work with the captivate?
Battlehymn said:
I downloaded the UK version of Kies, this was an utter waste of time. [...]
Has anyone gotten the Kies utility to work with the captivate?
Click to expand...
Click to collapse
Try the Canada version, that's been working great for me, in Kies mode and all.
I had the similar kind of issue, look for the thread with ODIN and windows drivers, that is what worked for me...
Hi everyone!
I've got an Apollo (GT-i5801), and after a successful root using z4root, i can't use my phone with Kies. It worked great before root.
When i connect it to the pc, the phone is recognized as an SD card( fine!) but with Kies, the "Connecting" option stays there forever...
Any help?
Thx
Try it without sd card. you can't access your files with kies now but you can upgrade when it's time.
Humpie said:
Try it without sd card. you can't access your files with kies now but you can upgrade when it's time.
Click to expand...
Click to collapse
It's the same... no connection.
Should i unroot it, to update with Froyo, using Kies?
I think you should try
Froyo?
?
i had same problem with kies few days ago after installing froyo on my galaxy 3... problem solved with "reinstall driver" option in kies...
martin.jeremic said:
i had same problem with kies few days ago after installing froyo on my galaxy 3... problem solved with "reinstall driver" option in kies...
Click to expand...
Click to collapse
Didn't work for me.
mine doesnt work too after flashing 2.2 froyo... tried to reinstall driver doesnt work too
not that i care for kies anyway
AnyDroid said:
Didn't work for me.
Click to expand...
Click to collapse
infestedd said:
mine doesnt work too after flashing 2.2 froyo... tried to reinstall driver doesnt work too
not that i care for kies anyway
Click to expand...
Click to collapse
disconect phone from usb, select "driver recovery" option in kies and wait for it to finish... then connect phone to usb... that's how it worked for me... when i tried to reinstall drivers with connected phone, it just do nothing....
martin.jeremic said:
disconect phone from usb, select "driver recovery" option in kies and wait for it to finish... then connect phone to usb... that's how it worked for me... when i tried to reinstall drivers with connected phone, it just do nothing....
Click to expand...
Click to collapse
I've tried that way, didn't worked
i dont know if was martin tip, or an update on kies
what worked for me :
try to disconect the phone, reinstall drivers (do that after kies update, if you need to)
dont set the phone to ask on connection what to use (mass storage, kies, internet) but set it to connect directly on kies
start kies, and plug the phone
worked for me
Did you verified that USB Debugging was unchecked ? because when it's checked there is no connection possible using USB port neitherfor OS or KIES?
I am also facing the same problem with my I5801. Initially I rooted with z4root 1.1. version later I felt its because of the old version. Later I installed latest Z4root 1.3 version and re-rooted it but no use. My phone is not at all getting recognised (though I get a sound from my phone after connecting to pc but there is no option to choose KIES or Mass storage etc. It simply getting charged)
The KIES didn't recognise my phone even after connecting it to PC.
Later I tried
http://www.careace.net/2010/08/25/how-to-fix-samsung-kies-connection-problem/comment-page-5/
Though not of much use nothing happened.
Even I tried (Dial part in the below link)
http://forum.xda-developers.com/showpost.php?p=8667486&postcount=524
Fortunately this time my KIES recognises some unknown phone is connected but it mounts my phone in Memory card mode. Though I couldn't do much in this mode, this might help some of you to understand the problem deep enough to solve the issue. Thanks.
P.S. Though connecting to KIES is not of much use as we can back up data with some other apps but the major concern here is if in case (no hopes though) Samsung releases official firmware then we should have to use KIES to upgrade our OS version, then we will be in trouble.
After rooting with FuguRoot, Kies can't find my phone either. This seems to be a known issue but nikademus hasn't replied in his thread for some time now. Does anyone know why this happen and how to fix it? It seems a bit strange seeing how everything but the added su and busybox is stock..
Maybe some cache issue?
I can verify on that. After rooting my phone to make a backup with Titanium backup before upgrading with Kies, just to be on the safe side Kies doesnt work anymore with my galaxy3.
I tried unrooting the phone, but it did not help.
Strange thing is, that the usual information on the phone screen, saying that it is now connecting to the Kies did not show up. I did som trick like writing *#723572# (not pretty sure anymore what it realy was) and then setting it to modem and back to pda mode. Now I see the information saying on the mobile screen that it is trying to connect to samsung kies, but it still does not work.
I tried it on a virgin computer running xp sp3. I installed the newest Kies, than connected the phone, but now it says, that the connected phone is not in Kies (or Pc connect) mode, and I should change it to that. However the galaxy 3 screen says that it is definitely in Kies usb mode.
I will try later a factory reset and then an update through Kies to the latest fw. And after that a restore with Titanium backup.
sikolymester said:
I can verify on that. After rooting my phone to make a backup with Titanium backup before upgrading with Kies, just to be on the safe side Kies doesnt work anymore with my galaxy3.
I tried unrooting the phone, but it did not help.
Strange thing is, that the usual information on the phone screen, saying that it is now connecting to the Kies did not show up. I did som trick like writing *#723572# (not pretty sure anymore what it realy was) and then setting it to modem and back to pda mode. Now I see the information saying on the mobile screen that it is trying to connect to samsung kies, but it still does not work.
I tried it on a virgin computer running xp sp3. I installed the newest Kies, than connected the phone, but now it says, that the connected phone is not in Kies (or Pc connect) mode, and I should change it to that. However the galaxy 3 screen says that it is definitely in Kies usb mode.
I will try later a factory reset and then an update through Kies to the latest fw. And after that a restore with Titanium backup.
Click to expand...
Click to collapse
Try unmounting your MicroSD card (Settings -> SD Card and Phone Storage -> Unmount SD Card) and then connect it to PC.
If you're on windows 7==> Kies, preference==> check: compatible with windows xp (service pack 3)
Hi,
I am trying hardly to connect to the PC when the phone is in download mode. All the time the PC(doesn't metter in XP or W7) is telling me that the USB is not recognized.
When I am connected normally it's working and I can connect with Kies.
What's going on?
BR,
Mircea
PS: I'm trying to update the i9000 software to I9000XWJS8
Update your USB drivers (Samsung ones) with Kies closed and try again. I only had this kind of problem while using old/bad USB drivers.
Options
Have you tried:
1) Battery out then immediately into download (its a little tricky with holding all the buttons and sliding in the battery).
2) Reinstall the drivers as suggested - not from kies but the independent drivers.
and remove and reinstall of kies is another avenue to try.
3) You could try to do the whole android adb thing (see info elsewhere) and push the phone into download (I think). Useful for troubleshooting at least.
4) try cleaning the usb port with alcohol (never hurts and might cause some issues if it is dirty).
5) changing the connection order (usb in computer and phone, then on/download then connect/download with usb in and reboot computer etc). And if you are using odin add that in the mix too (load after connected, load before)
6) sim card and sd card in may effect the download mode (I think I read that when I was trying the same - only I had no recognition at that time).
7) if you need Odin, you could try heimdall in ubuntu as another option.
8) try various usb ports (ie on the back of a desktop - no hubs)
Going though all of these takes a long time and I know how frustrating it can be.
If it were me doing it again with another phone I would try drivers/re and re kies/ clean port and try back of the computer first. You can likely do all that in about 20 minutes. I'd go right to ADB to see if it can see the device. I think it also installs its own driver which might help too.
Good luck, let people know what worked.
Hi,
Thanks for the answers.
I already updated USB drivers several times from Kies. From where should I take the indepedent of Kies USB drivers?
I tried with all USBs from my PC and laptop....
Thannks,
BR,
Mircea
try here
http://forum.xda-developers.com/showthread.php?t=961956
I did not check if the link was active but it seems recent. I know I got mine off softpedia several times (It was a long time before I solved my own issues!).
On re reading the post where it is sort of recognized from the PC, I would definately clean the port with alcohol if the new drivers don't work right away. Once I did that for mine I had like 7 drivers install right away. That usb connection seems very finnicky on the i9000.
If you don't have rubbing alcohol handy you might just try blowing in the port or compressed air on the off chance that is enough.
If Kies picks up your connection via USB .
Then open Kies shrink it go to download mode and connect USB see what happens .
jje
Same things happened to me. So i conected the phone first to the computer (it was off), and then put it into download mode.
Otherwise you can try the app "spooffw" to spoof Kies2 and update the phone to XWJS8, like i did it.
This has worked for me several times.
Problem - Kies stays in connecting mode forever.
Reason - Think I once had Odin and Kies open at same - seems to mess up drivers and connection.
Solution:
1. Make sure Odin is closed.
2. Put phone into download mode.
3. Start Kies with phone connected to PC in download.
4. Leave it to install drivers. This may take a few minutes, be patient)
5. Disconnect phone from PC and reboot
6. Ensure USB debugging mode is off
7. Ensure nothing is running on phone and you are on home screen
8. Connect phone to PC and run Kies
9. It should connect.
This has worked for me several times.....I hope it works for anyone having this problem. If it doesn't please don't flame me. If it does, please hit the "thanks" button.
Best of luck!
What worked for me was using the default TwLauncher instead of LauncherPro. Don't ask me how this fixed my problem, but it did!
Also make sure Bluetooth is off and no apps are running in the background (use the built in Task Manager for this)
lolturnip said:
What worked for me was using the default TwLauncher instead of LauncherPro. Don't ask me how this fixed my problem, but it did!
Click to expand...
Click to collapse
The problems most people appear to be having connecting to KIES are with standard phone setup after dabbling with Odin. I first encountered the connection problem after forgetting to close Odin and opening Kies, even after reinstalling drivers. Hence me connecting my phone in a few different modes to see if drivers got sorted...and it appears they did !
I really hope my solution helps others out too
Hiya. Been reading and trying these solutions.
My wife's SGS2 will not connect to Kies no way no how. Tried all of the available solutions. It will not connect to NPS either, although NPS sees the internal and external storage and media but not the phone to be able to upgade to Android 4 which is supposed to be out this week on Orange.
Any help appreciated.
I am using windows 7 Ultimate and the phone is stock orange
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.