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

[Magendanz]

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 (T510XXU5CWA1).
• 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:

• twrp-3.7.0_11-0-T510XXU5CWA1-20230330.tar.md5
• twrp-3.7.0_11-0-T510XXU5CWA1-20230330.img

Build archives:

• Android File Host

Change Log:
v3.7.0_11-0 (20230330):

• Updated to T510XXU5CWA1 OEM stock kernel.

v3.7.0_11-0 (20221102):

• Updated to TWRP 3.7.0 release built from AOSP-11 branch.

v3.6.2_11-0 (20220905):

• Updated to TWRP 3.6.2 release built from AOSP-11 branch.
• Updated to T510XXU5CVG2 OEM stock kernel.

v3.6.1_11-1:

• Minor update to incorporate fix from TWRP repo.

v3.6.1_11-0:

• Updated to TWRP 3.6.1 release built from AOSP-11 branch.
• Updated to T510XXU5CVB1 OEM stock kernel.

v3.6.0_11-2:

• Updated to T510XXU5CUL1 posted kernel source.

v3.6.0_11-1:

• Updated to T510XXU5CUJ1 posted kernel source.
• Updated to TWRP 3.6.0 release built from aosp-11 branch.

v3.5.2_9-0:

• Updated to T510XXU5CUF4 posted kernel source.

v3.5.2_9-0:

• Updated to TWRP 3.5.2 release built from omni-9.0 branch.

v3.5.1_9-0:

• Updated to T510XXU4BUA1 posted kernel source.
• Updated to TWRP 3.5.1 release built from omni-9.0 branch.

v3.5.0_9-0:

• Updated to T510XXU3BTK1 posted kernel source.
• Updated to TWRP 3.5.0 release built from omni-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:

• android_device_samsung_gta3xlwifi
• android_device_samsung_gta3xl

Donations:

• Your support is always appreciated! Just click here.

 

[ianmacd]

Good work. Well done.

 

[beta990]

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]

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.

 

[cambunch]

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.

 

[3c]

[*]Ensure you're running the T510XXU1ASC7 release

I just received the tablet and it's running T510XXU1ASCE, I suppose I should downgrade first, if possible, or will it work as-is?

 

[Magendanz]

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.

 

[3c]

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).

 

[massivekind]

@Magendanz, l'm willing to test twrp for the 515 model. Dm me ?

 

[Awesomeslayerg]

I did a backup and did a restore but it kept bootlooping idk if this was because i rooted it first or what..

 

[Awesomeslayerg]

They released the latest kernel

 

[Magendanz]

They released the latest kernel

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).

 

[messi2050]

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 ?

 

[Magendanz]

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]

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

 

[b2574028]

Are there any release for SM-T515?

 

[Magendanz]

Are there any release for SM-T515?

I have a volunteer to test it, but I was waiting for Samsung to post kernel source for the May 2019 update (T515XXU1ASEH).

 

[redexit]

'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]

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.

 

[redexit]

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.