Develop Bugs

[PrimoC:CDMA]ROM reboots after a minute no matter what you do? Here's the solution!

I know the feeling! You're all excited because you just unlocked your One V's bootloader, flashed a recovery, and flashed a steamin' hot new ROM. You boot up for the first time and get ecstatic, the tension building as you put in your Gmail info. You finish the start up but OH NO!!! Your phone reboots! You blame yourself... you blame your cat... you blame your wife... you blame the war in the Middle East. You think, I must've done something wrong! Stupid, stupid, stupid! Don't fret! Take my experience with this quite seriously (despite the jokes). For 2 weeks, I retraced my steps and tried EVERYTHING! I thought it was just the ROM's problem, so I flashed one after another to the same end. Finally, I decided to post a new thread asking for help. Nothing became of the first thread, so I posted a second one. To my great relief, along trotted Curiousn00b. After shoving me in the correct direction, I figured out the rest. A big thanks by the way, Curiousn00b! The following is the method that I used to get my phone to finally run a ROM. Also, a thanks to CafeKampuchia for the quoted directions below.
A few things to make sure you have:
Windows (with Administrator's priveleges)
Fastboot installed and working
Your phone (duh!)
A USB cable
Time and patience
The following quote is from CafeKampuchia's thread over here.
Solution #1
CafeKampuchia said:
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thus far you should have the stock recovery back and be bootlocked again. Now, back in fastboot mode, you should already be connected to your computer via USB (if you disconnected, just reconnect it and wait for "FASTBOOT" to change to "FASTBOOT USB")
Run this command:
Code:
fastboot oem rebootRUU
Next, start up the RUU program again and let it run through without interruption. After this process is done, the phone should boot up to the stock ROM. Let it do its thing, but this time don't do the OTA update. From here, just unlock the bootloader again, install your recovery of choice, and install your ROM of choice or reroot the stock ROM (I know some want to keep it stock).
As also pointed out by RoyalYeo, you can let HBOOT take care of the problem:
Solution #2
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse
My personal solution (Solution #1) is the more technical side of things and also exposes you to the nitty-gritty. Having said this, #1 is quite touchy because if you do something wrong, there is a good chance that you could... well uh, brick your phone to be quite honest. On the other hand, #1 requires no SD card (given the event that your SD card won't mount, your SD reader is broken, or you just plain don't have an SD card). Ultimately, the choice is up to you.
A note for Mods: I'm not sure if this technically falls under Development or Q&A (or both). If it can stay here in Development, I'll also post a thread in Q&A.

hello there,
So i've followed these instructions and I still get a bootloop... Occasionally when i flashed the MIUI.us rom it will get up to the start out screen... then restart... and do it repeatedly... but at the current moment... it's simply bootlooping on the MIUI logo. I've ran RUU approximately 20 times on this phone... i've tried different SD cards because something is recently they have been randomly disconnecting and not showing up... i Plugged my phone in and set it to Disk Drive mode, wrote files to it... and when i check on my phone... all the files are gone except for the original.. so i preceded to take the card out plug it into my computer and format there... i do that... and all the files show back up when i plug into my phone... ALL the original files that i just formatted... i don't know what steps to take next to get any of it working. I've tried flashing sick kernel and the MIUI rom and still nothing has worked... any assistence would be greatly appreciated, I'm tired of resetting my phone EVERY time i try and flash a new rom
I have a thread here but Everything i have tried there has failed to work but you could use some of the info from there to possibly diagnose?
http://forum.xda-developers.com/showthread.php?t=2013489
Thanks a million!

[Q] Very weird root issue - didn't sleep for two days

When I first bought my ZL, I rooted the phone using binary4 V27 on superuser mode and that was very fast and simple. I could modify system files and do everything.
One day using my ultimate stupidness, I updated the firmware to 10.1.1.....253 then I did factory reset without doing a backup for my root.
Right now, when I go to settings -----> about ----> I get Kernal version 3.4.0 with android version 4.1.2 but unfortunately It seems like I don't have a rooted phone + I am unable to do any function of a rooted phone like modifying system files or ....etc .
I've tried million ways such as:
1- rooting the phone using the same method --------> the result is stucking at the wight screen and nothing happened.
2- Using motochopper method --------> doesn't work
3- Using the method of installing Android SDK and using the command prompt window to push (Su-busybox-superuser.apk) files to data/local/tmp/ --------> when reach sysrw step (sysrw not found)
tried to type SU (su not found)
tried to use one of the alternative commands like cd /system/usr/we-need-root or ./su-backup -----> file not found
or mount -o remount,rw '' /systemmount ---------> Operation not permitted
I will be following your instructions directly and give u the feed back
I am not gonna move anywhere until solving this issue BC I am getting crazy
I would highly appreciate your help guys , ... Thank you so much in advance

Check this out:
I did the same, was on rooted 434 version and updated to 253 and it unrooted. The 253 update can't be rooted by the normal exploit methods, but this post worked for me:
http://forum.xda-developers.com/showpost.php?p=41727431&postcount=39
Took a little time, and everything on my phone was wiped when I had to unlock the bootloader again, but I now have my stock 253 ZL rooted and unlocked.

mattabyte said:
I did the same, was on rooted 434 version and updated to 253 and it unrooted. The 253 update can't be rooted by the normal exploit methods, but this post worked for me:
http://forum.xda-developers.com/showpost.php?p=41727431&postcount=39
Took a little time, and everything on my phone was wiped when I had to unlock the bootloader again, but I now have my stock 253 ZL rooted and unlocked.
Click to expand...
Click to collapse
Thank you so much for your reply but you know, that really seems to be so complicated
Ufffff

It's a lot more simple than it looks. Here's a slimmed-down version of the instructions:
Since you're already on the 253 update, you can skip numbers 1 & 2 from the other page and just start with numbers 1 & 2 below.
1) Download from this link the 0.9.10.2beta6 version of Flashtool: http://forum.xda-developers.com/showthread.php?t=2201189 and run the installer. Make sure to install to your computer's HDD root (ie; C:\Flashtool).
2) Make sure you have flashmode and fastboot drivers installed for your device. Easiest way to tell if they're done correctly is to open your Device Manager (in Windows), power off your phone, and plug it into a USB port in each of the modes and make sure no errors show up in the Device Manager.
3) Unlock your bootloader with the Flashtool. It'll have you first go into flashmode, and then prompt you to unplug and plug back into fastboot mode.
4) Download v07 of DooMKernel from this link: http://forum.xda-developers.com/showthread.php?t=2230826 and extract the boot.img file from the ZIP. Place the boot.img file into this directory: C:\Flashtool\x10flasher_lib where the fastboot.exe file is located.
5) Open a command window and type this while your phone is connected in fastboot mode:
Code:
cd C:\Flashtool\x10flasher_lib
- and then:
Code:
fastboot flash boot boot.img
- and then:
Code:
fastboot reboot
6) If you miss the chance to boot into recovery after that last step, reboot the phone once it has booted all the way and when you see the DooMKernel splash screen press (repeatedly, if necessary) the volume+ button. It should vibrate once. Once in recovery, just select to reboot system and it'll prompt whether you would like to root or not. Select the option to root and once it's done it should reboot.
Then just go and reconnect (in Android OS, not flash or fastboot modes) to Flashtool and install BusyBox, and download whichever SuperUser app you'd like from the Google Play Store and you're all set!

mattabyte said:
It's a lot more simple than it looks. Here's a slimmed-down version of the instructions:
Since you're already on the 253 update, you can skip numbers 1 & 2 from the other page and just start with numbers 1 & 2 below.
1) Download from this link the 0.9.10.2beta6 version of Flashtool: http://forum.xda-developers.com/showthread.php?t=2201189 and run the installer. Make sure to install to your computer's HDD root (ie; C:\Flashtool).
2) Make sure you have flashmode and fastboot drivers installed for your device. Easiest way to tell if they're done correctly is to open your Device Manager (in Windows), power off your phone, and plug it into a USB port in each of the modes and make sure no errors show up in the Device Manager.
3) Unlock your bootloader with the Flashtool. It'll have you first go into flashmode, and then prompt you to unplug and plug back into fastboot mode.
4) Download v07 of DooMKernel from this link: http://forum.xda-developers.com/showthread.php?t=2230826 and extract the boot.img file from the ZIP. Place the boot.img file into this directory: C:\Flashtool\x10flasher_lib where the fastboot.exe file is located.
5) Open a command window and type this while your phone is connected in fastboot mode:
Code:
cd C:\Flashtool\x10flasher_lib
- and then:
Code:
fastboot flash boot boot.img
- and then:
Code:
fastboot reboot
6) If you miss the chance to boot into recovery after that last step, reboot the phone once it has booted all the way and when you see the DooMKernel splash screen press (repeatedly, if necessary) the volume+ button. It should vibrate once. Once in recovery, just select to reboot system and it'll prompt whether you would like to root or not. Select the option to root and once it's done it should reboot.
Then just go and reconnect (in Android OS, not flash or fastboot modes) to Flashtool and install BusyBox, and download whichever SuperUser app you'd like from the Google Play Store and you're all set!
Click to expand...
Click to collapse
WOOOOOOW this is really an awesome reply
Well done and well organized
I will try this very soon and reply to you with the results
I really don't know how to thank you for this help , hope it works fine
Thank you again and again mate :good: :good: :good:

mahmoud.kunbaz said:
WOOOOOOW this is really an awesome reply
Well done and well organized
I will try this very soon and reply to you with the results
I really don't know how to thank you for this help , hope it works fine
Thank you again and again mate :good: :good: :good:
Click to expand...
Click to collapse
I am so sorry for these silly questions,
But I honestly couldn't understand how to perform step 6
and lastly how to reconnect to flash tool in android system????
Thanks a lot in advance

mahmoud.kunbaz said:
I am so sorry for these silly questions,
But I honestly couldn't understand how to perform step 6
and lastly how to reconnect to flash tool in android system????
Thanks a lot in advance
Click to expand...
Click to collapse
For step 6 just repeatedly press the VOLUME+ button after you reboot your phone, and it will vibrate once after you see the splash screen for the kernel. The light at the bottom should turn fuchsia or pinkish, and you'll know it's going to boot into recovery. Once there, just select to reboot and it'll ask you if you want to root.
The last part about connecting back into the Flashtool is simple. Just boot your phone normally after it's rooted, and once your phone is powered on and USB debugging is enabled then start the Flashtool and plug your phone into your computer with a USB cable.

mattabyte said:
For step 6 just repeatedly press the VOLUME+ button after you reboot your phone, and it will vibrate once after you see the splash screen for the kernel. The light at the bottom should turn fuchsia or pinkish, and you'll know it's going to boot into recovery. Once there, just select to reboot and it'll ask you if you want to root.
The last part about connecting back into the Flashtool is simple. Just boot your phone normally after it's rooted, and once your phone is powered on and USB debugging is enabled then start the Flashtool and plug your phone into your computer with a USB cable.
Click to expand...
Click to collapse
Everything has worked perfectly :victory:
I honestly don't know how to thank you
you did a great favor for me
May god bless you

i bricked my ZE551ML bad need help PLZ

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.

[Q] Possibly Softbricked Zenfone 2 after CyanogenMod 12.1 install

Hi guys, I have an issue with my Zenfone 2 (ZE551ML).
I flashed CyanogenMod 12.1 and everything was working fine. That is, until I decided I wanted to go back to stock ROM. That's when everything went wrong.
1) I went into recovery mode (using Power + Volume UP).
2) I wiped cache partition (probably my first mistake)
3) I restored to factory settings (possibly my second mistake)
4) After this I tried to flash the "recovery1.img" of the stock ROM I had.
5 ) That didn't work so I tried using ADB to flash different ".zip" files (all firmware downloaded from Asus website)
When that didn't work either, I abandoned and rebooted the phone. But it doesn't boot anymore.
It is stuck on the Asus screen and nothing happens.
Does anyone know if and how I can get out of this situation?
I must insist on the fact that I am only a novice. Until now I've only ever known iOS and have no knowledge whatsoever of how Android works.
I already posted my question here ("http://forum.xda-developers.com/general/xda-assist/possibly-softbricked-zenfone-2-t3248318") and was told I might want to try posting it here as well. I hope one of you can help me repair my mess !

Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.

shawnchalfant said:
Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.
Click to expand...
Click to collapse
Thanks for the reply. Do you have a link for the one click root with CWM Recovery ? Can't seem to find it... Also, when I connected my phone to the computer and opened oneclickroot (basic) it says my phone needs to have USB debugging activated (which it did).
I can't get into recovery mode anymore, the phone just loops back to fastboot with no error message.

You just need fast boot only. Look around the forum for the CWM root its here and esy to find.

shawnchalfant said:
You just need fast boot only. Look around the forum for the CWM root its here and esy to find.
Click to expand...
Click to collapse
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.

Boot into fastboot, Vol Up + Power, once it vibrates quickly press and hold volume down a few seconds. Fastboot should appear. Then run the batch file. Adb does not run in fastboot mode.

m3j said:
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.
Click to expand...
Click to collapse
there is still hope ... go for a lower version of recovery, boot (flash it in fastboot) and then keep the rom by keeping it in the external sd card renaming it to MOFDS_Update (i dont remember the name ). flashing should be done on its own...

search "Tutorial Upgrade / Downgrade / Unbrick Zenfone 2" in Asus ZenTalk. it helps for me

Thank you all for trying to help but I wasn't able to repair the phone.
I sent it back and by some miracle they accepted to give me my money back. Buying a new one now but I won't do anything stupid with it this time !

Zenfone 2 bricked. Cannot access Recovery Mode.

Hello All,
I would like to start by saying that I am a novice when it comes to rooting phones so ANY help received here will be greatly appreciated. I have come across a few people within the various forums who have a very similar issue to the one I am having, but nothing exact. Now to the point.
Phone: Zenfone 2 (Model: ZE551ML-23-4G64GN-BK) came unlocked from amazon.com
Carrier: Metro PCS.
PC used to root: Win 7 64 bit / AV: Avast Free.
Issue: About 1 month ago I rooted my phone. Last night I received a prompt to do an OTA update, and selected install. I realized after that I shouldn't have done that, but it was too late. My phone would not load past the black and white ASUS loading screen.
I then proceeded to do some research online, and try to "unbrick" my phone myself. I figured out how to hold the power button + volume up key, select Recovery Mode with the power key, and press power + volume up again to get into the Recovery Mode. I was following some instructions online that didn't really make sense, which led me to choosing Wipe Cache Partition. This didn't work, so I had to manually reboot the phone (Hold the power key, and turn it back on). From that point forward I have been unable to get back into the Recovery Mode. Once I get to the sleeping android with the red triange I have tried holding power + volume up (which got me into recovery mode the first time), power + volume down, power + both volume up and down, I've rebooted my phone several times to make sure I was doing this as soon as the little android appeared and nothing happens. The android just pulses in and out and nothing happens. This is the first of my many problems as I have never flashed a ROM before, and I am a novice. Also my PC does not recognize my phone at all at this point. I'm using the same cable and port that I always use when transferring files. The port has been tested with a tablet and iPhone, which works. My questions are as follows:
1. Am I screwed? lol.
2. Is there a way/trick to getting into recovery mode again?
3. Can I still unbrick my phone without getting into recovery mode? Is there something I can do with my phone connected to the PC perhaps?
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089

For anyone who may have found this thread I think I found a fix here. I will let you know after I test this if it works:
http:
//valuestuffz.blogspot.com
/2015/10/fix-zenfone-2
-stuck-in-recovery-wipe-cache-partition.html?m=1
Sorry. I had to break up the link in order to post it.

Clavin0089 said:
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
Click to expand...
Click to collapse
i was in same sit with a brick of sorts and used this guid to help me:
> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html *** I used this to go from the 168/174 ( 174 didnt fix issue that 168 caused ) back to 160
> http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html *** How to enter recovery if you dont know how
make sure the phone is plugged into a usb2 port and not a 3.0
what got me is when i installed adb, it put adb files in a default directory on my hdd, so i just copied the files to the folder where where i had all files at See below
i used the .160 file to restore my phone and it worked..
now if phone isnt detected yet, you may still need files. have you tried iSocUSB-Driver ?

I followed the steps outlined in the link:
http
://valuestuffz.blogspot.com/2015/10/fix-zenfone-2-stuck-in-recovery-wipe-cache-partition.html?m=1
And everything appeared to have gone smoothly, however, now my phone just loads, and will not enter the home screen. I just have that ASUS IN SEARCH OF INCREDIBLE screen now. I was able to get into the recovery mode, but it doesn't appear to have worked. I also received the "Permission denied" errors mentioned in the link. Any suggestions?
My phone is now detected by the PC for the record.

didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time

Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
I did push over 3 files, but when I downloaded the .160, it only had droidboot.img,and boot.img. I tried both .168 (Which may have been totally wrong, but had all 3 files) and .160 from the asus website where you can select firmware. I did the .160 most recently. I put the recovery.img, droidboot.img, and boot.img into the adb folder, and ran the following CMDs:
Fastboot erase cache
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
I then used adb sideload CMD to load the .160, and it reached 100% and said successful. I attached a screenshot of what the "permission denied" CMD looks like.

Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
Tonight after work I will try the links you suggested to me once more, and let you know the results. I sincerely appreciate all of your help here! Thank you very much!

anytime...
i never seen/encountered that error message before... try adb kill-server command if you run into any issues. when you start again it will load automaticaly... have you tried different usb ports? stay on usb2.0 when connected and try original oem cable that came with the phone. if you dont have it, try different micro-usb cables ( i had issues when i had my lg g3 being on a usb3 port, so i made sure mine was plugged in a 2.0 port )

Currently i am on beanstalk, and want to go back to stock.
I flashed the stock recovery via fastboot, but when i enter into Stock Recovery mode, it gives me Error icon.
The whole process is to flash the stock zip via sideload, but i am not able to enter the stock recovery.
The stock version i am trying to flash is 2.20.40.160.
I flashed all three files, Droidboot.img, recovery.img, boot.img.
And then turned the phone off, and now it is stuck on Asus screen. Urgent Help!!

btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file

Pu$$nBooT$ said:
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Click to expand...
Click to collapse
Yeah, i looked it up, power + volume up. That did it. Thanks!

np...