• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

FAIL! (Size)

Search This thread

m7mel

New member
Apr 13, 2014
2
0
<OSM> G900FXXU1ANCE_G900FOJV1ANCD_G900FXXU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

device from Hong Kong
plz help me when i flash soft G900F 16GB
 
Last edited:

danielfg87

Member
Apr 9, 2009
46
31
holstebro
www.goblue.dk
Got this issue too as far i can understand we need PIT file...

Trying to flash with PIT file right now. Will post results in a few minutes

EDIT:
Did not work still fails on the Hidden.img.ext4

The Phone says:
ODIN : Invalid EXT4 image.

ODIN log:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
 
Last edited:

danielfg87

Member
Apr 9, 2009
46
31
holstebro
www.goblue.dk
Found a Solution

First flash the firmware of choice let it fail.
Unplug the device and plug it back in with out rebooting it let it stay in the failed download mode.

Now uncheck the PDA/AP and add the PIT file attached here.
make sure repartion is checked and PDA/AP is not

Flash PIT and the phone will reboot and start up with your new firmware.

Note the PIT is for G900F 16GB EU

My log:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
 

Attachments

  • G900Fonly_KLTE_EUR_OPEN.rar
    1 KB · Views: 19,192

born4trance

Senior Member
Jan 5, 2008
117
24
www.playfreeminecraft.nl
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)

Got this issue too as far i can understand we need PIT file...

<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)

@ danielfg87: I may be wrong but i see a difference between FAIL! (Size) and FAIL! (Ext4).

Are you sure that these aren't two different types or errors?

Also: The .pit of my SM-G900F is 4.640 bytes in size, but if i leave out the empty/00 hex data (padding?) in the end, the filesize and CRC32/MD5/SHA-1 matches the .pit you've attached.

Proof:
uqwEE47.png
 
Last edited:

born4trance

Senior Member
Jan 5, 2008
117
24
www.playfreeminecraft.nl
Well, guess what happened.

I tried to flash back the 4.640 bytes pit that i pulled from my device, but in Odin (download) mode it said:

SECURE CHECK FAIL : pit


However, after i hex-edited out the empty/null (padding) data and another flash attempt,

...it worked ;)


My guess is that the additional padding data wasn't supposed to be there in the first place.
Perhaps the tutorial i used to pull the .pit data wasn't "universal" or "correct" enough.

Here's a photo of the error:
6I0neNI.jpg
 
Last edited:

born4trance

Senior Member
Jan 5, 2008
117
24
www.playfreeminecraft.nl

There is a lot of guesswork and misinformation on this subject. The flash is failing because you are flashing an incompatible firmware image from another carrier. hidden.img.ext4 contains carrier specific data and is partitioned. The failure arises from several error conditions that may arise e.g. a size mismatch between the new hidden partition and the old PIT file which refers to the old (not new) firmware structure. An undefined address location, checksum error, et cetera. If the new firmware image happens to overwrite the partition boundaries the write will fail and depending on the specifics may soft brick your phone. Worse, the reverse write will succeed but leave you open to undefined calls and an unstable system, without an easily discerned cause.

You cannot (safely) flash software from any carrier onto your device despite a lot of people claiming you can. They tried it once and it worked and have erroneously assumed that it will therefore work in all cases. That is demonstrably wrong.

Better informed users can examine the partition structure and determine if the partition would be corrupted by the new firmware. But the proper method would be to flash the proper PIT (partition information) file for the new carrier in conjunction with the new firmware. A temporary workaround might be installing a custom recovery like CWM which will often resolve the issue. But you should obtain a proper PIT file for a reliable resolution.

.


You are a wise man, thank you :) (you're spot on btw; i should've examined my device's .pit in EFS Professional's Pit Magic, then i would've knew it)
 
Last edited:

u1988

Senior Member
Dec 22, 2011
408
64
Better informed users can examine the partition structure and determine if the partition would be corrupted by the new firmware. But the proper method would be to flash the proper PIT (partition information) file for the new carrier in conjunction with the new firmware. A temporary workaround might be installing a custom recovery like CWM which will often resolve the issue. But you should obtain a proper PIT file for a reliable resolution.

.

Where can i get proper PIT (partition information) file for the new carrier in conjunction with the new firmware ?!
Can we extrat from the rom itself ?

installing a custom recovery like CWM will trip the knox,
but it will clean the pit ,partition structure ?
 
  • Like
Reactions: nimbosa

buoissa

New member
Apr 22, 2013
1
0
fail

thanks a lot
I have been looking for this problem.
thanks to you my phone is back and working

you save the day
:good::good::good::good::good::good::good::good:
 

attari13

Member
Aug 26, 2012
35
4
changing frimware from KSA to SER..

i tried to change and got the hidden.ext4.tar error... how to use the pitfile ? steps please
 

vndnguyen

Senior Member
Sep 11, 2009
4,254
1,920
Vinnitsa
i tried to change and got the hidden.ext4.tar error... how to use the pitfile ? steps please

Not all flashing needs pit file. Typically only HK device needs coz it is not compatible with another devices.
On the 1st page there was a link to the pit file's thread to download.
check the pit option in the Odin software.
 

HOPNIRMO

New member
Feb 16, 2015
1
0
S5 SM-G900F Fail (size)

Guys, After reading this post, I still don´t know what to do.
I am a total amateur, Don´t know sh** , I am just following steps I found.
What happened was that after upgrading (automatically via the mobile) my S5 (G900F - bought in UK) the mobile became useless, e.g. 1 min to open whatsapp.... or photo gallery, memory crash when playing with MadSkill Motocross, and also camera problems. So I decided to go back to kitkat 4.4.2 and following the phone specifications I downloaded the stock firmware. After flashing it, I got the fail (size).

Please what to do? Because reading about the pit file I still am not sure about which file to use, or even using it.

What I had before in my mobile was - G900FXXU1B0A3 (lollipop), and I tried the downgrade with G900FXXU1BNL9_G900FTTR1BNK6_G900FXXU1BNL9_HOME.tar (kitkat)

I just wanna put my device working again. If I need to provide any information more, please let me know.

Thanks
Iuri Marmo
 

Top Liked Posts

  • There are no posts matching your filters.
  • 19
    Found a Solution

    First flash the firmware of choice let it fail.
    Unplug the device and plug it back in with out rebooting it let it stay in the failed download mode.

    Now uncheck the PDA/AP and add the PIT file attached here.
    make sure repartion is checked and PDA/AP is not

    Flash PIT and the phone will reboot and start up with your new firmware.

    Note the PIT is for G900F 16GB EU

    My log:
    <ID:0/005> Added!!
    <ID:0/005> Odin v.3 engine (ID:5)..
    <ID:0/005> File analysis..
    <ID:0/005> SetupConnection..
    <ID:0/005> Initialzation..
    <ID:0/005> Get PIT for mapping..
    <ID:0/005> Firmware update start..
    <ID:0/005> SingleDownload.
    <ID:0/005> sbl1.mbn
    <ID:0/005> NAND Write Start!!
    <ID:0/005> aboot.mbn
    <ID:0/005> rpm.mbn
    <ID:0/005> tz.mbn
    <ID:0/005> sdi.mbn
    <ID:0/005> NON-HLOS.bin
    <ID:0/005> boot.img
    <ID:0/005> recovery.img
    <ID:0/005> system.img.ext4
    <ID:0/005> modem.bin
    <ID:0/005> cache.img.ext4
    <ID:0/005> hidden.img.ext4
    <ID:0/005> FAIL! (Ext4)
    <ID:0/005>
    <ID:0/005> Complete(Write) operation failed.
    <OSM> All threads completed. (succeed 0 / failed 1)
    <ID:0/005> Removed!!
    <ID:0/005> Added!!
    <ID:0/005> Odin v.3 engine (ID:5)..
    <ID:0/005> File analysis..
    <ID:0/005> SetupConnection..
    <ID:0/005> Initialzation..
    <ID:0/005> Set PIT file..
    <ID:0/005> DO NOT TURN OFF TARGET!!
    <ID:0/005> Get PIT for mapping..
    <ID:0/005> Firmware update start..
    <ID:0/005> SingleDownload.
    <ID:0/005> RQT_CLOSE !!
    <ID:0/005> RES OK !!
    <ID:0/005> Removed!!
    <ID:0/005> Remain Port .... 0
    <OSM> All threads completed. (succeed 1 / failed 0)
    3
    Got this issue too as far i can understand we need PIT file...

    Trying to flash with PIT file right now. Will post results in a few minutes

    EDIT:
    Did not work still fails on the Hidden.img.ext4

    The Phone says:
    ODIN : Invalid EXT4 image.

    ODIN log:
    <ID:0/007> Added!!
    <ID:0/007> Odin v.3 engine (ID:7)..
    <ID:0/007> File analysis..
    <ID:0/007> SetupConnection..
    <ID:0/007> Initialzation..
    <ID:0/007> Set PIT file..
    <ID:0/007> DO NOT TURN OFF TARGET!!
    <ID:0/007> Get PIT for mapping..
    <ID:0/007> Firmware update start..
    <ID:0/007> SingleDownload.
    <ID:0/007> sbl1.mbn
    <ID:0/007> NAND Write Start!!
    <ID:0/007> aboot.mbn
    <ID:0/007> rpm.mbn
    <ID:0/007> tz.mbn
    <ID:0/007> sdi.mbn
    <ID:0/007> NON-HLOS.bin
    <ID:0/007> boot.img
    <ID:0/007> recovery.img
    <ID:0/007> system.img.ext4
    <ID:0/007> modem.bin
    <ID:0/007> cache.img.ext4
    <ID:0/007> hidden.img.ext4
    <ID:0/007> FAIL! (Ext4)
    <ID:0/007>
    <ID:0/007> Complete(Write) operation failed.
    <OSM> All threads completed. (succeed 0 / failed 1)
    1
    Better informed users can examine the partition structure and determine if the partition would be corrupted by the new firmware. But the proper method would be to flash the proper PIT (partition information) file for the new carrier in conjunction with the new firmware. A temporary workaround might be installing a custom recovery like CWM which will often resolve the issue. But you should obtain a proper PIT file for a reliable resolution.

    .

    Where can i get proper PIT (partition information) file for the new carrier in conjunction with the new firmware ?!
    Can we extrat from the rom itself ?

    installing a custom recovery like CWM will trip the knox,
    but it will clean the pit ,partition structure ?