[Asus Fonepad 7] Mindcracker:
Need help! Can't post it in a comment though!

Hi! I have two FE170CG fonepads that have had hard-bricked several times. And I was able to completely fix one of them using your method. And sometimes it bricks again, specially when tweaking or simply updating Google Play Services!

But, that's not my problem here. My problem is the second device, which has only been broken once, and since then I have not been able to fix it. Currently it will power on but get stuck on Asus loading logo. If I use VolUp+Pwr it will go to fastboot mode, showing this:

DROIDBOOT PROVISION OS

IFWI VERSION: 64.25

SERIAL_NUM: 1111111111111111

DROIDBOOT VERSION: WW_fonepad-11.2.3.33-20150302

Product: K012

Everything seems to be normal, except for that freaky serial number! I can flash the device using fastboot or ASUS Flash Tool, but no matter what, the phone will just stuck on loading after everything is done.

I also tried to fix the device using xfstk downloader, which I am almost sure I had successfully passed this step for at least once in the past. But for now all I see are the following errors:

00:57:07 - XFSTK-LOG--USBSN:E450988F6CBE7BD5--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field

00:57:07 - XFSTK-LOG--USBSN:E450988F6CBE7BD5--LogError

00:57:07 - XFSTK-STATUS--USBSN:E450988F6CBE7BD5--Error Code: 1 - Connection error

00:57:07 - XFSTK-STATUS--USBSN:E450988F6CBE7BD5--Failed to start Dldr state machine, aborting ...

00:57:07 - XFSTK-LOG--USBSN:E450988F6CBE7BD5--void CloverviewPlusDownloader::do_abort()

00:57:07 - XFSTK-LOG--USBSN:E450988F6CBE7BD5--Abort

00:57:07 - XFSTK-STATUS--USBSN:E450988F6CBE7BD5--FAIL

00:57:07 - XFSTK-STATUS--USBSN:E450988F6CBE7BD5--Errors encounter during download. Aborting...

00:57:17 - XFSTK-STATUS--Reconnecting to device - Attempt #1

etc.....

Everytime I plugg this phone while holding VolUp or not, it does not make any difference, the device vibrates and turns on with a white charge sign and then show the collored charging animation.

My computer detects a "CLOVERVIEW" device for a second and then the device is immediately disconnected. It then detects an "Unkown device" while the phone is charging itself!

The xfstk downloader shows "Target detected: 1" for one sec and starts the proccess, but will fast chang to "target 0" and reports connection errors as shown above.

I must mention that I am aware of all the steps taught and I follow them exactly. I'm using a win 10 64bit PC for this fix and am aware of driver signature enforcement, but I'm not sure if my attemps were enough to properly install all required drivers or not!

I know it makes sense to try to make sure the device is fully charged, and try this method on another system with Windows 7. But since there are other errors, and besides, I'm not even sure if the xfstk method is really necessary, I decided to ask you a question and get help by leaving a message! :D

Thank you very much in advance for taking the time to read this message. Any guidance or suggestion will be appreciated from the bottom of my heart!

I hope that by repairing this tablet and giving it as a gift to a needy girl I know, I will be able to help her study easily in this pandemic situation -despite my low income! :D