Project

General

Profile

Actions

Issue #1856

closed

Heimdall does not proceed to flashing recovery mode

Added by Jan Prunk about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
12/28/2017
Due date:
% Done:

0%

Estimated time:
Resolution:
Device:
Galaxy S 3 (I9300)
Grant:
Type of work:

Description

Hello,

I have noticed that heimdall will not proceed to flashing i9300 into 6.0 0003 recovery mode, when using "wrong"/incompatible USB cable. Maybe this should somehow be mentioned on the wiki (if someone else gets stuck on the same error)?

Here was my heimdall output when using the "wrong" USB cable...

  1. dmesg
    [ 113.008107] usb 4-2: new full-speed USB device number 4 using uhci_hcd
    [ 113.136124] usb 4-2: device descriptor read/64, error -71
    [ 113.372116] usb 4-2: device descriptor read/64, error -71
    [ 113.600120] usb 4-2: new full-speed USB device number 5 using uhci_hcd
    [ 113.728124] usb 4-2: device descriptor read/64, error -71
    [ 113.964124] usb 4-2: device descriptor read/64, error -71
    [ 114.192129] usb 4-2: new full-speed USB device number 6 using uhci_hcd
    [ 114.608126] usb 4-2: device not accepting address 6, error -71
    [ 114.728135] usb 4-2: new full-speed USB device number 7 using uhci_hcd
  1. heimdall flash --BOOT /path/to/0003/recovery-i9300.img --RECOVERY /path/to/0003/recovery-i9300.img
    Heimdall v1.4.1

Copyright (c) 2010-2014 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.
---
At this point I have manually compiled heimdall ver. 1.4.0 and heimdall ver. 1.4.2, which did not help and gave me the same error.

When I have repled the USB cable the heimdall got to work properly.
---
  1. dmesg
    [ 441.080126] usb 8-2: new high-speed USB device number 5 using ehci-pci
    [ 441.230490] usb 8-2: New USB device found, idVendor=04e8, idProduct=685d
    [ 441.230496] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 441.230500] usb 8-2: Product: Gadget Serial
    [ 441.230503] usb 8-2: Manufacturer: SAMSUNG
    [ 441.295962] usbcore: registered new interface driver cdc_acm
    [ 441.295964] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

Heimdall v1.4.1

Copyright (c) 2010-2014 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...
Claiming interface...
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 BOOT
100%
BOOT upload successful

Uploading RECOVERY
100%
RECOVERY upload successful

Ending session...
Rebooting device...
Releasing device interface...
---

Regards,
yang

Actions #1

Updated by Fil Bergamo about 6 years ago

  • Status changed from New to Feedback

Hello.

From what you say, this issue seems to lay in the USB cable and/or in heimdall.
Nothing seems to be related to Replicant at all.
If no further information is brought up involving Replicant, I'd close this issue as non-replicant-related in a few days.

Actions #2

Updated by Fil Bergamo about 6 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF