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

[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk

Search This thread

Tirofog

Senior Member
Dec 6, 2011
407
116
Hi all
First of all, thanks for the great guide.

Just a bit of off topic question:

Thinking of buying this tablet
( the WiFi only version)

Are you guys happy with it?
Good performance?

Cheers
( OP please forgive my little off topic ) :p

Edit: Did Samsung released the android 10/11 kernel sources for this device?

This is an absolute must to get development going on
IMO it's well worth the money, a big improvement on my old Lenovo, especially the speakers! I've rooted and did a bit of debloating and it does seem that the stock rom isn't fully utilising the potential of the tablet as it can be quite laggy. I haven't tried the LOS port on here but reading the thread it looks as though there is a performance gain to be had.
 
Apr 6, 2016
7
0
OnePlus 5T
I tried to root my SM-T500 according to these instructions. Unfortunately, I keep having problems with unsigned vbmeta (AVB). No matter which FW I try (Android 10.11 T500XXU3 ...- EUX). It doesn't work. I've tried several versions of Magisk with the same result. I also tried to delete the vbmeta in the BL, or to replace it there and in the AP with a vbmeta disabler, the FW is not accepted.
I have the exact same problem. Has anyone solved this problem?
 

Shyonnu

Member
Jul 13, 2012
44
5
Newcastle
here
guide for Install latest ADB and Fastboot Drivers on Windows 10 than in windows clic on start - "write" cmd - "write" adb shell - "write" sm list-disks - "write" sm partition disk: 179.32 private (in my case) "or as an alternative write" sm partition disk: 179.32 mixed 50 - "write" reboot
that's all
alternatively use
Tool all in one
for the same command. May be easier for beginner?
 

Mogster2K

Senior Member
Jun 25, 2011
349
68
Hi all
First of all, thanks for the great guide.

Just a bit of off topic question:

Thinking of buying this tablet
( the WiFi only version)

Are you guys happy with it?
Good performance?

Cheers
( OP please forgive my little off topic ) :p

Edit: Did Samsung released the android 10/11 kernel sources for this device?

This is an absolute must to get development going on
It's not bad for the price, but 32 GB is too small and sdcards can't be formatted as adopted/internal. I'd get the 64 GB version if you can. Android 10 kernel source has been released but I'm not sure about 11.
 
  • Like
Reactions: superdragonpt
FINALY!!!

after 4 days i did get Magisk root to work! after all vague explanations.

FLASH AB with magisk "etc, etc"

here comes the part how it will work.to fix boot loop with a message about it not being offical Samsung software custom binaries are installed
FLASH vbmeta_disabled_R.tar in userdata. the tab will say no operating system installed would you like to factory reset.
i rebooted in to download mode without factory reset.

then i did following.
in ODIN flash
AP"magisk_patched file"
BL-"stock" CSC"
USER_DAT:"vbmeta_disabled_R.tar"

on the setup, i clicked 4 times outside of the setup window for setting upp with QR code.
kumped back and forth from accesebility and country, clicked a coupple of more times outside of the setup window for setting upp with QR code

did this a few times untill i dident get the restart optionand got straight in to the wifi setup etc ect installed magisk magisk rebooted all works
 

wildechap

Member
Nov 15, 2012
36
14
Buea
It's now possible to move apps to the sd card, with the September update. And the root method still works.
photo_2021-10-09_15-43-21.jpg
photo_2021-10-09_15-43-32.jpg
photo_2021-10-09_15-43-36.jpg
photo_2021-10-09_15-43-39.jpg
 
It's now possible to move apps to the sd card, with the September update. And the root method still works.
Hello guys, and thank you all for the good work you did.

Widechap I get this update on my t505 with name "BUJ1" and it doesn't really move your data folder, which is most important.I have tried the commands(without root) in adb "sm partition Disk" to separate the SD card and that also didn't help me at all.

So, the only one method to happen it's rooting and using the method from the other Thread.
About the rooting that for me was easy, just "Frija" doesn't have my version "BUJ1" and I was waiting about 7 hours from the free server. Everything went well, until I get to the final step to manually reboot and get to the recovery, but was confusing in that moment, because after the first splash Screen I get that message for the unlocked bootloader and must continue with "ON/OFF" button and couldn't get to the recovery, the OS it's start normally, install the magisk and didn't work. So that was the first time trying.

The second try (just to mention, I've got many years of experience and the most important thing is to have patience and get your time) I've get training with the buttons for the recovery, after 15 times I thought I don't have recovery🤔 I was keep trying to escape somehow from this message and it happen, I get to the recovery with "volume up" and " power on".

So I've got prepared for the second try and finally after almost 2 days work I've got root and moving data folder to the SD card, which is "Samsung 128 Evo plus Class 10 UHS-1 U3" , and everything is working perfect. I have "Mobile legends: Bang bang" which is about 4Gigs and keep growing in my ext2 formatted partition.

P.S. Thank you again to every person who is keep working for ours devices make our life better!
 

stonkr

New member
Jan 16, 2011
4
2
only official released binaries are allowed (vbmeta)

Had this issue with the above message on an SM-T500 yesterday when I didn’t uncheck the Auto Reboot option in Odin. Yes, silly me, I’ve successfully rooted two previous T500s. From a bit of research it seems I’d tripped a 7-day timer. So, you can either wait a week or convince the tablet that a week has already passed.

With your tablet bootloader unlocked and running stock firmware, you need to check the OEM unlocking option is visible and greyed-out in Developer options (Settings > About tablet > Software information > tap Build number 7 times). If OEM unlocking is not visible at all then you’ve tripped that timer and you’ll keep getting the red vbmeta message.

Settings > General management > Date and time. Turn off Automatic date and time. Manually set the date forward 7 days. Make sure Wifi is on and connected. Restart the tablet.

This was enough for my tablet to show the greyed-out OEM unlocking option, if you still don’t see it and wifi is still connected, either move the date even further forward and/or try running a software update check via settings, then restart the tablet.

I was able to complete a successful rooted firmware flash with Odin. Don't forget - when you reboot into recovery, keep that vol+ button pressed – it’ll restart about 3 times until you see recovery.
 
  • Like
Reactions: babrdala and vegaz

TheHeroBilly

Member
Apr 8, 2016
45
7
Just got 2 of these tablets rooted a few days ago, now I have an update available to day, is it possible to update and reroot without resetting the tablet?
 

Mogster2K

Senior Member
Jun 25, 2011
349
68
Just got 2 of these tablets rooted a few days ago, now I have an update available to day, is it possible to update and reroot without resetting the tablet?
Yes, follow steps 3 - 6 from the first page. Use Frija to download the full ROM, and flash the HOME_CSC file instead of the CSC file to keep your settings. BTW you can copy the AP file to your sdcard, but you will need ~5GB free in internal storage for Magisk to patch it. If anyone knows a way around this please LMK.
 

TheHeroBilly

Member
Apr 8, 2016
45
7
Yes, follow steps 3 - 6 from the first page. Use Frija to download the full ROM, and flash the HOME_CSC file instead of the CSC file to keep your settings. BTW you can copy the AP file to your sdcard, but you will need ~5GB free in internal storage for Magisk to patch it. If anyone knows a way around this please LMK.
okay, I can confirm this does not work, I get stuck loading with the SAMSUNG logo on screen, it looks like it still has to be factory reset each time an update is applied.
 

Krishbarnwal

Member
Nov 7, 2021
17
0
I am planning on to unlock bootloader only. Will I continue recieving official updates from Samsung and able to install them (not flashing that, OTA ones). I am not going to flash custom recovery or kernel or even custom rom. Will it work that way?
 

babrdala

Member
Jul 3, 2015
6
0
only official released binaries are allowed (vbmeta)

Had this issue with the above message on an SM-T500 yesterday when I didn’t uncheck the Auto Reboot option in Odin. Yes, silly me, I’ve successfully rooted two previous T500s. From a bit of research it seems I’d tripped a 7-day timer. So, you can either wait a week or convince the tablet that a week has already passed.

With your tablet bootloader unlocked and running stock firmware, you need to check the OEM unlocking option is visible and greyed-out in Developer options (Settings > About tablet > Software information > tap Build number 7 times). If OEM unlocking is not visible at all then you’ve tripped that timer and you’ll keep getting the red vbmeta message.

Settings > General management > Date and time. Turn off Automatic date and time. Manually set the date forward 7 days. Make sure Wifi is on and connected. Restart the tablet.

This was enough for my tablet to show the greyed-out OEM unlocking option, if you still don’t see it and wifi is still connected, either move the date even further forward and/or try running a software update check via settings, then restart the tablet.

I was able to complete a successful rooted firmware flash with Odin. Don't forget - when you reboot into recovery, keep that vol+ button pressed – it’ll restart about 3 times until you see recovery.
Just tell me what kind of angel are you? a big trunk of tanks pal
 
Last edited:

stonkr

New member
Jan 16, 2011
4
2
okay, I can confirm this does not work, I get stuck loading with the SAMSUNG logo on screen, it looks like it still has to be factory reset each time an update is applied.
I've updated two T500s several times with no problems and no need to factory reset. You need to remove any Google or Samsung accounts, use the HOME_CSC and leave auto reboot checked. Assuming, of course, you've downloaded the correct firmware for your device. Adding back your accounts afterwards doesn't seem to cause any problems.
 

TheHeroBilly

Member
Apr 8, 2016
45
7
oh, see I didn't remove accounts, that may be why I had to reset. I still have the second tablet to update, so I'm going to try that with this one.
 

Mogster2K

Senior Member
Jun 25, 2011
349
68
okay, I can confirm this does not work, I get stuck loading with the SAMSUNG logo on screen, it looks like it still has to be factory reset each time an update is applied.
Strange, it has worked for me thru multiple updates including BUJ1. Here's what I do:

1. Download the update using Frija (Model SM-T500 and CSC XAR for the US model)
2. Extract it to a folder on my PC
3. Copy the AP_something.tar.md5 file to my tablet's sdcard
4. Launch Magisk on the tablet, select "Install" and "Select and Patch a File" and select the AP file
5. Copy the magisk_patched-something.tar file back to the PC, then delete it from the tablet to make room
6. Put the tablet in download mode and use Odin 3.14.1 (not a patched version) to flash the BL, HOME_CSC and magisk_patched files

I have not needed to remove any accounts, so I'm not sure whether it would help you or not.
 
  • Like
Reactions: vegaz

valdonta

New member
Nov 24, 2021
2
0
How much space should be left on a 32gb tab after doing nothing but rooting using the newest samsung image? Mine is down to like 21gb, is that normal?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    okay, I can confirm this does not work, I get stuck loading with the SAMSUNG logo on screen, it looks like it still has to be factory reset each time an update is applied.
    Strange, it has worked for me thru multiple updates including BUJ1. Here's what I do:

    1. Download the update using Frija (Model SM-T500 and CSC XAR for the US model)
    2. Extract it to a folder on my PC
    3. Copy the AP_something.tar.md5 file to my tablet's sdcard
    4. Launch Magisk on the tablet, select "Install" and "Select and Patch a File" and select the AP file
    5. Copy the magisk_patched-something.tar file back to the PC, then delete it from the tablet to make room
    6. Put the tablet in download mode and use Odin 3.14.1 (not a patched version) to flash the BL, HOME_CSC and magisk_patched files

    I have not needed to remove any accounts, so I'm not sure whether it would help you or not.
  • 38
    I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed for the Tab 10.1 (2019)).

    It's been quite some time since I published a tutorial on XDA. So, I decided to put up this comprehensive tutorial, hope it helps everyone who's looking for it. We will take the direct approach of rooting the tab by patching the AP firmware and flashing the patched AP through Odin.

    /* I will be using the same images I prepared for the tutorial to be posted on my blog. Sorry that they have been watermarked, that is to prevent scrapers from stealing. It took me enough time to capture them and do some post-processing. */

    Before we start, here's the obligatory disclaimer and warning:
    • Unlocking the bootloader will erase all the data on your tab, including all the data that's on the internal storage. So, make sure that you have taken a complete backup of all your important data.
    • Flashing a custom binary (such as Magisk patched TAR in this guide) will trip the KNOX counter. Your device's official warranty will be void once KNOX is tripped.
    • You will not be able to use apps and services like Secure Folder, Samsung Pass, and anything that relies on KNOX.
    • Although I have tried this on my Galaxy Tab A7 (SM-500) and can confirm that this works, I will not take any responsibility of any bricked/toasted devices. Make sure that you fully understand what you're doing and accept the consequences if anything goes wrong.
    • If you do land your tablet in trouble, feel free to ask, I shall try my best to help.

    Update log

    Updated on March 2, 2021
    1. Added more info about the warranty. It seems like some users are still not aware of how KNOX affects the warranty. If you're getting into software modifications such as rooting, I expect you to have some prior knowledge about such things.
    2. Redacted the part where you needed to change Magisk's update channel under Step #5. Not needed anymore as Magisk v21.x was released to the Stable channel in January 2021.
    3. Replaced all instances of "Magisk Manager" with "Magisk App". Starting with Magisk v22, Magisk Manager is gone and merged with the core Magisk. It's now called the "Magisk App".

    Requirements
    • Your Galaxy Tab A7 with SM-T500 or SM-T505 model number
    • A compatible USB-C cable
    • A Windows computer. (Odin only works on Windows. If you're using Linux or Mac, you could try Heimdall)

    Instructions

    Step 1: Enable OEM Unlocking
    In order to unlock the bootloader, you must first enable the 'OEM Unlocking' toggle. This toggle resides inside the 'Developer options' screen, which is hidden by default on most Android devices.

    First, enable 'Developer options' by going to 'Settings' > 'About tablet' > 'Software Information' and repeatedly tap on the 'Build number' section five times. If you have a lock screen security set, you will need to input your PIN/Password/Pattern when prompted.

    fyOjj9C.jpg

    Once you do this, you should see a toast notification on the bottom of the screen saying that "Developer mode has been enabled".

    DS2QcOM.jpg

    Once that is out of the way, go to 'Settings' > 'Developer options' and turn ON the toggle next to "OEM unlocking". You will instantly be prompted to enter your PIN/Password/Pattern, so do it. Then select "Enable" to allow OEM unlocking.
    • Note: If the OEM unlocking toggle is grayed out, make sure that you have connected the tablet to the internet first (via WiFi or mobile network, your choice).

    P1e7Kks.jpg

    Step 2: Unlock the Bootloader
    Start by powering off your tablet completely. Then while holding the Volume Up and Volume Down keys together, connect it to your computer using the USB cable. This should take you to the bootloader screen (I call it that because logically that's what directs you to either Download Mode or Device Unlock Mode). Long-press the Volume Up key to enter the 'Device unlock mode'.

    A6rzA41.jpg

    Your tab should now prompt you with a confirmation screen, so press the Volume Up key to confirm and unlock the bootloader.

    DfBMlQI.jpg

    Your Tab A7's bootloader is now unlocked and it should reboot automatically. You should also see a warning message right before the Samsung splash screen, just as shown in the picture below. Don't worry, it's completely normal. And no, there's no way to get rid of it (unless of course, you relock the bootloader).

    zvQahPn.jpg

    The first boot after unlocking the bootloader could take some time (took around 3-4 minutes for me). So be patient.

    Now that the bootloader is unlocked, let's verify it. Samsung introduced a new feature known as "VaultKeeper", which will automatically relock the bootloader if you do not perform this step.

    After your tab boots, connect it to the internet. Then enable the Developer options as shown in step #1 and go to 'Settings' > 'Developer options'. The OEM unlocking toggle should be greyed out and say that the bootloader is already unlocked. Again, refer to the picture below.

    a3UaBV8.jpg

    Step 3: Download the firmware package
    With the bootloader properly unlocked, you can begin with the rooting part. As I mentioned, we will be patching the AP firmware file via Magisk App, as instructed by John Wu in his installation guide on Github.

    So, you will need to download the firmware package for the software version that's currently installed on your tab. This is very important, do not use an older firmware, as it will result in issues. You could of course use a newer firmware, which will update your tab at the same time as rooting it.

    To verify your software version, you can go to 'Settings' > 'About tablet' > 'Software information' and check the "Build number". The latter half of the mentioned build number is your tab's software version, which in my case as shown in the picture below is: T500XXU1ATJ2. So, I will need to download the firmware package for "T500XXU1ATJ2" and in your case you should download the one corresponding to the info you see under 'Build number'.

    Where to download? You could use online FW databases like SamMobile, Samfrew, etc. However, I would recommend using Frija or Samloader as they allow you to download the firmware directly from Samsung's Firmware Update Servers and without any speed caps. If you're operating on Windows, use Frija. On macOS/Linux, use Samloader.

    Step 4: Extract the AP firmware and transfer it to your Tab A7
    Once you have the ZIP package downloaded, you will need to extract it to get The extracted folder should contain the individual firmware files like BL, AP, CP (only for SM-T505 LTE variant), and CSC/HOME_CSC (in .tar.md5 file format).

    fwaedIp.jpg

    The file you'll require is the AP firmware, which in my case is "AP_T500XXU1ATJ2_CL19362637_QB34980135_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS10.tar.md5". Again, in your case, the filename would be a bit different, but it should follow the same structure.

    After extracting the AP firmware, connect your tab to the computer, enable File Transfer (MTP) mode on it, and copy over the AP firmware to your tab's internal storage. Copy it to the root directory, that is, outside all the folders as shown below. The location of the file doesn't matter, you can copy it anywhere, but I prefer this for easier access.

    LqSc4mN.jpg

    Step 5: Patch the AP firmware using Magisk App
    Now's the time to patch the AP firmware. To do this, download the latest version of the Magisk app from the official Github releases page to your Tab A7. This will be an APK file. Once downloaded, install the APK file using your choice of file manager.

    Warning about unofficial sources of Magisk: Magisk does not have any officially registered domain. If you Google for it, you will probably come across multiple websites that have the word "Magisk" in their domain URL. They are there to deceive the users, and often misinform users, especially those who are new to the scene.
    John Wu, as well as XDA have previously warned the users from falling into these deceptive websites. The only official place to get Magisk is from Github.

    You do not need to change Magisk's update channel to Beta anymore. Starting January 12, Magisk v21.x was pushed to the stable channel (default).

    After installing, go to the app drawer and launch the Magisk Manager app. Before you start patching, you would want to change Magisk Manager's update channel to Public Beta. This is because Magisk's latest version (i.e. v21.0) is only available on the beta channel and hasn't been pushed to the stable channel yet (at least at the time of publishing this tutorial).
    To do this, press the settings icon on the top-right, tap on "Update channel" and select "Beta". Then go back to the app's main screen. It should refresh and show you the latest version as v21.0.


    Press the "Install" button and then "Select and Patch a File" from the list of available methods. This should open the file selector, so navigate to the internal storage and select the AP firmware you transferred during the previous step.

    T1gvi0A.jpg

    Once the file is selected, hit "LET'S GO" to start the patching process. This should take a minute or so because the AP firmware is quite a heavy file. Once it is done, the patched AP firmware with the filename "magisk_patched_xxxxx.tar" (where "xxxxx" is an arbitrary code) should be stored inside the "Download" folder of your tab's internal storage.

    94P21Zb.jpg

    Step 6: Flash the Patched AP Firmware using Odin
    The last step is to flash the patched AP firmware to your Galaxy Tab A7 and root it. For this, connect your tab to the computer over USB and copy the "magisk_patched.tar" file from the Download folder. Paste this patched AP firmware inside the firmware folder that was extracted during step #5, along with the rest of the firmware files (BL, CSC, etc). Disconnect it from the PC after transferring the file.

    fbir5NI.jpg

    Now, boot your Tab A7 into Download Mode. Power it off, and connect it to the computer over USB while holding the Volume Up and Volume Down keys together. This should bring up the bootloader screen. Simply tap the Volume Up key once to enter Download Mode. Here's what the Download Mode on the Tab A7 looks like.

    EZMsBVJ.jpg

    Next, download Odin v3.14.1 from this XDA thread (NOT the patched version, but the regular one) and extract the contents of the downloaded ZIP package. Then launch Odin on your computer by double-clicking the "Odin3 v3.14.1.exe" executable and click "Ok" when prompted. You should see the Odin interface on your computer screen now.

    lpAaacO.jpg

    Odin should automatically recognize your tab in Download Mode and display the COM ID on the top-left.

    Click the 'Options' tab and uncheck the 'Auto Reboot' option. This will prevent the tablet from being automatically restarted after the flash is complete.

    Now, load the firmware files in the respective slots of Odin.
    • The BL firmware file (BL_T500/5XXXXXXX_xxxxxxxxxxx.tar.md5) goes to the "BL" slot
    • The CP firmware file (CP_T505XXXXXX_xxxxxxxxxxx.tar.md5) goes to the "CP" slot. Note that the CP firmware only applies to the Tab A7 LTE variant with the SM-T505 model number.
    • The HOME_CSC firmware file (HOME_CSC_OMC_ODM_T500/5XXXXXXX_xxxxxxxxx.tar.md5) goes to the "CSC" slot. We will not be using the regular CSC, as it will erase all the data. If you want to do that, feel free to use it.
    • And finally, the patched AP firmware file (magisk_patched.tar) goes to the "AP" slot.
    Once the files are loaded in their respective slots, hit the "Start" button to flash them to your tab.
    • Note: While you could get away with just flashing the patched AP firmware alone, John recommends NOT doing it. Always flash the patched AP along with the rest of the firmware files like BL, CSC, etc.

    Wait for the flash to finish. Once it is, you should see the 'PASS!' message in Odin. Like so:

    VNhOwVj.jpg

    You can now close the Odin window and disconnect your tab from the computer.

    Step 7: Perform a Factory Reset
    Once the flash is complete, you will need to manually boot your tablet into the stock recovery mode and do a factory reset. This is only mandatory during the initial rooting process, which is exactly what we are doing here.

    To do this, hold the Volume Down and Power keys together for about 7 seconds. As soon as the screen turns off, release the Volume Down key and quickly hold the Volume Up key, while still holding the Power key. Keep holding the keys until you see the stock recovery screen.

    You should now see the stock recovery screen with some device information in yellow color at the top. Like so:

    BGLUiVu.jpg


    Use the Volume keys to move the selector to 'Wipe data/factory reset' and hit the Power key to confirm the selection.

    You will now see a confirmation prompt on the screen. Select 'Factory Data Reset' to confirm and finally perform a factory reset.

    ybcSiEf.jpg


    Once done, select the 'Reboot system now' option from the recovery's main menu. Your Tab A7 should now reboot may be more than once, so be patient.

    We're not done yet. After booting, you will need to open the Magisk app from the app drawer and follow the on-screen instructions to replace the Magisk stub with the actual full application, and further complete the required setup when prompted by Magisk app.

    Once this is done, your Tab A7 should reboot one last time and should be rooted thereafter.

    Your Tab is Rooted!
    You may now go ahead and start using root applications, install some modules, etc. Since v20.4, Magisk Hide has been disabled by default on new installations in light of the new hardware-backed SafetyNet attestation. So, to use banking/security, or any other sort of apps that may detect root, you will need to turn ON Magisk Hide from within the Magisk App settings.

    9f85hgh.jpg

    Before you leave, there are a few key things you should note:
    • Unlike some other Samsung phones, you will not need to follow any complex button combinations to boot into the stock recovery. A normal reboot will always boot your Tab A7 into the rooted Magisk system. On the other hand, the regular Volume Up + Power key combo will get your tab into the stock recovery mode.
    • Second, if a new software update is rolled out, you will need to repeat the same process from step #4 all the way to step #7. When updating the FW, you can simply use the HOME_CSC instead of the regular CSC to prevent your data from being wiped. A backup should still be taken.

    That's all from my side. If you run into any issues, feel free to post. Don't forget to share details like the software version your tab is on, the firmware package you downloaded and used, and of course your tab's complete model number.
    5
    Okay, so I found some spare time to verify that the method still works (using the latest FW and Magisk). I have attached an image for confirmation.

    Here's a log of the things I have updated in the tutorial. It seems like a good idea to do this so that I can easily track the things I have changed and when. A copy of this log is also present in the tutorial for users who are new.

    Log:
    1. Added more info about the warranty. It seems like some users are still not aware of how KNOX affects the warranty. If you're getting into software modifications such as rooting, I expect you to have some prior knowledge about such things.
    2. Redacted the part where you needed to change Magisk's update channel under Step #5. Not needed anymore as Magisk v21.x was released to the Stable channel in January 2021.
    3. Replaced all instances of "Magisk Manager" with "Magisk App". Starting with Magisk v22, Magisk Manager is gone and merged with the core Magisk. It's now called the "Magisk App".
    Now, for users who have faced issues with this method. The error you're seeing is caused by the Prenormal KG state being in effect. You will only get this error IF you do something that's not mentioned or skip something in the guide.

    So, what do you do after that? It's quite simple actually. First off, restore the official FW via Odin. Then boot into the OS, connect to the internet, enable Developer Options, and verify that "OEM Unlocking" is present and greyed out in an ON state.

    Then re-attempt the tutorial. Make sure that you do not deviate this time, I know you would believe that you didn't, but we all can make mistakes. So just cross-reference each step while attempting.

    More importantly, after you have flashed the Magisk Patched TAR and performed the factory reset, make sure that you boot straight into the OS, connect the tab to the internet, and do the initial Magisk setup. DO NOT REBOOT the tab before doing this.

    While I personally didn't face the issue, I believe this is where things might go sideways, because Magisk needs to run its code to complete the rooting process. If not, Samsung's ugly security features will kick in and show you the "Only official binaries are allowed to be flashed" error message.

    If you still have doubts, drop in a comment. I am sure you'll get the help.



    At last, I want to bring up something that I didn't wanted to. I received a PM from a reader of this thread expressing his frustration on why I was ignoring the thread and that this tutorial was "tricking" you guys into bricking your devices.

    I have a personal life aside from XDA, and I do not get the time to visit the forums on a daily basis like I did until a few years ago. If it's important, I ask you to mention me in the comments so that I can receive a notification.

    Next, the method is nothing new or special. It's the one provided by Magisk's creator John Wu himself (like I mentioned yesterday). It's being used by thousands of users in and outside the community.

    If you have come across an unusual error message, please do not go on blaming others for your mistakes/errors without valid proof.

    Going through the last few pages of this thread, you will find users who successfully rooted their Tab A7 using this guide.

    I, or anyone in this community, does this voluntarily to help the users. We are not being paid for the effort or time we spend writing down guides or developing ROMs. This community works by supporting each other, by sharing our knowledge about the things/technology we so love.

    If you face issues, I request you to be patient, read, and ask the fellow community members for help by providing some constructive information.

    Thanks.
    5
    Sdcard fix

    adb shell
    Su
    sm list-disks
    sm partition <DISK> private
    reboot
    Or sm partition <DISK> mixed (number)
    Example sm partition disk:179,64 private or
    sm partition disk:179,64 mixed 50
    3
    Hey man, I wanna take the time to apologize for that PM, that was uncalled for from my end. Ive been working with jailbreaking and rooting phones and tablets for 10+ years (2005-2015 mainly). I usually know what the hell Im doing XD

    I did read your guide thoroughly, but I misunderstood the part about soft reboot and hard reboot. Im new to Samsung with OS10 and the latest Knox functions. I think where it went wrong for me was after the Factory Reset inside the Recovery menu. While rebooting, it got stuck somewhere. I waited for a long while, but I concluded with a hard restart. (volume down + power)

    The mistake, as you wrote, probably happened during this hard restart, where Knox got tripped and it got stuck with "Only official released binaries are allowed to be flashed (vbmeta)" error.

    The problem tho, is after this state (knox tripped, and warrantystatus 0x01) it seemed impossible to reflash with Odin. As no matter what I tried (Stock rom, magisk repeat) it still wouldnt let me flash the Patched AP again. Download mode stopped Odin with the same red line "Custom binary VBmeta". I might be mistaken, but it seems that after Knox is tripped, if Magisk doesnt get to do its thing, it winds up locked without possibility of reflashing patched AP.

    Anyways, the end of the story for my Tab A7 was that I flashed stock rom, locked the bootloader and asked for a refund from the store. They didnt check Knox and I exchanged it for a Lenovo MT10+ instead. Better CPU and ram, and cheaper than the Samsung. So a happy ending anyways :p

    A couple of things tho:

    1) Odin 3.14.4 doesnt seem to exist, Ive roamed the forums and google for this version, and most sites have a bogus download where the CRC is all wrong. The correct latest version is 3.14.1. You might wanna change this in your guide, so people dont get lead down the wrong path.

    2) I would highly recommend expressing the importance of not actually hard rebooting your device before Magisk does its finishing touches. Maybe big letters in red and "Warning warning"? Especially seeing as a couple of other members here did the same mistake.

    Again, sorry for my noob-rage. I got kinda carried away. Thanks for all the effort youve put into this guide, @DJBhardwaj. Ill read your guide better next time ;)

    Greetings from Norway 🇳🇴
    That's completely alright. I can understand.

    Just for the sake of experimenting, I deliberately rebooted the tablet before completing the additional setup by Magisk to land my Tab A7 to the "Only official binaries are allowed to be flashed (vbmeta)" error.

    I will try and explain exactly what happened.

    1) This isn't caused by KNOX being tripped or the warranty status string changing its value to 0x1. That will never affect flashing in any way.

    2) As I mentioned in my comment, this is caused because Magisk didn't get the chance to patch and disable the important Samsung security features in the kernel. This, in turn, triggers the dreaded "Prenormal KG state". You can verify this from the Download Mode.

    When KG state is triggered, it will prevent you from flashing any non-official binary (like the Magisk patched TAR in this case).

    3) So, here's what I did to fix this. I force-booted the Tablet back into Download Mode and plugged it into the PC. Then:
    1. Launched Odin and flashed the official stock FW.
    2. Rebooted into the OS and skipped the initial setup.
    3. Connected the tab to WiFi.
    4. Enabled Developer Options and verified that OEM unlocking was present and greyed out in the ON position.
    5. Rebooted back into Download Mode.
    6. Launched Odin again and unchecked "Auto Reboot" within the Options tab.
    7. Flashed the Patched AP TAR, along with BL and CSC (no CP because I have the WiFi variant)
    8. Manually turn it off, and boot it straight into stock recovery mode
    9. Performed a factory reset via the stock recovery and finally rebooted into the OS.
    10. After the tab booted, I went ahead and did the initial setup (connecting to WiFi, logging into Google and Samsung accounts, and so on).
    11. Went to the app drawer and launched Magisk. It prompted to install the full Magisk app. So did that.
    12. Then re-launched Magisk and did the additional setup as prompted. Upon finishing the tab finally rebooted by itself.
    And voila! It was rooted without any problems.

    As you said, I think it would be a very good idea to mention not rebooting the tablet before the additional Magisk setup is finished. I will do that later today.

    v3.14.4 does exist. But I later came to know that it includes a phishy tracking DLL, thanks @realbbb for pointing in his thread.

    So, it's best to use 3.14.1. I will mention this in the post as well with the apt download link.

    At last, thank you for your message. It means a total win for us as a community. :) Take care and enjoy your new Lenovo tab. Hope you find some exciting things to do with it as well. (y)
    3
    Definitely nice to have a guide like this. Haven't rooted my tablet yet as i got it a few days ago. Really hope that in the long term there will be a dedicated forum for the tab a7 bcs cramming all tab a series devices into a single forum just makes it all unclear and confusing to navigate properly. Even the sm-t580 (tab a6) should have gotten it by the amount of threads i found with various custom roms for it alone.
    But enough about rambling about xda, thanks for this well written guide for the tab a7