Whoever wants to update the Zenwatch via ADB Sideload, here is a Link to the OTA File.
The others will receive the update pretty soon as it seems that the OTA has been triggered.
Updating via ADB as we speak...will let everyone know what the story is...
Worked fine for me. But don't expect WiFi
How did you guys push it via adb
kaylord84 said:
How did you guys push it via adb
Click to expand...
Click to collapse
For me, it was a nightmare. My Android SDK was out of date. Even when I upgraded, I was left with a lower revision of ADB than I needed to push the update. I had to completely uninstall and reinstall the SDK. Even then, the ADB wasn't the right rev. I found some obscure posting on XDA thst said not to use ADB, but ./adb (Ubuntu based system ). This worked.
Once I got it updated, the watch had nothing but issues. Lots of lag, connection issues, and inability to use any of the Asus watch faces. I had to do a factory reset on the watch. It took about 45 to sync all the apps (not sure why it took so long, I really don't have many apps.)
Things seem to be settled in now. We'll have to see how it goes.
Update Issues
jak341 said:
For me, it was a nightmare. My Android SDK was out of date. Even when I upgraded, I was left with a lower revision of ADB than I needed to push the update. I had to completely uninstall and reinstall the SDK. Even then, the ADB wasn't the right rev. I found some obscure posting on XDA thst said not to use ADB, but ./adb (Ubuntu based system ). This worked.
Once I got it updated, the watch had nothing but issues. Lots of lag, connection issues, and inability to use any of the Asus watch faces. I had to do a factory reset on the watch. It took about 45 to sync all the apps (not sure why it took so long, I really don't have many apps.)
Things seem to be settled in now. We'll have to see how it goes.
Click to expand...
Click to collapse
I also had issues. I struggled with ADB problems as well. I finally updated my Android SDK. I still had issues, but it finally worked. All was well, but I noticed an app that was on my watch but not on phone. (my fault) Reset the watch and it took forever to sync. Finally, all is well. So far, I like it.
ADB Sideload was a pain in the a** for me as well. Also had an outdated version but went for "15sec ADB" on XDA. Worked fine.
However ADB always found two devices. On my Mac I had no idea how to fix it, so I went to Windows, disabled the offline flagged device (which was not the one I disabled first of course. And every disable requires a reboot. Windows really didn't improve at all) and ran the ADB Sideload afterwards.
At the first boot of the watch everything was running like crap. Rebooting helped and made everything smooth for me
FutureBSD said:
Whoever wants to update the Zenwatch via ADB Sideload, here is a Link to the OTA File.
The others will receive the update pretty soon as it seems that the OTA has been triggered.
Click to expand...
Click to collapse
Got my update early this evening.
What's worse when you try to sideload the Zenwatch is that when you sideload it via Ubuntu, it needs a udev rules entry. But I can't find that anywhere.
L0rDKadaj said:
What's worse when you try to sideload the Zenwatch is that when you sideload it via Ubuntu, it needs a udev rules entry. But I can't find that anywhere.
Click to expand...
Click to collapse
See if this helps. It did for me.
http://forum.xda-developers.com/showthread.php?t=2302780
no need to push, I found a trick.
If you want the update just uninstall the zenwatch manager. Then on your watch, hit reset to do the factory reset. After its done reconnect to phone and it will first install the old software and then you can select "system update".
Flexnuts said:
If you want the update just uninstall the zenwatch manager. Then on your watch, hit reset to do the factory reset. After its done reconnect to phone and it will first install the old software and then you can select "system update".
Click to expand...
Click to collapse
tried it, didn't work for me, unless im doing something wrong. UK
Mine came OTA two days ago. I wish it hadn't, it's broken my battery charge indicator which is now stuck on 86%. I'm in the UK too.
I'm really confused, I dont have bluestacks installed, its showing one device when i connect my watch, then when i reboot into recovery it shows the same device 2 times, one is sideload, the other duplicate is offline...its not allowing me to sideload the zip because there is more than one device or emulator attached, also tried adb kill-server then adb devices, still the exact same serial.... what am I doing wrong?
kingkoopa85 said:
I'm really confused, I dont have bluestacks installed, its showing one device when i connect my watch, then when i reboot into recovery it shows the same device 2 times, one is sideload, the other duplicate is offline...its not allowing me to sideload the zip because there is more than one device or emulator attached, also tried adb kill-server then adb devices, still the exact same serial.... what am I doing wrong?
Click to expand...
Click to collapse
I don't think you're doing anything wrong. I ran into that too. I updated my Android SDK, and tried again. I had to restart the watch a few times after updating the SDK and it finally worked.
Any idea when will the official OTA from Asus be rolled out?
Heres how
kaylord84 said:
How did you guys push it via adb
Click to expand...
Click to collapse
I think a lot of us found our old ADB version out of date since it still worked on most phones. Android Wear obviously wants the latest and greatest, and it was the watch that complained about the ADB version. Here's where to grab a quick basic install of ADB and Fastboot from an XDA contributor - I installed it and once I restarted the phone and used the newer ADB to put it in recovery and sideloaded the file all was well -
Link to minimal install of ADB and Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Instructions how to sideload a FW package to the watch ( it's for 5.0.1 but same process, just substitute the new FW File)
http://forum.xda-developers.com/zenwatch/general/how-to-install-5-0-1-ota-via-adb-t2974659
Hope that helps you. It was a bit of a pain, but nothing overly cumbersome. Enjoy - if your like me waiting was only an option for a couple hours, after that it was lets see what we can do to hurry this along, lol!
kingkoopa85 said:
I'm really confused, I dont have bluestacks installed, its showing one device when i connect my watch, then when i reboot into recovery it shows the same device 2 times, one is sideload, the other duplicate is offline...its not allowing me to sideload the zip because there is more than one device or emulator attached, also tried adb kill-server then adb devices, still the exact same serial.... what am I doing wrong?
Click to expand...
Click to collapse
If you run the whole sideload process on Windows (I had to in the end because I didn't know how to get rid of one of the devices on Mac OS X) just disable one of the devices, check which one is still available in ADB. If it's the sideload version, great. In this case you can sideload the firmware. If it's the "offline" version, disable it and enable the other one again.
Kermit33 said:
Any idea when will the official OTA from Asus be rolled out?
Click to expand...
Click to collapse
As I posted above, I got mine days ago.
how do you disable a device? I think my problem is that both devices shown have the exact same serial numbers, once plugged in it shows one device, once it goes into recovery, there are 2, one offline, one sideload. I used the links above on a different computer and it does the same thing, after multiple reboots and adb kill server commands. sorry for being such a noob, I really don't want to annoy you guys. but thank you for all the help, I may just wait for the OTA update hehe.
Related
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Nobody?
hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
hxdrummerxc said:
Nobody?
Click to expand...
Click to collapse
only thing i can think of right now, before suggesting omap flash or odin, would be try a different usb port, another computer, another OS!
try installing the latest CWM recovery and see if it helps.
hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
Try going to settings and look for something related to Root Access and it would have three options:
1. Apps only
2. ADB only
3. Apps & ADB
Choose the 3rd.
You might have to hunt the exact location under Settings where this option will be available as I don't remember them exactly.
Hit Thanks, if this helps...
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
hxdrummerxc said:
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
Click to expand...
Click to collapse
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
freezer2000 said:
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
Click to expand...
Click to collapse
hi. i try all this ways. i know that my usb debuging have problem, in development option i'll checked this, and it says enable. but infact it's not enable and still i got device offline error.
also i use z4root app and when i touch on root, it says that rooting need usb debuging enable (please enable it)!!
then move me to development setting to enable that, but this was checked and enable.
is any way that we make device online from my phone? for example using terminal emulator to turn on usb debuging or turn it off. this way is only my way! any one know some trying this?
i also use usb debugger app, but it move me in settings too! LOL
i need enable my device to root that.
thanks every one
I know this is an old topic, but if somebody else googles it, I had that offline issue, the solution was to upgrade adb : http://stackoverflow.com/questions/10680417/error-device-offline
You simply need to upgrade to the latest version of adb. Went thru this a few weeks ago.
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
vbrtrmn said:
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
Click to expand...
Click to collapse
I don't know too much about adb, but I'll try to help
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
I just turned on my console and have come to the conclusion that the automatic update broke su. How, i'm not sure, but it would seem that possibly you'll have to restart the process from scratch, redo adb and reload su.
lets just hope this isn't a sign that all future automatic updates will break su.
*EDIT* So it would seem that there is problems with the drivers. I have gotten ADB to work once again by deleting all the OUYA drivers from my computer and following the steps found at https://devs.ouya.tv/developers/docs/setup HOWEVER this presents a problem in that the system is only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know). Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
After getting ADB back, I got SU back by running through the steps found here: http://forum.xda-developers.com/showthread.php?t=2272266 under how to install busybox, superuser, and su binaries. You should only have to go from step 1 to 4 on that one (only 4 if you still have the files on your computer).
I will note that the steps to get ADB on that second link did NOT work this second time. I'm not sure what this is due to. I'll be starting a new thread with this info, too.
JLCollier2005 said:
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Click to expand...
Click to collapse
Nope.
JLCollier2005 said:
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
[/QUOTE[
No drivers, running OSX & Linux.
Click to expand...
Click to collapse
Hard boot the OUYA and laptop, adb via USB seems to work again.
So far every OTA has removed su.
Sent from my GT-P3113 using Tapatalk 4 Beta
Some video tutorials to help out n00bs as well as confused members:
How to get working ADB and Fastboot, as well as drivers for Windows 8.1 64 bit:
Video embed not working? Click here for a direct link!
How to lock the bootloader and go S-ON:
Video embed not working? Click here for a direct link!
How to go S-OFF and unlock the bootloader with Firewater S-OFF:
Video embed not working? Click here for a direct link!
You are free to link to any of these tutorials or to this thread.
Enjoy these tutorials and leave a reply if you have any suggestions for future guides.
Good to see you over here on the M7 doing your thing like the old days wolf. Keep it up.:good:
synisterwolf said:
Good to see you over here on the M7 doing your thing like the old days wolf. Keep it up.:good:
Click to expand...
Click to collapse
Been so busy in the past few months or so that I couldn't do my helpful stuff. Now I have more free time.
Awesome tutorials! this is where I'm stuck at the moment.
I went as far as to restore my computer to Windows 7 and start over erasing everything. I've tried different USB cables. I know it won't work on my USB 3, i Have one USB 2, I believe I have the drivers installed. I even went as far as to download and install Cyanogenmod on my Verizon HTC One. Enable root, Apps and ADB. allow USB Debugging. I also uninstalled HTC Sync, because another XDA guy mentioned that it can get in the way of things. here is where i am stuck at when attempting to lock my Boot loader.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
So that is where I am stuck. I see my phone reads fastboot usb, and it will do other commands, so i know it is connected, just not recognizing it? Dumb question, but if I RUU to say 4.2.2, because my phone is able to do that, can I do a software update and install 4.4.2, would that LOCK my bootloader and get me on the right software, so that all i have to do is give the command to go from S-Off to S-On? or will that command even work for me because i cant get the command to even open the shell? Also, is there a way to manually install a driver? I go to my device manager in control panel, and I'm not seeing anything that says Other Devices > One.(UPDATE; I found where HTC is in device manager, I tried updating the driver manually, it say's that driver is already up to date.) and I've gone to the start menu > Run > and ran a command to allow me to install unknown drivers to Windows 7. I have also unplugged anything usb on my laptop, including my wireless mouse.
I've been trying really hard to get my phone back to stock to return back to HTC. Probably a solid 10 to 12 hours last night and this morning working on it. lol
Update: Am I supposed to do anything with Android SDK?
Update 2: I can flash Decripted RUU running adb on CMD with commands and have HTC's Official software running with no problem and it recognizes my phone plugged in. So i went back to Cyanogenmod for now. but for whatever reason, adb device and adb shell are not recognizing my phone that is plugged in
Update 3. Re-installed HTC Sync and installed HTC Sync Manager for the fun of it, and now daemon doesn't even show up when doing command adb devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
Update 4: I swear, when we get this working, I'm gonna send whoever a little kickback through Pay pal for helping out with my issues.lol. I feel that maybe it could be my laptop, I'll have to try my 10 year old toshiba.
BygSii said:
Awesome tutorials! this is where I'm stuck at the moment.
I went as far as to restore my computer to Windows 7 and start over erasing everything. I've tried different USB cables. I know it won't work on my USB 3, i Have one USB 2, I believe I have the drivers installed. I even went as far as to download and install Cyanogenmod on my Verizon HTC One. Enable root, Apps and ADB. allow USB Debugging. I also uninstalled HTC Sync, because another XDA guy mentioned that it can get in the way of things. here is where i am stuck at when attempting to lock my Boot loader.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
So that is where I am stuck. I see my phone reads fastboot usb, and it will do other commands, so i know it is connected, just not recognizing it? Dumb question, but if I RUU to say 4.2.2, because my phone is able to do that, can I do a software update and install 4.4.2, would that LOCK my bootloader and get me on the right software, so that all i have to do is give the command to go from S-Off to S-On? or will that command even work for me because i cant get the command to even open the shell? Also, is there a way to manually install a driver? I go to my device manager in control panel, and I'm not seeing anything that says Other Devices > One.(UPDATE; I found where HTC is in device manager, I tried updating the driver manually, it say's that driver is already up to date.) and I've gone to the start menu > Run > and ran a command to allow me to install unknown drivers to Windows 7. I have also unplugged anything usb on my laptop, including my wireless mouse.
I've been trying really hard to get my phone back to stock to return back to HTC. Probably a solid 10 to 12 hours last night and this morning working on it. lol
Update: Am I supposed to do anything with Android SDK?
Update 2: I can flash Decripted RUU running adb on CMD with commands and have HTC's Official software running with no problem and it recognizes my phone plugged in. So i went back to Cyanogenmod for now. but for whatever reason, adb device and adb shell are not recognizing my phone that is plugged in
Update 3. Re-installed HTC Sync and installed HTC Sync Manager for the fun of it, and now daemon doesn't even show up when doing command adb devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
Click to expand...
Click to collapse
Uninstall the phone in device manager. Disconnect the phone. Disable windows updates to prevent it from auto installing a generic windows driver. Then plug the phone back in and try to manually install the driver from the video.
Okay. I'll try that out here in a little bit. Another thing I found to be odd, is that my OS is showing up as blank. I hope it will show the correct OS that I'm on, when I get far enough to flash an RUU.
Success! I had to disable updates, even after that, it still would update when plugged in. So I uninstalled updates. Then, I had to catch the device drivers before updating by cancelling them. Installed drivers like in the video, followed steps, everything is a success! this post should be stickied, but that's just me. Good job!
BygSii said:
Success! I had to disable updates, even after that, it still would update when plugged in. So I uninstalled updates. Then, I had to catch the device drivers before updating by cancelling them. Installed drivers like in the video, followed steps, everything is a success! this post should be stickied, but that's just me. Good job!
Click to expand...
Click to collapse
Glad you got it working.
Windows update is nice, but it is really annoying when you want to manually install a better driver.
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
wellsheit said:
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
Click to expand...
Click to collapse
It should work. No promises though.
Sticky?
wellsheit said:
Great tutorials. Much appreciated.
Can you verify this is working for version 4.4.2? I gave up on my One a while back after running into 8.1 driver issues. Apparently that has been resolved now as well.
Click to expand...
Click to collapse
I rooted and got S-Off on Win 8.1. I was stock 4.4.2 at the time and never rooted a smartphone before. The tutorial for the driver was spot on. As for the other 2 tutorials, I didn't use them as I found the rest of the process to be pretty straight forward (using WeakSauce & Firewater to root and get S-OFF).
Vids now viewable in OP.
Link added to roll up in Development
dagrx8 said:
I rooted and got S-Off on Win 8.1. I was stock 4.4.2 at the time and never rooted a smartphone before. The tutorial for the driver was spot on. As for the other 2 tutorials, I didn't use them as I found the rest of the process to be pretty straight forward (using WeakSauce & Firewater to root and get S-OFF).
Click to expand...
Click to collapse
Excellent to hear. Been waiting for this to get sorted out. Will report back when I get time to sit down and run through it all.
I can confirm it works on win 8, got my surface pro adb and fastbooting like a baws in minutes. As above poster mentioned, you either have to uninstall and prevent auto device installation, or if you find it in device manager you can force update the driver , you may have to take the extra step to "Have Disk", manually select the androidusb.inf file from unpacked drivers, then select My HTC
Sent from my HTC6500LVW using Tapatalk
Files are missing from the first video, could you reupload or post another link for the driver?
nekubg said:
Files are missing from the first video, could you reupload or post another link for the driver?
Click to expand...
Click to collapse
Updated.
Thanks for the fast reply!
I am having issues, after following the steps. In ROM and recovery it shows up in ADB devices and device manager. However in bootloader it shows device manager, but not in ADB Devices. Tried multiple cables, including the original. Any ideas?
Plauges said:
I am having issues, after following the steps. In ROM and recovery it shows up in ADB devices and device manager. However in bootloader it shows device manager, but not in ADB Devices. Tried multiple cables, including the original. Any ideas?
Click to expand...
Click to collapse
What version of Windows?
If it is Windows 8 you need to make sure that you installed the drivers while signature enforcement was off. I have also posted an updated video with new drivers, give it a try.
So when I originally got my OP3 and rooted it, installed a recovery and installed SuperSu, I had basically no problems. Installed drivers I found on here and never had an issue. Today I found a guide on the OP forums to disable doze which I apparently need to do since certain notifications aren't working right. I plugged my phone in and tried to follow the instructions, listed here under push notification issues
https://forums.oneplus.net/threads/...3-guide-solutions-e-t-c.448097/#post-14886949
When typing in adb devices, my device shows offline. I have done numerous things to try and fix the issue which I will try to lay out here. Initially I didn't install adb or the drivers as the guide suggests, since I had already done that - but after things not working I did try that and that didn't help. Still receive the "offline" next to my serial number device. The device works fine, and I can see it and transfer files to it just fine in the MTP mode. I have also tried to "revoke" permissions like described in the youtube guide I found here https://www.youtube.com/watch?v=eSApv8NXqD4
However that didn't work either. I should note that even after revoking permissions and turning usb debugging on and off again, the phone never asks me to authorize my computer as it does in that guide. In fact I don't believe it ever asked me to authorize my computer even when I first got the device. I don't know if that is part of the issue or not. I have also used a different adb version since somewhere I found that you needed to use the newest version. The version I had was 1.32 and I found the newest here on the forums here http://forum.xda-developers.com/showthread.php?t=2317790 that it was 1.4 as the newest. That adb returns the same results.
I should also note that the guide I linked from oneplus never actually tells me to put the phone into fastboot mode to execute the command, so I tried it initially booted up, and then in fastboot thinking it was supposed to be executed there, however in fastboot mode the phone is not seen at all. adb devices returns nothing, and booted it returns offline mode. Please help me
Nobody?
Have you tried some of the suggestions on https://stackoverflow.com/questions/14993855/android-adb-device-offline-cant-issue-commands? I'm not really sure what the situation is like on Windows but first I'd ensure you've installed the latest official Android SDK just to rule out an issue with the version of ADB you're using. You could also try using ADB over WiFi.
Apart from that, you can probably get by without ADB for now. Just run the commands in a terminal emulator on the device and/or create an init script.
I am currently on Android Wear 2.0 preview 2. My Huawei watch is not being detected by my PC although I have ADB enabled. In fact, the watch is not even detected as an unknown device in the device manager. I am able to get Bluetooth debugging working. However, since fastboot doesn't detect my device I am unable to flash either a new recovery or upgrade my watch. I am able to enter the fastboot/recovery mode manually by clicking on the button when the huawei logo appears during boot. However, I get an error message saying /sdcard cannot be mounted and am unable to flash any zip file due to this using the Droid recovery. The watch boots up normally and works well otherwise except that i am stuck with the preview 2.0.
Is the issue due to a faulty cable or a badly flashed recovery or is there anything else i can try so that i can revert back to stock or flash a new rom? Any suggestion is greatly appreciated..
I'm having the same issue on two separate watches, and have been for quite some time. Have tried multiple computers, multiple chargers, to no avail... Using stock recovery, preview 2. Watch will charge, no problem, but the PC won't notice that the watch is plugged in in any way no matter fastboot, recovery, or just booted.
same here, watch will charge but no prompt to access interal memory. Is simply stock, so no preview version
Same here. Flashed the 2.0 preview and now can't get ADB through a wired connection. Hoping someone can help.
Are you guy's using linux? I had the same problem on multiple linux distro's. As soon as I went back to windows 10 I was able to connect through ADB and flash the beta firmware.
vicvon said:
Are you guy's using linux? I had the same problem on multiple linux distro's. As soon as I went back to windows 10 I was able to connect through ADB and flash the beta firmware.
Click to expand...
Click to collapse
I've tried on Mac OS X Sierra and Windows 10.
firefurby said:
I've tried on Mac OS X Sierra and Windows 10.
Click to expand...
Click to collapse
On Windows 10 did you install all the ADB stuff? I had to install a bunch of stuff for ADB to actually work.
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
vicvon said:
On Windows 10 did you install all the ADB stuff? I had to install a bunch of stuff for ADB to actually work.
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Click to expand...
Click to collapse
Yeah, I've tried the Minimal ADB and Fastboot as well as a full install of Android Studio. I'll give this walk through a shot too. I'm desperate.
Anyone have any luck getting their watch to be recognized again?
try pdanet adb drivers
also, sometimes even if fastboot doesn't register as detected, you can still flash anyways
Anyone ever get anywhere with this? I'm still hoping for a solution.
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Hmmm... I'm using a Mac mainly. I'll give this a try on my windows machine later. Thanks!
Pkt_Lnt said:
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
Pkt_Lnt said:
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
Click to expand...
Click to collapse
The problem is that you can´t do anything if the watch isn´t recognized on the pc, it doesn´t matter if an adb driver is installed or not...
Same problem, watch is charging only, tried 7 pcs an no one can handle the device...nothing.
Same here. The Android Wear version on the watch is 1.3.0.2145535.
Device Manager does not detect the watch at all. Nada (no entries with exclamation marks). Just charging. Does that mean the cable has a defect?
It's driving me nuts, as I am not able to get OTA updates, adb debugging would be my only chance to upgrade to Android Wear 1.5.
Build Number: LCA37B
Android Wear: 1.3.0.2145535
Goolge Play Services: 7.8.99
Android OS: 5.1.1
SirRobin78 said:
The problem is that you can´t do anything if the watch isn´t recognized on the pc, it doesn´t matter if an adb driver is installed or not...
Same problem, watch is charging only, tried 7 pcs an no one can handle the device...nothing.
Click to expand...
Click to collapse
mysteray said:
Same here. The Android Wear version on the watch is 1.3.0.2145535.
Device Manager does not detect the watch at all. Nada (no entries with exclamation marks). Just charging. Does that mean the cable has a defect?
It's driving me nuts, as I am not able to get OTA updates, adb debugging would be my only chance to upgrade to Android Wear 1.5.
Build Number: LCA37B
Android Wear: 1.3.0.2145535
Goolge Play Services: 7.8.99
Android OS: 5.1.1
Click to expand...
Click to collapse
Have you tried just running the flash-all.bat? I've have seen posts and experienced it myself that the watch is not detected after a screw up on my part, yet the flash-all.bat will run and install the OTA, even though I was in panic mode. Manually boot the watch to bootloader mode with the watch button and try, it might work, worth a try. Good luck.
Even though I was pretty convinced that this could never work, I nevertheless gave it a try. After executing flash-all.bat it just says < waiting for any device > and does nothing, as was expected by me. Would have been magic, if it had communicated with the watch having no entrypoint for it in the system.
Pkt_Lnt said:
Have you tried just running the flash-all.bat? I've have seen posts and experienced it myself that the watch is not detected after a screw up on my part, yet the flash-all.bat will run and install the OTA, even though I was in panic mode. Manually boot the watch to bootloader mode with the watch button and try, it might work, worth a try. Good luck.
Click to expand...
Click to collapse
mysteray said:
Even though I was pretty convinced that this could never work, I nevertheless gave it a try. After executing flash-all.bat it just says < waiting for any device > and does nothing, as was expected by me. Would have been magic, if it had communicated with the watch having no entrypoint for it in the system.
Click to expand...
Click to collapse
Use the watch button to reboot to bootloader when you the the < waiting for any device > message and it *might* work. That is what happened to me. Sorry I was not clear about that in my post above. You need to boot into bootloader mode while that message is displayed.
Tried that, as well. Doesn't make any difference.
Thanks for the suggestion, though.
Pkt_Lnt said:
Use the watch button to reboot to bootloader when you the the < waiting for any device > message and it *might* work. That is what happened to me. Sorry I was not clear about that in my post above. You need to boot into bootloader mode while that message is displayed.
Click to expand...
Click to collapse
Same issue here
I'm also having this problem but not on Android Wear 2. I'm using stock, non rooted, and locked bootloader and therefore Android Wear 1.x. I only became aware of this issue when I decided that I wanted to get Android Wear 2 on my watch (using the preview).
The watch charges but in no way can I get my PC to detect that the watch is actually there, tried two Windows 10 PCs but both have the same issue. I think the problem is either with the watch itself or with the charging dock/cable. I rebooted into fastboot mode but this does not make a difference. The fact fastboot also does nothing makes me think its more likely that the charging dock is at fault. Unfortunately, installing ADB/Fastboot drivers is pointless if the PC can't even see the device to communicate with.