yashsingh1/xdaforums huggingface dataset:
[Asus ZenWatch 3] MikaelG:
Hi guys,

I have a ZenWatch 2 and want to revert back to Android Wear 1.5 and based on everything I read in this thread, I think that I will be fine doing so (I have a link to the correct dump) but the only thing that keeps me from doing so is that I don't see an easy way to prevent the 2.0 update... In the original post, it seems that the steps will not work, and the second suggestion seems a bit complicated because it is done via TWRP and I'm not familiar with this, and don't know where to find the good file for the ZW2.

Can you please advise if there is any other solution without TWRP and root, and if not, can you please detail the process for an beginner/intermediate user?

Thank you in advance!
[Asus ZenWatch 3] Misterjunky:
Block / Disable OTA Updates and Notifications for OTA Updates

I have spent many many hours trying to hunt google for a sure way to block/disable any firmware

updates and those persistent OTA notifications for the Android Wear 2.0 Zenwatch 3 update after

I installed / downgraded to the good old Android Wear 1.5 firmware.

Finally I have found a sure way to do it!

Please note: this procedure will work on any android wear watch.

You will need to either boot into TWRP or install TWRP

in your watch before you can do any of this.

Don't forget to MOUNT SYSTEM in TWRP before you

use the ADB commands below.

Be sure to enable adb debugging at developer options

in your watch before doing any of this.

Here it is, it's easy IF you know how to use ADB.

To disable OTA updates and OTA notifications do this:

adb shell

cd /cache/

echo "" > update.zip

chattr +i update.zip

Reboot the watch.

Here is the download link for the 1 byte update.zip file (don't try to unzip it):

https://www.dropbox.com/s/0qvmjqz9w5l882t/update.zip?dl=

copy or push this 1 byte update.zip into the /cache folder in the

root of your watch BEFORE using the ADB commands above.

Once you have finished doing this successfully you will no longer

get notifications or ota updates. ROOT IS NOT REQUIRED.

If you decide you want notifications and updates at a future time

then do this:

adb shell

cd /cache/

chattr -i update.zip

rm update.zip

Reboot the watch

PLEASE NOTE:

Everything in the above information assumes that you

have already downgraded to Android Wear 1.5 and

your watch is currently working properly.

The above information will NOT downgrade your firmware,

it will only disable ota updates and ota notifications.

Good luck, have a great day!
[Asus ZenWatch 3] nmdang:
There're steps I did to prevent OTA for my watch (root required):

*** revert steps ***

./fastboot devices

./fastboot oem unlock

fastboot flash system system.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img

*** root steps ***

./fastboot oem unlock

./fastboot boot recovery_swift-3.1.0-0.img

./adb push root_watch.zip /sdcard

./fastboot oem lock

*** disable OTA steps (after rooted, we have to enable adb debugging at developer options) ***

./adb shell

su

pm disable com.google.android.gms/.update.SystemUpdateService

pm disable com.google.android.gsf/.update.SystemUpdateService

exit

*** Links ***

Recovery twrp: https://xdaforums.com/zenwatch-3/development/recovery-unofficial-twrp-3-0-2-0-touch-t3528478

Root file: https://docs.google.com/a/thanhdo.e...=0BwxryTxXnpbKbDQ3WlJDeVIzWm8&export=download
[Asus ZenWatch 3] Boateys:
My watch is shot

I have attempted this and followed all directions. The watch never boots past the "Device software can't be checked for corruption" notice. It either boots into recovery or just reboots again until it gets to recovery. I installed TWRP to check if I can see what the problem is. I am unable to mount /data. Can anyone shed any light on this?
[Asus ZenWatch 3] Misterjunky:
Is your watch a Zenwatch 3 or a Zenwatch 2 ?

Also why is it that after searching my watch for those 2 systemupdate

files names I never could find any files even close to those filenames?

Where are those 2 files located in the watch?

Thanks for the info, have a great day!
[Asus ZenWatch 3] nmdang:
My watch is Zenwatch 3. What "2 system update file names" do you mean? You mean pm disable com.google.android.gms/.update.SystemUpdateService and pm disable com.google.android.gsf/.update.SystemUpdateService? They are not really 2 files. They are just commands to disable system services for OTA updating of the watch. But you have to type "su" before using those commands. It means that you have to root your watch. Other files like recovery_swift-3.1.0-0.img or, system.img, .. *.img, root_watch.zip should be stored in the computer folder where fastboot and adb are put. After you call "./adb push root_watch.zip /sdcard". root_watch.zip will be stored to your watch to be ready for rooting.
[Asus ZenWatch 3] Misterjunky:
re: disable OTA updates and notifications

Ok, I will try it again,... my watch is already rooted, that's no problem.

But I did do the adb shell and su and there was a "#" charactor meaning the watch was rooted properly

and yet issuing those two commands systemupdateservice gave me some errors,, forgot exactly what it was.

Thanks for letting me know that those were not files and that's why I never did find them.

I will try it again though.

Thanks, have a great day!
[Asus ZenWatch 3] asafgolan:
I was able to flash AW 1.5 successfully but I don't seem to understand how to disable the OTA.

Any chance for a more detailed guide?
[Asus ZenWatch 3] Misterjunky:
re: Android Wear 1.5 rom.

Did you flash the 3 IMG files in FASTBOOT or did you

flash the excellent rootable custom Android Wear 1.5 rom? (which is 1 zip file)

Here is how to disable updates and notifications about the 2.0 update:

Please note: This only works with a rooted rom, if your watch is not

rooted then the following will not work.

*** disable OTA steps (after rooted, we have to enable adb debugging at developer options) ***

./adb shell

su

pm disable com.google.android.gms/.update.SystemUpdateService

pm disable com.google.android.gsf/.update.SystemUpdateService

exit

If you are interested in flashing the 1.5 rooted custom rom then here

is the link with full instructions on how to do it.

This following link also contains download links for the two files which

are required. One is the 1.5 rom and the other is the rooting file.

https://xdaforums.com/zenwatch-3/development/rom-asus-zenwatch-3-swift-t3537340

The custom rom is a lot smoother and way less laggy than the stock android wear 1.5.

It's very easy to to do.

Have a great day...
[Asus ZenWatch 3] asafgolan:
I flashed the 3 files in fastboot.

I'll give that custom rom a try, thanks!
[Asus ZenWatch 3] mkengel:
Ota update notification

I'm doing something wrong

This is what I get:

C:\adb>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

~ # [6n cd /cache/

/cache # [6n echo "" > update.zip

/cache # [6n chattr +i update.zip

Or from your other post:

C:\Users\Mike\Desktop\ADB_Fastboot_Windows>adb shell

adb server is out of date. killing...

* daemon started successfully *

~ # [6ncd /cache/

cd /cache/

/cache # [6nchattr -i update.zip

chattr -i update.zip

/cache # [6nrm update.zip

rm update.zip

NO LUCK!

Can you give me an idea of what is going on?

Thanks for share. :D
[Asus ZenWatch 3] cushcalc:
Shortcomings of AW 2.0

I did the revert to 1.5, then let it go to 2.0 again because I thought I was rooted and the OTA wouldn't stick but it did. One thing worked that wasn't before - InstaWeather watch faces.

But it seems like on 2.0, the watch is frequently losing its bluetooth connection to phone. I don't remember that happening on 1.5.

Also it seems wasteful/redundant that left swipes and right swipes both take you to watchface change screen.

Many things seem to take extra steps to complete, compared to 1.5.

So I am going to revert again, and root, and try to stay on 1.5!
[Asus ZenWatch 3] cushcalc:
custom ROM for ZenWatch 2? or 3?

<redacted>
[Asus ZenWatch 3] cushcalc:
Didn't work for me.

But perhaps Will work if add command "su" after getting into shell, before executing other commands. (?) I say this after the other method recommended, using PM disable, wouldn't work until executing "su" after getting into shell (as recommended by [MENTION=4715550]GTDarthYoda[/MENTION])
[Asus ZenWatch 3] Hrishi135:
Android 1.5 downgrade

Hello, i am hating this android 2.0 update for zenwatch 3 and want to downgrade badly ... Many have posted the procedure nicely in this forum but as i have not done anything like this before i am scared to do it as a small mistake can make my watch non working... So can anyone please post a video of the procedure in detail so amateurs like me can do it with confidance... Thanks in advance

update: thanks to this thread i have successfully downgraded to 1.5 and my watch is back to being great...yhank u guys. but facing few issues.. hope u guys can guide me

1. i see a red sign on zenwatch manager in watch.. on clicking it tells me to download zenwatch manager 3.0 . but it ia allready installed on my phone.. tried resyncing apps from android wear app but same problem.

2. cant find gmaps anywhere on watch though its installed on phone. voice commands to navigate say something went wrong.

( using nexus 6p running android 8.0)
[Asus ZenWatch 3] WaxysDargle:
in the instructions for disabling updates, the first two commands need to be:

adb shell

su

then disable the packages. doesn't seem to work without the "su"
[Asus ZenWatch 3] avchd:
Please, someone, just post the entire procedure.

All these commands, "su", "mu", "flu"... Are so confusing
[Asus ZenWatch 3] BIGWORM:
Would definitely advise you read up on how to run ADB before you attempt ANYTHING with ADB. You easily brick anything you're sending commands to.
[Asus ZenWatch 3] Coltonbyu:
may have bricked it

I have had issues with my zenwatch 3 being crazy slow on android wear 2.0, and i read some possible solutions..

I also have an issue where whenever i turn my watch on it says "device software cannot be checked for corruption" and it makes it take an additional 10-15 seconds to boot up. This has been on the watch since i got it (i bought used and the bootloader was already unlocked, if thats why its doing that. When going through forums I also saw mention for disabling dm verity and wondered if that would get rid of that annoying screen.

I wanted to see if i could remove the zenfit stuff, cause i saw that some users claimed speed improvements, so i flashed twrp, and when i booted in i accidentally said to allow modifications (even though now i see that people say not too). I didnt make any changes while in here, but thought that might be important to state. In the instructions to remove zenfit i again saw to disable dm verity, so i moved onto that.

I then connected through adb and ran the command fastboot oem disable_dm_verity, but that didnt seem to do anything. I then ran the command "adb reboot "dm-verity enforcing" which i dont think was a good one to run, and i wonder if caused my issue. When i tried to boot back into twrp it would boot to a dead android.

I decided at this point that instead of screwing things up further, i would just flash to AW 1.5 and hope for speed improvement there. I downloaded the files, and through fastboot flashed the stock 1.5 boot, system, and recovery. using this thread https://xdaforums.com/zen...-boot-t3535589

i rebooted the device and it went to the android wear screen and loaded for a while, and then to the upgrading android screen. when it got to step 7 it went back to the aw loading animation and then attempted to boot up and gave an error "unfortunately process android.process.acore has stopped" and started all over again trying to upgrade android and then getting to this point and failing. I then downloaded the images for stock 2.0 and flashed and got the same exact error.

I then tried to flash twrp again, and now if i try to flash 1.5 or 2.0 it just goes to a dead android screen. I can boot into twrp still with the boot adb command

I want to try flashing 1.5 or 2.0 through trwp, but my watch will not mount/connect at mtp to my PC while at twrp for some reason...

Any ideas or solutions? how can i flash everything straight back to default. Including whatever i may have done to the dm verity?

Please help
[Asus ZenWatch 3] csrow:
I got tired of AW 2.0 losing sync and asking to connect the watch again time after time.

So, I down graded to 1.5 which worked fine but could not stop the OTA updates. I tried the 'chattr' setting to +i. That didn't work. Tried setting the permission using pm but pm was not found.

As a last step, I installed the custom ROM based on MWG68 odexed. After the start up, I used the build prop editor of Root Essential to change the build name from MWG68 to MWR68_hold.

That seems to work. When I try to force the system update, it tries but does not complete.

So for me, this is a good solution to have a rooted custom ver1.5 based ROM with few extra helpful apps.
[Asus ZenWatch 3] Misterjunky:
re: downgrade to v1.5 Android Wear

I think I will do the same thing and downgrade to v1.5 too.

But I don't want to do it unless I am absolutly sure that by editing the build-prop the watch will no longer

notify me about the the 2.0 ota update AND that the watch will NOT download the update.zip file into

the watch's /cache folder without me even knowing it that the file is being downloaded.

If the watch still downloads the file without my permission it wastes over 50% of the free user space

in the watch....... So please check your free user space in internal sdcard using the AIDA64 app from

the play store. If I use the Android Wear 1.5 the watch automatically sends/downloads the 2.0 OTA file

a few hours or even the next day without me notifiying me at all.

After the 2.0 ota is done downloading into my watch it does NOT automatically install the ota but it sends

a notification telling me that it's ready to install.

So how long has it been since you edited the build-prop file? was in more than a couple days hopefully?

Also have you checked your free user memory using the AIDA64 app which gives you all the watch's

information including used and free space in its internal sdcard?

Thanks, please let me know.

Have a great day!
[Asus ZenWatch 3] csrow:
Well, I was golden for two days but this morning the update downloaded and upgraded back to V2.0.

So far, chattr doesn't work and changing the build ID doesn't work.

So this afternoon I am trying the last option of using the pm command to disable the update service.

Getting this last option done is a bit of work so if it works, I will do a write up the exact steps needed to go from V2.0 down to custome ROM v1.5 with OTA disabled.

I will let you know in 2 to 3 days to see if the watch remain in V1.5.

Fingers crossed.
[Asus ZenWatch 3] Misterjunky:
re: notifications

Okay, thanks... And good luck with it.
[Asus ZenWatch 3] Misterjunky:
re: excellent instructions

Excellent easy to follow instructions!

Now just wait 3-4 days to see if it truly works!

Forgot to ask, but is the custom rom the deodexed or odex version?

Good luck, have a great day!
[Asus ZenWatch 3] csrow:
(I went with the odex version just to stay closer to the stock version.)

It's been 3 mornings with no updates or downloads so I think the fix is good. I tried forcing the software update multiple times but the watch just times out and goes back to the normal screen. It will remain in V 1.5 until I change the settings back to enabled.

I'm really enjoying the smoothness of V 1.5. The notifications show up instantly; no more losing the connection; quicker app start; and good battery life. Makes the watch joy to use again.

I'm not a heavy watch user but for me going from 7 AM to 11 PM, I end up with around 40% charge left at the end of the day.
[Asus ZenWatch 3] TurboFool:
(quote shrunk to save space)

You're a lifesaver! I feel like I'm back at home now with 1.5. This is the first time in history I've ever downgraded ANY OS. It feels so weird doing it. But 2.0 was so slow, and had such horrible battery life that I just couldn't stand it anymore. I liked a lot of what they tried to do with it, and a few things they succeeded at, but I'm very happy to be back on 1.5. Your guide made that way, way easier.
[Asus ZenWatch 3] csrow:
Glad it worked out for you.

I've using V1.5 since when I wrote the guide and I can't believe how much better it is than V2

Apps load faster, battery lasts longer, notifications are immediate, and watch never asks me to re-link the device. I don't miss any features of V 2.0

Google assistant is almost instantaneous and now it's useful.

Enjoy.
[Asus ZenWatch 3] Misterjunky:
re: downgrading to android wear 1.5

[MENTION=699288]csrow[/MENTION]

Before you disabled notifications and the download of the update

was the custom 1.5 rom you were using rooted when you gave the

adb commands? and would the adb commands still work if the v1.5

rom was not rooted?

Thanks, have a great day!
[Asus ZenWatch 3] csrow:
The custom ROM comes rooted.

I don't think adb su command will work if ROM is not rooted and plus I believe package manager utility is not in the standard ROM.

You can just try it with your current V2.0 ROM. Go into adb shell and issue a PM command.
[Asus ZenWatch 3] Misterjunky:
re: v1.5 custom rooted rom

[MENTION=699288]csrow[/MENTION]

Okay, thanks...

Also... (sorry to change the subject)

Do you happen to know know if it makes any difference flashing superSU.zip

using the adb sideload command or using twrp to flash it?

Thanks, have a great day!
[Asus ZenWatch 3] csrow:
I've never sideloaded using adb so I couldn't tell you. I've always have used twrp.
[Asus ZenWatch 3] TurboFool:
Crap. Just received an update notification.
[Asus ZenWatch 3] csrow:
I also started seeing the OTA update notification today. As far as I can tell, there is no downloaded update zip file. Even if you try to update nothing happens.

I just need to figure out a way to get rid of the notification.

[MENTION=4438613]nmdang[/MENTION] any ideas?
[Asus ZenWatch 3] csrow:
Figured out how to get rid of the OTA notification

[MENTION=3516441]Misterjunky[/MENTION] [MENTION=4438613]nmdang[/MENTION]

It took me a while to figure out why I was getting a OTA message suddently.

So it happened on 12/9, Google Play Service got updated on the watch which wiped out the previous disable setting.

So the fix is to set the disable flag once more for Google Play Service.

1) adb shell

2) su

