[How To] Installing Custom Kernels - Kindle Fire General

Okay, this guide is for users with less experience and want to overclock their Kindle Fire. This is for Windows.
This section is if you haven't installed ADB yet
1) You need to download the Android SDK
Android SDK: http://developer.android.com/sdk/index.html
2) Open the SDK Manager and install the SDK Tools and SDK Platform Tools
3) You need to add the ADB path. First find where you installed the Android SDK.The default is in C:\Program Files\Android\Android-sdk or C:\Program Files (x86)\Android\Android-sdk, you can check in the SDK Manager at the top, it will tell you your path. Then click on the start button, and right click on my computer and hit properties. Then on the left click Advanced System Settings In the next box at the bottom is Environment Variables click on this. Under System Variables find the variable that says Path DO NOT DELETE THIS VARIABLE! Hit Edit and at the the end put:
;YOUR ANDROID SDK PATH\tools;YOUR ANDROID SDK PATH\platform-tools
Then hit OK.
ADB install tutorial is now finished
4)Now we want to add the correct drivers. There are a couple of ways to do this, this is the way I do it. Again right click on My Computer, and click properties. Now in the top left corner is Device Manager click on this. Now find where it says Kindle and right click it. Click the drivers tab and then Update Drivers and then browse my computer for driver software. Then click, let me choose from a list on my computer and click adb interface, and then either a ADB Testing Interface, or fastboot Interface, both work for what we are doing.
5) The next thing you want is a kernel so download and put in the \platform-tools folder.
IntersectRaven's: http://forum.xda-developers.com/showthread.php?t=1382999
DoomLord's: http://forum.xda-developers.com/showthread.php?t=1372625
6) Plug your Kindle Fire into your computer
7) Open a CMD window. Hit start and run CMD.exe or search for CMD. Then type into cmd:
adb shell
idme bootmode 4002
reboot
8) Open another CMD and type cd YOUR ANDROID SDK PATH \platform-tools. Then type:
fastboot boot NAME OF KERNEL.img
9) Now your Kindle will reboot, make sure it boots! Now that you have verified that it works we are ready to flash it.
10) Shutdown your Kindle Fire.
11) Use your old CMD with fastboot, and type:
fastboot flash boot NAME OF KERNEL.img
12) It will probably get stuck in booting at this point. With the fastboot CMD type:
fastboot oem idme bootmode 4000
it will say waiting for device, do not close this CMD!
13) Now hold down the power button until your device turns off. Then turn it on again, and the command will register.
14) Let your Kindle Fire boot and enjoy your new kernel!
If this doesn't work please leave a comment, or if I forgot anything, I am kind of tired while writing this. I may add pictures later. Thanks!

All this does is boots the custom kernel a single time (which you MUST do to test it). You still need to flash it.
Sent from my Gingervolt-ed VS910 4G using xda premium

Sorry, I will add the rest soon, slipped my tired mind.

do we really need the whole android and java sdk ?
the only commands used is adb and fastboot.
woud'nt the tools directory of KFU be enough since it contains the necessary commands ?
furthermore the driver installation is a essential part for correct operation of adb and fastboot
and don't forget so say your how-to is for windows

I haven't looked at the KFU much yet, so I don't know. I added that it is for windows and removed the java sdk. And added how to flash the kernel.

Accessory mode suppot
Are any Fire kernels available that support Accessory Mode aka ADK.
The changes that need to be made to the kernel are available from Google. They are in the main 3.x kernel source tree and in the samsung source tree of the 2.6.35 kernel.

Related

