[ROM][SM-T510][UNOFFICIAL] LineageOS 18.1 for Galaxy Tab A 10.1 (2019) - Samsung Galaxy Tab A series ROMs, Kernels, Recover

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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:
lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2.tar.md5 (Odin tarball)
lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2.zip (TWRP update)
Build archives:
Android File Host
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:
Initial release based on lineage-17.1-20200227-UNOFFICIAL-treble_a64_bvN
MTP file transfers no longer require USB Debugging to be enabled.
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:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
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!

---

Does the ethernet-function (LAN) work?

---

When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?

---

andreasoz said:
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
Click to expand...
Click to collapse
Yes, I've noticed that myself, and it seems to occur when writing to certain modified vendor partitions. Anyone have an idea of what might cause that?

---

Magendanz said:
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
When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Click to expand...
Click to collapse
Hiya
Just got this device today.. pretty stoked to get it rooted & Lineage going.. thanks for your projects & info
I'm curious do I need to change any of the Options tab in Odin ?
Auto Reboot off for example ?
Auto Reboot & F. Reset Time are checked by default none of the others are.
At this point in this device's progress assuming I unlocked correctly & get into Download mode.. flash with Odin successfully I should just Auto Reboot right into TWRP & can go from there ?
NoKnox is a thing of the past ?
What about Multi-disabler ?
If I install Magisk & plan to how do I ensure I don't "boot outside Magisk" I keep hearing people say.. where Vaultkeeper & similar things may become problematic or so I've read.
Someone did offer some advice on not booting outside Magisk a few weeks ago I'm going to go find their message too but yeah I've read a lot of threads here & it seems like since certain packages & older methods like patching TWRP with Magisk are things of the past.. I just want to confirm what all else is
is charging past 80% an issue at all with this ROM ?
That's one thing I see people mention about custom kernels is they fix that.. well that & EX or Franco would be rad if they exist for this device & rom
/salute

---

jaladhjin said:
I'm curious do I need to change any of the Options tab in Odin ? Auto Reboot off for example ?
Click to expand...
Click to collapse
Nope.
jaladhjin said:
NoKnox is a thing of the past ?
Click to expand...
Click to collapse
Yep.
jaladhjin said:
What about Multi-disabler ?
Click to expand...
Click to collapse
You still need to run Multi-disabler if you're installing TWRP, but it's baked into this custom ROM.
jaladhjin said:
is charging past 80% an issue at all with this ROM ?
Click to expand...
Click to collapse
No longer an issue with this custom kernel.
jaladhjin said:
If I install Magisk...
Click to expand...
Click to collapse
I don't use Magisk, and so I'm really not the person to ask. Note, however, that custom kernels in boot and recovery partitions are slightly different wrt MTP. Boot kernel uses Google MTP and recovery one uses Samsung MTP to maintain compatibility with OEM system if patched with Magisk.

---

Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.
Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.
andreasoz said:
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
Click to expand...
Click to collapse
OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
https://sourceforge.net/projects/opengapps/files/
https://www.cyanogenmods.org/downloads/bitgapps-for-android-10-download/

---

I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"
I cannot get back into lineage any advice?
I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more

---

Warrenchild said:
I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"
I cannot get back into lineage any advice?
I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more
Click to expand...
Click to collapse
Did you re-enable Developer mode and OEM?

---

lewmur said:
Did you re-enable Developer mode and OEM?
Click to expand...
Click to collapse
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
I even downgraded to sk1 and then let it do a OTA update while locked

---

Warrenchild said:
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
I even downgraded to sk1 and then let it do a OTA update while locked
Click to expand...
Click to collapse
I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.
edit: The original instruction are a little confusing. They tell you that after each step you have to boot and enable Dev mode in order to chech OEM enable. The real reason is that you have to enable Dev mode in order to flash anything but stock. Without it enabled, you get the message in red saying that only original firmware can be installed.

---

lewmur said:
I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.
Click to expand...
Click to collapse
I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.
Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
Error : "only official released binaries are allowed to be flashed(BOOT)"
and the flash stalls out on odin.
So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.

---

Warrenchild said:
I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.
Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
Error : "only official released binaries are allowed to be flashed(BOOT)"
and the flash stalls out on odin.
So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.
Click to expand...
Click to collapse
Did you read my "edit" where I said that was caused by not having enable Developer mode?

---

lewmur said:
Did you read my "edit" where I said that was caused by not having enable Developer mode?
Click to expand...
Click to collapse
I did not see your edit, thank you I will try and inform the community.

---

installing
BiTGApps-arm-10.0.0-R1_signed
BiTGApps-arm-10.0.0-v0.2_signed
open_gapps-arm-10.0-pico-20200219
open_gapps-arm-10.0-nano-20200305
with twrp will force reboot while installing
what maybe not work is miracast/widi. i can't find my tv with my tab.
phh-treble entry in settings does nothing / does not open.
(both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])

---

[email protected] said:
installing
BiTGApps-arm-10.0.0-R1_signed
BiTGApps-arm-10.0.0-v0.2_signed
open_gapps-arm-10.0-pico-20200219
open_gapps-arm-10.0-nano-20200305
with twrp will force reboot while installing
what maybe not work is miracast/widi. i can't find my tv with my tab.
phh-treble entry in settings does nothing / does not open.
(both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])
Click to expand...
Click to collapse
Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.

---

lewmur said:
Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.
Click to expand...
Click to collapse
my mi a1 with stock pie and the t510 stock rom still can use it

---

[email protected] said:
my mi a1 with stock pie and the t510 stock rom still can use it
Click to expand...
Click to collapse
Maybe so. But it isn't officialy supported, so if it doesn't work, it doesn't work. I tried it with several apps on several ROMs and could only get it work on my T580 by reverting to an Android 8. Every thing I tried in Pie either froze or caused the tablet to reboot.

---

Warrenchild said:
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
Click to expand...
Click to collapse
You triggered Samsung's VaultKeeper "feature" when you rolled back to the OEM firmware. In order to prevent that, you need to immediately enable Developer Options while connected to the Internet after setup (before rebooting). If you don't, VaultKeeper places the device in a hybrid state where it looks like the bootloader is still unlocked, but it still won't allow Odin to flash firmware unless it's signed with Samsung's release keys.
Flashing a known-good OEM firmware should remedy the problem, provided you verify that the OEM Unlocking setting is enabled in Developer Options and go back for a Volume Up long press from the blue warning screen to complete the bootloader unlock. Did you do that after booting while holding the Volume Up & Down with the USB cable attached?

---

betacrypt said:
Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.
Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.
OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
https://sourceforge.net/projects/opengapps/files/
https://www.cyanogenmods.org/downloads/bitgapps-for-android-10-download/
Click to expand...
Click to collapse
No luck for me with this, TWRP still reboots when trying to install gapps/bitgapps . I'm not sure what else to try.