It's not my ROM and I don't know if you can or not. Did you do as I suggested and look for post from others with the problem?
My stock rom is XSG but it still worked (i got it online lol cus it was cheap lol 100$ less just more delivery payment)I think that may because this ROM is based on the US/Canada stock ROM. If your stock ROM is from another country, then that is the problem. If you search back through this thread, I think you'll find others had the same problem but I don't know if they ever solved it.
hi, can u help me set the cpu speeds to the proper ones?It's not my ROM and I don't know if you can or not. Did you do as I suggested and look for post from others with the problem?
edit: I don't know if it will work or not, but you might try flashing just the CSC for your country via Odin.
I just clicked on the files in the OP and had no problem downloading.anyone out there with a copy of the files on here. i think someone hasn't paid their hosting bill on Cloudflare.
hello I've got some questions, for start my wifi is not working or auto rotate or volume is there any fix for this?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.
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.
- Update to latest stock ROM as of 3/24/2022 (T500XXU3BVB3).
- 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.
- Boot to download mode, then install VBMeta Disabler via Odin.
- Reboot to download mode, then install TWRP via Odin.
- Reboot to download mode again, then install LineageOS via Odin.
- Boot to TWRP, push "fix_brightness.sh" to the device and run it, then format data.
Known Issues:
Sources:
- 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.
Files:
- 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#
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.
Hi, I was trying it and when i flashed the vbmeta file, my tablet showed "only official released binaries are allowed to be flashed(vbmeta)" how can i fix it?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.
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.
- Update to latest stock ROM as of 3/24/2022 (T500XXU3BVB3).
- 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.
- Boot to download mode, then install VBMeta Disabler via Odin.
- Reboot to download mode, then install TWRP via Odin.
- Reboot to download mode again, then install LineageOS via Odin.
- Boot to TWRP, push "fix_brightness.sh" to the device and run it, then format data.
Known Issues:
Sources:
- 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.
Files:
- 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#
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.
Did you unlock the bootloader? Did you enable Dev mode and OEM after unlocking?Hi, I was trying it and when i flashed the vbmeta file, my tablet showed "only official released binaries are allowed to be flashed(vbmeta)" how can i fix it?
Yes, but still, it gave that errorDid you unlock the bootloader? Did you enable Dev mode and OEM after unlocking?
Now it says "partition vbmetaDid you unlock the bootloader? Did you enable Dev mode and OEM after unlocking?
Now it says "partition vbmeta
Reason vbmeta: error verifying vbmeta image: HS_IMTHSGAUEMSAC"
Odin detects it but when i click start, this shows in logs:
<ID:0/006> Odin engine v(ID:3.1303)..
<ID:0/006> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
After doing this, does "OEM unlocking" show in Dev Options?"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."
Yes, it did.
So, vbmeta installed OK. If you got this far into flashing "super.img", you must have a corrupted download or your stock ROM version is later than the one used by the OP.
Really? I thought it was fixed, what should i do?So, vbmeta installed OK. If you got this far into flashing "super.img", you must have a corrupted download or your stock ROM version is later than the one used by the OP.
So, vbmeta installed OK. If you got this far into flashing "super.img", you must have a corrupted download or your stock ROM version is later than the one used by the OP.
Unplug the USB cable from your device. Try pressing and holding the power button and vol+ to get it to reboot (and likely to bootloop.) If that doesn't work, try power and vol-. Then press and hold the power button and both vol buttons, and plug the USB cable back in while still holding the buttons in. You should eventually be able to get back to the download screen. (Trial and error.)
I mean exactly what I said. If flashing the latest stock firmware doesn't fix the bootloop, then I don't have any idea what else to do. Maybe someone else does, but I don't.
You should be able to root with Magisk, but there are two different ways to do it. One is to patch the entire AP file and flash it with BL, and CSC and the other is to extract the boot.img from the AP file, patch it and then tar the modified file and flash it by itself from the AP slot. But it has been so long since I've done it on this tablet that I don't recall which method works. You'd have to search back trough the treads to find out which to use.so i cant do ANYTHING not even root or download something els or anything
Well, that changes every thing. You can flash Magisk from TWRP without needing to modify the AP or boo.img, in order to root. You can also use fastboot from TWRP to flash GSI ROMs.
without the help and support you gave i wouldnt even get it fixt i have been trying to fix this for a week now and you saved me THANK YOU!Well, that changes every thing. You can flash Magisk from TWRP without needing to modify the AP or boo.img, in order to root. You can also use fastboot from TWRP to flash GSI ROMs.
Firsh of all, what worked on one install, won't work on another. I depends on what the DEV included in their tar. Some include vbmeta and recovery in their ROM. This one doesn't. You have to start from stock, FACTORY RESET, flash vbmeta, FACTORY RESET, and then flash TWRP.Then yes vbmeta flahed on userdata odin ..here once was successful.then another attempt red notice appear only official files can be flashed (vbmeta)....this way.
I remember in my attempt on Skyhawk recovery. Flashed both vbmeta and recovery one sitting in ap for recovery userdata for vbmeta..then press conbination buttons power off volume up volume down all together . And. Da da .wowo i am in eecovery working fine .
So my reading on flashing are different methods i get lost . What is the proper one .