yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series Guides, News, & Discus] Clamtacos:
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:

updato.com

sammobile.com

samfrew.com

sfirmware.com

samfw.com​

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.

[ROM][T510][10.0][XXU3BTK1] *09.12.2020* Stock ROM v4.0​

To root the device and eventually flash custom ROMs or GSIs download some.

Start by downloading the matching version of TWRP made by Magendanz:

twrp-3.4.0-0-T510XXU3BTH4-20201120.tar.md5​

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

Nexus_Stock_AQ_T510XXU3BTH4-20201130.zip

Nexus_Stock_LQ_T510XXU3BTH4-20201121.zip

(XDA Thread)

​

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

lineage-17.1-20201121-UNOFFICIAL-T510XXU3BTH4.zip​

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.
[Samsung Galaxy Tab A series Guides, News, & Discus] rhythm_dx:
Many thanks to everyone who contributed to this process and the various guides/tutorials/explainers. I've used guidance from XDA to root every device I've had since the Droid X. (Still have that phone, too!)

In case anyone else gets stuck on the "SAMSUNG" boot screen after rooting (not the "powered by Android" one, but the one after that), just wait a while. I got stuck on this screen and thought I'd made a mistake, so I redid the whole process three or four times and kept getting frustrated. The last time, I decided to just keep it plugged in and wait. About 15-20 minutes later, the tablet rebooted and finally loaded the system correctly. Hope this helps someone in the future!
[Samsung Galaxy Tab A series Guides, News, & Discus] wolfyj1:
Everything works fine up to this point. When I try to install RMM_Bypass_v3 it gives the message

-Mounting /system ...

Failed! Can't mount /system, aborting!

How do I make the system mountable? Did I miss something?
[Samsung Galaxy Tab A series Guides, News, & Discus] Sage:
you ever work this out? i am getting the same error.

"Only official released binaries are allowed to be flashed (Recovery)"

BL is unlocked. I too get the warning on boot saying that it is unlocked and when i go into DEV settings it says "Bootloader is already unlocked" though cannot flash TWRP..

I was on BTK1 and had to downgrade to BTH4.. maybe the downgrade only worked on the ROM and not on the Recovery/Bootloader hence it may not take the BTH4 based TWRP??

Does that make sense??
[Samsung Galaxy Tab A series Guides, News, & Discus] Sage:
actually this kinda worked. i flashed your TWRP and it worked. though Recovery was now corrupt and coming up with an "Invalid" footer error.. though with the corrupt recovery in place it now let me flash the TWRP from the #1 post!! yay! up and running!
[Samsung Galaxy Tab A series Guides, News, & Discus] Clamtacos:
Guess #1

The system reboot after flashing TWRP.

Flashing TWRP disables something that allows you to mount the system. But if you let the system boot first instead of booting to TWRP, then the system re-enables the something. If this was the mistake, please note that bold and

underlined

words were used to highlight importance. :geek:

Guess #2

When you enter TWRP it asks you to swipe to allow modifications to the system. You must choose this option. Before going any further once you do, check TWRP's settings menu. There is an option in there that unmounts system before installs which might be trolling you.
[Samsung Galaxy Tab A series Guides, News, & Discus] lewmur:
The instruction to not boot to system applies to flashing TWRP from a stock ROM. If you do boot to system instead of recovery, the stock ROM will just rewrite the stock recovery over TWRP.
[Samsung Galaxy Tab A series Guides, News, & Discus] Sage:
I had the same issue. Once you have the invalid recovery you can then flash the older twrp via Odin and it accepts it
[Samsung Galaxy Tab A series Guides, News, & Discus] Hyperfludd:
Just got my hands on my tablet, and yeah I just googled and found this source of guides - though it is old. I was wondering if the steps

still apply to the current tablet

on the latest firmware/etc? (Current software info as of Feb 7th 2021) I was thinking of grabbing one of the roms in this forum. (Was eyeing this one since it's recent, and the customization in it looks good.) I haven't messed with rooting/flashing/etc in the longest of times so I'm real rusty - so any guides and such that I can pointed to would be appreciated!
[Samsung Galaxy Tab A series Guides, News, & Discus] lewmur:
The latest ROM for the T510 is the Nexus stock ROM based on Android 11. I think you need to downgrade from the current stock ROM to the previous one ending BTK1 instead of BUA1. But the first thing you have to do is unlock the bootloader and the steps to do that haven't changed.
[Samsung Galaxy Tab A series Guides, News, & Discus] Chinaberry:
Will this method work for the SM-517P version?
[Samsung Galaxy Tab A series Guides, News, & Discus] KingCheetah:
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:

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
[Samsung Galaxy Tab A series Guides, News, & Discus] Broman400:
Was wondering if this guide is still valid. Was gonna root my tablet later tonight
[Samsung Galaxy Tab A series Guides, News, & Discus] pankspoo:
Finally i was able to root galaxy tab SM-T515 by some modification on android 10 firmware
[Samsung Galaxy Tab A series Guides, News, & Discus] acura4ever:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] htchd2sucks:
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?
[Samsung Galaxy Tab A series Guides, News, & Discus] J.Michael:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] BillSchutt:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] J.Michael:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] BillSchutt:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] J.Michael:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] Az Biker:
* * * 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.
[Samsung Galaxy Tab A series Guides, News, & Discus] BillSchutt:
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?
[Samsung Galaxy Tab A series Guides, News, & Discus] J.Michael:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] BillSchutt:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] BillSchutt:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] J.Michael:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] BillSchutt:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] Clamtacos:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] CrimsonEclipse:
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
[Samsung Galaxy Tab A series Guides, News, & Discus] Desertio:
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
[Samsung Galaxy Tab A series Guides, News, & Discus] rhythm_dx:
Did you wipe/format data after flashing multi disabler?
[Samsung Galaxy Tab A series Guides, News, & Discus] Desertio:
yes
[Samsung Galaxy Tab A series Guides, News, & Discus] rhythm_dx:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] Clamtacos:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] Desertio:
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?
[Samsung Galaxy Tab A series Guides, News, & Discus] Clamtacos:
Correct.
[Samsung Galaxy Tab A series Guides, News, & Discus] Desertio:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] lewmur:
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.
[Samsung Galaxy Tab A series Guides, News, & Discus] dedeoglumrt:
i get device x binary x errors. kernel rev. errors. how can i resovle this guys. i almots broke the device...