Install /e/OS on a Murena Murena One - “one”

The instructions in this guide will assist you to install /e/OS on your one. Please read through the instructions at least once before actually following them, so as to avoid any problems later.

It is important that you know that downgrading Smartphones on OS versions greater than the /e/OS OS version you plan to install, can cause instability or at worst brick some devices. We recommend that you check your current OS version, before attempting the installation.

It is advisable to flash your device only if you know what you are doing and are ok taking the associated risk. All /e/OS builds are provided as best effort, without any guarantee. The /e/OS project and its project members deny any and all responsibility about the consequences of using /e/OS software and or /e/OS services.

Requirements

If required take a backup of all important data from your phone on an external storage device before proceeding.
Do not take a backup on the same device as some of these actions will format the device and delete the backup.
Ensure your phone is charged more than 50%
Check that adb and fastboot are enabled on your PC. If not you can find the setup instructions here
Download all the files and images mentioned in the download section below before starting the installation
Make sure you have a working data cable to connect your device to the PC. There are cables which are only for charging and do not transfer data.
Enable USB debugging on your device. You can find the instructions here
Make sure that your model is listed in the Smartphone Selector. Check the model supported. Where available, information on the model supported should show as a pop-up when you hover the cursor on the Device name. The model number supported should be the exact same.
Boot your device with the stock OS at least once and check every functionality.

Warning: Make sure that you can send and receive SMS and place and receive calls (also via WiFi and LTE, if available), otherwise it will not work on /e/OS as well. Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.

Please share your experience , suggest tips or changes to this install guide documentation by visiting the Murena One specific topic on our community forum.

To report issues in /e/OS please refer this guide

Downloads for one

/e/OS build : S stable

To understand the difference between /e/OS builds check this guide

Warning: Please note some of the above links can lead to external sites

Unlocking the bootloader

Tip: The steps given below only need to be run once per device.

Warning: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or an online drive

Warning: Some vendors/manufacturers prevent the bootloader from being unlocked. Depending on where your device was acquired you may or may not be able to unlock the bootloader. To verify if your device is compatible please check the devices list.

Enable OEM unlock in the Developer options under device Settings, if present.
Connect your device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
```
 adb reboot bootloader
```
You can also boot into fastboot mode via a key combination:
- With the device powered off
- hold Volume Up + Power to open the menu. Use Volume Up to navigate and Volume Down to select. Select Fastboot Mode
Once the device is in fastboot mode, verify your PC finds it by typing:
```
 fastboot devices
```
Tip: If you see no permissions fastboot while on Linux or macOS, try running fastboot as root.
Now type the following command to unlock the bootloader:
```
 fastboot flashing unlock_critical
```
If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.

Installing /e/OS

Installing /e/OS using IMG or image file

Boot your Murena One in bootloader mode, and plug it to your computer
On your computer, download the zip file from the link provided above. Unzip the folder and browse into it
Flash /e/OS with the following commands:

fastboot erase userdata
fastboot format md_udc

fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash cam_vpu1 cam_vpu1.img
fastboot flash cam_vpu2 cam_vpu2.img
fastboot flash cam_vpu3 cam_vpu3.img
fastboot flash dtbo dtbo.img
fastboot flash gz1 gz.img
fastboot flash gz2 gz.img
fastboot flash lk2 lk.img
fastboot flash lk lk.img
fastboot flash logo logo.bin
fastboot flash md1img md1img.img
fastboot flash preloader preloader_g1970upt_v2_gk_p60c_oj_r.bin
fastboot flash recovery recovery.img
fastboot flash scp2 scp.img
fastboot flash scp1 scp.img
fastboot flash spmfw spmfw.img
fastboot flash sspm_2 sspm.img
fastboot flash sspm_1 sspm.img
fastboot flash super super.img
fastboot flash tee2 tee.img
fastboot flash tee1 tee.img
fastboot flash teksunhw teksunhw.bin
fastboot flash userdata userdata.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta vbmeta.img

fastboot reboot

Success: Congratulations !! Your phone should now be booting into /e/OS !!

To find some troubleshooting tips… click here

adb

Getting a Total xFer ':' 0.01x message - Try to upload the /e/OS to internal storage and retry to install
adb ':' sideload connection failed ':' insufficient permissions for device error - Try to execute the commands adb kill-server and adb start-server and retry
Running adb shell twrp install /sdcard/</e/OS zip package> raise non-existent directory error - Try to check solution here
Getting an insufficient permissions error - Try the solution given here
When running "adb devices" in bash a device is shown as "unauthorized" - Try the solution given here

TWRP

Errors while running TWRP version 3.4.x.x or above - Try downloading and using a previous TWRP version.. below 3.4.x.x
In TWRP if this error shows up failed to mount /preload - Try in TWRP wipe screen in advanced menu select preload and swipe to wipe
/cache/recovery/xxx -> no such file or directory error while flashing a ROM - On PC run adb shell in the console now create a folder called recovery for e.g. here the devicecode name is violet "violet :/cache# mkdir recovery"

Connectivity

Trying to troubleshoot mobile connectivity issues - Read this guide

Please share your experience , suggest tips or changes to this install guide documentation by visiting the Murena One specific topic on our community forum.

To report issues in /e/OS please refer this guide