I am having a fundamental problem understanding the process for flashing an unofficial build:
I have both looked at the the above thread and at the LineageOS documentation that as I understand it, /e/ is based on. I am using Fedora 39 for my desktop computer OS and understand that at some point in mid-February, I should be able to use the snap package listed here:
However at this point in time, I am assuming that the following LineageOS guide should be used as a frame of reference for installing an /e/ OS unofficial build?
The following is straight forward for Linux (and I already have the udev rules installed and configured from when I installed GrapheneOS on my Pixel 6a phone (using web install):
I repeat that I would like to install /e/ OS, but am really confused as to how to flash the tablet with the unofficial build, from a Linux computer… Can anyone spell this out for me?
OK, so far, so good. I have downloaded heimdall and “installed” it using $ sudo cp heimdall /usr/local/bin and confirmed by $ heimdall version v1.4.2 The e-1.18-t-20231213-UNOFFICIAL-gta4lwifi.zip file has been downloaded and I have unzipped the file. I have located the file recovery.img in the resulting directory. My assumption is that after booting the tablet it download mode, I should run the following command:
However, things start getting hazy here. recovery-e looks like it is Windows software, so I am assuming that using TWRP is the way to go… It looks like TWRP is an Android install, so I guess that i should install that before running the above heimdall command? After a wipe, format data, advanced wipe and swipe to wipe, it appears that I need to use TWRP to sideload the original e-1.18-t-20231213-UNOFFICIAL-gta4lwifi.zip file? I have never used TWRP, so I am not quite sure how this fits in with the instruction at the bottom of the wiki that piero linked to…
TWRP recovery is the Swiss Army Knife for all custum ROMs.
The /e recovery is tailored towards /e so it has the greater compatibility with /e OTA updates, or maybe even some customisation /e depends on.
(Personally, I always start with a TWRP and the ROM on a SD card, if the device has a SD)
Thanks for that. Where is this TWRP that needs to be installed on the Galaxy Tab A7, and do I use heimdall to get this on the A7? As far as I can see there is a different TWRP for each device, and there doesn’t appear to be an official version of TWRP Recovery for the Samsung Galaxy Tab A7 10.4 WiFi SM-T500…
I am unable to get to that point. I have run into problems with “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” instruction. No problems with enabling USB debugging. However, the OEM unlock option only appears from time to time. Not sure why.
OK, I shutdown the tablet and then booted as instructed. Working from the correct directory, I got the following message:
$ heimdall flash --VBMETA vbmeta.img --RECOVERY recovery.img --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
$ heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
I got a similar screen as the picture in the post that was linked to. OEM lock was listed as on, despite while in settings OEM unlock was on.
Any other clues on your Download mode screen ? Do you see Prenormal ? What is the history of the tablet, have you been using it “normally” for a while before attempting /e/OS install ?
The tablet was expressly purchased for this purpose. It arrived from an eBay seller two days ago and was listed as “new - other”. There was no box, power supply, etc. however it does appear to be new.
Nothing with Prenormal. The current binary is listed as “Samsung Official”.
Different generations of Samsung may behave slightly differently … but it is a regular thing that a Samsung may not fully unlock until Remote Monitoring decides the device is in normal use. In recent generation devices it is recorded that Prenormal is not displayed but is active.
Another move is to check for updates in the Samsung UI, this will trigger a connection to RMM… many other things that might happen listed in Know your hardware - Samsung Troubleshooting section. The possible need for Samsung account on the device to satisfy RMM is also mentioned; but such account must be removed after unlock is indicated and before flashing a custom ROM.
OK, so what I have been able to find out is that while Odin4 and Samloader (both are apparently needed) are official Samsung tools, neither has been released by Samsung. Rather, there are just copies floating around on the Internet.
As I am looking for a system that not only is de-Googled, but also provides added security when I am on the Internet, using these tools are a step too far. Which is unfortunate, as I am no closer to a tablet that is de-Googled, as well as takes reasonable security measures to address current and future threats on the Internet. That doesn’t mean that /e/ OS doesn’t provide that, it means that I am not going to do things that could potentially compromise those key goals to find out if /e/ OS provides those things…
It can seem that way and some sites and links are doggy. That said I use the very same ODIN3 since ~2016 — on a Win notebook, just for AOSP, ROMs… related stuff.
You can look at ODIN a bit like Thunar, Dolphin… but build for Android file operations.
It may not be everbodies cup of tea to use Win, but I have flashed first on a Android 1.6 on Sony-Ericson and later on, I started with ODIN on Samsung Galaxy S2 — and would not do any Samsung flashing without ODIN (as of today ~240 phones) as it has not filed me ever.
I do server admin work, bash scripts, php… but ODIN just has that place in my workflow.