Database Develop

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

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). Downlkoad 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 (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.
There is actually a manual way of doing what the 15 second installer is doing, by extracting the adb.exe and fastboot.exe to your computer and using the Windows Enviroment variable PATH to make the executables work system wide, however the installer is much quicker, but for reference:
Code:
right-click computer > properties > advanced > environment variables.
under system variables click "path" and click "edit"
at the end of the line, add the below:
;c:\adb_fastboot
where c:\adb_fastboot is where you decided to extract adb and fastboot executables.
Please note, the semi-colon ; is VERY important.
You can do this if for some reason the installer becomes unavailable
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 Universal Naked driver which has better compatibility.
Here is a link to the naked driver: DOWNLOAD THIS which has been taken from this thread:
[ADB/FB/APX Driver] Universal Naked Driver
Some of the below instructions are taken from the thread above by @1wayjonny but I have moved them here to make it easier for you guys.
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 5 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 then follow the wizard to the end.
*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 must 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. If they're not working (mainly Windows users) you may want to check this additional thread about troubleshooting drivers.
[*] Diagnosing USB Driver and ADB issues in Windows - Ensure ADB and fastboot WORK before you root (by @MaxRabbit)
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. If you actually want to do this, please follow this guide:
How to Unlock Bootloader, Install Custom Recovery and Root - The preferred method. Allows you to learn and understand the basics (by @Chromium)
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 bot image (kernel) as you would if you were returning to stock. If you want to return to stock, please use this guide:
How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63)
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

This should absolutely be a sticky!!
Sent from my EVO using XDA Premium 4 mobile app

Evolution_Freak said:
This should absolutely be a sticky!!
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. I created it specifically to put in the general sticky in my signature. Section 1a and 4

Great work @rootSU definitely should be sticky!

psycho693 said:
Great work @rootSU definitely should be sticky!
Click to expand...
Click to collapse
Thanks. Its in there. All in the main sticky thread
Sent from my Nexus 5 using Tapatalk

rootSU said:
Thanks. Its in there. All in the main sticky thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It helps a lot because I have been looking for a good guide to pull system files while the phone is running

psycho693 said:
It helps a lot because I have been looking for a good guide to pull system files while the phone is running
Click to expand...
Click to collapse
Cool
The main thing for me was we had a diagnosis thread and we had a full guide for rooting or returning to stock but nothing to answer the how to set up or how to adb push basic questions... I've seen several threads today alone
Sent from my Nexus 5 using Tapatalk

Very cool, didn't actually know the push/pull commands or that driver you reference

wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:

simms22 said:
wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:
Click to expand...
Click to collapse
LMAO! rootSU, this is freakin awesome. Every thread that I find complaining about issues with toolkits will be redirected here. If this isn't stickied it should be a crime.
Sent from my Nexus 5 using xda premium

I suggested to the mods that we have just one sticky in general that has all the threads we believe to be Stickies within it. That way we can control it ourselves but without making it messy, so we have that now ( see signature).
Sent from my Nexus 5 using Tapatalk

Thanks for listing my Nexus Tools

corbin052198 said:
Thanks for listing my Nexus Tools
Click to expand...
Click to collapse
Thanks for making them
Sent from my Nexus 5 using Tapatalk

simms22 said:
wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:
Click to expand...
Click to collapse
How do I flash the toolkit? I think its bricked :silly:
Good thread.

Amazingly detailed thread. There's no way to mess up reading this thread, the noobs will definitely learn if they can do the reading first that is.
I will laugh when a noob asks, "fastboot? It takes about a minute for me to boot!"
Sent from my Nexus 5 using XDA Premium 4 mobile app

I'm not sure what this all is, but awesome guide!!!!
? I'll be frequently linking this too.

Good job my friend, i am sure it's really helpful for a lot of people
Tapatalk Team SlimRoms

Added the below section about using command prompt. Hopefully a little more detail should help.
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 <directory>" 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:
Click to expand...
Click to collapse

Added a bit more about using directory paths with spaces.
Sent from my Nexus 5 using Tapatalk

After a week with my new nexus, it's time for a litlle fun... But first must say thank you for this explanation.
Sent from my Nexus 5 using Tapatalk 2

