so the issues goes like that i was using cloudy 2.2 rom my varient was g3f400l i accedently installed 855 version from twrp the fone stated in fastboot mode . using fastboot i erased boot.img modem and recovery img laf.img and also reflashed those file flashboot gave error on partitiongt img file stating tha no file to flash so the fone did start with wrong rom that is d855 with a lot of errors i tried to falsh tot with flashtools it refused to flash stating that i am using wrong file so i edited build pro from d855 to f400l then i entered download mode connected flash tools i did start flash just after laf.img i gives an error stating unable to flash partion some thing like that and stops my fone is permanently in download mode when i turn it on the pc does detect it so as LG support tools but the KDZ flasher never worked for me nor the lg support tools they do download the right file but just as starts to updates it says disconnected check cable( same issue occured when my fone was working properly i tried to flash on windows 8 and windows 7 mechines ) any ways flashtools only flash laf.img and gives error and KDZ flasher for some wired reason didnt flash my fone before. i am thinking if some how i could enter the fastboot mode then i would manually flash all the files included system.img the fone would boot but how to i enter fastboot. and why the kdz never worked for me doesnt it work on win 7 and win 8 or is it the drivers what should i do help really appriciated thanks what if when falsh tools start to flash laf.img i remove the cable so laf.img cannot get flashed would that allow me to enter fastboot or there is any software that would work in download mode and manually flash all the img files plz help me thanks
satirg said:
so the issues goes like that i was using cloudy 2.2 rom my varient was g3f400l i accedently installed 855 version from twrp the fone stated in fastboot mode . using fastboot i erased boot.img modem and recovery img laf.img and also reflashed those file flashboot gave error on partitiongt img file stating tha no file to flash so the fone did start with wrong rom that is d855 with a lot of errors i tried to falsh tot with flashtools it refused to flash stating that i am using wrong file so i edited build pro from d855 to f400l then i entered download mode connected flash tools i did start flash just after laf.img i gives an error stating unable to flash partion some thing like that and stops my fone is permanently in download mode when i turn it on the pc does detect it so as LG support tools but the KDZ flasher never worked for me nor the lg support tools they do download the right file but just as starts to updates it says disconnected check cable( same issue occured when my fone was working properly i tried to flash on windows 8 and windows 7 mechines ) any ways flashtools only flash laf.img and gives error and KDZ flasher for some wired reason didnt flash my fone before. i am thinking if some how i could enter the fastboot mode then i would manually flash all the files included system.img the fone would boot but how to i enter fastboot. and why the kdz never worked for me doesnt it work on win 7 and win 8 or is it the drivers what should i do help really appriciated thanks what if when falsh tools start to flash laf.img i remove the cable so laf.img cannot get flashed would that allow me to enter fastboot or there is any software that would work in download mode and manually flash all the img files plz help me thanks
Click to expand...
Click to collapse
You can try this , It always works for me and this youtuber is great:
youtube.com/watch?v=1WgXuxDbmbc
satirg said:
so the issues goes like that i was using cloudy 2.2 rom my varient was g3f400l i accedently installed 855 version from twrp the fone stated in fastboot mode ....................................................................................................................................................................plz help me thanks
Click to expand...
Click to collapse
Hi there.
Sorry to hear you are having such problem.
Please check this thread out because the OP also flashed the wrong ROM on his phone but he found a solution to fix it http://forum.xda-developers.com/lg-g3/help/solution-flashed-wrong-model-rom-to-d852-t2987242
Let me know if this helped you please as I always feel sorry for people who brick their devices. Good luck.
Hi there, first topic on XdaDev, as I really need some help here.
I flashed the wrong system file on my Zenfone 2, I installed the 550ML version instead of the 551 one, at first I had a black screen but managed to get a clean install and the phone seem to work fine. But it is also running at the settings of the 550ML, which means 720p resolution and lower CPU frequency, and I would like to roll back to the original settings of the 551ML with the stock firmware if possible.
My issue is that I cannot load the System.img anymore. I follow these steps :
In CMD:
"Adb reboot-bootloader"
Daemon started successfully - The phone reboots in fastboot mode
Then I enter:
"fastboot flash system system.img"
but I encounter the "cannot load system.img" issue
What am I supposed to do now ?
Thanks for any advice you can provide guys.
PS : The system file is inside my fastboot folder and this file is a rooted one, I also downloaded the firmware from Asus but I have no idea how to use it.
EDIT : So I finally managed to go back to the correct rooted system, which is the 551ML, thanks to this topic : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
But I have another question, as it is my first android phone : If I want to update my system, will I encounter issues with the rooting ? What if I want to roll back to the stock system, how do I proceed ? Thank you guys, amazing forum you have there.
you can't go back right now,a file need another compatible file so you just have to reflash all the stuff from the beginning.
enter bootloader.wipe cache.in bootloader.ABSOLUTELY DONT SHUT DOWN.it can takes 15-20 minutes too.download latest firmware (2.19.40) for 551ml from here mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw check if your device is ww or cn.unzip the file and move the files in the adb/fastboot folder.these are the sizes of the files you should have in the adb/fastboot folder
droidboot.img should be ~ 13MB
recovery.img should be ~ 11MB
boot.img should be ~ 11MB
system.img shuld be ~ 2GB
connect to pc.enter bootloader again.type ' fastboot devices ' to see if your device is recognized
flash files in this order.at the end of each line type enter
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then choose normal boot in bootloader.after all,wipe cache again
you will have a rooted firmware.good luck man
My ZE551ML was rooted and I decided to update it being unaware that I was supposed to unroot it before updating. Once I got to the recovery menu, I attempted to sideload the newest firmware but the device was not found despite being able to be found during the bootloop. I then performed a factory reset and now it is stuck on a bootloop and cannot be detected by adb at any point.
U can use fastboot to flash ur device
But be careful with it u can hard brick ur device if done the wrong way
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
U can use fastboot to flash ur device
But be careful with it u can hard brick ur device if done the wrong way
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
But how do I fastboot to flash? Every tutorial I found told me to use adb sideload which I never found possible.
Edit:
I solved my problem by copying the firmware I downloaded into an external sd card under the name MOFD_SDUPDATE.zip and going to recovery mode.
download full firmware according to ur device from here https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw give Thanks @shakalaca for this
download (Z00A)2.19.40.18 if u want to unlock ur bootloader cause latest one cause problems with unlocking bootloader
when the device is off press power wait till it vibrates once then immediately press vol up button
u will boot into fastboot mode
there u can use fastboot commands
now form ur pc go to the path where u downloaded the firmware
press & hold shift & right click
select open command window here
now in command prompt give these commands
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
all done ur device will reboot
now u have a rooted device
remember if u want to update than first unroot it reboot than update
where do u get the system.img?
im also in a similar situation where im out of usb debug cause of factory reset
loganj said:
where do u get the system.img?
im also in a similar situation where im out of usb debug cause of factory reset
Click to expand...
Click to collapse
Here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
ultramag69 said:
Here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
thank you
well i manage to do adb sideload even though my phone was wiped completely clean from recovery and still unable to start the android.... it was a miracle . but thanks to your link i know now how to get the system.img
now if i can only understand what system.img is compare to entire firmware zip.....probably i should try to mount one and have a look
loganj said:
thank you
well i manage to do adb sideload even though my phone was wiped completely clean from recovery and still unable to start the android.... it was a miracle . but thanks to your link i know now how to get the system.img
now if i can only understand what system.img is compare to entire firmware zip.....probably i should try to mount one and have a look
Click to expand...
Click to collapse
System.img is the entire firmware except for boot, droidboot and recovery... These can be flashed separately BUT make sure you use the right commands...
If you get to the usb symbol only displaying on your screen, you've stuffed up and it is a true brick...
yakub234go said:
when the device is off press power wait till it vibrates once then immediately press vol up button
u will boot into fastboot mode
there u can use fastboot commands
now form ur pc go to the path where u downloaded the firmware
press & hold shift & right click
select open command window here
now in command prompt give these commands
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
all done ur device will reboot
now u have a rooted device
remember if u want to update than first unroot it reboot than update
Click to expand...
Click to collapse
Hey the procces struck whe i flash system img, stuck at "sending sparse 'system' (524056 KB)" Can you help me please?
After a long time waiting, probably over 1 hour i touch my phone screen then it just powered off suddenly. I really need help please
EDIT: i figured out that when sending sparse, after 10 second my phone just turned off
Maybe this tutorial works for you: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Sent from my GT-I9500
krasCGQ said:
Maybe this tutorial works for you:
Sent from my GT-I9500
Click to expand...
Click to collapse
I can't access my phone, how am i gonna turn on USB Debuggin when it's on bootloop ?
okokokokok i meet it
i have done adb side load but cant turn my phone. so, i went fastboot mode to flash it. but the bootloader is locked and cannot unlock it. when i enter the command flashing unlock,there is no response in the command prompt. can you also tell me how can i turn on usb debugging without switch on my android phone
I have the same problem than vinod.katakam!
I try to update my Asus Zenfone 2 Laser (ze601kl), to a recente version of Android, because i'm stuck on a older version of Lollipop.
My system had a SKU WW, so i downloaded the recent version WW (marshmallow) from Asus website, and treid to update, and that gives me an error. But i reboot the phone a it works fine. But still on my old android version.
Then i tried to just update to a more recent version of Lollipop, the process appears to start fine, but then it gives me an error. Now, i tried to reboot and i end up with a endless bootloop.
I tried everithing, update by adb (cant open the file), update by sdcard (E:Error in /sideload/package.zip (Status 1) E: fota_return_code 408), and fastboot boot.img, recovery.img, but on system.img says the file is to big.
I dont have de USB Debbugind activated. Is that a problem?
I dont have important data on the phone, i just want to make it work again.
Please help!!!!
pedrofg said:
I have the same problem than vinod.katakam!
I try to update my Asus Zenfone 2 Laser (ze601kl), to a recente version of Android, because i'm stuck on a older version of Lollipop.
My system had a SKU WW, so i downloaded the recent version WW (marshmallow) from Asus website, and treid to update, and that gives me an error. But i reboot the phone a it works fine. But still on my old android version.
Then i tried to just update to a more recent version of Lollipop, the process appears to start fine, but then it gives me an error. Now, i tried to reboot and i end up with a endless bootloop.
I tried everithing, update by adb (cant open the file), update by sdcard (E:Error in /sideload/package.zip (Status 1) E: fota_return_code 408), and fastboot boot.img, recovery.img, but on system.img says the file is to big.
I dont have de USB Debbugind activated. Is that a problem?
I dont have important data on the phone, i just want to make it work again.
Please help!!!!
Click to expand...
Click to collapse
if you are on 64 bit windows and fastboot flash system system.img gives you error. probably you are not using 64 bit fastboot tool below is the link to 64 bit tool
https://drive.google.com/open?id=0B72QQTXqZSRwUkFRMl81b1pWa0k
The problem still remains!
The problem still remains!
"C:\adb>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.022s]
sending sparse 'system' 1/12 (259338 KB)...
OKAY [ 11.418s]
writing 'system' 1/12...
FAILED (remote: size too large)
finished. total time: 11.471s"
Hello guys!
Well, i manage to understand my problem and solv it!
I bought my phone from Gearbest, and the problem begins there. Why? Because, regarless my phone is a CN device, it came somehow with a WW sku. You must know that a CN device have system partition smaller than the WW device.
So, when i tried to updated it with a more recent WW system there was no room for that, and the instalation stops with a error message.
After many "Trial and error", i understand what my problem is, and tried to install a CN system version by "fastboot flash" with a system.img with root that i find here: "https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw"
To fastboot i used the fastboot tool that sukhwant717 told me to, in the post #15.
Well, that worked, so i now have a phone working. Them i go to Asus website and downloaded the latest CN firmware to my divece, copy it by USB to the internal memory of my device and upgrade it.
So, now i have a phone working with a factory system but with no google apps.
I found this website with google installer: "https://www.digitbin.com/google-installer-apk/" follow the intructions and finaly i have Google play in my phone!
Now everithing works fine!
I hope that my story could help someone with the same problem!
I have zenfone 2 with a cn recovery on it but says it has a ww build. I keep getting a pop up permission, which is really irrating. If I want to put a development rom on my phone do I have to change the recovery first(cn to ww)? What is the procedure I need to go through to get this phone working properly? I've read the cn to ww threads but the links to builds are old. Which ww build do I start process of changing the cn to ww recovery?
Where do I start...?
Any help would be welcomed
Look at this : http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=14962
I also have a CN version, however I updated my phone to the most recent Chinese Version ( 2.20.40.185) and now whenever I try to execute step Write adb sideload file.zip I get error: protocol fault (no status). However the version I tried it with is not more recent thatn 2.20.40.185 do I have to wait for a new update in order for it to work?
Master.Mind said:
I also have a CN version, however I updated my phone to the most recent Chinese Version ( 2.20.40.185) and now whenever I try to execute step Write adb sideload file.zip I get error: protocol fault (no status). However the version I tried it with is not more recent thatn 2.20.40.185 do I have to wait for a new update in order for it to work?
Click to expand...
Click to collapse
Did you enable developer mode in settings and tick USB debugging?
If not you go to settings>about, find build number in about and click on it until you see developer mode enabled. Go back up one level in settings and you'll see developer settings, turn on and tick box for USB Debugging.
Then go back to and try adb sideload again.
If you want root then the best idea is to go to Shakalaka's pre-rooted rom thread in Android developement and download the version you want, I believe he has 2.20.40.184WW there now, then use fastboot to replace the boot, droidboot, recovery and finally system files. Be VERY careful about copy and paste as there have been people who brick their devices due to overwriting the same partition with all the above files.
To Change CN to WW - Use Fastboot Flashtools
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Cheers...
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