yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S9 series] ArchVisions:
Did you download it from the first post?
[Samsung Galaxy Tab S9 series] BigDog210:
Yes I downloaded it from the first post.
[Samsung Galaxy Tab S9 series] BigDog210:
I just deleted and redownloaded but still only comes out as image file.
[Samsung Galaxy Tab S9 series] BigDog210:
My apologies. I was unzipping it. sorry. ban me if need be. lol
[Samsung Galaxy Tab S9 series] Anghirrim:
Ah I think I know. Use the top right download button, not the one in the middle of the screen.

I don't know why but GDrive file preview offers to download the .tar content directly.
[Samsung Galaxy Tab S9 series] Anghirrim:
Lol no problem.

While for the vbmeta, that's indeed the disabled one that you need.
[Samsung Galaxy Tab S9 series] BigDog210:
Ok I just tried it but got an error about only official release binaries are allowed to be flashed. Thanks for the help. I don't think its possible for mine.
[Samsung Galaxy Tab S9 series] Anghirrim:
What's your device, is it a SM-X510?

Did you unlock your bootloader?
[Samsung Galaxy Tab S9 series] Anghirrim:
@BigDog210

I just realized that I did not detail enough the requirements to be successful in flashing TWRP.

So before you even start flashing vbmeta.img and the recovery, you should ensure that you:

- Run the latest X510XXS2BXB3 firmware update

- Have unlocked the bootloader of your tablet ==> This is most probably why you received the message about Official Binaries.

- Have a working Odin 3 + Samsung usb drivers installed on your computer (I think you have)

For bootloader unlock, please check the following instructions, taken from BlackMesa123's TWRP thread.

Open the Settings app, enter Developer Options and enable OEM unlocking (If you don't see Developer Options, enter into About phone>Software info and tap "Build number" 10 times to show it).

Enter Download Mode: to do so power off your device, connect it to a computer via an USB cable and hold both volume up and volume down buttons.

Long press volume up to unlock the bootloader. This will wipe your data and your phone will automatically reboot.

Go through the initial setup. Skip through all the steps since data will be wiped again later. Make sure to connect the device to Internet during the setup.

Enter Developer Options and check that the OEM unlocking option exists and is grayed out. This means our bootloader is unlocked and your phone has no KnoxGuard lock set.

And below, a complete guide for the above steps, with pictures, information, etc...

Unlock Bootloader on Samsung Galaxy Phones and Tablets [Guide]

A step-by-step guide on how to enable OEM Unlocking and unlock the bootloader on Samsung Galaxy smartphones and tablets, and disable the VaultKeeper service.

www.thecustomdroid.com
[Samsung Galaxy Tab S9 series] ArchVisions:
Well you need to unlock the bootloader, first. Just note once you flash TWRP Knox will be tripped and there is never going back! So, just be sure about this decision. You are the one deciding to do this. Once, Knox is tripped you can't use apps like Samsung Pass or Secure Folder.
[Samsung Galaxy Tab S9 series] ChingMiles:
Hello sir, I saw that you have an inquiry about TWRP on Samsung Galaxy A54 5G and you mentioned the problem of AVB signature verification because I faced the same problem as you while adapting TWRP for the variant A5460 of Samsung A54 5G Question, how did you solve this problem, I will be very happy to get your answer!
[Samsung Galaxy Tab S9 series] ArchVisions:
Hello! I suggest you check the Galaxy A54 TWRP thread that Salvo has made. You will find the little chat between us there. https://xdaforums.com/t/recovery-unofficial-twrp-3-7-1-0-for-galaxy-a54-5g.4656597/post-89426953
[Samsung Galaxy Tab S9 series] Anghirrim:
(Editing my previous message).

The key is to use magiskboot to unpack/repack your recovery.

When repacking, use the stock recovery.img as a source, and magiskboot will repack it with the proper footer.
[Samsung Galaxy Tab S9 series] ChingMiles:
Thank you very much, I have started TWRP correctly
[Samsung Galaxy Tab S9 series] Anghirrim:
If you need guidance about decryption, let us know.
[Samsung Galaxy Tab S9 series] Anghirrim:
Hey, just out of curiosity, did you manage to play a bit with TWRP this week-end?
[Samsung Galaxy Tab S9 series] Crashogre:
Sorry no, real life got in the way and I had no time. Hopefully I'll get some time by this next weekend.

Sent from SM-X510 using ReLabs
[Samsung Galaxy Tab S9 series] ChingMiles:
Since I quoted the device tree of BlackMesa123's Samsung A54 5G and made appropriate modifications, the subsequent progress went smoothly and the decrypted data was normal. I also successfully flashed the GSI later.
[Samsung Galaxy Tab S9 series] Anghirrim:
@ArchVisions managed to boot LeOS with DSU :)
[Samsung Galaxy Tab S9 series] Anghirrim:
New build with April 1st OneUI update support available.
[Samsung Galaxy Tab S9 series] Crashogre:
the Twrp flashed with no issues. Next will be to install LeOS gsi. I will do that on Saturday and will let you know how flashing a gsi goes.

Sent from SM-X510 using ReLabs
[Samsung Galaxy Tab S9 series] ArchVisions:
Awesome. Great to hear!
[Samsung Galaxy Tab S9 series] Crashogre:
I am able to switch to the January LeOS gsi using DSU Sideloader. February version doesn't seem to boot. @ArchVisions is this what you used and if so did you run into the same thing?
[Samsung Galaxy Tab S9 series] ArchVisions:
Yup I ran into the same thing. Same way both with DSU and actually flashing it. Do you have problems with touch whenever the screen times out by chance, but the spent still works after turning it on again?
[Samsung Galaxy Tab S9 series] Crashogre:
I haven't had the issue occur yet but I have noticed a slight response lag with the SPen after it turns off and I turn it back on. I am going to run it for bit under DSU and see how it goes. when you actually flashed did you use Twrp and if so what did you install it in? The install fails when I attempt putting it in the system item. Should it put in super?
[Samsung Galaxy Tab S9 series] ArchVisions:
@Crashogre you can't flash with system in TWRP because it is read-only. You need to enter fastboot in TWRP.
[Samsung Galaxy Tab S9 series] Crashogre:
doh, I should have thought of that. I read it somewhere before. Thanks.

Sent from SM-X510 using ReLabs
[Samsung Galaxy Tab S9 series] ldeveraux:
I don't think I updated to X510XXS2BXB3 before installing TWRP, because now I can only boot to TWRP. Well, TWRP and download mode, but not the OS. I assume it's because I used the disable_vbmeta.tar which is from a different version? I'm not really sure at all. I can't find the actual X510XXS2BXB3 image file anywhere for my SM-X510, how would I proceed here? I don't mind wiping obviously.

EDIT: Nope, now I tried to flash something else and I can only get into download mode. Can't even get back to TWRP. And I can't flash a bootloader because I think I OEM locked the tablet.

EDIT2: I was able to get the latest stock image from Frija and flash each image to recover. I started from scratch and can unlock my bootloader. I am unable to install TWRP correctly as it gets stuck in TWRP. I can power down, but every attempt to reboot to the system just boots to TWRP. To get there, I added the TWRP-3.7.1_X510_decrypt-X510XXS3BXD6.img.tar in the BL slot and the disable_vbmeta.tar in the USERDATA slot in Odin v3.14. What am I doing wrong?? I cannot seem to get a correct verity disabled vbmeta file, is that it?
[Samsung Galaxy Tab S9 series] Anghirrim:
Hello (or Bonjour),

TWRP should be flashed as "AP", not " BL".

Is it a typo in your Edit 2?
[Samsung Galaxy Tab S9 series] ldeveraux:
It's possibly a typo! I'll have to retry when I'm home later to confirm I've been using the AP slot. But the disable_vbmeta.tar on the first page should work with build BXD6?
[Samsung Galaxy Tab S9 series] Anghirrim:
Yep it should. It's the one Archvision used, and most probably Crachogre too.

If you flashed it under BL instead of AP, you'll have to reflash stock BL.
[Samsung Galaxy Tab S9 series] ldeveraux:
Flashing all 3 partitions from the stock image was the only way I could recover from my bad flash. I hope I was just being stupid and this solves it.
[Samsung Galaxy Tab S9 series] Anghirrim:
Keep us posted.
[Samsung Galaxy Tab S9 series] ldeveraux:
No I had done everything correctly, it only boots to TWRP. I flashed TWRP in the AP slot and disable_vbmeta in the USERDATA slot. it will only boot to TWRP at this point. If I try to factory reset in TWRP, it fails to mount /sec_efs and /data. Maybe when flashing incorrectly earlier I set it in a bad state? How can I reset the tablet to factory and start over? I have the BXD6 image from Bifrost.

Unlocking works, flashing slots seems to work, it automatically reboots me to TWRP. I can only get around in TWRP and Download mode bfeore I have to flash the AP, BL, and CSC slots from the image and start all over.
[Samsung Galaxy Tab S9 series] Anghirrim:
Are you back to a working state after flashing the stock firmware?
[Samsung Galaxy Tab S9 series] ldeveraux:
Yes I can always return to what I think is stock by flashing the 3 slots in Odin. But every time I do, the bootloader is still unlocked in Developer Options (the setting it blue so active, but greyed out such that I can't disable it). This even after a Factory Reset within the OS. What is my best course to start over from scratch here? I'm keeping hte box in case I need to return it, but I only have 10 days until I need to send in my trade-in.
[Samsung Galaxy Tab S9 series] Anghirrim:
So now, you're in a state with:

- Stock firmware

- Unlocked bootloader

Correct?

Can you eventually try with flashing KernelSu from Archvision first (along with the vbmeta), then TWRP?

I'd like to see if the stock kernel causes your problem.
[Samsung Galaxy Tab S9 series] ldeveraux:
Again, I BELIEVE I am on the stock fw, assuming I flashed back correctly. And I BELIEVE the bootloader is unlocked due to what I said about the slider icon.

How would I flash KernelSU from Archvision in Odin?
[Samsung Galaxy Tab S9 series] ArchVisions:
Hello! Actually, it is pretty easy. You just grab the .tar file I linked on the second post of the thread and flash it in AP. I am coming out with a new version soon with @fede2782's help to add support for Wireless DeX.
[Samsung Galaxy Tab S9 series] ldeveraux:
Grab the tar from where? This thread?

[CLOSED] Development for Tab S9 KernelSU (NINJASU)

KERNELSU FOR THE TAB S9 FE HAS MOVED TO A NEW THREAD: https://xdaforums.com/t/kernel-ninjasu-sm-x510-sm-x516-b-n-kernelsu-v0-9-3-for-samsung-galaxy-tab-s9-fe.4670346/

xdaforums.com
[Samsung Galaxy Tab S9 series] ArchVisions:
Yep.
[Samsung Galaxy Tab S9 series] ldeveraux:
When I try to flash KernelSU in AP and disable_vbmeta in USERDATA at the same time, it errors thekernel with KERNEL REV. CHECK FAIL. DEVICE:3, BINARY:2 (INIT_BOOT). It also says Secure Download is ENABLED in Download mode. What should I try now?
[Samsung Galaxy Tab S9 series] ArchVisions:
Shoot. That is because you are on the latest firmware version. Can you maybe wait a little bit? I have been working on a new release with Wireless DeX support. I mean like give me 2 hours or so.
[Samsung Galaxy Tab S9 series] ldeveraux:
No now!

JK, of course I can wait, it's been 3 days of dealing with this, I'll await your direction.
[Samsung Galaxy Tab S9 series] ldeveraux:
Any luck mate?
[Samsung Galaxy Tab S9 series] ldeveraux:
I can't even Magisk patch the boot.img, it just hangs. If I create a boot.tar with the original boot.img and flash to the AP, it boots right up again. What the heckfire is going on here?
[Samsung Galaxy Tab S9 series] ArchVisions:
Hey, so sorry to leave you hanging. I have just been trying to build another kernel I have been working on for the past 2 weeks. I will create a new thread with KernelSU for our tablets soon.

Sent from SM-A156U using ReLabs
[Samsung Galaxy Tab S9 series] Anghirrim:
That's so weird... Where it is hanging exactly?

While for your bootloader, can you please send us a picture of the toogle, showing if it's unlocked or not?

Thanks
[Samsung Galaxy Tab S9 series] ldeveraux:
I give up!
[Samsung Galaxy Tab S9 series] Anghirrim:
Too bad. That's definitely weird though.

Let us know when you want to give it another try.
[Samsung Galaxy Tab S9 series] ldeveraux:
You've not given anything else to try or I would. I have to setup this tablet ASAP lest I can't return the old one for credit.
[Samsung Galaxy Tab S9 series] Anghirrim:
I've asked you some questions to know exactly in which state your tablet is.

There was no answer so far.

Sorry, but helping you based on assumptions only is quite difficult.

So, in order to move forward, we need to understand where you are now.

Can you please let us know:

- The exact stock firmware name you took from the Net.

- Provide a picture of the Parameters=> About the tablet => Software info

- Provide a picture of the Parameters => Dev options => OEM unlocking toggle

Thanks
[Samsung Galaxy Tab S9 series] ArchVisions:
Ok, this I don't understand anymore. What do you expect us to do? You are providing no logs and almost no information.

Magisk should boot just fine. You did something wrong in the process.
[Samsung Galaxy Tab S9 series] ArchVisions:
Try this kernel I made yesterday. It isn't fully tested on my end so keep that in mind.
[Samsung Galaxy Tab S9 series] ldeveraux:
I thought I'd answered all your questions and I was awaiting a kernel to test something out. What that was, I don't know. I can't go back and install TWRP at this point unless it will not wipe, as I've already setup the tablet. But I'll answer your questions:

1) The image I downloaded from Bifrost is:

SM-X510_2_20240405043010_j6bt2xqnvj_fac_X510XXS3BXD6_X510OXM3BXD6_X510XXS3BXD6_X510XXS3BXD6_XAR.zip

2) Hopefully these images attach correctly

3)
[Samsung Galaxy Tab S9 series] ArchVisions:
This is just stock?
[Samsung Galaxy Tab S9 series] ldeveraux:
Stock what? I believe this is stock as I've said, just rooted with Magisk. The bootloader should be unlocked, I was able to use magisk to process the entire AP file, then flash it in Odin. That's how I'm rooted.
[Samsung Galaxy Tab S9 series] ArchVisions:
Ok, did you try the kernel yet?
[Samsung Galaxy Tab S9 series] ldeveraux:
I just got home, no. I know nothing about this kernel. Will it wipe? What happens when this doesn't work, how do i recover? If it flashes successfully what would i do next? You'll understand how I'm hesitant to flash something you made an hour ago and still needs testing.
[Samsung Galaxy Tab S9 series] ArchVisions:
Yeah, I understand. I managed to boot the kernel just fine on my Tab S9 FE. Everything seems to work just fine.
[Samsung Galaxy Tab S9 series] ArchVisions:
Wiping entirely depends on several factors. If you are with Magisk the best way to remove it is through the Magisk app and restore stock firmware and the flash my kernel for a clean slate so there is no traces of Magisk and so KernelSU and Magisk don't have conflict with each other.
[Samsung Galaxy Tab S9 series] ldeveraux:
Why would I do this? To what end?
[Samsung Galaxy Tab S9 series] ArchVisions:
Again to make sure to remove Magisk, and to have a clean slate. If you flash KernelSU you are dirty flashing. Which generally is not a good idea as it can cause a lot of problems underneath.
[Samsung Galaxy Tab S9 series] ldeveraux:
again, to what end? why do i want kernelsu?

Sent from Pixel 7 using ReLabs
[Samsung Galaxy Tab S9 series] ArchVisions:
Ah, nevermind.
[Samsung Galaxy Tab S9 series] Anghirrim:
As @Archvision said, nevermind for now.

You seem to be in stock state (rooted, but stock). Thanks for the pictures. The only weird thing is that you seem to have flashed a US version of the stock firmware (assuming you're in Europe), but @ArchVisions is in the US and everything works like a charm for him.

So, back to your first attempt with TWRP. From what I've read, you flashed it properly, TWRP in AP and disabled_Vbmeta in userdata.

Then, rebooted

right away

under TWRP?

Once you were done with those steps, you ended up with a tablet that could only boot under TWRP.

Before trying to factory reset under TWRP, did you mount and formatted /data?

Not managing to perform a factory reset under TWRP might be the culprit to your TWRP endless reboot issue.
[Samsung Galaxy Tab S9 series] ldeveraux:
No offense, I don't feel like being a guinea pig to something whose effects haven't been explained to me.

What exactly are you saying is in 'stock state'? I'm rooted, yes, but everything else is from the image I mentioned. I could never successfully boot to Android after flashing TWRP to recovery.

Also, I'm in the US, it's just a name...

Correct

Odin rebooted automatically after flashing, it rebooted straight to TWRP. At that point I could only reboot back to TWRP or enter Download mode.

Yes

Was I meant to manually mount and format data? I don't see that mentioned in the OP, I didn't see it in this thread. Consequently, I already mentioned this, but I tried whatever TWRP's version of a reset is and it said it could not mount /data, so could not reset.

OK so maybe this is the root of the problem then? Where is this step explained, and how should I mount the /data if TWRP can't do it automatically?
[Samsung Galaxy Tab S9 series] Anghirrim:
Oh don't worry, the nvm was just because the kernel itself shouldn't have any effect on your ability to use TWRP.

While for being a guinea pig, you're totally free to test it or not. However, there are only few people interested in this device for now and without testers, we won't go very far.

@ArchVisions was successful in using his latest kernel on his own tablet, others were happy with his previous build too. Thanks to the download mode, Samsung tablets are close to unbrickable so there is nothing to loose but time in testing it.

So once again, there is absolutely no problem in not trying the kernel that was mentioned, you're free to do whatever suits you. But we don't consider anybody as a guinea pig, it's more fellow members of a testing team. ;)

Stock state refers to stock firmware (the original firmware that comes with the device). So if you flashed the firmware you found on Internet and did not alter or modified it in any way, then your tablet is under the stock firmware (like just out of factory). You could attempt sending it back as you said. However I don't know how the warranty or right to send back work in your country, but the fact that you unlocked the bootloader and flashed custom recovery and also patched boot.img might have tripped it...

Ok, the steps are not mentioned in the OP because they're out of the scope as I overthought the fact that people would factory reset their device. I'll add it once we're done solving your problem.

Well, in principle it shouldn't fail erasing data. But not erasing data is definitely an issue.

The next steps below will factory reset your tablet, so you'll loose your setup. Do it only if you're ready to spend some time doing it. And I can't guarantee that it'll work. The TWRP is known to work and other users were able to flash GSI's though.

So you can try the following:

- Flash TWRP along with the vbmeta as stated in the OP (untick the autoreboot option from Odin)

- As soon as you're done flashing, reboot under

- On TWRP home screen, click on the "Mount" button, then mount data and cache

- Get back on TWRP home screen and select the "Wipe" button, then click on "Format data"

- Finally, "Swipe to factory reset"

This should, in principle, be equivalent to a factory reset from within the booted Android, and your tablet should start normally.

Again, do as you wish/can, there is absolutely no problem.

And if you want to stop here and send your tablet back to the seller, then remove root by flashing the stock firmware.
[Samsung Galaxy Tab S9 series] ldeveraux:
My point is that I've unlocked bootloader, rooted with Magisk, I'm going to leave well enough alone. I don't really need TWRP installed, I don't plan on installing CFW. I'm not returning my S9FE, I think you misunderstood. I have to send my previous tablet in soon to maintain the discount I received on the S9FE, and I didn't want to do that until I knew the S9FE was working. It's working well enough, so back goes the old tablet. Sorry for the confusion, and if there's ever a time in the future I feel like revisiting this, I'll be back.
[Samsung Galaxy Tab S9 series] ArchVisions:
Btw, the kernel has been tested by multiple people: https://xdaforums.com/t/kernel-ninjasu-sm-x510-kernelsu-v0-9-3-for-samsung-galaxy-tab-s9-fe.4670346

It works just fine. I am not forcing you are anything, as I don't personally want to treat you as a "guinea pig", but I just wanted to let you in case you ever want to switch as KernelSU is less detectable than Magisk and you have more control over root with KernelSU than Magisk.
[Samsung Galaxy Tab S9 series] ldeveraux:
This is the first in 3 pages you've explained 'why KernelSU'. Yes, I could have googled it, but I didn't, and I still don't see how it would have helped me get anywhere with TWRP. 😉
[Samsung Galaxy Tab S9 series] veekay:
Is there any possibility the screen off issue gets fixed or are we just stuck with keeping the tablet on during backup/restore?
[Samsung Galaxy Tab S9 series] ArchVisions:
AFAIK no. This is most likely something with the /vendor modules of the tablet not working properly in TWRP. I actually had similar problems with multiple GSIs, but me and @Anghirrim will look into it in the upcoming days, as OneUI 6.1 just got released for the tablet. We are currently waiting for Samsung to release the source code from the update for the kernel.
[Samsung Galaxy Tab S9 series] veekay:
I just went ahead and did the oneui 6.1 update and installed twrp - it was frozen for a bit so I thought it might not work with the update, but finally did load. Very disappointed this thing already came with A14 as most of the customization apps I use stopped support with A13.

Edit - seems the current TWRP cannot decrypt data in the oneui 6.1 update?
[Samsung Galaxy Tab S9 series] ArchVisions:
Yes, the current TWRP can't decrypt data on One 6.1 as we didn't add support for it yet. As mentioned earlier we are waiting for Samsung to release the source code for the OneUI 6.1 update. Till they release it, we will not be updating TWRP. The source code release can take days, or even weeks. I already sent a inquiry to them earlier today.
[Samsung Galaxy Tab S9 series] veekay:
Thanks. For now I'll just flash something that disables encryption. Seems DFE bootloops the tablet. Have to send in my old tablet for trade and need a replacement going.

Eh, stuck waiting it seems. Since the latest firmware isn't downloadable yet I can't reflash the stock firmware.
[Samsung Galaxy Tab S9 series] Anghirrim:
Hey,

DFE means Encryption disabler?

As long as you can boot into TWRP, you should be fine flashing stuff no?

Maybe someone could get the stock OneUI 6.1 firmware from Frija. I'll try if I have time today.

Where are you from? Would a EU firmware be OK for you?
[Samsung Galaxy Tab S9 series] veekay:
Right, TWRP is all I have access to. Oddly enough, Frija doesn't find any firmware for my device when I try using it. Had the wrong serial number it seems, it finds the firmware now. Still have to wait though for the TWRP update. Back to the old trust Galaxy Note 10.1 from 2014.
[Samsung Galaxy Tab S9 series] Anghirrim:
I'll give a try to a TWRP update today, just updating the decryption part.

In the meantime, can you please check what the DFE was supposed to modify? To see which partition has been affected.

Can't you reboot to download mode from fastbootd or TWRP then flash the stock firmware?

@ArchVisions , if you have time before I extract the stock super.img, can you please pull the /tee from the new firmware (if you're already on OneUI 6.1)? I should have time to do it this afternoon, but not sure.

Thanks