Prevent exausting CPU in WaitForDevice method
Entering an endless loop will exaust CPU.
  Since this method must be called in a child thread in Windows Presentation Foundation (WPF) or Windows Form Apps,
  sleeping thread for 250 miliSecond (1/4 of a second)
  will be more friendly to the CPU. Nontheless checking 4 times for a connected device in each second is more than enough,
  and will not result in late response from the app if a device gets connected.
Any thoughts?

Submitted By: DeepUnknown from Xda-Developers.com
Checking for command output length rather than comparing it to an empty string after calling Trim().
It's more accurate to check for length of a string when we are expecting an empty string after calling Trim().
Submitted By: Omar Bizreh [DeepUnknown from Xda-Developers.com]
Update Adb & Fastboot to work with Android 4.2.2
Merge pull request #3 from OmarBizreh/master

Prevent exausting CPU in "WaitForDevice" method. Update adb and fastboot binaries for 4.2.2