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

Search This thread
Look at this 2 threads:
1. https://forum.xda-developers.com/t/get-param-bin-file-samsung.3782066/ (FIRST)
2. https://forum.xda-developers.com/t/guide-how-to-find-param-partition-block-samsung.3906650/ (Look at this one when told in first one)
You can try to extract the param file using this method. These commands can be run from the terminal in TWRP.
I understand getting a pc command prompt but not 100% sure what 'state' the device must be in when connected to the PC. i.e. must it be in download mode or TWRP ? or just standard active running mode? Do you just suggest abandoning the pc access and try via TWRP alone ?
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,815
2,060
Samsung Galaxy Tab A series
ebod said:
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
I think you are wasting your time trying to eliminate the nag screen before you address the real issue.

Getting the tablet to automatically boot when power is applied is going to involve manipulating the filesystem. I don't think you're going to be able to just remount /system and edit something. That thread @Minionguyjpro found talks about unpacking the boot image and modifying it's ramdisk and repacking the boot image. That's a lot of steps where something can go wrong.

If you decide to live with having to push a button to boot the tablet, you will probably find that waiting for the nag screen to time-out is not such a big deal.

And it probably takes a lot of work to make the tablet shut down when you turn off the car. So, unless you go a long time without using the car, the tablet is already booted. At worst, you need to get past the lock screen. I haven't seen anyone talk about that. Maybe you just disable it in Android Settings.
 
I think you are wasting your time trying to eliminate the nag screen before you address the real issue.

Getting the tablet to automatically boot when power is applied is going to involve manipulating the filesystem. I don't think you're going to be able to just remount /system and edit something. That thread @Minionguyjpro found talks about unpacking the boot image and modifying it's ramdisk and repacking the boot image. That's a lot of steps where something can go wrong.

If you decide to live with having to push a button to boot the tablet, you will probably find that waiting for the nag screen to time-out is not such a big deal.

And it probably takes a lot of work to make the tablet shut down when you turn off the car. So, unless you go a long time without using the car, the tablet is already booted. At worst, you need to get past the lock screen. I haven't seen anyone talk about that. Maybe you just disable it in Android Settings.
And that, and it goes automatically further, even though no one presses it.
 
I understand getting a pc command prompt but not 100% sure what 'state' the device must be in when connected to the PC. i.e. must it be in download mode or TWRP ? or just standard active running mode? Do you just suggest abandoning the pc access and try via TWRP alone ?
It can be either in TWRP or in the normal mode, as long as ADB/USB debugging is enabled, I think.
 
It can be either in TWRP or in the normal mode, as long as ADB/USB debugging is enabled, I think.
tried both and no success either way, I selected a Samsung as a car based tablet because I genuinely thought it would be the most supported device brand to configure. Seriously concluding why do I bother as nothing is straighforward. It would less stress just listening to crackly FM radio as can't see me getting this device to behave like a car head unit. I've successfully got a stock LG G5 phone running as a car based unit that switches on/off etc without my input. Only problem with that is its too small screen'wise

Like they have Apple stores in all major cities, kinda wish I could take in this tablet to a Samsung store and get an in-store expert make it car friendly :-/
 

tamtc84

Member
Jul 9, 2018
5
2
You can roll back to android 9, but with version 3 of the loader, say T290XXS3ATF1 . Alternatively, on the current full firmware of android 11, just look at how charging works when the device is turned off.Then flash the bootloader from android 9 aboot_vbmeta_T290XXS3ATF1.tar and compare the picture when charging. You don't need to root, just see the root of the problem...
I never turn off the device, so I don't see a problem when charging...
I upgrade A8 T295 from T295XXS3ATB2_T295OLM3ATB2_XEV_9.0 to T295XXS5CWA1 by Odin. Success to upgrade.
When i want to rollback to T295XXS3ATB2, i received message: "sw rev check fail fused 5 binary 3".

How do I do to rollback to T295XXS3ATB2? or setup T295XXS3ATB2 again to root with Magisk?

Many thank.
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,815
2,060
Samsung Galaxy Tab A series
I upgrade A8 T295 from T295XXS3ATB2_T295OLM3ATB2_XEV_9.0 to T295XXS5CWA1 by Odin. Success to upgrade.
When i want to rollback to T295XXS3ATB2, i received message: "sw rev check fail fused 5 binary 3".

How do I do to rollback to T295XXS3ATB2? or setup T295XXS3ATB2 again to root with Magisk?

Many thank.
You don't. Not without more control than anyone we know has. They don't want you to be able to roll back. They seem to have done a good enough job, you cannot roll back.
 
  • Like
Reactions: Talich52

J.Michael

Recognized Contributor
Jan 20, 2018
1,815
2,060
Samsung Galaxy Tab A series
Can i use another combination firmware to reset fused. After that flash again with T292XXS3ATB2?
Still no. Just throwing their software against their gatekeeper is not going to bypass their "protection".

Where did you get "sw rev check fail"?

If in download mode, when you used Odin, and you could then boot to Android, then they didn't even let you write the unapproved software. You would need some secret super-Odin, or you would need to open the box and place probes in the right place to rewrite PROM, to force your choice of software back onto the device.

If you get the failure when trying to boot Android, and you have to use Odin to restore the approved bootloader, and you are able to use Odin to restore the approved bootloader, and then you can boot, then there is a software solution. But you would probably have to crack their signing protocol to create a bootloader that claims to be the right revision, and yet allows you to do what you want. I think you could solve the challenge of burning a PROM more easily than you could crack Samsung's encryption.
 

tamtc84

Member
Jul 9, 2018
5
2
Still no. Just throwing their software against their gatekeeper is not going to bypass their "protection".

Where did you get "sw rev check fail"?

If in download mode, when you used Odin, and you could then boot to Android, then they didn't even let you write the unapproved software. You would need some secret super-Odin, or you would need to open the box and place probes in the right place to rewrite PROM, to force your choice of software back onto the device.

If you get the failure when trying to boot Android, and you have to use Odin to restore the approved bootloader, and you are able to use Odin to restore the approved bootloader, and then you can boot, then there is a software solution. But you would probably have to crack their signing protocol to create a bootloader that claims to be the right revision, and yet allows you to do what you want. I think you could solve the challenge of burning a PROM more easily than you could crack Samsung's encryption.
In download mode, when i use Odin with S3 rom, i received "sw rev check fail fused 5 binary 3".
I will research more.
Many thank you.
 
  • Like
Reactions: J.Michael
I upgrade A8 T295 from T295XXS3ATB2_T295OLM3ATB2_XEV_9.0 to T295XXS5CWA1 by Odin. Success to upgrade.
When i want to rollback to T295XXS3ATB2, i received message: "sw rev check fail fused 5 binary 3".

How do I do to rollback to T295XXS3ATB2? or setup T295XXS3ATB2 again to root with Magisk?

Many thank.
You should be able to downgrade your firmware, but it requires wipe of a few things. Actually l, I heard from multiple sources it was possible.
 
  • Like
Reactions: J.Michael
tried both and no success either way, I selected a Samsung as a car based tablet because I genuinely thought it would be the most supported device brand to configure. Seriously concluding why do I bother as nothing is straighforward. It would less stress just listening to crackly FM radio as can't see me getting this device to behave like a car head unit. I've successfully got a stock LG G5 phone running as a car based unit that switches on/off etc without my input. Only problem with that is its too small screen'wise

Like they have Apple stores in all major cities, kinda wish I could take in this tablet to a Samsung store and get an in-store expert make it car friendly :-/
What exactly goes wrong at the installation of the auto boot part? Let's include a screenshot where possible, and some text???
 
  • Like
Reactions: J.Michael
tried both and no success either way, I selected a Samsung as a car based tablet because I genuinely thought it would be the most supported device brand to configure. Seriously concluding why do I bother as nothing is straighforward. It would less stress just listening to crackly FM radio as can't see me getting this device to behave like a car head unit. I've successfully got a stock LG G5 phone running as a car based unit that switches on/off etc without my input. Only problem with that is its too small screen'wise

Like they have Apple stores in all major cities, kinda wish I could take in this tablet to a Samsung store and get an in-store expert make it car friendly :-/
We'll get atleast a few things to work, I'm very sure about that.
 
Please tell me how to do it.
Current, i still search to do it but it still error.
You could try to flash the latest TWRP if it works and then try to flash the firmware. By the way, it may not be possible to downgrade, but you may be able to downgrade to another firmware with the same binary version? And also, why are you downgrading?
 
  • Like
Reactions: tamtc84

Talich52

Senior Member
Dec 24, 2010
476
249
Please tell me how to do it.
Current, i still search to do it but it still error.
Do not torment the device and do not suffer yourself - Google & Samsung forbade downgrading the bootloader version, that is, with version 4 or 5, do not install version 3. In addition, bootloaders 4 and 5, even unlocked, do not allow you to install any custom files, such as a patched kernel or recovery TWRP. All questions to Samsung, but support for the device is over by the manufacturer...
 
I think you are wasting your time trying to eliminate the nag screen before you address the real issue.

Getting the tablet to automatically boot when power is applied is going to involve manipulating the filesystem. I don't think you're going to be able to just remount /system and edit something. That thread @Minionguyjpro found talks about unpacking the boot image and modifying it's ramdisk and repacking the boot image. That's a lot of steps where something can go wrong.

If you decide to live with having to push a button to boot the tablet, you will probably find that waiting for the nag screen to time-out is not such a big deal.

And it probably takes a lot of work to make the tablet shut down when you turn off the car. So, unless you go a long time without using the car, the tablet is already booted. At worst, you need to get past the lock screen. I haven't seen anyone talk about that. Maybe you just disable it in Android Settings.
I feel I've got further with a stock non-root LG G5 than I'll ever get with this SM-T295. That device literally starts on demand ( no bootlock warnings ) and auto shutdowns ( with help from Tasker /Autoinput ). I was just expecting once I got this unit rooted, it would be all just plain sailing. Its been anything but...
I have root, and I have the Magisk app on my device asking to let it update itself. However last time I tried it bombed out and I had to go back to square one.
I'll live with a stock Android 10 rom, in reality the device will just spend most of its life running Vivid launcher. So I just want to achieve a non-intervention turnkey startup in usb power as fast as is practical...preferably without the bootlock warning. I hoped this was a simple request that ANY novice could follow given clear enough instruction, but so far its been a combination of me being too dumb and nobody giving me a straightforward enough path to follow..
 
Last edited:
I feel I've got further with a stock non-root LG G5 than I'll ever get with this SM-T295. That device literally starts on demand ( no bootlock warnings ) and auto shutdowns ( with help from Tasker /Autoinput ). I was just expecting once I got this unit rooted, it would be all just plain sailing. Its been anything but...
I have root, and I have the Magisk app on my device asking to let it update itself. However last time I tried it bombed out and I had to go back to square one.
I'll live with a stock Android 10 rom, in reality the device will just spend most of its life running Vivid launcher. So I just want to achieve a non-intervention turnkey startup in usb power as fast as is practical...preferably without the bootlock warning. I hoped this was a simple request that ANY novice could follow given clear enough instruction, but so far its been a combination of me being too dumb and nobody giving me a straightforward enough path to follow..
I once saw a flashable TWRP zip, but I should not flash it as some people bricked their device with it, I thought.
 
I feel I've got further with a stock non-root LG G5 than I'll ever get with this SM-T295. That device literally starts on demand ( no bootlock warnings ) and auto shutdowns ( with help from Tasker /Autoinput ). I was just expecting once I got this unit rooted, it would be all just plain sailing. Its been anything but...
I have root, and I have the Magisk app on my device asking to let it update itself. However last time I tried it bombed out and I had to go back to square one.
I'll live with a stock Android 10 rom, in reality the device will just spend most of its life running Vivid launcher. So I just want to achieve a non-intervention turnkey startup in usb power as fast as is practical...preferably without the bootlock warning. I hoped this was a simple request that ANY novice could follow given clear enough instruction, but so far its been a combination of me being too dumb and nobody giving me a straightforward enough path to follow..
You could try to take a look at this:
 

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: