[RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2019 Galaxy Tab A 8.0 [SM-T290]

[Magendanz]

What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this low-cost tablet. My thanks to @mehanik6 for blazing this trail on 4PDA.

Notes:

• The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
• This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.

Not working:

• Support for file-based encryption

Downloads:

• twrp-3.7.0_11-0-T290XXU3CVG3-20221120.tar.md5
• twrp-3.7.0_11-0-T290XXU3CVG3-20221120.img

Build Archives:

• Android File Host

Change Log:
v3.7.0_11-0: (2022-11-20)

• Updated to TWRP 3.7.0 release built from AOSP-11 branch.
• Updated to T290XXU3CVG3 OEM stock kernel.

v3.6.1_11-0: (2022-03-27)

• Updated to TWRP 3.6.1 release built from AOSP-11 branch.
• Updated to T290XXU3CUK4 OEM stock kernel.
• Using FFS MTP so that custom kernel builds are no longer necessary.

v3.6.0_11-1: (2022-02-20)

• Added wipeingui for ext4 partitions.

v3.6.0_11-0: (2022-01-23)

• Updated to TWRP 3.6.0 release built from AOSP-11 branch.

v3.5.2_9-0: (2021-10-17)

• Updated to T290XXU3CUG4 posted kernel source.

v3.5.2_9-0: (2021-05-16)

• Updated to T290XXU3BUC1 posted kernel source.
• Updated to TWRP 3.5.2 release built from android-9.0 branch.

v3.5.1_9-0: (2021-03-30)

• Updated to T290XXU3BUB2 posted kernel source.
• Updated to TWRP 3.5.1 release built from android-9.0 branch.

v3.5.0_9-0: (2021-01-02)

• Updated to T290XXU3BTI2 posted kernel source.
• Updated to TWRP 3.5.0 release built from android-9.0 branch.

v3.4.0-1: (2000-12-09)

• New custom T290XXS3ATC1 kernel that actually fixes MTP support.

v3.4.0-0: (2000-12-04)

• Included legacy aboot and vaultkeeper in tarball to allow Odin flash on Android 10 OEM firmware.

v3.4.0-0:

• Initial release based on @mehanik6's device tree and T290UES3ATC1 kernel.
• Fixed MTP
• Default language is now English

Instructions:
From OEM stock firmware:

• Unlock bootloader
• Hold Vol Up & Vol Down buttons during restart to enter Download mode
• Install TWRP to AP with Odin
• Hold Power & Vol Up buttons during restart to enter TWRP recovery
• Install latest Multidisabler that preserves encryption from TWRP
• Wipe->Format Data
• Reboot to system

From existing TWRP install: (No need for data wipe.)

• Hold Power & Vol Up during restart to enter TWRP recovery
• Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
• Reboot to system

What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.

Source:

• android_device_samsung_gtowifi

Donations:

• Your support is always appreciated! Just click here.

 

[Tralien]

are there any custom roms for sm-t290?

 

[Magendanz]

are there any custom roms for sm-t290?

I'll have a release of my Nexus Stock custom ROM shortly. It's basically the same as what I've been releasing for the 10.1" version of this tablet over the past year. I'm basically just waiting for Samsung to post the latest kernel source.

 

[Magendanz]

Update for TWRP v3.5.0 release...

Downloads:

• twrp-3.5.0_9-0-T290XXU3BTI2-20210102.tar.md5
• twrp-3.5.0_9-0-T290XXU3BTI2-20210102.img

Change Log:
v3.5.0_9-0:

• Updated to T290XXU3BTI2 posted kernel source.
• Updated to TWRP 3.5.0 release built from android-9.0 branch.

 

[dark_friend]

I have tried installing via Odin your twrp custom recovery for my t290 device.
The process with Odin seem to go well and after installation my device restarts however, when I press the + volume button, android recovery shows up and not TWRP.
Any idea why?

 

[Magendanz]

I have tried installing via Odin your twrp custom recovery for my t290 device.
The process with Odin seem to go well and after installation my device restarts however, when I press the + volume button, android recovery shows up and not TWRP.
Any idea why?

There are two issues here:

1. The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
2. If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.

So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.

 

[dark_friend]

There are two issues here:

1. The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
2. If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.

So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.

Got it! thank you very much!

 

[Heeni]

There are two issues here:

1. The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
2. If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.

So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.

Presumably, if you miss the first time, you reflash and try again? (and as many times as needed?)

 

[Magendanz]

Presumably, if you miss the first time, you reflash and try again? (and as many times as needed?)

If you miss, hold Power + Vol Down for 7 seconds during the boot animation to do a hard reset and try again. Alternatively, you can wait for it to finish booting and then restart, but then you risk Samsung's VaultKeeper "feature" putting the bootloader into a stealth locked state. You can prevent that by connecting to the Internet, enabling Developer Options, and then confirming the OEM Unlocking state as soon as you finish setup. (You don't need to log into Google or Samsung services for Vaultkeeper to maintain the bootloader unlock, but you've got to have Internet access and reenable Developer Options right away.)

 

[Heeni]

Thanks for pointing out some of the potential potholes along the way. I'm not a stranger to modding, but have experience only with fastboot, so the Samsung method is a whole new ballgame for me. Maybe I just need to take a deep breath and jump in. And backup everything before starting.

 

[Magendanz]

Thanks for pointing out some of the potential potholes along the way. I'm not a stranger to modding, but have experience only with fastboot, so the Samsung method is a whole new ballgame for me. Maybe I just need to take a deep breath and jump in. And backup everything before starting.

Yeah, it never ceases to amaze me how Samsung believes it's adding value with Knox security features like Vaultkeeper and its special Download mode that only works with Odin. My main phone is a Pixel 4a, and I've never felt that Google has taken any flak for making bootloader unlocking and firmware flashing painless. Why does Samsung feel the need to reinvent the wheel?

 

[Heeni]

Somewhat to my surprise, I was able to get TWRP installed and boot into it on the first try. In fact, the biggest difficulty by far was getting Samsung drivers to work in my Windows 10 vm. The vm is still having problems, so hopefully, now that TWRP is installed, I won't need to use Odin for a while.

 

[Heeni]

Tried patching TWRP with Magisk. No bootloops or other drama, but wifi doesn't work. I notice on the Magisk Github site that a number of people are running into this. Fortunately, restoring the unpatched TWRP also restored wifi.

I think I can live without root much more easily than without wifi!

 

[temporarium]

Tried patching TWRP with Magisk. No bootloops or other drama, but wifi doesn't work. I notice on the Magisk Github site that a number of people are running into this. Fortunately, restoring the unpatched TWRP also restored wifi.

I think I can live without root much more easily than without wifi!

I have root and wifi, but didn't use the TWRP install method

 

[Heeni]

Further to this post about the inability to set a password, PIN or pattern:

I reflashed the stock ROM and I can verify the following:-

Stock ROM with (or without) bootloader unlocked will allow me to set up a PIN (I didn't try the other options but would expect that they'd work.

As soon as I install TWRP, the stock ROM will no longer allow me to set up a PIN. I can have "swipe" or "nothing" to unlock, and that's it.

I've tried installing LineageOS 17 GSI, LineageOS 18 GSI and Magendanz's Nexus stock ROM. None of these will accept a PIN, password or pattern.


Therefore, I think that the issue has to do with TWRP, or possibly with something in the multidisabler script.

Googling has come up with nothing other than the instruction to remove /data/system/locksettings.db and related files. I've tried this numerous times without success. I've even tried comparing permissions and ownership with the (working) equivalent on my Moto phones, with no luck.

I'm happy to do any tests, provide logs etc if it would help. The only other alternative seems to be to revert to stock if I need to travel.

 

[Wadzii]

I'm going to be using the table in an install that does not allow easy access to be able to use the physical buttons, if I lock the boot loader back after all this will it keep root?

I need root so that I can modify the files necessary to make the tablet turn on automatically whenever power is connected.

 

[Magendanz]

New release posted...

Downloads:

• twrp-3.5.1_9-0-T290XXU3BUB2-20210330.tar.md5
• twrp-3.5.1_9-0-T290XXU3BUB2-20210330.img

Change Log:
v3.5.1_9-0: (2021-03-30)

• Updated to T290XXU3BUB2 posted kernel source.
• Updated to TWRP 3.5.1 release built from android-9.0 branch.

 

[Heeni]

Do we need to update the underlying stock ROM first if TWRP is already installed? Or is it sufficient to flash TWRP from the existing TWRP?

 

[Magendanz]

Do we need to update the underlying stock ROM first if TWRP is already installed? Or is it sufficient to flash TWRP from the existing TWRP?

You can just flash the new .img file from an existing TWRP install. The version of the kernel is only important if you're using Magisk (which boots through the recovery partition).

 

[Heeni]

Thanks. That was easy. As far as I can tell at this point, it all works.

 

[JCARLOS123]

Hello,
I am new to TWRP. I have a couple of questions. What is the proper way to back up your rom? I mean what boxes should i check when creating a backup? Also, what is the proper way to do a wipe when I want to restore a backup of a rom? I find myself having to reflash the rom all over again when I try to restore a backup. The rom freezes on the google bootup icon with the bar going across every time I try to restore a backup. I notice that the google icon flickers when it is not going to bootup. I think it has something to do with what I select when I wipe before I restore the rom. I have installed twrp-3.5.0_9-0-T290XXU3BTI2-20210102.tar.md5, Nexus_Stock_AQ_T290XXS3BTL6-20210104, Magisk-v21.4. I love the ROM b the way. Thank You for your hard work. Very much appreciate any assistance.

Thank You,