[RECOVERY][UNOFFICIAL] TWRP 3.5.2 for 2019 Galaxy Tab A 10.1 [SM-T510]

Search This thread

1x2d3a

New member
Mar 13, 2021
1
0
Hi,

thanks a lot @Magendanz for your hard work.

For all SM-T515 (LTE version) owners - here's what I gathered after spending a few hours on that topic (can be important for anyone who wants to root/install TWRP on SM-T515, not on SM-T510):

1. This is probably the only thread on the entire web where you can get TWRP (and root) for SM-T515. Other websites, even foreign ones, reference this thread.

2. If you buy SM-T515 now it will probably come with "T515-XXS-4ATB4" firmware.
(Android 9, March 2020 security patch)

3. If you upgrade your system more than once (to anything after the 1st update (T515-XXS-3ATE3, May 2020 security patch)), you will be OUT OF LUCK, installing TWRP will NOT be possible.

On top of that, SEVERAL people here claimed to have bricked their devices trying to install TWRP on newer firmwares (*XXU*, Android 10) without any path to downgrade.

The main developer here even stopped supporting SM-T515. All new builds are for wifi version only.


4. There is only ONE confirmed success story here from April 30, 2020 for TWRP build "T515-XXS-4ATB4".


5. Other success story here is about installing T510 TWRP build ("T510-XXS-3ATE3-20200626") on T515 from Jul 3 2020.
It's not clear, unfortunately, how well (if) this T510 version worked.
The problem is that there is also T515-XXS-3ATE3 version on github (the last one that was released) and there is no info if anyone tested it.

Here's another from Aug 5 2020, even less clear.

However, if "T510-XXS-3ATE3" worked, "T515-XXS-3ATE3" will probably work fine on your device upgraded to May 2020 security patch.


So, as a summary:
  • if you want to root/install TWRP on SM-T515, you'll have to use old firmware and Android 9,
  • if you install it on Android 10, you'll brick your device.

P.S.
@Magendanz, as I understand you don't have any plans to return to SM-T515 or release old code with kernel fixes, right?
 

htchd2sucks

Senior Member
May 23, 2010
897
363
Hi,
I'm having issues flashing TWRP on the SM-T510:

Settings/About/Android version: SM-T510; Android 10;...

I did the unlock bootloader properly.
Then I did use odin3_v3.13.3, to flash the sammy firmware for my version (AUT-T510XXS5BUC4-20210421105041)
(I even tried Odin3 v3.14.1.exe after)

There were three things:
BL :BL_T510XXS5BUC4_CL20709318_QB39002062_REV02_user_low_ship.tar.md5
AP: AP_T510XXS5BUC4_CL20709318_QB39002062_REV02_user_low_ship_meta_OS10.tar.md5
CSC: CSC_OMC_OXM_T510OXM5BUC4_CL20709318_QB39002062_REV02_user_low_ship.tar.md5

That went ok.

Then I try again odin to flash twrp-3.5.2_9-0-T510XXU4BUA1-20210508.tar.md5 to AP.

It gives me:
<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> recovery.img
<ID:0/004> vbmeta.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


Any clue?
Thanks
 
Last edited:

