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
Hi, anybody know if is there a new version of vbmeta.img that make vbmeta_patch.img not mandantory anymore in the Root Process ?
Thanks
I'm curious if anyone has loaded a gsi on the oneplus 7t and if they know what boots and any workarounds that might be needed.:fingers-crossed:
on fastbootd
fastboot -w
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img " use the vbmeta.img from oxygen "
All those should be flashed in one go without rebooting. boot and vbmeta are those taken from OOS stock rom.
i have looked and i can not find the t-mobile stock rom i can get these files from. i have the files used by the msm tools but can find one that can be used. could you explain or link me please
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.
Hello, i am trying to install android 13 gsi on GM8. I installed system.img but when i try to install vbmeta.img it says
fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
I don't know what to do, I would be glad if you help me.
try to flash in slot directly. use proper flags.
Code:
fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_b vbmeta.img
aIecxs said:
try to flash in slot directly. use proper flags.
Code:
fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_b vbmeta.img
Click to expand...
Click to collapse
thank you but it doesn't work for me
afowd007 said:
thank you but it doesn't work for me
Click to expand...
Click to collapse
Were you able to figure out?
You may not be on fastbootD. If you are, then it should work. And for some reason it was deleted. You can re-add it with command:
Code:
fastboot create-logical-partition vbmeta 800000
if you are on fastboot 1, then use command:
Code:
fastboot reboot recovery
then you should be able to select fastboot from menu and fastbootd should show up