Glad to help you out here, but I need to prod you for some more info.  What model phone and adroid version? is it rooted?

Lesson 2
Part 2: adb commands

Adb commands can be given to the device while booted normally, or in most recoveries.  Adb debugging is enabled by default in almost all custom recoveries, so theres no need to boot up, enter your info, and enable debugging. 

The most common adb commands are the push/pull commands.  Here is the syntax.

adb push [local path/filename] [device path]

adb pull [device path/filename] [local path]

In a recent case I used these commands to pull a Nandroid before wiping my device that had a broken screen.  I used the command to pull an entire folder.

C:\Users\Username>adb pull /sdcard/clockworkmod/ \clockworkmod\

This created a parent folder at C:\Users\Username\clockworkmod\ and included all subsequent files and folders. 

Once many users become comfortable pushing the limits of their device, they opt into rooting.  With the Nexus 7, the easiest method of obtaining root is a flashable zip that can be flashed in any custom recovery.  So download the zip UPDATE-SuperSU-v1.04.zip from here move to the command promt path and use:

adb push UPDATE-SuperSU-v1.04.zip /sdcard/
Install the zip through recovery and you're rooted!


A useful trick for those more seasoned adroid users.
adb pull /system/build.prop build.prop
use a text editor to make changes
adb remount
adb push build.prop /system/build.prop

Notice the use of the "adb remount" command.  This mounts the /system/ as read/write.  There are other ways to do this, but that gets into the adb shell commands.  Shell commands are not exactly adb commands, but linux terminal commands.  They are more advanced, so we'll get into that later as well.

Heres a useful, but less common command: "adb install [local path/filename.apk]" You can install apps from recovery or fully booted with this process.  This is another method of sideloading.

This thread will be dedicated to learning about and teaching our members about fastboot and adb commands.  It is a work in progress.  If you have any specific questions, please don't hesitate to ask or PM.  This is a guide specific to the Nexus 7 running fastboot commands from a Windows PC.

Lesson One
What is fastboot and how do I use it?

Fastboot is a tool used by the Android development platform, mainly for diagnostic and flashing partitions, over a USB interface.   There is a driver seperate from your USB device drivers that allows the communication protocol.  I will assume that the normal device drivers are installed before proceeding to fastboot commands.  The fastboot tool is device specific.  The tool is available in the Android SDK and must be compiled.  Most toolkits for your device have the drivers already compiled for you and are contained in the root of the tool folder. 

In order to use the fastboot tool, your device must be in the fastboot mode.  The simplest way to get there is to hold both volume buttons while powering on.

I will assume that this lesson is redundant if you are using an Android SDK.  For those who are not, you must execute the fastboot commands from a command prompt within the directory that the tool is located, unless the tool binary is in your PATH. It is easy to add the tool binaries to your PATH, but you must have a folder that is stationary containing the tools and binaries.  on a windows computer, clicck START>right click My Computer>Properties>Advanced>Environment Variables>System Variables>double click Path.  Add the full path to your tools folder. 

If this seems too complicated, close all windows on your PC. Click Start>Run>cmd [hit enter].
This should bring up a command window.  This will be where the fastboot commands are executed.  There should be a command prompt with a file path.  You need to place the fastboot file in this file path.  Once the files are placed in this path, boot into fastboot mode, open a command window and type "fastboot devices" you should see this.

fastboot devices
list of devices attached
[device serial number]         device

If this is not what you see, double check the path that you entered or make sure that the files are placed at your command prompt path. 
If you see the serial number you have already begun sucessfully using fastboot commands.


What is "adb" and how do I use it?

Adb is what is known as Android Debugging Bridge.  It is another communication protocol that functions inside the Android operating system. There are three portions of the protocol: client, server, and daemon. The client is run from the computer, the server is also on the computer, but only manages the communication, and the daemon runs on the device. This protocol can move files and perform functions with your data inside the OS.  With Android version 4.2.2 there has been a security feature added requiring one to unlock the device and allow the connection upon the first connection to a new client. 

Adb is used through a command prompt as well.  USB debugging is required.  Go to Settings>Developer Options>Android Debugging.  Make sure this option is checked.  If you extract the contents of the download folder and add it to your path, there should be no further setup.  If you were not able to setup your path, follow the same procedure mentioned above by manually moving the files.  You should be able to begin adb commands. Open a command window while connected to USB with debugging enabled (you should have a notification icon, windows may also install new drivers on first connection) type "adb devices." you should see the following. 

adb devices
* daemon not running. starting it now on port 5037 *
* daemon started sucessfully *
List of devices attached
[device serial number]          device



download link for Nexus 7 platform-tools
download here

I would try the hard reboot (hold down all buttons until it turns off) and boot into bootloader (hold both volume buttons while turning on)and then press power again to boot normally when the screen displays start in the upper right.

Post moved to What can you do with "fastboot" and "adb" commands?

New version of recovery? Simple.  Download to PC and rename to recovery.img.  Boot into fastboot mode.
fastboot flash recovery recovery.img

=ROM toolbox finds the trashcan.

I'm not badmouthing the app.  There are some uses for it.  Ever tried changing a font face with it or applying a incompatible boot splash screen? Frankly, it can be scary.  I do use ROM Manager though.  It will update Clockworkmod Recovery, but not the touch version without a fee. I have the Premium Version, but it still charges for some features. I used it the other day to manage my Nandroids.  I couldn't locate the new directory. 

By the way, ES File Explorer has an integrated .prop file editor. 

Do you know if it was low on battery during the update?  What is the current battery status? Try holding all three buttons on the side for 30 seconds, then power it back on. 

Do you have an existing system that you are trying to monitor, or are you doing research to see what would be best for your situation?

There are a couple methods, but the baby monitor specific route is more expensive.  Of course theres no price you can put on a baby's well being, but I prefer the alternative method.  If you buy a baby monitor that has an app, the video feed will be exclusive to that app, and you have to pay a bit more for additional cameras that are matched to the frequency.  I prefer using a wireless IP camera. 

You can set up any wireless IP camera with sevaral apps that are universal across all smartphones and tablets.  They are secure video feeds and offer more options.  You can link multiple cameras together and even use cameras with built in pan and tilt.  My brother has a setup that he can monitor the baby in the crib with infared lighting while he sleeps.  If he rustles, the app can alert him.  He can also speak through the two cay communication built into the camera to calm the baby.  Works well with the cats while he's away too.  He has four cameras that he can control remotely to monitor the entire house.  I've been thinking about doing this myself.  One app that comes to mind is IP Cam Viewer.  Most wireless IP cameras will let you know what the recommended app and compatability is.  I would do some research on the cameras that have the features that you are looking for and the associated apps.