[Q] Kies Installation Error - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi Guys,
Hope you could help me out. After Installing a new version of Kies (1.5.3.10093_31_1) I got an uninstall prompt. Upon selecting yes, An error window pops out: UseDLL Failed(FsUsbExDevicelib.dll). Kies would then uninstall the previous Kies software and then prompts you to run file setup again. The cycle just repeats and i am not able to proceed with any installations. Please help! By the way, I am running winxp 32-bit.

skindred28, this thread belongs in the Q&A section, not in development. Take a moment and read the "STOP, READ THIS BEFORE POSTING" thread at the top of both of these sections, it has clear guidelines for proper thread placement.

my apologies sirphunkee.

I have a similar problem tonight. Solved wit luck and heavy regedit work. If you have another pc you can try to install kies then look at the change made in the pc (i used total unistall 5)to make same change in your registry...
PS I'm not exper but Kies is a terrible program
Sent from my GT-I9000 using XDA App

Related

Cant get Heimdall drivers to work

Ok this is my first time ever using heimdall. I am on windows 7, I have the C++ pack. When I put my galaxy tab into download mode and plug it into my computer and then go run zadig, then select options and list all devices my options are just my regular stuff and "gadget serial". I thoguht it was supposed to be something along the lines of composite device or something like that????????
Please help as I need to get this working
EDIT: Ok I just decided to go with it and it worked so MODS please delete this thread
did u install samsung kies first?
MasterRy88 said:
EDIT: Ok I just decided to go with it and it worked so MODS please delete this thread
Click to expand...
Click to collapse
Plus the fact that you've posted this in the development forum instead of the questions forum.

[Q] Problem rooting Stock froyo captivate

Hi All,
I just purchased my Captivate yesterday from Costco (Expecting to still get the 2.4 Eclair) but unfortunately I got the Froyo 2.2 on my new captivate.
I tried rooting it using superoneClick and it just gets stuck on "Waiting for Device". I have drivers properly installed on my windows 7 64 bit machine (because I can use the phone and access its internal SD card).
Can anyone have suggestion or faced similar problems?
I have tried disabling/re-enabling usb debgging while it says "Waiting for the device"
Search the forum. There are a few threads floating around on different ways to root the stock froyo build. I don't know why the superoneclick wont work in your case but a search will turn up some info for you.
thanks. I will search the the threads and will post my results here in this thread for someone like me struggling with the same problem.
If you were planning on flashing a custom ROM after rooting anyway, you could use Odin one-click from download mode to flash 2.1 eclair, and then go from there.
Are you sure you are enabling debugging? I just used superoneclick on my phone last night after I flashe dback to stock.
First thing I do is change the phone in settings to - Ask on Connection, then I enable debugging.
Also you could try a different USB port on your computer and also make sure you have all of your necessary drivers installed.
I hope you get it figured out!
PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??
22andy2 said:
PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??
Click to expand...
Click to collapse
want a much easier method? install speedmod kernel using odin, reboot into recovery, advanced features (not the CWM version), and choose the option that says something like "root phone" and choose the "simple" option. congratulations, you are now rooted and running a custom kernel with CWM that can install a custom ROM.
next time, please do not post this in development as this has NOTHING to do with development. Q&A or general next time, please.
How did someone with no posts, post a question in this section? I thought you had to have a minimum of 10 posts to post in here.
I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..
22andy2 said:
I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..
Click to expand...
Click to collapse
So why is your join date Dec 2007?
CB650 Wolf said:
So why is your join date Dec 2007?
Click to expand...
Click to collapse
thats when I just registered.. I will be the active member now as I officially own the android phone.
I really appreciate all of you guys work and I didn't mean to offend any one by posting the thread here.
I already apologize for missing the rule for the 10 minimum posts on forum before posting.
I rooted my device successfully by using odin. Thanks all of you for the suggestions.

[Q] computer can't see Galaxy S

