I unlocked bootloader,and able to root etc. But unable to flash vbmeta via fastboot .each time I got system destroyed. Any has detailed information about how to flash ? Any thread ?
I Used this command on fastboot mode
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Not working.
Problem solved by installing updated ADB installer 1.4.5
https://androiddatahost.com/up9hg
drmuruga said:
Problem solved by installing updated ADB installer 1.4.5
https://androiddatahost.com/up9hg
Click to expand...
Click to collapse
fastboot flash boot path to patched boot img
and then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
this command?
That's it? just these two commands? I wonder if the second one is even necessary. someone help. I am currently stuck at MIUI logo!
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I have a problem with it on newer ADB editions as it is not working...any ideas?
vassiliszacharis said:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I have a problem with it on newer ADB editions as it is not working...any ideas?
Click to expand...
Click to collapse
try this
Hey everybody.
So I've recently got this Redmi Note 8 (2021) and figured I'd root it.
After the week of waiting to unlock the bootloader, I did the next step to install Magisk.
Due to the lack of custom recovery, I patch the bootimage, and flash it with fastboot.
However after this, the phone is stuck on fastboot, so I guess something is missing.
I also tried the canary versions, but no success yet.
Did anybody succesfully instal Magisk on this phone? Or some other type of root?
I'll just answer my own question here.
Android 11 MIUI devices need enabled verification in boot.img AVBv2 signature​
This pull request will fix it (for me): https://github.com/topjohnwu/Magisk/pull/4975
Trying the vvb alpha worked for me.
You should flash first vbmeta.img with this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then flash the previously modified boot image with Magisk:
fastboot flash boot boot.img
pierzale said:
You should flash first vbmeta.img with this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then flash the previously modified boot image with Magisk:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I heard about this vbmeta at several occasions, but I haven't found a proper resource or download location for it.
How do I create or download a patched vbmeta?
Other than that, the solution I posted does work for rooting my device. But I think flashing vbmeta might open some options up for me like a custom recovery.
pierzale said:
You should flash first vbmeta.img with this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then flash the previously modified boot image with Magisk:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hi.
when ich put that command i became that error:
C:\adb\fastboot.exe: unknown option -- disable-verity
sorry, i made a mistake. got it now
hello can you help me to root
Sure.
Install the newest magisk.
First unlock the bootloader, then patch a boot image with magisk, and flash it to your boot partition with fastboot.
I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?
I'd suggest waiting for the next OTA and do it again.
However, I don't understand why you did the uninstall, update, install to the other partition etc part. I usually just do the following steps:
Install OTA (do NOT reboot yet)
Install Magisk in the other partition
Reboot
So far it has worked for me for each update.
Ecna said:
I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?
Click to expand...
Click to collapse
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good
Appreciative said:
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good
Click to expand...
Click to collapse
How would I copy my good partition to the broken one?
viktak said:
I'd suggest waiting for the next OTA and do it again.
Click to expand...
Click to collapse
The current OTA is still pending, and I don't have root anymore, so waiting won't get me anywhere.
However, I don't understand why you did the uninstall, update, install to the other partition etc part.
Click to expand...
Click to collapse
I just followed the Magisk instructions here:
https://topjohnwu.github.io/Magisk/ota.html
Ecna said:
How would I copy my good partition to the broken one?
Click to expand...
Click to collapse
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm
Appreciative said:
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm
Click to expand...
Click to collapse
Thank you, I'll dig into these links!
I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?
sumfahg said:
I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?
Click to expand...
Click to collapse
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version
TheGhost1951 said:
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version
Click to expand...
Click to collapse
I am on Windows, where can I download fastboot enhanced?
sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
There is an xda threads on it. Just search xda forums for fastboot enhanced.
sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)
zjhjack123 said:
I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.
Ecna said:
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.
Click to expand...
Click to collapse
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.
Appreciative said:
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)
Click to expand...
Click to collapse
Fastboot --set-active=a or b which ever you need in bootloader mode
Ecna said:
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.
Click to expand...
Click to collapse
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.
zjhjack123 said:
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.
Click to expand...
Click to collapse
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
When you flash tom in the system, it only update the firmware in another slot. So if your current good rom is in slot b, you can just boot into slot b and apply system update via local update, the updated rom will be in slot a.
Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
If you have the images:
fastboot flash system_a system_a.img
fastboot flash system_b system_b.img
it's also possible to pull the whole partitions down with msm tool (press f8, select partitions and readback, files go to c:\) or using dd.
If not, #19 above
hi guys,
i am t total noob so please be patient.
i like to install twrp from here but i stuck on the first step because of because of
Spoiler: this
To disable AVB via fastboot, grab the vbmeta image from the ROM you are on, and flash it with the following command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
can anyone help me to find the the vbmeta ( i am on MIUI Global 12.5.1.0).
Download your stock rom. You will find many websites in the internet. Download according to your miui version & device codename.
Then extract the zip file. Copy vbmeta.img to platform tools. Open cmd there and execute that command.
You could use an empty vbmeta.img directly from google (here), i used on my tablet not on the F3.
I am using EEA MIUI 12.5.15.0(RGGEUXM) version. I have downloaded the ROM from here, which I got the vbmeta.img from.
When trying to disable AVB 2.0 using the
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
command, it reports as being flashed successfully but causes my phone to keep booting into recovery until I flash stock ROM using MIFlash.
Why does that happen?
@theimpulson afaik no A/B device, so the above cmd should work, right?
alecxs said:
@theimpulson afaik no A/B device, so the above cmd should work, right?
Click to expand...
Click to collapse
I don't know but I have got new phone since this time so not important