Could please someone check if widevine is level 1 and Amazon prime video is full HD? Please? :/
The bad news is that it can't be done. You can't downgrade. The good news is that Samsung has supposedly released the source for your version and that it won't be too long before a new version of this ROM will be available.I have the same question. I am unable to downgrade without an error.
MicroG project also works on that problem. Though I never tried it
It's better be in the image OR someone could share it as a installable zip/img.
I flashed 3BUF3 kernel and it didn't help, Wifi still doesn't work. Needs something else. Maybe /vendor/firmware or modem?
I met this issue, my solution is format data **again** after all the flashes are doneHi hellas, long time lurker, first time user, new to all of this, having a few issues and looking for some pointers as i seen to be in some form of a boot loop now.
So i followed the guide to do the magisk thing from here
![]()
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed...forum.xda-developers.com
And i think ive done it all correct. So i proceed on and go through getting the files needed.
Open odin and do the vbdata on the user data, reboot back into dl mode, flash twrp, and reboot into twrp, woohoo 1 step closer.
Heres where my issues start, i go into the wipe and format data as instructed but i get the error
failed to mount '/keydata'
failed to mount '/keyrefuge'
But it does say done. So i went ahead and clicked install from image and selected the extracted linage image, and then the nikapps, which it all looks good. Reboot, and it just boot loops, occasionally booting me back to twrp. So i had a google and tried clearing the dalvik cache and rebooting but all to the same avail. Either stuck in twrp, or boot looping.
Any suggestions, its the t500 i have, and the firmware was on the T500_EUX_T500XXU3BUF3 firmware version.
Just wondering if i done something specific or if ive missed a step somewhere.
Has the latest version been updated to use the latest stock BUJ1?Hi hellas, long time lurker, first time user, new to all of this, having a few issues and looking for some pointers as i seen to be in some form of a boot loop now.
So i followed the guide to do the magisk thing from here
![]()
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed...forum.xda-developers.com
And i think ive done it all correct. So i proceed on and go through getting the files needed.
Open odin and do the vbdata on the user data, reboot back into dl mode, flash twrp, and reboot into twrp, woohoo 1 step closer.
Heres where my issues start, i go into the wipe and format data as instructed but i get the error
failed to mount '/keydata'
failed to mount '/keyrefuge'
But it does say done. So i went ahead and clicked install from image and selected the extracted linage image, and then the nikapps, which it all looks good. Reboot, and it just boot loops, occasionally booting me back to twrp. So i had a google and tried clearing the dalvik cache and rebooting but all to the same avail. Either stuck in twrp, or boot looping.
Any suggestions, its the t500 i have, and the firmware was on the T500_EUX_T500XXU3BUF3 firmware version.
Just wondering if i done something specific or if ive missed a step somewhere.
it was yeah. About to do an odin restore back to full stock, then ill go through the rooting and magisc again and give another tryHas the latest version been updated to use the latest stock BUJ1?
There has been so little support for this tablet that I just flashed back to stock and relocked the bootloader. Frustrating. The old 2016 tablets have a lot more devs.OP has not been around here for quite some time, right?
Any way we could get a group of people to continue the work that OP started?
My issue with this ROM is that it always gets some hiccups when Firefox is open. Either it is very lightweight pages, bloated javascript, playing audio or playing video, it starts to stutter and then freeze whole tablet for up to 3 minutes, and then un-clogs itself and goes back to normal. An issue that I would very much like to see resolved.
Also, I'm somewhat surprised that there is so little activity around this tablet model. It appears so insignificant that even the sm-t500 tag is basically a 404 (sm-t404 lol). How? This is a tablet from one of the biggest manufacturers, and here where I live, this thing is being sold in almost every tech store.
The Sources of this build would be a good starting point. @agreenbhm: Do you mind to share those? Or a little guide at least? This way we could possibly get at least security updates for LOS.OP has not been around here for quite some time, right?
Any way we could get a group of people to continue the work that OP started?
My issue with this ROM is that it always gets some hiccups when Firefox is open. Either it is very lightweight pages, bloated javascript, playing audio or playing video, it starts to stutter and then freeze whole tablet for up to 3 minutes, and then un-clogs itself and goes back to normal. An issue that I would very much like to see resolved.
Also, I'm somewhat surprised that there is so little activity around this tablet model. It appears so insignificant that even the sm-t500 tag is basically a 404 (sm-t404 lol). How? This is a tablet from one of the biggest manufacturers, and here where I live, this thing is being sold in almost every tech store.
Right now I'm reading about GSI versions for this tablet. I've gotten so far has installing a TWRP version that allows a reboot to Fastboot. Seems you can't flash the GSI ROMs via Odin but must use ADB and Fastboot. They're working right now on Android 12 ROMs and there are several to try. All seem to have minor problems and are what I would call BETA released. But it seems they are getting close. Look for the TWRP 3.6 for SM-T500 thread for a starting point to see what's happening.The Sources of this build would be a good starting point. @agreenbhm: Do you mind to share those? Or a little guide at least? This way we could possibly get at least security updates for LOS.
The solution is to flash original software that ends with 3BUF3, and then install Lineage.It's actually working, found two bugs till now.
1. Wifi is not working at all
2. Device won't flip landcape or any way.
Didn't find the solution's yet. Anybody?
I'm on SM-T500XXU3BUJ1.The solution is to flash original software that ends with 3BUF3, and then install Lineage.![]()
Great news!! But I think you need to post it in the ROMs, Kernels, Recover thread.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:
- Unlock device bootloader using instructions from other threads.
- Patch stock ROM (AP) using Magisk, then flash rooted ROM. Will likely need to wipe device after this.
- Boot into rooted ROM and ensure "OEM Unlocking" is still enabled in "Developer Tools".
- Boot back into download mode and flash "vbmeta_disabled_R.tar" to disable verified boot.
- Boot device back into rooted stock ROM to ensure things are still functional (may require a device wipe at this step).
- Boot device into download mode and use ODIN to flash TWRP recovery.tar file via "AP" slot.
- Boot device into TWRP to verify functionality (hold Vol-Up + Power during boot).
- Access TWRP via adb using "adb shell" or with USB mouse (touch functionality currently not working).
- Format data partition on device.
- Via ADB shell: twrp format data
- Via USB mouse: Wipe -> Advanced -> Format Data
- Boot device into download mode.
- Via ADB shell: twrp reboot download
- Via USB mouse: Reboot -> Download
- Flash LineageOS tar file via ODIN using the "AP" slot.
- If device boots into TWRP after flashing LineageOS, use USB mouse to select: Reboot -> System
- 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:
- LineageOS 18.1 20210615 with TWRP 3.5.2: https://mega.nz/file/vMVglThZ#TepIHvdEypezq3z4S_4Lln7FRFVfC7CUjVGq3ByFb6U
- TWRP 3.5.2: https://mega.nz/file/GYU1yCCQ#JsthI8BYNtfB08Pzt1eeXta2Lb1zCkUI185Zm88dEW4
- vbmeta_disabled_R: https://mega.nz/file/iMFx3CQI#8cP4mPoRaQNwDATqt0vKD8wxqRWSTz1EL79U0fNpW8M
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.