Originally posted by alak dey
View Post
Unconfigured Ad Widget
Collapse
Announcement
Collapse
No announcement yet.
DC-Phoenix
Collapse
This is a sticky topic.
X
X
-
which firmware i use for recover BLL-L22 i dont found any BLL-L22 firmware in support area.
i find this thread in gsmhosting http://forum.gsmhosting.com/vbb/f102.../#post13265474
but which file used can someone advice me.
Leave a comment:
-
Originally posted by hafiz4saqib View PostI have also issue from PRA-LA1
Its stuck on EMUI circle logo after incomplete firmware and also now it wont go in fastboot mode.
Screenshot_41.png
Screenshot_43.png
Is this EMMC fault or some thing else? Even I can`t find Board software of this model for repair it via test point.
Screenshot_45.png
Leave a comment:
-
I have also issue from PRA-LA1
Its stuck on EMUI circle logo after incomplete firmware and also now it wont go in fastboot mode.
Screenshot_41.png
Screenshot_43.png
Is this EMMC fault or some thing else? Even I can`t find Board software of this model for repair it via test point.
Screenshot_45.pngLast edited by hafiz4saqib; 2018-08-10, 02:22 AM.
Leave a comment:
-
Huawei Mate 10 Pro DC Phoenix log:
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: AQH7N18109002288
2018/08/10 01:08:57 Starting extracting partitions from file UPDATE.APP
Current version: BLA_Global_C999
Cannot create extract directory: E:\DC_Phoenix_v57\tmp\20180810_010857_UPDATE\
Extract files to directory: E:\DC_Phoenix_v57\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: HHEE OK
Extracting partition: FASTBOOT OK
Extracting partition: VECTOR OK
Extracting partition: VBMETA OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: MODEMNVM_CUST OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: KERNEL OK
Extracting partition: RAMDISK OK
Extracting partition: RECOVERY_RAMDISK OK
Extracting partition: RECOVERY_VENDOR OK
Extracting partition: RECOVERY_VBMETA OK
Extracting partition: ERECOVERY_KERNEL OK
Extracting partition: ERECOVERY_RAMDISK OK
Extracting partition: ERECOVERY_VENDOR OK
Extracting partition: ERECOVERY_VBMETA OK
Extracting partition: HDCP OK
Extracting partition: DTS OK
Extracting partition: DTO OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: ISP_FIRMWARE OK
Extracting partition: MODEM_FW OK
Extracting partition: HISEE_IMG OK
Extracting partition: HISEE_FS OK
Extracting partition: ODM OK
2018/08/10 01:10:59 Extracting partitions finished OK
2018/08/10 01:10:59 Starting to write device in FASTBOOT mode...
Device found: AQH7N18109002288
IMEI: 868389032033571
Build number: :BLA-L29 8.0.0.145(C432)
Product model: BLA-L29
Device not supported
In previous firmware versions, everything was OK. On version 145 is the first time the error occurs. Please fix, because I paid for nothing... This is totally abnormal! I sent my phone to service repair!
Leave a comment:
-
Originally posted by Mumtaz View PostPlease, Help me.
I upgraded My Honor 8 (FRD-L09C432) to unapproved Oreo update. After that the phone is working 2 days, but after a restart the phone just boot to eRecovery and nothing more. Fastboot, eRecovery and Recovery accessable, but system won't boot anymore.
I buyed a 3 day licence to DC-Phoenix + HCU. After try to flash the rom (what i downloaded from DC-Unlock database) just failed to flash. Many "FAILED" messages appeared in log, and phone won't reboot to upgrade mode. The screen after reboot leave blank and LED flashing sometimes in green. If I check the phone in fastboot ('fastboot devices'), the phone is appear. 'fastboot restart' command is restart the phone to fastboot mode. Some reboots later on the screen the 'Honor' logo showing and phone boot to eRecovery.
TWRP installed, before the restart.
So this is the phone status:
Bootloader locked
FRP locked
Android version: 8.0.0.521
How do i rollback or flash a working rom? What rom is working?
Here is the DC-Phoenix log:
"
"
This is, what I'm see if I want to flash the Oreo. And after that the phone is "rebooting", but I don't see anything and DC-Phoenix cant find the phone in upgrade mode.
If I want to use the method 2, the log is:
"
Leave a comment:
-
Originally posted by manager77 View PostLooking for a device in force upgrade mode
No devices detected in force upgrade mode
Looking for a device in fastboot mode
Device found: 0123456789ABCDEF
8/4/2018 11:42:43 PM Starting to write device in FASTBOOT mode...
File to update: ALP-AL00A-BD_1.0.0.48_Board_Software_China_Nonspecific_Andro id_8.0.0_EMUI_8.0.0_05022DUL.dgtks
Device found: 0123456789ABCDEF
Cannot get IMEI from device
Build number: :System 8.0.0.38(018L)
Product model:
Device not supported
this is what l get when l am trying to flash board softare....my phone is ALP L29 and for mate 10 you have only one board software
You told me yesterday on chat that's ok flashing this one
May l know for what l've paid 19 euro...
Leave a comment:
-
tried 100 times....DEVICE NOT SUPORTED!!
l want a refund because it.s not normal to pay for something wich doesnt work with my phone...take care!
Leave a comment:
-
Please, Help me.
I upgraded My Honor 8 (FRD-L09C432) to unapproved Oreo update. After that the phone is working 2 days, but after a restart the phone just boot to eRecovery and nothing more. Fastboot, eRecovery and Recovery accessable, but system won't boot anymore.
I buyed a 3 day licence to DC-Phoenix + HCU. After try to flash the rom (what i downloaded from DC-Unlock database) just failed to flash. Many "FAILED" messages appeared in log, and phone won't reboot to upgrade mode. The screen after reboot leave blank and LED flashing sometimes in green. If I check the phone in fastboot ('fastboot devices'), the phone is appear. 'fastboot restart' command is restart the phone to fastboot mode. Some reboots later on the screen the 'Honor' logo showing and phone boot to eRecovery.
TWRP installed, before the restart.
So this is the phone status:
Bootloader locked
FRP locked
Android version: 8.0.0.521
How do i rollback or flash a working rom? What rom is working?
Here is the DC-Phoenix log:
"
2018.08.05. 14:51:14 Starting to write device in FASTBOOT mode...
Device found: XXXXXXXXXXXXXXXXXX
IMEI: XXXXXXXXXXXXXXXXXXXXX
Build number: :FRD-L09 8.0.0.521(C432)
Product model: FRD-L09
Extracting partition XLOADER...
Preparing file to write...
Writing XLOADER partition with file XLOADER
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Extracting partition XLOADER...
Preparing file to write...
Writing XLOADER partition with file XLOADER
XLOADER partition UPDATE ...OK
Extracting partition FW_LPM3...
Preparing file to write...
Writing FW_LPM3 partition with file FW_LPM3
FW_LPM3 partition UPDATE ...OK
Extracting partition FASTBOOT...
Preparing file to write...
Writing FASTBOOT partition with file FASTBOOT
FASTBOOT partition UPDATE ...OK
Extracting partition MODEMNVM_UPDATE...
Preparing file to write...
Writing MODEMNVM_UPDATE partition with file MODEMNVM_UPDATE
MODEMNVM_UPDATE partition UPDATE ...OK
Extracting partition TEEOS...
Preparing file to write...
Writing TEEOS partition with file TEEOS
TEEOS partition UPDATE ...FAILED
Extracting partition TRUSTFIRMWARE...
Preparing file to write...
Writing TRUSTFIRMWARE partition with file TRUSTFIRMWARE
TRUSTFIRMWARE partition UPDATE ...FAILED
Extracting partition SENSORHUB...
Preparing file to write...
Writing SENSORHUB partition with file SENSORHUB
SENSORHUB partition UPDATE ...FAILED
Extracting partition FW_HIFI...
Preparing file to write...
Writing FW_HIFI partition with file FW_HIFI
FW_HIFI partition UPDATE ...FAILED
Extracting partition BOOT...
Preparing file to write...
Writing BOOT partition with file BOOT
BOOT partition UPDATE ...FAILED
Extracting partition RECOVERY...
Preparing file to write...
Writing RECOVERY partition with file RECOVERY
RECOVERY partition UPDATE ...FAILED
Extracting partition RECOVERY2...
Preparing file to write...
Writing RECOVERY2 partition with file RECOVERY2
RECOVERY2 partition UPDATE ...FAILED
Extracting partition DTS...
Preparing file to write...
Writing DTS partition with file DTS
DTS partition UPDATE ...FAILED
Extracting partition MODEM...
Preparing file to write...
Writing MODEM partition with file MODEM
MODEM partition UPDATE ...OK
Extracting partition MODEM_DSP...
Preparing file to write...
Writing MODEM_DSP partition with file MODEM_DSP
MODEM_DSP partition UPDATE ...OK
Extracting partition 3RDMODEM...
Preparing file to write...
Writing 3RDMODEM partition with file 3RDMODEM
3RDMODEM partition UPDATE ...OK
Extracting partition CACHE...
Preparing file to write...
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file CACHE
CACHE partition UPDATE ...FAILED
Extracting partition SYSTEM...
Preparing file to write...
Writing SYSTEM partition with file SYSTEM
SYSTEM partition UPDATE ...OK
Extracting partition MODEM_DTB...
Preparing file to write...
Writing MODEM_DTB partition with file MODEM_DTB
MODEM_DTB partition UPDATE ...OK
Extracting partition USERDATA...
Preparing file to write...
Erasing USERDATA partition
Partition USERDATA erased
Writing USERDATA partition with file USERDATA
USERDATA partition UPDATE ...OK
Software written
2018.08.05. 14:55:54 Writing device finished - INCOMPLETE
Waiting for fastboot device...
Device found: XXXXXXXXXXXXXXXXXXXXX
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
This is, what I'm see if I want to flash the Oreo. And after that the phone is "rebooting", but I don't see anything and DC-Phoenix cant find the phone in upgrade mode.
If I want to use the method 2, the log is:
"Looking for a device in upgrade mode
COM4: DBAdapter Reserved Interface (COM4)
COM5: Android Adapter PCUI (COM5)
Update file FRD-EMUI5.0_HL1FRDL09M303_Board Software_inc_testpoint SKIPPED because was not detected any device in fastboot mode
2018.08.05. 15:58:14 Starting to write device in UPGRADE mode...
File to update: FRD-L09_C432B389_Firmware_United_Kingdom_Nonspecific_A ndroid7.0_EMUI5.0.APP
Validating file...
Looking for attached port...
Preparing to write...
Writing partition: SHA256RSA...OK
Writing partition: CRC...OK
Writing partition: CURVER...OK
Writing partition: VERLIST...
Error downloading file FRD-L09_C432B389_Firmware_United_Kingdom_Nonspecific_A ndroid7.0_EMUI5.0_3.dtwork, partition: VERLIST
Error writing software
2018.08.05. 15:58:38 Starting to write device in UPGRADE mode...
File to update: update_FRD-L09_C432B389_hw_eu.APP
Validating file...
Looking for attached port...
Preparing to write...
Device does not support this update file
Error writing software
2018.08.05. 15:59:00 Writing device finished with ERRORLast edited by Mumtaz; 2018-08-05, 03:06 PM.
Leave a comment:
-
Looking for a device in force upgrade mode
No devices detected in force upgrade mode
Looking for a device in fastboot mode
Device found: 0123456789ABCDEF
8/4/2018 11:42:43 PM Starting to write device in FASTBOOT mode...
File to update: ALP-AL00A-BD_1.0.0.48_Board_Software_China_Nonspecific_Andro id_8.0.0_EMUI_8.0.0_05022DUL.dgtks
Device found: 0123456789ABCDEF
Cannot get IMEI from device
Build number: :System 8.0.0.38(018L)
Product model:
Device not supported
this is what l get when l am trying to flash board softare....my phone is ALP L29 and for mate 10 you have only one board software
You told me yesterday on chat that's ok flashing this one
May l know for what l've paid 19 euro...
Leave a comment:
-
Originally posted by holgadom View Post
I do the testpoint but the cell phone does not turn on, it is completely dead
DC-Phoenix :
Looking for a device in force upgrade mode
No devices detected in force upgrade mode
Looking for a device in fastboot mode
No devices detected in fastboot mode
No device detected to update
Leave a comment:
-
Originally posted by Valdemaras View Post
Please paste here info from dc-phoenix when flashing board software via testpoints.
I do the testpoint but the cell phone does not turn on, it is completely dead
DC-Phoenix :
Looking for a device in force upgrade mode
No devices detected in force upgrade mode
Looking for a device in fastboot mode
No devices detected in fastboot mode
No device detected to updateLast edited by holgadom; 2018-08-02, 09:20 PM.
Leave a comment:
-
Originally posted by holgadom View Post
Method 3 did not work, the phone is still dead, what can I do? some solution, because I lost the cell phone and the license I bought: /
Leave a comment:
Leave a comment: