Install adb and fastboot from /e/ documentation

Is there anyone that can explain with easy words and step by step this documentation?

I dont understand really how to do it.

I have delete by mistake /usr/bin/fastboot and now I cant make it run the fastboot

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

Since you refer to a step by step guide already … Where do you start having problems with it?

And since /usr/bin/fastboot sounds like Linux … which Linux do you use?

And since /usr/bin/fastboot sounds like this fastboot was installed via means of the Linux you use (following the guide fastboot doesn’t end up there, I think) … can’t you just (depending on which Linux you use)

… or reinstall adb and fastboot via your Linux’s graphical software install center?



I am using a Ubuntu 20.
I wil not like to use the package from ubuntu cause is outdated.

Fair enough, it tends to be outdated. It might still work, though, and would have been a quick fix.

So, where does trouble start for you with the /e/ guide?

I know that it will have been fast but then I will not learn something new. And e/ also ssugested to use the last build of fastboot.

I start in here in the terminal, in the first step

‘/home/noax/platform-tools’ /platform-tools/adb
bash: /home/noax/platform-tools: Is a directory

‘/home/noax/platform-tools’/platform-tools/adb devices
bash: /home/noax/platform-tools/platform-tools/adb: No such file or directory

Type the below command to you .bashrc file

I have done this and nothing happen?

I have just got this one that it makes it easy and works:


unzip \
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot`

Just a quick tip: When you first open the Linux terminal, it starts you in the home directory (i.e. the one called by your user name). That means, if I understand what you typed, you would not start your command by typing “/home” since you’re already there.

From the home directory, to change to a different directory, for instance “noax”, you would type cd noax and then hit the enter key, which means “change directory to noax.” Or cd noax/platform-tools to go deeper in the directories.

Once you’re in the directory you want, then execute the appropriate commands.

To return to a previous directory, type cd and then enter.


This might be useful: The Linux command line for beginners | Ubuntu


To avoid having to type the above commands every time you can add the location of the folder where you save the extracted platform tool file to you system configuration

On Ubuntu systems

Type the below command to you .bashrc file

You will be able to see the .bashrc file which are hidden files by pressing on your keyboard ctrl and h keys

export PATH="$HOME/platform-tools:$PATH"

here we have assumed you have saved the downloaded files to a folder named platform-tools and this is in your home directory

After this you should be able to access adb and fastboot by typing only the below commands in a console

adb devices


fastboot devices

I have copy that in the file but the fastboot still is not reconizing the device. If I use the command

platform-tools/fastboot devices

then it can recognize it


After you add
export PATH="$HOME/platform-tools:$PATH"
to your ~/.bashrc you will have to logout and log back in again to make the change effective.


I have done that but it doesnt work either

$ fastboot devices
List of devices attached

And doesnt matters where is add export PATH="$HOME/platform-tools:$PATH" ? I add it at the end of the text

That is correct, you add it as a new line at the foot of the existing text.

Can we just check that platform-tools got unzipped in the expected place. Please can you show the output of:

cd ~
cd platform-tools

Edit. The above is academic if you already did:


unzip \
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot`

Please can you confirm if you actually did that? If you did then you should probably delete your added line in .bashrc.

1 Like

~$ cd ~
noax@noax:~$ cd platform-tools
noax@noax:~/platform-tools$ ls
adb fastboot make_f2fs_casefold sload_f2fs
dmtracedump hprof-conv mke2fs
e2fsdroid lib64 mke2fs.conf sqlite3
etc1tool make_f2fs NOTICE.txt systrace

Yes I did it cause the other on from e/ was not evn working to.
Should I start from 0 again?

I have uninstall the adb fastboot now again. And now I try to open from the file platform-tools the adb and adb devices and it says that bash : /usr/bin/ad no such file or directory

I have just found how to do it :

1.Extract the zip of the adb/fastboot in home
2.write in terminal :
cd platform-tools
sudo install adb /usr/bin/adb
sudo install fastboot /usr/bin/fastboot

And you will be able to use the last update of adb/fastboot tools

One problem with your method is that you have considered adb and fastboot, but have you considered all the other components of platform-tools?

I think it would be quite a good exercise to check out what you have wound up with. The following will help to try to check if any duplicates remain from your novel method. I suggest you read this link to become familiar with what I propose.

I suggest you run:

echo $PATH
which -a adb
which -a fastboot

The output of the above will determine your next move. But I recommend you also check the version of adb and fastboot that you are going to be available. Version checking is a good way to determine that any command is actually available to you.

adb version
fastboot --version

1 Like

noax@noax:~$ echo $PATH
noax@noax:~$ which -a adb
noax@noax:~$ which -a fastboot
noax@noax:~$ adb version
Android Debug Bridge version 1.0.41
Version 32.0.0-8006631
Installed as /usr/bin/adb
noax@noax:~$ fastboot --version
fastboot version 32.0.0-8006631
Installed as /usr/bin/fastboot

It was a good point of what to do with the other files.

Ok, so what to do next then?

What I did has help me to use adb and fastboot recognize the phone again. While I had the platform-tools extracted and copy paste the line in the bashrc, it was keeping saying in the terminal that was not such a file or directory in usr/bin

So we see duplicates in /usr/bin/ and /bin/. Notice that the usr/bin commands are taking preference. I wonder, what is the source of /bin/adb and /bin/fastboot?

what to do next then?

My reply would have to include that imho the instuctions we are using should include a sentence to say something like this.

If you have no platform-tools on your Linux machine go ahead and provide them as follows.

If platform-tools already exist on your machine you will need to consider if you are sufficiently expert to run two sets of identical commands.

If you don’t want to be compromised by duplicates please read your distribution’s instructions and fully uninstall the system platform-tools or android-tools as appropriate, before you start this process.

I think you will have learned quite a lot in this process. For the safety of any phones you are about to connect I would recommend you seriously consider undoing all you did and try to get /e/ method right, so that all platform-tools components are from the “same set”.

For interest you might check

/bin/adb version
/bin/fastboot --version
1 Like

noax@noax:~$ /bin/adb version
Android Debug Bridge version 1.0.41
Version 32.0.0-8006631
Installed as /usr/bin/adb
noax@noax:~$ /bin/fastboot --version
fastboot version 32.0.0-8006631
Installed as /usr/bin/fastboot

Seems that comes from the same platform-tools

I am in Ubuntu and I have apt unistall the packeage of Ubuntu.

How to undo all of it right?

First point first! Please can you try

cd /bin
./adb version
./fastboot --version

I am not a Ubuntu user, I am aware they do it different from Debian, so I am sorry but I cannot help much on the Ubuntu system tools.

1 Like

noax@noax:~$ cd /bin
noax@noax:/bin$ ./adb version
Android Debug Bridge version 1.0.41
Version 32.0.0-8006631
Installed as /usr/bin/adb
noax@noax:/bin$ ./fastboot --version
fastboot version 32.0.0-8006631
Installed as /usr/bin/fastboot

Good, so if you now use a file manager and look in /bin do you see that adb and fastboot there are in fact symbolic links to /usr/bin? If you confirm that you will know you do not seem to have old “system” versions left behind.

How do you propose to undo
sudo install adb /usr/bin/adb
sudo install fastboot /usr/bin/fastboot
from Post #13 ?

1 Like