Database Users

Not able to flash my galaxy y stock rom in odin mode

Hi i am trying to flash my galaxy y with stock rom it show the below error message.
<ID:0/003> Added!!
<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> boot.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me to get my mobile working...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

premskumar56 said:
Hi i am trying to flash my galaxy y with stock rom it show the below error message.
<ID:0/003> Added!!
<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> boot.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me to get my mobile working...
Click to expand...
Click to collapse
close samsung kies after your phone detected by odin

premskumar56 said:
Hi i am trying to flash my galaxy y with stock rom it show the below error message.
<ID:0/003> Added!!
<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> boot.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me to get my mobile working...
Click to expand...
Click to collapse
Excuse me, have u placed the same file in those PDA, PHONE & CSC fields...??
Sent Via XDA™ Premium

Galaxy_Rohit said:
Excuse me, have u placed the same file in those PDA, PHONE & CSC fields...??
Sent Via XDA™ Premium
Click to expand...
Click to collapse
+1
Seems to be same file in all fields,,
Are you extracted the package..

premskumar56 said:
Hi i am trying to flash my galaxy y with stock rom it show the below error message.
Added!!
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed /=
Click to expand...
Click to collapse
You need to flash pda file only
Sent from my GT-S6102 using xda app-developers app

You extract the zip file,place it appripriate locations and u also need to place totro.pit file Google on how to flash odin on galaxy y for more info

Sorry bro but i think there is no need to place totoro.pit ....
Read the file read me.txt in package.......
Sent from my GT-S5360

bro. this means that that when u r diownloading rom via odin ur device removed ,same as this happening to me ,i am searching for a solutuion but until now i am not succeess

Galaxy_Rohit said:
Excuse me, have u placed the same file in those PDA, PHONE & CSC fields...??
Sent Via XDA™ Premium
Click to expand...
Click to collapse
This thing is happening with my old galaxy y also... It is 1yr 9 mnth old...
I flashed many roms in it before... Jelly Blast v3 also...
& came back to original rom by CWM backup...
I seen the update is available, I tried to update it...
But it stops at 15% every time & rebooted ...
So I tried to flash firmware by ODIN but it also stopping like that...
I searched .pit file & also added it... But this problem is not solved...
[ first of all I get problem of connectivity of Y, I solved the driver problem]
anyone can solve this problem ???

INDIAN ODIN Flashable Original ROM
premskumar56 said:
Hi i am trying to flash my galaxy y with stock rom it show the below error message.
<ID:0/003> Added!!
<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> boot.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me to get my mobile working...
Click to expand...
Click to collapse
Just now I flashed ROM on Galaxy Y...
If you are in INDIA... Then just tell me, I will give you link of files which are required to flash original ROM by ODIN (INDIAN Version)...
If you think given information is useful, Then hit below thanks button...

premskumar56 said:
Hi i am trying to flash my galaxy y with stock rom it show the below error message.
<ID:0/003> Added!!
<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> boot.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me to get my mobile working...
Click to expand...
Click to collapse
Extract the .zip and then, in csc- place the file with csc in it's name
In phone- place the file with modem in it's name
In pda- put the file with pda in it's name
sent from my katana

I installed kies on my pc through the CD i have got with my phone, it means it automatically installed the USB driver or I have to mannually installed it by downloading from other site.

im in india, and im also having the same problem... can u gimme the files link that i need?
Tech-G.ONE said:
Just now I flashed ROM on Galaxy Y...
If you are in INDIA... Then just tell me, I will give you link of files which are required to flash original ROM by ODIN (INDIAN Version)...
If you think given information is useful, Then hit below thanks button...
Click to expand...
Click to collapse

rawman3d said:
im in india, and im also having the same problem... can u gimme the files link that i need?
Click to expand...
Click to collapse
Dude... Theres a thread by sir doky fr this.
Sent from my GT-S5360 using xda app-developers app

c.r.e.e.d said:
Dude... Theres a thread by sir dolly fr this.
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Hey bro,
Your error: ( )
Who is sir dolly? I thought he was Doky? LOL!
@premskumar56 And as for the OP, I recommend you use Kies Repair Phone option! or consult my thread. (FOLLOW STEPS EXACTLY PLEASE)

hey u must rename the files as .md5
for example
pda.tar as pda.tar.md5.
modem.tar as modem.tar.md5
csc.tar as csc.tar.md5..................
then u flash via odin .....it works i thin so......................
THANKZZZZZZZZZ:good:

Help!
I tried to flash Jellyblast v3 custom ROM on my Samsung Galaxy Y s5360l but its stuck at boot now. i have Odin downloaded and i downloaded the necessary files from hotfile to flash the stock rom back on my phone but when i click PDA on odin and search for the file, it is not appearing. Help would be greatly appreaciated. Thank you.

sgyboy8 said:
I tried to flash banned rom custom ROM on my Samsung Galaxy Y s5360l but its stuck at boot now. i have Odin downloaded and i downloaded the necessary files from hotfile to flash the stock rom back on my phone but when i click PDA on odin and search for the file, it is not appearing. Help would be greatly appreaciated. Thank you.
Click to expand...
Click to collapse
If it's from dokys thread you need to unzip the downloaded file
You will have three files
pda goes in pda
Modem in phone
csc in csc

thank u guys but i have same problem
hii
1st thank u all
but if u can pass us the link of those three files i would be thankful
i have same problem and the castumer is eating my mind for his mobile and i try all the ways but still cant flash it.
marcussmith2626 said:
If it's from dokys thread you need to unzip the downloaded file
You will have three files
pda goes in pda
Modem in phone
csc in csc
Click to expand...
Click to collapse

Wesam-syria said:
hii
1st thank u all
but if u can pass us the link of those three files i would be thankful
i have same problem and the castumer is eating my mind for his mobile and i try all the ways but still cant flash it.
Click to expand...
Click to collapse
See
http://forum.xda-developers.com/showthread.php?t=1465800
For odin flashable firmware
If you get it from elsewhere you need to split it using the splitter tool also on that thread

[Q] Soft Brick... Need Help :(

So I tried flashing a stock Poland 4.2.2 ROM and when I tried to flash it with Odin I got the invalid Ext4 firmware error... I tried flashing like 6 different roms and none of them work... I keep getting either that or some other weird fused 3 > BInary 2 message...
I have no idea what to do... Is it fixable? I can't get to recovery. Only download mode.
PS: i searched for an answer here and found someone with a similar problem. He just flashed a ROM and it worked for him. I tried to do the same, and no luck...

Ok I managed to get Recovery to work and I tried putting Roms in there and flashing... It's stuck on the Samsung Logo and it bootloops... Any ideas? :/

Sinotek said:
Ok I managed to get Recovery to work and I tried putting Roms in there and flashing... It's stuck on the Samsung Logo and it bootloops... Any ideas? :/
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2507403
try this but dont know if it works on 4.4.2

jaythenut said:
http://forum.xda-developers.com/showthread.php?t=2507403
try this but dont know if it works on 4.4.2
Click to expand...
Click to collapse
No luck... I think the problem is the phone assumes it's updated to 4.4.2 so now I can't do any rollback to 4.3 and I'm just stuck... No ROM is working out for me... This is horrible... Seems a lot of people are experiencing the same issue as well.

Sinotek said:
No luck... I think the problem is the phone assumes it's updated to 4.4.2 so now I can't do any rollback to 4.3 and I'm just stuck... No ROM is working out for me... This is horrible... Seems a lot of people are experiencing the same issue as well.
Click to expand...
Click to collapse
looks like your going to have to flash stock again

jaythenut said:
looks like your going to have to flash stock again
Click to expand...
Click to collapse
That's the point... Doesn't work either... My phone is stuck... I tried all possible stock ROMS. All of them either give me invalid Ext4 error or that Fuse error...
I'm starting to worry... It doesn't seem fixable...

Sinotek said:
That's the point... Doesn't work either... My phone is stuck... I tried all possible stock ROMS. All of them either give me invalid Ext4 error or that Fuse error...
I'm starting to worry... It doesn't seem fixable...
Click to expand...
Click to collapse
I would suggest trying to flash the Kitkat rom again, the one that was broken up originally from Sammobile.
Make sure the new bootloader is also flashed.
I wonder if you flashed with re-activation lock on?I know it caused a buttload of problems with 4.3 so it would definately NOT like 4.4.2....

Extract PIT file from the leaked firmware and flash the Kit Kat with the PIT file.

ultramag69 said:
I would suggest trying to flash the Kitkat rom again, the one that was broken up originally from Sammobile.
Make sure the new bootloader is also flashed.
I wonder if you flashed with re-activation lock on?I know it caused a buttload of problems with 4.3 so it would definately NOT like 4.4.2....
Click to expand...
Click to collapse
I tried. It doesn't even start to flash. Invalid Ext4 image error straight away...
vndnguyen said:
Extract PIT file from the leaked firmware and flash the Kit Kat with the PIT file.
Click to expand...
Click to collapse
There is no PIT file. It's an md5 file. I extracted all the files from it anyways. No Pit there... Maybe you could upload it for me or link it to me?

Sinotek said:
That's the point... Doesn't work either... My phone is stuck... I tried all possible stock ROMS. All of them either give me invalid Ext4 error or that Fuse error...
I'm starting to worry... It doesn't seem fixable...
Click to expand...
Click to collapse
try another new recovery, like cwm 6 that is compatible with ext4..

Sinotek said:
There is no PIT file. It's an md5 file. I extracted all the files from it anyways. No Pit there... Maybe you could upload it for me or link it to me?
Click to expand...
Click to collapse
you can find the PIT file in the CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar
download it here: http://x-mirror.cu.cc/Samsung/Note3...NA5_327209_REV03_user_low_ship_MULTI_CERT.tar

emanuelefreddo said:
try another new recovery, like cwm 6 that is compatible with ext4..
Click to expand...
Click to collapse
Recovery works fine. It's the stock ROM flashing via Odin that keeps failing.
I tried flashing ROMs via CWM. No go. Flashing goes fine but the phone bootloops on the Samsung logo...
It's so annoying Samsung doesn't have EFR on Kies for Note 9005...
vndnguyen said:
you can find the PIT file in the CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar
download it here: http://x-mirror.cu.cc/Samsung/Note3...NA5_327209_REV03_user_low_ship_MULTI_CERT.tar
Click to expand...
Click to collapse
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Ext4)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Same. Invalid EXT4 Image
Any other ideas?

