Database Users

Unlocking the bootloader

Hey all, finally got my N1 today and I've been trying to unlock the bootloader for a bit following the instructions at redmondpie
You can follow the step by step guide posted below (on your own risk) to unlock the bootloader on the Google Nexus One phone. We are not to be held responsible if you ended up bricking your phone. The steps are as follows.
Step 1: Download and extract fastboot from here (Windows, Linux and Mac included).
Step 2: Run a command prompt / terminal at the directory you just extracted.
Step 3: Type ‘fastboot-windows oem unlock’ or ‘./fastboot-mac oem unlock’ or ‘./fastboot-linux oem unlock’ (as appropriate).
Step 4: Proceed on your merry bootloader unlocked way.
Our complete coverage on the Google Nexus One phone can be found here.
Click to expand...
Click to collapse
Problem is I get a "fastboot-windows is not recognized as an external or internal command.
I've tried the command while in fastboot mode and while in the bootloader.
Any help is appreciated.
Carlos
Fastboot devices does recognize my N1

you need to start your phone in fastboot mode. turn off your phone, hold trackball button down, power on your phone while still holding trackball down.
also when you open a command prompt type cd followed by the path to the folder where your fastboot file is at (example: cd C:/myfolder/) and press enter. then type the command

I don't have my N1 yet so I haven't tried.
You're sure you are in the proper directory in the command prompt?
also maybe run the command prompt as admin? (right click on the icon run as administrator)

I'm an idiot.
I was supposed to download the zip attached in that thread and run the command prompt from the extracted folder. FYI: you can hold ctl+shift and left click on the folder to open a command prompt.
Well, might as well sticky this so other people don't have the same problem.

[GUIDE] Linux Ubuntu: Unlocking Bootloader / Rooting Nexus S

One thing I've noticed is there isn't a lot of documentation for getting set up and unlocking your bootloader on a Linux OS. Setting up your machine to get adb and fastboot to recognize your device takes a tiny bit of extra work on a Linux operating system, but what exactly needs to be done may not be clear to everyone. Whether it's because you're new to the Android SDK/adb, somewhat new to Linux, or can't simply can't seem to find the Vendor Code for the Nexus S. (For those who are looking specifically for this, it's '18d1', and I assume will be the same on all Nexus devices to come; If this means nothing to you right now, read on.)
Disclaimer: I take no responsibility if something goes wrong (if it does, it should be fixable though), Unlocking your bootloader voids your warranty (but you can lock it back), Unlocking the bootloader will wipe your entire phone, including USB Storage; so make a copy of all those family photos and other files you may have put onto the USB storage if you want to keep them.
For the sake of sanity, this guide assumes you are using Ubuntu. If you're using something else (or different applications), there are terminal commands offered, and you probably have an idea on how to adapt the given instructions to your Linux OS.
Preparation: Installing the Android SDK, ADB, Fastboot & Setting Up Your Nexus S to be Recognized
1. Download the Android SDK for Linux: http://dl.google.com/android/android-sdk_r08-linux_86.tgz
2. Save it in a folder of your choice. I chose to keep it in my Downloads folder, myself. If you'd like, you can rename it to the simpler name of 'AndroidSDK.tgz'. The rest of the guide will assume that you did, because I'm lazy, and it makes things simpler; it will also assume you saved it in Downloads. If you feel that you have the intuition to rename and edit the path names based on your own choices, then fine; but if you're utterly lost here, just stick with what I'm doing; download to 'Downloads', rename to 'AndroidSDK.tgz'.
3. Now that you have it, navigate to the folder you downloaded it to, right-click, and click 'Extract' to unzip it. If for some reason you cannot do this, open up a terminal and try this command:
Code:
tar zxvf /home/<your-user-name>/Downloads/AndroidSDK.tgz
You may have to adjust the command if you didn't save it under Downloads or didn't rename the file to AndroidSDK.tgz.
4. Now, we'll install adb and some other software packages by starting up the Android SDK and AVD Manager. Start it either by:
- Navigating to your AndroidSDK folder, going to the 'tools' folder and double-clicking the file called 'android'; if a popup opens asking you what you want to do with it click 'Run'.
- Using this command:
Code:
/home/<your-user-name>/Downloads/AndroidSDK/tools/android
5. In Android SDK and AVD Manager, click on "Available packages". Check the box next to "Android SDK Tools, revision 8" and "Android SDK Platform-tools", and click on "Install Selected" then "Install". When prompted click "Yes" to restart ADB.
6.You should now have a folder in /home/<your-user-name>/Downloads/AndroidSDK/ called "platform-tools".
7. Download fastboot here: http://developer.htc.com/adp.html
- Save it to the aforementioned platform-tools folder.
- Now, navigate to the file, right click it, click 'Properties', go to the 'Permissions' Tab and check 'Allow executing file as program'. Alternatively, run this command:
Code:
chmod +x /home/<your-user-name>/Downloads/AndroidSDK/platform-tools/fastboot
8. Now to set things up so adb and fastboot recognize your Nexus.
- Type this command into a terminal:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
- Paste this into the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
- Click save and close.
- Then, type the following terminal command:
Code:
sudo restart udev
9. Almost done with preparations! Run this command:
Code:
gedit .bashrc
And add this line to the top of the file:
Code:
#AndroidDev PATH
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Then save the file and close.
10. Download this file and save it to /home/<your-user-name>/Downloads/AndroidSDK/platform-tools: http://www.mediafire.com/?4pe5y906zr67nfh
10.We're ready to go!
Unlocking the Bootloader on your Nexus S and Rooting
Once again, unlocking your bootloader wipes everything on your device, including USB storage. Make a backup of any files you want to keep.
1. On your Nexus S, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
2. Power off the phone, and then hold down the Volume Up button and the Power button simultaneously to get into Bootloader/Fastboot mode. Connect your Nexus to the computer via USB.
3. Run this command to unlock your bootloader: (Once again WIPES EVERYTHING!)
Code:
fastboot oem unlock
Hit Enter and on your phone you will be prompted to confirm the action. (Use Volume +/- buttons to choose, power button to confirm choice) Confirm. At this point you will have an unlocked bootloader.
4. Copy/paste the following into the Terminal window:
Code:
fastboot flash recovery /home/<your-user-name>/AndroidSDK/platform-tools/recovery-clockwork-herring.img
5. Use the Volume +/- buttons to choose the Recovery option, then press the power button.
6. In Recovery, go to 'mounts and storage' and choose 'mount USB storage'.
7. Go to this page: http://forum.xda-developers.com/showthread.php?t=682828
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Link As..." Save that file to your desktop and then copy it to the main directory of your mounted phone.
8. Click 'Unmount'. Go back to 'mounts and storage' and choose 'mount /system'. Then Go Back and choose 'install zip from sdcard'>'choose zip from sdcard'>su-2.3.6.1-ef-signed.zip
9. When it's finshed installing, reboot. You are now rooted.
Special Thanks
Amin Sabet; I used your Mac guide as a reference and copy/pasted some things for convenience.
Koush; For first posting the unlocking information, developing ClockworkMod Recovery, and ROM Manager. You should probably hook him up with a donation. https://www.paypal.com/us/cgi-bin/w...63663d3faee8d9384d85353843a619606282818e091d0
Michael.B.; for suggesting adding the platform-tools folder to the .bashrc file.
Linus Torvalds; Without which we'd have neither Android nor Ubuntu.
Feel free to leave your comments on the guide below.

Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ and platform-tools directories to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Click to expand...
Click to collapse
Be sure to update your username above.

Thanks a lot man, great guide. I didn't get my NS yet but this is gonna be very useful soon
ps: someone please stick this

Michael.B. said:
Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
Be sure to update your username above.
Click to expand...
Click to collapse
Thanks for the tip. I added your tip and instructions for marking fastboot as executable.

Stuck due to the thread's usefulness

I forgot to ask: will this work for 64 bit systems?

nicholasbgr said:
I forgot to ask: will this work for 64 bit systems?
Click to expand...
Click to collapse
It should work just fine.

Thanks, got me rooted nice and quickly.

BlackOtaku said:
It should work just fine.
Click to expand...
Click to collapse
Yes but don't forget to install 32 libs.
Thanks for guide
Useful !
I'm waiting for cyanogen ROM so i'll able to install
Cheers

To confirm, yes it works on 64bit. I am running that

Thanks for the confirmation, guys

Good stuff, much appreciated.

I'm working on a simple shell script that should automate some of the more menial tasks while holding the user's hand through the process. I should have it up later today.
UPDATE: It's up! Link on the first page.
Sent from my Nexus S using XDA App

question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?

confiq said:
question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?
Click to expand...
Click to collapse
Or, I don't get OTA until i change OS with zip file (ex: su app) ?

confiq said:
Or, I don't get OTA until i change OS with zip file (ex: su app) ?
Click to expand...
Click to collapse
You shouldn't flash the recovery in the boot partition, I think that will cause problems with the phone period. :S
If you flash a custom boot.img (which this guide doesn't cover, though the script will flash Superboot) or kernel like Paul's Superboot, Supercurio's Voodoo Kernel, or Koush's insecure boot.img, OTA updates will fail to install. OTA updates will also reflash your recovery back to stock. One of the devs around here will probably start modifying them so they don't check the boot.img or reflash the recovery though.

Thanks for this! Worked perfectly

Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska

matroska said:
Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska
Click to expand...
Click to collapse
To fix the problem, before selecting zip file, you have to select mount /system. Then go to apply update.zip and proceed as usual.
Thanks

ok im stock
with this part fastboot oem unlock ware i put this code in my terminal of my pc ,,i put the cell in fasboot , i intall everiting if i put that code in my terminal
bash: /home/toshiba/.bashrc: line 2: syntax error near unexpected token `('
bash: /home/toshiba/.bashrc: line 2: `export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools# ~/.bashrc: executed by bash(1) for non-login shells.'
[email protected]:~$ fastboot oem unlock
fastboot: command not found
[email protected]:~$
what can i do or im doing wrong

Need help returning to stock

I purchased my nexus 7 from Walmart. The first thing I did was unlock and root it. But it turns out that my nexus has the screen flicker hardware issue. So how do I unroot, relock, and return to stock?
I think Google gives the factory .img's that I could flash through fast boot, but will that relock the boot loader and unroot it?
Also does the splash screen keep the 'unlocked' icon after being relocked?
That's a lot of questions, but if anyone can help that'd be great. Thanks!
Sent from my Nexus 7 using xda app-developers app
EDIT: since its a hardware issue, can I just factory reset? Its not like the people at Walmart will know...

you can follow this guide.
1. Download the 4.1 (JRN84D) image files to your computer. A direct download link is found here: [Only registered users can view links. ]
While a link to the Google page you can search on if you need, is here: [Only registered users can view links. ]
2. Extract the files from that downloaded file. This will give you a folder called "nakasi-jrn84d-factory-8b0bd791"... inside of which you will find a folder called "nakasi-jrn84d"... and inside of that you will see the files we are going to fastboot to your tablet. We want to place these files into the folder we located earlier which contains our "fastboot" file. Move or copy them over to that folder.
Note: On Linux/Ubuntu you may just extract them to any easily located folder.. Create a new one on the desktop or your home folder is my recommendation.
For reference, there should be 4 files, named:
bootloader-grouper-3.34.img
flash-all.sh
flash-base.sh
image-nakasi-jrn84d.zip
3. Open a command prompt inside the folder we have set up our files in. On windows this can be done by holding shift as you right-click in the folder, then select "Open command window here". On Mac or on a Linux system you want to open a terminal/command prompt and navigate to that folder using "cd" or "change directory" commands. For example if your folder is called "fastbootfiles" and it is on your desktop, you would enter:
Code:
cd desktop
Code:
cd fastbootfiles
4. Power down your tablet. Reboot into the bootloader by holding Volume Down + Power until you see the bootloader screen. In red letters toward the top of the text you will see fastboot mode. Once here, plug it into your computer.
5. Let's make sure you have your fastboot drivers installed and recognizing your device. Enter in the command prompt:
Code:
fastboot devices
For Mac:
Code:
./fastboot-mac devices
And press enter. You should see "List of attached devices" Followed by a string of numbers. If you do not see this, you do not have your drivers installed correctly! Go back to Zero Neck's Unlocking guide and grab the correct drivers, and make sure you install them correctly. You can also find the procedure during the video posted by Ragnarokx.
If you got the expected response, let's move on to fastbooting you back to stock...
6. This first command is going to wipe all your old EVERYTHING from the device. Credit to our resident AC cowboy, Jerry Hildenbrand, for pointing out to me a minor bug with the Nexus 7 bootloader that makes this a wise step to do first. Type each of these lines followed by Enter between them, waiting for one to finish before moving on to the next:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
7. This command will flash the stock bootloader on to your device. Enter:
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
And press enter. Make sure you type the command exactly as you see it.
Note: As we noted earlier, replace "fastboot" above with the exact name of the fastboot file in your folder, for your system, such as "fastboot-windows" or "fastboot-mac". Addtionally for Mac's only, the command should be entered as such
Code:
./fastboot-mac flash bootloader bootloader-grouper-3.34.img
Noting the period and forward slash before the command.
Going forward you Mac folks just remember that with the rest of the commands
Now reboot the bootloader:
Code:
fastboot reboot-bootloader
Enter.
8. This next command will both wipe your old system and flash the factory image in its place, which includes the stock system, recovery, kernel, and userdata partitions:
Code:
fastboot -w update image-nakasi-jrn84d.zip
Enter, and wait, make sure the command finishes. This might take a few minutes.
Reboot the bootloader again:
Code:
fastboot reboot-bootloader
Enter.
9. We are done with the hard part... pretty easy right? Now we're just going to lock that bootloader.
Code:
fastboot oem lock
Enter.
Yes, this step is optional but I strongly recommend it if you had issues earlier which led to this procedure. Now you can unlock again if you like, which will give your tablet that final full wipe to clear out any bad data remaining:
Code:
fastboot oem unlock
Enter.
10. Finally, reboot and setup your tablet again from scratch!
Code:
fastboot reboot

5implelove said:
you can follow this guide.
1. Download the 4.1 (JRN84D) image files to your computer. A direct download link is found here: [Only registered users can view links. ]
While a link to the Google page you can search on if you need, is here: [Only registered users can view links. ]
2. Extract the files from that downloaded file. This will give you a folder called "nakasi-jrn84d-factory-8b0bd791"... inside of which you will find a folder called "nakasi-jrn84d"... and inside of that you will see the files we are going to fastboot to your tablet. We want to place these files into the folder we located earlier which contains our "fastboot" file. Move or copy them over to that folder.
Note: On Linux/Ubuntu you may just extract them to any easily located folder.. Create a new one on the desktop or your home folder is my recommendation.
For reference, there should be 4 files, named:
bootloader-grouper-3.34.img
flash-all.sh
flash-base.sh
image-nakasi-jrn84d.zip
3. Open a command prompt inside the folder we have set up our files in. On windows this can be done by holding shift as you right-click in the folder, then select "Open command window here". On Mac or on a Linux system you want to open a terminal/command prompt and navigate to that folder using "cd" or "change directory" commands. For example if your folder is called "fastbootfiles" and it is on your desktop, you would enter:
Code:
cd desktop
Code:
cd fastbootfiles
4. Power down your tablet. Reboot into the bootloader by holding Volume Down + Power until you see the bootloader screen. In red letters toward the top of the text you will see fastboot mode. Once here, plug it into your computer.
5. Let's make sure you have your fastboot drivers installed and recognizing your device. Enter in the command prompt:
Code:
fastboot devices
For Mac:
Code:
./fastboot-mac devices
And press enter. You should see "List of attached devices" Followed by a string of numbers. If you do not see this, you do not have your drivers installed correctly! Go back to Zero Neck's Unlocking guide and grab the correct drivers, and make sure you install them correctly. You can also find the procedure during the video posted by Ragnarokx.
If you got the expected response, let's move on to fastbooting you back to stock...
6. This first command is going to wipe all your old EVERYTHING from the device. Credit to our resident AC cowboy, Jerry Hildenbrand, for pointing out to me a minor bug with the Nexus 7 bootloader that makes this a wise step to do first. Type each of these lines followed by Enter between them, waiting for one to finish before moving on to the next:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
7. This command will flash the stock bootloader on to your device. Enter:
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
And press enter. Make sure you type the command exactly as you see it.
Note: As we noted earlier, replace "fastboot" above with the exact name of the fastboot file in your folder, for your system, such as "fastboot-windows" or "fastboot-mac". Addtionally for Mac's only, the command should be entered as such
Code:
./fastboot-mac flash bootloader bootloader-grouper-3.34.img
Noting the period and forward slash before the command.
Going forward you Mac folks just remember that with the rest of the commands
Now reboot the bootloader:
Code:
fastboot reboot-bootloader
Enter.
8. This next command will both wipe your old system and flash the factory image in its place, which includes the stock system, recovery, kernel, and userdata partitions:
Code:
fastboot -w update image-nakasi-jrn84d.zip
Enter, and wait, make sure the command finishes. This might take a few minutes.
Reboot the bootloader again:
Code:
fastboot reboot-bootloader
Enter.
9. We are done with the hard part... pretty easy right? Now we're just going to lock that bootloader.
Code:
fastboot oem lock
Enter.
Yes, this step is optional but I strongly recommend it if you had issues earlier which led to this procedure. Now you can unlock again if you like, which will give your tablet that final full wipe to clear out any bad data remaining:
Code:
fastboot oem unlock
Enter.
10. Finally, reboot and setup your tablet again from scratch!
Code:
fastboot reboot
Click to expand...
Click to collapse
Thanks for the quick reply! I'll do this in the morning and report back. Does anyone have a link to the factory .imgs?
Sent from my Nexus 7 using xda app-developers app

https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz

A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; there are two possible issues with v1.5.2 mentioned but I didn't encounter any driver issues on win7 x64 nor did I encountered the issue with adb mentioned)
4. Run the flash stock + unroot script.
5. Run the relock script.

taltamir said:
A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; I didn't have any driver issues on win7 x64 not did I encountered the issue with adb mentioned there as a possible workaround)
4. Run the flash stock + unroot script.
5. Run the relock script.
Click to expand...
Click to collapse
I agree the toolkit is the way to go. I stayed away from it when I rooted because the whole one click method never appealed to me on any of my android devices. That was until I soft bricked my n7 by trying to change the LCD density, then I went to the toolkit it is the real deal.
Sent from my EVO using xda premium

taltamir said:
A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; there are two possible issues with v1.5.2 mentioned but I didn't encounter any driver issues on win7 x64 nor did I encountered the issue with adb mentioned)
4. Run the flash stock + unroot script.
5. Run the relock script.
Click to expand...
Click to collapse
I used the root tool kit to root. I have a windows 7 x64 also and I had no problems with it.
Sent from my Nexus 7 using xda app-developers app

Help me please!!!!

I have a problem.
I don't have any roms in my SD card. and I'm in recovery with nothing to flash. So my phone is pretty useless. Is there a way I can do something to get a rom on my phone to flash it somehow?
:crying:

Download a rom & gapps on your PC/laptop, you can/should be able to Mount your SD card in recovery, copy it over and flash.
Edit:
You could try booting your phone up anyway, if that works you can copy one from your PC or download it straight to your phone.
Sent from my One using Tapatalk 4

GANJDROI4 said:
Download a rom & gapps on your PC/laptop, you can/should be able to Mount your SD card in recovery, copy it over and flash.
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
not on a nexus 4, you can mount your sd storage via recovery.
but you can push files to your device via recovery mode with adb. twrp has a push files with adb option, and so should cwm recovery.

simms22 said:
not on a nexus 4, you can mount your sd storage via recovery.
but you can push files to your device via recovery mode with adb. twrp has a push files with adb option, and so should cwm recovery.
Click to expand...
Click to collapse
How do I do this?

You can push the necessary files to your phone using adb. Download the kit we have provided here in the forums and using a cmd prompt you can flash a ROM back onto your Nexus 4. If you need help doing so I can walk you through the steps!

droidscoop said:
you can push the necessary files to your phone using adb. Download the kit we have provided here in the forums and using a cmd prompt you can flash a rom back onto your nexus 4. If you need help doing so i can walk you through the steps!
Click to expand...
Click to collapse
yes please!

Have you downloaded the adb kit yet?

Yes

DroidScoop said:
Have you downloaded the adb kit yet?
Click to expand...
Click to collapse
Yes

Which custom recovery are you running?

Clockword Mod Recovery 6.0.2.3

xxMAGICxx said:
Clockword Mod Recovery 6.0.2.3
Click to expand...
Click to collapse
Ok, I'm writing a step by step instructional as we speak. Please bear with me.

Thank you so much

Flash a ROM Using ADB [Step by Step Guide]
Read Very Carefully First Before you Start
If you like this please press the Thanks button!
After you Download the ADB Kit extract the file and place it on your desktop. Now Download the ROM you want and place it inside the Folder. Make sure you change the name of the ROM to something simple. I'd suggest ROM.ZIP
1.) Make sure your drivers are installed correctly. To do this open the ADB Kit file and (Hold Shift + Right Click inside the Folder and select "Open Command window here") after the cmd prompt opens plug in your phone and boot into Fastboot mode (Volume Down + Power)
Next type FASTBOOT DEVICES into the Cmd window and press enter.
Your cmd window should read an alphanumeric serial or device number like 04d3be7317d511e8
If not please look up how to download the device drivers its easy
2.) Now keep your Command window open and boot into the recovery.
From the recovery navigate to (Wipe Data/ Factory Reset) and select it
Once your phone is wiped navigate to (install zip.> install .Zip from Sideload)
3.) It's time to flash now!
Go back to your command window while your phone is still connected and type with spaces: ADB SIDELOAD _______.zip
For example if my ROM was named AOKP.zip
I would type: ADB SIDELOAD AOKP.ZIP
After you type this press enter and thats it your phone will begin flashing the new ROM!
Please Reference questions here with our post Quoted!
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
xxMAGICxx said:
Thank you so much
Click to expand...
Click to collapse
Your walk through is all set please let me know if everything goes smoothly and if your satisfied please hit that thanks button!

I'll give it a try,...standby your computer in case i need a fast response lol

I have a mac.... I also need the Drivers. The only downloads for those are windows.

DroidScoop said:
Read Very Carefully First Before you Start
If you like this please press the Thanks button!
After you Download the ADB Kit extract the file and place it on your desktop. Now Download the ROM you want and place it inside the Folder. Make sure you change the name of the ROM to something simple. I'd suggest ROM.ZIP
1.) Make sure your drivers are installed correctly. To do this open the ADB Kit file and (Hold Shift + Right Click inside the Folder and select "Open Command window here") after the cmd prompt opens plug in your phone and boot into Fastboot mode (Volume Down + Power)
Next type FASTBOOT DEVICES into the Cmd window and press enter.
Your cmd window should read an alphanumeric serial or device number like 04d3be7317d511e8
If not please look up how to download the device drivers its easy
2.) Now keep your Command window open and boot into the recovery.
From the recovery navigate to (Wipe Data/ Factory Reset) and select it
Once your phone is wiped navigate to (install zip.> install .Zip from Sideload)
3.) It's time to flash now!
Go back to your command window while your phone is still connected and type with spaces: ADB SIDELOAD _______.zip
For example if my ROM was named AOKP.zip
I would type: ADB SIDELOAD AOKP.ZIP
After you type this press enter and thats it your phone will begin flashing the new ROM!
Please Reference questions here with our post Quoted!
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
Your walk through is all set please let me know if everything goes smoothly and if your satisfied please hit that thanks button!
Click to expand...
Click to collapse
I have a Mac. I also need the Drivers. The only downloads for the drivers are for windows.

