Originally posted by AleksandrVZ
View Post
Unconfigured Ad Widget
Collapse
Announcement
Collapse
No announcement yet.
DC-Phoenix
Collapse
This is a sticky topic.
X
X
-
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: X9LDU14A07000012
05.11.2018 6:34:50 Starting extracting partitions from file UPDATE.APP
Current version: H60-L04V100R001C900B500
Cannot create extract directory: D:\H60-L04\DC-Phoenix_v63\tmp\20181105_063451_UPDATE\
Extract files to directory: D:\H60-L04\DC-Phoenix_v63\
Extracting partition: PTABLE OK
Extracting partition: XLOADER OK
Extracting partition: FASTBOOT OK
Extracting partition: FW_LPM3 OK
Extracting partition: FW_HIFI OK
Extracting partition: TEEOS OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: SENSORHUB OK
Extracting partition: DTS OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: CUST OK
Extracting partition: SYSTEM OK
Extracting partition: CACHE OK
Extracting partition: USERDATA OK
05.11.2018 6:36:23 Extracting partitions finished OK
05.11.2018 6:36:23 Starting to write device in FASTBOOT mode...
Device found: X9LDU14A07000012
SN: 9LDU14A07000012
Build number: H60-L04C900B521
Product model: H60-L04
Batery state: 3612mv
Writing PTABLE partition with file D:\H60-L04\DC-Phoenix_v63\PTABLE.img
PTABLE partition UPDATE ...FAILED
Writing PTABLE partition with file D:\H60-L04\DC-Phoenix_v63\PTABLE.img
PTABLE partition UPDATE ...FAILED
Writing XLOADER partition with file D:\H60-L04\DC-Phoenix_v63\XLOADER.img
XLOADER partition UPDATE ...FAILED
Writing FASTBOOT partition with file D:\H60-L04\DC-Phoenix_v63\FASTBOOT.img
FASTBOOT partition UPDATE ...FAILED
Writing FW_LPM3 partition with file D:\H60-L04\DC-Phoenix_v63\FW_LPM3.img
FW_LPM3 partition UPDATE ...FAILED
Writing FW_HIFI partition with file D:\H60-L04\DC-Phoenix_v63\FW_HIFI.img
FW_HIFI partition UPDATE ...FAILED
Writing TEEOS partition with file D:\H60-L04\DC-Phoenix_v63\TEEOS.img
TEEOS partition UPDATE ...FAILED
Writing BOOT partition with file D:\H60-L04\DC-Phoenix_v63\BOOT.img
BOOT partition UPDATE ...FAILED
Writing RECOVERY partition with file D:\H60-L04\DC-Phoenix_v63\RECOVERY.img
RECOVERY partition UPDATE ...FAILED
Writing SENSORHUB partition with file D:\H60-L04\DC-Phoenix_v63\SENSORHUB.img
SENSORHUB partition UPDATE ...FAILED
Writing DTS partition with file D:\H60-L04\DC-Phoenix_v63\DTS.img
DTS partition UPDATE ...FAILED
Writing MODEMNVM_UPDATE partition with file D:\H60-L04\DC-Phoenix_v63\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...FAILED
Writing MODEM partition with file D:\H60-L04\DC-Phoenix_v63\MODEM.img
MODEM partition UPDATE ...FAILED
Writing MODEM_DSP partition with file D:\H60-L04\DC-Phoenix_v63\MODEM_DSP.img
MODEM_DSP partition UPDATE ...FAILED
Writing 3RDMODEM partition with file D:\H60-L04\DC-Phoenix_v63\3RDMODEM.img
3RDMODEM partition UPDATE ...FAILED
Erasing CUST partition
ERASE partition CUST ...FAILED
Writing CUST partition with file D:\H60-L04\DC-Phoenix_v63\CUST.img
CUST partition UPDATE ...FAILED
Writing SYSTEM partition with file D:\H60-L04\DC-Phoenix_v63\SYSTEM.img
SYSTEM partition UPDATE ...FAILED
Erasing CACHE partition
ERASE partition CACHE ...FAILED
Writing CACHE partition with file D:\H60-L04\DC-Phoenix_v63\CACHE.img
CACHE partition UPDATE ...FAILED
Erasing USERDATA partition
ERASE partition USERDATA ...FAILED
Writing USERDATA partition with file D:\H60-L04\DC-Phoenix_v63\USERDATA.img
USERDATA partition UPDATE ...FAILED
Update fastboot mode failed
05.11.2018 6:41:24 Writing device finished - INCOMPLETE
What does this log mean? same log with any firmware. i tried to flash H60-L04C900B521 in this log.Last edited by piarman; 2018-11-05, 04:12 AM.
Leave a comment:
-
2018/11/5 11:03:10 Starting to write device in FASTBOOT mode...
File to update: STFAL00S001046_Board Software_general_Android 7.0_EMUI5.1_05022CLB.dgtks
Device detected:
COM3: HUAWEI USB COM 1.0 (COM3)
Writing bootloader...
Writing STFAL00S001046_Board Software_general_Android 7.0_EMUI5.1_05022CLB_3.dtwork...
Error writing Bootloader
The phone cann't into bootloader. screen and Indicator light cann't bright,even if it connection usb. how can i do? TAT
Leave a comment:
-
1. There is a bug with last and all previous DC Phoenix versions regarding "Not erase/write nvm" and "Not erase oeminfo" checkboxes. They do not have any effect unless you check/uncheck them and choose some ANOTHER board software file, NOT THE SAME you had before in the field. If you won't re-choose the file, they won't have any effect either.
2. There is a HUGE problem with 3G networks at least with RNE-, CHM-, NEM- and some other phones. After you restore NV partitions backup, 3G networks would became totally broken. I replaced eMMC with all three forementioned phones and there were no 3G networks at all! While playing with some other NV backups I somehow managed to revive 3G on RNE- phone, but still unable to do that with CHM and NEM. Hardware of the phones is safw and sound, the only problem was dead eMMCs. So there's a big deal about it and we need you to check the procedure and tell us how to repair 3G networks after loosing original NVM partitions.
Leave a comment:
-
Yes, it work, unbricked with test point flash.. but lost imei, . enable Manufacture mode repair with HCU client not work. please assite.
New IMEI 1 : 8662150304*****
New IMEI 2 : 8662150304******
New SN : UDN0217A17********
New Vendor : all
New Country : cn
New Model : ALP-TL00
2018-11-02 21:01:59.853 Connecting to server...
2018-11-02 21:02:00.294 Connected!
2018-11-02 21:02:00.309 Open COM port COM10 (Android Adapter PCUI (COM10))...
2018-11-02 21:02:01.268 ERROR!
Insufficient credits!
- Likes 1
Leave a comment:
-
good day!
1.Is the device flashing and how many credits do you need for a regular firmware?
2.Try pressing yes, I will not spoil the device with the appropriate firmware, if I click!
Attached FilesLast edited by AleksandrVZ; 2018-11-02, 04:32 PM.
Leave a comment:
-
Nar1624...you have to disconnect battery first...usb cable must be connected to your phone and not to pc..hold touched testpoint and metal and connect usb cable to pc...wait 2,3 sec until in pc device manager it shows at com ports: Huawei USB COM 1....release the testpoint..done
- Likes 1
Leave a comment:
-
does not work,I connect USB with phone off/charging, hold Vol- down then ground testpoint, we get a boot to fastboot but I'm not seeing COM port. still in fastboot mode.
Leave a comment:
-
Nar1624...you need testpoint to get Huawei usb com 1...after that you have to flash last boardsoftware 1.0.0.58 from dc phoenix download and flash your phone...
- Likes 1
Leave a comment:
-
Kenchanfr...try with google to find ASC-Driver_Handset WinDriver 2.01.00.00.exe
Leave a comment:
-
I cannot flash my device. Please assist.
DC Phoenix username:::: sfc8818
Huawei mate 10 ALP-TL00
Bootloader relocked, FRP locked
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: 0123456789ABCDEF
10/09/2018 23:34:40 Starting to write device in FASTBOOT mode...
Device found: 0123456789ABCDEF
IMEI: 866215030422106
Build number: :System 8.0.0.38(00KH)
Product model:
Extracting partition XLOADER...
Preparing file to write...
Writing XLOADER partition with file XLOADER
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Cannot get HW FBlock info from device
Extracting partition XLOADER...
Preparing file to write...
Writing XLOADER partition with file XLOADER
XLOADER partition UPDATE ...FAILED
Extracting partition FW_LPM3...
Preparing file to write...
Writing FW_LPM3 partition with file FW_LPM3
FW_LPM3 partition UPDATE ...FAILED
Extracting partition HHEE...
Preparing file to write...
Leave a comment:
-
Originally posted by kenchanfr View PostDevice: Mate 10 Pro
Enter Phone Model:BLA-L29(C636)
Version number: BLA-L29 8.0.0.143 (C636patch01)
Security Patch Level: 2018/08/01 Androld Program Security Patch Level
Use the program (HWOTA8_Mate10) to lower the Firmware as follows:
From the original system BLA-L29C636B143-SP1 (8.0.0.143)
Reduced to BLA-L29C636B128 (8.0.0.128)
After rebooting, the result turns into a black brick. It can't be turned on and cannot be charged, but the computer can find the phone, and the device administrator appears USB SER.
Can this be solved?
thank
Leave a comment:
-
Originally posted by Samiral View PostSorry my english (google translate)
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: QMU7N18130000430
20.10.2018 9:22:53 Starting to write device in FASTBOOT mode...
Device found: QMU7N18130000430
Cannot get IMEI from device
Build number: :ALP-LGRP2-OVS 9.0.0.108(log)
Product model: ALP-L29
Batery state: 5650mv
Device not supported
Since the phone model is not supported, is it possible to refund the money spent on loans (the name Samiral1)?
Leave a comment:
Leave a comment: