Home » Topic » fastboot oem unlock wont work after update

fastboot oem unlock wont work after update

Welcome. Forums BLOX2 Forum General fastboot oem unlock wont work after update

This topic contains 8 replies, has 4 voices, and was last updated by  Erick 6 days, 20 hours ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #844

    chris
    Participant

    Hi,

    I did the BLU update and had to factory reboot the phone so want to install a custom rom. i have done the developer options and selected allow OEM unlocking and USB debugging but it wont let me oem unlock.

    #845

    Josh
    Participant

    Same. Can’t oem unlock. Says to do an oem unlock-go over and over to wipe userdata but never actually works.

    #848

    Erick
    Participant

    I’m trying to see if a partial firehose will work.  But I have to setup my environment and this could take a moment.

    #849

    Michael
    Participant

    It seems like after the update RSA never actually validates, there’s an old method to take them from other devices I’m trying once it charges.

    #851

    Michael
    Participant

    Yeah, I can’t even go through USB debugging anymore.

    #852

    Erick
    Participant

    QFIL doesn’t go through USB debugging, it goes through emergency mode which is basically the hardware level flash tool which Qualcomm has in their processor’s firmware.  However, I’ve hit a snag.

    Version binding binds keys to operating system and patch level version. This ensures that an attacker who discovers a weakness in an old version of system or TEE software cannot roll a device back to the vulnerable version and use keys created with the newer version. In addition, when a key with a given version and patch level is used on a device that has been upgraded to a newer version or patch level, the key is upgraded before it can be used, and the previous version of the key invalidated. As the device is upgraded, the keys “ratchet” forward along with the device, but any reversion of the device to a previous release causes the keys to be unusable.
    From Android.com

    If anyone wants to continue the attempt, emmcdl download the kernel partition from a working phone and firehose it via QFIL to an affected phone to see if it fixes the problem.  I’m not going to download the update to attempt this.

    <span class=”_Tgc”>Lasciate ogne speranza, voi ch’intrate.

    At this point, I’ll simply hope that your Google backups may have your pictures and the like.  Anyone want to send an old boot to BLU and address it to the behind of their kernel programmer?
    </span>

    #854

    Michael
    Participant

    Where would I find the kernal partition? I only have a single x2. If someone could provide it I’ll try it out.

    #856

    Michael
    Participant

    Hey, the update from blu relocks the phone but it allows you to unlock the bootloader again. I ran this after factory resetting.

    #890

    Erick
    Participant

    What kind of update? Like another OTA update after their current one that broke the ability to do anything? Or is it on their website?

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.