Hi all,
I've searched the forums (honestly), but I can't find an answer to my problem.
I have a Vodafone branded 32B phone.
I installed the AndroidSDK as supposed to, added the path, made the phone root, booted into the recovery console using fastboot and flashed my phone with different operating systems... but during all this time I hever got ADB to work.
Whatever I do, adb never finds the phone. Fastboot works and finds it, when it's in fastboot mode, but ADB never. So, I can't permanently install the recovery console nor do any of the other funky stuff.
ADB doesn't work when the phone is in fastboot mode nor normally operating. I have USB Debugging turned on. The phone works normally and I can access the SDCard just fine.
Any help?
Suggestion.
Look into purchasing a G1 to be kept as a spare and used for development. That's what I've done with my G1. GParted is within most recovery images nowadays, therefore you can do most anything there, well...important functions that is. Keep that in mind.
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Reignzone said:
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Click to expand...
Click to collapse
that's what i had to do to get it to recognise my phone.
i'm pretty sure the driver came with SDK. either way i've attached the one i used.
go into device manager and update the driver it's currently using with the attached one.
Incorrect driver.
It should be the 1st driver listed in the Android SDK file.
As far as I know, you could also choose to push ADB to your system32 file folder under the C: drive in your computer. That is if you're using a Windows machine.
just a thought
Are you on windows or linux? If you're in ubuntu try sudo adb ... the default unprivilaged user doesnt automatically have access to the device.
If you're in Windows I would uninstall the Android Phone device in device manager and reboot with the phone disconnected. Then connect it and install the usb driver from the sdk when prompted. Might also pay to download the sdk again.
Install HTC Sync
Another known way to fix the issue is to download and install HTC Sync http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
This seems to install the correct drivers
For more info check the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec02
Hey Guys,
Forgot to mention I'm on Windows Vista 64 bits.
That last suggestion did the trick. I went to the site and downloaded the HTCDriverUpdate_Vista_64bits.exe, and within seconds I had an ADB connection.
Thanks for your help!
Related
Hello
I have a stock Vodaphone Magic and I'm looking to root it, but to do this I need to get adb to see it, which I'm having problems with.
When I plugged it in first to charge it used window's default drivers for the SD card etc. Trying to update the drivers with the ones included in the SDK dosn't seem to work as Windows says that they're less recent.
Also, I can't see any sort of "ADB" section in the device manager, even with USB debugging turned on in the phone.
Any help? I'd really like to root my phone so I can use WPA Enterprise!
Edit: Already read the wiki page, no help.
I remember having this problem when I first set up the Android SDK.
However in my device manager I did have a device, it wasn't called Android or Magic or anything similar. From what I remember it was a bunch of random letters and numbers.
From there I right clicked it, went to Properties, Update Driver and then pointed it to the directory with the drivers.
Thats how I did it in Windows 7, if that doesn't work for you then I'm not sure sorry.
Hi,
I recently had the same problem as you. The first time you plug in your phone sometimes Windows will assign USB drivers to the device instead of the ADB interface. To correct this, I uninstalled the drivers and pointed the computer to the ADB files as the new drivers. After those install it should be labelled correctly and work.
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.
Hi guys.
Sorry for this noobish post, but i cannot remember for the life of me on how to install things by using 'adb' - i know there is an option on the phone, but where bouce is it? I used it when rooting, but i just cant find it.
I'm trying to install a new boot image, but when i go into cmd i type "adb remount" and the reply is "device not found"... AndroidSDK is in my C directory.
Another EDIT; I just rebooted my device into the recoverymode, and i didn't see ndroid back up thing, does that mean my phone hasn't actually been rooted... - But my phone is deffently debranded.
Thanks if anyone can help my noobish style.
Slim.
When in recovery mode you must have the driver installed. If you enter 'adb devices' it should give you the serial number of your device, if the driver is installed correctly.
To enter the recovery menu you must run the recovery-windows.bat from modaco if using windows or a similiar file (recovery-linux.sh, recovery-mac.sh) according to your operating system. The file should be run when in recovery-mode or else it returns a whole bunch of errors.
Awesome, thanks mate. Just what i needed! Could i have advice what driver i need to be able to acsess the adb?
I just use the driver supplied in the newest version of ADB.
You can get it here. usb_driver.rar
Or else just install HTC Sync from htc.com. It also has the driver files needed.
Remember to have USB Debuging enabled from the Programs/Development menu.
Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
wakers said:
Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
Click to expand...
Click to collapse
Have you got Android SDK installed on your PC, Im sure the driver is in there...android .1.0 driver I think..
Without Android SDK you cant use fastboot flash for clockwork image..
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Did you install and launched HTC sync? It should install all the necessary drivers.
f.
Sent from The Galactic Empire using the Dark Side of The Force
wakers said:
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Click to expand...
Click to collapse
Ok try this.... shut phone down, boot (volume down and power button) selected fastboot so it turns red, put the files into android-sdk-windows\tools. i-e the clockwork image and fastboot files
Plug usb cable in.
In "windows search program files" type cmd
now type cd c:\android-sdk-windows (unless you placed the android sdk somewhere else!!)
type cd tools
Type fastboot-windows flash recovery recovery-clockwork-2.5.1.2-ace-modaco-r2.img
When done type fastboot-windows reboot
You should now have CWM.
Now I know you may have tried this but It would help to find out what happens if you haven't already do so.
EDIT ...I also ask this because my laptop doesn't do anything either when I plug in usb cable in fastboot mode..im on windows 7....
Just trying to help...
Really appreciate the reply.
I got a "cannot load" Error.
I think its down to a driver for my phone when in the fastboot mode.
Whats might shed some light on something for someone with a bit more windows/android knowledge than myself is
When the phone is in Fastboot USB mode in Device manager the phone is listed as Android Bootloader interface but when i type into cmd "adb devices" nothing is listed.
When the phone is switched on normally and syncing with HTC sync in device manager the phone is listed as "my htc" and when i type adb devices in cmd, the message adb server is out of date killing...
then daemon is started and the device shows in my list ?
But HTC sync stops working ?
And the internet on my laptop stops working bizarrly.
I'm really scratching my head now lol
I'm thinking it must be something to do with not having the correct driver for Fastboot USB mode ?
Finally sorted it, had to remove the phone from device manager and delete the driver.
Then went into programs and features and removed everything to do with HTC.
Re-Installed HTC Sync
which also reinstalled HTC drivers
Plugged the phone in let windows select the driver and instead of showing in device manager as Android Bootloader Interface it showed as My HTC Sync and worked first time, not sure what happened but sure glad thats finally sorted..
Rixsta really appreciate the advice...
Cheers
Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.