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

Search This thread

Magendanz

Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    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.
     
    Last edited:

    beta990

    Senior Member
    Apr 18, 2013
    66
    8
    Great stuff! I've received the device today, although I'm willing to test this recovery, it maybe better to wait a bit longer for a patched kernel/ROM instead? From my understanding this prevents the needs of booting in recovery every time to start the tablet and may be better to prevent Samsung/KNOX from bricking this device.

    If this is untrue, please let me know and I'll remove this post asap. :)
    Also let me know if you need any (debug) info.
     

    Magendanz

    Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    Great stuff! I've received the device today, although I'm willing to test this recovery, it maybe better to wait a bit longer for a patched kernel/ROM instead? From my understanding this prevents the needs of booting in recovery every time to start the tablet and may be better to prevent Samsung/KNOX from bricking this device.

    NoKnox above will patch the T510XXU1ASC7 OEM firmware with the custom kernel and includes the vendor partition fixes in @ianmacd's Multi-disabler. Booting to recovery each time is only required with the Magisk root, which patches itself into recovery (TWRP or stock). More details on @ianmacd's post here.
     
    Last edited:
    • Like
    Reactions: beta990

    cambunch

    Senior Member
    Sep 11, 2009
    858
    1,480
    Thanks for this! I successfully flashed NoKnox, TWRP and Magisk last night and all is working well! @PiCkLeS posted some helpful instructions here for those needing some extra help. Follow the instructions in this thread, but replace the last step with flashing your Magisk-patched TWRP image. No need to mess with running magisk on the stock AP file, you can just modify the TWRP recovery.img.
     

    Magendanz

    Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    I just received the tablet and it's running T510XXU1ASCE, I suppose I should downgrade first, if possible, or will it work as-is?
    Unfortunately, they've only posted the source for T510XXU1ASC7 at this point, so that's what we're stuck with. The safe bet is to downgrade (especially since NoKnox includes a modified vendor partition), but I wouldn't be surprised if you can mix and match these two versions.

    Note: I see that the May 2019 update (T510XXU1ASCF) is already available. I've put in a request for the kernel source to be posted.
     
    • Like
    Reactions: zfk110 and 3c

    3c

    Senior Member
    Jul 19, 2005
    2,745
    1,873
    www.3c71.com
    Unfortunately, they've only posted the source for T510XXU1ASC7 at this point, so that's what we're stuck with. The safe bet is to downgrade (especially since NoKnox includes a modified vendor partition), but I wouldn't be surprised if you can mix and match these two versions.

    Note: I see that the May 2019 update (T510XXU1ASCF) is already available. I've put in a request for the kernel source to be posted.

    Thanks, downgrading from ASCE worked very well, had to change OEM unlock in dev settings again though (with the date trick).
     

    messi2050

    Senior Member
    Nov 1, 2012
    2,299
    3,276
    Yep, it's already downloaded and I'm building the kernel tonight. Unfortunately, we didn't get the May 2019 update for SM-T515 (T515XXU1ASEH).

    hello, thanks for your work, i'm building twrp for a device with the same soc [7904], i was wondering does disabling [proca] is a must to boot twrp ? if it's can you provide changes you have made to vendor partition to remove it
    regards

    edit: ok i see that you remove the init file for proca service [pa_daemon_teegris.rc] so my question now is, does using a custom kernel in boot image is a must ? i already use one in twrp with most of the security features such as defex/proca/samsung restrictions..etc disabled and if possible can you provide the used kernel source or used defconfig ?
     
    Last edited:
    • Like
    Reactions: Ziauddin_Sameer

    Magendanz

    Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    hello, thanks for your work, i'm building twrp for a device with the same soc [7904], i was wondering does disabling [proca] is a must to boot twrp ? if it's can you provide changes you have made to vendor partition to remove it

    I just manually perform everything that @ianmcd's multi-disabler script does to the vendor partition.

    ok i see that you remove the init file for proca service [pa_daemon_teegris.rc] so my question now is, does using a custom kernel in boot image is a must ? i already use one in twrp with most of the security features such as defex/proca/samsung restrictions..etc disabled and if possible can you provide the used kernel source or used defconfig ?

    Yes, you've got to build a custom kernel to disable Samsung's rooting restriction features. The custom defconfig is here.
     

    messi2050

    Senior Member
    Nov 1, 2012
    2,299
    3,276
    I just manually perform everything that @ianmcd's multi-disabler script does to the vendor partition.


    Yes, you've got to build a custom kernel to disable Samsung's rooting restriction features. The custom defconfig is here.
    Been trying for a week now, still it bootloop at every attempt to enter twrp according to the testers.. not sure what's wrong, I'm building using twrp minimal source also custom kernel works good on stock rom so no idea where is the problem
     

    redexit

    Member
    Jul 11, 2008
    5
    0
    'Only official released binaries are allowed to be flashed'

    Thank you for this great work. I ended up getting the 'Only official released binaries are allowed to be flashed' at booting after flashing:

    - NoKnox-T510XXU1ASEF.tar
    - twrp-3.3.1-1-gta3xlwifi.tar

    After the flash, the tablet successfully booted into new factory status OS. Once the intial setup was done and rebooted, the phone is just soft bricked with the message. Any idea what I've done wrong?

    Thank you very much in advance.
     

    Magendanz

    Senior Member
  • Mar 25, 2008
    782
    736
    Issaquah, WA
    www.Vote4Chad.com
    After the flash, the tablet successfully booted into new factory status OS. Once the initial setup was done and rebooted, the phone is just soft bricked with the message. Any idea what I've done wrong?.
    That's Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.

    So to recover, just flash the stock OEM firmware package with Odin, repeat the steps you took, and be sure this time to enable Developer Options and verify that OEM Unlocking is enabled. (It should also be grayed out, since the bootloader is already unlocked.)

    And if you want to more permanently disabled VaultKeeper, I have a modified version of @ianmcd's multi-disabler script for the SM-T510 that you can install in TWRP.
     
    Last edited:
    • Like
    Reactions: betacrypt

    redexit

    Member
    Jul 11, 2008
    5
    0
    Thank you!

    That's Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.

    So to recover, just flash the stock OEM firmware package with Odin, repeat the steps you took, and be sure this time to enable Developer Options and verify that OEM Unlocking is enabled. (It should also be grayed out, since the bootloader is already unlocked.)

    And if you want to more permanently disabled VaultKeeper, I have a modified version of @ianmcd's multi-disabler script for the SM-T510 that you can install in TWRP.

    Whoa, thank you so much for your quick and thorough reply!

    I will do what you instructed after another 7 days I guess, (assuming there is no way to get around with this one).

    Again I truly appreciate your contribution and hard work.
     

    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.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone