[ROM][SM-T510][UNOFFICIAL] LineageOS 19.1 for Galaxy Tab A 10.1 (2019) - Samsung Galaxy Tab A series ROMs, Kernels, Recover

[ROM][SM-T510][UNOFFICIAL] LineageOS 19.1 for Galaxy Tab A 10.1 (2019) - Samsung Galaxy Tab A series ROMs, Kernels, Recover

Reserved

Thank you dear @Magendanz very much for keeping my Old Youtube Tab Alive!
Quick Question, is an update from "lineage-18.1-20220417-UNOFFICIAL-T510XXU5CVB1.zip" to the new 19.1 Possible or do i have to update the base version first?

Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?

NJey90 said:
Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?
Click to expand...
Click to collapse
Is the task bare active? I have the same layout when it is. You can turn it off in settings, but research the bar, you might want to use it.

@Magendanz , I dirty installed it over my lineageos gsi, and it works great so far. One problem I see, and had with the gsi is that I have a notification to finish installation, but there is no way to get past the network selection. There is no button to either skip or continue. Is there a way to fix this?
Thank you for this - I know how hard it is given your other responsibilities!

Thanks Magendanz for this news!
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Thanks.

galoneta said:
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Click to expand...
Click to collapse
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).

Magendanz said:
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).
Click to expand...
Click to collapse
Thanks Magendanz for this clarifying tutorial!
So you must first always update \ have the samsung base AND the custom recovery to a MINIMUM combination set? In this case the minimum "combo" set would be a samsung rom with android 11 as base (and recovery 3.6) right ?
Will try this sequence and give feedback as soon as possible.
Thanks again.

Hey there, just wondering -- does hardware video acceleration work on this build seeing as its based on a GSI? Thanks

I tried to flash this on T515 via twrp. Seems like it only detect and allow install on t510

Can you also make a variant for sm-t515?
Cheers and thanks

dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.

lewmur said:
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.
Click to expand...
Click to collapse
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks

dissidius said:
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks
Click to expand...
Click to collapse
Yes, TWRP can work on both but recovery doesn't access the LTE modem. And, again, I'm stating MY experience from over ten years of having people ask the question about many, many SAMSUNG tablets only.

Has anyone successfully installed MindTheGApps on lineageos19? did you use an sdcard or adb or some other method? I don't have access to an sdcard but I am curious if this is the only way. I have not been successful in using adb..... yet!

This version of Lineage 19 already has Gapps installed. So MindtheGapps is not needed. Installing it using the tar ball and Odin means you don't need an SD card. Or have I missed something?

dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.

DingusestDingus said:
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.
Click to expand...
Click to collapse
Scratch that, I restarted it and its now in a bootloop

This is the 2019 version. I can't get this to install. Bootloader is unlocked and tablet is rooted

Related

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note8 Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note8 ExynosOnly for exynos variants - N950F (Single SIM: Europe, Australia); N950FD (Global Dual SIM: Europe, LATAM, Brazil; Australia); N950N (South Korea)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
https://twrp.me/samsung/samsunggalaxynote8.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
Device tree - https://github.com/TeamWin/android_device_samsung_greatlte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal8895/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible

Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary

FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

No Download. Img file?

corsicanu said:
TWRP
Click to expand...
Click to collapse
Well done mate
Benny100 said:
No Download. Img file?
Click to expand...
Click to collapse
Its directly in the github link

No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags

Benny100 said:
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Click to expand...
Click to collapse
Did you tried taping on Assets?

Found and is working Thx!...

I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero

tabish84 said:
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
Click to expand...
Click to collapse
datafix is for oreo issues where twrp could not properly access internal storage.
format is if you come from stock rom and still have encrypted storage.

Very nice start of the Note 8 Exy journey Bro ?
It is a big pleasure to see U around N8 development!
I am really excited now for the nearest few months and Your 'crazy' ideas which always bring some goodies ?
Thx for Ur efforts and good luck! ?

Works great thank you.
Dev Base August
Sent from my SM-N950F using XDA Labs

After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?

Pinan said:
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Click to expand...
Click to collapse
im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.

bober10113 said:
1. im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
2. did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
Click to expand...
Click to collapse
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!