xxMAGICxx said:
I have a mac.... I also need the Drivers. The only downloads for those are windows.
Click to expand...
Click to collapse
All of the files in the adb essentials kit are set up for windows
The guide at the link below will help you then. Once you have finished the set up for Mac OS, follow my steps.
http://forum.xda-developers.com/showthread.php?t=1917237

If my usb debugging isn't on (Don't know if it is or not) then what happens? I can't obviously go back into the phones settings. I can't even get my phone to boot.

DroidScoop said:
Read Very Carefully First Before you Start
If you like this please press the Thanks button!
After you Download the ADB Kit extract the file and place it on your desktop. Now Download the ROM you want and place it inside the Folder. Make sure you change the name of the ROM to something simple. I'd suggest ROM.ZIP
1.) Make sure your drivers are installed correctly. To do this open the ADB Kit file and (Hold Shift + Right Click inside the Folder and select "Open Command window here") after the cmd prompt opens plug in your phone and boot into Fastboot mode (Volume Down + Power)
Next type FASTBOOT DEVICES into the Cmd window and press enter.
Your cmd window should read an alphanumeric serial or device number like 04d3be7317d511e8
If not please look up how to download the device drivers its easy
2.) Now keep your Command window open and boot into the recovery.
From the recovery navigate to (Wipe Data/ Factory Reset) and select it
Once your phone is wiped navigate to (install zip.> install .Zip from Sideload)
3.) It's time to flash now!
Go back to your command window while your phone is still connected and type with spaces: ADB SIDELOAD _______.zip
For example if my ROM was named AOKP.zip
I would type: ADB SIDELOAD AOKP.ZIP
After you type this press enter and thats it your phone will begin flashing the new ROM!
Please Reference questions here with our post Quoted!
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
Your walk through is all set please let me know if everything goes smoothly and if your satisfied please hit that thanks button!
Click to expand...
Click to collapse
DroidScoop said:
All of the files in the adb essentials kit are set up for windows
The guide at the link below will help you then. Once you have finished the set up for Mac OS, follow my steps.
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
If my usb debugging isn't on (Don't know if it is or not) then what happens? I can't obviously go back into the phones settings. I can't even get my phone to boot.

