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

[Magendanz]

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 16.0 I just created based on the latest OEM firmware and @AndyYan's latest LineageOS 16.0 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.

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 February 2020 Update (T510XXS3ATB4).
• Stock recovery will be replaced with my latest TWRP build for the SM-T510..
• This is built with root support (enabled in Developer Options). To remove (and enable vendor spoofing), just run "/system/bin/phh-securize.sh" with root access.
• 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-16.0-20200422-UNOFFICIAL-T510XXS3ATB4.tar.md5 (Odin tarball)
• lineage-16.0-20200422-UNOFFICIAL-T510XXS3ATB4.zip (TWRP update)

Change Log:
20200422:

• New private build of LineageOS GSI with April 2020 Security Patch.
• Updated to the OEM T510XXS3ATB4 kernel and vendor partition.

20200405:

• Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
• Fixed crash on first two attempts to launch Phh Treble Settings.
• New private build of LineageOS GSI with the above fixes (#663 & #1228).

20200324:

• New LineageOS GSI build of treble_a64_bvN target with March 2020 Security Update.
• Switched to ext2simg for sparse image conversion to improve Odin compatibility and reduce download size.
• Updated to T510XXS2ASK5 kernel (November 2019 Update)

20200308:

• MTP file transfers should now work even with USB Debugging disabled.
• Charging after full shutdown will no longer hang during level-of-charge animation.
• Updated to T510XXS2ASK1 kernel (November 2019 Update)

20191019:

• Initial release based on lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN

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
• Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
• Tap Install, select your update (.zip file), and then swipe to install
• Reboot to system

Source:

• android_device_samsung_gta3xlwifi
• treble_build_los
• Phh-Treble
• treble_build_los

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!

 

[AndyYan]

Leaving my own donation link here if anyone's feeling like it: https://paypal.me/AndyCGYan

One thing to note: LineageOS includes LiveDisplay and Night Light which affect the tone of the display (I like colder displays), but on this device both features lag the UI horribly, probably due to lack of HW acceleration. In this case, try the build.prop trick here to make things perceptibly smooth.

 

[uknetfreak]

Gapps?

Thanks for this great ROM. I have managed to get it installed on my Black Friday purchased device. However, it would appear no to come with any Google stuff (which I would expect). Normally I would install from OpenGapps but it don't think any of those of suitable. Can anyone advise me what would be suitable. I was looking for the equivalent of the Full package on OpenGapps.

 

[Magendanz]

Can anyone advise me what would be suitable. I was looking for the equivalent of the Full package on OpenGapps?.

Check out my Nexus Stock ROM.

 

[Minekim09]

ahhhh how to install.. im first rooting,....(for galuxy tab a 10.1 rooting tutorial)

 

[Laykun]

#EDIT, wrong ROM

 

[sc00bied00]

Fairly certain I followed all the steps but it has been a very long time since I've used Odin. Here's the failure log. Any idea where I'm going wrong? Tried running Odin as Administrator, same results. Thanks in advance for any help.


edit: Just tried your Nexus ROM and same results





<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1487 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> product.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

 

[demoneg]

Works like charm! thank you so much for the great work, are you going to release TWRP zip update files for coming version? also any idea why the tablet can't be encrypted? on other note, gsmarena mention that the CPU is Exynos 7904, which is not correct, mine is Exynos 7885! which isn't 64bit as far as I can tell, any idea of there was some versions with Exynos 7904 released?

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 16.0 I just created based on the September 2019 Update and @AndyYan's latest LineageOS 16.0 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.

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 September 2019 Update (T510XXU2ASI4).
• 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:

• Double-tap to wake
• Support for file-based encryption
• MTP only works when USB Debugging is enabled
• Charging after full shutdown will hang during level-of-charge animation.

Downloads:

• lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5

Change Log:
20191019:

• Initial release based on lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN

Instructions:

• Unlock bootloader
• Hold Vol Up & Vol Down buttons during restart to enter Download mode
• Install custom ROM to AP with Odin
• When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
• Reboot to system

Source:

• android_device_samsung_gta3xlwifi
• treble_build_los
• Phh-Treble
• treble_build_los

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!

---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------

Had some issues with TWRP, turned out to be a bad cable, was crashing with Odin and heimdall on Linux, but at 85% changed the cable and everything worked fine also not USB-C to USB-C cable in my case it had to be USB-A to USB-C cable.

Fairly certain I followed all the steps but it has been a very long time since I've used Odin. Here's the failure log. Any idea where I'm going wrong? Tried running Odin as Administrator, same results. Thanks in advance for any help.


edit: Just tried your Nexus ROM and same results





<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1487 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> product.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

 

[Hypfer]

Hi

I've flashed this Rom yesterday and it does seem to work relatively well.
There are some issues, though. Mostly stability. Also the Tablet thinks that it is a phone. How do I tell it that it's a Tablet?

So.. where do we go from here? What are the next steps? How is this Rom built? What is the process to build it?

Regards

 

[sc00bied00]

Had some issues with TWRP, turned out to be a bad cable, was crashing with Odin and heimdall on Linux, but at 85% changed the cable and everything worked fine also not USB-C to USB-C cable in my case it had to be USB-A to USB-C cable.

Just tried with a brand new C -> A cable plugged into a USB 2.0 port and same error. I was originally using the cable that came with the tablet. Not sure what to try next.

 

[whoiswes]

Just tried with a brand new C -> A cable plugged into a USB 2.0 port and same error. I was originally using the cable that came with the tablet. Not sure what to try next.

I ran into this (the Odin error on product.img) on the 2 T510's I picked up for my kiddos. Both were initially running the November update, and both upon first boot and setup patched to the December update (this was before I realized there was a Lineage build available).

I was able to successfully flash this build by first downgrading to the September Samsung release (T510XXU2ASI4). I just pushed that through Odin, and immediately entered download mode again post-install, and then install Lineage without an issue. This worked on both of the tablets I have.

I ended up paying for a 3 day pass on samfrew.com because the download speeds are horribly crippled. I would be happy to upload/host the OEM firmware files somewhere to help others if it's not against the rules.

 

[sc00bied00]

I was able to successfully flash this build by first downgrading to the September Samsung release (T510XXU2ASI4). I just pushed that through Odin, and immediately entered download mode again post-install, and then install Lineage without an issue. This worked on both of the tablets I have.

OK, that's odd. I bought this one at Costco about a month ago and it shipped with and factory resets to September AS14 :/
I'd already downloaded that rom from samfrew and even tried to flash it after both this and the Nexus ROMS failed. Same results as those two and failed with the same error at product.img
I wonder if I'll need to roll back to an even earlier one, or would loading a ROM earlier than what's in the recovery be a bad thing?
FWIW, in order to unlock the bootloader I went through the "disable auto-updates, auto time adjust, set the time to the past/future manually" trick.

 

[whoiswes]

OK, that's odd. I bought this one at Costco about a month ago and it shipped with and factory resets to September AS14 :/
I'd already downloaded that rom from samfrew and even tried to flash it after both this and the Nexus ROMS failed. Same results as those two and failed with the same error at product.img
I wonder if I'll need to roll back to an even earlier one, or would loading a ROM earlier than what's in the recovery be a bad thing?
FWIW, in order to unlock the bootloader I went through the "disable auto-updates, auto time adjust, set the time to the past/future manually" trick.

Odd. I didn't have any issues with applying the ASI4 updates (just the BG, AP, and CSC files) with Odin 3.14.1. I don't think OEM unlocking comes into play for this part.

What "KG STATE" in download mode showing? Prenormal means the knox protection got tripped which is probably (part of?) your issue. I can't say more because I honestly don't know (first Samsung device since the Galaxy Nexus). If you're at ASI4, and download mode shows KG STATE: checking, then you're in the same place I was for a successful flash of Lineage.

Sorry I can't be of more help.

 

[sc00bied00]

Whelp, thar's mah problem. KG state is Prenormal. No idea how I tripped it but this is my first sammy since the S2. I'll start googling and would welcome any advice on what to do to get to a better state.

Thanks! At least now I know what's borked :/


EDIT [SOLVED]: The clue was in Menendez's reply in post #6 of MossyT's guide where he indicates that wifi should be enabled on the restart immediately after the Volume Up long press to unlock, thus revealing OEM Unlock in developer options. The very first go around, I was able to see the option and must have borked a stdep before or during Odin. All subsequent attempts after doing factory resets, I failed to activate wifi on first boot and went straight to Odin. Until the OEM rom can phone home, KG will remain 'prenormal'. Simply turning wifi on and verifying OEM Unlock in devops, KG changed to 'checking' and the flash went through fine.
Thanks for pointing me in the right direction. My daily drivers are a Moto G5+ and X so I'm a bit rusty at the "samsung way"

 

[dussl]

Any Chance to get double tap to wake (dt2w) running?

There seems to be a solution:
github.com /phhusson/treble_experimentations/issues/663

 

[Hypfer]

Any Chance to get double tap to wake (dt2w) running?

There seems to be a solution:
github.com /phhusson/treble_experimentations/issues/663

For now you can flash magisk and run those commands via adb as root on each reboot.

I suppose at some point we either fix the init.rc or phh extends the phh treble app to also run the connection check command.

 

[dcillusions77]

Is this ROM still being updated or worked on? Just curious been 2 months and nothing from the OP. Thanks.

 

[Crashogre]

I am on T510xxu1ASEF. Am I correct to assume I need to upgrade the Firmware to the september release and then install the rom? Or is it as simple as flashing the new rom? I have unlocked the bootloader and have stopped until I find out what to do.


Edited because I'm an idiot and kept saying kernel when obviously the file I downloaded from Samsung was full rom not just kernel.

 

[Magendanz]

Is this ROM still being updated or worked on? Just curious been 2 months and nothing from the OP. Thanks.

I'll update it with the latest kernel source when I get back from holiday, but I wouldn't expect much because there haven't been any GSI updates from @AndyYan.

 

[dcillusions77]

I'll update it with the latest kernel source when I get back from holiday, but I wouldn't expect much because there haven't been any GSI updates from @AndyYan.

Ok thanks for all your work much appreciated