Menu
I try to access an android device (Samsung Galaxy Y) through usb using adb. When the phone is running as usual, with USB debugging activated, adb works just fine and I see the device with a call to "adb devices". However I need adb access in the recovery mode (I want to execute fsck on /data and thus need to unmount it first). I reboot the phone in recovery mode and run CWM (ClockworkMod ROM Manager) but then the phone does not show up with "adb devices".
I looked this up and it appears that on windows systems the solution is to change the drivers. However I am on Ubuntu 14.04 LTS and I am stuck with my problem. I tried several suggestions of udev rules in /etc/udev/rules.d but none worked for me.
How can I solve this issue ?
585
1) Select your SDK manager from the Start menu > Run as administrator. 2) When the SDK manager launches, navigate and expand the Extras folder > select Google USB Driver> click Install 1 package. 3) After installing the driver, connect your Android smartphone. 4) Hit the Windows logo + R keys.
ADB commands when phone is in recovery mode (e.g. adb devices gives a blank result). However, I can sideload a ROM (clean install) via ADB when the phone is in recovery mode. This is probably the only adb command that works in recovery.
In the past, I've found that running adb kill-server, followed by su -c adb {command} works pretty well in these situations. It's a tiny bit ugly, but some devices refuse to recognize adb unless it's started by root.
Note that you probably can't use sudo adb {command} unless your root user has the android tools on its path.
97
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
