[ROM][OFFICIAL][13] LineageOS 20.0 for the SM-T290 (gtowifi)

Search This thread
Feb 6, 2023
11
0
It's been a while this tablet was running old software, so I decided to clean install lineageos but I'm facing with this error when I flash recovery.tar via odin and try to boot into recovery. The recovery.img was downloaded from lineageos downloads page. Bootloader is unlocked by the way, I'm stuck.
 

Attachments

  • 20230607_193724.jpg
    10.4 MB · Views: 85
It's been a while this tablet was running old software, so I decided to clean install lineageos but I'm facing with this error when I flash recovery.tar via odin and try to boot into recovery. The recovery.img was downloaded from lineageos downloads page. Bootloader is unlocked by the way, I'm stuck.
What bootloader version has your tablet? Check so in download mode.
 
It's been a while this tablet was running old software, so I decided to clean install lineageos but I'm facing with this error when I flash recovery.tar via odin and try to boot into recovery. The recovery.img was downloaded from lineageos downloads page. Bootloader is unlocked by the way, I'm stuck.
Try to install TWRP 3.7.0 on it. Then use TWRP to flash the LineageOS ZIP.
 
Feb 6, 2023
11
0
Try to install TWRP 3.7.0 on it. Then use TWRP to flash the LineageOS ZIP.
I get SW REV CHECK FAIL : [aboot]Fused 4 > Binary 3 whenever I try to flash twrp, I believe it's due to me who made a unawarely mistake updated to version T290XXS4CWC1, the recent twrp is incompatible with bootloader 4 I think. Apparently, I'll stick with the stock rom onwards.
 
I get SW REV CHECK FAIL : [aboot]Fused 4 > Binary 3 whenever I try to flash twrp, I believe it's due to me who made a unawarely mistake updated to version T290XXS4CWC1, the recent twrp is incompatible with bootloader 4 I think. Apparently, I'll stick with the stock rom onwards.
It is not that TWRP needs to change anything. This is due to Samsung's new policy which will reject to flash TWRP. At the moment there is no way to get around it and will probably need to stick indeed with the stock ROM.
 

G_Bot

Member
Jul 4, 2020
40
13
I just installed LOS 20.0 on my Sm-T290 And it's running very smooth, and everything works well. Thanks so much for this work. 👍
 

Kaldun13

Member
Jul 16, 2019
23
1
Just installed latest nightly build, everything is smooth, but how can i get my ds4 controller work? Another BT controller works good, but ds4 just connecting, but not work at all, even i installed magisk module onecontroller.
Could someone check if dualshock controller works or not ?

UPD. rolled back on build 20-06 this is the last one with dualshock 4 supporting.
Last 2 builds from 27-06 and 04-07 there are no DS4 support
 
Last edited:

Kaldun13

Member
Jul 16, 2019
23
1
I dont know why i decided to update fw using this instruction but as i had LOS20 installed with los recovery i got blue screen on boot "secure check fail : boot.img"
At the end of that instruction said after all of it if i have custom recovery Download this downgrade package, but the linked file "1-downgrade-aboot.tar" no more available.
So i stucked on it. Should i flash stock rom first ?

UPD just flashed last T290XXU3CVG3 official rom via odin, than installed LOS20 again.
 
Last edited:

Meloferz

Senior Member
Just installed latest nightly build, everything is smooth, but how can i get my ds4 controller work? Another BT controller works good, but ds4 just connecting, but not work at all, even i installed magisk module onecontroller.
Could someone check if dualshock controller works or not ?

UPD. rolled back on build 20-06 this is the last one with dualshock 4 supporting.
Last 2 builds from 27-06 and 04-07 there are no DS4 support
With 27/06/2023 update, PS4 controller doesnt work. Only works wired
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Dear guys don't loose hope. i successfully flashed GSI to T290 tablet shipped with android 10. soon i will be making a guide to that
    WhatsApp Image 2023-09-07 at 17.09.34.jpeg
    1
    Suspense is building :)
    1
    runs well thank you! couple of notes during install that might help someone:
    i had to use a usb c to usb a 2.0 adapter to get the bootloader unlock screen to show when plugging in. using the native usb a 3.1 port on my computer would just pop up the charging screen. Had to downgrade to the firmware listed in OP thankfully my bootloader version is still U3 so it is able downgrade with patched ODIN. If you have upgraded it *may* be possible to downgrade by externally restore a full dump to the emmc since as far as i know budget low end qualcomm chips dont have efuse like exynos.
  • 12
    WARNING: Samsung rolled out a new firmware update starting roughly at the end of January 2023.
    This contains bootloader version 4. From what we understand with SM-T295 bootloaders, this may or may not permanently lock you out from ever flashing anything custom. Considering that we even have to downgrade our bootloader to the Android 9 version to get anything going, updating your bootloader this time will very likely block you from downgrading it, ever.

    Our last known bootloader version is T290XXU3CVG3. Do not update past this, you will not be able to flash custom anything again.


    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.

    * Your warranty is now void.
    (But I mean it's probably already void at this point... bleh.)

    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed.
    * Please do some research if you have any concerns about features
    * included in this ROM before flashing!
    * YOU are choosing to make these modifications and if
    * YOU point the finger at us for messing up your device,
    * WE will laugh at you.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS GitHub organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Device source code:
    Credits:
    • LineageOS team
    • @Magendanz for TWRP
    • @SebaUbuntu for twrpdtgen
    • AndroidDumps on Telegram for help extracting blobs
    • @retiredtab for much initial testing and feedback
    3
    do you know how to patch bootloader. i tried to patch it using ghidra. i went through all error messages and code blocks. can you tell me how you got the unlocked boot abn. is there any way we can bypass the secure boot or signature verification
    The bootloader isn't patched. We use a very early version of the bootloader (I believe the first or second stock ROM to have ever shipped) which actually respects the vbmeta settings.

    I don't know whether reverse engineering the aboot will really solve the issue. I can't seem to figure out where the issue is, either (I've thrown it in ghidra at one point as well). That's before even thinking about whether a modified aboot will even boot on the device.

    So we're stuck until someone with legitimate hacking experience finds out. Which is probably rare for a cheap tablet where I'm the only one tinkering with it.
    3
    Dear guys don't loose hope. i successfully flashed GSI to T290 tablet shipped with android 10. soon i will be making a guide to that
    WhatsApp Image 2023-09-07 at 17.09.34.jpeg
    2
    @2faraway2 I think I reproduced the vbmeta thing.

    It seems the TWRP method isn't totally right. It doesn't like it when vbmeta is combined with other files in the tar.

    So far, I tried reverting to stock, and:
    1. flash aboot and vaultkeeper
    2. reboot, then flash vbmeta
    3. finally, flash LOS recovery

    and that seemed to work.

    I'll try to do a writeup, upload relevant files and get back to you.