We're hiring! Apply Now

Hovatek Forum DEVELOPMENT Android ITEL A56 IN BOOTLOOP AFTER FLASHING CUSTOM SIGNED VBMETA FOR ROOT PURPOSE

ITEL A56 IN BOOTLOOP AFTER FLASHING CUSTOM SIGNED VBMETA FOR ROOT PURPOSE

ITEL A56 IN BOOTLOOP AFTER FLASHING CUSTOM SIGNED VBMETA FOR ROOT PURPOSE

Ubakaemma360
Ubakaemma360
Ubakaemma360
Newbie
3
04-10-2024, 01:46 PM
#1



Hello
so i ran into problems while trying to root my itel a56 using various guides from this platform where i was able to unlock the bootloader with a guide that was not conventional about me using a modified fastboot 
so after successful unlock i patched the recovery.img i'd extracted from the stock firmware with magisk and tried to flash it using fastboot but it kept gettting stuck at the 'writing recovery' each time then i stumbled upon a thread that insisted a signed vbmeta be flashed before flashing the patched recoveery.img... so i managed to sign the vbmeta and flash it but afterwards my device has been in a bootloop and i cant access the recovery, the bootloader and fastboot... i'd even wanted to flash the stock firmware back but my pc cannot even see/recognize my phone when connected via usb, adb devices or fastboot devices... i've been stuck here and hope for a fix...please help me its giving me headaches.

i will attach the signed custom vbmeta i flashed and the vbmeta i used to sign it


i use linux pc btw...
This post was last modified: 04-10-2024, 01:50 PM by Ubakaemma360.
Attached Files
.img
vbmeta-sign.img
Size: 1 MB / Downloads: 2
.img
vbmeta-sign-custom.img
Size: 1 MB / Downloads: 1
justshez
justshez
justshez
Intern
2,433
04-10-2024, 06:00 PM
#2
(04-10-2024, 01:46 PM)Ubakaemma360 Hello
so i ran into problems while trying to root my itel a56 using various guides from this platform where i was able to unlock the bootloader with a guide that was not conventional about me using a modified fastboot 
so after successful unlock i patched the recovery.img i'd extracted from the stock firmware with magisk and tried to flash it using fastboot but it kept gettting stuck at the 'writing recovery' each time then i stumbled upon a thread that insisted a signed vbmeta be flashed before flashing the patched recoveery.img... so i managed to sign the vbmeta and flash it but afterwards my device has been in a bootloop and i cant access the recovery, the bootloader and fastboot... i'd even wanted to flash the stock firmware back but my pc cannot even see/recognize my phone when connected via usb, adb devices or fastboot devices... i've been stuck here and hope for a fix...please help me its giving me headaches.

i will attach the signed custom vbmeta i flashed and the vbmeta i used to sign it


i use linux pc btw...
Flashback stock vbmeta with research download tool @ https://www.hovatek.com/forum/thread-1231.html

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Gargoyle
Gargoyle
Gargoyle
Contributor
540
05-10-2024, 03:08 AM
#3
I'm not surprised, the keys absolutely do not agree, where did you get them??

[Image: 1-2024-10-05-04-03-49.jpg]
Gargoyle
Gargoyle
Gargoyle
Contributor
540
05-10-2024, 03:56 AM
#4
[ Login to download]
Code:

Minimum libavb version:   1.0
Header Block:             256 bytes
Authentication Block:     576 bytes
Auxiliary Block:          12416 bytes
Public key (sha1):        2597c218aae470a130f61162feaae70afd97f011
Algorithm:                SHA256_RSA4096
Rollback Index:           0
Flags:                    0
Rollback Index Location:  0
Release String:           'avbtool 1.1.0'
Descriptors:
    Chain Partition descriptor:
      Partition Name:          boot
      Rollback Index Location: 1
      Public key (sha1):       ea410c1b46cdb2e40e526880ff383f083bd615d5
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          system
      Rollback Index Location: 3
      Public key (sha1):       e2c66ff8a1d787d7bf898711187bff150f691d27
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          vendor
      Rollback Index Location: 4
      Public key (sha1):       9885bf5bf909e5208dfd42abaf51ad9b104ee117
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          product
      Rollback Index Location: 10
      Public key (sha1):       766a95798206f6e980e42414e3cb658617c27daf
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          dtbo
      Rollback Index Location: 9
      Public key (sha1):       ea410c1b46cdb2e40e526880ff383f083bd615d5
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          recovery
      Rollback Index Location: 2
      Public key (sha1):       2597c218aae470a130f61162feaae70afd97f011
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          w_modem
      Rollback Index Location: 5
      Public key (sha1):       e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          w_gdsp
      Rollback Index Location: 6
      Public key (sha1):       e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          pm_sys
      Rollback Index Location: 7
      Public key (sha1):       e93e7d91ba1a46b81a5f15129b4dc5769bf41f26
      Flags:                   0
    Chain Partition descriptor:
      Partition Name:          dtb
      Rollback Index Location: 11
      Public key (sha1):       ea410c1b46cdb2e40e526880ff383f083bd615d5
      Flags:                   0
Ubakaemma360
Ubakaemma360
Ubakaemma360
Newbie
3
05-10-2024, 03:23 PM
#5



(05-10-2024, 03:08 AM)Gargoyle I'm not surprised, the keys absolutely do not agree, where did you get them??

[Image: 1-2024-10-05-04-03-49.jpg]

i used a guide on here to extract my keys from stock signed vbmeta in firmware and compiled the custom one...bummer coz i thought i did it correctly
Ubakaemma360
Ubakaemma360
Ubakaemma360
Newbie
3
05-10-2024, 03:24 PM
#6
maxpayne
maxpayne
maxpayne
Intern
4,115
10-10-2024, 06:54 PM
#7
(04-10-2024, 01:46 PM)Ubakaemma360 i will attach the signed custom vbmeta i flashed and the vbmeta i used to sign it


i use linux pc btw...

Your priority now is to unbrick.
Which tool are you using to try flash the firmware and can you get a Windows PC?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
Join us
WhTlYt