eguy@antix112:~
$ fastboot --version
./fastboot --version
pwd
fastboot version 29.0.6-debian
Installed as /usr/lib/android-sdk/platform-tools/fastboot
bash: ./fastboot: No such file or directory
/home/eguy
will procede with all that again
Something of a guess but 29.0.6 (February 2020) comes from a period where ADB was evolving almost monthly, so it is possible that this is the cause of odd problems. We also need to bear in mind that your install instructions tell you to work in a very specific directory.
You previously indicate
~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
but now /home/eguy
This is just a question to collect facts ⦠did you follow the instruction from Requirements in your install page:
Check that
adbandfastbootare enabled on your PC. If not you can find the setup instructions here
Thanks @piero below ⦠you did say
My comments (before I had coffee) on version are only about ācomplicationsā.
What you may have missed from
Install /e/OS on a Nothing Nothing CMF Phone 1 - ātetrisā
or
[HOWTO] a Clear Guide to install "IMG-e-builds" when /e/ web installer fails
is :
- Ask for unlock with
fastboot flashing unlock- Approve with volume +
i have followed the install instuctions more than a few times. Only letting you know so that you donāt think i am completely stupid - which is how i feel i must be because something isnāt working for me.
if itās not one thing, itās another. I was making progess, again, and suddenly the power went out for about 30 seconds throughout the house and i lost everything! Start again, somewhere.
I went to platform tools directory on terminal (linux) got adb devices:
$ ./adb devices
- daemon not running; starting now at tcp:5037
- daemon started successfully
List of devices attached
0011334AT003017 device
but when trying fastboot devices only get:
eguy@antix112:~/platform-tools
$ ./fastboot devices
now where? i am forgetting having been around in circles so many times.
SO I put in fasboot devices (trying it):
$ fastboot devices
bash: fastboot: command not found
and yes, i have set the path in .bashrc
thank you for your continued patience
EDIT: I entered fastboot mode on phone with power and up volume buttons (which is not in the instructions on the install page that i can see:
and now get:
$ ./fastboot devices
0011334AT003017 fastboot
back to:
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ sudo chmod +x flash_tetris_factory.sh && ./flash_tetris_factory.sh
[sudo] password for eguy:
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)ā¦
@aibd Iāll re-check the Requirements as you suggested in case i overlooked anything.
Understood ⦠but I think you go wrong by accelerating ahead before you know the last step was a success.
Just so you know
This is fine it is just the same as the instruction
Reboot on fastboot by running the command in the PC console
adb reboot bootloader
You probably have not. You just need to tick off the items complete, then go one step at a time. It looks from here your only error (but we are guessing because you did not confirm) would be if you did the unlock commands one after the other without.
back to platform-tools directory first?
$ adb reboot bootloader
bash: adb: command not found
what is the adb console?
Tip: All the console commands are run on an adb enabled PC and in the
adbconsole.
I imagine that you need to plug phone into PC/computer here?
-
- Boot the device
- Enable Developer options
- From developer options, enable OEM unlock
- Reboot on fastboot by running the command in the PC console
adb reboot bootloader
that point is missing for people who donāt know. Reboot on fastboot⦠means? Power off first, connect to computer then run command adb reboot bootloader ?
Slightly unhelpful but he is saying a Terminal where you already established that ADB, that is abd and fastboot are already working correctly and you understand if and why you might use./.
You cannot be experimenting with this stuff while you are throwing commands at the phone. ![]()
- to 3. being on phone tasks do not require connection to PC.
Connect to PC to throw commands at it.
I get stuck so try to find out why. I need to wait for step by step instruction, perhaps?
I mentioned about
because it isnāt clear to simple folk who might not understand. I only guess at some of these things. Others might too. But it seems something is not working as i seem to be taking a lot longer than average! Sorry.
Please read my last comments on previous post that i edited in.
Iāll not do ANYTHING until I hear back.
You could connect the phone in normal mode to the PC. Move to the directory
~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
run
adb --version
adb devices
Now manually boot the phone to Fastboot mode and run
fastboot --version
fastboot devices
Without drawing any conclusions from the above, please now perform the actions and run all four commands with a leading ./
Please give the whole Terminal output.
eguy@antix112:~
$ cd Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ adb --version
adb devices
bash: adb: command not found
bash: adb: command not found
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ fastboot --version
fastboot devices
bash: fastboot: command not found
bash: fastboot: command not found
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ ./adb --version
bash: ./adb: No such file or directory
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ ./adb devices
bash: ./adb: No such file or directory
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ ./fastboot --version
bash: ./fastboot: No such file or directory
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ ./fastboot devices
bash: ./fastboot: No such file or directory
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
This is not altogether a surprise, but it does tell us you were not successful in adding adb and fastboot in your $PATH.
I will take a break as there are āthings to doā right now, sorry.
30 minute later Edit. but it also tells us that the fastboot version 29.0.6-debian seen in Post #41 is now absent. Did you uninstall it?
try the same, but from the ~/ directory (same as /home/erguy)
try the same, but from the ~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux/ directory
try the same, but from the ~/Downloads/platform-tools/ directory
Please give the whole Terminal output.
.
explanation :
spoiler :
currently installed version is v 29.0
embeded into /e/ install .zip is v 33.0
in downloaded platform-tools is v 36.0
yes. I was looking for a more up to date version.
Perhaps I should re-install it?
Good to know. We advised not to use system installed; this fits with /e/ documentation.
I did however suggest in a previous post
sudo apt-get install android-sdk-platform-tools-common
This may now be missing. I suggest you run that command for best results in light of earlier fails.
eguy@antix112:~
$ adb --version
bash: adb: command not found
eguy@antix112:~
$ adb devices
bash: adb: command not found
eguy@antix112:~
$ cd /Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux/
bash: cd: /Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux/: No such file or directory
eguy@antix112:~
$ cd Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
$ adb --version
bash: adb: command not found
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
$ ./adb --version
bash: ./adb: No such file or directory
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
$ adb devices
bash: adb: command not found
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
$ fastboot --version
bash: fastboot: command not found
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
$ fastboot devices
bash: fastboot: command not found
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
$ ./fastboot --version
fastboot version 33.0.3-8952118
Installed as /home/eguy/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86/fastboot
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
$ ./fastboot devices
0011334AT003017 fastbooteguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris/bin-linux-x86
$ cd
eguy@antix112:~
$ cd platform-tools
eguy@antix112:~/platform-tools
$ adb --version
bash: adb: command not found
eguy@antix112:~/platform-tools
$ adb devices
bash: adb: command not found
eguy@antix112:~/platform-tools
$ ./adb --version
Android Debug Bridge version 1.0.41
Version 36.0.0-13206524
Installed as /home/eguy/platform-tools/adb
Running on Linux 6.1.105-antix.1-amd64-smp (x86_64)eguy@antix112:~/platform-tools
$ ./adb devices
List of devices attached
0011334AT003017 deviceeguy@antix112:~/platform-tools
$ fastboot --version
bash: fastboot: command not found
eguy@antix112:~/platform-tools
$ fastboot devices
bash: fastboot: command not found
eguy@antix112:~/platform-tools
$ ./fastboot --version
fastboot version 36.0.0-13206524
Installed as /home/eguy/platform-tools/fastboot
eguy@antix112:~/platform-tools
$ ./fastboot devices
0011334AT003017 fastboot
eguy@antix112:~/platform-tools
$
Thanks @aibd
was still installed ![]()
$ sudo apt-get install android-sdk-platform-tools-common
[sudo] password for eguy:
Reading package lists⦠Done
Building dependency tree⦠Done
Reading state information⦠Done
android-sdk-platform-tools-common is already the newest version (28.0.2+9)
Cool we can work with that. I have a couple of things to do during the afternoon, so I will tend to defer to @piero if he is available to help at this time.
Just to make life a little easier, please can you try to get platform-tools in your $PATH.
1 line in ~/.bashrc in your case I believe it should read
export PATH="$HOME/platform-tools:$PATH"
Please add that line. Logout / login or restart the PC and try
fastboot --version
adb --version
from your /home folder and show the whole output.
and not :
export PATH=ā$HOME/eguy/platform-tools:$PATHā ?