Database Info

anyone else having problems with 64bit galaxy S drivers?

I did the one click root with no problem, now can't do the clockwork mod because the drivers keep failng , even tried the root again and it won't work either because of the drivers. I can get it to sync like 1 in 10 times, verified because I can get adb shell working. but it seems if I try to do anything, the drivers basically reset themselves. i didn't have this problem previously, although i did have to reinstall the drivers everytime, now that isn't even working, has anyone got this working correctly? I only have windows 64 bit machines.
EDIT: if someone could post a link to drivers that are known to be working, that would be appreciated, then at least I know I'm using ones that are working for people.

What version of windows are you running?
does it give you any errors, or does it just not regonize it? Maybe an issue with driver signing.
Sent from my SPH-D700 using XDA App

windows 7 ultimate 64 bit. the device manager usually shows errors, i show a bunch of drives listed, after a few tries of deleting the J drive, I get it to show up as wpd file or something like that, then it works for a minute or so, it will let me into adb shell and I can do SU, but if i try adb push, it hangs. same thing when trying to do the 1 click scripts, I know if its working or not, because if it isn't working, the script just hangs, then 10 tries of unplugging and plugging in and it finally connects and runs the scrips although giving errors and such, I did root just fine using the scripts, so I'm not sure whats going on with these drivers. maybe if I knew which things to uninstall from the device manager, i could start from scratch, using back usb port, front usb port, makes no difference. i'm gonna wear out the micro usb port if I keep plugging and unplugging the phone like this.

Hmm it sounds to me that finding the associated driver files in the registry/file system and clearing them. Rebooting. And reinstall of driver would be the best plan of action.
In device manager you should notice a new driver pop up when you plug in your phone. From there you could uninstall the driver, but be aware if you just uninstall the driver without removing the driver files 7 will auto find them and reinstall them when it sees your device.
Without being able to look specifaclly at the computer its hard for me to tell if its a corupt/broken driver causing the problem. There could be a few things doing it.
Sent from my SPH-D700 using XDA App

is there a way to clean everything out? like what things in device manager would I clean out? I can't seem to find them all.
Nanncee said:
Hmm it sounds to me that finding the associated driver files in the registry/file system and clearing them. Rebooting. And reinstall of driver would be the best plan of action.
In device manager you should notice a new driver pop up when you plug in your phone. From there you could uninstall the driver, but be aware if you just uninstall the driver without removing the driver files 7 will auto find them and reinstall them when it sees your device.
Without being able to look specifaclly at the computer its hard for me to tell if its a corupt/broken driver causing the problem. There could be a few things doing it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse

It's not so much in device manager that your looking to remove it. Usually when a driver is installed, it places a directory on your c drive with all the files needed. now those files could be located in /windows or /program folders, or they could be in their own folder for titled samsung for example. (this usually isn't the case for storage drivers like we are dealing with)
I am not sure how samsung wrote their driver package, but you may be able to run it again and have it remove the files for you. I would verify on a windows system, but I don't have one running right now. You may also be able to use the driver installer to follow the path to where it places the files. again it all comes down to how the driver installer was written.
also just thought of this, and it is a long shot, but verify that you don't have an antivirus/firewall blocking the connection.
I don't know if you have another computer, if you do I would try it on that system as well.
Sorry I can't be more definitive on where to remove them. But without a windows system I hate to send you looking in the wrong spot and deleting things that shouldn't be.

http://www.nirsoft.net/utils/usb_devices_view.html this program will let you wipe any usb device from the history... worth a shot/try a different port

On 64-bit Windows, you'll probably need to manually set the driver for the ADB composite device. Just do update driver from the device manager, browse for drivers and hit let me pick from device drivers on my system.
Worked for me anyway.
But it sounds to me like your problem is not driver related. Try another USB cable. The stock one is pretty poor. My first Epic's had this problem, so I got another cable and it magically started working again. Also, front USB ports are more finicky, so you could try the back ones.

Linux FTW.

I never got the most recent clockwordmod one click method to work, I always have to use 2.5.0.9, then do the update.zip method for 2.5.1.0., I tried on both of my laptops, one running 7U64, the other running 7U32.

did this and tried two cables from both of our epics, also, it worked fine to do the clockwork mod. used front and back usb ports. no luck.
Firon said:
On 64-bit Windows, you'll probably need to manually set the driver for the ADB composite device. Just do update driver from the device manager, browse for drivers and hit let me pick from device drivers on my system.
Worked for me anyway.
But it sounds to me like your problem is not driver related. Try another USB cable. The stock one is pretty poor. My first Epic's had this problem, so I got another cable and it magically started working again. Also, front USB ports are more finicky, so you could try the back ones.
Click to expand...
Click to collapse

Try a NON Samsung cable. Not one from another Epic box.

i finally got it to work, used the wifes laptop, something apparently is screwed up on my machine. wish I knew what.

robl45 said:
i finally got it to work, used the wifes laptop, something apparently is screwed up on my machine. wish I knew what.
Click to expand...
Click to collapse
Glad to hear you got it solved. As to whats wrong with your computer, I have no clue. Good luck though. If all else fails, wipe and reinstalls are your friend.
Sent from my SPH-D700 using XDA App

robl45 said:
EDIT: if someone could post a link to drivers that are known to be working, that would be appreciated, then at least I know I'm using ones that are working for people.
Click to expand...
Click to collapse
.....
I have had many problems with drivers on my windows 7 64 bit machine.
To get the epic drivers to work I had to uninstall all other samsung phone drivers first. Download the x64 drivers from that post, upzip.
Plug your epic in mount it. Open the device manager and manually point it at the unrecognized device at that folder. I had to do this for 3 or 4 separate entry's.
Play with it a bit and you should be able to get it working with those.
Hope this helps.
Bah new user bs. Cannt post the link. Go over to SDX developers epic development section. There is a sticky "Confirmed Working Drivers"

I said screw it with the Samsung Drivers. Just installed PDAnet when I got this computer a week ago and no issues (win7 home 64-bit). It asks during setup what phone drivers you want to install. Select Samsung, let it do its thing, and you're all set. ADB works flawlessly, no need to mount sd card to get it to work.

[Q] Device debugging with Eclipse

I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?

Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim

Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?

More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!

Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.

Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck

JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device

I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.

I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.

One thing I forgot. Do not unplug your device between uninstall and hardware scanning.

AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.

rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim

jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!

rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim

[Q] ADB not working, HTC Android Phone USB Device only

