yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mbsans:
To my knowledge, with Root (Magisk) only and stock recovery the chances are that it'll take the updates, but there's always a possibility of a bootloop, so have a backup just in case. Whereas when the tablet has TWRP or TWRP+Root, the update will simply fail.

This at least has been my experience, I've always considered that when the tablet had modifications done, I'd forget about manufacturer's updates, unless I revert to stock rom+recovery.

---------- Post added at 08:40 PM ---------- Previous post was at 08:17 PM ----------

Yes TWRP and Root are working fine in my tablet with the latest update, just had to rename the twrp file (remove .md5 extension).

These are the steps that worked for me, ... from OEM stock firmware:

- Enable Developers Options -> Enable OEM Unlocking, enable USB debugging
- Rename twrp file in your PC, remove .md5 extension from its file name, example twrp-xxxx.xxx.tar.md5 -> twrp-xxxx.xxx.tar
- Reboot into Download mode.
- Unlock bootloader, (a big warning about unlocking bootloader will show up afterwards.)
- Power Off, or reboot until the Welcome screen shows up.
[ Note - In the process of unlocking the bootloader, the tablet will reset itself to factory settings. ]
- Go to stock recovery (Power+Volume UP buttons), then press wipe data/factory reset
- From stock recovery menu select Power Off. Wait until it shuts down
- Enter Download mode. While tablet is off, hold Vol Up & Vol Down buttons and plug its USB C cable into the PC USB port while both above buttons are pressed.
- Install TWRP to AP with Odin, verify its success.
- Reboot, (careful here -> directly follow the next step.)
- Hold Power & Vol Up buttons during restart to enter TWRP recovery
- Install latest Multidisabler from TWRP
- Wipe data in TWRP (factory reset from TWRP), Wipe -> Format Data
- Reboot to system

---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------

Thanks a lot Magendanz for your work!

Yes, I changed the file name, I renamed it by removing the .md5 extension from it. If I left it as is the flashing of TWRP from ODIN would always fail, with a message "binaries are not verified by Samsung ...." or some such. I didn't notice any failure of the MD5 checksum in ODIN, it just worked without the .md5 extension. Using latest ODIN version.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] redhonker:
What should be disabled/frozen to avoid accidentally OTA update?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mbsans:
I disabled (froze) Software Update, service and program. There are 2 components with the same name.

I believe this is enough.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 0KimT1:
When u say the latest update do u mean build number T510XXS2ASK1?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 0KimT1:
is the kernel version the same as the build number?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mbsans:
No, I mean the most recent OTA update from Samsung, build number: PPR1.180610.011.T510XXU2ASI4.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 0KimT1:
I am 99% sure that's not the most recent OTA update from Samsung, because that was my Tab's build number out of the box, before i updated it to T510XXSI2ASK1....

T510XXSU2ASI4 has security patch level 1 August

T510XXSU2ASK1 has security patch level 1 November

Hmmmm
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mbsans:
Roger that! As I said that (T510XXSU2ASI4) was my latest OTA update from Samsung. When I manually checked before rooting it, it said "you've got the latest update". I'm not arguing that mine was the latest update ever from Samsung. In that case I can't answer about installing TWRP+ROOT in our tablets, even though I'm sure that it'll be available soon from this great community.

Best.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 1337haXXor:
I can't get TWRP to flash. I'm using Odin 3.12.7, got the md5 file from OP, unlocked the bootloader, and booted into Download Mode immediately after a stock recovery factory reset (to avoid encryption of the data partition), but Odin just hangs on boot.img.lz4. Looking at the data at the top left of download mode, it says FRP Lock and OEM Lock are off. Also that Warranty Void is 0, and KG state is Prenormal. If any of those make a difference.

Tablet is currently on ASEF, should I do an OEM update first? This is a T510.

EDIT: Okay, I relocked the bootloader and tried unlocking it again, and still the same thing. But looking at another user's post here, it seems the problem may be with the KG State being "Prenormal." I did the 7 day "trick" with the dates to allow the OEM unlock option, and it's ticked (because the bootloader's unlocked), is this another thing I have to wait the actual, full 7 days for?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, but you might want to wait a few hours. Last night Samsung posted kernel source for the November 2019 Security Update (T510XXS2ASK1 & T515XXS3ASK1), and I'm in the process of building a new release of TWRP for both devices.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 1337haXXor:
I see. Thanks a ton for your hard work and your quick response! I'm excited to root and debloat. :D
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Okay, the 20191207 builds are now posted, which is using the November 2019 Security Update (ASK1). While the TWRP device tree is unchanged, I did pick up this fix for linker problems from [MENTION=7187684]ianmacd[/MENTION].
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
In the process of flashing the ASK1 OEM build to start testing today's release, I apparently left the device unattended too long which triggered VaultKeeper and the red "Only official released binaries are allowed to be flashed (BOOT)" log entry in Download Mode when I tried to flash the TWRP build in Odin. Unfortunately, this old workaround didn't work for me anymore, and I actually had to do a full flash of ASI4 to get the disabled OEM Unlock option to show back up. Another approach that's even more thorough is documented here.

What's so insidious about this "feature" is that you get the full-screen unlocked bootloader warning and two entries in the Download Mode log saying "FRP LOCK: OFF" and "OEM LOCK: OFF". So, by all appearances the bootloader is unlocked...but it still won't flash unsigned image files. It's really a horrible user interface decision. If they're going to relock the bootloader, then they should make that obvious rather than creating some new hidden mode.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kerabit:
Anyway to flash the TWRP then?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Ummm...I just described how I ultimately cleared the VaultKeeper state above. After that you can flash images not signed by the OEM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kerabit:
Ah, for me even if I followed that, I cannot flash the TWRP, the writing just fails. As you said, for me too the bootloader seems to be unlocked.

EDIT: I think the problem for me is that I didn't notice that my NEE version of the tablet doesn't have ASK1 build.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Just for grins, I tried installing the latest ASK1 TWRP build over ASI4...and it seemed to work just fine. The "Only official released binaries are allowed to be flashed (BOOT)" message when flashing in Odin is something I only get when the OEM Unlock option is hidden in Developer Options, a state caused by VaultKeeper.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
If I already have the AS14 version install and working, is there a reason to install the ASK1 version?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Well, I wouldn't use a mismatched kernel if you could avoid it. And just noting that it boots and runs isn't exactly exhaustive testing. the point was more that it successfully flashed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 0KimT1:
Im currently on the ASI4 kernel. This might be a dumb question but does flashing the ASK1 TWRP zip not update my own kernel to ASK1? if not, is there a way for me to update my kernel version without having to wipe?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Flashing the ASK1 TWRP gives you a version of the boot image with the ASKI kernel, which is required on OEM builds to disable the Knox boot security features. If you already had those Knox features disabled with a ASI4 custom kernel, they you really wouldn't need that new kernel and could just flash the recovery.img that's inside the TWRP tarball or .zip update file. That said, I haven't noticed any problems running the newer kernel with the ASI4 vendor partition.

This is going to get even more interesting with more custom kernel releases such as [MENTION=1529302]ibanezbass[/MENTION]'s Infinity Kernel, which I'm planning to incorporate with my Nexus Stock custom ROM release.

I think the plan going forward is that my Odin tarballs will include the boot image, but the .zip updates (which you install from TWRP) won't. This will prevent you from stomping on a custom kernel when updating TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 1337haXXor:
Hmm, I'm still having the same issue. Had the device over a week now, so that's not an issue. Bootloader is unlocked. I do a factory reset, power off, boot into download mode, put TWRP in the AP section on Odin to flash, but it just hangs on boot.img.lz4. I'm still on ASI4, using the previously provided ASI4 TWRP image.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 0KimT1:
Every time I reboot, my Smart Lock 'trusted devices' list gets reset.

Does anyone else have this issue?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dcillusions77:
Same thing happening to me, is there any fix yet?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] IlPicchioRosso:
this twrp bricked my tab.

thank you for your ****.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Your tablet is not bricked., since I don't modify the bootloader. Just flash the OEM firmware in Odin and you'll be fully restored.

I'm on holiday until Jan 3rd and am about 8,000 miles from my build machine. If people are going to be rude, I'll just delete this entire thread and let you build TWRP on your own from the device tree that I've posted.

Until then, please read the original post carefully...especially the part that says, "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."

Previous builds are also archived here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gustutu:
Hi,

i'm tryning to install twrp-3.3.1-5-T515XXS3ASK1-20191207.zip.md5 i guess i need first to install twrp-3.3.1-5-T510XXS2ASK1-20191207.tar.md5 . Am i right?

Thank for your help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] maelstromm:
Your work is appreciated. Don't worry about people who can't follow instructions, understand the risks of rooting or installing non-OEM builds.

Enjoy your holiday!!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kriskurtgc:
probleme

Hi I have a problem, I have a tablet SM-T510XXS2ASK1, I try to put the twrp recovery, it go on the recovery , I have the logo teamwin but impossible to enter inside, it's block on the logo, when I reboot the tablet, I have the samsung logo with the warning, and it go directly in recovery mode with the logo teamwin and impossible to go inside the recovery, impossible to open the tablet normally on android, I can reboot in download mode, I use jOdin on mac, I downloaded a rom on sammobile who match my tablet, everytime they ask me the pit files, I do what they ask for have one but when I put start I have always corrupt files, I try to use Odin on windows, Odin don't recognize the tablet it stay blank, I downloaded the usb samsung drivers, it not work it not recognize the tablet, I don't know what to do because I can't use the tablet, I had a S7 edge in the past and never had this kind of problem it was really easy to root. But with the tablet big problem, need help if someone have some informations, I put some photos.

bootloader unlock

And impossible to switch off the tablet, everytime I try it reboot and go on the recovery mode

Thank you for your help
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Skyfire1:
I just viewed your ss, looks like you flashd wrong way. In odin it should look like this :
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Skyfire1:
So just flash oem firmware with odin and retry flashing twrp.

Good luck and merry christmas. :)

https://samfrew.com/model/SM-T510/region/XAR/
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kriskurtgc:
But I did that the other photo it's try to flash the rom , I put exactly the good files, it sucess for the TWRP but when he reboot it block on the logo Teamwin and I cant go inside the recovery mode
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kriskurtgc:
When I use the TWRP of this post, it block it don't flash, it's write running but nothing happen
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kriskurtgc:
Hi I downloaded on the link but I have exactly the same problem, everytime I want to flash a rom I have this error message corrupt file, I don't have one I downloaded who don't write that, I don't understand what's the problem
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] IlPicchioRosso:
Sorry

Sorry i was angry...but anyway. No, its complitely bricked, there is no fastboot and no recovery, im just ****ed up.

I am a usual modder, i know that i can flash by odin, but odin cant ricognize my tab...

Anyway sorry for my angry words, i know that you make best work that can you do.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
You may be a "usual modder" and that's why you're ****ed up. Samsung doen't do anything the usual way and doesn't even use fastboot.

And getting into recovery mode can be difficult, but your tablet is NOT bricked. I've had my T510 get into a loop where I had to let stay on till the battery ran down, but I was eventually able to get it working. But to help you, we don't need to know what it is NOT doing. We need to know exactly what it IS doing. Does it turn off? How are you turning it on? Take photos of what screens are showing.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gustutu:
Hi, how did you install the firmware ?

I tried this one twrp-3.3.1-5-T515XXS3ASK1-20191207.zip.md5 but odin is stuck at file analysis step i guess maybe because of .zip .

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Fredgido:
I can't flash on a T5110 because it says "Only official released binaries are allowed to be flash(BOOT)" but I don't see any guide for that?:(

bootloader is already unlocked...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Sounds like your bootloader was relocked by VaultKeeper.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Billy Botllerr:
I have the same problem, trying to flash TWRP with Odin leads to the whole thing hanging. The settings in the developers options remain ok. If vaultkeeper is a problem, how do I deactivate it?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Fredgido:
I read only way is having device uptime of 7 days is this true?

I already used time skip for OEM unlock.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
There are a bunch of posts in this thread on the woes of VaultKeeper. I'd start this this one.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] xchoch:
To unlock bootloader be complete - turn off, press volume up and down, and connect to pc via usb.

That solved my problem with hang while flashing with Odin..
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Billy Botllerr:
Thanks for the reply. I managed to boot into bootloader by this mechanism and the same thing happened. I tried it again, and no matter how long I held the vol-up & vol-down buttons, it wouldn't boot. Non capisco.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
It must be done exactly this way. Turn off the tablet. Plug the cable into the PC only. Not the tablet. Now, while pressing both the vol up and down buttons, plug the cable into the tablet. It will turn on right away to a green screen with instructions to unlock the bootloader. Again, the cable must be plugged into a PC with Odin installed, not a charger. And not into the tablet until the up and down are pressed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] tehkyle1:
There was December security update to t515xxu3ask5 and looks like I can't flash TWRP (stuck at File analysis..) - can you let me know if it is my issue or if the md5 needs to be updated?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Please confirm that the OEM unlock toggle in developer settings is still there, this is most likely the reason you cannot flash TWRP.

If the OEM unlock option is no longer there you may have to wait 7 days to get it back or you can factory reset the tab and during the setup process when you get to the date set it back a few weeks then complete setup.

Check developer settings and see if the OEM unlock toggle is back then try flashing TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dylanmurzello:
Without that option too I am able to flash it by unlocking bootloader ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mulperi:
[MENTION=903232]Magendanz[/MENTION], thank you for your hard work.

I noticed that the T515 tarball is actually a zip file with md5 checksum.

Perhaps that is why Odin hangs analyzing the file. Older Odin 3.07 did flash but failed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, this should be a .rar file with an md5. You can try fixing it by following this article, or wait until I return from holiday on January 6th.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mulperi:
YES! Can confirm successful TWRP + Magisk root on T515 with 1st of December 2019 security patch level (T515XXU3ASK5).

For anyone wanting to try it, this is what I did in ubuntu:

- Unpacking vbmeta.img.lz4 from the T510...tar.md5

- Extracting boot.img and recovery.img from T515...zip.md5

- Repacking them with "tar -H ustar -c boot.img recovery.img vbmeta.img > twrp.tar"

- Calculating md5 checksum "md5sum -t twrp.tar >> twrp.md5"

- Appending checksum to the tarball "cat twrp.md5 >> twrp.tar"

- Renaming the final flashable file "mv twrp.tar twrp.tar.md5"

I know, the last steps could be done in one command but anyway my "twrp.tar.md5" binary worked in Odin!

Thank you again [MENTION=903232]Magendanz[/MENTION]
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dylanmurzello:
There was an option in twrp resize system partition I did that now how do I get it back to default?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Billy Botllerr:
Thanks guys,

I have managed to unlock the bootloader and I have TWRP installed. I'm trying to decide what to do next. I have the T510XXS3ASK1 firmware, since I managed to upgrade it when I was trying to sort things out before. So I'd like to put another ROM on, but all the present options are based on T510XXU2ASI4. It's not clear whether flashing a new ROM is better with Odin or TWRP or both are OK. I want Magisk so I will install that and I'm not entirely clear about whether I still need the multidisabler. Thanks for your advice.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] razr2312:
Binary files request

