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

Search This thread
Hi All, I have just bought a used SM-T295 which I want to use in an old car to hook up to its existing audio system , so that it can auto startup/shutdown etc.
Presently its stock android 10 and I would prefer to root it from the outset.

I here as a newbie and always fall at the first hurdle, more often because I see instructions on XDA only to learn that parameters/events have changed since a guideline was first written. For example on this tab, I've done the multiple tapping to get dev options, and already stuck as there seems to be no OEM unlock option.

So I would greatly appreciate advice on whether ...as of Feb24 are the instructions at the top of this thread still 100% valid to achieve root.

Secondly, if this tab is stock Android 10, ( rom T295XXU3BTI4 ) is there a standard go-to rom upgrade to make it 'better'. Nothing that makes it flakey...only want 100% stable rom upgrades.

Many thanks
 
Hi All, I have just bought a used SM-T295 which I want to use in an old car to hook up to its existing audio system , so that it can auto startup/shutdown etc.
Presently its stock android 10 and I would prefer to root it from the outset.

I here as a newbie and always fall at the first hurdle, more often because I see instructions on XDA only to learn that parameters/events have changed since a guideline was first written. For example on this tab, I've done the multiple tapping to get dev options, and already stuck as there seems to be no OEM unlock option.

So I would greatly appreciate advice on whether ...as of Feb24 are the instructions at the top of this thread still 100% valid to achieve root.

Secondly, if this tab is stock Android 10, ( rom T295XXU3BTI4 ) is there a standard go-to rom upgrade to make it 'better'. Nothing that makes it flakey...only want 100% stable rom upgrades.

Many thanks
Hi there,
I think you must wait for 7 days, because the device just got installed, and after that you will find the option in developer options. If you don't want to wait, you could try to set the date to earlier or further.
 
  • Like
Reactions: J.Michael

Talich52

Senior Member
Dec 24, 2010
476
249
if this tab is stock Android 10, ( rom T295XXU3BTI4 ) is there a standard go-to rom upgrade to make it 'better'. Nothing that makes it flakey...only want 100% stable rom upgrades.
Do not update the firmware to version 4 and 5 of the bootloader, otherwise you will not be able to root the device ...
 
  • Like
Reactions: J.Michael
Do not update the firmware to version 4 and 5 of the bootloader, otherwise you will not be able to root the device ...
Right now I wish I even knew what was installed on the device. It was bought used off ebay but I've got no reason to believe its ever been modded before. How can I check what version I have? Would this mean doing one of them startups holding the vol+ & power button?
 
OK next hurdle : I have definitely achieved OEM unlock / unlock bootloader., and started the next steps..

I have installed Odin"3B PatcheD/ModdeD v 3.14.1." and followed instruction step 1/2/3/4/5/6 i.e.
> the BL bootloader file ( presumably in box BL to be ticked )
> the AP TWRP 'tar' file via the AP slot.

But here I am now stuck , for a few reasons possibly
- During a re-boot I keep getting the new frequent annoying Samsung warning message about the fact the device has an unlocked bootloader which interferes things.
- I don't quite have the dexterity to follow the confusing sequence of button pressing
- I'm stuggling to visualise what view/image I should be seeing as all the button pressing is occurring...in other words....the words are in not enough, I need to visually see the sequential events.

Is anyone able to look at these instructions beyond step #5 and either find a YT vid link or illustrate with pics of what I should be seeing.

EG I've I now experienced four different boot screens.
1. The Blue screen achieved by pressing vol up + vol down then plugging in a USB feed
2. The boot screen achieved by pressing vol up + pwr. Is this 'recovery' ?
3. The screen displayed when via opting for 'reboot to bootloader' on previous screen. So is this 'bootloader' or 'download'
4. An options screen overlaid onto the unlocked bootloader warning, I stumbled upon this when trying to follow the complex sequence of button pressing and can't even recall how I got this.

... so when I read 'in download mode' and 'in TWRP' , as a greenhorn I need assistance to join the dots. What do these look like?

Beyond this , I see 'Install Fix_vendor_10.0.zip' and 'Install magisk'. Yes I've downloaded the files to my PC...but I need further explanation on what method/means I use to install.

These instructions are aimed at regular device modders, not occasional passers by. I've attached the images I've described and would greatly appreciate some assistance.
Thanks

EDIT : I've stumbled further forward into accessing this TWRP thing and changed ment from Russian? to English.

I've installed the 'Fix Vendor 10" and cleared cache. Now I'm on step #15 which says "You will then format (NOT WIPE) data." OK so there are no options on this TWRP menu to format...only 'WIPE'. So what needs to be done to 'Format' per step #15 ??

EDIT 2: Regardless of the step #15 I carried on andTWRP installed the final 'Magisk' file and let it auto reboot.

So for better or for worse, it autobooted and when I checked via 'Rootchecker app...and...yey I gpt root!!
Mote screen pics added in case they help others down the line.

Next for me is finding the best 'go-to' rom to install :)
 

Attachments

  • 1-UNLOCK_BOOT.jpg
    1-UNLOCK_BOOT.jpg
    306.9 KB · Views: 14
  • 2-BOOTLOADER.jpg
    2-BOOTLOADER.jpg
    270.2 KB · Views: 14
  • 3-DOWNLOAD.jpg
    3-DOWNLOAD.jpg
    250 KB · Views: 11
  • 4-OPTIONS.jpg
    4-OPTIONS.jpg
    245 KB · Views: 10
  • IMG20230202123425.jpg
    IMG20230202123425.jpg
    180.7 KB · Views: 12
  • IMG20230202151657.jpg
    IMG20230202151657.jpg
    277.1 KB · Views: 9
  • IMG20230202145722.jpg
    IMG20230202145722.jpg
    221.8 KB · Views: 9
  • IMG20230202145847.jpg
    IMG20230202145847.jpg
    260.6 KB · Views: 9
  • IMG20230202150635.jpg
    IMG20230202150635.jpg
    202.4 KB · Views: 9
  • IMG20230202151443.jpg
    IMG20230202151443.jpg
    237.5 KB · Views: 10
  • IMG20230202151508.jpg
    IMG20230202151508.jpg
    262.3 KB · Views: 8
  • IMG20230202151750.jpg
    IMG20230202151750.jpg
    245.7 KB · Views: 8
  • IMG20230202153536.jpg
    IMG20230202153536.jpg
    272.8 KB · Views: 8
  • IMG20230202154755.jpg
    IMG20230202154755.jpg
    252.3 KB · Views: 12
Last edited:
  • Wow
Reactions: bingo1951
OK next hurdle : I have definitely achieved OEM unlock / unlock bootloader., and started the next steps..

I have installed Odin"3B PatcheD/ModdeD v 3.14.1." and followed instruction step 1/2/3/4/5/6 i.e.
> the BL bootloader file ( presumably in box BL to be ticked )
> the AP TWRP 'tar' file via the AP slot.

But here I am now stuck , for a few reasons possibly
- During a re-boot I keep getting the new frequent annoying Samsung warning message about the fact the device has an unlocked bootloader which interferes things.
- I don't quite have the dexterity to follow the confusing sequence of button pressing
- I'm stuggling to visualise what view/image I should be seeing as all the button pressing is occurring...in other words....the words are in not enough, I need to visually see the sequential events.

Is anyone able to look at these instructions beyond step #5 and either find a YT vid link or illustrate with pics of what I should be seeing.

EG I've I now experienced four different boot screens.
1. The Blue screen achieved by pressing vol up + vol down then plugging in a USB feed
2. The boot screen achieved by pressing vol up + pwr. Is this 'recovery' ?
3. The screen displayed when via opting for 'reboot to bootloader' on previous screen. So is this 'bootloader' or 'download'
4. An options screen overlaid onto the unlocked bootloader warning, I stumbled upon this when trying to follow the complex sequence of button pressing and can't even recall how I got this.

... so when I read 'in download mode' and 'in TWRP' , as a greenhorn I need assistance to join the dots. What do these look like?

Beyond this , I see 'Install Fix_vendor_10.0.zip' and 'Install magisk'. Yes I've downloaded the files to my PC...but I need further explanation on what method/means I use to install.

These instructions are aimed at regular device modders, not occasional passers by. I've attached the images I've described and would greatly appreciate some assistance.
Thanks

EDIT : I've stumbled further forward into accessing this TWRP thing and changed ment from Russian? to English.

I've installed the 'Fix Vendor 10" and cleared cache. Now I'm on step #15 which says "You will then format (NOT WIPE) data." OK so there are no options on this TWRP menu to format...only 'WIPE'. So what needs to be done to 'Format' per step #15 ??

EDIT 2: Regardless of the step #15 I carried on andTWRP installed the final 'Magisk' file and let it auto reboot.

So for better or for worse, it autobooted and when I checked via 'Rootchecker app...and...yey I gpt root!!
Mote screen pics added in case they help others down the line.

Next for me is finding the best 'go-to' rom to install :)
You could try the latest LineageOS GSI rom from here, if you want. I recommend you download the 'Treble Info' app from Google Play, and check there whether it is supported. Also look at the section which rom you are going to need for the device.
 
You could try the latest LineageOS GSI rom from here, if you want. I recommend you download the 'Treble Info' app from Google Play, and check there whether it is supported. Also look at the section which rom you are going to need for the device.
Thanks Minionguy, I've just looked on 'Treble Info' app and it tells me 'Generic System Image Found!' and confirms my device supports , image is "system-arm64-ab.img,xz".

I see an option to browse images. Do I continue to action from this app...or via the link you gave ? My device is presently stock Android 10, what version can it reach with 'lastest LineageOS GSI" ?
Thanks
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,811
2,048
Samsung Galaxy Tab A series
@ebod The nag screen is an unfortunate fact of life with Samsung. In spite of it telling you to press the power button, you can just wait and it eventually goes away. I agree, it is an especial nuisance when struggling to boot to Magisk-in-recovery.

The screen that says "Android recovery" at the top is recovery.

The screen that says "download mode" at the bottom of 8 lines is download mode.

That funny overwriting menu is something I have triggered. I also cannot get it consistently. From the options, I assume it is a backup (secondary; fallback; reserve; emergency) recovery mode. I do not think it is any more capable than the normal recovery mode.

Bottom line: You got it to work. Mazel tov! Now stop poking it before you break something. And never let anything update.
 
  • Like
Reactions: Talich52
@ebod The nag screen is an unfortunate fact of life with Samsung. In spite of it telling you to press the power button, you can just wait and it eventually goes away. I agree, it is an especial nuisance when struggling to boot to Magisk-in-recovery.

The screen that says "Android recovery" at the top is recovery.

The screen that says "download mode" at the bottom of 8 lines is download mode.

That funny overwriting menu is something I have triggered. I also cannot get it consistently. From the options, I assume it is a backup (secondary; fallback; reserve; emergency) recovery mode. I do not think it is any more capable than the normal recovery mode.

Bottom line: You got it to work. Mazel tov! Now stop poking it before you break something. And never let anything update.
haha yep thanks. This Tab A is destined to be a car mounted unit in an old 2008 Volvo C70.
( to illustrate..see this YT vid
)

I just knew that a rooted device makes a lot of the complexities of auto-start/auto-stop etc etc possible.

I'm also a newbie to the 'Tasker app' world, but that is key to making the device behave like a head unit and run seamlessly. So I'll hang around to see if a better custom rom is worth installing before I move forward to setting up Tasker on it. I want a fast autoboot on sensing usb power, so that 'nag screen' is a hindrance I'd prefer to do without..

opps finally one more thing .. When you say 'never let anything update' should I literally switch off the software update option' within settings>Software update? Anything else?
 
Last edited:

J.Michael

Recognized Contributor
Jan 20, 2018
1,811
2,048
Samsung Galaxy Tab A series
haha yep thanks. This Tab A is destined to be a car mounted unit in an old 2008 Volvo C70.
( to illustrate..see this YT vid
)

I just knew that a rooted device makes a lot of the complexities of auto-start/auto-stop etc etc possible.

I'm also a newbie to the 'Tasker app' world, but that is key to making the device behave like a head unit and run seamlessly. So I'll hang around to see if a better custom rom is worth installing before I move forward to setting up Tasker on it. I want a fast autoboot on sensing usb power, so that 'nag screen' is a hindrance I'd prefer to do without..

opps finally one more thing .. When you say 'never let anything update' should I literally switch off the software update option' within settings>Software update? Anything else?
Yes, I meant turn off every automatic update option you can turn off. And set the wi-fi (if any) to "metered" to discourage the ones you can't turn off.

As for the nag screen: my car came with a screen, and every time it comes on there's a warning that staring at the screen while driving could be hazardous to someone's life. I just grit my teeth and wait for it to go away. Kind of like I grind my teeth from the time it starts playing whatever it's playing to the time the controls become active, so I can mute the damned thing before I start the car.

Given how long it takes the tablet to boot, the nag screen is really nothing.
 
  • Like
Reactions: Talich52 and ebod
Thanks Minionguy, I've just looked on 'Treble Info' app and it tells me 'Generic System Image Found!' and confirms my device supports , image is "system-arm64-ab.img,xz".

I see an option to browse images. Do I continue to action from this app...or via the link you gave ? My device is presently stock Android 10, what version can it reach with 'lastest LineageOS GSI" ?
Thanks
You could use any of those versions:


Screenshot_20230203_081116_Samsung Internet.png


LineageOS 20 is Android 13, LineageOS 19 is Android 12.1, LineageOS 18 is Android 12 and so on (I thought). The latest is version 20 for Android 13. If you want to install this one, you have a few options:
Screenshot_20230203_081532_Samsung Internet.png

And this is for the filenames to get the good one for your device:
Screenshot_20230203_081559_Samsung Internet.png
 
OK Many thanks Minionguy, yes if its stable I will be happy to go lineage 20. I am UK based so please can you steer me to a suitable safe/stable file, and then what is the method to install (ODIN or via this TWRP boot screen)?? Forgive me whilst I have done this kind of thing before...it was many many years ago back on devices like Galaxy S3. Since then I have had LG/Huawei/OPPO and never had the need/desire to tinker with devices in 8<>10yrs
 
OK Many thanks Minionguy, yes if its stable I will be happy to go lineage 20. I am UK based so please can you steer me to a suitable safe/stable file, and then what is the method to install (ODIN or via this TWRP boot screen)?? Forgive me whilst I have done this kind of thing before...it was many many years ago back on devices like Galaxy S3. Since then I have had LG/Huawei/OPPO and never had the need/desire to tinker with devices in 8<>10yrs
It should be flashed as a zip in TWRP. I recommend you this one. It has Google apps, but not superuser. I recommend you install superuser later on via TWRP and then Magisk.
 
It should be flashed as a zip in TWRP. I recommend you this one. It has Google apps, but not superuser. I recommend you install superuser later on via TWRP and then Magisk.
Right I'm on it , step 1 new rom via TWRP, step 2 will be SU ( link to appropriate file would be greatly appreciated ). Just regarding this 'mgkisk' file, I thought I already installed this as part of the root steps? or do you mean I need to 're-install' after the new rom is added?

Finally will this new lineage 20 rom stop any kind of Samsung auto-update which could wipe out all the mods? Or will I have to force / switch off any auto-update settings?
Thanks again :)
 
Right I'm on it , step 1 new rom via TWRP, step 2 will be SU ( link to appropriate file would be greatly appreciated ). Just regarding this 'mgkisk' file, I thought I already installed this as part of the root steps? or do you mean I need to 're-install' after the new rom is added?

Finally will this new lineage 20 rom stop any kind of Samsung auto-update which could wipe out all the mods? Or will I have to force / switch off any auto-update settings?
Thanks again :)
You will need to reinstall root, will link the file later. I think that because you use a different rom, you do not need to worry about that.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    Many thanks for the recompiled BL file --upgrading done!
    Next step will try twrp-3.5 + magisk --for rooting rights.
    If you plan to use TWRP, then you need to disable encryption. To do this, install multidisabler and make format data-yes (no wipe data). Well, then install Magisk.zip for rooting.
    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: