Install /e/OS on a SHIFT SHIFT6mq - “axolotl”
The instructions in this guide will assist you to install /e/OS on your axolotl. 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 adbandfastbootare 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.
Please share your experience , suggest tips or changes to this install guide documentation by visiting the SHIFT6mq specific topic on our community forum.
To report issues in /e/OS please refer this guide
If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device. Click on
Details below for detailed informationTo check the security patch level on your phone with a locked bootloader, prior to installing /e/OS, open your phone
Settings » About Phone » Android Version » Android Security Patch Level.Then compare it against the level of the security patch on the /e/OS build as visible in the Downloads for axolotl section below.
The following values control whether anti-rollback features are triggered on axolotl:
* Rollback protection errors trigger if you install an update whose version number is
LESS than the rollback index’s value stored on device.
* The value of rollback index is
UPDATED to match ro.build.version.security_patch’s value of the currently installed version, but only if the bootloader is LOCKED.
* The value of rollback index is
NOT dependent on the currently installed ANDROID VERSION.
* The value of rollback index can
NEVER be DOWNGRADED.
* Rollback protection errors are
FATAL when the bootloader is LOCKED.
* Rollback protection errors are
IGNORED when the bootloader is UNLOCKED.
Here are some examples to help you understand how anti-rollback features work:
Example 1
* Your axolotl with Google Android has a Security Patch Level saying June 5, 2022
* The /e/OS build available says: /e/OS build : R official (Security patch: 2022-05-05)
* In this example, the /e/OS build has an older Security Patch level than the origin, so the anti-roll back protection will trigger, and you will brick your phone
Example 2
* Your axolotl with Google Android has a Security Patch Level saying June 5, 2022.
* The /e/OS build available says: /e/OS build : R official (Security patch: 2022-06-05)
* In this example, the /e/OS build has the same Security Patch level than the origin, so the anti-roll back protection will pass, and you will be able to install /e/OS with no issues.
Example 3
* Your axolotl runs Google Android -R while /e/OS is now available based on AOSP -S.
* Your axolotl with Google Android has a Security Patch Level saying 2022-10-03 or October 3rd, 2022.
* The /e/OS build available says: /e/OS build : S official (Security patch: 2022-06-05)
* In this example, the /e/OS build has an older Security Patch level than the origin, so the anti-roll back protection will trigger, even if the /e/OS version runs on a more recent version of AOSP. In this example, you will brick your phone.
Downloads for axolotl
- /e/OS build : A15 community (Security patch: 2025-10-01)
To understand the difference between /e/OS builds check this guide
Unlocking the bootloader
- 
    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 bootloaderYou can also boot into fastboot mode via a key combination: - With the device powered off
- hold Volume Up + Power.
 
- Once the device is in fastboot mode, verify your PC finds it by typing:
    fastboot devicesTip: If you seeno permissions fastbootwhile on Linux or macOS, try runningfastbootas root.
- 
    Now type the following command to unlock the bootloader: fastboot flashing unlock
- 
    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
Let’s proceed with the installation:
- 
    Unzip the file you downloaded from the link in the Downloads for axolotlsection 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-x86directory - which contains linux tools including fastboot and adb
- bin-msysdirectory - which contains Windows tools including fastboot and adb
- .imgfiles - The- .imgfiles that are to be flashed onto the device.
- flash_axolotl_factory.sh- The installer script.
 
- 
    Next boot your axolotl 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 or in Git Bash UI if the desktop OS is Windows. - Make sure you are in the current directory which contains the flash_axolotl_factory.shfile.
- 
        To execute the chmodcommand as suggested in the next step you may require root orsudoprivileges.
- Linux
        - Right click -> Open terminal here
- Execute the following command which makes the file executable and starts the installation process
 chmod +x flash_axolotl_factory.sh && ./flash_axolotl_factory.sh
- Windows
        - Right click -> Git Bash here
- Execute the following command which makes the file executable and starts the installation process
 chmod +x flash_axolotl_factory.sh && ./flash_axolotl_factory.sh
 
- Make sure you are in the current directory which contains the 
- After installing all the required files the device will reboot.
To find some troubleshooting tips… click here
adb
- Getting a  Total xFer ':' 0.01xmessage - Try to upload the /e/OS to internal storage and retry to install
- adb ':' sideload connection failed ':' insufficient permissions for deviceerror - Try to execute the commands- adb kill-serverand- adb start-serverand retry
- Running adb shell twrp install /sdcard/</e/OS zip package>raise non-existent directory error - Try to check solution here
- Getting an insufficient permissionserror - 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 TWRPwipescreen in advanced menu selectpreloadandswipe to wipe
- /cache/recovery/xxx -> no such file or directoryerror while flashing a ROM - On PC run- adb shellin 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 SHIFT6mq specific topic on our community forum.
To report issues in /e/OS please refer this guide