Related
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
EdoIsa said:
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
Click to expand...
Click to collapse
What are FZ DnX, IFWI, FW DnX and OS images files ?
How to extract them from the site you mentioned?
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
I have no experience with FZ DnX, IFWI, FW DnX files, but the OS image file is on the site I posted.
Follow my link. Once there, expand the list 'Firmware' and download firmware Version WW_2.15.40.10. Once its downloaded, open the zip file. Inside should be a System.img file. Extract the System.img file into your Fastboot folder. This is the OS image the guide is referring to.
Ask around for the meaning of the other files. Meanwhile, I will research more about those files later tomorrow and get back with any info I can find. Good luck!
cde2006 said:
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
Click to expand...
Click to collapse
install driver manually. see attachment.
When you plug your phone into the computer, does the phone show up in the device management? Typing devmgmt.msc into the windows 7 start menu or the start run menu on XP is the fastest way to get to Device Manager.
Is the device already known by your computer?
What does device manager think it is?
If its unknown, please let us know what the Hardware Ids and Compatible Ids for this device show up as. In device manageer, you can open the devices properties and under the details tab choose Hardware Ids and Compatible Ids. you could screen shot these with Alt + PrtScn and use mspaint to save them off. Otherwise you have to use Ctrl + C to copy them out . You can choose all lines by selecting the first and while holding Shift, select the last. Then you can Ctrl + C to copy all of them out.
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Chinaphonearena said:
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Click to expand...
Click to collapse
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
I think that avoiding flashing droidboot and recovery, and making sure file hashes match, everything should be fine.
Same issue
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
cde2006 said:
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
Click to expand...
Click to collapse
I put my 64gb sd in my ZF2 that I originally partitioned for my LG Optimus Pro and I moved a bunch of apps to the SD with link2sd and the first time I rebooted, the same screen with the USB logo and a full progress bar showed up. It won't recognize any fastboot or adb commands even though the ASUS adb is showing up in device manager. Nothing else shows up. In devices and printers I get Moorefield. The phone randomly reboots and goes back to the same screen over and over and each time the asus adb disappears from device manager and then returns. I found a guide on the zenfone 5 that looks promising, using the intel flash tool, however it requires the ZenFone 2 raw firmware files and I can't find them... Hopefully someone could help me salvage my ZF2 cuz I was really beginning love the phone... Thanks ahead of time for anyone that looks into this for me!
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
sry, had only the files for V5. I will load down and put it here.
boot error and bricked zenfone 2
i have same problem with my phone please send moorefields or other intel based boot drivers.. tanks
please tutor how to fixed it, thanks for advice
cde2006 said:
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
Click to expand...
Click to collapse
Lol @ "got sequence on this forum" and "more safe proven way."
You didn't read the instructions carefully enough and made a big mistake as a result. The correct sequence was given. You just didn't read it carefully. Lesson learned.
Hopefully you can unbrick it.
No offense, but this type of thing is what happens when people just copy/paste and don't understand what they're doing.
What you did was overwrite the fastboot partition each time you flashed. You flashed a 2GB system img on top of your fastboot partition. This probably seemed like it locked up and you either unplugged or turned it off. This likely caused a corrupt partition.
Reading is key when you do anything with your phone.
This is perfectly safe. This is the way it works for all devices. It has nothing to do with the files or the phone. This was 100% user error. Simple as that.
ze550ml hard brick
http://forum.xda-developers.com/zenfone2/help/zenfone2-ze550ml-hard-bricked-t3148174#post61657126
my ze550ml hard brick too. please help me
sorry for bad english.
hardbrick zenfone 2
konsolen said:
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
Click to expand...
Click to collapse
Hello, i have the same issue with my zenfone 2, I download the firmware files from Asus website, but the Intel flash tool can't found a flashable image file. My question is to, if you have the firmware files that send it to me?
same issues here please help,
same issues here please help,
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
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)
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
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