Last Updated: December 16th, 2014

You saw Android Wear a couple of months ago when Google unveiled the SDK and both LG and Motorola presented the first promotional pictures. Then you watched the Google I/O keynote that officially launched the LG G Watch and Samsung's surprise addition of the Gear Live. And now you've got a shiny, brand new Android Wear watch before you... but all you can think about is ripping into the digital guts of that thing and doing all of the awful things that Google never intended. Admit it, you're one of us.

Android Police is here with a guide to fill all of your hacking and modding needs. Since Android Wear is so new, some of these methods may not be of much use at first, but the community will surely rise to the challenge before you know it. Let's get started!

These instructions assume that you are moderately familiar with using adb and fastboot. If you're using Windows, you will also need to have the USB drivers from the Android SDK installed and working properly. While it seems the KitKat SDK is sufficient for these steps, it's still best to get the most up-to-date versions of all of these tools before starting. Using outdated tools may result in unpredictable behavior.

Turn on (ADB) Debugging over USB and Bluetooth

Most of the things you'll want to do with Android Wear are going to require enabling debug mode. Since this is a necessity for most developers, the necessary steps have already been documented on the Android developer portal. The instructions in this guide are mostly identical to those provided, but with a few additional details and screenshots.

  1. Open Settings.
    1. Tap on Wear's watch face. This will take you to the voice prompt. Be sure to hit the watch face instead of a notification card.
    2. Wear will wait up to 3 seconds for you to say something, then it'll change to a scrollable list of native actions. You can speed this up by swiping up or tapping on the voice prompt.
    3. Scroll down and select Settings.
  2. Open About.
  3. Find Build number and tap on it 7 times. You're done when a toast popup appears with the message, "You are now a developer!"
  4. Swipe right (to go back) to the Settings menu.
  5. Open Developer options.
  6. Find and set ADB debugging to Enabled.
  7. You'll be asked if you're sure you want to enable. Tap the checkmark button to confirm.
  8. [Optional] If you want to also turn on debugging over Bluetooth, Find and set Debug over Bluetooth to Enabled.



Note: As long as debugging is enabled, attaching Android Wear to any computer with ADB installed will open a prompt like this on the phone your Wear device is paired with. If the computer belongs to you, it's probably safe to check the box and tap Ok so you won't have to authorize it each time. If you ever see this dialog when you aren't expecting it, you should probably play it safe and press Cancel.


Debugging Over Bluetooth

For most of the objectives in this guide, you will have to use adb and fastboot over a wired USB connection. However, if you're taking screenshots or developing an app, it might be more convenient to use adb over a wireless Bluetooth connection. This can be done by forwarding a socket through adb. That sounds more complicated than it really is.

  1. On your Android Wear device:
    1. Enable Debug over Bluetooth (described in the previous section).
  2. On the phone your Android Wear device is paired with:
    1. Attach the phone to your computer with a USB cable.
    2. Open the Android Wear companion app.
    3. Open the Settings screen (it may be an icon represented by a pair of gears, or it may be in the overflow menu).
    4. Enable on Debugging over Bluetooth.
      Note: Don't worry if the companion app indicates the target device is not connected, the status doesn't always refresh correctly.
  3. On your computer:
    1. Open a terminal window and enter this command:

adb forward tcp:4444 localabstract:/adb-hub; adb connect localhost:4444

The first part of that line will map a socket through the phone that is paired to your Wear device, while the second part makes a connection. At this point, we've got two devices attached to your computer. You can see a list of attached devices with:

adb devices

Screen Shot 2014-07-05 at 8.06.15 AM

The identifiers are listed on the left side, and their connection status on the right side. Since there are two devices visible to adb, it cannot automatically pick a default device. All of your commands will have to be sent using the -s flag along with a device identifier. We already declared the Android Wear watch would be on port 4444, so it's identifier appears as localhost:4444. For example, if we want to open a shell, the command will look something like this:

adb -s localhost:4444 shell

Taking Screenshots

Sometimes you want to snap a shot of what your device is showing you at a given moment. Unfortunately, the current run of Android Wear devices lack a convenient method for taking a screenshot. Until a better solution can be worked out, <cough>already on it<cough>, we have to rely on adb to fill the gap. Taking screenshots with adb requires debugging to be turned on and a connection to a computer through Bluetooth or USB.

