Related
I realize that this is a common issue, but I figured I needed to post it since I've exhausted all the options I know.
First of all, my phone is running stock JL2 with hardcore's K13a kernel - one day, it stopped getting recognized by my PC. All I would see was the message "USB Device Not Recognized". I need to connect my phone to my PC for file transfers and mp3 sync...
Here's what I've tried:
- All four options for USB connection
- Debugging on and off
- Uninstalling all USB Root Hub drivers and reinstalling
- Uninstalling and reinstalling Kies
- Installing USB drivers from the XDA forums
- Three different cables (I have extras)
- Three different computers (all of which work fine with my Captivate and used to work)
Any ideas?
I don't want to flash a custom ROM since it will kill the internal SD card (I have a Bell I9000M)
Any ideas on what could cause this issue randomly like this? Is there anyway to get it recognized in some other mode? Could it be related to my kernel?
Tried my last option (that I know of) and tried a different kernel (damienGTO's) but still getting the issue...
any suggestions?
Would really appreciate any suggestions...can't so much for my fiancee without this.
Sent from my Samsung Captivate SGH-I896
what do you mean when you say that if you flash a custom ROM since it will kill the internal SD card? flashing back to stock firmware is always best when it comes to fixing problems.
sfms said:
what do you mean when you say that if you flash a custom ROM since it will kill the internal SD card? flashing back to stock firmware is always best when it comes to fixing problems.
Click to expand...
Click to collapse
The Bell I9000M has faulty hardware, particularly with its internal SD card. I've gone through four of them. Although, boone knows the real cause, flashing custom ROMs seems to accelerate the problem. Regardless, this is the stock rom that I'm seeing problems on and a factory reset didn't fix it.
Sent from my Samsung Captivate SGH-I896
I'm kind of getting this same problem and it's pretty anger inducing. I recently had my first I9000m die out on me (internal sd problem, phone lasted 4.5 months!), and I just got my replacement from Bell. Now I can't connect this new one, despite any attempts at connecting, reconnecting, and installing and reinstalling drivers/kies.
It's killing me. I do notice I'm getting some MTP USB device installation error/failure when I try to connect the phone
Edit: I actually just tried plugging me new I9000m into my old no-longer-used laptop and the phone connected properly. My old computer has Vista, and my new main computer has 64-bit windows 7. Could be a part of the problem?
I thought it was a driver issue, but my Captivate connects fine. I've tried win xp and win 7 and have the issue with both.
Weird thing is that it stopped working randomly. Could it be a driver conflict?
Sent from my Samsung Captivate SGH-I896
Would really like some help on this... I can't connect ODIN, and therefore can't flash the stock firmware/kernel, and therefore can't return this for warranty...
Any ideas? I'm out of ideas...
Think you have gone through all the steps .
Service centre your next step .
jje
JJEgan said:
Think you have gone through all the steps .
Service centre your next step .
jje
Click to expand...
Click to collapse
Thanks... just needed validation.
I wasn't sure if I should try loading a Gingerbread ROM to see if that resolves the issue.. but it just seems more and more hardware related.
I also can't get a lock on GPS, despite having tried about 5-6 different modems. Hardware is failing here...
Hi,
I have a problem connecting my phone to Samsung KIES. My phone is Galaxy S I9000 running Android 2.2. My PC is runnning windows 7 x64 and the latest KIES version 2.0.0.11032_12. When I connect my phone to PC, phone's screen shows that it is ready to connect with KIES. PC founds the divice as a memory card. But when I turn on KIES it only shows 'Connecting...' but it never really connects. Moreover, when phone is in DOWNLOAD mode even ODIN cannot connect.
Maybe someone had a similar problem or has an idea how it could be solved. It would be very helpful.
wenoxx said:
Hi,
I have a problem connecting my phone to Samsung KIES. My phone is Galaxy S I9000 running Android 2.2. My PC is runnning windows 7 x64 and the latest KIES version 2.0.0.11032_12. When I connect my phone to PC, phone's screen shows that it is ready to connect with KIES. PC founds the divice as a memory card. But when I turn on KIES it only shows 'Connecting...' but it never really connects. Moreover, when phone is in DOWNLOAD mode even ODIN cannot connect.
Maybe someone had a similar problem or has an idea how it could be solved. It would be very helpful.
Click to expand...
Click to collapse
Multiple posts on the subject you could search .
jje
Believe me I did. I have tried solutions that i have found in this forum and what i have found in Google. However, nothing helped. There are many different cases in this situation and I hope that I have missed something or at least some one could tell me is this my PC's problem or phone's
kies is a buggy program & this shows more on win7 x64 which is very particular about the driver behavior, I just lost phone connection & now cant get it to connect.
+1 I have a quad-core running W7x64 and Kies takes about 30 seconds just to load. It's so ridiculously slow and has only ever detected my phone twice.
Hopefully you can find a 32-bit laptop or PC to use temporarily.
As an aside... a VM such as XP Mode may help as you could install XP 32-bit and connect the USB through to the VM guest? Unsure if this would help so may be useless advice
The latest Kies loads and finds phone on my X64 but did not before .
Clear your USB drivers .
http://www.nirsoft.net/utils/usb_devices_view.html
jje
I just want to know how to get into this "PC Studio" mode Kies mentions everytime I start it up. Its really ticking me off cuz I want to get the latest firmware on there but I can't seem to figure out how....
Download latest Kies from Samsung .
Connect phone using Kies mode selected on phone .
Connection fails its worth setting phone to USB mass storage mode and let the drivers install .
Tools Firmware upgrade . PC Studio nothing to do with firmware upgrade its an older version of Kies type software .
Android 2.2 next upgrade was 2.2.1 but not all network phone providers have updated to 2.2.1 as most are waiting for the release of 2.3 .So dont go looking for 2.3 its not on the servers .
jje
JJEgan said:
The latest Kies loads and finds phone on my X64 but did not before .
Clear your USB drivers .
http://www.nirsoft.net/utils/usb_devices_view.html
jje
Click to expand...
Click to collapse
you've got a thanks from me. this tool sorts it!
Dear fellow forum members ! good evening . i
bought a samsung galaxy GT i9003 smartphone
with android OS. when i tried installation of
Samsung kies software on windows xp sp3 bundled
with phone , it threw a error and didn't initialises.
error is as follows :fatal error provide value on
system. windows Baml2006.Type converter
mark up extension threw an exception. version
info :1.5.3-10124.. Please clarify whether it is a my machine fault or there is a corrupt file in the cd. Moreover i installed latest version of kies from samsung official website but it also resulted in same outcome. please help me overcoming this problem . thanks n regards.
Fatal Error = windows your PC .
Might be to do with an older OS used .
jje
wenoxx said:
Hi,
I have a problem connecting my phone to Samsung KIES. My phone is Galaxy S I9000 running Android 2.2. My PC is runnning windows 7 x64 and the latest KIES version 2.0.0.11032_12. When I connect my phone to PC, phone's screen shows that it is ready to connect with KIES. PC founds the divice as a memory card. But when I turn on KIES it only shows 'Connecting...' but it never really connects. Moreover, when phone is in DOWNLOAD mode even ODIN cannot connect.
Maybe someone had a similar problem or has an idea how it could be solved. It would be very helpful.
Click to expand...
Click to collapse
Hi, I had the same problem, in another forum someone said start kies on your PC and then plug your usb in, it worked for me.
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.
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
rahbert said:
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
Click to expand...
Click to collapse
Have you tried with a different USB cable?
No because i connected succesfully my friends galaxy fit with it, so the cable is not the problem.
thry manualy installing galaxy s drivers on pc?
Uninstall and reinstall the drivers.
Try different drivers.
Make sure you're using a Samsung wrong with the Samsung drivers.
Use a different PC.
Keep trying!
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
rahbert said:
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
Click to expand...
Click to collapse
To try using different drivers you would need to uninstall the current driver.
And just to be sure, you didn't flash to CM7/MIUI recently, not realizing Samsung drivers won't recognize your phone anymore, right? Nexus S drivers for those ROMs.
Its on the original ROM i think. Recently bought it second hand, 1 year old.
I couldn't find different drivers...except 32 bit and 64bit, but they all are the same version. Maybe post a link or something. Mine are 1.4.4.
Firmware version: 2.3.3
Baseband version i9000XXJVO
Kernel Version: 2.6.35.7-i9000xwjvh - CL184813 [email protected] #Dark_core_2.4 Mon May 16 15:02:38 EEST 2011
Build Number: DarkyRom JVH v10.1
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
rahbert said:
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
Click to expand...
Click to collapse
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
upichie said:
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
Click to expand...
Click to collapse
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
rahbert said:
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347899
upichie said:
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
rahbert said:
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
Click to expand...
Click to collapse
Throw it against the wall then. You ask us for help, disregard all of it, and then update us on what the service desk told you. If you will only listen to them, then don't ask us, kay? Appreciated.
Hi, there.
Actully, the rahbert's question is not bad. How can i use Mobile Odin if i can't root the device?
Or, how can I root without PC? Is it possible? I have exactly the same problem:
Nexus S (I9020), ICS 4.0.4(stock). When I plug the device: the error is reported(Code 43).
Should I try wipe data/factory reset? I really don't want to do this, because there is another good question: How can I fully backup my data(Titanium and so on) without root access? Can you suggest me something? Thanks.
Herman76 said:
Have you tried with a different USB cable?
Click to expand...
Click to collapse
Changing the USB cable worked for me. Thanks!!
Hello guys,
I have now tried for the last 8 hours to connect my phone via USB to my computer without any success.
I have read many threads concerning this problem but by now I just assume that my USB port is partly broken as I have tried all the solutions and none worked for me.
I can still charge the phone but windows isn't even showing that a device has been connected. Twice of probably thirty times windows showed me that an unknown device has been connected for a couple of seconds and then the phone isn't connected anymore.
I would like to root my phone and would like to know if there is a possible way to do it. Some say it's possible (depending on the Firmware already installed), some say it isn't.
My i9000 phone has:
Firmware 2.2
Kernel 2.6.32.9
[email protected]#1
Build Number Froyo.XWJPA
I hope you guys can help me, I am getting desperate...
Try this : http://www.unlockroot.com/
Here is the drivers : http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
Hey guy,
did you install Kies on your Computer? Your PC need the latest USB Samsung drivers. Note that you couldn't install Samsung drivers for newer devices like the Galaxy 9000 on Windows 2000 or older. You also have to look for the right drivers for your system. Maybe you did install x86 driver on 64 bit system or x64 drivers on 32 bit system.
Driver solution:
Go to settings, system and look for the hardware manager or simply check the "windows brenchmark settings" (included in vista and win7).
Try to follow that instruction: http://forum.xda-developers.com/showthread.php?t=1542633
Note:
If you have a working USB connection, you should search for flashing instructions because flashing is always on your own risk! It isn't hard to learn but you have to know which risks are there. Don't be scared by faults they can be undone (mostly).
Flashing:
First you should upgrade your phone to an early Gingerbread (3.2) build. Just search for "Gingerbread Stock Rom" or use "Darky's Resurrection" package. You'll find them here on XDA or in the world wide web
If you get trouble you'll get support here but first you should read about flashing and rooting.
best regards
As I told you I think that my USB port is damaged and hence I can't establish a usb connection to my phone.
I tried several drivers, Kies, different settings, simply everything which was already discussed.
My Galaxy will not even show up as an "unknown device" in my Windows 7 32bit (of course I used 32bit drivers).
Unlockroot requires me to connect the Galaxy via USB to the computer, so I can't use that.
Any other suggestions?
If your using a acer computer and you have never reinstalled window than it more than likely wont work. But you can google apps like z4root and universaland root i think thats what its called. Those apps i have rooted a few froyo devices with but z4 i have never seen work with the i9000 but try and see
Sent from my GT-I9000 using xda app-developers app
taz0697 said:
If your using a acer computer and you have never reinstalled window than it more than likely wont work. But you can google apps like z4root and universaland root i think thats what its called. Those apps i have rooted a few froyo devices with but z4 i have never seen work with the i9000 but try and see
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thanks z4root worked perfectly.