Galaxy S Plus GT-i9001 not working with heimdal version v1.4 RC2 #107

Closed
hschraep opened this Issue Mar 19, 2013 · 19 comments

10 participants

@hschraep

Hello,
i have installed heimdal version 1.4 RC2 bit it will not work with the galaxy S plus.
$ heimdall version
v1.4 RC2

$ heimdall print-pit --verbose
Heimdall v1.4 RC2

Copyright (c) 2010-2012, 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...

        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:6601
     bcdDevice: 0100

iMan:iProd:iSer: 1:2:0
nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
ERROR: Setting up interface failed!
Releasing device interface...

Here the dmesg message after the phone goes in the downloading mode:

[ 1674.167889] usb 1-1.4: USB disconnect, device number 3
[ 1681.387584] usb 1-1.4: new high-speed USB device number 4 using ehci_hcd
[ 1681.483433] usb 1-1.4: unable to get BOS descriptor
[ 1681.490479] cdc_acm 1-1.4:2.0: This device cannot do calls on its own. It is not a modem.
[ 1681.490535] cdc_acm 1-1.4:2.0: ttyACM0: USB ACM device

@Benjamin-Dobell

Have you installed the udev rules and rebooted (or restarted the udev subsytem)?

Also, please try the WIP/1.4RC3 branch.

@hschraep

What i have to do with the udev? I have not create a udev rule for the device. Have i to do this? Have nothing found
within the readme.

@hschraep

OK, i have restart udev now i get this message:

$ heimdall print-pit --verbose
Heimdall v1.4 RC2

Copyright (c) 2010-2012, 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...
Manufacturer: "Sasmsung"
Product: "MSM7x30"

        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:6601
     bcdDevice: 0100

iMan:iProd:iSer: 1:2:0
nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Checking if protocol is initialised...
ERROR: libusb error -7 whilst receiving packet.
Protocol is not initialised.

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response.
ERROR: Protocol initialisation failed!

Releasing device interface...
Re-attaching kernel driver...

@Benjamin-Dobell

Okay, yeah please try the wip/1.4RC3 branch, I believe this is fixed.

@hschraep

Will try out this version but get this error during compiling:

Heimdall-wip-1.4RC3/heimdall$ sudo make
make all-am
make[1]: Betrete Verzeichnis '/usr/local/src/Heimdall-wip-1.4RC3/heimdall'
depbase=echo source/Arguments.o | sed 's|[^/]*$|.deps/&|;s|\.o$||';\
g++ -DHAVE_CONFIG_H -I. -I/usr/include/libusb-1.0 -std=c++0x -I../libpit/Source -g -O2 -MT source/Arguments.o -MD -MP -MF $depbase.Tpo -c -o source/Arguments.o source/Arguments.cpp &&\
mv -f $depbase.Tpo $depbase.Po
depbase=echo source/BridgeManager.o | sed 's|[^/]*$|.deps/&|;s|\.o$||';\
g++ -DHAVE_CONFIG_H -I. -I/usr/include/libusb-1.0 -std=c++0x -I../libpit/Source -g -O2 -MT source/BridgeManager.o -MD -MP -MF $depbase.Tpo -c -o source/BridgeManager.o source/BridgeManager.cpp &&\
mv -f $depbase.Tpo $depbase.Po
source/BridgeManager.cpp: In Elementfunktion »bool Heimdall::BridgeManager::DetectDevice()«:
source/BridgeManager.cpp:504:36: Fehler: »LIBUSB_LOG_LEVEL_NONE« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:508:36: Fehler: »LIBUSB_LOG_LEVEL_ERROR« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:512:36: Fehler: »LIBUSB_LOG_LEVEL_WARNING« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:516:36: Fehler: »LIBUSB_LOG_LEVEL_INFO« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:520:36: Fehler: »LIBUSB_LOG_LEVEL_DEBUG« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp: In Elementfunktion »int Heimdall::BridgeManager::Initialise(bool)«:
source/BridgeManager.cpp:569:36: Fehler: »LIBUSB_LOG_LEVEL_NONE« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:573:36: Fehler: »LIBUSB_LOG_LEVEL_ERROR« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:577:36: Fehler: »LIBUSB_LOG_LEVEL_WARNING« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:581:36: Fehler: »LIBUSB_LOG_LEVEL_INFO« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:585:36: Fehler: »LIBUSB_LOG_LEVEL_DEBUG« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp: In Elementfunktion »void Heimdall::BridgeManager::SetUsbLogLevel(Heimdall::BridgeManager::UsbLogLevel)«:
source/BridgeManager.cpp:1369:37: Fehler: »LIBUSB_LOG_LEVEL_NONE« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:1373:37: Fehler: »LIBUSB_LOG_LEVEL_ERROR« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:1377:37: Fehler: »LIBUSB_LOG_LEVEL_WARNING« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:1381:37: Fehler: »LIBUSB_LOG_LEVEL_INFO« wurde in diesem Gültigkeitsbereich nicht definiert
source/BridgeManager.cpp:1385:37: Fehler: »LIBUSB_LOG_LEVEL_DEBUG« wurde in diesem Gültigkeitsbereich nicht definiert
make[1]: *** [source/BridgeManager.o] Fehler 1
make[1]: Verlasse Verzeichnis '/usr/local/src/Heimdall-wip-1.4RC3/heimdall'
make: *** [all] Fehler 2

$ sudo aptitude versions libusb-1.0-0-dev
Paket libusb-1.0-0-dev:

i 2:1.0.9~rc3-2ubuntu1 precise 500

Any idea what is missing or is wrong?

@Benjamin-Dobell

Heimdall now uses libusbx instead of libusb-1.0. You'll need to install the former.

@hschraep

What did you mean with former? Within the download from branch WIP/1.4RC3 is only a Win32 lib from libusbx.

@Benjamin-Dobell

I believe this is fixed the 1.4.0 release (https://github.com/Benjamin-Dobell/Heimdall/tree/v1.4.0).

If not, please reopen the issue.

@jensMF

I cloned the repository a few minutes ago, and I get the very same error. I could use some help. Thanks in advance.

@Benjamin-Dobell

@jensMF There are a few issues mentioned in here. Could you please be specific; in particular could you please run Heimdall with the --verbose flag and paste the output here?

@jensMF

sorry, that one hschraep mentioned.
All of these an the following:
source/BridgeManager.cpp:504:36: Fehler: »LIBUSB_LOG_LEVEL_NONE« wurde in diesem Gültigkeitsbereich nicht definiert
and it is the same leapylee metiont here in the 4th reply:
#105

but the problem is not with heimdall. the problem is, that libusbx is missing.
I'm on ubuntu 12.04 and there is no libusbx package in the repositories.
So I tried to build it from source but it faild.
Finally I found a working .deb packed here: http://205.196.122.126/4ltzlej8u1kg/lgyguq8b7bdrgok/libusbx-1.0.14_1.0.14-1_amd64.deb and my Problem is solved.

@m3phisto

@Benjamin-Dobell : I fear this bug is still open. I own a GT-i9001 and encountered the exact same behavior with Heimdall 1.4 and libusbx as described above. After a fresh compilation and installation of heimdall plus restarting udev:

heimdall print-pit --verbose

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...
Manufacturer: "Sasmsung"
Product: "MSM7x30"

        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:6601
     bcdDevice: 0100

iMan:iProd:iSer: 1:2:0
nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response.
ERROR: Protocol initialisation failed!

Releasing device interface...


If you need more details, please ask.

@meistermagus

Same here.... I followed the install intructions for Cyanogen here:
http://wiki.cyanogenmod.org/w/Install_CM_for_p5100

and used Heimdall 1.4 under Linux-Mint as well as 1.4rc2 under Windows7 with both the same error:

failed to receive handshake response.

Tried on an Galaxy Tab 2 10.1 (5100)

Any ideas?

Thanks for your time.
m

@jloehel

Same Error here.

Ubuntu 13.04
Kernel: 3.8.0-27-generic
Heimdall: v1.4.0 from Github
libusb:

i A libusb++-0.1-4c2                - userspace C++ USB programming library     
i   libusb++-dev                    - userspace C++ USB programming library deve
i   libusb-0.1-4                    - Userspace USB-Programmierbibliothek       
i A libusb-0.1-4:i386               - Userspace USB-Programmierbibliothek       
i   libusb-1.0-0                    - Userspace USB-Programmierbibliothek       
i A libusb-1.0-0:i386               - Userspace USB-Programmierbibliothek       
i   libusb-1.0-0-dev                - userspace USB programming library developm
i   libusb-dev                      - userspace USB programming library developm
i   libusb-ocaml                    - OCaml bindings to libusb-1.0 (runtime)    
i   libusbmuxd-dev                  - USB multiplexor daemon for iPhone and iPod
i   libusbmuxd2                     - USB multiplexor daemon for iPhone and iPod
i   libusbprog-dev                  - Entwicklungsdateien für Libusbprog        
i   libusbprog0                     - Library for programming the USBprog hardwa
i   libusbtc08-1                    - Hardware interface library for PicoTech US

Btw.: The libusbx-Package from above is not properly packed and it make no difference, if it installed or not.

Samsung: GT-I9001

Error:

heimdall flash --recovery zImage --kernel zImage --verbose
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...

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:xxx
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...
libusbx: error [op_set_interface] setintf failed error -1 errno 71
ERROR: Setting up interface failed!
Releasing device interface..

Sometimes I get these Error-Messages:

heimdall flash --recovery zImage --kernel zImage --verbose
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...
      Manufacturer: "Sasmsung"
           Product: "xxx"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:xxx
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response.
ERROR: Protocol initialisation failed!

Releasing device interface...
@AntonGut

Issue is not solved with v1.4.0. See
#34 (comment)

@jloehel

You can flash your samsung gt-i9001 in the standard recovery mode. (Volumne UP + Power + USB Cable must be plugged in) That's how I finally did it. There is no need for heimdall.

@fertilo

Having a Galaxy W I8150 here. Getting the same error messages as above:

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response. Retrying...
ERROR: Failed to receive handshake response.
ERROR: Protocol initialisation failed!

Using heimdall 1.4.0 on Debian. I'm not sure whether the phone is possibly broken, because ODIN under Windows doesn't work either. Unfortunately, I'm trying to UNroot the device after using Cyanogen on it for more than a year. I feel like I shouldn't send it back with custom software on it.

Any suggestions?

@kriswebdev

Same issue here on GT-I9000 on Unbuntu 13.10 under VMware.
I'm also unable to get the driver working for the Windows version of Heimdall.
EDIT: This seems to be working partially. Answer is I think (source): "protocol initialization can (does?) fail if the device is connected via a USB hub - connect directly to the PC". Note that VMware is acting like a hub I think. You should avoid using Heimdall inside a VM.

@uferta

Having same problem with gt-i5500, rooted, stock rom.

Claiming interface...
Setting up interface...

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response. Retrying...
Retrying...
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response. Retrying...
Retrying...
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response. Retrying...
Retrying...
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response. Retrying...
Retrying...
ERROR: Failed to receive handshake response.ERROR: Failed to receive handshake response.

ERROR: Protocol initialisation failed!

ERROR: Protocol initialisation failed!

Releasing device interface...

I have successfully flashed gt-i9000 couple of months before on same computer with same cable and same software so it shouldn't be libusbx or something. Unfortunately I don't have it anymore to test it again.

debian testing
heimdall 1.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment