yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, the MTP fix for TWRP and AOSP breaks MTP on the Samsung stock firmware. I don't actually include the MTP fix in the boot partition for this reason, but by installing Magisk you're now loading the kernel from TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jimbo77:
Bummer so it's the same as the S10+ ianmad fixed MTP in TWRP while keeping MTP while booted to magisk Rooted system.

Will this commit help in anyway?

https://github.com/ianmacd/twrp_beyond2lte/commit/1d59218b065578d5a8ff40f2d1e89ad76e246d93

Thanks!!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, and it just means that I'll need to modify init.exynos7885.usb.rc in the vendor partition of my custom ROMs with this same fix, but it overall looks much simpler than maintaining two custom kernels. Thanks for the link!

I should have new builds of TWRP out shortly. Custom ROMs may wait for the next releases of the kernel and/or AOSP from [MENTION=1915408]phhusson[/MENTION].

UPDATE: The build 20190924 is posted, and it includes this fix for MTP with Magisk.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] jimbo77:
I can confirm it works wonderfully now. Thank you!!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iIuvweed:
Does this only work for 515?

What about t517p? (Sprint)?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
I'm game, if someone wants to send me one. ;)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iIuvweed:
I'd send u mine

Sprint talked me into it anyway. But it's my wife's and don't need that drama haha. Hope someone gets one to you, dunno much about these tabs if it's even worth the hassle.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Fin9ers:
Hello,

Well done on developement, but I am having some issues...

So, i started out with OEM firmware (T515XXU1ASEH).

Followed the instructions to the nail.

Rebooting into recovery causes a freeze at the TWRP splash screen.

I then tried the stock nexus ROM mentioned as that flashes TWRP also, but same result. Freezes at TWRP splash screen...

I installed OEM firmware again to get back to a working tablet. But now im stumped...

Where do I go from here?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
The problem is that you didn't do a factory wipe in stock recovery prior to flashing TWRP. Unfortunately, TWRP currently hangs on the splash screen if it encounters file-based encryption (FBE), so you've got to wipe the data partition first and then reboot directly to the bootloader to flash with Odin.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Fin9ers:
I did perform a factory wipe in stock recovery though :/ ...

I just tried again and this time it worked, possibly might have been a OEM firmware mismatch.... I was tired last night trying to piece things together.

Anyways, TWRP now working. Now I'm trying out your nexus stock ROM :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] davekaz:
I could do this fine but cant get nexus rom going keeps failing at product during Odin. I though it was a bootloader issue. I've downloaded it several times but still fails and have to odin stock to come back. Wrong thread I know.. sorry
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
I've had it fail because I let it reboot to system after the factory wipe, and the first thing the OEM system does is restore file-based encryption. Basically, if you let it get to the boot animation, you're hosed and need to repeat the factory wipe from stock recovery.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Pinage:
When flashing recovery via Odin ap, I got this error only official release binaries are allowed to be flashed (boot). The loading bar just struck there forever. Am I doing something wrong? I did the oem unlock and hard reset beforehand already.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
That message means that you haven't completed the bootloader unlock. You've got to long press the Vol Up button from the blue Warning screen after setting OEM Unlocking to finish the job.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Pinage:
Thanks for replying. But now what should I do? Restart the whole unlock process? If yes I no longer see the oem unlock option under developer settings. Possible to advise me further. Thank you
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Well, I'd first try rebooting with the USB cable connected holding Vol Up & Vol Down. If you get the Warning screen, long press the Vol Up to complete the bootloader unlock. From there, you can try again.

If you've allowed it to reboot and triggered VaultKeeper, the OEM Unlocking setting will be hidden and I usually just do a clean flash of the OEM firmware to get me back to square one.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Pinage:
I tried to download Odin and oem firmware to reflash to stock but it seems Odin feeling failing. I already installed the Samsung drivers and enter download mode by pressing volume up and down before plugging in USB cable to computer. Is there any step I miss out?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DanXbix:
These images are specific to those rom in title releases can I flash with later oem stock image? I am on the latest Aus XSA firmware and it fails even after completed unlock wipe etc
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Pinage:
I encountered same issue and is stucked at twrp logo. How did you get out of it mind sharing?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PopCaps1996:
flash stock rom/then reboot to stock recovery/wipedata/flash twrp/reboot to system complete setup/reboot flash root
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Pinage:
I'm stuck now with juz twrp. How do I flash back to stock ROM using Odin? What mode do I need to be in? I juz can't seems to get it now I'm all stuck
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PopCaps1996:
download mode an yes flash with odin
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Pinage:
I tried but Odin keep say fail. Juz to confirm I press Vol up and down before plugging in cable to get to download mode right?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Fin9ers:
That is correct. I noticed that entering download mode via recovery always ended with failure to flash. No idea why, but the vol up+vol down while insert USB c worked.

I think what I done was allow reboot after flashing twrp instead of going direct to twrp recovery. This caused freeze.

So, flash stock firmware. Then go stock recovery, wipe data/factory reset. Then reboot tablet but get ready to boot download mode straight away. As soon as screen goes black to reboot, hold vol up+vol down and insert USB c. Flash TWRP and hold recovery key combo straight after reboot, before Samsung splash screen appears. Wipe data in twrp and your golden. Remember to also install Multidisabler.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 7Nanashi4:
I am also running into problems!

I tried to flash twrp from a different source (found xda too late)

And after the reset, I allowed the system to boot back up and did the setup. Because of that, I think I was stuck with a frozen twrp-screen without any buttons.

Today I finally made it to Download-Mode again holding +/- while startup. Accidentally I selected the option lock bootloader and was prompted with the question if I want to factory wipe the tablet. I confirmed and now I'm stuck with a loop into Download-Mode and in the left upper corner is this prompt in red letters:

VBMETA: Error verifying vbmeta image: OK_NOT_SIGNED (3)

CUSTOM VBMETA

VBMETA : No sign info

VBMETA ,

Any ideas what I need to do now? Just flash a stock rom or a stock bootloader?

Btw ... I am completely new to flashing and rooting so I am a bit unsure what to do, being the reason for my post.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Pinage:
Great your advise works wonder!! Tku so much!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] PopCaps1996:
i believe you just hard brick your tablet an you can not recover from it! since you locked your bootloader back up on a corrupted system! I suggest next time (KNOW WHAT YOUR ARE DOING BE4 YOU START)an i may be wrong cause i never tried flashing stock ROM to a Samsung device with a locked bootloader
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
No, you should be able to flash OEM firmware in Odin to reset to a known good state and start again. You can download them here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Samsung just posted the kernel source for T510XXU2ASI4, and so I've updated the TWRP build to use it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 7Nanashi4:
Thank you very much.

I bought the tablet in Mexico and for that I have two options:

PDA/AP Version T510XXU1ASEF

CSC Version T510OWO1ASE2

MODEM/CP Version T510XXU1ASEF

Region MXO — Mexico

Build Date 2019-05-27

Changelist 15874928

OS Pie

OS Version 9

----------

PDA/AP Version T510XXS2ASH4

CSC Version T510OWO2ASH1

MODEM/CP Version T510XXS2ASH4

Region MXO — Mexico

Build Date 2019-08-06

Changelist 15874928

OS Pie

OS Version 9

----------

Beware the noobie-question

Does it mater which version I choose? I think it does but how can I find out which is the correct version? Or is there a always-safe-choice?

I bought the tablet at the end of July so I would choose the first option (T510XXU1ASEF) ...

Sorry to bother you all with stupid questions but to avoid more trouble, I think its better to ask stupid questions than doing more stupid things :eek:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Well, TWRP is going to use a custom kernel based on the latest kernel source release, which as of yesterday is T510XXU2ASI4. The custom recovery uses this, but it will also substitute a new boot partition with the custom kernel so that Knox boot security features are disabled and you can still boot to system. I'd think the goal would be to match them as closely as possible.

That said, often newer bootloader releases will prevent downgrading, so it's not entirely without risk to use the newest release. The safest bet is to always match the version exactly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 7Nanashi4:
Ok, I get that ... But how do I find out the correct version to fit? I can't boot the os to view the settings. Is there a different method to find that out or is it ok to just flash an older version, just to be shure?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kenaz Rune:
Heimdall Package for TWRP 3.3.1-3

All,

Last night, I finally made some time to update TWRP from the original release to -3. Since I'm on Linux and JOdin 3 isn't clear to me (it uses Heimdall under the hood, though), I extracted the archive and built a Heimdall archive, which I'm happy to share. However, I need someone to give me instructions on where and how to post the file.

I'll look into doing this with the Nexus ROM eventually.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] KILLTonz:
So I've been reading through the forums for an hour now. I'm just a regular user of this tab a sm-t510. What exactly is this "recovery" thing for ? Is their any benefits that come with this process?

Currently using tab a (:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] SMOKEmcoc:
why isnt this working on my tab? i had to factory reset my tab now im trying to root again....i flash twrp to my tab and it stays frozen on teamwin. there isnt a firmware update on my tablet. SM-T510. ive checked for updates and there isnt any. i dont understand how the twrp recovery is updated for ASI4 but there isnt such firmware for my tab. only ASEF. ive looked on sammobile and many other sites and the only ones who have an updated firmware are everyone else but the US (cellular south)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] beta990:
Thanks for releasing TWRP for this device. :)

