[rom] [twrp] sm-t290 & sm-t295 [discussions & help thread]

Search This thread
By:
Advanced…
J

J.Michael

Recognized Contributor
Jan 20, 2018
1,816
2,064
Samsung Galaxy Tab A series
V0latyle said:
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:
  1. Flash latest firmware. Force reboot to download mode.
  2. Flash TWRP in AP using Odin. Force boot to recovery (hold volume up) to boot into TWRP.
  3. Wipe data. Flash multidisabler. Command reboot to recovery via TWRP reboot menu.
  4. Flash Magisk in TWRP. Reboot to system.
  5. Have rooted device.
Click to expand...
Click to collapse
Admittedly, those instructions need to be read in a spiral.

I just looked at them again and do not see what I remembered: they say "will reboot automatically", I remember something saying it's important to make sure go from Odin to recovery with no intervening boot of Android (regular Android, not the stripped down thing they use for recovery).

From your description, what you did is what I thought it should be, as long as we equate TWRP with recovery.

Now, if @HyruleanKnight can reproduce your steps...
 
  • Like
Reactions: barpasc and V0latyle
barpasc

barpasc

Member
Jul 27, 2022
8
0
Hi,

I'm also on T295 U4. Can I apply the steps mentionned in this thread to install TWRP?

Quick summary below as per my understanding:

1.PLug device to Odin and start flashing
I understand the crucial part is to not let device reboot automatically after flashihg TWRP in AP using Odin. Does this mean to manually grap the device and reboot it just right after Odin logs display ok or pass green?

2.Flash multidisabler. What is multidisabler and to download it?
3.Then same, reboot to recovery and flash Magidisk (for root access?)

Any risks to soft or hard brick with steps above?
 
J

J.Michael

Recognized Contributor
Jan 20, 2018
1,816
2,064
Samsung Galaxy Tab A series
barpasc said:
Hi,

I'm also on T295 U4. Can I apply the steps mentionned in this thread to install TWRP?

Quick summary below as per my understanding:

1.PLug device to Odin and start flashing
I understand the crucial part is to not let device reboot automatically after flashihg TWRP in AP using Odin. Does this mean to manually grap the device and reboot it just right after Odin logs display ok or pass green?

2.Flash multidisabler. What is multidisabler and to download it?
3.Then same, reboot to recovery and flash Magidisk (for root access?)

Any risks to soft or hard brick with steps above?
Click to expand...
Click to collapse
1. Odin has a checkbox "Automatically reboot". I remember unchecking it. I think sometimes my tablet rebooted automatically anyway. It doesn't matter so much. The point os to pay attention, there is a clear sign that the tablet is rebooting, mash the appropriate buttons to get it to boot to recovery. If the normal Android logo shows up, shut down the tablet and start over -- back to download mode and run Odin again.

2. Search this thread. Someone will say where to look.

3. I would go back and forth between TWRP and Android a few times to make sure it worked, and to savor the victory. Don't waste time setting up the Android -- something could still go wrong, and you will have to wipe data again.

Certainly risks. Soft brick constantly. Hard brick possible.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
barpasc said:
Hi,

I'm also on T295 U4. Can I apply the steps mentionned in this thread to install TWRP?

Quick summary below as per my understanding:

1.PLug device to Odin and start flashing
I understand the crucial part is to not let device reboot automatically after flashihg TWRP in AP using Odin. Does this mean to manually grap the device and reboot it just right after Odin logs display ok or pass green?
Click to expand...
Click to collapse
Not quite. When flashing factory firmware in Odin, DO NOT allow the device to boot to Android. This means that as soon as Odin finishes and the device reboots, hold Volume Up to boot into recovery. Then, using the volume buttons, select Reboot to bootloader. Reset Odin and flash TWRP in the AP slot. Again, hold Volume Up while rebooting to force device to boot into TWRP.

The device will flash a "Unlocked Bootloader" warning at you. Click Power to continue, then hold Volume Up immediately.
barpasc said:
2.Flash multidisabler. What is multidisabler and to download it?
Click to expand...
Click to collapse
Try this...then read Rule #1 of the Forum Rules linked in my signature.
The XDA thread describes exactly what it does. In a nutshell, it disables encryption so that TWRP can "see" your file/folder structure properly.
barpasc said:
3.Then same, reboot to recovery and flash Magidisk (for root access?)
Click to expand...
Click to collapse
Yes. However, if you're flashing a custom ROM, you'll need to wipe /system. Many custom ROMs come pre-rooted, such as the LineageOS GSI images.
barpasc said:
Any risks to soft or hard brick with steps above?
Click to expand...
Click to collapse
Slim to none. Ensure you're flashing the right files in the right slots in Odin. Don't flash anything in the Userdata slot - just BL, AP, CP, and CSC. If you use the CSC file, it will factory reset the device. HOME_CSC preserves user data. Keep in mind that a data wipe is required for Multidisabler to work correctly.
J.Michael said:
1. Odin has a checkbox "Automatically reboot"
Click to expand...
Click to collapse
Odin 3.14.1 does not.
 
  • Like
Reactions: barpasc
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
Played some more with the tablet. Updated to CVE1 and successfully flashed TWRP. I did run into a couple issues:
  • Flashing Magisk before flashing the Multidisabler resulted in a boot failure which required a whole flash to fix.
  • I'm not sure exactly what caused it, but at some point the device refused to accept the TWRP flash, with KG:PRENORMAL displayed. This was fixed by allowing it to boot to system and completing setup, then going back into download mode.
 
Last edited:
  • Like
Reactions: Deleted member 6405149 and barpasc
barpasc

barpasc

Member
Jul 27, 2022
8
0
thanks for replies

I'll give it a try when I have time to concentrate on steps. The idea behind using TWRP is to find out later if I can multiboot the T295 phone. I guess to do so stock recovery will not work and TWRP will allow some workaround to set multiboot.

I still use galaxy note 3 and android jelly bean with TWRP and safestrap. This allows me to have multiple roms each in an individual container or memory space or something like sandbox as I understand (I have little knowledge in this)

The multiboot I would like to do with T295, is to have a light rom (I saw a post where it says chinese rom requires less power and is good for battery but still with gps), and a rom with google play and 4g and maybe install lineage OS

Are these expectations way beyond what's possible to be done :rolleyes:? Or is it possible to have at least 2 roms (dual boot) from receovery?
 
T

Talich52

Senior Member
Dec 24, 2010
476
249
V0latyle said:
When flashing factory firmware in Odin, DO NOT allow the device to boot to Android. This means that as soon as Odin finishes and the device reboots, hold Volume Up to boot into recovery. Then, using the volume buttons, select Reboot to bootloader.
Click to expand...
Click to collapse
You can make everything easier :) . After uploading parts of the firmware, the device will start rebooting and the first thing a screen will appear with a warning about the unlocked bootloader - press any volume button - a menu will appear - select Recovery with the volume buttons - briefly press the Power button - the device will enter the firmware mode and you can upload the TWRP file.
This method is easier, because with an unlocked bootloader there is a difficulty in entering the recovery. I've been using this method for a long time...
 
Last edited:
  • Like
Reactions: J.Michael
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
barpasc said:
thanks for replies

I'll give it a try when I have time to concentrate on steps. The idea behind using TWRP is to find out later if I can multiboot the T295 phone. I guess to do so stock recovery will not work and TWRP will allow some workaround to set multiboot.

I still use galaxy note 3 and android jelly bean with TWRP and safestrap. This allows me to have multiple roms each in an individual container or memory space or something like sandbox as I understand (I have little knowledge in this)

The multiboot I would like to do with T295, is to have a light rom (I saw a post where it says chinese rom requires less power and is good for battery but still with gps), and a rom with google play and 4g and maybe install lineage OS

Are these expectations way beyond what's possible to be done :rolleyes:? Or is it possible to have at least 2 roms (dual boot) from receovery?
Click to expand...
Click to collapse
I doubt it. These tablets only have 32GB of storage.
Talich52 said:
You can make everything easier :) . After uploading parts of the firmware, the device will start rebooting and the first thing a screen will appear with a warning about the unlocked bootloader - press any volume button - a menu will appear - select Recovery with the volume buttons - briefly press the Power button - the device will enter the firmware mode and you can upload the TWRP file.
This method is easier, because with an unlocked bootloader there is a difficulty in entering the recovery. I've been using this method for a long time...
Click to expand...
Click to collapse
Good point.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
Talich52 said:
Thank you.
I will check the way to install TWRP, but not on 4 versions of the bootloader, but on 3 versions, but 10 android T295 ...
Initially, there was the same problem and just changed the bootloader to 9 android ...
Click to expand...
Click to collapse
I've been able to flash TWRP on CUK4, CVD3, and CVE1.
 
  • Like
Reactions: Deleted member 6405149 and J.Michael
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
barpasc said:
Galaxy note 3 runs also on 32 GB of internal storage memory so it should be possible to run multiple rom?
Click to expand...
Click to collapse
Maybe? I honestly don't know anything about multiple boot. I do know some devices, like the Pixel series, have A/B slots so it's technically possible to have multiple boot...but in practice, the slots are used for seamless OTA updates.
 
  • Like
Reactions: J.Michael
T

Talich52

Senior Member
Dec 24, 2010
476
249
V0latyle said:
I've been able to flash TWRP on CUK4, CVD3, and CVE1.
Click to expand...
Click to collapse
Is it on the T290 model ? by the way, the maximum version of the loader is 3 on it, but for the T295 model all the latest firmware with the 4 version of the loader. But there were problems with installing TWRP and on version 3 of android 10, I want to try out your method over the weekend... I will not check with version 4 yet, since there is no way to go back from 4 to 3...

So, I flashed T295XXU3BUA5_OLM_XEV_20210129194935 of course with the CSC part (no HOME_CSC), that is, with a data reset, since I rolled back from android 11 to 10. But the main thing is now the bootloader version 3, but already 10 android, with which I remind you also could not rut earlier device or even install TWRP. Without letting the device boot after uploading the firmware, I switched it to the firmware mode and uploaded the TWRP file. I tried to enter the recovery and I get the SECURE CHECK FAIL: recovery.img error and now do nothing until you return the stock recovery :(
 

Attachments

  • 20220730_172836.jpg
    20220730_172836.jpg
    896 KB · Views: 21
Last edited:
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
Talich52 said:
Is it on the T290 model ? by the way, the maximum version of the loader is 3 on it, but for the T295 model all the latest firmware with the 4 version of the loader. But there were problems with installing TWRP and on version 3 of android 10, I want to try out your method over the weekend... I will not check with version 4 yet, since there is no way to go back from 4 to 3...
Click to expand...
Click to collapse
Yes, I have a T290, so it's entirely possible the T295 has a different bootloader.
Talich52 said:
So, I flashed T295XXU3BUA5_OLM_XEV_20210129194935 of course with the CSC part (no HOME_CSC), that is, with a data reset, since I rolled back from android 11 to 10. But the main thing is now the bootloader version 3, but already 10 android, with which I remind you also could not rut earlier device or even install TWRP. Without letting the device boot after uploading the firmware, I switched it to the firmware mode and uploaded the TWRP file. I tried to enter the recovery and I get the SECURE CHECK FAIL: recovery.img error and now do nothing until you return the stock recovery :(
Click to expand...
Click to collapse
Can you describe the exact steps you took?
 
T

Talich52

Senior Member
Dec 24, 2010
476
249
V0latyle said:
Can you describe the exact steps you took?
Click to expand...
Click to collapse
1) through ODIN, I filled in the firmware T295XXU3BUA5_OLM XEV 10 of the android, I did not check it with the 4th bootloader, otherwise I would not be able to return to the 3rd version of the bootloader.
2) At the end of uploading the files, the device began to reboot and at first a screen appeared with a warning about the unlocked bootloader. I briefly pressed the volume button, a menu appeared, selected Recovery with the volume buttons and briefly pressed the Power button - the device entered the Downloading firmware mode.
3) in ODIN I selected the TWRP file and clicked Start
4) after uploading the file, the device began to reboot, pressed the volume button more and power to get into the recovery.
5) the device in the recovery did not boot and gave out a screen with an error :(
P.S. If you upload not TWRP, but the patched Magisk boot.img kernel file, then there will also be an error, but the boot.img file
Exiting this screen is only by entering Downloading and flashing stock files of the kernel or recovery ...
Well, either the bootloader firmware is also 3 versions, but from 9 android. The latest rooted firmware T295XXU4CVE4 is working with it now
 
Last edited:
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
timba123 said:
Ok thanks. I have downgraded to A10. Will try again and again until I finger it out. It's just been awhile. I left Samsung devices a couple years ago but was gifted this tablet recently. I'd be happy with twrp and rootless viper4android
Click to expand...
Click to collapse
I'm on CVE1 on the T290, running LineageOS 19.1. It's a bit of a pain installing TWRP but it's possible.
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
timba123 said:
This happened to me but was still able to boot into twrp! I kept going into download mode by accident, but never booted system which is key!
Click to expand...
Click to collapse
I'll be honest I haven't played much with Samsung either, but this is what I discovered:

When in Download Mode, ensure the text in the upper left does not say anything about KG Status. If it says "Checking" or "Prenormal", you won't be able to flash TWRP. You'll need to allow the device to boot into system and connect to the Internet (you can skip the setup wizard), and wait a few minutes before rebooting into download mode. If there is no longer any text about KG Status, you're good to go.

Remember to force boot into recovery right after flashing TWRP. You will need to wipe data and flash the Multidisabler. From that point you can proceed as desired - either flash Magisk on the stock ROM, or you can flash a custom ROM like LineageOS.

If "Secure Check Fail: vbmeta" appears, this means you tried to flash a custom binary (like TWRP) while the KG Status was either Prenormal or Checking.
 
  • Like
Reactions: temporarium and Deleted member 6405149
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
6,638
2
10,790
The Heartland of America
Google Pixel 5
Google Pixel 5a
timba123 said:
You guys are fast to edit a someone's speech but can't clean this thread up?
Click to expand...
Click to collapse
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.
 
  • Like
Reactions: Badger50, Oswald Boelcke, temporarium and 1 other person
You must log in or register to reply here.

Similar threads

SvenHee
Root for SM-T290 (tab a 8.0 2019)
Replies
645
Views
104K
L
LUCID_DREE
gcrutchr
SM-T295 - Finally rooted tablet!! (updated 19-March-2021)
Replies
735
Views
83K
T
Talich52
C
T280 Custom ROM Progress Thread
Replies
190
Views
113K
Alixbot
Alixbot
repey6
[ROOT][SM-T580/585&all Tabs A][CF-AUTO-ROOT][Simplest method to get ROOT & TWRP ]
Replies
108
Views
97K
S3nd41
S3nd41
DJBhardwaj
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
Replies
399
Views
159K
ljgjm
ljgjm

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    V0latyle
    V0latyle
    timba123 said:
    You guys are fast to edit a someone's speech but can't clean this thread up?
    Click to expand...
    Click to collapse
    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.
    View
    3
    L
    LogicOverflow
    Is 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:
    Code: 
    dd conv=notrunc if=<POST_PROCESSED_EXTRACTED_*.img_FILE> of=<PRE_PROCESSED_EXTRACTED_*.img_FILE>
    22) Delete the post_boot.img file to prevent any confusion
    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.
    View
    3
    gcrutchr
    gcrutchr
    xompax said:
    I too have this same black screen problem. I just recently posted over on the TWRP 3.5.1 thread here. How I got into this mess is that I tried flashing the TWRP v3.5.1 to my brand new Costco (link) SM-T290NZKCXAR using Odin3 vs 3.14.4 by checking the AP box and putting the TWRP v3.5.1 in the original top post in text area. When it finished successfully, my screen turned on (backlight illuminated) but black and vibrates when touched. If I turn it off by holding the power button, it turns on again to this same state. Odin v 3.14.4 seems to recognize it as COM 1 sometimes (and when it does, Windows shows it as a device in the device manager). When I attempt to hold the power, vol up and vol down buttons to reboot into download mode (perahps im not doing it correctly) it will "reboot" into the same black screen/illuminated background state but without Windows or Odin detecting it. If it helps my serial number begins with R9 and I just bought it from Costco yesterday ($111 with tax / on sale for $99) Any thoughts or ideas appreciated and happy to answer questions or provide more details. thx in advance!
    Click to expand...
    Click to collapse
    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.
    View
    2
    secretwolf98
    secretwolf98
    Here 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.tar
    View
    2
    gcrutchr
    gcrutchr
    secretwolf98 said:
    Well, the SM-T290 can handle ROMs. But only Project Treble enabled GSIs will work on it. So far, I’m trying to figure out how it could be installed through Odin without TWRP. Because Samsung devices doesn’t have a proper bootloader to be able to accept fastboot commands.
    Click to expand...
    Click to collapse

    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.
    View

New posts