Database Users

[Q] Galaxy Y Bricked

Hi,
I am completely new in phone flashing. I met some troubles with my Galaxy Y device.
I will explain the details and hope someone can give me guidelines to fix it.
I have a Galaxy Y that freezes at logo screen when powered up.
We can access Download mode, but not Recovery one.
Initially it had an official rom that has not been modified.
I get trouble with it with a boot loop.
So, I went to Recovery Mode and did a wipe Data. This worked once and then I get boot loop problem 2 days later.
I tried again to wipe data through Recovery mode, but now with out result.
So I decided to flash it … Odin failed and now it stays frozen at the logo screen when powered up.
For the flashing:
- I try on 3 different PC (1 Win7 and 2 XP) and tried different USB ports
- For the drivers, I tried by installing Kies_2.3.3.12085_7_5 and by installing USB drivers only (SAMSUNG_USB_Driver_for_Mobile_Phones.exe)
- I tried a lot of time, with and without restarting Odin
- I tried with Odin 1.83, 1.84 and 1.85 ( I know that 1.84 and 1.85 support S5360 model)
- And I tried using different ROMs
The communication between Odin and the device seems correct (I can see the yellow highlight when connecting the device in Download mode)
I tried some Doky’s packages from here http://forum.xda-developers.com/showthread.php?p=21846620:
- S5360_XXKK6_OXXKK2_XXKK5
- S5360_XXKL3_OXXKL1_XXKL3
- S5360_XXLF3_OXXLF3_XXLF3
I tried also some other packages containing only one file and one dll (retrieved from here as example http://www.tsar3000.com/Joomla/inde...laxy-y-firmwares&catid=55:samsung&Itemid=82):
- S5360XXKL3_LUXKJ1_Luxembourg_Android_2.3.6
- S5360TAJKK3_TLPKK3_Austria_Android_2.3.6
- S5360LUHKJ2_PSNKJ2_Argentina_Personal_Android_2.3.6
- S5360XXLA2_S5360OXXLA2_EUR
- S5360XXKL3_S5360OXXKL1_EUR
I tried also this package, as I saw that some people were able to unbrick there device with it:
GalaxyS5360_DDLA1_2.3.6
This last package contains totoro_0623.pit file. So I tried with and without Re-Partition checked.
I tried also to download totoro_0623.pit file again from other locations and the .pit file with other packages from the previous lists, but without success (Odin always fails).
On point that can be perhaps important is then when flashing, with Odin, the CSC package alone it always succeeds.
The same, when flashing only BOOT package (taken from GalaxyS5360_DDLA1_2.3.6), is it always successful.
I tried also to flash different couples of BOOT and CSC packages and it is always successful.
Unfortunately, I am completely new in this domain and I do not know the purpose of each package (BOOT, PDA, MODEM and CSC).
So, I do not know what to do now ... Perhaps someone can have some advices or guidelines to help.
Thanks again.
Yacy.

refer to youtube watch with video TUT

yabyuh22 said:
refer to youtube watch with video TUT
Click to expand...
Click to collapse
Thank you very much, Tabyuh22, for your advice.
Unfortunately, I did a lot of search already (xda forum and google), but unfortunately without success.
The only unbrick tutorial I found, related to Galaxy Y, is flashing GalaxyS5360_DDLA1_2.3.6 packages with Odin. I tried this already, but unfortunately, it was not successful (Odin flash fails, except if I flash, BOOT and CSC packages only, as explained previously).
Perhaps you have in mind a specific link that I can try?
Thanks again.
Yacy.

Most probably, the Odin you downloaded is a corrupt one, or maybe you're using an older version. Try the one from Doky73's thread.

sorry but i believe its the Odin,
try the v1.85 and do not use a pit file,
very well detailed question,
thanks

can you post screenshot for odin after "Fail" and/or all text in Message area
and I will help I've unbricked my phone just today

Thank you very much for your advice and help.
In fact, I tried already to download Odin 1.85 from different sources. I just tried again, but unfortunately I get the same bad result.
What I find strange is that the flash is successful when using the CSC package only.
I do not know how to put images in the post, so I attached 2 .jpg snapshots of Odin failure and success.
Here is Odin's log when failure (when trying to flash PDA, MODEM and CSC packages):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXLF3.tar.md5 is valid.
<OSM> MODEM_S5360_XXLF3.tar.md5 is valid.
<OSM> CSC_S5360_OXXLF3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And here is Odin's log when success (when trying to flash CSC package only):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXLF3.tar.md5 is valid.
<OSM> MODEM_S5360_XXLF3.tar.md5 is valid.
<OSM> CSC_S5360_OXXLF3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> csc.rfs
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
Thanks again for your help.
Yacy

Just choose PDA and It's required file and live Phone and CSC alone then you'l be able to boot into Recovery mod

Mohamed.Anwar said:
Just choose PDA and It's required file and live Phone and CSC alone then you'l be able to boot into Recovery mod
Click to expand...
Click to collapse
It seems it is what I did. The result is in the Failed snapshot I attached.
Do you see any thing wrong in this snapshot and the associated logs?
(I tried also to flash PDA or PHONE alone, but failed. It is successful only if I flash CSC alone)
Thanks again.
Yacy.

Try data/cache wipe after flash,maybe it helps
MANY GREEEEETZ!!!

Alright, now when you downloaded the firmware package, there would be 4 different .tar files - BOOT_something.tar, PDA_something.tar, CSC_something.tar and MODEM_something.tar. Sometimes, there is one more, DefaultCalDataBOOT_something.tar, which i use in place of BOOT. Try flashing that in place of BOOT file. Still if it dosen't work, flash the PIT file along. Make sure the PIT's right. Our device's pit is "totoro_0623.pit".

CALIBAN666 said:
Try data/cache wipe after flash,maybe it helps
Click to expand...
Click to collapse
I imagine we can do this only by accessing Recovery Mode.
Unfortunately, I cannot access this mode, but the Download one only

anasdcool71 said:
Alright, now when you downloaded the firmware package, there would be 4 different .tar files - BOOT_something.tar, PDA_something.tar, CSC_something.tar and MODEM_something.tar. Sometimes, there is one more, DefaultCalDataBOOT_something.tar, which i use in place of BOOT. Try flashing that in place of BOOT file. Still if it dosen't work, flash the PIT file along. Make sure the PIT's right. Our device's pit is "totoro_0623.pit".
Click to expand...
Click to collapse
The only package I get containing BOOT file is GalaxyS5360_DDLA1_2.3.6. This package contains:
- BOOT_S5360DDLA1_REV05.tar.md5
- DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5
-PDA_S5360DDLA1_REV05.tar.md5
-MODEM_S5360DDLA1_REV05.tar.md5
-GT-S5360-MULTI-CSC-ODDLA1.tar.md5
Flashing BOOT_S5360DDLA1_REV05.tar.md5 alone is successful and here is Odin’s log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOT_S5360DDLA1_REV05.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> BcmBoot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
Flashing DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5 alone fails and here is Odin’s log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> BcmBoot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> HEDGE_NVRAM8_RF_LE.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Selecting totoro_0623.pit alone fails and here is Odin’s log:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The remark when flashing DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5 alone, I can see on the device the progress bar increasing, but it fails before the end.
(I do not have this at all when trying to flash PDA or MODEM files)
Thanks again.
Yacy.

Possible solution : That what I did
Keep ODIN alive don't close it then try changing USB ports and use man ports ( in the back if you're using Desktop PC ) and flash only pit and PDA if it didn't worked restart download mode
then check if you could boot into Recovery mod

