pretty much the only thing ive seen about it is https://source.android.com/devices/bootloader/fastbootd?authuser=1
but im interested to know what its actual point is. since on my phone when i use adb/fastboot reboot fastboot it doesnt let me use no fastboot or adb commands and in its ui you cant do anything either, which left me quite confused as why it even exists. havent come across any proper documentation or tutorials of it either so it all has just left me very confused.
Typically both the adb and the fastboot are executables to be run on Windows / MacOS / Linux computers. Their counterparts on Android device are adbd and fastbootd. Both requires Android device and computer got connected via USB-cable - preferredly the one that came with Android device. Neither adb nor fastboot have an UI, they only have a CLI, what is run on computer's shell.
On Android-side both the adbd and fastbootd are started when Android boots up.
Of course you also can run both the adb and the fastboot from within one Android device connected to another Android device, but this requires to have Termux shell installed on the one Android device, AFAIK.
Related
Ok, total noob here. I've been trying to get CWM on my TF700. I have Windows7 64 bit. I plug in either the tablet alone or docked, using any combination of USB2.0 dedicated charge/comm cable, USB3.0 dedicated charge/Comm cable and usb 2.0 and usb3.0 ports. The computer finds the "fastboot device" (usb2.0 port) or the AsUsTeK Fastboot device (USB3.0 port). It shows up in my devices list as an unknown type, but the drivers appear to be loaded correctly since the computer sees the devices and calls it the "Fastboot Device". I've tried the "ADB devices" and the "Fastboot Devices" commands but my tablet is never found (the command never returns the device string) and issuing the fastboot command to flash the CWM recovery just sits there waiting for the device. I'm lost. Can anyone give me a clue?
SDK
Washedman said:
Ok, total noob here. I've been trying to get CWM on my TF700. I have Windows7 64 bit. I plug in either the tablet alone or docked, using any combination of USB2.0 dedicated charge/comm cable, USB3.0 dedicated charge/Comm cable and usb 2.0 and usb3.0 ports. The computer finds the "fastboot device" (usb2.0 port) or the AsUsTeK Fastboot device (USB3.0 port). It shows up in my devices list as an unknown type, but the drivers appear to be loaded correctly since the computer sees the devices and calls it the "Fastboot Device". I've tried the "ADB devices" and the "Fastboot Devices" commands but my tablet is never found (the command never returns the device string) and issuing the fastboot command to flash the CWM recovery just sits there waiting for the device. I'm lost. Can anyone give me a clue?
Click to expand...
Click to collapse
You have downloaded the sdk from google yes??Put the .exe is the right place??Opened you CMD window with admin rights???
lj50036 said:
You have downloaded the sdk from google yes??Put the .exe is the right place??Opened you CMD window with admin rights???
Click to expand...
Click to collapse
To the best of my knowledge (slim, I AM a noob, after all) I would say yes to all the above. The only thing I would question would be which .exe and which place? I still have a problem with reading peoples minds...
fastboot/adb
Washedman said:
To the best of my knowledge (slim, I AM a noob, after all) I would say yes to all the above. The only thing I would question would be which .exe and which place? I still have a problem with reading peoples minds...
Click to expand...
Click to collapse
Fastboot.exe/adb.exe in the root of your local hard drive
lj50036 said:
Fastboot.exe/adb.exe in the root of your local hard drive
Click to expand...
Click to collapse
No, I didn't place them in the root. I created a folder in the root called Android (for the ADB files) and Fastboot for the fastboot files. I opened the command line and CD to the appropriate folder for the fastboot. For the ADB.exe, I added a path statement in the environment variables as suggested. I can type in either command and the computer will recognize it and give the all the command structure, so I would assume that is operating correctly, yes?
Washedman said:
No, I didn't place them in the root. I created a folder in the root called Android (for the ADB files) and Fastboot for the fastboot files. I opened the command line and CD to the appropriate folder for the fastboot. For the ADB.exe, I added a path statement in the environment variables as suggested. I can type in either command and the computer will recognize it and give the all the command structure, so I would assume that is operating correctly, yes?
Click to expand...
Click to collapse
Yes that is great. With the tablet in fasboot mode type
fastboot devices what is the outcome of this
lj50036 said:
Yes that is great. With the tablet in fasboot mode type
fastboot devices what is the outcome of this
Click to expand...
Click to collapse
Nothing. It returns no string, letters or numbers. Blank. I tried every combination of ports and cables and drivers. Getting a bit frustrated.
I had a similar problem with flashing a custom recovery on the tf700 as well (mainly because of the dock), so let me share with you a few pointers that may help you fix this (it certainly helped in my case):
1. Never do any flashing, adb or fastboot with the tablet docked, especially when flashing recovery: I spent three hours scratching my head figuring out why I couldn’t flash the recovery (fastboot stuck at sending file), only to find out that everything worked perfectly when I removed the dock. In my opinion, the dock makes things unpredictable, so do everything with the dock.
2. As for adb and fastboot, you should just start setting up from scratch as it is always easier than troubleshooting for errors. After unlocking the bootloader using ASUS tool, what I suggest you should do are as below:
a. Uninstall COMPLETELY your current adb/fastboot drivers and install Universal Naked Driver 0.73 (http://forum.xda-developers.com/showthread.php?t=2513339). Take note of the warning in red on how to uninstall existing adb driver.
b. Also take note that you actually need 2 sets of drivers, 1 for adb and 1 for fastboot (which are both included in the Universal Naked Driver). When you connect your tablet with Android running to your PC, you are installing driver for adb. With the driver properly installed, “adb devices” command will work and give you the list of connected devices to your PC through Windows’ CMD. Please also Google or search xda for adb files (no need to download the whole Android SDK just to get those adb files).
c. After successfully installing adb driver, you can manually reboot your tablet into fastboot mode through the button combo (power + volume down) with the tablet still connected to your PC. By then, your Device Manager should have another device listed as fastboot device. Again, follow the steps in the link to uninstall and reinstall fastboot driver. With this set up, you should be able to run “fastboot devices” command.
d. With fastboot, you can now flash a custom recovery. As a side note, since all this flashing custom recovery and ROM can potentially brick your tablet, after you have finished fixing adb/fastboot and get your ROM running, I strongly suggest you follow this link to obtain nvflash (http://forum.xda-developers.com/showthread.php?t=2455925) and make your tablet unbrickable. I actually did this before flashing a custom ROM, but I honestly don’t know if the timing makes any difference.
So after a lot of headache and messing with drivers, 3 machines, 1 grumpy wife and staying up until 4am. I figured the issue wasn't the drivers. But the version of ADB and Fastboot which I was trying to use. That and the USB hub I was trying to go through.
The way I solved the issue was to install the tools and drivers from the following thread and to plug directly into a USB port rather than a USB hub:
http://forum.xda-developers.com/showthread.php?t=2588979
A friend of mine has a Stylo 6 that says corrupted when it boots. It is however already set to USB debugging. However, I do not have access where I'm at to a PC or a Chromebook to install the dev tools. Is it possible even with third party paid software to install the dev environment on another Android phone and use it for fastboot etc?
You don't need to add ADB and/or Fastboot to any Android device. In common both ADB and Fastboot ( the latter only unless OEM decided to omit it ) are integral part of every Android release: ADB is housed in Android's user-space, Fastboot typically is part of device's bootloader unless Android has a Dynamic Partition layout, then Fastboot is also housed in Android's user space.
Ok, I guess what I need to know if I can install and use adb server on an Android device. I don't have access to a PC Mac or Chromebook to install the sdk tools. Can this be installed on my phone ( using a Linux or windows emulator maybe) to use to fix his phone?
ADB is nothing more than a tool that allows you to execute commands which would interact with Android shell. So you can install / open in Android a shell app ( e.g. Termux ) and run the commands ( Linux compliant ) therein. Will say you don't need a computer to operate on Android system of device,
Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.
You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day
Chrisp3 said:
Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.
Click to expand...
Click to collapse
On Windows, make sure your phone is connected and you can run ADB commands. Enter Device Manager in Windows and verify that there is a listing for Android ADB Interface.
I just connected to a new computer and I could do ADB but not Fastboot. Discovered that instead of ADB Interface in Device Manager, it just said "Pixel 3a."
If this is the same for you, go install the Android USB drivers.
KaptinBoxxi said:
You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day
Click to expand...
Click to collapse
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!
Chrisp3 said:
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!
Click to expand...
Click to collapse
The issue with the fastboot method (realized this when I upgraded to Win11 Beta) is the ADB Quick Installs are missing some stuff, and cause certain flash methods to not work via flash-all.bat's from Google or Graphene or others.
When I install ADB System Wide, I also download the platform-tools from Google, and over-write everything in the c:\adb folder, also adding the stuff missing. Idk why the adb quick installers don't just download from google directly, would save a lot of headaches
Hey, im having trouble finding working ways to root my op7pro GM1913 (OOS 11.0.4.1 GM21BA)
Ive been trying this https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Currently trying to unlock bootloader. (Step 2)
I can connect via adb but when i go to bootloader/fastboot i lose connection to the phone.
Ive tried regular adb command tools and "TOOL ALL IN ONE" When the phone is on it responds to adb commands but when i need fastboot commands its not working and i can see the device id dissapear from the all in one tool.
I have tried multiple usb ports (2.0 and 3.0) and multiple usb C cords (Op oem + Samsung) Tried removing Windows signature verification and installing oneplus usb drivers, but it gets stuck at "Execute the commands..." (99% or so) When i try again it finds some installation files. When im in bootloader, Windows device manager still shows a generic android phone. Oem unlocking and usb debugging is on, also set default usb configuration to file transfer. No help.
I want to keep Oxygen os, but i want to be rooted and have magisk, preferably TWRP too but im open to other ways.
Windows 10 20H2 if that matters. (Latest update for me)
Oneplus 7pro GM1913 (Eu nordic)
Oxygen os 11.0.4.1 GM21BA
Download a Linux distro and install adb and fastboot like this: https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Just download adb and fastboot tools package from Google, extract it,open command prompt inside where you extract it and enter these in terminal:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Then adb --version (enter) fastboot --version (enter) like Nathan says in guide. Super easy and I guarantee you if you go this route you won't have any hiccups. Sounds like stupid windblows driver issues or outdated adb/fastboot tools. One of the two. Are you flipping on dev options and check marking little box that pops up on your phone to allow it to communicate with PC? A simple : adb devices (enter) should make it appear on phone screen. You don't even have to install Linux, you can boot it off a live USB. Takes about one minute to make one. If you make one you can boot the live USB , download adb and fastboot, and install as Nathan's guide says then reboot when you are done and your back in windblows. IDK why anyone wouldn't want Linux installed though. Best decision I ever made was switching from windows to Linux about 9 years ago. It really makes anything you do to your devices MUCH easier to do!! This may sound stupid but have you rebooted your PC? Because you will definitely need to , probably more than once on windblows to get it to work.
Thank you for the reply. No stupid questions, yes i tried rebooting pc/phone. Ill try your way and report in a couple days.
Solution is simple. From Android 11 on, OnePlus (and Android phones in general) uses the universal drivers, you just need to install them in Windows in order to use fastboot commands. See my answer in this post.
There are a few things you can try if your OP7 Pro is not responding to fastboot commands:
1. Make sure you have the latest drivers installed for your phone.
2. Try using a different USB cable.
3. If you're using Windows, try running the fastboot commands from a command prompt with administrator privileges.
4. Try booting your phone into recovery mode and running the fastboot commands.
I'm really having a hard time getting ADB drivers to work on Windows 7 so that I can connect my Android phone to my computer to run some ADB commands. I've tried three different packages; I guess the latest ADB MSI installer and another couple various packages. And I can't get any devices to show up when I type ADB devices. I need something simple if somebody can help treat me like a newbie although I have some experience with Linux and the command prompt but I really need something dead simple that will just install ADB on my computer so I can run a command on my phone. Any help would be greatly appreciated.
Wjbell said:
I'm really having a hard time getting ADB drivers to work on Windows 7 so that I can connect my Android phone to my computer to run some ADB commands. I've tried three different packages; I guess the latest ADB MSI installer and another couple various packages. And I can't get any devices to show up when I type ADB devices. I need something simple if somebody can help treat me like a newbie although I have some experience with Linux and the command prompt but I really need something dead simple that will just install ADB on my computer so I can run a command on my phone. Any help would be greatly appreciated.
Click to expand...
Click to collapse
While plenty of people know adb better than I do, I can try to help you where we need to start at the beginning I think, which is to state that there is nothing to "install" on either Android or Windows, other than the one adb.exe executable on Windows.
However, you do need to enable a few options in Android settings.
With that, you can get Windows to talk to Android over adb as shown in my screenshots below, whether over USB or completely over Wi-Fi.
My first question to you to help you is to ask a basic question.
Q: Did you turn on USB debugging in Developer options?
A: ?
Yes I have us debugging on on my Android phone. I've installed USB drivers before on an older phone to allow me to use my Android phone for an internet connection on my PC and it was pretty simple and word flawlessly.