3) pm disable com.google.android.gms/.update.SystemUpdateService

4) exit

5) exit

6) Using Root Essentials app on the watch, go ahead and clear the cache and data for Google Play Service.

Reboot the watch and the OTA message will be gone. It will take sometime for the phone to reconnect to the watch but it will be back to normal.
[Asus ZenWatch 3] TurboFool:
I'm going to have to try it again later, but on the first try the notification came right back after a reboot.
[Asus ZenWatch 3] csrow:
Did you clear the data? If not, it will show up again because the bit is already set.

Use the Root Essentials / Apps to find Google Play Services. Then after selecting, go down to the Clear Data and Clear Cache buttons to clear both.

It's the Google Play service and not the Google Play Store.
[Asus ZenWatch 3] TurboFool:
I'm dumb. Your instructions were explicitly clear, but I missed step 6 entirely anyway. Message disappeared as soon as I completed that last step. I'm about five minutes past the reboot, though, and I'm not yet getting any notifications on the watch, and the apps don't seem to be communicating. I tried disconnecting my watch from the phone side (not unpairing) and then closing and reopening the app, and now the app wants to setup my watch as though from scratch. Which I'm afraid will start this cycle from scratch...

EDIT: Eventually through a combination of restarting the app, cycling Airplane mode on the watch, and letting the app think it was setting up a new watch, I got them to communicate properly without a full reset. So we seem to be back in business.
[Asus ZenWatch 3] csrow:
Yes, it takes some time but the watch and the phone will sync back up. Just need to restart the phone and the watch and then wait a bit.
[Asus ZenWatch 3] en0203:
Hi, I would like to downgrade my zw3 to 1.5. However, i would like to keep the keyboard. Is it possible to sideload aw2.0 keyboard to 1.5? Thank you.
[Asus ZenWatch 3] csrow:
You can side load the keyboard but I do not know of a way to enable it as an input method. Version 1.5 does not support native keyboards.
[Asus ZenWatch 3] TurboFool:
You cannot. The keyboard relies on the OS being designed for it, and 1.5 is not.
[Asus ZenWatch 3] en0203:
Can you try to install appfour messaging and email apps? I read some can use the keyboard via these apps after they sideload the google ime. I do not have 1.5 to try.

