SM-T295 - Finally rooted tablet!! (updated 19-March-2021)

Search This thread

NEwguy0101

Member
May 5, 2021
6
0
Tell us what firmware came on your tablet. Also what firmware you downloaded as "stock", and what firmware you downloaded as Android 9.

When you say "failed", do you mean you flash something and the tablet no longer boots? Or boots, but Magisk not installed? Or no sign that flashing changes anything?
I also have the same problem this happened after I flashed the latest firmware T295XXU4BUD4. Now I cant flash android 9 bootloader and when I tried downgrading it won't allow me to. Can anyone pls help me with this I will send the files if required.
 

Talich52

Senior Member
Dec 24, 2010
326
141
I'm currently now on T295XXU4BUD3.....is there any way to root this now??
@gcrutchr @Talich52 sir
If the current bootloader version is already 4, then there is no solution. : (
But if someone has not yet upgraded to UD3 or UD4 ,they can do it via ODIN, using the attached bootloader file with version 3 and then get Root rights :)
 

Attachments

  • BL_T295XXU4BUD3_OS9.tar.zip
    19 MB · Views: 22
  • BL_T295XXU4BUD4_OS9.tar.zip
    19 MB · Views: 18

VampiruX

Senior Member
Jan 19, 2007
127
11
Hi All,

I just got a new Samsung TAB A 8" (4G) SM-T295, and I would like to root. Unfortunately, my firmware is T295XXS3ATB4 and I don’t find the file and a clear tutorial to root with TWRP & Magisk.
Can someone help me?

Thank you very much.
 
Last edited:

Talich52

Senior Member
Dec 24, 2010
326
141
Hi All,

I just got a new Samsung TAB A 8" (4G) SM-T295, and I would like to root. Unfortunately, my firmware is T295XXS3ATB4 and I don’t find the file and a clear tutorial to root with TWRP & Magisk.
Can someone help me?

Thank you very much.
This is Android 9 firmware which is easily rooted :)
1) unlock bootloader
2) flash the attached file
3) install the current version of Magisk Manager and update the current Root-rights from it
Recovery TWRP can be installed through the Flashify application ...
P.S. unpack the file to tar, select as part of AP in ODIN and flash ...
 

Attachments

  • boot_vbmeta_T295XXS3ATB4_root.tar.zip
    10.1 MB · Views: 12
Last edited:
  • Like
Reactions: J.Michael

VampiruX

Senior Member
Jan 19, 2007
127
11
Sorry I made a mistake, my firmware is T295XXS3ATB2. ATB4 is The VBMeta I tried unsuccessfully. I searched for the ATB4 firmware (French), but I didn't find.
 
Last edited:

Talich52

Senior Member
Dec 24, 2010
326
141
Sorry I made a mistake, my firmware is T295XXS3ATB2. ATB4 is The VBMeta I tried unsuccessfully. I searched for the ATB4 firmware (French), but I didn't find.
Ok, here's the file you need :)
If you install a root file from another firmware, then Wi-Fi will not work, it seems there is a connection between the kernel and the system ...
P.S.Firmwares for XEF France region:
This is an OXM multi-region, there is no separate firmware for France.
 

Attachments

  • boot.img_vbmeta_T295XXS3ATB2_M20.4.tar.zip
    10.1 MB · Views: 8
Last edited:
  • Like
Reactions: J.Michael

VampiruX

Senior Member
Jan 19, 2007
127
11
Many thanks Talich52. I'll try the VBmeta ATB2 next week and I'll report here the result. I'll download ATB4 as we never know...
Do you thing TWRP 3.40.1 is the right version or is there a better version for my device as my preceding action were unsuccessfully, but I am not able to determine if it is TWRP or the VBmeta story which is the cause of the trouble?

Edit:
I have a doubt, as I am looking if I have all that is necessary to root, I saw that my Base band is T295XXS3ATB2 and my Version Number is T295XXS3ATB4 (see screen capture enclosed).
So, I am no longer sure of what file I have to use ?
Any advice, please?

Screenshot_20210621_101732.jpg
 
Last edited:

Talich52

Senior Member
Dec 24, 2010
326
141
I have a doubt, as I am looking if I have all that is necessary to root, I saw that my Base band is T295XXS3ATB2 and my Version Number is T295XXS3ATB4 (see screen capture enclosed).
So, I am no longer sure of what file I have to use ?
Any advice, please?
T295XXS3ATB2 this is the modem version.
T295XXS3ATB4 this is the firmware of the device :)
So you need a file for firmware T295XXS3ATB4,
It is posted in the post above ...
 
  • Like
Reactions: J.Michael

VampiruX

Senior Member
Jan 19, 2007
127
11
Thank you for your help.
It worked very easily.
What I did, as you instructed me:
  • I had already unlocked the bootloader,
  • I flashed the VBmeta ATB4 with Odin 3.13.1 and I was a little anxious as Odin didn't detect an error, but on the device I got a red message "Security failed: VBmeta". So nothing seemed bad: I tested starting in download, recovery (the original one) and, of course, in normal way. I decided to continue.
  • I picked TWRP 3.40.1 (by mehanik6) file up and flashed with Odin. It seems to work well as I just tested backup and file explorer, but all seems OK. I just have a problem as every time I start TWRP, the language is unknown but in Cyrillic as I don't understand anything. I have to find and set in French or English.
  • I installed the v23 Magisk APK and with some trials and errors, it finally worked.
  • After that I tested and my device is rooted.
Next days I'll be very busy, so I won't have time to intensively test me tablet, if I encountered any trouble, I'll report.
Bye for now.
 
Last edited:
  • Like
Reactions: J.Michael

Talich52

Senior Member
Dec 24, 2010
326
141
I just have a problem as every time I start TWRP, the language is unknown but in Cyrillic as I don't understand anything. I have to find and set in French or English.
Yes, in TWRP, the default language is Russian, since it was done in Russia. After starting TWRP, go to the Settings and select the desired language. Настройки - Select language - Установить язык.
 
  • Like
Reactions: J.Michael

Talich52

Senior Member
Dec 24, 2010
326
141
Thanks, but is it something to do to keep my own language for the next runs?
Well, after changing the language, it will remain, but when reinstalling TWRP it will again be the default, that is, Russian ... You can try to unload (save) the recovery after changing the language, perhaps during the subsequent installation it will be ...
P.S. No, it didn't work out that way, but I found a solution :) Before installing TWRP, you need to copy the TWRP folder with the settings file to the internal memory of the device. I attached the folder in the archive ...
The language is English, but after changing the language to your own, you can save the TWRP folder with the changed settings file ...
 

Attachments

  • TWRP.zip
    625 bytes · Views: 6
Last edited:
  • Like
Reactions: J.Michael

VampiruX

Senior Member
Jan 19, 2007
127
11
I'll try that, English is very well for.
But for now, I experienced a new trouble when I want to made a full Nandroid backup from TWRP: boot, cache, vendor, image , vendor image worked very well, while at the beginning of data partition backup it stopped with the error message: "processus createFork()finishe with ERROR: 255".
Nothing interesting in the log file, just one line containing the name of the file file.
Unable to go ahead. Any idea ?

Edit: Sorry there is a log file, but with a lot of things, what do I have to look for ?
 
Last edited:

Talich52

Senior Member
Dec 24, 2010
326
141
I'll try that, English is very well for.
But for now, I experienced a new trouble when I want to made a full Nandroid backup from TWRP: boot, cache, vendor, image , vendor image worked very well, while at the beginning of data partition backup it stopped with the error message: "processus createFork()finishe with ERROR: 255".
Nothing interesting in the log file, just one line containing the name of the file file.
Unable to go ahead. Any idea ?

Edit: Sorry there is a log file, but with a lot of things, what do I have to look for ?
I won't tell you about working with TWRP, I'm not a programmer and rarely use TWRP, usually to root the device, and I don't see the point in TWRP backups, since I often change the firmware, and I save the data to the memory card with the Samsung Smart Switch Mobile application and make a Titanium backup ... When restoring, I first restore all applications and many SSSM data and then purely Titaniumom data. This is the best variant :)
P.S. There are other alternative custom recoveries ...
 

VampiruX

Senior Member
Jan 19, 2007
127
11
I won't tell you about working with TWRP, I'm not a programmer and rarely use TWRP, usually to root the device, and I don't see the point in TWRP backups, since I often change the firmware, and I save the data to the memory card with the Samsung Smart Switch Mobile application and make a Titanium backup ... When restoring, I first restore all applications and many SSSM data and then purely Titaniumom data. This is the best variant :)
P.S. There are other alternative custom recoveries ...
Thank you.
I suspected a data error, But I tried to backup data only, and then, I get the error:
"Can not create '/data/media/0/TWRP' folder (Required key not available)). Failed to make backup folder."
So, there is another reason.
I need help as I am now blocked.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Ok, its been some time since i last played with my SM-T295 and now i am thinking of updating it. Just need @Talich52 , @gcrutchr , @J.Michael or anybody else to help me out so that i dont mess it up !

    * First my current status:

    Device: SM-T295
    Bootloader: Unlocked and Rooted with TWRP and + Magisk 23.0
    CSC: INS
    BL VersionL T295XXS3ATB2
    CSC: T295ODM3ATC1
    Android Version: P-9

    * I have already downloaded the latest update (R-11) through Frija - T295XXU4CUF7/T295ODM4CUF8 (INS)


    ## Now, i know that i need to keep BL version at 3 for root rights. My questions are:

    1) Can i replace the BL file (.tar) in R-11 firmware by simply unpacking and repacking the .RAR or it requires linux for .lz4?

    2) From which specific firmware should i extract the BL Version 3 file to be used as replacement?

    3) Is there any specific Odin version which works best for flashing or should i just use the latest v3.14.1?

    3) From what i gather, patching files is no longer required to get root. But i think my preinstalled TWRP will be wiped during update through Odin so i should flash TWRP again ? Will reflashing TWRP also require formatting data again to read storage files?

    4) Do i need to flash specific vendor_fix zip for R-11 or can i simply flash multidisabler-samsung-2.7_test zip ?

    1: Use the attached BL
    2. See #1
    3. Use attached TWRP & disabler...yes formatinfgis required - SAVE YOUR DATA
    4. the attached disabler will fix everything

    See this link for install instructions:
    2
    Any chance I can root this? Been researching and waiting for updates on root for this device with this firmware.

    View attachment 5357971
    Bootloader Version: T295XXU4BUD3, that is, already version 4. The bootloader version cannot be downgraded, so the known method of rooting does not work when the 10 android version 3 bootloader was changed to the android 9 bootloader of the same version 3 ...
    Whether there will be a solution, I do not know.
    At the same time, I have firmware 11 android and Root-rights, as well as TWRP, since I did not update the bootloader and left from android 9, the screen above ...
    2
    There is a way to do that root
    You are on bootloader 'U4'. You cannot root. Samsung has signed kernel/recovery preventing rooting. Also, you cannot downgrade to 'U3'.
    2
    Ok, its been some time since i last played with my SM-T295 and now i am thinking of updating it. Just need @Talich52 , @gcrutchr , @J.Michael or anybody else to help me out so that i dont mess it up !

    * First my current status:

    Device: SM-T295
    Bootloader: Unlocked and Rooted with TWRP and + Magisk 23.0
    CSC: INS
    BL VersionL T295XXS3ATB2
    CSC: T295ODM3ATC1
    Android Version: P-9

    * I have already downloaded the latest update (R-11) through Frija - T295XXU4CUF7/T295ODM4CUF8 (INS)


    ## Now, i know that i need to keep BL version at 3 for root rights. My questions are:

    1) Can i replace the BL file (.tar) in R-11 firmware by simply unpacking and repacking the .RAR or it requires linux for .lz4?

    2) From which specific firmware should i extract the BL Version 3 file to be used as replacement?

    3) Is there any specific Odin version which works best for flashing or should i just use the latest v3.14.1?

    3) From what i gather, patching files is no longer required to get root. But i think my preinstalled TWRP will be wiped during update through Odin so i should flash TWRP again ? Will reflashing TWRP also require formatting data again to read storage files?

    4) Do i need to flash specific vendor_fix zip for R-11 or can i simply flash multidisabler-samsung-2.7_test zip ?
    You can use alternative versions of TWRP and multidisabler:

    3)about the data, I always update or change the firmware with the data saved :) Conditions: after the firmware, do not allow the device to reboot into the system. Specifically, after filling the firmware, we look at how the device enters the normal recovery mode and exits it with a reboot,while at first there will be a warning screen about the unlocked bootloader.We press any volume button, select Recovery in the menu and briefly press the Power button,get into the firmware mode, flash the TWRP file,enter it and install the multidisabler to disable encryption.Installing Magisk.zip and load into the system... Everything, the device is rooted,and the data is intact ;)
  • 6
    I have root on my SM-T295 A8 tablet!!

    See my new post: How to Install TWRP and Root T295


    Update 19 March 2021
    Tested on T295XXU3BUC3 ROM

    Prerequisites:
    Bootloader unlocked - search forums.xda-developers for instructions how to do this.
    OEM unlock on. In Settings/developer options, OEM Unlock slider should be to the right.


    I see people still trying to patch files to get root.
    If you flash the TWRP posted by @Talich52, with reboot unchecked you can install Magisk from TWRP.

    1. If prerequisites met: install Android 9 bootloader through ODIN
    2. Reboot to system
    3. Go into download mode.
    4. Open ODIN and in the AP slot put TWRP (see attachment below)
    5. Uncheck auto reboot
    6. Flash TWRP
    7. Press vol dn + pwr keys.
    8: When screen goes blank, press vol up + pwr keys.
    9. Keep holding down both keys after reboot.
    10. Tablet will reboot again.
    11. When Samsung logo appears stop pressing pwr key.
    12. When bootloader msg appears, release vol up key, quickly press & release pwr key, and quickly press vol up key until in TWRP.
    13. You will then format (NOT WIPE) data. Answer yes to the format prompt
    14. Clear dalvik/cache if prompted
    15. Install Fix_vendor_9.0.zip or Fix_vendor_10.0.zip. See attached files.
    16. Clear dalvik and cache.
    17. Reboot back into recovery.
    18. Install magisk - see attached
    19. Reboot into system. May reboot again - that's okay
    20. Enjoy!!


    Updated (23 March 2020) my Tab A with XXS3ATB2 and got it rooted!!

    Attached AP.tar file is for XXU2ASL3 only.

    T295-Magisk-AP.tar

    Okay, after multiple failed attempts, I read about a method to root my T295. It did not work!! But, I decided to just use Magisk Manager on the boot.img file only. The resultant file would not flash - it will fail. The original boot.img & recovery.img files are 65,536K bytes each. I had to take the Magisk modified boot.img and overlay it onto the original boot.ing file. I did the same for the recovery.img. Then the files would flash successfully. The first thing after booting was to check Magisk Manager. It showed I have Magisk 20.3 installed. So, I tested this with Root Explorer. I did have root!!

    If you are going to try this, you need to unlock your boot loader, I think. I have not tried this with a locked bootloader.


    Basic instructions


    PLEASE READ ALL OF THIS BEFORE STARTING!! VERY IMPORTANT!!

    Here are the steps to root your tablet:
    Make a backup of you apps & data before doing this. This procedure will
    wipe all you data.

    Go to settings.
    Select software info
    Tap build number 7 times to get into developer mode
    Go back to main settings page.
    Scroll to bottom and select developer mode
    In middle of page find OEM unlocking
    Make sure slider is all the way to the right (should say allow bootloader to be unlocked)

    Unlock bootloader:
    1. turn off tablet
    2. press and hold down vol up & vol down keys together
    3. insert usb cable (should already be connected to computer)
    4. when bootloader screen appears, release all keys
    5. press and hold vol up key for 5 seconds, then release
    6. read instructions on screen to unlock bootloader (this will wipe all your data)

    After reboot, go through normal setup.

    Now for the hard part.

    You need to download the complete ROM you have installed on your Tablet.
    It will be better if you have the same ROM version as I do in post in this post (#1).
    You need to unzip the ROM so you can flash it in ODIN.

    If you are on the same ROM version as in my post #1, then you can just download my rooted files.

    Unzip my downloaded root files zip file.
    Unzip the downloaded ROM files.

    In the AP* file, you need to replace my files in the zip: boot.img, recovery.img & vbmeta.img

    Start ODIN. Select files for BL*, AP*, CSC* & CP*
    For CSC file, select HOME_CSC*
    *** Uncheck auto reboot ***

    Flash ROM.
    After flashing ROM. press vol dn + pwr key
    As soon as screen goes blank press vol up key and hold
    When get into recovery, select data wipe, then reboot
    Set up phone as you normally would.
    After setup, go to Play store and install Magisk Manager. Run Magisk Manager to see if you have root.


    Do It Yourself Instructions
    You need to do some research before doing this. This is NOT a walk you by the hand tutorial. You need to learn some things before following these instructions. Learn how to use lz4.exe. Learn how to use simg2img. Learn how to make a .tar file.



    Make a backup of you apps & data before doing this. This procedure will
    wipe all you data.

    Go to settings.
    Select software info
    Tap build number 7 times to get into developer mode
    Go back to main settings page.
    Scroll to bottom and select developer mode
    In middle of page find OEM unlocking
    Make sure slider is all the way to the right (should say allow bootloader to be unlocked)

    Unlock bootloader:
    1. turn off tablet
    2. press and hold down vol up & vol down keys together
    3. insert usb cable (should already be connected to computer)
    4. when bootloader screen appears, release all keys
    5. press and hold vol up key for 5 seconds, then release
    6. read instructions on screen to unlock bootloader (this will wipe all your data)

    After reboot, go through normal setup.

    Now for the hard part.

    You need to download the complete ROM you have installed on your Tablet.
    Extract ROM files
    Extract system.*.lz4, recovery*.lz4 and vbmeta*.lz4
    Use tar to make an AP.tar file with the 3 above files. **Search the Internet if you do not know how to use tar.
    Copy the AP.tar file to your phone. It is better to use adb push to prevent file correuption.
    Install Magisk Manager from Play store.
    Run Magisk Manager. Select install Magisk. Choose Select and Patch a file. Follow directions on screen to patch the AP.tar file.
    Once the AP.tar file has been patched, use adb to pul the file to yur computer.
    Extract the file from the AP.tar file.

    Now come the hard part:

    You cannot edit .lz4 directly. You have to decompress them. After decompressing system*, use simg2img to decompress the sparse file. Search the Internet if you do not know how to do this.

    Now we make our modified files so they will flash in ODIN.

    Instructions:
    I used hex editor neo - a windows 10 app
    I opened the stock kernel & recovery files in hex editor neo
    I opened the Magisk modified kernel & recovery files in hex editor neo
    I copied the modified kernel & recovery code onto their respective stock files in hex editor neo
    I saved the stock files & closed hex editor neo.
    I used cygwin to create a tar file: boot.img, recovery.img, vbmeta.img plus other files in original AP*.MD5 file.
    You should also flash all ROM *.MD5 files (BL, CP, CSC) per Magisk instructions.
    New AP.tar contents:
    boot.img
    dtbo.img.lz4
    meta-data
    recovery.img
    system.img.ext4.lz4
    userdata.img.ext4.lz4
    vbmeta.img
    vendor.img.ext4.lz4

    I used Odin to flash the tar file

    Flash ROM.
    After flashing ROM. press vol dn + pwr key
    As soon as screen goes blank press vol up key and hold
    When get into recovery, select data wipe, then reboot
    Set up phone as you normally would.
    After setup, go to Play store and install Magisk Manager. Run Magisk Manager to see if you have root.

    After installing Magisk:

    (Powering up normally) → (System with NO Magisk)
    (OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
    (OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)

    Please follow my instructions and the install instructions from Magisk web page.

    Magisk Installation
    3
    What system do you use to manipulate the files? (Windows? Linux? Android?)

    What is "overlay"? Do you extract the boot.img from the original AP.tar.md5, and from the magisk-patched.tar, copy the magisk-patched-boot.img to the beginning of the original-boot.img, and then replace the boot.img in magisk-patched.tar?

    Do you give Odin four files, or just AP? Do you use CSC or HOME_CSC?

    In answer to your question, basically, yes.
    I only flash the 3 files in the .tar file

    I am on a Windows 10 laptop. Only 3 files need to be modified by Magisk: boot.img, recovery.img, vbmeta.img
    I use Hex Editor Neo for overlaying the modified kernel and recovery files..
    At the end of these 2 stock files is code that needs to be there, thus the 65 MB file size.
    So I open the stock .img files (boot, recovery) in Hex Editor Neo, and copy the modded boot, recovery code into each stock .img file..
    I use cygwin to create the .tar file, then flash with ODIN 3.1.14
    3
    Better Android 9 or Android 10 to root? Which firmware is better and faster for this device (SM-T295)?


    Are there any problems with knox for downgrade or root?
    To root 10 android, you need to install the bootloader from the previous firmware 9 android, and then the rooting itself is the same - either patch the kernel and flash, or install TWRP and root the device from it ... The TWRP option is easier, but there is some difficulty in entering TWRP after it installation ...
    On this KNOX device, cropped ...
    In particular, there is no KNOX counter, that is, you can root the device, and then flash the stock firmware and there will be no traces ...
    There is no KNOX flag as such 0x0 and 0x1 ...
    Here find the SM-T295 model: https://www.samsungknox.com/en/knox-platform/supported-devices/2.5+
    Our model does not support KNOX function ...
    There is really a KNOX Guard application in the system, but if you Disable or Remove it, the device will be locked ...
    It is not KNOX that prohibits downgrading the firmware version, but the bootloader. The version of the bootloader cannot be downgraded. From the 10th android you can return to the 9th android, since the version of the bootloader is 3 both there and there, but below you will not be able to install the firmware with versions 2 and 1 of the bootloader ...
    3
    Ok, its been some time since i last played with my SM-T295 and now i am thinking of updating it. Just need @Talich52 , @gcrutchr , @J.Michael or anybody else to help me out so that i dont mess it up !

    * First my current status:

    Device: SM-T295
    Bootloader: Unlocked and Rooted with TWRP and + Magisk 23.0
    CSC: INS
    BL VersionL T295XXS3ATB2
    CSC: T295ODM3ATC1
    Android Version: P-9

    * I have already downloaded the latest update (R-11) through Frija - T295XXU4CUF7/T295ODM4CUF8 (INS)


    ## Now, i know that i need to keep BL version at 3 for root rights. My questions are:

    1) Can i replace the BL file (.tar) in R-11 firmware by simply unpacking and repacking the .RAR or it requires linux for .lz4?

    2) From which specific firmware should i extract the BL Version 3 file to be used as replacement?

    3) Is there any specific Odin version which works best for flashing or should i just use the latest v3.14.1?

    3) From what i gather, patching files is no longer required to get root. But i think my preinstalled TWRP will be wiped during update through Odin so i should flash TWRP again ? Will reflashing TWRP also require formatting data again to read storage files?

    4) Do i need to flash specific vendor_fix zip for R-11 or can i simply flash multidisabler-samsung-2.7_test zip ?

    1: Use the attached BL
    2. See #1
    3. Use attached TWRP & disabler...yes formatinfgis required - SAVE YOUR DATA
    4. the attached disabler will fix everything

    See this link for install instructions:
    2
    Ok, its been some time since i last played with my SM-T295 and now i am thinking of updating it. Just need @Talich52 , @gcrutchr , @J.Michael or anybody else to help me out so that i dont mess it up !

    * First my current status:

    Device: SM-T295
    Bootloader: Unlocked and Rooted with TWRP and + Magisk 23.0
    CSC: INS
    BL VersionL T295XXS3ATB2
    CSC: T295ODM3ATC1
    Android Version: P-9

    * I have already downloaded the latest update (R-11) through Frija - T295XXU4CUF7/T295ODM4CUF8 (INS)


    ## Now, i know that i need to keep BL version at 3 for root rights. My questions are:

    1) Can i replace the BL file (.tar) in R-11 firmware by simply unpacking and repacking the .RAR or it requires linux for .lz4?

    2) From which specific firmware should i extract the BL Version 3 file to be used as replacement?

    3) Is there any specific Odin version which works best for flashing or should i just use the latest v3.14.1?

    3) From what i gather, patching files is no longer required to get root. But i think my preinstalled TWRP will be wiped during update through Odin so i should flash TWRP again ? Will reflashing TWRP also require formatting data again to read storage files?

    4) Do i need to flash specific vendor_fix zip for R-11 or can i simply flash multidisabler-samsung-2.7_test zip ?
    You can use alternative versions of TWRP and multidisabler:

    3)about the data, I always update or change the firmware with the data saved :) Conditions: after the firmware, do not allow the device to reboot into the system. Specifically, after filling the firmware, we look at how the device enters the normal recovery mode and exits it with a reboot,while at first there will be a warning screen about the unlocked bootloader.We press any volume button, select Recovery in the menu and briefly press the Power button,get into the firmware mode, flash the TWRP file,enter it and install the multidisabler to disable encryption.Installing Magisk.zip and load into the system... Everything, the device is rooted,and the data is intact ;)