yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zippy Dufus:
Greetings! ... Some questions

Hi everybody.

I'm interested in purchasing this tablet and the version available in Canada (Best Buy, Costco) is SM-T510NZDAXAC.

So I have some questions:

Will this ROM work on it? (I see T510XXS3ATE3 embedded in the ROM's file name which doesn't match above.)

If so, and I manage to root and install it, I would like to build it myself and hack with different compilers, etc:

I see several source trees each with a manifest, is there a single, consolidated local_manifest.xml available?

Are there any hints or tricks that I need to know?

I've successfully built for other Samsung devices not referenced in my signature below but they all had a single manifest which adapted well in my build environment on a Fedora 32 virtual machine.

In advance, thanks!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Downloads:

lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN.tar.md5 (Odin tarball)

lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN.zip (TWRP update)

Build archives:

Android File Host

Change Log:

20200812:

Based on the latest build of LineageOS 17.1 GSI (20200808) with August 2020 Security Patch.

Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sharkfins0up:
Downloading this now. Thanks

2 biggest issues are live display not working and the random reboots. Fingers crossed they go away
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jean_C:
After flashing this my tablet seems to be stuck in a bootloop or something. I had an existing twrp install someone else did for me with this rom. As per instructions i only flashed the zip, then rebooted. For 3 hours the LO logo kept playing. Rebooted with powerdown/volumedown but same issue. I'm not at ease with the tablet, i'm used to have an sd card for LO so i can wipe everything and now i have to be carefull not to do that,

Any suggestions please?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
Did you install the latest firmware before flashing last release?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jean_C:
Sh*t no I didn't. Didn't know it was required, can you point me to some instructions please? At the moment i can't get into twrp it seems.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
Flash with Odin on PC.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
I believe this is because you need to upgrade to Android 10 using the OEM firmware first. Dirty flashing usually only works for incremental updates.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jean_C:
Hi Magendanz,

I don't understand, i was running the previous version of this rom which is android 10. Someone unlocked the bootloader for me, couldn't do it myself with this knox stuff, so now im a bit unsure about it all. First i will figure out how to flash the firmware back.

ps, did you see the logact i posted?

LineageOS Version: '17.1-20200713-UNOFFICIAL-'
Build fingerprint: 'samsung/gta3xlwifixx/gta3xlwifi:9/PPR1.180610.011/T510XXS3ATE3:user/release-keys'
Revision: '4'
ABI: 'arm'
Timestamp: 2020-07-13 14:29:49+0200
pid: 3863, tid: 3863, name: wifi@1.0-servic >>> /vendor/bin/hw/android.hardware.wifi@1.0-service <<<
signal 35 (<debuggerd signal>), code -1 (SI_QUEUE), fault addr --------
Abort message: 'attempted to close file descriptor 11, expected to be unowned, actually owned by DIR* 0xec645000'
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
The previous version was an Android 10 GSI running on Android Pie vendor and boot partitions. The T510XXU3BTFN OEM release has Android 10 vendor and boot partitions, and you really need to do the full OEM update in Odin (BL, AP & CSC) prior to flashing any custom ROM.

Yes, and this logcat tells me the new Android 10 vendor partition is having trouble launching the WiFi service, most likely because some device tree (DTB) or firmware update for the WiFi chipset hasn't been applied.

I just reinstalled the lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN.zip TWRP update on my test tablet, and it's working just fine. You need to be installing it over T510XXU3BTFN, though.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sharkfins0up:
I used to have T713 and when they switched I used this guide: https://xdaforums.com/tab-s2/general/guide-update-firmware-using-heimdall-t3957645

I think you only need to flash a few files rather than the entire Samsung ROM: sudo heimdall flash --SBL1 sbl1.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --HYP hyp.mbn --SEC sec.dat --KEYMASTER keymaster.mbn --CMNLIB cmnlib.mbn --DSP adspso.bin --MODEM modem.bin --APNHLOS NON-HLOS.bin

Hopefully it's the same here
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jean_C:
Does it matter which language firmware you download? I downloaded T510XXU3BTFN from 2020-06-30 Netherlands language.

Flashed with odin AP BL CSC, i had a working tablet.

Then flashed lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN.tar.md5 rebooted but LO does not start, keeps displaying it's logo animation.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Did you format the userdata partition in TWRP? The LineageOS 17.1 build can't deal with OEM file-based encryption.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jean_C:
I can't recall reading about formatting that partition, so no, i did not. :(

And after installing the samsung rom there is no TWRP, so i have trouble understanding what to do sorry.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] desidero:
Try this as mentioned in the first post:

Instructions:

From OEM stock firmware:

...

Hold Vol Up & Vol Down buttons during restart to enter Download mode

Install custom ROM tarball (.tar.md5 file) to AP with Odin

If TWRP launches, factory reset with Wipe->Format Data and reboot to system.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jean_C:
Thanks that worked, i'm now on the 20200808 version, no playstore / magisk, guess i have to flash those separately.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] desidero:
Exactly

https://opengapps.org/

https://github.com/topjohnwu/Magisk/releases
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
My Nexus Stock custom ROM has the Google apps and a few other tweaks like Pixel Experience, based on your choice of LineageOS 17.1 (LQ) or AOSP 10 (AQ). This is just the plain LineageOS 17.1 build.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jean_C:
I know. I've been reading that thread and gonna finish reading it, then flash that rom. I've also saw you mention you prefer that rom. It seems more convenient, and hopefully less reboots. Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
Install Twrp with Odin.

I have installed the Netherlands firmware and working fine.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Jean_C:
I have succesfully installed Nexus_Stock_LQ_T510XXU3BTFN-20200812.tar.md5, all went without a hussle. I like google voice working, finally someone who listens to me. Thanks people for the help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] danielmm1997:
Hi all,

i already flashed this Rom on one Galaxy Tab i use and it worked.

But currently i am stuck. I do not know what i am doing Wrong.

I tested to install the Rom now on three different Devices now and they are all Stuck at the Linage OS Boot Logo.

What ive done:

1. Opened a new Device.

2. The Firmware on the Device is Android 9.

3. Unlocked the Bootloader

4. Flashed the Linage OS Rom with Odin.

5. Go to TWRP deleted Data --> Installed the multidisabler --> Factory Reset

6. Rebootet

Does someone what i am doing wrong?

EDIT:

I downloaded the latest Samsung Firmware and flashed it before with Odin now it is working *-*
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] danielmm1997:
Since i updated to T510XXU3BTFN i am not able to change the bootscreen with the param.bin anymore. Do you know how to fix this?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
No, I don't. I've asked in other forums, too. Strangely, changes to svb_orange.jpg are being picked up just fine, but not logo.jpg.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] piro.lito:
Hi Guys,

i'm using adb and fastboot to try to run a command.

With ADB the device is recognized, but with FASTBOOT (after: adb reboot bootloader) it won't recognize any devices?

Do you have the same issue? Any tip to overcome this situation?

PS: I'm on Windows 10 x64
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Samsung uses Odin and not fastboot. Don't expect any fastboot commands to work.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] piro.lito:
[MENTION=903232]Magendanz[/MENTION] does the boot.img file has the init.rc file?

I was trying to do change it using the Adnroid Image Kitchen tools to do this:

Drag-and-drop boot.img to unpackimg.bat.

Open ramdisk/init.rc

Search for on charger and add at the end (after write /sys/class/power_supply...):

setprop ro.bootmode "normal"

setprop sys.powerctl "reboot"

So it would turn on when the charger is connected, can you give me a patched boot.img with this implemented?

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] danielmm1997:
Hi

i also needed the Autoboot Feature. This is what i did:

## 3. Setup Autoboot on Charger
1. Enable Developer Options in the Device Settings
2. Open CMD in Windows
3. Run the following commands
1. `adb devices`
2. Always Allow the Connection the the Device (automatic prompt)
3. `adb root`
4. Go to the Device Developer Options and enable the Root option
5. `adb root`
6. `adb remount`
7. `adb shell`
8. `su`
9. Press `Allow` on the Prompt on the Device
10. `cd /system/bin`
11. `echo /system/bin/lpm > /system/bin/lpm.bak`
12. `nano lpm`
13. Paste the following into the Interface
```
#!/system/bin/sh
# Enable kernel commands.
su -c "echo 1 > /proc/sys/kernel/sysrq"

# Send an immediate reboot request.
echo b > /proc/sysrq-trigger
```
14. Save the file with CTRL + X --> y --> Enter
15. `reboot`
4. Remove the Charger
5. Shutdown the Device and plug in the Charger
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] piro.lito:
How do you have nano installed?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
First of all, there's no more ramdisk. They killed that back with system-as-root. The init.rc is in the system root and a full boot from charger mode can be signaled using the sys.boot_from_charger_mode property, but that still won't prevent the kernel from disabling the touchpad. That's the more difficult fix.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] danielmm1997:
Is already installed
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] danielmm1997:
15. `chmod 755 /system/bin/lpm`
16. `chown 0:2000 /system/bin/lpm`
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sharkfins0up:
76 hours uptime and counting. Whoohoo

But still no live display unfortunately
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yeah, I asked [MENTION=4467696]AndyYan[/MENTION] and he was also coming up blank on how we might fix that. I suspect it's a problem for everyone running the LineageOS 17.1 GSI.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Zippy Dufus:
SM-T510 hardware variants?

Hello (again),

A question - Does the T510 Tab A (2019) have multiple hardware variants or will this ROM work on all such T510 devices?

Specifically, I am considering purchasing the Canadian SM-T510ZKAXAC model and want to be sure that this ROM will work on it.

In advance, thanks.

== // ==

I originally asked this question plus some other questions in this prior post and have since being doing a lot of research.

However, I am still not sure whether there are multiple hardware variants of the T150 or is it just the in the firmware. It isn't very clear to me yet the naming convention of Samsung devices and firmware. "XAC" means Canadian, that much I figured out.

My Galaxy Grand Prime SM-G530W has many different hardware variants and corresponding ROMs as designated by the training "W".

It is fascinating to see how much has changed with building Android ROMs since I last built one. The "GSI" concept (Generic System Images) is indeed fascinating.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
The only hardware difference is in the amount of RAM and storage. The hardware is the same for different countries. Only the firmware changes for the CSC/HOME_CSC modules.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sharkfins0up:
Thanks for all your work on this Magendanz. I would not have bought this tablet but for custom ROM support. I cannot stand manufacturer UIs

Does your NEXUS rom support livedisplay? I think I'll migrate over if it does. I think it's better being baked in than using the Twilight app
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
No, the LQ variant of the Nexus Stock custom ROM is based on this same LineageOS 17.1 build, so it has the problem too. The AQ variant is based on AOSP 10.0, which doesn't have the Live Display feature.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Geek_Ceará:
Try this: With the tablet still connected - do not disconnect the cable, close or reset Odin - restart in download mode again. It is possible that the rom will install normally after that.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] riverstyxxx:
As usual, Magendenz never fails to disappoint. The latest build (20200812) causes the tablet to get stuck on the loading screen for twenty minutes. This is his second os I've had issues with, the other being the previous lineageos for this tablet. Don't know why they continue to let this guy be on here because it's obvious he doesn't test anything. You can force a shutdown by holding volume down + power for five seconds. Use your micro sd card then go to the build archive and revert back to the previous version (20200713). Booted to the os within 10 seconds after doing so.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Did you update to the new Android 10 OEM release (T510XXU3BTFN) before you flashed this custom ROM?

From the OP...

Notes:

Custom kernels are specific to OEM releases, and this one is based on the new Android 10 release (T510XXU3BTFN).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] henworth:
I may be having this same issue, although it’s been booting for about 30 minutes now. Went from stock Android 9 as the OEM build of 10 is not available in the US, apparently.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, you can't install custom ROMs built for Android 10 on Android 9. You need to do a full OEM upgrade to Android 10 first. While the US OEM firmware hasn't yet been posted, the UK version works just fine.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] henworth:
Ah, ok, that certainly explains it. Appreciate it, been a few years since I’ve messed with flashing ROMs. Assuming I can use Odin to flash those OEM bits on to it in its current state, rebooting to download mode of course.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yep, you should install all parts (BL, AP & CSC) in Odin, just to ensure you get the new partition table.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] themace51:
incremental upgrades

Hey, i have the 20200713 version on my tablet, and i tried to do incremental upgrade to 20200812 via twrp.

It just loops for me. Do i need to flash the new official T510XXU3BTFN Samsung firmware , and redo twrp etc? do not really want to lose my stuff if i do it this way.

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, please see above and OP. You can't flash custom ROMs build for Android 10 (T510XXU3BTFN) on previous releases that were based on Android 9. The new OEM vendor partition and kernel are incompatible. And yes, flashing T510XXU3BTFN in Odin will do a factory reset, so you'll need to restore from a backup in the cloud.

UPDATE: Apparently, someone figured out how to do the Android 10 upgrade without the factory reset. Some basic instructions are here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Suzook1:
I have an app that needs a 64bit OS to operate. (DJI Fly) I know Samsung is supposed to upgrade the SM-T510 wifi sometime in September to Android 10 but I dont want to wait. Is this a 64bit OS?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] waterpolo:
Unfortunately not 64 bit. It's already Android 10.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] peking12:
FDE

This Full Disc Encryption problem is driving me crazy!

I get this errormessage when trying to encrypt my tablet:

I've tried to reduce the /data partition with 16 KB, but that didn't help at all.

I've also tried to encrypt the the tablet using the stock ROM and then try to install Lineage without formatting the /data partition. Nothing helps.

Does anyone have a clue how to solve this?

Btw, thanks alot for the work with the ROM!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Rand Brittain:
Hm, I hadn't realized the Pie firmware wasn't out for the USA region yet. Maybe it's better to wait for it before I start using a custom ROM?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] klemen241:
i installed new updat, its for italy, and its not 64bit -.- samsung sux, ill never buy their tablet again
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
It isn't for Italy. Are you incapable of doing something as simple as changing the lanquage on the first screen? And, no it is NOT 64bit. If you needed 64bit and were silly enough to buy a tablet without checking, then its your own fault.:p
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] klemen241:
first learn to read please. I installed rom for italy, because they first got the update. And i didnt say anything about italian language. Second, they promised 64bit update, even t580 has custom rom 64bit. So yea, before attacking, read it again :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I can read very well, thank you. You can change the default language no matter what ROM you install. The ROM people have linked to in this thread is the BTU version from the UK. When you first boot it, it is in Italian. But you can easily change it to the language of your choice. I don't know what "they" you are referring to but it certainly wasn't Samsung. Samsung has never even mentioned 64bit in reference to the SM-T510. Samsung promised to upgrade to Android 10 but made no referrence to 64bit. As to custom 64bit ROMs on the T580, they ARE NOT true 64bit either and won't run 64bit only apps. Maybe it is you who needs to learn to read.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] klemen241:
hahahahaahah i literarly installed 64bit games on my old t580 with 64bit rom. So if you didnt own it and try it, dont comment please :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Aguamandan:
You sure about that? My T510 was Pie before, and this 17.1 lineageOS installed easily. And the tablet confirms it is 10 now. I didn't know that was an issue, so I just did it.

However, It does have its share of problems, and I'd like to revert back to stock or similar for now. Can you point me in the right direction? This is my first experience flashing a custom ROM, and I'm really not sure how to reverse the process. I appreciate whatever help you can provide.

---------- Post added at 10:29 PM ---------- Previous post was at 10:10 PM ----------

Naw, did that. Didn't work. LOS still thinks the card is corrupted, though everything else I have reads it fine. Sucks. Same with my other cards.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Have you tried installing the Infinity kernel?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andreapier:
I know this is a dumb question but... How do I exactly enter recovery after I flash the ROM from Odin? If I press Power + Volume Up nothing happens.

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rw_on_xda:
Hallo

I'm thinking to buy an SM-T510 (even since I found this thread/ROM), but one question: is the display sharp/good enough to read ebooks on it ?

---------- Post added at 22:51 ---------- Previous post was at 22:49 ----------

a wild guess: keys need to be pressed/held when the device is OFF
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I use mine to read for hours at a time. I go through several books every week. But then again, I've used much cheaper tablets than this for reading and I've never found reading to be a challenge for any of them.:confused:

edit: I just opened my reader and reduced the font size down to the smallest size possible and the type was still very clear.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rw_on_xda:
[MENTION=4034185]lewmur[/MENTION]

thanks for lightning fast response !
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] xdaM:
Given that this latest version now uses the Q kernel on all images, can I update the ROM seamlessly through TWRP or do I have to reflash everything/something in Odin? (I'm still on the July version with Pie firmware)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Phk:
Fantastic work, thanks for this
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rw_on_xda:
got my T510 yesterday with last stock installed.

Today I tried to install LOS on it, but without success - so far -

I always get "Custom Binary (Boot) Blocked By OEM Lock" even if "OEM unlocking" is ON in the dev options.

Idea's ?

additional notes:

to enter Download Mode holding Power and Vol up + down doesn't work for me.

I need to press Power and Vol up, then choose "Reboot to bootloader" to get Download Mode.

Is this new ?

my fault ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] elliwigy:
hold both vol buttons while powered off and plugging in
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rw_on_xda:
Thanks, got this already this early morning from comment #40, Page 4.

with that I was able to flash LOS, but it seems it stucks in some sort of a loop. I waited ~ 20 minutes, then I stopped that boot.

somewhere I read to "reset to factory defaults" just after flashing, but how ?

Do I need to wait longer after successful LOS flash ?

It seems this device is some sort of tricky:

- usual I see "OEM unlocking"

- but sometimes not ( (sometimes) fixable via an internet connection mentioned by [MENTION=903232]Magendanz[/MENTION] somewhere in this thread, keyword "hybrid state" or the like)

- sometimes greyed out, but enabled

- it seems there are "two" download modes with stock rom:

1. power +vol up => gets to stock recovery => boot to boot loader = download mode

2. vol up+down and usb plugging => vol up (long/short) => download mode

:confused:

what key to press after vol up+down and usb pluging in ?

short vol up or long vol up

it's not that clear to me !

how to enter recovery after LOS flash ?

I feel I'm just a few steps away from successful flashing LOS, but need to find out the right combination of that steps ... :cool:

===

correction to my prev. post:

Power and Vol up+down gets me *sometimes* to an sort of "safe mode" ( faded in in the lower left screen corner) and boots to graph. env. when stock rom is installed.

Is this everywhere the case ?