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 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 SHIFT6mq specific topic on our community forum.

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

Caution: The axolotl comes with an anti-rollback feature. Google Android anti-roll back feature is supposedly a way to ensure you are running the latest software version, including the latest security patches.

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 information

To 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 : T community (Security patch: 2024-10-05)

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.

  1. Enable OEM unlock in the Developer options under device Settings, if present.

  2. Connect your device to your PC via USB.

  3. 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. Release when boot logo appears.
  4. 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.

  5. Now type the following command to unlock the bootloader:

     fastboot flashing unlock

  6. If the device doesn’t automatically reboot, reboot it. It should now be unlocked.

  7. Since the device resets completely, you will need to re-enable USB debugging to continue.

Installing /e/OS

Tip: For Windows users, we advise to use Git Bash. For more info about Downloads and Installation see Official Documentation
Caution: axolotl comes with an anti-rollback feature. Please read the paragraph marked Caution in Requirements section of this guide, before you proceed to install /e/OS on axolotl.

  1. Unzip the archive

     unzip <fileyoudownloaded>

    In the command above, replace <fileyoudownloaded> with path of the downloaded archive.

    Alternatively, you can unzip the archive using a File Manager/File Explorer.

  2. Confirm that extracted directory contains following content:

    • 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_axolotl_factory.sh - The installer script.

  3. Boot into bootloader/fastboot mode.

    • Power OFF the device.
    • Hold Power + Volume Down button combo simultaneously.

  4. Run the installer script on Terminal(Linux) or on Git Bash UI(Windows).

    • Make sure you are in the current directory which contains the flash_axolotl_factory.sh file.
    • Linux
      • Right click -> Open terminal here
    • Windows
      • Right click -> Git Bash here
    • Execute the following command: 
        chmod +x flash_axolotl_factory.sh && ./flash_axolotl_factory.sh

    The script will flash all required files and will wait for input at the last step. Proceed to locking the bootloader.

Locking the Bootloader

Caution: axolotl comes with an anti-rollback feature. Please read the paragraph marked Caution in Requirements section of this guide, before you proceed to install /e/OS on axolotl.

Once you have completed the above steps and before rebooting you can lock your Bootloader.

  1. Download the avb custom key
  2. Erase the previous key fastboot erase avb_custom_key
  3. Flash the new key previously downloaded fastboot flash avb_custom_key avb_murena_rsa4096.bin
  4. Lock critical partition with the following command
    • fastboot flashing lock_critical
    • Approve with Volume + then power
  5. Reboot your device into bootloader, and plug it to your computer
    • Power OFF the device.
    • Hold Power + Volume Down button combo simultaneously.
  6. Lock the device with the following command
    • fastboot flashing lock
    • Approve with Volume + then power
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 SHIFT6mq specific topic on our community forum.

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