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
Related
Hi there,
I've been a bit of a [email protected] and fudged my Huawei P6. I Was on South African Vodacom Stock Jelly Bean Rom, read this forum and got so excited about the world out there that i thought, why don't i try flashing a rom, i've only bricked a sgs2 and lg-g2 before... I should know what to do by now (never done a day's computer course in my life!)!
So flashed kitkat beta and then tried to flash Kit Kat... I have left the phone for about a week in the hopes I'd come back to it & it would miraculously work as I've read a lot of the forum posts on here and have a gut feeling I'm screwed so hoping one of you Huawei P6 XDA Guru's can Help. From what I remember I did this...
1) Rooted the phone with SRS Root or Root Genius
2) After a few attemps managed to install official kitkat beta from dload/update.app from external SD Card so I could then install official Chinese KiTKAT rom or HYDRO Rom.
3) Played with the kitkat beta for a while all working (bar the beta crashes etc) ( I think at that point I intalled CWMOD or TWRP)
4) It was very late, I should have gone to bed, I'd had a few beers, but no I carried on & was planning to install Hydrorom & (Mis)understood got mixed up with official chinese kit kat rom installation
5) Booted into recovery & flashed official chinense kitkat rom with GAAPS ticked to flash as well (maybe that will tell you guys if I was using CWM or TWRP!)
5.0117...c) If my memory serves me right I didn't (4am idiot/tired/few beers/rushing etc) wipe dalvic or any of that... just flashed from external sd card ZIP streight over kitkat beta (aaaarrgh!)
6) Phone is now stuck in bootloop with Huawei Ascend words first, then loading a Huawei flower logo. Goes no further, just stays on until battery flat...
7) Left phone plugged into power with screen on for a day hoping it was just taking a while to flash rom... & nothing happened
8) Tried the following but hope I'm doing them all wrong and you GURU's will have a giggle at my comlete lack of skills:
a) reboot phone - no luckb) hold down power & +vol & -vol -... no luck just flower logo againc) every combination of power and two volume buttons - no luck just flower logod) putting folder dload/update.app on external sd card and using b)method to flash update - no luck just flower logoe) putting stock recovery.img on root of external sd card and doing b) - no luck just flower logof) putting all of extracted TWRP download " TWRP_Installer_20140414 on root folder of external sd card - no luckg) spending 4 hours finding a "how to remove the battery from huawei P6" link and watched a russian guy remove battery on you tube. Did that as read that can reset boot loader/recovery.... no luckh) downloaded various versions of Android SDK Tools. Phone shows up as a "please insert sd card" in windows file manager and appears "offline" when trying to access it from command prompt ADB etc
checked that HiSuite was stopped in Task Manager etc, reinstalled drivers etc. One problem I'm hoping you'll all say is 100% to blame for SDK Tools not working is I'm on latest update of Windows 8.1 64bit...
Edit: Read other forum... I see the red led when turning phone on as well...
Edit: Just installed propper android sdk tools not small made up file and now phone changed from showing "offline" to "unauthorised" in adb...
So, please help.
Fixed it
Ok managed to fix this and hope it will help others. Was up till 2am last night after deciding to give it another go after getting no replies! The main problem here must have been that as device was seen as unrecognized on PC and I couldn't get past boot screen so there was no way to allow debugging/authorize I.e. No pop up on phone as stuck in Hauwei flower screen.
Previously I Couldn't get fastboot or adb on PC to do anything, just kept saying phone was offline or unauthorized.
Rebooted phone from boot loop screen of huawei flower on screen holding power and - vol button for a long time until only boots to huawei ascend words logo (phone still plugged into PC), let go of both. PC makes sound to show there is USB device, now it doesn't boot the huawei flower screen just stays on the Hauwei ascend screen (I think normally this would open recovery etc), so maybe it is in recovery just not showing on screen... I don't know?!
Adb devices says no device however... And obviously no adb commands work at all...
However, fastboot commands for some reason work even though devices still shows nothing... so I tried various commands but what worked for me was typing the following in command promt on PC:
Fastboot flash boot boot.img (Stock)
Where all the img,zip,app files I was flashing were were in the platform-tools folder where adb and fastboot are.
Then
Fastboot flash recovery recovery.img. (Stock)
Then I think what did it, I was obviously on a broken twrp recovery... Was I flashed
Fastboot flash recovery twrp_2_6_3_3_recovery.img
To my amazement twrp touch recovery loaded and I could then go about wiping dalvik etc and reflashing all the correct files.
So I'm now finally running HYDROROM_V7
All the files I used are on the hydro rom page here so thanks to them for that! :
http://forum.xda-developers.com/showthread.php?t=2630208
Hope this works for all of you stuck in bootloop etc as I really thought my phone was stuffed!
Ciao
pommiesa said:
Ok managed to fix this and hope it will help others. Was up till 2am last night after deciding to give it another go after getting no replies! The main problem here must have been that as device was seen as unrecognized on PC and I couldn't get past boot screen so there was no way to allow debugging/authorize I.e. No pop up on phone as stuck in Hauwei flower screen.
Previously I Couldn't get fastboot or adb on PC to do anything, just kept saying phone was offline or unauthorized.
Rebooted phone from boot loop screen of huawei flower on screen holding power and - vol button for a long time until only boots to huawei ascend words logo (phone still plugged into PC), let go of both. PC makes sound to show there is USB device, now it doesn't boot the huawei flower screen just stays on the Hauwei ascend screen (I think normally this would open recovery etc), so maybe it is in recovery just not showing on screen... I don't know?!
Adb devices says no device however... And obviously no adb commands work at all...
However, fastboot commands for some reason work even though devices still shows nothing... so I tried various commands but what worked for me was typing the following in command promt on PC:
Fastboot flash boot boot.img (Stock)
Where all the img,zip,app files I was flashing were were in the platform-tools folder where adb and fastboot are.
Then
Fastboot flash recovery recovery.img. (Stock)
Then I think what did it, I was obviously on a broken twrp recovery... Was I flashed
Fastboot flash recovery twrp_2_6_3_3_recovery.img
To my amazement twrp touch recovery loaded and I could then go about wiping dalvik etc and reflashing all the correct files.
So I'm now finally running HYDROROM_V7
All the files I used are on the hydro rom page here so thanks to them for that! :
http://forum.xda-developers.com/showthread.php?t=2630208
Hope this works for all of you stuck in bootloop etc as I really thought my phone was stuffed!
Ciao
Click to expand...
Click to collapse
Hey very good that you managed to fix your problem, when I first read your question I didn't had any ideas on how to fix it. But you had a bootloop I think and when you press power and vol- until it reboots you come in the bootloader, on our device it only shows the bootlogo so its seems that it is stuck but actually you are in the boot loader and can use fastboot commands. So glad you fixed your problem.
Gesendet von meinem P6-U06
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!
Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED <remote: flash write failure>
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
Cheers
Mattia
Did you update to the latest sdk tools? I think fastboot has been updated. Also, make sure you are using a good cable in a good port. I had trouble flashing with a USB 3.0 cable in a USB 3.0 port. It worked in a USB 2.0 port just fine.
I suspect your device is in a dirty state- it wants to wipe data to unlock the bootloader, but it didn't complete, so it is unwiped, but still considered encrypted. Maybe try flashing the stock system using fastboot -w update some-update.zip. The update zip is inside the factory image- you'll need to untar it. This is a destructive flash and will erase your data! If it works, let the system boot up since it will take a while to encrypt so that it is in a sane state.
I think download mode is for factory programming. I've been there a few too many times already, and I think it is vol up and power. It'll tell you not to disconnect the cable and the percentage bar will be stuck at 1%. I'll let you guess on how to get out of it.
Make sure you update android sdk like ^ he said, I spent 3 hours trying to get back to stock and trying to figure why fastboot system image wasn't workking -_-
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.
So, I was trying to revert to total stock on my Zenfone 2 (Z00A), and now it will not boot into fastboot, or to system. It just boot loops. Everything I found online requires I can get into recovery or fastboot to do anything, and neither of these appear to be working for me. Am I totally screwed, or is there a way to unbrick from here?
HopelesRomantc91 said:
So, I was trying to revert to total stock on my Zenfone 2 (Z00A), and now it will not boot into fastboot, or to system. It just boot loops. Everything I found online requires I can get into recovery or fastboot to do anything, and neither of these appear to be working for me. Am I totally screwed, or is there a way to unbrick from here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
follow this link.. please search before making new thread. if you have any question plz post there
I was unable to find this while searching (must not have searched hard enough). But thanks!
guys you got to do this , i am having yureka plus5510a complete bootloop no recovery
guys bootloop no recovery access no fastboot access
its all started with the king root i wanted to flash twrp in my yu yureka plus 5510a no idead what " A" stands for then i used flashify from playstore and downloaded the twrp by the official twrp and flashed it with the flashify and boom boot stuck with no recovery some how removing battery and connecting the phone goes to the charging disp from where i did enable the fast boot but cmd was not able to identify adb devices nor the flashboot commands were working so i did same with win 10 powershell but nothing no devices , so i decided to use a method of ygdp , much hopes with this used ***** 5.1.153.00.P0.160604.8675_I02.def.CPB ******* dont know where the log file is but it was showing old bootloader error downloading and error and error and terminated at 2 % , then this one of your thread by unziping the official files and clicking on flash-all.bat file which he provided img(1) "some trials your phone will be all right " i tried with some "waiting devices error " message but then it just started something happened oem unlock blah_blah and then successful , tried to boot again but this time phone was automatically jumping into fastboot mode , then i finally tried one last time in that power shell thing by typing using cmd and applied fastboot code , even no devices was showing in powershell ,, but then i used some different code something like "fastboot ix902 recovery " and i was able to install a real old twrp recovery.. phone was showing the cyanogen loading ....but later after 1 hour i felt its stuck = + = but luckily recovery was working but but dont know why the buttons setup used to go in fastboot mode was now taking me in recovery,, and fastboot was no longer acessable , i was fine with it so i downloaded latest recovery from your respected thread file named as " twrp-3.0.2-0-20160604-UNOFFICIAL-tomato.img " i wanted to install nougat aosp so i thought its a nice idea to update the recovery first i. so i did the normal recovery update from the recovery it self , and now i guess that recovery was so old , the new one was kinda mindblower for the older one and booom no recovery , no fastboot , tried all the combination and came up with this one volume+ vol- and power shown img (2) same as boot logo but a small "official" tag
:cyclops: pls help i know this post dont suits your professional level , right now i havent slept from kinda like three days cause of exams and this sarcasm of being in trouble.. like my every devices is rooted o in onyx m in tab 2 , it frustating pls help ........i will edit this and make it more polite but if you are one who can solve this .. i am ready to donate man. cause u deserve it , it will gonna be learning experience with you i will be totally into the reply and pls dont scream for drivers i did installed coolpad driver adb drivers everything required i feel yureka is a real fake company their parts isnt distinguishable i did al the steps nicely and cleanly except the (kingroot ) and pls dont brag about the old threads , they didnt helped me much.. and probably why my phone is kinda dead