As I am not a kind of patient guy I sideloaded it too... No problem with locked bootloader. New version is nice especially launching with button press
It is said that you need your wach full stock (no root etc...) but the no status error is caused by something different, you need to update your adb to fix it. I recommend this installer, used it aswell:Do you need to have the stock kernel for this to work or can I do it with the custom kernel posted here in the forum? I tried doing it last night but kept getting an ADB error when trying to sideload (something about "error fault (no state)" or something like that).
Hi, thank you for the tutorial.Since the update process described here was a little bit cluttered (at least for me), here my brief description of the manual update of the OTA 5.1.1 update (Works at least for me on OSX 10.10)
Note: You must have at least version 1.0.32 of adb.
1. Power off Watch
2. Boot into Fastboot Mode (Press and Hold Power Button until the LG Screen appears, then quickly swipe from upper left to lower right)
3. Unlock Bootloader: fastboot oem unlock
4. Boot into Recovery mode (from Fastboot Menu on Watch)
5. select "update from dab"
6. flash update: adb sideload <zip name>
7. After successful flash, reboot straight into fastboot mode
8. Lock bootloader: fastboot oem lock
I hope this works
When I type and devices, I receive the message "list of devices attached". And nothing more.Unlocking bootloader is not mandatory... you can proceed directly...
You have to be in the update from adb menu in order for you computer to see adb interface, install driver and dectect the watch.
You can check if adb see your watch by typing : adb devices
You need to flash the zip file itself (no unzipping)
If you are not sure of what you are doing and don't want to waste much time you can wait the OTA for a few days...![]()
Before, I had the watch listed in the device manager, then no.Are you on recovery mode on the watch ?
Is it listed as "Android ADB interface"
Hi, thank you for the tutorial.
Can you help me?
When I try the adb sideload 9de320966ac906bf3e49314a97aab24e48a798bf.signed-lenok-LDZ22D-from-LWX49K.9de32096 (or .zip) I received the message "error: device not found" or "cannot read 9de320966ac906bf3e49314a97aab24e48a798bf.signed-lenok-LDZ22D-from-LWX49K.9de32096".
I appreciate if you can help me with this.
Thanks.
Damn, I feel so dumb n00b now... It was just that my watch was super low on battery and I just didn't have enough to even boot.... Which sucks! ??Ive sideloaded the OTA but my watch isn't booting now. It starts to boot, and then it powers off. Damn it! Dont know what to do. Also, I noticed it's getting quite hot while booting.
Ive tried a factory reset from recovery, no luck same happens... Any idea?
I'm in the same boat. Started at 91% charge but various attempts and dirty contacts drained my battery. Any chance the watch charges in the fastboot menu? :silly:Damn, I feel so dumb n00b now... It was just that my watch was super low on battery and I just didn't have enough to even boot.... Which sucks!
I've flashed phones so many times, never happened to me... I guess there always a first time.
Thanks God, it managed, I wonder how, to boot this time, and it's now charging!
Sent from my OnePlus One with Tapatalk
Apparently, yes.Any chance the watch charges in the fastboot menu? :silly:
hey im having same issue as you i get to 64% then it quits same error status 7, what do you mean you flashed the whole image can you help explain. thanks.just tried to sideload...
"EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:609689....." has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
:silly:
//EDIT: Nevermind... flashed the whole 5.1.1-image![]()
Hi, you need at least 1.0.32 ADB version, so download latest Android SDK zip and install "Android SDK Build-tools" and "Google USB Drivers", then put OTA update in same ADB and Fastboot folder (Eg: "platform-tools" under Android SDK decompressed zip), open terminal (or windows cmd) and navigate in "platform-tools" folder under Android SDK, then put Smartwatch in ADB mode, and in terminal (or windows cmd) writehey guys i dont know what i am doing wrong but when i try to sideload the update im getting
loading: 'update.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
serving: 'update.zip' (~0%) * failed to read command: cannot connect to daemon
adb kill-server
adb devices
adb sideload 9de320966ac906bf3e49314a97aab24e48a798bf.signed-lenok-LDZ22D-from-LWX49K.9de32096.zip

thanks i got it via ota todayHi, you need at least 1.0.32 ADB version, so download latest Android SDK zip and install "Android SDK Build-tools" and "Google USB Drivers", then put OTA update in same ADB and Fastboot folder (Eg: "platform-tools" under Android SDK decompressed zip), open terminal (or windows cmd) and navigate in "platform-tools" folder under Android SDK, then put Smartwatch in ADB mode, and in terminal (or windows cmd) write
thenCode:adb kill-server
Smartwatch appear in list, if doesn't appear, in Windows you need to install ADB Drivers.Code:adb devices
Finally write
and wait 100%...Code:adb sideload 9de320966ac906bf3e49314a97aab24e48a798bf.signed-lenok-LDZ22D-from-LWX49K.9de32096.zip
Now you have successfully installed Android Wear 5.1.1 on your brilliant LG G Watch R W110![]()
Put the watch in sideload mode from its recovery, and the PC should detect it and install any additional adb drivers required.I recently received the watch and it is on 4.4W1 and it still says System up to date. I am trying to manually update the watch, but I am getting stuck. When I am in recovery, my PC cannot see my watch in recovery resulting in "error:device not found" message.
Not that I think that there is anything associated with the carrier but the watch came from ATT.
Any help is appreciated.
Thanks in advance!
I did that and PC is not detecting the watch in that mode. I have tried two different PCsPut the watch in sideload mode from its recovery, and the PC should detect it and install any additional adb drivers required.