[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

The Complete Noob-iots Guide To Rooting, Recovery, and Troubleshooting

The purpose of this tutorial is not to teach you everything. It's just to give the less-than-average user (noob) an idea of why certain steps are taken and how to prevent and or troubleshoot problems that most people have when rooting or flashing ROMs on their device. I am also assuming that if you do decide to root your device you have at least a basic working knowledge of a computer. If you don't know what a desktop is or how to find the "any" key, you have no business being anywhere near a computer much less an android device…continue no further. Read my tutorial…If you like it, let me know. If I missed anything or got something wrong, let me know…I'll try to fix it. If you're impartial to it, I couldn't care less. If you hate it, PM me…I have some important information for you about anger management.
ROOTING
While there are different rooting "methods" they all rely on the same basic concept. Get temporary root access to your system in order to use the adb (Android Debug Bridge) to transfer necessary files and change permissions to permanently root (take ownership of) the device.
Before programs like KindleFireUtility and KindleWater, rooting the Kindle Fire was done manually through a command line interface (command prompt). Although those programs still use the same methods, you never see it. But why use command prompt? What do those commands mean anyway? Anyone can point and click but if you don't know what is going on behind the scenes then you are big trouble when things go wrong…and they inevitably will. So, let's get started.
From here on out we will consider this the beginning of the tutorial. Read everything first before doing anything. Pay close attention to what's being said and follow instructions carefully. Now...
Before anything your device needs to be fully charged and have the Android SDK and the Kindle adb drivers installed onto your computer. I'm not going to go into how to install SDK or Kindle adb drivers here because there are millions of pages on the internet that will teach you, and quite frankly that's not the purpose of this tutorial. That being said, lets get down to business and talk about the older (manual) methods of rooting the Kindle Fire.
First, lets start with the device turned on. Now go to your Kindle Fire settings and scroll down and select "Devices". Make sure "Allow Installation of Applications" is set to ON. This allows you to install apps not downloaded from the Amazon App Store. Next we open the App Store and search for and install a file management utility (ES File Explorer is a good one to start with). This will be necessary to temporarily root your device. Exit the App Store.
Now plug your device into the computer. For the purposes of this exercise there are two USB modes you will need to know, USB debugging and USB file transfer. On stock devices when you plug into your computer you will see a black screen that says "You can now transfer files from your computer to Kindle". This we will call USB file transfer mode. You will use this to transfer a program to your device that will give you temporary root permissions. The old program for this was ZergRush, nowadays its BurritoRoot and tomorrow it will probably be something else. Whatever it is, find whichever one works for your device's software version and transfer it to your device using Explorer (Windows) or Finder (Mac). Since you don't have root access yet, everything you put on your device for now will go directly to the SDcard partition, far away from system folders (for all intents and purposes).
Press "disconnect" on your Kindle Fire. Now, and by default, your Kindle is in USB debugging mode. What that means is that when you are not in USB file transfer mode your device is constantly listening for debugging commands coming from the USB port. We will be using this to send adb commands to the device which are necessary for rooting and setting up recovery. Now open the file management app you installed from the App Store, navigate to the temporary root program you transferred from your computer and open it. Install and follow the instructions, if any. Next go to your computer and navigate to your Android SDK folder and look for a folder called "platform-tools" if you don't see it, open the tools folder and double-click the file named "Android". Select "platform-tools" and install.
To make things simple, lets to take the platform-tools folder and place it on your desktop (just be sure to put it back when this is all over).
At this point we need to get Superuser. This is what we will use to give your apps root access. Go to http://www.androidsu.com/superuser and download the one for Gingerbread. Extract the superuser.zip file, open the folder and navigate to the system folder inside. There, inside the "app" and "bin" folders you will see two files called "superuser.apk" and "SU". Place them in the platform-tools folder that is now on your desktop. And now the fun part, it's time to start rooting.
Open your command prompt (or terminal for mac users) and type and enter:
cd Desktop/platform-tools
Here, you are telling the computer to cd (change directory) to the platform-tools folder located inside the Desktop folder. This is going to be your workspace. Everything you do from here on will be done from this folder. If you don't get any errors then you are in good shape. Otherwise you messed up somewhere and probably skipped a step...go back and read from the beginning. Make sure your Kindle Fire is turned on and NOT in USB file transfer mode. If you are not sure what mode you're in, go back to the beginning. If this is your second time around, stop. You need to learn more about how to change directories using command line interface.
When you are in the platform-tools folder, type and enter this command:
adb devices
Mac and Linux users will put ./ before all adb and fastboot commands from here on out. It will look like: ./adb devices
Here you are using the adb program to print a list of connected devices. You should see a bunch of numbers that mean nothing to you at this skill level. Move on. If you don't see any numbers then you either don't have your drivers installed properly or you skipped a step; go back to the beginning.
If you do get a bunch of numbers your device is connected. Now type and enter:
adb root

...gives root permissions to the adb
adb remount
...mounts the system partition to a "read/write" state allowing you to make changes to system files and folders. Consequentially, if you enter adb remount a second time, you will change it back to "read only". Don't do that.
adb push su /system/xbin/su
...will push (transfer) the file named "SU" that is in your workspace (platform-tools folder) to the su folder inside the xbin folder of your device's system folder. The SU binary file is what other apps call to when they need superuser rights.
adb shell chown 0.0 /system/xbin/su
...this is where it gets a little funky. It opens a shell interface within the adb in order to chown (give ownership permissions) to user 0.0 for the su folder. A shell is a piece of software with a particular set of commands built in to act as sort of a go-between between the user, operating system and hardware kernel services. But who is user 0.0? [Edit:] User 0.0 is the root user. Thanks to b63 for that piece of knowledge
adb shell chmod 06755 /system/xbin/su
...opens a shell within the adb to chmod (change mode) of the su folder to 06755. What that basically means is you are changing the folder permissions to rwxr-xr-x or read/write/execute for the owner, and read/execute for the group and others.
adb install superuser.apk
...installs the program superuser.apk located in the platform-tools folder. Superuser.apk maintains a database of what apps you allow to access SU binary file.
That's how the rooting process works. Again if you get any errors, you did something wrong. Go back to the beginning and read it all over again. Attention is key.
Also, I suggest you skip the one-click methods for rooting and get used to using the command line interface so you understand how the process works in order to quickly troubleshoot problems should they arise. Oh and congratulations, you are rooted.
RECOVERY
Now lets install a custom recovery utility and a new boot-loader. For this you will be using the fastboot command. Before we go on, one thing you absolutely must get your head around is the difference between how fastboot interacts with your device versus how adb interacts with your device. fastboot deals with the boot portion of the device whereas adb only deals with the system portion. What that means is adb will only work when the device is completely booted. If for some reason your device doesn't boot properly then you should not be issuing adb commands. It's like trying to light a match in a vacuum. Fastboot works in the same way in that you must be in the fastboot bootmode in order to issue fastboot commands. Unless you have custom recovery installed or a factory programming cable there is only one way to get into fastboot mode. We'll talk about that later.
Installing recovery is a simple process but it is where people tend to have the most problems. Part of the reason is the misunderstanding of the different bootmodes. For now, you only need to be concerned with two of them; normal bootmode (4000) and fastboot bootmode (4002). The main reason people run into trouble is that once you are in a particular bootmode, it doesn't change until you tell it to (with the exception of temporary fastboot which we will get into later).
In normal bootmode your device will boot...normally (imagine that). With the fastboot bootmode the boot-loader will hang at the Kindle Fire splash screen (or yellow triangle if you have recovery installed) to wait for further commands. If this happens to you, chances are your only problem is you are in the wrong bootmode, which is easy to fix. Knowing that, installing a custom recovery should be a breeze.
First find whatever recovery you want to use (unzip it if you have to) and place the .img file into your platform-tools folder that you were using earlier. We're going to use adb to change the bootmode to fastboot in order to install custom recovery. Remember, anything that pertains to the boot-loader, (Kindle Fire logo/yellow triangle) will be done in the fastboot bootmode; that includes custom recovery installation. For more information on Kindle Fire bootmodes, boot-loaders, fastboot and just about everything else, see this post:
http://forum.xda-developers.com/showthread.php?t=1552547
From your command prompt type and enter:
adb shell
su
idme bootmode 4002
reboot
What that does is tells adb to open a shell and su (substitute user) for the root user, change the bootmode from normal (4000) to fastboot (4002) and reboot. The root user has the necessary permissions to change the bootmode from the adb. Your device will reboot then hang at the splash screen because it is in the fastboot bootmode.
Now install your custom recovery (we'll call it customrecovery.img for now)
fastboot -i 0x1949 boot customrecovery.img
again, for Mac and Linux you would type: ./fastboot -i 0x1949 boot customrecovery.img
That tells your computer to, using the fastboot program that is in your platform-tools folder, boot the device with the ID of 0x1949 (your Kindle) with the file named "customrecovery.img"
After installation, reboot, but you will still be in the fastboot bootmode. So type:
fastboot -i 0x1949 oem idme bootmode 4000

fastboot reboot
…tells the device to reset the partition where the recovery(?) is located, change the bootmode to normal (4000) and reboot.
TROUBLESHOOTING
Flashing custom ROMS are another source of frustrations as they add too many variables to the equation. Some ROMS can be very unstable and cause weird things to happen to your device. But just knowing how this stuff works will help you fix 90% of the problems that may come up. If you are having trouble with your device, troubleshoot the problem:
Does the device turn on?
No

Is it fully charged?
No--> Charge it

Is it fully charged?
Yes--> Hold the power button for 30 seconds and restart

Does the device turn on?
No--> Hold the power button for 3 minutes and restart
Does the device turn on?

No--> Google search "Motorola USB factory programming cable"

Does it boot normally?
No

Do you have custom recovery installed
No--> You need to get into fastboot mode to issue fastboot commands. Google search "Motorola USB factory programming cable"

Do you have custom recovery installed?
Yes--> During the first 5 seconds of seeing the boot splash screen (this is temporary fastboot mode that comes with custom recovery) issue fastboot command to change bootmode to 4000. Reboot

Does it boot normally?

No

Can you get into recovery?
No--> During the first 5 seconds of seeing the boot splash screen (temporary fastboot mode) issue fastboot command to install a new customrecovery.img. Reboot.

Can you get into recovery?

Yes--> Re-flash your ROM. Reboot.

Does it boot normally?

No--> Enter recovery, factory reset, wipe cache, wipe dalvik cache, re-flash your ROM. Reboot

Does it boot normally?
No--> Enter recovery, factory reset, wipe cache, wipe dalvik cache, flash a different ROM. Reboot

Does it boot normally?
No--> Post your problem on the XDA forum. Include all pertinent information such as what rom you are using, what the exact problem is, what you were doing before the problem occurred and all the steps you have taken to try and fix the problem.

Does it boot normally?
Yes--> Give yourself a pat on the back, because you rock!
Do you Rock?
No--> Start over from the beginning
nice
--sent from my glacier.

[TOOL]Latest ADB and Fastboot for Win, Linux, Mac

Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android​
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
The last SDK Platform-Tools for Win, Linux and Mac you can always find here - https://developer.android.com/studio/releases/platform-tools
Arhive:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
sorry for being a noob and asking for another device in a different forum,
but will these adb drivers also work with nexus 4???
need them to sideload 5.0.1
IS this for android 5.0 GPE?
http://forum.xda-developers.com/htc-one/general/guide-windows-8-1-fastboot-adb-t2970692
i have anaged to get it working after expereincing the problems stated here by others ... follow my steps here for those who still have trouble
lewonsky said:
IS this for android 5.0 GPE?
Click to expand...
Click to collapse
Yes, this for all version. It' latest update from official Android SDK Platforms.
See link in OP.
Golv said:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
Click to expand...
Click to collapse
I think you forgot to mention that this is only for Windows. So it does not work for Linux or Mac.
Quick, fast, no frills, just the necessary files itself. Hopefully this thread gets updated whenever a new release comes up
thanks, nice share bro :good:
how to use those files
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
open a command window and change directory to the folder where adb.exe is installed. Then you can use adb commands. Commands syntax is as follow:
Code:
adb [target] <command>
You only need to specify the [target] if you have more than 1 android device or emulator connected simultaneously, otherwise the command will be directed to the only connected device, so the syntax will be:
Code:
adb <command>
So if you want to sideload a rom to your device, boot in your custom recovery and start the "sideload" mode.
In the command window:
Code:
adb sideload my_rom.zip
Don't forget that the rom.zip must be in the same folder where adb.exe is
If you want to use "adb push" instead of "adb sideload" then boot in custom recovery (not in sideload mode) and use the following command:
Code:
adb push my_rom.zip /sdcard
You can read more about adb commands here: http://developer.android.com/tools/help/adb.html#issuingcommands
adb sideload explained here: http://android-revolution-hd.blogspot.in/2013/12/ow-to-use-adb-sideload.html
If you have more question about what file to sideload or push a rom to your device, you should ask in the correct forum, Amazon Fire HD 6 forum is here: http://forum.xda-developers.com/fire-hd
thank u
save my day
How do you install the new adb 1.0.32 over the old version and will it work with the moto X 2014?
its dosnt work for me
and i need it ((
every phone i want use sideload , its say me , use adb 1.0.32 or newer
and when i want use adb 1.0.32 , show me this error in all adb commands :
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
what should i do ?
update adb
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
go to this website: https://fl1.androidfilehost.com/dl/...803384/minimal_adb_fastboot_v1.3.1_setup.exe?
download and install it to your computer, then try to sideload it through there.
if that doesn't work just download the stand alone SDK from the android studio website and after its downloaded, open the .rar file and extract it to a new folder to your desktop. after that open it and search for a folder that says platform tools and look for the ADB .exe file and copy it, then go to your C drive and go to programs and try to find the android studio folder, when you have located it open it and look for a folder named platform tools, then delete the adb.exe in that folder and paste the new one in there or you can probably just copy the whole platform tools folder and replace the other one in the C drive.
I hope this helps, if it doesnt just message me and im sorry for the late reply.
alishadlou said:
* failed to start daemon *
error: unknown host service
what should i do ?
Click to expand...
Click to collapse
this usually means the phone is not communicating with your PC.
- either your phone is corrupt
- the connection is corrupt
- or the cable is bad
Tip: add the path of ADB.exe to your system Environment Variables, so you can call it w/out first navigating to it.
- Right click Computer > Properties > Advanced system settings
- Environment Variables ... > edit "Path" by adding the path to ADB.exe.
ie.
Windows 10 x64, i simply add: D:\PortableApps\ADB
for other Windows, you may have to add to the end of "Path", click edit > scroll to the end > add ;D:\PortableApps\ADB;
(don't forget to add the semicolon at the end)
Now you can simply launch Command Prompt and enter: ADB sideload *file*
Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android​
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
Not working on Android 6.0
This and older versions will not work on Samsung S7E for system backup and restore.
It accepts the commands, but the confirmation popup supposed to open on the device never does. For a few 6.0 users on other devices, it opened up but the backups were not really completed.
thanks bro. nice share :good:
Thanks, you save me too much time!!
my adb was working fine for my Note 4. I followed the instructions to upgrade bootloader
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Now, I keep getting device offline when used adb devices command. Do you think, upgrading ADB will solve this? thank you

[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....

[Win, Mac, Linx] Simple-ADB

This is simply ADB/Fastboot, with a Graphical User Interface.
Click to expand...
Click to collapse
HOW-TO
• Installation
make sure you have java installed on your PC
• first you have to install adb system-wide:
[windows] : try ADB Installer tool.
[Linux] : adb support comes with most Linux distributions.
• then run Simple-ADB.jar and that's it!
[Windows shortcut]
[Linux shortcut]
Click to expand...
Click to collapse
• Usage
• select from "ADB", "Fastboot" or "Your command" modes:
- if "ADB" is selected the dropdown will contain lots of adb commands :
adb devices -l
adb connect <host>
adb disconnect
adb usb
adb logcat
adb install
adb uninstall
adb push
adb pull
adb kill-all
adb shell top
adb shell free
adb shell ps,
adb shell netstat,
adb shell pm list packages,
busybox df -h
rm /data/system/gesture.key
adb reboot
adb reboot recovery
adb reboot download
adb reboot bootloader
adb reboot fastboot
adb reboot sideload
adb help
adb kill-server
- if "Fastboot" is selected the dropdown will contain lots of Fastboot commands :
fastboot devices -l
fastboot reboot-bootloader
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot flash
fastboot flash recovery
fastboot flash boot
fastboot flash system
fastboot flash data
fastboot flash cache
fastboot flash userdata
fastboot flash bootloader
fastboot flash radio
fastboot help
- if "Your command" is selected the dropdown will be disabled , and you can write your own command.
• You can Save output from the Options menu or simply press Ctrl+S.
Click to expand...
Click to collapse
COMPATIBILITY
• Windows
• Linux (Thanks a lot for @topnomi for testing and confirming Linux support, follow his Instructions for linux).
• Mac OS (read this post for details)
TO-DO/FIX
• fix memory leak because of large output to the JTextArea [(e.g during adb logcat).
• support for Mac (I really don't know why it's not working there, contributions are always welcome!)
Code:
*** Disclaimer
there are some commands I've never tested (like password command),
please use the tool at your own risk.
If you want to support the development of this program, feel free to donate.
Click to expand...
Click to collapse
XDA:DevDB Information
S-ADB, Tool/Utility for all devices (see above for details)
Contributors
mhashim6
Source Code:
GitHub
Source-Forge
This tool is based on System Command Executor Library
Version Information
Status: Stable
Current Stable Version: update6
Stable Release Date: 2018-02-03
Created 2016-07-12
Last Updated 2020-06-15
XDA:DevDB Information
S-ADB, Tool/Utility for all devices (see above for details)
Contributors
Mohamed Hashem
Source Code: https://github.com/mhashim6/Simple-ADB
Version Information
Status: Stable
Current Stable Version: update6
Stable Release Date: 2018-02-03
Created 2016-07-12
Last Updated 2020-06-14
CHANGELOG
update6 [stable] [16/09/2017]
Code:
• fixed the memory leak that occurred when a command with a large output is being executed, finally!
• support for using quotes in commands.
• fixed a bug in adb push command.
• updated with latest version of System Command Executor library.
.
update5 [stable] [16/09/2017]
Code:
• fixed the memory leak that occurred when a command with a large output is being executed, finally!
• fixed a freeze in some special cases.
• fixed the weird layout issue on linux.
• replaced the "output contains errors" prompt with a more informative text, including the exit code.
• update to the last version of System-Command-Executer library.
• updated donate url.
• overall performance improvements
• reduced jar size to 44 kbs
.
update4 [stable] [07/05/2017]
Code:
•I quote google: "several bug fixes, and speedy improvements".
•fixed a bug in adb pull command.
•errors are highlighted in red.
•added:
adb shell ip,
adb shell ps,
adb shell netstat,
adb shell pm list packages,
adb usb
version 5.6 [stable] [31/07/2016]
Code:
•Stability, stability, stability, all possible weak spots are fixed, with lots of enhancements , this program is now stable (Hopefully)
•Saving output now is through File dialog
•Shortcuts added for options menu items
•lots of fixes to "your own command" mode + (you can execute by hitting enter)
Version 5.5 [27/07/2016]
Code:
now it's open-source; check the op.
in supported commands:
•added:
adb connect [to connect the phone wirelessly]
adb disconnect
adb root
adb unroot
adb reboot sideload
fastboot reboot-bootloader
•renamed:
adb > adb help
fastboot > fastboot help
in UI :
•enhanced all UI colors.
Version 5.2 [21/07/2106] :
Code:
in compatiblity with Linux and Mac :
•Confirmed for Linux
need a confirmation from you for OsX.
in UI :
•new icon
•the whole UI (including file explorer and information panels) now is totally revamped to Windows Look and feel, now You can say it's beautiful.
•now every mode (adb, fastboot, your own command) has it's output color.
in Errors and Exception:
•now all exceptions are more detailed, to guide you and me to the problem.
in supported commands
•renamed all commands in the list to what they really are to avoid confusion and complexity.
•added :
adb
adb kill-server
fastboot
•changed :
adb devices to adb devices -l
fastboot devices to fastboot devices -l
•removed :
unlock password 2nd method to avoid confusion and complexity.
in output :
•you can save the output using "save output" in "options" menu.
•fixed some output issues.
in code :
•I've changed some algorithms > hmmm, the app size now is 30 kbs lol.
900 downloads
Version 5.0 [initial release] [12/07/2016] :
Code:
the tool now is much more stable and smart, renamed to SADB [Simple ADB]
in how the tool is working:
as I said I've rewrittten the whole code:
•now we have an output area, no files or any leftover data files at all, it's just the tool
•now the tool is executing the commands in really different and cleaner/faster way
•added the Abort button, to abort currently running operations
•added "Your own command" mode [experimental]
•the tool size is 27 kbs
in Errors and Exception:
•all exceptions and errors are caught and handled i believe
•the tool now can determine whatever the output is an error or not
in UI :
•now you can choose from adb, fastboot by radio buttons, instead of this large comboBox
•removed most of the annoying dialog panes
•the overall UI is certainly better and smoother
2800 downloads
Code:
In the future, I might make other changes and fixes,
but they may not be that big to include in separate updates,
so, if you're interested in the latest releases,
feel free to compile the code yourself.
In Debian, there are "android tools" packages and adb and fastboot are simply there. Otherwise, the executable may come with any of Android API packages.
So this runs on Linux. Install adb does nothing. Own command has no command input to use. Need a on-phone file-browser for file to pull. Need option to save logcat to a file. Small things.
I run adb CLI without much ado.
Dovidhalevi said:
In Debian, there are "android tools" packages and adb is simply there. Otherwise, the executable may come with any of Android API packages.
Click to expand...
Click to collapse
Thanks for the help, I'll check.
Edit: own command, intended to allow users to write their command in the same red area, But I'll check, and yes save logcat into file is coming.
Mohamed Hashem said:
ANNOUNCEMENT:
one year & half ago I've created this tool, the main idea was not new, it has been implemented so many times, but I believe that majority of implementations has just covered the most basic and direct commands of ADB/Fastboot,
So, this revive shall FIX WHATEVER PROBLEM YOU FACED WITH THE OLD TOOL. make sure to check the changelog [2nd post].
INSTALLATION :
(make sure you have java installed on your PC)
• first you have to install ADB Installer tool, it will install ADB to your System directly, so no need for any additional files (make sure to give @Snoop05 a Thanks :good .
• then run Simple ADB.jar and that's it!
GUIDE :
• select from "ADB", "Fastboot" or "Your own command" buttons :
- if "ADB" is selected the combobox will contain lots of adb commands :
Check if Device connected properly (adb devices).
Android Logcat.
Install a specific APK file(Android Application).
Uninstall apk <package> .
pull a file from your Android Device to your PC.
push a file from your PC to your Android Device.
View tasks running in your Android device.
Check your Android Device Memory usage.
Check your Android Device storage usage.
Kill all background processes.
Normal Reboot.
Reboot to recovery mode
Reboot to download mode (for Samsung Devices).
Reboot to bootloader mode.
Unlock Patterns/passwords [first method]
Unlock Patterns/passwords [formatting phone method]
- if "Fastboot" is selected the combobox will contain lots of Fastboot commands :
Reboot to Fastboot mode.
Flash Update.zip.
Flash recovery.img.
Flash boot.img.
Wipe (System,data & cache) before restoring nandroid backup.
Flash system.img.
Flash data.img.
Flash cache.img.
- if "Your own command" is selected the combobox will be disabled , and you can write your (still one line) command in the red area.
• Hit Activate to (well, activate the command :cyclops: ).
• Hit Abort to stop the currently running operation ( please think twice before aborting a command).
• You have the Options menu that contains :
-Donate : to support my development and studying (first year college :cyclops: )
- Main thread : to visit this thread.
- ADB Installer : to visit ADB Installer thread.
- Reset : to set the frame as you first opened it.
COMPATIBILITY:
windows (till now)
•the first issue preventing it from being compatible with other OS's is that the way java is executing commands, it's tricky to keep the same simple functionality with the mass compatibility, so i'm still working on that.
•also in other OS's you need to install adb system-wide, and i didn't find any adb-installer-like tool for Linux or Mac os.
I hope i'll get help from the community
Code:
*** Disclaimer
there are some commands I've never tested (like password commands),
because I don't have a spare phone to test on, please use the tool at your own risk.
! note: if you want to support the development of this program, it would be appreciated to click
under my avatar, and Click
:good:
XDA:DevDB Information
SADB, Tool/Utility for all devices (see above for details)
Contributors
Mohamed Hashem
Version Information
Status: Beta
Current Beta Version: 5.0
Beta Release Date: 2016-07-13
Created 2016-07-12
Last Updated 2016-07-12
Click to expand...
Click to collapse
This seems like a really nice tool to users new to ADB, nice work man!
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
thanks, that would be great help for sure.
Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
Please change "adb devices" to "adb devices -l" (lowercase L). Longer output with board name.
ranf said:
Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
Please change "adb devices" to "adb devices -l" (lowercase L).
Click to expand...
Click to collapse
Does everything work fine? Thanks for testing!
I only tried adb devices and logcat so far. -l is just a feature request.
More features I miss
Code:
fastboot devices -l
fastboot reboot
ranf said:
Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
ranf said:
I only tried ad devices and logcat so far. -l is just a feature request.
Click to expand...
Click to collapse
@ranf fastboot reboot does exists: reboot to fastboot mode
Thanks, I'll change it, and thanks for testing, feel free to test other commands
topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
What about starting now, it would be helpful if you tested it now, it seems working, although I don't really know (why) lol
Click to expand...
Click to collapse
Mohamed Hashem said:
@ranf fastboot reboot does exists: reboot to fastboot mode
Click to expand...
Click to collapse
fastboot knows 2 reboots:
- reboot reboot device normally
- reboot-bootloader reboot device into bootloader
ranf said:
fastboot knows 2 reboots:
- reboot reboot device normally
- reboot-bootloader reboot device into bootloader
Click to expand...
Click to collapse
Oh I see, it's found under adb commands as reboot to bootloader, maybe I'll move it to fastboot to avoid confusion.
Great! I love it.
Will you add more commands?
Newyork! said:
Great! I love it.
Will you add more commands?
Click to expand...
Click to collapse
I'm open for suggestions
Also, that's why I've implemented "Your own command" option.
@Mohamed Hashem i belive i can tweak the UI to get close to the window's metro ui which is attractive, stunning and simple if you make it's source open. It's already a good program. And with some furnishings on the UI, it can be the de facto adb for a few years. What say?
iamsubhranil said:
@Mohamed Hashem i belive i can tweak the UI to get close to the window's metro ui which is attractive, stunning and simple if you make it's source open. It's already a good program. And with some furnishings on the UI, it can be the de facto adb for a few years. What say?
Click to expand...
Click to collapse
well, after seeing the initial poll answers, I think I'm taking the Open-source option seriously so whenever I publish it, You're free to do so
Also, I'm about to take a look at JavaFx to polish the ui, thus, We will have multiple good user interfaces, and this is definitely always better
Mohamed Hashem said:
well, after seeing the initial poll answers, I think I'm taking the Open-source option seriously so whenever I publish it, You're free to do so
Also, I'm about to learn javaFx to polish the ui, thus, We will have multiple good user interfaces, and this is definitely always better
Click to expand...
Click to collapse
I know about JavaFX and CSS stuff quite well from my self learning of 1 and a half years. I have some good metro like stylesheets ready to go with built in accent and base theme changing support. I look forward to the aforementioned happening.
Dovidhalevi said:
...
So this runs on Linux. Install adb does nothing. Own command has no command input to use. Need a on-phone file-browser for file to pull. Need option to save logcat to a file. Small things..
Click to expand...
Click to collapse
I indeed ran it under linux, usual java -jar ....was able to exercise adb commands as I describe.
Will always get io-exceptions when hitting abort.
Other exceptions may be due to the Process.start()
Mohamed Hashem said:
Till now I've been using java's regular Process.start() method, It's for Windows only,
Thanks for the help, I'll check.
Edit: own command, intended to allow users to write their command in the same red area, But I'll check, and yes save logcat into file is coming.
Click to expand...
Click to collapse
Great!
topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
You can run it right now as described!
Dovidhalevi said:
I indeed ran it under linux, usual java -jar ....was able to exercise adb commands as I describe.
Will always get io-exceptions when hitting abort.
Other exceptions may be due to the Process.start()
Actually I think that IOExeption comes from start()
did you face other exceptions?
Besides Abort, does executing commands actually work?
You can run it right now as described!
Click to expand...
Click to collapse
The described solves the second problem (adb installation) but the second problem still needs testing\investigation
Thanks for testing and information

Categories

Resources