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

Search This thread

J.Michael

Recognized Contributor
Jan 20, 2018
1,815
2,060
Samsung Galaxy Tab A series
This occurred:-/

VVVVVVV

Here's the result, only syntax is the initial hello didn't have a capital H...would that matter?
View attachment 5845309

STOP THE PRESS!! I've got there (auto-start that on usb power that is ).
I jumped onto this thread @Post #212 and got schooled to a successful outcome.

So left on the list is trying to replace Samsung boot animations with VOLVO ones...and that damned annoying bootloader unlock warning...gawd I'm sick of seeing that!
In reverse order:

Congratulations. How you can navigate the process of unpacking/modifying/repacking a boot image, reassembling the initial ramdisk on the way, but you can't make a text file is beyond me.

The command to list files is "LS -L", except all lower case.
The point of the exercise was to demonstrate a way to create a text file. A second "echo" command, this time with a double greater-than (">>") would result in appending the second line to the existing file.
Since you've downloaded Notepad++ to your Windows machine, you are probably past caring.

I have no idea what to do with "VVVVVVVVV" (I didn't count).
 
  • Like
Reactions: ebod
STOP THE PRESS!! I've got there (auto-start that on usb power that is ).
I jumped onto this thread @Post #212 and got schooled to a successful outcome.

So left on the list is trying to replace Samsung boot animations with VOLVO ones...and that damned annoying bootloader unlock warning...gawd I'm sick of seeing that!
You can also speed up loading by adding a few lines to the build.prop file in /system. I've made a post about it like 1, 2 or 3 pages ago.
 
  • Like
Reactions: ebod
You can also speed up loading by adding a few lines to the build.prop file in /system. I've made a post about it like 1, 2 or 3 pages ago.
yep something worth coming back to. Right now although I have an auto-boot, it boots twice, i.e. once and the battery animation flicks on...then a second later it boots again onwards into system. 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
 

Talich52

Senior Member
Dec 24, 2010
476
249
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 ... ;)
 
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 😎!
 
Using LineageOS 20, with the tweaked build.prop, and still having a unlock warning it'll boot in 20-30 seconds 😎!
Keeping it though, it works very nice. It has some exclusive features than from stock, also having a newer Android version. If LineageOS 21 releases for Android 14, I'll ask the developer from the official version to LineageOS 21, if it isn't yet from then. I saw that the version of LineageOS was first 19.1, as I saw a branch with it on the GitHub and also a LineageOS 20 branch.
 
Animation files when loaded at /system/media. 2 files - bootsamsung.qmg & bootsamsungloop.qmg. Can be replaced via TWRP.
I've been exploring this logo action today and using the downloaded Samsung Theme creator tool I've managed to create what I 'hope' will be a Volvo looping image. Its set at 1280x800 and aimed to run in landscape on a car dash.
I've followed this old guide but its pics have long gone

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 ?
1677431067931.png


A YT vid mentions '644' ?
1677431171726.png



ezgif.com-optimize.gif
 

Talich52

Senior Member
Dec 24, 2010
476
249
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.
 

Attachments

  • Screenshot_20230226-204230_Root Explorer.jpg
    Screenshot_20230226-204230_Root Explorer.jpg
    217.2 KB · Views: 7
  • Like
Reactions: J.Michael
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.
yey it did work without bricking the device ( rw-r-r- 0644 ). Only issue is its a squashed animation as I got the 1280x800 wrong, primarily I think it needed to be 800x1280 with the logo indexed round 90degrees to suit landscape viewing
But the method is proven, I just need to try again and once the animation loop file is correct...then do similar for the static boot/shutdown images.
 
yey it did work without bricking the device ( rw-r-r- 0644 ). Only issue is its a squashed animation as I got the 1280x800 wrong, primarily I think it needed to be 800x1280 with the logo indexed round 90degrees to suit landscape viewing
But the method is proven, I just need to try again and once the animation loop file is correct...then do similar for the static boot/shutdown images.
And? Did you still do some stuff?
 

doniedogawa

Member
Oct 29, 2021
46
3
Indonesia
Hello, i just bought used T295 XID (indonesian version) with android 11 WC1 firmware and it's already bootloader unlocked. Can I install magisk without TWRP with this method?
 
Last edited:
Hello, i just bought used T295 XID (indonesian version) with android 11 WC1 firmware and it's already bootloader unlocked. Can I install magisk without TWRP with this method?
Sadly, no, not anymore. Your bootloader version must be 3, which is 4. Version 4 does not allow ANY custom stuff anymore. The bootloader cannot be downgraded, for now.
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,815
2,060
Samsung Galaxy Tab A series
So, I can't flash the OS back to 9 or 10?
You can probably flash the OS back to 9 or 10. What you cannot do is reduce the version number of the bootloader.

I do not know whether flashing the version 3 bootloader (BL.tar file) results in successfully flashing and then having the tablet refuse to boot; or if the flashing phase results in failing to flash.

I am pretty sure people in this thread describe mixing and matching .tar files, i.e., they run Odin and specify an AP.tar from one release and a BL.tar from another -- that's how some people update Android to 10 without updating the bootloader past v3.
 
So, I can't flash the OS back to 9 or 10?
You can probably flash the OS back to 9 or 10. What you cannot do is reduce the version number of the bootloader.

I do not know whether flashing the version 3 bootloader (BL.tar file) results in successfully flashing and then having the tablet refuse to boot; or if the flashing phase results in failing to flash.

I am pretty sure people in this thread describe mixing and matching .tar files, i.e., they run Odin and specify an AP.tar from one release and a BL.tar from another -- that's how some people update Android to 10 without updating the bootloader past v3.
It might indeed be possible to lower the OS. I thought when you try to flash a lower bootloader, it just fails to flash it.
 
  • Like
Reactions: J.Michael

Talich52

Senior Member
Dec 24, 2010
476
249
Hello, i just bought used T295 XID (indonesian version) with android 11 WC1 firmware and it's already bootloader unlocked. Can I install magisk without TWRP with this method?
 

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: