i tried to install the e Os on my phone via microsoft edge. The installation stopped at 22% and now the phone doesnt work. When i start it it just says its in the orange state and turn off after 5 seconds after saying OS not being verified Or custom OS. Dismiss after 5 seconds. Even when i try to hold up + Volume i cant reach another state.
Did i broke the phone??? 
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
hello @Marcosch, Welcome to the /e/ forum.
have a try with this instructions Install /e/OS on a Nothing Nothing CMF Phone 1 - “tetris”
Hey, thank you very much i am trying this but when it comes to work with the command prompt, I’m lost. I think i need technical support via video or a call or somebody who works this out with me.
There is even no problem if i have to drive to somebody with the phone. Europe is no problem 
ok. I arrived at installing the adb and fastboot on my pc but when i enter “adb device” in the command prompt, it shows me nothing. if it would detect an usb device it would show a number or something.
No you didn’t, orange state is normal if you use custom ROM like /e/OS. Nothing to worry too much.
You just have to copy paste…
Ist is volume up + power
hi. i managed somehow (10hours with chatgpt to get through the installation. I ended up with git hub and the final Installation command on the installation manual from e foundation. The result is, that git hub says, that everything worked well. BUT my phone stays in the orange state… Im tired… 
meanwhile i know enough about the orange state. I am not worried, even not stressed. i just want an answer to how i can manage that my phone will be usable and at best with e OS. Love to all
As far as I can see here:
https://doc.e.foundation/devices/tetris
Your device is not lockable.
Maybe change the title to lock bootloader then more people with the device might pitch in. When you habe installation issues it is usually the 5 same people helping but not having the device
thanks. What does that mean “not lockable”. Does i have to lock it to fix it?
somehow it works. Im in E OS now. but when i restart the phone the orange state comes back. I have to restart it several times and the n it goes somehow on.
AOSP devices are required to “Communicate Verified Boot state to users”
and this includes your warning
ORANGE: Warning screen for UNLOCKED devices
… so you are always going to see the warning at boot; more fully explained here Flujo de inicio | Android Open Source Project.
The warning text for an unlocked bootloader is super misleading. If you didn’t know better you’d think your device is highly open to attack. That’s simply not true. The risk of compromise with an unlocked bootloader is so minimal it’s almost not worth a mention.
It’s like they’re trying to scare the user into using what they want, their proprietary system that broadcasts all your personal data to the world. That’s way worse than an unlocked bootloader with a de-googled operating system like /e/os.
Hi there. I had the same problem with my new cfm. I spend hours on trying e os and then other os and nothing seemed to work. I just got stuck in the orange state loop. At the and i installed e OS again and didnt expect any solution to my problem… Buuuuuuuuuut in the orange state loop it is mentionned that the phone will shut down after 5 secondes. This message comes twice when you turn the phone on. By the second time it also sais, that you can push the power button to going forward. So when i did this after the installation the phone opens in e os after the 5 seconds and i screamed out loud because of happiness. if you have any question please ask me!! Have luck, have fun, have love!
Hello Everyone,
I end up here because, as you may already know, I fail into orange loop 
all the step above are the same, except that the phone does not propose to boot by pushing the power button…
I tried to install with auto installer on E/os website*
Any idea? I am desperate to have bricked my phone.
Hello @GitGit, Welcome to the /e/ forum.
Reading user’s feedback for some more than 4 month, → I don’t trust the “faill installer”
Install /e/OS on a Nothing Nothing CMF Phone 1 - “tetris”
If you still can boot in fastboot mode → your phone is not bricked…
thank you for your answer!
phone not bricked is a very good news!
Unless I missed something, I really used the auto installer from e/os webpage,
I will try to uninstall and reinstall ADB and other and try install again
Ok, after few hours, I managed to boot on e/os
If you face same situation after trying to install with that “easy” installer 
1-uninstall all adb drivers from win
2-update all drivers and install ADB and Fastboot ++ ( Release v1.1.1 · K3V1991/ADB-and-FastbootPlusPlus · GitHub)
3-connect your phone fastboot mode
4- Do the install classic way