Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

DC Phoenix unsupported security patch (BLA-L29C432)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DC Phoenix unsupported security patch (BLA-L29C432)

    Hello,

    Thanks for your great software... I have a bricked Mate 10 PRO that refuses to be updated with DC Phoenix. Error is unsupported security patch. I had EMUI9 (Pie) update running just fine when I decided to update to 9.0.0.197 through HuRupdater (my bootloader is unlocked). After flashing in TWRP I got 'no system' error in TWRP and indeed it bootloops. I get to the bootloader, but cannot flash TWRP again.
    I decided to give DC a try, but now I'm stuck at this unsupported security patch error. I read in the forum I need to use the update OEM info tab, but not sure what Kirin 970 version to use. OEM info is being read correctly I think (it reads 'vendor: hw' and 'country: la').

    Your help is much needed - and appreciated

    Rgds

    David

  • #2
    You should try this with all loaders matching your phone's processor.
    >>Free Octohide VPN for Android, find it on Google Play Here<<

    Comment


    • #3
      Hi,

      Thanks for your reply . Whenever is try to update using bootloader it says there is no phone in upgrade mode detected. Does this mean I need to open up and use test points? Rather not with that glass back...

      Comment


      • #4
        Yes, it would require to open the device.
        >>Free Octohide VPN for Android, find it on Google Play Here<<

        Comment


        • #5
          Hi,

          So I removed the back, found the test point using DC-Phoenix picture, but I'm not sure how to enable upgrade mode. I tried several things, either booting with shorted test point, or booting into erecovery then short the testpoint. Either way the phone is not being detected by DC-phoenix as forced upgrade mode. I searched for drivers, tried those found in your repository (Huawei_usb_driver_2.0.6.601 and Huawei_Android_phone_drivers_2) but no luck.

          - do I need special drivers, or is my installation just messed up and should it work with these?
          - am I doing it wrong with the test point? At what point should I short the test point and for how long?

          Device is only able to boot into fastboot or erecovery, other options are stuck at 'device is booting'. Bootloader and FRP show unlocked in fastboot.

          Please advice, I have now bought a timed license for a second time...

          Comment


          • #6
            How does your phone appear in device manager when connected using testpoint? I can not teach you how to short circuit, its better if you won't do it at all if you do not know how to as it may fry whole board.
            >>Free Octohide VPN for Android, find it on Google Play Here<<

            Comment


            • #7
              Hi,

              I'm not worried about shorting the test pin, I'm an electronics engineer, I simply miss the instructions on how long and at what point I need to short the test pin. The phone appears in the device manager as different devices depending on what mode the phone is in. I simply need some guidance on the test mode, none of the guides is very clear in what drivers are expected to be installed, etc. and none of them are clear on when to ground the test pin (while phone is off? while in fastboot/erecovery/other mode?)

              Rgds

              Comment

              Working...
              X