yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
Yes, if you are able to boot into recovery, feel free to immediately flash the ROM. As usual, format data before doing so.

Please provide a log, as stated in OP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] antisomnic:
GAPPs don't appear to be working right, they can't access the internet. I'm not sure why. The rest of the system can access the internet.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
@lifehackerhansol :

As feared ... flashing worked without any prob, but the device doesn't let me boot into the recovery: secure check fail (see attachment) ..

I'm at a loss right now :cry:

But anyway, a huge thanks for your support .. If I can help in any way, please let me know !
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
This is interesting... and you are certain you were on T290XXU3CVG3, yes?

I ask because this bootloader screen looks nothing like my tablet. That BL screen feels reminiscent of the version from Android 9, even though that screen should have changed to a black background LONG ago.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
For audio over bluetooth not working, I'll send you a PM with the logcat, but looking through your 20 commits, you probably need to add the following because Google made major changes to Android 13 wrt to bluetooth. See

https://review.lineageos.org/c/LineageOS/android_device_essential_mata/+/346377

https://review.lineageos.org/c/LineageOS/android_device_nubia_msm8998-common/+/346716

https://review.lineageos.org/c/LineageOS/android_device_nubia_msm8998-common/+/346719

On my bluetooth test, I can see it pairs, but there's no audio over bluetooth shown in the volume rocker and then it disconnects after a bit.

On my legacy devices, I've had to make similar changes to the above to get it working.

BTW, I rarely use my 2.4Ghz wifi, but when I tried it, this 20 build seems unstable as the wifi drops even though I'm probably only 25 feet away. For your 18.1 and 19.1, I was using 5Ghz with no problems. I'll do some more testing with 2.4Ghz over the next couple of days and send you a PM log if I capture anything. If this 2.4Ghz is an issue, it could have been in 18.1 and 19.1, but I never tested it.

Thanks for bringing up 18.1, 19.1 and 20 all from scratch!!! Great Job!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
Yes, definitely sure
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
The above 'secure check fail' screen is the second one after trying to boot into the LOS recovery.

The first 'warning screen' is this one, which is to be confirmed with the POWER button ..

May be you meant this one @lifehackerhansol ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
Yes, I do not get this screen at all. I can't capture it right now, though.

I can't tell what's different about this one, unfortunately...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] antisomnic:
So I dug my galaxy tab out of a drawer and decided to resurrect it. I finally figured everything out to install Lineage 10 on it after being away from Android for probably 8 years.

I did not realize (or rather remember) that this tablet only has 2 gb of RAM. That is severely limiting. I am very curious what "zRAM" is?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] xperiazu21:
Yes, only 2GB RAM is not enough for today's Apps.

As I understand it, zRAM is a virtual memory compression feature.

Compared to traditional Swap pagefile on hard disk, zRAM compresses low priority processes and stores them in faster RAM.

However, since zRAM requires compression, it takes up CPU performance.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
If you're interested in looking deeper into this issue personally I could borrow you my device for a while (couple of days or weeks) .. Of course only if the shipping costs doesn't blow my budget .. ;)

Pm me if you like
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
@cdepping @retiredtab BT audio is fixed for the next build. Stay tuned (pun intended).

Even my true wireless earbuds work now, interestingly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
think this will fix the bluetooth keyboard not working too?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
Took out my BT keyboard, seems to work. Was able to search something on the Play Store.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
I tried something again.

This is what gts4lv does, I just adapted it for gtowifi.

Basically flash everything here, then flash LOS recovery like earlier:

Release T290XXU3CVG3 · lifehackerhansol/gto-fw

Contribute to lifehackerhansol/gto-fw development by creating an account on GitHub.

github.com
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] shadyg:
I have de same problem this it what I get

I think is the recovery, if i instalat TWRP is fine but I can't boot in Los
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lifehackerhansol:
Sorry, your post is a little confusing. Do you mean you can't boot LOS when you install using TWRP, or you can't install LOS recovery?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
You can unlock the bootloader (without any risk), but even with the unlocked bootloader your device won't let you install anything 'custom', e.g. recovery, custom rom or gsi ..

So your unlocked bootload won't bring any advantage, but you will loose your google play integrity (if google play store should be important for you)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gored103:
Now i understood, even though it is possible to unlock bootloader theres a"second layer of security" that stop u from flashing anything non stock. And u have to stick with this laggy system.

It makes me feel sad because i rescued this poor gtowifi, in front of my house with broken back cover and smashed screen and tried repairing, buying the pieces left and managed to do it and I was gonna use it for myself but it works much worse than my SMT580 (gtaxwifi) (2016) that has unofficial lineage and works like a charm. I wanted to try this one but when i read the disclaimers I got disappointed (FAKIN SCAMSUNGG)

I'm now thinking of selling it, because i guess is it impossible to make a downgrade or even less modify the bootloader, obviously samsung aint gonna do ****, they want u to buy new stuff.

Thanks anyways,

Gored
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
Yipp, it's a shame how Samsung take care of the customer experience .. :mad:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Thelords88:
How do i get Nikgapps Core version to work, after flashing it through TWRP successfully, it either doesnt show up when i boot the SM-T290 or Gapps just crashes and none of them work
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] shyamjayakar143:
@lifehackerhansol can you let me know how to make a eng build. i think i'm close to finding a solution
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
I got it before the bootloader change but I did actually complain to them about it shutting down the community for this device. My work gave us all Samsung phones and they are also junk. Won't buy another Samsung again.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] shyamjayakar143:
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
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] yogibaaeer:
Suspense is building :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] shyamjayakar143:
https://xdaforums.com/t/flash-gsi-on-t290-with-twrp-blackscreen.4627759/

here is the guide
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] echow2001:
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.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] shahdyaar:
hello every one! i have a very good experience at this site, to update android of my tablet. now i want to choose the best ROM for Samsong galaxy tab A SM-T295 made in 2019.

IF the way to install custom ROM is the same as Samsong N8000 , i know what i should do.

TWRP is the same? just use odin for TWRP and next ...?

Please is i am right, just give me link of a very smooth and fluent ROM for SM-T295

thanks for your kind attention.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] G_Bot:
Hello. just wanted to mention I had a problem after updating Magisk using the app direct isntall. My device rebooted into download mode and got stuck there for some reason.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
You have to pull the boot.img, patch it with magisk and reflash. Flashing directly from the app doesn't work right, at least the older version.

Did you get it fixed?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] smashedpotato:
Hi, I'd really appreciate some help. I followed the instructions for the Installation of Lineageos 20 https://wiki.lineageos.org/devices/gtowifi/install

I'm stuck at "Warning: If, on this step, your device is stuck on a black screen, your device’s bootloader is not unlockable and you cannot continue with these instructions. To return to the stock ROM, boot to Download mode and flash the BL package here."

Is there a detailed Instruktion how to install the package to get back to beginning.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
Can you not use the directions located directly above the warning you posted? It should be the same process only use the bl in your link right?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Hello, Sorry if this has already been covered....

I think that I did everything right. Only thing I did differently is to install TWRP.

Now my tablet is only booting into Download Mode.

May be unrelated, it happened sometime after installing Magisk.

I am able to boot into system if I get into TWRP and then choose reboot system.

Any help would be greatly appreciated. Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
Does rebooting through TWRP get you into the system? If not, does adb reboot system get you there or is it unreachable altogether?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Rebooting though TWRP is the only way I have found to boot the system.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Solved:

Update. I am now able to boot into the system with no problem. I think the problem was a failure in flashing Magisk properly. i downloaded a fresh copy for flashing and it seems to have worked.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
I am Ungoogled and using Magisk's MicroG.

Has anyone figured out an easy way to enable Signature Spoofing on the SM-T290?

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
@TamD: You can install microG like described here . This method isn't related to specific roms or devices, but is universal ..
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Thank you for the link. It looks promising. I will give it a try. :-)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Success! My new SM-T290 has passed the MicroG Self-Check with flying Colors!

Thank you 2faraway2 for you help!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 2faraway2:
Perfect, good to hear that (y)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Newbie to the SM-T290....

My tablet is still wanting to boot into Download Mode. The only work around I have found is to boot into TWRP and from there booting into system.

So, I am running through the instructions provided trying to figure out what I did wrong.

The only thing that I can find is that I seem to have two files, dtbo.img and vbmeta.img, that I did nothing with, and I could not find anything in the instructions regarding them. Was I supposed to do something with them?