[noob-read] adb and fastboot. What is it? How can it help you?

Please note, I can only speak with any degree of certainty about devices bought from Play / Moto. I cannot attest to the accuracy of this information for US carrier versions etc. Anything you do is at your own risk
Contents / Thread overview
Introduction
What is Fastboot?
What is adb?
How to install adb and fastboot
How to test adb and fastboot work
OK Gimme some useful fastboot commands please!
OK Gimme some useful adb commands please!
A little more about using Windows command prompt
Myth Busters
Introduction
adb and fastboot are very useful command line tools. They can be used from Windows, Linux or Mac to carry out tasks on your android device, such as moving and backing up files, rooting and restoring your phone to it's factory state. Understanding how to use these tools could save your phone when you get yourself in trouble. This is especially true of rooted users. Particularly those of you who are "new to the scene". You definitely should read and understand this thread before you do ANYTHING root related.
This thread is not intended to be a non-exhausted reference. It is merely here to give an overview of the most basic of basics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is fastboot?
Fastboot comprises of 2 components.
1) Fastboot mode on the phone (The Bootloader)
2) Fastboot tool on your computer
Fastboot is a small command line tool that you can use from your computer whilst the phone is connected via USB and you are booted into the bootloader. The most common uses for fastboot are:
Unlocking the bootloader - needed as part of the rooting process
Flashing a custom recovery to the device - needed as part of the rooting process
Flashing factory images - used for saving / trestoring your device back to stock
Being able to do these 3 things are essential before rooting. Many new users skip learning these and use a toolkit to root. As a result, when they mess up and we try to explain what they need to do to fix their issues, it becomes very difficult for us to help as fastboot is not understood. It is YOUR responsibility to understand these things BEFORE you mess up.
What is adb?
adb is another small command line tool that stands for "Android Debugging Bridge". Again, it can be used from a computer connected via USB to your android device. It can be used whilst the device is booted into Android or (if you have a custom recovery), it can be used in recovery too, unlike fastboot (yes, adb and fastboot are NOT the same thing) which can only be used in the bootloader.
adb can be used to push files to (or pull files from) your phone. It can also be used to execute many of the commands available in Linux terminals (Or Android terminal emulators) on the device itself. We're not here to cover all these commands however. We just want to cover the basics.
How to install adb and fastboot
adb and fastboot are very easy to install and can be installed on Windows, Linux and MAC computers. The Windows install can be a little bit more complicated than the other 2 and may need additional drivers installing too.
Windows.
There is a very handy tool that can install adb and fastboot in 15 seconds. It is recommended that you use this to install adb and fastboot. Please see the link immediately below for that tool:
ADB, Fastboot and Drivers - 15 seconds ADB Installer - Really quick and easy way to install adb and fastboot (by @Snoop05). Download links are at the bottom of post 1.
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide .. This is asking to install for all windows users. < 15 second installer needs updating to SDK 23, which is required for latest Android versions.
Download the latest SDK (adb and fastboot) versions here: https://developer.android.com/sdk/index.html (Scroll down to SDK tools only) then download the Windows *Installer*.
Open the installer and select "Platform-tools" and install the packages. This should create "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Now we want to set this path as a Windows Environment variable PATH to make the executables work system wide:
right-click computer > properties > advanced > environment variables.
under system variables click "path" and click "edit"
at the end of the line, add the below:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Please note, the semi-colon ; is VERY important.
You may also need to install drivers.
Here is a link to the Google USB Driver: DOWNLOAD THIS
Code:
To install on Windows 7:
- Ensure existing drivers are uninstalled first*
- Extract the zip to c:\adb (created earlier by the installer)
- Right-click "Computer" > Manage in windows and choose "Device Manager"
- Boot the Nexus 6 to the bootloader (Volume down + Power) and connect the USB Cable
- Watch for any new devices with exclamation marks appearing
- Right-Click the new device > Update driver software
- Choose the "browse" method and browse to c:\adb, find teh folder you extracted then follow the wizard to the end - using amd6 64 if you're on a 64 bit system and i386 if you're on a 32 bit system.
*To uninstall existing drivers, boot into Android and connect the USB cable. Monitor device manager for the device showing up. To uninstall the device, right-click it to uninstall it. At the prompt, ensure you also choose to delete the driver. Repeat this for bootloader and recovery.
Code:
To Install on Windows 8, you may need to additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
Once that is done, your Windows computer is configured for adb and fastboot.
In device manager, the device should show up as below, depending whether you are booted into recovery or bootloader...
Recovery - Android Device > Google Nexus 4 ADB Interface
Bootloader - Android Device > Google Nexus 4 Bootloader Interface
If it shows as something different, either you have existing drivers in the way or something went wrong.
Linux and Mac
Here is a really simple tool to install adb and fastboot on the above OS. The only expectation is you know how to open and run a terminal command. Please see the link immediately below:
Nexus Tools 2.2 (Featured by XDA) - adb and fastboot installer for Linux and Mac (by @corbin052198)
Once you have installed adb and fastboot from the above link, you're ready to go.
How to test adb and fastboot work
As previously mentioned, adb and fastboot are both command line tools. That means you must run these tools from command prompt (cmd in Windows) or Terminal (Linux and Mac).
Remember earlier, I mentioned that fastboot can only be used in bootloader? and adb can only be used in Android (or custom recovery - lets cover that later)? We can use the command "fastboot devices" and "adb devices to see if we have adb and fastboot working correctly.
Lets try it.
Boot your phone into android
Connect it to your computer via USB
Open cmd (start > type "cmd" on Windows) or Terminal (Mac/ Linux
Type in the windows "adb devices" and press enter
Here is what we don't want to see:
Notice how there is nothing underneath where it says "List of attached devices" That means it cannot see any device
Here is what we DO want to see:
We can see that there is now a device listed.
OK lets test fastboot. Unplug the USB and turn off the phone. When it is off, hold down Volume down + power until you feel the vibrate. You will now be in the bootloader. Reconnect the USB cable.
In the same window (cmd or terminal) we're going to now type "fastboot devices".
Again, here is an example of what we don't and do want to see:
If in both modes, you can see your devices "Serial Number", then you know they are both working.
Please note that if you cannot get adb and fastboot to work "system wide", you can open the command prompt to the location of the adb and fastboot executables exist and try from there.
OK Gimme some useful fastboot commands please!
Here are some of the most useful fastboot commands you will come across. Fastboot is used mostly for flashing images to the devices partitions on the internal memory.
Code:
fastboot oem unlock
This unlocks your bootloader and allows you to flash a recovery to root. WARNING, this will wipe your device. Rooting the N6 is essentially unlocking the bootloader, flashing a recovery and then putting the SuperSU zip on your sdcard and flashing it via the recovery. This thread covers rooting: [HOW-TO] The Nexus 6 All-In-One Beginner's Guide by @xBeerdroiDx
Code:
fastboot flash recovery recovery.img
This will flash a recovery.img to the recovery partition. The command is broken down into "fastboot flash" (what to do) "recovery" (where to flash to) "recovery.img" what to flash there. In the terminal or command prompt, you cannot just type "recovery.img" though. It has to be the path to where the recovery image is. For example, if my recovery image is on my desktop, I would have to type:
Code:
fastboot flash recovery c:\users\rootsu\desktop\recovery.img
It is worth noting, that it IS case sensitive, meaning if your file is called Recovery.img, you must type the capital R...
Other things you would flash:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
These will flash the system image (ROM) and boot image (kernel) as you would if you were returning to stock.
A full guide to returning to stock can be found here: [TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader by @Mr hOaX
You can also boot into a recovery.img without flashing it...
Code:
fastboot boot c:\users\rootsu\desktop\recovery.img
which is "fastboot boot" (what to do) "c:\users\rootsu\desktop\recovery.img" what to do it with. As you may have noticed, we did not define the recovery partition in this command, that's because we're not flashing it....
OK Gimme some useful adb commands please!
At the moment, we are going to assume you have a custom recovery and you have booted into recovery. The reason for this is using adb in recovery can be much simpler.
Here are some useful scenarios for using adb.
Backup your sdcard to your PC
Code:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
**Please note, some recoveries may "mount data" automatically on boot, so don't be disheartened if you get an error stating device or resource busy. This probably just means you can't mount what is already mounted**
/data/media/0 is the real location of /sdcard for your information. Also referred to as "The mount point". What we have done here is "adb pull" (what to do) "data/media/0" (what to move) "c:\MyBackup" (where to move it to)
Push a zip file from your PC to your sdcard (useful if you wiped your sdcard and rom)
Code:
adb shell
mount data
exit
adb push c:\rom.zip data/media/0
What we have done here is "adb push" (what to do) "c:\rom.zip" (what to move) "data/media/0" (where to move it to)
You can of course also use adb to push and pull files to and from /system too. You just need to:
Code:
adb shell
mount system
exit
I mentioned earlier that using custom recovery is much easier for adb than whilst booted into Android. You need to ensure you have a kernel that allows insecure adb before you do anything with system and data partitions. You also need to ensure that USB debugging has been enabled in developer options.
For example, to mount system to pull files whilst android is running you have to:
Code:
adb root
adb shell
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
...which is clearly a little bit more involved, so I recommend you use recovery for adb push and pull. You can find more detailed information on adb here: http://developer.android.com/tools/help/adb.html
A little more about using Windows command prompt
One thing to understand is that like Windows, command prompt (cmd.exe) works with directories (or folders if you like). The Linux and Mac terminals are the same, but most linux users, we expect you would already know this.
Here you will see I have downloaded a recovery image that I want to flash using fastboot.
As you can see, the recovery.img is located in C:\users\rootSU\Desktop
Usually when you open the command prompt from the start menu, or run command, the command prompt will default to your user location as seen below:
So lets try and fastboot flash recovery recovery.img...
It fails with a not-too-accurate error message. It has failed because you have not told it where the recovery image is. It assumes it is in the directory as listed in the prompt
So, how do we deal with this? Well, there are 3 ways.
1) We tell the command prompt where the recovery.img actully is in the command itself
Success! As you can see, we have told the command that the location for the file is Desktop\recovery.img
2) We can change the directory in command prompt to the directory where the file is. In this example, we change directory to "Desktop". The change directory command is "cd " or in this case "cd Desktop"
3) ...and possibly the simplest method. We hold shift whilst we right-click on the folder we want to change directory to, and directly open a command prompt there:
Another point to make with command prompt or terminals, is if you do a particular command, it is "pre-programmed" to "expect" a particular format of that command.
For example, we know that adb push as a command expects after it . This means the command is actually
Code:
adb push
BUT if you put something AFTER , for example -
Code:
adb push somethingelse
, it will assume that the "somethingelse" is a bad parameter, and the command will fail. It will probably display (or "print" which is the technical term in a terminal) a helpful guide of how the command should be used instead of trying to run the command which it does not understand.
You're probably wondering why I am telling you this. Well quite simply, it is a warning about folder names. Imagine you have c:\users\rootSU\My Documents as a folder. You assume the command is then
Code:
adb pull /data/media/0 c:\users\rootSU\My Documents
but it is not... There is a space in between My and Documents. What you have actually done is
Code:
adb pull Documents
because it uses a space to signify the end of a command or parameter. It is best to avoid using folders with spaces in them. Avoid as much as you can. In the event it is unavoidable (Although when is it ever>) then please surround the path with quotation marks,
Code:
adb pull /data/media/0 "c:\users\rootSU\My Documents"
so that way, it sees everything between the " " as a single parameter.
Myth Busters
Myth 1: You need USB debugging on to use adb and fastboot
If you cannot boot into Android, it doesn't matter. You DO NOT need USB Debugging turned on to use adb outside of android. USB Debugging is an Android ONLY setting. Fastboot obviously also does not need debugging either as this too is outside of Android
Myth 2: to adb push or fastboot flash files, they must be in the same folder as adb or fastboot executables. Sorry but this is rubbish. You can pass the full path of the image you're flashing or file you're pushing in the command and fastboot / adb can be called system wide if you've set them as an environment variable or used the 15 second installer

