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

wantpizza

Senior Member
Nov 3, 2007
81
3
0
Naperville
Alright - this is probably a stupid question but I got really flustered yesterday when things weren't going the right way for me. During which time I downloaded the AOSP and LOS versions of Magendanz's ROMs. I am not exactly sure which one I flashed with ODIN to get to where I am at. Now if I click in Settings/about/Android version... no where do I see something that looks familiar. I am probably missing an easy one here. Oh and - I don't get the Lineage splash inverted smile at boot so - guessing I am on AOSP but.. just a guess.
Thanks a bunch!!!
 

CarinaPDX

Senior Member
Jun 30, 2013
226
71
0
I have been beating my head against the wall for many hours, so now I need some help.

The SM-T510 is upgraded to latest OS, and unlocked, with the warning about non-Samsung firmware on boot. I can get to the download screen either through up-volume+power at startup and then choose bootloader in menu, or by "adb reboot bootloader" from system. So I think the tablet should be ready to take a new ROM. Is there anything else I should check on the tablet?

I started out trying to do the install from Linux but ran into problems with the tools: Odin isn't available for Linux, and I had build errors with Heimdall which may or may not have been the reason it didn't work, and finally while ADB works to find the device and to reboot the tablet fastboot doesn't find the device. For the time being I have given up on the Linux approach.

So I finally got my hands on a Windows 10 machine and installed Odin 3.14.1, both the stock and patched versions from the XDA thread. When trying to flash this ROM it downloaded boot.img, param.bin, then while downloading product.img it came up with "FAIL!" (both Odin versions). So I tried to just install TWRP from another thread (same dev) with Odin and that went boot.img, recovery, FAIL!. ADB worked but not fastboot. Heimdall failed with a libusb error -12.

I am running out of ideas. The tablet was directly connected to a USB port on the relatively new Win10 laptop, which was probably USB 3.0. If it were a USB problem then why would it download some partitions and not others? I could put a USB 2 hub in the middle if that might help...

Any suggestions gratefully accepted.
 

Magendanz

Senior Member
Mar 25, 2008
667
580
123
Issaquah, WA
www.Vote4Chad.com
I have been beating my head against the wall for many hours, so now I need some help.

The SM-T510 is upgraded to latest OS, and unlocked, with the warning about non-Samsung firmware on boot. I can get to the download screen either through up-volume+power at startup and then choose bootloader in menu, or by "adb reboot bootloader" from system. So I think the tablet should be ready to take a new ROM. Is there anything else I should check on the tablet?

I started out trying to do the install from Linux but ran into problems with the tools: Odin isn't available for Linux, and I had build errors with Heimdall which may or may not have been the reason it didn't work, and finally while ADB works to find the device and to reboot the tablet fastboot doesn't find the device. For the time being I have given up on the Linux approach.

So I finally got my hands on a Windows 10 machine and installed Odin 3.14.1, both the stock and patched versions from the XDA thread. When trying to flash this ROM it downloaded boot.img, param.bin, then while downloading product.img it came up with "FAIL!" (both Odin versions). So I tried to just install TWRP from another thread (same dev) with Odin and that went boot.img, recovery, FAIL!. ADB worked but not fastboot. Heimdall failed with a libusb error -12.

I am running out of ideas. The tablet was directly connected to a USB port on the relatively new Win10 laptop, which was probably USB 3.0. If it were a USB problem then why would it download some partitions and not others? I could put a USB 2 hub in the middle if that might help...

Any suggestions gratefully accepted.
If you're getting the warning about non-Samsung firmware on boot, then VaultKeeper has relocked your bootloader. (In many ways it looks like it's still unlocked, but it isn't.) Do a search for how to work around Samsung's VaultKeeper "feature", but you're probably going to have to flash OEM firmware again and repeat the bootloader unlock process, this time not giving VaultKeeper an opportunity to relock it.
 
  • Like
Reactions: AlmostIdiot

CarinaPDX

Senior Member
Jun 30, 2013
226
71
0
OK. Thanks. Will do some research on vaultkeeper, and download the stock ROM from Samsung. At least it looks like Win10 Odin was working, if the tablet was rejecting it, so should go better next time.
 

wantpizza

Senior Member
Nov 3, 2007
81
3
0
Naperville
Hi again,

Lovin this ROM. Very slick and snappy!!

Still wondering which one Iam rocking though. I was having troubles that night.... and now I don't know if I have Aosp or los version.

Oh and - since this identifies as a phone.... you can install whatsapp. I know it doesnt meet their TOS but handy for repair/reflash times for my daily driver cell phone.

Thanks so much!
 

morgads

Member
Nov 30, 2005
9
0
1
relock bootloader?

Thanks for this ROM!

Noob question here: After I unlocked the bootloader to flash I get a warning on every boot saying the device has an unlocked bootloader and that it should not be trusted. Can I enter download mode and relock it with this ROM installed to get rid of that warning? I realize that will factory reset the device, but I believe that is OK.

Thanks!
 

lewmur

Senior Member
Apr 30, 2011
1,604
323
103
Thanks for this ROM!

Noob question here: After I unlocked the bootloader to flash I get a warning on every boot saying the device has an unlocked bootloader and that it should not be trusted. Can I enter download mode and relock it with this ROM installed to get rid of that warning? I realize that will factory reset the device, but I believe that is OK.

Thanks!
No. The only way to relock the bootloader is to revert to the stock ROM. The "nag screen" is just that. It is a meaningless "nag". Makers don't really like it when you take control of your device and get rid of their BLOAT!:(
 

Magendanz

Senior Member
Mar 25, 2008
667
580
123
Issaquah, WA
www.Vote4Chad.com
No. The only way to relock the bootloader is to revert to the stock ROM. The "nag screen" is just that. It is a meaningless "nag". Makers don't really like it when you take control of your device and get rid of their BLOAT!:(
Yeah, I've edited the nag screen down so that it's a little less obnoxious, but to make further changes would require changes to the bootloader, and I'm not willing to risk that.
 
  • Like
Reactions: d4dave

X_Wolverine

Member
Nov 16, 2017
25
8
0
Can anyone confirm after Installing Magisk ..Gps via WiFi location breaks?

I checked pre installing Magisk and post,Google Maps and other apps such as Sygic,Google Earth was unable to get location via WIFI

Satellite GPS gets fixed if I take TAB outside.

Again Thank you for the rocking rom (using based AOSP version as facing instability with Lineage and it has more battery drain compared to AQ and ofcourse Memory card format issue)
 

xincale

Member
Apr 23, 2017
38
2
0
How can I revert to the stock rom with ota updates? :)

Do I need to download the file (right country) from samfrew.com and flash it in odin? And is it normal that the downloadspeed is very slow?
 
Last edited:

xincale

Member
Apr 23, 2017
38
2
0
Hi I'm new to this forum. Today I received my tablet and instantly installed this custom rom. I like this rom very much!
But.. :)
Is there a way to get better sound out of the speakers? Because the Dolby Atmos I tested on stock rom was awesome!
And is there a way to fix the Google search bar bug?
Also in the phh treble settings are there any good things to toggle?
Btw Thanks!
 
Last edited: