[Q] ABD Drivers + Windows 7 issues (plus a couple more questions) - Hero CDMA Q&A, Help & Troubleshooting

Hello XDA Community.
I'm attempting to install the new RC of CyanogenMod-6 for the Hero CDMA. I'm currently running the stock 2.1 version of Android. I've been following the guides that were referred to in the thread (I tried posting the urls but new users can't do so to prevent spam).
I've successfully rooted my phone and now I'm trying to do a Nandroid backup. I'm running Windows 7 32-bit and have hit a road block with ADB not recognizing my device. I followed the guide put together by Nephron to install the Android SDK. I've spent several hours going through threads and doing google searches looking for the solution. I have debugging turned on and I don't mount my SD drive when I plug the USB cord in. I've used USBDeview as some have suggested to delete current HTC drivers and then reinstall - no luck.
Here is a screen shot of what happens when I plug in my Hero:
See attached - "failedinstall.jpg"
Then I'll go to device manager to manually install the driver (it never allows me to manually select upon connection for some reason):
See attached "devicemgr.png"
And then this is the message I get when I point it to the "right" folder with the drivers:
See attached - "unabletoinstall.png"
So, on the Android SDK site I noticed this message:
"The USB driver for Windows provides support for the following Android-powered devices:
T-Mobile G1* / ADP1
T-Mobile myTouch 3G* / Google Ion
Verizon Droid*
Nexus One
* Or similar hardware on other carriers
Any additional devices will require Windows drivers provided by the hardware manufacturer.
^So is all of this HTC's fault? I've downloaded a couple of different .zip folders from different threads claiming that these drivers would work. But none of them have yet to do the trick for me.
I'm new at this so I have a few other questions as well:
Most guides I've read about how to do a Nandroid backup always recommend flashing a ROM b/f doing a backup. But I want to backup my current stock rom and settings before I flash. Wouldn't I want to create a recovery image before installing any other ROMs? Perhaps I'm misunderstanding some requirements?
Referring again to the thread on the CyanogenMod RC, can someone help me understand step #3? How do I know if it is necessary to update my radio? What implications does this have? I tried looking for info about this on the wiki and I couldn't find anything comprehensive enough to answer my question.
I'd appreciate any guidance!

Before you modify anything you will want to boot into recovery, assuming you flashed one, by holding down Home and turning the phone phone back on(power button). But since you don't have adb working then you probably haven't. You can still do this using terminal on your phone.
Download terminal emulator from market and then download a revoery image (AmonRa 1.6.2 or Darch's 1.7xx) and then mount your sdcard to the computer and transfer the recovery to the root of the sdcard. Open up terminal emulator and type in
Code:
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.6.2.img(type the exact file name of the recovery you are using)
reboot recovery
If you had factory 2.1 on your phone then you have the latest radio. The radio can be flashed just like any ROM, but make sure that the radio is not for GSM phones as this will destroy your phone.
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others)
Latest windows sdk version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may change with further updates..
Run C:\AndroidSDK\SDK Setup.exe
If you get an error about not having Java SDK installed but you do, add the path to 'bin' within your Java installation location to the Path environmental variable as described above before the sdk entry you just made. (eg add "C:\Program Files\Java\jdk1.6.0_20\bin;") This is likely to only be necessary where the 64 bit Java SDK is installed (obviously) on a 64 bit machine.
If it gives you an error about http go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
If all else fails try installing HTC Sync software-- http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC_Sync_2.0.40.exe and then removing the drivers for it and then trying to install the android sdk drivers
Or you can dual boot with Linux and all you will need to do is download and unzip android sdk and edit 2 files and everything will work.

WOW>>>>>no that is way to confusing. the best thing to do is install vmware workstation. Then do a virtual WINDOWS XP MODE. from there you will be able to install the drivers and such in order to get the phone to be seen.

the version of htc sync i used for all my computers including win 7 was 2.0.33
if you want it then just pm me and I will get it to you
they don't offer it for a download anymore
this version corrected all my driver issues

