Database Develop

How to update LG G WATCH R International Version to 5.0.1

I recently bought LG G Watch R international version and unfortunately its running on android 4.4 and iam unable to use some of the features such as Changing Watch Faces via my sasmsung galaxy note 4 which is running on android 5.0.1. Kindly help me out how can i update the watch to 5.0.1

I am having the same issue here,i just bought the watch yesterday and figures i can't change the face watch.
my verstion is 4.4w.1 or something like that
Also when i press system update in the settings it tells me it's up to date.
please help

Mine just popped up a notification about a system update being available all by it self. Never had to force one.

Doronibi said:
I am having the same issue here,i just bought the watch yesterday and figures i can't change the face watch.
my verstion is 4.4w.1 or something like that
Also when i press system update in the settings it tells me it's up to date.
please help
Click to expand...
Click to collapse
Same here, just got my yesterday and can't get the update to happen. Been looking around but haven't found a way to force it myself either.

Im stuck on 4.4W2 and not receiving an update...

Genna7 said:
Im stuck on 4.4W2 and not receiving an update...
Click to expand...
Click to collapse
at least you have a more advanced update..
I have spent half a day trying to installing a more advanced update manually and almost ruined my new watch with no success...
why their guides have so much missing info and couldn't find a proper video on how to update.
all i found is how to root my watch and that's it.
If some one could make/find a good tutorial on how to manually update could be nice

Doronibi said:
at least you have a more advanced update..
I have spent half a day trying to installing a more advanced update manually and almost ruined my new watch with no success...
why their guides have so much missing info and couldn't find a proper video on how to update.
all i found is how to root my watch and that's it.
If some one could make/find a good tutorial on how to manually update could be nice
Click to expand...
Click to collapse
Yes, i know your pain. But i cant change the faces too. I dont know if it's normal or not.

How to update LG G watch R from 4.4w.2 to 5.1.1
How to update LG G watch R from 4.4w.2 to 5.1.1
After many hours and some hair pulling I managed to do it. Give this a try, hope it helps. Cheers.
This was taken from several forums including XDA and i just placed it all in one place.
How to update LG G watch R from 4.4w.2 to 5.1.1
These are the steps I did to update my watch from 4.4w.2 to 5.1.1 please do them at your own risk. if your at 4.4w.1 just locate the .zip file for 4.4w.1 to 4.4w.2 and follow the below instructions.
Save all files downloaded below to “c:\Watch Update” then you can copy and paste the below instructions or just alter that path below to your own path.
Download ADB Installer
http://forum.xda-developers.com/show....php?t=2588979
Download the flash 5.0.1 recovery.img https://www.androidfilehost.com/?fid=95864024717071058
Download 5.0.1 Package
http://android.clients.google.com/pa...R.149e0c34.zip
Download 5.0.2 package http://android.clients.google.com/pa...P.69530b2c.zip
Download 5.1.1 package http://android.clients.google.com/pa...K.9de32096.zip
Setup
1. On Watch - Enable Developer Options: "OK Google" -> Settings -> about Device -> Tab Build Number 7 times -> go back to main Settings -> enter Developer Options -> enable ADB Debugging
2. Connect Watch to PC
3. Open phone and accept yes to debug mode
4. Check driver installed if not go to device manager, then right click watch > update driver software > browse my computer for driver software > let me pick from a list > android device > Android composite ADB interface > next > close
Update Watch time
Open a Windows Administrator Command Prompt
On PC From command prompt type:
Adb devices (check if you device is listed)
adb reboot bootloader
fastboot oem unlock (watch may reboot and require re-pairing if so just do so and run adb reboot bootloader again then do the next step)
fastboot flash recovery “c:\Watch Update\intersectRaven_GWR_5.0.1_stock_recovery.img ”
Reboot watch
Update from 4.4w.2 to 5.0.1
On PC From command prompt type:
adb reboot bootloader
On Watch – click > until “Recovery mode” is selected then hit “0”, then tap screen and swipe down until “apply update from ADB” is select then swipe right
On PC From command prompt type:
adb sideload “c:\Watch Update\149e0c34d0ab10d3e356d6301915dcc04552d9db.si gned-lenok-LWX48P-from-KNX01R.149e0c34.zip”
On Watch – when the watch displays “reboot system now” tap button to restart once done
Update from 5.0.1 to 5.0.2
On PC From command prompt type:
adb reboot bootloader
On Watch – click > until “Recovery mode” is selected then hit “0”, then tap screen and swipe down until “apply update from ADB” is select then swipe right
On PC From command prompt type:
adb sideload “c:\Watch Update\69530b2c7a4e8fc32b20b8d0bfa24b1b8930d1a0.si gned-lenok-LWX49K-from-LWX48P.69530b2c.zip”
On Watch – when the watch displays “reboot system now” tap button to restart once done
Update from 5.0.2 to 5.1.1
On PC From command prompt type:
adb reboot bootloader
On Watch- click > until “Recovery mode” is selected then hit “0”, then tap screen and swipe down until “apply update from ADB” is select then swipe right
On PC From command prompt type:
adb sideload “c:\Watch Update\69530b2c7a4e8fc32b20b8d0bfa24b1b8930d1a0.signed-lenok-LWX49K-from-LWX48P.69530b2c.zip”
On Watch – when the watch displays “reboot system now” tap button to restart once done
Final Step
On PC From command prompt type:
adb reboot bootloader
fastboot oem lock
On Watch - click > until “Power off” is selected then hit “0”
You have now updated to 5.1.1 Enjoy
---------- Post added at 10:07 PM ---------- Previous post was at 10:03 PM ----------
I will also add, once i was upgraded to 5.1.1 all of my other issue i.e. apps not working, couldn't load new watch face etc. went away. Cheers

Thanks dragonhsv!
That's a very good and clear set of instructions. I'll give this a go tonight.
I almost had it figured out but the stock recovery in 4.4w.1 doesnt allow adb sideload. I wasn't sure it was OK to jump ahead and use the 5.0.1 recovery.

How to update LG G watch R from 4.4w.1 to 5.1.1
I followed dragonhsv's instructions and was able to update from 4.4w.1 to 5.1.1.
Here are the additional steps I had to do.
The update file from 4.4w.1 to 4.4w.2 can be found here (Delta: KIW52H). Save it to the C:\Watch Update folder alongside the other downloads.
Follow dragonhsv's instructions down to and including:
fastboot flash recovery “c:\Watch Update\intersectRaven_GWR_5.0.1_stock_recovery.img ”​Reboot watch​
New steps
Update from 4.4w.1 to 4.4w.2
On PC From command prompt type:
adb reboot bootloader​
On Watch – click > until “Recovery mode” is selected then hit “0”, then tap screen and swipe down until “apply update from ADB” is select then swipe right
On PC From command prompt type:
adb sideload “c:\Watch Update\4beff7b6437440dceee842ca90bc23f51bb7b990.signed-lenok-KNX01R-from-KIW52H.4beff7b6”​(Note: you don't have to type the file location and name. You can simply drag the file into the command prompt window and it'll fill it all in for you.)
On Watch – when the watch displays “reboot system now” tap button to restart once done
This update will write a 4.4w.2 recovery and this doesn't seem to support adb sideload so we need to load the 5.0.1 recovery image again.
On PC From command prompt type:
adb reboot bootloader​
After the watch has loaded the bootloader type:
fastboot flash recovery “c:\Watch Update\intersectRaven_GWR_5.0.1_stock_recovery.img ”
Reboot watch​
After that you can use dragonhsv's instructions from "Update from 4.4w.2 to 5.0.1" to the end.
Thanks again to dragonhsv for taking the time to share these instructions.

I'm in the same boat as you guys. I recently got my replacement watch because the last one had screen issues. Now I'm on 4.4W.2 and no software updates in sight . The strange thing is that the gesture of raising the watch turns on the display, which if I remember correctly wasn't available on 4.4W.2.
The point of my post is that I think that the reason why our watches aren't getting OTA's is because LG "closed the doors" if you will in preparation of the "August" update ( http://phandroid.com/2015/07/12/exclusive-android-wear-interactive-watch-faces/ ). Originally the rumour was that the update would start on July 28th, then August 11th and now Derek Ross said he heard that the 18th is the correct date. So even though flashing the 5.1.1 update probably won't damage your watch (if you do it correctly), I think patience will bring you the same results, but with the latest software.

I have a international lg gwr and was able to upgrade the software to 5.1.1 when the ota update first came out.

I updated my watch manualy to 5.0.1 and now waiting for official update to 5.1.
But if you are on 4.4W1/2 you can use the how-to to update your recovery and then update your rom.
Recovery of 4.4 has a bug which wont let you side load the file. That's why you have to update it to 5.0.1 first.

Hi there !
I received my Lg G Watch R last week in V4.4...
When I ask for update the only answer I get was : "System already up to date".
Even after delete cache, uninstall android wear or wathever.
I didn't want to root my watch, so I've done what I've read somewhere : wait for an OTA.
And after 1 week, I finally get them : I say "them", because, in two days, I had 3 OTA...
Now, my watch is in V5.1.1
and it work fine !
Hope it'll help and reassure other users.

No luck in forcing the ota on my new watch and am not sure if I can go through the manual downloads and update it
... So I guess I'll have to wait till it arrives question is will it arrive ?
Recently bought this on amazon , its in software version 4.4w.1 ,when I try to update it says something went wrong , kept on trying nothing happens , I am from Maldives could it be because of the region I'm not being able to update it or is this a fake product BUILD#KIW52H.

???

Help anyone I was able to update my g watch r to 4.4W.2 from 4.4W.1 but after that I'm unsuccessful. Always end up with Error: Device (null) not found. I know that I've installed the drivers and I can command it via CMD to reboot bootloader/recovery. However, after that I can't sideload the next update. It's really frustrating.
EDIT: Managed to pull it off. Didn't reboot after flashing the recovery image.

MM Update

was just wondering : has anyone got the MM update already ?
cheers

OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
This next part is assuming you have ADB installed on your computer. If you don't, google how to install ADB first.
To sideload the update:
1. Enable Developer Options: Settings>About>Tab Build Number 7x
2. Go back to the Settings Menu
3. Go into Developer Options (All the way at the bottom, below About)
4. Enable USB Debugging
5. Go to wherever ADB is installed on your PC (For me, it is C:\Program Files (x86)\Android\android-sdk\platform-tools\)
6. Shift+Right Click inside the folder, but not on a file in the folder, then click "Open command window here"
7. Type "adb devices"
8. At this point, on your watch, it should pop up a dialog asking if you would like to authorize the connection. Hit Always.
9. Type “adb reboot recovery”
10. On your watch, tap the screen once, then swipe down until you're hovering on “apply update from ADB.” then swipe to the right.
11. In the command prompt on your PC type “adb sideload” followed by a single space then drag and drop the zip to the command prompt window then hit Enter.
12. It will now begin installing the update on your device. Whatever you do, do not disconnect your watch from the computer or close the command prompt window.
13. Depending on the situation, your watch may or may not reboot automatically. If it doesnt, after it is done installing the update and goes back to the main Recovery menu, swipe to the right on "Reboot system now."
Click to expand...
Click to collapse

BTW I highly recommend forgetting your watch from the Android Wear app on your phone/tablet and factory resetting your watch after updating.
After I installed it, settings on the watch were funky, like it offering phone options which we shouldn't have without a speaker, and it wouldn't install the new Wear Messenger app that is included in the newest version of Google Messenger.

Dudash said:
OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
Click to expand...
Click to collapse
cool, thanks, have just installed it !
cheers

Dudash said:
OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
This next part is assuming you have ADB installed on your computer. If you don't, google how to install ADB first and since the zip file doesn't say which "version-from-version" it is for like they normally do, for example LCA43-from-LDZ22J, I'd recommend being on LCA43 before sideloading the update.
Click to expand...
Click to collapse
Someone correct me if I am wrong, but that OTA update is a full image unlike all previous updates. So, it should work as long as you have partition in place. Also, it looks like they added "new" features to the stock recovery. It has more options now.

aligatro2010 said:
Someone correct me if I am wrong, but that OTA update is a full image unlike all previous updates. So, it should work as long as you have partition in place. Also, it looks like they added "new" features to the stock recovery. It has more options now.
Click to expand...
Click to collapse
It is possible that you could flash it from an earlier build and end up with the same system. If you want to be a guinea pig for other people, be my guest
I was merely stating the safest way to not end up with a watch that won't go past the boot logo.
Also, since MM updates for other watches include the "version-from-version" text in the name of the update.zip, I assumed they just forgot to put it in the Gear Live .zip.

Dudash said:
It is possible that you could flash it from an earlier build and end up with the same system. If you want to be a guinea pig for other people, be my guest
I was merely stating the safest way to not end up with a watch that won't go past the boot logo.
Also, since MM updates for other watches include the "version-from-version" text in the name of the update.zip, I assumed they just forgot to put it in the Gear Live .zip.
Click to expand...
Click to collapse
Nope, they didn't forget, but its just a full image. I was able to sideload it to my watch after formatting the partitions(so no prev firmware at all).

Does anyone know if root is available already ?
Cheers !
Enviado desde mi Galaxy Nexus mediante Tapatalk

thagringo said:
Does anyone know if root is available already ?
Cheers !
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Haven't tried it on the latest version, but I think you can root it by installing latest supersu. Just need to remove the apk that comes with it, as it will crash on launch.

One thing I don't like about the new update is how they changed the "Simple" and "Incremental" watchfaces.
They used to have a daytime color (light blue), an evening color (yellowish-orange), and a nighttime color (dark blue/purple).
Now the colors/images are updated (more clouds) but there isn't an evening color anymore and it doesn't change to the nighttime one until like 10pm.
Kind of a strain on the eyes to see a light blue background after the sun goes down.
I'm curious why they removed the evening color.

thagringo said:
was just wondering : has anyone got the MM update already ?
cheers
Click to expand...
Click to collapse
Mine updated automatically. I left it charging and when I came back, there it was, waiting to be installed.
One thing though: it won't show starred contacts (favorites) anymore, which it did before the update, and I can't figure out how to fix it.
Anyone else notice this?

I got it. So far so good
Sent from my SM-G935P using XDA-Developers mobile app

Downgrade & Root LG G4 LS991 / SPRINT ONLY ZVA-ZV6

Verified Downgraded from ZVA to ZV6 with full root access
LS991 Sprint Only.
QUICK GUIDE & TESTING
(Please read the entire guide before trying anything.)
I nor anyone at XDA is responsible for anything that may happen to your device.
Simply, by taking incentive to change the stock setup provided by the manufacturer for your device; you assume all responsibility for anything that happens.
download LGUP
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
(Thanks to shakeyabooti)
download LS991ZV6_00.zip and extract to get .tot file with winrar/7zip or any other unzipping program
http://downloads.codefi.re/autoprime/LG/LG_G4/LS991/LS991ZV6/LS991ZV6_00.zip (or google/xda search for mirrors) (Thanks to autoprime)
download LGROOT
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
(Thanks to Unjustified Dev)
download LG Drivers
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 (or google)
(Thanks to Unjustified Dev)
download rootedsystem.ls991.zip and extract to get .img file with winrar/7zip or any other unzipping program
http://forum.xda-developers.com/sprint-g4/general/zv6-root-success-t3205963/page3
(scroll down to parin11's post. #29 and thank you to both parin11 and mswlogo)
-install drivers
-enable oem unlock in developer settings
-plug device in as charge only, switch to mtp to verify drivers are working correctly, then disconnect
--if on mtp then switch to charge only to verify drivers are working correctly, then disconnect
-enable usb debugging
-reconnect and drivers auto install
-disconnect after 2 minutes.
--while you wait;
-for LGUP extract and install _dll version then the second msi.
-for LGROOT extract to a folder to keep things organized
-remove the back cover of your device and leave it off for access to battery pulls.
-power off device
-hold volume up key and plug in your device and keep holding the volume down key until it passes the screen that says download mode.
-open LGUP
-make sure UPGRADE is checked/has a little circle/bullet point
-click in the empty space directly to the right of where it says BIN with the checkmark
-3 dots will appear to the right of the program in the same row that says BIN; which is your browse option
-navigate to LS991ZV6_00.tot and select
-reconfirm your UPGRADE option is checked
-press start and allow the device to fully complete the process.
-your device will boot to the loading screen right before showing the android desktop and "freeze"
-In most if not all new flash scenarios; your device will not boot up until a factory restore and clear cache is done.
-To do this you must simply remove the battery and usb cable from your device AFTER it has hung on the logo for about 3 minutes / 180 seconds.
(Most new devices average a first time boot of up to 150 seconds maximum to be considered fully "loaded")
-With the battery and cable removed; hold the power and volume DOWN button together at the same time.
-insert the battery while holding these buttons together and just wait while holding them and you will see it says booting into recovery.
-once your in the recovery you use the power key to select and the volume keys to navigate.
-navigate to factory restore/reset hit the power button, navigate to "yes" out of all the "no's" and hit the power button again
-it will say its complete and either ask you to go back reboot or return to menu. RETURN TO THE MENU, do not boot up yet.
-Once returned to the main menu you will see it says clear cache. Select and press yes and now you can select reboot; or return to menu then reboot.
Your device will be on ZV6 stock and fully booted after this.
Now this is where it gets kind of odd because my device never actually loaded the rootedsystemls991.img file nor did I run a root script
when attempting to flash it with the steps listed in the other root guides BUT i followed this guide from step one to step 9 (and outlined continuing through the guide)
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
this allowed all the necessary rooting files to be in the places necessary to execute the root but I did one extra step
I did an adb.exe push rootedsystem.ls991.img /data/local/tmp command as well while the device was on the home screen.
This was so I could basically emulate the command listed by |Unjustified Dev| as it also states to do in the ZV5 guide.
So this is what I did,
-After my device booted up and loaded to the home screen on stock zv6, I opened the LGROOT folder
-held shift and clicked "open command prompt here"
-when cmd opened I ran the following command
adb.exe devices
This allowed me to see that my device was connected to the PC with its generated serial number.
-then i ran the following command
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
-After this I applied the command to push the .img file to the same location. This was the "emulated command" I spoke of.
adb.exe push rootedsystem.LS991.ZV6.img /data/local/tmp
-I then added the .img file directly to the Internal Storage / Stock Phone MTP storage
-Afterwards I simply powered off my device, removed the usb cable, held the volume up button, then plugged it back in still holding the volume button until
the text download mode was gone again; and no this is not a timing thing im just saying that again incase anyone forgot how to get into download mode. lol.
-I then ran the ports.bat file included in LGROOT to find the COM port drivers.
-Followed up with this command
Send_Command.exe \\.\COM8 (<--Replace number here with the COM port listed for the "DIAG" portion of the device.)
-Now, still in download mode I executed this command about three times with no avail.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
(Which by the way I had the file in both the MTP side of root and in the data/local/tmp)
or you could change it to /data/local/tmp/ like
dd if=/data/local/tmp/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This would possibly solve the issue I was having. So you would have root now.
THIS PART REQUIRES TESTING.
BUT continue reading you'll be shocked.
sidenote:
They state that all you have to do is put the .img file into the root of your Internal Storage / Stock Phone MTP storage
and run the command in download mode but this failed when I tried to execute it.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
The command above was the command they listed to be able to restore the device from stock to stock with root access. Please note I tried this command while the phone was turned on in debugging with enable oem unlock on, while in download mode and while in recovery mode all with debugging and enable oem unlock checked with either no response / device detected, or attempts causing the command prompt to show the # symbol after a few seconds of executing the line above which shouldn't happen,
since the size of the file is 4GB... The ENTIRE SYSTEM PARITION. -_-. There is a considerable amount of hangtime here is what I'm saying.
If the dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0 command worked for you then great, boot up and enjoy root! BUT.
For those who didnt have luck doing so with the command that failed me above, for some odd reason after pushing both the SuperSU bundle and the entire .img file to /data/local/tmp/ with the files in the internal storage /data/media/0/ as well
trying to only execute the command for the .img (/media/0/ not /local/tmp/) | (not the "fixed" command") and NOT for the SuperSU
eg.
-This was for the image which was the only one I used. (USED)
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This was for root only which I did not touch. (NOT USED)
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
-This caused the device to simply show the # sign almost immediately as I spoke of above.
-I typed in LEAVE and the device booted back up.
-The odd thing I'm speaking about is when I turned the device back on it showed that SuperSU was installed and was requesting to be "updated".
-I chose normal and it asked for a reboot. Rebooted started back up and it asked for root access when I clicked on it.
-Granted and successful.
-Went to the playstore.
-It said update next to SuperSU which was even odder.
-Clicked it and updated it and it got the latest version, asked for one more reboot, started back up, then I opened the app. Everything was normal.
-Downloaded root checker basic, titanium backup, and greenify immediately.
All passed with flying colors.
-There is an error that pops up in titanium backup regarding adding underscores or slashes into modified file directories for backup purposes assumed but
opening greenify ended up picking up this issue and requesting to fix it.
Why not right?
-Heh. It worked.
I have never experienced this type of latency within programming so this is extremely odd and without executing the SuperSU script command or,
a sucessful flash of the .img it just seems too odd, but; there you have it! All of the mods / developers working on this device I would like to hear
your insight on this.
So you have two options. Follow what I did or test the command with /data/local/tmp/ and try your luck flashing stock with root again or just run the root script on stock instead of trying to flash from stock to stock rooted.
Thank you and enjoy your root!
P.S. I didn't end up experiencing this issue since it works perfectly but in the event that SuperSU does not install after trying to flash the .img and getting
the 2 second delay with the # sign appearing immediately and rebooting after 3 attempts I would have personally tested the original adb SuperSU script command recommended for the ZV5 users
which was listed above and is
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
And for the love of your device. Don't try to update your device from an older version using this method. Ayeeeyiyiy
I will re-test what I stated and make a completely organized guide and video for everyone.
I just wanted to let you all know now to assist the entire community in understanding this device's root process a little more.

Will this work with brand new phone?
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.

wow, thanks!
Thanks for all your hard work. This phone has been one of my best and the only thing missing has been root, etc. Chewing over your instructions and thoughts. My confidence level is not quite there to pull the trigger, but i'm getting close. Hoping this is a promising method for those of us on Sprint ZVA. I will continue to do research and watch this thread. Thanks so much for your time, tips and expertise.

brpaaron said:
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
As long as its not been updated to zvb. Antirollback implemented on zvb

Still running zv6
I am still running zv6 and never updated. Do I need to update to downgrade to root or can I just skip to after the downgrade?

i am running zv9 i can not stock zv6

I have ZVC can i downgrade to ZV6?
LG G4 LS991.
LG G3 D850 ROM Fulmics 6.6
Recovery TWRP v2.8.7.0 bumped

LS991 ZVD
Hi there does anyone know whether or not it will work on the ls991 zvd update??? Sprint variant

Ls 991 ZVD
Will this method work on ls991 zvd i havent found anything on it

Expo6810 said:
Will this method work on ls991 zvd i havent found anything on it
Click to expand...
Click to collapse
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower

TheMadScientist420 said:
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
Click to expand...
Click to collapse
Is there anything i can do for my zvd

Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as far as i know. nothing
new root methods and tweaks come out everyday.
all the good devs as far as i know have stopped developing g4 and moved on due to the locked bootloader d other issues
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
a root method has been exposed on the g5
intime it may come for the g4 also but not adapted rite now

Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
Right now i have ZVC software version can i downgrade zv6????

hawzsth said:
Right now i have ZVC software version can i downgrade zv6????
Click to expand...
Click to collapse
no u will brick

TheMadScientist420 said:
no u will brick
Click to expand...
Click to collapse
its already brick any solution...... now its show 9008 no power on ...

hawzsth said:
its already brick any solution...... now its show 9008 no power on ...
Click to expand...
Click to collapse
octoplus box with jtags the only fix
thats a hardbrick
---------- Post added at 08:30 AM ---------- Previous post was at 08:29 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as of rite now no

If I downgrade my zva will it allow me to sim unlock it

Somebody know if can downgrade ZVI to another version

Pls any update on locked bootloader?

Thank you!
Just learned here enough. Thank you!
I just head through UsU thread after reading this; Respectively thanks for the post again! ??

BACK TO WEAR 1.5 FROM 2.0(COMPLETE GUIDE) and ELIMINATE THE PERSISTENT UPDATE NOTIFIC

Hello everyone,
Some Italian guys asked me for this guide because they did not find anything complete and detailed. Thanks to the XDA members' publications I could put together the pieces and write it down. I apologize for my English but I'm not very good, especially for technical terms. I hope I can help someone.
BACK TO ANDROID WEAR 1.5 FROM 2.0(COMPLETE GUIDE)
1. Download the software ADB installer 1.4.3 from this link compatible with Windows 10: http://uploadboy.com/tsp1bpbe9gtj/1082/zip
From here you can download an older version 1.3 for Windows 7: https://forum.xda-developers.com/showthread.php?t=2588979
2. Open the .exe file already downloaded with administrator privileges and follow the installation procedure to install the drivers
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
4. Insert the files into the folder that created the ADB Installer that is normally the path "c:\adb"
5. Download tool "WinDroid Toolkit" from here (some antivirus swapping it for threat and eliminating it, in this case turn it off momentarily) :
https://forum.xda-developers.com/devdb/project/dl/?id=17244
6. Start with administrator privileges "WinDroid Toolkit"
7. Follow the instructions for installing the drivers required by the tool and select the model of the clock
8. Activate developer options on the clock: (Settings> System) by clicking "build number" repeatedly until unlocking the menu that will be among the main options
9. In the developer options menu, activate the "debug ADB"
10. Turn off the clock
11. With the clock off, hold down the physical key and in the meantime repeatedly tap your finger on the screen from minute 55 to 25 until the watch has entered the mode fastboot
12. Connect the clock to PC usb port via cable and charging base
13. Now "WinDroid Tool" should recognize the clock and below you will see that the "Offline" script becomes "Fatboot"
14. Click on "Unlock Bootloader" and proceed by accepting the various message from the tool
15. A confirmation message appears on the clock display, click on the right arrow and then on the central button to continue
Now the bootloader of the clock is unlocked and we can continue to install the three previously downloaded files. Close "Windroid Tool"
16. In the "adb" folder at the "c:\adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
17. In the newly opened window, give the following commands one at a time and wait for each one to complete the operation:
1) fastboot -w
2) fastboot flash boot M1D65H_boot.img
3) fastboot flash recovery M1D65H_recovery.img
4) fastboot flash system M1D65H_system.img
Finally, to restart the clock, use the following command:
5) fastboot reboot
N.B. Before pairing the watch on the cellphone again remove the link, inside the Android wear app, clock and uninstall and reinstall the app.
Finished!
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
1. Download the .zip file containing the custom recovery and root to this address:
http://www.mediafire.com/file/qllnc7...+R+Utility.zip
2. Unzip the .zip file and insert the "twrp-3.0.0-0-lenok+squashfs.img" file into the "c:\adb" folder
3. In the Clock Developer Options menu, activate the "Debug ADB" (to enable them to follow the procedure above)
4. Connect the clock to the pc via the cable and charging base
5. Open "WinDroid Tool", go to the "Commands" tab and click on "push file". Select the file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete and disconnect the clock from the PC.
6. Turn off the clock
7. With the clock off, hold down the physical key and in the meantime crawl your finger repeatedly on the screen from minute 55 to minute 25 until the clock has entered fastboot mode
8. Connect the clock to the pc
9. In the "adb" folder at the "c: \ adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
10. In the window just open, give the following command and wait for the completion:
-) fastboot flash recovery twrp-3.0.0-0-lenok+squashfs.img
11. From the clock using the arrows and the confirmation button down to start the "recovery mode"
12. Accept the warning message and after selecting the language click on "install" and select, with the touchscreen, the .zip file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete.
13. Restart the system and wait for the clock to turn on.
14. In the previously opened command window, give the following commands one at a time and wait for them to complete and complete:
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Finished!

Many thanks riccardo423
I have managed to rollback my lg g watch r to android wear 1.5 AND suppress those pesky update notifications using your guide. I noticed your mediafire link to the custom recovery file is broken. There is an alternative download at http://www.mediafire.com/file/qllnc77jtdqxtdl/Lg+Watch+R+Utility.zip (posted by Dettofatto in a previous xda thread) which also contains the two additional required files.
Luigino1

Hello, thanks for inserting a working link. I've modified the text of the guide by entering your link. I'm glad to have helped you.
Riccardo423

For step 3 if I click the link it says the post does not exist. Anyway here's where I found the images if anyone needs it: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
BTW: Thank you for the complete guide, step by step, i was able to go back to 1.5 and disable the persistent notification thank you very much!

Hi, thank you for inserting the working link. I'm glad to have helped you. Riccardo423

After downgrade from 2.0 to 1.5, I don't received Facebook messenger notifications on watch. Other notifications work fine (Gmail, sms etc). Anyone know what's going on?

Hi I have never had this problem I think I can depend on your Facebook app. Which version of Facebook and which cell phone?

Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates

szczurx said:
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
Click to expand...
Click to collapse
You've already tried uninstalling and reinstalling the app?
The app wear permissions are unlocked for notifications?

Android wear app reinstalled twice. Even made watch factory reset. On Phone in settings/apps, Android Wear app have permissions for everything possible

Thanks for this Riccardo ( or grazie, from a fellow italian )!
Can't believe I managed to do the entire procedure without making a mess of it, lol. Everything appears to be working again, I'm so happy! Really hated AW 2.0. Hope the notification does not come back, I'll keep an eye out for it in the coming days.

hello, can anyone answer me why these commands dont work
pm disable com.google.android.gsf/.update.SystemUpdateService
and why superSu crashes on watch

Thank you Riccardo423 for great manual, it works great for my watch. No AW2 anymore!

riccardo423 said:
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
charging base
Click to expand...
Click to collapse
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?

LionheartSilver said:
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
Click to expand...
Click to collapse
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.

pidobeuliou said:
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
Click to expand...
Click to collapse
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?

LionheartSilver said:
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
Click to expand...
Click to collapse
Nothing specific, just installed the basic factory image + root . I have installed about 16 apps (including Watchmaker with a quite "sophisticated" watchface, wear messenger, WearMail, Wear Battery stats, Feel the Wear, Runtastic, ...) but mainly I have deactivated Google Fit which is a true battery killer app on both the Smartwatch and the Smartphone!.

mediafire link is dead (twrp) - please, reupload it!

Thanks so much for this, it worked perfectly! So great to have my watch back!

Hi, I have problem connecting in ADB mode to PC - when I plug in craddle nothing is happening Win10 not even play a sound, not trying to find drivers etc. Is it connected with new version NXG47C/LENOKZ22b ??
In fastboot mode there is green "secure boot" enabled, lock state - locked and bootloader in Z22b version. Is it possible to connect ADB in this case? Im stucked witn AW2 and there is nothing I can do for now Please help.

[GUIDE] How to revert back to Android Wear 1.5

How to revert back to Android Wear 1.5
Flashing stock AW1.5 build:
- Unlock your bootloader
- Reboot into FASTBOOT MODE
- Download STOCK ROM MWG68 images
- via adb type commands:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase userdata
fastboot reboot
How to block OTA to AW 2.0
- adb shell
- pm disable com.google.android.gms/.update.SystemUpdateService
- pm disable com.google.android.gsf/.update.SystemUpdateService
- exit

ingbrzy said:
How to block OTA to AW 2.0
- adb reboot bootloader
- adb shell
- pm disable com.google.android.gms/.update.SystemUpdateService
- pm disable com.google.android.gsf/.update.SystemUpdateService
- exit
Click to expand...
Click to collapse
This probably won't work, you don't have adb shell available in bootloader, and while booted up you can't use the pm disable command without root..

Maxr1998 said:
This probably won't work, you don't have adb shell available in bootloader, and while booted up you can't use the pm disable command without root..
Click to expand...
Click to collapse
true.. it will be more easier to boot TWRP, disable dm-verify and edit build.prop line
Code:
ro.build.id=MWG68
to
Code:
ro.build.id=MWG68_something

Thanks, i had to revert because i started getting random reboots since 2.0... Now I'mm gonna wait and see if it continues.
BTW, i think you forgot "fastboot oem lock" after downgrading.

after following the guide and flashing aw 1.5 I get an error saying zenwatch manager has stopped and then the reboots, and so on.
any ideas what went wrong and how can I fix this?

asafgolan said:
after following the guide and flashing aw 1.5 I get an error saying zenwatch manager has stopped and then the reboots, and so on.
any ideas what went wrong and how can I fix this?
Click to expand...
Click to collapse
make factory reset.. unpair and reset in the settings..

ingbrzy said:
make factory reset.. unpair and reset in the settings..
Click to expand...
Click to collapse
Thanks, that did the trick!

I'm having to much issues with 2.0 and overall I hate the update, so this guide is very appreciated, yet my watch is brand new and I don't want to mess things up, can you please do a complete guide with links to all the software needed and stuff? This seems to be for those who are already in the "knowing how to flash the FW", I believe I need to unlock the bootloader to in order to revert to AW 1.5 right? Or isn't that needed?
Thanks for the help @ingbrzy

Any chance one of you can help with this issue?
https://forum.xda-developers.com/zenwatch-3/how-to/fastboot-recovery-getting-g-co-abh-t3637403

Ok, I've been doing some reading and I'm almost ready to flash the watch back to 1.5, but just in case I'll make here the full list of what I've done/about to do, please check if all is correct:
1 - Download and place the Platform-tools folder from here on a easy access place to access on your PC
1.b - Edith Path Variable as shown here just be make things easier
2 - Enable USB debugging on watch by going to the watch Settings/System/About and pressing a few times on the Build Number
2.B - To check if the connection is well done between watch and PC open a command line on Windows and write "adb devices", it should show the watch SN listed
3 - Unlock the bootloader!
3.1 - Reboot to fastload (via *adb command* (You do this by opening a command prompt window from within windows itself) "adb reboot bootloader")
3.2 - type command "fastboot oem unlock"
4 - Download STOCK ROM MWG68 images
From here is where I have doubts, DON'T FOLLOW THESE INSTRUCTIONS until someone more experienced confirms if it's correct or not
5 - Place the files unziped: system.img / boot.img and recovery.img downloaded on point 4 inside the platform-tools folder in point 1
6 - Open a command prompt window and past the following code ***DOUBT*** Full code at once as shown bellow or line by line followed by enter??
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase userdata
fastboot reboot
7 - make factory reset on watch by... "unpair and reset" in the watch settings...
7.1 - Re-lock bootloader is advised? How and why to do it?
8 - Don't install AW 2.0 again?
@ingbrzy is this correct or am I missing something?

Thank you for this thread :good:
I'm back on 1.5 it's better for me in this moment...
My watch understand me again :laugh::laugh::laugh:
Edit:
I have two questions:
How I lock bootloader?
How to block Ota? Easiest way?
Thank you very much

Android Wear Updates
Does anyone know if leaving the bootloader unlocked prevents android wear 2.0 OTA
updates or any other updates?
Thanks, have a great day!

Misterjunky said:
Does anyone know if leaving the bootloader unlocked prevents android wear 2.0 OTA
updates or any other updates?
Thanks, have a great day!
Click to expand...
Click to collapse
No, I have unlocked bootloader and after night my watch download AW2.0 update

TWRP Recovery
I wonder if installing TWRP recovery might prevent Android Wear 2.0 OTA update?
I am on Android Wear 1.5 and do not want to update or get notifications to update.
Thanks,
---------- Post added at 01:02 AM ---------- Previous post was at 12:47 AM ----------
Hoffmanns said:
No, I have unlocked bootloader and after night my watch download AW2.0 update
Click to expand...
Click to collapse
Have you or anyone found a way to delete the AW2.0 update file from the watch?
Thanks!

Misterjunky said:
Have you or anyone found a way to delete the AW2.0 update file from the watch?
Thanks!
Click to expand...
Click to collapse
In this moment NO
Factory reset in recovery may help...
But I need block OTA update first

