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

Search This thread
By:
Advanced…
T

tymclrewhjbcpo

New member
Feb 6, 2023
2
0
My mom's SM-T290 was really sluggish so I decided to install LineageOS in it. I successfully installed it but there are several issues which bothers her.
1. Wi-Fi connection drops whenever she turns the tablet's screen off. She sells stuff online so she needs to receive notifications even when the tablet's screen is off. This is the worst issue we think so far.
2. There are no double tab to wake and double tab on home screen area to lock functions.
3. She can't set "confirm PIN without tapping OK" because it doesn't exist. She uses PIN, not pattern and that feature was enabled on stock ROM.
Is there anything we can do for those issues? The Wi-Fi one is really important so we started to consider going back to stock ROM even though it's far slower than LineageOS.
 
LedTV1

LedTV1

Member
Feb 7, 2023
17
0
hi, this instruction help me to falsh this tabled with problem on TWRP black screen?
 
lifehackerhansol

lifehackerhansol

Senior Member
Dec 17, 2016
182
110
Samsung Galaxy S III I9300
Google Nexus 4
This ROM is now official.

Because official builds are signed, converting from unofficial to official builds require a full factory reset. I do not have access to signing keys, so I cannot fix this for you.

As promised, I have fixed the BT issues, and it is part of the first official build released today.

New instructions: https://wiki.lineageos.org/devices/gtowifi/install

bozayibogan said:
My mom's SM-T290 was really sluggish so I decided to install LineageOS in it. I successfully installed it but there are several issues which bothers her.
1. Wi-Fi connection drops whenever she turns the tablet's screen off. She sells stuff online so she needs to receive notifications even when the tablet's screen is off. This is the worst issue we think so far.
2. There are no double tab to wake and double tab on home screen area to lock functions.
3. She can't set "confirm PIN without tapping OK" because it doesn't exist. She uses PIN, not pattern and that feature was enabled on stock ROM.
Is there anything we can do for those issues? The Wi-Fi one is really important so we started to consider going back to stock ROM even though it's far slower than LineageOS.
Click to expand...
Click to collapse
1. I have no idea how to fix this. I've tried all known ideas and they'd just break Wi-Fi further... But it's definitely on my to-do list.
2. AFAIK double tap to wake didn't exist in stock either. Though, feel free to prove me wrong, and then I'll look at it.
3. I don't understand what this is. I'm able to set a PIN and unlock my screen. Are you talking about something different?
 
Last edited:
LedTV1

LedTV1

Member
Feb 7, 2023
17
0
lifehackerhansol said:
This ROM is now official.

Because official builds are signed, converting from unofficial to official builds require a full factory reset. I do not have access to signing keys, so I cannot fix this for you.

As promised, I have fixed the BT issues, and it is part of the first official build released today.

New instructions: https://wiki.lineageos.org/devices/gtowifi/install


1. I have no idea how to fix this. I've tried all known ideas and they'd just break Wi-Fi further... But it's definitely on my to-do list.
2. AFAIK double tap to wake didn't exist in stock either. Though, feel free to prove me wrong, and then I'll look at it.
3. I don't understand what this is. I'm able to set a PIN and unlock my screen. Are you talking about something different?
Click to expand...
Click to collapse
Not working( After this part https://disk.yandex.ru/i/K5zgTRY1_gERZw i get black screen again
 
lifehackerhansol

lifehackerhansol

Senior Member
Dec 17, 2016
182
110
Samsung Galaxy S III I9300
Google Nexus 4
LedTV1 said:
yes/ Try again by now, flashing https://disk.yandex.ru/i/KSlKhYu19rjU_g I buy this tabled with android 10 on boaard, have some trouble wuth flshing twrp(
Click to expand...
Click to collapse
The LineageOS guide splits what TWRP is doing into 3 steps, and it only works when starting from stock ROM.

I'm not sure which step is the problem with the black screen. My assumption is that TWRP itself is the problem.

So after flashing everything back to stock, let me know if the guide works, or, if it doesn't, which exact step causes issues.
 
R

retiredtab

Senior Member
Nov 16, 2017
1,433
1,073
lifehackerhansol said:
This ROM is now official.
Click to expand...
Click to collapse
I look at

https://review.lineageos.org/q/status:open

each day and was pleasantly surprised to see that you had submitted this device for official status. Congratulations on achieving that status. I've already upgraded my T290 to this build and everything seems to be working fine so far. I'm only using Aurora Store so I have no gapps which helps with performance and low memory usage.

For non developers, this is a big achievement considering @lifehackerhansol basically built the device tree from scratch by himself starting with 18.1, then moved to 19.1 and now official 20 in about 40 days.

I know there were problems that were reported that I couldn't solve on my own. Some bugs takes me 3 months to figure out if I'm lucky.

lifehackerhansol said:
As promised, I have fixed the BT issues, and it is part of the first official build released today.
Click to expand...
Click to collapse
Audio over bluetooth works now.

Thanks for all your hard work and insightful comments in the PMs. I have certainly learned a lot from you.
 
lifehackerhansol

lifehackerhansol

Senior Member
Dec 17, 2016
182
110
Samsung Galaxy S III I9300
Google Nexus 4
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, unless you are a brave soul and want to take one for the community...
 
babyrexy

babyrexy

Member
Sep 9, 2009
8
0
shadyg said:
happens with gapps and without them, i wil try to go back to stock, root the device from 0 and try to install los 20 that way, hop that works.

Stock rom "SM-T290_ROM_T290XXU3CVG3_fac"

Thank you for all your help!

Question, what stock rom did you use ?
Click to expand...
Click to collapse
Hi,
Did you manage to fix your issue?
I'm running into the same issue as you.
I've followed the new instructions without any issues until after I reboot, it will go into a reboot loop and back to recovery. Have tried LOS recovery and twrp recovery. Same result.
- Confirmed OEM unlock is greyed out and enabled.
- flashed a-boot via ODIN
- flash los recovery
- disabled VBMeta
- installed LOS20 with and without gapps too.
-Revert back to stock and tried again
- no luck
- flashed twrp recovery
- flashed LOS20
- no luck and reboot loops

SM-T290 T290XXU3CVG3
I'm stuck and have just gone back to stock until there's a fix.
 
Last edited:
lifehackerhansol

lifehackerhansol

Senior Member
Dec 17, 2016
182
110
Samsung Galaxy S III I9300
Google Nexus 4
babyrexy said:
Hi,
Did you manage to fix your issue?
I'm running into the same issue as you.
I've followed the new instructions without any issues until after I reboot, it will go into a reboot loop and back to recovery. Have tried LOS recovery and twrp recovery. Same result.
- Confirmed OEM unlock is greyed out and enabled.
- flashed a-boot via ODIN
- flash los recovery
- disabled VBMeta
- installed LOS20 with and without gapps too.
-Revert back to stock and tried again
- no luck
- flashed twrp recovery
- flashed LOS20
- no luck and reboot loops

SM-T290 T290XXU3CVG3
I'm stuck and have just gone back to stock until there's a fix.
Click to expand...
Click to collapse
Just like I told the other guy, please provide the last_kmsg file
 
You must log in or register to reply here.

Similar threads

V
[ROM][SM-T580][SM-T585][UNOFFICIAL] LineageOS 16.0 64bit 20191211
Replies
482
Views
165K
vietan
vietan
J
[ROM][LINEAGEOS][7.1.2][OMS][microG][UNOFFICIAL] Samsung Galaxy Tab A 7.0 LTE SM-T285
Replies
507
Views
190K
T
TsPcs
_mone
[ROM][LineageOS-14.1] Samsung Galaxy Tab A 7.0 - SM-T280 (gtexswifi)
Replies
327
Views
135K
G
gtexswifienjoyer
Magendanz
[ROM][SM-T510][UNOFFICIAL] LineageOS 18.1 for Galaxy Tab A 10.1 (2019)
Replies
638
Views
155K
S
sip4050sip
jcadduono
[Recovery][T580] Official TWRP for Galaxy Tab A 10.1 WiFi 2016 (gtaxlwifi)
Replies
645
Views
265K
vietan
vietan

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 2
    Minionguyjpro
    Minionguyjpro
    Ragnak said:
    I took one for the community, out of despite and rage against my bad luck of finding out that I could install official LineageOS, but having the wrong bootloader version. "Let it be free or let it be bricked" I said last night.

    But the bootloader fails when using ODIN. On the bootloader screen, this appears:
    Code: 
    #SW REV CHECK FAIL <ABOOT> FUSED 4 > BINARY 3

    ODIN says it failed to do anything, and the screen freezes. Powering the phone off at that point does a factory reset, and there you go.
    Click to expand...
    Click to collapse
    Already expected that, as the bootloader with version 4 and higher doesn't allow flashing any custom stuff..., but now were sure.
    View
    1
    Ragnak
    Ragnak
    lifehackerhansol said:
    Our last known bootloader version is T290XXU3CVG3. Do not update past this, unless you are a brave soul and want to take one for the community...
    Click to expand...
    Click to collapse

    I took one for the community, out of despite and rage against my bad luck of finding out that I could install official LineageOS, but having the wrong bootloader version. "Let it be free or let it be bricked" I said last night.

    But the bootloader fails when using ODIN. On the bootloader screen, this appears:
    Code: 
    #SW REV CHECK FAIL <ABOOT> FUSED 4 > BINARY 3

    ODIN says it failed to do anything, and the screen freezes. Powering the phone off at that point does a factory reset, and there you go.
    View
    1
    Ragnak
    Ragnak
    Minionguyjpro said:
    Already expected that, as the bootloader with version 4 and higher doesn't allow flashing any custom stuff..., but now were sure.
    Click to expand...
    Click to collapse
    Glad to be part of the team.
    View
    1
    Minionguyjpro
    Minionguyjpro
    default_user8 said:
    I'm looking at a tablet that has build T290XXU3BTG1,

    can anyone tell me if that build is early enough to flash a new ROM?
    Thanks
    Click to expand...
    Click to collapse
    Yes, you can. Your bootloader is version 3, which is good.
    View
  • 7
    lifehackerhansol
    lifehackerhansol
    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.
    Click to expand...
    Click to collapse

    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
    View
    2
    lifehackerhansol
    lifehackerhansol
    @babyrexy @shadyg next build on official site has some updates that may help solve the problem. It's scheduled on Tuesday.

    Basically, I'm scrapping the vbmeta instructions and bundling it into the ROM altogether, which hopefully solves this issue...? maybe, perhaps.

    What I'm seeing here is that a few services critical to file encryption is failing, and I genuinely don't know why at this point. I'll keep trying though.
    View
    2
    lifehackerhansol
    lifehackerhansol
    @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.
    View
    2
    lifehackerhansol
    lifehackerhansol
    babyrexy said:
    Here's the latest last_kmsg file.
    Was able to load into LOS 20 and set up the device.
    Rebooted and shutdown. Seems to work.

    Wifi works
    BT works


    Thanks for resolving the issue. Did you manage to pinpoint and figure out what was the cause?
    Click to expand...
    Click to collapse
    It turns out this is also a bug on Samsung's side. I assume Samsung (or their ODM, Wingtech) worked around their dumb issue somewhere else.

    Essentially, Android has a bunch of "init" scripts that prepare the device on boot for general usage. In custom ROM development, device-specific init scripts must be extracted from the device in order to build stuff. So my init scripts are the same as Samsung's for the most part.

    Two things going on here:
    - This tablet has file-based encryption (FBE) turned on by default.
    - According to Google's docs here, they require the keymaster service (basically hardware cryptography stuff) to be active before the FBE-encrypted user data is loaded, and the most common way is to load the user data last. However Samsung did not wait for keymaster, and just loaded everything without verifying anything, causing a race condition that only happened to a couple devices, yours being one of them.

    That was a lot of explaining, but the actual fix was like 5 lines of code: https://review.lineageos.org/c/LineageOS/android_device_samsung_gtowifi/+/348851

    The next official LineageOS build will also contain this fix. As a general reminder, to convert from unofficial to official builds, you must clean flash, but given this is your first time booting literally anything at all, I don't think that would be too much work for you.

    PS: I only ever need last_kmsg it if it's failing to boot, which was the case here. Any issue that happens while the device is running, you can refer to here: https://www.xda-developers.com/how-to-take-logs-in-android/
    View
    2
    R
    retiredtab
    Ventur83 said:
    Hello.Now I want to download this ROM and flash it on my tablet. I had a few suggestions. One is that the sourceforge link is very slow, I think it is better to upload the ROM file somewhere else besides the sourceforge.
    Click to expand...
    Click to collapse
    There are no problems with sourceforge for me. It downloads fairly quickly. The reason I host my roms on sourceforge is so I can see download stats on where it's being used in the world and how many people are using my roms.

    I've never had anyone complain about sourceforge in 2 years that I've been using it. Androidfilehost, on the other hand, has lots of uptime problems which is why I switched to sourceforge 2 years ago.
    Ventur83 said:
    The second suggestion is to create a Telegram group and channel to support the ROM or all the developments of this tablet.
    Click to expand...
    Click to collapse
    The idea of open source software is so that everyone can use it and the discussion about it's capabilities should be in a public forum. Telegram is NOT an open forum because it forces people to give away their phone number to join and participate. I or anyone can view xda posts without an userid/password if I choose so.
    View

New posts