From a terminal, enter the command:

adb shell screencap -p /sdcard/DCIM/screenshots/screenshot1.png

Reminder: change the file name for each screenshot.

The path can be set to any location you prefer, but the filename should be changed for each screenshot. If a filename already exists, it will be overwritten without warning. Also, if more than one device is attached, you'll have to use the -s flag to tell adb which device should be taking the screenshot.

Once you're done collecting screens, use adb pull to copy them over to your computer.

adb pull /sdcard/DCIM/screenshots/screenshot1.png

-or, to copy all of them at once-

adb pull /sdcard/DCIM/screenshots/

Modding 101

Welp, it's time to talk about voiding your warranty. If that's not your cup of tea, this is probably a good place to stop. It's possible to do some real damage with most of the things you would do from this point forward. You've been warned.

Disclaimer: Android Police isn't responsible for any harm to your device - proceed at your own risk.

Bootloader / Fastboot

If modding your Android Wear wristwatch is more your speed, it's time to start poking around the device internals. The first step is to get into the bootloader, also known as fastboot mode. The lack of physical buttons necessitates a few different methods for accessing the bootloader than we're familiar with on most handsets and tablets, but it's not that much different.

Method 1 - Swipe

This is probably the fastest and easiest way to reach fastboot mode. All you have to do is start (or restart) the watch and look for the OEM logo during boot up. While the logo is showing, and before the screen dims, swipe your finger from the top-left corner across to the bottom-right corner. If you're using a Samsung Gear Live, you'll also have to hold down the power button on the side. If executed correctly, you should be looking at your bootloader.

(Working on the video now)

Method 2 - Command Line

In some instances, it might be more convenient to use the command line if you happen to be at your computer and already have a terminal window open and ready to go. As long as debug mode is enabled and the watch is connected, just enter:

adb reboot bootloader

Both devices provide touch-enabled bootloaders. The LG G Watch places three on-screen buttons across the bottom. There are left and right arrows on either side to cycle through different actions (shown in red near the top of the screen). The commands are: Start, Power Off, Recovery Mode, and Restart Bootloader. Tap the arrows until the correct command is shown, then tap the circle in the center to perform the action. The Samsung Gear Live offers the same options, but you have to swipe downward to change your selection, and swipe to the right to activate it.


Left: Samsung Gear Live bootloader, Center: LG G Watch bootloader, Right: prompt to unlock


For your primary flashing needs, recovery mode is usually the way to go. There aren't any direct button or gesture combinations to enter recovery mode, but getting there is still quick enough.

Method 1 - Fastboot Menu

This one is pretty obvious. Simply get into the bootloader through whatever means suit you, then use the menu to access Recovery Mode.

Method 2 - Command Line

You already know the bootloader is easy to reach with a simple command, and there's also one for Recovery Mode.

adb reboot recovery

Download Mode

If you find yourself in a bind, there's a chance that you'll be able to fix things in Download Mode. This is more of an interactive flashing tool that relies on a live connection to a computer. At this point in time, there aren't any good reasons to enter this mode, but it is worth mentioning. The steps to enter and leave download mode are a bit different depending on the device.

G Watch

The watch must be fully powered off, and then connected to the computer through the charging cradle. When the LG logo appears during boot up, swipe your finger from the bottom-left corner across to the top-right corner.

If you haven't done anything in download mode, or if the flashing tool doesn't automatically restart the device, it's possible to exit by simply breaking the connection with the computer. WARNING: Disconnecting the watch while flashing firmware will almost certainly brick it. Don't do this if there's any risk of writing data.

Gear Live

Restart the watch (it doesn't need to be powered off) and wait for the Samsung logo during boot up. With the logo on the screen, hold down the power button and swipe your finger from the top-right corner across to the bottom-left corner. Once in this screen, navigate downward by pressing the power button, and activate an option by long-pressing.

If you need to leave download mode, and the flashing software didn't automatically restart, navigate the menu to either "Start" or "Power Off."

Unlocking The Bootloader

Unlocking the bootloader will wipe user data from the device. Your installed apps should be restored after your phone is re-paired, but the data for some apps may not be. This includes collected data from your step counter, device pairings, and debug authorizations.

While it's possible to use adb over Bluetooth to reboot into the bootloader, you'll lose the connection once you're in there. The only way forward is with a wired USB connection to your Android Wear device.

The LG G Watch and Samsung Gear Live are shipping with locked bootloaders, but they are easily unlocked using a standard fastboot command, just like a Nexus device. In fact, if you've ever unlocked a Nexus phone or tablet, the process is basically the same.

To unlock your device, reboot it into bootloader mode and run this command from a terminal:

fastboot oem unlock

Warning: Samsung does not prompt for confirmation!!! It immediately unlocks the device and wipes your data. Come on, Samsung, get it together...

The LG G Watch will present you with the standard prompt advising you that this action may void your warranty and that your data will be wiped. The only thing of significance you're likely to lose is your pedometer info. Just about everything else should be stored by the apps on your phone. Once your watch is paired with your phone again, almost everything will be restored automatically.

To move ahead with the unlock, tap either arrow to change the option to "Yes - Unlock (may void warranty)," then tap the circle. It will only take a moment to wipe user data, and then the unlock is finished. Before making any other modifications, you should reboot the device, even if you're just rebooting back into the bootloader. Some devices may begin bootlooping without a restart after unlocking.


Left: LG bootloader unlocked, Right: LG boot screen with unlock icon

Oh, and before we assume Samsung is the only one that did a rush job with its bootloader, take a closer look at LG's unlock screen. Not only does it falsely claim that it will delete personal information on your phone, but it wants to inform the user that unlocking will allow for the installation of a "custome operting system" and that may void your "warrenty". Way to go, LG.


Since the release of Android 5.0 Lollipop on Android Wear, rooting hasn't been closely examined. For watches with custom recoveries and unlockable bootloaders, it should be possible to flash SuperSU, but this process hasn't been examined yet.

Alright, you've unlocked your bootloader and you're ready to tear it up with custom roms and other assorted mods. But wait, this is probably a good time to stop. No, I'm not messing with you. Justin Case and I only just acquired root on the G Watch on July 4th, and there's very little that can be done with it at this point. Additionally, there are no superuser managers (eg. Chainfire's SuperSU or Koush's Superuser) available to prevent an app from abusing root for malicious purposes. This situation will surely change over a matter of days, or even hours, but that's where we're at for the moment. I'm not suggesting that people avoid rooting, only that they wait until it can be done a little more safely.

If you're one of the people that wants to get started on building some root apps, or you just need to be on the bleeding edge, you're in the right place. So far, we only have the process worked out for the LG G Watch, but the Samsung Gear Live should be ready fairly soon.

LG G Watch

The process is very straight forward, but it requires that you already have your bootloader unlocked. If you haven't already done so, go back and complete that step first.

First, download our modified boot image (thanks to Justin Case):

File name: LGGW-rootboot.img

MD5: fe2e8e3bb008096100da3e2014c597f1

  1. AndroidFileHost
  2. MediaFire
  3. ZippyShare
  4. Mega

Now, reboot into the bootloader:

adb reboot-bootloader

And boot the G Watch using the modified boot image. Warning: Do not flash the boot image, just boot from it!

fastboot boot LGGW-rootboot.img

The watch will play the boot animation for about 2 seconds, then automatically reboot. The modified boot image is only meant to run once so that it can install the necessary superuser binaries. After the watch automatically reboots, it will be running on the stock boot image. There will be no outwardly obvious signs the G Watch has been rooted, but you can check it by opening a shell through adb and running su.

adb shell


If your prompt turns from shell@dory to root@dory, then you've got root on your G Watch. Congratulations!

Samsung Gear Live

Still waiting on a stock root method.

Custom Recovery

Rooting your smartwatch is certainly a good way to get a handle on its operation, but there are times when the stock software just isn't good enough. At this point, you'll want to switch over to running a custom ROM. For that, you really want to use a custom recovery to do all of your flashing.

The process for installing a custom recovery on the G Watch is exactly like it would be for any other unlocked device. If you haven't already unlocked your bootloader, go back and complete that step. There's no need to root your device to install a custom recovery.

First, download the recovery image appropriate for your device:

Then, while your device is connected to a computer, get to your bootloader screen through whatever means you would like to use and enter this command to flash the recovery image.

fastboot flash recovery <filename.img>

The bootloader will briefly display the words "Downloading..." and then "Writing..." Once it is finished, tap the arrows until you see the option to reboot into Recovery Mode, and tap the circle button. That's all it takes!


Since a lot will be changing with Android Wear over the next few days and weeks, I'll try to keep this post updated as new information comes in.


  • 2014-07-05: Initial Version
  • 2014-07-25: Added details for TWRP custom recovery on G Watch. Also broken out a separate section to describe accessing fastboot, recovery, and download mode.
  • 2014-12-16: Struck out the Rooting section until it can be rewritten with respect to the changes made for Android 5.0.
Cody Toombs
Cody is a Software Engineer and Writer with a mildly overwhelming obsession with smartphones and the mobile world. If he’s been pulled away from the computer for any length of time, you might find him talking about cocktails and movies, sometimes resulting in the consumption of both.

  • abobobilly

    Quick question. Rooting a phone makes sense that you'd want to run apps which require root, or maybe backup roms or use titanium back. What could you possible do on a rooted WATCH, which can't be done otherwise?

    • Mystery Man


      • abobobilly

        These watches are severely limited in functionality. I wonder if you will even get ads on these lol.

        • Fatal1ty_93_RUS

          They would probably cover the whole screen

          • abobobilly

            Mandatory Gif


        • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

          3rd party apps can install applications on the watch, and as far as I can tell, any app can do it. I sincerely doubt we're going to even make it 2 weeks before some app is trying to push ads of some kind to the watch. Of course, any app that does will instantly see a flood of uninstalls.

          • abobobilly

            Isn't this the world of Android we live in? I wouldn't be surprised if this happens. I am more interested in the counter measures offered by devs. Deep down, i feel these watches would be somewhat 'underpowered' to take on such tasks. But thats just a self assessment.

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      That lands squarely in the *we'll see* category. At the most basic level, it might just be useful for backing up and restoring data, just like we do on a phone. There are definitely some utility functions that I and a few other people are eagerly looking forward to. I sincerely doubt there will be very many people that have a need to root their watches, but we'll see what happens.

    • Syukri Lajin

      I root my phones because i can. :P

      • abobobilly

        WOW. You sound like a real genius :p

      • Leo

        For the good of all of us (except the ones who are dead)?

    • http://www.androidpolice.com/ Artem Russakovskii

      I really want a native screenshot functionality, and bonus points for saving directly to the phone where FolderSync would pick it up and stick it straight into Dropbox.

      • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

        It's in the works ;)

    • microcabin

      lot of possibilities. AdBlock, firewall, web server (lol)

      • http://blog.artesea.co.uk/ artesea

        If the watch accesses the net through your phone, wouldn't AdBlock on your mobile already do the blocking?

        • Bluewall

          That's true !

  • Brandon Smith

    How did Justin Case manage to dump the G Watches' kernel? Any info, AP?

    • Justin Case

      *magic*, no further comment.

  • Narciso

    Are you fucking kidding me? There's LG logo on watch's bootanimation?

    • Fatal1ty_93_RUS

      Did you expect to see Google there? it's not a nexus after all

    • Brandon Smith

      It's only the boot loader screen; it changes to the actual boot animation after a few seconds.

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      Not the boot animation, just the boot screen. It goes through 4 different phases over just a few seconds. First is the LG logo, then an opener to the boot animation, then the regular boot animation that is on repeat until the watch is ready, then it finally closes on the Android Wear logo.

    • Gerjannn

      Hey c'mon, Life's good! :)

    • GazaIan

      You seem surprised that a manufacturer put's it's logo on it's own device. They've been doing this since 2008...

      • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

        2008 -> 8

  • Fatal1ty_93_RUS

    Oh my god, the G Watch's codename is Dory? Gotta love LG on this one

    • olgahmccoin

      my Aunty
      Allison recently got a nice 6 month old Jaguar by working from a macbook.this website C­a­s­h­d­u­t­i­e­s­.­C­O­M­

  • Shacha GC

    quick question can u run full android apps on android wear

    • RichardG867

      Most apps will crash on startup, since Wear doesn't support the action bar, WebView or widgets.

      • Shacha GC


      • Sso

        if my app don't use those things, can it run on Wear?

  • pigo666

    and finally learned,Led Lampen the best

  • wmsco1

    Nice! Can you get the original Galaxy gear to sync with Android Wear?

  • http://www.lupoalberto12.it/ lupoalberto12

    So, unlock the bootloader is simple like on Nexus and lock? Is it "Samsung style" (with some counter) or just fastboot oem lock and everything is back as before?
    ! :) !

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      I only have the G Watch, and there's no obvious sign of a counter. Artem is the only one of the AP team with a Gear Live, so he's the best to ask about that. I can't see any sign of a counter in any of the images he has shared with me, so I'm going to assume there isn't one unless it's hidden elsewhere.

      • Tarun Pemmaraju

        fastboot oem device-info?

        • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

          (bootloader) Device tampered: true
          (bootloader) Device unlocked: true
          (bootloader) off-mode-charge: true

          There's a tamper flag on the LG G Watch, but that's basically universal these days. The Nexus 5 has it, too.

          Until shipments start arriving (probably tomorrow), Artem is the only person I know with the Gear Live. Maybe he'll check his.

      • http://www.lupoalberto12.it/ lupoalberto12

        Ok, it's a good news.
        I'm waiting for Motorola 360 but if it'll be very expensive, I'll buy or G Watch or Gear Live... which would you (two) recommend?
        I don't like Samsung and prefer the G Watch but the Gear Live has the "heart rate detector" and it would be useful with Google Fit.... again, which would you (two) recommend :D ?
        ! :) !

        • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

          I started this as a quick response and it quickly grew out of control. tl;dr -> I lean towards the G Watch, but it's mostly a toss up. Just try to get a 360.

          I'm probably not the best judge, having only briefly seen the Gear Live. As far as I'm aware, most I/O attendees went for the G Watch.

          The only thing I can really judge by are the comments I've seen in various places. The top complaint I've about the Gear Live is that the heart rate sensor is virtually useless. As I've seen it described, the measurements are wildly inaccurate unless the band is tight enough to restrict blood flow to your hand. I've also read that if you're sweating, it won't detect anything at all. In other words, that feature is basically useless during workouts, the one time when you want it most.

          Both devices are fairly inaccurate with their step counters, but that's not surprising since they go on your wrist instead of your shoe.

          Most people have said the G Watch is slightly more attractive and has better looking watch faces, and I suppose I agree. The band on the G Watch is a bit easier to find replacements for, if that matters to you. Neither device is exactly fashion-forward, but we all know that wasn't a target in this initial line-up. That's an area to be addressed by the Moto 360 and several of the subsequent products (I'm eager to see what HTC has in store).

          The G Watch has the always-on feature, which is both nice an obnoxious. However, that can be disabled if you don't like it, which means the LG battery life can smoke Samsung.

          Otherwise, I don't think there's really much of a difference between the Gear Live and the G Watch. At least, not yet. Future updates will probably change that, because Samsung will probably try to load on some extra stuff over time while LG will probably leave it a little bare. However, LG's watch is the nudge-nudge-wink-wink, unofficially Google-sanctioned developer watch, which kinda makes it the spiritual counterpart to the HTC G1 and Motorola Xoom - sort of a pre-Nexus for each form factor. it will probably receive updates for a little while after Samsung loses interest in the Gear Live. Of course, given the rapid pace we're likely to see on Android Wear, I'm not sure either one is going to be remembered by next year.

          Having said all of that, and knowing a little more now than I did when I had to pick the watch, I would still take the G Watch over the Gear Live. Even then, I really don't think it matters all that much. They're so similar that it's almost better to stick with brand loyalty over feature comparisons.

          Frankly, I'm not personally invested in either of them. I feel like both of these are just placeholders for the Moto 360 and everything else that's coming later this year. They both feel a bit rushed, so I'm not even sure we'll make it 6 months before either LG or Samsung (or both) announce follow-up versions with better specs and designs.

    • saf1927

      The Nexus does have a tamper flag which is set to true when you unlock the bootloader. Though it can easily be set to false if you have root access, so it is indeed a non-issue.

  • Douglas Crawford

    Thanks!! Looking forward to rooting as soon as phone gets here Tuesday

  • http://vinu.info Vinayak Prabhu

    "Custome" "Warrenty"

    R.I.P Inglis :(

    • someone755

      Don't forget "operting system"!
      Well at least you get a warning, unlike that Sammy crap.
      I bet the only reason Sammy didn't include a warning is because they knew they'd fuck it up, probably even more so than LG did.

  • lynx

    I really hate things on my wrist. I hope moto makes a pocket watch version of the 360...

    • itched

      You could just make your own. Take off the bands & create a cover for it & you have a fancy smart pocket watch.

      • someone755

        But pocket watches need that cute little cover that opens with a button. And you open and close it and feel like having a flip-phone again. xD
        Anyways, no way would I manage to create a cover that fits, let alone add a button and a spring to all that.

    • someone755


    • DrakeTungsten

      I'd just as well take my phone out of my pocket at that point.

  • Sandeep Saini

    I haven't tried to do any of the above said things but when flashing the rootboot.img, shouldn't the command be "fastboot flash boot LGGW-rootboot.img" instead of "fastboot boot LGGW-rootboot.img"?

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      In this instance, you don't want to permanently flash the boot image. The modified boot image provided here will run once and write su into /system/xbin, then the watch restarts with the default boot image. If this image is flashed, it might cause a boot loop.

      • Sandeep Saini

        Oh.. Thanx for the clarification. 😊

        • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

          Thanks for asking. I probably wasn't quite clear enough about what what was going on. I just updated the post to explain this a little better.

  • Namy
  • nxtiak

    An easier way to take screenshots is to go into the tools folder of the sdk folder and run ddms.bat (Dalvik Debug Monitor), then click on the G Watch on the left, then go to Device and choose Screen Capture, you get a nice GUI for a screenshot. You can also pick Screen Record to record a video!

    • http://www.androidpolice.com/ Artem Russakovskii

      Actually, monitor.bat has replaced ddms in the newer SDKs. But yeah, that's definitely the easiest for me too.

  • http://www.androidpolice.com/ Artem Russakovskii

    A quick warning for everyone.

    Never-ever unlock the bootloader and flash a custom recovery in one step. TWRP doesn't understand the initialization procedure and keeps bootlooping. The only way to resolve this is to re-flash the stock recovery first.

    You can find the Gear Live recovery here http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696.

    I just restored my Gear Live back from the dead by flashing the recovery back, restarting, letting it initialize, then flashing TWRP.

  • http://www.androidpolice.com/ Artem Russakovskii

    For some reason the Gear Live completely disappears from my Windows device list as soon as I enter sideload mode in the stock recovery or TWRP. If anyone knows a way around this, I'd love to hear it, because the only way to flash updates now is to push using adb first, then install a local file, which requires a custom recovery (and therefore bootloader unlock).

  • Scott Odle

    bash script for taking screenshots in one step:

    #! /bin/bash
    adb shell screencap -p "$shotpath";
    adb pull "$shotpath";

    Assumes that you already have your watch properly configured through ADB. Saves as "wear-shot-dateandtime.png" in the current directory.

    Tested on a Mac + LG G Watch.

  • Alex Sorkin

    I have a Moto 360 and to only way to debug it is through bluetooth. I have ADB and Bluetooth debugging checked on my Moto 360 and I have USB debugging and Enable Bluetooth debugging also checked on my phone. I plug my phone into my computer and it says "Host: disconnected" "Target: Connected". When I use "adb forward tcp:4444 localabstract:/adb-hub; adb connect localhost:4444" IT doesn't connect to my Moto 360. PLEASE HELP...

    • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

      I've been meaning to get back in here and make some 360-specific updates to the article. I can't do it tonight, but I'll see if I can squeeze it in tomorrow.

  • Brian Hall

    Has anyone tried adb backup and/or Helium with Android Wear?

    In my own experiment, adb backup gets as far as waiting for the confirmation dialog on the device, but then the device (watch) doesn't show one.

  • Mod or Die

    Nice, Thank you!