Flash some kernel.tar in place of PDA file....
Then you'll be able to boot into recovery and then install any rom ....!!!!

Sorry for the late answer, as I was not available these days.
And thank you for your guide lines.
Mohamed.Anwar said:
Possible solution : That what I did
Keep ODIN alive don't close it then try changing USB ports and use man ports ( in the back if you're using Desktop PC ) and flash only pit and PDA if it didn't worked restart download mode
then check if you could boot into Recovery mod
Click to expand...
Click to collapse
I tried this operation again many times, but I always get flash failure
The_animaToR said:
Flash some kernel.tar in place of PDA file....
Then you'll be able to boot into recovery and then install any rom ....!!!!
Click to expand...
Click to collapse
I had a look to the Development area and tried to flash different kernels.
Unfortunately, I get failures again.
What is different now is that
1/ Odin hangs at the steps below:
<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> NAND Write Start!!
Click to expand...
Click to collapse
2/ In the phone, “custom bin down” counter is now uncremented.
Its value is 10 (it was zero, before trying to flash kernels from custom roms).
Do you have any other idea?
Does an alternative tool to flash the device exist?
Is there a way (perhaps by using Android design tools) to get more information about why the flash does not work (a more precise error message)?
Thanks again for your help.
Yacy.

Hi try this one ,hope it helps

denniz05 said:
Hi try this one ,hope it helps
Click to expand...
Click to collapse
Hello Yacy, I'm sorry I have no Idea about your problem. I just wanted to ask if you got your issue solved?
Actually, I bought my SGY about 3 weeks ago and I was going through problems of Flashing. I'm also interested in Flashing with a Custom ROM.
And I'm Totally new to Android. If you got the problem sorted out, can you tell me a DETAILED and CLEAR TUT for flashing one?

asd
please give me a link about galaxy y duos bricked please.

yacy said:
Hi,
I am completely new in phone flashing. I met some troubles with my Galaxy Y device.
I will explain the details and hope someone can give me guidelines to fix it.
I have a Galaxy Y that freezes at logo screen when powered up.
We can access Download mode, but not Recovery one.
Initially it had an official rom that has not been modified.
I get trouble with it with a boot loop.
So, I went to Recovery Mode and did a wipe Data. This worked once and then I get boot loop problem 2 days later.
I tried again to wipe data through Recovery mode, but now with out result.
So I decided to flash it … Odin failed and now it stays frozen at the logo screen when powered up.
For the flashing:
- I try on 3 different PC (1 Win7 and 2 XP) and tried different USB ports
- For the drivers, I tried by installing Kies_2.3.3.12085_7_5 and by installing USB drivers only (SAMSUNG_USB_Driver_for_Mobile_Phones.exe)
- I tried a lot of time, with and without restarting Odin
- I tried with Odin 1.83, 1.84 and 1.85 ( I know that 1.84 and 1.85 support S5360 model)
- And I tried using different ROMs
The communication between Odin and the device seems correct (I can see the yellow highlight when connecting the device in Download mode)
I tried some Doky’s packages from here http://forum.xda-developers.com/showthread.php?p=21846620:
- S5360_XXKK6_OXXKK2_XXKK5
- S5360_XXKL3_OXXKL1_XXKL3
- S5360_XXLF3_OXXLF3_XXLF3
I tried also some other packages containing only one file and one dll (retrieved from here as example http://www.tsar3000.com/Joomla/inde...laxy-y-firmwares&catid=55:samsung&Itemid=82):
- S5360XXKL3_LUXKJ1_Luxembourg_Android_2.3.6
- S5360TAJKK3_TLPKK3_Austria_Android_2.3.6
- S5360LUHKJ2_PSNKJ2_Argentina_Personal_Android_2.3.6
- S5360XXLA2_S5360OXXLA2_EUR
- S5360XXKL3_S5360OXXKL1_EUR
I tried also this package, as I saw that some people were able to unbrick there device with it:
GalaxyS5360_DDLA1_2.3.6
This last package contains totoro_0623.pit file. So I tried with and without Re-Partition checked.
I tried also to download totoro_0623.pit file again from other locations and the .pit file with other packages from the previous lists, but without success (Odin always fails).
On point that can be perhaps important is then when flashing, with Odin, the CSC package alone it always succeeds.
The same, when flashing only BOOT package (taken from GalaxyS5360_DDLA1_2.3.6), is it always successful.
I tried also to flash different couples of BOOT and CSC packages and it is always successful.
Unfortunately, I am completely new in this domain and I do not know the purpose of each package (BOOT, PDA, MODEM and CSC).
So, I do not know what to do now ... Perhaps someone can have some advices or guidelines to help.
Thanks again.
Yacy.
Click to expand...
Click to collapse
hey just see http://forum.xda-developers.com/showthread.php?t=1465800

[Q] cant get back to stock firm plz help warranty nearly expired

hi everyone i have an s4 mini but the cam isnt working i bought it with the CM 10 already on it
i tried getting it back to stock using odin but it always fail
i m using odin 1.85
stock firm I9195XXUBML4_I9195OXABML4_I9195XXUBML4_HOME.tar.md5
what am i doing wrong ?? plz help i still have 1 month or so in the warranty
when i put my s4 mini on download mode it displayes the following:
odin mode
product name : GT-I9190
current binary:custom
system status :custom
csb-config-lsb:0x30
write protection :enabled
and after odin fails it displayes : secure check fail :sbl2
the log odin is displaying
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUBML4_I9195OXABML4_I9195XXUBML4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

1. First of all u have a GT-I9190 no a GT-I9505.
2. Is normal that ODIN gives u error for the step 1
3. The unique u need is one firmware for ur GT-I9190
4. This correct thread for ur phone is: HERE

Joku1981 said:
1. First of all u have a GT-I9190 no a GT-I9505.
2. Is normal that ODIN gives u error for the step 1
3. The unique u need is one firmware for ur GT-I9190
4. This correct thread for ur phone is: HERE
Click to expand...
Click to collapse
thanks for the help
i m downloading the correct firmware but do i need a different odin version than the 1.85 ? if yes wich one do i need ?
best regards

fantomezone said:
thanks for the help
i m downloading the correct firmware but do i need a different odin version than the 1.85 ? if yes wich one do i need ?
best regards
Click to expand...
Click to collapse
No. But u can update ur Odin to 3.04, 3.07 or 3.09. Take a look in this forum if u want update it :highfive:

samsung galaxy s5 g900f ERROR

hi i want to update my s5 g900f but i get an error please help me fix that
---
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANE2_G900FOXA1ANE2_G900FXXU1ANE2_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
---
i am using odin 3.09
G900FXXU1ANE2_G900FOXA1ANE2_G900FXXU1ANE2_HOME.tar
with this update file

fantasy24 said:
hi i want to update my s5 g900f but i get an error please help me fix that
---
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANE2_G900FOXA1ANE2_G900FXXU1ANE2_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
---
i am using odin 3.09
G900FXXU1ANE2_G900FOXA1ANE2_G900FXXU1ANE2_HOME.tar
with this update file
Click to expand...
Click to collapse
Here is the guide-line before flashing:
1. Was USB Debugging enabled on your device?
2. You got the latest Samsung drivers installed on your pc?
3. Did you make sure Samsung kies is not running in the system tray?
4. Make sure any antivirus or firewalls are switched off.
If you still cannot flash, this normally happens when the partitions on the embedded multi media card gets corrupted for whatever reason, also known as the emmc
The phone can be restored by flashing a pit file to repartition the emmc in order so it can be written to.
Download and unzip this file and you will have a .pit file which you put in the tab marked PIT in Odin
Next make sure: re partition, f /reset, and auto reboot are ticked in options in Odin.
Reflash your stockfirmware
Let me know if it's fixed

babygau said:
Here is the guide-line before flashing:
1. Was USB Debugging enabled on your device?
2. You got the latest Samsung drivers installed on your pc?
3. Did you make sure Samsung kies is not running in the system tray?
4. Make sure any antivirus or firewalls are switched off.
If you still cannot flash, this normally happens when the partitions on the embedded multi media card gets corrupted for whatever reason, also known as the emmc
The phone can be restored by flashing a pit file to repartition the emmc in order so it can be written to.
Download and unzip this file and you will have a .pit file which you put in the tab marked PIT in Odin
Next make sure: re partition, f /reset, and auto reboot are ticked in options in Odin.
Reflash your stockfirmware
Let me know if it's fixed
Click to expand...
Click to collapse
1. Was USB Debugging enabled on your device?
now i have no android rom in my cell because in plizz i format that now there is no os

babygau said:
Here is the guide-line before flashing:
1. Was USB Debugging enabled on your device?
2. You got the latest Samsung drivers installed on your pc?
3. Did you make sure Samsung kies is not running in the system tray?
4. Make sure any antivirus or firewalls are switched off.
If you still cannot flash, this normally happens when the partitions on the embedded multi media card gets corrupted for whatever reason, also known as the emmc
The phone can be restored by flashing a pit file to repartition the emmc in order so it can be written to.
Download and unzip this file and you will have a .pit file which you put in the tab marked PIT in Odin
Next make sure: re partition, f /reset, and auto reboot are ticked in options in Odin.
Reflash your stockfirmware
Let me know if it's fixed
Click to expand...
Click to collapse
no still the same error

Well, could you pull off your sd card and sim card then retry again

had same problem.. turn off in settings - security the reactivation lock

babygau said:
Well, could you pull off your sd card and sim card then retry again
Click to expand...
Click to collapse
i pull my sd card and sim but still same error and how i go in secaurity bcoz now there is no os in my phone

any update friends...........

could you try to flash a custom recovery (whatever your choice is: Philz Touch, CWM...), then boot into recovery, wipe /data, /cache, and /system
then follow my above instruction step by step

there: http://forum.xda-developers.com/showthread.php?t=2784737 work fine
THANK YOU babygau!

Borfas said:
there: http://forum.xda-developers.com/showthread.php?t=2784737 work fine
THANK YOU babygau!
Click to expand...
Click to collapse
Well, I'm glad it helped

babygau said:
could you try to flash a custom recovery (whatever your choice is: Philz Touch, CWM...), then boot into recovery, wipe /data, /cache, and /system
then follow my above instruction step by step
Click to expand...
Click to collapse
oooh still same error

fantasy24 said:
oooh still same error
Click to expand...
Click to collapse
You should use Kies then, bcoz I have no idea what you did
Open Kies, choose Firmware Upgrade and Initialization and follow its step by step instruction.

babygau said:
You should use Kies then, bcoz I have no idea what you did
Open Kies, choose Firmware Upgrade and Initialization and follow its step by step instruction.
Click to expand...
Click to collapse
ookz i am using now kies ... and tell me the update i download is correct

fantasy24 said:
ookz i am using now kies ... and tell me the update i download is correct
Click to expand...
Click to collapse
Kies automatically download the suitable firmware for you, just sit back and relax mate

babygau said:
kies automatically download the suitable firmware for you, just sit back and relax mate
Click to expand...
Click to collapse
okz but now i get this message
sm-g900f does not support initialising.

fantasy24 said:
okz but now i get this message
sm-g900f does not support initialising.
Click to expand...
Click to collapse
Couldn't help you more bro unless you showed me your steps.
I really don't know what's wrong with your phone.
If you have remote connection (teamviewer ...), I might have a look but not sure I can help you out, send me your private message if you want, I'm available now

babygau said:
Couldn't help you more bro unless you showed me your steps.
I really don't know what's wrong with your phone.
If you have remote connection (teamviewer ...), I might have a look but not sure I can help you out, send me your private message if you want, I'm available now
Click to expand...
Click to collapse
thanks alot bro..

Code:
<ID:0/015> cache.img.ext4
<ID:0/015> hidden.img.ext4
<ID:0/015> FAIL! (Size)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea why the f*ck does ODIN 3.09 show this when trying to flash official 5.0 firmware? Just bricked my phone because of this. Everything goes ok until hidden.img.ext4. After that, FAIL.

[HOW TO] Fix (system rev. check fail device: 2 binary 1) In 5.1.1 G920F

How to fix system rev. check fail device: 2 binary 1 error when flashing a custom 5.1.1 ROM
If this error has appeared after flashing the new Bootloader and Modem for BOFJ
Download this: https://mega.co.nz/#!E05hTYaS!_vad3fvvKCwWiMmgWGrGgc69KYdgYRa1wFCmxYzwH3s
(Stock 5.1.1)
Once installed and passed with ODIN (Flash as AP)
Power off the phone and boot into download mode
Once in download mode flash the latest TWRP 2.8.7.1
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570
After flashed you'll be able to boot into recovery and flash your custom ROM ​

Thanks
Just fixed my baby s6

I get error..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Reflash with stock 5.1.1 via odin.
ROMs for G920F:
http://www.sammobile.com/firmwares/database/SM-G920F/

Is there a 920T version of this?

Here you go:
http://www.sammobile.com/firmwares/database/SM-G920T/

G920I version?
Is there a 920I version as well?
Found it.
http://www.sammobile.com/firmwares/database/SM-G920I/

Criticalstriker said:
I get error..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
>>>>>>>>>>>>>First of all thank you very much to the OP!! <<<<<<<<<<<<<<<
I got the same error and solved it.
I think the reason was that I tried flashing a 502 stock when I had already flashed the 511 bootloader and modem. In my case I have a Brazilian SM-G920I GS6 and the 511 stock rom is/was not readily available for it. So I tried downloading the latest available official stock version (502) and it resulted in the error you mentioned.
So I dowloaded the India 511 version (region INU) for 920I and it finally worked.
I used samfirm to download it (http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647).
You need to input the exact model name (for me it was literally SM-G920I) and the region code for your phone. Then download it, DON'T close samfirm software, then click on Decrypt and you will finally have a ZIP from which you can extract the stock rom. And to find out your region code, you can go to www.sammobile.com and click on Firmware in the main menu at the top. Then you enter the model number and after that you will get to a screen with a dropdown menu for all available regions and their codes (for instance, region codes for Brazil are ZTO, ZTA..).
You can also download the stock roms from sammobile diretcly but it is too slow (takes a day or so).
Good luck!
:fingers-crossed:

gamekill said:
>>>>>>>>>>>>>First of all thank you very much to the OP!! <<<<<<<<<<<<<<<
I got the same error and solved it.
I think the reason was that I tried flashing a 502 stock when I had already flashed the 511 bootloader and modem. In my case I have a Brazilian SM-G920I GS6 and the 511 stock rom is/was not readily available for it. So I tried downloading the latest available official stock version (502) and it resulted in the error you mentioned.
So I dowloaded the India 511 version (region INU) for 920I and it finally worked.
I used samfirm to download it (http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647).
You need to input the exact model name (for me it was literally SM-G920I) and the region code for your phone. Then download it, DON'T close samfirm software, then click on Decrypt and you will finally have a ZIP from which you can extract the stock rom. And to find out your region code, you can go to www.sammobile.com and click on Firmware in the main menu at the top. Then you enter the model number and after that you will get to a screen with a dropdown menu for all available regions and their codes (for instance, region codes for Brazil are ZTO, ZTA..).
You can also download the stock roms from sammobile diretcly but it is too slow (takes a day or so).
Good luck!
:fingers-crossed:
Click to expand...
Click to collapse
Ok, now I'm stuck.
I've downloaded the same version as you (INU 5.1.1 for G920I) and flashed. Used for some days and now I have to take my SGS6 to service to check if they can give me a new one because I´m having some trouble with the radio of my network (the problm was before flashing any ROM). Any way, I've tried to flash stock 5.0.2 and Odin still giving the same error. In my case I tried many of 5.0.2 stocks ROMs for the G920I and none of them worked, even the stock from Claro (my carrier) doesn't work.
This is the log in Odin, after reflashing INU 5.1.1, wiping and apply download mode.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920IDVU1AOD1_G920IUWA1AOD6_G920IDVU1AOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what to do. I can't downgrade

andifds said:
Ok, now I'm stuck.
I've downloaded the same version as you (INU 5.1.1 for G920I) and flashed. Used for some days and now I have to take my SGS6 to service to check if they can give me a new one because I´m having some trouble with the radio of my network (the problm was before flashing any ROM). Any way, I've tried to flash stock 5.0.2 and Odin still giving the same error. In my case I tried many of 5.0.2 stocks ROMs for the G920I and none of them worked, even the stock from Claro (my carrier) doesn't work.
This is the log in Odin, after reflashing INU 5.1.1, wiping and apply download mode.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920IDVU1AOD1_G920IUWA1AOD6_G920IDVU1AOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what to do. I can't downgrade
Click to expand...
Click to collapse
It's not possible to downgrade to 5.0.1 if your bootloader is on 5.1.1.

Downloading now. So like all the other Odin roms it passed but does it pass in download mode on the phone that then blocks the download ?

hello!
This works on any 5.1.1?
i mean can i download any 5.1.1. for 920F and it will be fixed or i have to use exactly the rom that is posted on OP?

Once in download mode flash the latest TWRP 2.8.7.1
[url said:
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570[/url]
After flashed you'll be able to boot into recovery and flash your custom ROM [/COLOR][/SIZE]
[/CENTER]
Click to expand...
Click to collapse
hi! can someone help me to flash this recovery.img ?
thanxx in advance.

Thank you so much for this topic, Rossyyy! :good::good::good::good::good::good::good:!!!!!!!!!
Edit; The only thing is that i still get a message (top left) in really small red letters every time i boot. For a few seconds and than boot proceeds by itself....

Rossyyy said:
How to fix system rev. check fail device: 2 binary 1 error when flashing a custom 5.1.1 ROM
If this error has appeared after flashing the new Bootloader and Modem for BOFJ
Download this: https://mega.co.nz/#!E05hTYaS!_vad3fvvKCwWiMmgWGrGgc69KYdgYRa1wFCmxYzwH3s
(Stock 5.1.1)
Once installed and passed with ODIN (Flash as AP)
Power off the phone and boot into download mode
Once in download mode flash the latest TWRP 2.8.7.1
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570
After flashed you'll be able to boot into recovery and flash your custom ROM ​
Click to expand...
Click to collapse
Hey, once I am facing the "system rev. check fail device: 2 binary 1 error", I don't think I can power off the phone completely. I can just reboot the phone into the download mode. If I try to reboot into recovery it will say "recovery is not seandroid enforcing"...
How do I power off the phone completely or how do I reboot into recovery?

aeroxy said:
How do I power off the phone completely or how do I reboot into recovery?
Click to expand...
Click to collapse
Volume up, home and power button.

richajax said:
Volume up, home and power button.
Click to expand...
Click to collapse
Oh yes, I have tried this. It will reboot and says "recovery is not seandroid enforcing"...

I think you will find your answer in one of these topics?
http://forum.xda-developers.com/search.php?searchid=379334690

Thanks, fixed the soft brick on my 920i. Used the Indian 5.1.1 version but it takes an age to download. Here is an alternate link.
https://mega.co.nz/#!VZcARCrC!-Zj8gwLGkqmlEnSBemyfqsTrr4C_ilf3koUOS6_w2pE

brettule said:
Thanks, fixed the soft brick on my 920i. Used the Indian 5.1.1 version but it takes an age to download. Here is an alternate link.
https://mega.co.nz/#!VZcARCrC!-Zj8gwLGkqmlEnSBemyfqsTrr4C_ilf3koUOS6_w2pE
Click to expand...
Click to collapse
Thanks for the link. I panicked when this happened, glad i was able to find this topic through google
---------- Post added at 02:46 PM ---------- Previous post was at 02:39 PM ----------
Okay, so it failed. Now what?
I'm starting to panic lol.
<OSM> Please wait..
<OSM> G920IDVU2COF8_G920IODD2COF8_G920IDVU2COF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Can't open the specified file. (Line: 2012)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
**EDIT**
for anyone else that may ever encounter this.. .make sure your "re-partition" option is unchecked in odin.

I bricked my Note because i didnt flash the kernel :(

Hey guys,
i tried to flash my note 4 using the openrecovery method
but i forgot to flash the kernel and now my phone is stuck in the booting at the Samsung symbol. Can someone please help? i can still get into the download mode
Thank you!!!

If you can access download mode, your phone is not bricked.
Simply download last firmware for your model from sammobile, and flash it with odin...

ok thanks, will do.
But how do I safely root the note 4 5.1.1? CF-Autoroot isnt compatible

Ok, I just finished download a stock rom for my phone (.tar.zip) but when I click start in Odin it always fails for some reason...<ID:0/003> Can't open the serial(COM) port.
Edit: tried a different port now it fails at:
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
What can I do?
Does upgrading via Kies will result in losing all data?

I'm working on this issue for hours now but I'm stuck
Using Odin it will fail at sboot.bin
And kies doesnt recognize my note 4

Here's the log:
<ID:0/003> Added!!
<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/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone: SW REV. CHECK FAIL, DEVICE 2, BINARY 1

Nixdax said:
Hey guys,
i tried to flash my note 4 using the openrecovery method
but i forgot to flash the kernel and now my phone is stuck in the booting at the Samsung symbol. Can someone please help? i can still get into the download mode
Thank you!!!
Click to expand...
Click to collapse
Restore your backup in recovery

What is your exact model, G or F, what? You download the ROM from sammobile with your exact model no., and then flash.

It's N910H
I resolved it by recovering my phone via Kies though I lost all my data
Then I tried to install Xposed framework and now it's stuck in the bootloop again ...........

Never heard about the H version before! Anyway, make sure you are flashing the correct Xposed, that is Wanam's, but Arter's, and read the installation instructions closely.

Nixdax said:
It's N910H
I resolved it by recovering my phone via Kies though I lost all my data
Then I tried to install Xposed framework and now it's stuck in the bootloop again ...........
Click to expand...
Click to collapse
Please, search before flash.

H model is with Exynos processor.
http://www.sammobile.com/firmwares/database/SM-N910H/