I'm a bit confused about the Magisk root part - is it simple flashing it in TWRP or do I need additional stuff?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
New v3.3.1-5 release posted that avoids the hang on splash when the user data partition is encrypted (but file-based encryption is still not supported). Also now includes OTA update (.zip file) suitable for installing from TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Qrion:
Hi newbie here. i tried to root my SM-T515 without doing much research and ended up with bootloop. The device in now stuck on TWRP logo and i am unable to shutdown or boot to recovery or download mode.

1. Enabled USB debugging and OEM unlock

2. Booted to Download mode and removed OEM lock by long pressing vol up.

3. Rebooted to bootloader and rooted using Odin3_v3.13.1 and twrp-3.3.1-1-gta3xlwifi.tar

4. Odin root PASS

But after reboot the device it stuck on TWRP splash screen. Have i bricked the tablet or is there any hope of recovery?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Just connect the USB cable, return to Download Mode (hold Power & Vol Down for 8 secs, then hold Vol Up & Vol Down) install the latest (v3.3.1-5) version of TWRP here. This version doesn't hang when it encounters file-based encryption.

Once you reboot into TWRP v3.3.1-5, do a factory wipe and then reboot to system.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Qrion:
Thanks a million, i was able to exit the boot loop. I tried the SM-T515: twrp-3.3.1-3-T515XXU1ASEH-20190924.tar.md5 with same issue.

Would the SM-T510: twrp-3.3.1-5-T510XXU2ASI4-20191019.tar.md5 work on my T515?

Thanks again, really appreciate your quick help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
The SM-T515 doesn't have that fix yet. Sorry, I just haven't had the time and I'm also waiting for the September 2019 kernel source to be posted.

The SM-T510 version of TWRP *might* work, but I don't have the the SM-T515 to confirm.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Qrion:
Thank you, ill wait until a fix is available. In the mean time any workaround to recover the device temporarily?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Just revert back to the OEM stock firmware and repeat this time being sure to do a factory wipe in stock recovery before flashing TWRP or a custom ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I didn't think a wipe would be needed if just flashing recovery, but I was wrong. I installed TWRP without wiping first and even though wiping once in TWRP fixed the bootloop, it DID NOT solve all of the problems. The file system was still all messed up and a lot of apps wouldn't function. Starting with MyBackup Pro not restoring the backup. I haven't tried it with a wipe prior to flashing TWRP yet. It's now 1 AM, so it will have to wait till tomorrow.:crying:

edit: I did notice there was a setting about encrypting the data files that I've seen on my T580. Maybe that has to be turned off prior to flashing TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, this TWRP build can't handle encrypted file systems. Also, it comes with a custom kernel to disable the Knox boot security features. If you mix and match that packaged kernel with a different OEM build, you're inviting problems like what you described. That's doubly true if you try to use a SM-T510 build on a SM-T515.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Qrion:
Thanks you! That worked perfectly.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Almost, but no cigar. I started from scratch after re-flashing stock ROM and wiped factory reset prior to flashing TWRP. Worked great. Booted system and was able to restore from MyBackup Pro. Installed Magisk via TWRP. Took a long time booting but finally made. Tried turning of data encryption via /Settings/Security/Other security settings/Strong protection disabled. TWRP still shows Internal folders with encrpted folder names and Backup won't backup the data partition.

How do I turn the encryption off?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
After installing the Multi-disabler (which will disable forced encryption), just do a factory wipe (Wipe->Format Data).
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] kylerxx:
Is it hard-bricked ?

Hey guys, so basically i had magisk root with everything working properly, but i had an issue with the tab so i decided to update the kernel to lastest one, I followed all the new steps and everything went smoothly, had twrp installed and tab was working, decided to boot back to twrp to check if it was still working and now I believe my device has been hard-bricked. When I try turning it on it shows the "Samsung Galaxy Tab" Logo with "Protected by Knox" screen with a message in red on the top left side of the screen saying "Only official released binaries are allowed to be flashed" if I let go of the power button the screen almost instantly turns off and if I keep it pressed in the screen just sits there.

**edit** : Fixed it by plugging the tab onto my pc and pressing the 2 vol buttons to put it back to download mode
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MossyTC:
Not a big issue, just reporting so that you know.

In v3.3.1-4/5 after Reboot | Power Off, powering up boots into TWRP again.

The only way to go from TWRP to System is Reboot | System.

AFAIK this was not the case in v3.3.1-3.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I think I may have succeeded in brick my T510. I lflashed "Multi-disabler" and then formatted the data partition. Now, no matter what buttons I push, including holding both vol up and down, the tablet boots to "Download" but with an error message saying vbmeta.img has "no sign info" and NOTHING will flash. Not TWRP or stock ap, bl, csc. And it won't turn off. If I use power and vol down, it shuts down but immediately boots back to the same screen. TWRP acts like it is flashing but stops about 90% as if the bootloader is locked. But I can't get to the unlock holding vol up and down.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Do you have a USB cable connected? If so, just holding Power + Vol Down for 7 seconds and then immediately switching to holding Vol Up + Vol Down should get you back into Download Mode.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Cable in or out makes no difference. And my problem isn't getting into download mode, it's getting out of it. Doesn't help to be in download mode if nothing will flash. I need to be able to unlock the bootloader and/or wipe and reset. The normal procedure would be to uplug the cable and turn off the tablet. Then, while holding vol up and down, plug the cable back in. But I can't turn the tablet off, so this doesn't work. If I hold vol down and power for 7 seconds, the tablet turns off for about 1 second but then boots right back to the download screen. Even if I release the power button as soon as the screen goes black, and switch to holding both vol buttons, it still boots back to the same screen. And it does with the cable in or out. Makes no difference.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
If VaultKeeper relocked your bootloader (likely because you forgot to install Multi-disabler before rebooting), then you've got to flash an OEM firmware release in Odin and start the process over.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I've tried both the ASC7 and the ASEF and neither one will flash in Odin. Though I've flashed the ASEF several times before this problem popped up.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, that's expected now that your bootloader is relocked. You can now only flash official OEM stock firmware, which you can download from the link I provided above.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
I clicked on the link in your post and scrolled down to North America and clicked on United States and that where I found the two versions I downloaded. Was that wrong?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Update: I let the tablet battery run completely down and then held the up and down vol buttons while plugging in the charger cable. This put me back in the screen allowing me to unlock the bootloader. Now, if I just turn it off, it bootloops at the first Samsung screen with the yellow triangle showing it is unlocked. But, if I hold the up and down, I can get back to the download screen. But it still won't flash anything. I'm in the process of downloading the AS14 stock version but it still has a couple of hours to go.

edit: Let it charge overnight and it flashed AS14.:D:D So I'm back up and running. I think I'm just going leave it as is for awhile till the zip version for TWRP gets done.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] fpozar:
Quick question, rooting by just flashing Magisk with TWRP won't work? What about Lineageos official root extension? Sorry, I'm new to Exynos rom scene

Edit : I have 515 model.

---------- Post added at 12:14 PM ---------- Previous post was at 12:00 PM ----------

Also, T515 open source was updated and is now in equal state as T510, in case you didn't see ?

https://opensource.samsung.com/uploadSearch?searchValue=t515
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] MossyTC:
Quick answer, Magisk v19.3 or later can be flashed with TWRP as normal. Needs to be re-flashed when you update TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Apparently it IS wrong. Neither of the XAR region versions would flash, but I got the AS14 version working. It defaults to Italian but it allows you to choose U.S. English, so that's no big deal. Don't know why the U.S. versions fail.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] fpozar:
Many thanks :good:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] 7Nanashi4:
I wrote a post starting with #118 through #125

Last advice from Magendanz was, that I download the original OEM firmware and flash it to solve my problems of that:

I'm stuck with a loop into Download-Mode and in the left upper corner is this prompt in red letters:

VBMETA: Error verifying vbmeta image: OK_NOT_SIGNED (3)

CUSTOM VBMETA

VBMETA : No sign info

VBMETA ,

I didn't have the time to work further on the tablet so I left it for a few days. And then I was able to break the loop into Download mode just like that. Now I am stuck with the flashing SAMSUNG screen but I am also able (didn't do anything) to enter the TWRP (Version 3.3.1-1) by holding Power + VOL+ Keys during the restarting process. That didn't work before because I was prior to the Download-Mode loop stuck with a TWRP-Screen loop without any functions ... don't know why it works now :confused:

What should be my next step? I learned from my mistakes and won't just try stuff.

.) Should I still flash the OEM firmware? I found 2 versions:

PDA/AP Version T510XXU1ASEF

CSC Version T510OWO1ASE2

MODEM/CP Version T510XXU1ASEF

Region MXO — Mexico

Build Date 2019-05-27

Changelist 15874928

OS Pie

OS Version 9

----------

PDA/AP Version T510XXS2ASH4

CSC Version T510OWO2ASH1

MODEM/CP Version T510XXS2ASH4

Region MXO — Mexico

Build Date 2019-08-06

Changelist 15874928

OS Pie

OS Version 9

----------

If necessary how can I determine what is the correct version? I installed every update until the end of September. Is that meant with the "build date" or does that mean when I bought the tablet? Still confused with that point ... :confused:

.) Should I just wipe the tablet using TWRP?

.) Should I just install Magisk using TWRP?

Hopefully, I described everything good enough.

Thank you for your help in advance!

Best reguards