Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

ERROR: Failed to confirm end of file transfer sequence! on Galaxy S III when flashing CF-Root v6.3 #43

Closed
roblem opened this Issue · 20 comments

18 participants

Rob Hicks Benjamin Dobell Christoph Giesel tarsea Daniele Scasciafratte Bráulio Bhavamitra alfs Ales Guzik Chris Nolan David Stark Diego Viola Hans-Christoph Steiner Brian Eft vintermann Carlos C Soto myHelloWorld Emanuele Olivetti James Miller
Rob Hicks

Been trying to root my Galaxy S III via Heimdall and CF-Root and following the OP here (http://forum.xda-developers.com/showthread.php?t=1695238) tried to execute the linux command on my mac (OSX 10.7.4). I should note that using the heimdall frontend leads to the same outcome.

Here is what happened:

Pinnacle:CF-Root-SGS3-v6.3 $ sudo heimdall flash --recovery recovery.img --cache cache.img
Heimdall v1.3.2, 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...
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

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

Uploading RECOVERY
100%
RECOVERY upload successful
Uploading CACHE
100%
ERROR: Failed to confirm end of file transfer sequence!
CACHE upload failed!

Ending session...

Then I get a softbrick. To fix that, I have to run
Pinnacle:CF-Root-SGS3-v6.3 $ sudo heimdall flash --recovery recovery.img

and the phone reboots normally except with no root and no clockwork mod recovery.

Rob Hicks

Sorry: here is the verbose output

Pinnacle:CF-Root-SGS3-v6.3 $ sudo heimdall flash --recovery recovery.img --cache cache.img --verbose
Password:
Heimdall v1.3.2, 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: "SAMSUNG"
Product: "Gadget Serial"

        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 021B

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: 83
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: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

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

Uploading RECOVERY
0%File Part #0... Response: 0 0 0 0 0 0 0 0

1%
File Part #1... Response: 0 0 0 0 1 0 0 0

3%
File Part #2... Response: 0 0 0 0 2 0 0 0

5%
File Part #3... Response: 0 0 0 0 3 0 0 0

7%
File Part #4... Response: 0 0 0 0 4 0 0 0

8%
File Part #5... Response: 0 0 0 0 5 0 0 0

10%
File Part #6... Response: 0 0 0 0 6 0 0 0

12%
File Part #7... Response: 0 0 0 0 7 0 0 0

14%
File Part #8... Response: 0 0 0 0 8 0 0 0

16%
File Part #9... Response: 0 0 0 0 9 0 0 0

17%
File Part #10... Response: 0 0 0 0 A 0 0 0

19%
File Part #11... Response: 0 0 0 0 B 0 0 0

21%
File Part #12... Response: 0 0 0 0 C 0 0 0

23%
File Part #13... Response: 0 0 0 0 D 0 0 0

25%
File Part #14... Response: 0 0 0 0 E 0 0 0

26%
File Part #15... Response: 0 0 0 0 F 0 0 0

28%
File Part #16... Response: 0 0 0 0 10 0 0 0

30%
File Part #17... Response: 0 0 0 0 11 0 0 0

32%
File Part #18... Response: 0 0 0 0 12 0 0 0

34%
File Part #19... Response: 0 0 0 0 13 0 0 0

35%
File Part #20... Response: 0 0 0 0 14 0 0 0

37%
File Part #21... Response: 0 0 0 0 15 0 0 0

39%
File Part #22... Response: 0 0 0 0 16 0 0 0

41%
File Part #23... Response: 0 0 0 0 17 0 0 0

43%
File Part #24... Response: 0 0 0 0 18 0 0 0

44%
File Part #25... Response: 0 0 0 0 19 0 0 0

46%
File Part #26... Response: 0 0 0 0 1A 0 0 0

48%
File Part #27... Response: 0 0 0 0 1B 0 0 0

50%
File Part #28... Response: 0 0 0 0 1C 0 0 0

52%
File Part #29... Response: 0 0 0 0 1D 0 0 0

53%
File Part #30... Response: 0 0 0 0 1E 0 0 0

55%
File Part #31... Response: 0 0 0 0 1F 0 0 0

57%
File Part #32... Response: 0 0 0 0 20 0 0 0

59%
File Part #33... Response: 0 0 0 0 21 0 0 0

61%
File Part #34... Response: 0 0 0 0 22 0 0 0

62%
File Part #35... Response: 0 0 0 0 23 0 0 0

64%
File Part #36... Response: 0 0 0 0 24 0 0 0

66%
File Part #37... Response: 0 0 0 0 25 0 0 0

68%
File Part #38... Response: 0 0 0 0 26 0 0 0

70%
File Part #39... Response: 0 0 0 0 27 0 0 0

71%
File Part #40... Response: 0 0 0 0 28 0 0 0

73%
File Part #41... Response: 0 0 0 0 29 0 0 0

75%
File Part #42... Response: 0 0 0 0 2A 0 0 0

77%
File Part #43... Response: 0 0 0 0 2B 0 0 0

79%
File Part #44... Response: 0 0 0 0 2C 0 0 0

80%
File Part #45... Response: 0 0 0 0 2D 0 0 0

82%
File Part #46... Response: 0 0 0 0 2E 0 0 0

84%
File Part #47... Response: 0 0 0 0 2F 0 0 0

86%
File Part #48... Response: 0 0 0 0 30 0 0 0

88%
File Part #49... Response: 0 0 0 0 31 0 0 0

89%
File Part #50... Response: 0 0 0 0 32 0 0 0

91%
File Part #51... Response: 0 0 0 0 33 0 0 0

93%
File Part #52... Response: 0 0 0 0 34 0 0 0

95%
File Part #53... Response: 0 0 0 0 35 0 0 0

97%
File Part #54... Response: 0 0 0 0 36 0 0 0

98%
File Part #55... Response: 0 0 0 0 37 0 0 0

100%
RECOVERY upload successful
Uploading CACHE
0%File Part #0... Response: 0 0 0 0 0 0 0 0
File Part #1... Response: 0 0 0 0 1 0 0 0

1%
File Part #2... Response: 0 0 0 0 2 0 0 0
File Part #3... Response: 0 0 0 0 3 0 0 0

2%
File Part #4... Response: 0 0 0 0 4 0 0 0

3%
File Part #5... Response: 0 0 0 0 5 0 0 0
File Part #6... Response: 0 0 0 0 6 0 0 0

4%
File Part #7... Response: 0 0 0 0 7 0 0 0

5%
File Part #8... Response: 0 0 0 0 8 0 0 0
File Part #9... Response: 0 0 0 0 9 0 0 0

6%
File Part #10... Response: 0 0 0 0 A 0 0 0

7%
File Part #11... Response: 0 0 0 0 B 0 0 0
File Part #12... Response: 0 0 0 0 C 0 0 0

8%
File Part #13... Response: 0 0 0 0 D 0 0 0

9%
File Part #14... Response: 0 0 0 0 E 0 0 0
File Part #15... Response: 0 0 0 0 F 0 0 0

10%
File Part #16... Response: 0 0 0 0 10 0 0 0

11%
File Part #17... Response: 0 0 0 0 11 0 0 0
File Part #18... Response: 0 0 0 0 12 0 0 0

12%
File Part #19... Response: 0 0 0 0 13 0 0 0

13%
File Part #20... Response: 0 0 0 0 14 0 0 0
File Part #21... Response: 0 0 0 0 15 0 0 0

14%
File Part #22... Response: 0 0 0 0 16 0 0 0

15%
File Part #23... Response: 0 0 0 0 17 0 0 0
File Part #24... Response: 0 0 0 0 18 0 0 0

16%
File Part #25... Response: 0 0 0 0 19 0 0 0

17%
File Part #26... Response: 0 0 0 0 1A 0 0 0
File Part #27... Response: 0 0 0 0 1B 0 0 0

18%
File Part #28... Response: 0 0 0 0 1C 0 0 0

19%
File Part #29... Response: 0 0 0 0 1D 0 0 0
File Part #30... Response: 0 0 0 0 1E 0 0 0

20%
File Part #31... Response: 0 0 0 0 1F 0 0 0

21%
File Part #32... Response: 0 0 0 0 20 0 0 0
File Part #33... Response: 0 0 0 0 21 0 0 0

22%
File Part #34... Response: 0 0 0 0 22 0 0 0

23%
File Part #35... Response: 0 0 0 0 23 0 0 0
File Part #36... Response: 0 0 0 0 24 0 0 0

24%
File Part #37... Response: 0 0 0 0 25 0 0 0

25%
File Part #38... Response: 0 0 0 0 26 0 0 0
File Part #39... Response: 0 0 0 0 27 0 0 0

26%
File Part #40... Response: 0 0 0 0 28 0 0 0

27%
File Part #41... Response: 0 0 0 0 29 0 0 0
File Part #42... Response: 0 0 0 0 2A 0 0 0

28%
File Part #43... Response: 0 0 0 0 2B 0 0 0

29%
File Part #44... Response: 0 0 0 0 2C 0 0 0
File Part #45... Response: 0 0 0 0 2D 0 0 0

30%
File Part #46... Response: 0 0 0 0 2E 0 0 0

31%
File Part #47... Response: 0 0 0 0 2F 0 0 0
File Part #48... Response: 0 0 0 0 30 0 0 0

32%
File Part #49... Response: 0 0 0 0 31 0 0 0

33%
File Part #50... Response: 0 0 0 0 32 0 0 0
File Part #51... Response: 0 0 0 0 33 0 0 0

34%
File Part #52... Response: 0 0 0 0 34 0 0 0

35%
File Part #53... Response: 0 0 0 0 35 0 0 0
File Part #54... Response: 0 0 0 0 36 0 0 0

36%
File Part #55... Response: 0 0 0 0 37 0 0 0

37%
File Part #56... Response: 0 0 0 0 38 0 0 0
File Part #57... Response: 0 0 0 0 39 0 0 0

38%
File Part #58... Response: 0 0 0 0 3A 0 0 0

39%
File Part #59... Response: 0 0 0 0 3B 0 0 0
File Part #60... Response: 0 0 0 0 3C 0 0 0

40%
File Part #61... Response: 0 0 0 0 3D 0 0 0

41%
File Part #62... Response: 0 0 0 0 3E 0 0 0
File Part #63... Response: 0 0 0 0 3F 0 0 0

42%
File Part #64... Response: 0 0 0 0 40 0 0 0

43%
File Part #65... Response: 0 0 0 0 41 0 0 0
File Part #66... Response: 0 0 0 0 42 0 0 0

44%
File Part #67... Response: 0 0 0 0 43 0 0 0

45%
File Part #68... Response: 0 0 0 0 44 0 0 0
File Part #69... Response: 0 0 0 0 45 0 0 0

46%
File Part #70... Response: 0 0 0 0 46 0 0 0

47%
File Part #71... Response: 0 0 0 0 47 0 0 0
File Part #72... Response: 0 0 0 0 48 0 0 0

48%
File Part #73... Response: 0 0 0 0 49 0 0 0
File Part #74... Response: 0 0 0 0 4A 0 0 0

49%
File Part #75... Response: 0 0 0 0 4B 0 0 0

50%
File Part #76... Response: 0 0 0 0 4C 0 0 0
File Part #77... Response: 0 0 0 0 4D 0 0 0

51%
File Part #78... Response: 0 0 0 0 4E 0 0 0

52%
File Part #79... Response: 0 0 0 0 4F 0 0 0
File Part #80... Response: 0 0 0 0 50 0 0 0

53%
File Part #81... Response: 0 0 0 0 51 0 0 0

54%
File Part #82... Response: 0 0 0 0 52 0 0 0
File Part #83... Response: 0 0 0 0 53 0 0 0

55%
File Part #84... Response: 0 0 0 0 54 0 0 0

56%
File Part #85... Response: 0 0 0 0 55 0 0 0
File Part #86... Response: 0 0 0 0 56 0 0 0

57%
File Part #87... Response: 0 0 0 0 57 0 0 0

58%
File Part #88... Response: 0 0 0 0 58 0 0 0
File Part #89... Response: 0 0 0 0 59 0 0 0

59%
File Part #90... Response: 0 0 0 0 5A 0 0 0

60%
File Part #91... Response: 0 0 0 0 5B 0 0 0
File Part #92... Response: 0 0 0 0 5C 0 0 0

61%
File Part #93... Response: 0 0 0 0 5D 0 0 0

62%
File Part #94... Response: 0 0 0 0 5E 0 0 0
File Part #95... Response: 0 0 0 0 5F 0 0 0

63%
File Part #96... Response: 0 0 0 0 60 0 0 0

64%
File Part #97... Response: 0 0 0 0 61 0 0 0
File Part #98... Response: 0 0 0 0 62 0 0 0

65%
File Part #99... Response: 0 0 0 0 63 0 0 0

66%
File Part #100... Response: 0 0 0 0 64 0 0 0
File Part #101... Response: 0 0 0 0 65 0 0 0

67%
File Part #102... Response: 0 0 0 0 66 0 0 0

68%
File Part #103... Response: 0 0 0 0 67 0 0 0
File Part #104... Response: 0 0 0 0 68 0 0 0

69%
File Part #105... Response: 0 0 0 0 69 0 0 0

70%
File Part #106... Response: 0 0 0 0 6A 0 0 0
File Part #107... Response: 0 0 0 0 6B 0 0 0

71%
File Part #108... Response: 0 0 0 0 6C 0 0 0

72%
File Part #109... Response: 0 0 0 0 6D 0 0 0
File Part #110... Response: 0 0 0 0 6E 0 0 0

73%
File Part #111... Response: 0 0 0 0 6F 0 0 0

74%
File Part #112... Response: 0 0 0 0 70 0 0 0
File Part #113... Response: 0 0 0 0 71 0 0 0

75%
File Part #114... Response: 0 0 0 0 72 0 0 0

76%
File Part #115... Response: 0 0 0 0 73 0 0 0
File Part #116... Response: 0 0 0 0 74 0 0 0

77%
File Part #117... Response: 0 0 0 0 75 0 0 0

78%
File Part #118... Response: 0 0 0 0 76 0 0 0
File Part #119... Response: 0 0 0 0 77 0 0 0

79%
File Part #120... Response: 0 0 0 0 78 0 0 0

80%
File Part #121... Response: 0 0 0 0 79 0 0 0
File Part #122... Response: 0 0 0 0 7A 0 0 0

81%
File Part #123... Response: 0 0 0 0 7B 0 0 0

82%
File Part #124... Response: 0 0 0 0 7C 0 0 0
File Part #125... Response: 0 0 0 0 7D 0 0 0

83%
File Part #126... Response: 0 0 0 0 7E 0 0 0

84%
File Part #127... Response: 0 0 0 0 7F 0 0 0
File Part #128... Response: 0 0 0 0 80 0 0 0

85%
File Part #129... Response: 0 0 0 0 81 0 0 0

86%
File Part #130... Response: 0 0 0 0 82 0 0 0
File Part #131... Response: 0 0 0 0 83 0 0 0

87%
File Part #132... Response: 0 0 0 0 84 0 0 0

88%
File Part #133... Response: 0 0 0 0 85 0 0 0
File Part #134... Response: 0 0 0 0 86 0 0 0

89%
File Part #135... Response: 0 0 0 0 87 0 0 0

90%
File Part #136... Response: 0 0 0 0 88 0 0 0
File Part #137... Response: 0 0 0 0 89 0 0 0

91%
File Part #138... Response: 0 0 0 0 8A 0 0 0

92%
File Part #139... Response: 0 0 0 0 8B 0 0 0
File Part #140... Response: 0 0 0 0 8C 0 0 0

93%
File Part #141... Response: 0 0 0 0 8D 0 0 0

94%
File Part #142... Response: 0 0 0 0 8E 0 0 0
File Part #143... Response: 0 0 0 0 8F 0 0 0

95%
File Part #144... Response: 0 0 0 0 90 0 0 0

96%
File Part #145... Response: 0 0 0 0 91 0 0 0
File Part #146... Response: 0 0 0 0 92 0 0 0

97%
File Part #147... Response: 0 0 0 0 93 0 0 0
File Part #148... Response: 0 0 0 0 94 0 0 0

98%
File Part #149... Response: 0 0 0 0 95 0 0 0

99%
File Part #150... Response: 0 0 0 0 96 0 0 0
File Part #151... Response: 0 0 0 0 97 0 0 0

100%

ERROR: Failed to confirm end of file transfer sequence!
CACHE upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!

Benjamin Dobell
Christoph Giesel

I got the same error. Heimdall 1.3.1 works. ;)

tarsea

Hello,
I get the same issue on Ubuntu 12.04 with Heimdall v1.3.2.

Daniele Scasciafratte

same problem on debian sid 64bit

Bráulio Bhavamitra

same here, any fix/workaround for this?

alfs

I got the same problem. I'm on Ubuntu 12.04 (64 bit). I first used 1.3.2 from https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.2_i386.deb which flashed recovery fine, but failed on cache flash.

I downgraded to 1.3.1 from https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_amd64.deb and it worked.

Two factors are involved, i386 vs amd64 and version 1.3.1 and 1.3.2.

Ales Guzik

Same problem here, ArchLinux x86_64

Chris Nolan

Same problem here on OSX 10.6.8 with 1.3.2, but works fine with 1.3.1.

David Stark

I just compiled up 1.3.2 on centos6.3 (64) and had the same issue, I'm not familiar with github, how can I download the 1.3.1 source o_O ?

Diego Viola

@starkd if you cloned the repo you can just git checkout v1.3.1

Benjamin Dobell

Please try the Heimdall 1.4 release candidate to ensure this is fixed. If not, you can let me know if the problem still persists by re-opening the issue.

Hans-Christoph Steiner

I'm seeing this same issue when running heimdall to flash recovery for a Samsung Galaxy S III Sprint (SPH-L710). On Linux Mint Maya 64-bit (Ubuntu/precise/amd64) I installed heimdall from the official Debian/sid/amd64 packages v1.4~rc1+dfsg-1. This heimdall install worked perfectly flashing recovery to my Galaxy Note 2 N7100.

$ heimdall flash --recovery recovery-clockwork-6.0.2.3-d2spr.img --no-reboot
Heimdall v1.4 RC1

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...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.

Initialising protocol...
Protocol initialisation successful.

Beginning session...
Session begun.

In certain situations this device may take up to 2 minutes to respond.
Please be patient!

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

Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!

Ending session...
Releasing device interface...
Re-attaching kernel driver...
Hans-Christoph Steiner

I just tried with master from git and it succeeded, nice work! so it should still be closed :)

Brian Eft

I'm having the same problem on Arch Linux x86_64. I'm following the instructions here for my Galaxy S III Verizon. I tried 1.4 RC1 linked on the above Cyanogenmod page, 1.4 RC2 from the heimdall AUR package, and the latest build from git (858a347), with the same results each time.

$ ./heimdall flash -ABOOT aboot.mbn --verbose
Heimdall v1.4 RC1

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: "MSM8960"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         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
Protocol initialisation successful.

Beginning session...
Session begun with device of type: 30.

In certain situations this device may take up to 2 minutes to respond.
Please be patient!

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

Uploading BOOT
0%File Part #0... Response: 0  0  0  0  0  0  0  0 

86%
File Part #1... Response: 0  0  0  0  1  0  0  0 

100%
ERROR: Failed to unpack received packet.

ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!

Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
vintermann

I'm still getting this at the end of transfering my modem file (mdm.bin). I'm using Ubuntu 12.04 x86, with the precompiled binaries for that system. The target is a GT-P7320, otherwise known as Galaxy Tab 8.9 LTE (the version sold in Europe and Hong Kong).

Carlos C Soto

Same here using debian
Linux localhost 3.10-1-amd64 #1 SMP Debian 3.10.3-1 (2013-07-27) x86_64 GNU/Linux
libusb-1.0-0:amd64 2:1.0.16-1

Heimdall v1.4 RC1

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: "SAMSUNG"
Product: "SAMSUNG USB DRIVER"
Serial No: " "

        length: 18
  device class: 2
           S/N: 3
       VID:PID: 04E8:685D
     bcdDevice: 80B1

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

interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
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: 02
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.ERROR: libusb error -1418746216 whilst receiving packet.

Protocol is not initialised.

Initialising protocol...
Protocol initialisation successful.

Beginning session...
Session begun with device of type: 180.

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

Uploading RECOVERY
0%File Part #0... Response: 0 0 0 0 0 0 0 0

2%
File Part #1... Response: 0 0 0 0 1 0 0 0

5%
File Part #2... Response: 0 0 0 0 2 0 0 0

7%
File Part #3... Response: 0 0 0 0 3 0 0 0

10%
File Part #4... Response: 0 0 0 0 4 0 0 0

13%
File Part #5... Response: 0 0 0 0 5 0 0 0

15%
File Part #6... Response: 0 0 0 0 6 0 0 0

18%
File Part #7... Response: 0 0 0 0 7 0 0 0

21%
File Part #8... Response: 0 0 0 0 8 0 0 0

23%
File Part #9... Response: 0 0 0 0 9 0 0 0

26%
File Part #10... Response: 0 0 0 0 A 0 0 0

29%
File Part #11... Response: 0 0 0 0 B 0 0 0

31%
File Part #12... Response: 0 0 0 0 C 0 0 0

34%
File Part #13... Response: 0 0 0 0 D 0 0 0

36%
File Part #14... Response: 0 0 0 0 E 0 0 0

39%
File Part #15... Response: 0 0 0 0 F 0 0 0

42%
File Part #16... Response: 0 0 0 0 10 0 0 0

44%
File Part #17... Response: 0 0 0 0 11 0 0 0

47%
File Part #18... Response: 0 0 0 0 12 0 0 0

50%
File Part #19... Response: 0 0 0 0 13 0 0 0

52%
File Part #20... Response: 0 0 0 0 14 0 0 0

55%
File Part #21... Response: 0 0 0 0 15 0 0 0

58%
File Part #22... Response: 0 0 0 0 16 0 0 0

60%
File Part #23... Response: 0 0 0 0 17 0 0 0

63%
File Part #24... Response: 0 0 0 0 18 0 0 0

66%
File Part #25... Response: 0 0 0 0 19 0 0 0

68%
File Part #26... Response: 0 0 0 0 1A 0 0 0

71%
File Part #27... Response: 0 0 0 0 1B 0 0 0

73%
File Part #28... Response: 0 0 0 0 1C 0 0 0

76%
File Part #29... Response: 0 0 0 0 1D 0 0 0

79%
File Part #30... Response: 0 0 0 0 1E 0 0 0

81%
File Part #31... Response: 0 0 0 0 1F 0 0 0

84%
File Part #32... Response: 0 0 0 0 20 0 0 0

87%
File Part #33... Response: 0 0 0 0 21 0 0 0

89%
File Part #34... Response: 0 0 0 0 22 0 0 0

92%
File Part #35... Response: 0 0 0 0 23 0 0 0

95%
File Part #36... Response: 0 0 0 0 24 0 0 0

97%
File Part #37... Response: 0 0 0 0 25 0 0 0

100%
ERROR: Failed to unpack received packet.
ERROR: Failed to unpack received packet.

ERROR: Failed to confirm end of file transfer sequence!
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!

ERROR: (null) upload failed!

Ending session...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error -1418746216 whilst receiving packet. Retrying...
Retrying...
ERROR: libusb error -7 whilst receiving packet.ERROR: libusb error -1418746216 whilst receiving packet. Retrying...
Retrying...

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

myHelloWorld

Mac 10.7.4, fails at sboot.bin while recovery, hidden, cache, boot and modem are fine.

michaels-MacBook-Pro:CHN-N7100ZCDMG1-20130808095446 michaelz$ ~/programs/heimdall_v1.4rc1_mac/heimdall flash --BOOTLOADER sboot.bin --verbose
Heimdall v1.4 RC1

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: "SAMSUNG"
Product: "Gadget Serial"

        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 021B

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: 83
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: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...

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

Initialising protocol...
Protocol initialisation successful.

Beginning session...
Session begun with device of type: 0.

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

Uploading BOOTLOADER
0%File Part #0... Response: 0 0 0 0 0 0 0 0

14%
File Part #1... Response: 0 0 0 0 1 0 0 0

29%
File Part #2... Response: 0 0 0 0 2 0 0 0

44%
File Part #3... Response: 0 0 0 0 3 0 0 0

59%
File Part #4... Response: 0 0 0 0 4 0 0 0

73%
File Part #5... Response: 0 0 0 0 5 0 0 0

88%
File Part #6... Response: 0 0 0 0 6 0 0 0

100%
ERROR: Failed to unpack received packet.

ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!

Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...

Emanuele Olivetti

I'm experiencing a similar issue with a Samsung S2 i9100P on Ubuntu 12.04. I've tried several different versions of heimdall (v1.3.0, v1.3.1, v1.3.2, v1.4.0 and latest git as of today), both on i386 and on amd64. Uploading a kernel hangs at 100%, as shown in the example log below. Note: the mobile phone is in a sort of soft-brick state, which could be part of the problem...

$> heimdall flash --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: "SAMSUNG"
           Product: "Gadget Serial"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 021B
   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: 83
           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: 02
           max packet size: 0200
          polling interval: 00
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 KERNEL
0%
12%

25%

37%

50%

62%

75%

87%

100%
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.

ERROR: Failed to confirm end of file transfer sequence!
ERROR: KERNEL upload failed!

Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...

$> 
James Miller

Same issue with an S3 SGH-i747 (ATT) downgrading to an older modem firmware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.