Magendanz

Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    I'm having issues flashing TWRP on the SM-T510:
    It looks like you triggered Samsung's VaultKeeper "feature" during the reboot between flashes. You've can connect to the Internet and enable Developer Options immediately after OEM setup to prevent that. Do a search for more details.

    Personally, I just prefer to skip OEM setup and hold Vol Up & Down after reboot to immediately return to Download mode to flash TWRP. Then in TWRP you can install Multidisabler to disable VaultKeeper for real.
     

    htchd2sucks

    Senior Member
    May 23, 2010
    897
    363
    It looks like you triggered Samsung's VaultKeeper "feature" during the reboot between flashes. You've can connect to the Internet and enable Developer Options immediately after OEM setup to prevent that. Do a search for more details.

    Personally, I just prefer to skip OEM setup and hold Vol Up & Down after reboot to immediately return to Download mode to flash TWRP. Then in TWRP you can install Multidisabler to disable VaultKeeper for real.
    Thanks. Yesterday I had suspected that, after seeing some of your old replies. I am trying related steps again now.
    Is there a way to verify that Vaultkeeper is active/activated? I had discarded that possible root cause because I was still able to go into bootloader, so I though it was letting me do everything ...
    Edit: that does not seem to be that...
    I went into download mode, pressed "Up" long to reach the mode again, allowed OEM unlock.
    Rebooted, did the internet + setup + enabled OEM and usb debugging.
    Powered off + booted into download mode using vol up + down,
    Tried AP flashing from ODIN of TWRP: same situation:

    <ID:0/004> Added!!
    <ID:0/004> Odin engine v(ID:3.1401)..
    <ID:0/004> File analysis..
    <ID:0/004> Total Binary size: 40 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> recovery.img
    <ID:0/004> vbmeta.img
    <ID:0/004> RQT_CLOSE !!
    <ID:0/004>
    <ID:0/004> Complete(Write) operation failed.
    <OSM> All threads completed. (succeed 0 / failed 1)

    Having said that, I do have in ODIN a red message "custom Binary (Recovery) blocked by OEM lock".
    Before it was saying only official rom were valid...

    I'll try again.

    Edit2: I did it again, bootloader, volume up, accept OEM unlock... and again the rest of procedure and this time it flashed properly...
    Surely something weird with vaultkeeper...

    Thanks!
     
    Last edited:

    I AM THE GOD

    Member
    Jun 11, 2021
    12
    0
    twrp-featured.jpg

    After @geiti94 and @ianmacd started the ball rolling for the Samsung Galaxy S10 series (Exynos 9820), it was really only a matter of time until we could do the same for the 2019 Galaxy Tab A 10.1 (Exynos 7904). The kernel source was released last May, allowing me to build a custom kernel with many of the problematic Knox security features disabled. What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive 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 rely on the latest posted kernel source (T510XXU4BUA1).
    • 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:
    v3.5.2_9-0:
    v3.5.1_9-0:
    • Updated to T510XXU4BUA1 posted kernel source.
    • Updated to TWRP 3.5.1 release built from android-9.0 branch.
    v3.5.0_9-0:
    • Updated to T510XXU3BTK1 posted kernel source.
    • Updated to TWRP 3.5.0 release built from android-9.0 branch.
    v3.4.0-0:
    • Updated to TWRP v3.4.0 source
    • Updated to latest custom kernel
    v3.3.1-7:
    • Updated to latest custom kernel
    v3.3.1-6:
    • Switched to .img file for installation from TWRP
    v3.3.1-5:
    • Fixed hang on splash with encrypted user data partition
    • Added OTA update (.zip) for installation from TWRP
    v3.3.1-4:
    • Fixed MTP support in a way that supports Magisk
    v3.3.1-3:
    • Fixed MTP support
    • Included boot image with custom kernel
    • Deprecated separate NoKnox releases
    v3.3.1-2:
    • Changed system partition mount point to /system_root
    • Fixed screen brightness control
    • Restored screen timeout

    Instructions:
    From OEM stock firmware:
    • Unlock bootloader
    • Hold Vol Up & Vol Down buttons during restart to enter Download mode
    • Install TWRP to AP with Odin
    • Hold Power & Vol Up buttons during restart to enter TWRP recovery
    • Install latest Multidisabler from TWRP
    • Wipe->Format Data
    • Reboot to system
    From existing TWRP install: (No need for data wipe.)
    • Hold Power & Vol Up during restart to enter TWRP recovery
    • Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
    • Reboot to system

    What about rooting with Magisk?
    These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.

    Source:

    Donations:
    • Your support is always appreciated! Just click here.
    hey so I'm new to this whole thing and I have a few questions
    1) my SM-T510 is android 10 and the bit I m not sure it says 64bit armv8-a ( 32 bit )
    so will this twrp work for my device?
    2)also will it work for no root
    3 do you need Odin
     

    I AM THE GOD

    Member
    Jun 11, 2021
    12
    0
    Hi,
    I'm having issues flashing TWRP on the SM-T510:

    Settings/About/Android version: SM-T510; Android 10;...

    I did the unlock bootloader properly.
    Then I did use odin3_v3.13.3, to flash the sammy firmware for my version (AUT-T510XXS5BUC4-20210421105041)
    (I even tried Odin3 v3.14.1.exe after)

    There were three things:
    BL :BL_T510XXS5BUC4_CL20709318_QB39002062_REV02_user_low_ship.tar.md5
    AP: AP_T510XXS5BUC4_CL20709318_QB39002062_REV02_user_low_ship_meta_OS10.tar.md5
    CSC: CSC_OMC_OXM_T510OXM5BUC4_CL20709318_QB39002062_REV02_user_low_ship.tar.md5

    That went ok.

    Then I try again odin to flash twrp-3.5.2_9-0-T510XXU4BUA1-20210508.tar.md5 to AP.

    It gives me:
    <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> recovery.img
    <ID:0/004> vbmeta.img
    <ID:0/004> RQT_CLOSE !!
    <ID:0/004>
    <ID:0/004> Complete(Write) operation failed.
    <OSM> All threads completed. (succeed 0 / failed 1)


    Any clue?
    Thanks
    hey so i am a dumbass and don't understand any of this
    so basically your sm-t510 had kernel version t510xxs5buc4
    and you flashed the twrp for kernel t510xxu4bua1 right?
    i just want to flash a lineage rom and root my tablet for gaming .
    any guide or advice.
    (I am a prof. codm player and recently broke my iPad and have to manage with the smt-510
    and the world cup codm stage 2 is starting so I need to boost performance asap)
    any help/advice would really be appreciated
     

    lewmur

    Senior Member
    Apr 30, 2011
    1,764
    377
    hey so i am a dumbass and don't understand any of this
    so basically your sm-t510 had kernel version t510xxs5buc4
    and you flashed the twrp for kernel t510xxu4bua1 right?
    i just want to flash a lineage rom and root my tablet for gaming .
    any guide or advice.
    (I am a prof. codm player and recently broke my iPad and have to manage with the smt-510
    and the world cup codm stage 2 is starting so I need to boost performance asap)
    any help/advice would really be appreciated
    First of all, the T510 is an "economy class" tablet. It is NOT meant to compete with iPads and anyone expecting one to replace an iPad for gaming is going to be sadly disappointed. Second, rooting and installing a custom ROM requires many steps and if you get a single step wrong, it isn't going to work. The first step is to check what version of the stock ROM your tablet has. If it is later than BUA1, then you are flat out of luck.
     

    I AM THE GOD

    Member
    Jun 11, 2021
    12
    0
    First of all, the T510 is an "economy class" tablet. It is NOT meant to compete with iPads and anyone expecting one to replace an iPad for gaming is going to be sadly disappointed. Second, rooting and installing a custom ROM requires many steps and if you get a single step wrong, it isn't going to work. The first step is to check what version of the stock ROM your tablet has. If it is later than BUA1, then you are flat out of luck.
    So how do I check
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 24
      twrp-featured.jpg

      After @geiti94 and @ianmacd started the ball rolling for the Samsung Galaxy S10 series (Exynos 9820), it was really only a matter of time until we could do the same for the 2019 Galaxy Tab A 10.1 (Exynos 7904). The kernel source was released last May, allowing me to build a custom kernel with many of the problematic Knox security features disabled. What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive 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 rely on the latest posted kernel source (T510XXU4BUA1).
      • 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:
      v3.5.2_9-0:
      v3.5.1_9-0:
      • Updated to T510XXU4BUA1 posted kernel source.
      • Updated to TWRP 3.5.1 release built from android-9.0 branch.
      v3.5.0_9-0:
      • Updated to T510XXU3BTK1 posted kernel source.
      • Updated to TWRP 3.5.0 release built from android-9.0 branch.
      v3.4.0-0:
      • Updated to TWRP v3.4.0 source
      • Updated to latest custom kernel
      v3.3.1-7:
      • Updated to latest custom kernel
      v3.3.1-6:
      • Switched to .img file for installation from TWRP
      v3.3.1-5:
      • Fixed hang on splash with encrypted user data partition
      • Added OTA update (.zip) for installation from TWRP
      v3.3.1-4:
      • Fixed MTP support in a way that supports Magisk
      v3.3.1-3:
      • Fixed MTP support
      • Included boot image with custom kernel
      • Deprecated separate NoKnox releases
      v3.3.1-2:
      • Changed system partition mount point to /system_root
      • Fixed screen brightness control
      • Restored screen timeout

      Instructions:
      From OEM stock firmware:
      • Unlock bootloader
      • Hold Vol Up & Vol Down buttons during restart to enter Download mode
      • Install TWRP to AP with Odin
      • Hold Power & Vol Up buttons during restart to enter TWRP recovery
      • Install latest Multidisabler from TWRP
      • Wipe->Format Data
      • Reboot to system
      From existing TWRP install: (No need for data wipe.)
      • Hold Power & Vol Up during restart to enter TWRP recovery
      • Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
      • Reboot to system

      What about rooting with Magisk?
      These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.

      Source:

      Donations:
      • Your support is always appreciated! Just click here.
      6
      Hello.
      Source code of SM-T510 Android 10
      T510XXU3BTFN
      on https://opensource.samsung.com/uploadSearch
      ...and we just got a new drop of the AOSP 10 GSI. Please stand by...
      6
      Just a quick update: Samsung posted the T515XXS3ASK5 source last night, so I expect T510XXS2ASK5 to follow soon. When that happens, I'll update TWRP for both the SM-T510 and SM-T515.
      5
      As soon as kernel source is posted for T515XXS4ATE3, I'll post that too.

      Downloads:
      SM-T510:

      Change Log:
      v3.4.0-0:
      • Updated to TWRP v3.4.0 source
      • Updated to latest custom kernel
      4
      I just released a TWRP build for the T510XXS3ATB4 kernel, which just had its source posted by Samsung today.