[ZenFone 2 General] Level99:
Testing Results:

adb reboot bootloader:

Sends device to white screen boot logo, then to bootloader. See faux info (Serial number is not my serial, 0123456789ABCDEF or whatever), says FASTBOOT CMD WAITING..., followed by Unlock Successfully. Reboot in 5 seconds. Reboots in five seconds, goes back to white boot logo, proceeds to boot normally.

Keypress Bootloader (single instance):

Phone is cold booting using Power+Vol Up key combination. As soon as the phone vibrates, power button is unpressed while Vol Up continues to be pressed through the white boot logo. After the logo flashes white a second time, enters bootloader. See faux info (Serial number is not my serial, 0123456789ABCDEF or whatever), says FASTBOOT CMD WAITING..., followed by Unlock Successfully. Reboot in 5 seconds. Reboots in five seconds, goes back to white boot logo, proceeds to boot normally.

Keypress Bootloader (multi instance):

Phone is cold booting using Power+Vol Up key combination. As soon as the phone vibrates, power button is unpressed while Vol Up continues to be pressed through the white boot logo. After the logo flashes white a second time, enters bootloader. See faux info (Serial number is not my serial, 0123456789ABCDEF or whatever), says FASTBOOT CMD WAITING..., followed by Unlock Successfully. Reboot in 5 seconds. As soon as phone reboots, I press Vol Up. Phone vibrates again, goes back into bootloader, says FASTBOOT CMD WAITING..., followed by Unlock Successfully. Reboot in 5 seconds. This cycle will repeat forever if continued.

Keypress Bootloader (Vol Up Interruption):

Phone is cold booting using Power+Vol Up key combination. As soon as the phone vibrates, power button is unpressed while Vol Up continues to be pressed through the white boot logo. After the logo flashes white a second time, enters bootloader. As SOON as bootloader is entered, I press Vol Up a few times. Either on this boot or on a second bootloader loop (using Vol Up keypress), bootloader will load and right after a brief FASTBOOT CMD WAITING..., it will switch to show my actual serial number and display the message RESULT: FAIL(can not mount the necessary partition). From here, I am not forced into a 5 second reboot. The following fastboot tests were performed in the bootloader in this state:

fastboot devices: shows my serial number and fastboot next to it.

fastboot getvar all:

(bootloader) max-download-size: 536870912

(bootloader) version-bootloader: 2.0

(bootloader) kernel: droidboot

(bootloader) product: moorefield

all:

finished. total time: 0.140s

fastboot boot ZF2CM.img (this is a renamed CM for the ZF2 Z00A):

downloading 'boot.img'...

FAILED (data transfer failure (Unknown error))

finished. total time: 5.100s

fastboot flash recovery ZF2TWRP.img:

sending 'recovery' (15094 KB)...

FAILED (command write failed (No such device or address))

finished. total time: 0.010s

I am unable to test recovery flashing via ADB as I did not have root when I bootloader unlocked and I am unable to get root now that fastboot is acting up. See below. Every attempt to do a command with fastboot that modifies anything at all on the target device fails. So, in effect, the bootloader is unlocked and fastboot is broken.

target reported max download size of 536870912 bytes

sending '/system/bin/resize2fs' (6 KB)...

FAILED (data transfer failure (Unknown error))

finished. total time: 5.160s

sending '/system/bin/tune2fs' (1386 KB)...

FAILED (command write failed (No such device or address))

finished. total time: 0.030s

sending '/system/bin/partlink' (2940 KB)...

FAILED (command write failed (No such device or address))

finished. total time: 0.050s

...

FAILED (command write failed (Unknown error))

finished. total time: 5.030s

sending '/system/bin/logcat' (3 KB)...

FAILED (command write failed (No such device or address))

finished. total time: 0.040s

...

FAILED (command write failed (Unknown error))

finished. total time: 5.030s

'