re: Build Prop file
ingbrzy said:
true.. it will be more easier to boot TWRP, disable dm-verify and edit build.prop line
Code:
ro.build.id=MWG68
to
Code:
ro.build.id=MWG68_something
Click to expand...
Click to collapse
@ingbrzy
Is it possible to use adb to pull and push the build-prop
file from /system to /sdcard or some other place where it would be
accessible making it easy to edit without rooting the watch?
(preferably someplace in Windows 10 or in my S7 Edge phone?)
If it's possible, could you please post the adb commands to pull and push the file?
Thanks in advance, have a great day!

I may go back as well. Aw 2.0 hasn't been a totally smooth experience even after wiping data and clearing cache. Sometimes it'll stutter and I will end up clearing all notifications instead of going one by one

Someone, please explain how to block OTA update to 2.0.... Please

re: Block OTA notifications
avchd said:
Someone, please explain how to block OTA update to 2.0.... Please
Click to expand...
Click to collapse
The only way I found to block updates and notifications for updates
is to ROOT the watch.
I rooted my watch 3 days ago after really trying to like this AW 2.0
but after all was said and done I just could not see any reason to
keep the new AW 2.0.
The only two things which we good and nice in AW 2.0 was the
really good looking and smooth/fast scrolling of the app drawer
and the nicer notifications which AW 2.0 has.
But everything else in AW 2.0 is really crappy way too crappy for me.
If you are interested in rooting and twrping your watch here is the link
with step by step instructions and download links for the rom.
Android Wear v1.5 pre-rooted and twrp'ed custom rom:
https://forum.xda-developers.com/zenwatch-3/development/rom-asus-zenwatch-3-swift-t3537340
The main problem with keeping AW 1.5 without flashing
a custom rom is all those OTA notifications you get over
and over again without a way to disable the notifications.
Come on guys, do we really need a Google Play store in our watch... LOL
Also the only way a watch can be called "stand-alone" is if it has a sim card.
Good luck, have a great day!

Even though I knew what I was doing, I was on a new computer so I "followed" your instructions because I've never seen anyone write it out so thoroughly from no ADB at all, and glad to say you pretty much nailed it through that. Except step 2, it's more like a whole bunch of times. Don't know why you've gone un-thanked and un-replied!
Step 5 is unnecessary because of the method of setting up ADB with the path variable described in 1b (if you don't do step 1b, then the files need to be in the platform-tools folder). You just need to get to the same folder in the command prompt as the files. The command prompt by default opens to C:\Users\pyroguysf (or whatever your own name is), which is where your downloads folder is located by default, so if you unzip the files to your downloads folder, type "cd Downloads" to navigate into your downloads folder. Once you're in the same folder as the img files you unzipped, then run the commands listed in step 6, each line, one at a time. After each one, it should show the progress, and make sure it says completed not failed (I forget the exact words used) before going to the next. If it fails that's a separate topic, but it shouldn't. I always advise a factory reset after any significant software changes. Re-locking the bootloader is for security's sake, and while not 100% necessary, is highly recommended, unless you plan to be changing the software again anytime soon (I see a modified version in this thread that supposedly has OTA's disabled I might try, but this is slightly more advanced). Re-locking is basically the reverse of step 3 - reboot into bootloader with "adb reboot bootloader" and then once it's there "fastboot oem lock" instead of unlock.
Edit: That's right, you get the message upon boot for a while that your device can't be checked for corruption when it's unlocked. Also, my watch won't boot now, so I'm going to try a few more things... That's why I waited until the weekend.
Edit2: Re-unzipped the files (md5 was fine), did boot, recovery, then system, and did "fastboot format userdata" instead of "fastboot erase userdata" in step 6.
Edit3: Edited the quote from MK2ever below with what worked for me.
MK24ever said:
Ok, I've been doing some reading and I'm almost ready to flash the watch back to 1.5, but just in case I'll make here the full list of what I've done/about to do, please check if all is correct:
1 - Download and place the Platform-tools folder from here on a easy access place to access on your PC
1.b - Edit Path Variable as shown here just be make things easier
2 - Enable USB debugging on watch by going to the watch Settings/System/About and pressing repeatedly on the Build Number until it says "you are a developer!"
2A. Go to Settings>Developer Options and turn on "ADB Debugging" and plug your watch cradle into your computer and wait until windows installs drivers (Win 7 found them automatically for me)
2.B - To check if the connection is well done between watch and PC open a command line on Windows and write "adb devices", it should show the watch SN listed
2.C - when your watch asks to allow connections, tap "always allow from this computer"
3 - Unlock the bootloader!
3.1 - Reboot to fastboot (via *adb command* (You do this by opening a command prompt window from within windows itself) "adb reboot bootloader")
3.2 - wait until the watch says "fastboot mode" then type command "fastboot oem unlock"
4 - Download STOCK ROM MWG68 images
5 - Place the unzipped files system.img boot.img and recovery.img into your downloads folder.
6 - Open a command prompt window and type "cd Downloads" to get to navigate into your downloads folder (Windows 7 default, 8 and 10 too I think) and then enter the following commands one at a time waiting for it to give a "completed" message before moving on
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
7 - make factory reset on watch by... "unpair and reset" in the watch settings...
7.1 - Re-lock bootloader is advised. Repeat steps 2 through 3.1 and then "fastboot oem lock"
8 - Don't install AW 2.0 again?
Click to expand...
Click to collapse