My zenfone 2 completely stopped working. I can get into fastboot, but cannot flash anything (some end up cmds_error, others finish but don't make a difference), going recovery into recovery takes me to a black screen, and xfstk gives me usb_bulk_read() windriver at 11%, even though I have uninstalled and reinstalled drivers many times. Managed to get into tethered twrp and cwm. Cannot mount anything, and twrp shows 0mb internal storage. When trying to repartition the phone in fastboot using partition.tbl, it gives me gpt command error. Is there anything I could do, or is the phone dead? Thanks for reading.
If can get into bootloader ?
Scroll to power off , select. Can you see battery charging ?
Leave on charge .
If can get into bootloader what IFWI VERSION number is it ?
Don't use xFSTK if can get into bootloader .
If on 5.0 LP you can flash raw in bootloader .
If on 6.0 you can downgrade by recovery and ext sd , see my signature below
Three ifwi is 0094.0177. I am on LP, but asus flash tool ends with error one. In the log, it ends a partition /tmp/partition.tbl and says GPT command failed. I cannot access recovery, it just turns off my phone. The only recovery I can access is the temporary recovery (cwm) and it tells me that it can't mount any partitions. I also booted into a temporary twrp for another intel device, and it tells me I have 0mb storage. Also my serial number days 0123456789ABCDEF which is not normal, HW_VERSION says unknown, BOOTLOADER VERSION says unknown, SIGNING says ?, and SECURE_BOOT says ?. Thanks for the help.
Related
Hey Folks,
Ran a bit of trouble with my new Zenfone 2 , got it just a couple of days ago and a system update seems to have messed up. The phone froze half way through the update process and I had to turn it off (ran out of patience) and when I booted it up it just loads up to the ASUS logo and stays there for eternity.
I was not able to get to the Recovery mode, had a war with the dead android guy with the red triangle, ( holding power and volume up didn't help). I did however manage to get the device recognized on the Platform tools command like when I connected to my PC. I tried the ADB reboot command, ADB reboot recovery, and they didnt help. I did manage to work a couple of fastboot commands, fastboot erase data and fastboot erase cache BUT, looks like that's got me into deeper trouble.
Ever since I did that, I cannot manually go into the recovery mode anymore using the power and volume keys. I get a white USB logo and something that looks like a battery status bar below it. No combination of keys seem to help.
To make it worse, my device is not recognized on my PC anymore, ADB devices command doesn't list it, and neither does fastboot devices. I did however notice that now on my device manager, the phone shows up as a 'ortable Device - MTP USB Device'. No ammount of uninstalling and re-installing various kinds of ADB and USB drivers seem to help.
I did see a few blogs that give a fix for the same issue on a zenfone 5, but being a noob (hate to admit it) at this, I dont wanna risk it unless I'm sure it will help.
Can anyone help me out on this please? Any kind of help would be much appreciated
Download the Lastest firmware from here
https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
If you WW then download.
keep the zip file in SD card and rename it as MOFD_SDUPDATE.zip
Now go to bootloader and then recovery mode. it will automatically apply update. update may take time 10~20 mins
From your description you probably need to read this thread
http://forum.xda-developers.com/showthread.php?t=3162848
Sorry it's not good news
Sent from my ASUS_Z00AD using Tapatalk
It's showing error (status 7) . Help Me !!
stuck on usb logo
please help me my asus zenfone 2 z008d got the same problem from yesterday . its stuck on usb logo
Search xFSTK for repair/temporary fastboot, do the tutorial. Then goto recovery if still can. If recovery missing try to fastboot recovery. If failed then u must use Asus Flashtool to flash raw image. After that retry to flash droidboot, recovery, boot. Reboot to fastbootand go to recovery, then choose adb. Run adb sideload to flash full firmware.zip
I become an expert at unbricking hehe 
Stuck on USB logo...
Turn your phone off...
Start downloader ..flashing ifwi and fwr dnx and os image..connect phone.
Try flash os image on its own repeatedly ...ignore errors just keep doing it .
Then after 10 goes at it ..flash ifwi and dnx with it repeatedly till success.
Note that when it succeeds ..
Stop! and pause, keep an eye on your screen of phone..you see it flash , might take 5 mins before you see this start ..but when its finished ..you flash raw in flash tool after and it will reboot straight into system all by itself 
Me have been guilty of flashing raw before the flash of downloader...and a bet many others have too.
Ps select, wipe data in flash tool too.
i did update using the new firmware as u told by renaming the file to MOFD_SDUPDATE.zip
but after that my imei changed to 0049100491.....
then i formated whole using miracle box
now its stuck on asus logo and can't update now
hang on logo
please help
ritupaul91 said:
i did update using the new firmware as u told by renaming the file to MOFD_SDUPDATE.zip
but after that my imei changed to 0049100491.....
then i formated whole using miracle box
now its stuck on asus logo and can't update now
hang on logo
please help
Click to expand...
Click to collapse
You may want to reflash your phone using RAW firmware.
Sent from my ASUS_Z00A using XDA Labs
Makes TWRP useless, fastboot device cmd show [email protected]!#@!#@#[email protected][email protected]%%%@#%@#% - device
and only 3e recovery open but anything you flash comes up FAIL.
system used is B708_BbN
i have tried flashing thru fastboot using
B120_P6-U06_forFastboot
P6_Toolkit20140527- shows installed but still only 3e recovery can be opened. key combinations failed, adb recovery command still 3e, oem already unlocked
kernel used is angel-kernel-AROM_v5_b708
downgrading not possible as it wont even flash twrp
tried creating update.app but does not even recognize it and after flashing anything from external storage it comes back rejecting any mounted partition.
any suggestions for any more possible ways?
I think your emmc was dead bro, just like my ascend p6. I cannot do anything with my phone. You must replace your emmc. maybe on online store you can get the sparepart.
i dont know if thats the case... because i tried using Jurassic Uni Android Tool. its the only application that can read the brick P6. and the Build.prop is still intact, the storage still has all my file but i cant copy or download anything from it. the root system files are still present i used the file viewer option of Jurassic. i think its the theres a problem with the fastboot as it shows my device with crazy characters in fastboot devices command. when i manually flashe everything from fastboot it says everything went fine no error messages of any kind. but when i reboot. recovery, and everything is still the same. as if i did exactly nothing. jeezz..... i'll try to relock the bootloader. and flash anything i can think of. hahaha.....
So I've been following unbricking tutorials, and I have fastboot. Serial number is the 0123456789 ABCDEF thing, ifwi is 0094.0177, bootloader and hw version are unknown, and signing and secure boot are ?. So I've tried asus flash tool, and it tells me error 1, and if I check the logs it ends at "fastboot oem partition /tmp/partition.tbl." I've followed a tutorial to do it manually, and whenever I get to "fastboot oem partition /tmp/partition.tbl," it tells me gpt partition error. Recovery doesn't work, but I was able to boot into temp twrp and cwm. They both can't mount anything, and twrp tells me I have 0 mb of internal storage. Is it fixable? Thanks in advance.
135hussein said:
So I've been following unbricking tutorials, and I have fastboot. Serial number is the 0123456789 ABCDEF thing, ifwi is 0094.0177, bootloader and hw version are unknown, and signing and secure boot are ?. So I've tried asus flash tool, and it tells me error 1, and if I check the logs it ends at "fastboot oem partition /tmp/partition.tbl." I've followed a tutorial to do it manually, and whenever I get to "fastboot oem partition /tmp/partition.tbl," it tells me gpt partition error. Recovery doesn't work, but I was able to boot into temp twrp and cwm. They both can't mount anything, and twrp tells me I have 0 mb of internal storage. Is it fixable? Thanks in advance.
Click to expand...
Click to collapse
Can you connect in bootloader again , also load everything to AFT ,then whilst attached to pc ..then press vol+ once ?
Is the serial corrected now ?
Nope nothing. Still the same.
135hussein said:
Nope nothing. Still the same.
Click to expand...
Click to collapse
Have you used xFSTK on this device ? Did you buy this device in this state ?
If you did use xFSTK , then i would reflash again and follow my unbrick procedure in the link in my signature for correcting serial during the two part flash in AFT.
If you did buy this device in this state , then somebody could`ve incorrectly flashed wrong files in xFSTK
.
Going off your ifwi version , you have a 551 , but if someones flashed a 550 with 551 files (which i`ve witnessed on here ) then anything and everything could go wrong.
timbernot said:
Have you used xFSTK on this device ? Did you buy this device in this state ?
If you did use xFSTK , then i would reflash again and follow my unbrick procedure in the link in my signature for correcting serial during the two part flash in AFT.
If you did buy this device in this state , then somebody could`ve incorrectly flashed wrong files in xFSTK
.
Going off your ifwi version , you have a 551 , but if someones flashed a 550 with 551 files (which i`ve witnessed on here ) then anything and everything could go wrong.
Click to expand...
Click to collapse
Yes, I've used xfstk, and whenever I try it, it ends at 11%, and yells me usb_bulk_read() windriver error. I've tried the files from multiple posts, all ZE551ML, but still no luck.
135hussein said:
Yes, I've used xfstk, and whenever I try it, it ends at 11%, and yells me usb_bulk_read() windriver error. I've tried the files from multiple posts, all ZE551ML, but still no luck.
Click to expand...
Click to collapse
Thanks for that , when you get success in xFSTK you will then get temp bootloader 0094 0169 , then if incorrectly flashed raw in AFT you get 0-F serial or if correctly flashed 0-F to start with which is normal but then following the two part flash procedure , it then gets corrected -- Flashed incorrectly or correctly in AFT will leave you with 0094 0177 bootloader.
So , correctly flashing now in xFSTK seems the way to go .
So i am assuming you did get success at some point in xFSTK but are now no longer -- am i right ?
timbernot said:
Thanks for that , when you get success in xFSTK you will then get temp bootloader 0094 0169 , then if incorrectly flashed raw in AFT you get 0-F serial or if correctly flashed 0-F to start with which is normal but then following the two part flash procedure , it then gets corrected -- Flashed incorrectly or correctly in AFT will leave you with 0094 0177 bootloader.
So , correctly flashing now in xFSTK seems the way to go .
So i am assuming you did get success at some point in xFSTK but are now no longer -- am i right ?
Click to expand...
Click to collapse
Thanks for taking the time to help me. I've never gotten success in xFSTK. Always windriver error. I thought I had divers installed incorrectly, since that's what it sounds like, but after reinstalling multiple times, still nothing.
135hussein said:
Thanks for taking the time to help me. I've never gotten success in xFSTK. Always windriver error. I thought I had divers installed incorrectly, since that's what it sounds like, but after reinstalling multiple times, still nothing.
Click to expand...
Click to collapse
Okey so we need to try and get xFSTK to run successfully , i`m not sure whether it part flashing to a certain percent corrupts but i think it must have in your case.
1 if xFSTK Downloader opens up and you can fill in the files , then isoc driver is installed correctly.
2 you are putting in gp over ride value at 0x80000807 in the bottom section that ends in [bla bla CRC] ?
and ticking the box ?
3 you are running xFSTK as administrator too?
---------- Post added at 07:37 PM ---------- Previous post was at 06:56 PM ----------
A few things to try going off what you have give me so far , if above you understand and have already preset in xFSTK -- Try, uninstall AFT -- uninstall xFSTK -- clean pc with ccleaner , registry too(free)
reinstall xFSTK from my files in my unbrick thread in my signature -- the 3 files for xFSTK are there too.
Power off pc , power off phone but leave connected to pc.
Reboot pc -- when set up -- power up phone to bootloader and repeat xFSTK flash with my files.
@135hussein
Hows it going ?
Sorry for not replying sooner. I've been busy. Will try this tomorrow, and I'll get back to you. Thanks for the help.
Fastboot erase config....
After that I stucked at boot logo
Used xfstk then aft but stucked at boot used fastboot commands for flashing system all gonna smooth but stucked at boot...
Used recovery to sideload marshmallow ... succeed. But also stucked at boot ..unlock boot loader flash TWRP flashing custom rom also stucked at boot logo... PLZZ help me guyzzz
And it shows error in TWRP
Unable:to mount Config(invalid argument)
Hello guys
I have a problem
Description:
I have ZUK Z2 and its great phone. I installed latest LineageOS ROM which have OTA updates and yesterday prompt a comunicate that I can update my phone so i clicked to upgrade. But then system is not launching and there is only twrp mode so it's bricked i tried to restore my phone with method described here but it did't work :/ QFIL says" Download Fail: Sahara Fail: QSahara Server Fail: Name of directory is invaid (last one I translated because it was written in my native language). I checked FAQ and i restarted my computer and phone, i changed name of directory to ZUK and it still doesn't work :/ Then I found that ulocked bootloader may be a problem so I tried to lock it but it doesn't work either :/ i wrote adb reboot bootloader and my phone runs fastboot mode but command "fastboot oem lock" don't work, it says only "waiting for device" and nothing happenes :/
Could you help me to unbrick my phone? i'm very desperate
Since you can enter the recovery mode go to mainscreen of twrp, wipe system, data, dalvik etc (but do not wipe internal storage!!!) and then install again lineage, google apps, and addon superuser (in case you want root)...
Regarding QFIL method. I have flashed twice the ZUK orginal software with unlocked bootlader and the bootlader remains unlocked also after the flash. I guess you cannot flash with QFIL and you get the Sahara notice because it is either:
+ you have installed the wrong ZUK drivers or
+ the rom folder name is too long or it is something else.
QFIL method will wipe your entire phone though. So i would try first to wipe with twrp and if it does not work then try QFIL.
Modest Mind said:
Since you can enter the recovery mode go to mainscreen of twrp, wipe system, data, dalvik etc (but do not wipe internal storage!!!) and then install again lineage, google apps, and addon superuser (in case you want root)...
Regarding QFIL method. I have flashed twice the ZUK orginal software with unlocked bootlader and the bootlader remains unlocked also after the flash. I guess you cannot flash with QFIL and you get the Sahara notice because it is either:
+ you have installed the wrong ZUK drivers or
+ the rom folder name is too long or it is something else.
QFIL method will wipe your entire phone though. So i would try first to wipe with twrp and if it does not work then try QFIL.
Click to expand...
Click to collapse
I tried to flash ROMs via twrp like you wrote but still only TWRP starts and nothing else happens :/
Hi, what if I cannot get the the phone connected to CFIL? It always starts into twrp as soon as the phone is connected to the PC and it doesnt matter what buttons I keeped pressed.....
You wrote it wrong, when you try fastboot you need to use "fastboot -i 0x2b4c" otherwise it judt wont work and will always showing "waiting for device" hope you can get futher now.
Sorry, I dont got your point...
Hi
Head for zukfans.eu
Theres a thread and plenty of guides
Yes, there are guides but no one works for me so I came here for help :/ i'm desperate and i don't know what to do now :/
Are you able to boot into twrp? If yes, then wipe system, data, cache and flash rom again. If not, then boot into fastboot mode by holding down both volume button and connect your phone to PC. Once you're in the fastboot mode you have to flash recovery using the
Code:
fastboot -i 0x2b4c flash recovery <recoveryname.img>
, after flashing boot into recovery and allow for system modifications if a dialogue pops up and flash any custom rom with latest gapps (but you still need to wipe system and data) .
This worked for me on the advice of one of the users at zukfans:
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/soc/7464900.sdhci/by-name/misc
Modest Mind said:
Regarding QFIL method. I have flashed twice the ZUK orginal software with unlocked bootlader and the bootlader remains unlocked also after the flash.
Click to expand...
Click to collapse
even after flashing chinese 1.9.044 with QFIL?
I have an Asus Zenfone 2 Z00AD (ZE551ML). I tried to unlock the bootloader, which turned out to be a disaster as when the bat file said "All done", I wasn't able to get any input or display from the device. However, my computer was able to "Recognize" it by playing "Device plugged in" sound and then "Device plugged off" sound (I guess the device was still functional?). I tried to un-brick it using the xFSTK download tool and the ASUS Flash Tool, which again yielded the same result being the phone's not responding but still being recognized. I managed to get it into OS (with the boot animation thing) but I noticed that whenever i went to the bootloader and restart into recovery mode, the device shows the "ASUS" logo, then flashes and then it continues to boot into OS, not the recovery. I've tried flashing the recovery through fastboot but that didn't work as well. I don't even know what to do right now. Does anyone here know how to fix it? I need to get the device functional as soon as possible.
Try to flash custom recovery in fastboot mode
(If your bootloader is unlocked)
You have not lost your recovery partition, you only haven’t a recovery image properly installed. You have to flash a recovery (fastboot flash recovery.img) suitable for your os configuration (which is compatible with the boot loader version, divided in Lollipop and Marshmallow).
You can find here the latest TWRP.