[Please help] what is next step? after flashing vbmeta
[Please help] what is next step? after flashing vbmeta
(26-02-2021, 06:37 PM)hovatek(26-02-2021, 01:16 PM)Hasan Mahmud BD ...
This outcome isn't surprising. it means your OEM didn't use default keys to sign partitions.
Its down to custom.
There's going to be a lot of repetition with slight differences so ensure to do exactly as instructed.
Now, build a vbmeta from scratch (all keys from stock vbmeta) and change only flag to 2.
The last one you did was different at boot (from the output of python avbtool info_image --image) so re-check to be sure that your extracted public key for boot is correct and you didn't put a custom public key for boot partition when building vbmeta
Lets see the output of info-image for both to compare
(27-02-2021, 11:52 AM)Hasan Mahmud BD changed only flag to 2
all keys are same (attached 1 image)
image : custom flag2 vbmeta vs stock vbmeta
(01-03-2021, 09:03 AM)hovatekvbmeta flashed but sign boot img not flashing...(27-02-2021, 11:52 AM)Hasan Mahmud BD changed only flag to 2
all keys are same (attached 1 image)
image : custom flag2 vbmeta vs stock vbmeta
Flash this created vbmeta and confirm if the phone boots fine.
Next,
1. Create a vbmeta with just boot partition having a custom public key
2. Patch the stock boot using magisk manager
3. Unpack and repack the patched boot using android image kitchen
4. Sign the newly repacked image (ensure the custom public key used for boot partition when creating the vbmeta was generated from the private key you'll use to sign the boot image)
5. Flash this boot image then boot the phone
(02-03-2021, 09:50 AM)Hasan Mahmud BD vbmeta flashed but sign boot img not flashing...Repeat my last instruction but this time, dont unpack-repack with android image kitchen.
.
.
after this i made new vbmeta with this command *:
avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 0 --chain_partition boot:1:keys/key_boot.bin --padding_size 16384 --output vbmeta-sign-custom.img
.(it was a big mistake)
.
and i flashed it ! now my phone just showing logo and nothing working !
i hvae to flash my phone after install windows
then i will back,,,,, if you have any suggestion give me
(02-03-2021, 11:03 AM)hovatek(02-03-2021, 09:50 AM)Hasan Mahmud BD vbmeta flashed but sign boot img not flashing...Repeat my last instruction but this time, dont unpack-repack with android image kitchen.
.
.
after this i made new vbmeta with this command *:
avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 0 --chain_partition boot:1:keys/key_boot.bin --padding_size 16384 --output vbmeta-sign-custom.img
.(it was a big mistake)
.
and i flashed it ! now my phone just showing logo and nothing working !
i hvae to flash my phone after install windows
then i will back,,,,, if you have any suggestion give me
just patch with magisk manager canary version then sign and try flash
if it still doesn't flash then something must be wrong with how you're signing boot
(06-03-2021, 12:52 PM)Hasan Mahmud BD
error for magisk canary patched img:
avbtool add_hash_footer --image magisk_boot.img --partition_name boot --partition_size 36700160 --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096
/usr/bin/avbtool: Image size of 36700160 exceeds maximum image size of 36630528 in order to fit in a partition size of 36700160.
.
but avbtool able to sign stock boot img without any error
(09-03-2021, 10:37 AM)hovatek(06-03-2021, 12:52 PM)Hasan Mahmud BD
error for magisk canary patched img:
avbtool add_hash_footer --image magisk_boot.img --partition_name boot --partition_size 36700160 --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096
/usr/bin/avbtool: Image size of 36700160 exceeds maximum image size of 36630528 in order to fit in a partition size of 36700160.
.
but avbtool able to sign stock boot img without any error
Stick to gaining root via the recovery partition then
avbtool info_image --image magisk_patched_boot.img
Footer version: 1.0
Image size: 36700160 bytes
Original image size: 17793024 bytes
VBMeta offset: 17793024
VBMeta size: 2112 bytes
--
Minimum libavb version: 1.0
Header Block: 256 bytes
Authentication Block: 576 bytes
Auxiliary Block: 1280 bytes
Algorithm: SHA256_RSA4096
Rollback Index: 0
Flags: 3
Release String: 'avbtool 1.1.0'
Descriptors:
Hash descriptor:
Image Size: 17303552 bytes
Hash Algorithm: sha256
Partition Name: boot
Salt: a76f7eb77befe20d8a9a2b455f0d68199aac7940fb7e1883baef66db52407238
Digest: 80b0f0ac5335e3a5d4102ec48e48835ca7c791a40c467adb12ada0d9157cee81
Flags: 0
(13-03-2021, 08:05 AM)Hasan Mahmud BD ..
then i compared sotckboot and magisk boot img
only the vbmeta original size and vbmeta offset not matching (screenshot given)
[/b]