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:
And per the Magisk installation instructions:
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
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.
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
Last edited:
Was wondering if this guide is still valid. Was gonna root my tablet later tonight
Cannot downgrade my tablet on firmware T510XXS5BUC4. So i'm stock waiting to have a new version de lineageOS or another OS that support my firmware ?
Thanks
After trying to flash the fiwmare T510XXU4BUA1 within odin, I received SYSTEM REV. CHECK FAIL.
Thanks
After trying to flash the fiwmare T510XXU4BUA1 within odin, I received SYSTEM REV. CHECK FAIL.
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?
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.
I've had a Galaxy SM-T510 for about 18 months. I installed a custom ROM and it worked fine. When it booted up I received a message "Bootloader is unlocked and security cannot be guaranteed, press power button" and when you pressed the power button it booted up fine. Recently, I installed TWRP and when I rebooted it goes to the some "Bootloader is unlocked, etc" error message, but when you press the power key it restarted and looped back to the same point. Eventually, solved the problem. Holding down both volume up & volume down at the same time, and plugging it in puts the device into download mode.
Then if I installed a ROM either thru Odin or TWRP, the device went into a bootloop and never booted completely. Eventually, I was able to install stock ROM with a Magisk modified AP tar file which installed a stock ROM and booted up into a rooted phone. Installing TWRP thru Odin fails, and root disappears whenever the phone is rebooted. (I note others have had this problem)
At the moment I still have root, but it'll disappear if I reboot. I don't have Magisk Manager but if I try to install it from an apk file it says it's already present, and the install fails. I was hoping to install LSPosed but without a function Magisk Manager I can't.
Then if I installed a ROM either thru Odin or TWRP, the device went into a bootloop and never booted completely. Eventually, I was able to install stock ROM with a Magisk modified AP tar file which installed a stock ROM and booted up into a rooted phone. Installing TWRP thru Odin fails, and root disappears whenever the phone is rebooted. (I note others have had this problem)
At the moment I still have root, but it'll disappear if I reboot. I don't have Magisk Manager but if I try to install it from an apk file it says it's already present, and the install fails. I was hoping to install LSPosed but without a function Magisk Manager I can't.
Did you ever have Magisk Manager?
Did you rename it?
Check your apps drawer for hidden copies of Magisk Manager. It could have any name -- maybe Settings, maybe something you made up. Uninstall any you find.
When was the last time you wiped data? The initial installation of Magisk requires a data wipe between burning the patched AP.tar and the first boot to Android.
Thanks for the advice. I have lucky patcher and I can't see Magisk Manager there, only Magisk. I would like to install obbs to sd, and keep the root open when I reboot. I've experimented with this several times and I usually wipe data.
I've installed the software several times now using Odin with a Magisk modified AP file and BL and CSC files. I'm wondering if I reinstalled using just the AP file, it might regard it as an update and not wipe everything. Before everything went wrong, I had the Nexus OS system with a stable root and in theory I would like to get back to this point. I'll just go back to the device and check again.
I don't know what "lucky patcher" is. I don't know where you are seeing Magisk, but not Magisk Manager. I say "Magisk Manager" when I am talking about an Android app that gets installed using an .apk file. I am trying to distinguish it from "Magisk", which gets injected into boot images. If in the equivalent of the app drawer you see items labeled "Magisk", they are probably instances of "Magisk Manager app". Those are the things, all of which you should uninstall before trying to install a new "Manager" app.
Having successfully installed Magisk once, I believe some people succeed in updating "Magisk" by re-patching the appropriate image and flashing it. On a Samsung where you must use Odin, I think running Odin with all slots filled, but using "HOME_CSC" instead of "CSC", results in re-flashing without requiring a data wipe, and so without disturbing existing data.
If you change your operating system, I think you have to accept wiping your data. If you are just updating your operating system, you might get away with not wiping data.
- Jun 2, 2012
- 7,918
- 17,757
* * * 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.
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.
Thanks for your advice. I'd sort of worked this out but I remain confused. I have an app on my SM-G965F called Magisk Manager but it says it's version 23, which is Magisk, whereas the MM is version 8.0.2. All this began when I wanted to download Riru and then a version of Xposed so I could put some obbs on SD. There are descriptions of downloading from the MM
Thanks for your advice. Next time I flash I'll try Home_CSC, but I hope I don't have to. One of my posts was deleted for an inadvertent breach of the rules, I apologise. The App named Magisk Manager in another device says it's version 23.0, not 8.0.2 as MM is supposed to be. So I'll uninstall Magisk and then re-install it. Do you suggest, I use the Magisk APK23.0 or the Magisk Manager APK8.0.2?
If you are confused by the version numbers, don't change anything, it's probably right.
Magisk has several version numbers. I don't mean there are several versions of Magisk, I mean one version of Magisk spits several numbers at you. Then Magisk Manager has several version numbers. I don't think you can tell who goes with what in older versions. That might have changed.
If you start with "stock" ROM (i.e., no Magisk), install a Magisk apk, use that to patch an image file, install the patched image file -- those have to be a compatible pair of Manager and Magisk, it was the Manager that patched the image.
Before updating a working system, read the Magisk thread (and a dozen similar-device threads) to see if a newer version fixes something you care about, and is likely to work on your device.
Thanks for your advice JM. I'll recap at the moment, I had a SM-T510 which had worked fine for 18 months with Nexus OS and root. I can't remember how I did it at that time. I tried to install something with TWRP and it went wrong. It developed a bootloop which I was concerned was fatal because I couldn't get the device into download. Eventually, I discovered you could get intodownload by pressing vol up+down and inserting a cable. But every attempt at flashing ended up in a bootloop, either thru Odin or TWRP.
Eventually I discovered I could flash the original firmware with a Magisk modified tar file and get root. If I tried to flash a custom ROM beyond this I got a bootloop. If I tried to reflash TWRP or Orange Fox via Odin, the flash failed with an error message about unauthorised flashes. I'd resigned to the original OS with root, but soon discovered that root disappeared on reboot.
So I'm flashing a fresh OS with a Magisk modified tar, and it boots up with the Magisk app in situ. If you then run Magisk, it says it has to upgrade, reboots the device (this initial single reboot maintains root), I then install other apps including those that require superuser permission.
JM & anyone else reading-I didn't finish the story in my last post because it's a long story. I tried uninstalling Magisk, the device rebooted and root was gone. Tried reinstalling the OS with just the AP in Odin with the Magisk modified tar file hoping this would be treated as an update but when I rebooted it had reset and there was no Magisk at all. So I again reinstalled with Odin, Magisk modified tar in AP, and tar.md5 files in BL & CSC. I'm now back where I started-I have root but I know it'll disappear if I reboot. I'm wondering if there is a way to install a terminal emulator which will keep the root open? I can't install TWRP because the booting up closes the root and prevents a flash.
I don't know how you imagine a "terminal emulator" will "keep the root open".
The original instructions said that, after Magisk is installed to recovery, every time you reboot, if you want Magisk, you have to "boot to recovery", only not quite. Some people have it easier -- my SM-T290 reboots with Magisk active as long as I "shut down" before rebooting. Some people report needing to connect a cable to the tablet to boot to Magisk. You need to read a lot and try a lot of things.
If you get root, and lose root when you reboot, stop trying to reinstall Magisk -- spend some time trying to boot better.
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.
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.
Last edited:
I seem to be going in circles from guide to guide referencing a guide to get to a guide to guide a guiding guide to guide me guiding.
So far, I have unlocked the bootloader, installed drivers on my PC, installed and run ODIN, downloaded TWRP latest edition.
Attempting to load TWRP results in FAIL!
and I'm stumped
T510
Android 11
KNOX 3.7
So far, I have unlocked the bootloader, installed drivers on my PC, installed and run ODIN, downloaded TWRP latest edition.
Attempting to load TWRP results in FAIL!
and I'm stumped
T510
Android 11
KNOX 3.7
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
16The 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
***OverviewTo 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:
- Read the TWRP instructions
- 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.
- Unlock Bootloader - Click to see original post:
- Install TWRP recovery .tar.md5 file via Odin by following the TWRP instructions.
Click to see instructions from the TWRP OP - - [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]:
- Read the custom ROM instructions: Nexus Stock / LineageOS 16.0
- 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.
- Unlock Bootloader - Click to see original post:
- 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 -
Click for instructions from OP for LineageOS 16.0 -
Note that "wipe data" means Wipe -> Format Data
- [Optional] Install Magisk to get root - see Rooting section below
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.
***DownloadsYou 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 BootloaderClick to see Unlock Bootloader original post...
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.
***RootingRoot 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 OdinOdin 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:
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:
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> Enter CS for MD5 <OSM> Check MD5... Do not unplug the cable... <OSM> Please wait...
... 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.Code:<OSM> Checking MD5 finished Successfully... <OSM> Leaving CS...
@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.3I 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:
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.
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 Cheetah3* * * 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
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
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:
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+VolDownbuttons 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.
- HoldVolDown+Powerfor 7 seconds to reboot.
- Then holdVolUp+Powerduring 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.
- Select
Install > Install Zipand 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.