I am thinking that my problems are related to the boot.img installation. I am considering starting the whole installation process over after doing a little more study.

Any suggestions would be greatly appreciated. :)

PS. Is the SM-T290 supposed to have Ramdisk? My Majisk install says "no" which seems odd to me......
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
That's kinda of weird. It only did that once after flashing the rom. I think adb reboot system from TWRP then solved that. If you have twrp installed then it should just be as easy as putting the img file on an sdcard and flashing it. Ive done it over and over and over with the other gsi images with no problems and switched to this one when it came out. make sure to wipe cache before reboot. Also you should just be able to flash the whole zip. youll have to hit the flash zip button or something. I detailed it in the lineageos 18 forum if I remember right.

Also when flashing magisk and modules, do it from twrp, not from the magisk app. You can pull the boot.img from twrp and then patch it with the updated magisk app, reboot to twrp and flash the patched.img.

No, there is no ram disk according to mine also. Zygisk yes, ramdisk no.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Thank you for all of your suggestions.

I flashed the boot.img from TWRP and that might have done the trick.

I think that I did the Magisk patching correctly, but then I could not find the patched.img file afterwords. ?

I did reflash Magisk from TWRP (again) and that seems to be working fine now.

Is there a reason you flash Magisk modules from TWRP?

Thank you for all of your assistance. Best Regards.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
So pay attention to where magisk says it puts it. It won't be named patched.img. If you have to run it again to see, it doesn't hurt anything.are you reflashing the boot.img from the Web site or the one you pull after flashing the nightly zip? I never flashed the stand alone boot.

Even though magisk installed through the app, it wasn't right and would not except modules until I learned to pull the img myself and patch it. I've also had issuess with the modules not working after being flashed through androidacy module manager. They worked after flashing through TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Thank you for the info. I did find the patched image. :-)

I am flashing the boot.img that was provided in the instructions (on page 1). I am new to Samsung, my old Nexus 7 (2013) was so much easier to deal with, with huge amounts of support.

Again, thanks for your help. I will give it another try later.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
These are a pain and the only rom I've seen is this one. My attempts at making stuff for it failed. Plus Samsung locked the bootloader.

I couldn't figure how to link to it so I just copied and pasted but this is how I detailed it in another thread

Change the first line to the nightly build of lineage instead of this gsi image.

--------------------------------------------------------------------------------

-- extract lineage-20.0-20221023-UNOFFICIAL-gsi_arm64_vN.img.xz

-- rename Magisk-25.2.apk to Magisk-25.2.zip

-- copy the resulting lineage.img and Magisk.zip files to the sdcard

-- boot into twrp -> flash -> find your linage.img file and flash the system partition

-- before you reboot, back out and go to wipe-> format data-> type yes

-- this step maybe optional but I rebooted and made sure the device booted into the os - if you want gapps, my understanding is that you do that before your first boot.

-- reboot to twrp -> flash -> flash the magisk.zip also to the system if it asks

-- reboot system and observe that you have a magisk icon in app draw

-- once in app, click the app install button, I also installed under the magisk title but i think that it is unnecessary and worked fine with out doing it.

-- observe that the icon changed, that it says installed under magisk, and use your favorite root checker to make sure that it works.

Take not that I haven't got gapps to work although I'm not 100% how, cause I'm also a noob :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Thank you for your instructions. Much appreciated.

Well, I have absolutely no interest in having Google/Gapps on any of my devices.

I am running Magisk Aurora Store Services (and sometimes Aptoide) for most of my apps. Otherwise I use APKCombo to download from Google Play Store. Works like a dream:

https://apkcombo.com/downloader/

Noobs... how I have managed to be labeled as a Senior Members on XDA is beyond me..... it might give someone the impression that I know what I am talking about! :-)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
my appologies, rereading my last post I realize that those didn't include the actual patching of the boot and reflashing as you should have done to insure modules work, but the process is the same as on their offical site and sounds like you got it figured out.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
No wonderI have been have such difficulties with booting up.

Interesting..... regarding the lack of ramdisk with TWRP.

Copied this from another thread....

This is from https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

"Since some devices no longer use ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
TWRP + MAGISK

I have read online that there is a (mythical?) Unofficial TWRP with built-in Magisk (pre-rooted) that accommodates the lack of Ramdisk on the SM-T290.

Does anyone have a copy of it, or can point me in a link for it?

Thanks. :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
That's weird to me. I don't have a ramdisc and I don't have to boot into recovery every reboot. everytime I flash a new version, yes. But unless something magical happened, the only thing that I put to recovery was TWRP.. I've even set it up so that I can reboot it from ssh because I've built it as the head of a Beowulf cluster :)

I did flash the "nexus" rom before messing with lineage os. Don't know if that did something. Theres a multi disabler that does something, you might investigate that.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
The problem I am having is with mostly with Magisk.

When I open Magisk I get the message "Magisk needs additional setup", if I proceed to follow its instructions the tablet will then restart into bootloader, and the only way that I can restart the system is to boot into TWRP, and then boot into the system. After that it will boot normally, but I will still get the message from Magisk. Mainly just irritating.....

Same thing happens when I install a Magisk Module.

I have tried installing Magisk.zip via TWRP, as well as creating a Boot.img Magisk package... always the same result.

So, if I ignore the "Magisk needs additional setup", and don't install Magisk again as directed I can do a normal restart without going into TWRP. In spite of the "Magisk needs additional setup" message I still seem to be rooted and Modules still seem to work. So, I will tinker at my leisure and hopefully I can resolve this issue.

Thank you for the suggestion. I have read a little about the multidisabler.... I will try to hunt that down and give it a try.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
Yep and that's the issue I was talking about. It's rooted but not right. Are u pulling the boot from your device or using the one on the website?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
I took the one from the website.... I no longer have the original from this tablet.

I contacted Magendanz who seems very knowledgeable about TWRP and he sent me this link.

Installation

The Magic Mask for Android

topjohnwu.github.io

So, I might try some of this when I get a break...... :-)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
Nah, after u install los, pull a fresh boot.img from the device. I've only read problems with people using the one on the website. Also, I may have had an issue with the lastest magisk. I can try to update it when I get home tonight and make sure it works. For that matter if it does then I could probably upload the new boot.img that I make.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Hmmm. Are you saying that the operating system creates its own boot.img? I thought that boot.img was independent of the operating system.....
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
Every thing should be functional after flashing only the los.zip. I think the boot.img off website is something with the los recovery,, as in not TWRP. Or something. I don't know. There's a lot of confusing instructions and the boot.image never worked for me.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
The system should be functional* not magisk
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
Alright, so I just did a quick (not really) run through of flashing/patching and getting the microg from above post to work. Ill not detail the steps but general over view and it looks like i can post my resulting .img so ill do that if its not against board rules.

~first get all of your files on sdcard- latest nightly.zip, magisk 26.3(26300), and do a quick drag and drop to get the boot.img out of the nightly.zip. This just saves a step later.

~flash nightly.zip-->reboot --> ensure function

~install magisk, patch the boot.img you pulled and reflash.

reboot. at this point I believe magisk again complains that it needs to reflash. so do that only this time pull a backup from your device. twrp saves as .win and thats fine ->patch and reflash.

~magisk should now work with no complaints, install microg stuff from above and the microg check should all light up checked.

The uploaded boot.img is patched from the latest lineage-20.0-20231102-nightly-gtowifi-signed.zip
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Thank you for that.

You lost me at "pull a backup from your device. twrp saves as .win and thats fine ->patch and reflash."

Is that "pull a back up" a just in case measure, or do i do something with it? Are you saying patch the twrp win. file?

Because backing up with twrp is a problem for me right now as I am getting error 255, which I have tried a few things to correct but have yet to resolve.....

Thank you for any clarification. :-)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SunSlide:
So, I mean backup the boot partition. What we re doing is pulling the boot.img from the device. go in to TWRP and into the backup menu and make sure only the boot partition is selected, scroll down cause my data partition was hiding but selected. Pay attention to where you save the file. It should only be 64 megabytes big. It will be in a weird spot with a hash file and another file but the .win is boot.img. I wish it would have le to me upload the one I made :/

I dunno about that 225 error, we hat else is it saying?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] TamD:
Thank you lifehackerhansol for a great build!​