Develop Bugs

Unable to flash vbmeta

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

General edit: guide how to flash stock via fastboot and fastbootd

hay i flashed the open beta android 12 on my le2123
i noticed thet i dont have root so i trying download twrp and flash magisk.zip
i boot the phone into fast boot and run this commend
"fastboot boot twrp.img"
and then i flash magisk
the phone refuse to boot normal
i able to boot it to fastboot, what should i do now?
i convart to payload of the open beta via payload dumper and i have now a lot of .img file
should i flash them 1 by 1?
there is any order of doing that?
edit:
first i sorry for my bad english
i finally boot up the phone by first download stock rom and extract the .bin file into payload dumper (i found it on xda)
after that i flash allmost any of the output img the phone came to liva again.
(i have to download the fastboot from android sdk, the minimal adb and fastboot not incloude the specific command of "reboot fastboot.
the command boot the phone into fastbootd (new to me, i never heard about it))
this is the command i use if any one here do my mistake
1. fastboot -w (this will erease anything on the phone)
2.now you need to flash the following img
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
3. now use this command to reboot the fastboot into fastbootd
fastboot reboot fastboot
4. Flash the remaining files
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
5. finnaly use this command to reboot your phone into stock rom
fastboot reboot
i really hope this will halp anyone who stuck on the same situation as me
credit to other forum for the flash guide

How to Root Android 12 via Magisk patched boot.img (without TWRP)
In this tutorial, we will show you the steps to root your Android 12 device via Magisk patched boot.img, without using TWRP Recovery.
www.droidwin.com

FizzyAps said:
How to Root Android 12 via Magisk patched boot.img (without TWRP)
In this tutorial, we will show you the steps to root your Android 12 device via Magisk patched boot.img, without using TWRP Recovery.
www.droidwin.com
Click to expand...
Click to collapse
i'll do it after i get my phone boot, you have any idea what should i do now? im stuck on fastboot

msm tool

awesome
but not all thats need to flash stock

FizzyAps said:
awesome
but not all thats need to flash stock
Click to expand...
Click to collapse
so for the next time, how to flash stock?
i was on 12 beta and back to 11 so i flash all the files

elad0elad said:
so for the next time, how to flash stock?
i was on 12 beta and back to 11 so i flash all the files
Click to expand...
Click to collapse
On 12 you can actually downgrade using the updater app they provi
Or
I have a fastboot script .bat flash the essential that are need to flash

FizzyAps said:
On 12 you can actually downgrade using the updater app they provi
Or
I have a fastboot script .bat flash the essential that are need to flash
Click to expand...
Click to collapse
The phone refuse to boot so I can't use the app...
I'll be glad If you can send the script

Question Magisk install stuck on fastboot

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.

Question Konabess in C.47

On firmware C.47 after changing any settings the system stops booting. Flashing a modified vbmeta which helped to solve the problem on C.44 firmware doesn't work anymore and also leads to problems with booting the system. Perhaps someone knows how to get Konabess to work on the latest C.47 firmware?

For me it works like before. Please try following commands and use extracted images from c.47:
fastboot flash boot root.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img

corneo said:
For me it works like before. Please try following commands and use extracted images from c.47:
fastboot flash boot root.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
Click to expand...
Click to collapse
please share the files if you have them.

You can extract it by yourself with using payload dumper go. Please try forum search.
GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com

corneo said:
For me it works like before. Please try following commands and use extracted images from c.47:
Click to expand...
Click to collapse
corneo said:
You can extract it by yourself with using payload dumper go. Please try forum search.
GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go
an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thank you! It worked!

Mi Bodya said:
Thank you! It worked!
Click to expand...
Click to collapse
Can you share your konabess configs?

rejectedjs said:
Can you share your konabess config
Click to expand...
Click to collapse

what about in oos 13 f72? tried several combinations with vbmeta and vendor partitions, no luck. always ends up dmverity crashdump or constant reboot cycle to fastboot.

gsser said:
what about in oos 13 f72? tried several combinations with vbmeta and vendor partitions, no luck. always ends up dmverity crashdump or constant reboot cycle to fastboot.
Click to expand...
Click to collapse
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
...
It works in me

Mi Bodya said:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verification --disable-verity flash vbmeta_vendor vbmeta_vendor.img
...
It works in me
Click to expand...
Click to collapse
For some reason it didnt for me. I tried flashing in each slot one by one and it works
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_b vbmeta_vendor.img

Here is my config, i made it for my previous mi 11 ultra but it works just as fine for my 9 pro.

D
Mi Bodya said:
On firmware C.47 after changing any settings the system stops booting. Flashing a modified vbmeta which helped to solve the problem on C.44 firmware doesn't work anymore and also leads to problems with booting the system. Perhaps someone knows how to get Konabess to work on the latest C.47 firmware
Click to expand...
Click to collapse
Disable vbmeta

I haven't tried this, running OOS 13. Does this wipe any data? Or it keeps all data in place?

Is there a guide about this (for first timers)? Or have I got to just follow the post #2
Thanks

observingi said:
Is there a guide about this (for first timers)? Or have I got to just follow the post #2
Thanks
Click to expand...
Click to collapse
there is a telegram group with guides and support. Search adreno_konabess in telegram

Hi, how can i use this files ? i dont know anything about konabess, can you help me? i have rooted LE2123 F72 version

sefai77 said:
Hi, how can i use this files ? i dont know anything about konabess, can you help me? i have rooted LE2123 F72 version
Click to expand...
Click to collapse
Join the telegram group mentioned above or visited the Konabess GitHub. The info is there. There are also YouTube videos. Lots of info about it if you simply search for it.

Peeps kept asking me in Telegram and in xda so here is what you do to update OOS without crash dump.
From your CURRENT ROM payload.bin, extract dtbo, vendor_boot, vbmeta, vbmeta_system, vbmeta_vendor. Then use the commands i put below. After that just local flash the ota and use magisk to patch inactive slot.
Spoiler: Reverting Kona Changes and Restoring Verity.
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot magisk.img - the magisk patched boot.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vbmeta_system_a vbmeta_system.img
fastboot flash vbmeta_system_b vbmeta_system.img
fastboot flash vbmeta_vendor_a vbmeta_vendor.img
fastboot flash vbmeta_vendor_b vbmeta_vendor.img
------------------------------------------------------------------
To re-use Konabess after the update, extract the images above from the OTA payload.bin and just use the commands down below.
Spoiler: Using Kona
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_b vbmeta_vendor.img
This works for me in OOS 13 ROMs.

Development Unofficial Lineageos 19.1 for capri moto g10 and moto g10 power

!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot

thanks for the amazing work on this rom

sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon)
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
Thank you, guys, for your awesome work. Hope we'll get a stable update. Good luck

sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon)
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
So installed fine on a G10 now the problem is a lack of google apps I want it and I need magisk for half the apps to to add a custom way to run apps that need root.
I cannot get gapps on it for starters as can't go into a recovery menu it's twrp I need to do all this with and the recovery on this is stock really, I will say though that is is an amazing firmware I mean really clean brilliant work but I must have twrp so I can root but also so I can add google apps which is my primary necessity root is a distant second if at all needed i do newed my apps to make images and other tools I use it for daily driver wise.
l Tried to use this TWRP https://cloudhazy.com/download/motorola-moto-g10-xt2127-2-twrp-recovery-3-5-2/ and it fails but I know the model number XT2127-2 is correct so it just doesn't allow installing or launching it, from inside platform tools openeing in a command window here mode????
I am stuck completely now.

@PHYSC-1 you should be able to find magisk inside the attached lineageos zip. Flash that to boot and you should be rooted. I am working on gapps and dual sim currently. Also, don't feel like you are stuck. At any moment, you can flash the stock firmware and go back to stock if you are not able to daily drive lineage os without gapps.
I don't want to have gapps on my phone so I didn't work on it at all until now. I see that many people are asking for gapps, so giving it a try.
In case you don't find the magisk boot image in the lineage os zip, you can create one yourself by installing magisk app and passing this lineageos boot image to it.

@PHYSC-1 we are testing gapps on this ROM now. Me and two users present on our group are testing GAPPS on this ROM. As of now, its running smooth, will publish the update in a week or so.

sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
Thank you for this work! I'm also anxious to get a stable, dual chip working version too.

I think the Gapps should be separate to ROM. Of course if it is possible.

Gapps works 2 problems found in testing 1 is a big one for anyone using screen cast the network auto switches from 2.4ghz to 5ghz and back intermittently causing screen cast to drop out mid use and this stuns it and creates constant bad image quality and freezing completely up.
Secondly this could be unrelated to the OS but it doesn't happen on official Motorola OS's when using the app from F-Droid called simple gallery pro if you edit an image and try to draw on an image the drawing occurs in the wrong position the pointer is below where you draw on?