Hi, I have a Thunderbolt, CM7.1.0 RC0-Thunderbolt-KANG, Kernel 2.6.35.9-cyanogenmod, Android 2.3.4
I've not updated to the one in http://forum.xda-developers.com/showthread.php?t=1049542 because of the Radio problems, and I can't push a Radio because of THIS problem (I've got a few, but a thread for each):
I can't get ADB to detect my device at all. The Android ADB Interface will show up for other rooted devices, just not this one. Laptop, XP SP3, bit old, but works fine. Similarly, I can't get PDANet to detect it, no matter which driver I use. The only device that shows up in Device Manager is "HTC Android Phone USB Device".
Oh, and I've run SDK Manager, making sure everything is up to date. If you want to double check this, just tell me what info to post, I'll gladly do so.
I can't do anything ADB without this. Help?

Bumping this because of how swiftly it got buried. Two hours it's up, and it was four pages down...

triaddraykin said:
Hi, I have a Thunderbolt, CM7.1.0 RC0-Thunderbolt-KANG, Kernel 2.6.35.9-cyanogenmod, Android 2.3.4
I've not updated to the one in http://forum.xda-developers.com/showthread.php?t=1049542 because of the Radio problems, and I can't push a Radio because of THIS problem (I've got a few, but a thread for each):
I can't get ADB to detect my device at all. The Android ADB Interface will show up for other rooted devices, just not this one. Laptop, XP SP3, bit old, but works fine. Similarly, I can't get PDANet to detect it, no matter which driver I use. The only device that shows up in Device Manager is "HTC Android Phone USB Device".
Oh, and I've run SDK Manager, making sure everything is up to date. If you want to double check this, just tell me what info to post, I'll gladly do so.
I can't do anything ADB without this. Help?
Click to expand...
Click to collapse
Quick Question! Are you trying to connect with a MAC or a Windows Computer? Oh... you said Laptop XP SP3... this is not the problem. You know how I made it work on a ViewPad7 connected to a Mac? Activating the USB Tethering...
Can you try if activating the USB Tethering the ADB is able to see your device?

Make sure you have installed the drivers first (adb driver + phone drivers) .... check that in Administrative Tools -> Computer Management (%windir%\system32\compmgmt.msc /s) -> Device Manager -> check if any devices with an ! mark on them, it means the driver for that device is not properly installed.

Right... Well, small new update, and sorry that I haven't responded in a while. Kinda hard to get internet lately.
Anyways, I got a hold of another phone I'd rooted a while back, and decided to test that device. ADB DEVICES worked perfectly for it, but it still can't detect mine. There's no unidentified devices on my laptop's Device Management.
Help?

*sighs* Bump!

Drivers for Micromax A52!??

Hi, I have a Micromax A52 device that I am trying to use for application development. Unfortunately, I can't seem to find the correct drivers for the phone. I scoured the Micromax website, but the drivers I found there did not seem to work at all. I searched these forums, and there are a few topics about the phone, but they all seem to be unsuccessful rooting attempts. All I need is drivers that will let me interface the phone with eclipse for testing. I didn't see a section for this phone (probably because the handset is not very popular) so I didn't know where a better place to post this was. Sorry if it's in the wrong section or something. Anyway, does anyone have working drivers for this device? I tried installing the drivers for the A50 (the previous model that has working drivers) but it did not work. Please help

Hello so I read trough your complains and this is the driver which should work in any case: http://www.priceandspecification.in/micromax-a52-pc-suite-modem-driver-download.html
A few questions:
What operating system your using: XP, 7 or MAC?
Have you installed ADB drivers?

I have the ADB drivers installed, and I am running Windows 7. These are the same drivers I found on the Micromax website which did not work for me. Maybe I am just installing it wrong or something, but I honestly can not make head or tail of it because there are so many folders with so many installers. I tried running a few of the intaller exe/bats but none of them worked for me. Is there some process I don't know about? Because as far as I can tell, this installer does not work. Thanks for any help!

pachufir said:
I have the ADB drivers installed, and I am running Windows 7. These are the same drivers I found on the Micromax website which did not work for me. Maybe I am just installing it wrong or something, but I honestly can not make head or tail of it because there are so many folders with so many installers. I tried running a few of the intaller exe/bats but none of them worked for me. Is there some process I don't know about? Because as far as I can tell, this installer does not work. Thanks for any help!
Click to expand...
Click to collapse
Hi,
If you are looking for Micormax A52 (unknown device/no suitable in device manager) then you can also install A56 driver.
Code:
http://www.micromaxsuperfone.com/products/PDF/Drivers_A56.zip 13MB
Right click on Micromax A52 and update driver software and choose the android_winusb.inf which will show you three different driver company's and drivers.
Choose Google Inc and on right side choose Android ADB interface.
Then your adb devices would display your device.

not able to install driver
Not working. Driver not installed Error. Any method to get the driver??

A52 ADA- Drivers
helloansuman said:
Not working. Driver not installed Error. Any method to get the driver??
Click to expand...
Click to collapse
Hi,
I have found some software that poses the same USB drivers that this mobile has
first install the server software and navigate to the programs folder and extract the driver for your OS.
Password : micromax

Refer to below link
The complete driver list posted by me.
http://forum.xda-developers.com/showthread.php?p=30906925#post30906925

install driver using software
use moborobo software to install your driver in pc
first to the download moborobo software and install it
after open moborobo and connect your mobile in pc
moborobo will find your mobile driver and install autometicly
click thnks button

[Resolved] [Q] Rooting Imagine 7 (Skytex) via Bin4ry Method

EDIT: Got this figured out...
Hi,
Yes I have searched, but it seems the Imagine 7 is both new enough, and not mainstream enough to have much info.
So I would like to get some input/thoughts from others. Yes, I'm a 'noob' here, but I am extremely grateful to any insight large or small anyone here is willing to provide. So, that said, thanks in advance!
I'm attempting to root a Skytex Imagine 7 tablet using Bin4ry's tool. However, I cannot seem to have it be recognized. The usb portion of the device is recognized as a rockchip_usb... this is fine. However, to root I also need the ADB driver. The device shows up as IMAGINE under devices, but Windows is unable to find a driver. After going to the Skytex website, I downloaded their driver for the Imagine 7. However, this driver is actually just the Nexus 7 driver, at least from what I can gather reading through the inf. Either way, windows will not find it even after telling it to install from the folder, so instead you must click 'have disk' and manually install the inf. Once installed, it will show up as Android Phone>ADB Driver (or similar).
Unfortunately this is where I am stuck, even with the driver installed, Bin4ry's script hangs at looking for device. So what can I modify to create recognition? Or have I done something stupid... which is entirely possible...
Thanks again!