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 Mehmetdalgic View Post
    How much credit do I need to add new software to the Brick phone?
    Sorry do not understand the question, price list here https://www.dc-unlocker.com/buy/user_prices maybe it will help.

    Leave a comment:


  • Mehmetdalgic
    replied
    How much credit do I need to add new software to the Brick phone?

    Leave a comment:


  • Valdemaras
    replied
    Originally posted by dom009 View Post
    Hello, I try to connect to DC-Phoenix but he tells me that the password is wrong. I try to connect with my word dôasse dc. What should I do?
    DO not quite fully understand, make sure you are not trying to log in with your forum account.

    Leave a comment:


  • dom009
    replied
    Hello, I try to connect to DC-Phoenix but he tells me that the password is wrong. I try to connect with my word dôasse dc. What should I do?

    Leave a comment:


  • Valdemaras
    replied
    Originally posted by eugene93 View Post
    hi after install board software and follow the step for mate 9.. my phone bricked again when follow step 8..flash full stock rom..

    Step 8

    Connect phone to PC in fastboot & rescue mode. Set flash mode to "Standard", select full stock rom files matching mobile's data (Model/ country/ vendor with new security version - R1, R3 Android 8, Android 9 etc.). Put check mark on "Rescue Recovery" and if mobile has Kirin659 or Kirin960 cpu check "Old algo" box too and press "Update"

    Which only means that you've flashed incorrect firmware.

    Leave a comment:


  • eugene93
    replied
    hi after install board software and follow the step for mate 9.. my phone bricked again when follow step 8..flash full stock rom..

    Step 8

    Connect phone to PC in fastboot & rescue mode. Set flash mode to "Standard", select full stock rom files matching mobile's data (Model/ country/ vendor with new security version - R1, R3 Android 8, Android 9 etc.). Put check mark on "Rescue Recovery" and if mobile has Kirin659 or Kirin960 cpu check "Old algo" box too and press "Update"


    Leave a comment:


  • Valdemaras
    replied
    Your only hope is method 3.

    Leave a comment:


  • satfan
    replied
    Hi, I tried now 2 different files to update my Honor 8 FRD-L09
    It comes back with diffrent errors. pls help:

    Code:
    07.11.2019 11:11:12 start to write update file
    File to update: D:\Daten-16\Coffee Maker\Downloads\FRD-L09_C432B389_Firmware_United_Kingdom_Nonspecific_Android7.0_EMUI5.0.APP
    
    Process identifier:20191120
    
    Validating file...
    Looking for attached port...
    Preparing to write...
    
    Extracting partition SHA256RSA...
    Writing partition: SHA256RSA...OK
    
    Extracting partition CRC...
    Writing partition: CRC...OK
    
    Extracting partition CURVER...
    Writing partition: CURVER...OK
    
    Extracting partition VERLIST...
    Writing partition: VERLIST...OK
    
    Extracting partition PACKAGE_TYPE...
    Writing partition: PACKAGE_TYPE...OK
    
    Extracting partition EFI...
    Writing partition: EFI...OK
    
    Extracting partition XLOADER...
    Writing partition: XLOADER...OK
    
    Extracting partition FW_LPM3...
    Writing partition: FW_LPM3...OK
    
    Extracting partition FASTBOOT...
    Writing partition: FASTBOOT...OK
    
    Extracting partition MODEMNVM_UPDATE...
    Writing partition: MODEMNVM_UPDATE...OK
    
    Extracting partition TEEOS...
    Writing partition: TEEOS...OK
    
    Extracting partition TRUSTFIRMWARE...
    Writing partition: TRUSTFIRMWARE...OK
    
    Extracting partition SENSORHUB...
    Writing partition: SENSORHUB...OK
    
    Extracting partition FW_HIFI...
    Writing partition: FW_HIFI...OK
    
    Extracting partition BOOT...
    Writing partition: BOOT...
    
    Trying update again(2)
    
    Exception: Access violation at address 0040B326 in module 'DCPhoenix_v118(1).exe'. Read of address C0000118
    Error downloading file FRD-L09_C432B389_Firmware_United_Kingdom_Nonspecific_Android7.0_EMUI5.0_14.dtwork, partition: BOOT
    
    
    Error writing software
    07.11.2019 11:11:45 Writing device finished with ERROR
    ************************************************** ************************************
    with the stock rom I found the following happend ...
    ************************************************** ***********************************

    Model: FRD-L09
    Vendor/Country: Vendor/Country: hw/eu
    Battery state: 1577mv
    OEM lock state info:
    FB LockState: LOCKED
    USER LockState: UNLOCKED
    OEM get bootinfo:
    unlocked


    Process identifier:20193293

    Getting build number...
    Getting base version...
    Getting cust version...
    Getting preload version...

    Erasing ver .. .
    Cannot get FBlock info from device
    Trying to unlock device...

    Signing process may take few minutes

    Trying to get data from server
    Waiting in queue for signing service. Expected time 1 second(s) to get data from server

    Trying to get data from server
    Unlock process finished successfully


    Erasing ver .. .
    File size: 3.386.459.760 bytes
    Current version(CURVER): FRDC432B001
    Writing rescue_recovery partition
    RESCUE_RECOVERY partition update ...OK

    USB Device REMOVAL
    Type: @oem15.inf,%singlebootloaderinterface%;Android Bootloader Interface
    VidPid: VID_18D1&PID_D00D
    Instance id: 73QDU17124002604

    Looking for device in upgrade mode...

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

    COM11: DBAdapter Reserved Interface (COM11)
    COM12: Android Adapter PCUI (COM12)

    07.11.2019 11:55:08 Starting to write device in UPGRADE mode...
    Device found: 73QDU17124002604


    Old slow algo NOT selected

    07.11.2019 11:55:11 start to write update file
    File to update: D:\Daten-16\Coffee Maker\Downloads\update(8)\UPDATE.APP
    File size: 3.386.459.760 bytes
    Current version(CURVER): FRDC432B001

    Process identifier:20193329

    Validating file...
    Looking for attached port...
    Preparing to write...
    Writing file 1 of 23: SHA256RSA...OK
    Writing file 2 of 23: CRC...OK
    Writing file 3 of 23: CURVER...OK
    Writing file 4 of 23: VERLIST...OK
    Writing file 5 of 23: EFI...OK
    Writing file 6 of 23: XLOADER...OK
    Writing file 7 of 23: FW_LPM3...OK
    Writing file 8 of 23: FASTBOOT...

    Trying update again(2)

    Exception: Access violation at address 0040B326 in module 'DCPhoenix_v118(1).exe'. Read of address C0000118
    Error downloading file 8 of 23


    Error writing software
    07.11.2019 11:55:26 Writing device finished with ERROR
    hope 4 help ... thx
    Last edited by satfan; 2019-11-07, 11:15 AM.

    Leave a comment:


  • Valdemaras
    replied
    Connecting to server problem now fixed.

    Leave a comment:


  • kiptr4s
    replied
    hi.. what happen with the server? i cant access the server after login...
    time continues to decrease from 72 hours..please fix the server sir..
    my username :herdi93

    Leave a comment:


  • eugene93
    replied
    hi same here.. cannot connect to server.
    i bought the 3 days timed license.
    Username : eu6gene
    thanks

    Leave a comment:


  • invisix
    replied
    I cannot connect to server. 72 hours license purchased. Any problem with the server? My username: invisix

    Leave a comment:


  • akaygsm
    replied
    Originally posted by Valdemaras View Post

    If device does not enter fastboot mode then no. Otherwise it may just be driver problem, hard to tell from this, you should monitor device manager.
    TKS
    in device manager device is
    Qualcomm HS-USB QDLoader 9008 (com71)

    and it stays the same when phoenix tries to get it in fastboot
    i install oll need driver from support
    Android_phone_Qualcomm_Drivers_1.03.04.11
    Huawei drivers testpoint
    Huawei_Android_phone_drivers

    Leave a comment:


  • Valdemaras
    replied
    Originally posted by akaygsm View Post
    hy, i have a problem with one Y550-L01.
    flash tp error

    DC Phoenix 0.0.0.115
    user:akaygsm

    Looking for a device in force upgrade mode

    Device detected:
    COM71: Qualcomm HS-USB QDLoader 9008 (COM71)
    23.10.2019 11:51:38 Starting to write device in FORCE UPGRADE mode...
    File to update: Y550-L01_V100R001C00B258_Board Software_inc_testpoint.dgtks

    Device detected:
    COM71: Qualcomm HS-USB QDLoader 9008 (COM71)

    Process identifier:19772399

    Writing MPRG...OK...
    Writing BOOTLOADER...OK...

    Waiting for fastboot device...

    USB Device REMOVAL
    Type: @oem166.inf,%qcomdevice90080%;Qualcomm HS-USB QDLoader 9008
    VidPid: VID_05C6&PID_9008
    Instance id: 6&1cc1c4e3&0&2


    USB Device INSERTION
    Type: @oem166.inf,%qcomdevice90080%;Qualcomm HS-USB QDLoader 9008
    VidPid: VID_05C6&PID_9008
    Instance id: 6&1cc1c4e3&0&2


    Error detecting device in fastboot mode
    23.10.2019 11:52:29 Writing device finished OK

    is sollution from this error?
    tks.
    akaygsm
    If device does not enter fastboot mode then no. Otherwise it may just be driver problem, hard to tell from this, you should monitor device manager.

    Leave a comment:


  • akaygsm
    replied
    hy, i have a problem with one Y550-L01.
    flash tp error

    DC Phoenix 0.0.0.115
    user:akaygsm

    Looking for a device in force upgrade mode

    Device detected:
    COM71: Qualcomm HS-USB QDLoader 9008 (COM71)
    23.10.2019 11:51:38 Starting to write device in FORCE UPGRADE mode...
    File to update: Y550-L01_V100R001C00B258_Board Software_inc_testpoint.dgtks

    Device detected:
    COM71: Qualcomm HS-USB QDLoader 9008 (COM71)

    Process identifier:19772399

    Writing MPRG...OK...
    Writing BOOTLOADER...OK...

    Waiting for fastboot device...

    USB Device REMOVAL
    Type: @oem166.inf,%qcomdevice90080%;Qualcomm HS-USB QDLoader 9008
    VidPid: VID_05C6&PID_9008
    Instance id: 6&1cc1c4e3&0&2


    USB Device INSERTION
    Type: @oem166.inf,%qcomdevice90080%;Qualcomm HS-USB QDLoader 9008
    VidPid: VID_05C6&PID_9008
    Instance id: 6&1cc1c4e3&0&2


    Error detecting device in fastboot mode
    23.10.2019 11:52:29 Writing device finished OK

    is sollution from this error?
    tks.
    akaygsm

    Leave a comment:

Working...
X