[ROM][11.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510]

Search This thread

rw_on_xda

Senior Member
Jun 24, 2013
404
228
Berlin
Where did you get that?
caos is here (but it's also outdated regarding samsung security patches)

I see 20220219 on the OP.
yup, the last nexus.
don't know if @Magendanz is working on a new nexus, but if so I guess it would contain android 12.
caos v316 is still android 11 and doesn't contain the last samsung security patches

I was looking for an updated ROM to match the current kernel and security patches.
best offer for your claims might be Quack Phh-Treble

I successful installed with the above TWRP AOSP 12.1 v414 (what is android 12)
see comment #1,515.

AFAIK, july security patch are in AOSP 12.1 v415 only (a PreRelease !!!)

but I reinstalled the above caos, cause I had some trouble with some apps I use.
Background was: the apps were outdated, what I realized later foremost after the switch
caos v316 has:
security patches are from Feb 2022
kernel is 4.4.177-22626479


caos and Quack Phh-Treble are coming in different flavors and might be different from nexus, what I currently don't use cause of too much google stuff active I don't want/need.

another option could be:

IIRC, @Magendanz is working on /will release soon a rom based on Andy Yan's LOS 19.x.
don't know what the currently samsung security patch state is ..., but LOS 19.x is android 12
 
Last edited:

Magendanz

Senior Member
Mar 25, 2008
941
974
Issaquah, WA
www.Vote4Chad.com
IIRC, @Magendanz is working on /will release soon a rom based on Andy Yan's LOS 19.x.
don't know what the currently samsung security patch state is ..., but LOS 19.x is android 12
I should have updates for TWRP, Nexus Stock and LineageOS 19.1 soon after Samsung posts kernel source for CVG2 (July 2022 Update).
 

Kenaz Rune

Senior Member
Mar 29, 2019
132
37
Google Pixel 6
I should have updates for TWRP, Nexus Stock and LineageOS 19.1 soon after Samsung posts kernel source for CVG2 (July 2022 Update).
That is even better than I hoped. I figured you might've given up on this device and hoped you might simply update your prior release with the recent Samsung updates.

However, the presence of 19.1 implies you are releasing A12L! I'm ecstatic! You make dealing with Samsung's weirdness so much easier, thank you.

Separately, if you can find someone to create a customized kernel or port Kirisakura Kernel to this device, we'll be set for at least descent device responsiveness for another year or two!
 

Magendanz

Senior Member
Mar 25, 2008
941
974
Issaquah, WA
www.Vote4Chad.com
That is even better than I hoped. I figured you might've given up on this device and hoped you might simply update your prior release with the recent Samsung updates.
My son, wife and mother-in-law are all using this tablet as their daily drivers, so I can't give up on it just yet.
Separately, if you can find someone to create a customized kernel or port Kirisakura Kernel to this device, we'll be set for at least descent device responsiveness for another year or two!
If you can get me a _defconfig diff for his custom kernel, I'll try to build it.
 
  • Like
Reactions: waterpolo

Kenaz Rune

Senior Member
Mar 29, 2019
132
37
Google Pixel 6
My son, wife and mother-in-law are all using this tablet as their daily drivers, so I can't give up on it just yet.

If you can get me a _defconfig diff for his custom kernel, I'll try to build it.
I just sent a message to the guy doing it for the P6, maybe he can give me some info. While I'm a developer, my expertise is business applications with C#, Java, JS, etc., so forgive me if I'm completely off base on this interpretation of your request....

Is _defconfig the default configuration properties for the kernel needed for a device? You're looking for a diff between the one he's using and the one you're using? Or mabye a diff from a device independent kernel? How can I get the right diff?
 

Kenaz Rune

Senior Member
Mar 29, 2019
132
37
Google Pixel 6
I just sent a message to the guy doing it for the P6, maybe he can give me some info. While I'm a developer, my expertise is business applications with C#, Java, JS, etc., so forgive me if I'm completely off base on this interpretation of your request....

Is _defconfig the default configuration properties for the kernel needed for a device? You're looking for a diff between the one he's using and the one you're using? Or mabye a diff from a device independent kernel? How can I get the right diff?
For reference, here's the Link.
Edit: original link broke. Pixel 6 pro kernel
 
Last edited:

Magendanz

Senior Member
Mar 25, 2008
941
974
Issaquah, WA
www.Vote4Chad.com
Is _defconfig the default configuration properties for the kernel needed for a device? You're looking for a diff between the one he's using and the one you're using? Or mabye a diff from a device independent kernel? How can I get the right diff?
Yeah, the _defconfig contains all the kernel configuration (Kconfig) settings, and I'm looking for what he's changed for his custom kernel.
 

Kenaz Rune

Senior Member
Mar 29, 2019
132
37
Google Pixel 6
Well, until I hear back, if ever, there is the infinity kernel for y This device that was abandoned after Android 10. Would that be something you could upgrade to A11 or 12?.

@Magendanz, I didn't tag you in the above message. I'm wondering if you can work with the infinity kernel (sources available above). I don't think @Freak07 is going to get back to me on his kernel, unfortunately.
 

Magendanz

Senior Member
Mar 25, 2008
941
974
Issaquah, WA
www.Vote4Chad.com
@Magendanz, I didn't tag you in the above message. I'm wondering if you can work with the infinity kernel (sources available above). I don't think @Freak07 is going to get back to me on his kernel, unfortunately.
Frankly, I'm stretched too thin right now to take on a custom kernel. School is back in session and I'm developing mobile campaign apps as a side hustle and handling my own reelection to the WA state legislature as well. Just not enough hours in the day.
 

rw_on_xda

Senior Member
Jun 24, 2013
404
228
Berlin
I need to sell this device so how do I go about returning this to stock please? Maybe just flash the latest official Samsung firmware with Odin and then re-lock the bootloader?
FRP too
to check Bootloader, FRP: boot into download mode and check the text in top left corner.

what I copy out of INet:
Factory Reset Protection (FRP)
==============================
https://www.fonepaw.com/android-lock/enable-bypass-factory-reset-protection.html

https://www.samsung.com/nz/support/mobile-devices/what-is-google-frp/



Factory Reset Protection (FRP), also known as Google account verification, is a feature added to Android device since Android Lollipop.
Most stock Android models are equipped with this feature.

FRP is designed to make sure that no one can easily wipe out the data and factory reset your phone if the phone is lost or stolen.
FRP is automatically enabled once you have added a Google account to your phone.

To disable FRP, you just have to remove Google account from your phone:

Settings > Accounts > Google

Once you enable FRP on your phone, when you or others try to set up the phone after factory reset in recovery mode, the phone will require you to verify your account.
You must enter Google username and password to access the phone.


Factory Reset: Settings > General Management > Reset > Factory Data Reset, the FRP Lock will be enabled.


To conclude, before you send your phone to the next user, you should first remove Google accountfrom your phone to disable FRP, then you wipe out all data in your phone.
In this way, the next user can set up the phone without stopping by FRP.

Tip:
to avoid the trouble of FRP, you should not factory reset your phone in 24 hours after you have recently changed the Google password associated to your phone.
Due to security reason, Android wouldn't allow you to set up your phone with a Google password that is newly reset within 24 hours.

you know that the prices increased for SM-T510 ?
I bought my 3 GB RAM, 64 storage for ~194€ ~2years ago.
now already the smaller (2GB Ram, 32GB storage) is sold for ~270 €
 
  • Like
Reactions: vanzan

rw_on_xda

Senior Member
Jun 24, 2013
404
228
Berlin
I jusţneed to know how to re-lock the bootloader....
same procedure as unlook.
maybe this one:

the last 4, after "Let's do it"
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I guess it should do (untested here) cause it's the same android version (11) and the same binary version (5).
    and @Magendanz lastest TWRP is also based on T510XXU5CVG2

    EDIT
    please report here !
    Yes, with T510XXU5CVG2 working this Nexus ROM good. I am on it right now after fresh flash :)
    2
    I try every available ROM for SM-T510, custom and latest official stock and this @Magendanz Nexus A11 ROM is in my opinion best and for daily use without lags and errors. Working better without Magisk in my experience. Thanks.
  • 23
    qPD09.png

    Well, we're finally getting some relatively stable builds of AOSP GSIs and OpenGApps for Android 11.0, so here's my first effort at migrating the Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.0 [SM-T510] to the latest Android OS release. 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 are generally based on the latest update for the SM-T510. Note that the bootloader in this release has roll-back prevention.
    • The system is based on eremitein's CAOS GSI project 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.
    • The properties now correctly identify the device as a tablet, and so the Google Dialer is no longer installed. I've also disabled the Emergency button, but SetupWizard still insists on reminding you to insert a SIM (sigh!).
    • 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
    • Cold charging (low power mode) animates to about 39% and then reboots.
    Downloads:
    Build archives:

    Change Log:
    20220219:

    • Vendor partition and custom kernel based on T510XXU5CUL1 OEM firmware (December 2021 Update)
    • System partition based on CAOS 11.0 v315 (January 2022 Security Update)
    • Latest Google apps from OpenGApps (20220215) w/ rollback for GoogleTTS
    20211125:
    • Vendor partition and custom kernel based on T510XXU5CUJ1 OEM firmware (October 2021 Update)
    • Update to TWRP v3.6.0 custom recovery on AOSP 11
    • Latest Google apps from OpenGApps (20211125) w/ rollback for GoogleTTS
    20211120:
    20210825:
    • Vendor partition and custom kernel based on T510XXU5CUF4 OEM firmware (June 2021 Update)
    • System partition based on CAOS 11.0 v312 (August 2021 Security Update)
    • Update to TWRP v3.5.2 custom recovery
    • Latest Google apps from OpenGApps (20210825-TEST)
    20210318:
    • Fixed custom Pixel Launcher so that icon positions are saved.
    • Fixed clipped pixels on edge of launcher search bar.
    • Defaults icon layout to 7 columns for main, hotseat and app drawer, just like it used to be for the Nexus 10. (For 6 column layout bump display scaling to Large.)
    20210314:
    • Vendor partition and custom kernel based on T510XXU4BUA1 OEM firmware (January 2021 Update)
    • System partition based on CAOS 11.0 v302 (March 2021 Security Update)
    • Update to TWRP v3.5.1 custom recovery
    • Latest Google apps from OpenGApps (20210130-TEST)
    20210216:
    • Initial build based on T510XXU3BTK1 kernel (November 2020 Update) and CAOS 11.0 v300m.
    • Latest Google apps from OpenGApps (20210130-TEST)

    Instructions:
    From OEM stock firmware:

    • Unlock bootloader
    • Ensure matching OEM build (e.g. T510XXU3BTK1) is installed
    • 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
    From existing TWRP install (for incremental updates):
    • 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:

    Donations:
    • Your support is always appreciated! Just click here.
    • I'm leveraging a ton of work done by @phhusson for Treble GSIs and @eremitein for CAOS, so please show them some love!
    8
    I just posted a new release. Note that I'll be following up with another update for T510XXU5CUJ1 (October 2021 Update) as soon as Samsung posts the kernel source.

    Downloads:
    Change Log:
    20211120:

    • System partition based on CAOS 11.0 v313+ (October 2021 Security Update)
    • Latest Google apps from OpenGApps (20211120) w/ rollback for GoogleTTS
    7
    New build just posted...

    Downloads:
    Change Log:
    20220219:

    • Vendor partition and custom kernel based on T510XXU5CUL1 OEM firmware (December 2021 Update)
    • System partition based on CAOS 11.0 v315 (January 2022 Security Update)
    • Latest Google apps from OpenGApps (20220215) w/ rollback for GoogleTTS
    6
    New build just posted...

    Downloads:
    Build archives:
    Change Log:
    20210318:

    • Fixed custom Pixel Launcher so that icon positions are saved.
    • Fixed clipped pixels on edge of launcher search bar.
    • Defaults icon layout to 7 columns for main, hotseat and app drawer, just like it used to be for the Nexus 10. (For 6 column layout bump display scaling to Large.)
    6
    New build is posted. Note that this is the first build with the new Android 11 OEM kernel, and so you should expect some issues. In particular, I've noticed that MTP with Android Debugging enabled can cause reboots. There's also the issue with the reboot during the cold charging animation (but it no longer hangs). I'm also creating my own stock variant for OpenGApps, which still hasn't updated the TEST release from January.

    Also, note that the new OEM bootloader for Android 11 has rollback prevention, so there's no going back to Android 10 releases.

    Downloads:
    Change Log:
    20210825:

    • Vendor partition and custom kernel based on T510XXU5CUF4 OEM firmware (June 2021 Update)
    • System partition based on CAOS 11.0 v312 (August 2021 Security Update)
    • Update to TWRP v3.5.2 custom recovery
    • Latest Google apps from OpenGApps (20210825-TEST)