How can I find "vbmeta.img" for "a73xq"?

Hi, to everyone.

I’m new to Custom Rom things. I wanted to install /e/os to my Samsung Galaxy A73 5g “a73xq“ phone. I’ve done some instructions from Installation Guide. Such as adb, usb debugging, downgrading from android 16 to latest android 14 version. (I don’t know if CSC is important, is it?)

But when I’ve came to Pre-Install Instructions, I couldn’t find “vbmeta.img“ in “/e/OS build or /e/OS recovery zip folders“ (There is no recovery zip folders, only recovery img?) I’ve downloaded all 33 version of /e/os builds (A13-14-15) and I still couldn’t find it in neither of them. Guide says I can also find it in Lineage OS website but what i find is vbmeta.img for LOS 23.2 which is using Android 16. So I’m not sure if it is compatible with /e/os a15 version.

What would you recommend me to do now? Is there a way to find this file, or should I wait until A16 Community Version come to “a73xq”? If that’s the case, would installing LOS 23.2 for now, will cause any problem for me when I want to switch to /e/os? Also, if there is anything I must know beside the guide, please let me know.

Have a good day!

*English is not my native language, as you can see from the flag…

Hello @Tsuem, Welcome to the /e/ users forum.

Well done !
But if you want /e/OS-a15 or /e/OS-a16, so latest Samsung a15 is the best recommended.
Absolutly void a16 that include OneUI-8 and nomore allow OEM bootloader to be unlocked !

I believe custom vbmeta is system less so you can use this one if you don’t find one provided by /e/.

Install /e/OS on a Samsung Galaxy A73 5G - “a73xq”

1 Like

Hello @piero, thank you for your respond. And also for welcoming.

I was also thinking if /e/os using a15, why we are supposed to install a13/14. I guess, the guide is not updated in that case..?

I will try it with that then. I hope it works. Thank you :slight_smile:

If official instructions from /e/ is to get a14 firmware as a base, you are right with downgrading firmware to a14 Install LineageOS on a73xq | LineageOS Wiki recommend the same.

1 Like

I downgraded again. I completed all the instruction before Installing a custom recovery using Odin

Now, I’m trying to flash the recovery image but Odin closes itself when I click the “Start” button.

From /e/ instructions, i understand you need to unlock the bootloader between flashing vbmeta and recovery

On the following screenshot we see OEM unlockable → (U)
but still locked bootloader → OEM LOCK : ON

Some others instructions recommend to unlock first, then put the recovery.tar in AP and vbmeta.tar in BL, or to use 7zip.exe to create an unique .TAR including both, and put it in AP slot.

I’ve checked this. It’s OFF.

I’ve tried but it’s still not working. Program closes itself immediately when i hit the Start button.

I haven’t tried it nor understood how to do it. I’m searching right now.

Also sorry for the late response, I was busy..

I have seen that in the past, but can’t remember the tip.

Did you reboot Odin ? then plug the device to get the “added” notification in the log.

Did you tried version 3.14 ?
samfw.com

It worked for vbmeta, but nomore for recovery ?

I’ve tried with 3.13.1, 3.13.3, 3.14.1, 3.14.4 versions.

All of them flashed vbmeta alone but not the recovery tar (or ap recovery.tar + bl vbmeta.tar)

I also tried that too.

Hmmm. Can this be about vbmeta?

You told it it musn’t be crucial but could it be? I can try with the lineage os recovery.img. If it will be flashed, then the vbmeta is the problem? If it will also error with Lineage recovery, then I don’t know what to do.

Does installing Lineage OS, make any complication when i will switch to /e/os? If it does not, then I will try Lineage OS first.

You also can use the lineage-recovery to install /e/

Have you opportunity to try installation on a linux machine ?

1 Like

I managed to flash lineage os recovery. But I got some errors on adb sideload. adb terminal stopped at %47 and this errors on the phone

ERROR: recovery: failed to verify whole-file signature

Update package verification took 97.7s (result 1)

ERROR: recovery: Signature verification failed

ERROR: recovery: error: 21

Now program asks me: Signature verification failed. Install anyway?

No/Yes

Unfortunately, no. I do want to switch to linux someday but I haven’t done yet.

Is time restriction only for new users or for every one? It didn’t let me post until one hour completed?

Signature mismatch :

YES !

Get to trust level 1 by…

  • Entering at least 5 topics
  • Reading at least 30 posts
  • Spend a total of 10 minutes reading posts
2 Likes

@piero

Now, I’ve installed /e/os :slight_smile: Thank you for all the care, it helped a lot. I appreciate it.

1 Like