[GUIDE] workaround for invisiblek v6 adb bug - LG G Watch

Due to this new update if you ever factory reset your watch while on invisiblek v6/6.1 kernel you will lose the ability to do anything with adb as the watch no longer looks for your pc's vendor keys and those not create its own.
This guide will show you how to regain access to your watch once again.
1. Download the recovery from my watch root guide here and if you want root the watch
2.reboot to bootloader by turning off watch then swiping top left to bottom right on the screen as soon as you put the watch on to charge
3. once there just flash the recovery with
Code:
fastboot flash recovery recovery.img
and boot into recovery mode by selecting it in the bootloader
4.On your PC go to C:\Users\namehere\.android\ and copy the file named adbkey.pub and rename it to "adb_keys"
5.move this file to your watch via adb in the recovery like so:
Code:
adb push adb_keys /data/misc/adb/
Reboot to system (ignore OS not installed, just squashfs bug) and voila you now have adb on your watch again!

---

Huh? I've factory reset my watch several times, and I had never used adb on it until the last time it went stupid and I tried using ADB to force it to re-pair bluetooth.. Worked just fine, no fuss.

---

khaytsus said:
Huh? I've factory reset my watch several times, and I had never used adb on it until the last time it went stupid and I tried using ADB to force it to re-pair bluetooth.. Worked just fine, no fuss.
Click to expand...
Click to collapse
Ok cool i just made this guide for all the people who are affected by this bug myself included

---

Xmaster24 said:
Ok cool i just made this guide for all the people who are affected by this bug myself included
Click to expand...
Click to collapse
{
"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"
}

---

Well add 5 more guys I got 3 thanks here and another two on another help request

---

Fantastic!! Thank you. I have been pulling my hair out trying to figure out why my watch was all of a sudden "unauthorized" after updating. to 6.0.1

---

Guys just realised the whole cause of this when I flashed everything stock for the new update. It turns out that the actual cause of the problem was invisiblek's kernel and not the new system itself. sorry for any inconvenience this may have caused you.

---

(deleted)

---

New script
Made a windows batch script for ease of use, inspired by the linux version made by dynamic donkey

---

Xmaster24 said:
Made a windows batch script for ease of use, inspired by the linux version made by dynamic donkey
Click to expand...
Click to collapse
Thanks a bunch! Will be sure to give you credit on the thread.

---

I can't get the watch recognized by ADB either booted or in recovery. Fastboot works though? Strange.

---

GohanBurner said:
I can't get the watch recognized by ADB either booted or in recovery. Fastboot works though? Strange.
Click to expand...
Click to collapse
Make sure you have the adb driver installed, fastboot uses a separate driver and it does not require authentication either

---

KevinX8 said:
Due to this new update if you ever factory reset your watch while on invisiblek v6/6.1 kernel you will lose the ability to do anything with adb as the watch no longer looks for your pc's vendor keys and those not create its own.
This guide will show you how to regain access to your watch once again.
1. Download the recovery from my watch root guide here and if you want root the watch
2.reboot to bootloader by turning off watch then swiping top left to bottom right on the screen as soon as you put the watch on to charge
3. once there just flash the recovery with
Code:
fastboot flash recovery recovery.img
and boot into recovery mode by selecting it in the bootloader
4.On your PC go to C:\Users\namehere\.android\ and copy the file named adbkey.pub and rename it to "adb_keys"
5.move this file to your watch via adb in the recovery like so:
Code:
adb push adb_keys /data/misc/adb/
Reboot to system (ignore OS not installed, just squashfs bug) and voila you now have adb on your watch again!
Click to expand...
Click to collapse
i knew it has something to do with adbkey