Database Users

Google Maps, Facebook and ADB

Hello All.
I've had my UK, T-Mobile G1 for quite a while now. I have rooted it and it is running the latest CyanogenMod recovery image and ROM. I also have Apps2SD set up on my 8GB SD card, on a 512MB ext partition. This was all working fine until the problems below occurred...
I'm having some problems with several apps and ADB.
My PC runs Windows 7, 64 bit, and I can't seem to find a driver for the G1's ADB. I'm probably being incredibly stupid, but I just can't find one. I have used one before on Vista, where I had to set some boot options, but I'm not too sure / happy about doing that on my nicely functioning Windows 7. And as my friend once said; "You mess around with windows, then windows will mess around with you"...
But, anyway, I can't seem to get ADB working, if someone could either send me a link to the drivers or guide me through it, I'd be grateful...
Also, it may be due to me running CyanogenMod, but if I try to update the Facebook app, it downloads the app, and then when it tries to install, gives me the error "Installation Unsuccessful - Incompatible Update".
And with the Google Maps app, it says "Installation unsuccessful - Package file was not signed correctly". This may be due to me trying to get the hacked version of the app to get the Google Maps Navigation working in the UK, but I couldn't get that to work, so I uninstalled it and Nav Launcher, and now when I try to update from the Market it gives me that error.
I've seen a guide online with ADB commands, but as I have no access to ADB, I'm a tad screwed. I've tried runnign the commands in the Terminal Emulator in the phone, which does approximately nothing whatsoever.
So, can anyone give me any guidance on any of my Android problems?
Thanks in advance - Ethan

To the best of my knowledge no one has successfully used ADB with Windows 7/64bit

jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Ah. Looks like I'll be reinstalling Ubuntu then for the ADB. Thank you for such a fast response.
- Ethan

jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Lies, I'm running windows 7 64bit and ADB works fine.

chris4500uk said:
Lies, I'm running windows 7 64bit and ADB works fine.
Click to expand...
Click to collapse
In that case, do you remember where you obtained the driver from? I would love a link, or a zip file or something...

I'm on Vista x64 SP2 and I can use ADB just fine. You just need to download the SDK and then get the USB driver through there. It used to come included, but now you need to use the ADV and SDK manager and download the drivers as an SDK Component through there.
After that, make sure your phone is set to USB Debugging mode and plug it in then point windows to the new drivers. If it doesn't want to install the new drivers, you might need to remove the old ones first. I had to use USB Deview (DL link at bottom of page) and removed all installed HTC drivers. After that I plugged my G1 back in, pointed it at the newly downloaded drivers and all was well.

I'm running adb/fastboot/android sdk on win7 64b ultimate. The drivers are included in the sdk download. Once you download the sdk, make sure you have java installed. (I had to install JRE and JDK to get it to work properly, not sure if this was needed) Anyhow, when you have the sdk downloaded, run the sdk setup program. Go to settings and check the box for force update (unsure of the exact terminology used there) then go to available updates and your drivers are the last option on the list.

[Q] Epic USB drivers for win7 32bit HELP

Hello all I'ave been trying to root my epic 4g for the last couple of days now without any success. I narrowed the problem down to not getting the USB drivers install. I am running windows7 32bit and have downloaded the same drivers from links on this site and also from samsung's site directly. The file that I downloaded comes as a "windows installer package type" after its unzipped so it installs automatically upon opening.
After the attempt install I get the following message:
Device driver software was not successfully installed
Coprocessor X No driver found
Base System Device X No driver found
Base System Device X No driver found
Can someone please help on this issue. I have searched the forums without any success and I refuse to believe that I'm the only one with this problem..

reinstall the .exe file, but right click and run as administrator. when you plug your phone in, uninstall the drivers through the device manager to make it "search" for updated drivers. worse comes to worse, instead of "automatically search for drivers" in the device manager, manually choose where the drivers are and navigate to the program (usually samsung something or another) and tell it to search.
make sure you have any other samsung driver or program uninstalled. some people have been having trouble with this.

This is the problem because this file is a windows installer package type after unzipping if I right click on the program my only option is to install, repair or uninstall. I'm not getting an option to run as administrator or am I even getting to see any files much less an EXE file.

Is there any way I can change the file type from the Windows Installer Package (.msi)?? And what should I change it to so it would act a little more friendly.

I would install pda net which is bundled with the app, plus you get a decent tethering app.
Sent from my SPH-D700 using XDA App

sflores91 said:
I would install pda net which is bundled with the app, plus you get a decent tethering app.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That did it.
Thanks alot. Now I can get some sleep.
You guys are great...
Goodnight.

I personally would like to know of any foolproof way of installing drivers on windows 7... I scripted an all in one root and recovery program, and by far the biggest issue is failed drivers in windows 7... I've been avoiding installing window 7 on my bootcamp partition, but I may have to just so I can experience the same hell as everyone else.
Even if Odin3 is Windows only, at least drivers aren't an issue on my Mac.
Sent from my SPH-D700 using Tapatalk

You can install regular drivers by holding F8 at windows boot and disabling "driver signature" and then installing the drivers.
You can also permenantly dissable "driver signature" just google it,i forgot how to do it,its in gpedit.msc somewhere,i think.

DRockstar said:
I personally would like to know of any foolproof way of installing drivers on windows 7... I scripted an all in one root and recovery program, and by far the biggest issue is failed drivers in windows 7... I've been avoiding installing window 7 on my bootcamp partition, but I may have to just so I can experience the same hell as everyone else.
Even if Odin3 is Windows only, at least drivers aren't an issue on my Mac.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Above is a fullproof way,just dont install 64bit.

lviv73 said:
Above is a fullproof way,just dont install 64bit.
Click to expand...
Click to collapse
Thanks for the response, I'll look into it...
Does that mean to install 32 bit drivers even on 64 bit windows?
Just trying to clarify...
Once I find a solution that works reliably, I want to put it in my original posts so that others can benefit from it.

bugee_d said:
This is the problem because this file is a windows installer package type after unzipping if I right click on the program my only option is to install, repair or uninstall. I'm not getting an option to run as administrator or am I even getting to see any files much less an EXE file.
Click to expand...
Click to collapse
not to beat a dead horse or anything....but .msi's shouldnt need to be unzipped, they should be executable that will bring up windows installer...maybe im missing something but glad you got it worked out!

So i was trying install ADB on both my windows XP and windows seven/ no Usb package?

So I'm desperately working to get my n1 installed on either of my machines but it needs the USB driver package in order to install the android 1.0 thing it usually does otherwise it will be unsuccessful (Any other ways to install the n1 would be greatly appreciated) ANYWAYS I just completely removed my SDK from my computer and when I went back in I coudn't help but notice on both of my machines (Xp sp3, Windows 7 ult) there was no USB package.
Am i forgetting something? It's been so long since I've had to do this.

When you unzip the sdk, you have to run SDK Manager in the sdk folder. Ignore the "chose packages to install" window, and take a look at the SDK AVD Manager window. Select Available Packages, then expand the Third Party Add-ons, then expand Google Inc. USB Drivers is the next to last option...
Sent from my Nexus One using XDA App

i also recommend trying out the PDANet drivers. Just install the PDANet application on your PC and it should make sure you have the proper drivers set up. Alternatively, use the "USBdeview" utility to delete all USB drivers related to Android/HTC/adb and then install the PDANet drivers.
Good luck.

[Q] fastboot no longer works

I have a folder for android stuff like fastboot and adb that I keep for fixing my phone. I keep the minimum files required for fastboot to work... adb.exe, adbwinapi.dll, fastboot.exe and the 64bit usb drivers.
I used to be able to use fastboot even after formatting my computer (and reinstalling the drivers), but it's been a long time and when I tried to do the same again, it no longer works.
Windows says the driver is not compatible with the device. I download Android SDK Tools to download the usb drivers there. They install, but fastboot still doesn't detect the phone.
I tried following tutorials out there to get fastboot to work, but I tried on 2 HTC Dreams and they don't get detected. What am I missing?
Only thing I remember being different is that I'm using Windows 7 x64 SP1 now and before I was using plain Windows 7 x64.

You need to use the usb driver removal tool and install the usb driver from SDK.

yes you've got my same trouble.
this is my thread.. http://forum.xda-developers.com/showthread.php?t=1032249
i solved with backtrack 3.. don't ask me why because i don't know.. i just have a try with bt3 because i use bring it with me on my pendrive (it can ever be useful )

BeenAndroidized said:
You need to use the usb driver removal tool and install the usb driver from SDK.
Click to expand...
Click to collapse
The old drivers I had were never installed. For some reason, Windows did not recognize a compatible driver. I did download a fresh set of drivers from SDK and windows did install them, but fastboot devices is not listing anything.
P4p3r1n0 said:
yes you've got my same trouble.
this is my thread.. http://forum.xda-developers.com/showthread.php?t=1032249
i solved with backtrack 3.. don't ask me why because i don't know.. i just have a try with bt3 because i use bring it with me on my pendrive (it can ever be useful )
Click to expand...
Click to collapse
I see no reason why I can't use fastboot on Windows if it worked before. Perhaps if there is no other way, I'll try Linux distros.

It sound like there is no compatible driver for Windows 7 x64 SP1. Check google to see may be they might have an updates.

BeenAndroidized said:
It sound like there is no compatible driver for Windows 7 x64 SP1. Check google to see may be they might have an updates.
Click to expand...
Click to collapse
So there is an actual difference between win7 and sp1 in regards to the drivers and not that I set it up wrong?

From my experience on working with Windows. Every version always different. As far as how much different, I can't tell.
If you had it working with W7 before SP1, then there is a change in driver that causing it not to work correctly. Do you required to upgrade to W7 SP1? Or is that your preference?

BeenAndroidized said:
From my experience on working with Windows. Every version always different. As far as how much different, I can't tell.
If you had it working with W7 before SP1, then there is a change in driver that causing it not to work correctly. Do you required to upgrade to W7 SP1? Or is that your preference?
Click to expand...
Click to collapse
Well that's all I can think of. Just wanted to know if anyone else had problems with sp1. I think faastboot should work with my winxp vms.. gonna try that next time I try to use fastboot..

MTP Drivers for Windows

Does anyone know where I can find the MTP drivers for the Nexus 10? I made a mistake and need to re-install it for my PC to be able to transfer files to my N10 vice versa. Any help would be much appreciated.

MTP Drivers shouldn't typically be needed for Windows. If you have just standard Windows (not N or KN), MTP should be included with the OS (at least for Vista+)
N and KN versions of Windows need a Media Pack from Microsoft (free download).
Also, you could try installing the Google USB Driver from Android SDK if you haven't already; may or may not make MTP appear if it doesn't appear under normal circumstances.

version 1.5.15.0 (32 and 64 bit) from this last August:
http://www.mediafire.com/?qp9gw2i9lwbr3qb
Also the ADB interface driver if you need that:
http://drivers.softpedia.com/get/Ot...-29505831-for-Vista-Windows-7-Windows-8.shtml

Thank you. Exactly what I was looking for. Works now

EniGmA1987 said:
version 1.5.15.0 (32 and 64 bit) from this last August:
http://www.mediafire.com/?qp9gw2i9lwbr3qb
Also the ADB interface driver if you need that:
http://drivers.softpedia.com/get/Ot...-29505831-for-Vista-Windows-7-Windows-8.shtml
Click to expand...
Click to collapse
The Google USB driver from Android SDK doesn't work? I'm confused as to why you would need either of those drivers; thought MTP was just a standard thing in Windows, and that those drivers were specifically for ADB purposes?

espionage724 said:
The Google USB driver from Android SDK doesn't work? I'm confused as to why you would need either of those drivers; thought MTP was just a standard thing in Windows, and that those drivers were specifically for ADB purposes?
Click to expand...
Click to collapse
IDK. Im just providing a link to the drivers that were asked for. Samsung says those are their mobile drivers so thats what I post. If the ones that come with the SDK work then no need to bother with these. For all I know they could both be the exact same thing, but the OP says his problem is fixed and things work now. So I guess they are good for something if you are having problems

espionage724 said:
The Google USB driver from Android SDK doesn't work? I'm confused as to why you would need either of those drivers; thought MTP was just a standard thing in Windows, and that those drivers were specifically for ADB purposes?
Click to expand...
Click to collapse
I downloaded the SDK but I couldn't find where the Google USB Driver was located. It said sdk >> extras >> google >> google_usb_driver
but I have sdk >> extras >> android >> support >> XXXXXXXXXXX
it then splits off into folders for samples, v4, v7, and v13. None of them had the usb drivers.
If you could help me find out where I can find a legitimate copy of the usb driver from the download it would be much appreciated.
What enigma posted worked after I uninstalled everything android driver related from my computer so they might have a connection?
I would still like the official google version but I just can't locate it within the sdk download.

espionage724 said:
MTP Drivers shouldn't typically be needed for Windows. If you have just standard Windows (not N or KN), MTP should be included with the OS (at least for Vista+)
N and KN versions of Windows need a Media Pack from Microsoft (free download).
Also, you could try installing the Google USB Driver from Android SDK if you haven't already; may or may not make MTP appear if it doesn't appear under normal circumstances.
Click to expand...
Click to collapse
keyword being 'typically', if this POS was working right, we wouldn't be in here looking for friggin drivers. there are tons of threads with people like me that cannot get MTP to work. We just want to transfer some files; why can't **** just work?
---------- Post added at 09:39 PM ---------- Previous post was at 09:38 PM ----------
EniGmA1987 said:
version 1.5.15.0 (32 and 64 bit) from this last August:
http://www.mediafire.com/?qp9gw2i9lwbr3qb
Also the ADB interface driver if you need that:
http://drivers.softpedia.com/get/Ot...-29505831-for-Vista-Windows-7-Windows-8.shtml
Click to expand...
Click to collapse
the mediafire link seems to be for Samsung drivers... why would that fix a Nexus 10 (or 7 which i have)

drumtrucker said:
keyword being 'typically', if this POS was working right, we wouldn't be in here looking for friggin drivers. there are tons of threads with people like me that cannot get MTP to work. We just want to transfer some files; why can't **** just work?
Click to expand...
Click to collapse
But with MTP drivers; you would either have OS support, or have to download Microsoft's media pack; drivers shouldn't have anything to do with MTP. If MTP doesn't "just work" then:
- Your on an unsupported OS (below Vista (such as XP); or a N/KN version of Vista+)
- If on a N/KN OS, you need the Media Pack from Microsoft (N/KN lacks the needed media features by default)
- If on Linux, you'll most likely need something to read MTP (gMTP on Ubuntu worked fine)
- You have "messed up" ADB drivers (in which case; uninstall them, and MTP should immediately become available on a supported OS; I had this happen a few times, but it wasn't too common, nor do I even know why it happened lol)
- USB port (on computer or Nexus 10), driver (on computer), or cable itself is malfunctioning in some way
As for ADB however; in order to have it with the Android SDK, you need to download the USB drivers with the SDK executable (I think it actually automatically checks itself anyway when you open the SDK for the first time). But ADB and MTP shouldn't affect one another.
I've installed Windows 7 and 8 numerous times, and even messed with Linux a bit. On 7 and 8, MTP just worked. Linux (Ubuntu) needed some program to read MTP, but worked just fine afterwards.

espionage724 said:
But with MTP drivers; you would either have OS support, or have to download Microsoft's media pack; drivers shouldn't have anything to do with MTP. If MTP doesn't "just work" then:
- Your on an unsupported OS (below Vista (such as XP); or a N/KN version of Vista+)
.
Click to expand...
Click to collapse
On windows 7HP... and it doesn't just work. Before posting above whine I had tried all the solutions that seemed even vaguely appropriate. Before installing SDK kit to apply 'fresh drivers' it would see as 'unidentified device'. After installing ADB stuff, it will see as Android device if debugging on and MTP if debugging off... BUT 'MTB' drivers do NOT install... no driver installs for MTB function.
Tried another posters work around of going to camera mode (which it will do) and moving files into the DCIM folder and moving with Astro (or some such) afterward. It worked once then kept rejecting my .avi and .mkv files because 'camera [would not like them]. Then it started letting me do it again. Also found AirDroid and WiFi File Explorer as way to accomplish file transfers.

drumtrucker said:
On windows 7HP... and it doesn't just work. Before posting above whine I had tried all the solutions that seemed even vaguely appropriate.
Click to expand...
Click to collapse
I imagine your also on the latest Service Pack, know for a fact your not on a N/KN OS, and also have nothing intentionally blocking MTP (Group Policy Settings, Security Clients, Automatic-Tweak Programs, etc.)?
The MTP device appears whether or not my ADB drivers are installed, and whether or not Android USB Debugging is enabled. Not sure what else I could suggest to get yours working other then a fresh (non-OEM) re-install of Windows.

espionage724 said:
I imagine your also on the latest Service Pack, know for a fact your not on a N/KN OS, and also have nothing intentionally blocking MTP (Group Policy Settings, Security Clients, Automatic-Tweak Programs, etc.)?
The MTP device appears whether or not my ADB drivers are installed, and whether or not Android USB Debugging is enabled. Not sure what else I could suggest to get yours working other then a fresh (non-OEM) re-install of Windows.
Click to expand...
Click to collapse
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!

drumtrucker said:
SOLVED:
in device messenger, right click on 'unknown device' and update driver/browse my computer../let me pick from list.../portable device/Manufacturer(standard MTP device)/MTP USB device
say YES to install anyway (even though it will blow up the world). after install, unknown device changes to Nexus 7 (or 10 I would hope, but I have 7), this also fixes problem with my Kindle Fire HD 7.
YaY!
Click to expand...
Click to collapse
this has worked for me, thank you