Develop Bugs

error when flashing ROM via Odin

hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Mashari_F said:
hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
1) Have you tried to use an other usb port?
2) do you use the original usb cable?
3) do you have all the samsung drivers installed?
4) make eure that samsung kies is not running in the background
Hope it helps you
Gesendet von meinem SM-P600 mit Tapatalk

Got the same problem, so recovered it from kies
Skickat från min SM-P605 via Tapatalk

Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.

ronaldphl said:
Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.
Click to expand...
Click to collapse
Is it giving you a FAIL after flashing , or doesn`t show up after a successful flash.
If it doesn`t show up after flashing , re-flash but untick "Auto-Reboot" within odin before flashing & restart manually after flashing.

I have a "Fail after flashing" - complete (Write) - operation failed in Odin

Which odin
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck

FSkyman said:
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck
Click to expand...
Click to collapse
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well

Recovery Flashing
ronaldphl said:
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well
Click to expand...
Click to collapse
Now I am confused are you talking about recovery or rom ?
The only recovery I could get to work was the TWRP - this Zip file comes with a Odin that works.
Cwm philz are not working.
But keep in mind as soon you installed twrp your knox counter is tripped.
For rom flashing you have to wipe your tablet and then follow these instructions xxxx://www.droidgator.com/update-galaxy-note-101-sm-p605-android-43-xxubmj9-firmware/.
Before starting backup your tab then everything should be fine.

Thanks for your effort in helping me out...
Before I sent my tablet for servicing... I restored the tablet with Kies to the original factory setting and rom as I HAD rooted my P605 and flashed a custom rom before. [Although the Know count is 0*1 anyway.... but the service centre was kind enough to fix my tablet as it's a hardware failure instead of anything to do with the ROM ]
When I got my tablet back and tried to flash the TWRP into it, this problem surfaced. And I read from another post that some say flashing a Samsung original rom could help I tried but to no avail. Still I am waiting and looking for a solution.
I tried Odin 3.04 3.07 and 1.85 with the two versions of TWRP but still none of them work.

Cant flash Stock firmmware
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3

aelaan said:
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?
Click to expand...
Click to collapse
Although it failed, I was able to recover using kies and use tablet as normal without data loss. It might be because at that point I had not rooted my tab and system state was still original in odin.
By the way I was on MJ4 xsa(AUSTRALIA) trying to install NC2 TGY(HONG KONG).
Now I have rooted it and have I installed NC2. I am still not sure what the issue was. But the only thing I did different was, first was using a virtual machine, but now did in an actual windows machine.
Can you please try this? If you can, install back NC2 using odin. Boot it once, then try recovering using kies. Kies recover mode gets your latest firmware based on your serial number. Not what firmware you are running.
Please post back the result. Interested to know the outcome.
Sent from my SM-P605 using XDA Premium 4 mobile app
---------- Post added at 08:38 AM ---------- Previous post was at 08:33 AM ----------
Khazaad said:
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3
Click to expand...
Click to collapse
I don't think it is. Although the specs are the same, read somewhere that the internal partition structure for carrier branded firmware are different to generic. Don't remember where I read that. But can't confirm that either.
Sent from my SM-P605 using XDA Premium 4 mobile app

Bricked my phone and need help

So, I've recently wanted to use a custom ROM for my phone, and I have done this before, but there's a bunch of changes I guess. I thought that "unified s3" meant that the ATT variants and others (including my i747m) would be compatible, so I tried to flash "Liquid Smooth v3.0" ROM but it didn't work with TWRP. So I got CWM and restored my phone (also my restore file by accident) so my phone was totally wiped, but I could flash the ROM. The problem occurs here, the phone WILL NOT boot, it is stuck at the "Samsung Galaxy S III" splash and won't go past it. I cannot delete the cache or anything without the phone restarting itself. I tried to flash a modem with Odin but get an error also.
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've been searching the forums for a way to fix my i747m but I cannot find anything. Any solutions or is my phone dead. Also I can get into both recovery and download screen. I cannot flash a stock ROM because another error pops up. And when I go into download mode and flash, the "QUALCOMM SECUREBOOT: ENABLE" turns into "SECURE CHECK FAIL : aboot"

Tonamon said:
So, I've recently wanted to use a custom ROM for my phone, and I have done this before, but there's a bunch of changes I guess. I thought that "unified s3" meant that the ATT variants and others (including my i747m) would be compatible, so I tried to flash "Liquid Smooth v3.0" ROM but it didn't work with TWRP. So I got CWM and restored my phone (also my restore file by accident) so my phone was totally wiped, but I could flash the ROM. The problem occurs here, the phone WILL NOT boot, it is stuck at the "Samsung Galaxy S III" splash and won't go past it. I cannot delete the cache or anything without the phone restarting itself. I tried to flash a modem with Odin but get an error also.
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've been searching the forums for a way to fix my i747m but I cannot find anything. Any solutions or is my phone dead. Also I can get into both recovery and download screen. I cannot flash a stock ROM because another error pops up. And when I go into download mode and flash, the "QUALCOMM SECUREBOOT: ENABLE" turns into "SECURE CHECK FAIL : aboot"
Click to expand...
Click to collapse
Since you can get into both download and recovery modes, there is plenty of hope and your phone is far from dead. Odin probably failed because you were trying to flash incompatible firmware or one that involved a bootloader downgrade attempt. You may be able to recover by re-flashing the correct firmware from (custom) recovery. You need to provide more information including what stock were you on before going custom and what stock you are now trying to revert to. When flashing stock firmware, however, you need to be sure you are working with the right ones. In spite of the near similarity in the names, firmware for the i747U... (AT&T) is different from the Canadian versions (i747M...) and you should be careful to pick only the ones specific to your phone model. You probably were on a 4.3 bootloader so your safest bet now may be to search for and download the i747M 4.3 stock rom, bootloader/modem and kernel zips and reflash these via recovery. If you are on TWRP, you may also do an advance wipe to remove all existing firmware before flashing new ones.

Telus Note 2 stuck in bootloop

I have a Telus Note 2 sgh-I317M I believe it has android 4.3 on it but not sure. It was rooted using chainfires method.
I am not able to enter recovery mode but I can enter download mode.
If the phone is in download mode and I open Kies it spins on connection but never connects. If phone isnt in download mode Kies doesnt see it.
With Odin is able to see the phone in download mode but when I try and do anything the results are below.
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried uninstalling Kies and I have used Odin v1.85, V1.3 and V3.10
and I have tried different firmware for the phone starting with 4.3
I have tried using a different computer and different usb cables.
I have a second note 2 that is able to connect to both Odin and kies on this computer.
If I should post this question else where my apologies and please point me in the right direction.
What am I missing in trying to get this fixed? Google research mentions PIT files but Im not familiar with them and I haven't found a step by step guide.

Try using Odin 3.07. I only use 3.07 and I have had great success.
Download the latest Telus ROM from sammobile. Open Odin, do no check anything except F.reset time. Flash the ROM in PDA. When you see the word Reset in the status window, remove the usb cable from the phone, pull the battery and leave it out for about 10 seconds, replace the battery, boot into recovery, perform a factory wipe, and reboot.

[Q] Revert to stock or fix CM12.1

So here are my issues.
I used CF-auto root to install custom ROMS. Roms like Hybrid just got stuck in a bootloop, regardless of how many times I wiped everything. CM works almost fine. However, it randomly reboots. No timing, app, battery, usage, or other patterns I can see. It just randomly reboots itself.
I downloaded the BOB7 and tried to Odin back, but it just fails everytime.
Log on the phone says
UDC START
SW REC CHECK FAIL: [aboot]Fused 2 > binary 1
[1]eMMC write fail: ABOOT
Odin reports:
<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> 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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I either need to fix CM so it quits randomly rebooting, or go back to stock. I'm not too picky as to which option, so I'll take whatever I can get.

James.Q.Campbell said:
So here are my issues.
I used CF-auto root to install custom ROMS. Roms like Hybrid just got stuck in a bootloop, regardless of how many times I wiped everything. CM works almost fine. However, it randomly reboots. No timing, app, battery, usage, or other patterns I can see. It just randomly reboots itself.
I downloaded the BOB7 and tried to Odin back, but it just fails everytime.
Log on the phone says
UDC START
SW REC CHECK FAIL: [aboot]Fused 2 > binary 1
[1]eMMC write fail: ABOOT
Odin reports:
<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> 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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I either need to fix CM so it quits randomly rebooting, or go back to stock. I'm not too picky as to which option, so I'll take whatever I can get.
Click to expand...
Click to collapse
Use your backup and try to fix CM

xxSTARBUCKSxx said:
Use your backup and try to fix CM
Click to expand...
Click to collapse
Yeah, accidentally deleted backup. Kicked myself plenty for it. I've wiped and reinstalled CM half a dozen times now with no luck. 3x factory reset, cache, dalvik, data and system wiped 3, 4 or even 5 times.
Still reboots randomly.

James.Q.Campbell said:
Yeah, accidentally deleted backup. Kicked myself plenty for it. I've wiped and reinstalled CM half a dozen times now with no luck. 3x factory reset, cache, dalvik, data and system wiped 3, 4 or even 5 times.
Still reboots randomly.
Click to expand...
Click to collapse
Ever thought of trying Noterized? it will flash through Odin, give that a test drive.

xxSTARBUCKSxx said:
Ever thought of trying Noterized? it will flash through Odin, give that a test drive.
Click to expand...
Click to collapse
I downloaded it, but have no idea how to flash it through Odin. Help?

James.Q.Campbell said:
I downloaded it, but have no idea how to flash it through Odin. Help?
Click to expand...
Click to collapse
When you click on PDA (AP) , does it not show up in the folder you downloaded it to/desktop when trying to select said file?

Try downloading cwm in odin

James.Q.Campbell said:
I downloaded it, but have no idea how to flash it through Odin. Help?
Click to expand...
Click to collapse
You don't flash it via Odin. Install thr latest TWRP through Odin then boot into recovery make a backup first then factory reset and wipe system and you should be able to install Noterized.
Sent from my SM-N910P using Tapatalk
---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------
Kayotick said:
You don't flash it via Odin. Install thr latest TWRP through Odin then boot into recovery make a backup first then factory reset and wipe system and you should be able to install Noterized.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sounds like the only thing that will work for you is CM or Noterized both flashable via TWRP.
Sent from my SM-N910P using Tapatalk

Sorry for the misinformation, i thought Noterized worked via Odin after taking the OE1 update.

T-Mobile SIII Bricked

Hey,
I had a non-rooted T-Mobile SIII with stock ROM installed. A few days back, it just rebooted automatically and got in a boot loop. I don't know what happened. After that, I tried to install the stock ROM again via Odin but it seems that Odin is not writing anything on it. The download mode shows
ODIN MODE
PRODUCTNAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV:1​
WHAT HAPPENS
The Phone turns on but cannot go further than the "Samsung Galaxy S3" logo
When I try to go to the recovery mode, the Samsung logo with booting recovery comes and then it just shifts to the boot loop
I can get to the Download Mode and Odin recognizes the device.
It shows the PASS status after writing a recovery image but it just doesn't work
WHAT I HAVE DONE UNTIL NOW
Tried to flash CMW (touch and non-touch both). Odin gives pass but it still boots to boot loop
Same happens with TWRP
Tried to flash the Stock F/W but Odin fails every time before even trying

What error is shown in the Odin log? Tried using different usb cables and usb ports with Odin?

T-999 unbrick
By your description, it looks like your kernel is corrupt. It happened a few times with my note 3 stock, as well as my S III back in the day.
The way I unbricked successfully each time, was to feed Odin one piece of the stock ROM at a time, in this order:
1. Kernel
2. TWRP 2.7.0
3. ROM
IMPORTANT: if you end up going this way, be sure to power down the unit after each STEP. I even removed the battery, just to be sure.
DO NOT ALLOW ODIN TO REBOOT THE UNIT.
Last thing, be aware that the stock upgrade you use has to match any firmware upgrade you may have flashed in the past.
This is a way doable solution.
Ping me if you have questions or need links. I'm still a newly registered user on this board and can't post links yet.
Good luck!
Abdullah.tariq1988 said:
Hey,
I had a non-rooted T-Mobile SIII with stock ROM installed. A few days back, it just rebooted automatically and got in a boot loop. I don't know what happened. After that, I tried to install the stock ROM again via Odin but it seems that Odin is not writing anything on it. The download mode shows
ODIN MODE
PRODUCTNAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV:1​
WHAT HAPPENS
The Phone turns on but cannot go further than the "Samsung Galaxy S3" logo
When I try to go to the recovery mode, the Samsung logo with booting recovery comes and then it just shifts to the boot loop
I can get to the Download Mode and Odin recognizes the device.
It shows the PASS status after writing a recovery image but it just doesn't work
WHAT I HAVE DONE UNTIL NOW
Tried to flash CMW (touch and non-touch both). Odin gives pass but it still boots to boot loop
Same happens with TWRP
Tried to flash the Stock F/W but Odin fails every time before even trying
Click to expand...
Click to collapse

dangmouse said:
The way I unbricked successfully each time, was to feed Odin one piece of the stock ROM at a time, in this order:
1. Kernel
2. TWRP 2.7.0
3. ROM
Click to expand...
Click to collapse
I followed all your steps. I made it sure after every step that my phone powered down. I also removed the battery for a while after every step but it all ends up the same way. The Kernel and The Recovery are successfully written but it gives an error on the ROM. And nothing changes, I still can't boot to recovery or OS
ODIN LOG
<ID:0/011> Added!!
<ID:0/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> boot.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> recovery.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin engine v(ID:3.1203)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> sbl2.mbn
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Are you using the latest stock ROM from sammobile.com?

audit13 said:
Are you using the latest stock ROM from sammobile.com?
Click to expand...
Click to collapse
Yes, I downloaded the latest firmware available on the sammobile.com

Maybe try flashing with a pit file.

audit13 said:
Maybe try flashing with a pit file.
Click to expand...
Click to collapse
Where can I get the pit file??

You'll have to search to find the correct pit file ford your phone's model number and onboard memory size.
Did you flash the stock firmware as a single file in Odin? Tried different usb ports and usb cables?

audit13 said:
You'll have to search to find the correct pit file ford your phone's model number and onboard memory size.
Did you flash the stock firmware as a single file in Odin? Tried different usb ports and usb cables?
Click to expand...
Click to collapse
Yes I tried one file and different usb ports and cables

So you unzipped the file from sammobile only once to get a tar.md5 file?

audit13 said:
So you unzipped the file from sammobile only once to get a tar.md5 file?
Click to expand...
Click to collapse
Yes I used the tar.md5 file

If you can find a pit file and it still doesn't work with the pit file, the memory chip in the phone may be damaged.
https://www.androidfilehost.com/?w=files&flid=6471

audit13 said:
Maybe try flashing with a pit file.
Click to expand...
Click to collapse
Same result after trying with a pit file.

Based on everything you have tried and the end result, I think the memory chip is damaged.

audit13 said:
Based on everything you have tried and the end result, I think the memory chip is damaged.
Click to expand...
Click to collapse
Is there anything I can do 'bout that?

I don't think so. The simplest solution may be to find a used phone with a damaged screen and working motherboard.

audit13 said:
I don't think so. The simplest solution may be to find a used phone with a damaged screen and working motherboard.
Click to expand...
Click to collapse
Thanks for your help man. It seems that the memory chip is fried. Searching for a motherboard now

In your first post you said you can get into download mode.
As last resort I'd try ADB. Try flashing recovery and or boot or even the entire ROM (sideload) via adb (and not Odin). Plenty of tutorials here and on the web and you seem knowledgeable enough to do that yourself.