DC-Phoenix

[Nymos]

License doesn't start until you successfully log in on software. Please provide your public IP address as well to check the problem.

another thing. my phone is on Emui 11 android 10, can i still use testpoint software service? thx

[Nymos]

License doesn't start until you successfully log in on software. Please provide your public IP address as well to check the problem.

i sent a request of refund because you did not helped me in time, accept it. bye

[Valdemaras]

Look at our work hours before posting something with an expectation of reply. Refund is available, but due to changes in policy by PayPal regarding refunds, taxes are applied. If you see no use in those remaining credits we can do a refund, but you should be aware that refunded amount will be less than you paid because of these changes. Please let me know your decision.

[dpavlenok]

Привет,
DC версия Phoenix: 0.0.0.164
Телефон: Huawei P9
Модель: EVA-L19.
I am updating the firmware from Fdroid 6 emui 4.1.1 to android 8 emui 5.

Extracting recovery partition

Extracting partition: RECOVERY
RECOVERY partition extracted

17.08.2021 23:55:22 Starting to try Rescue Recovery...


Looking for a device in fastboot mode
Device found: XVV7N17905000249


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

SN:XVV7N17905000249
IMEI:868445025393586
IMEI1:868445025396290
Build number: :EVA-L19C10B190
Model: EVA-L19
Vendor/Country: hw/ru
Battery state: 3834mv
OEM lock state info:
FB LockState: LOCKED
USER LockState: LOCKED
OEM get bootinfo:
locked


Process identifier:32700208


Erasing ver .. .
Getting lock state info...
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 .. .
Writing rescue_recovery partition
RESCUE_RECOVERY partition update ...OK
Update recovery parttion OK

USB Device REMOVAL
Type: @oem19.inf,%hwfastboot%;Android Sooner Single ADB Interface
VidPid: VID_18D1&PID_D00D
Instance id: XVV7N17905000249
Looking for device in upgrade mode...

USB Device INSERTION
Type: @oem23.inf,%busfilter.devicedesc%;USB Composite Device
VidPid: VID_12D1&PID_107E
Instance id: XVV7N17905000249
COM3: DBAdapter Reserved Interface (COM3)
COM5: Android Adapter PCUI (COM5)
Enter recovery mode OK

17.08.2021 23:56:25 Starting to write device in UPGRADE mode...

Old slow algo NOT selected

17.08.2021 23:56:26 start to write update file
File to update: C:\Users\Anna\Downloads\EVA-L19_C10B389_Firmware_Russian_Federation_Belarus_Mo ngolia_Nonspecific_Android_7.0_EMUI_5.0.APP

Process identifier:32700233

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 CURVER...
Writing partition: CURVER...OK

Extracting partition VERLIST...
Writing partition: VERLIST...OK

Extracting partition PACKAGE_TYPE...
Procesing .. ..
Error downloading file EVA-L19_C10B389_Firmware_Russian_Federation_Belarus_Mo ngolia_Nonspecific_Android_7.0_EMUI_5.0_4.dtwork, partition: PACKAGE_TYPE

Error writing software
17.08.2021 23:56:50 Writing device finished with ERROR



What am I doing wrong?

[Valdemaras]

Problem is forcing incorrect version of firmware onto one that runs in mobile. Probably build too high as it should go incrementally as developer intended.

[tek3195]

Is there a way to recover BAH-W09 from USB_DIAGNOSTICS 9006 mode? Or test point ?

[Valdemaras]

Is there a way to recover BAH-W09 from USB_DIAGNOSTICS 9006 mode? Or test point ?

Sadly but no, we do not support flashing this device in neither testpoint or 9006 diagnostics port https://www.dc-unlocker.com/supportedmodelsdcpx.php

[SHARIFF100]

DC Phoenix 0.0.0.131
user: PROTECTED


Standard update
Not Reboot NOT cheked
Update Verlist to server on file load NOT checked
Try Rescue Recovery NOT checked
Bypass version check NOT checked
Old slow algo NOT checked

Looking for a device in force upgrade mode
Device detected:
COM3: HUAWEI USB COM 1.0 (COM3)
17/09/2022 14:46:02 Starting to write device in FASTBOOT mode...
File to update: D:\PROTECTED\ANE-BD_1.0.0.39_Board_Software_Android_8.0_EMUI_8.0_05 022JKP.dgtks
Device detected:
COM3: HUAWEI USB COM 1.0 (COM3)

Process identifier:50896204


Writing bootloader...
Step 1...
Step 2...

Waiting for device REMOVAL/INSERTION...

USB Device REMOVAL
Type: @oem51.inf,%qcomdevice00%;HUAWEI USB COM 1.0
VidPid: VID_12D1&PID_3609
Instance id: 5&de3b74c&0&2


USB Device INSERTION
Type: @oem24.inf,%hwfastboot%;Android Sooner Single ADB Interface
VidPid: VID_18D1&PID_D00D
Instance id: 5&de3b74c&0&2


Waiting for fastboot device...
Device found: 9WVDU19328004387


Looking for a device in fastboot mode
Device found: 9WVDU19328004387


Getting IMEI...
Getting build number...
Getting model ...
Getting battery state...
Getting backdoor info...
Getting lock state info...
Getting lock boot info...

SN:9WVDU19328004XXX
IMEI:861819048251XXX
IMEI1:861819048287XXX
MEID:00000000000000
Build number: :ANE-LX1 9.1.0.401(C432E13R1P7)
Model: ANE-LX1
Vendor/Country: hw/eu
Battery state: 0
OEM lock state info:
FB LockState: UNLOCKED
USER LockState: LOCKED
OEM get bootinfo:
unlocked


Erasing ver .. .
Waiting for answer...
Getting lock state info...
Getting backdoor info...

Erasing ver .. .

Erasing nvme partition
ERASE partition nvme : FAIL erase one of the oeminfo and nve items failed!

Erasing cust partition
ERASE partition cust : FAIL failed to erase partition

Erasing product partition
ERASE partition product : FAIL failed to erase partition

Erasing version partition
ERASE partition version : FAIL failed to erase partition

Erasing misc partition
ERASE partition misc : FAIL failed to erase partition
Erasing userdata partition
ERASE partition userdata : FAIL failed to erase partition

Writing xloader partition
XLOADER partition update ...OK

Writing ptable partition
PTABLE partition update ...OK

Writing fastboot partition
FASTBOOT partition update ...OK

Writing dts partition
DTS partition update ...OK

Writing fw_lpm3 partition
FW_LPM3 partition update ...OK

Writing sensorhub partition
SENSORHUB partition update ...OK

Writing fw_hifi partition
FW_HIFI partition update ...OK

Writing teeos partition
TEEOS partition update ...OK

Writing recovery_vbmeta partition
RECOVERY_VBMETA partition update ...OK

Erasing cache partition
Partition cache erased
Writing cache partition
CACHE partition update ...OK

Writing nvme partition
NVME partition update ...OK

Writing trustfirmware partition
TRUSTFIRMWARE partition update ...OK

Writing modem_fw partition
MODEM_FW partition update ...OK

Writing modemnvm_update partition
MODEMNVM_UPDATE partition update ...OK

Writing modem_om partition
MODEM_OM partition update ...OK

Writing modemnvm_img partition
MODEMNVM_IMG partition update ...OK

Erasing userdata partition
Partition userdata erased
Writing userdata partition
USERDATA partition update ...OK

Writing system partition
sending sparse file 413714128 bytes
Waiting for answer...
send sparse file OK
sending sparse file 471379936 bytes
Waiting for answer...
send sparse file OK
sending sparse file 463200008 bytes
Waiting for answer...
send sparse file OK
sending sparse file 77705316 bytes
Waiting for answer...
send sparse file OK
SYSTEM partition update ...OK
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

[Valdemaras]

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.

[SHARIFF100]

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"

[Valdemaras]

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.

[waletogo]

Dc phoenix can't detected dgtks files solution please

[Valdemaras]

Dc phoenix can't detected dgtks files solution please

Please send a screenshot with the problem visible.

[waletogo]

at left is my download folder , you can see that is no dgtks files when i wan to select it in tool

[Valdemaras]

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?