This is an easy way to skip the wait when a new version of Android is released for Nexus devices. Note that this process is more complicated than simply waiting for an over-the-air update. To flash a system image, your device will need to be unlocked. Nexus devices allow you to unlock their bootloader with a single command. You can unlock your boot loader in several different ways. For example, there are separate images for the Nexus 7 with Wi-Fi only and for the Nexus 7 with cellular data.
Make sure you download the right one. Download the file to your computer and use a file-extraction program, like the free 7-Zip , to extract its contents to your ADB folder.
if you're having trouble with OSX + fastboot like i did - OnePlus Community
Sadly, all I've found on the internet are variations of "unplug and replug the device", which is obviously not a solution for us we can't spare a human being to sit by the CI server to unplug and replug devices before each build. While approaching the problem I thought that if at the OS level the device is found, that's at least a start.
I've attempted a few rather lame commands to "refresh" all USB activity, but I've gone nowhere. My lurking of the ADB source code was a very, very long shot. So at this point I'm all ears for a solution that would allow us consistently running Android on our CI server. Be it a few commands before each Jenkins job, patching ADB or any other black magic trick.
Found a way of solving it, so posting here for completeness. Please note that I'm not saying this is the best way of solving it, but it's worked for us.
So, we realised the problem happened after long periods of CI inactivity in the range of hours. So we created a simple script that calls adb devices every 10 seconds. And the problem is gone, no more "waiting for device" issues. I believe the problem is that you are allowing Jenkins to start the adb server. The causes problems because Jenkins jobs are associated with shells that come in and out of existence. If Jenkins kicks off the adb daemon with an "adb devices" call for example , then the adb daemon will be owned by some short-lived Jenkins shell, and when that shell finishes executing and closes, the adb daemon will be cleaned up, until it is started back up automatically by another adb call.
This results in a cycle of starting and stopping the adb daemon, but what you want is for it to just stay up indefinitely.reohunjochec.gq
This is intentional, so your files are invisible to the user of the connected computer. Pull down the notification from the top of the screen of the smartphone while it is connected to your computer. From here, press on the USB connection type. We found success with both options.
Click on the line displaying your device, and then click Install. This should install the appropriate ADB drivers for your smartphone. If you have problems, you need to open the Device Manager , delete existing entries with your smartphone and repeat the installation. Now we want to make use of the ADB drivers. Unpack the archive and open the SDK Manager. Wait ten seconds, until the right window see above opens. Next, open up the new platform-tools folder in the previously extracted folder.
Hold shift and right click anywhere in the white space of this folder and click Open a command window here. With your smartphone connected via USB to your computer, type in the command window adb devices. On your smartphone, you will see a warning message bottom-right image. Once you have enabled USB debugging on your device and allowed it from the computer pictured above , you device should appear in the device list within the command window. Firstly, they eliminate the hassle of drivers.
Step Two: Install ADB and Fastboot
Secondly, the ADB tools keep themselves up to date thanks to simple package management systems. Linux users need to look in the package system for android-platform-tools and install it. Subsequently, the ADB tools should be defined globally, so you are able to use the following ADB commands in the command line. The idea here is that you make a full backup of your app data. In practice, the results are unreliable. Not all apps allow for an ADB backup, meaning you might need to find an alternative method. With this command you will receive an overview of all devices connected to the computer device with ADB support.
Here you can see the device identifier and the status.
Once it is in this mode, you can communicate with the device via the fastboot command. To take a screenshot, saved to your computer. More complex installations, such as those of Custom ROMs, however, are done through the fastboot interface. Command Not Found: No Device: Your USB cable is not connected properly, the ADB interface on your phone is not running or your computer does not recognize your smartphone. Try using a different USB port, another cable, enable USB debugging, check the drivers, the computer, and restart your device.
Server is out of date: The version of ADB Tools on your computer and the version of Android on your smartphone must be compatible. If they are not, this error occurs. Update your version of ADB Tools. Waiting for device: