Database Info

[Guide] SDK r11, Installing adb/fastboot drivers for windows Vista/7

Ok so I've been looking around all over google and XDA for the correct way to install the usb drivers for adb and fastboot from sdk manager(r11) and there are no updated guides out there for the latest r11 sdk program... so here is my quick guide just to clearify how this is done on (Windows Vista/7) PC with Sdk r11!!!
Install Java and SDK
First Install Java jre, jdk... http://www.oracle.com/technetwork/java/javase/downloads/index.html
install programs and restart if required...
Now go visit the SDK site and download latest version (r11).zip... http://developer.android.com/sdk/index.html
Now unzip file directly to C: drive.. and rename folder to 'android'..
open 'android' folder and run 'sdkmanager.exe' install updates and packages than restart if neccessary..
ADB Driver install...
Now go to your device and enable 'usb debugging' located in settings>applications>development...
Now plug device into computer via usb and DO NOT mount device (storage) to computer!!
Now press START button on computer desktop..
Right-click on 'computer' and select properties..
Now select 'Device Manager' on upper left corner of newly opened window..
Look for device named 'Android' and open selection.. right click on under-link and select 'install drivers' or 'update drivers'...
Now select browse and go to this location than press ok..
C:/(sdk folder)/extras/google/usb_drivers
Now should say driver has been installed correctly..
Test method: Open CMD
cd/
cd (sdk folder)/platform-tools
adb devices
Should see device and number pop-up...
(ADB is located in Platform-tools folder now along with 2 .dll files needed for fastboot to work)
Fastboot Drivers Install
First powe off device, than power on holding (Back+Power)
Now plug usb cable from computer into device..
Do same exact method as 'ADB Driver Install' method..
(Fastboot drivers are located in same folder as ADB drivers)
Now to run fastboot mode in cmd prompt enter this..
cd C://
cd (sdk folder)/platform-tools
Should see device and number pop-up...
Alt method is to copy the 2 .dll files located in 'platform-tools' folder and paste them into 'tools' folder, than fast boot will run correctly off this in cmd prompt...
cd/
cd android/tools
fastboot devices
Should see device and number pop-up...
Also you could just go to ..
C:/android/extras/google in 'windows explorer'
and move the 'usb_drivers' folder to root of sdk folder (android) so then all the older guides out there for installing the drivers would actually kinda make sense.. lol
if i missed anything please feel free to add a comment!!

Edited for brevity: I'm setting up a Galaxy Tab 10.1 Retail with a W7 64 machine.
I completed the ADB section of your guide just fine and went to the Fastboot section. It says to power on using back+power. When I hold power+down volume (only option?) I end up in CWM Recovery.
Should I just power on normally and finish the guide or is there something else I should do?
Thanks for the guide btw

MarcAntonyy said:
Edited for brevity: I'm setting up a Galaxy Tab 10.1 Retail with a W7 64 machine.
I completed the ADB section of your guide just fine and went to the Fastboot section. It says to power on using back+power. When I hold power+down volume (only option?) I end up in CWM Recovery.
Should I just power on normally and finish the guide or is there something else I should do?
Thanks for the guide btw
Click to expand...
Click to collapse
well to install the fastboot driver you need to be in fastboot mode on your device... for the G1 it is back+power...

Ok, I tried it again and I left out a detail (sry). When I power on with pwr+left vol it gives me two icons. One is an Android in a box, which takes me to recovery. The other is an icon that says 'Downloading'.
This time I went to it and now I'm at a screen which says
ODIN3 Download Mode
(Protocal v2)
Reason: Force Key
Secure Mode: Nonsecure
Check Signature: Check
Waiting USB Cable.....
Click to expand...
Click to collapse
And then it has a big Android in the middle of the screen with
Downloading.....
Do Not Turn Off Target!!
Click to expand...
Click to collapse
written under it.