Hi, I have the same model tablet with bootloader unlocked and the same version of firmware. Could you please upload these files? thanks in advance.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mulperi:
Please use the real file, it has now been fixed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Billy Botllerr:
I had trouble installing TWRP and at one stage allowed T510XXS3ASK1 to be installed. I eventually worked out how to unlock the bootloader as descibed by . I have now been able to install after unlocking the bootloader as described by xchoch. I was then able to install TWRP by Magendanz - https://androidfilehost.com/?fid=4349826312261654685
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
This link has now been fixed: twrp-3.3.1-5-T515XXS3ASK1-20191207.tar.md5
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] trabando:
Anything for T510XXU2ASK5 yet as i'm on this firmware ? Odin 3.13 and 3.14 stuck on recovery flash. I did everything by the book. Unlocked bootloader which factory reset my device. Instantly went to download mode and put the tar file in AP but odin stays on this

<ID:0/004> Added!!

<ID:0/004> Odin engine v(ID:3.1401)..

<ID:0/004> File analysis..

<ID:0/004> Total Binary size: 58 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> boot.img

<ID:0/004> recovery.img

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

On tablet it says only official released binaries are allowed to be flashed(BOOT)

EDIT:

Seems vaultkeeper has locked my bootloader in some way .. i flashed stock rom with odin and OEM unlocking is greyed out and says bootloader already unlocked. After trying again now it worked.

Thanks alot OP!!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
I can only use it after kernel source is posted, and the latest we have is T510XXS2ASK1.

Yeah, you're not alone experiencing problems with VaultKeeper. It's insidious.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DAOWAce:
Was this updated without a version change?

The one I installed on my device is: twrp-3.3.1-5-T510XXU2ASI4-20191019

The one on the main page now is: twrp-3.3.1-5-T510XXS2ASK1-20191207

Is there a changelog anywhere for this?

Edit: I must have originally downloaded/flashed at an inopportune moment. I remember reading the thread in early december, including the posts for the updated Dec 7 build, but nothing appeared to change on the main page so I guess I didn't think anything changed. Checking back now I see the differing version numbers and date.

So it's the November security update. And we can update without data loss just fine, aye?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, there was no change to TWRP...only the kernel update.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Billy Botllerr:
Hi Guys,

I've got my T510 working with Nexus ROM provided by Magendanz, but I'm having a few problems. It seems to be rooted ok with Lucky Patcher, TWRP and BusyBox being granted Superuser status. I can explore down to the root with Root Explorer. But the emulated/0/ contains a lot of garbage.

https://drive.google.com/open?id=0B3ae1Gh01NpndTFfc3p0bmJ0R2lyTUZWMS0ydnctcEU3NURJ

https://drive.google.com/open?id=0B3ae1Gh01NpnWHV3UkhDVnJiZXlXR1hXSlZiQnRINFNobUpZ

https://drive.google.com/open?id=0B3ae1Gh01NpnLXp0VTdjNHFMSmdxWk5vNGlhOGVNZ2lzZjN3

https://drive.google.com/open?id=0B3ae1Gh01NpnRXlKRlQxdTFpZjlMcnh5Rk1FOTlEYVRobFhB

There is no Download, Android, DCIM or other folders. When I try to create a folder named "Android", it fails. It also fails if I try to copy an obb folder into the emulated/obb/ folder. (All folders are designated RW)

I have also a problem where some apps can't write to the SD card, although the permissions seem ok. For example, if I try and change the icon of a program using Nova Launcher, I get a can't write to SD-card error.

I shall be thankful for any opinions, I have T510XXS2ASK1 installed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
Did you format data as instructed in the main post?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Danizer:
I have build no. T510XXS2ASH3. Can I use

twrp-3.3.1-5-T510XXS2ASK1-20191207.tar.md5
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Billy Botllerr:
I believe I did. I wiped all the date before installing the process and installed over a virgin process..