yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jonpjingleheimler:
I raised my eyebrow a couple times too. I have always gotten great support on XDA. Unless I am asking a dumb question. Wanna know how you know if you are asking a dumb question? Wait a couple days, if you get no response? It's a dumb question, likely researchable and XDA is going to let YOU waste your time figuring it out not there's. I love this site and the decorum here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vegeta2:
Update:

ok if anyone have the same Problem:

https://xdaforums.com/t/recovery-un...laxy-tab-a-10-1-sm-t510.3934805/post-87740573

Flashed Original FW

click until I get to the home screen

Settings: Build Number some times to get Developer mode

Developer mode: Debugging: USB-Debugging = One

insert Calbe, say yes to allow USB debugging

disconnect cable

connected wifi

Rebootet!

get to Developer Options Again, and now there was the Option for Unlocking bootloader!

then unlocked

Recovery

there was the option for long press up for unlocking the bootloader

now flash worked

oO

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

Old:

Hi,

i have the Problem that Recovery cant be flashed, always an error.

i have this:

T510XXU5CWA1

SM-T510_2_20230111191720_hnttj7k1k2_fac

original rom,

this I can flash every time.

my way:

flash original Rom (downloaded with SamFirm_Reborn_0.3.6.3)

Checking firmware for SM-T510/DBT/T510XXU5CWA1/T510OXM5CVG2/T510XXU5CWA1/T510XXU5CWA1

Model: SM-T510

Version: T510XXU5CWA1/T510OXM5CVG2/T510XXU5CWA1/T510XXU5CWA1

OS: R(Android 11)

Filename: SM-T510_2_20230111191720_hnttj7k1k2_fac.zip.enc4

Size: 3418261488 bytes

LogicValue: ob6rd9dli1626z9d

click until I get to the home screen

Settings: Build Number some times to get Developer mode

Developer mode: Debugging: USB-Debugging = One

insert Calbe, say yes to allow USB debugging

disconnect cable

shut down

start download mode (+/-, than cable in, then up)

use Ap and use :

lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.tar.md5

start

if it gets to recovery img it hangs there a long while.

then error:

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin engine v(ID:3.1301)..

<ID:0/007> File analysis..

<ID:0/007> Total Binary size: 2665 M

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

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

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

<ID:0/007> SingleDownload.

<ID:0/007> boot.img

<ID:0/007> param.bin

<ID:0/007> recovery.img

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

<OSM> All threads completed. (succeed 0 / failed 1)

same problem when I try to flash

twrp-3.7.0_11-0-T510XXU5CWA1-20230330.tar.md5

in App

only

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin engine v(ID:3.1301)..

<ID:0/007> File analysis..

<ID:0/007> Total Binary size: 42 M

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

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

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

<ID:0/007> SingleDownload.

<ID:0/007> param.bin

<ID:0/007> recovery.img

<ID:0/007> vbmeta.img

<ID:0/007> RQT_CLOSE !!

<ID:0/007>

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

<OSM> All threads completed. (succeed 0 / failed 1)

any suggestion?

thanks =)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] K-BOX2022:
I have a problem. I cannot boot Lineage Os 20 on GSI. When I enter TWRP the sdcard memory is empty. I tried Factory Reset and Format Data and it did not help. Tablet goes into bootloop with lineage os logo. what is the problem?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DarkSteve:
How big is the card?

I've had issues with large cards. It would recognise my 512GB card sometimes, but usually not. However it sees my 256GB card (and smaller) without a problem.

It could also be a random incompatibility with that brand of card, causing it to be intermittantly undetected - have you tried another card?

(This problem caused me no end of grief last year, resulting in my accidentally bricking my tablet!)

EDIT: Another thought - sometimes partitions aren't mounted properly after flashing. Go into TWRP and check your system partition mount is actually ticked.

EDIT2: Another thought, in TWRP you can "fix context", which has helped me in the past. It's under Advanced.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] masin206:
Hi Everyone! Hope someone can guide me, I have 2 issues

1. I can't install new apps from DE playstore, first time using leneage OS on this tablet is this normal? Seems like it isn't recognizing the storage.

2. Charge is too slow it says almost 16 hours to charge, I am using the original Samsung cable and charger
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] masin206:
OK was able to fix the issue with the charging, cable was bad, still trying to fix the storage issue
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DarkSteve:
This has helped me in the past:

In TWRP, go into "Advanced", then "Fix Contexts". That's solved similar issues for me.

Also in TWRP, go into "Mount", and make sure everything is mounted properly. (This is more of a fix for boot loops, but you never know!)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] masin206:
Thank you for your help, I tried both, but unfortunately it didnt work
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] StarGeneral:
I can confirm that the latest LineageOS-Version behaves exactly like @masin206 wrote. I canot install apps via Playstore since it says "insufficient storage space" - while showing more than 20GB free space.

@Magendanz is there anything known about this error or a possible fix?

I did a clean install of the latest Samsung firmware - reboot - enable OEM Unlock - flash Lineage via Odin.

Edit: "Storage" in settings cannot be opened as well (force-close).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bardmaster:
I have been running the 4/18 Lineage20 with Android 13 for over 2 months now and it is perfectly stable and has good performance. There is ONE nagging thing, though: My Google Chrome will not stay in sync with my Google account and asks me to sign back in. This just means changes to my bookmarks isn't getting updated, but it's annoying. Other Google apps lie Gmail have no issue, and even my banking and investment apps are fine with the platform., so it doesn't seem like it's a security concern related to the platform.

Before I take the leap to Any Yan's next release (currently 5/7), since I'd have to reinstall and re-verify my identity etc., has anybody else run into this and has a solution? Thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] StarGeneral:
I am back to latest Stock firmware now, because the bug mentioned in #134 makes the rom unuseable for me...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AfiqAffandi:
Sir @Magendanz if you have free time you can try the latest build from andy lineage-20.0-20230622-UNOFFICIAL-a64_bgN-vndklite. I have tried factory reset and format data successfully booted into the rom. Can someone else confirm back?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Will do.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AfiqAffandi:
Sorry, wrong quote. Should be a64 not arm64. 😅
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AfiqAffandi:
1. Flash TWRP recovery using odin

2. Enter TWRP > factory reset > format data

3. Reboot

Refer OP here

Edit: LOS19.1 from magendanz already included twrp. Skip to step no.2
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] StarGeneral:
Thank you. Did that -> no change, still "insufficient storage" in Playstore.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AfiqAffandi:
Maybe you can reflashing back from stock firmware.

1. Flash SM-T510_XME_T510XXU5CWA1 firmware using Odin

2. Reboot and finish setup

3. Enter donwnload mode to flash LOS 19.1 Magendanz

4. Reboot to TWRP, factory reset & wipe data

5. Boot up LOS 19.1 and finish setup (no problem with internal and external storage, able to install app from Play Store)

I already reflash my tab just now and everything looks fine.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] memleketim05:
same problem here with 'insufficient storage'

i was on Magendanz's NexusExpreience Rom.

Yesterday flashed newest Oirignal firmware. Did the setup with WIFI connected and was sure, that OEm-Unlock was active but greyed out.

Then flashed newest lineageOS Rom from here with Odin. Again did the Setup with WIFI connected. After the Setup i got the 'insufficient storage' message and thought it was a bug. Then did a Wipe via TWRP and did the setup routine again. But nothing changed.

Am i doing something wrong ?

---- EDIT ----

Working now!

After flashing LineageOS, i also did a format over TWRP where you have to type in 'yes'
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] wesleyhey:
when the bootloader is unlocked it gives you the bootloader is unlocked on every reboot.

When i tried the steps and than tried to lock the bootloader i got a message saying vbmeta mismatch. I also tried to upgrade to andriod 13 and same issue not sure what step I am missing
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
You'll need to revert to a signed OEM firmware release before you can relock the bootloader, and it will do a factory reset.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] wesleyhey:
ok which one do you reload using odian? i tried to load it but than it seemed to just load andriod 11 back on so i must have selected the wring bootloader or AP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Here's where I get the latest OEM release to flash with Odin, but your region may be different. https://samfrew.com/model/SM-T510/region/XAR/
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] wesleyhey:
with odin which one do i select to do the right one? the BL? AP? I have all those files downloaded
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] wesleyhey:
is there going to be a version for andriod 13 / 20
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DarkSteve:
I had exactly the same question back on Magendanz's old 18.1 forum, and one awesome person answered it for me.

Follow that link and read the conversation. (Seriously, read it, the more context you have the better.) I continued to have issues for a little while, but it was all solved and I was able to get back to stock, and then back to LOS18.1.

1. Load the Binaries from Samfw (look for your Firmware and Country!)​

​

AP_T510XXU5CVB1_CL22626479_QB49304683_REV02_user_low_ship_meta_OS11.tar.md5​

BL_T510XXU5CVB1_CL22626479_QB49304683_REV02_user_low_ship_meta_OS11.tar.md5​

CSC_T510XXU5CVB1_CL22626479_QB49304683_REV02_user_low_ship_meta_OS11.tar.md5​

​

2. open Odin and load the images for AP, BL, CSC​

You only need to load those files, not all four. Good luck!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] strikoo:
+1
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ktownmods:
I installed the Rom and ITS really smooth,but i dont have a Gallery App?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DarkSteve:
I prefer my own selection of apps anyway, such as Simple Gallery Pro.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Azerox:
Anyone has a idea what is going wrong? I unlocked bootloader, enabled debugging, accepted my host/pc, went to download mode, odin sees the connection, flash the tar file but when it gets to flashing recovery it takes ages and then after it says failed.

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin engine v(ID:3.1303)..

<ID:0/007> File analysis..

<ID:0/007> Total Binary size: 2665 M

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

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

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

<ID:0/007> SingleDownload.

<ID:0/007> boot.img

<ID:0/007> param.bin

<ID:0/007> recovery.img

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

<OSM> All threads completed. (succeed 0 / failed 1)

Edit: Reinstalled stock, did it all over again and now its flashing. Weird but oke.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DarkSteve:
<snip>

I had exactly the same issue just over a year ago, with the previous LOS18.1 build. I even provided a screenshot that duplicated the error you got.

I managed to brick my tablet, and if you read further down the thread, you'll see it took me a bit longer to figure out how to flash again. There doesn't appear to be any concrete answer, I reinstalled stock multiple times and it didn't fix the issue. I had to tweak other settings and then it worked.

I just wanted to provide a link to my experience so anybody else having the same issue as us won't give up!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Azerox:
Ye softbricked it here as well, easy fix with some tool i already deleted (hijack). I did a new install of the stock rom two times and did all the steps but only after the second time it "accepted" the recovery.img install. Still have no idea because i did the exact same steps as i did the very first time (exept oem unlock, that stays). It works now and runs great, my wife is happy its not that sluggish anymore.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
Is this ROM running smooth on the SM-T510? I have currently the Nexus Stock ROM installed, is after 1 or 2 days slow and have give a reboot to use it normally.

Is it possible to release an update with the latest security patches?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DarkSteve:
Admittedly, I'm currently running version 18.1, but I reboot once every few months. Every couple of days is really unacceptable.

I don't run gapps, though, so I have that going for me, which is nice. I didn't upgrade to 19.1 since it has google's malware built in.

While I'm unhappy with the built-in google spyware in 19.1, Magendanz is really good at what he does. He releases a new build when necessary, and will no doubt release another build if a significant security issue is discovered.

There's no specific schedule for new releases. Keep in mind, there were seven months between the initial and second build, and it's only been four months since the last release. Don't hold your breath for the next one.

But he's giving us this for nothing, and he does provide us updates. I'd say it would be worth switching just so you don't have to reboot every couple of days.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
I switched this weekend to this ROM. It's working great, thank you @Magendanz
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] faheyd:
Came from 18.1 T510. Booted into recovery and installed 19.1. No go, just the smiley face scrolling over and over. Was able to reboot into download mode. Flashed 19.1 with ODIN (said success). Rebooted into now emergency mode. Was able to get back into download mode, used odin to flash recovery, FAIL. Screen on tablet said only official roms (or something to that effect). D/L'd factory ROM and odin flashed fine. However, the Bootloader unlock button was missing. Did update on factory image and low and behold, have bootloader unlock symbol shows up. Reboot into download mode, go to unlock bootloader, all good. Reboot into facotry imaage and boots good (meanwhile I must have wasted hours inbetween getting to the settings so I could verify bootloader was unlocked in setting (got very tired last night and don't know if I'm saying this correctly). Anyway, bootloader unlocked, now to download again. Odin flashed 19.1 and FAIL, even though bootloader unlocked, on the tablet downloader screen, says Official Roms (or something to that effect) only. Somehow ended up in Emergency mode again and was able to get back into download mode using the hold down volume keys again for the millionth time. Flashed latest factory image and booted. Updated image and the unlock bootloader is visible. At this point It was 2AM and I started on this around 10pm with all the updated, flashes, reboots, trying to figure where to go, I GAVE UP. I used 'app control' this morning and just wiped all the apps I could off the samsung image and I'm done. I think in all the posts here some people were missing that there are messages on the tablet when flashing if it fails. I know this rambling and I'm sure you pro's just 'know' where to go, what buttons to push and how to quickly get things into the right position, but I rarely do this stuff and forget a lot between phones and tablets, samsung, LG, OnePlus etc. I wish the ones that this thread worked for good luck and I'm happy for you, but I'm done.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DarkSteve:
Jesus christ dude, paragraphs are your friend. It's incredibly hard to parse such a massive block of text, and the bad grammar and typos didn't help. You should edit your post to put in line breaks where you would naturally take a breath or the focus changes. You could probably clarify a few things while you're at it.

It sounds like you haven't properly unlocked the bootloader, but it could be the result of a dirty upgrade. I bricked my tablet last year by flubbing a dirty upgrade from Magendanz's LOS17 to 18.1. You haven't been clear about what you did to get where you are.

You also haven't been clear about what you're using. Are you using TWRP? Which version? Did you dirty flash, or wipe everything first? WTF is the scrolling smiley face you're referencing? Why would the stock ROM have a bootloader unlock button?

Have another go, break up the brick of text, provide a better explanation of what recovery you're using and how you used it, and FFS get that chip off your shoulder. I don't just "know" where to go, or what buttons to push. I learned the hard way, just like everyone else here. You could learn too if you wanted to.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] faheyd:
On your encouragement, I tried one more time. From a fresh factory load on the tablet, I was able to get the damn bootloader unlocked and actually rebooted normally, instead of emergency mode.

I went to " [GUIDE][SM-T510/T515]Unlock/TWRP/Odin HowTo/Root - Tab A 10.1 (2019) " and followed that. I was able to get TWRP installed and then installed the Multidisabler from TWRP. I did the ' Wipe->Format Data ' . I think this was key for my tablet.

After that, I used ODIN to install 19.1 and booted into (had to hold power down/vol up for while) TWRP and formatted data again and wiped caches, just to make sure.

And to all amazement, Lineage 19.1 booted and I'm configuring as I type.

I hope I never have to go through this again.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] epicguy1:
How do i edit the boot animation please help.

Been trying this for donkeys.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] epicguy1:
Nevermind
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bardmaster:
Hi all, I'm happy to announce the latest version of Andy Yan's Lineage 20.0, dated 8/15/2023, allows you install it directly (instead of the workaround from 19.1 I had posted earlier). Here is the location of the file specific to this thread's Galaxy Tab that worked for me:

https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/lineage-20.0-20230815-UNOFFICIAL-a64_bgN.img.xz/download

So far it has been very fast and responsive.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] djibril13:
I flash it via twrp but can't power off or reboot it goes into twrp and needs factory reset.

Edit: nevermind didnt install multidisable to remove encryption.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] supasibss:
Is this a 64 bit OS or 32 bit? The Exynos 7904 processor in the Tab A supports 64 bit however it has a 32 bit OS; so I was just wondering.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
Did you upgrade (dirty flash) form Lineage 19.1 or clean flash.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bardmaster:
Clean flash

From existing TWRP install:

Hold Power & Vol Up during restart to enter TWRP recovery

Tap Install, Install [system] Image, select your update (.img file), and then swipe to install

Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)

Reboot to system
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jim16127:
@Magendanz​

​

What exactly does the OP do to these lineageOS builds that Andy Yan creates? Does anyone know? I'd like to install this latest rom build but would also like to apply any patches/mods that @Magendanz includes. Would someone be willing to layout a summary? I don't wanna be that "ETA guy". Rather attempt myself while waiting patiently.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
One other thing that I do is rebuild the kernel to revert from Samsung's proprietary FunctionFS implementation of MTP (f_mtp_samsung.c) back to the standard gadget function driver for MTP (f_mtp.c). LineageOS 20 has a new build property setting "vendor.usb.use_ffs_mtp=1" that looks like it's intended to do this without the kernel rebuild, but it doesn't seem to work for me on the SM-T510.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] skills14:
Thanks for your hard work, did you manage to find a fix for the power off issue?

Thanks in advance
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
No, Samsung's LPM implementation doesn't port to newer releases of the OS. My workaround is the off_mode_charge.rc: init file that just does a boot (just like in iOS). Not ideal, but at least it doesn't hang.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
I just released an unofficial build of LineageOS 20.0 (20230815) for the SM-T510 here: https://xdaforums.com/t/rom-sm-t510-unofficial-lineageos-20-0-for-galaxy-tab-a-10-1-2019.4623077/
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
Thanks for the new release.

Can this LineageOS 20.0 dirty flashed over the LineageOS 19.1?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
If you're updating over the latest 19.1 release you should be fine, since they're both based on T510XXU5CWA1. I haven't tested it yet, though. Please let me know how it goes!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
Hereby the confirmation that dirty flash LOS20 over LOS19. 1 is working. Root is still available.

After the upgrade only the homescreen and quick launch bar has been reseted to default.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] stanchankk:
I want to extend my sincere thanks for your hard work; it's truly appreciated. Following the installation of this ROM, I've observed that certain apps don't appear in full screen. Do you have any recommendations for resolving this issue? Additionally, is there a way to adjust the size of the three buttons at the bottom?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
That's really more of a question for the LineageOS 19.1 forum. Have you tried the LineageOS 20.0 release?