WI501Q Stuck with locked bootloader - Button does not work - Asus ZenWatch 2

Hi guys,
I just got a Zenwatch 2 WI501Q Sparrow,
I had some issues with calls on my phone and decided to update the firmware, but something went wrong during the flashing.
After that, the watch will keep rebooting every 10 seconds, unless i swipe to get into Fastboot mode.
Fastboot works and i can send commands from prompt, but whenever i try to unlock it, in order to be able to reflash, the unlock screen does not respond to pressing the button.
I know the button is working, because it was working before flashing, and holding it for 9 seconds turrns the watch off, but at the lock screen, there´s no effect in pressing it, short or long press, unles is long enough to turn off, but in that case, when reboot, it remains locked.
In this scenario, is there anything that i could try to recover my watch? Or did I killed the poor little guy?
Image that failed to flash was "Google-sparrow-img-M6E69Z-signed", but i also have files of "Google-sparrow-img-LCA49B-signed" ans factory image "Factory_V4_15_1_19_sparrow-eng_20151222"

---

Use the fastboot image provided here if you ever get it working: https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3601596
Also I don't even recall that it asks for a button press tho the last time I unlocked mine was about 7 months ago haha Can you take a photo and upload it? Maybe I can help.

---

EpicLPer said:
Use the fastboot image provided here if you ever get it working: https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3601596
Also I don't even recall that it asks for a button press tho the last time I unlocked mine was about 7 months ago haha Can you take a photo and upload it? Maybe I can help.
Click to expand...
Click to collapse
When I use the command [fastboot oem unlock], the device goes to the following screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That´s where i get stuck, because it should unlock by long pressing the button, but nothing is happening here.
Like I said, no image can be flashed due to the LOCKED state.
Is there any way to make the device select the Unlock option, by sending some command from console?
For the system image, as I said before, I have ASUS original firmware files
"Google-sparrow-img-M6E69Z-signed"
"Google-sparrow-img-LCA49B-signed"
"Factory_V4_15_1_19_sparrow-eng_20151222"
You may check all from the link below:
https://drive.google.com/drive/folders/0B2Ru4ATp1lY0cXhhTnpsVHF0bkU
Any help on this will be welcome.

---

JoseBatista said:
When I use the command [fastboot oem unlock], the device goes to the following screen:
That´s where i get stuck, because it should unlock by long pressing the button, but nothing is happening here.
Like I said, no image can be flashed due to the LOCKED state.
Is there any way to make the device select the Unlock option, by sending some command from console?
For the system image, as I said before, I have ASUS original firmware files
"Google-sparrow-img-M6E69Z-signed"
"Google-sparrow-img-LCA49B-signed"
"Factory_V4_15_1_19_sparrow-eng_20151222"
You may check all from the link below:
https://drive.google.com/drive/folders/0B2Ru4ATp1lY0cXhhTnpsVHF0bkU
Any help on this will be welcome.
Click to expand...
Click to collapse
That is super weird...
Maybe try "fastboot -w" to format all userdata on the watch, last bet. And then update the watch the normal way, maybe they fixed something in the bootloader for later versions.

---

EpicLPer said:
That is super weird...
Maybe try "fastboot -w" to format all userdata on the watch, last bet. And then update the watch the normal way, maybe they fixed something in the bootloader for later versions.
Click to expand...
Click to collapse
Nothing.
[fastboot -w] requires the device to be unlocked first.
The command gisves me the following:
Creating filesystem with parameters:
Size: 2759831552
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 10527
Label:
Blocks: 673787
Block groups: 21
Reserved block group size: 167
Created filesystem with 11/168672 inodes and 22128/673787 blocks
target reported max download size of 63963136 bytes
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
erasing 'userdata'...
(bootloader) Device is locked.
(bootloader) Please unlock device first!
FAILED (remote failure)
finished. total time: 0.011s
I also have tried
[fastboot flash bootloader bootloader.img]
[fastboot flash recovery recovery.img]
[fastboot flash system system.img]
[fastboot flash boot boot.img]
Any flash commands require unlock in order to work.
I did [fastboot oem device-info] and that´s the info that came up:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Debug Uart Disabled!
(bootloader) ASUS Dongle authorized: false
(bootloader) Sparrow
(bootloader) APQ_8026 - V1
(bootloader) eMMC=HYNIX-4G-1-748000
(bootloader) CPU_RV=108040e1
(bootloader) SB=Y
OKAY [ 0.020s]
finished. total time: 0.021s
I´m reaching the conclusion that what I would need is some way to command the unlock straight from the console, without having to confirm in the device.
If there´s no such command, nor any workaround to this, then i´m thinking I may be fully dead.

---

JoseBatista said:
Nothing.
[fastboot -w] requires the device to be unlocked first.
The command gisves me the following:
Creating filesystem with parameters:
Size: 2759831552
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 10527
Label:
Blocks: 673787
Block groups: 21
Reserved block group size: 167
Created filesystem with 11/168672 inodes and 22128/673787 blocks
target reported max download size of 63963136 bytes
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
erasing 'userdata'...
(bootloader) Device is locked.
(bootloader) Please unlock device first!
FAILED (remote failure)
finished. total time: 0.011s
I also have tried
[fastboot flash bootloader bootloader.img]
[fastboot flash recovery recovery.img]
[fastboot flash system system.img]
[fastboot flash boot boot.img]
Any flash commands require unlock in order to work.
I did [fastboot oem device-info] and that´s the info that came up:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Debug Uart Disabled!
(bootloader) ASUS Dongle authorized: false
(bootloader) Sparrow
(bootloader) APQ_8026 - V1
(bootloader) eMMC=HYNIX-4G-1-748000
(bootloader) CPU_RV=108040e1
(bootloader) SB=Y
OKAY [ 0.020s]
finished. total time: 0.021s
I´m reaching the conclusion that what I would need is some way to command the unlock straight from the console, without having to confirm in the device.
If there´s no such command, nor any workaround to this, then i´m thinking I may be fully dead.
Click to expand...
Click to collapse
Even "fastboot format userdata" won't work? I never thought they'd be locked down when the bootloader is locked...
Can you try to boot up TWRP via "fastboot boot TWRP...img"? Should be somewhere in the Original Android Development section here. I know for a fact that you can boot TWRP while locked since I did it and tried to make an image from partitions which f*cked them up then lol... managed to recover tho
Anyways, try that and in TWRP choose to wipe the data then.