Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

DC-Phoenix

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Valdemaras
    replied
    Originally posted by uradryct View Post

    im still stuck


    All i get is a bricked phone and this useless thing:
    2023-10-02 16:52:22.630 Write Bootloader code success! Code: 36KYPYUUYHVKFDOX

    Is it possible a refund?
    Refund for time license is unavailable. The code you see is the bootloader code that you can use on cmd. If you bricked your phone by writing random incorrect CPU data as visible from your logs you may need to reflash it from scratch with board software if reset, clear data/cache from the recovery menu and reflashing stock ROM does not help.

    Leave a comment:


  • uradryct
    replied
    Originally posted by uradryct View Post

    970 but which version? T1 or T2? V2, V3,...?

    And where is the option to write OEM file?

    I also tried flashing from Phoenix with recommended firm and it's give the error "no recovery found"


    I'm unable to enter download mode or erecovery indeed.

    Update1:
    I manage to enter rescue mode but i cant unlock FRP because recovery partition doesnt exist

    Update 2:
    EMUI 9.1 installed with erecovery and download mode working. Hisuite doesnt let my to repair it.
    Phone dont boot: Your device has failed verification.

    Now doenst show FPR locked, just Phone locked.
    im still stuck


    All i get is a bricked phone and this useless thing:
    2023-10-02 16:52:22.630 Write Bootloader code success! Code: 36KYPYUUYHVKFDOX

    Is it possible a refund?
    Last edited by uradryct; 2023-10-02, 03:54 PM.

    Leave a comment:


  • uradryct
    replied
    Originally posted by Krzysztof GorÄâ¦czko View Post

    P20 Pro - Clt-l09 - > Kirin 970 not 710.

    Use write Oem file to downgrade software
    970 but which version? T1 or T2? V2, V3,...?

    And where is the option to write OEM file?

    I also tried flashing from Phoenix with recommended firm and it's give the error "no recovery found"


    I'm unable to enter download mode or erecovery indeed.

    Update1:
    I manage to enter rescue mode but i cant unlock FRP because recovery partition doesnt exist

    Update 2:
    EMUI 9.1 installed with erecovery and download mode working. Hisuite doesnt let my to repair it.
    Phone dont boot: Your device has failed verification.

    Now doenst show FPR locked, just Phone locked.
    Last edited by uradryct; 2023-10-02, 01:23 PM.

    Leave a comment:


  • Krzysztof GorÄ…czko
    replied
    Originally posted by uradryct View Post
    Hi, i tried to enter in software testpoint and I got it.
    My device:
    Huawei P20 Pro CLT-L09 hw eu Charlotte-L09C 9.1.0.387(C432E8R1P11)

    The log from entering in softwar testpoint:
    Code:
    DC Phoenix 0.0.0.173
    user:uradryct
    
    
    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 9.1.0.387
    Cust Version:CLT-L09-CUST 9.1.0.8(C432)
    Preload Version:CLT-L09-PRELOAD 9.1.0.11(C432R1)
    Name:CLT-L09
    Model:CLT-L09
    Board:CLT
    
    USB Device REMOVAL
    Type: @oem44.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: 5&2485d9d1&0&2
    Looking for device in upgrade mode...
    
    USB Device INSERTION
    Type: @oem44.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: 5&2485d9d1&0&1
    Looking for device in upgrade mode...
    COM7: DBAdapter Reserved Interface (COM7)
    COM8: Android Adapter PCUI (COM8)
    Devices detected in UPDATE mode
    
    01/10/2023 17:01:18 Starting to write device in UPGRADE mode...
    Device found: LCL7N18C10002089
    
    
    
    01/10/2023 17:01:20 start to update enable testpoint
    File to update: ENABLE_TESTPOINT.dtwork
    
    Process identifier:73485951
    
    Validating file...
    Looking for attached port...
    Preparing to write...
    Bypass version checked
    Checking partition ...
    
    Extracting partition SHA256RSA...
    Writing partition: SHA256RSA...
    Writing partition: SHA256RSA...OK
    
    Extracting partition CRC...
    Writing partition: CRC...
    Writing partition: CRC...OK
    
    Extracting partition BASE_VERLIST...
    Writing partition: BASE_VERLIST...
    Writing partition: BASE_VERLIST...OK
    
    Extracting partition PACKAGE_TYPE...
    Writing partition: PACKAGE_TYPE...
    Writing partition: PACKAGE_TYPE...OK
    
    Extracting partition XLOADER...
    Writing partition: XLOADER...
    Writing partition: XLOADER...OK
    Software written
    01/10/2023 17:01:36 Writing device finished OK​
    The problem comes when I try to read info from HCU, repair unlocking bootloader or even trying to exit from testpoint.
    As soon as HCU start to download dtwork files or step2 in DC-Phoenix, the phone disconect and reconect, and the process always fail.

    Code:
    01/10/2023 22:01:23
    HCU Client v1.0.0.0382
    Account: uradryct
    
    Before operation turn phone to TestPoint mode:
    Turn off phone, then short TestPoint on phone pcb
    and plug USB cable
    Wait for device "HUAWEI USB COM 1.0" in Ports
    
    
    Repair
    New FB User Lock : UNLOCKED
    Unlock downgrade/customization limitations
    Selected Cpu/Bootloader - Kirin710_P1_V2
    2023-10-01 22:01:24.379 Connecting to server...
    2023-10-01 22:01:24.566 Connected!
    2023-10-01 22:01:25.207 Find device COM4, handle 10864
    BOOTLOADER selected to update:Kirin710_P1_V2
    downloading file Kirin710_P1_V2_0.dtwork...
    downloading file Kirin710_P1_V2_2.dtwork...
    Process file Kirin710_P1_V2_2.dtwork Fail, repeat...
    2023-10-01 22:01:31.013 unknown responce!​
    Code:
    01/10/2023 21:57:57
    HCU Client v1.0.0.0382
    Account: uradryct
    
    Before operation turn phone to TestPoint mode:
    Turn off phone, then short TestPoint on phone pcb
    and plug USB cable
    Wait for device "HUAWEI USB COM 1.0" in Ports
    
    
    Read phone info
    2023-10-01 21:57:57.341 Selected Cpu/Bootloader - Kirin710_P1_V2
    2023-10-01 21:57:57.349 Connecting to server...
    2023-10-01 21:57:57.641 Connected!
    2023-10-01 21:57:58.351 Find device COM4, handle 10588
    BOOTLOADER selected to update:Kirin710_P1_V2
    downloading file Kirin710_P1_V2_0.dtwork...
    downloading file Kirin710_P1_V2_2.dtwork...
    Process file Kirin710_P1_V2_2.dtwork Fail, repeat...
    2023-10-01 21:58:04.522 unknown responce!
    ​
    Code:
    bootloader file download successfully
    DC Phoenix 0.0.0.173
    user:uradryct
    
    
    Doing job: Disable software testpoint
    
    Looking for devices...
    
    Looking for devices in testpoint mode
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    BOOTLOADER selected to update:Kirin710_P1_V2
    DC Phoenix 0.0.0.173
    user:uradryct
    
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    BOOTLOADER selected to update:Kirin710_P1_V2
    01/10/2023 22:44:57 Starting to write device...
    
    Process identifier:73490478
    
    Validating file...
    
    Writing bootloader...
    Step 2...
    
    USB Device REMOVAL
    Type: @oem43.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&2485d9d1&0&1
    
    USB Device INSERTION
    Type: @oem43.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&2485d9d1&0&1
    
    Error writing Bootloader
    01/10/2023 22:45:59 Writing device finished - INCOMPLETE
    
    Doing job: Read info
    
    Looking for devices...
    
    Looking for devices in testpoint mode
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    BOOTLOADER selected to update:Kirin710_P1_V2
    DC Phoenix 0.0.0.173
    user:uradryct
    
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    BOOTLOADER File to update: Kirin710_P1_V2
    01/10/2023 22:46:51 Starting to write device...
    
    Process identifier:73490489
    
    
    Writing bootloader...
    Step 2...
    
    USB Device REMOVAL
    Type: @oem43.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&2485d9d1&0&1
    
    USB Device INSERTION
    Type: @oem43.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&2485d9d1&0&1
    
    Error writing Bootloader
    01/10/2023 22:47:50 Process finished - INCOMPLETE​
    P20 Pro - Clt-l09 - > Kirin 970 not 710.

    Use write Oem file to downgrade software

    Leave a comment:


  • uradryct
    replied
    Hi, i tried to enter in software testpoint and I got it.
    My device:
    Huawei P20 Pro CLT-L09 hw eu Charlotte-L09C 9.1.0.387(C432E8R1P11)

    The log from entering in softwar testpoint:
    Code:
    DC Phoenix 0.0.0.173
    user:uradryct
    
    
    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 9.1.0.387
    Cust Version:CLT-L09-CUST 9.1.0.8(C432)
    Preload Version:CLT-L09-PRELOAD 9.1.0.11(C432R1)
    Name:CLT-L09
    Model:CLT-L09
    Board:CLT
    
    USB Device REMOVAL
    Type: @oem44.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: 5&2485d9d1&0&2
    Looking for device in upgrade mode...
    
    USB Device INSERTION
    Type: @oem44.inf,%busfilter.devicedesc%;USB Composite Device
    VidPid: VID_12D1&PID_107E
    Instance id: 5&2485d9d1&0&1
    Looking for device in upgrade mode...
    COM7: DBAdapter Reserved Interface (COM7)
    COM8: Android Adapter PCUI (COM8)
    Devices detected in UPDATE mode
    
    01/10/2023 17:01:18 Starting to write device in UPGRADE mode...
    Device found: LCL7N18C10002089
    
    
    
    01/10/2023 17:01:20 start to update enable testpoint
    File to update: ENABLE_TESTPOINT.dtwork
    
    Process identifier:73485951
    
    Validating file...
    Looking for attached port...
    Preparing to write...
    Bypass version checked
    Checking partition ...
    
    Extracting partition SHA256RSA...
    Writing partition: SHA256RSA...
    Writing partition: SHA256RSA...OK
    
    Extracting partition CRC...
    Writing partition: CRC...
    Writing partition: CRC...OK
    
    Extracting partition BASE_VERLIST...
    Writing partition: BASE_VERLIST...
    Writing partition: BASE_VERLIST...OK
    
    Extracting partition PACKAGE_TYPE...
    Writing partition: PACKAGE_TYPE...
    Writing partition: PACKAGE_TYPE...OK
    
    Extracting partition XLOADER...
    Writing partition: XLOADER...
    Writing partition: XLOADER...OK
    Software written
    01/10/2023 17:01:36 Writing device finished OK​
    The problem comes when I try to read info from HCU, repair unlocking bootloader or even trying to exit from testpoint.
    As soon as HCU start to download dtwork files or step2 in DC-Phoenix, the phone disconect and reconect, and the process always fail.

    Code:
    01/10/2023 22:01:23
    HCU Client   v1.0.0.0382
    Account: uradryct
    
    Before operation turn phone to TestPoint mode:
    Turn off phone, then short TestPoint on phone pcb
    and plug USB cable
    Wait for device "HUAWEI USB COM 1.0" in Ports
    
    
    Repair
    New FB User Lock : UNLOCKED
    Unlock downgrade/customization limitations
    Selected Cpu/Bootloader - Kirin710_P1_V2
    2023-10-01 22:01:24.379 Connecting to server...
    2023-10-01 22:01:24.566 Connected!
    2023-10-01 22:01:25.207 Find device COM4, handle 10864
    BOOTLOADER selected to update:Kirin710_P1_V2
    downloading file Kirin710_P1_V2_0.dtwork...
    downloading file Kirin710_P1_V2_2.dtwork...
    Process file Kirin710_P1_V2_2.dtwork Fail, repeat...
    2023-10-01 22:01:31.013 unknown responce!​
    Code:
    01/10/2023 21:57:57
    HCU Client   v1.0.0.0382
    Account: uradryct
    
    Before operation turn phone to TestPoint mode:
    Turn off phone, then short TestPoint on phone pcb
    and plug USB cable
    Wait for device "HUAWEI USB COM 1.0" in Ports
    
    
    Read phone info
    2023-10-01 21:57:57.341 Selected Cpu/Bootloader - Kirin710_P1_V2
    2023-10-01 21:57:57.349 Connecting to server...
    2023-10-01 21:57:57.641 Connected!
    2023-10-01 21:57:58.351 Find device COM4, handle 10588
    BOOTLOADER selected to update:Kirin710_P1_V2
    downloading file Kirin710_P1_V2_0.dtwork...
    downloading file Kirin710_P1_V2_2.dtwork...
    Process file Kirin710_P1_V2_2.dtwork Fail, repeat...
    2023-10-01 21:58:04.522 unknown responce!
    ​
    Code:
    bootloader file download successfully
    DC Phoenix 0.0.0.173
    user:uradryct
    
    
    Doing job: Disable software testpoint
    
    Looking for devices...
    
    Looking for devices in testpoint mode
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    BOOTLOADER selected to update:Kirin710_P1_V2
    DC Phoenix 0.0.0.173
    user:uradryct
    
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    BOOTLOADER selected to update:Kirin710_P1_V2
    01/10/2023 22:44:57 Starting to write device...
    
    Process identifier:73490478
    
    Validating file...
    
    Writing bootloader...
    Step 2...
    
    USB Device REMOVAL
    Type: @oem43.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&2485d9d1&0&1
    
    USB Device INSERTION
    Type: @oem43.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&2485d9d1&0&1
    
    Error writing Bootloader
    01/10/2023 22:45:59 Writing device finished - INCOMPLETE
    
    Doing job: Read info
    
    Looking for devices...
    
    Looking for devices in testpoint mode
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    BOOTLOADER selected to update:Kirin710_P1_V2
    DC Phoenix 0.0.0.173
    user:uradryct
    
    Device detected:
    COM4: HUAWEI USB COM 1.0 (COM4)
    BOOTLOADER File to update: Kirin710_P1_V2
    01/10/2023 22:46:51 Starting to write device...
    
    Process identifier:73490489
    
    
    Writing bootloader...
    Step 2...
    
    USB Device REMOVAL
    Type: @oem43.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&2485d9d1&0&1
    
    USB Device INSERTION
    Type: @oem43.inf,%qcomdevice00%;HUAWEI USB COM 1.0
    VidPid: VID_12D1&PID_3609
    Instance id: 5&2485d9d1&0&1
    
    Error writing Bootloader
    01/10/2023 22:47:50 Process finished - INCOMPLETE​
    Last edited by uradryct; 2023-10-01, 09:54 PM.

    Leave a comment:


  • waletogo
    replied
    thanks , i got it.

    Leave a comment:


  • Valdemaras
    replied
    I see, you need to click on selection window "Files of type" box and select .DGTKS manually for those files to be visible.

    Leave a comment:


  • waletogo
    replied
    In factory mode please
    You do not have permission to view this gallery.
    This gallery has 1 photos.

    Leave a comment:


  • Valdemaras
    replied
    Originally posted by waletogo View Post
    at left is my download folder , you can see that is no dgtks files when i wan to select it in tool
    In what mode is your phone when you are trying to select/flash board software?

    Leave a comment:


  • waletogo
    replied
    at left is my download folder , you can see that is no dgtks files when i wan to select it in tool
    You do not have permission to view this gallery.
    This gallery has 2 photos.

    Leave a comment:


  • Valdemaras
    replied
    Originally posted by waletogo View Post
    Dc phoenix can't detected dgtks files solution please
    Please send a screenshot with the problem visible.

    Leave a comment:


  • waletogo
    replied
    Dc phoenix can't detected dgtks files solution please
    Last edited by waletogo; 2023-01-25, 05:05 PM.

    Leave a comment:


  • Valdemaras
    replied
    Originally posted by SHARIFF100 View Post

    hisuite Not installed on my pc and device on device manager existing,
    but still problem "Fatal error: Cannot access to device

    Fatal error: Cannot access to device

    Cannot access to device
    17/09/2022 14:53:02 Writing device finished - INCOMPLETE​"
    That's even worse then, means problem most likely in drivers. You should uninstall current ones, install hisuite, and make sure to change its settings so that it won't launch upon device connection. , then connect phone directly to pc port on pc, do not use any hubs and repeat flashing.

    Leave a comment:


  • SHARIFF100
    replied
    Originally posted by Valdemaras View Post
    Please monitor the device in the device manager on a computer if it exists there and make sure no hisuite is running or launches in the background during this process, it must be closed at all times.
    hisuite Not installed on my pc and device on device manager existing,
    but still problem "Fatal error: Cannot access to device

    Fatal error: Cannot access to device

    Cannot access to device
    17/09/2022 14:53:02 Writing device finished - INCOMPLETE​"

    Leave a comment:


  • Valdemaras
    replied
    Please monitor the device in the device manager on a computer if it exists there and make sure no hisuite is running or launches in the background during this process, it must be closed at all times.

    Leave a comment:

Working...
X