[ROM][SM-T510][UNOFFICIAL] LineageOS 18.1 for Galaxy Tab A 10.1 (2019)

[dadmi]

That seems quite obvious. So on the download page there are different versions for Android 11. I assumed the one with 11.0 in the filename was the right one. But it should be the latest? I'll try when back at home...

@spezialzt mentioned version MindTheGapps-11.0.0-arm-20220217_095902.zip earlier in the thread which didn't work for me. Let me know if it works for you.

 

[Skyfire1]

So none of the mindthegapps versions are flashable for me.
Open Gapps will install (arm, not arm64) but then I'm told not play protect certified. And It is not possible to setup a Google account so no playstore for me. Quite possible that I dont need gapps at all but I'm curious what's wrong...
I'm sure I'm doing something wrong...but what is it exactly?

 

[spezialzt]

So none of the mindthegapps versions are flashable for me.
Open Gapps will install (arm, not arm64) but then I'm told not play protect certified. And It is not possible to setup a Google account so no playstore for me. Quite possible that I dont need gapps at all but I'm curious what's wrong...
I'm sure I'm doing something wrong...but what is it exactly

Already told you and Others. It only has to be a arm Not arm64...

 

[Skyfire1]

Already to and Others. It only has to be a arm Not arm64...

Your post does not help in any way, why don't you just take a look at the screenshot that I posted earlier. When trying to flash mind the gapps the installer states that this package is for arm64 but your device is arm 64. And when trying to flash the non 64 version it says the package is for non 64 but device is arm 64. So something is clearly wrong.
If you have a working version why not just tell us which one it is?
The soc is 64 capable but is the rom a 64 version?

 

[spezialzt]

Your post does not help in any way, why don't you just take a look at the screenshot that I posted earlier. When trying to flash mind the gapps the installer states that this package is for arm64 but your device is arm 64. And when trying to flash the non 64 version it says the package is for non 64 but device is arm 64. So something is clearly wrong.
If you have a working version why not just tell us which one it is?
The soc is 64 capable but is the rom a 64 version?

The solution was posted several Times in this Thread!
I pointed to a working gapps Version and a way to Install gapps cleanly.
The whole 64bit soc vs rom topic was answered before.

Read the Thread!

Whats wrong is your Attitude!

 

[Skyfire1]

The solution was posted several Times in this Thread!
I pointed to a working gapps Version and a way to Install gapps cleanly.
The whole 64bit soc vs rom topic was answered before.

Read the Thread!

Whats wrong is your Attitude!

maybe you should check your attitude, if you find the time while being busy patting yourself on the shoulder,,,

 

[spezialzt]

maybe you should check your attitude, if you find the time while being busy patting yourself on the shoulder,,,

mkay, so if your faulty installion is still Given. How can i support you with a recommendation ragarding a working version... when simply speaking every working version wont work with your handset?

Okay again...
your CVB1 device needs:
lineage-18.1-20220417-UNOFFICIAL-T510XXU5CVB1.zip

checked Gapps:
MindTheGapps-11.0.0-arm-20220217_095902.zip
open_gapps-arm-11.0-mini-20220503.zip
open_gapps-arm-11.0-pico-20220503.zip
open_gapps-arm-11.0-nano-20220503.zip
open_gapps-arm-11.0-aroma-20220503.zip

If you have a faulty installion the twrp install process will tell you something funny like you have expierienced.(CANT INSTALL ARM64 ONTO ARM64) yadda yadda.

Open Gapps will install (arm, not arm64) but then I'm told not play protect certified. And It is not possible to setup a Google account so no playstore for me. Quite possible that I dont need gapps at all but I'm curious what's wrong...
I'm sure I'm doing something wrong...but what is it exactly?

So you even had Gapps installed and still complaining.. you had alot of popups, right?
In order to make Gapps work you need to Factory Reset your Device after the installation. otherwise it wont work!
After this you can boot like usual and register your device ID here: Register

 

[Skyfire1]

OK,
I apologize I didn´t mean to be so salty!...

So the rom is flashed in odin and works fine for me.
It is the version you posted above.
Befor flashing it I flashed newest ( cvb1 ) samsung stock rom because I had a very old rom , not cvb1, before.
Now ,as for the other user as well, the gapps that work for you cannot be flashed. Open gapps is flashable but with warning that the the device is not play protect certified and so I can´t set up a google acount. No playstore for me.
Maybe there is something wrong with my tablet but I guess we´ll never know.
Only thing I can try is to flash the rom from TWRP. Maybe that changes something.

 

[spezialzt]

OK,
I apologize I didn´t mean to be so salty!...

So the rom is flashed in odin and works fine for me.
It is the version you posted above.
Befor flashing it I flashed newest ( cvb1 ) samsung stock rom because I had a very old rom , not cvb1, before.
Now ,as for the other user as well, the gapps that work for you cannot be flashed. Open gapps is flashable but with warning that the the device is not play protect certified and so I can´t set up a google acount. No playstore for me.
Maybe there is something wrong with my tablet but I guess we´ll never know.
Only thing I can try is to flash the rom from TWRP. Maybe that changes something.

Im sorry too, stopped smoking some days ago and im on the edge of my seat all day!

however, back to your problem. Stick to the ARM(32) version. you sir have a totally diffrent problem.

1.) get yourself this beauty. it will show and copy your "android device id"

2.) register your "android device id" here at google

3.) Reboot and grab some sandwich.

 

[dadmi]

Im sorry too, stopped smoking some days ago and im on the edge of my seat all day!

however, back to your problem. Stick to the ARM(32) version. you sir have a totally diffrent problem.

1.) get yourself this beauty. it will show and copy your "android device id"

2.) register your "android device id" here at google

3.) Reboot and grab some sandwich.

Thank you for these details. I couldn't find the version of open gapps you mentioned but was able to install this version open_gapps-arm-11.0-nano-20220215.zip and registered device Id with google to sign in to play store.

 

[DarkSteve]

I suspect the problem above is that you didn't first flash the T510XXU5CVB1 OEM firmware before flashing the custom ROM. There is no dirty flash support from Lineage 17.1 to Lineage 18.1.

I need some advice. I accidentally dirty flashed Lineage 18.1 over 17.1, and even worse, I used a machine that didn't have the Samsung drivers installed. It soft-bricked my T510. (I'm going through chemotherapy, and my mind was not clear at the time. I won't make the same mistake again!)

The Samsung load screen is no longer there, I'm instead getting a "nexus" logo (with a coloured "x"). I've never seen the nexus logo before or used a nexus rom. I'm positive I used a Lineage rom I got from your androidfilehost account.

I used the advice you gave to others to get into download mode and reinstall twrp, but I can't install 18.1 at all, and 17.1 installs but sits forever in the Lineage boot animation. LOS16 installed, but internal storage is not available, among other buggy behaviour.

I assume I should flash a stock rom to recover from the damage I did. I downloaded a 2019 stock rom from Samfrew, but I'm not sure how to use it. The zip contains four md5 files:

• AP_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship_meta_OS9.tar.md5
• BL_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship.tar.md5
• CSC_OMC_OLM_T510OLM1ASEF_CL15874928_QB23938566_REV02_user_low_ship.tar.md5
• HOME_CSC_OMC_OLM_T510OLM1ASEF_CL15874928_QB23938566_REV02_user_low_ship.tar.md5

I'm using Odin3 v3.14.1_3B_PatcheD. I assume I add the file starting "AP" to the AP section of Odin, and the "BL" file to the BL section, but what about the other two? There are two CSC files and only one CSC section.

When I tried flashing just the BL and AP files, the BL flashed but the AP failed. Should I use a different stock rom?

I'm not sure what to do next. Any suggestions? I promise not to flash anything while mentally unfit!

 

[dadmi]

I need some advice. I accidentally dirty flashed Lineage 18.1 over 17.1, and even worse, I used a machine that didn't have the Samsung drivers installed. It soft-bricked my T510. (I'm going through chemotherapy, and my mind was not clear at the time. I won't make the same mistake again!)

The Samsung load screen is no longer there, I'm instead getting a "nexus" logo (with a coloured "x"). I've never seen the nexus logo before or used a nexus rom. I'm positive I used a Lineage rom I got from your androidfilehost account.

I used the advice you gave to others to get into download mode and reinstall twrp, but I can't install 18.1 at all, and 17.1 installs but sits forever in the Lineage boot animation. LOS16 installed, but internal storage is not available, among other buggy behaviour.

I assume I should flash a stock rom to recover from the damage I did. I downloaded a 2019 stock rom from Samfrew, but I'm not sure how to use it. The zip contains four md5 files:

• AP_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship_meta_OS9.tar.md5
• BL_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship.tar.md5
• CSC_OMC_OLM_T510OLM1ASEF_CL15874928_QB23938566_REV02_user_low_ship.tar.md5
• HOME_CSC_OMC_OLM_T510OLM1ASEF_CL15874928_QB23938566_REV02_user_low_ship.tar.md5

I'm using Odin3 v3.14.1_3B_PatcheD. I assume I add the file starting "AP" to the AP section of Odin, and the "BL" file to the BL section, but what about the other two? There are two CSC files and only one CSC section.

When I tried flashing just the BL and AP files, the BL flashed but the AP failed. Should I use a different stock rom?

I'm not sure what to do next. Any suggestions? I promise not to flash anything while mentally unfit!

You need to install factory ROM T510XXU5CVB1 and not use Home_CSC. Use the other CSC.

 

[DarkSteve]

You need to install factory ROM T510XXU5CVB1 and not use Home_CSC. Use the other CSC.

Thanks for the quick reply, dadmi.

I'm in Australia, is that rom still appropriate? I thought getting an old (AU) rom might be better, but I'll look for T510XXU5CVB1 now on Samfrew or Sammobile or something, and I won't use the Home_CSC.

But I won't be flashing tonight, I don't want to make things worse. (It's after 1am here and I don't trust myself anymore!)

EDIT: Ah, I found it on Samfw, and I can choose the Australian region (XSA). Over 3GB. I was worried newer stock roms would include security that would stop me installing Lineage again, but everyone with a clue is saying T510XXU5CVB1, so I trust you know what you're talking about

 

[spezialzt]

However i have another issue @Magendanz
Everthing works Like a charm. However compared to your other Rom the audio Volume is silent and Missing some decibel.

Fixed it with V4A magisk module, just had to put the Legacy Option in it. Together with mxplayers hw+ mode the volume is Loud enough for daily business.

Is there a way to "rename" the device? In Linux/Win its listed as PHH Treble?

 

[AfghanBoy1]

can't install gapps in this rom
MindtheGapps gives me error 1 in twrp.
opengapps gives play protect certified error...

back to nexus Rom.

 

[dadmi]

can't install gapps in this rom
MindtheGapps gives me error 1 in twrp.
opengapps gives play protect certified error...

back to nexus Rom.

Check post 590 how I was able to resolve the play protect error.

 

[5innl05]

Hi Guys,
first, many thanks to Magendanz for the New Release 20220417.
I installed your release 20220417 over the 20210526.
After that, I forgot to "Format Data", cause incremental update.
Now my Tab is in a boot loop, which seems to be to short in time to respond on holding the power button.
So my Tab is rebooting without responding to any action.
Is there any other solution than waiting till the battery is drained?

 

[spezialzt]

I installed your release 20220417 over the 20210526.
...
Is there any other solution than waiting till the battery is drained?

Hi,
first of all you had to flash a vannilla CVB1 rom. and then flash the lineage-18.1-20220417-UNOFFICIAL-T510XXU5CVB1. between major versions this is my approch for updates.

secondly, yeah there is a way. its listed somewhere here in the thread. TLDR You need to time your key combination or write yourself a simple script to do so.

Have a nice day.

 

[Suji2k]

Any guide to install custom rom on sm-t510, from unlocking bootloader?

 

[spezialzt]

Any guide to install custom rom on sm-t510, from unlocking bootloader?

No worries, we are a helpful bunch. However First of all i need to be certain you met the requirements! Are you able to read?

For ****s sake read the First Post.

Friendly greetings me, still Not Smoking.