[ROM][9.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510] - 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/T515], here's one I just created based on the September 2019 Update and @AndyYan's 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 may require 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 November 2019 Update (T510XXS3ATB4) for the SM-T510.
The system is based on @AndyYan's LineageOS 16.0 GSI with the latest Stock variant from OpenGApps.
Boot logo and default wallpaper is from my Nexus series of custom ROMs for Android TV, and I'm using the Pixel boot animation with black background.
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
I've dialed back most of scary bootloader warnings and Knox Security branding from the boot sequence.
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:
SM-T510:
Nexus_Stock_LP_T510XXS3ATB4-20200422.tar.md5 (Odin tarball)
Nexus_Stock_LP_T510XXS3ATB4-20200422.zip (TWRP update)
SM-T515:
No longer supported (since I don't have hardware for testing), but archives are posted here.
Change Log:
20200422:
New private build of LineageOS GSI with April 2020 security patch.
Updated to T510XXS3ATB4 kernel and vendor partition (February 2020 Update)
Updated to latest OpenGApps (20200422), with private fix for Chrome issue.
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).
Updated to latest OpenGApps (20200404), with private fix for Chrome issue.
20200325:
Switched back to Pixel Launcher updated with Nexus tablet device profiles.
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 OpenGApps 20200311. (Subsequent builds have issues.)
20200308:
Charging after full shutdown will no longer hang during level-of-charge animation.
MTP file transfers no longer require USB Debugging to be enabled.
Updated to T510XXU2ASK5 kernel (November 2019 Update)
Updated to latest OpenGApps (20200307)
20200103:
Updated to T510XXS2ASK1 kernel (November 2019 Update)
Updated to latest OpenGApps (20200103)
20191109:
USB Debugging is enabled by default (MTP workaround)
SurfaceFlinger optimization to improve scrolling performance
Updated to latest OpenGApps (20191109)
Now building TWRP update (.zip file)
20190922:
Switched from AOSP base to LineageOS.
Updated to latest OpenGApps (20191022)
20190921:
Updated to T510XXU2ASI4 kernel and TWRP v3.3.1-5..
20190909:
Scoped MTP fix more tightly, preventing charging cap at 79%.
20190906:
Fixed MTP support, so you can now transfer files easily via USB.
20190828:
Google Play Protect now plays nice. You no longer have to register your GSF ID. (Thanks, @phhusson!)
Removed DeviceID app, since it's now unneeded.
20190825:
AOSP 9.0 v119
Updated to TWRP 3.3.1-2
Restored some security features to custom kernel
20190810:
AOSP 9.0 v117
August security patch
Nexus default wallpaper
20190629:
Initial release based on AOSP 9.0 v114
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, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gta3xlwifi
android_device_samsung_gta3xl
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!

---

Oo our first custom rom!! Thanks alot!! Cant wair to try it soon

---