Sinotek said:
Recovery works fine. It's the stock ROM flashing via Odin that keeps failing.
I tried flashing ROMs via CWM. No go. Flashing goes fine but the phone bootloops on the Samsung logo...
It's so annoying Samsung doesn't have EFR on Kies for Note 9005...
Click to expand...
Click to collapse
can stock rom be flashed by recovery?i dont like client like odin...

emanuelefreddo said:
can stock rom be flashed by recovery?i dont like client like odin...
Click to expand...
Click to collapse
Would be awesome if there would be such way... I never found it tho...

Sinotek said:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Ext4)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Same. Invalid EXT4 Image
Any other ideas?
Click to expand...
Click to collapse
Did you select to flash the pit file?
All other files are selected properly?
Can you post the screenshot of the ODIN?

Sinotek said:
Recovery works fine. It's the stock ROM flashing via Odin that keeps failing.
I tried flashing ROMs via CWM. No go. Flashing goes fine but the phone bootloops on the Samsung logo...
It's so annoying Samsung doesn't have EFR on Kies for Note 9005...
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Ext4)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Same. Invalid EXT4 Image
Any other ideas?
Click to expand...
Click to collapse
corrupted stock rom file?

vndnguyen said:
Did you select to flash the pit file?
All other files are selected properly?
Can you post the screenshot of the ODIN?
Click to expand...
Click to collapse
There are only 2 files so yeah.
I'll post a sreenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sinotek said:
There are only 2 files so yeah.
I'll post a sreenshot:
Click to expand...
Click to collapse
No, that's not correct. You should:
- Load all of 5 files to the Odin: PIT, BL, AP, CP, CSC
- Select the checkbox Re-Partition
Download all needed files here: http://x-mirror.cu.cc/Samsung/Note3/UnofficialFW/Extracted/

vndnguyen said:
No, that's not correct. You should:
- Load all of 5 files to the Odin: PIT, BL, AP, CP, CSC
- Select the checkbox Re-Partition
Download all needed files here: http://x-mirror.cu.cc/Samsung/Note3/UnofficialFW/Extracted/
Click to expand...
Click to collapse
Hmm... Odd that this wasn't in Samfirmware's site...
Will give it a shot and report back shortly. Thanks

Sinotek said:
Hmm... Odd that this wasn't in Samfirmware's site...
Will give it a shot and report back shortly. Thanks
Click to expand...
Click to collapse
This is a mirror. There is also a copy in the sammobile, and they are the same.
Look here: http://www.sammobile.com/2014/01/12...-galaxy-note-3-sm-n9005/#.UtMGEIhqC48.twitter

FAIL! (Size)

<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

i have same problem.
I dont know what wrong Pls help
Thank you.

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)

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)

m7mel said:
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
Click to expand...
Click to collapse
danielfg87 said:
Got this issue too as far i can understand we need PIT file...
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
Click to expand...
Click to collapse
@ 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:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

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:

..

fffft said:
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.
.
Click to expand...
Click to collapse
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)

fffft said:
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.
.
Click to expand...
Click to collapse
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 ?

..

If you read post five it will tell u the file name u need for the pid. The one uploaded is messed up but try the other one.
http://forum.xda-developers.com/galaxy-s5/help/help-soft-bricked-phone-t2850714

9th file down SM-G900F_pit_16GB_SER.zip
From here
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2

juDGEY2k10 said:
9th file down SM-G900F_pit_16GB_SER.zip
From here
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Click to expand...
Click to collapse
Does flashing the PIT file cause a full data wipe?

@AMoosa
yes mate

juDGEY2k10 said:
@AMoosa
yes mate
Click to expand...
Click to collapse
ok thanks. That's a pain. I have been trying to install NH6 over the top of my current NG2 ROM. It fails with the hidden.img error and I don't really want to wipe. I have flashed NG2 back on and everything is intact, so need to find a BTU-compatible NH6 I guess, unless I wipe.

how come u dont want to wipe mate no backup ?

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:

changing frimware from KSA to SER..
i tried to change and got the hidden.ext4.tar error... how to use the pitfile ? steps please

attari13 said:
i tried to change and got the hidden.ext4.tar error... how to use the pitfile ? steps please
Click to expand...
Click to collapse
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.

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

How To DO "NAND Erase " S5 (SM-G900F) !?

Hi Guys
I Had A problem with My s5 And i Have Full Thread about the problem But No one Have solve it !!
so my friend who is junior-Developer say that i must do Nand Erase !
So Please give me the way to do Nand Erase to My s5 (SM-G900F) !

ODIN can NAND erase, but be warned, it could brick your phone
Backup EFS first

*Detection* said:
ODIN can NAND erase, but be warned, it could brick your phone
Backup EFS first
Click to expand...
Click to collapse
I Have Done Nand erase With odin !!
i have putted the pit file then the stock firmware then i have checked nand erase all and efs clear and i have forget to do backup efs what should i do !? :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url]http://www.up-00.com/[/IMG]

try with odin 3.10.7
http://dl.sammobile.com/Odin3_v3.10.7.zip

daniel3x said:
try with odin 3.10.7
http://dl.sammobile.com/Odin3_v3.10.7.zip
Click to expand...
Click to collapse
i have seen the problem !!
that the internal storage is 0 MB !!

*Detection* said:
ODIN can NAND erase, but be warned, it could brick your phone
Backup EFS first
Click to expand...
Click to collapse
___________________

*Detection* said:
___________________
Click to expand...
Click to collapse
is that means that my phone is brick

Flash this PIT file with ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit, add to the PIT section, and add the stock ROM to ODIN at the same time
Stock ROM
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Flash them both together

*Detection* said:
Flash this PIT file with ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit, add to the PIT section, and add the stock ROM to ODIN at the same time
Stock ROM
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Flash them both together
Click to expand...
Click to collapse
It Says :-
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.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! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
:crying:
What should i do !?

Boot into download mode, and check which model S5 it says at the top

*Detection* said:
Boot into download mode, and check which model S5 it says at the top
Click to expand...
Click to collapse
SM-G900F

statiicz said:
SM-G900F
Click to expand...
Click to collapse
Try flashing just this with ODIN 3.10.7 (Will trip KNOX)
Code:
https://mega.nz/#!SB4jDQhY!1jGg47kUTu5eCuGaWiPpUanUHIOeTXeJvxPEUJMUGy0

*Detection* said:
Try flashing just this with ODIN 3.10.7 (Will trip KNOX)
Code:
https://mega.nz/#!SB4jDQhY!1jGg47kUTu5eCuGaWiPpUanUHIOeTXeJvxPEUJMUGy0
Click to expand...
Click to collapse
I'm Flashing With ODIN 3.10.7

statiicz said:
I'm Flashing With ODIN 3.10.7
Click to expand...
Click to collapse
Good, well that's a new ROM to try

*Detection* said:
Good, well that's a new ROM to try
Click to expand...
Click to collapse
I'm Flashing the last stock rom (Marshmallow UAE )

statiicz said:
I'm Flashing the last stock rom (Marshmallow UAE )
Click to expand...
Click to collapse
Might not work, different regions are failing with Size! error, which region was it running originally?
The one I linked it modded for BTU G900F
You can try KIES emergency firmware recovery too
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Tutorial
http://forum.xda-developers.com/showthread.php?t=2261153

*Detection* said:
Might not work, different regions are failing with Size! error, which region was it running originally?
The one I linked it modded for BTU G900F
You can try KIES emergency firmware recovery too
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Tutorial
http://forum.xda-developers.com/showthread.php?t=2261153
Click to expand...
Click to collapse
Thanks It Worked :]

Great
Next time, read warnings before jumping in

my SM-G900M feels really slow, i think my memory chip is dying, does it help with this problem? i already have the right rom to flash in my device, whats' next?

Trying to root my SM-G935V, having problems, odin error

I have being trying to root my Samsung Galaxy S7 Edge (Verizon). Android Version Oreo 8.0.0
Need help, tried a bunch of things I continue to get error codes from ODIN every time.
Example 1:
Log:
<ID:0/005> Added!!
<ID:0/005> Odin Engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 40m
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0/ failed 1)
<ID:0/005> Removed!!
<ID:0/004> Added!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot: prntscr.com/ n3d0xn

same issue
EquinoxPDX said:
I have being trying to root my Samsung Galaxy S7 Edge (Verizon). Android Version Oreo 8.0.0
Need help, tried a bunch of things I continue to get error codes from ODIN every time.
Example 1:
Log:
<ID:0/005> Added!!
<ID:0/005> Odin Engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 40m
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0/ failed 1)
<ID:0/005> Removed!!
<ID:0/004> Added!!
Screenshot: prntscr.com/ n3d0xn
Click to expand...
Click to collapse
I am running into this very same issue with my SM-G930V running 8.0.0. Big bummer. I was looking forward to flashing Android Pie on my S7. I'm hoping for a solution to this problem soon.

calscoo said:
I am running into this very same issue with my SM-G930V running 8.0.0. Big bummer. I was looking forward to flashing Android Pie on my S7. I'm hoping for a solution to this problem soon.
Click to expand...
Click to collapse
If you figure out the problem could you let me know, because I'm still trying to figure it out.

EquinoxPDX said:
If you figure out the problem could you let me know, because I'm still trying to figure it out.
Click to expand...
Click to collapse
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today.
more info here for root u8 or below
https://forum.xda-developers.com/tm...ts-engboot-t3889844/post79228084#post79228084

zfk110 said:
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today.
more info here for root u8 or below
https://forum.xda-developers.com/tm...ts-engboot-t3889844/post79228084#post79228084
Click to expand...
Click to collapse
How do I find what boot loader i'm on?

EquinoxPDX said:
How do I find what boot loader i'm on?
Click to expand...
Click to collapse
go to settings, about and then look for baseband Version then start counting from right to left, 5th letter from right to left shows your bootloader version

zfk110 said:
go to settings, about and then look for baseband Version then start counting from right to left, 5th letter from right to left shows your bootloader version
Click to expand...
Click to collapse
Thank you. Baseband version: G935VVRS9CSC1 Is my device rootable?

EquinoxPDX said:
Thank you. Baseband version: G935VVRS9CSC1 Is my device rootable?
Click to expand...
Click to collapse
Quote:
Originally Posted by zfk110
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today unfortunately your on U9, see the 5th # its "9"

zfk110 said:
Quote:
Originally Posted by zfk110
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today unfortunately your on U9, see the 5th # its "9"
Click to expand...
Click to collapse
Dangit, so I just have to wait? I was looking forward to rooting.