if you add adb.exe to system32 folder is windows u can adb from anywhere in command prompt.. just in case adding the variables dont work
Yes!!!! That...is...Gold
vision...
if you add adb.exe to system32 folder is windows u can adb from anywhere in command prompt.. just in case adding the variables dont work
I have tested and uploaded a Mini ADB package and the ADB USB drivers for Windows Vista / Windows 7, to the Resources Centre, easy tutorial + FAQs thread here:
http://xdaforums.com/showthread.php?t=835777
I thought this would make things easier for newbies or people who don't want to download the whole SDK / Sync software
INSTALLING ADB ON MAC
Coming soon ...
INSTALLING ADB ON LINUX
Coming soon ...
Hi guys,
I've just written a guide on how to install ADB on a Mac and also cut out the need to navigate into the SDK folder to run ADB each time you want to run it.
Please take a look and let me know what you think. I'd be more than happy to merge the guides if you wanted but let me know!
http://xdaforums.com/showthread.php?p=9842005
That looks great. Would you be happy if I plagiarise your guide for the "how to install" bits on Mac, and give you full credit (of course) in my posting ?
I could just cross-link but I'd rather have all the stuff in one thread here if that's ok with you (if not I won't do it).
Yes that's fine - copy the info but if you can say it was me and maybe link somewhere to my thread or hyperlink my name or something.
That's why I posted it up here to spread the knowledge !!!!
Thanks. I need someone to help me come up with the different steps for Mac/Linux users please ? Then I can add those in.
I have a short video I did when I rooted, using my Mac, on getting ADB going with the latest sdk. I can edit/upload if you think this would be helpful.
a small question. When it prompts on the phone to select a mode, which mode should we select? Charge or disk drive? I put it in 'Charge' and the phone serial number came out nice after input 'adb devices', but wasn't sure if I'm doing right.
A little bit more info here:Hi guys,
Been doing lots of reading since my attempt to permroot my G2 last night using Visionary failed and the phone is stuck on the HTC logo screen when booting up. Still S-ON and I can get into the stock recovery ok. Tried to recover using the stock ROM but since it doesn't contain the OTA updates, it won't let me overwrite/downgrade it. So seems like my best bet is to get ADB working and then follow the procedure on that thread about dealing with semi-bricked G2. I'm comfortable with UNIX and the instruction seems to make sense but I haven't got ADB to recognize my phone yet. I have full Android SDK installed and have tried both HTC sync and ADB_HTC_Drivers_Win.zip I found on this site. In my Device Manager, (Win 7 64-bit) I do see the phone as My HTC under Android USB Devices but "adb devices" returns nothing. Now at this point, my phone is in recovery screen connected through USB, and "fastboot devices" returns the serial number for the phone. I've been pulling my hair out trying to get ADB to see my G2 and have installed/reinstalled/manually updated the drive quite few times to no avail. Any idea on how to proceed?
Thanks in advance. You guys are pretty awesome.
Steve
A little bit more info here:
When I'm on the main hboot menu, "adb devices" returns nothing and "fastboot devices" returns my G2 correctly. When I'm in stock recovery, looking at that triangle with exclaimation point, "adb devices" returns my G2's serial number but says it's offline. I have tried couple of computers with Windows 7 and XP, couple of USB cables with different ports and got the same results every time.
Any ideas? Thanks!
C:\> adb devices
List of devices attached
XXX12345 device
C:\> adb devices
List of devices attached
XXX12345 device
cd ~
touch .bash_profile
open -e .bash_profile
export PATH=${PATH}:
adb devices
C:> adb push hello.txt /data/local/tmp
C:\> adb pull /sdcard/error.log error.log
C:\> adb install Superuser.apk
C:\> adb shell
C:\> adb shell ls
C:\> adb reboot
C:\> adb reboot bootloader
C:\> adb reboot recovery