/e/ OS Version Upgrade

Manually upgrade mata to R

Warning : Downgrading Smartphones already on Android Q or LineageOS 17.x to Pie or from Pie OS to Oreo or Nougat can cause instability or at worst brick some devices.

Tip: To suggest changes to this install guide documentation, please visit the Essential PH-1 specific topic on our community forum. To report issues in the build please refer this guide

Basic Requirements

  • adb and fastbooot should be setup and working on your PC

    To set up adb follow details provided here

  • adb and fastboot need root rights in Linux and administrator rights in Windows.

    In Linux prepend sudo to any adb or fastboot command For e.g. “sudo fastboot reboot” and in Windows start the command window as administrator.

Caution: Before following these instructions please ensure that the device is on the latest Android firmware available for your device. For example if available, before flashing /e/R install Stock Android 11, before /e/Q it should be Stock Android 10 or before /e/ Pie it should be Stock Android 9.

Warning:

  • Please note this upgrade build could not be tested as there were no device specific testers available.
  • Some devices may need a revert to stock ROM prior to upgrade.
  • To flash the stock ROM you would need to use a tool provided by your vendor
  • You may also need to download a recovery image built specifically for your device.

Download

  • Download Upgrade Build for the mata here

  • R (dev) (R)

  • Download TWRP

Download of TWRP is not required if you already have it running on your mata

Steps to Flash the Upgrade /e/OS ROM

  1. Open a command window and change into the directory where you downloaded the files

  2. Take a complete backup of your phone data
  3. Ensure your mata smartphone is fully charged
  4. Remove any pattern or PIN locks you may have set on your phone

    you can set these up after the OS has been successfully installed on your phone

  5. If you already have TWRP recovery installed on your device
    • skip steps 6 and 7
    • Go directly into TWRP recovery (step 9)
    • To do that reboot your device and during startup follow the steps as given here
    • With the device powered off, hold Volume Up + Power.
  6. To flash TWRP recovery
    • Reboot your device and press volume-down during startup.
    • This will bring the device into fastboot mode
  7. Flash the TWRP image in the fastboot mode by running below command in the PC
     fastboot flash recovery twrpimagename.img

    on some devices the below command may be required

     fastboot boot twrpimagename.img

    replace the twrpimagename.img with the name of the twrp image file name you downloaded previously the boot command will flash a temporary TWRP image on your smartphone

  8. Reboot the device via the command
    fastboot reboot

    and press volume-up while booting to go into TWRP recovery

  9. If your device is un-encrypted
    • Continue with installing the new build as given in step 13
  10. If your device is encrypted
    • Ensure you have taken a backup as proposed in step 2
    • Continue to step 11

  11. In TWRP wipe screen on your device click the format data button on the lower side to remove encryption

  12. Select the Wipe button and in the wipe screen select system + data + cache and swipe to wipe

  13. Sideload the /e/ .zip package

    • On the device, In TWRP select

    Advanced » ADB Sideload » then swipe to begin sideload

    • On the host machine, sideload the package by running the below command
       adb sideload /e/ OS image name.zip

      replace the /e/ OS image name.zip with the name of the /e/ OS zip file name, e.g. adb sideload e-0.7-p-2020011437643-test-FP2.zip

  14. Once the installation is successfully completed reboot system from the TWRP screen.

  15. Your mata should now be running the R version of /e/..enjoy !!!

Answers to some questions you may have on the process

Why do I need to manually upgrade the OS

  • The updater app does not support upgrades from one Android version to another. It will hide any update of a different version.
  • We are working on resolving this issue.
  • While this issue is resolved, users need to manually upgrade their OS.
  • Upgrading manually requires similar steps to installing /e/OS for the first time.