I read from here

https://www.reddit.com/r/AndroidWear/comments/5xi9jp/help_swipe_keyboard_on_wear_15/

Thank you.

---------- Post added at 08:59 AM ---------- Previous post was at 08:49 AM ----------

Also, does the following work?

https://xdaforums.com/moto-360/general/minuum-keyboard-android-wear-t2871609

The adb command given in the above link seems to be the command needed to activate any ime but need to find out ime service name. The steps are as follow:

1. Open [Debug] mode on your android wear device.

2. connect your wear device to a computer via USB.

3. Open a command line window, and navigate to ADB directory.

4. using this command to install your signed IME apk. "adb install ime.apk"

5. activate your input method. "adb shell ime enable com.example.xxx/.yourInputServiceName"

6. set your ime as default. "adb shell ime set com.example.xxx/.yourInputServiceName"

It will be great if we can sideload aw2's google keyboard from https://www.apkmirror.com/apk/google-inc/gboard-the-google-keyboard-android-wear/gboard-the-google-keyboard-android-wear-1-0-1-release/gboard-google-keyboard-1-0-1-android-apk-download/ and activate it as ime using adb command! I just do not know what service name to use.

Can someone please try with keyboards which the service name is known on your 1.5? mine is running 2.0. Thank you so much!

---------- Post added at 09:16 AM ---------- Previous post was at 08:59 AM ----------

Further study from https://stackoverflow.com/questions/15253983/change-the-default-android-keyboard-using-adb-or-java-code shows that we may be able to find out the IME ID after we install the ime and activate it with the following method:

$ adb shell ime list -a

$ adb shell ime enable ID

$ adb shell ime set ID

Now if you link all together you will be able to isntall and activate ime in aw1.5. I hope it works, can someone with 1.5 please try?

Thank you so much!
[Asus ZenWatch 3] csrow:
I managed to install the Google keyboard and set it as a default but it still does not show up as an input method on Keep, Messages, or Hangouts app.

I don't have any other app that requires text input. No go.

If you want to try the id is

com.google.android.inputmethod.latin/com.google.android.apps.inputmethod.wear.latin.WearLatinIME

V1.5 is not designed to support a keyboard. Certain apps can be made to use a keyboard like appfour stuff. Their keyboard do work but I did not like their apps.
[Asus ZenWatch 3] TurboFool:
Notification returned yesterday, so I ran the process again, successfully. It's back again today. Sounds like this isn't going to be a viable long-term solution, sadly.
[Asus ZenWatch 3] csrow:
hmm... that's strange. I have not seen any notifications.

Try running disable command on both as in the original instruction.
[Asus ZenWatch 3] irmatt:
I ran both disable commands and cleared the data, the notification seems to return the next day. Strange because I hadn't seen the notification for quite some time.
[Asus ZenWatch 3] csrow:
That's strange. I am clear of notifications since the 9th when I disabled and cleared.

Try disabling both again and clearing data and cache for both and then reboot. I don't know what else it can be.

Google Service Framework has not been updated on mine. Only the Google Play Service got updated on 12/9. Check the dates on both apps and see.