Samsung Galaxy Tab A7 community /e/OS install using LMDE computer

[globetrotterdk]

I have previously posted about trying to install /e/OS on a Samsung Galaxy Tab A7, but in the end gave up because I had no experience and barely understood the concepts, as well as having security concerns about the programs needed to flash the tablet. Since I have recently been able to successfully flash a Fairphone 4, thanks to the help of the community, I have enough confidence to try this project with the Galaxy Tab A7 again.

The tablet currently has Android 12 installed (with Knox 3.8) and patch level June 1, 2024. I have noted that there is something new called Galaxy Flasher that has been developed, but it is unclear to me whether this includes Odin4 and Thor or not, after having looked through the documentation.

Next, last time I posted about the Tab A7, there was a suggestion that the /e/OS Recovery for community build image should be used, rather than trying to flash with the /e/OS build : U community image. What is the current thought?

Other than what I have posted above, I don’t have any experience with community builds and am trying (with difficulty) to understand where to go from here. I would appreciate if people responding to this post try to be clear and concise as possible as I am in deep water here. Thanks.

[piero]

@globetrotterdk

having security concerns about the programs needed to flash the tablet

What is the OS running on your PC ?

[globetrotterdk]

LMDE (Linux Mint Debian 12).

[piero]

@globetrotterdk

having security concerns about the programs needed to flash the tablet.

If it is for flashing an entire Samsung Firmware, i would advise to use Odin3 windows, or Odin4 linux, or Galaxy-Flasher (that include Thor and Odin4linux)

If it is for flashing a custom recovery, it will be clearly easier using Heimdall (for recent devices like your’s, prefer Heimdall v2.1.0 New Heimdall version 2.x.x

as your linux-mint is debian based, i think you can use the one i have builded for my ubuntu
Download Heimdall_2.1.0_Ubuntu.zip (custom android builds)

The real Trick is to reboot directly into recovery mode just after to have flashing the custom recovery.

[piero]

@globetrotterdk

The tablet currently has Android 12 installed (with Knox 3.8) and patch level June 1, 2024

So it is the latest Samsung Firmware, but

what is the device model-number ?

SM-T500 Install /e/OS on a Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) - “gta4lwifi”
SM-T505 Install /e/OS on a Samsung Galaxy Tab A7 10.4 2020 (LTE) - “gta4l”

@globetrotterdk

I would appreciate if people responding to this post try to be clear and concise as possible

[HOWTO] an Unified Install Guide Project for /e/

posts are editable as a Wiki. Here is the summary : (1) install the appropriate Flashing Tools (2) allow “Non Vendor OS” to be installed on the device (3) Check the communication between the PC and your smartphone (4) Download a custom recovery manager (5) Download an /e/OS build (6) Unlock the Bootloader (7) Flash a custom recovery manager on your device (8) install /e/ from your computer, using the “adb sideload” method or (9) Install /e/ without computer using the “Device-Storage…

Boot Modes

Recovery

With the device powered off - hold Volume Up + Power.

Download

With the device powered off - With USB plugged in, hold Volume up + Volume Down + Power

@globetrotterdk

with the /e/OS build : U community image. What is the current thought?

you can create a folder called “special” containing :

• e-2.8-a14-20250221470208-community-gta4lwifi.zip
  

  

• Heimdall 2.1.0 New Heimdall version 2.x.x

• recovery-e-2.8-a14-20250221470208-community-gta4lwifi.img
  rename it into recovery.img
  (or extract it from e-2.8-a14-20250221470208-community-gta4lwifi.zip)

• vbmeta-e-2.8-a14-20250221470208-community-gta4lwifi.img
  rename it into vbmeta.img
  (or extract it from e-2.8-a14-20250221470208-community-gta4lwifi.zip)

6) Unlock the Bootloader

the device in download mode,
Open a terminal from the special folder, and copy/paste

./heimdall print-pit

7) Flash the custom recovery manager, TWRP or recovery-e

the device in download mode,
Open a terminal from the special folder, and copy/paste

./heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img --no-reboot

8) Install the image of /e/OS on the rom of your device from your Computer using the ADB sideload method.

considering “platform-tools” is correctly installed on your system
the device in recovery mode,
Open a terminal from the special folder, and copy/paste

adb sideload e-2.8-a14-20250221470208-community-gta4lwifi.zip

[globetrotterdk]

[quote=“piero, post:4, topic:68395”]
The real Trick is to reboot directly into recovery mode just after to have flashing the custom recovery.[/quote]

So, with that in mind, is it recommended to flash an entire Samsung firmware or a custom recovery to get /e/OS installed on the Galaxy Tab A7 (SM-T500)?

@piero

SM-T500 Install /e/OS on a Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) - “gta4lwifi”

