Installation of e/OS on CMF Phone 1

/e/OS Devices Nothing
84

There has never been any Approve messages on my phone, if that is what you mean?

While I admit any user error on my part, willingly, I can’t understand why fastboot commands are not working, even though they did some time ago, as you noted. Thank you.

I can do a factory reset now if that is the next move? I haven’t done one recently. Might have before the info you mention from post#39

peace

EDIT should i do a quick downgrade first? I know you said last resort.

or do a factory rest and try it all again first?

I was looking at what I had on phone before factory rest and that is one thing I saw that will be deleted at reset. @aibd

85

To avoid Downgrade of Android version I think Factory reset would be useful now.

Thank you for the image showing confirmation that the phone is still locked.

This allows us to move on to the Unlock Instructions if you wish.

1 Like
86

Happy to do so. After I do a factory reset?

87

I think so, yes, significant is the confirmation that the device is locked.

1 Like
88

Device/phone factory reset.

Developer options all ticked.

ready for Unlock Instructions.

If you are able to post them I can tackle them tomorrow, all things being equal.

Must get shut-eye. Off to Cardiologist first thing in morning.

Peace and thank you

89

We all wish you good luck with that.

We have now seen confirmation that the phone is locked.

When you are ready the unlock instructions are

  • Boot to fastboot mode, make connection USB to PC, test fastboot connection with
fastboot devices
  • Ask for unlock with fastboot flashing unlock
  • Approve with volume +
  • Unlock critical with fastboot flashing unlock_critical
  • Approve with volume +
  • Reboot the device fastboot reboot
  • The device proceeds with a factory reset

We see here the advice

(You need to be quite fast {with pressing volume + } , otherwise phone goes back to normal fastboot mode without changing)

If in doubt volume + represents the Volume Up hardware button on the phone.

1 Like
90

thank you. All good in that department.

Now…

I got excited but for who-knows-why reason, i keep running into unauthorized!

Have been through the fix a few times:

but no improvement!

eguy@antix112:~
$ adb kill-server
eguy@antix112:~
$ adb devices

  • daemon not running; starting now at tcp:5037
  • daemon started successfully
    List of devices attached
    0011334AT003017 unauthorized

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

eguy@antix112:~
$ adb kill-server
eguy@antix112:~
$ adb devices

  • daemon not running; starting now at tcp:5037
  • daemon started successfully
    List of devices attached
    0011334AT003017 unauthorized

plus a couple more i didn’t include

Regarding

I did not realize all i had to do was press that button. I have been waiting and looking for an onscreen approval read out. No wonder I never got it happening.

Anyway, i can’t go there until i/we sort out the authorization thing.

Every time i get excited about getting there, something else goes wrong.

I did a factory reset. Maybe the tight, invasive and limiting gooogle settings, etc and/or Nothing settings on the phone are the problem. I had previously nuked as much goooogle stuff as possible and other privacy settings etc. But for now, the phone is fresh from factory reset.

thank you.

91

We ran into unauthorised before. It has occurred following Factory reset, the PC requires to be authorised. Please just treat it as Post #31 again.

This is the support page again Fix unauthorized device error in adb.

You say you tried already. It is written as a 7 stage job. Perhaps you should tick off each stage and ask if any stage is problematic.

I see that you did point #2 in the document already.

The popup mentioned as point # 6 is this one.

1000018380
1000018380641×367 29.2 KB

At point # 6 if you miss this notification, be sure to pull down the Notifications from top of phone screen, and tap on the reference to USB. Be sure to tap on “Always Allow”.

92

Hi @aibd

yes I have gone through each step a few times but I never got the pop up “Allways Allow” screen. Don’t know why. Did before when relevant.

Tried again, and after adb devices it popped up. Ticked and all good now.

$ adb devices
List of devices attached
0011334AT003017 device

so on to the next step from

thank you

1 Like
93

@aibd

@piero

Hi, to start with, I have tried this numerous times:

almost instantaneously, even same time as pressing enter on command in terminal, and also once before pressing it. But still no unlock, only blinking cursor. Perhaps I am too fast at pressong Volume down button?

I tried entering fastboot via phone volume up and power buttons. Same result. Here it shows entering fastboot mode via terminal to see if that made any difference:

$ adb reboot bootloader

  • daemon not running; starting now at tcp:5037
  • daemon started successfully
    eguy@antix112:~
    $ fastboot devices
    0011334AT003017 fastboot
    eguy@antix112:~
    $ fastboot flashing unlock

Is there a script or command that would/can bypass the volume down button process?

When on the manual fastboot method the readout said it was locked as per the picture i gave earlier.

Trying not to get frustrated.

I have followed every step given. I go slowly and make sure i don’t miss or skip any.

94

Yes perhaps. We do know that your phone has been more than a little reluctant to accept fastboot commands. But it is significant that you now get successful

fastboot devices

So we probably don’t want to go back over previous steps.

You might try giving a moment for the phone to process the fastboot command.

You might restart both devices for a fresh start.

(You might include

fastboot --version

as a reminder.)

1 Like
95

Please go ahead and exhaust the above suggestions.

As for what next if the above fails.

One might think that the original system had been compromised by previous errors.

Your link How to Downgrade Nothing Phone from Android 15 to Android 14 - TheDroidWin does not use fastboot commands so I think it will work.

Perhaps you will get familiar with the method and ask if necessary before you start.

1 Like
96

Hi again,

no luck until i sent the command with phone unplugged (but in fastboot mode) then plugging it in and a screen popped up with warning about it and choice to use volume up button.

eguy@antix112:~
$ fastboot flashing unlock
eguy@antix112:~
$ fastboot flashing unlock
< waiting for any device >
(bootloader) Start unlock flow

OKAY [ 3.517s]
Finished. Total time: 3.517s
eguy@antix112:~
$

to be continued/edited

again, with phone plugged in to pc, nothing but when send command, unplugged then plug in, same as before:

bear1@antix112:~
$ fastboot flashing unlock_critical
bear1@antix112:~
$ fastboot flashing unlock_critical
< waiting for any device >
(bootloader) Start unlock flow

OKAY [ 1.320s]
Finished. Total time: 1.320s
bear1@antix112:~
$

same with next command. no response until i unplug and send command and then plug back in.

Phone has rebooted.

eguy@antix112:~
$ fastboot reboot
Rebooting eguy@antix112:~
$ fastboot reboot
< waiting for any device >
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.051s
eguy@antix112:~
$

yippy do!

so, @aibd

what next, please Sir?

97

Praise be.

Let me just print the introduction for you to review. I guess you did this already.

Let’s proceed with the installation:

Unzip the file you downloaded from the link in the Downloads for tetris section above.

 `unzip <fileyoudownloaded>`

In the command given above, replace <fileyoudownloaded> with the name of the file you downloaded. You can unzip the file using a File Manager/File Explorer.

Confirm that the folder where you unzipped the files contains the following :

  • bin-linux-x86 directory - which contains linux tools including fastboot and adb
  • bin-msys directory - which contains Windows tools including fastboot and adb
    .img files - The .img files that are to be flashed onto the device.
    flash_tetris_factory.sh - The installer script.

Next boot your tetris into bootloader/fastboot mode using this key combination

  • With the device powered off
    hold Volume Up + Power.

Now we will run the installer script in a terminal on a Linux PC

Make sure you are in the current directory which contains the flash_tetris_factory.sh file.

To execute the chmod command as suggested in the next step you may require root or sudo privileges.

  • (End of prelimminary checks)

Execute the following command which makes the file executable and starts the installation process

chmod +x flash_tetris_factory.sh && ./flash_tetris_factory.sh
  • (After installing all the required files the device will reboot. Success.)
1 Like
98

@aibd

my very patient and much appreciated and super valued instructor,

please give yourself a hug and kiss from me!

what joy to see “murena” with the bouncing dot!!!

Thank you so very, very much.

my phone is now in ‘tetris’ mode.

what a relief. wow… I am so happy.

anyone reading this, don’t give up. It’s worth it. My situation is probably not the average and I am probably more fuddled and fumbling than most. Get e/OS on your phone. You’ll be glad you do.

Thank you again @aibd

and thank you also, @piero

I am so happy!!!

THANK YOU

blessings and peace

2 Likes
99

I’m also having troubles while trying to install /e/OS/ on a freshly bought Nothing CMF Phone 1 - “tetris” (orange colour).

Right now Nothing OS 2.6 (Android 14) is on the phone (which I just bought for the purpose of installing /e/OS on it and hence never even connected to the internet).

I tried installing via command line from Debian 13.2 and followed your instructions exactly as instructed!

Here a few of the results I got for trouble shooting purposes:

As the instruction commands I execute the following command as root: “chmod +x flash_tetris_factory.sh && ./flash_tetris_factory.sh”.

This is what I always get as output:

root@-debian-11:/media//**_128GB/Nothing_CMF_Phone_1_tetris/IMG-e-3.3-a14-20251210556409-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: 0011134AV000116).
Info: Your phone is in regular bootloader mode.
Sending ‘apusys_a’ (1160 KB)                       OKAY [  0.066s]
Writing ‘apusys_a’                                 OKAY [  0.007s]
Finished. Total time: 0.080s
Sending ‘apusys_b’ (1160 KB)                       OKAY [  0.072s]
Writing ‘apusys_b’                                 OKAY [  0.007s]
Finished. Total time: 0.086s
Sending ‘ccu_a’ (104 KB)                           OKAY [  0.008s]
Writing ‘ccu_a’                                    OKAY [  0.004s]
Finished. Total time: 0.019s
Sending ‘ccu_b’ (104 KB)                           OKAY [  0.009s]
Writing ‘ccu_b’                                    OKAY [  0.004s]
Finished. Total time: 0.020s
Sending ‘connsys_bt_a’ (1472 KB)                   OKAY [  0.087s]
Writing ‘connsys_bt_a’                             OKAY [  0.008s]
Finished. Total time: 0.102s
Sending ‘connsys_bt_b’ (1472 KB)                   OKAY [  0.084s]
Writing ‘connsys_bt_b’                             OKAY [  0.008s]
Finished. Total time: 0.100s
Sending ‘connsys_gnss_a’ (516 KB)                  OKAY [  0.030s]
Writing ‘connsys_gnss_a’                           OKAY [  0.005s]
Finished. Total time: 0.043s
Sending ‘connsys_gnss_b’ (516 KB)                  OKAY [  0.031s]
Writing ‘connsys_gnss_b’                           OKAY [  0.005s]
Finished. Total time: 0.043s
Sending ‘connsys_wifi_a’ (3088 KB)                 OKAY [  0.177s]
Writing ‘connsys_wifi_a’                           OKAY [  0.109s]
Finished. Total time: 0.293s
Sending ‘connsys_wifi_b’ (3088 KB)                 OKAY [  0.174s]
Writing ‘connsys_wifi_b’                           OKAY [  0.109s]
Finished. Total time: 0.291s
Sending ‘dpm_a’ (884 KB)                           OKAY [  0.054s]
Writing ‘dpm_a’                                    OKAY [  0.006s]
Finished. Total time: 0.067s
Sending ‘dpm_b’ (884 KB)                           OKAY [  0.052s]
Writing ‘dpm_b’                                    OKAY [  0.006s]
Finished. Total time: 0.065s
Sending ‘gpueb_a’ (520 KB)                         OKAY [  0.031s]
Writing ‘gpueb_a’                                  OKAY [  0.005s]
Finished. Total time: 0.043s
Sending ‘gpueb_b’ (520 KB)                         OKAY [  0.030s]
Writing ‘gpueb_b’                                  OKAY [  0.005s]
Finished. Total time: 0.042s
Sending ‘gz_a’ (1852 KB)                           OKAY [  0.109s]
Writing ‘gz_a’                                     OKAY [  0.009s]
Finished. Total time: 0.125s
Sending ‘gz_b’ (1852 KB)                           OKAY [  0.108s]
Writing ‘gz_b’                                     OKAY [  0.109s]
Finished. Total time: 0.224s
Sending ‘lk_a’ (3040 KB)                           OKAY [  0.174s]
Writing ‘lk_a’                                     OKAY [  0.109s]
Finished. Total time: 0.291s
Sending ‘lk_b’ (3040 KB)                           OKAY [  0.191s]
Writing ‘lk_b’                                     OKAY [  0.108s]
Finished. Total time: 0.306s
Sending ‘logo_a’ (4716 KB)                         OKAY [  0.300s]
Writing ‘logo_a’                                   OKAY [  0.109s]
Finished. Total time: 0.416s
Sending ‘logo_b’ (4716 KB)                         OKAY [  0.285s]
Writing ‘logo_b’                                   OKAY [  0.108s]
Finished. Total time: 0.400s
Sending ‘mcf_ota_a’ (29296 KB)                     OKAY [  1.730s]
Writing ‘mcf_ota_a’                                OKAY [  0.109s]
Finished. Total time: 1.845s
Sending ‘mcf_ota_b’ (29296 KB)                     OKAY [  1.833s]
Writing ‘mcf_ota_b’                                OKAY [  0.108s]
Finished. Total time: 1.949s
Sending ‘mcupm_a’ (700 KB)                         OKAY [  0.045s]
Writing ‘mcupm_a’                                  OKAY [  0.005s]
Finished. Total time: 0.057s
Sending ‘mcupm_b’ (700 KB)                         OKAY [  0.049s]
Writing ‘mcupm_b’                                  OKAY [  0.005s]
Finished. Total time: 0.061s
Sending ‘modem_a’ (85072 KB)                       OKAY [  5.279s]
Writing ‘modem_a’                                  FAILED (Status read failed (Protocol error))
fastboot: error: Command failed

ERROR: Could not flash the modem_a partition on device 0011134AV000116.

ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB-C)
ERROR: (cable until the fastboot menu appears.)

ERROR: Aborting now (press Enter to terminate).

After which I reboot the phone and start over again.
Even reapplying the following steps again won’t change the results:
Ask for unlock with fastboot flashing unlock
Approve with volume +
Unlock critical with fastboot flashing unlock_critical
Approve with volume +
Reboot the device fastboot reboot

What else should I do to fix the problem and successfully install /e/OS on my new Nothing CMF Phone 1?

100

at the moment, i see a thing to try first :

  • replace the fastboot binary in /IMG-e-3.3-a14-20251210556409-official-tetris/bin-linux-x86 folder by the latest version platform-tools for Linux
1 Like
101

Perhaps also significant that the script has made a lot of progress but failed at the largest partition encountered.

Be sure to run the script with very few other programs running.

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

Does the PC have plenty of RAM available.

CMF-Phone 1 Install script hangup
FP6, Trying To Install /e/os But Failed Again
102

Thanks @aibd and @piero for the help. I tried another USB-cable and now it worked seamlessly.

(The prior USB-cable worked for the installation of Custom-ROMS on multiple other devices without any problems before.)

2 Likes
Can´t install FP6 with installer
103

Great to hear that you got /e/ installed.

It is good for others to see this – at first sight one would imagine that a working cable is a working cable, but these fastboot commands must have large amounts of data to transmit and verify at high speed.

2 Likes