I will test in the next days…
Here are the instructions again:
Is there a chance, that the version T813 of the S2-Tablet gets re-supported by /e/os? That would be really great since this Tablet is still in 2023 a powerful and very slim & light peace of Hardware…
There are probably no official maintainer
This rocks! Thank you ronnz98 for getting this started!!
I’m still using the very same tab (Exynos 5433) on my home network and could not agree more – it is very powerfull, slim and light.
This could be the to be announced /e supported tablet 
I will report back, once I got it running – any issues so far?
Cheers
This goes to:
(gts28vewifi)
Released 2016
Specifications
SoC Qualcomm MSM8976 Snapdragon 652
It should be:
Info about gts210wifi | LineageOS Wiki
Samsung Galaxy Tab S2 9.7 (Wi-Fi) (gts210wifi)
Released September 2015
Specifications
SoC Samsung Exynos 5433
Up to now I could not get the [UNOFFICIAL e-1.14-t] (gts210wifi) 3G/32G
to boot. I would even show up e logo.
Anyone able to help me with debugging?
The latest LOS20 version for this device from 13-AUG does work fine
Are you using TWRP?
It has a file manager, does logs during flashing… you can mount system read only and look for logs, from when it tried to boot, maybe!?
Or do you have adb working during the black screen?
yes I’m using TWRP. Unfortunately I cannot connect via USB (charging does work though).
I did install via SD card.
I will try again and search for log files. The logs during flash looked fine
Do you have version number and, or link, please?
(I only asked about TWRP, after someone here said he had never heard of it – only ever learned adb, I gues)
I am still working on several S7 and S7edge, so not tried flashing the tablet, yet.
here is the link:
https://dl.twrp.me/gts210wifi/
On XDA forum its stated
A5. You MUST use TWRP 3.6.2_9.
https://forum.xda-developers.com/t/unofficial-rom-alpha-lineageos-20-for-sm-t810-aug-13-2023.4600445/
There is however also a newer version which I tried and also could successfully install LOS20
1 Like
For old devices, i prefer old twrp, such as 3.3.x-x
Same here, also better luck with those.
I often also just look at the size and pick the last <10mb, if there is a long list of versions.
I tried some older version of TWRP but still not luck
I could also build now for SM-T710 a eOS version of 1.14-S. But in lack of owning this device I cannot test. I own only a SM-T713 which I’m looking to create a manifest file
Do anyone can support in debugging the SM-810 version I build?
Remember Dex2oat jumped in, but there should be alternative ways to check the reported
verification errors
I think, perhaps printed to a .txt file not shown in the quoted output.
during build to print a log file or during booting (is this possible tough?)
I mean during build.
You showed this
to clarify, I think you can see or generate more verbose detail, by following the full text of the passage.
This followed the repo forall incident – now that we have a “new” tag repo sync will have work to do, then repo forall has a chance to pull in anything missed, perhaps.
Can you guide me please?
This was your starting point – Are we ok with that ? Are you confident that environment is ok ?
And / or are you using https://gitlab.e.foundation/steadfasterX/android_vendor_e ?
Save all your manifests and self generated data unless you have this already saved correctly with git.
You might clean the environment with https://groups.google.com/g/android-building/c/QIne5MVjO7U.
If you choose to follow rm -rf * – you may be surprised to find that the hidden folder .repo (potentially ~100+ GB) is not destroyed). (In this case don’t follow through with repo sync -l)
If this seems unsafe, ask again, I know no more of your environment than I quoted.
Never do any form of rm -rf advised from a stranger without double-checking the consequences – /out is also destroyed, back it up if anything is needed
Now you can
repo init -u https://gitlab.e.foundation/e/os/releases.git -b refs/tags/v1.15-beta-t
Sort out all the bits you already saved.
repo sync
repo forall -c ‘git lfs pull’
1 Like
Thanks! I think my environment is ok. I have a LOS20 and eOS T enviroment for repo builds.
The manifest.xml I took from
https://forum.xda-developers.com/t/unofficial-rom-alpha-lineageos-20-for-sm-t810-aug-13-2023.4600445/
and put into respective local_manifest in .repo folder
I rebuild yesterday on my desktop pc and had fewer error than on my laptop while building. Though build (now 1.15T does also not boot).
I encountered the following errors:
/interfaces/camera/device/1.0-legacy
/interfaces/wifi/1.0-legacy
→ Replaced it with respective LOS20 folder
eOS prebuilds apps. I downloaded the complete zip package from
https://gitlab.e.foundation/e/os/android_prebuilts_prebuiltapks_lfs
and copied to:
/prebuilts/prebuiltapks