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

[piero]

you’ve done the hardest part !

@globetrotterdk

I never got an Android Recovery menu

so good fingers and timing coordination

@globetrotterdk

Where do I go from here?

for installing the eOS.zip. There are just a few basic steps to carry out:

@piero

The e-recovery.img will perform many of the same functions as twrp and is probably a bit easier in some respects for installing the eOS.zip. There are just a few basic steps to carry out:

• (only for new install, not for update), select Factory Reset, then Format data / factory reset and continue with the formatting process
• Return to Home Screen
• Select Apply Update, then Apply from ADB

Now turn to your computer and issue the command to sideload the eOS installation zip

adb sideload filename.zip

When installation has finished, return to the main menu, tap Reboot system now

Your phone should now boot into eOS.

Step-by-step, with images

The e-recovery Home Screen. Select Factory reset

Select Format data/factory reset (notice the output appearing at the bottom of the screen)

Then press the arrow at the top of the screen to return to Home Screen

Select Apply Update, then Apply from ADB

The screen should now change and the output at the bottom ask you to send the package from your computer.

On the computer issue command to sideload the eOS installation zip.

adb sideload e-1.18-t-for-your-device.zip

the phone screen will be mostly blank with just the output at the bottom showing progress.

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!) and you can expect to see the following screens

Then press the arrow at the top of the screen to return to Home Screen

Tap Reboot system now to boot into eOS.

[aibd]

You might compare your situation with Installing /e/ OS on Pixel 5 - #45 by opensource.

[globetrotterdk]

@piero

(only for new install, not for update), select Factory Reset, then Format data / factory reset and continue with the formatting process

If you look at my last picture, you will see that the options aren’t the same as you describe. I think that this is where it went wrong last time.

[piero]

did you already done the sideload ?

@globetrotterdk

i got the same screen yesterday on my FP3 because i tried to avoid wiping data without success.
finally i had to format /data .

.

as i remember from my Tab2 (android 7), the next step (first boot setup wizzard) may have to be done in portrait mode

[globetrotterdk]

Just as I thought. This was where things go wrong. I chose “factory data reset” in the recovery-e menu and then used “format data”. After that, the device reboots and I get this SamsungOS welcome screen (sorry for the poor quality photo):

Now I am back the same place as I was before, and after setup, there will be a reboot and I will get the same warning about a non-Samsung operating system. I have gone full circle again, wihtout getting anywhere.

[piero]

sorry for your wasted time, i got two ideas :

1. try without flashing custom vbmeta.img
   as it is clearly not provided on the /e/ website (for a long time), it could be unnecessary → there are a few exemples of devices from the same generation as galaxy A52 where vbmeta even evocated in instructions, is not provided, not necessary…

2. try using older builds as latest can be faulty.

3. try making .TAR from vbmeta and recovery, then use Odin4 or Galaxy-Flasher as some recent device don’t like Heimdall 1.4.2, they could unlike Heimdall 2.1.0 too

@aibd have you other things in mind ?

.

.

some are more lucky :

@Loonlywolf

Hi i have a tablet Samsung t805, and i try very differents roms for changing for android 10 or 11.
But i dont have suusses… Its possible for any one help me with the instrutions manual and files, to try again? Thank you!

6 hours later :

@piero

@Loonlywolf

Muito obrigado!
Utilizei a Rom “e-1.17-q-20240308-UNOFFICIAL-chagalllte.zip”

@Loonlywolf

Instalar a rom e 100% ok.

glad it worked for you without issue

[aibd]

If this is repetition my apologies, but can you show the evidence @globetrotterdk of the Samsung model and device codename … the bad luck you seem to have had seems unusual without something wrong at a fundamental level.

[Xxpsilon]

@piero

2. try using older builds as latest can be faulty.

sing an older build (downgrade) rarely works because of Samsung’s (anti-) rollback protection.

The current build S (Android 12) T500XXS8CXG1 = BIT 8 (BINARY/U/SW REV.) 8 ( eight ). An earlier version with BIT 8 is not available.

Try new /e/OS version …
e-2.9-a14-20250323478432-community-gta4lwifi.zip
recovery-e-2.9-a14-20250323478432-community-gta4lwifi.img

… but both builds e-2.8-a14 + e-2.9-a14 are signed with release-keys …

metadata ~ BIT 7

post-build=samsung/gta4lwifixx/gta4lwifi:11/RP1A.200720.012/T500XXS7CXB1:user/release-keys

[Xxpsilon]

LineageOS has supported the current BIT 8 Galaxy firmware for months. For comparison: lineage-22.1-20250309-microG-gta4lwifi.zip

post-build=samsung/gta4lwifieea/gta4lwifi:12/SP1A.210812.016/T500XXS8CXG1:user/release-keys

[globetrotterdk]

[quote=“piero, post:27, topic:68395”]
sorry for your wasted time, i got two ideas[/quote]

I have again had time to look at the problems related to this device. Switching from the download mode to the recovery mode (recovery-e) is a bit problematic, as it isn’t really possible to predictably boot into recovery mode using the buttons, as there doesn’t appear to be a way to force the device to power down. It is however possible, by issuing the following command in the terminal $ adb reboot recovery. The recovery mode is of course recovery-e and not Android recovery, which confused me for a while. Unfortunately, I can’t get any further, as I get the following:

$ adb sideload e-2.8-a14-20250221470208-community-gta4lwifi.zip
adb: sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

I have yet to try any of the alternatives that you suggested yet, as I wanted to establish a baseline behavior that I could recognize. Are there any suggestions regarding this error, or should I move on and try some of the alternative suggestions?

[globetrotterdk]

I finally got it working. Thanks to all with input.

Unfortunately, it looks a bit crap with the unlocked boot loader warning and the booting non-standard system warnings. Is there anything that I can do about that?

Mainly, I am just happy that I have /e/OS on the device now!