thanks(im out of thanks). but ill be back to leave one here!!!!!

simms22 said:
thanks(im out of thanks). but ill be back to leave one here!!!!!
Click to expand...
Click to collapse
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks

rootSU said:
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks
Click to expand...
Click to collapse
it was up in the n5 threads before, and was needed here. but its here now as well, so thank you

Good guide. Needs to be a sticky. In fact, I think every device general forum should have a sticky like this. Would have saved me a lot of grief back when....

Excellent update.

Very good to see. I'm sure lots of people will be sending noobs here for the basics.

Up to your usual helpful, good work I see.

rootSU said:
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide (to which again, you should answer Y)... This then allows you to type adb commands in the command prompt without having to open a particular directory first. You may or may not understand what I mean when I say that, but take it from me, its much more convenient and easier to use this way.
Click to expand...
Click to collapse
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
rootSU said:
It will also ask if you want to install device drivers. Actually, say N to this as we're going to cover that next, using the google USB drivers
Here is a link to the Google USB Driver: DOWNLOAD THIS
Click to expand...
Click to collapse
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:

Snoop05 said:
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:
Click to expand...
Click to collapse
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.

rootSU said:
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.
Click to expand...
Click to collapse
Path is added in both cases.

Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?

papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Can you be very specific with your issue please?

papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Android M no like root, you'll either have to live with stock or wait for chainfire to do his thing.

This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?

ScottyChaos said:
This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?
Click to expand...
Click to collapse
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801

cam30era said:
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801
Click to expand...
Click to collapse
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".

ScottyChaos said:
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".
Click to expand...
Click to collapse
Error 28 means drivers not installed. Try the driver help thread that I linked above.
---------- Post added at 12:33 PM ---------- Previous post was at 12:04 PM ----------
cam30era said:
Error 28 means drivers not installed. Try the driver help thread that I linked above.
Click to expand...
Click to collapse
@ScottyChaos,
Just a fundamental question: I assume you have enabled "Developer Options" in Settings, and then checked "enable USB debugging"?
---------- Post added at 12:39 PM ---------- Previous post was at 12:33 PM ----------
[/COLOR @ScottyChaos,
Here is a thread that you might find interesting > http://forum.xda-developers.com/android/help/metro-pcs-kyocera-hydro-life-rooted-t2870678

Windows 10 device driver management is even more locked down then windows 8. I got two of the three drivers loaded but when going into adb mode on the phone through recovery it just disappeared out of the device manager. I had to unplug and plug in while in that mode to trigger a unloaded driver in the device manager. Once there I had to force the adb driver manually with the nasty windows driver warning and all. Once I did that I could see the device in adb mode and sideload my marshmallow OTA. woot!

I decided to drop a thanks bomb...
ADB is good.
But that fastboot.
Seriously, its ONE command. OK, a few different arguments to use.... But it is so easy, and so powerful. People are afraid to mess up on command line, but its actually way harder to type the wrong thing out then to click the wrong thing.
LEARN IT. Forget your toolkit.
You can fix almost anything, Its not too hard for you. It may be new... YOU CAN DO IT.
Also, I have to say it... Its not going to help anyone, but it will keep me from punching something. ADB and Fastboot... Not the same. You don't ADB a new system image....