SM-T500 is the device model.

[piero]

@globetrotterdk

is it recommended to flash an entire Samsung firmware

No,
as you already have latest installed on your device.

@globetrotterdk

is it recommended to flash a custom recovery to get /e/OS installed on the Galaxy Tab A7 (SM-T500)?

Yes,
as it is mandatory…

@globetrotterdk

@piero

The real Trick is to reboot directly into recovery mode just after to have flashing the custom recovery.

@piero

…NOW COMES THE CRUTIAL STEP !..

• To get out of the Download mode you must Force Power Off your Samsung device,
  (on some old devices, unplug the device,)
  hold Volume Down + Power.
  release when you see the screen turn off…

…IT IS THE CRUTIAL STEP !..

• immediately Boot to Recovery before any other boot mode attempt,
  hold Volume up + Home + Power
  release Power when you see the very little blue line in the top of the screen…

…IT WAS THE CRUTIAL STEP !..

[globetrotterdk]

@piero

you can create a folder called “special” containing :

• e-2.8-a14-20250221470208-community-gta4lwifi.zip

OK, I am starting to get a little confused here by switching between documents all of the time. Here are the steps that I have completed necessary android bits are already installed from my last project).

• Downloaded and installed Galaxy Flasher (as flatpak).
• Downloaded both recovery-e-2.8-a14-20250221470208-community-gta4lwifi.img and e-2.8-a14-20250221470208-community-gta4lwifi.zip.
• Enabled Developer Options.
• Enabled OEM unlocking
• Enabled USB debugging
• Confirmed that my device is listed under the command $ adb devices

I am now at preinstall instructions item number three for Install /e/OS on a Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) - “gta4lwifi”.

That item talks about “extracting the contents of the /e/OS build zip file”, however I need to use the recovery-e-2.8-a14-20250221470208-community-gta4lwifi.img with Galaxy Flasher, don’t I? That is at least what item number four in [HOWTO] an Unified Install Guide Project for /e/ suggests.

Is this where I use the Galaxy Flasher? That would mean that I have jumped over item four on Install /e/OS on a Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) - “gta4lwifi” and am actually at item number five - “Power off the device, and boot it into download mode:”?

[piero]

be carefull : Install /e/OS on a Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) - “gta4lwifi” are instructions for users using Windows

@globetrotterdk

however I need to use the recovery-e-2.8-a14-20250221470208-community-gta4lwifi.img with Galaxy Flasher, don’t I?

Heimdall manage .IMG files
Thor and Odin4 manage .TAR files

.

look like you want to try Galaxy-Flasher (i like it, because unlike Heimdall, it is very confortable to flash entire Firmware)
but again for single partition flash, easier is the traditionnal / historical way : Heimdall
.

post #5 of the present thread contains personnalised commands to execute the corresponding steps in [HOWTO] an Unified Install Guide Project for /e/

[globetrotterdk]

Galaxy Flasher does not accept using an .img file, regardless of adding the Odin4 or Thor plugins for Galaxy Flasher.

[globetrotterdk]

@piero

With the device powered off - With USB plugged in, hold Volume up + Volume Down + Power

I seem to be unable to get the device in “download” mode for heimdall to recognise.

[piero]

could be bad formulate on /e/ documentation page,

if found this on the web :

HardReset.info : https://www.hardreset.info/devices/samsung/samsung-galaxy-tab-a7-2020/download-mode/

How to Open Download Mode on SAMSUNG Galaxy TAB A7 2020?

1. In the first step, push Volume Down and Power button for a short while and tap on Restart option twice.
   
2. When the SAMSUNG logo shows up, press Volume Down and Volume Up and connect the tablet with PC or laptop by using USB cable.
   
3. Let go of all held keys if you see Download mode on the screen.
4. Now select OK with Volume Up.
   
5. Great!
   

.

HardReset.info : https://www.hardreset.info/devices/samsung/samsung-galaxy-tab-a7-2020/recovery-mode/

How to Open Recovery Mode on SAMSUNG Galaxy TAB A7 2020?

1. Start by holding Volume Down + Power button for a few moments.
2. Then push Volume Up and Power key together for a couple of seconds.
3. Release both held keys when you see Recovery Mode on the screen.
4. In this mode use Volume buttons to scroll and the Power key to confirm that.

[globetrotterdk]

OK, thanks. I finally got into “download mode”. The result was as follows:

$ ./heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img --no-reboot
Heimdall v2.1.0

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna https://glassechidna.com.au
Copyright (c) 2021-2024 Henrik Grimler
This software is provided free of charge. Copying and redistribution is encouraged.

Initialising connection...
Detecting device...
Claiming interface...
Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading RECOVERY
100%
RECOVERY upload successful

