Hello,
i have a problem debug eclipse app on my Sgs i9000.
Info:
1. my cable is good galaxy nexus worked debug threw this cable.
2. Windows 7 64 Bit.
3. android version 4.1.2 kernel version 3.0.45 semaphore build number c-rom mix v3
Link Device Mennger
tried a lot of ways... went over google no luck yet.
i came to here as a last resort.
Thanks a lot.
:good:
Have you tried to restart adb server (adb kill-server, adb start-server) and check the connected device (adb devices)?
Sent from my GT-I9000 using xda app-developers app
Yep i tried that severel times
anyone?
i9000 Error in Device Manager...
HarryGN said:
Hello,
i have a problem debug eclipse app on my Sgs i9000.
Info:
1. my cable is good galaxy nexus worked debug threw this cable.
2. Windows 7 64 Bit.
3. android version 4.1.2 kernel version 3.0.45 semaphore build number c-rom mix v3
Link Device Mennger
tried a lot of ways... went over google no luck yet.
i came to here as a last resort.
Thanks a lot.
:good:
Click to expand...
Click to collapse
I ran into a similar problem this evening on my Bell Canada Galaxy S i9000m. This surprised me as I have debugged with this phone in the past but I have recently flashed the custom Cyanogenmod 10.1 Rom on it.
Two things:
1. What version of Android are you running? (Stock or Rooted with a custom rom?)
2. Have you installed the Samsung drivers for Windows 7, 64 bit?
If you are running the stock OS and have not installed the Samsung Windows 7 drivers, either download and install the ones posted here:
http://forum.xda-developers.com/showthread.php?t=728929
or try the steps in "solution" below...
I am running CyanogenMod 10.1 and while I had been debugging source in the past on this phone, I had not debugged since installing CM10.1. I noted, similar to your experience that Windows Device Manager was showing an error for my i9000m, no driver had been found and assigned. I have installed the Samsung drivers in the past and they are still installed but I suspect some difference in naming of the device in CM10.1 which confused Device manager.
The solution: Click on the device (GT-I9000) and select properties. Then click on the "Update Driver" option and selected the option that has windows go search for the correct driver. To my surprise, Windows 7-64 bit found and installed what appears to be a Generic Android Device named "Android Composite ADB Device". I am able to debug without any problems now.
Related
I recently bought the Samsung Galaxy S 19000 & installed the latest version of Kies onto my PC. When i open Kies i get about 8 of these error messages- FsUsbService64 / Service Initial Failed, then when Kies has fully loaded they stop. Kies then works with no problems. How can i stop this error. The PC uses Vista HP 64bit SP2.
i am also getting the error.... any ideeas?
The same problem with me, I have windows vista 64 Home Premium, but my problems began whit the last version of Kies because the version 100 was running well.
fsusb64service failed
Me too, but with windows 7 (64)
Ditto, with Vista 64 Business and Windows 7 64 Ultimate. Get about 12 popups with this error
I have sorted the problem i had with the pop-up.I removed the latest version of Kies from the PC and installed an older version of Kies. Google - "Samsung Kies - Older Version - Android Forums", Click ,& then click on the link posted by Jack45. I used the 1.5.3.10092_2_1exe, and it`s working a treat, no pop-up`s.
JEL8 said:
I have sorted the problem i had with the pop-up.I removed the latest version of Kies from the PC and installed an older version of Kies. Google - "Samsung Kies - Older Version - Android Forums", Click ,& then click on the link posted by Jack45. I used the 1.5.3.10092_2_1exe, and it`s working a treat, no pop-up`s.
Click to expand...
Click to collapse
Did you try updating it to the latest then ? And if so, does it cause the error again ?
fylim said:
Did you try updating it to the latest then ? And if so, does it cause the error again ?
Click to expand...
Click to collapse
Hi fylim, no i have not tried that yet. I will do though just to see what happens.
*EDIT * I opened Kies and clicked update. It has installed the latest version. I closed the program then opened it again and never got any error`s, so that worked
It's the problem with 64bit driver. Try to download the older version of the Kies.
Sent from my GT-I9000 using XDA App
In my quest to resolve the FsUsbService64 Service Initiali Failed errors, I found a newer version of KIES on this website.
http://dls.scione-music.de/KIES/
Downloaded and installed Kies_1.5.3.10104_66.exe 20-Nov-2010 16:14 136M
and voila, no more errors !! Problem Resolved !! Loads super fast as well.
However, I am not sure where this version come from as it is newer... than official Samsung version. If any one knows, please share.
If you have USB driver issues, click on KIES pull down menu at top left and click on Driver Recovery. It should resolve your USB Driver issues.
I just installed windows 8 Consumer preview. I had my Galaxy note working before with the USB connection on windows 7, but now after windows 8 is installed over 7 I have a problem connecting my Galaxy note with the computer. It seems that it is an MTP problem or something went wrong after windows eight is installed. I have read on a Microsoft MSDN post that the mtp protocol is not yet supported with windows 8. If there is something that I can use to work around that It would be appreciated.Please help.
Sent from my GT-N7000 using XDA
Try installing Droid Explorer on your PC.
All of us on ICS Roms have the same USB connection problem, and this little program is the solution. It recognizes our Notes automagically without Windoze drivers.
Don't know if it'll work for you, but it's worth a try.
I will do that. But would it make a difference if I still have GB on my note? Thanks
Sent from my GT-N7000 using XDA
I had this problem as well, easiest solution is to put the Note in USB Debugging mode, and it will connect with Windows 8 fine.
You can find USB Debugging mode in Settings -->Applications --> Development.
weird, I have a similar problem : I want to install CWM, but "adb devices" doesn't see any devices....I have "USB debugging" checked, I tried to install samsung drivers, Droid explorer, Kies won't install, and it is not recognizes as a device by Windows. Strange thing is, if I remember correctly, I successfully flashed a stock firmware using PC Odin. Any ideas ?
Windows 8 Desktop, ICS Note. Everything's working fine here. Haven't had to install anything on either end to get it to work.
I do have USB debugging enabled though, as suggested above.
i am having the same problem. at 1st win8 detects it and i always charge on it but lately i noticed it does not detect. i went to my home pc win 7 64bit which is detecting before but now i did not detect also. i did everything kies. driver of droid but still the same problem. Weird yet still it charges.
Sent from my GT-N7000 using Tapatalk
It worked a few times after that when I installed the google driver but now I have the same problem with both windows 7 ultimate 64bits and windows 8 release preview. It is charging but not detected. I also tried different cables with no progress. I sudpect it could be that one of the pins of the note connector is not OK. Can anyone help please
Sent from my GT-N7000 using XDA
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.
Hi all,
Hoping someone can help me a few pointers:
Firstly I have spent 1/2 the day googling and reading the existing stuff on this and other forums.. This post is a last resort.
I am trying to install CM on my Galaxy and am getting the following error every machine I try on:
Error: claiming interface failed!
I have the following setup:
Samsung Galaxy S
Model: GT-I9000
Firmware: 2.2
Base I9000BOJP3
Kernal 2.6.32.9
Build: Froyo.BOJPB
Macbook Pro Running Windows 7 x64
x2 HP 8300 Running Windows 7 x64 (1 on domain / 1 on workgroup)
Heimdall_V1.4rc1_win
Hardcore-Speedmod
I have done the driver installs from zadig (elevated and not) and can only assume the drivers are installing correctly on all machines - if I dont do the driver install I get an error in heimdall (error-12, once I install the drivers that goes away).
I have found fixes on MACs and LINUX but nothing for Win.
Can anyone shed any light on what might be causing this error? Starting to suspect its the phone itself??
x1tom said:
Hi all,
Hoping someone can help me a few pointers:
Firstly I have spent 1/2 the day googling and reading the existing stuff on this and other forums.. This post is a last resort.
I am trying to install CM on my Galaxy and am getting the following error every machine I try on:
Error: claiming interface failed!
I have the following setup:
Samsung Galaxy S
Model: GT-I9000
Firmware: 2.2
Base I9000BOJP3
Kernal 2.6.32.9
Build: Froyo.BOJPB
Macbook Pro Running Windows 7 x64
x2 HP 8300 Running Windows 7 x64 (1 on domain / 1 on workgroup)
Heimdall_V1.4rc1_win
Hardcore-Speedmod
I have done the driver installs from zadig (elevated and not) and can only assume the drivers are installing correctly on all machines - if I dont do the driver install I get an error in heimdall (error-12, once I install the drivers that goes away).
I have found fixes on MACs and LINUX but nothing for Win.
Can anyone shed any light on what might be causing this error? Starting to suspect its the phone itself??
Click to expand...
Click to collapse
Have you tried using Odin?
Sent from my GT-I9000 using XDA Premium HD app
I've found a link, but connot past it there.
search for
blog.scott.wallace.sh/2012/03/
getting-heimdall-to-work-on-your-mac.html
kevtrysmoddin said:
Have you tried using Odin?
Sent from my GT-I9000 using XDA Premium HD app
Click to expand...
Click to collapse
Combination of super oneclick and odin did it - thanks!!
One last question If I can....
Is there any need for CWR for CM10 or other roms? can I not just use the android system recovery <3e> ??
thanks again...
x1tom said:
Combination of super oneclick and odin did it - thanks!!
One last question If I can....
Is there any need for CWR for CM10 or other roms? can I not just use the android system recovery <3e> ??
thanks again...
Click to expand...
Click to collapse
Yup sure will
Sent from my GT-I9000 using XDA Premium HD app
Been trying to install the USB driver for my Galaxy S.
I'm able to use the USB storage feature, yet strangely enough it isn't detected in ADB/device manager.
Downloading the driver online doesn't work.
I suspect it could be my Android being 4.3.1, can any other users confirm this?
ROM would be C-Rom.
Graci.
Hmhh it is not the Android-Version 4.3.1 ...for me CM 10.2 (= Android 4.3.1) the USB-drivers works perfectly in my odin ...
ShadedCyan said:
Been trying to install the USB driver for my Galaxy S.
I'm able to use the USB storage feature, yet strangely enough it isn't detected in ADB/device manager.
Downloading the driver online doesn't work.
I suspect it could be my Android being 4.3.1, can any other users confirm this?
ROM would be C-Rom.
Graci.
Click to expand...
Click to collapse
ShadedCyan said:
Been trying to install the USB driver for my Galaxy S.
Click to expand...
Click to collapse
Follow this guide to resolve connections problems or look in My Android Solutions link below
Check this out! You , YES! you are an " Android ". Not your phone but U.​