• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

MossyTC

Senior Member
Oct 2, 2013
60
30
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.
 
Last edited:

DdDnt

New member
Oct 26, 2019
2
0
Hi,

Please help, my tablet SM-T515 got stuck at: teamwin Recovery Project 3.3.1-1 ...blue with black/gray screen, at boot. I can't do anything, it keeps on looping to this screen. If I try to do a Power+VolumeDown it resets the tablet but I can't do anything else, nor entering in Download mode or shut it down. I have no idea how to fix it. Can anyone give me some hints, please ?! PS: I wanted to root it...I might have downloaded on the tablet with ODIN some weird TWRP (I didn't found this post before starting the process from some weird site ...:( ).

Please, help me,
D
 
Last edited:

MossyTC

Senior Member
Oct 2, 2013
60
30
@DdDnt The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.

Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.

The next steps are

  1. Flash stock firmware via Odin
  2. Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set
  3. Flash TWRP or Custom ROM via Odin
 
Last edited:
  • Like
Reactions: DdDnt

fpozar

Senior Member
Apr 7, 2016
222
94
@DdDnt The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.

Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.

The next steps are

  1. Flash stock firmware via Odin
  2. Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set
  3. Flash TWRP or Custom ROM via Odin

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?
 
Last edited:

MossyTC

Senior Member
Oct 2, 2013
60
30
@fpozar There are two problems that I know of that can cause a FAIL on the product.img line in Odin -

  1. USB debugging not turned on
  2. Incomplete boot loader unlock

Looks like option 2.

As Magendanz has said elsewhere -
Did you reboot with the USB cable inserted holding Vol Up & Vol Down to get the light blue Warning screen and then long press Vol Up to finish unlocking bootloader? A short press, rebooting to bootloader from stock recovery, or adb reboot bootloader in debugging mode won't cut it.

Update: More from Magendanz, on missing OEM unlock option:
This is what the VaultKeeper "feature" does. You've got to open Developer Options with internet connectivity for it not to automatically undo your efforts to unlock.

So connect to wifi before doing the Developer options thing, then try the bootloader thing.
 
Last edited:

fpozar

Senior Member
Apr 7, 2016
222
94
@fpozar There are two problems that I know of that can cause a FAIL on the product.img line in Odin -

  1. USB debugging not turned on
  2. Incomplete boot loader unlock

Looks like option 2.

As Magendanz has said elsewhere -


Update: More from Magendanz, on missing OEM unlock option:


So connect to wifi before doing the Developer options thing, then try the bootloader thing.

Yes, I have done the light blue screen long press step.
Now I've held vol buttons while starting the tablet and chose the short click step (the long click step only leads me to locking bootloader again) and entered a bit different looking download mode (the same one you get by using recovery to enter bootloader, but with a bit more colorful text on the sides), but to no avail, the flashing didn't go through and only lead me to emergency recovery. And again, flashing stock worked.
Secondly, OEM trick worked for me, it appeared when I connected to my home network and made it that oem unlock was greyed out and said "oem unlocked".

Tommorrow I'll try to lock the bootloader and unlock it again. It's really weird though because the blue screen part was done correctly it seems (because long pressing leads me to locking).

Bootloader screenshot when entered by volume + and - combination
 
Last edited:

Orite

Senior Member
Sep 15, 2010
130
1
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"
 
Last edited:

MossyTC

Senior Member
Oct 2, 2013
60
30
@Orite I'm sorry that I haven't been clearer, but I did say to read the relevant guides and read my thoughts below.

In the OP I said

Root can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). There is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.

Full details in the Rooting section in the OP.

You should have been following the TWRP Recovery guide for installing TWRP which clearly states at what point to install Multi-disabler.

If you can boot into TWRP you can flash the Multi-disabler zip file. Tap Install then select the zip file. That should fix the problem of not being able to flash via Odin, though you don't need Odin to install Magisk.
 

fpozar

Senior Member
Apr 7, 2016
222
94
Update : So today I've reunlocked bootloader again and still got stuck at product.img step. Again, this is all on fresh windows and Odin works on original firmware.
This time, the error message displayed on my tablet is :
SYSTEM REV. CHECK FAIL. DEVICE:2 BINARY:1 (PRODUCT)
I can only assume this is some anti rollback feature similar to what happens on LG devices when you try to flash software older than what you're currently at.
I guess now we wait for dev's confirmation and if anyone else has something smart to say please feel free to join the discussion. I would try and download older official firmware and try to flash nexus while on something older, but my network connection is kinda unstable and it takes hours to download without a paid account.

Just to avoid questions, my method of unlocking followed exactly the link in the OP and method of flashing was following the mini guide on Nexus rom's OP.


EDIT : For all the T515 users, it seems odin isn't allowed (by some security features) to downgrade bootloader, and since Nexus ROM is based on May update for T515, anyone on updates newer than May can't flash the ROM. I found the answer on Galaxy s9 forums so that might be untrue for our device, but I didn't see many of us T515 users talking about custom roms so that might be it, and the error code makes sense.
Thanks again @MossyTC for trying to help
 
Last edited:

MossyTC

Senior Member
Oct 2, 2013
60
30
@fpozar

Magendanz doesn't explicitly say so in his OPs, but in some of his posts he does suggest matching the kernel versions.

magendanz said:
Well, TWRP is going to use a custom kernel based on the latest kernel source release, which as of yesterday is T510XXU2ASI4. The custom recovery uses this, but it will also substitute a new boot partition with the custom kernel so that Knox boot security features are disabled and you can still boot to system. I'd think the goal would be to match them as closely as possible. That said, often newer bootloader releases will prevent downgrading, so it's not entirely without risk to use the newest release. The safest bet is to always match the version exactly.

Anyway it looks like you're stuck with stock until there's a newer t515 custom ROM.
 
Last edited:

trashbag1

New member
Oct 30, 2019
3
0
Hi, I have seem to messed up my process somehow, this tutorial seems kind of out of place.
When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.
I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.
I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.
 

tomdot

Senior Member
Mar 23, 2007
277
33
Does unlocking Bootloader on the T510 change Widevine from L1 to L3? This is my only hestitation to bootloader unlock and root
 

MossyTC

Senior Member
Oct 2, 2013
60
30
this tutorial seems kind of out of place.

This isn't really a tutorial, more like additional information to help you follow the guides linked in the OP.

When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.

You're internal data is encrypted by default by Android, but the version of TWRP we're using can't handle encryption. We get around that by disabling encryption by wiping the data partition as one of the first things we do when TWRP starts up, as per the instructions in Magendanz's threads. Ideally you should have the Multi-disabler zip on your sdcard before flashing TWRP. I have amended the instructions above to suggest as much.

I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.
I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.

Is your device an SM-T515? You may be having the same problem as @fpozar.

Can you get into Download mode again?
 

fpozar

Senior Member
Apr 7, 2016
222
94
The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab
 

lewmur

Senior Member
Apr 30, 2011
1,824
396
The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab
"And resetting". That's the problem. You can't relock without resetting and having to start over from scratch.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    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
    I've had some further adventures with my SM-T510. I'd reinstalled the OS and had root but was reluctant to reboot the device, expecting to lose root. Eventually, App Manager twice rebooted the device, I pressed Power + Vol Up and I quite unexpectedly still had root. Some time later, I rebooted it and root was gone, but I rebooted it again holding Power + Vol Up until rebooted and root had reappeared. Yesterday, I forgot to recharge and the device went flat. When I tried to reboot with Power + Vol Up, it went to the stock recovery (stating that I had a free space problem), and I have since then only been able to reboot the device without root. I'd like root back, but probably are not willing to start from scratch again to achieve it.

    I'm also constrained by the fact that I installed the OS T510XXU4BUA4 stock which may make it more difficult to install a custom ROM.
    Hi Bill. This is actually the expected functionality of Magisk on devices where it installs to recovery. Click here to read more about it from the creator of Magisk. You can eventually get around this and have root each time you reboot even without holding down the power+vol combos, there's a lovely guide right here in this forum section but you'll have to do some digging to find it. Here's an in-a-nutshell-version:
    - Extract the recovery.img from the nexus stock archive and adb push it to phone.
    - Install magisk to it and adb pull it back to your PC.
    - Reinsert the recovery.img to the Nexus stock archive and then flash that archive to your phone.

    I'm personally using Nexus Stock T510XXU4BUA1 on my SM-T510. I tried CR first and had some trouble doing unmentionable things, but I've since gone to CQ and it seems to be operating flawlessly as a base for a variety of GSIs as I'm sure it could for you too.
    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.