cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
dar_k
Blue Screen Again
Posts: 1
Registered: ‎09-11-2013
Location: Ukraine
Views: 26,119
Message 1 of 9

Lenovo K900 k900 firmware problem

Hi
If you try to flash the device has received an error.
Log:

Spoiler

09/11/13 14:44:32.549 DEBUG : Removing disconnected device

09/11/13 14:44:32.549 DEBUG : Port 0/0/2 #0: FlashManager::do_new_soc_device on port 2

09/11/13 14:44:32.549 DEBUG : Port 0/0/2 #0: Start XFSTK thread for device 69DAC9820587A2CB with status 0

09/11/13 14:44:32.549 DEBUG : Port 0/0/2 #0: New device detected - SN : 69DAC9820587A2CB

09/11/13 14:44:32.550 DEBUG : Flash ifwi with GPFlag 0x80000045

09/11/13 14:44:32.550 DEBUG : IFWI flash started for device 69DAC9820587A2CB (Ср 11. сен 14:44:32 2013)

09/11/13 14:44:32.551 INFO : Port 0/0/2 #0: IFW flash started - SN : 69DAC9820587A2CB

09/11/13 14:44:32.551 INFO : Disabling xFSTK wipe out ifwi option

09/11/13 14:44:32.551 INFO : Disabling xFSTK Misc DnX

09/11/13 14:44:32.551 DEBUG : XFSTK Downloader API 1.3.6

Copyright (c) 2012 Intel Corporation

09/11/13 14:44:32.551 DEBUG : fwdnx -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_FwDnx.bin

09/11/13 14:44:32.551 DEBUG : fwimage -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin

09/11/13 14:44:32.551 DEBUG : osdnx -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_OsDnx.bin

09/11/13 14:44:32.551 DEBUG : osimage -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/pos.bin

09/11/13 14:44:32.551 DEBUG : gpflags -- 0x80000045

09/11/13 14:44:32.551 DEBUG : usbsn -- 69DAC9820587A2CB

09/11/13 14:44:32.551 DEBUG : softfuse -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/signed_soft_key_CLAK.bin

09/11/13 14:44:32.551 DEBUG : XFSTK SN: 69DAC9820587A2C B -- Initiating download...

09/11/13 14:44:32.551 DEBUG : XFSTK SN: 69DAC9820587A2C B -- Attemp 1 times to start download ...

09/11/13 14:44:32.551 DEBUG : New SOC device -> serial: 69DAC9820587A2CB port: 2

09/11/13 14:44:32.752 DEBUG : XFSTK SN: 69DAC9820587A2C B -- Starting downloading thread...

09/11/13 14:44:32.757 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusDownloader:Smiley FrustratedetDevice

09/11/13 14:44:32.757 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusDownloader::UpdateTarget

09/11/13 14:44:32.757 DEBUG : XFSTK-LOG--USBSN:--FWDnxPath -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_FwDnx.bin

09/11/13 14:44:32.757 DEBUG : XFSTK-LOG--USBSN:--FWImagePath -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin

09/11/13 14:44:32.757 DEBUG : XFSTK-LOG--USBSN:--SoftfusesPath -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/signed_soft_key_CLAK.bin

09/11/13 14:44:32.757 DEBUG : XFSTK-LOG--USBSN:--OSDnxPath -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_OsDnx.bin

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--OSImagePath -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/pos.bin

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--MiscDnxPath --

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--Gpflags -- 80000045

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--DebugLevel -- ffffffff

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--UsbDelay ms -- 1

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--TransferType -- USB

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--WipeIFWI -- False

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--Idrq -- False

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--Verbose -- True

09/11/13 14:44:32.758 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusDownloader::Init

09/11/13 14:44:32.759 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusWdUsb20Device:Smiley Surprisedpen

09/11/13 14:44:32.759 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusUtils:Smiley FrustratedetUsbsn

09/11/13 14:44:32.759 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB USB Device found - USBSN: 69DAC9820587A2CB Address:2