Uploading VBMETA
100%
VBMETA upload successful

Ending session...
Releasing device interface...

I eventually was able to get out of download mode and into recovery mode (not really sure how). I did get recover-e though. I also ran the steps as listed in Format the device. Unfortunately, after having gone through all of the steps, I ran out of instructions for Linux.

The device rebooted for some reason, and now I get the following (apologies for photo quality):

[piero]

@globetrotterdk

I also ran the steps as listed in Format the device . Unfortunately, after having gone through all of the steps, I ran out of instructions for Linux.

@piero

On the computer the sideloading shows progress as a percentage figure that will stop at 47%. The phone will still be installing though (even though it might feel like nothing is happening sometimes!)

.

.

"only official released binaries are allowed to be flashed"

you will need to restart from scratch and use Galaxy-Flasher to flash Samsung Firmware

Samsung Galaxy Tab A7 (Wi-Fi) Firmware Download SM-T500 Free Download

then reflash a custom recovery and finally /e/OS

[globetrotterdk]

@piero

you will need to restart from scratch and use Galaxy-Flasher to flash Samsung Firmware

I have no way to restart from scratch, as long as I can’t get past the pictured screen, to somehow get the installed android tools on my computer to recognize that my device is connected. All I get is an error message from Galaxy Flasher that no Samsung devices can be found. Running

$ adb devices
List of devices attached

nor any other command seems to currently work as long as there is no system on the device.

[piero]

adb commands will only works with the phone in normal mode or recovery mode.

you need to reboot the device into download mode to use Odin or Galaxy-Flasher.

[globetrotterdk]

OK, finally succeeded:

$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
R9WR30T54QJ	unauthorized

Not sure why the device is listed as “unauthorized”.

[globetrotterdk]

So, at this point, I am assuming that I have what appears to be a working Android system on my device. This is a good time to mention my experiences with the procedure, before I try again:

Firstly, this is the only procedure that has worked for me - 1. Power off the device, and again boot it into download mode:

• With USB plugged in, hold Volume up + Volume Down + Power

This can be found at Install /e/OS on a Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) - “gta4lwifi” at item eleven, under " Pre-Install Instructions".

Secondly, Heimdall appears to download both recovery.img and vbmeta.img, however it is unclear as to the location where it is downloaded to on the device. This becomes important later.

Thirdly, “Format the device” functions as advertised, as described on the install guide linked to above in this post. However, it diverges at the next section “Install /e/OS”, as it for some inexplicable reason is only a guide for those people using Windows on their PC. So, I tried following the [HOWTO] an Unified Install Guide Project for /e/.

Unfortunately, item four " Download a custom recovery manager .img" in that howto is vague regarding using the “recovery-e” method. As stated earlier, the download to the device (of apparently both files) functions fine, however it is unclear where the files are located on the device. This becomes important when arriving at the “recovery-e” main screen, as when choosing the “factory reset” option, there is a prompt as to where the vbmeta.img is on the device, and a file manager pops up, and it is necessary to find that file. As I didn’t know where the location was, I chose “Android” folder on internal storage. The script then rebooted the device and started to run an Android system setup, and apparently had also locked the bootloader at some point, thus resulting in the situation that I posted about, with the photos. At no point did I ever get “android recovery”, as in your picture.

So, where do I go from here? Do I just re-run the same procedure as I did before? If I don’t get more information or other form of guidance, the most likely result will be the same as last time, as far as I can see.

[piero]

@globetrotterdk

I have what appears to be a working Android system on my device

Do you mean SamsungOS or /e/OS ?

@globetrotterdk

it is unclear as to the location where it is downloaded to on the device.

the vbmeta.img file is an image of the /VBMETA partition
the recovery.img file is an image of the /RECOVERY partition

@globetrotterdk

it diverges at the next section “Install /e/OS”

I do not see divergence here, the “official documentation” only describe the sideload method, when the “unified guide” also talk about local install (from internal storage that is not possible on all device using the recovery-e)

@globetrotterdk

at the “recovery-e” main screen, as when choosing the “factory reset” option, there is a prompt as to where the vbmeta.img is on the device, and a file manager pops up, and it is necessary to find that file

sorry, I do not understand any of this.

“factory reset” leads to

what you call a “file manager pops up” results of the “apply update” → “from internal storage”, it ask for the e-2.8-a14-20250221470208-community-gta4lwifi.zip to install it on the system…

[globetrotterdk]

OK, let’s skip that for now. I am trying again. Here is what I get:

After I get the same message from Heimdall as I posted last, I try to get to recover mode. This is what I get, and where I am at the moment:

I never got an Android Recovery menu when I tried to get into Recovery Mode. Where do I go from here?