Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

FAIL! (Size)

OP m7mel

13th April 2014, 05:28 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Apr 2014
<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 by m7mel; 13th April 2014 at 06:15 PM.
17th April 2014, 03:49 PM   |  #2  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Aug 2010
i have same problem.
I dont know what wrong Pls help







Thank you.
18th April 2014, 10:01 AM   |  #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)
Last edited by danielfg87; 18th April 2014 at 10:12 AM.
The Following User Says Thank You to danielfg87 For This Useful Post: [ View ]
18th April 2014, 10:27 AM   |  #4  
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)
Attached Files
File Type: rar G900Fonly_KLTE_EUR_OPEN.rar - [Click for QR Code] (1.0 KB, 904 views)
1st July 2014, 12:35 AM   |  #5  
born4trance's Avatar
Member
Flag Rotterdam(ned)
Thanks Meter: 16
 
87 posts
Join Date:Joined: Jan 2008
More
Quote:
Originally Posted by m7mel

<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)

Quote:
Originally Posted by danielfg87

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:
Last edited by born4trance; 3rd July 2014 at 01:30 AM.
3rd July 2014, 02:49 AM   |  #6  
born4trance's Avatar
Member
Flag Rotterdam(ned)
Thanks Meter: 16
 
87 posts
Join Date:Joined: Jan 2008
More
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:
Last edited by born4trance; 13th July 2014 at 09:47 PM.
14th July 2014, 10:05 AM   |  #7  
fffft's Avatar
Senior Member
Thanks Meter: 622
 
1,978 posts
Join Date:Joined: Jul 2013
..
Last edited by fffft; 17th November 2014 at 10:55 AM.
The Following 2 Users Say Thank You to fffft For This Useful Post: [ View ]
14th July 2014, 10:12 AM   |  #8  
born4trance's Avatar
Member
Flag Rotterdam(ned)
Thanks Meter: 16
 
87 posts
Join Date:Joined: Jan 2008
More

Quote:
Originally Posted by fffft

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 by born4trance; 14th July 2014 at 10:17 AM.
23rd August 2014, 10:08 PM   |  #9  
Senior Member
Thanks Meter: 47
 
302 posts
Join Date:Joined: Dec 2011
Question
Quote:
Originally Posted by fffft

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 ?
24th August 2014, 02:22 AM   |  #10  
fffft's Avatar
Senior Member
Thanks Meter: 622
 
1,978 posts
Join Date:Joined: Jul 2013
..
Last edited by fffft; 17th November 2014 at 10:55 AM.

The Following User Says Thank You to fffft For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes