[ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510]

robertozombie

Member
Sep 4, 2018
14
0
1
I spent a few days experimenting with this when working on the cold charging fix. While I could get it to boot "normally" when the charger is connected, the kernel was still disabling the touch screen in LPM mode. So, this is possible, but would require kernel modifications. (Note that LPM does bypass the bootloader warning delay, which I'm sure you would appreciate.)
Hi @Magendanz, I was able to modify the lpm file that is inside /system/bin/ with the following code:

Code:
#!/system/bin/sh
su
/system/bin/reboot
and now it boots into android when connecting usb charger and thankfully the touch screen is working as it should :)

The only thing is that I am still getting the bootloader warning delay, do you know why?

Thanks again for your excellent work.
 

robertozombie

Member
Sep 4, 2018
14
0
1
I am having the following wish:

When the tablet is already on but with the screen off, when I connect a charger the screen remains off.
I would like the screen to turn on when connecting a charger, does anyone know what file to edit?

Thanks
 

Magendanz

Senior Member
Mar 25, 2008
667
580
123
Issaquah, WA
www.Vote4Chad.com
New release posted...

Downloads:
Based on LineageOS 17.1:
Build archives:

Change Log:
20201121:
  • Based on latest LineageOS 17.1 GSI build (20201114) with November 2020 security patch.
  • Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
  • Updated to latest stable 10.0 release of OpenGapps Stock variant (20201121), which now includes Google Recorder.
 

pbonamy

Senior Member
Feb 3, 2011
75
10
38
Rouen
New release posted...

Downloads:
Based on LineageOS 17.1:
Nexus_Stock_LQ_T510XXU3BTH4-20201121.tar.md5 (Odin tarball)
Nexus_Stock_LQ_T510XXU3BTH4-20201121.zip (TWRP update)

Build archives:
Android File Host


Change Log:
20201121:
Based on latest LineageOS 17.1 GSI build (20201114) with November 2020 security patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
Updated to latest stable 10.0 release of OpenGapps Stock variant (20201121), which now includes Google Recorder.
It is LQ, is there also a AQ version.
Thanks for the work.
Take care.
 

Crashogre

Member
Sep 25, 2013
12
0
0
I am a little confused. I would like to put in the AQ_T510XXU3BTFN-20200807 build. Do I use T510xxU3BTFN or the T510xxU3BTH4 original stock rom to go from 9 to 10? I am currently running the Nexus stock 16 that you created and enjoy it thoroughly.
 

Magendanz

Senior Member
Mar 25, 2008
667
580
123
Issaquah, WA
www.Vote4Chad.com
I am a little confused. I would like to put in the AQ_T510XXU3BTFN-20200807 build. Do I use T510xxU3BTFN or the T510xxU3BTH4 original stock rom to go from 9 to 10? I am currently running the Nexus stock 16 that you created and enjoy it thoroughly.
Well, both BTFN and BTH4 are Android 10, so you can probably get away with loading either. If you hold on a few days, you'll probably have a BTH4 release of the AQ build, though. I just haven't had the time to get the GSI patches working with the latest AOSP 10.0 build.
 

Magendanz

Senior Member
Mar 25, 2008
667
580
123
Issaquah, WA
www.Vote4Chad.com
Hi @Magendanz, I was able to modify the lpm file that is inside /system/bin/ with the following code:

Code:
#!/system/bin/sh
su
/system/bin/reboot
and now it boots into android when connecting usb charger and thankfully the touch screen is working as it should :)

The only thing is that I am still getting the bootloader warning delay, do you know why?
Yeah, that reboot is going to restart the bootloader regularly, not in lpm mode, and so you'll get the bootloader warning. I was calling class_stop charger and trigger late-init, which didn't cause a restart...but kept the touchscreen (and probably other devices) disabled. Ultimately, I think the best solution is going to be to build a custom kernel that completely ignores lpm mode.
 

djscopesofm

Senior Member
Nov 7, 2009
380
88
0
Merrylands
technofaq.org
New release posted...

Downloads:
Based on LineageOS 17.1:
Nexus_Stock_LQ_T510XXU3BTH4-20201121.tar.md5 (Odin tarball)
Nexus_Stock_LQ_T510XXU3BTH4-20201121.zip (TWRP update)

Build archives:
Android File Host


Change Log:
20201121:
Based on latest LineageOS 17.1 GSI build (20201114) with November 2020 security patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
Updated to latest stable 10.0 release of OpenGapps Stock variant (20201121), which now includes Google Recorder.
Legend!!!
 

inevitable_one

Senior Member
Nov 25, 2014
100
12
0
Breda
Updated two t510 tablets today with
Nexus_Stock_LQ_T510XXU3BTH4-20201121 both are now stuck on the G logo loading screen. First tried the twrp update method then wiped and did odin tarball install with same result.

Anyone have same problem or know what is wrong?
 
  • Like
Reactions: MikePhDPE

lewmur

Senior Member
Apr 30, 2011
1,604
323
103
Updated two t510 tablets today with
Nexus_Stock_LQ_T510XXU3BTH4-20201121 both are now stuck on the G logo loading screen. First tried the twrp update method then wiped and did odin tarball install with same result.

Anyone have same problem or know what is wrong?
What did you have on the tablets before flashing? I was running Nexus AQ from Aug and did a simple clean install from TWRP. Everything works fine.:confused:
edit: BTW, are you certain it is stuck? It takes quite a while to boot the first time. I know mine felt like it was never going to get past the logo, but it finely did.
 
Last edited:

lewmur

Senior Member
Apr 30, 2011
1,604
323
103
@lewmur I was on LQ_T510XXS3ATB4-20200413 before this.
And tablets are trying to boot close to 20 mins now.
You can't go diriectly from ATB4 to the latest Nexus. You first have to flash the latest stock ROM via Odin, then the Nexus ROM via Odin, boot to TWRP and format (FORMAT not wipe) the data partion to get rid of the encryption, and then flash the Nexus ROM again, either via TWRP or Odin.
 
Oct 17, 2017
38
10
8
Hi all,

The AOSP-based NEXUS is working very smoothly on my T510. I managed to root my device with TWRP+Magisk and install NEXUS rom (AOSP variant) on my T510 and set-up my Android back to the way it was before I began this adventure and while the tablet was still on the stock rom from Samsung.

I did encounter something strange recently though, the ANDROID SETUP notification keeps popping up prompting me to finish the setup. I remember seeing this intially after a fresh install of NEXUS rom, but this prompt kept coming back, and engaging in what the notification wanted me to do, which was to complete the ANDROID SETUP, it infinite loops back to the start of the ANDROID SETUP as if nothing took.

My only work-around for this problem is to DISABLE the ANDROID SETUP app altogether. Is it safe to disable this app if my T510 is already setup? Will I need the ANDROID SETUP app for future updates? I had to DISABLE the app because I could not turn off the notification, the radio button that controls the notification for ANDROID SETUP was not responsive.

Please let me know, thanks!
 
Oct 17, 2017
38
10
8
good day.

system ui crashes when I turn on WIFI or BLUETOOTH on the notification bar. any fix guys? thanks
Did you do a clean install or dirty? I did a dirty install and was scratching my head why the local user files were completely corrupted and gabbledegook (such as the Downloads folder being eehfhfhtjfu84747282927576fnvncyy4 for example).

I realized it was because of my dirty install, I did a full wipe of everything except external storage in TWRP, then loaded the rom back into the external storage, and did a clean install and all the strange behavior went away.