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.
Related
The easiest way of getting ADB to work:
Turn your phone OFF (Yes, off)
Connect it to your pc and wait for windows to finish "installing the drivers"
Try ADBing by going to ure fastboot folder (assuming it has the ADB executable inside the folder as well).
You could check if your device was recognized by firing
Code:
adb devices
If it doesn't show anything then do the following:
Grab the appropriate pc drivers from here: http://www.android-advice.com/2012/how-to-root-the-htc-one-x-and-htc-one-s/
Extract the drivers
Now go to Start menu and right click on my computer and then click manage.
Now go to device manager and there you should see your connected One X listed as being without a driver.
Right click on that entry and select 'update driver'
Now tell it that you have the driver on local disk and then browse to the folder you extracted.
Update your driver.
Disconnect and reconnect the device and try ADBing again.
Should work.
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
EddyOS said:
If your phone is off then Windows won't see it. Just install HTC Sync (so you get the drivers - you can uninstall HTC Sync afterwards if you're not going to use it) then plug the phone in when booted into Android. Repeat process when in FASTBOOT to get Windows to see the phone in FASTBOOT mode as well
Simples!
Click to expand...
Click to collapse
That is the thing -- IT DOES SEE IT! Try it yourself.
I didn't think it would but Jotha told me that it would. I tried it and it worked. I was surprised.
Yes device is seen through adb when off.
This is because as soon as you plug the USB cable, offmode comes up with charging and ADB support
Offmode is embeded in the recovery partition
PS: This needs latest clockworkmod recovery to work...
Latest ADB?
Hi!
When i was restoring my Sensation to S-ON i noticed that ADB was complaining about version out of date something....
Where can i get the latest version of ADB for using with my One X when i've decided if i should wait or use hTC bootunlocker...
Is there a way for Linux?
D0GuKaN said:
Is there a way for Linux?
Click to expand...
Click to collapse
Android SDK straight from Google should take care of that.
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
DoeBoi said:
Also, use HTC USB cables, sometimes using non-standard USB cables can make searching for devices impossible.
Click to expand...
Click to collapse
No. As long as the cable is properly USB 2.0 compliant, it WILL work, otherwise HTC CANNOT certify against USB 2.0. Tried with proper Nokia, Sony Ericsson, Samsung and Google cables.
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
tashunke said:
that doesn't work for me.
I tried everything, adb only recognizes my phone when its ON.
Click to expand...
Click to collapse
See here a few posts back:
You have to have the latest clockworkmod recovery.
Can you help/guide me on how to install it ?
Sorry for being a dummy.
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
RaVe-N said:
Is there any way with an adb command that we can tell what bootmode the phone is in?
I.E: hotboot or fastboot mode?
Using adb get-state they both return "unknown"?
Cheers...
Click to expand...
Click to collapse
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
rilorolo said:
Huh? It's OFF. My guess would be that it's not in any BOOT mode.
Click to expand...
Click to collapse
Never mind... I found the androidlib.DLL (I think that's wrong, but its a .net DLL available here on xda) and that manages to return fast boot so I can tell programatically what state it's in...
Thanks
Thats Work
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
C:\adb>
Click to expand...
Click to collapse
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Thibor69 said:
.
Please - anyone have any advice as to what could be stopping me from using adb ( from my phone to my PC ) ?
I been working on this for a couple days now, and gotten nowhere. Any thoughts at all ???
Thanks
============================
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
Click to expand...
Click to collapse
I can understand the difficulty. This problem is pretty common because there are no official drivers for Win10. These drivers work best on XP. I also could not get the adb to work on my Win10 so I installed Ubuntu and rooting/installing ROM's from ubuntu is a breeze.. srry for not hvng a solution for this.
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed
I was having issues with adb not finding my device. These drivers worked for me...
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app
Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all
confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless
If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2
I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790
Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition
jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.
For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed
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.
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.