[GUIDE][SM-T510/T515]Unlock/TWRP/Odin HowTo/Root - Tab A 10.1 (2019)

Search This thread

Desertio

Senior Member
Sep 11, 2011
389
38
Houston, TX
OnePlus 10 Pro
Okay, I've tried this 20+times now and it fails every time. I unlocked my bootloader. Reboot, go into developer options and make sure OEM unlocking and usb debugging is on. I restart into download mode. Flash current firmware and that is successful. I reboot system, go through setup and back into developer options and make sure it is all on and that OEM is there (if not, i restart and that fixes it). At this point I reboot into download mode and flash twrp md5 through Odin ap, its successful and phone boots into twrp. Through twrp i flash multi-disabler.zip and its successful also. After this everything fails no matter what i do. In twrp i flash magisk.zip and it fails, I try flash either custon ROM.zip and it fails, This in turn causes emergency recovery mode on boot and i have to start fresh with firmware. I do complete wipe as directed and constantly clean dalvik. I am at a loss here and any help is greatly appreciated. Bwt its the SM-T510. Thank you for reading
 

rhythm_dx

Senior Member
Okay, I've tried this 20+times now and it fails every time. I unlocked my bootloader. Reboot, go into developer options and make sure OEM unlocking and usb debugging is on. I restart into download mode. Flash current firmware and that is successful. I reboot system, go through setup and back into developer options and make sure it is all on and that OEM is there (if not, i restart and that fixes it). At this point I reboot into download mode and flash twrp md5 through Odin ap, its successful and phone boots into twrp. Through twrp i flash multi-disabler.zip and its successful also. After this everything fails no matter what i do. In twrp i flash magisk.zip and it fails, I try flash either custon ROM.zip and it fails, This in turn causes emergency recovery mode on boot and i have to start fresh with firmware. I do complete wipe as directed and constantly clean dalvik. I am at a loss here and any help is greatly appreciated. Bwt its the SM-T510. Thank you for reading
Did you wipe/format data after flashing multi disabler?
 
  • Like
Reactions: J.Michael

rhythm_dx

Senior Member
I'm not seeing anything obviously wrong with your process, then. It can be pretty confusing to work through two sets of instructions, with one nested inside the other, but it appears you're doing it correctly. Best I can recommend is redownload the files in case something is corrupted. I've had that happen before, even though nothing seems wrong with a file in Windows.
 
  • Like
Reactions: J.Michael

Desertio

Senior Member
Sep 11, 2011
389
38
Houston, TX
OnePlus 10 Pro
Just wanna bring attention to this part again, because unless the multi-disabler is ****ed it's most likely that wipe was chosen rather than the format option.
I only format data and do not do a full wipe/factory reset. Multi disabler succeeds every time I flash it.
Also, to be clear, the Magisk zip i download is the apk and i rename to zip right?
 
  • Like
Reactions: Clamtacos

Desertio

Senior Member
Sep 11, 2011
389
38
Houston, TX
OnePlus 10 Pro
Alright. Update. I kept getting errors on both Rom's so i decided to not flash one. I flashed firmware successfully, then flashed twrp.md5 and booted into recovery. In twrp i flashed multi-disabler zip and then did <format data. Then rebooted into recovery and flashed fresh download of magisk and it took (Must have been a bad download before). Then, instead of flashing the dang ROM and risking it fail for the 30th time, i just rebooted system and let it do tis work. It topok about 20 minutes to get off of the boot screen but it finally did and i have root. That being said. In magisk I do not have Ramdisk. I know Samsung doesn't but im not sure the complications that arise from this. Any one have a nugget of knowledge they will share with me about this. Thank you to all who helped and thank y'all for reading this.
 

lewmur

Senior Member
Apr 30, 2011
2,401
514
Alright. Update. I kept getting errors on both Rom's so i decided to not flash one. I flashed firmware successfully, then flashed twrp.md5 and booted into recovery. In twrp i flashed multi-disabler zip and then did <format data. Then rebooted into recovery and flashed fresh download of magisk and it took (Must have been a bad download before). Then, instead of flashing the dang ROM and risking it fail for the 30th time, i just rebooted system and let it do tis work. It topok about 20 minutes to get off of the boot screen but it finally did and i have root. That being said. In magisk I do not have Ramdisk. I know Samsung doesn't but im not sure the complications that arise from this. Any one have a nugget of knowledge they will share with me about this. Thank you to all who helped and thank y'all for reading this.
Hint: If you get errors that others don't, you are doing something wrong. There are many steps to get custom ROM installed and if you miss JUST ONE, it won't work. Rather than trying the same thing over and over again, list here EXACTLY what steps you've taken, when it fails and what error you get, and maybe someone here can point out your mistake.
 
  • Like
Reactions: J.Michael

dedeoglumrt

Member
Sep 26, 2021
31
2
i get device x binary x errors. kernel rev. errors. how can i resovle this guys. i almots broke the device...
 

framC0

Member
Mar 17, 2022
11
0
The purpose of this thread is to have one post with links to all of the following guides:

Unlock Bootloader by @mingkee
TWRP Recovery by @Magendanz
Custom ROM Nexus Stock by @Magendanz - current release is SM-T510 only
Custom ROM LineageOS 16.0 by @Magendanz - SM-T510 only

All credit to @Magendanz and @mingkee for those.

Below are my own observations which supplement but do not replace the guides above. The original posts includes important information not quoted below. You need to read the relevant guides above (depending on what you want to do), and you may get some additional benefit from reading my thoughts below before following the guides above.


***

Contents

  • Overview
  • Downloads
  • Buttons
  • Unlock Bootloader
  • Rooting
  • How to use Odin


***

Overview
To root your device you need to first install the TWRP recovery. @Magendanz includes TWRP in his ROMs, so you have two options, TWRP without custom ROM, or TWRP with custom ROM.
To be able to install a ROM or recovery you first need to unlock your bootloader.

WARNING - take note of the kernel version of the custom ROM or TWRP you intend to use, e.g. T510XXU2ASI4. Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware/ROM/TWRP with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.

There are then two paths:
Original ROM:
  1. Read the TWRP instructions
  2. Download any zip you plan to flash (install) from TWRP (e.g. Multi-disable and Magisk) and save to your sdcard. Internal memory will be wiped (formatted) as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
  3. Unlock Bootloader - Click to see original post:
    Disclaimer: your tablet warranty will void. Proceed with your own risk
    Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
    Prerequisite:
    Host PC installed Samsung Smart Switch
    USB C cable
    Your tablet battery should be 70% or higher and you have done data backup
    OEM Unlock enabled
    1. About tablet
    2. Software version
    3. Hit Build Number few times
    4. Enable USB Debugging
    5. Allow your host computer
    6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
    https://www.xda-developers.com/fix-m...galaxy-note-8/
    Are you ready? Let's do it.
    1. Turn your tablet off and disconnect USB cable
    2. Press and hold both volume up and down buttons and connect to host computer
    3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
    4. If you see a warning screen on boot, the bootloader is unlocked.
  4. Install TWRP recovery .tar.md5 file via Odin by following the TWRP instructions.
    Click to see instructions from the TWRP OP -
    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, select your update (.zip) file, and then swipe to install
    Reboot to system

  5. [Optional] Install Magisk to get root - see Rooting section below

Don't forget to install Multi-disabler before doing Format Data! (as described in the guide) - In TWRP tap Install then select the Multi-disabler zip file.

Custom ROM [Allow several hours for the custom ROM download]:
  1. Read the custom ROM instructions: Nexus Stock / LineageOS 16.0
  2. Download any zip you plan to flash (install) from TWRP (e.g. Magisk) and save to your sdcard. Internal memory will be wiped as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
  3. Unlock Bootloader - Click to see original post:
    Disclaimer: your tablet warranty will void. Proceed with your own risk
    Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
    Prerequisite:
    Host PC installed Samsung Smart Switch
    USB C cable
    Your tablet battery should be 70% or higher and you have done data backup
    OEM Unlock enabled
    1. About tablet
    2. Software version
    3. Hit Build Number few times
    4. Enable USB Debugging
    5. Allow your host computer
    6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
    https://www.xda-developers.com/fix-m...galaxy-note-8/
    Are you ready? Let's do it.
    1. Turn your tablet off and disconnect USB cable
    2. Press and hold both volume up and down buttons and connect to host computer
    3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
    4. If you see a warning screen on boot, the bootloader is unlocked.
  4. Install custom ROM .tar.md5 file (which includes TWRP) via Odin, by following the custom ROM instructions.
    Click for instructions from OP for Nexus Stock -

    Unlock bootloader
    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, wipe data if installing for first time. (Not necessary for incremental upgrades.)
    Reboot to system



    Click for instructions from OP for LineageOS 16.0 -

    Unlock bootloader
    Hold Vol Up & Vol Down buttons during restart to enter Download mode
    Install custom ROM to AP with Odin
    When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
    Reboot to system


    Note that "wipe data" means Wipe -> Format Data
  5. [Optional] Install Magisk to get root - see Rooting section below
Dirty flash: If you had installed the custom ROM previously and are now updating to a newer version then all you need to do is use Odin to flash the latest tar.md5 file. It will enter TWRP after the flash, no need to Format Data, just reboot to system. Alternatively if the ROM developer provides a flashable zip, you can update with TWRP.


Some users have reported getting stuck on the boot animation after a dirty flash, I don't know if that still happens with the latest versions of @Magendanz's ROMs. If it does the solution is to boot into recovery and flash Multi-disabler.

For TWRP versions before v3.3.1-5 you MUST format the encrypted data partition after flashing TWRP or TWRP will hang on the splash screen. For later versions of TWRP you should format the encrypted data partition after flashing TWRP so that TWRP can access the data partition.

You can use TWRP to flash zip files, e.g. to install newer versions of TWRP itself, or custom ROM zips, as follows:

1. Download the zip file
2. Boot into Recovery
3. Install -> Select the TWRP zip file
4. Reboot to System

You *cannot* use TWRP to flash tar.md5 files, and you must use Odin at least once to get TWRP installed in the first place.



***

Downloads
You may not need ALL of these downloads, this is just a handy list of some of the downloads mentioned in the guides