Ok, I hooked up the USB and went through the steps and typed in the first two commands and am now in CMD at:
C:\Android\platform-tools>
But when I type in the "..\tools\fastboot.exe devices" command it says its not recognized as an internal or external command, operable program, or bath file
Btw, after I connected the USB, I got an additional line of text under "Waiting for USB" that says "===> Connected! Press the [Start] of Odin3!!"
***Update
Ok, so I copied the .dll files into Tools and ran CMD again and this time I at least did not get that error message, but it displayed no output at all, other than to begin another prompt at:
C:\Android\Tools
And that's where I'm at now.

wel uhhmmm this guide is for the G1... lol im not really sure what downloading mode is... if that is your version of fastboot than just follow the B. Instructions for the ADB driver install... the directions are the same exact for both..

Heh. Yeah its all good. I was able to install CWM and Root it, but I would like to get ADB/Fastboot working. Thanks for your help and patience with me

yeah no problem.. sorry if i couldnt help but the only thing i know is how to get it workin on G1 lol

i see many people on the G1 thread with sdk, adb and fastboot issues... FOLLOW THIS GUIDE!!! It is instructions for latest sdk Vr11... i promise this helps..

Thanks for the guide. Been trying to get ADB up & running on Vista with no success. I'll give this a try.

no problem.. sorry if i dont answer questions right away but send me a pm or comment on here and i will try to help as soon as possible!!!

ldrifta said:
no problem.. sorry if i dont answer questions right away but send me a pm or comment on here and i will try to help as soon as possible!!!
Click to expand...
Click to collapse
i do all waht you said but i can t see the number of my device i just got

did you manually install the drivers?
adb is acceses in platform-tools directory and fasboot is in tools directory.. the drivers for each are located in extras/google/usb_drivers

ldrifta said:
did you manually install the drivers?
adb is acceses in platform-tools directory and fasboot is in tools directory.. the drivers for each are located in extras/google/usb_drivers
Click to expand...
Click to collapse
Hi,
I have the same problem:
I manually install the drivers choosen located in extras/google/usb_drivers on device manager
then it say cash: "windows did fond no driver for your device.
I tried with XP SP3, Vista, Seven: always same problem

What is your device, this guide is for the dream but the same steps can be used for other devices, but you need the proper drivers for your device
Sent from my Nexus 4 using XDA Premium 4 mobile app

Super Noob question

I am trying to get adb to work. I am doing it on a x64 vista system and I think I am getting the Path wrong. I am trying to get it to run like the page says to initialize it to read the device so I know it is working.
I can't get it to start from command prompt with out navigating to the directory it resides in. Is that right for the newer versions of ADB or am I just a monkey and can't figure out simple pathing?

I just made a folder in my c drive called ADB, and placed the entire folder with adb and the dll files required in it, along with superuser, busybox, etc.
Right click on command prompt and run as administrator.
once at system32 type: cd C:\ADB
then you will have navigated to the folder containing your ADB files.
your command prompt should now read: C:\ADB
then you can type: adb devices
it will say something about starting daemon services, and then list attached devices.
you are free to proceed with whatever instruction or operation you are doing after that.
also, make sure you have the drivers for the phone installed, or your computer wont recognize the android debugging bridge.

LowRentTechGuy said:
I am trying to get adb to work. I am doing it on a x64 vista system and I think I am getting the Path wrong. I am trying to get it to run like the page says to initialize it to read the device so I know it is working.
I can't get it to start from command prompt with out navigating to the directory it resides in. Is that right for the newer versions of ADB or am I just a monkey and can't figure out simple pathing?
Click to expand...
Click to collapse
Android Development is not for questions or Problems
Please post in the correct Forums
Moving to General

Well thanks for moving it, I will keep a closer eye on which forum I am browsing when I post.
Sent from my SCH-I510 using Tapatalk

[Q] Noob Root Walkthru

I am new to the ASUS family of tablets, and j just can't figure out how to root. I have rooted many tablets and installed custom roms before but the i cannot follow the how tos listed here. For one fastboot doesnt work on my computer. It opens and closes immediately. What i would like is a detailed step by step guide with a trouble shooting guide. I mean now i reading about downgrading, blob files and a few other things i never dealt with on my galaxy. Someone help......would love to root this thing. Email me if u want [email protected]

You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?

Check this thread, it has videos about rooting and whatnot, hope it helps:
http://forum.xda-developers.com/showthread.php?t=1663244

Northern-Loop said:
You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?
Click to expand...
Click to collapse
Yes, Bootloader is unlocked. Ok, so I tried the flashboot command, so now what? I typed the command from the walkthru "fastboot -i 0x0B05 flash recovery recovery.img " but get an errorcannot load recovery.img. So what am I missing. I have the recovery image on my desktop.....

Put the recovery image in the same folder as your fastboot application and it should work.

xAshxMoneyx said:
Put the recovery image in the same folder as your fastboot application and it should work.
Click to expand...
Click to collapse
....what fastboot folder? I installed the ADK per the instructions, I downloaded the root and recovery image. I looked in the system for a fastboot folder and do not see it. Plus when I try to type in the fastboot command now, it says it is not a recognized command. I am sure this is something simple, but I am just not getting it. Is there a more detailed step by step somewhere that will actually walk you thru the steps without assuming you know what they are talking about? I can root my phone, my galaxy tab all day long and install and change ROMS, but this one has me upside down.

When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.

xAshxMoneyx said:
When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.
Click to expand...
Click to collapse
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.

That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.

xAshxMoneyx said:
That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.
Click to expand...
Click to collapse
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......

tccc143 said:
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......
Click to expand...
Click to collapse
Ok, so reinstalled everything.....did a quick refresher on CMD directions and had it rooted with CWM in 10 minutes. I have been working in Android so long without the use of a PC that I forgot how to use the PC. Thanks for the help....now we wait for some nice roms.

Sweet, glad you got it, I've done this stuff a few times but I always have to refresh myself and take it slow on each different device.

tccc143 said:
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.
Click to expand...
Click to collapse
You should not move the folder. This can cause all kinds of problems. in the cmd prompt just type
cd \folder\folder\etc.
The cd means change directory and you start off with a backslash to set the initial path to the root of your drive. if folder names include spaces then wrap the path with quotes, cd "\folder one\folder two\etc". the prompt should change from C:\windows or whatever to what you typed in.
if you've installed on a drive other than C: then first change to that drive by typing the drive letter followed by a colon, ie D:
Good old DOS will never die.
Sent from my SCH-I510 using XDA

[TOOL] Android ADB and Fastboot MSI installer with PATH variable

Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21

Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app

Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.

Installer updated to version 1.3 based on the Android SDK 24.0.2.

no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.

Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.

ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.

Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.

Unlocked bootloader

I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app

scoreboard said:
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't come unlocked, but you can unlock it. That's why are a lot of us are on this phone. I had an S5 ordered, but decided against it, when I saw there wasn't any progress being made on it. I cancelled my order, bought my M8, and haven't looked back. Give me an unlocked bootloader, or give me death.

You can S-OFF (which unlocks bootloader) & root it immediately after getting it.
I came from a locked Galaxy S4 and have to say this phone is snappier than an iPhone & as unlockable as a door thats compatible with all keys ;D. Love love loveeee this phone and highly recommend it! Go for it!
I unlocked mine the moment I got home with it, no OTA update required as some people have said to do before unlocking it & as far as I've seen no ones had an actual "Oh no! They made it impossible to unlock like Sammysung!" moment.

Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...

Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk

holla420 said:
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
Click to expand...
Click to collapse
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.

Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
U must not being in the right directory
Sent from my Insanely powered M8 using Tapatalk

Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
What that guy above me said, if you using Windows make sure you right click+shift in the platform tools directly then see if it shows up with adb devices, if not check your drivers.

Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.

Doc Ames said:
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Click to expand...
Click to collapse
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....

Frausbite77 said:
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Click to expand...
Click to collapse
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:

Doc Ames said:
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Click to expand...
Click to collapse
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!

Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
That's the proper command line for using Adb on a Mac. It won't work without using ./ before the command.
Sent from my HTC6525LVW using Tapatalk

Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.

Doc Ames said:
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Click to expand...
Click to collapse
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...

Frausbite77 said:
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Click to expand...
Click to collapse
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946

Doc Ames said:
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Click to expand...
Click to collapse
wow, man viper rom is insane, thanks for the update heads up...i wouldn't have even thought to do that...guess i have tons of reading to catch up on...thanks...