• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 18.1

Search This thread

Sift

Senior Member
Apr 20, 2016
70
7
Sepang
Xiaomi Mi Pad 4
Xiaomi Mi A2
Yes, that's to be expected.
Well that settles it then.

To note I do encounter something. Before this I installed Magisk and Swift Installer. Must be something Swift Installer messed up or something and my tab kept rebooting every 1 or 2 minutes even after uninstalling both Magisk and Swift Installer. Booted back into TWRP and wipe data. Now I'm not rooted and tab is working fine.

Just something to mention. I can live without both of the apps mentioned.

Thanks for the wonderful rom, now my tab works fine.
 

agreenbhm

Senior Member
Jun 14, 2010
208
112
USA
Samsung Galaxy S21
Well that settles it then.

To note I do encounter something. Before this I installed Magisk and Swift Installer. Must be something Swift Installer messed up or something and my tab kept rebooting every 1 or 2 minutes even after uninstalling both Magisk and Swift Installer. Booted back into TWRP and wipe data. Now I'm not rooted and tab is working fine.

Just something to mention. I can live without both of the apps mentioned.

Thanks for the wonderful rom, now my tab works fine.

The reboot thing happens if you mess with some root binaries on the device (and possibly other things). If you install Magisk use the fix script in the OP to make it work without causing the reboot issue. For theming, there is built in stuff within the Phh settings app that will hopefully cover what you wanted to do with Swift.
 

Sift

Senior Member
Apr 20, 2016
70
7
Sepang
Xiaomi Mi Pad 4
Xiaomi Mi A2
The reboot thing happens if you mess with some root binaries on the device (and possibly other things). If you install Magisk use the fix script in the OP to make it work without causing the reboot issue. For theming, there is built in stuff within the Phh settings app that will hopefully cover what you wanted to do with Swift.
Did the fix script before installing Swift Installer and still happened. I'm not too bothered by not having root so it's fine.
 

Mogster2K

Senior Member
Jun 25, 2011
342
65
Is it necessary to flash vbmeta_disabled_R.tar to use TWRP? I tried flashing it directly on an already-rooted (stock) system, but when I tried to make a backup I got the createtarfork() error.
 

agreenbhm

Senior Member
Jun 14, 2010
208
112
USA
Samsung Galaxy S21
Is it necessary to flash vbmeta_disabled_R.tar to use TWRP? I tried flashing it directly on an already-rooted (stock) system, but when I tried to make a backup I got the createtarfork() error.

If you were booted into TWRP then the problem isn't vbmeta. Try saving your backup to an SD card instead of internal storage. I'm thinking perhaps the encryption of the internal storage is causing your error.
 

lewmur

Senior Member
Apr 30, 2011
1,858
400
adb root
adb shell
cd /data/data/com.google.android.gsf/databases
sqlite3 gservices.db
select * from main where name = "android_id";
That worked for getting the number and I used it to register. I no longer get the constant nag and setup is now restoring apps from a google backup, but I still can't run Play Store. That still pops up the screen saying Play Protect isn't certified. But if I tap play.google.com on that screen, Play Store opens. I guess I can live with that.
 

agreenbhm

Senior Member
Jun 14, 2010
208
112
USA
Samsung Galaxy S21
That worked for getting the number and I used it to register. I no longer get the constant nag and setup is now restoring apps from a google backup, but I still can't run Play Store. That still pops up the screen saying Play Protect isn't certified. But if I tap play.google.com on that screen, Play Store opens. I guess I can live with that.
Give it a little time and a few reboots. Eventually it goes away.
 
  • Like
Reactions: Annonnimmouss

lewmur

Senior Member
Apr 30, 2011
1,858
400
Installed Magisk and ran the fixes script. Got an error on the rm line saying no such file but the tablet seems to be running ok. Have root and brightness control.

edit: there is a /system/xbin/su file but no /system_root directory. Should I delete the /system/xbin/su file?
 
Last edited:
  • Like
Reactions: Annonnimmouss

agreenbhm

Senior Member
Jun 14, 2010
208
112
USA
Samsung Galaxy S21
Installed Magisk and ran the fixes script. Got an error on the rm line saying no such file but the tablet seems to be running ok. Have root and brightness control.

edit: there is a /system/xbin/su file but no /system_root directory. Should I delete the /system/xbin/su file?
Don't delete anything or you risk causing it to randomly reboot.
 

lewmur

Senior Member
Apr 30, 2011
1,858
400
Yea, I'd go that route. Data secured with file based encryption is not something that has a clear way to access via TWRP. I tried looking for solutions on multiple occasions but haven't found anything yet.
On the T510, formatting the data partition got rid of the encryption and installing custom ROMs left it unencrypted.
 

agreenbhm

Senior Member
Jun 14, 2010
208
112
USA
Samsung Galaxy S21
anyone managed to get play store to let them sign in? my t500 keeps saying device not certified even after registering it and leaving it over night, have tried multiple reboots as well?
Try wiping data for the Play Store and Google Play Services. You may need to register again after that, but it definitely should work. I've done it several times with this device during development.
 

lewmur

Senior Member
Apr 30, 2011
1,858
400
anyone managed to get play store to let them sign in? my t500 keeps saying device not certified even after registering it and leaving it over night, have tried multiple reboots as well?
Before it started working without the not certified screen, I was able to get in by clicking on the play.google.com link on that page.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    When u register ur device wait for 5 min and restart the tablet and clear data in playstore and play service👌
    Perfect, thank you very much! It worked!
    1
    Hey, could you tell me how you got the certification fixed? i registered the device manually, but still it won't work.
    When u register ur device wait for 5 min and restart the tablet and clear data in playstore and play service👌
    1
    Hi, first : sorry my bad english! i'm a french noob.
    Second : a great congratulation for your hard work. I have tried your rom on my device. it's wonderful! After format and wipe, SD is ok. But the Wifi is allways over! with the first rom or the sacond one! What can i do for that? Thanks for yours helps!
    best regards from France!!
  • 17
    Update 9:46am EST July 15 2021: new builds of TWRP and LineageOS with TWRP touch fixed and LOS w/ space for Gapps is now live.

    WARNING: USE AT YOUR OWN RISK.

    I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.

    Here are the steps to follow:
    1. Update your device to the latest stock ROM (as of this writing) either using the built-in system updater or via Odin. You want the build that ends with "3BUF3".
    2. Unlock device bootloader using instructions from other threads. This will wipe your device.
    3. Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
    4. Boot device back into download mode and flash TWRP via Odin in the "AP" slot. If you boot up into the stock ROM rather than booting directly back into download mode then go through the initial setup process of the stock ROM and enable developer tools and ensure OEM Unlocking is still enabled (VaultKeeper can possibly undo OEM Unlocking if you get to the ROM but don't go into Developer Tools and view OEM Unlocking is enabled, so make sure to do this).
    5. Boot device into TWRP (recovery mode) and format (not wipe) your data partition. Then reboot back into TWRP.
    6. Push LineageOS (super.new.ext4.img) to device. Ideally push it to an SD card formatted with ExFat or EXT2/3/4 (FAT/FAT16/FAT32/VFAT won't work due to file-size limitations).
    7. Install LineageOS image to "Super" partition. Make sure to select "Install from Image" in order to show .img files in the install selector screen.
    8. (Optional) Push NikGapps Omni to your device and install the zip. Make sure you include a "nikgapps.config" file in your "/tmp" folder that is configured to install to "system" rather than "product" or "default".
    9. Reboot to system. You should now be in LOS with Gapps.
    10. (Optional, but recommended): Install Magisk via TWRP
    11. (Optional, but recommended): Run fix script to fix brightness slider not working and to make Magisk work. If you didn't install Magisk but only want the brightness fix, just enter "n" when prompted in the script. To run the script:
      1. NOTE: Script has .txt file extension to allow hosting on AFH. Remove that so it's just .sh to match the instructions below.
      2. Download and push to device when booted into TWRP
        1. adb push sm-t500_fixes.sh /tmp
      3. Enter an adb shell
        1. adb shell
      4. Change directories and set permissions
        1. cd /tmp
        2. chmod +x /tmp/sm-t500_fixes.sh
      5. Run script
        1. /tmp/sm-t500_fixes.sh

    Tips:
    • If you are not seeing all of your storage space in the OS on the internal flash, boot to TWRP and format data.
    • Flash TWRP via "AP" slot and flash VBMeta_Disabler via "Userdata" slot in Odin.
    • Flash LineageOS as an Image, not as a Zip.
    • For Gapps, use the latest NikGapps for ARM64 and Android 11/R.
    • For Gapps, make sure you install to the System partition and not Product. To do this you need to slightly modify a nikgapps.config file. Instructions on that can be found on the NikGapps site.

    Downloads:
    Known Issues:
    • OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
    • Brightness controls don't work: Fixed via "sm-t500_fixes.sh script.
    • TWRP touch screen doesn't work (use USB keyboard or adb). Should be fixed with TWRP Beta 3.
    • TWRP formatting external SD card may hardbrick device. Do not do this! Fixed with TWRP Beta 2.

    Source (device tree for TWRP from my Github): https://github.com/agreenbhm/android_device_samsung_gta4lwifi
    Source (kernel sources from Samsung): https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
    7
    Good news, my tablet should be back on Tuesday and I will be looking at continuing my dev work then.
    3
    I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.

    Here are the rough steps to follow:
    1. Unlock device bootloader using instructions from other threads.
    2. Patch stock ROM (AP) using Magisk, then flash rooted ROM. Will likely need to wipe device after this.
    3. Boot into rooted ROM and ensure "OEM Unlocking" is still enabled in "Developer Tools".
    4. Boot back into download mode and flash "vbmeta_disabled_R.tar" to disable verified boot.
    5. Boot device back into rooted stock ROM to ensure things are still functional (may require a device wipe at this step).
    6. Boot device into download mode and use ODIN to flash TWRP recovery.tar file via "AP" slot.
    7. Boot device into TWRP to verify functionality (hold Vol-Up + Power during boot).
    8. Access TWRP via adb using "adb shell" or with USB mouse (touch functionality currently not working).
    9. Format data partition on device.
      • Via ADB shell: twrp format data
      • Via USB mouse: Wipe -> Advanced -> Format Data
    10. Boot device into download mode.
      • Via ADB shell: twrp reboot download
      • Via USB mouse: Reboot -> Download
    11. Flash LineageOS tar file via ODIN using the "AP" slot.
    12. If device boots into TWRP after flashing LineageOS, use USB mouse to select: Reboot -> System
    13. Device should boot and stall for ~1m at the Samsung logo screen with red text below, then should go blank and then display LineageOS boot image.

    Downloads:
    Great news!! But I think you need to post it in the ROMs, Kernels, Recover thread.
    3
    Any new release of twrp
    I made a new build yesterday however I can't test it yet since my device is not back to me yet. If you want a copy to try dm me and I will share it. But be warned, I don't even know if it boots (though you could always reflash the old one if that's the case). The goal of the new build was to fix the SD card bug and make the touchscreen work.
    2
    Just tested your Beta2 of twrp (something that I usually don't do) and touch is working. MTP is not working; as I have a "working" (no decryption) twrp from quite some time if you share your source I may can help you (if you're interested).
    I have no intention on sharing builds or getting too much involved here on xda.. I own this device from a week before lockdown ended, I've managed to make a "working"ish twrp-3.5.1 and lineage-17.1 recovery (with fastbootd). Then I've started again to work so I've dropped the project to port LineageOS.. but if you're willing to share your source I may can help iron some bugs when I have time.
    Didn't test your Lineage build (maybe I will), I still have to update to official 11 firmware.
    Thanks for the reply. The sources can be found on the Github repo I made, which is here: https://github.com/agreenbhm/android_device_samsung_gta4lwifi.

    My Lineage build consists of the 18.1 Lineage GSI as the system partition along with stock vendor, odm, and product partitions within the super image.