Related
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.
Am I the only one having issues with adb?
I managed to get it working once yesterday night. adb logcat output was very helpful to fix the FC 'parameters' issue with libcamera under Eclair but I couldn't get it working after that. Also, when it did work, I couldn't get /system to remount rw.
I had to manually start adbd on the vogue but after I rebooted to test the new libcamera libs, I couldn't get it to work anymore, even after restarting adbd. I can see a HTC Android device in /proc/bus/usb/devices on my linux dev computer but 'adb devices' doesn't show any devices.
This was under VaniljEclair RLS6.
I did a quick search in 'Touch CDMA Android Dev' and 'Tilt Android Dev' forums, also search in google but couldn't find any quick answer.
I don't have much time (as everybody I guess) to mess with Android Dev so I would much rather spend the little time I have on something productive instead of searching for answers that somebody else might already have.
I don't mind switching to another Eclair ROM/build if I have to but I would appreciate if anybody could give me a few pointers to get adb working under eclair.
Thanks.
dlepage said:
Am I the only one having issues with adb?
I managed to get it working once yesterday night. adb logcat output was very helpful to fix the FC 'parameters' issue with libcamera under Eclair but I couldn't get it working after that. Also, when it did work, I couldn't get /system to remount rw.
I had to manually start adbd on the vogue but after I rebooted to test the new libcamera libs, I couldn't get it to work anymore, even after restarting adbd. I can see a HTC Android device in /proc/bus/usb/devices on my linux dev computer but 'adb devices' doesn't show any devices.
This was under VaniljEclair RLS6.
I did a quick search in 'Touch CDMA Android Dev' and 'Tilt Android Dev' forums, also search in google but couldn't find any quick answer.
I don't have much time (as everybody I guess) to mess with Android Dev so I would much rather spend the little time I have on something productive instead of searching for answers that somebody else might already have.
I don't mind switching to another Eclair ROM/build if I have to but I would appreciate if anybody could give me a few pointers to get adb working under eclair.
Thanks.
Click to expand...
Click to collapse
Are you using the Latest Kernel? Adb is supposed to be fixed with eclair a kernel or 2 ago. If so, Im no sure what the probem is.
Are you running windows, ubuntu ect...?
The adb problem is in the build itelf. As soon as I installed my adb quit working I went back to incubus build but it just gets really quirky after a while. I use Vanilj eclair for speed but really miss adb. And yes I am using the latest kernel I also tried troubleshooting by flashing other nbh files to no avail
incubus26jc said:
Are you using the Latest Kernel? Adb is supposed to be fixed with eclair a kernel or 2 ago. If so, Im no sure what the probem is.
Are you running windows, ubuntu ect...?
Click to expand...
Click to collapse
Eum, I'll have to check for the kernel version. It is the one included with KK VaniljEclair RLS6. The date of zImage is 24/06/2010. What was the issue again, /dev major/minor conflict between adb and 3d hardware? Is there a way to check if this is the issue from within my phone (with terminal)?
I am running Fedora Core 13 as a VirtualBox guest hosted on Windows 7 x64. As I can see a HTC Android device in /proc/bus/usb/devices in linux, I would say that VirtualBox usb passthru is not the issue but then again, I could be wrong.
Before I setup VirtualBox usb passthru, I was also having issues under Windows: it installed a few drivers but I still couldn't see the phone as Mass Storage under Windows. Is there a way to install Android Windows driver without installing the Android SDK under Windows? Since Windows is not supported for AOSP dev, I'd prefer to keep my Windows 'Android free' as far as SDK,tools, etc goes except for 'Mass Storage' access.
Hope I am making sense... As I said, all this Android business is new to me, I am probably forgetting something trivial in my setup.
Yes it is a issue in /dev with 3d hardware. You can flash latest nbh without reinstalling all system so i think that you go faster in this way.
dlepage said:
Eum, I'll have to check for the kernel version. It is the one included with KK VaniljEclair RLS6. The date of zImage is 24/06/2010. What was the issue again, /dev major/minor conflict between adb and 3d hardware? Is there a way to check if this is the issue from within my phone (with terminal)?
I am running Fedora Core 13 as a VirtualBox guest hosted on Windows 7 x64. As I can see a HTC Android device in /proc/bus/usb/devices in linux, I would say that VirtualBox usb passthru is not the issue but then again, I could be wrong.
Before I setup VirtualBox usb passthru, I was also having issues under Windows: it installed a few drivers but I still couldn't see the phone as Mass Storage under Windows. Is there a way to install Android Windows driver without installing the Android SDK under Windows? Since Windows is not supported for AOSP dev, I'd prefer to keep my Windows 'Android free' as far as SDK,tools, etc goes except for 'Mass Storage' access.
Hope I am making sense... As I said, all this Android business is new to me, I am probably forgetting something trivial in my setup.
Click to expand...
Click to collapse
There is a makedev script in the initrd.gz that differs between the initrd.gz originally included with the haretinstall.zip and the one I use. I use the initrd.gz that dzo shared here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
But first try the latest zImage from that site. If it still fails, try using the initrd.gz from this zip-file: http://sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
kallt_kaffe said:
There is a makedev script in the initrd.gz that differs between the initrd.gz originally included with the haretinstall.zip and the one I use. I use the initrd.gz that dzo shared here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
But first try the latest zImage from that site. If it still fails, try using the initrd.gz from this zip-file: http://sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
Click to expand...
Click to collapse
Did some more test.
adbd is not running under Android (VaniljEclair RLS6). Using Terminal emulator, I manually start adbd on the phone. Then, I connect the USB cable. From this point adb works from linux. Is it normal that adbd is not running after a fresh boot of the phone?
This is using the zImage and initrd from your androidinstall.tar, as far as I can see by the dates and files size. I am running from the sdcard, in case it matters.
No sweat though, I now have a work around so it is no big deal.
dlepage said:
Did some more test.
adbd is not running under Android (VaniljEclair RLS6). Using Terminal emulator, I manually start adbd on the phone. Then, I connect the USB cable. From this point adb works from linux. Is it normal that adbd is not running after a fresh boot of the phone?
This is using the zImage and initrd from your androidinstall.tar, as far as I can see by the dates and files size. I am running from the sdcard, in case it matters.
No sweat though, I now have a work around so it is no big deal.
Click to expand...
Click to collapse
Strange, this should be controlled by this in sysinit.rc:
Code:
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
And the persist.service.adb.enable property should be enabled by default.
So. I have a desktop and laptop.
The only difference between the two is that one (my laptop) is running a 64 bit OS. (win7)
I was able to install the sdk and drivers on my desktop, but not my laptop.
I use my laptop a lot more often and it would be nice to be able use it for my phone.
Any ideas?
It works, just check the guides. Where exactly are you stuck or how is it not working?
Well, it installed the drivers just fine.
But I use it (mainly) for adb and such,
which doesn't appear to be working,
and also, ddms for screenshots isn't opening.
For DDMS I used the following Java:
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=java_ee_sdk-6u1-wjdk-oth-JPR%40CDS-CDS_SMI
As for ADB, does your phone show as Android Composite ADB Device under Android Phone in the device manager?
Downloading that java now, thanks. Im pretty sure I already have it installed, but you can never be to sure. I will check the adb as soon as I find my cord. It probably DOES work, I think I've gotten it to work before, I just don't use it as often as ddms ( for some reason, my ROM doesn't let shootme and drocap to work, so I need a screenshot program )
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
Hello
Im brand new to Android and adb/fastboot.
I have looked at tutorials on youtube all day, and for everybody else their devices just pops up when you type adb devices.
I get nothing
I have done it correctly, because I get all the commands when I type adb/fastboot.
Im running windows8, could that be the problem?
Do I need some kind of extra USB drivers for my google glasses?
I do find my glasses as a camera tho.
EDIT:
So after watching a few more tutorials I understood my problem. Its windows8 usb drivers thats not correct.
I have tried to install correct drivers and edit the .ini files that need editing, but now I encountered a new problem.
Windows wont let me install correct usb drivers for google glass.
When I have device manager open, windows have already installed them as “Portable device – Glass1″
I click uninstall and they disaper from my device list, once I click “scan for new hardware” I can see that they reapper on my device list as other devices. Within 2sec windows autoinstall them as “portable device -glass1″ again.
So I try “update driver software” but this dont work either, I select the correct file and path, but I keep getting this message “windows has determined the driver software for your device is up to date”.
Im running windows8.
Any help is appreciated.
EDIT2:
As far as all the tutorial movies tell me to disable driver signing I have done so.
If all of the adb commands were working, then chances are you need to enable debugging on your Glass. Settings >> Device info >> Turn on debug
Update:
The way to bypass windows8 and installing usb drivers, is that I need to use the option "Have Disk" and then install usb drivers that way.
All works fine now.