15

When trying to flash a Galaxy S3 (ATT), I get

ERROR: Failed to detect compatible download-mode device.

below is the log,

$ sudo heimdall flash --RECOVERY recovery.img
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
ERROR: Failed to detect compatible download-mode device.
Evan Carroll
  • 4,257
  • 20
  • 57
  • 94

4 Answers4

16

Start off by making sure that you're plugged into a USB 2.0 port. Then,

put the device in download-mode,

$ sudo adb reboot download

continue flashing with heimdall,

$ sudo heimdall flash --RECOVERY recovery.img

That should work,

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading RECOVERY
100%
RECOVERY upload successful

Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Evan Carroll
  • 4,257
  • 20
  • 57
  • 94
  • 1
    I don't see how the error is related to the answer. Usually when heimdall tells you that there is 'no device in download mode' then it is unable to find a device. This can be caused because the permissions of the device's USB node, which prevent the user running heimdall to access the device node. – Flow Aug 14 '13 at 22:32
  • 1
    Oh I just saw the sudo before the heimdall command. Well this would fix the error of course. Maybe you want to point that little fact out in your answer. – Flow Aug 14 '13 at 22:35
  • Or using heimdall with a device in download mode and restrictive device node permissions could cause this error. Then sudo will "fix" it. – Flow Aug 15 '13 at 07:21
  • This error message, like most error messages, can have more then one cause. – Flow Aug 15 '13 at 07:25
  • 2
    What's wrong with USB 3? I tried everything, then noticed the first sentence! – PhilMacKay Nov 15 '14 at 16:18
  • 5
    adb reboot download gives "error: device not found" for me. – Geremia Apr 03 '15 at 08:33
4

Got the same issue years later, and solved it by.. using another USB cable!

Indeed, some USB cables are only made for energy transfer and do not support data transmission

You may also want to test other USB ports and check if your device is detected with lsusb

roneo.org
  • 141
  • 1
3

One possible explanation is that you have confused recovery mode and download mode which are (I have just discovered) two different things on some phones, mine included. I had the same error and switching to download-mode fixed it.

u38cg
  • 31
  • 2
-1

Install Teamwin recovery put in recovery mode wipe everything fix system partition reboot from recovery into download mode now flash worked for me

ken
  • 1
  • The question was asked in 2013, for this to be a valid answer you're going to have to elaborate. Include bullet point instructions, and screenshots. – Aaron Gillion Feb 24 '16 at 00:37