Skip to content
This repository

"Failed to confirm end of file transfer sequence, DATAFS upload failed" when flush samsung galaxy s2 #32

Closed
yupeng820921 opened this Issue · 17 comments

17 participants

yupeng820921 Benjamin Dobell Johannes Sjölund Artem Sidorenko Kumar McMillan Alvaro del Castillo mcayland tos69400 Rudikza David Alexander johnleuner raindog469 Michal Kottman Diego Viola LucasDeVil Michael Kitange Florian Rathgeber
yupeng820921

My command:

heimdall flash --repartition --pit PIT.pit --factoryfs factoryfs.img --cache cache.img --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin --hidden hidden.img --data data.img

The output of heimdall:

Heimdall v1.3.1, Copyright (c) 2010-2011, 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...
Handshaking with Loke...

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

Uploading PIT
PIT upload successful
Uploading KERNEL
100%
KERNEL upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DATAFS
100%
ERROR: Failed to confirm end of file transfer sequence!
DATAFS upload failed!
Ending session...
ERROR: Failed to send end session packet!
Re-attaching kernel driver...

Does anyone can help me?

Benjamin Dobell

I believe this is fixed in version 1.3.2. Please reopen the ticket if the problem still persists.

Johannes Sjölund
wulax commented

I am having this issue with 1.3.2, as well as latest git version (as of April 6). Using Heimdall on Linux and flashing a custom ROM to a Samsung Galaxy S II (GT-I9100). I think flashing radio and kernel images works (at least no error is shown) but flashing the larger factoryfs image does not. Libusb is version 1.0.8 (installed from distro package manager).

$ heimdall flash --factoryfs factoryfs.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...
Attempt failed. Detaching driver...
Claiming interface again...
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 FACTORYFS
45%
ERROR: Failed to confirm end of file transfer sequence!
FACTORYFS upload failed!
Ending session...
Rebooting device...
Re-attaching kernel driver...

Artem Sidorenko

Confirm, the same issue with 1.3.2 and with latest git version:

heimdall flash --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...
Attempt failed. Detaching driver...
Claiming interface again...
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 CACHE
100%
ERROR: Failed to confirm end of file transfer sequence!
CACHE upload failed!
Ending session...
Rebooting device...
Re-attaching kernel driver...

Kumar McMillan

Using 1.3.2:

heimdall flash --factoryfs system.img

was also resulting in

Uploading CACHE
100%
ERROR: Failed to confirm end of file transfer sequence!

Downgrading to 1.3.1 fixed the problem for me. As requested, I'm reopening (oh, heh, or someone with permission can do that).

Alvaro del Castillo
acs commented

Using 1.0.2

root@lenovix:/home/acs/devel/android/s2/firmware# heimdall flash --cache cache.img

Heimdall v1.0.2b, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
...
Claiming interface...   Failed. Attempting to detach driver...
Claiming interface again...   Success
Setting up interface...   Success
Beginning session...
Handshaking with Loke...   Success

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

Uploading CACHE
100%
CACHE upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
mcayland

@kumar303: Thank you thank you thank you!

I attempted to use Heimdall 1.3.2 yesterday built from source on Debian Squeeze to upgrade my Galaxy S2 to ICS, and I kept receiving the same "ERROR: Failed to confirm end of file transfer sequence!" message leaving my phone as a brick for several hours :(

For me, the bug only seemed to occur uploading larger files to larger partitions such as CACHE and FACTORYFS - smaller uploads seemed to work fine.

In short, I downgraded Heimdall to 1.3.1 and the upload completed successfully enabling me to get my phone back.

@Benjamin-Dobell: please can we urgently re-open this bug? And perhaps 1.3.2 should be temporarily removed from download until this has been fixed?

tos69400

Hello,
First excuse me for my bad english.
Today, I have tried to flash my Galaxy Note N7000 with Heimdall Frontend and I have the same issue : i can't flash cache or factoryfs with this built.
With the v1.3.1 i can't flash data. For me it is indispensable to flash it with the new Android Kernel (ICS 4.0.3) coming from Taiwan (ZSLPF).
If you want i can make deb package for x64 and send to you. Great Job.

Rudikza
Rudikza commented

I had the same issue trying to flash a Samsung Galaxy S using 1.3.2 but after downgrading to 1.3.1 everything worked fine.

David Alexander

Seconded on all counts with Galaxy S2 (i777) and heimdall 1.3.2. Installing 1.3.1 fixed this issue.

johnleuner

I saw the same thing flashing a Galaxy S2.

I used version 1.3.1 instead (git checkout -b fbbed42) and it worked fine.

raindog469

Regression confirmed on SGSII, Epic Touch 4G (SPH-D710).

heimdall flash --factoryfs factoryfs.img
...
Uploading FACTORYFS
21%
ERROR: Failed to confirm end of file transfer sequence!
FACTORYFS upload failed!

Reverting to 1.3.1 did the trick. Notably, it paused after each multiple of 21%, the phone updated its progress bar, and then the flash continued. Maybe there was some timeout value that got reduced in 1.3.2?

Michal Kottman

Confirming that Heimdall 1.3.2 fails with SG SII while uploading factoryfs:

Uploading FACTORYFS
43%
ERROR: Failed to confirm end of file transfer sequence!
FACTORYFS upload failed!
Ending session...
Rebooting device...

Reverting to 1.3.1 worked fine.

Diego Viola

I had this same problem when I was trying to flash the stock ICS ROM on my SGS2 GT-I9100G.

Reverting to Heimdall 1.3.1 worked fine.

LucasDeVil

Same problem using 1.3.2 here with the cache.img, trying 1.3.1 as well.

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.

Michael Kitange

doesn't work on latest commit. but works fine on tag v1.3.1

Florian Rathgeber
kynan commented

Mint Nadia (Ubuntu 12.10 amd64), Samsung Galaxy SII I9100: flashing factoryfs fails on 1.3.1, 1.3.2, 1.4.0rc2. Successful only on 9d7008e.

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.