yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] No3ight:
Yep,

I tried same GSI with 64svndklite. But I am always facing a bootloop. Is dm-disable-verity also needed with official GSI?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alecxs:
afaik yes except devices with DSU support. did you flash vbmeta_disabled.img?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] No3ight:
This has nothing to to with dm-verity? Where can I find a device specific vbmeta?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alecxs:
that's avb. not device specific, you can hexpatch yourself, patch with Magisk, create with avbtool.py or generate from shell

https://xdaforums.com/showthread.php?t=3924856
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] No3ight:
Okay, will give this a try tomorrow. I am wondering cause someone in this thread told he has successfully booted GSI on sm-t590
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alecxs:
I don't think this device has vbmeta partition as no one mentioned in this thread
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] No3ight:
Strange things is that it once booted up and worked fine with AOSP 12.0. I not really sure how the exact procedure was...

But I think I had stock and TWRP. Also Magisk with patched boot. I will give this a try and let you know.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
LineageOS 18.1 64-bit version works on our device with vendor libs from Galaxy A20s and a few more modifications.

Geekbench multi-core almost doubled compared to 32-bit systems. :cool:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] xd_@:
hello all,

on my t590 is running crdrom-v315+220220-a64-bgZ.img with deleting the two files as mentioned in #82 I can also lock the tablet! But what still makes problems is the wifi the mac address is generated after each reboot and I have constantly wifi tearing --> does anyone have an idea how I can fix this yet
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] russanandres:
hello, i have a couple of questions. I translated the text with the help of a translator, sorry for possible language errors in the text.

1. Is there any way to set a screen password? Maybe there are special programs?

2. Did LinageOS 19 start correctly?

3. What exactly doesn't work in LinageOS 18.1?

4. How to cleanly install 18.1/19? According to the instructions in the header or is it not suitable for these versions?

Thanks in advance.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alecxs:
@russanandres sorry for confusion, we are drifting discussion off-topic.

This thread is for LineageOS 16 / 17.1

common sense in xda is, only install ROM with state stable on your daily driver

Version Information

Status: Stable

regarding screen password - if you refer to lock screen bug reddit post #82 - that applies to rooting and is caused by Magisk. wait for a flashable.zip that will fix it, investigation is ongoing...

(or do you ask about encryption/secure start-up? password can be changed with vdc cryptfs or this app - soon even along with TWRP)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] russanandres:
Sorry. The header has not been updated for a long time, and the last 2 pages discuss 18.1 and 19.

Maybe someone needs to create a thread discussing 18 and 19 LOS?

It seems to me that this device (my version of t595) does not have firmware that is fully working. Even the instruction in the header says that I can’t set a password, but I need it(. Somewhere in a parallel thread I was told that you can delete 2 files and the password will work, but the MAC address will be unstable and the Internet connection is sometimes lost(.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] russanandres:
Hi again. I set myself LOS 18.1, could you make an instruction on how I can replace the libs to get a 64-bit system?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Hey!

I might open a new thread later with the modifications if I can fix the remaining bugs.

Basically you will need to extract the /vendor/lib64 folder from the firmware of Galaxy A20s (more specifically the A207FXXU2BUD4 version), modify default.prop and build.prop on the tablet's vendor partition with adding 64-bit CPU ABIs, also a 64-bit compatible kernel is required which is available for SM-T590 here: https://github.com/UDPSendToFailed/sm-t590_kernel_caf

I guess some changes are needed for the kernel to work on SM-T595 because of the different hardware, LTE modem, etc.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] No3ight:
Hey there,

is there a fix for stereo audio right now?

Thanks in advance!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] russanandres:
Hello! Try switching:

Settings ---> PHH Treble Settings ---> Qualcomm features ---> Use alternative audio policy

AND settings---> PHH Treble Settings ---> Samsung features ---> Use alternative audio policy ; Enable stereo audio mode.

But the problem is, as soon as there is silence (speakers turn off?), then the sound becomes mono, and you need to switch again Qualcomm features ---> Use alternative audio policy:(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] No3ight:
Hey,

thank you for your fast replay. I saw that there is a more recent version of mine. I am actually on lineage_treble_a64_bvS 20220120.182016. Are you facing the same issues with the latest build of LOS 18?

Have you also tested AndyYans build of LOS 19?

THX
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] russanandres:
Yes, I tested it, and in no case do not test it yourself. Even if it seems like it will pass you by. After installing LOS 19 and rebooting into recovery, you can only watch how TWRP tries to boot unsuccessfully. Odin mode, system - forget it. You won't be able to boot.

Sorry to bother again, but how exactly?:)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Already found a better solution thanks to AndyYan. While the device is stuck on TWRP screen, connect it to a PC, open a command prompt with adb and run:

adb shell

rm /data/system/storage.xml

reboot

Then it should boot into TWRP without issues.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] russanandres:
Oh no. My notebook (windows 10) and my PC (ubuntu 21.10) says device offline(. adb kill-server is not helpful.

nevermind

Thank you a lot! You are my savior)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dafunky:
Hello, I followed the OP instructions twice, each time the TWRP flash fails with this log :

<ID:0/003> Firmware update start..

<ID:0/003> NAND Write Start!!

<ID:0/003> SingleDownload.

<ID:0/003> recovery.img

<ID:0/003> RQT_CLOSE !!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

Then on reboot I can't reach the recovery with POWER+UP (not surprising) and the tablet takes 4mn to boot to the system showing the welcome screen.

Before all, I enabled the developper options then triggered the OEM Unlock. This forced me to make a factory reset, so I did. Since this factory reset, the "OEM Unlock" option in the developer options had disappeared.

I flashed the last official Firmware (2021/11) with success then it failed on the TWRP step.

On the DOWNLOAD MODE it is written

FRP LOCK : OFF

OEM LOCK : OFF

I don't understand what's wrong. I made the procedure twice.

EDIT : when I try to flash again and again I sometimes get the message

<ID:0/006> Firmware update start..

<ID:0/006> NAND Write Start!!

<ID:0/006> SingleDownload.

<ID:0/006> recovery.img

<ID:0/006> FAIL! (Auth)

EDIT 2 : I've read "somewhere on the internet" that samsung firmwares after 2018 don't propose the OEM Unlock anymore... But you would have warned people here if it was true for the 590.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
I'm not entirely sure but seems like you aren't using the patched Odin version from the first post.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dafunky:
The OP link is dead, I used these links to get a working patched Odin.

I just tried again with Odin3 v3.13.1_3B_PatcheD and Odin3-v3.14.1-3B-PatcheD , still the same problem.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
That's weird, it works fine for me with v3.14.1

Try reinstalling Samsung drivers in the device manager, use different USB port and cable. I had some connection problems too when I used an USB hub.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dafunky:
I just flashed a stock 2020 ROM and restarted the procedure.

Exact same result.

I noticed that when I fail flashing the TWRP recovery, this messages appears in red on the bootloader screen on the tablet : Only official released binaries are allowed to be flashed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Oh that makes sense. Have you connected the tablet to WiFi after the initial OEM Unlock and factory reset?

If I recall correctly I had to enable OEM Unlock again after performing the factory reset while having the tablet connected to WiFi. If the OEM Unlock option doesn't appear, try manually changing the date on the device 7 days forward.

Fix Missing OEM Unlock Toggle on Samsung Galaxy Devices (Guide)

Are you facing the missing OEM unlock issue on your Samsung Galaxy device? That’s because your phone has entered the Prenormal RMM/KG state. However, if you’d like to bypass it, then you can follow…

www.thecustomdroid.com
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dafunky:
Thank you for the PRENORMAL RMM tip, I could finally flash TWRP. Then I followed your advice + the procedure here : https://xdaforums.com/t/howto-sm-t5...vent-bootloop-magisk-gapps-safetynet.4403687/

But now I get bootloop. I flashed lineage-18.1-20220414-UNOFFICIAL-arm64_bvS-vndklite.img , and all went (including Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip , gapps nano and so on).

Except one thing : when I trigger the "resize partition", I get an error. I then go to "repair partition" -> success then "resize partition" -> success. But the tablet bootloops. I did the complete procedure twice, including flashing stock ROM. Did I miss something?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Yep, the issue is that you use arm64 version on stock vendor. Stock vendor is meant to be used only with a64 (arm32_binder64) ROMs since it's missing 64-bit libraries and a 64-bit compatible kernel which are required for arm64.

If you want to stick with stock kernel and vendor then you'll need an a64 GSI like this one: https://sourceforge.net/projects/an...4-UNOFFICIAL-a64_bvS-vndklite.img.xz/download

If you want to run 64-bit systems then you can follow the instructions in my thread with skipping the LineageOS installation part and using your previously downloaded lineage-18.1-20220414-UNOFFICIAL-arm64_bvS-vndklite.img instead.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dafunky:
Thank you very much for your patience. I'm getting crazy, still boot loop. Following your advice, I downloaded the

a64_bvS-vndklite.img of your link instead of the arm64_bvS-vndklite.img one, I did flashed everything from start : flash the stock rom, fix the PRENORMAL RMM problem again, flash TWRP, follow the procedure to the letter (start TWRP, wipe, reboot TWRP, wipe, flash, blablah).

Once again the resize step gives the red error :

/sbin/e2fsck -fp /dev/block/mmcblk0p41 process ended with ERROR : 1

Unable to repair System.

When I see this message I make "repair file system" -> OK, then "resize file system" -> OK, the summary gives :

Size : 3572Mb

Used : 1214Mb

Free : 2357Mb

Backup Size : 1214Mb

Then reboot system -> bootloop

I can still access TWRP recovery and download mode, fortunately.

EDIT : I don't know which you refers to by saying "the instructions in my thread". I'd prefer to stick with stock kernel and vendor. I need to switch to a Android 11 ROM or this tablet gets useless for me.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
The resize succeeded according to the output so the error shouldn't really matter.

What kind of bootloop do you get? Does it show the Lineage logo or is it stuck at the Samsung screen? If it's showing the Lineage animation, have you tried removing keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw?

As for my thread I meant I have some SM-T590 modifications in another thread to make it run 64-bit ROMs but if you don't care about the CPU performance then it's better to stay on stock kernel & vendor.

Edit: Btw, if you don't make modifications to the boot or vendor partitions then you don't have to reflash stock every single time in order to install GSI ROMs.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dafunky:
IT FINALLY WORKED, see bottom of the message

It bootloops on the SAMSUNG GALAXY start logo. On the boot screen I can read a yellow text : "Set Warranty Bit : kernel"

I just made a complete cycle STOCK -> TWRP -> lineage-17.1-20200808-UNOFFICIAL-treble_a64_avN.img

Still the same bootloop problem, still the same red message when resizing the SYSTEM partition.

Since this morning I tried with two STOCK firmwares, the last one (2021/11) and an older one (2020/6). Same problem each time.

I flashed the following images :

lineage-17.1-losfe-a64-bvN-vndklite.img

lineage-17.1-20200808-UNOFFICIAL-treble_a64_avN.img

lineage-18.1-20220414-UNOFFICIAL-a64_bvS-vndklite.img

lineage-18.1-20220414-UNOFFICIAL-arm64_bvS-vndklite.img (the bad ARM64 one)

lineage-19.1-20220410-UNOFFICIAL-a64_bvS-vndklite.img

From now I stop flashing stock firmwares as you confirm it is useless, it is a relief.

EDIT : I can read some debate about Magisk that may be required for the first boot. I never flashed magisk in my tests. I just tried but no more luck.

EDIT 2 : it finally worked

.

I can't explain why as I did the same previous procedure once again. The only difference is that after flashing MAGISK (see previous EDIT) I got the usual bootloop, then I went back to TWRP, I flashed lineage-18.1-20220414-UNOFFICIAL-a64_bvS-vndklite.img again, this time the "RESIZE SYSTEM" didn't make an error, then everything went smooth.

Thank you thousand time to @UDPSendToFailed for your help and patience.

EDIT 3 : Now I have the "just a sec" bug, stuck on the welcome wizard.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Glad you figured it out, I haven't had problems like that, maybe because I'm using a newer TWRP build.

Yep that's happening on a wide range of ROMs, even on my non-GSI 19.1 build, I just restart it until it goes through.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dafunky:
Well, I thought I wouldn't bother you anymore, but it seems like I'm cursed. I have rebooted about 30 times, trying all scenarios : simple restart, factory reset, with/without gapps nano, with/without wifi, flash dm_verity and magisk again, factory reset again, and so on... Still stuck on "Just a sec..." screen.

@UDPSendToFailed do you know an alternative ROM to Lineage OS in Android 11 proposing a64 compatibility? For instance Havoc, I don't see A64 + VNDKLITE (I don't know what VNDKLITE mean). https://xdaforums.com/t/11-official...m-a64-a-ab-ab-vndklite-gapps-vanilla.4076903/
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
Here is a list of GSI ROMs: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

You can use the ones with binder (which means a64) compatibility.

Can you upload the output of adb logcat -d > logcat.txt?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dafunky:
Many thanks for your help, I wouldn't have succeeded without you.

This morning I tried Havoc with no luck, this afternoon I read your message, I tried LeOS-R-RW-a64-bvN and it finally worked.

Index of /downloads/LeOS-R-GSI

EDIT : I'm going crazy, now I can use the tablet but I can't add a google account. Nothing happens. By the way, do I still need to flash dm_verity... after flashing this kind of roms?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] UDPSendToFailed:
LeOS is an ungoogled ROM, check the first post here: https://xdaforums.com/t/aosp-11-0-2020-11-27-leos-ungoogled-gsi.4195571/

It's for use without any Google Play related software.

I think you can skip that since it modifies the boot partition which is usually not affected by GSI flashing.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] russanandres:
Hello everyone again. I flashed crDroid 8.5 (A12L) and repaired TWRP following the UDPSendToFailed instructions. But after restarting, it loads to the lock screen for a second and gives a bootanim. Almost bootloop. Can this be fixed, or is there no access to a working TWRP and A12L together?

UPD.

I think that /data/system/storage.xml should not be deleted. It must be renamed or moved, and before exiting TWRP, return everything back. But at the current moment I can not check, only in the evening.

UPD. 2

Flashing the same system image to the old one, without formatting, did not help.(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ZONTAC:
Deleted
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dogo_shiva:
Heyho

First: big thank you to you guys doing all the modding here.

Second:

I try for 2 days now to flash LineageOS to my SM-T595. I got rid of the RMM/KG issue and managed to install TWRP. I followed the exact procedure mentioned here in the first post. My device ended up in a boot loop as described now:

Power On -> Samsung Galaxy Tab Screen -> Display Turns Off -> Vibration and Black Display -> Display Turns Off -> Vibration and Samsung Galaxy Tab Screen -> Display Turns Off -> Vibration and Black DIsplay......and so on.

I tried method of extracting the boot.tar from an original ROM and flashed that with ODIN. I restarted the whole procedure with the exact same result: above mentioned bootloop.

I tried another method mentioned here in this Thread ( https://xdaforums.com/t/howto-sm-t5...vent-bootloop-magisk-gapps-safetynet.4403687/ )

I did a full recovery with unpatched ODIN to latest Stock ROM I downloaded with Frija. Went through the RMM/KG **** again and installed TWRP again.

I skipped LineageOS 16 and went full for 18.1 a64_bvS_vndklite. After installing the image to System partition I flashed Disable_Dm-Verity and Magisk 24.1. The tab started now behind the Samsung Tab Screen and got stuck at the LineageOS animated logo. After about 40 minutes I rebooted to TWRP, cleared dalvik/cache and did a reboot. Still the same, it gets stuck at the Lineage animation.

I got a few error messages when flashing the zip files: failed to mount ODM partition. But in the execution log it said ODM mounted and a few lines later ODM unmounted. But at the end there is a red warning stating failed to mount ODM partition.

Does someone on here have any Idea why it would not work? Any help is appreciated.

**EDIT**

Nevermind. Got it. I used the files from another post and they worked. Guess these in here are outdated?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ZONTAC:
I have tried 5-6 different gsi of android11 in my t595 but every gsi have Volte issues , is there any fix for gsi(other than phh setting and fix gsi module of magisk as they are not working ) or any other gsi which have working Volte
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Bigdrago:
Why use this instead for the original one?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jpmaas:
Can you tell me, where you get the files from, i have the same issue.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] foxspirits:
idk if its becase im sm-t597p but after i got pass the first install and all fallowing it to at it put me into a boot loop
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] foxspirits:
same thing is happening to me
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] foxspirits:
how do you do this?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Arnav/n:
the links are taken down please help
[Google Pixel 3 XL Questions & Answers] Nayr438:
Im trying to figure out why there is a notch in the corner and if anyone else has experienced it. Its Factory image and you can see it during boot with the google logo as well. Its the same color as the notch outline and just looks like the notch cutout rotated at the edge of the screen. Corner notch is off in dev menu.

Guess I can post links to a picture or upload it.
[Google Pixel 3 XL Questions & Answers] bobbyphoenix:
https://9to5google.com/2018/10/29/pixel-3-xl-second-notch-bug/
[Google Pixel 3 XL Questions & Answers] Nayr438:
The only difference is, Instead of being rotated 90 degrees its more like 45 and pushed in the top right corner and it doesn't go away with a reboot. It may be related to the same bug though, hopefully it gets fixed soon and its not something hardware related.
[Google Pixel 3 XL Questions & Answers] crixley:
I bet you have corner notch turned on in developer settings
[Moto Maxx General] ktmom:
If you are reading this it's because you are using an application.

This thread redirects to: https://xdaforums.com/google-nexus-...lease-read-t2500184/post46847787#post46847787
[Touch Diamond, MDA Compact IV ROM Development] TwiterZX:
bonjour, je vous propose un thred pour parler des ROM francaises, si qq'un a une ROM en fr, merci de l'uploader et de donner les impressions..

cordiallement
[Touch Diamond, MDA Compact IV ROM Development] MonteCristoffOn:
In english please...

Hi TwiterZX,

And welcome on board...

1. You should write in english

2. You should read a little more...French Diamond

Thanks.

;)
[Touch Diamond, MDA Compact IV ROM Development] leflavorflav:
Salut,

Tous le monde ne maitrise pas l'anglais, très chère MonteCristoffOn.

Alors un peux de souplesse, il n'est pas interdit de s'exprimer dans une autre langue que celle de Shakespeare pour participer à ce forum !!!!!!

VIVE LA FRANCE
[Touch Diamond, MDA Compact IV ROM Development] geek78:
salut

il se trouve que c'est forum anglais... il te faut donc faire comme tout le monde, faire des efforts ou utiliser un traducteur en ligne... Sinon il existe des forums français où tu trouveras des infos de ce type. Lorsque on est sur des forums français on accepte assez rarement des gens qui ne font même pas un effort pour utiliser le français et là c'est la même chose... il n'y a rien de méchant ou d'anti-français, c'est tout simplement un forum anglais sans section en langue étrangères...

@+

So Please, only english....
[Touch Diamond, MDA Compact IV ROM Development] MonteCristoffOn:
Keep it cool

No offense or any lack of courtoisie in my words, my dear, but if you don't practise english, I'm not sure it's the good place for you...

The least would be to translate, and I think it can be a good way to learn WWE, isn'it ?

You already know that there are a lot of french forums if you want to read and write in Molière's language ;)

Anyway, you're welcome here as well !

;)
[Touch Diamond, MDA Compact IV ROM Development] spfrance:
If you're searching for a good french speaking forum : http://forums.smartphonefrance.info/

Si tu recherches un bon forum qui cause la france : http://forums.smartphonefrance.info/

Enjoy your day ;)
[Touch Diamond, MDA Compact IV ROM Development] leflavorflav:
bonsoir,

Et bien vous aurez malheureusement droit à une mauvaise traduction google, j'espère qu'il n'y aura pas de quiproquo de traduction.

Allons !!!!!, parlons anglais.

good evening,

And you will unfortunately be entitled to a bad translation google, I hope there will be no misunderstanding of translation.

Let !!!!!, speak English.

;):)
[Touch Diamond, MDA Compact IV ROM Development] Dj!pOner:
Dommage je trouvait l'idée d'un topic FR pratique car il est vrais que des fois l'anglais et moi sa fait deux...:(

Même si il est vais que que l'on se doit d'écrire en anglais... De plus c'est écrit dans les règles (il me semble...)

;)
[Touch Diamond, MDA Compact IV ROM Development] OvationAcoustic:
MAIS BUT !

Why not french CE OS 20755 traduction for DUTTY and SWOS PANOSHA ect ... ect ... :( I'm very TRISTE !!! ... AND the BEST and HIT of the "dernière" version !!!! IT'S HERE !!!! I'm French ! I cry !