Home  ›  Xfstk Does Not Continue to Os Asus Z00ad

Xfstk Does Not Continue to Os Asus Z00ad

Written By Thursday 13 October 2022 Add Comment Edit
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

[Guide] Recover Fastboot of bricked Zenfone 2 ze551ml/ze550ml

  • Thread starter Sumit007s
  • Start date
  • #121
Thanks everyone. This works for ze551ml.
Will list the process and where there are deviations so that it can help others.
What you need,
  1. iSocUSB-Driver-Setup-1.0.4 or install Intel flash tool, which comes with it. No need to disable windows security. Remember, I had problems, and I uninstalled Bitdefender for xfstk installation, and restarted sometimes.
  2. xfstk-downloader-setup-1.5.1, may show blank, or may not launch. Either it's bitdefender, or antivirus, or you may not have restarted pc after installation. Suggest, uninstall all antivirus and go with windows defender, and restart you pc a couple of times, and then the application will launch. Also run as admin to be safe.
  3. In xfstk GP flag override, use either 0x80000807 or 0x800000807(with extra 0), whichever works.
  4. xfstk can be used multiple times, if you fail in asus flash tool as well. This would bring you again to
  5. When stuck with result okay with asus flash tool after flash, do not i mean do not shutdown phone. Use volume up and down, and your phone with change and show right serial, and not abcdef... Force close asus tool, and launch again, while your phone is still on and connected. again volume up and down, and asus tool will detect the phone again, with correct serial this time. Now flash again.
  6. Highlighted deviations.
My phone is back from dead. and leaving phone to vibrate and restart does not drain battery, the process stops. So don't wait for battery to drain and fastboot, rather flash with xfstk.
  • #122
Hi everyone!!

I´ve tried everything but no success. Stucked in download OS (xFSTK Downloader).

My gadgets: Zenfone 2 ZE551 dead, no USB logo, no charger logo, just a black screen and vibrate sometimes.
I have instaled iSocUSB Driver, Intel Android Drivers, xFSTK ZE551 Downloader.

Using Window 10, when i press Power button + Volume Down it recognise a Moorefield Device.

I´ve tried to use 0x80000807 (4 zeros) and 0x800000807 (5 zeros) in xFSTK options (GP Flag Override Value). I even tried disconect and reconect battery.

I´ve tried over 100 times the xFSTK proccess but no success!!

See the log:

Please!! Can Anyone help me?

Thanks

Last edited:
  • #123
HELP

I'm having the same problem of eduardojunior, I still got the install part of raw, but gave problem and does not recognize usb after boot mini boot, only recognizes in Moorefield Device mode, has to delete this mini boot to restart the process zero?

  • #124
I solved the problem by calming myself, I put the cell phone to charge for 8 hours, I changed the USB cable for a more reliable one, and then I tried again, and on the third attempt it worked out, I even installed another custom rom :))))
Hi everyone!!

I´ve tried everything but no success. Stucked in download OS (xFSTK Downloader).

My gadgets: Zenfone 2 ZE551 dead, no USB logo, no charger logo, just a black screen and vibrate sometimes.
I have instaled iSocUSB Driver, Intel Android Drivers, xFSTK ZE551 Downloader.

Using Window 10, when i press Power button + Volume Down it recognise a Moorefield Device.

I´ve tried to use 0x80000807 (4 zeros) and 0x800000807 (5 zeros) in xFSTK options (GP Flag Override Value). I even tried disconect and reconect battery.

I´ve tried over 100 times the xFSTK proccess but no success!!

See the log:

xfstklog_ter_15._nov_16-59-45_2016.txt
16:59:09 - XFSTK Downloader API 1.7.0 Copyright (c) 2014 Intel Corporation
16:59:09 - fwdnx -- C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin
16:59:09 - fwimage -- C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin
16:59:09 - osdnx -- N/A
16:59:09 - osimage -- C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/droidboot_dnx.img.POS_sign.bin
16:59:09 - gpflags -- 0x80000807
16:59:09 - XFSTK-LOG--virtual bool MerrifieldDownloader::SetDevice(IGenericDevice*)
16:59:09 - Initiating download...
16:59:09 - XFSTK-LOG--virtual bool MerrifieldDownloader::UpdateTarget()
16:59:09 - XFSTK-LOG--FWDnxPath -- C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin
16:59:09 - XFSTK-LOG--FWImagePath -- C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin
16:59:09 - XFSTK-LOG--OSDnxPath -- N/A
16:59:09 - XFSTK-LOG--OSImagePath -- C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/droidboot_dnx.img.POS_sign.bin
16:59:09 - XFSTK-LOG--MiscDnxPath -- C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin
16:59:09 - XFSTK-LOG--MiscBinPath -- BLANK.bin
16:59:09 - XFSTK-LOG--Gpflags -- 80000807
16:59:09 - XFSTK-LOG--DebugLevel -- ffffffff
16:59:09 - XFSTK-LOG--UsbDelay ms -- 0
16:59:09 - XFSTK-LOG--TransferType -- USB
16:59:09 - XFSTK-LOG--WipeIFWI -- False
16:59:09 - XFSTK-LOG--Idrq -- False
16:59:09 - XFSTK-LOG--Verbose -- True
16:59:09 - XFSTK-LOG--void MerrifieldDownloader::Init()
16:59:09 - XFSTK-LOG--Open
16:59:09 - XFSTK-LOG--USB Device found - USBSN: B888FD4F68D3987F810F4703DE668BA8 Address:2
16:59:09 - XFSTK-LOG--void MerrifieldDownloader::do_update(MerrifieldOptions*)
16:59:09 - XFSTK-LOG--Start
16:59:09 - XFSTK-LOG--Sending DnER...
16:59:09 - XFSTK-LOG--WriteOutPipe DnER
16:59:09 - XFSTK-LOG--WriteOutPipe 0
16:59:09 - XFSTK-LOG--Write --->DnER
16:59:09 - XFSTK-LOG--GetOpCode
16:59:09 - XFSTK-LOG--ReadInAck
16:59:09 - XFSTK-LOG--GetAck - DxxM(4)
16:59:09 - XFSTK-LOG--Visit
16:59:09 - XFSTK-LOG--FW: Handle None virgin part DnX ...
16:59:09 - XFSTK-LOG--LogProgress
16:59:09 - XFSTK-LOG--GetOpCode
16:59:09 - XFSTK-LOG--Changing to DLDR_STATE_FW_MISC ...
16:59:09 - XFSTK-LOG--InitNoSize
16:59:09 - XFSTK-LOG--CheckFile
16:59:09 - XFSTK-LOG--CheckFile
16:59:09 - XFSTK-LOG--C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin size:110888 bytes
16:59:09 - XFSTK-LOG--C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/dnx_fwr.bin size:110888 bytes
16:59:09 - XFSTK-LOG--InitFwImage
16:59:09 - XFSTK-LOG--allocating buffers for FW images...
16:59:09 - XFSTK-LOG--C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
16:59:09 - XFSTK-LOG--C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
16:59:09 - XFSTK-LOG--allocating buffers for primary/secondary security FW images...
16:59:09 - XFSTK-LOG--loading buffers for FW images...
16:59:09 - XFSTK-LOG--loading buffers for FUPH...
16:59:09 - XFSTK-STATUS--FW(Miscdnx) download is in progress ...
16:59:09 - XFSTK-LOG--StartFw
16:59:09 - XFSTK-LOG--sending 6 DWORDS of DnxFW size and checksum...
16:59:09 - XFSTK-LOG--WriteOutPipe (±
16:59:09 - XFSTK-LOG--WriteOutPipe 0
16:59:09 - XFSTK-LOG--Write --->(±
16:59:09 - XFSTK-LOG--LogProgress
16:59:09 - XFSTK-LOG--End of MrfdStHandleFwMisc
16:59:09 - XFSTK-LOG--LogProgress
16:59:09 - XFSTK-LOG--GetOpCode
16:59:09 - XFSTK-LOG--ReadInAck
16:59:09 - XFSTK-LOG--GetAck - DCFI00(6)
16:59:09 - XFSTK-STATUS--FW: Sending DnX DCFI00 ...
16:59:09 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:09 - XFSTK-LOG--WriteOutPipe 0
16:59:09 - XFSTK-LOG--Write --->__BINARY__
16:59:09 - XFSTK-LOG--LogProgress
16:59:09 - XFSTK-LOG--GetOpCode
16:59:09 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - DXBL(4)
16:59:10 - XFSTK-LOG--FW: Sending DnX ...
16:59:10 - XFSTK-LOG--FwDXBL
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--Sending FW Dnx data...6dbd1a8
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - RUPHS(8)
16:59:10 - XFSTK-LOG--FW: Sending FW Update Profile Hdr Size...
16:59:10 - XFSTK-LOG--WriteOutPipe ¤
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->¤
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - RUPH(4)
16:59:10 - XFSTK-LOG--FW: Sending FW Update Profile Hdr...
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - DIFWI00(8)
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - DIFWI01(8)
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - DIFWI02(8)
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - DIFWI03(8)
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - DIFWI04(8)
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - DIFWI05(8)
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:10 - XFSTK-LOG--LogProgress
16:59:10 - XFSTK-LOG--GetOpCode
16:59:10 - XFSTK-LOG--ReadInAck
16:59:10 - XFSTK-LOG--GetAck - DIFWI06(8)
16:59:10 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:10 - XFSTK-LOG--WriteOutPipe 0
16:59:10 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI07(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI08(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI09(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI10(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI11(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI12(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI13(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI14(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI15(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI16(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI17(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI18(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI19(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:11 - XFSTK-LOG--LogProgress
16:59:11 - XFSTK-LOG--GetOpCode
16:59:11 - XFSTK-LOG--ReadInAck
16:59:11 - XFSTK-LOG--GetAck - DIFWI20(8)
16:59:11 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:11 - XFSTK-LOG--WriteOutPipe 0
16:59:11 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI21(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI22(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI23(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI24(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI25(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI26(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI27(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI28(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI29(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI30(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI31(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI00(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:12 - XFSTK-LOG--GetAck - DIFWI01(8)
16:59:12 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:12 - XFSTK-LOG--WriteOutPipe 0
16:59:12 - XFSTK-LOG--Write --->__BINARY__
16:59:12 - XFSTK-LOG--LogProgress
16:59:12 - XFSTK-LOG--GetOpCode
16:59:12 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI02(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI03(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI04(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI05(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI06(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI07(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI08(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI09(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI10(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI11(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI12(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI13(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI14(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:13 - XFSTK-LOG--GetAck - DIFWI15(8)
16:59:13 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:13 - XFSTK-LOG--WriteOutPipe 0
16:59:13 - XFSTK-LOG--Write --->__BINARY__
16:59:13 - XFSTK-LOG--LogProgress
16:59:13 - XFSTK-LOG--GetOpCode
16:59:13 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI16(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI17(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI18(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI19(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI20(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI21(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI22(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI23(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI24(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI25(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI26(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI27(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI28(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:14 - XFSTK-LOG--GetAck - DIFWI29(8)
16:59:14 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:14 - XFSTK-LOG--WriteOutPipe 0
16:59:14 - XFSTK-LOG--Write --->__BINARY__
16:59:14 - XFSTK-LOG--LogProgress
16:59:14 - XFSTK-LOG--GetOpCode
16:59:14 - XFSTK-LOG--ReadInAck
16:59:15 - XFSTK-LOG--GetAck - DIFWI30(8)
16:59:15 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:15 - XFSTK-LOG--WriteOutPipe 0
16:59:15 - XFSTK-LOG--Write --->__BINARY__
16:59:15 - XFSTK-LOG--LogProgress
16:59:15 - XFSTK-LOG--GetOpCode
16:59:15 - XFSTK-LOG--ReadInAck
16:59:15 - XFSTK-LOG--GetAck - DIFWI31(8)
16:59:15 - XFSTK-LOG--WriteOutPipe __BINARY__
16:59:15 - XFSTK-LOG--WriteOutPipe 0
16:59:15 - XFSTK-LOG--Write --->__BINARY__
16:59:15 - XFSTK-LOG--LogProgress
16:59:15 - XFSTK-LOG--GetOpCode
16:59:15 - XFSTK-LOG--ReadInAck
16:59:15 - XFSTK-LOG--GetAck - HLT$(4)
16:59:15 - XFSTK-LOG--FW: Firmware update completed...
16:59:15 - XFSTK-LOG--LogProgress
16:59:15 - XFSTK-LOG--LogProgress
16:59:15 - XFSTK-LOG--LogError
16:59:15 - XFSTK-STATUS--Error Code: 0 - Success
16:59:15 - XFSTK-LOG--void MerrifieldDownloader::do_abort()
16:59:15 - XFSTK-LOG--Abort
16:59:15 - XFSTK-LOG--C:/Users/junin_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
16:59:15 - XFSTK-STATUS--PASS
16:59:15 - XFSTK-STATUS--Firmware download completed. Continuing to OS...
16:59:25 - XFSTK-STATUS--Reconnecting to device - Attempt #1
16:59:26 - XFSTK-STATUS--Reconnecting to device - Attempt #2
16:59:27 - XFSTK-STATUS--Reconnecting to device - Attempt #3
16:59:28 - XFSTK-STATUS--Reconnecting to device - Attempt #4
16:59:29 - XFSTK-STATUS--Reconnecting to device - Attempt #5
16:59:30 - XFSTK-STATUS--Reconnecting to device - Attempt #6
16:59:31 - XFSTK-STATUS--Reconnecting to device - Attempt #7
16:59:32 - XFSTK-STATUS--Reconnecting to device - Attempt #8
16:59:33 - XFSTK-STATUS--Reconnecting to device - Attempt #9
16:59:34 - XFSTK-STATUS--Reconnecting to device - Attempt #10
16:59:35 - XFSTK-STATUS--Reconnecting to device - Attempt #11
16:59:36 - XFSTK-STATUS--Reconnecting to device - Attempt #12
16:59:37 - XFSTK-STATUS--Reconnecting to device - Attempt #13
16:59:38 - XFSTK-STATUS--Reconnecting to device - Attempt #14
16:59:39 - XFSTK-STATUS--Reconnecting to device - Attempt #15
16:59:40 - XFSTK-STATUS--Reconnecting to device - Attempt #16
16:59:41 - XFSTK-STATUS--Reconnecting to device - Attempt #17
16:59:42 - XFSTK-STATUS--Reconnecting to device - Attempt #18
16:59:43 - XFSTK-STATUS--Reconnecting to device - Attempt #19
16:59:44 - XFSTK-STATUS--Reconnecting to device - Attempt #20
16:59:45 - XFSTK-STATUS--Timeout to detect the device, make sure to charge up your phone before flashing

Please!! Can Anyone help me?

Thanks


I'm having the same problem of eduardojunior, I still got the install part of raw, but gave problem and does not recognize usb after boot mini boot, only recognizes in Moorefield Device mode, has to delete this mini boot to restart the process zero?
nikhilagarwal.005
  • #125
Xfstk Error

hey,
Everything i did step by step but,
while flashing files in xfstk it shows this Error,

Firmware downloading completed , Continuing to OS,
Reconnecting Device Attempt #1
" '' #2
.
.
'' '' #20
Timeout to Detect Device,make sure to charge up your phone before flashing

Note- I am not able to charge the phone as it is Bricked.
How to Fix this Error.?

  • #126
Put it in the charger, make sure the phone heats up a little, if it is, it will be charging even if it does not show anything on the screen or led
hey,
Everything i did step by step but,
while flashing files in xfstk it shows this Error,

Firmware downloading completed , Continuing to OS,
Reconnecting Device Attempt #1
" '' #2
.
.
'' '' #20
Timeout to Detect Device,make sure to charge up your phone before flashing

Note- I am not able to charge the phone as it is Bricked.
How to Fix this Error.?

nikhilagarwal.005
  • #127
Put it in the charger, make sure the phone heats up a little, if it is, it will be charging even if it does not show anything on the screen or led

Yup i flashed my Rom Successfully now i am facing another issue,

My issue is I flashed Droidboot.img and Recovery.img from the Update file downloaded from Asus Website now,

How to Get Lost Bootloader Back in Asus Zenphone 2 (ze550ml)
My System is working normally but Can't Enter Fastboot mod or Recovery Mod because lf flashing wrong Image.
1)In XFstk it shows Error while flashing OS
Reconnecting to device..... #1
.
.
Reconnecting Device...... #20
My phone battery is charged at 100% but I face this Error

2)XFstk shows FW Flashing Success, Continuing to OS
It boots up my phone.. And my System gets booted.
But unable to enter Fastboot Mod

How to Solve this Issue.!!

  • #128
"firmware download completed. continuing to os" my phone always disconnected when installing os image, how to fix that?

Sent from my Redmi Note 3 Pro using Tapatalk

  • #129
forum.php
Hi all.
My Zenfone was in cyanogen. I tried to return back Sock Rom.
But I have flash it with wrong firmware.
It wont boot anymore, and do not have fastboot, it just boot and reboot like in the picture.
I have try to follow your steps but I'have not succes to fix my problem.
Pleas help me if someone have solution to fix it.
broomer68
  • #130
forum.php
Hi all.
My Zenfone was in cyanogen. I tried to return back Sock Rom.
But I have flash it with wrong firmware.
It wont boot anymore, and do not have fastboot, it just boot and reboot like in the picture.
I have try to follow your steps but I'have not succes to fix my problem.
Pleas help me if someone have solution to fix it.
Just start with first message and follow every step.

Verstuurd vanaf mijn ASUS_Z00A met Tapatalk

  • #131
Whos on windows 10? Were u able to run the XFSTK app on ur laptop or desktop computer?
  • #132
Thanks guys, i'm backing up this guide just in case

Where's the guide? You can't call a guide when all you do is post download links, people who know less about this stuff don't know what to do with those links
joshg253
  • #133
Whos on windows 10? Were u able to run the XFSTK app on ur laptop or desktop computer?

xFSTK-Downloader is not working on my Windows 10 laptop, even after several reboots, troubleshooting compatibility, etc. :\

My ze551ml/z00ad currently has a mind of its own: seems to be rebooting itself every minute or so, doing two vibrations each time. Shows up as MOREFIELD with no driver, even after installing IntelAndroid and iSocUSB drivers. The screen nor any LEDs will light so I have no idea if it's even charging.

EDIT: you HAVE TO do the Disable Driver Enforcement thing before installing the SoC drivers. Then it'll actually give you some warnings when installing them, and once they are installed, xFSTK will launch!

Last edited:
Hnk1
  • #134
My experience which might be helpful to others in this situation
BEST VIDEO TUTORIAL

Hi there,
I also ended up with a bootloop when I decided to downgrade to Lollipop to unlock my bootloader. Mistake ? i did not flash droidimage(fastboot) as I was too sleepy to work on it with concentration.

I am mentioning most important things which are not mentioned in guide and in the video in detail.

All credits to the ones who worked it out.

SO ALWAYS WORK ON YOUR DEVICE WITH FULL CONCENTRATION.

First thing most people do not know is that you have to power off device and then HOLD VOLUME DOWN button so you can detect your device when you connect it to your PC.

Then you need to install the proper drivers and everything as shown in the video,

Once you flashed successfully, (again the volume down button while flashing using the xFSTK-Downloader) you will need ASUS FLASH TOOL and then flash the RAW firmware. THIS STEP IS MUST AS IT WILL REPAIR YOUR PARTITIONS

It will fail. Do not worry. If it gives any error. Simply do this trick

disconnect your device. (if device not detected. do this trick again)
close asus ftool
open asus ftool again
reconnect your device, DO NOT RESTART at all when you connect it again!

It may give errors many a times. Do not worry. Simply do the above trick again. Wait 20 minutes before you close asus if it is stuck on yellow label forever. and then reconnect device again. Eventually your serial will show instead of 0123456789ABCDEF.
this means now when you flash RAW image, you will boot up and your phone will be repaired without problems.

If you would not do the raw trick, you will not be able to flash recovery or droidimage via fastboot commands as your partitions are corrupt.

In case you are stuck, you can always use this commands to flash any other firmware you like. however, understand that i couldnot recover my device with these commands as i was not formating all my data. But RAW Image method via asus flash tool helped it to boot.

fastboot flash splashscreen splashscreen.img
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot

It is recommended to add these commands as well but it will format all your data. Else you would not boot.
fastboot format userdata
fastboot format cache
fastboot reboot

Good luck

Now only issue i have is that when I reboot my device, splash screen looks weird for a second (white lines) and if i boot into bootloader, i see boxes and lines (i know this is hardware driver issues and upgrading to latest MM again should fix it)

Last edited:
mrafin
  • #135
I m still stuck at 22%, anybody cn help me plz.... thx

I m still stuck at 22%, anybody cn help me plz.... thx

  • #136
Help!!!
My z008 is dead!!!

Ive tried this procedure, end up with

Firmware downloading completed , Continuing to OS,
Reconnecting Device Attempt #1
" '' #2
.
.
'' '' #20
Timeout to Detect Device,make sure to charge up your phone before flashing

Now, when I push the power button, nothing is happening. No buzz, no led, no flash, nothing. The same thing when I plug the charger. Its not charging, no heat, no battery splash. Nothing.
When I plug the usb to pc, sometimes it showing moorefield device on device manager. xFSTK showing device connected:0 , sometimes 1 or 2. Its blinking looks like a connection problem.

Is there anything I can do to safe my device? Any help would be apreciated.

  • #137
z008 bricked

hey guys i got my z008 bricked. when i use the xFSTK downloader, i get stuck "XFSTK-STATUS--Firmware download completed. Continuing to OS..." at this point my phone isn't detected anymore and the app attempts to reconnect in vain "08:39:19 - XFSTK-STATUS--Reconnecting to device - Attempt #20".
Charged my phone all noght and followed the procedue and even others similar to this one in vain ; I would need some help here guys.
I got nothing on phone, no vibration, no led, no hanging usb cable, no asus logo, just a black screen and device being detected as 'MOOREFIELD'

  • #138
Thanks everyone. This works for ze551ml.
Will list the process and where there are deviations so that it can help others.
What you need,
  1. iSocUSB-Driver-Setup-1.0.4 or install Intel flash tool, which comes with it. No need to disable windows security. Remember, I had problems, and I uninstalled Bitdefender for xfstk installation, and restarted sometimes.
  2. xfstk-downloader-setup-1.5.1, may show blank, or may not launch. Either it's bitdefender, or antivirus, or you may not have restarted pc after installation. Suggest, uninstall all antivirus and go with windows defender, and restart you pc a couple of times, and then the application will launch. Also run as admin to be safe.
  3. In xfstk GP flag override, use either 0x80000807 or 0x800000807(with extra 0), whichever works.
  4. xfstk can be used multiple times, if you fail in asus flash tool as well. This would bring you again to
  5. When stuck with result okay with asus flash tool after flash, do not i mean do not shutdown phone. Use volume up and down, and your phone with change and show right serial, and not abcdef... Force close asus tool, and launch again, while your phone is still on and connected. again volume up and down, and asus tool will detect the phone again, with correct serial this time. Now flash again.
  6. Highlighted deviations.
My phone is back from dead. and leaving phone to vibrate and restart does not drain battery, the process stops. So don't wait for battery to drain and fastboot, rather flash with xfstk.

Thanks abeyhere, you saved my life again. :) and this video
https://www.youtube.com/watch?v=fsAse5F5xtM
  • #140
go back to settings, change the flag override value to 0x80000807
that's four zeros between 800008. NOT five

You are the hero of the year friend! :good::good::good:
Now my ZE551ML starts working again.

Similar threads

sanderssomponts.blogspot.com

Source: https://forum.xda-developers.com/t/guide-recover-fastboot-of-bricked-zenfone-2-ze551ml-ze550ml.3284337/page-7

0 Response to "Xfstk Does Not Continue to Os Asus Z00ad"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel