Warning: If you aren't experienced with Android or ADB, or are wary about tinkering in recovery mode, do not attempt the following. I'm not responsible for any damage or bricking occurring after these steps.
Please also note that this will only work if you are already on 4.4W.2, build KNX01W.
Step .5: Download the OTA here. *big thanks to hedsick for providing the OTA link!*
1. Set up ADB (numerous tutorials on the internet)
2. Connect your watch via the charging block to a USB port on your computer
3. In the Settings menu on the watch, go into "About"
4. Go down to where it says "Build Number" and tap on it a bunch of times until the toast message says "You are now a developer!"
5. Swipe back one menu and head into the new menu that showed up below About, called "Developer Options."
6. Enable "ADB Debugging." At this point your computer should recognize the watch and take a few seconds to install the proper drivers
**6a.** Unlock your phone, and check the box that says "always allow from this computer" and accept the authorization by clicking "OK"
7. Open up a command prompt and type "adb reboot recovery"
8. Once you get the Android with the red triangle, swipe down to bring up the menu, and swipe down again to select "Apply update over ADB"
9. Swipe **left or right** and orange text should pop up that says "Now send the update via ADB"
10. Back on the computer, type "adb sideload C:\whatever\path\to\otafile.zip" (replace that with the actual path)
11. It will take about 5-7 minutes to update, once it's done the menu with the Android and red triangle should pop back up.
12. Make sure "reboot" (the first option) is selected (you may have to swipe down to bring up the menu again) and swipe **left or right** to select it and reboot the watch.
Voila, after rebooting, you should be on 5.0.1, build LWX48S.
*Note: There are reports of a supplemental LWX48T build going out. This is mostly seen for Moto 360 users so far, and it can be assumed that this is due to the non-centered watch faces. I haven't seen any issues with watchfaces so far, and seeing as how our builds are so close (S vs T), I doubt we'll get another OTA. But, if there is a new one, following the same steps above will work.*
Do you know where I can get the drivers? My computer isn't automatically downloading them. I looked on the Asus website, but they weren't there.
Edit: Nevermind, I got it.
Thanks, worked like a charm after the PDAnet driver install for my computer!
Thanks! Great step by step instructions. Took a cue from luckdog and used PDAnet to install the drivers.
Berzerker7 said:
Warning: If you aren't experienced with Android or ADB, or are wary about tinkering in recovery mode, do not attempt the following. I'm not responsible for any damage or bricking occurring after these steps.
[...]
Click to expand...
Click to collapse
Beautifully written step by step. Most of the ones I've read left off the 'pull down to get menu' and the swipe steps. Very well done!
Thanks for the rundown. I'm starting to get sick of the click on build number 10 times to become a developer thing. Anyway, it was very easy to follow and very easy to do, though I agree without adb experience it can be scary and is definitely a "try at your own risk".
gazelem37 said:
Thanks for the rundown. I'm starting to get sick of the click on build number 10 times to become a developer thing. Anyway, it was very easy to follow and very easy to do, though I agree without adb experience it can be scary and is definitely a "try at your own risk".
Click to expand...
Click to collapse
Hi, i tried my best to sideload the 5.0.2 through adb. I have used the 15 seconds ADB Installer v1.4.2 and I am able to push it into recovery. But when I am in recovery it is not recognized the computer /the drivers are not installed. Message: Device not found.
Any ideas how to solve this?
davidl1983 said:
Hi, i tried my best to sideload the 5.0.2 through adb. I have used the 15 seconds ADB Installer v1.4.2 and I am able to push it into recovery. But when I am in recovery it is not recognized the computer /the drivers are not installed. Message: Device not found.
Any ideas how to solve this?
Click to expand...
Click to collapse
For me it didn't connect and appear as a device until I chose the recovery option to "Apply update over ADB". At that point it appears as two devices, one for single ADB and one for ADB composite. I was only able to get it to work by installing a driver for the single ADB device, and NOT for the composite one.
Related
After toying with jailbreaking/modifying iPhones, taking a Unix/Linux course at a local community college, experimenting with different linux operating systems, and stalking these forums for about the last month, I figured I would purchase myself a "Bricked" Kindle Fire and have at it for funsies. Well, I bit off more than I could chew. I'm stuck as much as the Kindle Fire is at what I think is the boot screeen for the FireFireFire Bootloader. It powers on and loads the Kindle Fire blue logo with a v1.4a in the top corner. Then, selects and deselects "normal boot" "recovery" "reset boot mode" on it's own without ever picking one! I'm not sure what the prior owner did to this thing but I'm assuming they at least attempted to root it. I've tried SoupKit, KFU, Kindle Fire Unbrick Utility, and tried adding the google USB driver for the thing in Windows 8. The worst part of it is that it's not recognized in either Ubuntu (terminal - tried lsusb) or Windows 8. Any help, suggestions, or even comments telling me that I'm dumb for doing this would be much appreciated. Thank you!
Your saying it runs through the bootmenu selections on its own? That`s a new one for me. Have you tried to select one? To get the Driver installed on windows 8 you must disable driver signature verification then install the driver.
It doesn't respond to me trying to select any of the options. It just cycles through each one from top to bottom. Last night I went through the steps to disable driver signatures (posted here: http://forum.xda-developers.com/showthread.php?p=34626361) I was successful in installing the drivers but the computer still does not recognize the device. I was also able to download/extract the Android SDK to my computer. I ran ADB and it showed the driver was installed. I believe ADB should recognize the device?
There are two methods on that page which one did you use? The one in post #8 will work but I just simply hold shift then click restart then follow the rest of the instructions to disable it. If its in fastboot adb will not recognize it but I bet your shell is corrupted as well when you select recovery it should go there unless your recovery is broken.
I followed the instructions on #8. Additionally, the LED on the power button does not power on. I don't know if that's any indication of anything or not.
When you plug it to the pc or the wall charger? To the pc isn't that strange could be the cable itself, to the wall might raise an eyebrow to early to tell. Im gonna send you a pm.
CH1215 said:
I followed the instructions on #8. Additionally, the LED on the power button does not power on. I don't know if that's any indication of anything or not.
Click to expand...
Click to collapse
It looks like you need to replace the bootloader...probably via usbboot.
Arrrgh The dreaded broken bootloader time to work a little firekit.
I did try a few of pokey9000's firekit options in SoupKit but to no avail. I am a bit confused as to where I need to place my metal object to "short the point" as I couldn't find any threads with pictures. I will continue to reasearch/apply usbboot and return to you with my findings. I really appreciate the help both of you have given me.
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 this is the test point there is a small metal frame surrounding it . Start the script when it says waiting for omap44xx contact the test point and just as you lean whatever you are using to short against the small metal frame and plug in the usb at the same moment. Keep it shorted till the script runs through 4 stages. The script you need to run is the usb fix parts install fff and twrp. It is best to brace the kindle against something so it does not slip as your trying to perform this maneuver. Caution not to contact anything but the test point and the metal frame to prevent permanent hardware damage.
I used a modified safety pin, used the correct option in firekit, and followed your directions, but it didn't seem to do anything. I can tell that the prior owner(s) had tried this before as the area I am to place the pin looks a bit scratched. On another note, I had to boot my windows partition to get something off of there late last night and I left the device plugged in. Surprisingly, this morning the device was showing up in the system tray as "kindle." I was curious and looked at the properties and it's showing the drivers are working and that it's an "Android phone." I don't know if this is a good indication of anything or not.
When you exspand android phone in device manager what does it say? Shift+right click on the tools folder select open command window here
Code:
adb shell
see what you get.
Thepooch said:
When you exspand android phone in device manager what does it say? Shift+right click on the tools folder select open command window here
Code:
adb shell
see what you get.
Click to expand...
Click to collapse
"Android Phone" expanded in Device Manager shows "Android Phone ADB Interface." When I try the command you suggested it says, "error: device not found."
Just got my galaxy nexus (coming from evo lte). I'm trying to do all the fun stuff, but am kinda stuck. Any time I try to install the drivers I get "drivers not installed" with the error in device manager "SM Bus Controller no driver found" and "PCI Device no driver found". However, when I plug my Galaxy Nexus in, it says "ready to use" for the following: SAMSUNG Mobile USB Composite Device, Galaxy Nexus, SAMSUNG Android ADB Interface. The main thing I am getting is "waiting for device" to unlock bootloader. Any ideas?
Sounds like you're missing motherboard drivers.
Man I'm having the same problems with the drivers/connecting myself. Was trying to root and was able to recognize with PdaNet then once I unlocked the bootloader I was unable to flash a recovery. Now still can't get my GNex connected so hopefully our problem is solved soon.
RoadToNever said:
Sounds like you're missing motherboard drivers.
Click to expand...
Click to collapse
I fixed the mobo drivers. Reinstalled the USB drivers. However, it still hangs on the fastboot screen and adb is still waiting for device. Any clue?
I'm an idiot
Guess I skipped over this last night...im an idiot
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Your phone will ask if you want to unlock it. Select "Yes" by using the volume keys and use power to select it.
Now, navigate to "Recovery Mode" with the volume keys. Use power to select.
A screen with another Android will pop up. Press Volume Up and Power at the same time.
Select Factory Reset. This process may take a few minutes. Be patient and let it work.
Once finished, select "Reboot."
Your phone is now unlocked!
I've been spending the better part of the day trying to resolve this problem, including poring through a good chunk of the 200+ pages of the 10.1 Nightlies thread over in development. I've been trying to set up ADB over USB with CM 10.1 however it does not register at all except as a USB mass storage device. I've tried uninstalling drivers and reinstalling them both directly from Samsung in the driver package as well as via Keis, having it auto-detect in Download mode, as well as using the modified INF drivers that have been floating around but nothing seems to work. I've tried right-clicking the four unknown Android devices in the Device Manager to install the aforementioned drivers but nothing seems to take. I've also attempted to follow the instructions at .ttp://itekblog.com/cyanogenmod-10-1-with-adb-tutorial to no avail. The most recent ADB from the SDK doesn't pull it up when listing devices either; please see the attached image.
Any help with this would be greatly appreciated.
You can use adb devices in command prompt and it should show your phone or use clockworkmod app and application for computer will work . Also easy tether pro works need the app on phone and computer as well.
Sent from my SGH-T989 using Tapatalk 2
ADB devices in the command prompt displays no devices as connected. From what I've been able to find, it seems to be a driver problem but I'm at a loss as to how to get it installed correctly. I have CM10.1 as well as TWRP installed and working fine, but I've been trying to do some application development recently and this is a major stumbling block, since if I can't get this sorted out I'll probably end up having to go back to using stock.
Edit: I have since been able to fix it. Here are the steps I followed.
1. Right click on the device in the device manager.
2. Click "Update Driver Software".
3. Click "Browse my computer for driver software".
4. Click "Let me pick from a list of drivers on my computer".
5. Select Manufacturer: Google Inc. and Model: Android ADB Interface.
6. You may receive a warning at this point. Ignore it and click yes.
7. It should be working at this point.
Stromgarde said:
ADB devices in the command prompt displays no devices as connected. From what I've been able to find, it seems to be a driver problem but I'm at a loss as to how to get it installed correctly. I have CM10.1 as well as TWRP installed and working fine, but I've been trying to do some application development recently and this is a major stumbling block, since if I can't get this sorted out I'll probably end up having to go back to using stock.
Edit: I have since been able to fix it. Here are the steps I followed.
1. Right click on the device in the device manager.
2. Click "Update Driver Software".
3. Click "Browse my computer for driver software".
4. Click "Let me pick from a list of drivers on my computer".
5. Select Manufacturer: Google Inc. and Model: Android ADB Interface.
6. You may receive a warning at this point. Ignore it and click yes.
7. It should be working at this point.
Click to expand...
Click to collapse
Is this fix also for my Xperia Mini? I'm using PAC Rom which based on CM10.1 as well and I also can't connect to my phone via ADB
My ADB is working whenever the phone is in Fastboot or Recovery but not when it is fully booted.
I can't find the developer "google inc". I guess i'll have to try some of the other steps that you have taken.
EDIT: i followed this guide even though it is for a Samsung phone and I have a HTC One X
hxxp://itekblog.com/cyanogenmod-10-1-with-adb-tutorial/
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Downloaded the latest driver zip from Google
Open Device Manager
Expand Portable Devices
Right-click on the Phone entry (notice, that's the entry, "Phone". Not Razer.)
Choose Update Drivers
Browse my way to the drivers folder and click Next.
Windows then returns immediately "The best drivers for your device are already installed", and shows that it's an MTP USB Device.
I noticed that under USB devices, there's an ADB Interface device listed, and I get the same results when I try to update that, too (excepting it says it's an "ADB Interface" device, of course). I have tried uninstalling both devices to get the drivers to install, but no such. I've rebooted both phone and computer as well.
On the phone, USB Debugging is turned on, and USB mode is set to MTP file transfer.
Please help!
Figured it out...
tkarakashian said:
Howdy,
I'm trying to get my phone unlocked and rooted. As the first step, of course, I'm trying to get the Google USB drivers to install, but I simply can't. I feel like I'm the only person having this issue, though because I cannot find a solution... The steps I'm following:
Click to expand...
Click to collapse
In case anyone else is seeing the same issues, I wanted to put my resolution up: I'd been trying to install the drivers with the Razer booted. On a whim, I rebooted it into Download Mode using "adb reboot bootloader". Once there, I had an Android Device listed in Device Manager. I ran the driver update wizard, and installed the "USB ADB Interface" option from the choices presented. I was then able to run the OEM unlock command and received the confirmation prompt on the Razer. Yay!
Now, since it's been so long, I've got to re-back-up everything so I can actually do this thing. LOL
Here's the PDF from Razer's how to install a factory image over PC guide. It explains how to do it all
s3.amazonaws(.)com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf (remove parantheses)
Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows​
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Nice... Thanks for the guide... Many people needed it... Was about to make one myself...
Great. Many many thanks bro
kickyvivi said:
troubleshoot guide for updating the adb and fastboot drivers manually in a pc running any version of windows​
first, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
pre-requisites:
* pc running windows 7/8/10
* internet connection (just 20mb)
* working usb cable
steps:
(1) download the [official][tool][windows] adb, fastboot and drivers - 15 seconds adb installer v1.4.3 from xda
link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) install it with "y" confirmation for all 3 options and reboot the pc
(3) disable the internet connection of your pc
(4) reboot your phone to fastboot mode and plug it to your pc's usb 2.0 port (important)
(5) open device manager on pc and scan for hardware changes from the option if your device is not listed already
(6) if it shows 'asus android device' -> "asus android bootloader interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) now scan for hardware changes (magnifying glass icon)
(8) it will show 'android' with an ! Symbol
(screenshot 3)
(9) right click -> update driver -> browse my computer for driver software
(10) choose "let me pick from a list of available drivers on my computer"
(11) choose "android device" or "asus android device" or similar option and confirm it with yes or next option
(screenshot 4)
(12) a warning will pop up, press 'yes'
done
(13) go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
I am having same problem... Did you find any solution for it?
kickyvivi said:
Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows​
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
Hello, I followed your mentioned steps but in my drivers its showing "Samsung Android Device" is that okay for my asus zenfone max pro m1 device? Or there is one portable device option, is that it?
Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!
kickyvivi said:
(12) A warning will pop up, press 'Yes'
Done
Click to expand...
Click to collapse
After I completed all the steps, my phone showed on screen "press any key to shutdown" and even in device manager it shows android ADB interface as hidden. Help please. Rebooting again to fastboot mode doesn't help because it shows the same screen "press any key to shutdown" on reconnecting with PC.
May Asus x01bd can't in to the mode fastboot..how to solved it?
Kajin660 said:
May Asus x01bd can't in to the mode fastboot..how to solved it?
Click to expand...
Click to collapse
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it
D0CT0RFATE said:
Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!
Click to expand...
Click to collapse
this same with me,, n i donk know how it is??
my phone asus x01bd
Nightmonkeyps said:
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it
Click to expand...
Click to collapse
can u explaining me?? sorry i dont understand what u mean??
Kajin660 said:
can u explaining me?? sorry i dont understand what u mean??
Click to expand...
Click to collapse
Well you know how there's a BIOS in your PC which contains the basic commands required to run a computer. There is a setting called secure boot inside your BIOS. You need to turn it off and then install fastboot tools. To open the BIOS, repeatedly press F10 or F8 on your computer while it is opening. This is how it worked for me atleast
Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
this happen to me,, and i have solved this,,
step:
1. U must flash ur Phone via qfil,(*)
,than u will lost ur IMEI and SN will Change to 111111,, but dont worry thats can be back again
2. next step is u must recover ur IMEI and SN back (in tele group u wil found the step) after that U just flash stock firmware modified (via TWRP/ORFOX)n then ur phne willl back normally
Note : (*) in firmware for flash via qfil replace the recovery.img with twrp/orfox (rename To "recovery.img") this will bring u a twrp/orfox recovery after flash via qvil
i hope this can help..