Pinan said:
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Click to expand...
Click to collapse
i could extract it but u can basically get it from unziping stock.(see link below)
since we are on the n950n, I'm almost sure repulsa rom didnt update it because mostly all roms that might include the BL will have mainly the F/DS bootloader, most dont even update it though.
latest BL would be U3. might be a good idea to update cp(modem) while you are at it too, so grab latest stock firmware and extract both from:
https://samsung-firmware.org/model/SM-N950N/
if download is slow, i can provide these 2 files in a few minutes because package is so big just to get them smaller files.
so only put bl and cp in odin and at least you will be on the latest stuff. dont know what is taking so long for BL U4 to arrive for our korean n950ns....
edit
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though

bober10113 said:
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
Click to expand...
Click to collapse
Thank you very much. Most kind of you. :good:
Yes. I've used SamFirm before. Faster indeed.

@ bober10113.
All's well after new CP and BL. no more "Recovery is not seandroid enforcing".
Thanks again.

Good job mate :good:

Really glad we have this dev around. Will flash shortly

[RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2019 Galaxy Tab A 10.1 [SM-T510]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After @geiti94 and @ianmacd started the ball rolling for the Samsung Galaxy S10 series (Exynos 9820), it was really only a matter of time until we could do the same for the 2019 Galaxy Tab A 10.1 (Exynos 7904). The kernel source was released last May, allowing me to build a custom kernel with many of the problematic Knox security features disabled. What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and rely on the latest posted kernel source (T510XXU5CWA1).
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.7.0_11-0-T510XXU5CWA1-20230330.tar.md5
twrp-3.7.0_11-0-T510XXU5CWA1-20230330.img
Build archives:
Android File Host
Change Log:
v3.7.0_11-0 (20230330):
Updated to T510XXU5CWA1 OEM stock kernel.
v3.7.0_11-0 (20221102):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
v3.6.2_11-0 (20220905):
Updated to TWRP 3.6.2 release built from AOSP-11 branch.
Updated to T510XXU5CVG2 OEM stock kernel.
v3.6.1_11-1:
Minor update to incorporate fix from TWRP repo.
v3.6.1_11-0:
Updated to TWRP 3.6.1 release built from AOSP-11 branch.
Updated to T510XXU5CVB1 OEM stock kernel.
v3.6.0_11-2:
Updated to T510XXU5CUL1 posted kernel source.
v3.6.0_11-1:
Updated to T510XXU5CUJ1 posted kernel source.
Updated to TWRP 3.6.0 release built from aosp-11 branch.
v3.5.2_9-0:
Updated to T510XXU5CUF4 posted kernel source.
v3.5.2_9-0:
Updated to TWRP 3.5.2 release built from omni-9.0 branch.
v3.5.1_9-0:
Updated to T510XXU4BUA1 posted kernel source.
Updated to TWRP 3.5.1 release built from omni-9.0 branch.
v3.5.0_9-0:
Updated to T510XXU3BTK1 posted kernel source.
Updated to TWRP 3.5.0 release built from omni-9.0 branch.
v3.4.0-0:
Updated to TWRP v3.4.0 source
Updated to latest custom kernel
v3.3.1-7:
Updated to latest custom kernel
v3.3.1-6:
Switched to .img file for installation from TWRP
v3.3.1-5:
Fixed hang on splash with encrypted user data partition
Added OTA update (.zip) for installation from TWRP
v3.3.1-4:
Fixed MTP support in a way that supports Magisk
v3.3.1-3:
Fixed MTP support
Included boot image with custom kernel
Deprecated separate NoKnox releases
v3.3.1-2:
Changed system partition mount point to /system_root
Fixed screen brightness control
Restored screen timeout
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gta3xlwifi
android_device_samsung_gta3xl
Donations:
Your support is always appreciated! Just click here.

Good work. Well done.

Great stuff! I've received the device today, although I'm willing to test this recovery, it maybe better to wait a bit longer for a patched kernel/ROM instead? From my understanding this prevents the needs of booting in recovery every time to start the tablet and may be better to prevent Samsung/KNOX from bricking this device.
If this is untrue, please let me know and I'll remove this post asap.
Also let me know if you need any (debug) info.

beta990 said:
Great stuff! I've received the device today, although I'm willing to test this recovery, it maybe better to wait a bit longer for a patched kernel/ROM instead? From my understanding this prevents the needs of booting in recovery every time to start the tablet and may be better to prevent Samsung/KNOX from bricking this device.
Click to expand...
Click to collapse
NoKnox above will patch the T510XXU1ASC7 OEM firmware with the custom kernel and includes the vendor partition fixes in @ianmacd's Multi-disabler. Booting to recovery each time is only required with the Magisk root, which patches itself into recovery (TWRP or stock). More details on @ianmacd's post here.

Thanks for this! I successfully flashed NoKnox, TWRP and Magisk last night and all is working well! @PiCkLeS posted some helpful instructions here for those needing some extra help. Follow the instructions in this thread, but replace the last step with flashing your Magisk-patched TWRP image. No need to mess with running magisk on the stock AP file, you can just modify the TWRP recovery.img.

Magendanz said:
[*]Ensure you're running the T510XXU1ASC7 release
Click to expand...
Click to collapse
I just received the tablet and it's running T510XXU1ASCE, I suppose I should downgrade first, if possible, or will it work as-is?

3c said:
I just received the tablet and it's running T510XXU1ASCE, I suppose I should downgrade first, if possible, or will it work as-is?
Click to expand...
Click to collapse
Unfortunately, they've only posted the source for T510XXU1ASC7 at this point, so that's what we're stuck with. The safe bet is to downgrade (especially since NoKnox includes a modified vendor partition), but I wouldn't be surprised if you can mix and match these two versions.
Note: I see that the May 2019 update (T510XXU1ASCF) is already available. I've put in a request for the kernel source to be posted.

Magendanz said:
Unfortunately, they've only posted the source for T510XXU1ASC7 at this point, so that's what we're stuck with. The safe bet is to downgrade (especially since NoKnox includes a modified vendor partition), but I wouldn't be surprised if you can mix and match these two versions.
Note: I see that the May 2019 update (T510XXU1ASCF) is already available. I've put in a request for the kernel source to be posted.
Click to expand...
Click to collapse
Thanks, downgrading from ASCE worked very well, had to change OEM unlock in dev settings again though (with the date trick).

@Magendanz, l'm willing to test twrp for the 515 model. Dm me ?

I did a backup and did a restore but it kept bootlooping idk if this was because i rooted it first or what..

They released the latest kernel

Awesomeslayerg said:
They released the latest kernel
Click to expand...
Click to collapse
Yep, it's already downloaded and I'm building the kernel tonight. Unfortunately, we didn't get the May 2019 update for SM-T515 (T515XXU1ASEH).

Magendanz said:
Yep, it's already downloaded and I'm building the kernel tonight. Unfortunately, we didn't get the May 2019 update for SM-T515 (T515XXU1ASEH).
Click to expand...
Click to collapse
hello, thanks for your work, i'm building twrp for a device with the same soc [7904], i was wondering does disabling [proca] is a must to boot twrp ? if it's can you provide changes you have made to vendor partition to remove it
regards
edit: ok i see that you remove the init file for proca service [pa_daemon_teegris.rc] so my question now is, does using a custom kernel in boot image is a must ? i already use one in twrp with most of the security features such as defex/proca/samsung restrictions..etc disabled and if possible can you provide the used kernel source or used defconfig ?

messi2050 said:
hello, thanks for your work, i'm building twrp for a device with the same soc [7904], i was wondering does disabling [proca] is a must to boot twrp ? if it's can you provide changes you have made to vendor partition to remove it
Click to expand...
Click to collapse
I just manually perform everything that @ianmcd's multi-disabler script does to the vendor partition.
messi2050 said:
ok i see that you remove the init file for proca service [pa_daemon_teegris.rc] so my question now is, does using a custom kernel in boot image is a must ? i already use one in twrp with most of the security features such as defex/proca/samsung restrictions..etc disabled and if possible can you provide the used kernel source or used defconfig ?
Click to expand...
Click to collapse
Yes, you've got to build a custom kernel to disable Samsung's rooting restriction features. The custom defconfig is here.

Magendanz said:
I just manually perform everything that @ianmcd's multi-disabler script does to the vendor partition.
Yes, you've got to build a custom kernel to disable Samsung's rooting restriction features. The custom defconfig is here.
Click to expand...
Click to collapse
Been trying for a week now, still it bootloop at every attempt to enter twrp according to the testers.. not sure what's wrong, I'm building using twrp minimal source also custom kernel works good on stock rom so no idea where is the problem

Are there any release for SM-T515?

b2574028 said:
Are there any release for SM-T515?
Click to expand...
Click to collapse
I have a volunteer to test it, but I was waiting for Samsung to post kernel source for the May 2019 update (T515XXU1ASEH).

'Only official released binaries are allowed to be flashed'
Thank you for this great work. I ended up getting the 'Only official released binaries are allowed to be flashed' at booting after flashing:
- NoKnox-T510XXU1ASEF.tar
- twrp-3.3.1-1-gta3xlwifi.tar
After the flash, the tablet successfully booted into new factory status OS. Once the intial setup was done and rebooted, the phone is just soft bricked with the message. Any idea what I've done wrong?
Thank you very much in advance.

redexit said:
After the flash, the tablet successfully booted into new factory status OS. Once the initial setup was done and rebooted, the phone is just soft bricked with the message. Any idea what I've done wrong?.
Click to expand...
Click to collapse
That's Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.
So to recover, just flash the stock OEM firmware package with Odin, repeat the steps you took, and be sure this time to enable Developer Options and verify that OEM Unlocking is enabled. (It should also be grayed out, since the bootloader is already unlocked.)
And if you want to more permanently disabled VaultKeeper, I have a modified version of @ianmcd's multi-disabler script for the SM-T510 that you can install in TWRP.

Thank you!
Magendanz said:
That's Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.
So to recover, just flash the stock OEM firmware package with Odin, repeat the steps you took, and be sure this time to enable Developer Options and verify that OEM Unlocking is enabled. (It should also be grayed out, since the bootloader is already unlocked.)
And if you want to more permanently disabled VaultKeeper, I have a modified version of @ianmcd's multi-disabler script for the SM-T510 that you can install in TWRP.
Click to expand...
Click to collapse
Whoa, thank you so much for your quick and thorough reply!
I will do what you instructed after another 7 days I guess, (assuming there is no way to get around with this one).
Again I truly appreciate your contribution and hard work.

[ROM][SM-T510][UNOFFICIAL] LineageOS 18.1 for Galaxy Tab A 10.1 (2019)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 18.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 18.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the latest Android 11 release (T510XXU5CVG2).
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2.tar.md5 (Odin tarball)
lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20220907:
Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
Update to TWRP v3.6.2 custom recovery on AOSP 11.
20220417:
Based on the latest build of LineageOS 18.1 GSI (20220414) with April 2022 Security Patch.
Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVB1).
Update to TWRP v3.6.1 custom recovery on AOSP 11.
Replaced default wallpaper with custom one inspired by my Nexus ROMs.
Boots normally for offline (cold) charging.
20210526:
Based on the latest build of LineageOS 17.1 GSI (20210512) with May 2021 Security Patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU4BUA1).
20201121:
Based on the latest build of LineageOS 17.1 GSI (20201114) with November 2020 Security Patch.
Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
20200812:
Based on the latest build of LineageOS 17.1 GSI (20200808) with August 2020 Security Patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
20200713:
Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 Security Patch.
Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
20200413:
Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
Fixed crash on first two attempts to launch Phh Treble Settings.
Based on the latest build of LineageOS 17.1 GSI (20200413).
Updated to the OEM T510XXS3ATB4 kernel and vendor partition.
20200321:
Switched to latest stable version of ext2simg command for sparse image conversion.
20200314:
Now based on the latest build of LineageOS 17.1 GSI (20200309).
Fixed potential image corruption issue from outdated img2simg command.
20200308:
Charging after full shutdown will no longer hang during level-of-charge animation.
20200301:
Initial release based on lineage-17.1-20200227-UNOFFICIAL-treble_a64_bvN
MTP file transfers no longer require USB Debugging to be enabled.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, Install Image, select your update (.img file), and then swipe to install
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!

Does the ethernet-function (LAN) work?

When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?

andreasoz said:
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
Click to expand...
Click to collapse
Yes, I've noticed that myself, and it seems to occur when writing to certain modified vendor partitions. Anyone have an idea of what might cause that?

Magendanz said:
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Click to expand...
Click to collapse
Hiya
Just got this device today.. pretty stoked to get it rooted & Lineage going.. thanks for your projects & info
I'm curious do I need to change any of the Options tab in Odin ?
Auto Reboot off for example ?
Auto Reboot & F. Reset Time are checked by default none of the others are.
At this point in this device's progress assuming I unlocked correctly & get into Download mode.. flash with Odin successfully I should just Auto Reboot right into TWRP & can go from there ?
NoKnox is a thing of the past ?
What about Multi-disabler ?
If I install Magisk & plan to how do I ensure I don't "boot outside Magisk" I keep hearing people say.. where Vaultkeeper & similar things may become problematic or so I've read.
Someone did offer some advice on not booting outside Magisk a few weeks ago I'm going to go find their message too but yeah I've read a lot of threads here & it seems like since certain packages & older methods like patching TWRP with Magisk are things of the past.. I just want to confirm what all else is
is charging past 80% an issue at all with this ROM ?
That's one thing I see people mention about custom kernels is they fix that.. well that & EX or Franco would be rad if they exist for this device & rom
/salute

jaladhjin said:
I'm curious do I need to change any of the Options tab in Odin ? Auto Reboot off for example ?
Click to expand...
Click to collapse
Nope.
jaladhjin said:
NoKnox is a thing of the past ?
Click to expand...
Click to collapse
Yep.
jaladhjin said:
What about Multi-disabler ?
Click to expand...
Click to collapse
You still need to run Multi-disabler if you're installing TWRP, but it's baked into this custom ROM.
jaladhjin said:
is charging past 80% an issue at all with this ROM ?
Click to expand...
Click to collapse
No longer an issue with this custom kernel.
jaladhjin said:
If I install Magisk...
Click to expand...
Click to collapse
I don't use Magisk, and so I'm really not the person to ask. Note, however, that custom kernels in boot and recovery partitions are slightly different wrt MTP. Boot kernel uses Google MTP and recovery one uses Samsung MTP to maintain compatibility with OEM system if patched with Magisk.

Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.
Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.
andreasoz said:
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
Click to expand...
Click to collapse
OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
https://sourceforge.net/projects/opengapps/files/
https://www.cyanogenmods.org/downloads/bitgapps-for-android-10-download/

I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"
I cannot get back into lineage any advice?
I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more

Warrenchild said:
I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"
I cannot get back into lineage any advice?
I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more
Click to expand...
Click to collapse
Did you re-enable Developer mode and OEM?

lewmur said:
Did you re-enable Developer mode and OEM?
Click to expand...
Click to collapse
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
I even downgraded to sk1 and then let it do a OTA update while locked

Warrenchild said:
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
I even downgraded to sk1 and then let it do a OTA update while locked
Click to expand...
Click to collapse
I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.
edit: The original instruction are a little confusing. They tell you that after each step you have to boot and enable Dev mode in order to chech OEM enable. The real reason is that you have to enable Dev mode in order to flash anything but stock. Without it enabled, you get the message in red saying that only original firmware can be installed.

lewmur said:
I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.
Click to expand...
Click to collapse
I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.
Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
Error : "only official released binaries are allowed to be flashed(BOOT)"
and the flash stalls out on odin.
So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.

Warrenchild said:
I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.
Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
Error : "only official released binaries are allowed to be flashed(BOOT)"
and the flash stalls out on odin.
So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.
Click to expand...
Click to collapse
Did you read my "edit" where I said that was caused by not having enable Developer mode?

lewmur said:
Did you read my "edit" where I said that was caused by not having enable Developer mode?
Click to expand...
Click to collapse
I did not see your edit, thank you I will try and inform the community.

installing
BiTGApps-arm-10.0.0-R1_signed
BiTGApps-arm-10.0.0-v0.2_signed
open_gapps-arm-10.0-pico-20200219
open_gapps-arm-10.0-nano-20200305
with twrp will force reboot while installing
what maybe not work is miracast/widi. i can't find my tv with my tab.
phh-treble entry in settings does nothing / does not open.
(both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])

[email protected] said:
installing
BiTGApps-arm-10.0.0-R1_signed
BiTGApps-arm-10.0.0-v0.2_signed
open_gapps-arm-10.0-pico-20200219
open_gapps-arm-10.0-nano-20200305
with twrp will force reboot while installing
what maybe not work is miracast/widi. i can't find my tv with my tab.
phh-treble entry in settings does nothing / does not open.
(both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])
Click to expand...
Click to collapse
Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.

lewmur said:
Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.
Click to expand...
Click to collapse
my mi a1 with stock pie and the t510 stock rom still can use it

[email protected] said:
my mi a1 with stock pie and the t510 stock rom still can use it
Click to expand...
Click to collapse
Maybe so. But it isn't officialy supported, so if it doesn't work, it doesn't work. I tried it with several apps on several ROMs and could only get it work on my T580 by reverting to an Android 8. Every thing I tried in Pie either froze or caused the tablet to reboot.

Warrenchild said:
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
Click to expand...
Click to collapse
You triggered Samsung's VaultKeeper "feature" when you rolled back to the OEM firmware. In order to prevent that, you need to immediately enable Developer Options while connected to the Internet after setup (before rebooting). If you don't, VaultKeeper places the device in a hybrid state where it looks like the bootloader is still unlocked, but it still won't allow Odin to flash firmware unless it's signed with Samsung's release keys.
Flashing a known-good OEM firmware should remedy the problem, provided you verify that the OEM Unlocking setting is enabled in Developer Options and go back for a Volume Up long press from the blue warning screen to complete the bootloader unlock. Did you do that after booting while holding the Volume Up & Down with the USB cable attached?

betacrypt said:
Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.
Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.
OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
https://sourceforge.net/projects/opengapps/files/
https://www.cyanogenmods.org/downloads/bitgapps-for-android-10-download/
Click to expand...
Click to collapse
No luck for me with this, TWRP still reboots when trying to install gapps/bitgapps . I'm not sure what else to try.

[ROM][CrDroid v6.x][OFFICIAL][ocean][Discontinued]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Downloads
Official Website
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partitions zip is crucial in order to prevent bricks. It only needs to be done if you're coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.
Only use TWRP version 3.3.1-0, it has an advanced option for recovery bootloop fix. Sorry for some hassles with TWRP. It is not ROM related but the version I use works 100% of the time.
My apologies for any confusion/problems flashing!
Preparation for A/B Roms:
01. Download TWRP version 3.3.1-0 (do not use any other version)
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use the terminal to boot the latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmware.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash GAPPS + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
SOURCES:
ROM: https://github.com/crdroidandroid
Changelog::
https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_ocean.txt
Known issues:

Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
© 2020 GitHub, Inc.
XDA:DevDB Information
CrDroid, ROM for the Moto G7 Power
Contributors
Rondeau79
Source Code: https://github.com/Rondeau79/android_kernel_motorola_sdm632
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest TWRP unlocked bootloader
Based On: AOSP, Lineage OS
Version Information
Status: Stable
Current Stable Version: QQ2A.200305.003
Stable Release Date: 2020-03-22
Created 2020-03-22
Last Updated 2020-06-23

Reserved

Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:

flash713 said:
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
Click to expand...
Click to collapse
Thanks, this one was a tough task to get done. I don't mind a permissive kernel. I really don't dive too far into the Android system. I am a fan first and a developer second! I still really don't have an understanding of code and stuff. I just go with my instincts.

I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.

danny8 said:
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
Click to expand...
Click to collapse
You are not bricked. When coming from one version of android to another a clean flash must be done. You can dirty flash after that. Wipe both boot slots and then go about flashing like normal. First boot takes a while. It won't boot without wiping the system partition.

Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)

D13Gho said:
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
Click to expand...
Click to collapse
With the A/B partitions scene. When you flash a ROM it will be installed to the opposite slot. If you are on A then the zip will be installed to B and vica versa. Gapps are flashed after you reboot to recovery when you are on the boot slot the ROM was installed on same as Magisk.

Thank you, Rondeau79. I got it installed.
It looks great!

I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.

Johnfoo19 said:
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Click to expand...
Click to collapse
Give it a little time to set in. Usually a fresh install takes a bit.

danny8 said:
Thank you, Rondeau79. I got it installed.
It looks great!
Click to expand...
Click to collapse
You're welcome.

pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms

cgrimm9 said:
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
Click to expand...
Click to collapse
Go to display styles and wallpapers to change to colors.

Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch

Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one

n00b Samurai said:
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Click to expand...
Click to collapse
Sorry there isn't, I can't change the base features of the ROM. However you can change the color and thickness of the bar and it's position on the screen.
You can always adjust the screen in order to account for the notch. It's in the developer settings.

barados742 said:
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
Click to expand...
Click to collapse
You need an external sdCard for flashing ROMs. Wiping the user partitions properly is essential for a properly working ROM. If you just have internal storage then the installation of an OS won't be done right.

Thanks for the reply! I just bought an SD card and will try it tomorrow and will respond if it worked.

Good morning, guys I tried to install on my MOTO G 7 POWER 3/32 and the rom does not install says it is not compatible with the system. Any tips?

[RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2019 Galaxy Tab A 8.0 [SM-T290]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this low-cost tablet. My thanks to @mehanik6 for blazing this trail on 4PDA.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.7.0_11-0-T290XXU3CVG3-20221120.tar.md5
twrp-3.7.0_11-0-T290XXU3CVG3-20221120.img
Build Archives:
Android File Host
Change Log:
v3.7.0_11-0: (2022-11-20)
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to T290XXU3CVG3 OEM stock kernel.
v3.6.1_11-0: (2022-03-27)
Updated to TWRP 3.6.1 release built from AOSP-11 branch.
Updated to T290XXU3CUK4 OEM stock kernel.
Using FFS MTP so that custom kernel builds are no longer necessary.
v3.6.0_11-1: (2022-02-20)
Added wipeingui for ext4 partitions.
v3.6.0_11-0: (2022-01-23)
Updated to TWRP 3.6.0 release built from AOSP-11 branch.
v3.5.2_9-0: (2021-10-17)
Updated to T290XXU3CUG4 posted kernel source.
v3.5.2_9-0: (2021-05-16)
Updated to T290XXU3BUC1 posted kernel source.
Updated to TWRP 3.5.2 release built from android-9.0 branch.
v3.5.1_9-0: (2021-03-30)
Updated to T290XXU3BUB2 posted kernel source.
Updated to TWRP 3.5.1 release built from android-9.0 branch.
v3.5.0_9-0: (2021-01-02)
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.
v3.4.0-1: (2000-12-09)
New custom T290XXS3ATC1 kernel that actually fixes MTP support.
v3.4.0-0: (2000-12-04)
Included legacy aboot and vaultkeeper in tarball to allow Odin flash on Android 10 OEM firmware.
v3.4.0-0:
Initial release based on @mehanik6's device tree and T290UES3ATC1 kernel.
Fixed MTP
Default language is now English
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler that preserves encryption from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gtowifi
Donations:
Your support is always appreciated! Just click here.

are there any custom roms for sm-t290?

Tralien said:
are there any custom roms for sm-t290?
Click to expand...
Click to collapse
I'll have a release of my Nexus Stock custom ROM shortly. It's basically the same as what I've been releasing for the 10.1" version of this tablet over the past year. I'm basically just waiting for Samsung to post the latest kernel source.

Update for TWRP v3.5.0 release...
Downloads:
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.tar.md5
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.img
Change Log:
v3.5.0_9-0:
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.

I have tried installing via Odin your twrp custom recovery for my t290 device.
The process with Odin seem to go well and after installation my device restarts however, when I press the + volume button, android recovery shows up and not TWRP.
Any idea why?

dark_friend said:
I have tried installing via Odin your twrp custom recovery for my t290 device.
The process with Odin seem to go well and after installation my device restarts however, when I press the + volume button, android recovery shows up and not TWRP.
Any idea why?
Click to expand...
Click to collapse
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.

Magendanz said:
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.
Click to expand...
Click to collapse
Got it! thank you very much!

Magendanz said:
There are two issues here:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
So, try your best to get it right the first time, and don't be surprised if you end up with stock recovery if you mess up.
Click to expand...
Click to collapse
Presumably, if you miss the first time, you reflash and try again? (and as many times as needed?)

Heeni said:
Presumably, if you miss the first time, you reflash and try again? (and as many times as needed?)
Click to expand...
Click to collapse
If you miss, hold Power + Vol Down for 7 seconds during the boot animation to do a hard reset and try again. Alternatively, you can wait for it to finish booting and then restart, but then you risk Samsung's VaultKeeper "feature" putting the bootloader into a stealth locked state. You can prevent that by connecting to the Internet, enabling Developer Options, and then confirming the OEM Unlocking state as soon as you finish setup. (You don't need to log into Google or Samsung services for Vaultkeeper to maintain the bootloader unlock, but you've got to have Internet access and reenable Developer Options right away.)

Thanks for pointing out some of the potential potholes along the way. I'm not a stranger to modding, but have experience only with fastboot, so the Samsung method is a whole new ballgame for me. Maybe I just need to take a deep breath and jump in. And backup everything before starting.

Heeni said:
Thanks for pointing out some of the potential potholes along the way. I'm not a stranger to modding, but have experience only with fastboot, so the Samsung method is a whole new ballgame for me. Maybe I just need to take a deep breath and jump in. And backup everything before starting.
Click to expand...
Click to collapse
Yeah, it never ceases to amaze me how Samsung believes it's adding value with Knox security features like Vaultkeeper and its special Download mode that only works with Odin. My main phone is a Pixel 4a, and I've never felt that Google has taken any flak for making bootloader unlocking and firmware flashing painless. Why does Samsung feel the need to reinvent the wheel?

Somewhat to my surprise, I was able to get TWRP installed and boot into it on the first try. In fact, the biggest difficulty by far was getting Samsung drivers to work in my Windows 10 vm. The vm is still having problems, so hopefully, now that TWRP is installed, I won't need to use Odin for a while.

Tried patching TWRP with Magisk. No bootloops or other drama, but wifi doesn't work. I notice on the Magisk Github site that a number of people are running into this. Fortunately, restoring the unpatched TWRP also restored wifi.
I think I can live without root much more easily than without wifi!

Heeni said:
Tried patching TWRP with Magisk. No bootloops or other drama, but wifi doesn't work. I notice on the Magisk Github site that a number of people are running into this. Fortunately, restoring the unpatched TWRP also restored wifi.
I think I can live without root much more easily than without wifi!
Click to expand...
Click to collapse
I have root and wifi, but didn't use the TWRP install method

Further to this post about the inability to set a password, PIN or pattern:
I reflashed the stock ROM and I can verify the following:-
Stock ROM with (or without) bootloader unlocked will allow me to set up a PIN (I didn't try the other options but would expect that they'd work.
As soon as I install TWRP, the stock ROM will no longer allow me to set up a PIN. I can have "swipe" or "nothing" to unlock, and that's it.
I've tried installing LineageOS 17 GSI, LineageOS 18 GSI and Magendanz's Nexus stock ROM. None of these will accept a PIN, password or pattern.
Therefore, I think that the issue has to do with TWRP, or possibly with something in the multidisabler script.
Googling has come up with nothing other than the instruction to remove /data/system/locksettings.db and related files. I've tried this numerous times without success. I've even tried comparing permissions and ownership with the (working) equivalent on my Moto phones, with no luck.
I'm happy to do any tests, provide logs etc if it would help. The only other alternative seems to be to revert to stock if I need to travel.

I'm going to be using the table in an install that does not allow easy access to be able to use the physical buttons, if I lock the boot loader back after all this will it keep root?
I need root so that I can modify the files necessary to make the tablet turn on automatically whenever power is connected.

New release posted...
Downloads:
twrp-3.5.1_9-0-T290XXU3BUB2-20210330.tar.md5
twrp-3.5.1_9-0-T290XXU3BUB2-20210330.img
Change Log:
v3.5.1_9-0: (2021-03-30)
Updated to T290XXU3BUB2 posted kernel source.
Updated to TWRP 3.5.1 release built from android-9.0 branch.

Do we need to update the underlying stock ROM first if TWRP is already installed? Or is it sufficient to flash TWRP from the existing TWRP?

Heeni said:
Do we need to update the underlying stock ROM first if TWRP is already installed? Or is it sufficient to flash TWRP from the existing TWRP?
Click to expand...
Click to collapse
You can just flash the new .img file from an existing TWRP install. The version of the kernel is only important if you're using Magisk (which boots through the recovery partition).

Thanks. That was easy. As far as I can tell at this point, it all works.

Better Mobile App

welcome