• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

Broman400

Senior Member
Was about to unlock my bootloader and start the process of installing this ROM and started reading about RMM/KG lock/bypass. Someone posted a guide in Post #91 here, was wondering if thats recommended/needed after flashing this ROM?

 

Gamris

Member
Aug 23, 2017
5
0
Guys. I'm trying to understand why absolutely any android 10 rom gets stuck on boot screen after flashing, for example for this nexus rom it gets stock on that Google boot animation. The only roms that work on my SM-T510 are android 9 roms. For example Lineage OS 16.0..... Any ideas on what's wrong? I wipe pretty much everything and tried everything and they're always just on boot screen for hours. AND it doesn't matter if I flash it through ODIN or TWRP. Same result.
 

Magendanz

Senior Member
Mar 25, 2008
836
806
Issaquah, WA
www.Vote4Chad.com
Guys. I'm trying to understand why absolutely any android 10 rom gets stuck on boot screen after flashing, for example for this nexus rom it gets stock on that Google boot animation. The only roms that work on my SM-T510 are android 9 roms. For example Lineage OS 16.0..... Any ideas on what's wrong? I wipe pretty much everything and tried everything and they're always just on boot screen for hours. AND it doesn't matter if I flash it through ODIN or TWRP. Same result.
Sounds like you didn't update to the Android 10 OEM firmware release (BTU-T510XXU3BTFN or later).
 
  • Like
Reactions: Gamris

-BoneZ-

Senior Member
Oct 24, 2009
520
105
Indiana
Guys. I'm trying to understand why absolutely any android 10 rom gets stuck on boot screen after flashing, for example for this nexus rom it gets stock on that Google boot animation. The only roms that work on my SM-T510 are android 9 roms. For example Lineage OS 16.0..... Any ideas on what's wrong? I wipe pretty much everything and tried everything and they're always just on boot screen for hours. AND it doesn't matter if I flash it through ODIN or TWRP. Same result.

I'm having the same exact issue. I'm coming from an earlier version of this ROM. I updated TWRP and after installing this ROM, stuck at the "G" logo forever loading.
 
  • Like
Reactions: Gamris

lewmur

Senior Member
Apr 30, 2011
1,988
431
I'm having the same exact issue. I'm coming from an earlier version of this ROM. I updated TWRP and after installing this ROM, stuck at the "G" logo forever loading.
That is because Samsung changes the partitions and you have to first flash the stock ROM to match the version of the custom ROM you are trying to install. If you look in the first post of this thread, you'll see that this one is based on stock ROM ending in BUA1. That is what you need to flash with Odin, reboot and connect wifi, skip the rest of the setup and enable Dev mode. Then you can flash this ROM.
 
  • Like
Reactions: Gamris and -BoneZ-

-BoneZ-

Senior Member
Oct 24, 2009
520
105
Indiana
That is because Samsung changes the partitions and you have to first flash the stock ROM to match the version of the custom ROM you are trying to install. If you look in the first post of this thread, you'll see that this one is based on stock ROM ending in BUA1. That is what you need to flash with Odin, reboot and connect wifi, skip the rest of the setup and enable Dev mode. Then you can flash this ROM.
Yep, I flashed newer firmware and then flashed this ROM and I'm in now. Technically since I was on a previous version of this ROM, I was following the "incremental update" instructions, but we're good now. :)
 
  • Like
Reactions: Gamris

Gamris

Member
Aug 23, 2017
5
0
That is because Samsung changes the partitions and you have to first flash the stock ROM to match the version of the custom ROM you are trying to install. If you look in the first post of this thread, you'll see that this one is based on stock ROM ending in BUA1. That is what you need to flash with Odin, reboot and connect wifi, skip the rest of the setup and enable Dev mode. Then you can flash this ROM.
Indeed I overlooked this detail when I wasted a whole day a couple of months ago trying to flash android 10 roms. Then gave up and settled with android 9 and continued with my life. And I overlooked as well that the first page has links to stock roms. Albeit at extremely slow download speeds. So I spent 5-6 hours downloading a ROM ending with BUA1. Flashed with Odin. Then flashed the latest Nexus ROM Tarball in AP. And finally works. amazing.. Thanks for the help you guys!
 

zyzelement

New member
Nov 29, 2013
2
0
Hi - first thank you and the community for all the work and great content here.
I spent the last few hours trying to get this installed and I don't think it's going to work for me because my tablet is already on the next level of the official firmware and downgrades aren't allowed. I would love to know if this is WRONG so I can keep working on it :)

  1. My tablet is on the T510XXS5BUC4 (the version after the one this rom is based on.)
  2. I understand that I need to downgrade to the *BUA1 stock firmware before flashing this ROM.
  3. When I try to do that, Odin fails and I see the following on the tablet screen: SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 5: BINARY 4.
From my research, I believe this is because the boot loader prevents downgrading, so it's not possible to downgrade the official firmware (which in turn means I can't flash this rom.)

I guess my only option is to wait for the version of the Nexus rom based on *BUC4 to come out.

Am I thinking about this correctly or am I missing something?

Thank you again!
 

-BoneZ-

Senior Member
Oct 24, 2009
520
105
Indiana
I guess my only option is to wait for the version of the Nexus rom based on *BUC4 to come out.

Am I thinking about this correctly or am I missing something?

From what I've read, it's not possible to downgrade. The OP has been pretty good about getting updates out, so just hang tight. I went back to the stock Samsung ROM and it's just as fast as this ROM.
 

sr1sws

Member
Dec 3, 2020
14
6
Upgraded this morning without any apparent hitches. Play store is now seemingly updating every app (maybe... at least most of them). Thank you for your work!!
 
  • Like
Reactions: Magendanz

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    If I wanted to try this ROM coming from the latest version of another of your releases: https://forum.xda-developers.com/t/...-1-for-galaxy-tab-a-10-1-2019.4060153/page-26

    Or do I maybe want this 1? https://forum.xda-developers.com/t/...2019-galaxy-tab-a-10-1-sm-t510.4234889/unread

    Can I do it all through TWRP? 🤔

    If so which wipes do I do before flashing? 🤔
    If you're coming from the Android 10 OEM firmware (Bxxx), then you'll need to first install the latest OEM firmware and then this custom ROM via Odin. If you're coming from an Android 11 OEM firmware (Cxxx), then you probably could upgrade via TWRP and the data wipe is optional.

    The safest bet is always to do an Odin flash of the latest OEM firmware and then install the custom ROM via Odin, but this always does a factory reset.
    1
    Thank you very much for all your work in general & help now :)

    Regrettably I'm in trouble I can't seem to get back into TWRP or Download Mode or even power the tablet off: https://forum.xda-developers.com/t/...-galaxy-tab-a-10-1-2019.4060153/post-86264395
    Unless you corrupted the bootloader, you should be able to get back to Download Mode. Just connect to your PC via USB, press and hold Power + Vol Down for 7-8 seconds, and quickly switch to Vol Up + Vol Down. It may take a few tries, but there's no need to wait for the battery to deplete.

    From Download Mode, just flash that latest OEM firmware with Odin and try again.

    (I can't speak to the Magisk issues that you were running into, since that's really not my area of expertise.)
    1
    @Magendanz After flashing the OEM firmware do I need to boot once before flashing another ROM?
    No, but you can't flash twice in Odin. You'll need to reboot and hold Vol Up + Vol Down to reenter Download Mode. After the custom ROM, I usually reboot to TWRP to do a factory reset just to ensure the user data partition is clean and unencrypted.
  • 18
    qPD09.png

    Well, we're finally getting some relatively stable builds of AOSP GSIs and OpenGApps for Android 10.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 this one is based on the October 2020 Update (T510XXU4BUA1) for the SM-T510.
    • The new release is based on @eremitein's CAOS 10.0 GSI (CQ), which is an extremely lightweight set of tweaks to AOSP.
    • Previous releases were based on @AndyYan's LineageOS 17.1 GSI (LQ) or @phhusson's AOSP 10.0 (AQ).
    • Includes common set of Google apps from 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 and Messenger are 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

    Downloads:
    Build archives:

    Change Log:
    20210508:
    • Updated to TWRP v3.5.2.
    • Updated to latest stable 10.0 release of OpenGapps Stock variant (20200508).
    20210327:
    • Google Assistant setup no longer fails in Setup Wizard.
    • Updated to latest stable 10.0 release of OpenGapps Stock variant (20200327) with fix for Google News.
    20210322:
    • 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.)
    • Based on latest CAOS 10.0 v224 GSI build (20201029) with October 2020 security patch.
    • Updated to the OEM January 2021 Security Update (T510XXU4BUA1) kernel and vendor partition.
    • Updated to latest stable 10.0 release of OpenGapps Stock variant (20200311) with fix for Google News.
    20201130:
    • Based on AOSP GSI v222 (20200806) with August 2020 security patch.
    20201121:
    • Based on latest LineageOS 17.1 GSI build (20201114) with November 2020 security patch.
    • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
    • Updated to latest stable 10.0 release of OpenGapps Stock variant (20201121), which now includes Google Recorder.
    20200812:
    20200807:
    • Based on AOSP GSI v222 (20200806) with August 2020 security patch.
    • Includes patches to provide simple theme configuration section in Settings > Display, add Recovery to power menu, and match Pixel appearance.
    • Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
    • Updated to latest stable 10.0 release of OpenGapps Stock variant (20200714).
    20200713:
    • Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 security patch.
    20200712:
    • Based on AOSP GSI v221 (20200708) with July 2020 security patch and patch to provide simple theme configuration section in Settings > Display.
    • Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
    • Updated to latest stable 10.0 release of OpenGapps Stock variant (20200711).
    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.
    • Updated to latest release of OpenGapps (20200409-TEST), with private fix for Chrome issue.
    20200314:
    • Fixed potential image corruption issue from outdated img2simg command.
    20200312:
    • Now based on the latest build of LineageOS 17.1 GSI (20200309).
    • Uses v703 build of Pixel Launcher with 6x6 and 7x7 icon profiles migrated from the Android One Launcher.
    • Charging after full shutdown will no longer hang during level-of-charge animation.
    • MTP file transfers no longer require USB Debugging to be enabled.
    20200223:
    • Initial build based on T510XXU2ASK5 kernel (November 2019 Update) and AOSP 10.0 v212.
    • Latest Google apps from OpenGApps (20200216-TEST)

    Instructions:
    From OEM stock firmware:
    • Unlock bootloader
    • Ensure matching OEM build (e.g. T510XXU3BTFN) 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 @eremitein and @phhusson for Treble GSIs, so please show them some love here!
    12
    Once again for the AOSP purists...

    Downloads:
    SM-T510:

    Change Log:
    20200505:
    • Based on T510XXS3ATB4 OEM firmware and AOSP GSI v216 (20200505)
    • Updated to new stable 10.0 release of OpenGapps Stock variant (20200506).
    9
    Here's a drop of the AQ variant for T510XXU3BTFN, the new Android 10 OEM firmware release. There is an issue right now with the custom kernel not working with the OEM system, but the Nexus builds seem to be working fine. Also, Samsung seems to have made a change in the bootloader preventing the main logo.jpg in the param.bin from being picked up, so you won't see the Nexus logo on boot. However, it is picking up the other two custom images that dial back the scary bootloader unlock warnings. Finally, the latest OpenGApps Stock variant posted is almost a month old, and there's no indication when those will return.

    This is a pretty major update, and so I'm posting it here first for early adopters. If the rollout goes smoothly, I'll update in the OP.

    Downloads:
    Based on AOSP 10.0:

    Change Log:
    20200807:
    • Based on AOSP GSI v222 (20200806) with August 2020 security patch.
    • Includes patches to provide simple theme configuration section in Settings > Display, add Recovery to power menu, and match Pixel appearance.
    • Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
    • Updated to latest stable 10.0 release of OpenGapps Stock variant (20200714).
    7
    LineageOS 17.1 version is now posted.

    Downloads:
    SM-T510:

    Change Log:
    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.
    • Updated to latest release of OpenGapps (20200409-TEST), with private fix for Chrome issue.

    Note that a clean install is required to fix Double Tap to Wake feature, since the fix is in the rw-system.sh script that only runs on first boot.
    7
    For the AOSP purists...

    Downloads:
    SM-T510:

    Change Log:
    20200410:
    • Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
    • Fixed crash on first two attempts to launch Phh Treble Settings.
    • Based on AOSP GSI v215 (20200408)
    • Updated to latest release of OpenGapps (20200409-TEST), with private fix for Chrome issue.