my samsung galaxy s is not recognized by my computer no matter what i do!
don't know why, i've done some research, no results.
i've installed Kies, which i assume already installs the drivers, but when i connect, the computer shows no sign of connection (it says that i need to update drivers in device manager??) i tried different USB ports, toggled USB debugging on/off, NOTHING WORKS
the reason i want my computer to recognize the galaxy is because i want to update it to android 2.3.5 via odin. but when i enter download mode, the computer doesn't recognize it. when i'm in the system, the computer STILL doesn't recognize it...???
please somebody help, it's rooted, running a different MIUI version (not the ones in xda dev section), i'm not sure where i got it from, but it's called an ENG_MIUI?
CM7 (and subsequently MIUI) is built from the Nexus S source code, so find the proprer drivers for it. "CM7 drivers" should be a sufficient google search. Also, Kies sometimes interferes while using the other drivers. If you run into any problems, uninstall Kies.
Okaham said:
my samsung galaxy s is not recognized by my computer no matter what i do!
don't know why, i've done some research, no results.
i've installed Kies, which i assume already installs the drivers, but when i connect, the computer shows no sign of connection (it says that i need to update drivers in device manager??) i tried different USB ports, toggled USB debugging on/off, NOTHING WORKS
the reason i want my computer to recognize the galaxy is because i want to update it to android 2.3.5 via odin. but when i enter download mode, the computer doesn't recognize it. when i'm in the system, the computer STILL doesn't recognize it...???
please somebody help, it's rooted, running a different MIUI version (not the ones in xda dev section), i'm not sure where i got it from, but it's called an ENG_MIUI?
Click to expand...
Click to collapse
To get your phone recognized you need nexus s drivers. But that won't help you get it recognized by kies.
You need stock firmware on your phone to get it updated through kies.
Sent from my GT-I9000 using xda premium
I have same problem previously. But it solved after I do this: while Kies open, select Tools then press Install driver.
thanks guys, but how would i go about doing that? the directions i found don't make any sense?
ndemin said:
I have same problem previously. But it solved after I do this: while Kies open, select Tools then press Install driver.
Click to expand...
Click to collapse
Just to clarify, this won't help you. Samsung uses Samsung drivers. Since you do not currently have Samsung firmware on your phone, this won't do you any good. As previously stated by two very informative posters, you will need the Nexus S drivers to recognize your phone.
And, also as previously stated by just an absolutely wonderfully helpful poster, if you do a simple google search you'll find exactly what you need. Try either Nexus S Driver, CM7 Driver, Nexus S CM7 Driver, or really anything else similar. You could also check the CM7 Wiki, as I'm sure there would be a link for them there. And finally, if you simply search XDA Developers, I'm sure you'd find plenty of posts with what you need.
Hopefully that helps.
thanks
now my computer can see it when it's in android, but why does it STILL not see my Galaxy S in download mode???
do i need another set of drivers? (it said driver not found)
BTW THANKS GUYS!!! sorry if i'm being annoying
hello??
anybody??
Well did you install the Nexus S drivers yet?
upichie said:
Well did you install the Nexus S drivers yet?
Click to expand...
Click to collapse
yes, the nexus s drivers are installed, but i STILL can't connect through download mode...
try different computer, install samsung driver then connect your phone
still doesn't work???
Well, it seems to be a driver issue!
Try these (32-bit windows) but make sure that you are having a fresh win7 installed just in any case that your reg got corrupted with drivers (Ime ).
Still not working,then try on another pc..!
---------- Post added at 07:12 AM ---------- Previous post was at 07:06 AM ----------
upichie said:
Just to clarify, this won't help you. Samsung uses Samsung drivers. Since you do not currently have Samsung firmware on your phone, this won't do you any good. As previously stated by two very informative posters, you will need the Nexus S drivers to recognize your phone.
And, also as previously stated by just an absolutely wonderfully helpful poster, if you do a simple google search you'll find exactly what you need. Try either Nexus S Driver, CM7 Driver, Nexus S CM7 Driver, or really anything else similar. You could also check the CM7 Wiki, as I'm sure there would be a link for them there. And finally, if you simply search XDA Developers, I'm sure you'd find plenty of posts with what you need.
Hopefully that helps.
Click to expand...
Click to collapse
Well, CM7 drivers won't help SGS to get recognized on PC on DLD mode, you need another set of drivers and not those Nexus S's. I had the above ones installed on my PC (Google's your Best friend ) .
I had to install the drivers manually,
Right click on computer, click manage -> device something -> find your device in the list, select to update driver, search manually and enter the path to your android sdk and search.
Worked like a charm to me
Sent from my GT-I9000 using XDA App
pzayx said:
I had to install the drivers manually,
Right click on computer, click manage -> device something -> find your device in the list, select to update driver, search manually and enter the path to your android sdk and search.
Worked like a charm to me
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
computer could see device in download mode?
hi
i had same problem, but computer recognize the device as "unknown device"
in all modes, developed, storage etc...
i am close to think thats is problem of internal usb driver of the rom
want to downgrade from de device, whitout usb, but i dont know how do it, because i am not root, and its no possible in 2.3.4 whituot usb.
thanks
I had a lot of similar issues with my I9000, too.
Tried everything on ROM and driver side also on different computers.
Finally it turned out that my Micro USB connector was corroded.
I have around 30 people in our company that have the same phone, and 5 of them had similar issues. I guess it's a common problem with this device.
I took a toothpick and cleaned the contact of the connector by sliding it up and down for a couple of million times. This also did the trick for my colleagues.
I think it's at least worth to try it.
Good luck
i try to clean the contact, but still cant connect to the computer.
I wonder if a method of degrading the system with a signed rom from the recovery, without using the USB cable or ODIN.
i have a same problem. Any new solution?
snbmf said:
i have a same problem. Any new solution?
Click to expand...
Click to collapse
use this guide
Check this out! Links to useful Guides and " Banned " Documentaries ​

[Q] SuperOneClick won't initialize

I've downloaded and tried SuperOneClick 2.2 and 2.3. I'm really wanting to root my Lg Thrill but it just isn't cooperating.
I have my phone on usb debugging and unknown sources is checked! I've tried starting up SuperOneClick before and after plugging in my phone. Each and every time I get the same error:
"The application failed to initialize properly (0xc0000135). Click on OK to terminate the application"
I read in another thread that this could be caused by registry errors so I did what I could to fix any that I had. This has not worked either. Any help is greatly appreciated. Thanks in advance...
EDIT: I finally got it to root... mods please delete this post. Thanks.
Can you post how you figured out the problem?
I may start soon, would like to prepare for any possible predicament.
Thanks
The way I got it to work was installing the latest microsoft .net framework for my computer. I'm using an older laptop and it had recently been wiped clean so that I could do a fresh install. I forgot about about reinstalling all the microsoft garbage onto this computer Once I installed the new .NET framework, the superoneclick worked like a charm. Finally got all the bloatware off and even without a ROM this phone runs MUCH MUCH better than it did before.

[Q] Not recognised in Odin

Hello people,
I am trying to change the firmware of my galaxy mini. Installed correct drivers but it does not get recognised in Odin (v4.3 ofcourse).
Just to check it out, i run Odin v3.04 and a few others (i think 4.37 and 4.38) and it was recognised immediately!
What might the problem be?
P.S.
I know there are multiple threads asking for help with odin, i checked out too many of them but with no result.
Sorry for disturbing you!!
rafascy said:
Hello people,
I am trying to change the firmware of my galaxy mini. Installed correct drivers but it does not get recognised in Odin (v4.3 ofcourse).
Just to check it out, i run Odin v3.04 and a few others (i think 4.37 and 4.38) and it was recognised immediately!
What might the problem be?
P.S.
I know there are multiple threads asking for help with odin, i checked out too many of them but with no result.
Sorry for disturbing you!!
Click to expand...
Click to collapse
Similar threads have been posted before, pls use search next time.
Well, to solve ur problem, try uninstalling Samsung USB driver and installing it again. To uninstall the driver, go to control panel>uninstall programs then scroll down to Samsung USB driver and uninstall it from there. If that doesn't work, try using a different port or cable?
tietganFTW said:
Similar threads have been posted before, pls use search next time.
Well, to solve ur problem, try uninstalling Samsung USB driver and installing it again. To uninstall the driver, go to control panel>uninstall programs then scroll down to Samsung USB driver and uninstall it from there. If that doesn't work, try using a different port or cable?
Click to expand...
Click to collapse
I know that there are similar threads and I read them but didn't solve my problem, I told it in my previous post also.
I tried with 2 different (100% working) cables and 3 usb ports (100% working, I also used them to work on the Galaxy S3).
Uninstalled and reinstalled drivers many times. I tried installing through Kies, through the "Samsung USB Drivers" and through windows update. Nothing worked.
Let me tell you again that other versions of Odin (that can't help me work on the galaxy mini) recognise it. Maybe there is something wrong with Odin I use.
edit: take a look at this picture
i48.tinypic.com/14c5rao (dot) jpg
Anyone who can help people?

Categories

Resources