Related

Help with ADB

When I tried to install it, it failed and now when I try again it says
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
you dont install anything. you extract the android sdk into the c:\. then you copy the two files mention in the thread to c:\windows\system32. you then go to start>run>cmd(enter). type adb devices. ADB is ALL COMMAND LINE. THERE IS NO PROGRAM YOU INSTALL
what two files?
blackfire1 said:
what two files?
Click to expand...
Click to collapse
~sigh~ are you sure you read how to do this at all?
adb.exe and AdbWinApi.dll are the two files that need to go to system32
and then install the drivers from your usb_driver folder from the SDK. Use the AMD one if you're using a 64bit OS or the Intel one for 32bit OS.
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
blackfire1 said:
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
Click to expand...
Click to collapse
System Restore and try it again.
that has nothing to do with adb. that means your driver installer that is resident in windows is corrupted. unless you can system restore to a point at which it was working, the only real fix is going to be a new windows install. not entirely sure how one breaks the library for installing device drivers, but hey, thats what you've got.
Ok the problem was solved when I used my other computer.

Problems with ADB install..

Hello all,
I have been following the guide posted by Nephron http://forum.xda-developers.com/showthread.php?t=532719 but am having a few problems with my computer recognising my G1 as an ADB device...
My computer's OS is Vista. I have followed the guide to the letter, have downloaded the SDK and unzipped it to C:\ root. I have checked my phone and ensured that 'USB Debugging' is checked. My computer doesn't try to install the Android 1.0 driver (as the original drivers are already installed) and my device is ready to use as a storage device - HOWEVER it is not acknowledging it is an ADB device.
I have tried using USBDeview but it won't let me uninstall the 3 already installed Android drivers. I have even tried manually uninstalling them through the taskbar USB device manager. Even when I uninstall them and re-connect my phone, it automatically installs the standard drivers and doesn't give me an option to select the SDK drivers.
Hope that makes sense to someone. How can I install these damn SDK/ADB drivers on my G1?! Thanks.
Try this...
Remove every mass storage device except your phone (Any usb memory sticks, external HDD's, other phones, etc)
Open the start menu, right click on 'Computer', click 'Manage', and you may need to click continue here.
On the next page, click on 'Device Manager' on the left hand side. In the list on the right, open up the tree for 'Universal Serial Bus Controllers'
Find 'USB Mass Storage device' in the list. Right click it, click 'Uninstall'
Click 'Action' at the top, then 'Scan for hardware changes'.
If it all goes well, you should now be asked to locate a driver, point the the Android USB driver. Good luck.
PS, this is all from memory of the issues I had, so if you get stuck, post back .
Worked a charm, thanks!
(Mods...can this be merged to the NEWBIE Q&A thread for ADB/Fastboot etc...more useful place for it than here!)
Glad I could help .
OK...
New problem...
I am using command prompt on vista, entered the following:
cd C:\android-sdk-windows-1.5_r2\tools
adb devices (shows my device listed as HT845KV02724)
adb shell (shows a # on the following line)
However....when I enter adb it returns with /sbin/sh: adb: not found .....what have I done wrong? I have checked that the SDK is in C:\ and have downloaded the SDK again just to be sure. What do I need to change???
Once you type adb shell, you're in a terminal on your phone, you can type shell commands there, you need to type exit before typing adb again.
Basically, it's working as intended .

[How to] Install android_winusb.inf, create adb shell loop, and root your phone

First off you need to have Android-SDK installed on your computer. I will not go into details about that process but here is the link to Google's official install page. Navigate to the folder you placed Android-SDK and run the SDK Setup.exe and make sure that you download the usb 3.0 driver software from the sdk updater window. I recommend erasing any HTC Sync software or drivers so that you can start from a clean point then reinstalling them.
Once you get the SDK installed from Google you need to go in a modify the USB 3.0 .inf file. Navigate to the folder you placed the Android-SDK and one step down you will see a folder that is named usb driver. Open the usb driver folder and then open the android_winusb.inf file in notepad. It should default into notepad when you click it. Next you need to copy and paste this text into notepad.
Find the section labeled [Google.NTx86]. At the end of that section, add the following lines.
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
Then find the section [Google.NTamd64]. At the end of that section, add the following lines.
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
Again just copy and paste. I have attached pictures to show where these need to go.
So now we have the USB driver on the computer and ready to be installed once you plug-in your Incredible.
On your Incredible press->Menu->Settings->Applications->Development->(check)USB debugging. Plug in your Incredible and you should get the found new hardware notification, select the No, not this time radio button, Install from a specific location(Advanced), Don't search, I will chose the driver to install. You should now have "Android Composite USB Device" in the white field selection box, click have disk and browse to the location of the android_winusb.inf file and click ok. Click next and it should install the USB driver you need for ADB to work properly.
Now if you click Start->(right click)My Computer->Properties->Hardware(tab)->Device Manager, you should see Android Phone at the top then when you open the tree you should see Android Composite USB Interface.
This will enable you to use the Android SDK from a command prompt to access your Incredible.
Once that is done open a command prompt by clicking Start->Run(XP) or the search box in W7 and type CMD(in W7 you need to right click command prompt and run as admin.). Then in the command prompt window type; cd (your file path to Android-sdk). now to test it type adb shell and press enter then reboot recovery and press enter. This should reboot your Incredible into recovery. (You can also type reboot bootloader to get to that screen.)
Once you make sure that is working press vol. up and power, then select reboot with the power button. GO back into Settings and deslect the USB debugging check box. Now we need to get adb shell to loop so that it can catch the Incredible in its flawed sequence that allows us to access the phone in recovery. Navigate your command prompt box to your tools folder and then follow these directions courtesy of prerunnerseth over at AndroidForums.com
type edit loop.bat
in edit enter the following
Code:
@echo off
:TOP
adb shell
GOTO TOP
press alt-f then x
hit enter for yes
Here is a link to Androidforums.com with two different methods for gaining root access on your phone.
This is a great 10 min. video on how to root as well.
I hope this helps clear some confusion up for those that can't quite get the Android Composite USB interface going. This credited to all parties involved and is just a collection of info.
So what you are saying is we need to take it off of debug mode before looping the shell command?
Hmmm...I had mine in Debug mode every time (failed every time, too). Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Here's the android_winusb.inf file for the Incredible.
Switch this file out with the one that's inside your AndroidSDK/usb_driver folder.
http://www.megaupload.com/?d=S2H4R3QZ
Here's the adb shell loop for Windows.
I placed it inside my AndroidSDK/tools folder.
http://www.megaupload.com/?d=N0150VUI
I hope this helps!
SeanRinVA said:
Hmmm...I had mine in Debug mode every time. Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Click to expand...
Click to collapse
I had mine on and it worked. Try, try, try you'll get it!
Good luck!!!
SeanRinVA said:
Hmmm...I had mine in Debug mode every time. Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Click to expand...
Click to collapse
Report back. Rooting the DI will only get simpler and more reliable the old fashioned way: a LEAK from HTC!! If we had something to flash from fastboot or recovery without first obtaining root, we would all have root except for those who didn't check their MD5's, in which case they'd brick. So this new (not you, OP, or you Unrevoked team, but this exploit in general), ****ty, hard way = relatively safe, totally unreliable. Old way = almost 100% reliable but little room for error.
jesus this is frustrating
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
sylent101 said:
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
Click to expand...
Click to collapse
It is supposed to say that... and you can't install the android sdk you can only open it... its is just a basic dos applicarion with a GUI front of it if I'm not mistaken so just try redownloading it
Try following the 10 minute video exactly on a cpu that does not have the sdk already on it. I used the same exact sd card and could not get it on my pc that already had the sdk , sync , drivers on it. I followed the instructions on the 10 minute video using the sdk and htc sync from the video link on a machine that did not have them prior and it worked first try using the first (adb shell) method. I think it had something to do with the prior sdk install I had.
another let down, tried with the 10 mins video also, oh well
sylent101 said:
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
Click to expand...
Click to collapse
Right click on Android adb interface and then select update drivers, then follow the instructions above for installing the android_winusb.inf file. As stated before SDK doesn't actually "install' it is more on an interface that you can open to download the new sdk's for app development and debugging. you should get the black box and another box that is called Android SDK and AVD manager. Within that window you should have these options on the left; Virtual devices, installed packages, available packages, Settings, and About.
Edit; Did you follow the instructions about editing PATH with the C:\Android-SDK-Windows\tools directory path?

Cannot open ddms.bat in order to take screenshots on Nexus One

I wanted to take screenshots of my Nexus One (2.2 FRF91/T-Mobile/Stock) but I'm just a newbie so I followed the guide on andriodcentral Anrdroid 101 tips. (Sorry I can't link to it since I'm a new user on these forums
That guide led me to another guide on how to install the sdk
When I tried to pull my 3rd party apps, cmd didnt do anything it simply said "0 pulled, 0 skipped", however I was able to pull my standard apps. I'm confident the sdk was installed correctly though.
I'm using a laptop with Windows 7 64bit and an AMD processor, I'm not sure if that information is helpful or not
I've already downloaded and installed the android 2.2 sdk, java runtime environment, java development kit. I've also properly installed the ADB drivers for the Nexus One. I also downloaded Eclispe but when I tried to run it, the application won't open. I have a feeling its because I didn't install it properly.
My problem now is that the ddms.bat (Dalvik Debug Monitor) won't open when I double click on it. I tried to right click and run as administrator but that didn't work either. In both cases when I try to open it, a cmd windows opens for a fraction of a second and then closes before I can read it. So I googled it and found a website that seemed to be able to solve the problem but its geared towards linux users.
I specifically followed these directions "To fix this a replace of the bundled swt is needed. The file is located under android-sdk-linux_x86-1.5_r3/tools/lib/. Rename swt.jar to swt_32b.jar. Next download swt for your platform. I have used swt-3.4.2-gtk-linux-x86_64.zip. Unpack the file swt.jar in the zipfile to android-sdk-linux_x86-1.5_r3/tools/lib/ and finally start ddms" but that didnt work either. So now my android-sdk-windows/tools/lib/x86_64 is full of other files rather than just having that swt.jar file.
Can anyone please help on getting ddms.bat to open or on how to get eclipse to open?, I'm so close to being able to take screenshots.
Some notes:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
2. USB debugging was ON when I tried it
TaeKwonDonkey said:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
Click to expand...
Click to collapse
Do you have the right drivers installed?
When your phone is on, plugged in, SD not mounted, and USB turned on, you should see "Android Phone" and "Android Composite ADB Interface" underneath that.
If you don't want to root (it's so easy and painless if you can follow instructions) then I don't know what to tell you other than:
1. Install "USB Deview" and remove all HTC/Google/Android related drivers.
2. Completely uninstall and wipe out the SDK stuff.
3. Rebooted, and reinstall Android SDK, and make sure that Windows7 installs the right drivers.
Installing the SDK is no more difficult than installing any other piece of software. If you've got Java installed, and you've plugged your phone in, and debugging is turned on, what *should* happen when you double-click ddms.bat is, the command prompt window opens, but then the Debug utility should open.
I had the screenshots stuff working before I ever rooted.
I followed the steps here: http://www.knowyourcell.com/google/...take_screenshots_on_the_google_nexus_one.html
Rooting is easy and painless. If you root, you don't have to flash a custom ROM or anything, but then you can install an app that you simply open, enable, then whenever you're doing something that you want to take a screenshot of, you shake the phone, and there it is.

Recovery mode bricked on USB Notice picture after try to enable root

Hi
(Sorry for my little english, feel free to speak french if you can)
I have try to root my 4X HD for using a better recovery app (recover pictures deleted in sd card, now you know my skill). I have use this page: (as newbie i cant post outside links)
n fact, I never had an Android device where this was that easy to achive! Our friends at XDA-Developers offer a guide and the necessary tools in this thread. Having a "Microsoft free zone" and "only" running Linux machines (yeah, even the Android ones run a Linux kernel), I was able to follow up those steps with a little adaption here and there -- and so I will sum up the results for Windows and Linux users as well:
Preparation
First you need to download the required tools, all of them available at the linked XDA-Developers thread:
o4xr.zip is the rooting toolkit
IS11LG_SystemBackupTest.signed.apk to prepare your device
Windows users only: LGUnitedMobileDriver_Ver_3.7.2_LG-P880_LGO4XHD.zip -- the Windows drivers for the device
Having everything downloaded, some additional steps are necessary at your computer:
Windows users only: Unzip and install the drivers
Linux users: Make sure adb is able to detect the device (check with adb devices). If it's not, see at the end of this answer for some hints.
Everybody: Copy IS11LG_SystemBackupTest.signed.apk to your Optimus (e.g. after connecting it via USB in MTP mode, copy the file to the internal SDCard)
Everybody: Create a new directory, unzip o4xr.zip there, and change into this directory.
The rooting process
On your Optimus, go to Settings→Security and make sure "Unknown Sources" is TICKED (i.e. contains a checkmark)
Go to Settings→Developer Options and enable "USB Debugging"
Now install IS11LG_SystemBackupTest.signed.apk (e.g. use a file explorer to find and "launch" it)
Open the "SystemBackupTest" app you just installed. Nothing spectacular will happen, so don't be disappointed here.
Hold the power button and choose "Power off and restart".
When you can see the lock screen, you may notice that the phone is running very slowly, this is normal.
Once the device is fully started up again, connect it to your computer with an USB cable. Make sure the phone is in "Charging Only" mode.
On your PC, open a terminal (Linux) resp. command (cmd.exe, Windows) window and change into the directory you've extractedo4xr.zip` into.
(on Windows, you may need admin privileges: right click, run as administrator. On Linux it did fine for me without superuser/root permissions)
Now run the rooting script:
Windows users: type root followed by the enter key
Linux users: type ./root-linux.sh, also followed by the enter key
Any Mac users? Type ./root-mac.sh, also followed by the enter key. Don't worry, it won't root your Mac/Linux machine (Windows users: it is unlikely to root your box, either
DO NOT DISCONNECT YOUR PHONE WHILE THE SCRIPT RUNS! Wait while it does its job. During that process, the phone will reboot automatically a couple of times. The script will inform you about this in your command/terminal window. Once the command/shell prompt returns, the misdeed is accomplished
Now uninstall SystemBackupTest from your Optimus. Do not launch it again at this state, or you might have to start over from step 5
On your phone, open up Google Play Store and search for "SuperSU". Update the app when prompted, then open it. Press OK to update the SU binary.
You now have root and can safely restore the "Unknown Sources" and "USB debugging" settings back to how you had them! Congratulations! Next steps are to install Titanium Backup, LBE Privacy Guard, and all the other things you might need and which require root!
At step 8. i got "command not found" in Terminal (Linux Mint), assuming script don't work i have reboot my device.
Since my phone boot but is very very slow and screen is friezed, even if i can unlock my SIM card by memory pattern (without sim card and always by memory i can see Settings of android but not down the list).
In recovery boot (Sound up + Power), my device show me a picture that would say "dont unplug charge and usb".
I guess my phone is not rooted, adb can list it but not fastbood. LG software (on windows 7) cant communicate with it because usb driver not work. I guess i've try and read more since 8 hours but my brain is off right now. Any help will be very welcome.
Cheers

Categories

Resources