[ROOT][UNLOCK BOOTLOADER][CUSTOM RECOVERY][TUTORIAL] Root Android One using Linux

Hello everyone,
I wrote this walkthrough to show you how to unlock the bootloader,install custom recovery and gain root privileges on your Android One by using Linux.
Some of the instructions in this guide are not mandatory to accomplish the task but I decided to include them anyway just for informational purposes because this guide is intended for novice users.
This is my personal method and I will provide you with detailed information to avoid mistakes so read carefully and have fun.
Requisites:
*Backup your data before proceeding!
*Android One
*A Linux distro (Debian/Ubuntu/Mint/ElementryOS or etc)
*android_one_root.zip (Download it from http ://goo.gl/B3LjRJ ) [Note: Remove spaces from the link ]
Let's begin.
Chapter 1: Developer options, Android debugging & Android Tools
​
Phase 1: Developer options and Android debugging.
Go to Settings > About phone and tap 7 times on Build number to enable Developer options. You will see a little pop-up that says "You have enabled development settings!".
Go back to Settings menu and scroll down to Developer options. Tap on it and then enable Android debugging. You will be asked to allow USB Debugging, confirm by tapping on OK.
​
Phase 2: Installing Android tools (ADB & Fastboot) on Linux. (I'm using Ubuntu 15.04 here)
Open Terminal and run this command to install ADB and Fastboot tools:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Chapter 2: Unlock the bootloader.
​
In this chapter we will focus on the Linux Terminal rather than the phone. Don't be scared, it will be easy enough and you will have the opportunity to learn something new. :fingers-crossed:
Now you can connect your Android One phone to your computer.
Once your phone has been connected to your pc, open the Terminal and run this command:
Code:
adb devices
​
Check the phone. Your computer's RSA fingerprint will be shown and you will be asked to allow USB debugging. Confirm by tapping on OK.
​
Note: If you see offline instead of device, run the adb devices command once again.
If adb devices output looks like this:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
Run these commands:
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices
Put yourphone in Fastboot Mode by running this command:
Code:
adb reboot-bootloader
EASY WAY: You can put your phone in Fastboot Mode by holding down Power button and Volume up simultaneously for few seconds (it works either phone on or off).
Commands in Fastboot Mode need Administrator privileges on your pc, that's why we will use sudo.
Run this command to make sure that Fastboot Mode is working correctly:
Code:
sudo fastboot devices
​
Next command will unlock the bootloader:
Code:
sudo fastboot oem unlock
The phone will reboot and it will restore factory settings. All personal data and settings will be lost.
Once the reboot is complete, download & extarct the "android_one_root.zip" file to your pc.Now copy both "eu.chainfire.supersu.apk" and "update.zip" file to your phones sd card.Then install "eu.chainfire.supersu.apk" in your phone.
Then put the device back in Fastboot Mode by holding down Power button and Volume up simultaneously for few seconds (it works either phone on or off).
Chapter 3: Install Custom Recovery.​
You will find three custom recovery in the archive.Choose one of them. (I'm using TWRP here)
So put the recovery's .img file on your pc's Desktop.
On Terminal, change the current working directory by running this command: (Change Desktop to ypur current working directory)
Code:
cd Desktop
nstall TWRP Recovery by running this command: (If you want to flash CWM/PHILZ recovery,just replace TWRP.img to CWM.img/PHILZ.img )
Code:
sudo fastboot flash recovery TWRP.img
Now it's time to enter Recovery Mode. To do that, hold down Power button and Volume up.
In TWRP Recovery tap on Install, scroll down to the update.zip archive and select it. Perform a swipe to confirm the installation and lastly reboot your phone.
Once the reboot is complete, go to google play store and install "Root Checker" to check your device root status.
Congratulations, you made it!

If you are using phliz recovery mode
before install custom recovery format userdata
code
sudo fastboot format userdata
otherwise it will stuck in recovery mode

How to unlock, TWRP, root, etc from OSX Mavs - MacBook Air

somehow I managed to install the OTA MM update that I was holding off until I could unlock, root, blah, blah, blah.
I'm now on 20i.
And it responds to adb (v1.032) and fastboot commands from Terminal on my OSX MacBook Air.
Has anyone "authorized" (aka - fastboot oem unlock) their 811 and flashed TWRP from a Mavs Mac ?
Or do I need to go to my Bootcamp partition to accomplish?
Seems like to should work from Mavs direct, but …….

Bootcamp not needed.
system settings (tap on Build number until it says you’re a developer.)/developer/check oem unlock & USB debug
USB connect to Mac. I use Android File Transfer. I found it less annoying and very fast.
But it will not work with the LG drivers installed. aka LGUnitedMobileMacDriver_v4.23.zip, or LGMobileMacDriver_v5.2.zip, or LGBridge_Mac.dmg.
in Terminal:
adb devices - should reveal the devices serial - LGH811xxxxxxxxx. If not, your Mac and adb/fastboot are not set up properly.
adb reboot bootloader
fastboot devices - should reveal serial again. xxxxxxxx
fastboot oem unlock - this will WIPE the G4s internal SD that comes with the phone.
fastboot getvar unlocked - to confirm unlock
fastboot reboot - and set-up as a new device.
If you're on MM, and you set it up previously, restore should happen automatically upon reboot, after you enter your google or ID, etc.
If it seems to be taking too long, restart.
Make sure you recheck that USB debug is checked in developer options.

and then to flash TWRP and SuperSu so as to root.
Terminal:
adb reboot bootloader
fastboot boot (drag and drop the {I shortened the name of the file after duping} twrp.img into the Terminal window)
This will boot you into a temporary TWRP recovery. (v2.8.7.2)
Install twrp.img (select zip or img button bottom right)
Then install SuperSu 2.6.7.zip.
REBOOT SYSTEM
check root -
Terminal:
adb shell. should get #. if not - su. should get #.

troubleshooting.
May have to re-enter developer mode
sys settings/about/software/more/tap build number 7 times fast.
unplug USB.
Toggle USB debugging in Developer. Should get prompt about RSA.
re-plug USB
adb kill-server
adb devices
If TWRP isn't recognizing your b.u., write a new back-up. This creates the path TWRP wants to see. Copy your old b.u. into the new folder:
TWRP/BACKUPS/LGH811#########/2016-10-23--15-58-36_MRA58K
RenameÂ*the old b.u. the same as the new b.u. and toss the new one.
Reboot Recovery and you now should now able to to restore from the old b.u.

Cannot relock bootloader with Tool-all-in-one on ROG Phone 3

Hello,
despite presumably doing everything correctly, Tool spews this error when I'm trying to relock the BL by using "fastboot oem asus-lock" command:
FAILED (remote: 'Command not supported in default implementation')
1. I have connected the phone to the side port.
2. Tool folder is directly in C:\ directory.
3. ADB binaries are installed correctly.
4. Phone is in fastboot mode and detected, but the tool cannot detect correctly which phone it is and asks me to choose the model manually, but ROG 3 is not on the list, so I chose ROG Phone 2. Does it matter? If so, what do I do? I also set priviledges for Tool-all-in-one systemwide, does it matter?
Also, should I use the command line in Advanced Options of the tool, or should I rightclick the folder and summon the command line from there? Please help, I don't have any more ideas! Thank you!

use the side usb port (the top black one, not the bottom orange one) and try the command again through FB

Thank you for fast response!
I'm constantly using the sideport, and the command still fails with the message above.
What I can add is that EVERY fastboot process fails with the SAME message, so it's not just relocking that is the problem, but it seems that every fastboot command cannot be executed on my ROG Phone 3 (aside from fastboot devices, which correctly shows my device as connected).
Which suggests to me that something is wrong with my setup. Anybody has any idea?

When I try to relock my rog phone 3 I do the list devices command and it shows my device, I then reboot into fastboot
and type command fastboot oem asus-lock and all it says is <waiting for device> how can I relock bootloader???????? If there was an apk to unlock it shouldnt there be an apk to relock it?

You need install fastboot drivers on your pc, so device manager will see your phone

Question fastboot devices not showing

When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. I'm pretty new to rooting so I'm not sure what's going on. I don't have a SIM Card so that might be the issue, but I'm trying to find a root guide that doesn't require sim.
What I've installed;
Latest USB Driver (MTP USB Device)
Latest ADB/Fastboot from android.com/studio/releases/platform-tools
Installed Fastboot ROM MIUI V13.0.6.0.SKDMIXM Stable from https://xiaomirom.com/en/rom/xiaomi.../#download-xiaomi-11t-pro-stable-fastboot-rom
Device Specs:
- MIUI Global 13.0.6 Stable (SKDMIXM)
- Android ver. 12 SKQ1.211006.001
Following this guide to root and have been following step by step up to 3:12:

WhalePC said:
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. Not sure what's going on.
Following this guide to root and have been following step by step up to 3:12:
Click to expand...
Click to collapse
Maybe you summarized the command in your statement but with power shell the command is "./fastboot devices"
Do you see the device icon in the taskbar?

NOSS8 said:
Maybe you summarized the command in your statement but with power shell the command is "./fastboot devices"
Do you see the device icon in the taskbar?
Click to expand...
Click to collapse
Yeah i see the icon on my taskbar. Just tried running it via "./fastboot devices" and no devices show up. I haven't unlocked the bootloader yet (haven't enabled Mi Unlock status) yet is that maybe the issue? If so, is there a way to root without the need of a sim card?

WhalePC said:
Yeah i see the icon on my taskbar. Just tried running it via "./fastboot devices" and no devices show up. I haven't unlocked the bootloader yet (haven't enabled Mi Unlock status) yet is that maybe the issue? If so, is there a way to root without the need of a sim card?
Click to expand...
Click to collapse
You generally shouldn't need a SIM card to use ADB or fastboot commands.
Are you sure you have the correct drivers installed? Does the device appear under adb devices when in Android?

V0latyle said:
You generally shouldn't need a SIM card to use ADB or fastboot commands.
Are you sure you have the correct drivers installed? Does the device appear under adb devices when in Android?
Click to expand...
Click to collapse
How do i check that I have the correct drivers installed? I ran adb devices and it showed my device 3d37ace2 device was connected.
EDIT: Here's how I enter into fastboot and excute commands;
- Plug in phone into PC and wait for icon to show up on taskbar
- Open Powershell in platform-tools folder
- Power off phone and enter fastboot (hold down power button+vol down)
- Once Fastboot text shows up on my phone I run the command "fastboot devices" in powershell

WhalePC said:
How do i check that I have the correct drivers installed? I ran adb devices and it showed my device 3d37ace2 device was connected.
EDIT: Here's how I enter into fastboot and excute commands;
- Plug in phone into PC and wait for icon to show up on taskbar
- Open Powershell in platform-tools folder
- Power off phone and enter fastboot (hold down power button+vol down)
- Once Fastboot text shows up on my phone I run the command "fastboot devices" in powershell
Click to expand...
Click to collapse
This looks like a good place to start. It's possible you have a generic ADB driver installed and may need a device specific one.

V0latyle said:
This looks like a good place to start. It's possible you have a generic ADB driver installed and may need a device specific one.
Click to expand...
Click to collapse
Just reinstalled the latest ADB/Fastboot from https://androidmtk.com/download-15-seconds-adb-installer and still have the same issue. I also installed Xiaomi AB/Fastboot Tools to check if it can identify my device and it does.
Running adb shell in cmd prompt outputs:
Code:
C:\Users\Whale>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
vili:/ $
But once it's in fastboot it responds with:
Code:
C:\Users\Whale>adb shell
adb.exe: no devices/emulators found
Same for Powershell:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
3d37ace2 device
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
Currently, when my phone is turned on (not in fastboot), my device is detected as 3d37ace2 (codename: vili), but as soon as it goes to Fastboot, it no longer can detect the device.

WhalePC said:
Just reinstalled the latest ADB/Fastboot from https://androidmtk.com/download-15-seconds-adb-installer and still have the same issue. I also installed Xiaomi AB/Fastboot Tools to check if it can identify my device and it does.
Running adb shell in cmd prompt outputs:
Code:
C:\Users\Whale>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
vili:/ $
But once it's in fastboot it responds with:
Code:
C:\Users\Whale>adb shell
adb.exe: no devices/emulators found
Same for Powershell:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
3d37ace2 device
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
Currently, when my phone is turned on (not in fastboot), my device is detected as 3d37ace2 (codename: vili), but as soon as it goes to Fastboot, it no longer can detect the device.
Click to expand...
Click to collapse
ADB commands won't work in fastboot and vice versa. When your device is in Android or recovery, you can use ADB commands, but when it's in bootloader mode, you have to use fastboot commands. ADB shell won't do anything for you in fastboot because there's no kernel running, much less a shell.
Since your device isn't appearing under fastboot devices it's most likely a driver issue. You need two separate drivers; the ADB driver is not device specific, but the bootloader driver is.
Case in point: This is what appears when my Pixel 5 is connected while booted into Android:
When I reboot to bootloader, this is what I see:
So, this is what I suggest:
Reboot to bootloader, connect to your PC, and look at Device Manager to see if anything comes up as unrecognized. Make sure it's the right device by unplugging the USB cable; it should disappear. You'll then need to update the driver, and point it to the the Xiaomi driver folder.

V0latyle said:
ADB commands won't work in fastboot and vice versa. When your device is in Android or recovery, you can use ADB commands, but when it's in bootloader mode, you have to use fastboot commands. ADB shell won't do anything for you in fastboot because there's no kernel running, much less a shell.
Since your device isn't appearing under fastboot devices it's most likely a driver issue. You need two separate drivers; the ADB driver is not device specific, but the bootloader driver is.
Case in point: This is what appears when my Pixel 5 is connected while booted into Android:
View attachment 5731657
When I reboot to bootloader, this is what I see:
View attachment 5731663
So, this is what I suggest:
Reboot to bootloader, connect to your PC, and look at Device Manager to see if anything comes up as unrecognized. Make sure it's the right device by unplugging the USB cable; it should disappear. You'll then need to update the driver, and point it to the the Xiaomi driver folder.
Click to expand...
Click to collapse
Thanks fam, was able to solve it by installing a different driver from this video:
.
Now I'm getting an error:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot flash boot magisk_patched.img
Sending 'boot_a' (196608 KB) OKAY [ 4.210s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
which I assume means I need to unlock my bootloader via Mi Unlock status?

WhalePC said:
Thanks fam, was able to solve it by installing a different driver from this video:
.
Now I'm getting an error:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot flash boot magisk_patched.img
Sending 'boot_a' (196608 KB) OKAY [ 4.210s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
which I assume means I need to unlock my bootloader via Mi Unlock status?
Click to expand...
Click to collapse
Yep. I don't know how it works on Xiaomi devices but try fastboot flashing unlock
Unlocking your bootloader will wipe data, so if you need to back anything up, do that first.

Enter in FASTBOOT MODE: press Power+Volume down button for 4-5 sec in the same time,the phone reboot, at the vibration release the power button.Now plug in the phone to the PC.
Having the bootloader locked does not prevent seeing the device in Fastboot mode.(***Not useful at the moment)
To root you must first unlock the bootloader.(***your bootloader is locked)(FAILED (remote: 'Flashing is not allowed in Lock State')
Unlock the bootloader
You must have a Xiaomi account and a valid sim.
Procedure:
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
Why look for tutorials on You tube'Sometimes good, sometimes fake) while on XDA(Always good )in the How to section of your device these tutorials exist and specify that the bootloader must be unlocked.
https://forum.xda-developers.com/t/root-xiaomi-11t-pro.4441213/
https://forum.xda-developers.com/t/...structions-for-xiaomi-11t-pro-global.4362515/

check debugging via USB option.

WhalePC said:
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. I'm pretty new to rooting so I'm not sure what's going on. I don't have a SIM Card so that might be the issue, but I'm trying to find a root guide that doesn't require sim.
What I've installed;
Latest USB Driver (MTP USB Device)
Latest ADB/Fastboot from android.com/studio/releases/platform-tools
Installed Fastboot ROM MIUI V13.0.6.0.SKDMIXM Stable from https://xiaomirom.com/en/rom/xiaomi.../#download-xiaomi-11t-pro-stable-fastboot-rom
Device Specs:
- MIUI Global 13.0.6 Stable (SKDMIXM)
- Android ver. 12 SKQ1.211006.001
Following this guide to root and have been following step by step up to 3:12:
Click to expand...
Click to collapse
You will need to manually configure fastboot drivers.