yashsingh1/xdaforums huggingface dataset:
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
I got this error

C:\adb>fastboot boot recovery.img

< waiting for device >

downloading 'boot.img'...

FAILED (data transfer failure (Too many links))

finished. total time: 0.058s

---------- Post added at 01:27 PM ---------- Previous post was at 01:16 PM ----------

OH, it worked the second time. will have it posted in a moment

Here you go. I zipped up the WIN, SHA2, and Log files.

https://drive.google.com/open?id=1FSJeUbnOanxmgZTes_No47cbahIodVd5

---------- Post added at 02:14 PM ---------- Previous post was at 01:53 PM ----------

Im no pro, but did you clear dalvik cache after flashing the recovery. Apparently that solves some bootloop issues.
[Wear OS Q&A, Help & Troubleshooting] Flexia32:
Did anyone try to fastboot boot twrp.img then flash root?

I guess I'm assuming there is a root for Android Wear 2.0
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
I have the SuperSu 2.82 flashable zip on my wear24 phone, however I'm in a better role to support mkorenko's than proceeding, as he's gotten much further than I would have. I don't know anyone else with active OEM bootloader unlocked as of now.

So just let me know what I can do otherwise.
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Thanks for the stock recovery dump! I will try to recover my watch later today.

I got this error couple of times. Reconnecting the watch helps.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
My pleasure. Let me know if you need anything else. I think I killed my speaker cable like others have.
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
I restored the stock recovery and it works fine, but I'm still getting the bootloop :(

I think I can have an older system for this recovery, cause I had a new update available after updating to AW 2. Or I finally killed my watch :confused:

bens, could I ask you to make a full backup of all your partitions and share it (should be ~1.3Gb)?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
No problem. It'll take a long long long long time to copy over from the watch. Any suggestions on something better than adb pull? Something that shows progress or can resume.
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
No idea. I was pushing my self-made connector to the watch board and holded it like so for half an hour to adb push my yesterday's backup files :)
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Wow. I'm using WiFi adb for all file transfers. It just took a very long time for the 32MB recovery. Yeah there is no way I can hold the USB connector for more than 10 seconds.
[Wear OS Q&A, Help & Troubleshooting] groovadelickun:
Thanks guys, exciting!
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Hey guys, I need your help now.

I'm stuck with a bootloop and need a full TWRP backup from someone to try to revive the watch and move forward.

Bens sent me his backup of stock recovery. I flashed it, it boots up and works, but I still get the bootloop after restarting to the os.

My guess is that the recovery image from bens is newer than my system. Cause last time I was able to boot the os I had a new update available notification.

Bens also has a full backup on his watch, but he faced some issues transferring 1.3gb from the watch (his usb connector died).

So, if anyone is willing to help, please perform the next steps:

0. Make sure you are on AW 2 os and have the latest updates installed.

1. Download the recovery image from here.

2. Perform a factory reset.

3. Boot into bootloader once again, then boot to TWRP using my image:

fastboot boot recovery.img

Do not flash it using "fastboot flash recovery"!

4. Make a full backup, check all partitions that are available.

5. Grab backup files from the watch, they will be in /sdcard/TWRP/ and upload them somewhere.

I would really appreciate any help on this.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
My backup was 571MB. Let me know if it looks like anything is missing from my list. I'm stuck here with everything on my watch until I build a new USB connector or find a faster way to transfer via Wifi/Bluetooth.
[Wear OS Q&A, Help & Troubleshooting] shawndak:
Wow! We need a wear24 forum Asap. A lot of people would be posting topics there. Right now it looked like this thread has been hijacked for that purpose. Great work everyone!
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
And I'm back into the game!

First I reflashed bens recovery, then booted into it, factory reset + wipe cache, then booted into twrp again and flashed ota update, reboot and got android boot logo!

I'm already on the latest 2.10.0.188487362 os version.

Now I'll make a full backup and upload it to my gdrive.
[Wear OS Q&A, Help & Troubleshooting] soapbox23:
Glad it's back up! Have you tried flashing a root file like SuperSU or something?
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Not yet, but I think I will try later today.

Currently I'm doing experiments with twrp. I've uploaded more backups to my gdrive.

For now I can say that to unbrick wear24 you need:

1. Download twrp.img, TWRP_stock_recovery_2.0.0.151212853.zip, ota-update.zip from my gdrive

You will need to extract twrp backup from TWRP_stock_recovery_2.0.0.151212853.zip and upload it together with ota-update.zip to /sdcard. It is possible to do that later using adb push right in twrp.

2. Boot into the bootloader (don't do factory reset in the stock recovery - it will wipe your /sdcard)

3.

fastboot boot twrp.img

4. Do factory reset in TWRP, do not reboot

5. Restore stock recovery using backup files from TWRP_stock_recovery_2.0.0.151212853.zip, do not reboot

6. Flash ota-update.zip

7. Reboot and you should get an android booting logo

You will get 2.0.0.151212853 and then receive an update to 2.10.0.188487362 version.
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
So I flashed this zip from here using twrp and got root!

The script showed an error by the end, but it worked!
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Ok, now I got it. You get 2.0.0.151212853 os version within the system image, then you go through watch setup process and finally get the update up to 2.10.0.188487362 through google play store updates.

Btw I've updated twrp.img (slightly changed device config and recompiled). And successfully restored the system partition from my TWRP_backup_2.0.0.151212853.zip backup, cleared data and caches, rebooted and got 2.0.0.151212853 working with no bootloop!

It weans it is theoretically possible to backup the system, patch it and flash it back using my twrp image!
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Upd: I flashed my latest twrp.img using

fastboot flash recovery twrp.img

and didn't get the bootloop!

So now I have TWRP inside + bootable os + SU. It seems now I can finally put everything back together and close the back cover :)
[Wear OS Q&A, Help & Troubleshooting] lifeisfun:
Folks, we can request separate wear24 forum here, please show your support if you are interested

https://xdaforums.com/showthread.php?p=75907389#post75907389
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
OK, I'll build a USB adapter and replicate today. Is there anyway to disable System Updates (non-play store system updates)? I'm sure there is always a chance Verizon can push an update to break everything.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Worked like a charm. I'm now root as well.

I did Wipe Cache/Davlik before my first boot.
[Wear OS Q&A, Help & Troubleshooting] Flexia32:
Now can you edit build.prop for NFC?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
In the build.prop, all of the ro.nfc entries are missing. I don't think the NFC binaries are in this build, I remember someone pointing this out earlier. Just let me know what to do.
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Yes. I think we need to consider these as a base:

Sony SmartWatch 3 NFC Support Package

[MOD] Adding NFC support to ROM - Final

[MOD] NFC Enabler [JB] [ICS] [KK]
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
I think we should start a new thread "Wear24 - USB Found, Bootlocker Unlocked, TWRP installed, and Root Achieved" - with a copy of what mkorenko has done to get more people on the same page. I think the more people that join us, the faster we will get NFC functional and other great items. A separate forum would be ideal, but at least this will build the support group.

How many others are bootloader unlocked and rooted besides mkorenko and I?
[Wear OS Q&A, Help & Troubleshooting] Flexia32:
That would be a good thread to start. With directions in the first post.

I haven't had a change to get into mine yet. Hoping this weekend I can get it done
[Wear OS Q&A, Help & Troubleshooting] soapbox23:
How did you guys pull the back cover off? I was trying to pry it with a knife but wasn't really getting into a crack. Was thinking to use a plunger type thing?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
The adhesive is very strong, you have to use a lot of force. I marked up my back cover pretty badly. Make sure to start from the top.
[Wear OS Q&A, Help & Troubleshooting] lifeisfun:
Did you try to heat up the back cover with hair dryer?
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
I did. In theory, the more you heat it - the easier it should go.
[Wear OS Q&A, Help & Troubleshooting] lifeisfun:
That's what I thought, works great opening other devices
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Update:

I've uploaded the device tree for our watch to my github. It is used for recovery/rom compilation.

Also I made a request to add Wear24 to the official TWRP builds. Hopefully TWRP guys will notice it :)
[Wear OS Q&A, Help & Troubleshooting] soapbox23:
I was able to get it open and get to the test points but it seems my interface cable isn't working. When you guys touched the pins to the test points, did it just start installing the drivers automatically? I tried on both my Mac and my Win10 PC but nothing happens or shows up when checking ADB devices. ADB debugging is toggled on the watch
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
In windows you will instantly hear the new device sound and see device manager find the device. However it may take a few tries before it finally has the correct device driver. It will be instant. So if you don't hear the noise, your USB connector isn't working. On a rare occasion I had to restart the watch to reset the USB.
[Wear OS Q&A, Help & Troubleshooting] soapbox23:
Were you in the bootloader already or in the OS? Also, would you be able to take a pic of your USB cable end that you connect to the watch? I saw mkorenko's but couldn't really see the construction
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
It doesn't need to be in bootloader to be detected. What I did was cut a paper clip into quarters then crimped the end to each cable. Electric taped it all together spaced just right. You can't see much, but I can post an image tomorrow.

I originally tried that cat5 jack like the guy did with the moto360, but my USB cables we're stranded and couldn't be punched down right. That never worked for me.

With the commands, I recommend queuing them up. Fastboot commands are nice as they will sit and wait for a connection. Often they would send the command just before I'd hear the new device sound.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Here is that photo
[Wear OS Q&A, Help & Troubleshooting] joelphilippage:
I tried for about an hour to get the drivers working. Windows detects the device but says there was a problem. It is not even able to get the device ids. Is there a certain usb cable that I need to use? I have been using the type for printers since I have a lot extra, but none have worked. Also I read earlier that the second pin should go to data - but the picture shows a white cable. I thought negative was white.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Your USB cables should all be the same 4colors. So they should be red,white,green,black I order like the picture earlier in the thread. If you get an error retry or even reboot the watch. It might be that you have a bad data connection.
[Wear OS Q&A, Help & Troubleshooting] marcsoup:
I had the same issue. When I grabbed my multimeter, I checked the test points. Tp3 and tp4 were both grounded for me. At that point, I also got really frustrated with it so I took a knife to that whole speaker/Sim assembly and then brought the whole watch outside and set the battery on fire. I just ordered a second wear24 which should be here in a few days. Additionally, I forgot to take my project fi data sim out, so I got a replacement for that too. I'll also try to dump the os on whatever version of Android Wear it ships with when it arrives.

I wish I had thought ahead and filmed it. Lithium Ion batteries are fun xD
[Wear OS Q&A, Help & Troubleshooting] joelphilippage:
Okay. That is the order I did it in. I have tried rebooting multiple times normally and to the bootloader.

The pin out confused me because it said.

But this article said green would be negative:

https://turbofuture.com/computers/Color-Coded-Wire-inside-the-USB

I had tried switching the green and white but still didn't get anything so I switched back to the picture order. Maybe I will try different pins instead. Thanks for the help.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Even know the colors of the cables are a little confusing; this image should help everyone. If you are still having issues, post an image of your setup and an image of you actively connecting it with the terminals on the watch. I was lucky to have this work on the first shot, but after my connector broke; I did build 2 different connectors that DID not work.

What did not work

Punching down the stranded wires of a USB3 cable to an Ethernet Jack and bending the connectors out as they did for the Moto360.

Taping the loose stranded wires of a USB3 cable to the touch points on the watch.

What Worked

I used a microUSB to USB cable, so I know it was USB3. Maybe that is the issue everyone is having?

I cut a paper clip into quarters and crimped the edge around each usb cable end

I taped each cable and then taped the entire array together.

Red (tp1) - White (tp2) - Green (tp3) - Black (tp4)
[Wear OS Q&A, Help & Troubleshooting] marcsoup:
I was using a usb breakout board with a micro usb cable and some pogo pins to connect up to the test points. TP1 is Red/5V/VCC, TP2 is White/Data+, TP3 was SUPPOSED to be Green/Data-, but it was also grounded on mine, and TP4 is Black/Ground
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
That is nice to have, what do you do with the 5th cable "ID"? Maybe you need to bridge ID and GND?

BTW, You can get new Wear24s for $63.99 on eBay today; I just bought 2 more. Techrabbit $69.99 with promo code "PRETTYDAY"

It's not the $50 deal, but it's the best you'll find today for a new one.

---------- Post added at 05:25 PM ---------- Previous post was at 05:14 PM ----------

Maybe there is something else here. I've used the same Windows computer to ADB/fastboot to many other devices. It's possible mkorenko and I both had previously connected to devices (like the Nexus 6p) that installed lemobile android device drivers. Too many people are having an issue with something that sounds like they have it correct.
[Wear OS Q&A, Help & Troubleshooting] joelphilippage:
I have been using an old motherboard connector with wire stuck in the end then phone splicers to connect to the correct cables. I do not have any USB 3 connectors laying around, but would get one if I knew that was this issue. I have tried three different USB 2 cables with no luck. (I know the connectors are a bit off the pins in the last picture since I was having trouble getting a picture and holding the cable.)
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Marcsoup, do you get the same error as joelphilippage "There was a problem"? Or do you just hear that its detected but nothing adb doesn't seem to connect? joelphilippage, it looks good, but I think you may have an issue with your cable. I did receive the "There was a problem" time to time, but make sure to restart your watch if you have any of these errors.

Most of my work was not with adb, but already in bootloader. However I did get ADB to work as well for 10 minutes at a time MAX. It's not easy to hold it the connections together while typing!
[Wear OS Q&A, Help & Troubleshooting] marcsoup:
My computer was saying something like "USB Device Not Recognized. Device Descriptor Request Failed"

I have used the breakout board on various other projects in the past, so I know it's functional. My guess is one of two things. When I was messing with the antenna pins a few weeks ago, I might have fried it, or I may have been a little rough and accidentally shorted TP3 to ground some other way.

Also, I got the new one on techrabbit with a 15% off code, so it came to something like $75, including tax and shipping. Definitely not as good as the $50 deal, but it's not prohibitively expensive. Way better than $350 from Verizon though so I won't complain.

Btw, if you have any electronics hobby stores nearby, you can generally get breakout boards for anything really cheaply. It cost me $1.95 at you-do-it electronics, a phenomenal store in the Boston area. I'm like a kid in a candy shop any time I'm there

Online, check out sparkfun. Again, great place for diy/hobby electronics stuff.

The ID pin is used for USB OTG to determine which is the host device and which is the slave device. It's grounded on the host device and left floating for the slave device.

I think I'm going to see what I can do with a dremel on the old backplate. I'm thinking I can make a cutout for easy access to the test points while the watch is assembled, and maybe make some sort of silicone/rubber cover for when I'm wearing the watch.
[Wear OS Q&A, Help & Troubleshooting] joelphilippage:
That is the same error I am getting. I am interested to know if you have the same issue with your new watch.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
So I know this is crazy, but try it with the SIM CARD removed. again, looking at whats different between what works and what doesn't. Since we have 2 of each it should not be hard to figure out. Joel, did you test the USB connections via the terminals in the band (antenna leads)
[Wear OS Q&A, Help & Troubleshooting] marcsoup:
I went for the cheap shipping, and there's supposedly going to be a large storm in the Northeast US tomorrow, so I'll probably have it by the middle to the end of next week
[Wear OS Q&A, Help & Troubleshooting] joelphilippage:
I can try this afternoon. What do you mean the "terminals in the band" is there another place to connect?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Originally people thought the 4 connectors in the band were for USB as that is how it was done with the Moto360.
[Wear OS Q&A, Help & Troubleshooting] joelphilippage:
Good hunch buddy! I removed the sim card. It failed the first time to recognize the device then worked immediately after that and I was able to successfully unlock the bootloader. I'll try to flash recovery now.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
That's great to hear!
[Wear OS Q&A, Help & Troubleshooting] joelphilippage:
Now I keep getting:

fastboot flash recovery twrp.img
< waiting for any device >
target reported max download size of 262144000 bytes
sending 'recovery' (14484 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 0.007s

I tried two different computers and about every USB slot but always get the same thing.

I'm guessing it's the cable so I might try making another one tomorrow.
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
Good luck with the new cable. Keep it as SHORT as possible, another hunch from looking at your photos.
[Wear OS Q&A, Help & Troubleshooting] joelphilippage:
I made a cable as short as I could, but still keep getting the errors. I may wait until I go to town this weekend to buy some wire crimpers so I can make something a bit closer to your method.
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Hey guys! Sorry for the late response, was busy last couple of days.

You can find photos of my connector below. I've made it using jumper wires I had from the raspberry pi kit. I just put together 4 of them and taped with electrical tape. Also I've bent them a bit for easier handling.

As for the data +/- and colors. I googled and discovered contradictory info and pictures on the data +/- order. So just follow the colors order from my first photo.

As for the connection: it is really unstable when connecting. It usually takes around 5-30 tries for me to catch it.

Assuming you are using windows pc, just listen for the connection sound and then wait for "USB Device Not Recognized" error. If you get it - disconnect the connector entirely and try again. If not - you should see the usb device icon in the tray. My windows pc had no drivers installed before, but on the first successful connection I've got them installed automatically.

Also I noticed that if I touch the ground pin first (TP4) the success rate increases by 50% :)

When you'll catch the connection it will be pretty stable. Also, I'm not sure that it is the connector that gives those failures. Cause every time I run "adb/fastboot reboot" on a stable connection I loose it after reboot.

Wish you luck catching the connection! :)

P.S. I had an email conversation with TWRP guy. They built recovery image using my config and it worked! Also I made a pull request on adding wear24 to the twrp.me device list. So we should get an official TWRP build available shortly.

We should somehow involve rom devs here to help us with nfc/custom roms :)
[Wear OS Q&A, Help & Troubleshooting] mkorenko:
Update:

TWRP for Verizon Wear24 - official builds
[Wear OS Q&A, Help & Troubleshooting] mixdupkid2002:
Outstanding items on wear24

Hi all

I picked up wear24 yesterday and have two questions.

1. I read online that after updating from 1.5 to 2.0, Bluetooth audio via mic does not work. I tested this out via a phone call via watch and the other end can not hear me. So is there any solution to make this work?

2. I have two phones and would like to pair with wear24. I read on several forums here that you can do this without factory reset by doing adb commands. Reason I ask is that I have data plan on one phone but phone only plan on the other so I would like to get calls and notifications together onto the watch. Is there a workaround?
[Wear OS Q&A, Help & Troubleshooting] dandrumheller:
I've read mixed reports about the ability to switch paired devices without resetting the watch - most of the stuff I've seen recently indicates the workarounds aren't working for many people. That said, it CANNOT, to my knowledge, be paired with multiple devices simultaneously (i.e. you can't get data / notifications from one phone and calls from the other phone at the same time). If you're stuck with a data line and a phone line, can you get yourself a dual SIM phone?
[Wear OS Q&A, Help & Troubleshooting] mixdupkid2002:
Thanks Dand - I figured. I am struggling to get USB debugging to be recognized on PC machine right now. I mean what is going on - it just list devices as blank

Do you know if mic works on on AW 2.0 for this Wear24. All the forums state that it is not working - which really blows because its a functionality that is useful in my eyes.
[Wear OS Q&A, Help & Troubleshooting] GhostRider5666:
All we need now is a custom Rom.
[Wear OS Q&A, Help & Troubleshooting] trips555:
Is there any reason to suspect that there will be a method of all this that will not require opening the watch, or is that part going to be a given no matter what?
[Wear OS Q&A, Help & Troubleshooting] bensdeals:
They are now $59.99.

https://slickdeals.net/share/android_app/t/11402919
[Wear OS Q&A, Help & Troubleshooting] soskey22:
my wear24 is in like a bootloop only google assistant works, does anybody know how to reset it? i have a black screen, this happens after i tried to put my watch in fastmode using adb