[UNOFFICIAL BUILDS] Samsung Tab A 2015 8.0 SM-T350 (gt58wifi) and Galaxy Tab A [SM-T355 and SM-T357W/T] (gt58ltebmc) for /e/OS-S

Samsung Tab A 2015 8.0 SM-T350 (gt58wifi) and Galaxy Tab A [SM-T355 and SM-T357W/T] (gt58ltebmc) for /e/OS-S 2.4

e-2.4-s-20241020-UNOFFICIAL-gt58wifi.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-2.4-s-20241020-UNOFFICIAL-gt58wifi.zip/download

e-2.4-s-20241020-UNOFFICIAL-gt58ltebmc.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-2.4-s-20241020-UNOFFICIAL-gt58ltebmc.zip/download

Please see sources and install instructions including recovery here:
https://xdaforums.com/t/unofficial-rom-alpha-lineageos-19-1-galaxy-tab-a-sm-t350-july-14-2024.4479287/
https://xdaforums.com/t/unofficial-rom-alpha-lineageos-19-1-galaxy-tab-a-sm-t355-and-sm-t357w-t-july-14-2024.4479319/

Use it at you own risk!
Please support the developer(s)!

1 Like

Hello! so there’s this small problem: the e os logo shows up upto the point where it shows ‘my data is MY data’ and then e os boot animation again does the same thing and then bootloops to do the same problem. can you fix this?
(my device is gt58ltebmc, SM T355Y, )

Did you use this TWRP version:?

A5. You MUST use TWRP 3.5.2_9. Get it from

https://sourceforge.net/projects/retiredtab/files/SM-T357W/TWRP/

I will check if all patches were applied correctly… it is a lot of work to apply them
I did check and all patches are correctly in place!

1 Like

yes I did use this Twrp version. But it’s atleast better progress from before,

are these patches not the same as A11? The A11 e os rom boots and works fine

no, those for /e/OS are different

possibly you can make this at startup
adb logcat > problem.txt
1 Like

sorry I may not know this, but I know how to get logcat only when it is powered on and the rom is working. do you know how to get them when my tablet is booting up?

I think you can just start it in the terminal of your PC while connected to your device and boot your device… adb debug should be enabled of course (but you can do this on the working R version when not done already)

1 Like

please see if this helps

I don’t think this is the full log… error message is missing

1 Like

Please see these log files, i got via cmd:
here the problems_a11.txt and logcat_a11.txt are generated when I restarted my tablet while laptop was connected. new_a11.txt was when I powered off my tablet while laptop was connected.
This link has these text files, Download - UploadNow.io

Just to ensure, did you follow this steps:
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 19.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it’s likely because you didn’t follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.

1 Like

ok I’ll try once again :+1:

so I did it again, yet the same issue remains.

ok, thanks that we sorted that out. Can you do a logcat again please

To get a logcat, open up a terminal window.

Code:

# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
# attach the problem.txt ZIPPED as text files don't seem to get attached properly

in a11 rom, there are no problems you talk about. what should I make a logcat of again?

ah sorry, I would need that logcat for A12 /e/OS-S of course. But adb debugging needs to be enabled for this. I think you could do the following:
Install LOS19 version and enable adb debbugging
Install via adb sideload the /e/OS-S version (dirty update)
start logcat

1 Like

i already installed eos a12 from twrp by the usual process mentioned in your post 12. now as I have eos a12 installed I open twrp > advanced > adb sideload > install e os file via adb from pc? is that correct?

first install LOS19 version to enable adb debbugging. Then you can install eOS-S via TWRP or adb sideload

ok so I do this:

  1. install retiredtab’s latest LOS19 rom. enable developer options, enable USB debugging.
  2. Reboot to TWRP to install e os A12 version. in second step I can install normally, without adb sideload from laptop right?
1 Like