Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

CLT-L09 Cannot Enable Software Testpoint in DC Phoenix, Update Mode stuck at 5%

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

  • CLT-L09 Cannot Enable Software Testpoint in DC Phoenix, Update Mode stuck at 5%

    Hello,

    I am having trouble enabling software testpoint on my CLT-L09. The phone reboots into upgrade mode and then hangs at 5% and does not proceed any further. Rebooting manually into upgrade mode brings me back to the same 5% screen.

    DC Phoenix gets stuck at 'Looking for device in upgrade mode'. In device manager I see three devices called 'generic_a15' with no drivers installed.

    Current OS version EMUI 10.0.0.185.

    I have tried forcing a rollback to an older version of EMUI via HiSuite and HiSuite Proxy but this fails every time, I have tried many, many versions.

    My ultimate goal is to unlock the bootloader and install TWRP. Any help with this would be most appreciated. I only have 48h left on my licence!

    Thank you,

    Brandon

    Debug log:

    Doing job: Enable software testpoint

    Looking for devices...

    Looking for devices by ports
    No device deteced
    Number of devices found: 1
    Number of devices found: 1
    Device authorized
    Base Version:CLT-LGRP2-OVS 10.0.0.185
    Cust Version:CLT-L09-CUST 10.0.0.8(C432)
    Preload Version:CLT-L09-PRELOAD 10.0.0.3(C432R1)
    Name:CLT-L09
    Model:CLT-L09
    Board:CLT
    IMEI:867259038534917
    IMEI1:867259038534917
    MEID:A000009B77A7F8
    SN:LCL7N18A1500146

    USB Device REMOVAL
    Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: 5&2e2d6e34&0&2
    Looking for device in upgrade mode...

    USB Device INSERTION
    Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: 5&2e2d6e34&0&2
    Process was cancelled by user;
    No devices detected in UPDATE mode

    Process FAIL.
    Please, try with device in Update mode and selecting a compatible firmware file​

  • #2
    Update:

    I have managed to finally get the drivers working and the PC to see the phone in upgrade mode after installing some different drivers and using an older version of DC Phoenix. However, enabling software testpoint still fails.

    I would like to try the fastboot and upgrade mode methods but I am struggling to find an appropriate UPDATE.APP for my phones firmware. Can somebody please advise?

    Thank you,

    Brandon

    Debug log:
    DC Phoenix 0.0.0.153
    user:brandonjn


    Doing job: Enable software testpoint

    Looking for devices...

    Looking for devices by ports
    No device deteced
    Number of devices found: 1
    Number of devices found: 1
    Device authorized
    Base Version:CLT-LGRP2-OVS 10.0.0.201
    Cust Version:CLT-L09-CUST 10.0.0.8(C432)
    Preload Version:CLT-L09-PRELOAD 10.0.0.3(C432R1)
    Name:CLT-L09
    Model:CLT-L09
    Board:CLT
    IMEI:867259038534917
    IMEI1:867259038534917
    MEID:A000009B77A7F8
    SN:LCL7N18A1500146

    USB Device REMOVAL
    Type: @oem286.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: LCL7N18A15001465
    Looking for device in upgrade mode...

    USB Device INSERTION
    Type: @oem286.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: LCL7N18A15001465

    USB Device REMOVAL
    Type: @oem286.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: LCL7N18A15001465

    USB Device INSERTION
    Type: @oem286.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: LCL7N18A15001465

    USB Device REMOVAL
    Type: @oem286.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: LCL7N18A15001465

    USB Device INSERTION
    Type: @oem286.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: LCL7N18A15001465
    COM15: DBAdapter Reserved Interface (COM15)
    COM17: Android Adapter PCUI (COM17)
    Devices detected in UPDATE mode

    2025-02-09 18:07:07 Starting to write device in UPGRADE mode...
    Device found: LCL7N18A15001465



    2025-02-09 18:07:14 start to update enable testpoint
    File to update: ENABLE_TESTPOINT.dtwork

    Process identifier:73981725

    Validating file...
    Looking for attached port...
    Preparing to write...
    Bypass version checked
    Checking partition ...

    Extracting partition SHA256RSA...
    Writing partition: SHA256RSA...OK

    Extracting partition CRC...
    Writing partition: CRC...OK

    Extracting partition BASE_VERLIST...
    Writing partition: BASE_VERLIST...
    Error downloading file ENABLE_TESTPOINT_2.dtwork, partition: BASE_VERLIST

    Error writing software
    2025-02-09 18:07:30 Writing device finished with ERROR

    Process FAIL.
    Please, try with device in Update mode and selecting a compatible firmware file

    Comment


    • #3
      As per tutorial in software tp there is no guarantee that it will work hence you should always be prepared for the hardware one even before you attempt the software solution. Not all phones/versions support software tp sadly.
      >>Free Octohide VPN for Android, find it on Google Play Here<<

      Comment


      • #4
        After downgrading to EMUI 9.1 I succeeded in getting software testpoint. However, despite what HCU client is saying, my bootloader is still locked. Researching further, I've found if you search for the bootloader unlock code provided by HCU Client (36KYPYUUYHVKFDOX) you will see that this is a generic bootloader unlock code that does not work. This code also doesn't work in fastboot via 'fastboot oem unlock' method.





        I'd like to be considered for a refund please, since HCU was unsuccessful in unlocking my bootloader.

        Log:
        Bootloader User lock: locked

        Found signed IMEI:
        Key: 0x8F04
        IMEI1: 867259038534917
        IMEI2: 867259038534917
        SIM NW_LOCK status: LOCKED

        Found NV data.
        Modems: S
        IMEI1: 867259038534917
        IMEI2: 867259038534917
        IMEIS: 000000000000000
        PESN: 800606E
        MEID: A000009B77A7F8

        Found OEM data:
        Model: CLT-L09
        Firmware: CLT-L09 9.0.0.163(C432E5R1P9)
        Rescue: rescue Chipset-boston 8.1.0.001(01VW)
        Vendor: hw
        Country: eu
        Version limitation: ON
        SIMCARDMODE: single
        Bootloader User lock: locked
        Phone ID: 2631E7907D7787A

        2025-02-10 15:42:32.032 Repairing
        2025-02-10 15:42:32.215 Update PIHeadFile bin success!
        2025-02-10 15:42:32.750 Write Bootloader code success! Code 36KYPYUUYHVKFDOX
        2025-02-10 15:42:32.934 Write partition modem_secure
        2025-02-10 15:42:32.938 Write partition modem_secure success!
        2025-02-10 15:42:32.948 Write partition oeminfo
        2025-02-10 15:42:32.978 Write partition oeminfo success!
        2025-02-10 15:42:36.144 Unlocking restrictions
        2025-02-10 15:42:36.173 Unlock restrictions success!
        2025-02-10 15:42:36.179 Rebooting
        2025-02-10 15:42:36.196 Reboot success!
        2025-02-10 15:42:36.204 Done!

        Comment


        • #5
          Originally posted by brandonjjn View Post
          After downgrading to EMUI 9.1 I succeeded in getting software testpoint. However, despite what HCU client is saying, my bootloader is still locked. Researching further, I've found if you search for the bootloader unlock code provided by HCU Client (36KYPYUUYHVKFDOX) you will see that this is a generic bootloader unlock code that does not work. This code also doesn't work in fastboot via 'fastboot oem unlock' method.





          I'd like to be considered for a refund please, since HCU was unsuccessful in unlocking my bootloader.

          Log:
          Bootloader User lock: locked

          Found signed IMEI:
          Key: 0x8F04
          IMEI1: 867259038534917
          IMEI2: 867259038534917
          SIM NW_LOCK status: LOCKED

          Found NV data.
          Modems: S
          IMEI1: 867259038534917
          IMEI2: 867259038534917
          IMEIS: 000000000000000
          PESN: 800606E
          MEID: A000009B77A7F8

          Found OEM data:
          Model: CLT-L09
          Firmware: CLT-L09 9.0.0.163(C432E5R1P9)
          Rescue: rescue Chipset-boston 8.1.0.001(01VW)
          Vendor: hw
          Country: eu
          Version limitation: ON
          SIMCARDMODE: single
          Bootloader User lock: locked
          Phone ID: 2631E7907D7787A

          2025-02-10 15:42:32.032 Repairing
          2025-02-10 15:42:32.215 Update PIHeadFile bin success!
          2025-02-10 15:42:32.750 Write Bootloader code success! Code 36KYPYUUYHVKFDOX
          2025-02-10 15:42:32.934 Write partition modem_secure
          2025-02-10 15:42:32.938 Write partition modem_secure success!
          2025-02-10 15:42:32.948 Write partition oeminfo
          2025-02-10 15:42:32.978 Write partition oeminfo success!
          2025-02-10 15:42:36.144 Unlocking restrictions
          2025-02-10 15:42:36.173 Unlock restrictions success!
          2025-02-10 15:42:36.179 Rebooting
          2025-02-10 15:42:36.196 Reboot success!
          2025-02-10 15:42:36.204 Done!
          Refund for the time license account is not available after you log in with it. There is no such thing as generic bootloader code. Make sure you copy paste the code when unlocking it via cmd as per usual users make grammar mistakes in symbols such as 0 and O. Your user name doesn't show that repair/write bootloader code would of been done completed either.
          >>Free Octohide VPN for Android, find it on Google Play Here<<

          Comment

          Working...
          X