[ZenFone 2 Q&A, Help & Troubleshooting] nucleare:
Reply to topics that should be in a separate thread

To be sure that I understand you correctly: 1) You were able to bring your device back to life 2) It recovered back to Android Lollipop but you wanted to upgrade it to Marshmallow (Android 6.0) but when you tried to access the device with ADB/fastboot to flash the image, you can''t access recovery. 3) Therefore you'd like to know how you can upgrade it to Android 6.0

Is this correct? If I am understanding you correctly then I also experienced the same problem, but it's been quite some time since I overcame this so please feel free to interject if these are steps you've already attempted and failed to find success with:

1) Rather than try to flash the new OEM software with flashboot, instead take the current or previously used firmware and copy it to your Micro SD card (phone is on and transfer per MTP USB or simply use a card reader to load it onto the micro SD card and load microSD card into your Zenfone while it's off)

2) Either before or after it's transferred to a reliable micro SD card (avoid cheap imitation, go with a dependable name brand preferrable Class 10 or higher), then rename the .zip file to

[B]MOFD_SDUPDATE.zip[/B]

3) Boot up the device as if you were trying to enter recovery (holding down the volume up button... etc. etc. .) then as you do so, the device should automatically run the a command internally to apply the file update. No fastboot, no sideload, no adb commands need to be sent (nor should it be hooked up to the computer when booting into flashboot/recovery.)

Let me know if that works for you. And please note:

****Use the above steps with the SAME firmware version you recovered your phone to NOT the Marshmallow firmware you previously had before bricking your device but the same as the .img file version you used, or whatever version is displayed on your phone when you do boot it up. i.e. Presumably, If it was Lollipop, use a Lollipop firmware version. THEN, after successfully "updating" (but more like repairing since you're not actually going to a higher version number) the firmware,

then and only then

, do the same thing with the Marshmallow or Android 6.0 firmware you desire.

~***(It's worth noting that after applying the Lollipop firmware in the "manner of the manufacturer" as described above, you may be able to use normal OTA update if it existed in your region/country, because the MM or Marshmallow firmware update was not pushed OTA and was made optionally available through the Asus website (as far as I know from over a year ago and in the US)

****Firmware file must be on loaded onto an external Micro SD card,

NOT

the internal drive of the device and must be the original ZIP formwat, not .IMG

If this does not solve your issue and/or in the future should you have an issue that poses a new & different question, please start a new thread of your own describing your issue, if you have not yet already done so. This will better help you find a resolution by increasing the probability it is seen by those who may better assist you as well as avoids "bumping" an older thread with an unrelated reply that does not add to the discussion of the issue being addressed or described in the title. I only mention this as a gentle reminder of Rule #15 so please do not be offended by my saying this.

Aysuun, is this happening when you first connect with adb/flashboot and right away attempt to flash the partition table in an attempt to flash, OR is it following your entering these commands:

fastboot oem erase_osip_header
fastboot oem start_partitioning

If it is following entering the above commands, please let me know how the system responds to the above commands after being entered, a screenshot or log file will do.

-nucleare