Installation of e/OS on CMF Phone 1

[eguy]

thank you @aibd

and thank you also @Manoj for reopening this thread.

I have had a couple of days of resting. I’m looking at @piero s link as suggested by you both.

this part has me somewhat concerned:

@piero

It must be OLDER than the “android Security Patch Level” included in the /e/ build you want to install, otherwise you risk to change your device into Brick.

and

@piero

you will find this information about /e/OS build on the install instructions page for you device if your device is supported by /e/OS

Where can I find information about /e/OS build date, please? I have looked but can not find anything.

I noted to make sure there is no lock pin on my CMF P1.

Regarding ADB, sometimes my device is picked up in the terminal readout, but not always.

The phone does go into fastboot mode via terminal command.

but, as previously stated, when it comes to ‘connect’, i get a pop up read out telling me no device connected. It’s beyond me.

I did get connect a couple of times earlier on while trying. Downloaded (using the web install method) the file which took a very long time but then it is as if everything froze or went to sleep or on holidays! I did wait hours for something to start doing. So close but…. frustration.

I really like e/OS and think everything everybody does to provided us with it is super fantastic, so please understand (all who read) that i am not faulting or complaining.

I had good installs on previous model phones. Only changing due to Network upgrades that rendered my phone no longer permitted to be connected. (needed a new one anyway)

I shall persevere and plod on.

any and all help and directions gratefully received.

Peace

[eguy]

me again

I wonder if because I am trying the Official Build could be the problem?

I re-read everything about the community and official builds and it appears that maybe I should have been trying the Community Build? Any thoughts?

Peace

[aibd]

Firstly, you are not going to relock the bootloader after install, so you do not be concerned about dates of Android SPL.

Where there is a choice between community and official … official is likely to remain stable (might lag in providing an upgrade of Android version to a15 in times ahead) … community might get upgraded sooner.

In the actual install there is no expected difference.

Once install has actually started please don’t flip flop between the two.

Before moving to install … I suggested

@aibd

Did you work out the use of

please can you run those commands and show the output.

Before that, perhaps look at the whole USB chain. It has been reported that certain USB will not carry fastboot commands. You will need a good quality (full capacity) data cable, so not a thin, skinny cable. Avoid USB hubs including any USB hub that might be hidden in the PC / laptop; for predictably good results check (if necessary with a manual) that you are connecting to a USB-2 port soldered to the motherboard.

[piero]

The web installer cannot work on this device because it try to use the recovery method when the provided files are designed to be used by the install script method…

You can manually success though recovery but you will need guidance and download the OTA file.

You can manually success following the easier and documented install script method.

[eguy]

thank you for your patience. I haven’t got there yet due to personal things as much as i would like to.

I found something interesting a couple of nights ago, while grazing in the world wide wilderness of the internet.

I was looking at different distros for linux in case there was a better one i could install and use for this install. I saw one selection was for mobile distros and had a look out of interest. Murena was top of the list. One of the distros I looked into was

Nothing CMF Phone 1 (nothing-tetris) - postmarketOS Wiki

and if you scroll down to ‘Device quirks’

“ Fastboot appears to not work properly if the device is plugged into the host when entering fastboot mode. In this case, any fastboot command will halt seemingly forever and without action. A command can still be executed by unplugging the device, issuing the command, and then reconnecting the cable; or simply by rebooting to fastboot again without a cable connected. “

I won’t get much done tonight re my install but wanted to share this info as it may be useful for me and others who have the same problem with the CMF phone1 and i thought that both @piero and @aibd would find it interesting as you are always helping community folk so much.

peace

[branga]

I installed e OS on my CMF phone couple of months back. Initially i also faced issues since i use mac and the commands were different. I took a help of AI, and sent screenshot of my errors i face and AI guided me one by one steps and finally in 2 hours i was able to succussfully boot e OS on my phone.

[piero]

@piero

You can manually success though recovery but you will need guidance and download the OTA file.

You can manually success following the easier and documented install script method

I am ready to share instructions and links.

[eguy]

@aibd

@aibd

Did you work out the use of

please can you run those commands and show the output.

./adb reboot bootloader

• daemon not running; starting now at tcp:5037
• daemon started successfully
  error: device unauthorized.
  This adb server’s $ADB_VENDOR_KEYS is not set
  Try ‘adb kill-server’ if that seems wrong.
  Otherwise check for a confirmation dialog on your device.

@aibd & @piero I have, however, manually enabled USB debugging and allowed OEM unlocking through Developer Options.

Next:

./fastboot flashing unlock
< waiting for any device >

and

$ ./adb devices
List of devices attached

no devices come up this time.

xxxx@antix112:~
$ cd ~/platform-tools
xxxx@antix112:~/platform-tools
$ ./fastboot devices
xxxx@antix112:~/platform-tools
$ ./adb devices
List of devices attached

xxxx@antix112:~/platform-tools
$

Might try via the Install /e/OS on a Nothing Nothing CMF Phone 1 - “tetris”

any thoughts, suggestions, instructions before i proceed?

peace

[aibd]

@eguy

manually enabled USB debugging and allowed OEM

In a working phone Unauthorised can crop up due to the user missing this notification

So be sure to pull down the Notifications, and tap on the reference to USB.

The support pages are:

• Enable USB Debugging and OEM Unlock
• Fix unauthorized device error in adb
  • It is this second link which covers your error.

@eguy

Might try via the Install /e/OS on a Nothing Nothing CMF Phone 1 - “tetris”

All of my advice since Post #10 has favoured using the regular install page and not the eosinstaller.

[eguy]

@aibd thank you

yes, regarding debugging,

after hunting around and trying to get everything in order, including some java stuff, I saw here Installing ADB on Linux: A Comprehensive Guide — linuxvox.com

• Revoke USB debugging authorizations: On the Android device, go to Settings > Developer options and revoke USB debugging authorizations. Then, reconnect the device and accept the authorization request.

did that and bingo:

$ adb devices
List of devices attached
0011334AT003017 device

regarding your advice, there was also looking at and trying [HOWTO] a Clear Guide to install "IMG-e-builds" when /e/ web installer fails

I have tried your advice

@aibd

All of my advice since Post #10 has favoured using the regular install page and not the eosinstaller.

a few times and am about to embark on it again now the device is recognized. I very much value your advice. As you have probably worked out (?) i seem to be the problem along with my phone. Perhaps also the OS I’m running needing a few extra bits added, like the java stuff? Don’t know, but thank you for your patience and help. I am really keen to get e/OS on my new phone.

after 1:00 am again.

peace

[eguy]

now I reach here:

eguy@antix112:~
$ adb reboot bootloader
eguy@antix112:~
$ fastboot flashing unlock
< waiting for any device >

how long does one wait?

reboot bootloader put phone into FASTBOOT MODE

[aibd]

Don’t wait. The error says the “phone in fastboot” is not seen.

So you need to first resolve the response to

fastboot devices

when the phone is in Fastboot mode aka Bootloader

So it might be a USB port or cable issue, avoid USB hubs including hidden in PC / laptop. Try to use a USB 2 port soldered to the motherboard. It is common that adb commands go though a USB chain which does not support fastboot at a hardware level.

[eguy]

eguy@antix112:~
$ fastboot devices
no permissions (missing udev rules? user is in the plugdev group); see [http://developer.android.com/tools/device.html\] fastboot

[eguy]

Hi @aibd

I followed your advice which somehow i missed earlier

Installation of e/OS on CMF Phone 1

In a working phone Unauthorised can crop up due to the user missing this notification [Unauthoriseddebugging] So be sure to pull down the Notifications, and tap on the reference to USB. The support pages are: Enable USB Debugging and OEM Unlock Fix unauthorized device error in adb It is this second link which covers your error. All of my advice since Post #10 has favoured using the regular install page and not the eosinstaller.

and another bingo:

@aibd

Fix unauthorized device error in adb

• It is this second link which covers your error.

eguy@antix112:~
$ adb devices
List of devices attached
0011334AT003017 device

thank you

it’s 2;45 am

time to sleep a while

we’ll get there!

peace

[aibd]

@eguy

no permissions (missing udev rules? user is in the plugdev group)

Easy fix

Run your fastboot commands as sudo … so

sudo fastboot devices

---

Or if you prefer

The Ubuntu (adapt if necessary) fix for this appears on this page Android Studio guide.

1. Run this command in a terminal

sudo usermod -aG plugdev $LOGNAME

then

sudo apt-get install android-sdk-platform-tools-common

Hopefully this is enough. Logout / login or restart the PC. Now try

fastboot devices

Level 2

If a similar “Insufficient permissions” error should still occur you can now follow this guide Fix Insufficient permissions error in Linux.

The guide takes the example of the Gigaset GS290 device – the important bit is to create a new 51-android.rules based on the output of the lsusb command.

[eguy]

eguy@antix112:~
$ id
uid=1000(eguy) gid=1000(bear1) groups=1000(eguy),7(lp),20(dialout),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),106(netdev)

interestingly…

found here: linux drivers fastboot devices at DuckDuckGo

To use Fastboot effectively on Linux, proper drivers and configurations are necessary.

Installing Fastboot on Linux

1. Install Android Tools: Most Linux distributions include Fastboot in their package repositories. You can install it using the following commands:

Distribution	Command
Ubuntu	sudo apt install adb fastboot
Fedora	sudo dnf install android-tools

used Ubuntu command and Terminal readout (in part) :

The following NEW packages will be installed:
android-libsparse android-libziparchive fastboot
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 222 kB of archives.
After this operation, 718 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

maybe i was short a couple? I don’t pretend to understand much about these things.

bingo…

eguy@antix112:~
$ adb reboot bootloader
eguy@antix112:~
$ fastboot devices
0011334AT003017 fastboot
eguy@antix112:~
$

eguy@antix112:~
$ fastboot flashing unlock
OKAY [ 5.024s]
Finished. Total time: 5.024s

eguy@antix112:~
$ fastboot flashing unlock_critical
OKAY [ 5.024s]
Finished. Total time: 5.024s

eguy@antix112:~
$ fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.051s

[eguy]

but!!!

now I get this:

eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ chmod +x flash_tetris_factory.sh && ./flash_tetris_factory.sh
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)…
INFO: One CMF Phone 1 in fastboot mode found (serial number: 0011334AT003017).
Info: Your phone is in regular bootloader mode.
Error: Your device’s bootloader is still locked.
Please follow the instructions to unlock the bootloader!
Error: Your phone is not ready for flashing yet (see above), aborting…

and now, back to this:

eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ adb reboot bootloader
error: no devices/emulators found
eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ fastboot flashing unlock
< waiting for any device >

time to go back to square one and find the right actions to rectify it.

@aibd I know you have told me so I shall have to have a look.

ho hum

peace

p.s. I did quickly run commands to check

eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ fastboot flashing unlock
OKAY [ 5.021s]
Finished. Total time: 5.021s

and

eguy@antix112:~/Downloads/IMG-e-3.2-a14-20251022539005-official-tetris
$ fastboot flashing unlock_critical
OKAY [ 5.021s]
Finished. Total time: 5.021s

prior to all going pear shaped, after the initial attempt to do the chmod command.

[aibd]

Hmmm you followed a 2016 guide but you have a significantly modern phone.

This is not the recommended procedure from our documentation. [1]

Please assume your phone has survived this onslaught and only send commands to collect information from the phone please do not proceed with the install.

Please move into the directory or directories where you were previously working and give the output of

fastboot --version
./fastboot --version
pwd

[1] Installing adb and fastboot on a Linux PC

Caution: The default adb installation on OS like Ubuntu can be outdated and can cause errors. We would recommend that linux distribution users ensure they use the installation process given here.

The above commands will hope to untangle this situation.