Important Note: The Night Mode setting in Developer Options is set to "Always off" by default. Don't change it! When I set it to "Automatic (based on time of day)", the screen went black and I couldn't recover without a factory reset. (I'm assuming that this was a bug in SystemUI.apk.)

---

Thanks for the effort and time you've put into this.
Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.

---

NightHawkUndead said:
Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.
Click to expand...
Click to collapse
Well, I just verified the MD5s and they match. However, to be a little more squared away, I replaced the original .tar file that I uploaded with a .tar.md5 (a.k.a. "tarball) which has the MD5 footer that Odin can use to verify the file integrity. I've also compressed the contents with LZ4, which cut the size down by a third.
Installing the new tarball with Odin3 v3.13.3 on my tablet went smoothly, so I hope this works for you.

---

Finally got it to work. Had to flash back to stock. Wipe. Then immediately reboot bootloader again and flash Rom.
How do I go about rooting now?
Edit: nevermind, got it rooted. Everything is working fine now!
Sent you a donation for your work. ? ?

---

I have a new SM-T510 on T510XXU1ASEF
I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.
Tried to flash 3 times, same result.
Is there something to going back to stock, wiping, bootloader, flash again? Or is that just doing things until it works?

---

garyemiller said:
I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.
Click to expand...
Click to collapse
It's important that you wipe the data partition before TWRP boots, since it currently hangs when it encounters an encrypted file system. (Yes, this really shouldn't happen, but I haven't found a fix for that TWRP bug yet.)
Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM?

---

"Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM? "
Yes.
I got it to work. reinstalled stock rom (link above). Booted it stock. Enabled Developer Mode, Enabled USB debugging. confirmed OEM still unlocked. Boot to recovery, wipe, boot to bootloader. Flash this ROM with Odin3. reboot. All is well.
So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.
Along the way I also wasted a lot of time trying to flash with heimdall 1.4.2. But that was very flakey. Odin3 just worked.
---------- Post added at 08:46 PM ---------- Previous post was at 08:23 PM ----------
I guess I should mention my biggest issue was unlocking the bootloader. Not like before.
Power off. Hold Vol UP and Vol Down. Plug in USB. Long press Vol UP to unlock.

---

garyemiller said:
So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.
Click to expand...
Click to collapse
If you install Magisk, you might not have to do the device certification dance. It tries to fake out Play Protect.

---

The device certification was painless. I've doe that before on other devices.
Rooting with Magisk was also painless:
Grab boot.img from your tarball.
adb push boot.img /storeage/emulated/0/Download
patch using Magisk Manager
adb pull /storage/emulated/0/Download/magisk_patched.img .
heimdall flash --BOOT magisk_patched.img
I can't get SafetyNet to pass, even with Magisk SafetyPatch module. But not a big deal to me.
Is there a way to turn off the google page on the launcher?
Thanks for the nice ROM! So much better than stock.
I'm still looking for a good ad blocker for Pie. Up tile now I have used a Raspberry Pi as a dnsmasq server for ad blocking.

---

garyemiller said:
Is there a way to turn off the google page on the launcher?
Click to expand...
Click to collapse
If you open up the Android One Launcher settings, there's a "Display Google app" option that you can disable.
garyemiller said:
I can't get SafetyNet to pass, even with Magisk SafetyPatch module..
Click to expand...
Click to collapse
Yeah, I've tried the usual tricks like spoofing the fingerprint, but that didn't work either. This kind of hard Play Protect device rejection seems to happen for me whenever the vendor partition is using release keys and the system partition is using test keys.
I haven't found an XDA thread yet that really provided deep insight into the algorithm that Google uses for Play Protect and SafetyNet. And given the proprietary nature of what it's doing, we may never get it. I think our best long-term solution is to get LineageOS 16 builds that pass CTS testing, but we may have to scrounge for 64-bit drivers.

---

I just went with Nova Launcher. It has been good to me.
I can wait for Lineage to catch up. I'm happy to be rid of bloatware. And with root I can block ads and my firewall works.
Thanks for the ROM! I'm happy!

---

ankh_hikes said:
Which stock files do I need to replace the nexus boot splash screens? I would like have the Samsung ones.
Click to expand...
Click to collapse
Just restore the original param image. (But seriously, why would you? The stock boot splash is ugly! )

---

Just ordered my T510, can't wait to try this out when it arrives

---

d4dave said:
Just ordered my T510, can't wait to try this out when it arrives
Click to expand...
Click to collapse
The 3G/128G config was selling for just $250 USD through Costco until a few days ago. That's a pretty insane value....as long as you aren't stuck with Samsung's One UI, that is.

---

will there be a new release coming?

---

DarthGW said:
will there be a new release coming?
Click to expand...
Click to collapse
Yes, I'm trying to build an unofficial LineageOS 16.0 release, but am struggling with some build issues. The primary goal is to deal with the Play Protect device certification (but I definitely won't pass SafetyNet). Eventually, I'll also get to fixing MTP.

---

wow dude, thanks a lot for you work

---

Is it possible to install this on the 510 with Product code NEE
PDA T510XXU1ASF2
CSC T510OXM1ASF3
It's the stock may Nordic firmware