This is intended for people which run KIES and device is not seen, neither the message "connecting..." appear on KIES, and MTP application does not start on Samsung galaxy.
If you moved com.android.* and com.sec.android.* into some path which is not /data/data you may have this problem. At least this is what happend to me, after I moved file back MTP start and Kies recognize the device.
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
disabling launcherpro fixed it for me.
im told other launchers cause issues too
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Yes, you MUST run TWlauncher (standard launcher in Touchwiz) and if you got Windows 7, you might wanna download some third party drivers.
I'm on Windows 7 64bit and I downloaded the win7 x64 samsung galaxy s drivers form softpedia.
well the mtp driver doesnt install on my 64 bit computer.
It works on windows 7 32 and 64 bit just fine
No third party drivers and no magic. It's all down to individual system config otherwise it would be the same for everybody.
Incidentally, there is an update out for Kies taking it to version 1.5.1.10074_45
g0c said:
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
Click to expand...
Click to collapse
have you googled for FileSearcherforKiesFix and tried that? the only thing that fixed it for me.
Strange. Kies works fine on my both computers: Win7 x64 and WinXP. Had some issues before, but new Kies works without any issues.
hello all,
i got the gt-i9000 like 2 months back the kies s/w was workin fine for the first few days now the app itself fails to lauch even if the fone is not connected.
I have uninstalled and reinstalled kies s/w like a million times.
The installation is always successful but when i click on the kies icon to start the program nuthin happens :s
Please help.
Oh yeah i am running Win7 32bit legit.
BronzedDroid said:
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Click to expand...
Click to collapse
Works fine for W7 32bit flawlessly to. Also for me on 2.2 it works under launcher pro as well, added bonus of not having to use home switcher (or the like) every time I connect the phone
rocketpaul said:
well the mtp driver doesnt install on my 64 bit computer.
Click to expand...
Click to collapse
It works fine on my copy of Windows 7 64bit, but I have to switch to touchwiz, and go to driver recovery in the kies menu.
I use XP at home and at work.
From home with JP6 and Kies 1.5.3.10093_82 I can connect fine using a cheap USB cable and with phone having Samsung Kies as default running LauncherPro.
At work Kies cannot connect to the phone... it just says connecting, please wait.... all the time, its wierd...
I guess I have to remove all the USB hubs on the work computer.... Will install Windows 7 Pro 64 bit at work soon so... maybe ill just wait until then...
Kies not working with LauncherPro. You have to create a shortcut to MTP Application, when you connected the phone and selected Kies need to start with this shortcut.
This is the only way to connect Kies with LauncherPro.
Somewhere I read about this, LaucherPro not recognised like TW.
Hope this helps.
The only way I have ever ever gotten kies was following these steps:
1. Completely close kies
2. Connect your phone
3. Open up device manager, find I9000 (should be under portable devices), right-click and disable (if device manager lags after you click disable then unplug the phone)
4. Replugin the phone and wait for it to say connected on the phone's screen
5. Re-enable I9000 in device manager
6. Fire up Kies and it should connect
These steps have worked every time for me
ps: I'm on Windows 7 x64
http://arvindgaba.com/computer/sams...o-install-for-samsung-galaxy-s-kies-resolved/
Not tested but seems to be approved
I'm on linux so i never used kies. Jusi odin all the way and i have nothing to complain about
This issue has become rediculous. Samsung fail so much with this usb ****. I run Win 7 32 bit and kies previously worked and even when it occassionally wouldn't I used odin.
Now unfortunately the phone just isn't recognised even after various driver and spftware reinstallations and registry deletions etc... etc... etc....
If I enable USB debugging on my Verizon Galaxy Nexus and connect the phone to my Windows 8 machine, the PC crashes.
Has anyone else successfully connected to a win8 pc while in debug mode?
I have problems like this on my win8 too.
Windows 8, while it is in RTM mode, there is still a lot of work to be done on it. I would not recommend upgrading your desktop or notebook, unless you have a touch screen. Win8 is awful in my opinion, with some cool features.
Alehbye
Alehbye said:
Windows 8, while it is in RTM mode, there is still a lot of work to be done on it. I would not recommend upgrading your desktop or notebook, unless you have a touch screen. Win8 is awful in my opinion, with some cool features.
Alehbye
Click to expand...
Click to collapse
Sadly as an IT admin I don't have the luxury of "Skipping" OS's and must learn them whether I like them or not. I will test this out and get back to you OP.
Thanks. I don't mean for this to turn into the pros/cons of win8, I was curious if others had seen the same behavior.
The system looks like it tries searching for a compatible driver and crashes with a "Bad_Pool_Header" error.
For me windows 8 installed the correct drivers by itself all i had to do is enable it in device manager
Both of my Dell workstations crashed, but my Lenovo ThinkPad didn't. Appears to be hardware/driver related. I'll keep digging.
I also have the same problem and error. Any solutions?
had that problem only once, now it works fine
Sent via Tapatalk 2 from my GNex running CM10
vijaykd said:
I also have the same problem and error. Any solutions?
Click to expand...
Click to collapse
I resolved the blue screens by installing Samsung Kies which installs the USB drivers for the Galaxy Nexus. Afterwards Windows 8 (Pro RTM 64bit) correctly installs all drivers when using USB Debugging mode, no more blue screens.
tripmckay said:
I resolved the blue screens by installing Samsung Kies which installs the USB drivers for the Galaxy Nexus. Afterwards Windows 8 (Pro RTM 64bit) correctly installs all drivers when using USB Debugging mode, no more blue screens.
Click to expand...
Click to collapse
That seems to have fixed it! I even uninstalled the Samsung Kies software (but kept the drivers) and everything is working smoothly.
Thanks again.
Hi,
the touchscreen of my Vivotab RT is not working after booting Windows.
In recovery mode its working fine.
Reinstalling Windows RT did not help.
Anyone an idea?
THX,
sowath
You can plug a mouse to it, get to the device manager and look up for a touch screen device to see if windows sees it and if its turned off or something else is wrong
hello for all
i have samsung ativ 300t tablet it came with built in windows and with one partition the windows still update till win 10 then the tablet became too slow so i got to re install another windows win7 so i deleted the partition then create a new one through the windows setup suddenly it freezes so i installed win 10 through a usb
the problem now is win 10 didnt recognize the touch screen or the wireless driver or overall the tab it acts like a desktop
what are the solution for that should i go back to win 8 rt but i dont have a recovery for it also i saw recovery partition on the bios system and when i tried to recover it using win 10 it failed?
thx for all
Hi all,
I purchased a gemini wifi recently, but a 4g version arrived! I'm now trying to flash Linux on there, but I cannot get the flash tool to do anything.
I'm pretty sure that this is a driver issue, but I'm not sure what to do about it. I've tried windows 11 and 10, as well as ubuntu 20.04 to flash this thing and nothing is working.
On the windows 11 host I even disabled memory protection to allow the drivers to work correctly, but that made no difference.
Following the guides on planet computer, it's not clear what state the device should be in, but I've tried normally booted into android as well as in recovery mode (booted with Esc and side button depressed on boot}
What am I missing here? Does flashing this device just no longer work?
Thanks in advance for your help!
it still works presuming you are referring to this guide: https://support.planetcom.co.uk/index.php/Linux_Flashing_Guide
I unfortunately don't think I am able to help you debug the situation from the information you provided.
I am not sure where most of the users congregate, but I have seen some sporadic recent activity here: https://www.oesf.org/forum/index.php?board=192.0
From my own experience, windows 7 and windows 10 have worked flawlessly, ubuntu worked for me in the past, but had trouble recently. win7 and win10 in virtualbox requires delicate usb device setup adding device during gemini reboot, and still gives some trouble.
I haven seen any updates or security patches from planet on neither android nor debian, so got myself a sailfish X license to support their development, it looks like a lot of updates (most recently yesterday: https://forum.sailfishos.org/t/release-notes-vanha-rauma-4-4-0-72/ )
good luck