[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)

[agreenbhm]

Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release was Android 10-based). I have attempted to make this install as painless as possible. Please read the notes below carefully. WARNING: you are responsible for your own actions, so please be careful. If you brick something, that's on you.

1. Update to latest stock ROM as of 3/24/2022 (T500XXU3BVB3).
2. Unlock bootloader using steps described in this thread. Make sure that after your device wipes and reboots after the bootloader is unlocked that you go through the setup wizard again and back into Developer Settings and enable OEM Unlocking. I think you need to connect to wifi for this option to appear, so if you don't see it try that.
3. Boot to download mode, then install VBMeta Disabler via Odin.
4. Reboot to download mode, then install TWRP via Odin.
5. Reboot to download mode again, then install LineageOS via Odin.
6. Boot to TWRP, push "fix_brightness.sh" to the device and run it, then format data.

That should be all that is necessary. If you get stuck in a loop with TWRP where you can't boot to system (seems to happen regularly to me) I included a script in TWRP that should get you out. From the TWRP cli run the command "exit_twrp". It will say "out of space" when finished (instantly). Then reboot to system. If for some reason that still doesn't work and you boot back to TWRP, repeat.

Known Issues:

• OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
• TWRP touchscreen seems to be unresponsive for several seconds upon first booting into TWRP. Just patiently wait a few seconds and try again.
• You'll see errors in TWRP about /keyrefuge, etc. Ignore that. I believe it's related to the inability to decrypt internal storage using FBE.
• Installing Gapps (Nik and Flame) doesn't work, but no worry because the ROM includes Gapps
• Security: by default this ROM has root access and USB debugging (adb) is enabled unsecured. Anyone can plug into it and have full root access. So disable USB debugging if you don't want that! TWRP is the same way, though data is encrypted. Someone could install malware into your system partition though. In short, this is for hobbyists, not someone with security concerns.

Sources:

• Device tree for TWRP from my Github; branch TWRP-11 specifically: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
• Kernel sources from Samsung: https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#

Files:

• LineageOS 19.1 Beta2
• TWRP 3.6.1 Beta 5
• VB Meta Disabler
• Brightness Fix

Updates:

• You can update this ROM yourself by installing a new GSI to the system partition.
  • Download new GSI from here onto Micro SD card: https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
  • Boot into TWRP
  • Run command: blockdev --setrw /dev/block/mapper/system
  • Run command: dd if=/external_sd/<your_downloaded_gsi.img> of=/dev/block/mapper/system bs=1M
  • Wait for dd command to finish, then reboot into system. Don't forget to use "exit_twrp" command if you keep booting into TWRP.

 

[torekiki]

Thanx! I must flash gsi via Odin over AP?

 

[agreenbhm]

Thanx! I must flash gsi via Odin over AP?

If by GSI you mean the Lineage .tar file I linked to, then yes. That particular file is more than a GSI, it is a super partition including the GSI, vendor, product, and odm partitions. Flash this via Odin to AP and in the future you can install standalone GSIs of Lineage using TWRP with the instructions at the bottom of the post.

 

[lewmur]

After formatting data, tablet just keeps booting to TWRP. Won't boot to system.

 

[agreenbhm]

After formatting data, tablet just keeps booting to TWRP. Won't boot to system.

Read the op. I specifically address this.

 

[hakkers420]

Hi thanks for all your work. Question , I do step 3 successfully and it boots to OS, but step 4 when I try to install TWRP it fails and when trying to boot I get error "Only official released binaries are allowed to be flashed(vbmeta)" and I need to reinstall stock OS for it to boot again. Any Suggestions what I may be missing or doing wrong?

 

[agreenbhm]

Hi thanks for all your work. Question , I do step 3 successfully and it boots to OS, but step 4 when I try to install TWRP it fails and when trying to boot I get error "Only official released binaries are allowed to be flashed(vbmeta)" and I need to reinstall stock OS for it to boot again. Any Suggestions what I may be missing or doing wrong?

When you do step 3 and boot to the os make sure you verify that bootloader unlock is still enabled in Developer Options. If it is, I suggest reinstalling stock and then starting over.

 

[hakkers420]

When you do step 3 and boot to the os make sure you verify that bootloader unlock is still enabled in Developer Options. If it is, I suggest reinstalling stock and then starting over.

When I check OEM Unlock it's selected to ON its 'greyed out' bootloader is already unlocked.

 

[agreenbhm]

When I check OEM Unlock it's selected to ON its 'greyed out' bootloader is already unlocked.

Good, that's what it should be. Try reflashing the vbmeta disabler again and then flashing TWRP.

 

[hakkers420]

Good, that's what it should be. Try reflashing the vbmeta disabler again and then flashing TWRP.

So I tried that but it fails in Odin.


<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 0 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> vbmeta.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

 

[agreenbhm]

So I tried that but it fails in Odin.


<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 0 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> vbmeta.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I know I ran into this once the past few days but am having difficulty remembering exactly how I resolved it. I think your best bet is to start from scratch, reinstalling stock and doing a factory reset.

 

[hakkers420]

I know I ran into this once the past few days but am having difficulty remembering exactly how I resolved it. I think your best bet is to start from scratch, reinstalling stock and doing a factory reset.

Thanks will give it another shot see what happens.

 

[hakkers420]

On the page for unlocking bootloader that you provided are you supposed to do all 7 steps or can I just do up to step 3 and not worry about 4-7?

 

[agreenbhm]

On the page for unlocking bootloader that you provided are you supposed to do all 7 steps or can I just do up to step 3 and not worry about 4-7?

Correct, you can stop after 3.

 

[hakkers420]

Figured it out, before step 4 boot to OS and reenable developer options and USB Debugging.

 

[hakkers420]

Correct, you can stop after 3.

Now step 6 when trying to boot to TWRP it boots to the stock recovery for some reason. I think I may have to take a break for a bit.


edit: after a break and a reinstall of twrp all seems to be good now

 

[Noskilldode]

If by GSI you mean the Lineage .tar file I linked to, then yes. That particular file is more than a GSI, it is a super partition including the GSI, vendor, product, and odm partitions. Flash this via Odin to AP and in the future you can install standalone GSIs of Lineage using TWRP with the instructions at the bottom of the post.

I am a huge fan of GSI but doesnt realy understand what it is and how to use it ( this isnt my first account just forget my pw XD) so it would be a pleasure for me if you would write a few words about it thanks in advantage :_)

 

[Noskilldode]

Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release was Android 10-based). I have attempted to make this install as painless as possible. Please read the notes below carefully. WARNING: you are responsible for your own actions, so please be careful. If you brick something, that's on you.

1. Update to latest stock ROM as of 3/24/2022 (T500XXU3BVB3).
2. Unlock bootloader using steps described in this thread. Make sure that after your device wipes and reboots after the bootloader is unlocked that you go through the setup wizard again and back into Developer Settings and enable OEM Unlocking. I think you need to connect to wifi for this option to appear, so if you don't see it try that.
3. Boot to download mode, then install VBMeta Disabler via Odin.
4. Reboot to download mode, then install TWRP via Odin.
5. Reboot to download mode again, then install LineageOS via Odin.
6. Boot to TWRP, push "fix_brightness.sh" to the device and run it, then format data.

That should be all that is necessary. If you get stuck in a loop with TWRP where you can't boot to system (seems to happen regularly to me) I included a script in TWRP that should get you out. From the TWRP cli run the command "exit_twrp". It will say "out of space" when finished (instantly). Then reboot to system. If for some reason that still doesn't work and you boot back to TWRP, repeat.

Known Issues:

• OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
• TWRP touchscreen seems to be unresponsive for several seconds upon first booting into TWRP. Just patiently wait a few seconds and try again.
• You'll see errors in TWRP about /keyrefuge, etc. Ignore that. I believe it's related to the inability to decrypt internal storage using FBE.
• Installing Gapps (Nik and Flame) doesn't work, but no worry because the ROM includes Gapps
• Security: by default this ROM has root access and USB debugging (adb) is enabled unsecured. Anyone can plug into it and have full root access. So disable USB debugging if you don't want that! TWRP is the same way, though data is encrypted. Someone could install malware into your system partition though. In short, this is for hobbyists, not someone with security concerns.

Sources:

• Device tree for TWRP from my Github; branch TWRP-11 specifically: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
• Kernel sources from Samsung: https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#

Files:

• LineageOS 19.1 Beta2
• TWRP 3.6.1 Beta 5
• VB Meta Disabler
• Brightness Fix

Updates:

• You can update this ROM yourself by installing a new GSI to the system partition.
  • Download new GSI from here onto Micro SD card: https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
  • Boot into TWRP
  • Run command: blockdev --setrw /dev/block/mapper/system
  • Run command: dd if=/external_sd/<your_downloaded_gsi.img> of=/dev/block/mapper/system bs=1M
  • Wait for dd command to finish, then reboot into system. Don't forget to use "exit_twrp" command if you keep booting into TWRP.

thank you you did a amazing work

 

[agreenbhm]

I am a huge fan of GSI but doesnt realy understand what it is and how to use it ( this isnt my first account just forget my pw XD) so it would be a pleasure for me if you would write a few words about it thanks in advantage :_)

In short, a GSI is a special type of system image that is made to work across multiple devices. It stands for generic system image. The ROM that I included in the op is a super image which contains not only the system partition but also the vendor partition, which includes device specific drivers and things like that, plus a couple other partitions.

 

[lewmur]

What is the syntax to push the fix_brightness file? I have it on the extternal SD card. Can I just copy to a directory on the internal SD?