Related
What is "vbmeta.img" and why it is needed? How it works? Does anybody knows?
Có ***g câu hỏi
---------- Post added at 02:48 PM ---------- Previous post was at 02:44 PM ----------
I have the same question in
Google it
I have a question regarding vbmeta: I flashed it when I was installing a rom (let's say unofficial los). If I install another rom that doesn't ask me to flash vbmeta (let's say xiaomi.eu), will it flash another vbmeta? Is vbmeta included in xiaomi.eu's .zip?
As far as i understood it, correct me if i'm wrong, it disables verified boot for e.g. installing a gsi rom.
kennyk09 said:
Google it
Click to expand...
Click to collapse
Funny... I just did that and here I am.
I would like to know what is vbmeta as well...
Sent from my MI 9 using Tapatalk
After Android 8 they implemented Verified Boot. That's why you need vbmeta.img for some tasks (mostly to disable verified boot). In some cases, TWRP will not install if Verified Boot is on. Read more Here
kennyk09 said:
Google it
Click to expand...
Click to collapse
This is the 2nd reply on google rofl, got any better ideas genius
Yahoo it
kennyk09 said:
Google it
Click to expand...
Click to collapse
What if I bing it, sir?
Google sent me here — it's the first result when searching "vbmeta.img". Looks like we've entered a recursive function here! Let's add an exit condition.
Further digging led me to the Android Verified Boot 2.0 Readme which by skimming through it answered most of my questions.
So to get this clear, my current understanding is that vbmeta is akin to SecureBoot on PC — it uses hashes for each stage of the boot process to ensure that the final operating environment hasn't been tampered with at any stage of the startup process. Now since vbmeta actually contains the hashes/keys for the boot, system, and vendor partitions, that does mean that every ROM build will need a unique vbmeta.img if we wanted AVB to verify successfully, right? Also, I still don't understand how a vbmeta.img can disable AVB... does it simply set the hashes to zeros? And if we wanted to disable AVB, then where would THAT vbmeta.img come from? I presume we would need an image that is specific for our device, or would a generic vbmeta.img work across multiple devices (maybe with the limitation of being for A-only or A/B devices)?
I've been away from the custom ROM scene for a long time, so I'm trying to catch up with all these new features (AVB, A/B partitions, SafetyNet, etc.).
AFAIK, you need to flash vbmeta.img if you are going from an Miui ROM to a custom ROM.
And there is only one version of it.
rossarnie said:
AFAIK, you need to flash vbmeta.img if you are going from an Miui ROM to a custom ROM.
And there is only one version of it.
Click to expand...
Click to collapse
your right, vbmeta is responsible for checking initial boot to enter into boot or in recovery mode. thats why make sure you flash or restore system with its own vbmeta or you will end up bootloop or stock on fastboot mode.
kennyk09 said:
Google it
Click to expand...
Click to collapse
TOP answer! Do you know what happens if I search for "vbmeta.img" in Google? I end up in this thread!
A forum would be pretty much useless if every question in every thread would be answered in this way. A kind of "master solution": Google it!
Thank you!!
So is the vbmeta.img the same file for all phones?
Or is it vendor specific?
Or is it phone specific?
Thank you!
Elmarigo said:
So is the vbmeta.img the same file for all phones?
Or is it vendor specific?
Or is it phone specific?
Thank you!
Click to expand...
Click to collapse
As a part of a custom ROM or your firmware images it must be unique for your device model. It's like a boot.img for example.
A vbmeta.img contains checksums of the most important partitions to verify them.
A checksum is a small-sized datum derived from a block of digital data for the purpose of detecting errors that may have been introduced during its transmission or storage. By themselves, checksums are often used to verify data integrity but are not relied upon to verify data authenticity. (Wikipedia)
vbmeta=
verified boot metadata
Thank you!
I know what a checksum is, but didn't know that the vbmeta image contained checksums - which arised more questions:
When every partition is checksummed against vbmeta, wouldn't the phone need a different vbmeta everytime, depeding on Magisk being installed, or TWRP, or both combined?
Elmarigo said:
Thank you!
I know what a checksum is, but didn't know that the vbmeta image contained checksums - which arised more questions:
When every partition is checksummed against vbmeta, wouldn't the phone need a different vbmeta everytime, depeding on Magisk being installed, or TWRP, or both combined?
Click to expand...
Click to collapse
1. Not every partition, only /system, /vendor and /boot in most cases. But this could vary depending on your manufacturer.
2. Magisk is a systemless root solution. Have a look at /sbin/.magisk and you will see, that /system and /vendor were mounted as mirrors with all modifications that are needed, e.g. Magisk modules.
Only TWRP does some changes on /system.
Wow
Kudos to the guy who said google it. You'd better duckduckgo it to break this cycle, because I also ended up here as the first result!
Elmarigo said:
So is the vbmeta.img the same file for all phones?
Or is it vendor specific?
Or is it phone specific?
Thank you!
Click to expand...
Click to collapse
that was already answered. only 1 version of vbmeta exists.
Hello!
Just unlocked my mi 9t and installed magisk. So far it's working great but I really want to try a custom rom because I don't really like miui.
Now I came from a oneplus 3t that has simple zip files to install roms. Now I see for this device you have gsi roms. My question is do I need to flash vbmeta and how would I go about doing that? Is it device specific? Or is the one in the xda tutorial universal?
Thanks!
They are different.
GSI are for all (or most) of devices (treble-enabled).
Zipped ROMs are device specific.
We still don't have "normal" roms because developers haven't get this phone. So, for now, we have to use GSI.
Some people think vbmeta is specific, but actually, at least for GSI roms, it's universal.
You can flash it using fastboot mode and CMD/Terminal or if TWRP allow it, flash from there.
I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.
Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.
flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse
I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?
https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.
Hello . I really need some help with this problem. When I try to install for example the unofficial dirty unicorns ROM on my pixel 4 after flashing the boot.img the device won't boot into recovery. Its saying error boot prepare and it's stuck in fastboot. This also happens to other ROMs.
Thank you
And yes, I did use the commands to flash to the one slot only and on the both slots too
microcube123 said:
Hello . I really need some help with this problem. When I try to install for example the unofficial dirty unicorns ROM on my pixel 4 after flashing the boot.img the device won't boot into recovery. Its saying error boot prepare and it's stuck in fastboot. This also happens to other ROMs.
Thank you
Click to expand...
Click to collapse
Post your question on the unofficial dirty unicorn ROM thread. They should have the answer to your question.
Homeboy76 said:
Post your question on the unofficial dirty unicorn ROM thread. They should have the answer to your question.
Click to expand...
Click to collapse
This also applies to other ROMs
microcube123 said:
This also applies to other ROMs
Click to expand...
Click to collapse
With all the different types of devices and that use unofficial dirty unicorns ROM, how would one provide a solution without specific information:
- Device model
- Android Version
- ROM
- ROM Version
- etc.
On the other hand, if the information was posted on the thread of the ROM you are trying to install. A solution may have already been posted.
Did you search that thread?
Homeboy76 said:
With all the different types of devices and that use unofficial dirty unicorns ROM, how would one provide a solution without specific information:
- Device model
- Android Version
- ROM
- ROM Version
- etc.
On the other hand, if the information was posted on the thread of the ROM you are trying to install. A solution may have already been posted.
Did you search that thread?
Click to expand...
Click to collapse
Yes, I know and I have searched for it. No one seems to have this problem. Will the problem be fixed if I flash the whole stock factory image? Most people have this problem when magisk patching the factory/stock boot.img.
microcube123 said:
Yes, I know and I have searched for it. No one seems to have this problem. Will the problem be fixed if I flash the whole stock factory image? Most people have this problem when magisk patching the factory/stock boot.img.
Click to expand...
Click to collapse
Now, I understand your problem: I think.
In your original post you couldn't flash the boot.img not the magisk_patched.img.
microcube123 said:
Hello . I really need some help with this problem. When I try to install for example the unofficial dirty unicorns ROM on my pixel 4 after flashing the boot.img the device won't boot into recovery. Its saying error boot prepare and it's stuck in fastboot. This also happens to other ROMs.
Thank you
Click to expand...
Click to collapse
Try this:
- Flash the Stock boot.img to both slots:
(fastboot flash boot boot.img --slot all)
- Delete all magisk_patched.img
- Open Magisk (Beta or Canary) Manager
- Depending on the version of Magisk Manager installed: Set the Update Channel to Beta or Canary.
- Close Magisk Manager, reboot
- Open Magisk Manager
- Tap install (Next to Magisk)
- Tap Select and patch a file
- Navigate to the Stock boot.img that you extracted from the current Factory image (October 2020)
- Select it
- tap the ✓ (Check mark)
- Tap Lets Go
- Wait for Magisk to finish patching it.
- Reboot
- Move the magisk_patched.img from the download folder on your phone to the Platform-tools folder on your Computer
- Flash it
(fastboot flash boot magisk_patched.img)
Let's get this out of the way. I don't have much experience flashing ROMs. I've done it on a few phones, but I can't say I really understood what I was doing. I'm just good at following directions. So, I know about enough to get into trouble.
And ...I've gotten into trouble. My goal is to install LineageOS on my brother's Essential Phone. Based on directions I found here, I determined the active slot was b, so I installed TWRP on slot a. TWRP worked in recovery, but without touch. I then flashed twrp-3.2.3-0-mata.img to the non-active slot. Lastly, I sideloaded twrp-installer-mata-3.2.3-0.zip. I then changed the active slot back to b and rebooted. It now boots only to the bootloader and not to the OS. No matter what option I select--Start, Bootloader, Recovery--it reboots to the bootloader.
Any help to get out of this would be greatly appreciated.
Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps
MuddyDog said:
Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps
Click to expand...
Click to collapse
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.
mcmc08 said:
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.
Click to expand...
Click to collapse
Try:
Fastboot flash:raw boot_slot recovery.img
So, I found a solution. In order to overcome the errors I was getting, I had to use the raw command. So it was fastboot flash:raw boot [image file]. Once Lineage recovery was installed, I could boot to recovery and sideload Lineage.
MuddyDog said:
Try:
Fastboot flash:raw boot_slot recovery.img
Click to expand...
Click to collapse
I guess our replies crossed. At any rate, the raw command did the trick. Thanks for your help.
I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)
Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.
rocketrazr1999 said:
Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.
Click to expand...
Click to collapse
I installed Lineageos directly on the february android stock version. (which is the last one from Essential)
Simply by following the tutorial on the LineageOS website.
Everything worked the first time.
So there is no need to switch back to the January android stock version. The image recovery provided by Lineage works very well.
And for your information LineageOS is updated almost every Monday.
Moreover the developers of the TWRP are not the developers of Essential. Company which closed at the end of February.
---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------
KJannot said:
I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)
Click to expand...
Click to collapse
Which Rom would you like to install instead of Lineage?
groovebox said:
Which Rom would you like to install instead of Lineage?
Click to expand...
Click to collapse
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?
KJannot said:
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?
Click to expand...
Click to collapse
Paranoid Android: What I heard is VoLTE broken, if you enable it, SMS/MMS might not work properly.
Evolution: No update in Android 10 since August, not sure they contine to support Essential phone for Android 11
Pixel Experience: I don't think they Anroid 10 for Essential phone, only official Anroid 9 which is too old
TWRP issue: You need to go back to Jan stock rom before going to any rom if you just flashed LOS
What current stable rom with Nov security update: I'm using crDroid 6.12 (unofficial release but from XDA reliable source)
https://forum.xda-developers.com/essential-phone/development/rom-crdroid-v6-7-t4129739