Revert of Fix an errant pylint change.

Revert of Fix an errant pylint change. (https://codereview.chromium.org/143623007/)

Reason for revert:
crbug.com/342539 is likely happening because of the patch that this patch depends on. I need to ensure that logcats work on the bots before relanding (and that the corresponding steps fail if they don't.)

Original issue's description:
> I broke something by removing an apparently unused import that actually was used elsewhere. I addressed the issue by having the client code just call android_commands.GetAttachedDevices explicitly.
> 
> BUG=168518
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=250206

TBR=craigdh@chromium.org,frankf@chromium.org,cjhopman@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=168518
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=250264

[jbudorick, 2014-02-11 01:09:46]

Created Revert of Fix an errant pylint change.

[commit-bot: I haz the power, 2014-02-11 01:12:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-02-11 01:12:41]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a lowly provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[craigdh, 2014-02-11 01:13:33]

lgtm.

[jbudorick, 2014-02-11 01:13:49]

The CQ bit was checked by jbudorick@chromium.org

[commit-bot: I haz the power, 2014-02-11 01:16:24]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jbudorick@chromium.org/159453002/1

[commit-bot: I haz the power, 2014-02-11 01:20:35]

Change committed as 250264