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

Search This thread

Talich52

Senior Member
Dec 24, 2010
474
249
Per 295XXU4CVG3 android 11 ?
On this firmware, Root rights cannot be obtained, nor can TWRP be installed. We need a bootloader from Android 9, and it is 3 versions, rollback (downgrading) of the bootloader is prohibited ... :(
P.S. by the way, there is an update to firmware like T295XXS5CWA1 with version 5 of the bootloader...
 
Last edited:
Hi All, After several unsuccessful attempts to flash a new rom, I'm presently back to a rooted stock rom again. Tonight things went south when I tried to update the Magisk file that came as part of this tutorial. Are there any do's & don'ts associated with updating this app? eg what again the option regarding boot? I think I took it and all bombed out :-/
 

Attachments

  • IMG20230206214206.jpg
    IMG20230206214206.jpg
    238.1 KB · Views: 10

J.Michael

Recognized Contributor
Jan 20, 2018
1,646
1,818
Samsung Galaxy Tab A series
Hi All, After several unsuccessful attempts to flash a new rom, I'm presently back to a rooted stock rom again. Tonight things went south when I tried to update the Magisk file that came as part of this tutorial. Are there any do's & don'ts associated with updating this app? eg what again the option regarding boot? I think I took it and all bombed out :-/
What tutorial?

I wouldn't update Magisk. Or the Android.

If you want to update, lots of people have success by letting the Magisk manager app perform the update. I have lost track of the different versions of Magisk, and which can update to which. Another approach would be to start over: Whatever you did originally, do it again, but use a newer Magisk manager app apk to do the patching. Nothing changes in Odin. It might not be necessary to do all the wiping and reformatting. If you want to try to preserve your data, make sure you use the CSC file that does not force a wipe. (I think it's HOME_CSC.tar that does *not* force a wipe, but you should really find at least one other source that says the same.)
 
What tutorial?

I wouldn't update Magisk. Or the Android.

If you want to update, lots of people have success by letting the Magisk manager app perform the update. I have lost track of the different versions of Magisk, and which can update to which. Another approach would be to start over: Whatever you did originally, do it again, but use a newer Magisk manager app apk to do the patching. Nothing changes in Odin. It might not be necessary to do all the wiping and reformatting. If you want to try to preserve your data, make sure you use the CSC file that does not force a wipe. (I think it's HOME_CSC.tar that does *not* force a wipe, but you should really find at least one other source that says the same.)
The tutorial I meant was this original post or in particular the update thread that was linked from it. I only downloaded the Magisk file from the attachments there, and my screenshot shows what apparently is the latest.
But to be honest, I'm just beginning to conclude its more trouble than is worth trying to update to a newer rom. There is literally too much conflicting information to make sense of , and nobody so far has been able to give me a proven safe method to get me there.

I have Android 10 stock with root, root was my single biggest priority. If you say "I would update Magisk" then I probably just uninstall the app as its pointless being there.

My next priority is to try find out how to dump the stupid Samsung bootlock warning message as basically I need this SM-T295 to just quickly startup on sensing usb power ( is that called fastboot? )
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,646
1,818
Samsung Galaxy Tab A series
The tutorial I meant was this original post or in particular the update thread that was linked from it. I only downloaded the Magisk file from the attachments there, and my screenshot shows what apparently is the latest.
But to be honest, I'm just beginning to conclude its more trouble than is worth trying to update to a newer rom. There is literally too much conflicting information to make sense of , and nobody so far has been able to give me a proven safe method to get me there.

I have Android 10 stock with root, root was my single biggest priority. If you say "I would update Magisk" then I probably just uninstall the app as its pointless being there.

My next priority is to try find out how to dump the stupid Samsung bootlock warning message as basically I need this SM-T295 to just quickly startup on sensing usb power ( is that called fastboot? )
You do not have the latest version of Magisk. You might have the same version I used four years ago.

But I said "I would *not* update Magisk".

If that's what you meant to say just before you said "probably just uninstall the app as its pointless being there" -- that's a matter of taste: Magisk has other functions, the manager is of some use, but it's trivial to reinstall it when you think you want it. I don't think the app is involved in granting setuser privilege -- but it might be involved in clearing the flag if you inadvertently deny privilege to an app.

A lot of people hate the nag screen. I don't think anyone has been able to eliminate it. You do not have to respond to it, just wait and it goes away.

"fastboot" is a program like "adb" -- it runs on a PC and communicates with a device. It can only be used with a device that supports it. Samsung does not support fastboot -- that's why we have to use Odin.
 
The tutorial I meant was this original post or in particular the update thread that was linked from it. I only downloaded the Magisk file from the attachments there, and my screenshot shows what apparently is the latest.
But to be honest, I'm just beginning to conclude its more trouble than is worth trying to update to a newer rom. There is literally too much conflicting information to make sense of , and nobody so far has been able to give me a proven safe method to get me there.

I have Android 10 stock with root, root was my single biggest priority. If you say "I would update Magisk" then I probably just uninstall the app as its pointless being there.

My next priority is to try find out how to dump the stupid Samsung bootlock warning message as basically I need this SM-T295 to just quickly startup on sensing usb power ( is that called fastboot? )
Oh man, just download the latest version from here: https://github.com/topjohnwu/Magisk

The latest version is v25.2
 
You do not have the latest version of Magisk. You might have the same version I used four years ago.

But I said "I would *not* update Magisk".

If that's what you meant to say just before you said "probably just uninstall the app as its pointless being there" -- that's a matter of taste: Magisk has other functions, the manager is of some use, but it's trivial to reinstall it when you think you want it. I don't think the app is involved in granting setuser privilege -- but it might be involved in clearing the flag if you inadvertently deny privilege to an app.

A lot of people hate the nag screen. I don't think anyone has been able to eliminate it. You do not have to respond to it, just wait and it goes away.

"fastboot" is a program like "adb" -- it runs on a PC and communicates with a device. It can only be used with a device that supports it. Samsung does not support fastboot -- that's why we have to use Odin.
I'm a bit burned out getting root and then loosing it after trying to update things such as Magisk, then having to start all over again. So I'm just settling with a rooted stock rom as I can't get a dumbed down enough support that gives me confidence to.

Prime focus now is i) getting the device to start up on receiving usb power and ii) although I appreciate its just a warning that times out...I want to drop the Samsung bootlock warning as it just slows startup when the device gets mounted as a piggyback head unit in my Volvo.
I managed to get an old stock rom / non-root LG H850 to fire up on usb power, just need help to do the same for an SM-T295..
 
  • Like
Reactions: J.Michael
I'm a bit burned out getting root and then loosing it after trying to update things such as Magisk, then having to start all over again. So I'm just settling with a rooted stock rom as I can't get a dumbed down enough support that gives me confidence to.

Prime focus now is i) getting the device to start up on receiving usb power and ii) although I appreciate its just a warning that times out...I want to drop the Samsung bootlock warning as it just slows startup when the device gets mounted as a piggyback head unit in my Volvo.
I managed to get an old stock rom / non-root LG H850 to fire up on usb power, just need help to do the same for an SM-T295..
So, I've found some steps:
1. Download the firmware for your SM-T295.
2. Download the 7-Zip version from here. NOT THE NORMAL VERSION, as that one has not support for .tar files...
3. Open the BL file from the firmware package using the newly, custom version of 7-Zip.
4. Extract the ``up_param.bin.lz4`` file from the BL file.
5. And then extract the new ``up_param.bin.lz4`` file.
6. And then extract the ``up_param.bin`` file from the new ``up_param.bin.lz4`` folder
7. Open the ``up_param.bin`` file and delete the ``boot_warning.jpg`` and ``svg_orange.jpg`` if they exist.
8. Then right click the ``up_param.bin`` file and select 'Add to archive' from 7-Zip menu.
9. Now create an archive from the file with the format ``tar``.
10. Flash the ``up_param.tar`` file with Odin as BL file.
 
  • Like
Reactions: J.Michael
So, I've found some steps:
1. Download the firmware for your SM-T295.
2. Download the 7-Zip version from here. NOT THE NORMAL VERSION, as that one has not support for .tar files...
3. Open the BL file from the firmware package using the newly, custom version of 7-Zip.
4. Extract the ``up_param.bin.lz4`` file from the BL file.
5. And then extract the new ``up_param.bin.lz4`` file.
6. And then extract the ``up_param.bin`` file from the new ``up_param.bin.lz4`` folder
7. Open the ``up_param.bin`` file and delete the ``boot_warning.jpg`` and ``svg_orange.jpg`` if they exist.
8. Then right click the ``up_param.bin`` file and select 'Add to archive' from 7-Zip menu.
9. Now create an archive from the file with the format ``tar``.
10. Flash the ``up_param.tar`` file with Odin as BL file.
1. I have already got firmware as part of recovering from a failed GSI install. I'm on the samfw.com version T295XXU3BTI4 with the appropriate set of AP/BL/CP/CSC tar.md5 files
2. ???? here we go again! Unclear to a newbie, just a link to a page littered with download links. Haven't got a clue where to go / what I should be downloading :-/
 
1. I have already got firmware as part of recovering from a failed GSI install. I'm on the samfw.com version T295XXU3BTI4 with the appropriate set of AP/BL/CP/CSC tar.md5 files
2. ???? here we go again! Unclear to a newbie, just a link to a page littered with download links. Haven't got a clue where to go / what I should be downloading :-/
Clicking the blue 'here' which will open the download link of the custom 7-Zip program. I think you need to download the '7z22.01-zstd-x64.exe' asset, because I think your computer is 64-bit (most modern computers are).
 
Clicking the blue 'here' which will open the download link of the custom 7-Zip program. I think you need to download the '7z22.01-zstd-x64.exe' asset, because I think your computer is 64-bit (most modern computers are).
OK lets see where this one takes me :)

i) I thought as part of rooting, I replaced a stock tar.md5 file with a new one to get TWRP installed. There's no scenario here of me editing a stock file and then busting the device again due to what was modded for TWRP??

ii) only for info on the other task of auto booting on power/dock , I've found this to pursue, don't know what you to do with it but it shows it can be done : https://forum.xda-developers.com/t/q-power-on-when-plugged-in-boot-when-docked.1187631/
 
OK lets see where this one takes me :)

i) I thought as part of rooting, I replaced a stock tar.md5 file with a new one to get TWRP installed. There's no scenario here of me editing a stock file and then busting the device again due to what was modded for TWRP??

ii) only for info on the other task of auto booting on power/dock , I've found this to pursue, don't know what you to do with it but it shows it can be done : https://forum.xda-developers.com/t/q-power-on-when-plugged-in-boot-when-docked.1187631/
Wait, I don't really understand your first part, but I do understand the second one. I guess you want the tablet to boot up when you start your car, and that is possible by editing the file at '/system/bin/playlpm':
Bash:
#!/system/bin/sh
/system/bin/reboot
I guess that it's the same as told in the thread you listed to me. You can do this by installing a root explorer app or using TWRP.
Also be sure to set the permission of this file to '0755'. Well, let's say this:
1675877904733.png
 
OK lets see where this one takes me :)

i) I thought as part of rooting, I replaced a stock tar.md5 file with a new one to get TWRP installed. There's no scenario here of me editing a stock file and then busting the device again due to what was modded for TWRP??

ii) only for info on the other task of auto booting on power/dock , I've found this to pursue, don't know what you to do with it but it shows it can be done : https://forum.xda-developers.com/t/q-power-on-when-plugged-in-boot-when-docked.1187631/

Oh well, checked BL file via this new 7ZIP and no sign of a "up_param" file :-/
1675877663174.png
 
Wait, I don't really understand your first part, but I do understand the second one. I guess you want the tablet to boot up when you start your car, and that is possible by editing the file at '/system/bin/playlpm':

As part of getting root, I had to add another 'BL' file per the tutorial. So there is a stock BL file and one associated with the root tutorial. But in any case I've looked at both with the 7zip you linked and neither shows an "up_param" file
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I decided to measure the boot time from the off state. Total 1 minute 20 seconds. The unlocked bootloader splash screen for the first 10 seconds, then the Samsung Galaxy Tab A splash screen for 40 seconds. If the unlock splash screen is removed, the total time will decrease by 10 seconds to 1 minute 10 seconds ... ;)
    Using LineageOS 20, with the tweaked build.prop, and still having a unlock warning it'll boot in 20-30 seconds 😎!
    2
    The next target is to kill boot loader unlock warning as it adds to the time during this double boot.
    So cracking the process of getting this 'param' file is key
    I decided to measure the boot time from the off state. Total 1 minute 20 seconds. The unlocked bootloader splash screen for the first 10 seconds, then the Samsung Galaxy Tab A splash screen for 40 seconds. If the unlock splash screen is removed, the total time will decrease by 10 seconds to 1 minute 10 seconds ... ;)
    1
    My final question just before I drop the modded bootsamsungloop.qmg into system/media ( I have made a backup! ) is about file permissions. What should they be using Root Explorer ?
    My RootExplorer shows a different picture and a resolution of 0644.
    And the general rule is that the new file must have the same permission as the old one.
  • 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: