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

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

Search This thread

Abo7amed

Member
Jan 13, 2013
11
0
SM-T510 Please help me how to fix this ?!
I get Custom Binary ( Recovery ) Blocked by OEM Lock
 
Last edited:

Abo7amed

Member
Jan 13, 2013
11
0
You have first to unlock bootloader, see instruction also noted on first page
Already did!
16312867072727445538078489933039.jpg
 

Magendanz

Senior Member
Mar 25, 2008
836
806
Issaquah, WA
www.Vote4Chad.com
New release just posted. Note that the TWRP 3.6.0 release isn't official yet, so there could still be some bugs. This is also now based on AOSP 11 (vs. Omni 9.0), which we can do now that we have an Android 11 kernel from Samsung.

Downloads:
Change Log:
v3.6.0_11-1:

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

demoneg

Member
Feb 21, 2011
21
0
I am running CAOS 313+ and latest vendor.img from Samsung firmware, however, latest TWRP here just keeps rebooting, I have to get back to download mode and install older TWRP, am I missing something regarding installing latest "kernel"?

I also tried this:
- Fully installed latest Nexus room you posted online
- Then reboot, TWRP still reboot looping
 

jaladhjin

Senior Member
Jul 13, 2013
878
72
twrp-featured.jpg


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.
I'm not seeing this option to Patch a file in my Magisk Manager.

I've gone all through the settings & am not seeing it.

Has it been deprecated?

I'm looking to upgrade to: twrp-3.6.0_11-1-T510XXU5CUJ1-20211125.img from an older TWRP & upgrade my ROM after.

Magisk version 23.0
App 23.0 (23000)

Also can I flash this recovery img with Flashify?

Or better to do in TWRP?

Lastly will just flashing the newest ROM from here: https://forum.xda-developers.com/t/...geos-17-1-for-galaxy-tab-a-10-1-2019.4060153/

Take care of updating my TWRP too?

I'm still on the August 08 2020 build.
 

waterpolo

Senior Member
Aug 6, 2008
846
196
Naarden (NL)
I'm not seeing this option to Patch a file in my Magisk Manager.

I've gone all through the settings & am not seeing it.

Has it been deprecated?

I'm looking to upgrade to: twrp-3.6.0_11-1-T510XXU5CUJ1-20211125.img from an older TWRP & upgrade my ROM after.

Magisk version 23.0
App 23.0 (23000)

Also can I flash this recovery img with Flashify?

Or better to do in TWRP?

Lastly will just flashing the newest ROM from here: https://forum.xda-developers.com/t/...geos-17-1-for-galaxy-tab-a-10-1-2019.4060153/

Take care of updating my TWRP too?

I'm still on the August 08 2020 build.
You can use the 'old' TWRP to upgrade to 'new' TWRP to flash the image (*.img) file and choose the option 'Recovery'. Reboot to recovery and you will seen the new TWRP.
 
  • Like
Reactions: jaladhjin

jaladhjin

Senior Member
Jul 13, 2013
878
72
You can use the 'old' TWRP to upgrade to 'new' TWRP to flash the image (*.img) file and choose the option 'Recovery'. Reboot to recovery and you will seen the new TWRP.
Thank you!

So I did that & went through the process to patch TWRP with Magisk I figured out how.

When flashing the patched TWRP in TWRP I'm flashing the patched image to boot or recovery?

I'm accustomed to just flashing Magisk.zip which seems to be a thing of the past :-(

 

waterpolo

Senior Member
Aug 6, 2008
846
196
Naarden (NL)
Thank you!

So I did that & went through the process to patch TWRP with Magisk I figured out how.

When flashing the patched TWRP in TWRP I'm flashing the patched image to boot or recovery?

I'm accustomed to just flashing Magisk.zip which seems to be a thing of the past :-(

I patch the boot.img for working Magisk.
I install the TWRP image without patching with the Recovery option.
 
  • Like
Reactions: jaladhjin

jaladhjin

Senior Member
Jul 13, 2013
878
72
Magisk is still working in Android 11.
On my phone with Android 12 Magisk is also working.
Thank you for confirming that please could you help me get it working I am used to the old process of simply flashing Magisk.zip in TWRP but that no longer seems to be the process.

I am using this rom: https://forum.xda-developers.com/t/...2019-galaxy-tab-a-10-1-sm-t510.4234889/page-2

I see this info: https://topjohnwu.github.io/Magisk/install.html

But it seems like on the SM-T510 Ramdisk says No so do I patch recovery.img not boot.img ?

I remember from your other message you said you patched boot.img but was that on another device?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I'm not seeing this option to Patch a file in my Magisk Manager.

    I've gone all through the settings & am not seeing it.

    Has it been deprecated?

    I'm looking to upgrade to: twrp-3.6.0_11-1-T510XXU5CUJ1-20211125.img from an older TWRP & upgrade my ROM after.

    Magisk version 23.0
    App 23.0 (23000)

    Also can I flash this recovery img with Flashify?

    Or better to do in TWRP?

    Lastly will just flashing the newest ROM from here: https://forum.xda-developers.com/t/...geos-17-1-for-galaxy-tab-a-10-1-2019.4060153/

    Take care of updating my TWRP too?

    I'm still on the August 08 2020 build.
    You can use the 'old' TWRP to upgrade to 'new' TWRP to flash the image (*.img) file and choose the option 'Recovery'. Reboot to recovery and you will seen the new TWRP.
    1
    Thank you!

    So I did that & went through the process to patch TWRP with Magisk I figured out how.

    When flashing the patched TWRP in TWRP I'm flashing the patched image to boot or recovery?

    I'm accustomed to just flashing Magisk.zip which seems to be a thing of the past :-(

    I patch the boot.img for working Magisk.
    I install the TWRP image without patching with the Recovery option.
    1
    Attatched the patched boot.img with Magisk 23
  • 25
    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 (T510XXU5CUJ1).
    • 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.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:
    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:

    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
    5
    New build posted for T510XXU5CUF4. Note that the bootloader in this OEM firmware release has rollback prevention, so you might want to give some thought first before upgrading.

    Downloads:
    Build archives:

    Change Log:
    v3.5.2_9-0:
    • Updated to T510XXU5CUF4 posted kernel source.