Hey guys!
Hard-bricked my Z00AD, I'm able to get to bootloader using xFSTK but AFT flashing fails over and over.
Tried flashing with a couple raw images I found, waited an hour for one to complete and got nothing, then waited 7 hours for the other, still no go. currently have it running with a 2.20.40.139 image that I downloaded from this guy's video: https://www.youtube.com/watch?v=BboYFzgg7Jo
Also searched the forum a bit and found a couple more images that I'm currently downloading (2.15.40.13 and 2.20.40.196, gonna try to revert to android L with the first one, maybe it'll work)
It just gets stuck at the "Flash image" stage with "RESULT: OKAY" on my device.
Tried flashing manually with a later firmware after supposedly cleaning the partitions (I.E. sideloading via fastboot to flash splashscreen, droidboot, boot, recovery and system of the latest firmware) and nothing happened.
ATM Also downloading the 2.20.40.139 zip firmware to try and manually flash the same firmware on the device.
Any suggestions?
Thanks!
Hi @firecharge , there is a two part flash ritual to flashing raw file first part your serial is 0 - F
First flash,is approx 3 mins , where/when it says "RESULT =OK "
close flashtools , force close it. Keep phone attached.
Open /run flashtools again input raw again , press vol+ on phone and serial will be corrected this time ,start 2nd flash and let the second flash complete and it will boot into system by itself.
There is a unbrick thread with vid in my signature showing exactly this , from 2:17 mins in
Here
https://m.youtube.com/watch?feature=youtu.be&v=PmbRaJijIBs
timbernot said:
Hi @firecharge , there is a two part flash ritual to flashing raw file first part your serial is 0 - F
First flash,is approx 3 mins , where/when it says "RESULT =OK "
close flashtools , force close it. Keep phone attached.
Open /run flashtools again input raw again , press vol+ on phone and serial will be corrected this time ,start 2nd flash and let the second flash complete and it will boot into system by itself.
There is a unbrick thread with vid in my signature showing exactly this , from 2:17 mins in
Here
https://m.youtube.com/watch?feature=youtu.be&v=PmbRaJijIBs
Click to expand...
Click to collapse
Thanks for the quick reply
Tried that, the serial on the device does change but afterwards it doesn't recognize it ever on the flash tool or in fastboot (says "fastboot cmd waiting" on the device, tried to check fastboot devices on cmd and it doesn't appear, same for AFT v1.0.0.24)
@firecharge
Have another go with 1.17 AFT download in my unbrick thread.
If nothing gained from that , maybe related to fastboot cmds you flashed earlier so might need to re xFSTK flash again , then re two part flash raw file
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
PS , run aft as admin.
Check you are highlighting serial number before starting flash like in video, that line turns blue
timbernot said:
@firecharge
Have another go with 1.17 AFT download in my unbrick thread.
If nothing gained from that , maybe related to fastboot cmds you flashed earlier so might need to re xFSTK flash again , then re two part flash raw file
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
Click to expand...
Click to collapse
Tried to re xFSTK flash with files downloaded from your thread, still has the same result.
Bootloader reads:
Product_name - Z00A
Variant - Asus_Z00A
HW_Version -
Bootloader Version - unknown
IFWI version - 0094.1069
Serial Number - some number other than 0-F
Signing - ?
Secure_boot - ?
Again, tried to disconnect and reconnect phone to USB cable, does that recognition sound but isn't popping up on fastboot or AFT.
Did you buy this phone in bricked state ?
Reflash xFSTK .
Do not flash cmds in fastboot
Two part flash raw
Works
Everytime
timbernot said:
Did you buy this phone in bricked state ?
Reflash xFSTK .
Do not flash cmds in fastboot
Two part flash raw
Works
Everytime
Click to expand...
Click to collapse
Didn't buy the phone bricked, bricked it myself accidentally
Reflashed xFSTK
**Did not flash in fastboot** - fastboot was a measure of seeing if the phone is recognized - which it's not after the first raw flash. -Which is exactly my problem
For some reason the phone does recognize that it's supposed to be in fastboot mode - saying "fastboot cmd waiting", but my pc can't recognize it.
Gonna give it another try with xFSTK then two part as you say, if it doesn't work I'm gonna try it on another machine and see if same happens there.
Good stuff
Your first flash in AFT when it said 'result ok' shown fastboot was working , then you messed about in fastboot sideloading or whatever ,and then no longer with a serial other than 0 to F .
Shows , you did something there to damage the process.
Hopefully it can be fixed now , fingers crossed.
Messing about in temp bootloader with incorrect fastboot commands leads to loss of serial and of course imei.
It really does only take 15 mins from brick to system , flashing this method and safer should errors occur by flashing incorrect fastboot cmds at a critical stage
timbernot said:
Good stuff
Your first flash in AFT when it said 'result ok' shown fastboot was working , then you messed about in fastboot sideloading or whatever ,and then no longer with a serial other than 0 to F .
Shows , you did something there to damage the process.
Hopefully it can be fixed now , fingers crossed.
Messing about in temp bootloader with incorrect fastboot commands leads to loss of serial and of course imei.
It really does only take 15 mins from brick to system , flashing this method and safer should errors occur by flashing incorrect fastboot cmds at a critical stage
Click to expand...
Click to collapse
Thanks for the assistance - My fix was this:
Did the xFSTK to get to bootloader
Flashed once with AFT
Then going to another computer I flashed for the 2nd time since it was recognized and now I have the firmware installed properly and my phone is back up and running.
@firecharge
That WAS hard work
Wow lmao .
Messing with your phone , gives other people headaches
PS hit the thanks for me saving your life ???
Or next time you feck up , no help from me
OK back to plastering the walls , no rest for the wicked , funs over
timbernot said:
@firecharge
That WAS hard work
Wow lmao .
Messing with your phone , gives other people headaches
PS hit the thanks for me saving your life ???
Or next time you feck up , no help from me
OK back to plastering the walls , no rest for the wicked , funs over
Click to expand...
Click to collapse
Pushed that thanks button hard bro
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
HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site
Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.
timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[
quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.
Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
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)
Hi everyone, i'm kinda new here and noob i'll describe the problem.
I have already followed many guides about bricked phones, fastboot solving and xftsk.
I have this Zenfone 2 Deluxe that i have modded with Groovy Android, tried to root with magisk but it didn't work so i wiped everything with TWRP(every option). Only TWRP worked for 2 days telling me that there was no OS. So i tried to flash a stock firmware via ASUS Flash tool but it didn't work cause it couldn't enable ADB. ADB didn't work once, first it didn't detect phone, then it said device offline so I gave up. Found the xFTSK method. Tried it and worked ( it booted into bootloader with the rainbow icon and still does) but the serial changed to 0123456789ABCDEF. Tried Fastboot right after as guides said. Fastboot didn't and still don't work. He couldn't find files, couldn't load them and now it says " failed (write to device failed(unknown error)). So I tried ASUS flash tool again but he said flash image failure status read failed too many links, then that fastboot coulnd't be loaded and other errors.
Along the way recovery mode "disappeared" too. It doesn't work anymore. Plus sometimes the phone boots and keeps rebooting into a white usb icon.
What should I do? Feel free to re-link me guides, PM or something else, i'm open to almost everything to solve that.
Thanks in advance.
Edit: fastboot gaves some kinda errors with partitions too ex: can't erase cache.
Battery and cable are not ASUS original ones.
MixedFried said:
Hi everyone, i'm kinda new here and noob i'll describe the problem.
I have already followed many guides about bricked phones, fastboot solving and xftsk.
I have this Zenfone 2 Deluxe that i have modded with Groovy Android, tried to root with magisk but it didn't work so i wiped everything with TWRP(every option). Only TWRP worked for 2 days telling me that there was no OS. So i tried to flash a stock firmware via ASUS Flash tool but it didn't work cause it couldn't enable ADB. ADB didn't work once, first it didn't detect phone, then it said device offline so I gave up. Found the xFTSK method. Tried it and worked ( it booted into bootloader with the rainbow icon and still does) but the serial changed to 0123456789ABCDEF. Tried Fastboot right after as guides said. Fastboot didn't and still don't work. He couldn't find files, couldn't load them and now it says " failed (write to device failed(unknown error)). So I tried ASUS flash tool again but he said flash image failure status read failed too many links, then that fastboot coulnd't be loaded and other errors.
Along the way recovery mode "disappeared" too. It doesn't work anymore. Plus sometimes the phone boots and keeps rebooting into a white usb icon.
What should I do? Feel free to re-link me guides, PM or something else, i'm open to almost everything to solve that.
Thanks in advance.
Edit: fastboot gaves some kinda errors with partitions too ex: can't erase cache.
Battery and cable are not ASUS original ones.
Click to expand...
Click to collapse
do not use asus flash tool to flash raw firmware. use commands to flash firmware. second if you will use latest raw after xFSTK it will not work. Use old raw firmware provided in guide. Hoping that ASUS flash tool has not messed up your device. use old firmware in guide command's method. if fails once again use xFSTK and flash old firmware via commands. Stay away from asus flash tool.
sukhwant717 said:
do not use asus flash tool to flash raw firmware. use commands to flash firmware. second if you will use latest raw after xFSTK it will not work. Use old raw firmware provided in guide. Hoping that ASUS flash tool has not messed up your device. use old firmware in guide command's method. if fails once again use xFSTK and flash old firmware via commands. Stay away from asus flash tool.
Click to expand...
Click to collapse
Thanks for the advices. Fact is, fastboot commands do not work so I tried flashing varius raw files via Asus flash tool but without success. If u think u can help me I can post screenshots about the errors ( I don't know why they change everytime)
MixedFried said:
Thanks for the advices. Fact is, fastboot commands do not work so I tried flashing varius raw files via Asus flash tool but without success. If u think u can help me I can post screenshots about the errors ( I don't know why they change everytime)
Click to expand...
Click to collapse
yes a screenshot would be good. as i told earlier. new firmware version or bootloader have different set of commands. post raw firmware version number you are using along withifwi version and bootloader version you are on currently.
sukhwant717 said:
yes a screenshot would be good. as i told earlier. new firmware version or bootloader have different set of commands. post raw firmware version number you are using along withifwi version and bootloader version you are on currently.
Click to expand...
Click to collapse
Fine, bootloader version says " unknown " now, i'll try re-using xFSTK. About the screenshots here they are. http://puu.sh/D7tXU/b83ccf1502.png
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?
renatogui said:
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I had frozen twrp screen before but usually managed to fix just by restarting the phone and using twrp offain in adb.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?
Click to expand...
Click to collapse
1- Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2- Create a new folder on your C drive and name it: adb
3- Extract & place everything from the platform-tools into your adb folder
4- Download this: https://drive.google.com/open?id=1SKIlWS-y6kNI4YIE2Sj4_9CcRJ9W0xTh
5- Extract & place it to your adb folder
6- Reboot your phone to TWRP and wipe it, then reboot to bootloader
7- Connect your phone to your PC
8- Go into the daisy_global_images_V10.0.9.0.PDLMIXM_9.0 folder and run: flash_all.bat
A window will pop up and install the stock mi a2 lite rom. Let it finish then your phone boot up. You will have to update your phone since this stock rom that I linked is a pretty old one.
Someone had a similar question in another forum, so I just copy my answer from there. If you have adb already installed you can ignore the first 3 steps.
I had frozen twrp screen a couple of times but managed to fix it by restarting the phone and re-open the powershell window in adb. I use twrp-daisy-3.2.3-0-offain.img
I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.
I was thinking I did not try to install stock image using MiFlash tool. I can do it if I get a windows computer available.
I saw people suggesting fastboot oem edl but I could not find a clear explanation of the procedure.
I understood that I must use MiFlash in that case too but the steps are not clearly defined and I need a windows computer anyway.
Does someone have a step by step to use fastboot oem edl?
renatogui said:
I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.
Click to expand...
Click to collapse
No particular reason behind 10.0.9.0 ... I just had that uploaded to my drive and when I posted this to another forum I didn't wanted to "waste" time to search for a link so I just used mine. Anyways u have to wipe your phone before installing stock rom.
The way I fixed mine is not working for you so Im afraid Im out of ideas.
Hope someone can help you out with it
thanks, anyway for your kind and quick answer.
I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue. When it comes to EDL flashing:
1 - Grab the 20160401 version of MiFlash from here : https://www.xiaomiflash.com/download/ (You need this version because it's the only MiFlash version that's capable of EDL flashing, mind you, you need a Windows PC and 64-bit hardware for this)
2 - Connect the phone in fastboot mode and type this command :
Code:
fastboot oem edl
Hit enter, this will take the phone into EDL mode, which means the screen will go black and the notification LED will start blinking.
3 - Now you're in EDL mode, open the MiFlash version I mentioned and Browse to find the location the stock ROM is stored, then hit refresh so that the software can recognize the phone.
4 - Hit flash to start flashing, but remember EDL flashing is a very fragile process, so make sure you don't lose power/shutdown the app while it's doing its job. After a successful flash, the app will say it is successful. Unplug the phone and start holding the power button to reboot. If you want to lock the bootloader, make sure to hold vol down as well and go into fastboot then re-lock the bootloader with :
Code:
fastboot oem lock
5 - Voila!
Thank you marstonpear for the detailed answer.
I will try MiFlash this evening and will post the result here.
I am very glad to count with more experienced people in fixing my errors.
Hello marstonpear,
I downloaded daisy image v10.0.13.0 that was suggested in XiomiFlash how to and try to flash it.
I got the error "mismatch image and device". This is very strange. Never had this before flashing with fastboot.
Do you think I could scrambled mi A2 lite so MiFlash cannot recognize it as a mi A2 lite anymore?
The only different think I did was interrupting my first flasing try using ^C when it was frozen.
I made 2 other tries after this with no errors. The only problem was the never ending boot.
My next try will be using image v10.0.18.0, the one I had installed before all this problems begin.
renatogui said:
Hello marstonpear,
Click to expand...
Click to collapse
marstonpear said:
I'd suggest giving MiFlash a try.
Click to expand...
Click to collapse
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.
coolwei1 said:
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.
Click to expand...
Click to collapse
I'm sorry. I tried hard how to quote and did'nt find.:cyclops:
I am almost learning...
marstonpear said:
I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue.
Click to expand...
Click to collapse
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?
renatogui said:
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?
Click to expand...
Click to collapse
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?
renatogui said:
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?
Click to expand...
Click to collapse
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.
marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Now I know the reason of mismatching. All the scripts bundled with Xiaomi_Mi_A2_Lite_V10.0.13.0.PDIMIXM_20190807.0000.00_Global_9.0_XFT are made for jasmine. I will find another image more trustworthy than this one.
marstonpear said:
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.
Click to expand...
Click to collapse
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:
renatogui said:
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:
Click to expand...
Click to collapse
for others having the same probem I've learn in another thread that this error is issued because I did not choose the lock option below right of MiFlash tool. That is why it didn't catch the lock checkpoint. But the end of the message is not true because at this checkpoint, the flashing is already done. I simply turn the phone off and on again and the boot was normal.
Thanks for all that help me specially marstonpear.
Thread closed... until next problem.