hello, I have an M21s (F415), it has the bootloader unlocked and the root works normally, but this device has a serious problem with the VBMETA, which ends up preventing the phone from starting if you flash any customized recovery, could someone help? it's a good device but this problem is something that interferes in the development for it ;-;
The sense of a VBMETA.img is to prevent phone booting into a modded Android OS.
You can permanently bypass this lock by
Pulling out the vbmeta.img to PC
Sending back this vbmeta.img to phone by means of Fastboot with the directive to disable DM-Verity & AVB
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Related
Hi, how can i install a treble GSI without bootloop on this phone? THX
Have you unlocked the bootloader? If yes, then just go to the Developer Options & Select DSU Loader. You will be automatically offer the latest Android 12 DP2 with & w/o GMS bundle.
aimsjahan said:
Have you unlocked the bootloader? If yes, then just go to the Developer Options & Select DSU Loader. You will be automatically offer the latest Android 12 DP2 with & w/o GMS bundle.
Click to expand...
Click to collapse
yes but i want something installed, not emulated, also with 144hz enabled, even if i don't have the triggers
ASUS only validated GSI for Zenphone 8 so far. I think we have to wait for our turn.
aimsjahan said:
ASUS only validated GSI for Zenphone 8 so far. I think we have to wait for our turn.
Click to expand...
Click to collapse
No, i dont want A12 GSI, I want something like Lineage and stuff
Therazorsedge said:
No, i dont want A12 GSI, I want something like Lineage and stuff
Click to expand...
Click to collapse
Are you seeking a custom ROM based on LineageOS?
He mean gsi (not the dsu loader and not a custom rom )
aimsjahan said:
Are you seeking a custom ROM based on LineageOS?
Click to expand...
Click to collapse
Yes! i think it's not too complicated to make it boot on dtock recovery from Asus, anyone tried?
you have to erase system and from there, install via fastboot, i only need the command to try a PHH gsi
Rog 5is android 11 devices .
can be the system can only be flashed via fastbootd.
Use the comand
Fastboot -w
Fastboot flash system_a "name from the gsi.img"
Fastboot flash system_b "name from the gsi.img"
But I think that these two must also be flashed so that the gsi boots.
fastboot --disable-verity flash vbmeta_a vbmeta.img
fastboot --disable-verity flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity flash vbmeta_b vbmeta.img
fastboot --disable-verity flash vbmeta_system_b vbmeta_system.img
Vbmeta and vbmeta sytem use from the stock rom
ChrisFeiveel said:
Rog 5is android 11 devices .
can be the system can only be flashed via fastbootd.
Use the comand
Fastboot -w
Fastboot flash system_a "name from the gsi.img"
Fastboot flash system_b "name from the gsi.img"
But I think that these two must also be flashed so that the gsi boots.
fastboot --disable-verity flash vbmeta_a vbmeta.img
fastboot --disable-verity flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity flash vbmeta_b vbmeta.img
fastboot --disable-verity flash vbmeta_system_b vbmeta_system.img
Vbmeta and vbmeta sytem use from the stock rom
Click to expand...
Click to collapse
Haha, i will have a bootloop? hahahaha
Anyone can try?
Hello guys my phone is stuck in a bootloop because I tried to install twrp from fastboot.
I unlocked bootloader and started Fastboot.
Then I connected my phone to my mac via USB.
Then I ran this commands:
./fastboot flash recovery recovery.img
./fastboot flash vbmeta vbmeta.img
(The mistake I think I made was that I flashed recovery before vbmeta).
Then I restarted my phone and I could not get into android or fastboot.
Please I need help.
This is the tutorial which I used.
Thanks in advance.
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
jwoegerbauer said:
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
I will try to Flash the stock ROM using SP Flash Tool.
I won't try to install twrp anymore if this stock ROM flashing works.
I'll kill my dreams of rooting my phone and installing android 12.
(I hope it works because am not getting a new phone until next 3 years)
jwoegerbauer said:
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
Please do you know how to get the build number of my bricked phone?
mikkyboy said:
I will try to Flash the stock ROM using SP Flash Tool.
I won't try to install twrp anymore if this stock ROM flashing works.
I'll kill my dreams of rooting my phone and installing android 12.
(I hope it works because am not getting a new phone until next 3 years)
Click to expand...
Click to collapse
It's not hard to install TWRP to this device
I'm trying to root an Oukitel WP12 with Magisk.
I've downloaded the firmware from the vendor's link and flashed it successfully just like for other Oukitel phones (WP6, WP10).
I could also create a magisk-patched boot image. I followed regular practices: unlocked the bootloader, confirmed by orange state message and flashed the patched boot image.
The phone gets into a boot loop.
This phone differs significantly from other Oukitel phones I saw before. It comes with Android 11 by default, moreover: the device is an A/B device.
Also: apart from vbmeta, it also has vbmeta_system and vbmeta_vendor. I tried flashing a blank vbmeta for vbmeta first and than to all three vbmeta partitions without success.
Anyone came accross with a phone with vbmeta, vbmeta_system and vbmeta_vendor partitions? How I should correctly create blank vbmetas for these partitions?
Note that there's also a boot-debug partition and for several partitions there are partitions with a -verified suffix, like: dtbo-verified, tee-verified, etc.
I think it's probably the wrong vbmeta blanks I'm using causing the boot-loop. Flashing the original images restores the phone - although without magisk root of course...
If you have any ideas or instructions on how to overcome this obstacle, please let me know.
Thanks: Dw.
Unfortunately I can confirm the boot loop. I don't have a solution for now, if you have one, please share!
Hi @Dwokfur,
Finally I managed to root my Oukitel WP12. The recpie you posted is OK, you should only re-flash also the Verified Boot partitions with the proper fastboot flags.
WARNING: the vbmeta* partitions I downloaded from the phone were different from the ones found into the Oukitel firmware zip archive: So I used the one extracted from the phone with the SP Flash Tool v5 program.
After all the final fastboot recipe is:
Code:
fastboot flash boot_a magisk_patched-23000_rgkOP.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_a.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system_a.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor_a.img
wrong thread, ignore, sorry.
hello friends
I have tried to install GSI Rom on my Xiaomi 12X and it stays on fastboot. According to Treble info it is possible to install GSI on this device but I have never succeeded.
From EU Rom I go into fastboot and run the commands:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot -w
I reboot into stock recovery and do a format data and reboot
Outcome:
stays in fastboot
Has anyone managed to start any GSI on Xiaomi 12, 12 pro or 12X?
I will be attentive to your comments
Thank you
Now that I have my IMEI numbers restored, I am going to again attempt to flash LineageOS over my stock Android 9.
Let's say I want the latest revision of LineageOS 18, I understand that this is the required system image;
lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img.xz
I also know a vbmeta file is required. This is where I get confused and suspect it's the reason I always get bootloop when flashing.
Do I need a stock vbmeta, a modified vbmeta or a blank vbmeta? I have quite the collection.
Also do I add flags;
--disable-verity
and / or
--disable-verification
Now last, but not least, is my sequence of flashing correct?
fastboot flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot erase userdata
fastboot reboot
I appreciate your time and help.
probably stock vbmeta will work, or get the one in TWRP page for Nokia 2.2