I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...
Did you use the "cd" command to change the directory to where the platform-tools folder is?
That's assuming you have the Android SDK and Java Dev Kit (JDK) installed already..
Sent from my Atrix HD via XDA-Developers application
pianoman102 said:
I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...
Click to expand...
Click to collapse
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!
pianoman102 said:
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!
Click to expand...
Click to collapse
U're welcome
devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.
skeevydude said:
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.
Click to expand...
Click to collapse
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language
devilsking said:
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language
Click to expand...
Click to collapse
Thanks.
That's what I thought it did. I was going to do something similar, but I couldn't remember if the correct folder was and I was just too lazy to do the research and find out. I was thinking System32, but its been so long that I couldn't remember.
Related
I tried to follow the steps from androidandme to set up my phone for screen shots. I got java, got the android sdk and unzipped everything (nothing was installed?), changed the path under advanced settings, dowloaded eclipse (why not) and all that jazz - full 9 yards.
However, when I run ddms.bat in the tools folder and Dalvik comes up it never recognizes my phone. I have tried with the g1 mounted, unmounted, usb debugging on/off (which I also do not know what this means).
Anyone have any thoughts? I did not get any prompts about drivers and I am mounted to my computer.
Read the guides on how to install ADB.
for some reason when i ever i use ddms to take screen shots, i can't just go to take a screenshot, i have to run a logcat first, it will bring up a popup that says "failed!" i then close that and it runs a logcat, after i do that, then i can use it to take a screen shot.
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
s15274n said:
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
Click to expand...
Click to collapse
Sorry if this is not relevant, but I had a ton of trouble until I had the newest jave runtime installed. I never had trouble, got a new laptop at work and had no clue why it would not run. the newest JRE fixed it right up. Maybe not your problem but...
Also I like the program "droid explorer". It has screenshot built in.
EDIT.
I have one more thought...I (always have one more thought) try starting your phone in fastboot (camera and power) then back button when the skaters come up) and see if it asks for drivers then.
s15274n said:
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
Click to expand...
Click to collapse
adb.exe is a command line application, it doesn't have a GUI. To use an command line app you have to 'cd' to the directory where it's located and enter valid commands. I think you can type 'adb help' for a full list of commands.
Try reinstalling the drivers, it took me a few tries to get it working right on Vista (interestingly no drivers are needed for OS X )
Let me start very basic. Is there any "installing" of the SPK? Or, do I just extract the files? I extracted them and created a directory in PATH like the site said to do.
If there is no installation... are you saying for me to get in dos and just start keying commands, and not using any of the files from the zip?
There is no installation, but EVERYTHING for the sdk is ran in command prompt. Meaning click start, click run, type in cmd, then type cd path/to/your/toolsfolder/ then type adb remount see if it does, if not you NEED TO FOLLOW THE ADB INSTRUCTIONS FOR INSTALLING DRIVERS.
im trying to set up a adb so i can use my g1 as a webcam:
http://forum.xda-developers.com/showpost.php?p=4975656&postcount=17
however when i plug in my g1 it says everything was installed except the adb.
Do you have ADB setup on your computer in the first place? If not, http://forum.xda-developers.com/showthread.php?t=532719.
I installed the adb with the sdk as it was mentioned and my computer still doesnt show my phone as an adb device
Did you install the drivers for adb?
i cant find out how!
85Mario85 said:
i cant find out how!
Click to expand...
Click to collapse
a little search and VOILA!!!
http://forum.xda-developers.com/showthread.php?t=446274&highlight=64bit+usb
this works if you are running windoze 7 x64
i dont get how im supposed to put windows 7 on test mode =S
im getting this aswel "When running the command prompt adb install I receive an error dialog stating:
"This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.""
im getting so frustrrated with thiss
bump! i dont get this =[
Search for pdanet and install it. That's how I set up adb for Windows. (Btw - get rid of Windows. Finally did my switch to ubuntu today - ahahahahahahaha I'm sad I ever even used Windows.)
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
evilkorn said:
Yea, but adb is kind of a ***** about permissions and such on ubuntu. But each has its quarks.
@85mario85 - You have to cd to the adb.exe in the tools folder ie. c:\sdk\tools\ then run adb. Or add it to the paths part, but I can't remember at the moment.
Click to expand...
Click to collapse
adding it to the path just saves time. instead of having to cd all the time you can just run adb. i highly suggest it. and i agree - ubuntu is a ***** about permissions all the time. i love it, but i have to learn to use it. however, i'll probably always have a copy of windows in case i can't find out how to do something and have to have it done. better safe than sorry. =]
Can anybody help me set up ADB, SDK, and Emulator. I've tried all of the guides but I just don;t understand any of it. I really want Emulator too so f anyone can help, that'd be greatly appriciated. Thanks =D
I have a black G1 with Danger SPL and the latest Radio. I use a Windows Vista laptop and have the SDK downloaded in the C:/ folder but it's the zipped file. Should it be extracted in there? I've tried to do the whole SDK Setup process but for some odd reason it always downloads everything except for like, the firmwares like 1.0,1.1,1.5,1.6,2.0,2.0.1,2.1 or anything.
G1BRICKED said:
Can anybody help me set up ADB, SDK, and Emulator. I've tried all of the guides but I just don;t understand any of it. I really want Emulator too so f anyone can help, that'd be greatly appriciated. Thanks =D
I have a black G1 with Danger SPL and the latest Radio. I use a Windows Vista laptop and have the SDK downloaded in the C:/ folder but it's the zipped file. Should it be extracted in there? I've tried to do the whole SDK Setup process but for some odd reason it always downloads everything except for like, the firmwares like 1.0,1.1,1.5,1.6,2.0,2.0.1,2.1 or anything.
Click to expand...
Click to collapse
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd C:\sdk\tools
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
nephron said:
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
Click to expand...
Click to collapse
Also at what point are you having issues with setting this up?
nolimit78 said:
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd C:\sdk\tools
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
Click to expand...
Click to collapse
Ok so I have it setup as C:\android-sdk-windows and then all of the files. When I type in the first command it says
Code:
The system cannot find the path specified.
And I have the Droid Explorer Installed and everything but it doesn't have the Emulator and that's all I really want. That and FastBoot.
nolimit78 said:
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd [B]C:\sdk\tools[/B]
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
Click to expand...
Click to collapse
If you noticed it extracted it to C:\sdk\tools, you did yours to C:\android-sdk-windows. So you'll need to adapt to the changes..
Code:
cd C:\android-sdk-windows\tools
adb shell
Now it says,
Code:
Error: device not found
G1 is in Debugging mode and all.
G1BRICKED said:
Now it says,
Code:
Error: device not found
G1 is in Debugging mode and all.
Click to expand...
Click to collapse
A friend of mine had the same problem. Make sure the device is plugged into the back of your computer, reboot the PC and the Phone. See if that helps. And which ROM are you running?
Well see I'm on VegaMans Beta Legend Port, and my phone won't show up on my laptop at all not to mount or anything all that appears is the notification in my bar saying;
Code:
USB Debugging Connected
Select to disable USB Debugging
G1BRICKED said:
Well see I'm on VegaMans Beta Legend Port, and my phone won't show up on my laptop at all not to mount or anything all that appears is the notification in my bar saying;
Code:
USB Debugging Connected
Select to disable USB Debugging
Click to expand...
Click to collapse
I saw that, It could be that USB Debug is broken on the ROM (it is in early beta) Try using a different rom.
nolimit78 said:
I saw that, It could be that USB Debug is broken on the ROM (it is in early beta) Try using a different rom.
Click to expand...
Click to collapse
Well man, I tried it on FastTest and now I have a Custom Splash1 Image and now I'm not afraid of holding the Back button with the Red one. I think I'm going to throw Sense UI off to the side for now until it supports ADB and all. So thanks man, after all these monthes I finally have ADB Access. One more thing though, how can I get Emulator to work?
Now, when I try to go into Emulator through CMD, I se this;
Code:
C:\android-sdk-windows\tools>emulator
emulator: ERROR: You did not specify a virtual device name, and the system
directory could not be found.
If you are an Android SDK user, please use '@<name>' or '-avd <name>'
to start a given virtual device (see -help-avd for details).
Otherwise, follow the instructions in -help-disk-images to start the emulator
Then, I navigate to C:/Windows-SDK-Windows/SDK Setup and I allow it to run. I get two windows, one that says
Code:
Failed to fetch URL https://dl-ssl.google.com/android/repository/repository.xml, reason: HTTPS SSL error. You might want to force download through HTTP in the settings.
I close that window and go to the one that says Choose Package To Install, but the white box on the side is blank. I close that and go to Android SDK And AVD Manager. From there I go to Virtual Devices and it's blank and grey-ed out. I click new and see
Code:
Name - [I]Here I can write[/I]
Target - [I]Here I can't write[/I]
SD Card: Size [I]Here I can write[/I] MiB or KiB
File: [I]Here I can't write[/I] Browse [COLOR="DarkRed"]Dulled out[/COLOR]
Screw skins and Hardware I can do that on my own, but how can I set a Target if it is grey-ed out?
G1BRICKED said:
how can I get Emulator to work?
Click to expand...
Click to collapse
that is something I can't help you with. I am at work and it won't allow me to download what I need for that. But I am glad you got ADB workin!
Lol thanks =D
Totally new to android, anyone mind explaining?
the command is "adb install <path/name of apk>".
do it from your computer in a shell/terminal.
Do I have to mess with the NDK at al? I thought I saw something on that...
Bump, more info please?
NDK? Did you mean SDK (android for windows developer kit), If so yes. Download and install. Follow the link below for drivers.
http://forum.xda-developers.com/showthread.php?t=882751
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE. This means SDK and drivers were installed correctly. Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.
fprice02 said:
NDK? Did you mean SDK (android for windows developer kit), If so yes. Download and install. Follow the link below for drivers.
http://forum.xda-developers.com/showthread.php?t=882751
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE. This means SDK and drivers were installed correctly. Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.
Click to expand...
Click to collapse
Thanks!
Even though I installed the JDK 6u23, the Android SDK installer won't let me install because it doesn't see the JDK installed...
I used the same 623 package, installed that, then reboot, then install the SDK. BTW what OS are you using?
fprice02 said:
I used the same 623 package, installed that, then reboot, then install the SDK. BTW what OS are you using?
Click to expand...
Click to collapse
Win x64... I installed the 32-bit version of the JDK and got it..
If you're totally new, I'd suggest heading over to http://nookdevs.com/NookColor and reading up there.
fprice02 said:
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE.
Click to expand...
Click to collapse
CMD is giving me 'adb is not recognized as a command'
The nook drivers are installed, along with the SDK
ironcrotch said:
If you're totally new, I'd suggest heading over to http://nookdevs.com/NookColor and reading up there.
Click to expand...
Click to collapse
This helped, thanks
fprice02 said:
Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.
Click to expand...
Click to collapse
My SDK install is in C:\Program Files (x86)\Android\android-sdk-windows
When I run in cmd:
cd\
cd Program Files (x86)\Android\android-sdk-windows\platform-tools
I can run adb commands. The thread wants me to run sqlite3 commands too, but they are in a different directory:
C:\Program Files (x86)\Android\android-sdk-windows\tools
I am pretty confused on what to do
Do you guys use search at all or check the development forum for this device i mean come on its all in black and white.
I don't know what I did exactly, but I managed to install apk's from the root of my SD card
sweet
Please someone help!
After following instructions of Easy USB ADB Installer for Windows, and running adb devices, my nook didn't show up as a device.
Also I tried installing a software and it said application not install.
Thanks in advance
Easier thing to do is go into Settings --> Application --> Unknown Sources then download an APK with your Browser and install it from the Downloads window. I suggest finding an APK for Astro File Manager and get Dropbox, that way you can install Apps straight from Cloud storage.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
Try this Bro, it's the easiest way to get the USB Drivers onto your PC and then your NC recognized.
http://forum.xda-developers.com/showthread.php?t=910008
thereddog said:
Thanks!
Even though I installed the JDK 6u23, the Android SDK installer won't let me install because it doesn't see the JDK installed...
Click to expand...
Click to collapse
I have that same problem, have you found a fix for it yet?
I'm running Windows 7 x64
with an I-7 Processor
first, i have already unlocked my bootloader using windblowz on a boot camp partition of my mac. BUT, since android is a unix-like os, and osx is a unix-like os, FOR MY OWN EDUCATION, i want to be able to use the osx terminal to do this stuff to my n6.
so here's what i tried, and none of it works... as in, none of it even results in any like link between my phone and my osx computer.
1) i watched this youtube video from droidmodderX, and followed it to the letter:
https://www.youtube.com/watch?v=aUkcWlknFsE
from the time he plugs his n6 into his mac, NOTHING he says will happen, actually happened. it was as if i had plugged the phone into nothing. He says NOTHING about installing the android SDK for osx in his video. sooo....
2) next, i install the android SDK for osx, thinking droidmodderX was just careless in his video, and forgot to mention that you need to do this. NOTHING. i open the terminal and run the various fastboot commands from the root directory... NOTHING. using the terminal, i change over to the directory where i actually put the SDK, and then run the fastboot/adb commands from terminal again, and NOTHING. I tried this with the phone in fastboot, and with the phone not in fastboot, and NOTHING.
so how do you get osx to talk to this phone with fastboot/adb commands using the terminal?
fwiw, android file transfer works fine in the gui, so i know the physical connecction is good.
also, fwiw, i did use the search function and someone asked a similar question about his n5 about a year ago... and got no answer. not a single one.
-peter
If you run "./adb devices" without quotes does it see the phone at all? Make sure you have the most up to date SDK for OS X and also make sure you update the platform-tools in the SDK manager.
Check this thread out, might help a bit.
EDIT: Try running the commands as root/sudo.
I used this method on my MacBook Air to root my device without any issues. Make sure that you are in the correct folder when executing the commands. The first time it should ask you for your password. Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader. You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
geebee1932 said:
I used this method on my MacBook Air to root my device without any issues.
Click to expand...
Click to collapse
what method? can you be more specific? did you mean to put in a link describing the "method"?
geebee1932 said:
Make sure that you are in the correct folder when executing the commands.
Click to expand...
Click to collapse
I ran all the fastboot commands, to the letter, from the youtube video, from the terminal, in the folder where i had the SDK. nothing....
geebee1932 said:
The first time it should ask you for your password.
Click to expand...
Click to collapse
It didn't.
geebee1932 said:
Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader.
Click to expand...
Click to collapse
I did.
geebee1932 said:
You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
Click to expand...
Click to collapse
As I said in my original post, I already have Android File Transfer, no need to google it. It works great. Had it for years.
I made some headway when I started using ./adb before each command. It sees my device now and when i ran ./adb help, it put out a list of commands and switches in the terminal, that I'm starting to play with. thanks for the ./adb clue. that was a biggie now using ./adb i can reboot and boot into bootloader. but for example "./adb fastboot oem lock", (without the quotes), does nothing. (i used "oem lock" as a test, because the bootloader is already unlocked)
-peter
geebee1932 said:
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
pcrussell50 said:
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
Click to expand...
Click to collapse
No worries at all - I was frustrated myself until I found the YouTube video. I think after ./ you need a space before you use the command line. What I did was put the CF auto-root folder (unzipped) on my desktop. I renamed the folder CF to make it easy. I opened the folder and doubled clicked on the Mac file. It should open and say just press enter - it will not work. Keep the folder open and open up the terminal. Here is what I had to do.
Put the phone is download mode with "Start" appearing - then plug into computer. (make sure debugging on)
cd /Users/mycomputername/desktop/CF - I needed a space after cd
paste and copy the 3 sudo commands (with the sudo) out of the CF folder one at a time - pressing enter after each.
The first enter - you should be asked for your password.
Mike
Going well now guys thanks. I like having two unix-like devices (osx computer and android handset), talking without needing drivers.
-peter
sn0warmy said:
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Hello everyone,
I'm in the same boat, except my device won't show up under devices in transmission after the "./adb devices" command.
Got a Nexus 6, 2009 Macbook running OSX Mavericks. I followed http://forum.xda-developers.com/showthread.php?t=1917237 to a T, but no luck. Android File Transfer works just fine. Usb debugging and oem unlock is checked on my phone, I restarted both phone and computer. Any advice/guidance/direction would be greatly appreciated, thanks!