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
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
Hi,
I had a rooted Oneplus Nord (OOS 11)
I updated the device with the newly released ColorOS 12 update
The root disappeared, so I downloaded the Payload file to root again thru magisk
However, the payload.bin has boot.img, vendor.img files but there is no "vendor_boot.img" file
When I flash the patched boot.img file, the device gets stuck in bootlooop.
I am assuming this is because vendor_boot.img is not patched
Has anyone successfully rooted Oneplus Nord after ColorOS12 update? Can someone help?
Any help on rooting ColorOS 12 updated on Oneplus Nord?
Hi, I am undergoing the same issue. But, sort of have an idea how to fix it. Unfortunately I am a bit worried to try it out. I know there is no vendor_boot image to patch. But isn't it the same thing to patch vendor.img? Could you try patching that and let me know of the results?
I tried patching vendor image. There was an error in magosk.
I'm going to try flashing Twrp recovery on the phone and try installing magisk to root it. Will let you know how it goes
No luck, doesn't work for Android 12. Waiting on some update for rooting the Nord
puru said:
Hi,
I had a rooted Oneplus Nord (OOS 11)
I updated the device with the newly released ColorOS 12 update
The root disappeared, so I downloaded the Payload file to root again thru magisk
However, the payload.bin has boot.img, vendor.img files but there is no "vendor_boot.img" file
When I flash the patched boot.img file, the device gets stuck in bootlooop.
I am assuming this is because vendor_boot.img is not patched
Has anyone successfully rooted Oneplus Nord after ColorOS12 update? Can someone help?
Click to expand...
Click to collapse
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
This worked. I am still testing though.
Link to canary - https://github.com/topjohnwu/magisk-files/blob/canary/app-debug.apk
Mr.Lucky said:
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
Can anyone confirm this does work without having to wipe the entire phone's data?
Thank you
Hi
This works and data is intact.
Mr.Lucky said:
use the latest magisk canary version, just patch the boot.img then
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
Click to expand...
Click to collapse
How do I patch the boot img ?
Do I use those fastboot commands immediatly after flashing the new rom (reboot to fastboot). No need to install magisk to 2nd slot(after ota) ?
robuser007 said:
How do I patch the boot img ?
Do I use those fastboot commands immediatly after flashing the new rom (reboot to fastboot). No need to install magisk to 2nd slot(after ota) ?
Click to expand...
Click to collapse
Install OOS12, install magisk and patch the boot.img, then boot into the bootloader and type the commands. After an ota, magisk must be installed in the inactive slot.
Does this also work with Magisk v25 released today?
Where can I find those files? I guess I have to move those to the fastboot folder on my pc ?
fastboot flash boot patch_magisk.img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img
robuser007 said:
Does this also work with Magisk v25 released today?
Click to expand...
Click to collapse
No, I'm not able to have a bootable magisk patched boot image, also using magisk canary release.
After I flash the patched img the Nord goes in bootloop, the only way to have it working is to flash back original boot.img
About the vbmeta.img & vbmeta_system.img I have used the extracted from payload_output folder, I think is correct?!?
Did you manage to solve this ? I really want to upgrade but not loose root.
I rollback to stable Android 11, I have tested the new version for one day and is graphically bugged everywhere, seems they release a beta, not a stable version.
I rollback to stable Android 11 with Orange Fox recovery, Root, safetynet-fix ok, ecc ecc
I have tested the new version for one day and is graphically bugged everywhere, then no recovery, no root, Color OS seems not for me for the moment.
What do you mean with graphically bugged everywhere ?
How can I stay on having root, does it work with latest canary?
robuser007 said:
Did you manage to solve this ? I really want to upgrade but not loose root.
Click to expand...
Click to collapse
I'm also not upgrading because of 'loose of root"
Still not able to find fix of safety net fix for A12..
all method i tried but safetynet is not fix.... CTS profile always FAILED...
nobody has any method which is working...
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
In a moment of weakness, I finally allowed my G Stylus to update to Android 12, and my stability has been a nightmare since then. I have been reading through many guides here and elsewhere to getting a GSI installed.
So far, I have unlocked the bootloader and followed the instructions for installing TWRP using adb/fastboot for my device. When try to flash a GSI, the partitions in TWRP don't look like anything I've seen in guides. The options it shows me are:
-Boot
-Dtbo
-Persist
-Super (system system_ext product vendor)
-Install Recovery Ramdisk
I tried installing on Super, as I found a thread mentioning it should contain both vendor and system. However, when I flash the img for a gsi to it, it will only boot to bootoader. I can get it into TWRP recovery but the screen is entirely unresponsive, even attempting to power off prompt's a restart. I was able to use Moto's Rescue program to get it back in working order, but each time this happens I have to start over at square one.
I tried with a GSI for crDroid on my first attempt, and then LineageOS on a follow-up attempt, both I had the same issue.
I'm new to Android modding, so I could really use some guidance through getting this set up. I've extensively referenced guides on here and elsewhere, but I've struggled with parsing and figuring out what I need to do in this case. Currently my device has TWRP installed but I'll be doing nothing else until I know what the best way forward is. I'd be happy to provide additional info.
Edit: Just found the dedicated 5G section. Sorry about this.
I am not sure why people use TWRP and a GSI/crDroid /w LineageOS rom.
All you need to do is install the magisk module L Speed
Remember this phone has 2 boot partitions....1 is secured (even if you have the bootloader unlocked and your rooted) So if you trip the SafetyNet your going to have bootloading issues and boot loops
Not sure what the previous comment was about, what does safetynet have to do with anything? It fails the second you unlock the bootloader.
First, you'll want to make sure to have installed at least one OTA update so both your slots are occupied. You could also install copy-partitions from a custom recovery. Otherwise your phone might brick if it ever switches to slot b.
Download and extract the official firmware for your device that matches what is installed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
And reflash your vbmeta partition(s) from fastboot to disable verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_system.img
Then you need to reboot into fastbootd (you can also get into it from a custom recovery)
Code:
fastboot reboot fastboot
From there you can erase your system, install the GSI, wipe data, and reboot
Code:
fastboot erase system
fastboot flash system GSI_system.img
fastboot -w
fastboot reboot