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

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

Search This thread

Talich52

Senior Member
Dec 24, 2010
347
171
I tried again today, fresh install -->setup -->connect server and also the 7-days backdated trick --KG still prenormal.
Guess I have to wait 7-days and hopefully oem unlock reappear.
It is advisable to change the region and install the firmware where the device did not have the KG Status: Prenormal line or there was Checking, then the blocking will be removed faster. I was removed immediately after installing the stock firmware ...
 

dragth

Member
Apr 16, 2017
27
1
th
It is advisable to change the region and install the firmware where the device did not have the KG Status: Prenormal line or there was Checking, then the blocking will be removed faster. I was removed immediately after installing the stock firmware ...
I can flash factory installed OS10 (SM-T295XXU3BUA5_Thailand) with Odin pass message but it wont boot (looping).

I can boot both OS10 (SM-T295XXU4BUD3_Vietnam) and OS11 (SM-T295XXU4CUF8_Mexico) --with modded BL_OS9 --but "oem unlock" blocking still there...

I think user @Viggen66 is also having this problem.
 

Attachments

  • Screenshot_20211014-203403[1].jpg
    Screenshot_20211014-203403[1].jpg
    101.8 KB · Views: 34
  • Screenshot_20211014-203417[1].jpg
    Screenshot_20211014-203417[1].jpg
    102.4 KB · Views: 32
  • Screenshot_20211014-203434[1].jpg
    Screenshot_20211014-203434[1].jpg
    89.9 KB · Views: 24
  • Screenshot_20211014-203445[1].jpg
    Screenshot_20211014-203445[1].jpg
    108.9 KB · Views: 20
  • Screenshot_20211014-203456[1].jpg
    Screenshot_20211014-203456[1].jpg
    139.2 KB · Views: 20
  • Screenshot_20211014-203600_Software_update[1].jpg
    Screenshot_20211014-203600_Software_update[1].jpg
    48.6 KB · Views: 21
  • Screenshot_20211014-203617_Settings[1].jpg
    Screenshot_20211014-203617_Settings[1].jpg
    122.8 KB · Views: 32

Talich52

Senior Member
Dec 24, 2010
347
171
I can flash factory installed OS10 (SM-T295XXU3BUA5_Thailand) with Odin pass message but it wont boot (looping).
The current version of the modem is 4 (Baseband). If you install the full firmware with 3 bootloader, the device will not boot due to the downgrade of the modem version ...
If you flash the modem version 4, then the device will boot. Thus, a complete rollback cannot be done ...
 

dragth

Member
Apr 16, 2017
27
1
th
N.B.- The most irritating part about Samsung is that you must have cellular connectivity after first boot to allow the device to be registered on Samsung servers. Otherwise, it will show KG status: Prenormal in download mode.
Have spent a whole day reading/trying w/out success.
Thanks, already tried that (cellular connection trick) too before requesting help here.

I have read a few users with these 2021-produced device (myself included) having same KG blocking issue (aka anti-theft protection) and so the data connectivity to server seems logical to me for T295.
?? Maybe Y2021 devices have stricter protocols...

Next, I will reinstall latest firmware according to my CSC, insert SIM and wait out the 7-days period and hope...
 

Talich52

Senior Member
Dec 24, 2010
347
171
Hello, has anybody a compiled or can compile an OS9 BL for T295XXU4CUF8 ?
Here you go :)
The modification consists in replacing the aboot & vaultkeeper files with the files from the BL part of the 9 android.
Unpack the zip archive to tar before use.
 

Attachments

  • BL_T295XXU4CUF8_OS9.tar.zip
    18.8 MB · Views: 6
  • Like
Reactions: J.Michael

erSSe

Member
Oct 24, 2021
5
0
Here you go :)
The modification consists in replacing the aboot & vaultkeeper files with the files from the BL part of the 9 android.
Unpack the zip archive to tar before use.
Thank you so much buddy for the fast reply. This week will give a try. One of them is on BL 4 already. Not sure if the downgrade going to work.
 

Talich52

Senior Member
Dec 24, 2010
347
171
Just to update that after 260hrs (no reboot) --the kg status is still prenormal.
Firmware tested was OS11 (SM-T295XXS4CUG4_OLM).
These are wrong actions. To change the Prenormal status, you need to connect to the Samsung server, for this you should request a regular update and reboot the device. You cannot reset the data, otherwise the time counter will be reset ...
 

Talich52

Senior Member
Dec 24, 2010
347
171
I will try to update... thanks.
The issue is not about the update, it is better to disable the update. When checking for an available update, the device connects to the Samsung server and this is what is important :)
P.S. If after 7 days there is no result, then you can reset the data. At the first request for updates, the device is registered on the Samsung server and the counter starts counting 7 days, sometimes up to 10 ...
There is also a way to change the date 7 days ago with checking for updates and returning the current date, also checking for updates ...
 
Last edited:

dragth

Member
Apr 16, 2017
27
1
th
I downgraded OS (11 to 10).
Changed CSC (OLM to OXM).
Now I have "update available" from Samsung server.
OEM unlock still missing...
 

Leugadong

Member
Nov 7, 2021
5
0
hi I need help please...
I followed all the instructions, got root with TWRP 3.4.0.1+vbmeta t295 and magisk v.20.4 installed on my samsung T295XXS3ATB2.
But i have no idea why my wifi and bluetooth can't turn on. Am I did something bad, i cant figured it out. please help.
@Talich52 @gcrutchr @Tianhe
tried to flash back stock firmware with odin, but no luck. wifi still won't turn on.

Flashed with
Odin 3.14
TWRP 3.4.01
Multi Disabler 3.1
 

Talich52

Senior Member
Dec 24, 2010
347
171
hi I need help please...
I followed all the instructions, got root with TWRP 3.4.0.1+vbmeta t295 and magisk v.20.4 installed on my samsung T295XXS3ATB2.
But i have no idea why my wifi and bluetooth can't turn on. Am I did something bad, i cant figured it out. please help.
@Talich52 @gcrutchr @Tianhe
tried to flash back stock firmware with odin, but no luck. wifi still won't turn on.

Flashed with
Odin 3.14
TWRP 3.4.01
Multi Disabler 3.1
Flash the original stock firmware with the CSC part, not HOME_CSC, that is, with data reset. Wi-Fi should work. If the rooting was a file installation, but for a different firmware, then Wi-Fi will not work.Therefore, it is better to root through TWRP.
 

Leugadong

Member
Nov 7, 2021
5
0
Flash the original stock firmware with the CSC part, not HOME_CSC, that is, with data reset. Wi-Fi should work. If the rooting was a file installation, but for a different firmware, then Wi-Fi will not work.Therefore, it is better to root through TWRP.
Yes, i did tried flash the original stock firmware
put on BL, AP, CP and CSC and its passed without an error, just the wifi and bluetooth not working now.
Im sory what does this mean "If the rooting was a file installation, but for a different firmware" ?
I just followed all the instructions, or maybe I did something else on this part
13. You will then format (NOT WIPE) data. Answer yes to the format prompt
that caused this error.
 

Leugadong

Member
Nov 7, 2021
5
0
@Talich52 I just mentioned that you said with data reset. Does that mean I have to push this Reset button?
Screenshot 2021-11-07 150243.jpg

Because I just push Start button all the times im flashing.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    mine is aindroid 11, so there is no way to install twrp?
    The problem is not in android 11, but in the 4 version of the loader and now the loader of version 3 of android 9 cannot be installed.And the protection in Android loaders 10 and 11 is enhanced and does not allow you to install either a custom kernel or a custom TWRP recovery.
    1
    IS THERE A TWRP FOR VERSION T295XXU4CUF8?
    TWRP version does not depend on current firmware, just find and install TWRP for T295 model.
    However, the current bootloader version 4 will not allow the device to start and TWRP. This can only be done with android 9 bootloader, but it cannot be installed as version only 3, below ...
  • 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: