vbmeta error no sign info (samsung A51 exynos 9611)

[testz-99]

Hi When using AP magisk patched tar it makes vbmeta error with dowload screen: ODIN MODE (AVB Fail), vbmeta: error verifying vbmeta image: OK_NOT_SIGNED, VERIFICATION_DISABLED bit is set, custom vbmeta No sign info, vbmeta . magisk_install_log_KEEPON.log magisk_install_log_KEEPOFF.log

SM-A515F with A515FXXU1ASKJ firmware Android 10 has 2 vbmeta: vbmeta.img and vbmeta_samsung.img in AP. vbmeta_stock_imgs.zip

Only flashing boot.img makes bootloop. Magisk versions tested from 19.3, 20.3 to latest canary build.

TWRP is not available. The error appears after flashing and changing vbmeta.img. Bootloader is unlocked, KG is checking. With original vbmeta magisk recovery is not accepted.

What should be done to work?

[testz-99]

Still no success

[testz-99]

Some logs in here to help. Only flashing boot.img from the magisk_patched.tar work but with no magisk available. Flashing only boot patched img makes bootloop. Flashing all tar makes vbmeta sign error.

[hanung665]

I'm waiting for working solution <(",)>

[raw-raw]

I'm waiting for working solution <(",)>

Many people are. Please keep discussions to xda and away from github.com and only comment here if you have something noteworthy to add to the issue.

[kekoDev]

I faced the same problem Is there a solution?

[ahronshor]

here in xda is a full tread about this issue for a51.

But the solution to make a signed recovery for each device is not so good for magisk. Note that the same problem was also found in note 10 lite n770f, And probably that's what will happen even in many new Samsung models...

[Speeskees]

I can confirm the issue also exists on the Note 10 Lite SM-N770F when patching the AP, but when patching the boot image only, the device is succesfully rooted and does not enter a bootloop. The downside is that the CTS profile component of SafetyNet does not pass after rooting using this method. (or at least, for me: someone on XDA claims to have rooted his phone by patching the boot image, with passing SafetyNet.)

[nehaonestore]

I have tried to patch only boot.img but its showing unable to do normal boot.

[Speeskees]

I might need to add that I did a factory restore after patching the boot image. Otherwise, dunno why it works for me.

[osm0sis]

Is this still an issue with the current Magisk Stable?

[jhhuisman]

Is this still an issue with the current Magisk Stable?

I think so yes. Yesterday I spent a night trying to root the A51. Will keep an eye on this issue for updates.

[osm0sis]

You think so? I need someone to try and make sure with Magisk 20.4 stable, so we know for sure, please.

[map220v]

On Stable Magisk 20.4 issue still exists magisk_install_log_KEEPOFF.log

[osm0sis]

So just to be clear, Magisk has never worked on this device?

[map220v]

Yes. it's never worked on A51.

[nayessiva]

Hi, I've seen that : https://github.com/topjohnwu/Magisk/issues/1961 However I still have the issue on my A40. I know the topic here is A51 but probably the same issue ? Or is it really fixed and i messed it up flashing magisk-patched ...?

[map220v]

I Tried to patch only boot.img, on Samsung A51 (system as root) it's gives kernel panic. On Samsung A71 (system as root) it's not gives kernel panic. I got kmsg.txt from Samsung A51 last Magisk Canary (debug) kmsg.txt

[rodrigofd]

@osm0sis ping... this guy is spamming all around 👆🏻

[osm0sis]

@osm0sis ping... this guy is spamming all around 👆🏻

So it is indeed pure bullshit? Removed his comments. :+1:

[rodrigofd]

Anything that can be done, to help bump this issue? It's currently not possible to use Magisk on the A51.... (I could try pull my logs as well, but I don't think it would add more value to those that @map220v already posted above) 👆 CC @osm0sis

[ghost]

@osm0sis ping... this guy is spamming all around 👆🏻

So it is indeed pure bullshit? Removed his comments. :+1:

Yeh no need spaming, I see that everyone need this a51 root, cs I'm say I can root. I'm come for help all, okay bro god bless you..

[map220v]

I updated phone to A515FXXU3BTD4(OneUI2.1) and now patched boot.img not gives kernel panic.

[balanadi]

I would like to add my experience with M315F which has the same exynos 9611 and i tried to patch The entire AP-M315FXXU1ATB4 with magisk 7.5.1 and also with canary update and it gives the same error about vbmeta , but if i patch only the boot.img it is working but stays in bootloop and is restarting after 10 seconds ... Hope someone will find a way to fix this bug ... Thanks

[B1gM1k3]

Found a video how helps me installing successfully Magisk. CTS failed btw. https://www.youtube.com/watch?time_continue=216&v=oZD2jkkKX_E&feature=emb_logo

[balanadi]

I tryed already and it is staying in bootloop and restarting after 10 seconds ...

[B1gM1k3]

Maybe you missed a step ? I strictly followed the procedure step by step and it worked.

[balanadi]

Maybe you missed a step ? I strictly followed the procedure step by step and it worked.

i did same as in the video , 3 times already today .. same error : restarting after factory reset and keep restarting after 10 seconds ...AP-M315FXXU1ATB4 galaxy M31F from DBT germany

[map220v]

Maybe you missed a step ? I strictly followed the procedure step by step and it worked.

i did same as in the video , 3 times already today .. same error : restarting after factory reset and keep restarting after 10 seconds ...AP-M315FXXU1ATB4 galaxy M31F from DBT germany

This Video won't work for you. Because you using not A51. I recommend you to wait for Binary 2 or Binary 3 Update for your phone bootloader.

Edit: On A51 we got magisk working only after Binary 3 update.

[ghost]

I can fixed this problem.....

On Tue, 19 May 2020, 1:56 am map220v, notifications@github.com wrote:

Maybe you missed a step ? I strictly followed the procedure step by step and it worked.

i did same as in the video , 3 times already today .. same error : restarting after factory reset and keep restarting after 10 seconds ...AP-M315FXXU1ATB4 galaxy M31F from DBT germany

This Video won't work for you. Because you using not A51. I recommend you to wait for Binary 2 or Binary 3 Update for your phone bootloader.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/topjohnwu/Magisk/issues/2272#issuecomment-630477375, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALG3HWRBNSGJIBRXSUM2D4TRSG4LBANCNFSM4KHTRZLA .

[ghost]

Found a video how helps me installing successfully Magisk. CTS failed btw. https://www.youtube.com/watch?time_continue=216&v=oZD2jkkKX_E&feature=emb_logo

Osm0sis ... where are you, this is my tutorial.... do you need any help? Contact me...

[ghost]

If anyone need root a51 if u follow tutorial, but u cannot successful, contact me, i fixed your problem i'll come u by teamviewer.... thank you.

[map220v]

Found a video how helps me installing successfully Magisk. CTS failed btw. https://www.youtube.com/watch?time_continue=216&v=oZD2jkkKX_E&feature=emb_logo

Osm0sis ... where are you, this is my tutorial.... do you need any help? Contact me...

This video only working because you using A51 with Binary 3 update and patching boot.img instead of recovery.img

[balanadi]

Thank you guys for your help , but i will prefer to wait till a future update ... So far i manage to build a script and uninstall all the crap bloatware without root , and without affecting knox ... so i will make a tutorial on xda when i will finish ..

[ghost]

Thank you guys for your help , but i will prefer to wait till a future update ... So far i manage to build a script and uninstall all the crap bloatware without root , and without affecting knox ... so i will make a tutorial on xda when i will finish ..

Lool

[blue-pine]

Please help me......please...............anyone...........................................................topjohnwu? Same issue with my Samsung Galaxy Tab A8 2019 Wifi Only (SM-T290 ) : https://github.com/topjohnwu/Magisk/issues/2923#issue-646679716 My device is non A/B and is System-as-Root. Tried all possible ways but the same error is coming :

The device in download mode reports: "`SECURE CHECK FAIL : vbmeta"

And at the same time Odin reports " Complete (Write) operation failed " Even when I used a original, non patched version of Odin same output came on my Samsung tablet.

Also I noticed that Magisk patches the vbmeta.img.lz4 also along with boot.img.lz4

[soum91]

I opened issue #2917 which was closed and I have been told by @osm0sis to add my info here, so pasting it below

Can't bypass Secure Check Fail Screen on SM-A207F #2917

I am trying to flash magisk on my Samsung SM-A207F on Android 10 following this instruction. But after flashing the patched AP file I can't boot into stock recovery to Wipe data/factory reset at step 10. As soon as I press Volume Down + Power to escape Download Mode and press Volume Up + Power, it takes me to Secure Check Fail screen, no matter how many times I try. I even tried patching only Boot.img that too results in the same error. I have used Magisk 20.4. Can anyone tell how to fix this or what am I doing wrong?

I am guessing in my case it has to do something with bootloader unlock. This is a Qualcomm device and it has something called Qualcomm Secure Boot. Even though I have unlock OEM Bootloader, as you can see here, it still says Qualcomm Secure Boot: Enabled in bootloader. I tried googling about this but could find anything to unlock "Qualcomm Secure Boot". I am really worried about ever being able to root it!

[map220v]

@soum91 this problem has nothing to do with Qualcomm Secure Boot. SECURE CHECK FAIL : vbmeta caused by vbmeta_samsung that checks vbmeta there is only 2 fixes:

1.Patch boot.img only

2.Use original vbmeta.img and sign recovery.img using avbtool.py add_hash_footer --image image-new.img --partition_name recovery --partition_size <original recovery.img size in bytes>

[soum91]

@map220v I have tried flashing only boot.img so many times, always gives Secure Check Fail: boot.img. Any kind of modifications to any of the imgs is triggering this.

[blue-pine]

@map220v I have tried flashing only boot.img so many times, always gives Secure Check Fail: boot.img. Any kind of modifications to any of the image is triggering this.

Here on Samsung A8 Tab Wifi Only 2019 SM-T290 except it gives on my device: Secure Check Fail: vbmeta.img I know boot and recovery, what is vbmeta ?

[blue-pine]

@soum91 this problem has nothing to do with Qualcomm Secure Boot. SECURE CHECK FAIL : vbmeta caused by vbmeta_samsung that checks vbmeta there is only 2 fixes:

1.Patch boot.img only

2.Use original vbmeta.img and sign recovery.img using avbtool.py add_hash_footer --image image-new.img --partition_name recovery --partition_size <original recovery.img size in bytes>

Can you please tell me all steps to do so ?

[mu198]

The same problem is found on the galaxy tab s6 lite (SM-P610). It seems to be a new root lock from Samsung 🙈

[soum91]

I'm just wondering if @topjohnwu is even aware or remembers this issue. It's been more than 6 months, still haven't heard anything from John Wu.

[mu198]

Well, there were bigger problems in the world and this is still an open source project, so big thanks to @topjohnwu. Hopefully you will tackle this problem in the near future.

[blue-pine]

Please help me......please...............anyone...........................................................topjohnwu? Same issue with my Samsung Galaxy Tab A8 2019 Wifi Only (SM-T290 ) : https://github.com/topjohnwu/Magisk/issues/2923#issue-646679716 My device is non A/B and is System-as-Root. Tried all possible ways but the same error is coming :

The device in download mode reports: "`SECURE CHECK FAIL : vbmeta"

And at the same time Odin reports " Complete (Write) operation failed " Even when I used a original, non patched version of Odin same output came on my Samsung tablet.

Also I noticed that Magisk patches the vbmeta.img.lz4 also along with boot.img.lz4

Update for you guys mine is binary 3 update, any suggestions advice for me? You are fully welcome. Please help.

[blue-pine]

Please help me......please...............anyone...........................................................topjohnwu? Same issue with my Samsung Galaxy Tab A8 2019 Wifi Only (SM-T290 ) : https://github.com/topjohnwu/Magisk/issues/2923#issue-646679716 My device is non A/B and is System-as-Root. Tried all possible ways but the same error is coming :

The device in download mode reports: "`SECURE CHECK FAIL : vbmeta"

And at the same time Odin reports " Complete (Write) operation failed " Even when I used a original, non patched version of Odin same output came on my Samsung tablet.

Also I noticed that Magisk patches the vbmeta.img.lz4 also along with boot.img.lz4

Help me, anyone regarding this issue . I can provide all the information for my device you want.

[blue-pine]

Even when I flash just boot.img.tar after patching with magisk Odin says write operation failed. As soon as the flashing is at 99 % the write operation failed. 😢😭

[blue-pine]

Even when I flash just boot.img.tar after patching with magisk Odin says write operation failed. As soon as the flashing is at 99 % the write operation failed.

Because of this I think flashing is ok but some type of security program in bootloader is preventing the full flash as flash WAS about to get completed after 99 percent . Also even when I installed samsung official drivers , my device is not getting detected after typing "fastboot devices " on cmd .What do you all say? Please reply as I am in need of solving this issue . It's too important for me and I think some others also📲 . Also please tell me how to get fastboot/bootloader drivers of Samsung ,pls . Waiting for your reply.

[map220v]

@Navneet-Kumar-Singh Samsung using their Odin Download Mode instead of fastboot. (Also samsung even deleted fastbootd from recovery, so flashing custom roms difficult on devices with super.img)

[blue-pine]

What is super.img? I want to know. Pls

[map220v]

@Navneet-Kumar-Singh Phones released with android 10 uses super.img. super.img contains system.img, vendor.img, product.img and odm.img to install custom roms on these devices people using fastbootd recovery, but samsung removed it...