FlyCaptainHuaweiResurrector all versions flash error - GSM-Forum

MimiTena · 01-17-2021, 14:07

I have Huawei KII-L05 with android 5, I want to flash with android 6 rom. I download from support KII-L05_C654B350_Firmware_Canada_Rogers_Communications _Inc._Android6.0.1_EMUI4.0.2.cfs firmware but i get error on flashing.

FlyCaptainHuaweiResurrector_v53 Logs

Code:

 Fly Captain Huawei Resurrector 0.0.0.53
user:29xxxxx


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

Looking for a device in upgrade mode
COM214: Android Adapter PCUI (COM214)

17/01/2021 15:24:23 Starting to write device in UPGRADE mode...
No devices detected in fastboot mode
Old slow algo NOT selected

17/01/2021 15:24:24 start to write update file
File to update: C:\Users\One\Desktop\KII-L05_C654B350_Firmware_Canada_Rogers_Communications_Inc._Android6.0.1_EMUI4.0.2.cfs
17/01/2021 15:24:26 Writing device finished with ERROR
Fly Captain Huawei Resurrector 0.0.0.53

fastboot mode

Code:

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

Looking for a device in upgrade mode
No devices detected in upgrade mode
Device found: fd91e8e

Extracting recovery partition

Extracting partition: RECOVERY
RECOVERY partition extracted

Extracting partition: ERECOVERY
ERECOVERY partition extracted

17/01/2021 15:27:04 Starting to try Rescue Recovery...

Looking for a device in fastboot mode
Device found: fd91e8e

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

SN:2WMDU17607003359
Build number: KII-L05C654B130
Model: HUAWEI KII-L05
battery is present
OEM lock state info:
FB LockState: LOCKED
widevine LockState: LOCKED
OEM get bootinfo:
*******************************************

Bootloader Lock State: LOCKED

Root State: UNROOT

Bootloader WidevineKey: WidevineKey_VALID
System State: OK
Bootloader Version: 001.001.000

*******************************************

Process identifier:5470550

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
Unlock process finished successfully

Erasing ver .. .
Writing rescue_recovery partition
RESCUE_RECOVERY partition update ...OK
Uptade recovery parttion OK

USB Device REMOVAL
Type: @oem141.inf,%hwfastboot%;Android Sooner Single ADB Interface
VidPid: VID_18D1&PID_D00D
Instance id: 6&6f1b3ab&0&1

Looking for device in upgrade mode...

USB Device INSERTION
Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device
VidPid: VID_12D1&PID_1035
Instance id: 6&6f1b3ab&0&1

COM214: Android Adapter PCUI (COM214)
Enter recovery mode OK

17/01/2021 15:28:42 Starting to write device in UPGRADE mode...
No devices detected in fastboot mode
Old slow algo NOT selected

17/01/2021 15:28:44 start to write update file
File to update: C:\Users\One\Desktop\KII-L05_C654B350_Firmware_Canada_Rogers_Communications_Inc._Android6.0.1_EMUI4.0.2.cfs
17/01/2021 15:28:45 Writing device finished with ERROR

FlyCaptainHuaweiResurrector_v73 Logs

Code:

Fly Captain Huawei Resurrector 0.0.0.73
user:29xxxxx

Looking for a device in upgrade mode
COM214: Android Adapter PCUI (COM214)

Standard update
Not Reboot NOT checkked
Update Verlist to server on file load NOT checked
Enable testpoint NOT checked
Disable testpoint NOT checked
Try Rescue Recovery checked
Bypass version check NOT checked
Old slow algo NOT checked
Force OTA NOT checked


17/01/2021 15:11:27 Starting to write device in UPGRADE mode...


17/01/2021 15:11:28 start to write update file
File to update: C:\Users\One\Desktop\KII-L05_C654B350_Firmware_Canada_Rogers_Communications_Inc._Android6.0.1_EMUI4.0.2.cfs

We recommend to repeat the update from fastboot mode with Version check bypass and rescue recovery options checked

17/01/2021 15:11:32 Writing device finished with ERROR

Fastboot mode

Code:

Looking for a device in upgrade mode
No devices detected in upgrade mode
Device found: fd91e8e

Standard update
Not Reboot NOT checkked
Update Verlist to server on file load NOT checked
Enable testpoint NOT checked
Disable testpoint NOT checked
Try Rescue Recovery checked
Bypass version check checked
Old slow algo NOT checked
Force OTA NOT checked

Extracting recovery partition

Extracting partition: RECOVERY
RECOVERY partition extracted

Extracting partition: ERECOVERY
ERECOVERY partition extracted

17/01/2021 15:48:28 Starting to try Rescue Recovery...

Looking for a device in fastboot mode
Device found: fd91e8e

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

SN:2WMDU17607003359
Build number: KII-L05C654B130
Model: HUAWEI KII-L05
battery is present
OEM lock state info:
FB LockState: LOCKED
widevine LockState: LOCKED
OEM get bootinfo:
*******************************************

Bootloader Lock State: LOCKED

Root State: UNROOT

Bootloader WidevineKey: WidevineKey_VALID
System State: OK
Bootloader Version: 001.001.000

*******************************************

Process identifier:5470575

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 2 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
Uptade recovery parttion OK

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

USB Device INSERTION
Type: @usb.inf,%usb\composite.devicedesc%;USB Composite Device
VidPid: VID_12D1&PID_1035
Instance id: 6&6f1b3ab&0&1
COM214: Android Adapter PCUI (COM214)
Enter recovery mode OK

USB Device REMOVAL
Type: @oem5.inf,%vcom_da%;MediaTek DA USB VCOM (Android)
VidPid: VID_0E8D&PID_2001
Instance id: 6&6f1b3ab&0&2

USB Device INSERTION
Type: @oem5.inf,%vcom_preloader%;MediaTek PreLoader USB VCOM (Android)
VidPid: VID_0E8D&PID_2000
Instance id: 6&6f1b3ab&0&2

USB Device REMOVAL
Type: @oem5.inf,%vcom_preloader%;MediaTek PreLoader USB VCOM (Android)
VidPid: VID_0E8D&PID_2000
Instance id: 6&6f1b3ab&0&2

17/01/2021 15:51:50 Starting to write device in UPGRADE mode...

Old slow algo NOT selected

17/01/2021 15:51:50 start to write update file
File to update: C:\Users\One\Desktop\KII-L05_C654B350_Firmware_Canada_Rogers_Communications_Inc._Android6.0.1_EMUI4.0.2.cfs
17/01/2021 15:51:55 Writing device finished with ERROR

How to solve this error

**.:hack3r2k:.** · 01-18-2021, 12:02

Uncheck rescue recovery and retry flashing in fastboot

Br

MimiTena · 01-18-2021, 14:09

Quote:

Originally Posted by .:hack3r2k:.

Uncheck rescue recovery and retry flashing in fastboot

Br

Thank you, it working fine after uncheck rescue recovery

Mapamann · 01-18-2021, 15:50

Hmm,

I have the same problem.
But the error is still the same when i uncheck rescue recovery.
Is there anything else i can try?

**.:hack3r2k:.** · 01-19-2021, 14:01

Quote:

Originally Posted by Mapamann

Hmm,

I have the same problem.
But the error is still the same when i uncheck rescue recovery.
Is there anything else i can try?

Give details. which model, what the log etc tec

Br

01-18-2021, 12:02	#2 (permalink)
.:hack3r2k:. Product Manager Join Date: Aug 2002 Location: FuriouSTeaM Posts: 53,982 Member: 15022 Status: Offline Sonork: 100.53452 Thanks Meter: 61,572	Uncheck rescue recovery and retry flashing in fastboot Br

01-18-2021, 15:50	#4 (permalink)
Mapamann Freak Poster Join Date: Feb 2002 Location: Gemany Age: 41 Posts: 353 Member: 9493 Status: Offline Thanks Meter: 9	Hmm, I have the same problem. But the error is still the same when i uncheck rescue recovery. Is there anything else i can try?