Install /e/ on a Samsung Galaxy Tab S5e (LTE) - “gts4lv” (beta)

Tip: Please read through the instructions at least once before actually following them, so as to avoid any problems later.
Warning: Downgrading Smartphones already on Android Q or LineageOS 17.x to Pie or other OS can cause instability or at worst brick some devices
Caution: Flash your device only if you know what you are doing and are OK taking the associated risk. All builds are provided as best effort, without any guarantee. The /e/ project and its project members deny any and all responsibility about the consequences of using /e/ software and or /e/ services.
Tip: Installing a custom recovery or unlocking the bootloader will erase all data on your device! Take a backup of your data before proceeding!!

Requirements

  • Take a backup of all important data on your phone before proceeding.
  • A guide on backing up with TWRP is available here
  • 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
Caution: Before following these instructions please ensure that the device is on the latest Android Stock firmware same as the version of the /e/OS you are planning to install. This can be done by checking for OTA updates available in the Updater. If available run them before installing /e/OS

Downloads for the gts4lv

  • Custom recovery (not required if you already have it running on your phone)

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

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

Pre-Install Instructions

Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
  1. Connect the device to a Wi-Fi network.

  2. Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu

    • From within the Developer options menu, enable OEM unlock.
  3. Download this VBMeta image .tar file.

  4. Power off the device, and boot it into download mode:

    • plug in the device while holding Volume up + Volume Down + Power.
    • Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”, and insert the USB cable into the device.
  5. Download and install the necessary drivers.

    • Download the newest Samsung drivers from here. You will need to create a Samsung account and login to download them.
    • Install SAMSUNG_USB_Driver_for_Mobile_Phones.exe.
  6. Download this version of Odin.

  7. Extract “Odin_3.13.1.zip”.

  8. Run Odin3 v3.13.1 found in the newly extracted “Odin_3.13.1” folder.

  9. Check the box labeled next to the button labeled “AP”, and then click the “AP” button.

    • In the menu that pops up, select the newly downloaded custom VBMeta .tar file.
    Tip: The filename may very depending on your device, and version of TWRP.
  10. Check in the top left of thne Odin window that you see a valid device, it will show up as something like COM0.

    Tip: The COM port, or the number succeeding COM, may be any valid number.
  11. A blue transfer bar will appear on the device showing the recovery image being flashed.

  12. Your device will reboot, you may now unplug the USB cable from your device.

  13. The device will demand you format userdata, please follow the onscreen instructions to do so.

  14. Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.

  15. Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.

Important Information

Caution: The following instructions require a machine running Windows 7 or newer.

Samsung devices come with a unique boot mode called “Download mode”, which is very similar to “Fastboot mode” on some devices with unlocked bootloaders. Odin is a Samsung-made tool for interfacing with Download mode on Samsung devices. The preferred method of installing a custom recovery is through Download Mode – rooting the stock firmware is neither necessary nor required.

Tip: If this device’s install instructions already had you download Odin/Enable OEM Unlocking earlier in the installation process, you can skip steps 1, 3, 5, 6, and 7 below.

Installing a custom recovery using Odin

  1. Enable Developer Options by pressing the “Build Number” option 10 times, in the “Settings” app within the “About” menu
    • From within the Developer options menu, enable OEM unlock.
  2. Download a custom recovery - you can download . TWRP. Simply download the latest recovery file, named something like twrp-x.x.x-x-gts4lv.tar.
Tip: Ensure you download the .tar or the .tar.md5 file and not the .img version.
  1. Power off the device, and boot it into download mode:
    • plug in the device while holding Volume up + Volume Down + Power.
    • Now, click the button that the onscreen instructions coorelate to “Continue”, and insert the USB cable into the device.
  2. Download and install the necessary drivers.
    • Download the newest Samsung drivers from here. You will need to create a Samsung account and login to download them.
    • Install SAMSUNG_USB_Driver_for_Mobile_Phones.exe.
  3. Download this version of Odin.

  4. Extract “Odin_3.13.1.zip”.

  5. Run Odin3 v3.13.1 found in the newly extracted “Odin_3.13.1” folder.

  6. Check in the top left of the Odin window that you see a valid device, it will show up as something like COM0.
Tip: The COM port, or the number succeeding COM, may be any valid number.
  1. In the left side of the Odin window, you will see an “Options” tab, click it, and then un-check the “Auto Reboot” option.

  2. Check the box labeled next to the button labeled “AP”, and then click the “AP” button.

    • In the menu that pops up, select the newly downloaded custom recovery .tar or .tar.md5.
Tip: The filename may very depending on your device, and the version of your custom recovery.
  1. A blue transfer bar will appear on the device showing the recovery image being flashed.
Tip: The device will continue to display Downloading... Do not turn off target!! even after the process is complete. When the status message in the top left of the devices’s display reports that the process is complete, you may proceed.
  1. Unplug the USB cable from your device.

  2. Manually reboot into recovery, this may require pulling the device’s battery out and putting it back in, or if you have a non-removable battery, press the Volume Down + Power buttons for 8~10 seconds until the screen turns black & release the buttons immediately when it does, then boot to recovery:

    • With the device powered off, hold Volume Up + Power.
Caution: Be sure to reboot into recovery immediately after installing the custom recovery. If you don’t the custom recovery will be overwritten on boot.

Installing /e/ from recovery

  1. Before proceeding ensure you have downloaded the /e/OS for your device, from the link given in the Downloads section above

  2. If you aren’t already in recovery mode, reboot into recovery mode by typing the below command in the console of an adb enabled PC

     adb reboot recovery
    
    Tip: You can also do this manually using the below key combination
    • With the device powered off, hold Volume Up + Power.
  3. In TWRP return to main menu, then tap Wipe

  4. Now tap Format Data and continue with the formatting process.

    Here a new screen may show where you will have to type Yes and confirm the action by clicking a button.

    Caution: Format Data will remove encryption as well as delete all files stored on the internal storage. Remember to take a backup first. Check Requirements section above.
  5. Return to the previous menu and tap Advanced Wipe.

  6. Select the Cache and System partitions to be wiped and then Swipe to Wipe

  7. Sideload the /e/ .zip package.

    Tip: Sideload requires actions in two places to be done. One on your phone in the TWRP UI and secondly on the connected PC which should have adb enabled. Also note the sideload process while running may stop abruptly around 50%. The console would show a message Total xfer: 1.00x. This would mean that the transfer has successfully completed.
    • On the device in TWRP,

      select Advanced, ADB Sideload, then swipe to begin sideload.

    • On the host machine, in the console , start the sideload of the package by typing
     adb sideload filename.zip
    
    Tip: Change the filename to the name of the file you downloaded
  8. Once installation has finished, return to the main menu, tap Reboot, and then System

Warning: Avoid installing any additional apps or services if suggested by the recovery. They may cause your device to bootloop, as well as attempt to access and or corrupt your data.
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/ 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



Tip: To suggest changes to this install guide documentation, please visit the Galaxy Tab S5e (LTE) specific topic on our community forum. To report issues in the build please refer this guide

This documentation “Install /e/ on a Samsung Galaxy Tab S5e (LTE) - “gts4lv”” is a derivative of “install LineageOS on gts4lv” by The LineageOS Project, used under CC BY.