Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Galaxy S Plus GT-i9001 not working with heimdal version v1.4 RC2 #107
Comments
|
Have you installed the udev rules and rebooted (or restarted the udev subsytem)? Also, please try the WIP/1.4RC3 branch. |
hschraep
commented
Mar 19, 2013
|
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 |
hschraep
commented
Mar 19, 2013
|
OK, i have restart udev now i get this message: $ heimdall print-pit --verbose Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is If you appreciate this software and you would like to support future Initialising connection... iMan:iProd:iSer: 1:2:0 interface[0].altsetting[0]: num endpoints = 1 interface[1].altsetting[0]: num endpoints = 2 Checking if protocol is initialised... Initialising protocol... Releasing device interface... |
|
Okay, yeah please try the wip/1.4RC3 branch, I believe this is fixed. |
hschraep
commented
Mar 19, 2013
|
Will try out this version but get this error during compiling: Heimdall-wip-1.4RC3/heimdall$ sudo make $ sudo aptitude versions libusb-1.0-0-dev Any idea what is missing or is wrong? |
|
Heimdall now uses libusbx instead of libusb-1.0. You'll need to install the former. |
hschraep
commented
Mar 19, 2013
|
What did you mean with former? Within the download from branch WIP/1.4RC3 is only a Win32 lib from libusbx. |
|
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. |
Benjamin-Dobell
closed this
Jun 11, 2013
jensMF
commented
Jun 20, 2013
|
I cloned the repository a few minutes ago, and I get the very same error. I could use some help. Thanks in advance. |
|
@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? |
Benjamin-Dobell
reopened this
Jun 20, 2013
jensMF
commented
Jun 20, 2013
|
sorry, that one hschraep mentioned. but the problem is not with heimdall. the problem is, that libusbx is missing. |
Benjamin-Dobell
closed this
Jun 20, 2013
m3phisto
commented
Jul 18, 2013
|
@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 --verboseHeimdall v1.4.0 Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna This software is provided free of charge. Copying and redistribution is If you appreciate this software and you would like to support future Initialising connection... iMan:iProd:iSer: 1:2:0 interface[0].altsetting[0]: num endpoints = 1 interface[1].altsetting[0]: num endpoints = 2 Initialising protocol... Releasing device interface... If you need more details, please ask. |
meistermagus
commented
Aug 10, 2013
|
Same here.... I followed the install intructions for Cyanogen here: 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. |
jloehel
commented
Sep 11, 2013
|
Same Error here. Ubuntu 13.04 Btw.: The libusbx-Package from above is not properly packed and it make no difference, if it installed or not. Samsung: GT-I9001 Error: Sometimes I get these Error-Messages: |
AntonGut
commented
Oct 3, 2013
|
Issue is not solved with v1.4.0. See |
jloehel
commented
Oct 3, 2013
|
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
commented
Nov 30, 2013
|
Having a Galaxy W I8150 here. Getting the same error messages as above: Initialising protocol... 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
commented
Jan 26, 2014
|
Same issue here on GT-I9000 on Unbuntu 13.10 under VMware. |
uferta
commented
Feb 12, 2014
|
Having same problem with gt-i5500, rooted, stock rom. Claiming interface... Initialising protocol... 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 |
hschraep commentedMar 19, 2013
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...
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