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

Search This thread
Is there currently a solution how to install 18.1 more or less reliably?
I don't mean to be rude, but Spezialzt is correct. You don't have to read all 31 pages, there is information that might help on this very page. Did your read any of it? Did you try some of the things suggested?

As the old saying goes, the forum helps those that help themselves. We'll help where we can, but we can't install it for you.

So to answer your question....

Is there currently a solution how to install 18.1 more or less reliably?

Yes! LOS 18.1 installs as reliably as the user installing it 🔧
 

FA21

Member
Jan 8, 2021
11
3
I tried to upgrade from LOS 17.1 to 18.1 via TWRP within the release of Magendanz. Unfortunately didn't work. I ended up in a bootloop. Even LOS hasn't even started yet. Via Vol Up + Down and plugging in the USB cable at the same time, I was able to get into Download Mode. There I had also tried unsuccessfully to flash with Odin 18.1. I then flashed the stock rom which worked. However, I don't want to use the stock ROM. Is there currently a solution how to install 18.1 more or less reliably?

I misunderstood about the "incremental upgrade" and assumed it also works for an upgrade from 17.1 to 18.1. This had officially worked with an official version on another device. I don't do this every day. error and misunderstanding. Better read the thread next time.

I was finally able to solve my problem.
For this I installed the latest Samsung firmware (that was meant with the CVB1) with Odin from samfw.com (model code: SM-T510), as was also discussed here before (selected my country; didn't use Home CSC, but all the three other child files of CVB1 after unzip).

After that I wanted to install LOS18.1 from Magendanz with Odin.
That didn't work at first because the bootloader had caused problems. I then "factory reset" the (stock) device and connected it to the WLAN during setup, so that the "OEM Unlock" field was there again. USB debugging on and after that I was able to install Magendanz 18.1 as mentioned above.
 
  • Like
Reactions: spezialzt

riverstyxxx

Senior Member
May 9, 2015
152
18
"This device isn't play protect certified" error. This after I flashed the stock rom/kernel, then lineage, then open gapps pico. Registered the google services framework id, still doesn't work. My device shows up as "Phh-Treble vanilla".
 

acura4ever

Member
Aug 16, 2011
6
0
"This device isn't play protect certified" error. This after I flashed the stock rom/kernel, then lineage, then open gapps pico. Registered the google services framework id, still doesn't work. My device shows up as "Phh-Treble vanilla".
I got it working but don't know the good sequence.

I many problem with google apps crashing and loop This device isn't play protect certified.

I already register it on the website.

I reinstall the OS with Odin and the google apps nano 20220110 and magisk. Suddenly afterward, was OK.

Anyway, I'm not touching it anymore.
 

gambaaa

Senior Member
May 18, 2015
63
10
I love this ROM.
A little issue I have, maybe it's on my end but whenever I shutdown my tablet and connect it to a charger. It automatically boots it. Unsure what it is but shutting down the tablet works great but as soon as I connect it, instead of having the boot charging logo, it boots it.
Any insight? Thank you!
 
  • Like
Reactions: keithgravylewis

acura4ever

Member
Aug 16, 2011
6
0
I love this ROM.
A little issue I have, maybe it's on my end but whenever I shutdown my tablet and connect it to a charger. It automatically boots it. Unsure what it is but shutting down the tablet works great but as soon as I connect it, instead of having the boot charging logo, it boots it.
Any insight? Thank you!
The issue is documented on the 1st post. Same problem here maybe in the next update. Everything else works great. I can now use the sd card and extend it as system storage.
 

Magendanz

Senior Member
Mar 25, 2008
906
923
Issaquah, WA
www.Vote4Chad.com
New drop is posted below. I have noticed an instability with this build when both MTP (file sharing) and ADB (USB debugging) are active, sometimes resulting in an unexpected restart. They seem to work fine separately, though.

Downloads:
Change Log:
20220907:
  • Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
  • Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
  • Update to TWRP v3.6.2 custom recovery on AOSP 11.
 
Last edited:
New drop is posted below. I have noticed an instability with this build when both MTP (file sharing) and ADB (USB debugging) are active, sometimes resulting in an unexpected restart. They seem to work fine separately, though.

Downloads:
Change Log:
20220907:
  • Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
  • Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
  • Update to TWRP v3.6.2 custom recovery on AOSP 11.
I updated to this build and received the google play services error. I tried recertifying the device and see that the Device ID is blank. GSF is empty on Device ID app. Any suggestions? I don't want to reset the device if there is an easier option to fix.

Edit 1: Got it working by reinstalling GApps
 
Last edited:
  • Like
Reactions: Magendanz
Mar 10, 2018
5
0
I love this ROM.
A little issue I have, maybe it's on my end but whenever I shutdown my tablet and connect it to a charger. It automatically boots it. Unsure what it is but shutting down the tablet works great but as soon as I connect it, instead of having the boot charging logo, it boots it.
Any insight? Thank you!
Same here. I really hope this gets resolved asap. Do you also find it takes forever to charge it too or is this just me? Other than this, its the best rom for this tablet. SM T510.

I also try to install lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2 . It installs on twrp (my version is 3.3.1-1) but it doesn't install when rebooted and the only error says install successful then unable to mount storage.

When I boot it back up the build is RQ3A.211001.001 ENG.CROSSG.20220715.011912 TEST KEYS.
 
Last edited:

Magendanz

Senior Member
Mar 25, 2008
906
923
Issaquah, WA
www.Vote4Chad.com
Same here. I really hope this gets resolved asap.
I spent days trying to get the Lineage GSI charge mode or Samsung's low-power mode (lpm) working on this ROM, and it just wasn't happening. My workaround was to simply to have the charger service do a regular reboot, which is much like how iPhones work.

It's not ideal, but there's also a point of diminishing returns and I was well past that point.

If you want to see it's natural state, just remove my /system/ext/init/off_mode_charge.rc file. If I recall, it was hanging the device.
 
  • Like
Reactions: keithgravylewis
Mar 10, 2018
5
0
Thank you for getting back to me and with those details.

At least you've tried. I'm grateful for the rom regardless thanks for your efforts 👍
 

Zherot1

New member
Apr 17, 2020
1
1
Hi guys,

For those who have the issue "Device Isn't Play Protect Certified" and cannot use Play Store, this solution worked for me on the first try:


(I did not install firefox, just used the already pre-installed browser).

By the way, thank you for this amazing rom!!!
 
  • Like
Reactions: Magendanz

morgads

Member
Nov 30, 2005
15
0
The lack of support for mixed WPA2/WPA3 networks is obviously not ideal, but I have had limited success with this ROM by temporarily setting my network to WPA2 only, connecting the tablet, and then switching it back to WPA2/WPA3 mixed mode. So far so good.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    New drop is posted below. I have noticed an instability with this build when both MTP (file sharing) and ADB (USB debugging) are active, sometimes resulting in an unexpected restart. They seem to work fine separately, though.

    Downloads:
    Change Log:
    20220907:
    • Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
    • Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
    • Update to TWRP v3.6.2 custom recovery on AOSP 11.
    1
    New drop is posted below. I have noticed an instability with this build when both MTP (file sharing) and ADB (USB debugging) are active, sometimes resulting in an unexpected restart. They seem to work fine separately, though.

    Downloads:
    Change Log:
    20220907:
    • Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
    • Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
    • Update to TWRP v3.6.2 custom recovery on AOSP 11.
    I updated to this build and received the google play services error. I tried recertifying the device and see that the Device ID is blank. GSF is empty on Device ID app. Any suggestions? I don't want to reset the device if there is an easier option to fix.

    Edit 1: Got it working by reinstalling GApps
    1
    Same here. I really hope this gets resolved asap.
    I spent days trying to get the Lineage GSI charge mode or Samsung's low-power mode (lpm) working on this ROM, and it just wasn't happening. My workaround was to simply to have the charger service do a regular reboot, which is much like how iPhones work.

    It's not ideal, but there's also a point of diminishing returns and I was well past that point.

    If you want to see it's natural state, just remove my /system/ext/init/off_mode_charge.rc file. If I recall, it was hanging the device.
    1
    Hi guys,

    For those who have the issue "Device Isn't Play Protect Certified" and cannot use Play Store, this solution worked for me on the first try:


    (I did not install firefox, just used the already pre-installed browser).

    By the way, thank you for this amazing rom!!!
  • 30
    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 11 release (T510XXU5CVG2).
    • 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:
    20220907:
    • Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
    • Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
    • Update to TWRP v3.6.2 custom recovery on AOSP 11.
    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.
    4
    New drop is posted below. I have noticed an instability with this build when both MTP (file sharing) and ADB (USB debugging) are active, sometimes resulting in an unexpected restart. They seem to work fine separately, though.

    Downloads:
    Change Log:
    20220907:
    • Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
    • Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
    • Update to TWRP v3.6.2 custom recovery on AOSP 11.
    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?