[KevinB]

Hi all, I've tried (and failed) to unlock the bootloader of this device using the method found here: https://www.hovatek.com/forum/thread-32287.html 
I get stuck on the final step and receive the error "FAILED (remote: Unlock bootloader fail.)" I think the vbmeta-sign may have a different RSA key from the one used in the guide so I've attached the stock one to see if someone can confirm it. 
Another weird thing that pops up when I type "./fastboot oem get_identifier_token" is that it shows two Identifier Tokens instead of one, is that normal?

(bootloader) 54313031315336344742454XXXXXXXXX

(bootloader) 3733343XXXXXXX 


Any help would be appreciated!

[hovatek]

Hi all, I've tried (and failed) to unlock the bootloader of this device using the method found here: https://www.hovatek.com/forum/thread-32287.html 
I get stuck on the final step and receive the error "FAILED (remote: Unlock bootloader fail.)" I think the vbmeta-sign may have a different RSA key from the one used in the guide so I've attached the stock one to see if someone can confirm it. 
Another weird thing that pops up when I type "./fastboot oem get_identifier_token" is that it shows two Identifier Tokens instead of one, is that normal?

(bootloader) 54313031315336344742454XXXXXXXXX

(bootloader) 3733343XXXXXXX 


Any help would be appreciated!

You didn't attach anything.
Post a link to your stock vbmeta

[X3non]

Hi all, I've tried (and failed) to unlock the bootloader of this device using the method found here: https://www.hovatek.com/forum/thread-32287.html 
I get stuck on the final step and receive the error "FAILED (remote: Unlock bootloader fail.)" I think the vbmeta-sign may have a different RSA key from the one used in the guide so I've attached the stock one to see if someone can confirm it. 
Another weird thing that pops up when I type "./fastboot oem get_identifier_token" is that it shows two Identifier Tokens instead of one, is that normal?

(bootloader) 54313031315336344742454XXXXXXXXX3733343XXXXXXX 


Any help would be appreciated!

there's nothing anyone can do if the device uses a different private key, only the OEM can really help at this point
did you try combining both tokens into one?
e.g 54313031315336344742454XXXXXXXXX3733343XXXXXXX

also use the guide @ https://www.hovatek.com/forum/thread-32666.html
confirm if the vbmeta's algorithm is rsa4096 or something different

[KevinB]

You didn't attach anything.
Post a link to your stock vbmeta

Could've sworn I did   It's alright now as the problem has been resolved!

did you try combining both tokens into one?

This worked! Something so simple yet I didn't think of it, bootloader has been unlocked now. Thanks!