I went past the secure check fail: vk this time, device shut down and I held on to pwr+vol up but now I get a secure check fail: recovery. That's all I get.
Also, I am no longer able to boot the device, is it bricked?
[rom] [twrp] sm-t290 & sm-t295 [discussions & help thread]
- Thread starter secretwolf98
- Start date
Also, I am no longer able to boot the device, is it bricked?
Yes, it's blocked by the bootloader. You need to return the stock recovery and then the device will boot ...
If you are able to restore by flashing stock AP, BL, CP, CSC_HOME with Odin
Why not try patching AP with Magisk, flash that (with other 3 files), and see if you can get Magisk installed?
What's Magisk? Could you explain a bit more briefly, I'm completely new to all this.
I'm sorry, maybe I should not have intruded.
What are you trying to do? Why are you trying to do it?
I was trying to install LineageOS on my LTE Galaxy Tab A 8.0 (2019), and found a guide that dealt with the non-LTE version of my device. As I followed the guide I tried with Magendanz's TWRP 3.6.1 but it wouldn't work. Then I tried the solutions suggested by Volatyle and Talich52 to no avail. After research since my last post I now know I can't install any custom ROM onto my device because I have v4 bootloader. So my only choice as of now is to go back to official firmware.
I recommend installing the latest firmware for China for the T295C model (T295CZCU4CVF2_CHC_20220627160010). Install only AP & HOME_CSC files directly on the current firmware, but the bootloader must be unlocked. The firmware for China is much lighter and works faster
Thanks, but I'm not going to re-install and re-login everything for the 4th time XDI recommend installing the latest firmware for China for the T295C model (T295CZCU4CVF2_CHC_20220627160010). Install only AP & HOME_CSC files directly on the current firmware, but the bootloader must be unlocked. The firmware for China is much lighter and works faster
I bought this second hand just to read books and manga, so I won't mind the lag too much. I'll visit every once in a while to see if v4 is cracked so I'll refrain from updating my device for now.
You don't understand! Installing the AP part and most importantly HOME_CSC will save all the data, even Google Play will remain, which is initially absent in the Chinese firmware, but can be added. Many applications in the firmware are installed as custom(users) and are easily removed, others are normally disabled...
I see. I've already removed most of the bloatware and had the rest disabled. These are all the apps I have right now, minus the phone, contacts and messages apps and Galaxy store because they're hidden. Galaxy store was the only one that I couldn't get rid of.
Will installing the Chinese ROM be even better than this?
Considering the specific use of the device and the optimization done, probably the Chinese firmware will not be the best. By the way, Google Play is not initially available in the Chinese firmware, but it can be installed...
Then I'll pass. Android 11 is plenty new enough that I can install the apps I need for the next three or four years atleast, and hopefully by then v4 will be jailbroken and I'll be able to extend it's life a little more.
Or maybe I'll sell it off after uni who knows XD
I might get a nicer tablet later on, this one I got for dirt cheap because I'm strapped for cash right now. Thanks for all the support.
Hi secretwolf98:
I've got the SM-T295, too.
Can you please help me to install twrp, too?
I've got the SM-T295, too.
I would like to interject: I tried this previously, this resulted in a device that would only boot to a green screen with red warning text, "Only official binaries are allowed".
If you have the same bootloader version as @HyruleanKnight then I think @Talich52 said there is no way to run anything that is not signed with an approved key.
I've lost track, are you able to use LOS?
Who do we sue over the stupidity of "sure, you can unlock the bootloader, but that just means we'll let you write unapproved binaries to the device, we still won't let them run"?
Lol. Maybe they just don't care that much about severely neutered devices like the A's.
I would like to point out that while I didn't succeed after patching the AP image with Magisk, I have been able to successfully flash TWRP (and subsequently been able to install LineageOS). It just has to be done immediately after a whole flash; if the device is allowed to boot to system, any subsequent attempts to flash TWRP will result in /recovery being "auto-repaired". IIRC, I got the "official binaries" screen while I was attempting to somehow attain root, probably because I had forgotten the above requirement. So, it remains possible- although I haven't verified this - that as long as a Magisk patched AP binary is flashed either initially during a whole flash, or immediately after, it could be successful.
The John Wu installation instructions called for *not* letting the device reboot after Odin finished, but instead forcing a boot to recovery to wipe data. This was assuming Magisk was installed in recovery. Maybe the underlying principle is that you have to follow this (sub)procedure if you are modifying recovery.
I'm still confused: I thought @Talich52 said it was not possible to run altered software with bootloader v4.
What is the current state of installing Magisk? Do you still patch recovery? So people with TWRP are using Magisk to patch TWRP?
Where exactly did you see that? I must have missed it. The instructions are somewhat confusing for someone like me who doesn't know what category a particular device falls under.
This is what I've done:
- Flash latest firmware. Force reboot to download mode.
- Flash TWRP in AP using Odin. Force boot to recovery (hold volume up) to boot into TWRP.
- Wipe data. Flash multidisabler. Command reboot to recovery via TWRP reboot menu.
- Flash Magisk in TWRP. Reboot to system.
- Have rooted device.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4
If you have issues with posts in this thread, use the Report button. The only problems I've seen thus far have been your posts - you're rude, demanding, and abrasive. Perhaps you should take a moment to familiarize yourself with the Forum Rules linked in my signature before you continue posting in such a manner.3Is a TWRP root version of this being worked on? Having TWRP would be great as it provides a lot of great features.
I was able to root my SM-T290 using Magisk Manager and a collection of random instructions from different parts of the internet.
The purpose of rooting my device was to operate Kali Nethunter and its modules in which root access is needed.
I wanted to provide the steps I took to root my device. Disclaimer: PROCEED AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE OR DONT KNOW HOW TO RECOVER FROM A SOFT BRICK.
I do not take credit for this, I am simply aggregating what I found during my experience of trying to root my device.
Furthermore, at the time of writing, doing all the steps will have your ctsProfile set to false, which I believe means you can't do certain banking functions, etc. I've tried numerous guides online to attempt to fix it, but none have worked. They all just unroot the device and I have to do a quick root with Odin since I saved the files from all the steps.
Needed Items:
- Cable to connect SM-T290 to PC
- microSD card
- Ability to connect microSD card to a PC
- Paperclip or pinhole stick to open slot on SM-T290
- Linux (VM is not needed if you don't have one. You can use the Windows Linux Subsystem & obtain Ubtunu from Microsoft Store)
- Stock Firmware
DRIVERS
Install the drivers for your device on your computer. You can google this or connect it to the computer and let it install them on its own.
UNLOCK BOOTLOADER & USB DEBUGGING
Before you can do this, you need to enable developer options.
1) Go to Settings
2) Go to About tablet
3) Go to Software Information
4) Click on Build Number repeatedly. You will see a message at the bottom saying X amounts of taps remaining to enable it
5) Go back to Settings
6) At the bottom, you'll see Developer options, click it
7) Locate OEM Unlocking and enable it. Accept the warning is given, if it is shown
8) Scroll down and locate USB debugging and enable it
You've now enabled OEM Unlock & USB debugging.
9) Turn off the device.
10) Connect the USB cable to the computer. Do not connect it to the device yet
11) Press and hold the Up & Down volume buttons at the same time
12) While holding them down, connect the other end of the USB cable to the device
13) A warning screen should show up prompting about the risk of unlocking the bootloader
14) Press and hold (Long Press) the Up Volume button
Your bootloader should now be unlocked. You can confirm if this is the case as every time you boot the device, you'll receive a bootloader warning.
Download Stock Firmware
You need a copy of your stock firmware. First, you need to look up what version you are using.
1) Go to Settings
2) Go to About tablet
3) Go to Software information
4) Find Build Number and write down the portion after the bulk of numbers, ie. T290XXS3ATC2
5) Go to <I can't enter a URL since I don't have 10+ posts>. Google SFirmware Samsung SM-T290 (I do not own this site nor do I know how the firmware is obtained. Due to this, I don't store anything personal on the rooted tablet)
6) Find the build number matching your tablet and its country
7) Download the files to your computer
File Modification Needed Towards Root
1) Unzip the file downloaded
2) On your Linux VM or Linux Sub-Windows System, go to the folder where the extracted files are at
3) Find the AP*.tar.md5 file
4) Extract its contents using the following command: tar -xvf <filename>
5) Decompress the following files from the extracted AP tar file: boot.img.lz4, recovery.img.lz4, and vbmeta.img.lz4, using the following command: unlz4 <files>
6) Add the newly decompressed files from the last step into a new tar file, using the following command: tar -cvf pre-processed.tar <files>
7) Copy the newly created tar file named pre-processed.tar onto a microSD card
8) Insert the microSD card into the tablet
9) Using Files, copy pre-processed.tar from the microSD card to the Downloads folder on the Internal Storage. (This step may be optional, but I did this anyway).
10) Install Magisk Manager on the tablet. The software can be found here: <I can't enter a URL since I don't have 10+ posts> Google Magisk Manager
11) Open Magisk Manager
12) You will see it says Magisk is not installed, to the right there is an Install button, click it.
13) You will be prompted if you want to install it now, click Install.
14) Navigate to the pre-processed.tar file in Downloads and let it do its thing.
15) It will process and say it generated a new file, which can be found in the Downloads folder called something like magisk-patched.rar
16) Copy that file back to the microSD card
17) Copy that file to your computer
18) Extract its contents using the following command: tar -xvf post-processed.tar
19) Go into the new directory containing the extracted content and be sure to add post_ in front of each file there
20) Copy the files to the AP folder which you created the pre-processed.tar files from.
21) For post_boot.img and post_recovery.img (not post_vbmeta.img), perform the following command in Linux for each:22) Delete the post_boot.img file to prevent any confusionCode:dd conv=notrunc if=<POST_PROCESSED_EXTRACTED_*.img_FILE> of=<PRE_PROCESSED_EXTRACTED_*.img_FILE>
23) Delete the post_recovery.img file to prevent any confusion
24) Delete the vbmeta.img (original) file. Find post_vbmeta.img and rename to vbmeta.img
25) Create new AP tar file with all original extracted files in the AP folder, except replace the following:
Code:boot.img.lz4 -> boot.img (of= file from last step) recovery.img.lz4 -> recovery.img (of= file from last step) vbmeta.img.lz4 -> vbmeta.img (from post-processed.tar generated by Magisk)
Remember the command to create a .tar file is tar -cvf AP-Patched.tar <files>
Odin & Root
1) Download Odin if you don't have it already have it from <I can't enter a URL since I don't have 10+ posts> Google Odin3
2) Boot your tablet into download mode. (Device Powered Off -> Power + Up Volume -> Recovery Mode -> Download Mode)
3) Connect your tablet to your computer
4) Open Odin and load the files one by one from the downloaded stock firmware. The only difference should be the AP file which should be the newly created AP-Patched.tar file.
5) Start it & let Odin do its thing.
6) Once it's done and the device has restarted, you can check Magisk Manager.
7) If you see Magisk is up to date with a checkmark, congratulations, you now have root access.
Hope this helps folks out as I spent about 2-3 days trying to figure everything out.3
Turn off tablet.
Connect usb cable to PC, but NOT to tablet.
Press vol up + vol dn keys and hold them down.
Insert usb cable into table while holding down keys.
You should see a screen with text on it. Release keys.
Follow directions on screen.2Here is a TWRP test build for the SM-T290 model only:
Please test this out and give me feedback. Thank you!
https://github.com/secretwolf98/project/releases/download/vTWRPb1t1/twrp.tar2
Actually, my T295 has a fastboot option. I discovered it by accident. I modified the system.img file (new bootani*.qmg files). But, it would not boot. I got an error msg. When I did the vol up + vol dn + pwr keys, I ended up in a menu that showed a fastboot selection. I tried selecting it, but since my system.img would not boot, I could not get into it. Nor could I get into recovery, etc. So, I selected power down. After tablet was off, I could get into download mode.
New posts
-
-
-
-
[APP][XPOSED][8.1-12x] GPS Setter - Set Device Location
- Latest: supermansaga