Nothing CMF-1 stuck in Recorevy mode during install /e/Os!

[Xela]

Hi all,

I’m trying to install /e/os on my new CMF-1 using Web interface.

Starting download the 4.4.2 to the phone, at the end the phone reboot en stay but whitout Murena .

To to conitue, I am using Gemini to help me , I install SDK Platform-Tools for Mac-OS .

Download 4.0 and Recovery on /e/OS builds

Next :

./fastboot flashing unlock → < waiting for any device > OKAY [ 5.025s] Finished. Total time: 5.032s

On CMF screen : Unlock the device successfully! Will return to fastboot in 3s".

Next : ./fastboot flash vendor_boot recovery.img Sending ‘vendor_boot_a’ (65536 KB) OKAY [ 1.440s] Writing ‘vendor_boot_a’ OKAY [ 0.209s] Finished. Total time: 1.653s

After this last step my CMF is in bootloop on Recovery Mode : Start , CMF Nothing in middle of screen , on left down : => Recovery mode (during 1 second), next very short (flash) white screen, and reboot en restart the loop .

I am waiting aboit 14 hours to use the battery en restart using commands Vol-Down + Power , and send command from Terminal : ./bin-darwin/fastboot flashing unlock_critical , but is impossible to go away from the loop , and CMF is not visible from my Mac…

Can someone help me ?

[piero]

[HOWTO] a Safe Guide to install "IMG-e-builds" even if the /e/ web installer fails

. [e] . because even well illustrated, the “web-installer” often don’t work, and because the install instructions provided by /e/ can be imbuvable for some new users and can lead to errors. . here is a safe guide to install /e/OS . we take the Fairphone 6 as example, but it is the same logical and quite the same process for all the devices that have : "IMG-e-xxxxxxxxxxx.zip" file on their download page, that contains an install script named like flash_FP6_factory.sh. . (non ex…

Install /e/OS on a Nothing - Nothing CMF Phone 1 - "tetris"

[ieder1]

Basically you are now at step 7 from ‘Unlocking the bootloader’ when you follow the /e/OS documentation as mentioned above by piero.

I guess the install script fails because you only sent the command fastboot flashing unlock but not followed by fastboot falshing unlock_critical.