since fastboot and adb are common throughout the ecosystem (Google provided apps as part of the SDK), does that mean I can use the fastboot/adb I'm using on my one x on my TF700?
mrjayviper said:
since fastboot and adb are common throughout the ecosystem (Google provided apps as part of the SDK), does that mean I can use the fastboot/adb I'm using on my one x on my TF700?
Click to expand...
Click to collapse
Since adb and fastboot run on your PC, you can use the same tools for all Android devices. Note that the fastboot implementation in the TF700's bootloader is limited, it only accepts a subset of possible options and only likes to flash blobs in a specific format.
Related
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.
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
Driver Binaries for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
How do I install these ? No documentation is provided ? Please help.
Syntaxerror_s said:
Driver Binaries for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
How do I install these ? No documentation is provided ? Please help.
Click to expand...
Click to collapse
Install fastboot on your PC, install the Google android device drivers for Pixel devices on your PC.
Place the vendor.img(the binary file that you downloaded) in your fastboot folder on PC(not in another folder inside fastboot folder). Rename the file to "vendor.img", this makes the fastboot command easier.
Enable USB debugging on your device(not absolutely necessary but it makes things easier at some point).
Boot the device into fastboot mode, open a fastboot terminal on your PC, connect your device to PC.
Flash the vendor.img via fastboot using the following fastboot command:
fastboot flash vendor vendor.img
No, that isn't a typo, type it exactly as I typed it above, with both "vendors".
Droidriven said:
Install fastboot on your PC, install the Google android device drivers for Pixel devices on your PC.
Place the vendor.img(the binary file that you downloaded) in your fastboot folder on PC(not in another folder inside fastboot folder). Rename the file to "vendor.img", this makes the fastboot command easier.
Enable USB debugging on your device(not absolutely necessary but it makes things easier at some point).
Boot the device into fastboot mode, open a fastboot terminal on your PC, connect your device to PC.
Flash the vendor.img via fastboot using the following fastboot command:
fastboot flash vendor vendor.img
No, that isn't a typo, type it exactly as I typed it above, with both "vendors".
Click to expand...
Click to collapse
Have you looked at the binary files. I assume not judging by your answer. They are not in * .IMG. Format. Hence why I'm asking. I assume you think I'm talking about a factory image. Which I am not.
Syntaxerror_s said:
Have you looked at the binary files. I assume not judging by your answer. They are not in * .IMG. Format. Hence why I'm asking. I assume you think I'm talking about a factory image. Which I am not.
Click to expand...
Click to collapse
No, I assumed it was a vendor.img because that is what the Google page that you linked labels it as. it isn't a far stretch to think that Google would know what kind of file it is since they are the ones that built it, not to mention that they are the ones that invented android in the first place. Inside the file is a .sh file. Try finding instructions for flashing .sh files via adb/fastboot.
Droidriven said:
No, I assumed it was a vendor.img because that is what the Google page that you linked labels it as. it isn't a far stretch to think that Google would know what kind of file it is since they are the ones that built it, not to mention that they are the ones that invented android in the first place. Inside the file is a .sh file. Try finding instructions for flashing .sh files via adb/fastboo
Click to expand...
Click to collapse
I figured it out thanks for the input,
Basically just have to run the .sh in terminal and creates a make output which auto generates the files.
I use the command fastboot -w update insert rom.zip or fastboot -w also fastboot update rom name.zip does not work. I use minimal adb fastboot I can't seem to sideload any roms even with the current build. What is going on? I get invalid sparse then failed within 20 seconds. Yes, I am in the bootloader screen and my phone is bootloader unlocked. Ones like StagOS for example or the more recent roms. I have no problem with Graphene OS or Caylx OS though.
UltimateGamer83 said:
I use the command fastboot -w update insert rom.zip or fastboot -w also fastboot update rom name.zip does not work. I use minimal adb fastboot I can't seem to sideload any roms even with the current build. What is going on? I get invalid sparse then failed within 20 seconds. Yes, I am in the bootloader screen and my phone is bootloader unlocked. Ones like StagOS for example or the more recent roms. I have no problem with Graphene OS or Caylx OS though.
Click to expand...
Click to collapse
Because you're not supposed to use "Minimal ADB and Fastboot". The binaries inside that package are years old. No wonder you're getting all those errors and have issues while trying to flash a ROM that is straightforward.
Download the latest platform-tools from Android's website (google).
Also, make sure that you're not using Windows PowerShell, but the actual CMD.
ekin_strops said:
Also, make sure that you're not using Windows PowerShell, but the actual CMD.
Click to expand...
Click to collapse
What is the reasoning behind this? I pretty much always use PS, guess I'll have to stop?
It being PowerShell or cmdline is irrelevant. Anyways..
Well, you should be using the latest platform-tools and have it added to PATH. A lot of unofficial drivers floating around on the internet install outdated adb/fastboot along with the drivers. Please refrain from installing these as well as minimal adb & fastboot; Use the official google driver and official platform-tools instead.
Alternatively you can prefix each adb/fastboot cmd with ./ while in the platform-tools folder via powershell or bash, etc.
For example:
./adb sideload ./rom.zip
Or
./fastboot -w update ./rom.zip
This tells the shell "Hey, I want to execute this local file, not the one in PATH".