Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

I am having some problems with my Samsung Galaxy S2 and I want to start an fschk session on the device.

So, I installed Android SDK with platform-tools. I can access to the device when it's normally rebooted but I couldn't list and connect to the device when it's in recovery mode.

How can I connect via ADB when the device is in recovery mode?

share|improve this question
    
What OS are you running on? It sounds like the recovery is a stock recovery and therefore un-rooted hence lack of access to adb shell from there. –  t0mm13b Sep 26 '12 at 15:03
    
I rooted the device about a year ago by following a how-to and didn't update it since then. It runs Android 2.2.3 GINGERBREAD.XWKG1. –  Tim Sep 26 '12 at 15:13
    
I meant, are you running Windows or Linux? –  t0mm13b Sep 26 '12 at 15:28
    
I'm not certain that this is possible. I seem to remember that when I was rooting my N7 I was unable to adb while in recovery. I believe you have to be either fully booted or with just the bootloader... booted. –  SaintWacko Sep 26 '12 at 16:07
    
As I read, it's possible. I am on Windows and I installed the Google's USB drivers. I am trying to install a custom recovery but my phone is acting quite strange. I think I'll try the same steps on Linux. –  Tim Sep 26 '12 at 16:12
add comment

2 Answers 2

Stock recovery doesn't come with ADB access.

Try a recent version of ClockworkMod recovery for your device (the older versions don't all have ADB support)

You will need to flash the recovery on using fastboot (see @MishaP's answer)

share|improve this answer
add comment

adb is not available in the bootloader, try using fastboot instead

for a quick and dirty rundown of flashing your device with a new image using fastboot:

adb reboot bootloader
use fastboot devices to verify your device is visible, if not, you're probably running windows, and you have to install some funky drivers. if you don't see 'unlocked' at the bottom of the screen, use the command fastboot oem unlock then just:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img

If you feel super confident you could just:
adb reboot bootloader && fastboot oem unlock && fastboot flash boot boot.img && fastboot flash system system.img && fastboot flash userdata userdata.img && fastboot flash recovery recovery.img && fastboot reboot

PS You should only use the flash commands if the referenced files are present, if not you may or may not brick your phone (haven't tried flashing a non-existent file to the device yet)

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.