Samsung SM-T870 no vbmeta.img file in downloaded zip file for the device

Hi,

As the subject say there is no vbmeta.img file in the e-3.1.1-a15-20250830521751-community-gts7lwifi.zip file.

There are no previous version available in the download section. It would be nice to have this file in the zip. @Manoj can you maybe pass this on to the team.

For the great helpers around here, what is the best work around? I see some posts in the search of the site. Where is best place to get the payload file or should I find it in a Lineage build?

Any ideas welcome :blush:

You can try getting the vbmeta using Payload dumper. Lineage builds if for the same OS version should also have the vbmeta.
Passing on the information to the team.

I found the file I needed here:

https://download.lineageos.org/devices/gts7lwifi/builds

Just having issues getting to recovery, I recall it’s tricky.

I ended up bricking or softback this device. Anyone know where you find the stock ROM, the legitimate way LOL. What a joke all the websites that put you in a loop, then they want me to pay, like I would trust the site after that LOL

Anyway my error is:

partition vbmeta
Reason vbmeta: Public key used to sign dar rejected. (05)
CUSTOM vbmeta
VBMETA : No sign info.

Samsung do not publish their own builds so as I understand it you are down to one of four:

I cannot say which is best for a free download but if free, in my experience, it will be slow.

1 Like

aidb… I was unaware of this, thanks for the information and links. I think it is very short sited on Samsung part not to offer official stock ROM on their own site…

Judging by the error I get do I need to go back to stock or can I recover from this error in some way?

It is hard to brick a Samsung. The Odin mode seems made very strong, so all the time you can return to Odin mode your phone is ok.

It has been said borrowing a Lineage vbmeta will work but ofc it probably needs to be a fully matching build.

I has been said that vbmata may not be required on every device every time, idk.

Did you check out getting it by payload-dumper-go ?

Samsung errors seem always to point as “must come home” so perhaps just search the error rather than be directed by it.

1 Like

I will have a look at payload-dumper-go. So I am looking on git-lab, does it pull the ROM from the device or something?

As Post #2 [Walkthrough] Extract eRecovery and boot images using payload-dumper-go

Although that is a negative error does it stop progress, that is prevent the next step ?

1 Like

I will try some more attempts to load recovery tonight and this weekend or I will bit the bullet and get the ROM from one of those sites.

I have an extra long weekend this weekend there is a holiday on Tuesday and we are closing Monday also. I keep you in the posted :smile:.

I will also try to improve the instructions on the gts7lwifi page. They omit having to have the USB cable plugged in in some steps.

1 Like

Hey, One of the sites is working https://samfrew.com. Thanks again aibd…

Edit: I see what you mean by slow, death by download LOL. I think one site asked for like 12-13 Euros so like $20 Canadian. But I see this website will let me have for $10 US 30GB and 30 days. Once I get home I guess I will just pay. By the time the free one is finished here at work I will be retired…

1 Like

Best download speed are

sfirmware
and
samfw

1 Like

I ended up using samfrew. I downloaded two firmware so far. I wish I saw you post eariler piero :smile: The above site dropped the connection many times using Firefox (at 1GB) so I switched to Brave and was finally able to download the second firmware.

I have restored the tablet. I will take a try again at it this weekend.

So I am back at Stock ROM A13, in developer mode, have OEM unlocking ON and USB Debugging ON.

When I try to flash vbmeta.tar or recover.tar I get: “custom binary recovery blocked by oem lock samsung.” There are no accounts on the device, did a factory rest and repeated all steps with same issue. I just booted to download and it does say FRP lock OFF, OEM Lock ON. Any ideas?

OK I was able to unlock the bootloader by a long press on the volume up key once in download mode. I think that step is missing in instructions (at Lineage and eOS).

1 Like