All are included and flashed by the main /e/ .zip
Hi there,
I have the same problem as lukap, but in addition my phone seems now bricked. I am looking for some help… @lukap did you find a solution ?
BRICKED PHONE, here’s what I did :
- get this vbmeta file from lineage support (LineageOS Downloads), and transfer it via Odin 3.13 as suggested, then reboot.
- the phone gets stuck on download mode giving those lines :
partition vbmeta
Reason avb_slot_verify.c:741: ERROR: vbmeta: Public key used to sign data rejected
avb_slot_verify.c:741: ERROR: vbmeta: Public key used to sign data rejected
CUSTOM vbmeta
VBMETA : no sign info
- I tried to restore it to previous state using Odin and the stock ROM, but the operation FAILS.
- After flashing again this vbmeta file i got from lineageOS support, the boot message was different :
<!>
partition vbmeta
Reason avb_vbmeta_image?c:206 ERROR: Hash does not match!
avb_slot_verify.c:638 ERROR: vbmeta: Error verifying vbmeta image: HASH_MISMATCH
CUSTOM vbmeta
VBMETA A528BXXU1DWA4, 61148404R
- After that I can’t boot nor restore stock ROM using Odin.
PLEASE HELP
In my attempt there was no vbmeta involved. The only two things that were necessary was
- flashing recovery with
recovery-e-2.7-u-20250109460550-community-a52sxq.img, and - sideloading e/OS with a provided zip (something like
e-2.7-u-....community-a52sxq.zip
everything else was preparing the phone, unlocking the bootloader, etc…
this phone, as far as i know, does not have a ‘regular’ fastboot mode.
i don’t thing vbmeta is needed in that way as instructed on some other places.
regarding bricked phone, i really don’t have any experience with this, i’m sorry. i hope someone can help you or you find information how to completely factory reset the phone.
Ok, I could finally install /e/ with some more operations. Here’s what I did, if it can help someone else :
- install TWRP following the link given here : https://www.reddit.com/r/LineageOS/comments/1iw778k/help_infinite_loop_on_my_samsung_galaxy_a52s_5g/
=> I used tar version and odin software
=> install goes on without any authentication error - Then I tried to stock rom, but installation failed.
- I tried to boot “normally” : no normal boot, the only available boot would be to launch automatically recovery mode
- from TWRP I could follow usual steps before install : data wipe then dalvik & cache wipe, which were successful.
- I plugged the device on my favorite Linux PC, put TWRP on “sideload” mode, then adb sideloaded my /e/OS .zip file
- sideload was successful. System reboot on /e/
I don’t understand what happened in the end, I can just see that it finally worked. Device seems to give two very shortlasting red messages at boot, then warn user about oem unlock, then boot on my tiny new OS.
Hope I won’t have problems with updates !
Btw, thank you @lukap for answering.
However I can insist on some points :
- it was impossible to flash /e/ recovery using odin, as I said the process would fail because of some vbmeta error. This is why I used TWRP, which I know better because of previous install on other devices.
- I’m not sure, like you, that it is necessary to replace this vbmeta file as a pre-install operation as suggested in the /e/ install webpage. At least, this vbmeta problem does not seem to prevent from installaling TWRP recovery… Maybe it would be worth trying to skip this install step in the given procedure.
- hope my experience can help other users. I think some things could be improved on the installation procedure : giving a better procedure on how to get this “vbmeta” change before install, if this step is really necessary ; or invite people to skip this step, which can prevent from bricking the phone…
Thank you folks
Thanks for this list, that’s very helpful!
I got an issue with setting up my Samsung A52 SM-A525F/DS as I’m not able to turn on the OEM unlocking. The button in the developers settings is gray and I can’t active it.
As I’ve heard, that could be now a problem with all the Samsung phones, as Samsung removed the bootloader unlocking with One UI 8 (https://www.reddit.com/r/Android/comments/1mabuht/samsung_removes_bootloader_unlocking_with_one_ui_8/).
Does that mean, no Samsung is anymore available for e/os or did I misunderstand that?
Is there a way how I can still unlock my bootloader?
Thank you!
Do you have this One UI 8 ?
If no … there is plenty of good advice in this thread.
i believe that it will be down to following the Pre install instructions in an obsessively exact way. Note the internet connection, I think Wi-Fi is recommended as OK but maybe mobile data connection is better (Personal view even though this would alert your SIM with Samsung and Google).