[ROM][SM-T510][UNOFFICIAL] LineageOS 18.1 for Galaxy Tab A 10.1 (2019)

Search This thread

rintinfinn

Member
Mar 2, 2014
32
11
ROM works and can even be used with an older version of the security patches as long as you flash the correct (older) TWRP after flashing the ROM (although the pain of doing a full device update by flashing the newer stock rom first, is worth it).

But I have the following issue: I cannot connect to a specific WiFi network created by my Fritz Repeater 1750E, it is the one to which the device was connected before the upgrade of the ROM (I used an older version from last year before). All other wifi networks work.

It is basically the same issue as described here for the SM-T580:

It is stuck at "saved" and "Failed to connect to network". I am sure this is not a password issue. Anybody has got any ideas?
I've got the same issue after upgrading to Lineage 18. I can connect to my phones hotspot without problem but the tablet refuses to connect to my openwrt access point. Other android 11 devices (running calyxos) do connect fine.
 
  • Like
Reactions: BatZzn

rintinfinn

Member
Mar 2, 2014
32
11

With lineage-18.1-20220417-UNOFFICIAL-T510XXU5CVB1.zipi have no errors what so ever. Tested with FB7490, FB7590 AX, Ubiquity AP´s and an Asus DD-wrt Router. I´m Afraid i have no FB Extender to text with.

I found the solution for now. Wpa2/Wpa3 mixed mode was the problem. The tablet can only connect to wpa2 only networks on openwrt at the moment, it seems.
 
  • Like
Reactions: spezialzt
I tried several, ended up with the lineage wiki recommandation.

MindTheGapps-11.0.0-arm-20220217_095902.zip
Works fine for me.

However i have another issue @Magendanz
Everthing works Like a charm. However compared to your other Rom the audio Volume is silent and Missing some decibel.

I already tried Viper, without any gain.
Is there any possibility to import the Samsung audio "stuff" ?
Kind regards
MindTheGapps-11.0.0-arm-20220217_095902.zip didn't work for me.
 

BatZzn

Senior Member
Nov 20, 2011
539
127
I found the solution for now. Wpa2/Wpa3 mixed mode was the problem. The tablet can only connect to wpa2 only networks on openwrt at the moment, it seems.
Bwoah, thats a real deal breaker for me... I surely not goning to reduce my home wifi network security only for this old and slow tablet. will this be fixed soon?
 

Charfahl

Member
Aug 31, 2008
24
6
So I too am having the issue of no GAPPS from mind the gapps...

Tried Every single gapps 11 version... Am I missing something?

Everyone says these are for xxx but your system is amd64, same issue as others... no matter what version i use
 

Skyfire1

Senior Member
Jan 2, 2015
130
21
Hi there, I'm encountering a bootloop when flashing this ( latest version ) rom from first post. Tried through twrp and Odin. Even did a factory reset and format data. Always the same. The other rom ( Nexus ) by Magendanz works fine. After flashing the Nexus rom the tablet boots to TWRP automatically. After flashing this rom it boot loops. Is it the wrong TWRP ? I imagine it is something I overlooked or misinterpreted...
Any help very much appreciated! 🙂

Edit : I´m now waiting for the LineageOS 17.1 to complete first boot but it´s taking 10+ minutes now. How much longer should I wait?

Waiter 25 minutes and stopped it. Flashed Nexus again. Works fine.

Maybe I'll try flashing Samsung rom again and go from there again...
 
Last edited:
For example: your installed Version is T510XXU5CVB1, you can only Install a CVB1 Rom.

After i flashed a Rom via Odin
i Open twrp and do a factory wipe + Data,
Because i wear fancy pants i reinstall lionageTwrpVersion in twrp.
In twrp Install any gapps without Errors ( Like a Boss), confirm Install with factory Reset.
Repeat steps for magisk ... If needed.

Its no Rocket science.
 
  • Like
Reactions: Skyfire1
For example: your installed Version is T510XXU5CVB1, you can only Install a CVB1 Rom.

After i flashed a Rom via Odin
i Open twrp and do a factory wipe + Data,
Because i wear fancy pants i reinstall lionageTwrpVersion in twrp.
In twrp Install any gapps without Errors ( Like a Boss), confirm Install with factory Reset.
Repeat steps for magisk ... If needed.

Its no Rocket science.
Did the above steps work for anyone? Please share the gapps used?
 
PXL_20220529_012811836.MP~2.jpg

Again, installed from Aroma to nano several Versions without any Problems.

Stick to the Wiki Guide and it will Work.
 

Skyfire1

Senior Member
Jan 2, 2015
130
21
So my problem is solved! I flashed newest stock firmware and then I flashed this rom. Seems to work fine.
Happy now ! Special thanks to @Magendanz and everyone invovled in creating this rom ! :)
 
Last edited:

Skyfire1

Senior Member
Jan 2, 2015
130
21
View attachment 5625211
Again, installed from Aroma to nano several Versions without any Problems.

Stick to the Wiki Guide and it will Work.
A little hint which wiki guide you used would be great :)
Using opengapps makes the tablet say this device isn´t play protect certified ( will not allow me to use the playstore ) and mindthegapps makes twrp say error 1 and " this package is built for arm64 but your device is arm64 " No typo ...

Screenshot_2022-05-29-08-50-56.png
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Here is my little guide to get it back working after boot loop issue while upgrading to Linage 18.1


    1. Load the Binaries from Samfw (look for your Firmware and Country!)

    AP_T510XXU5CVB1_CL22626479_QB49304683_REV02_user_low_ship_meta_OS11.tar.md5
    BL_T510XXU5CVB1_CL22626479_QB49304683_REV02_user_low_ship_meta_OS11.tar.md5
    CSC_T510XXU5CVB1_CL22626479_QB49304683_REV02_user_low_ship_meta_OS11.tar.md5

    2. open Odin and load the images for AP, BL, CSC

    3. Reboot the Device into Download Mode (press volume up and down on reboot)
    * i'ts possible to get there, even during boot loop

    4. connect it to your PC

    5. flash the files downloaded in step 1 with Odin

    6. after successful start with the Stock Image reboot again into Download Mode

    7. flash the Linage OS from with factory reset Wipe->Format Data

    8. reboot into recovery

    9. copy the open_gapps-arm-11.0-nano-20220215 via USB to twrp 3.6.x

    10. install the zip with twrp 3.6.x

    11. reboot to system and set it up

    12. If this message occurs: "the device is not play protect certified" continue with the following steps

    13. Download [[https://apkpure.com/device-id/com.evozi.deviceid| APP Device ID]]

    14. Copy the GSF ID to [[https://www.google.com/android/uncertified/| Google Device Registration]] (You need to be logged in your Google Account)

    15. Wait 10-15 min till the warning disappear

    Hope it helps anyone.

    Still facing the Fritz!Repeater 2400 issue. (No Wlan connection possible) All other networks are good.
    Not sure about it has sth. to do with WPA3.

    Credit to @spezialzt @Magendanz and @dadmi
    2
    Did you managed to fix this?
    Um.... I think so?

    But I'm not 100% sure what I did that made the difference! So I'll explain what I did, and hopefully it will help you out. I think it was a combination of a few things. FYI, I started from an fresh install of stock firmware.

    I first tried the Samsung "Smart Switch" software installed on my laptop. I thought I might be able to "initialise" or "update" the firmware and fix the issues I was getting. It actually took a while transferring before dropping out with a "Your device does not support firmware updates" or some nonsense. Ok, dead end.

    I next tried tweaking Android, enabling developer options (tapping build several times), and enabling USB ADB. I then downloaded heimdall, thinking maybe software other than Odin might work.

    I booted the tablet into recovery, and ADB, and was able to connect from my laptop, but... then I didn't do much else. I rebooted into download mode, and flashed Lineage 18.1 using Odin, and it worked! :D

    But then it hung on system boot :confused: I let it go for about 15 minutes, hoping it would finish booting, but no luck. Just that little circle rolling left again and again.

    I rebooted into recovery, wiped all data, back into download, and reflashed LOS using Odin. Once back in TWRP, I "Fixed Contexts", and then I repaired all the partitions I could (some don't allow it). I then realised only half the partitions were mounted, so I mounted the unmounted partitions.

    I then rebooted to system and it worked! I had a functioning LOS 18.1 asking for setup :cool:

    Hopefully I won't have any niggling bugs like after I first bricked it. I haven't played with it much before letting you know I was able to flash. Sorry I don't have an explicit "do this to fix it" answer. I think it was lots of little things. But hopefully you can use this as a rough guide of things to try?

    Good luck!

    (And thanks again to dami for the support and Magendanz for the image. You rock, Magendanz!)
    2
    My tab display clicking itself, is that display issue? just to check that shifting to custom rom

    Primary device: Oneplus 6T, Evolution X
    On the osi Model, i think its related to Level 8
    1
    I booted the tablet into recovery, and ADB, and was able to connect from my laptop, but... then I didn't do much else. I rebooted into download mode, and flashed Lineage 18.1 using Odin, and it worked! :D

    Dude that was it! I was trying to flash the tablet using my desktop but for some reason, every USB port I tried didn't do anything.

    Then after reading your post, and more importantly, the laptop part, I remembered that Samsung and Odin are very picky when it comes to USB connectivity, so I tried using my laptop to flash the file and boom! It worked on the first try.

    Thank you so much for the explanation. While my solution is not on your to-do list, it served me well and could help any other member facing the same issue.
    1
    can't install gapps in this rom
    MindtheGapps gives me error 1 in twrp.
    opengapps gives play protect certified error...

    back to nexus Rom.
  • 28
    640px-Lineage_OS_Logo.png

    In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 18.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 18.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.

    Notes:
    • The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
    • Custom kernels are specific to OEM releases, and this one is based on the latest Android 10 release (T510XXU5CVB1).
    • Stock recovery will be replaced with my latest TWRP build for the SM-T510.
    • This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.

    Not working:
    • Support for file-based encryption
    Downloads:
    Build archives:
    Change Log:
    20220417:
    • Based on the latest build of LineageOS 18.1 GSI (20220414) with April 2022 Security Patch.
    • Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVB1).
    • Update to TWRP v3.6.1 custom recovery on AOSP 11.
    • Replaced default wallpaper with custom one inspired by my Nexus ROMs.
    • Boots normally for offline (cold) charging.
    20210526:
    • Based on the latest build of LineageOS 17.1 GSI (20210512) with May 2021 Security Patch.
    • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU4BUA1).
    20201121:
    • Based on the latest build of LineageOS 17.1 GSI (20201114) with November 2020 Security Patch.
    • Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
    20200812:
    • Based on the latest build of LineageOS 17.1 GSI (20200808) with August 2020 Security Patch.
    • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
    20200713:
    • Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 Security Patch.
    • Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
    20200413:
    • Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
    • Fixed crash on first two attempts to launch Phh Treble Settings.
    • Based on the latest build of LineageOS 17.1 GSI (20200413).
    • Updated to the OEM T510XXS3ATB4 kernel and vendor partition.
    20200321:
    • Switched to latest stable version of ext2simg command for sparse image conversion.
    20200314:
    • Now based on the latest build of LineageOS 17.1 GSI (20200309).
    • Fixed potential image corruption issue from outdated img2simg command.
    20200308:
    • Charging after full shutdown will no longer hang during level-of-charge animation.
    20200301:

    Instructions:
    From OEM stock firmware:
    • Unlock bootloader
    • Hold Vol Up & Vol Down buttons during restart to enter Download mode
    • Install custom ROM tarball (.tar.md5 file) to AP with Odin
    • If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
    From existing TWRP install:
    • Hold Power & Vol Up during restart to enter TWRP recovery
    • Tap Install, Install Image, select your update (.img file), and then swipe to install
    • Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
    • Reboot to system

    Source:

    Donations:
    • Your support is always appreciated! Just click here.
    • I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
    5
    New build posted...

    Downloads:

    Change Log:
    20200713:
    • Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 Security Patch.
    • Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
    4
    I read that the lineage-17.1 GSi is updated on 20200607 with security patch June. Can we also expect soon an update for SM-T510?
    Soon. I'm trying to get the adaptive brightness and a few other features working for this next release.
    3
    I'm convinced that Samsung's decision to go with ARM32 (with 64-bit binder) for the SM-T510 was because of the low 2GB RAM in the base configuration. While overall performance is usually better running in 64-bit, RAM-constrained devices will have some serious performance issues that can be avoided by using the 32-bit instruction set. It just has a smaller footprint in memory.

    I would be interested in migrating a 64-bit vendor partition from another Exynos 7904 device, such as the Galaxy A40. It can be a tedious process, however, so I wouldn't undertake it if there was any chance that the Android 10 release coming in September might be 64-bit.

    We need a 64-bit vendor image from Samsung (or someone to adapt it from another Exynos 7904 device like the Galaxy A40). Perhaps the Andriod 10 release (due in September) will be 64-bit.

    I built a 64bit LOS GSI just yesterday and I've been playing with it today, I got it installed and it boots up far enough to be able to access the logs, however it gets stuck looking for the 64-bit `libGLES_mali.so`.

    I tried looking around for the 64 bit version of the libraries for the `universal7885` board or `exynos5` platform but had no luck.

    I don’t think it would be hard to get the A40 vendor partition to work. Biggest hurdle is the partitions all have to be resized due to the extra space required by the x64 binaries.

    If you could point me to a binary-compatible propreitary vendor image with the 64-bit libs I'm missing for this architecture I will be glad to share the modified sm-t510 vendor image if I can get it working.

    Here is the boot stacktrace I'm current looking at:
    Code:
    07-26 09:43:33.144  4222  4222 D RenderEngine: RenderEngine GLES Backend
    07-26 09:43:33.145  4222  4222 F libEGL  : couldn't find an OpenGL ES implementation, make sure you set ro.hardware.egl or ro.board.platform
    07-26 09:43:33.145  4222  4222 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4222 (surfaceflinger), pid 4222 (surfaceflinger)
    07-26 09:43:33.168  4227  4227 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
    07-26 09:43:33.168  3934  3934 I /system/bin/tombstoned: received crash request for pid 4222
    07-26 09:43:33.169  4227  4227 I crash_dump64: performing dump of process 4222 (target tid = 4222)
    07-26 09:43:33.173  4227  4227 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    07-26 09:43:33.173  4227  4227 F DEBUG   : LineageOS Version: '17.1-20200726-UNOFFICIAL-'
    07-26 09:43:33.173  4227  4227 F DEBUG   : Build fingerprint: 'samsung/gta3xlwifixx/gta3xlwifi:10/QQ3A.200705.002/eng.robo.20200725.212218:userdebug/test-keys'
    07-26 09:43:33.173  4227  4227 F DEBUG   : Revision: '4'
    07-26 09:43:33.173  4227  4227 F DEBUG   : ABI: 'arm64'
    07-26 09:43:33.174  4227  4227 F DEBUG   : Timestamp: 2020-07-26 09:43:33-0400
    07-26 09:43:33.174  4227  4227 F DEBUG   : pid: 4222, tid: 4222, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
    07-26 09:43:33.175  4227  4227 F DEBUG   : uid: 1000
    07-26 09:43:33.175  4227  4227 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
    07-26 09:43:33.175  4227  4227 F DEBUG   : Abort message: 'couldn't find an OpenGL ES implementation, make sure you set ro.hardware.egl or ro.board.platform'
    07-26 09:43:33.175  4227  4227 F DEBUG   :     x0  0000000000000000  x1  000000000000107e  x2  0000000000000006  x3  0000007fdb9ded80
    07-26 09:43:33.175  4227  4227 F DEBUG   :     x4  fefeff75deeed027  x5  fefeff75deeed027  x6  fefeff75deeed027  x7  7f7f7f7fffffff7f
    07-26 09:43:33.175  4227  4227 F DEBUG   :     x8  00000000000000f0  x9  5684f34d959e7fdc  x10 0000000000000001  x11 0000000000000000
    07-26 09:43:33.175  4227  4227 F DEBUG   :     x12 fffffff0ffffffdf  x13 ffffffffffffffff  x14 0000000000000004  x15 ffffffffffffffff
    07-26 09:43:33.175  4227  4227 F DEBUG   :     x16 00000076dfbd18c0  x17 00000076dfbaf3b0  x18 00000076e1ade000  x19 000000000000107e
    07-26 09:43:33.175  4227  4227 F DEBUG   :     x20 000000000000107e  x21 00000000ffffffff  x22 0000000000000000  x23 00000076dfecd0cb
    07-26 09:43:33.175  4227  4227 F DEBUG   :     x24 00000076e1390020  x25 00000076e035a098  x26 00000076e0357028  x27 0000000000000001
    07-26 09:43:33.175  4227  4227 F DEBUG   :     x28 0000000000000001  x29 0000007fdb9dee20
    07-26 09:43:33.175  4227  4227 F DEBUG   :     sp  0000007fdb9ded60  lr  00000076dfb62f48  pc  00000076dfb62f74
    07-26 09:43:33.193  4227  4227 F DEBUG   : 
    07-26 09:43:33.193  4227  4227 F DEBUG   : backtrace:
    07-26 09:43:33.193  4227  4227 F DEBUG   :       #00 pc 0000000000081f74  /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: bf14cf7a62d1f91755beddd4a937354d)
    07-26 09:43:33.193  4227  4227 F DEBUG   :       #01 pc 00000000000089f8  /system/lib64/liblog.so (__android_log_assert+324) (BuildId: fa7cbba17f5086fc8671eb6757477dd0)
    07-26 09:43:33.193  4227  4227 F DEBUG   :       #02 pc 0000000000025600  /system/lib64/libEGL.so (android::Loader::open(android::egl_connection_t*)+1020) (BuildId: 8e88ab543c9573b9c0f7e94de5c7c70b)
    07-26 09:43:33.193  4227  4227 F DEBUG   :       #03 pc 000000000001c4d4  /system/lib64/libEGL.so (android::egl_init_drivers()+88) (BuildId: 8e88ab543c9573b9c0f7e94de5c7c70b)
    07-26 09:43:33.194  4227  4227 F DEBUG   :       #04 pc 000000000001c770  /system/lib64/libEGL.so (eglGetDisplay+56) (BuildId: 8e88ab543c9573b9c0f7e94de5c7c70b)
    07-26 09:43:33.194  4227  4227 F DEBUG   :       #05 pc 000000000011663c  /system/lib64/libsurfaceflinger.so (android::renderengine::gl::GLESRenderEngine::create(int, unsigned int, unsigned int)+64) (BuildId: 96b996cfa12bca08accd8031151ec993)
    07-26 09:43:33.194  4227  4227 F DEBUG   :       #06 pc 00000000001164c4  /system/lib64/libsurfaceflinger.so (android::renderengine::RenderEngine::create(int, unsigned int, unsigned int)+164) (BuildId: 96b996cfa12bca08accd8031151ec993)
    07-26 09:43:33.194  4227  4227 F DEBUG   :       #07 pc 00000000000d066c  /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::init()+184) (BuildId: 96b996cfa12bca08accd8031151ec993)
    07-26 09:43:33.194  4227  4227 F DEBUG   :       #08 pc 00000000000031bc  /system/bin/surfaceflinger (main+364) (BuildId: b78b8993428f334aea26a30d4e6545bc)
    07-26 09:43:33.194  4227  4227 F DEBUG   :       #09 pc 000000000007d780  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: bf14cf7a62d1f91755beddd4a937354d)

    I tried setting the `ro.hardware.egl=mali` prop just in case, but I think this is because it's 64bit looking in `/vendor/lib64/egl` only.

    I have the 32-bit version of the lib:
    Code:
    /media/robo/vendor/lib/egl/libGLES_mali.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[md5/uuid]=1828d04d5fa0d90064b37369e8a99cb5, stripped
    from the stock vendor image, but there's no `lib64` directory in /vendor at all...

    I don't suppose there's some magic setting or prop I can change to have it load 32-bit libs instead?