Samsung Smart Switch (for USB drivers)
Magisk - Download Latest Stable zip file to flash in TWRP (see Rooting below) and Latest Magisk Manager to install as an app
Odin
Multi-disabler (required by TWRP only tar.md5)
Firmwares SM-T510 SM-T515 - allow several hours, at least, for the firmware downloads to complete
WARNING - take note of the kernel version of the custom ROM you intend to use, e.g. T510XXU2ASI4 and your current version (Settings | About tablet). Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.


***

Buttons

  • Power On: Hold the Power button for 3 seconds
  • Boot to Recovery (Before unlocking bootloader) Power On and Press and hold Power and Volume Up until you see Recovery running.
  • Boot to Recovery (After unlocking bootloader) Power On and then press Power and Volume Up as soon as you see the unlocked bootloader warning. No need to hold.
  • Boot to Download: Press and hold Volume Up and Volume Down and connect to computer with USB cable.


Click to see Unlock Bootloader original post...
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.

After unlocking the bootloader every time you turn the device on a warning about the bootloader being unlocked will appear for ten seconds, unless you dismiss it by pressing the power button.
If you are holding the Power button and Volume Up to boot into recovery this warning screen will flash on and off briefly, at which point you can stop holding down the buttons. Recovery will start a few seconds later.


***

Rooting
Root can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). From Magisk 19.3 onwards there is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
You can even install Magisk the first time TWRP runs after flashing one of @Magendanz's tar.md5 files in Odin.
To do so follow @Magendanz's guide up to the point where you have Factory Reset/Wiped Data in TWRP then:

1. Reboot to Recovery
2. Install -> Select the Magisk zip file
3. Reboot to System
4. Install Magisk Manager

Otherwise you can start by installing the Magisk Manager app at any time.

Note: You will need to re-install Magisk after a TWRP update.



***

How to use Odin
Odin is a Windows tool for firmware flashing on Samsung devices via USB. Odin can be used to flash firmware, kernels, recoveries or ROMs to your device.

* Firmware zip (or rar) files need to be extracted and then install via Odin. Flashable zip files (e.g. new versions of TWRP or custom ROMs) can only be flashed from TWRP, not Odin, though you need to flash a TWRP tar.md5 file using Odin in the first place *

Preparing the device
  • Charge the device to at least 80%.
  • Bootloader unlocked
  • In developer options, turn USB debugging on. Click on Build number in Settings several times until you see the toast notification "You are now a developer". Go to Developer Options and turn on the USB debugging option.
    - In the stock ROM Build number can be found here: Settings | About Tablet | Software Information and the "Developer Options" menu item appears below About Tablet in the main Settings screen.
    - The locations may be different in custom ROMs. In the Nexus based ROM the locations are Settings | About phone for Build number, and System | Advanced for Developer options
  • Turn off the phone, hold down the Volumn Up and Volume Down buttons and connect the device to the computer with a USB cable (preferably the cable that came with the device). A warning will appear saying "A custom OS can cause critical problems in phone and installed applications".
  • Press the Volume Up button briefly to continue.

The device is now in Download mode.

Install Odin version 3.13.3.

When you run it a dialog will pop up in English and Chinese. Click OK.

The Odin window looks like this:

View attachment 4853507

Above ID:COM on the left is the progress bar, below ID:COM is the connection indicator which changes colour (and shows the COM id) when your device is connected in Download mode.

Below that is the "Log" tab which gives verbose output showing what's happening. Normally you will not need to go near the Option or Pit tabs.

There are four buttons in the middle of the screen corresponding to the types of file that you can flash: BL (boot loader), AP (Application Processor, PDA), CP (Core Processor, phone/modem), CSC (Consumer Software Customization)

Depending on what you are flashing you will need to load one or more files. To load each file type click on the corresponding button and select the file to be flashed.
Odin will show the following in the "Log" while the file is being processed:


Code:
<OSM> Enter CS for MD5
<OSM> Check MD5... Do not unplug the cable...
<OSM> Please wait...
For AP_ files this can take some time, during which the button will remain greyed out. When the file has loaded the "Log" will say:

Code:
<OSM> Checking MD5 finished Successfully...
<OSM> Leaving CS...
... the button will be enabled again, the text field beside the button will be filled with the fullpath of the selected file, and the checkbox next to the button ticked.

@Magendanz's TWRP and ROM files are both single files flashed to AP, so just click the AP button and the select the tar.md5 file.

If you are flashing firmware ( e.g. https://samfrew.com/model/SM-T510/ ) unzip the download into separate files and load each with the correspong button. The filenames begin with BL_..., AL_... etc so you'll know which is which.
There will be both a CSC_ and HOME_CSC_ file. You could flash HOME_CSC_ to keep your device's settings and data but normally you should use CSC_ for a clean install. If you have an SM-T515 then you'll have a CP_ file too, but if you have a SM-T510 then your firmware will not have a CP_ file because that's for the phone (SM-T510 is wifi only), so just leave CP alone, only load BL, AP and CSC.


Verify that your device is connected in download mode. The box below ID:COM should show the COM id of the connected device and there should be a line in the "log" saying something like <ID:0/008> Added!!

Click Start to flash the selected files. DO NOT UNPLUG THE CABLE UNTIL THE PROCESS IS COMPLETE. You can follow the progress in Odin and on the Download screen on your device. To flash a ROM or firmware will take several minutes.

If you are flashing one of @Magendanz's tar.md5 files then your device will reboot into TWRP once the install is complete. At that point continue following @Magendanz's guide.

Note: You will need to turn on USB debugging again after flashing firmware, or a clean install of a ROM, before you can use Odin to flash again. Also check that OEM unlock is still turned on.
SM-510. Stucked at "You *cannot* use TWRP to flash tar.md5 files, and you must use Odin at least once to get TWRP installed in the first place." Im on Android 11 with T510XXU5CUL1 and when flash twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar with Odin it just throw me to "Emergency screen" with no system and need to flash it again.

SM-T510
EDIT:
i solved this by flashing Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and NOT the T510XXU5CUL1 in AP using ODIN. After Flash will restart and the TWRP automatically starts (this ROM already comes with TWRP installed) and did WIPE/FORMAT DATA and boot to System. Do all setup and add google account. Install Magisk-v23.0.apk. Restart to TWRP and flash same Magisk-v23.0.apk. Done. You have now rooted 510 and with no "RAMDISK: yes"
Bootloader unlocked, USB Debug ON, File Transfer USB.
 
Last edited:

framC0

Member
Mar 17, 2022
11
0
I believe a critical issue is being missed in this process, and that is the T510 doesn't have a ramdisk available for boot, so Magisk must be installed to the recovery partition. Below is a screenshot of Magisk Manager data from my own tablet:
View attachment 5261043
And per the Magisk installation instructions:

In order to boot into system with active Magisk, one has to essentially boot into recovery. From the Magisk in Recovery section (Bixby button references can be ignored):

I can understand now why John Wu was spitting nails mad when Google switched to dynamic partitions with system-as-root: it completely effs up the architecture for rooting with Magisk. :mad:☠️

I don't know why Google and manufacturers persist in making it messy to nigh-impossible for end users--who desire to do so--to have full control of their own devices. Stupid. Just stupid. 😾 Usunoro...

On the positive side, I hope this helps everyone trying to root their T510 tablets, and explains the weirdness people may have encountered.

(P.S. Since hardware attestation is used on the T510, SafetyNet won't pass, no matter what. There aren't any modules that can address this, given that hardware is being used for the evaluation. Another baka change! Also, I'm sticking with Pie since I can't stand Scoped Storage. Can't. Stand. It.)

Fur and Purrs --
--
King Cheetah
i have no RAMDISK and im rooted! Just dont use the OFW but a CFW. done.

EDIT: and flash MAGISK23.APK with TWRP.
 
Last edited:

J.Michael

Recognized Contributor
Jan 20, 2018
1,646
1,818
Samsung Galaxy Tab A series
I believe a critical issue is being missed in this process, and that is the T510 doesn't have a ramdisk available for boot, so Magisk must be installed to the recovery partition. Below is a screenshot of Magisk Manager data from my own tablet:
View attachment 5261043
And per the Magisk installation instructions:

In order to boot into system with active Magisk, one has to essentially boot into recovery. From the Magisk in Recovery section (Bixby button references can be ignored):

I can understand now why John Wu was spitting nails mad when Google switched to dynamic partitions with system-as-root: it completely effs up the architecture for rooting with Magisk. :mad:☠️

I don't know why Google and manufacturers persist in making it messy to nigh-impossible for end users--who desire to do so--to have full control of their own devices. Stupid. Just stupid. 😾 Usunoro...

On the positive side, I hope this helps everyone trying to root their T510 tablets, and explains the weirdness people may have encountered.

(P.S. Since hardware attestation is used on the T510, SafetyNet won't pass, no matter what. There aren't any modules that can address this, given that hardware is being used for the evaluation. Another baka change! Also, I'm sticking with Pie since I can't stand Scoped Storage. Can't. Stand. It.)

Fur and Purrs --
--
King Cheetah
Originally, we were told that if there is no ramdisk in the boot.img, then Magisk must be installed in the recovery partition.

Since then, Magisk was updated to insert a ramdisk if there is no ramdisk in the boot.img. This does not always help. However, there are cases (notably MIUI / Xiaomi[sic]) where, in spite of the original boot.img not having a ramdisk, the bootloader and kernel are prepared to use a ramdisk. In those magical cases, the ramdisk inserted by Magisk works.

I don't think I've seen any reference in the Magisk thread to some Samsung devices working this way. Someone who can actually confirm that it works should post there.
 

waeking

Member
Nov 18, 2009
27
0
I unlocked the oem bootloader once and got the warning screen that it was unlocked. However I did not immediately hold down the vol up/down and after a few reboots it is now locked again. instead of waiting 7 days there is a link to get around this.

6. If you don't see OEM Unlocking, wait for 7 days or do the following trick [URL='https://www.xda-developers.com/fix-m...galaxy-note-8/']https://www.xda-developers.com/fix-m...galaxy-note-8/[/URL]

This link is not working... Could someone please update the link? or point me in the right direction
 

System23

Member
Hey, first of all thanks for the nice guide. I followed it to flash Nexus ROM for my T515 but I messed up the tablet and ended up in the emergency recovery mode. No biggie though, I have flashed back to original stock ROM but I can't seem to find OEM unlock option now in my developer settings (the tablet is still unlocked though, I have to use my power key while turning on to skip the warning screen)

So basically, now I can't figure out why I can't flash the nexus rom but was able to flash official firmware and why I don't have OEM unlock option in my developer settings.
Also, I made a clean install of Windows 10, downloaded the good drivers and used my best type C cord and plugged it directly into the motherboard and not into the front I/O panel, and still no luck with the nexus ROM.

P.S. I'm tagging @Magendanz, just in case you find it interesting how odin refuses to flash your Nexus rom. If you want to, I could test the nexus rom on the latest T515 firmware, perhaps the fw refuses to go below the current version I'm on?

P.P.S : added Odin output
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3048 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> param.bin
<ID:0/003> product.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)



Download mode screen spits out Only official released binaries are allowed to be flashed so I guess it is a matter of bootloader unlocking after all?
when you dont find the OEM Unlock Setting, than was Knox Triggered and to Reset this you must wait 7 Days wile the Phone is still connecting with Internet!!! or you Flash the StockROM "T510XXU5CVB1" with Odin again!!! Than you can normaly Boot your System and have the Full DeveloperOptions!!! when you have the Message System-Binary cant Flash at Download Mode ,you must too Flash the StockROM "T510XXU5CVB1" to Reset to Original than you have a new chance to Flash Custom Files!! Dont forgett to start After first Flash TWRP to reboot to TWRP than when ya not do , the System Overrides the Flashed custom Recovery!!! in most Szenarios the TWRP Starts Automaticly

I'm a bit confused on what I've been doing wrong and where to proceed from here. These are the steps I've done on my most recent try:

1) Downloaded:
- Samsung Smart Switch
- TWRP 3.3.1.5 .tar.md5
- Magisk (Latest Magisk Manager)
- Odin
- Firmware T510 (XAR-T510XXU1ASEF-20190605151710.zip)
- Multi-disabler

2) Followed Unlock Bootloader from mingkee
3) Installed TWRP recovery via Odin

4) Rebooted back into stock ROM
5) Installed Magisk.apk
6) Using Magisk Manager > Selected AP_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship_meta_OS9.tar.md5
7) That gave me magisk_patched.tar which I moved over to my desktop

8) Boot back into download mode
9) Flash the magisk_patched under AP, TWRP under BL, and HOME_CSC under CSC
10) Then Odin said it failed

Honestly I was pretty confused by the steps going from guide to guide so I'm not sure where I went wrong.

Also I'm not sure where I'm suppose to be flashing multi-disabler. The guide just said don't forget to install it but I'm not sure at which step I should be installing it via TWRP.

Any help would be appreciated.

Edit:

I tried again going with just steps from [GUIDE]Comprehensive T510 root guide.

I unlocked bootloader > patched the AP file I downloaded > Tried flashing the AP file only using Odin and it gave me an error:

"Only official released binaries are allowed to be flashed"
So ok you have done it so!! Do Following
1# Flash via Odin "T510XXU5CWA1" StockROM
2# Flash via Odin "twrp-3.7.0_11-0-T510XXU5CVG2-20221102.tar"

twrp-3.7.0_11-0-T510XXU5CVG2-20221102.tar.md5"

3# Start TWRP and Copy Following Files!!!
Magisk-v25.2.apk to /sdcard/Magisk-v25.2.zip yes rename apk to zip so you can Flash it with TWRP!!
Multi-disabler.zip to /sdcard/

Magisk_BusyBox_Module_Uninstaller

4# Flash the 2 Copied Zip Files and youre done!!!
5# when you now start the system you found a App Magisk and it effort you to download, do this and start the Magisk-Manager than reboot the system to Complete the Setup process!!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    The purpose of this thread is to have one post with links to all of the following guides:

    Unlock Bootloader by @mingkee
    TWRP Recovery by @Magendanz
    Custom ROM Nexus Stock by @Magendanz - current release is SM-T510 only
    Custom ROM LineageOS 16.0 by @Magendanz - SM-T510 only

    All credit to @Magendanz and @mingkee for those.

    Below are my own observations which supplement but do not replace the guides above. The original posts includes important information not quoted below. You need to read the relevant guides above (depending on what you want to do), and you may get some additional benefit from reading my thoughts below before following the guides above.

    ***​
    Contents
    • Overview
    • Downloads
    • Buttons
    • Unlock Bootloader
    • Rooting
    • How to use Odin

    ***​
    Overview
    To root your device you need to first install the TWRP recovery. @Magendanz includes TWRP in his ROMs, so you have two options, TWRP without custom ROM, or TWRP with custom ROM.
    To be able to install a ROM or recovery you first need to unlock your bootloader.

    WARNING - take note of the kernel version of the custom ROM or TWRP you intend to use, e.g. T510XXU2ASI4. Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware/ROM/TWRP with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.

    There are then two paths:
    Original ROM:
    1. Read the TWRP instructions
    2. Download any zip you plan to flash (install) from TWRP (e.g. Multi-disable and Magisk) and save to your sdcard. Internal memory will be wiped (formatted) as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
    3. Unlock Bootloader - Click to see original post:
      Disclaimer: your tablet warranty will void. Proceed with your own risk
      Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
      Prerequisite:
      Host PC installed Samsung Smart Switch
      USB C cable
      Your tablet battery should be 70% or higher and you have done data backup
      OEM Unlock enabled
      1. About tablet
      2. Software version
      3. Hit Build Number few times
      4. Enable USB Debugging
      5. Allow your host computer
      6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
      https://www.xda-developers.com/fix-m...galaxy-note-8/
      Are you ready? Let's do it.
      1. Turn your tablet off and disconnect USB cable
      2. Press and hold both volume up and down buttons and connect to host computer
      3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
      4. If you see a warning screen on boot, the bootloader is unlocked.

    4. Install TWRP recovery .tar.md5 file via Odin by following the TWRP instructions.
      Click to see instructions from the TWRP OP -
      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, select your update (.zip) file, and then swipe to install
      Reboot to system
    5. [Optional] Install Magisk to get root - see Rooting section below

    Don't forget to install Multi-disabler before doing Format Data! (as described in the guide) - In TWRP tap Install then select the Multi-disabler zip file.

    Custom ROM [Allow several hours for the custom ROM download]:
    1. Read the custom ROM instructions: Nexus Stock / LineageOS 16.0
    2. Download any zip you plan to flash (install) from TWRP (e.g. Magisk) and save to your sdcard. Internal memory will be wiped as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
    3. Unlock Bootloader - Click to see original post:
      Disclaimer: your tablet warranty will void. Proceed with your own risk
      Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
      Prerequisite:
      Host PC installed Samsung Smart Switch
      USB C cable
      Your tablet battery should be 70% or higher and you have done data backup
      OEM Unlock enabled
      1. About tablet
      2. Software version
      3. Hit Build Number few times
      4. Enable USB Debugging
      5. Allow your host computer
      6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
      https://www.xda-developers.com/fix-m...galaxy-note-8/
      Are you ready? Let's do it.
      1. Turn your tablet off and disconnect USB cable
      2. Press and hold both volume up and down buttons and connect to host computer
      3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
      4. If you see a warning screen on boot, the bootloader is unlocked.
    4. Install custom ROM .tar.md5 file (which includes TWRP) via Odin, by following the custom ROM instructions.
      Click for instructions from OP for Nexus Stock -

      Unlock bootloader
      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, wipe data if installing for first time. (Not necessary for incremental upgrades.)
      Reboot to system


      Click for instructions from OP for LineageOS 16.0 -

      Unlock bootloader
      Hold Vol Up & Vol Down buttons during restart to enter Download mode
      Install custom ROM to AP with Odin
      When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
      Reboot to system

      Note that "wipe data" means Wipe -> Format Data
    5. [Optional] Install Magisk to get root - see Rooting section below
    Dirty flash: If you had installed the custom ROM previously and are now updating to a newer version then all you need to do is use Odin to flash the latest tar.md5 file. It will enter TWRP after the flash, no need to Format Data, just reboot to system. Alternatively if the ROM developer provides a flashable zip, you can update with TWRP.


    Some users have reported getting stuck on the boot animation after a dirty flash, I don't know if that still happens with the latest versions of @Magendanz's ROMs. If it does the solution is to boot into recovery and flash Multi-disabler.

    For TWRP versions before v3.3.1-5 you MUST format the encrypted data partition after flashing TWRP or TWRP will hang on the splash screen. For later versions of TWRP you should format the encrypted data partition after flashing TWRP so that TWRP can access the data partition.

    You can use TWRP to flash zip files, e.g. to install newer versions of TWRP itself, or custom ROM zips, as follows:

    1. Download the zip file
    2. Boot into Recovery
    3. Install -> Select the TWRP zip file
    4. Reboot to System

    You *cannot* use TWRP to flash tar.md5 files, and you must use Odin at least once to get TWRP installed in the first place.


    ***​
    Downloads
    You may not need ALL of these downloads, this is just a handy list of some of the downloads mentioned in the guides

    Samsung Smart Switch (for USB drivers)
    Magisk - Download Latest Stable zip file to flash in TWRP (see Rooting below) and Latest Magisk Manager to install as an app
    Odin
    Multi-disabler (required by TWRP only tar.md5)
    Firmwares SM-T510 SM-T515 - allow several hours, at least, for the firmware downloads to complete
    WARNING - take note of the kernel version of the custom ROM you intend to use, e.g. T510XXU2ASI4 and your current version (Settings | About tablet). Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.

    ***​
    Buttons
    • Power On: Hold the Power button for 3 seconds
    • Boot to Recovery (Before unlocking bootloader) Power On and Press and hold Power and Volume Up until you see Recovery running.
    • Boot to Recovery (After unlocking bootloader) Power On and then press Power and Volume Up as soon as you see the unlocked bootloader warning. No need to hold.
    • Boot to Download: Press and hold Volume Up and Volume Down and connect to computer with USB cable.

    ***​
    Unlock Bootloader
    Click to see Unlock Bootloader original post...
    Disclaimer: your tablet warranty will void. Proceed with your own risk
    Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
    Prerequisite:
    Host PC installed Samsung Smart Switch
    USB C cable
    Your tablet battery should be 70% or higher and you have done data backup
    OEM Unlock enabled
    1. About tablet
    2. Software version
    3. Hit Build Number few times
    4. Enable USB Debugging
    5. Allow your host computer
    6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
    https://www.xda-developers.com/fix-m...galaxy-note-8/
    Are you ready? Let's do it.
    1. Turn your tablet off and disconnect USB cable
    2. Press and hold both volume up and down buttons and connect to host computer
    3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
    4. If you see a warning screen on boot, the bootloader is unlocked.

    After unlocking the bootloader every time you turn the device on a warning about the bootloader being unlocked will appear for ten seconds, unless you dismiss it by pressing the power button.
    If you are holding the Power button and Volume Up to boot into recovery this warning screen will flash on and off briefly, at which point you can stop holding down the buttons. Recovery will start a few seconds later.

    ***​
    Rooting
    Root can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). From Magisk 19.3 onwards there is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
    You can even install Magisk the first time TWRP runs after flashing one of @Magendanz's tar.md5 files in Odin.
    To do so follow @Magendanz's guide up to the point where you have Factory Reset/Wiped Data in TWRP then:

    1. Reboot to Recovery
    2. Install -> Select the Magisk zip file
    3. Reboot to System
    4. Install Magisk Manager

    Otherwise you can start by installing the Magisk Manager app at any time.

    Note: You will need to re-install Magisk after a TWRP update.


    ***​
    How to use Odin
    Odin is a Windows tool for firmware flashing on Samsung devices via USB. Odin can be used to flash firmware, kernels, recoveries or ROMs to your device.

    * Firmware zip (or rar) files need to be extracted and then install via Odin. Flashable zip files (e.g. new versions of TWRP or custom ROMs) can only be flashed from TWRP, not Odin, though you need to flash a TWRP tar.md5 file using Odin in the first place *

    Preparing the device
    • Charge the device to at least 80%.
    • Bootloader unlocked
    • In developer options, turn USB debugging on. Click on Build number in Settings several times until you see the toast notification "You are now a developer". Go to Developer Options and turn on the USB debugging option.
      - In the stock ROM Build number can be found here: Settings | About Tablet | Software Information and the "Developer Options" menu item appears below About Tablet in the main Settings screen.
      - The locations may be different in custom ROMs. In the Nexus based ROM the locations are Settings | About phone for Build number, and System | Advanced for Developer options
    • Turn off the phone, hold down the Volumn Up and Volume Down buttons and connect the device to the computer with a USB cable (preferably the cable that came with the device). A warning will appear saying "A custom OS can cause critical problems in phone and installed applications".
    • Press the Volume Up button briefly to continue.

    The device is now in Download mode.

    Install Odin version 3.13.3.

    When you run it a dialog will pop up in English and Chinese. Click OK.

    The Odin window looks like this:

    odin3.png

    Above ID:COM on the left is the progress bar, below ID:COM is the connection indicator which changes colour (and shows the COM id) when your device is connected in Download mode.

    Below that is the "Log" tab which gives verbose output showing what's happening. Normally you will not need to go near the Option or Pit tabs.

    There are four buttons in the middle of the screen corresponding to the types of file that you can flash: BL (boot loader), AP (Application Processor, PDA), CP (Core Processor, phone/modem), CSC (Consumer Software Customization)

    Depending on what you are flashing you will need to load one or more files. To load each file type click on the corresponding button and select the file to be flashed.
    Odin will show the following in the "Log" while the file is being processed:


    Code:
    <OSM> Enter CS for MD5
    <OSM> Check MD5... Do not unplug the cable...
    <OSM> Please wait...
    For AP_ files this can take some time, during which the button will remain greyed out. When the file has loaded the "Log" will say:

    Code:
    <OSM> Checking MD5 finished Successfully...
    <OSM> Leaving CS...
    ... the button will be enabled again, the text field beside the button will be filled with the fullpath of the selected file, and the checkbox next to the button ticked.

    @Magendanz's TWRP and ROM files are both single files flashed to AP, so just click the AP button and the select the tar.md5 file.

    If you are flashing firmware ( e.g. https://samfrew.com/model/SM-T510/ ) unzip the download into separate files and load each with the correspong button. The filenames begin with BL_..., AL_... etc so you'll know which is which.
    There will be both a CSC_ and HOME_CSC_ file. You could flash HOME_CSC_ to keep your device's settings and data but normally you should use CSC_ for a clean install. If you have an SM-T515 then you'll have a CP_ file too, but if you have a SM-T510 then your firmware will not have a CP_ file because that's for the phone (SM-T510 is wifi only), so just leave CP alone, only load BL, AP and CSC.


    Verify that your device is connected in download mode. The box below ID:COM should show the COM id of the connected device and there should be a line in the "log" saying something like <ID:0/008> Added!!

    Click Start to flash the selected files. DO NOT UNPLUG THE CABLE UNTIL THE PROCESS IS COMPLETE. You can follow the progress in Odin and on the Download screen on your device. To flash a ROM or firmware will take several minutes.

    If you are flashing one of @Magendanz's tar.md5 files then your device will reboot into TWRP once the install is complete. At that point continue following @Magendanz's guide.

    Note: You will need to turn on USB debugging again after flashing firmware, or a clean install of a ROM, before you can use Odin to flash again. Also check that OEM unlock is still turned on.
    3
    I believe a critical issue is being missed in this process, and that is the T510 doesn't have a ramdisk available for boot, so Magisk must be installed to the recovery partition. Below is a screenshot of Magisk Manager data from my own tablet:
    Screenshot_20210326-132318.jpg

    And per the Magisk installation instructions:
    Pay special attention to the Ramdisk info. If the result is Yes, congratulations, your device is perfect for installing Magisk! However, if the result is No this means your device’s boot partition does NOT include ramdisk. This means you will have to go through some extra steps to make Magisk work properly.

    If your device does not have boot ramdisk, read the Magisk in Recovery section after installing. The information in that section is VERY important!

    If you are using a Samsung device and the SAR result is Yes, please check its own section.
    If you are using a Huawei device and the SAR result is Yes, please check its own section.
    In order to boot into system with active Magisk, one has to essentially boot into recovery. From the Magisk in Recovery section (Bixby button references can be ignored):

    Magisk in Recovery​

    If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.

    When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.

    Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.

    Each device has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick Google search should easily get you this info of your device. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into actual recovery mode, continue to press volume up until you see the recovery screen.

    After installing Magisk in recovery (starting from power off):
    • (Power up normally) → (System with NO Magisk)
    • (Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
    • (Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Recovery Mode)
    I can understand now why John Wu was spitting nails mad when Google switched to dynamic partitions with system-as-root: it completely effs up the architecture for rooting with Magisk. :mad:☠️

    I don't know why Google and manufacturers persist in making it messy to nigh-impossible for end users--who desire to do so--to have full control of their own devices. Stupid. Just stupid. 😾 Usunoro...

    On the positive side, I hope this helps everyone trying to root their T510 tablets, and explains the weirdness people may have encountered.

    (P.S. Since hardware attestation is used on the T510, SafetyNet won't pass, no matter what. There aren't any modules that can address this, given that hardware is being used for the evaluation. Another baka change! Also, I'm sticking with Pie since I can't stand Scoped Storage. Can't. Stand. It.)

    Fur and Purrs --
    --
    King Cheetah
    3
    * * * REMINDER * * *

    Please remember per Forum Rules, warez (like lucky patcher) is prohibited from being shared, linked, or encouraged.

    ...........................
    6. Do not post or request warez.
    If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
    ...........................

    All comments that violate the rules on warez will be deleted.

    If you're going to steal the work of others, please don't post about it in Xda forums.

    Thanks for everyone's cooperation.
    2
    Hi
    Just to confirm, on the SM-T510, with TWRP +multidisabler-samsung-3.1.zip + Magisk, the safety tests from Magisk are failing right?
    That's normal?
    Check the Magisk version against posts in the Magisk thread. There was a point where Magisk reported SafetyNet test failed, but it was Magisk not getting a valid result from Google -- SafetyNet was passing, but Magisk did not know that. Problem corrected in later version of Magisk.
    2
    What worked for me was flashing stock firmware and starting over. But I'm still on Pie...
    After resolving RMM/KG lock, why go back to pie? Flash stock Android 10, matching versions. If you want the true stock firmware with T510XXU3BTH4, search for it at once of the big hosting sites:


    If you're more interested in convenience, hanspampel has provided a stock rom based on December 2020's security update with a few modifications, and it's compatible with BTH4.



    To root the device and eventually flash custom ROMs or GSIs download some.
    Start by downloading the matching version of TWRP made by Magendanz:



    Then download one of these custom roms, also by Magendanz, choosing from based on AOSP or LineageOS.

    Or you could download an unofficial version of LineageOS, which'll also do the trick.


    After you'll be able to flash to one of many GSIs available. Here are a couple I liked:

    Official Havoc-OS 3.8 - Android 10
    AOSP Q Mod //CAOS - Android 10 & 11

    After you load these files to your external SD, backup any data on the device; rooting and flashing is going to wipe it.
    • Enable dev options, check OEM unlock, USB debugging, and change USB configuration to file transfer. Don't worry, it'll still charge. Power off.

    • Hold VolUp+VolDown buttons and plug USB to PC.
      - Follow the directions to unlock bootloader and continue to download mode.

    • Open Odin 3.14.4 on PC, untick auto-reboot option, flash TWRP in AP slot.

    • Reboot your device to recovery without letting it boot to system.
      Important: do not let it boot to system.
      - Hold VolDown+Power for 7 seconds to reboot.
      - Then hold VolUp+Power during reboot to enter TWRP.
      - You can let go when you see the bootsplash.

    • Allow modifications to system, make sure it's mounted, and install RMM_Bypass_v3_corsicanu.zip to be free from RMM/KG lockstate.
      - Don't reboot.


      *** Restart here when finished to try other ROMs and GSIs. ***


    • Install multidisabler-samsung-2.6.zip.

    • Perform Wipe > Factory Reset.

    • SelectInstall > Install Zip and choose NexusAQ or Nexus LQ.

    • Install Disable_Dm-Verity_ForceEncrypt_Latest.zip.

    • Reboot and after completing any setup wizards, open Magisk Manager, select install Magisk, and choose the direct installation method, rebooting when complete.

    You will now have a rooted, SAR tablet and you can simply wipe everything and install new ROMs on without (reasonable) worry over nasty lockouts or having to reroot again.

    I know there are guides all over the place already, but I wrote this anyway 'cause my task saliency is dead and for reference cause I saw somebody complaining in another thread that there's nothing up-to-date.