09/11/13 14:44:32.759 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusDownloader::do_update

09/11/13 14:44:32.759 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState:Smiley Frustratedtart

09/11/13 14:44:32.759 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB Sending DnER...

09/11/13 14:44:32.760 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::WriteOutPipe DnER

09/11/13 14:44:32.760 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::WriteOutPipe 1

09/11/13 14:44:32.761 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::Write --->DnER

09/11/13 14:44:32.761 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::GetOpCode

09/11/13 14:44:32.761 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::ReadInAck

09/11/13 14:44:32.762 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::GetAck

09/11/13 14:44:32.764 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::GetAck - DFRM(0x4)

09/11/13 14:44:32.764 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB FW: Handle virgin part DnX ...

09/11/13 14:44:32.764 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::GetOpCode

09/11/13 14:44:32.764 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB Changing to DLDR_STATE_FW_NORMAL ...

09/11/13 14:44:32.765 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusFW::InitNoSize

09/11/13 14:44:32.765 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusFW::CheckFile

09/11/13 14:44:32.765 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusFW::CheckFile

09/11/13 14:44:32.766 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_FwDnx.bin size:99296 bytes

09/11/13 14:44:32.767 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_FwDnx.bin size:99296 bytes

09/11/13 14:44:32.767 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusFW::InitFwImage

09/11/13 14:44:32.768 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin size:2031420 bytes

09/11/13 14:44:32.768 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB allocating buffers for FW images...

09/11/13 14:44:32.775 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin size:2031420 bytes

09/11/13 14:44:32.775 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB allocating buffers for primary/secondary security FW images...

09/11/13 14:44:32.775 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB loading buffers for FW images...

09/11/13 14:44:32.776 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB loading buffers for primary/secondary security FW images...

09/11/13 14:44:32.778 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB loading buffers for FUPH...

09/11/13 14:44:32.778 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 69DAC9820587A2CB FW download is in progress ...

09/11/13 14:44:32.778 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState:Smiley FrustratedtartFw

09/11/13 14:44:32.778 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CLVP Total number of calculated steps : 30.000000

09/11/13 14:44:32.778 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB sending 6 DWORDS of DnxFW size and checksum...

09/11/13 14:44:32.778 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::WriteOutPipe àƒ

09/11/13 14:44:32.778 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::WriteOutPipe 1

09/11/13 14:44:32.779 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::Write --->àƒ

09/11/13 14:44:32.779 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB End of StHandleFwNormal

09/11/13 14:44:32.779 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::GetOpCode

09/11/13 14:44:32.779 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::ReadInAck

09/11/13 14:44:32.780 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::GetAck

09/11/13 14:44:32.780 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::GetAck - DXBL(0x4)

09/11/13 14:44:32.780 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB FW: Sending DnX ...

09/11/13 14:44:32.780 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::FwDXBL

09/11/13 14:44:32.780 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB Sending FW Dnx data...76d11b0

09/11/13 14:44:32.780 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::WriteOutPipe __BINARY__

09/11/13 14:44:32.780 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::WriteOutPipe 1

09/11/13 14:44:32.781 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::Write --->__BINARY__

09/11/13 14:44:32.787 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::LogProgress

09/11/13 14:44:32.787 INFO : Port 0/0/2 #0: XFSTK-PROGRESS SN: 69DAC9820587A2CB 3

09/11/13 14:44:32.787 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::GetOpCode

09/11/13 14:44:32.787 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB Changing to DLDR_STATE_SOFT_FUSES ...

09/11/13 14:44:32.787 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB softfusesFW::InitNoSize

09/11/13 14:44:32.787 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB softfusesFW::CheckFile

09/11/13 14:44:32.788 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB softfusesFW::InitSoftfusesBin

09/11/13 14:44:32.788 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/signed_soft_key_CLAK.bin size:880 bytes

09/11/13 14:44:32.788 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/signed_soft_key_CLAK.bin size:880 bytes

09/11/13 14:44:32.789 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/signed_soft_key_CLAK.bin size:880 bytes

09/11/13 14:44:32.789 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 69DAC9820587A2CB Soft fusing is in progress ...

09/11/13 14:44:32.789 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/signed_soft_key_CLAK.bin size:880 bytes

09/11/13 14:44:32.789 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB End of StHandleSoftfuses

09/11/13 14:44:32.789 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::GetOpCode

09/11/13 14:44:32.789 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB ClvpDldrState::ReadInAck

09/11/13 14:44:32.790 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::GetAck

09/11/13 14:44:32.873 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::GetAck - ER29(0x4)

09/11/13 14:44:32.873 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 69DAC9820587A2CB Unknown Ack code:0, aborting ...

09/11/13 14:44:32.874 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusDownloader::do_abort

09/11/13 14:44:32.874 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusWdUsb20Device::Abort

09/11/13 14:44:32.874 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin size:2031420 bytes

09/11/13 14:44:32.874 DEBUG : Port 0/0/2 #0: XFSTK-LOG SN: 69DAC9820587A2CB CloverviewPlusDownloader::GetStatus

09/11/13 14:44:36.195 DEBUG : Port 0/0/2 #0: SOC Device is disconnected - state:1 - status - Flashing IFWI

09/11/13 14:44:36.196 DEBUG : SOC device lost on port 2

09/11/13 14:44:42.976 DEBUG : XFSTK SN: 69DAC9820587A2C B -- Attemp 2 times to start download ...

...

09/11/13 14:44:50.977 DEBUG : XFSTK SN: 69DAC9820587A2C B--FW/OS download timeout aborting...

09/11/13 14:44:50.977 DEBUG : XFSTK SN: 69DAC9820587A2C B -- Download operation encountered errors.

09/11/13 14:44:50.977 DEBUG : XFSTK SN: 69DAC9820587A2C B -- Please verify fw/os image integrity and reprovision target.

09/11/13 14:44:50.977 WARNING: Port 0/0/2 #0: Retry IFW Flashing - Serial: 69DAC9820587A2CB

09/11/13 14:44:50.977 DEBUG : XFSTK Downloader API 1.3.6

Copyright (c) 2012 Intel Corporation

09/11/13 14:44:50.977 DEBUG : fwdnx -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_FwDnx.bin

09/11/13 14:44:50.977 DEBUG : fwimage -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin

09/11/13 14:44:50.977 DEBUG : osdnx -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_OsDnx.bin

09/11/13 14:44:50.977 DEBUG : osimage -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/pos.bin

09/11/13 14:44:50.977 DEBUG : gpflags -- 0x80000045

09/11/13 14:44:50.977 DEBUG : usbsn -- 69DAC9820587A2CB

09/11/13 14:44:50.977 DEBUG : softfuse -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/signed_soft_key_CLAK.bin

09/11/13 14:44:50.977 DEBUG : XFSTK SN: 69DAC9820587A2C B -- Interface is not available...

09/11/13 14:44:51.977 WARNING: Port 0/0/2 #0: Retry IFW Flashing - Serial: 69DAC9820587A2CB

09/11/13 14:44:51.977 DEBUG : XFSTK Downloader API 1.3.6

Copyright (c) 2012 Intel Corporation

09/11/13 14:44:51.977 DEBUG : fwdnx -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_FwDnx.bin

09/11/13 14:44:51.977 DEBUG : fwimage -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin

09/11/13 14:44:51.977 DEBUG : osdnx -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0318_LE_DVT3_PVT_2G_B1_OsDnx.bin

09/11/13 14:44:51.977 DEBUG : osimage -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/pos.bin

09/11/13 14:44:51.977 DEBUG : gpflags -- 0x80000045

09/11/13 14:44:51.977 DEBUG : usbsn -- 69DAC9820587A2CB

09/11/13 14:44:51.977 DEBUG : softfuse -- D:/K900_cn_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/K900_ROW_1_S_2_009_0081_130620_DVT3_CPUsign_full/signed_soft_key_CLAK.bin

09/11/13 14:44:51.978 DEBUG : XFSTK SN: 69DAC9820587A2C B -- Interface is not available...

09/11/13 14:44:52.978 ERROR : Port 0/0/2 #0: IFW flash failed - SN : 69DAC9820587A2CB

 

Help to solve the problems and the K900 back to life.

akshaysagar
HDMI
Posts: 175
Registered: ‎12-07-2013
Location: IN
Views: 24,827
Message 2 of 9

Re: Lenovo K900 k900 firmware problem

Can it still be connected to PC via data cable and in mass storage anyway mass storage doesn't matter much I just want to know that the system still detect it or not if yes there's a way to revive it
-----------------------------------------------------------------------------------------------------
Devices : K900, A7000, VIBE SHOT, VIBE S1, VIBE S1 lite, VIBE X3, VIBE X3 lite(A7010), A6600 plus, VIBE C2, VIBE P2
Sanan
Fanfold Paper
Posts: 1
Registered: ‎01-06-2014
Location: Baku
Views: 24,729
Message 3 of 9

Re: Lenovo K900 k900 firmware problem

Hi 

I also have problem like this ! planning set up K900_ROW_1_S_2_009_0131_130727 but stop and now smartphone not working!! please help me

leonelhs
Blue Screen Again
Posts: 6
Registered: ‎03-06-2014
Location: mexico
Views: 24,289
Message 4 of 9

Re: Lenovo K900 k900 firmware problem

Please somebody help me I have similar problem, I bought a Chinise K900 an I tried to install a row rom K900_ROW_1_S_2_009_0047_130603.inb  and after reboot the cellphone don't boot anymore. I made some changes to build.props in order to trick the system and let me install the row rom, as result my device is dead, neither I cant enter to recovery mode

leonelhs
Blue Screen Again
Posts: 6
Registered: ‎03-06-2014
Location: mexico
Views: 24,235
Message 5 of 9

Re: Lenovo K900 k900 firmware problem

Ufff, already I have unbricked my Lenovo K900, I have to do many steps nevertheless I cant write a standard method, so I'm posting what did works for me...

 

Don panic the cellphone appears to be dead but in fact its alive...

 

1) try to find some rom whit the firmware files: 

 

FW_DNX : CLAK_FwDnX_CLVP_20.24.bin
IFWI : CLAK_IFWI_CLVP_vF9.54_ww19_001_SOS.bin
OS_DNX : CLAK_OsDnX_CLVP_20.24.bin
OS IMAGE : pos.bin

 

You can find these files inside these roms just google it:

K900_ROW_0708_RootedByMouz.rar

K900_1_S_2_019_0142_130927_DVT3_CPsign.tar

 

2) Download and install the Intel®USB Driver for Android Devices at:

 http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices

You must pretty shure all the drivers are installed correctly be patient and wait for Windows finish install all the drivers. 

 

3)Download and install the xFSTK at:

https://dl.dropboxusercontent.com/u/26833962/K900%20Tools/xFSTK%2Bv1.3.6.rar

 

4) Uncompress the rom an load the firmware files FW_DNX, IFWI, OS_DNX, OS IMAGE. This is the most important step whit the device plugged and turn off, press Begin download in xFSTK, the tool will start to find the device, immediately just press and hold on the power button + volume up, the K900 wake up for 3 seconds just to be catch for the xFSTK.

 

5) At this point it supposed we should have an android fastboot device, but didn't works for me at my Windows so I had to change an plug my device into my Mac, that not means Win will not work whit others, we can do a test whit the command "fastboot devices"  it should printout out cloverfield... device.

 

6) So whit fastboot mode, we can proceed to flash the files from the uncompresed rom:     

fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase factory
fastboot erase logs
fastboot erase cache
fastboot erase config
fastboot erase data
fastboot erase spare
fastboot erase system
fastboot oem stop_partitioning
fastboot flash system system.img.gz
fastboot oem checksum
fastboot flash radio radio_firmware_6360.bin
fastboot flash /tmp/NV_130119.tlv NV_130119.tlv
fastboot flash splashscreen rocket_start_logo-1080,480-2.bmp.stitched.signed.bin
fastboot oem nvm apply /tmp/NV_130119.tlv
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.bin

 

7)If everything results ok, just reboot the device:
fastboot reboot

 

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

* Alternative method  *

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

 

There is another tool MFT

https://dl.dropboxusercontent.com/u/26833962/K900%20Tools/ManufacturingFlashTool_Setup_6.0.2.exe

 

This tool just need load the file flash-DVT3-CPU-sign.xml from the uncompressed rom, I didn't test but it should be the same procedure, the matter is the 3 seconds to catch the Android device.

 

There is a video: https://www.youtube.com/watch?v=BhvA_T694kw I don't understand what he said but its pretty graphical.

 

 

Excuseme my bad english.    

 

 

ilterkilinc
Paper Tape
Posts: 1
Registered: ‎07-17-2014
Views: 21,942
Message 6 of 9

Re: Lenovo K900 k900 firmware problem

hi leonel. I tried your method. but computer didnt see my phone. 

ı dont know what is my phone problem ?

when ı am seeing video on the internet. suddenly my phone shot down and ıt dıdnt work agaın. I lıve ın Turkey, lenovo phone's service doesnt exist here. What should ı do ? helpp me.

thanks .

leonelhs
Blue Screen Again
Posts: 6
Registered: ‎03-06-2014
Location: mexico
Views: 21,935
Message 7 of 9

Re: Lenovo K900 k900 firmware problem

well I cant help you because you don say to mouch at your post

hasbi23
Paper Tape
Posts: 1
Registered: ‎08-01-2014
Views: 21,592
Message 8 of 9

Re: Lenovo K900 k900 firmware problem

hi Leonel,

 

I have problem with K900 that it's died after i update Firmware from Lenovo (official update). 

firts of all, my K900 success with the update but after 2 hour my K900 stuck then bootloop by itself, i tried to turn it off but when i tried to turn it on back, my K900 wouldn't ON and still OFF. i tried to charge (may be low batt) but after 2 hour charges it's same as befor, my phone still off.

 

i want to flash it but how it come while my K900 doesnt detect on my Computer.

 

any suggest for me??

 

sorry for my bad english... Smiley Happy

 

Greetings from Indonesia.

BRENDAWANJALA
Paper Tape
Posts: 1
Registered: ‎12-25-2016
Location: KE
Views: 8,011
Message 9 of 9

LENOVO K900 WENT OFF AND WILL NOT POWER ON NOR CHARGE AFTER INSTALLING FACE BOOK MESSENGER POP UP

I WAS ON MY FACEBOOK PAGE AND I SAW THAT I HAD A MESSAGE. TRIED TO READ THE MESSANGE BUT WAS INSTRUCTED TO INSTALL FACEBOOK MESSENGER FIRST. AFTER CLIKING INSTAL MY LENOVO K900 FROZE AND THEN WENT OFF.I HAVE TRIED TO RESTART BUT IS SEEMS TO HAVE DIED.CANT POWER ON.I HAVE TRIED TO PRESS THE POWER ON AND VOLUME UP BATTONS ALL TOGETHER BUT STILL NO SIGN OF LIFE.IT DOES NOT INDICATE ANY SIGN THAT IT IS CHARGING.

 

I GUESE IT IS AVIRUS.WHAT SHOULD I DO TO GET MY PHONE BACK?

AM IN KENYA(AFRICA).LENOVO K900 PHONES ARE NOT SOLD HERE.THIS ONE WAS BOUGHT ABROAD.

 

PLEASE ADVISE/HELP

Check out current deals!


Shop current deals

Top Kudoed Authors