Database Users

[Q] [Q[ GT-I9505 odin fail while trying to restore 4.2.2 Firmware

Good Evening.
I had issues with my Rooted 4.2.2 (knox enabled firmware) and i wanted to unroot and flash my phone back to the Stock non Rooted Firmware.
Im well aware I cant Downgrade to a stock firmware With no Knox..So What i am trying to do is to flash the Official non rooted
I9505XXUDMH6_I9505OXXDMH4_I9505XXUDMH6_HOME (EUR) firmware That my phone had before it got Soft-brick.
I get to errors from Odin When i am doing the recovery Process
1) I Got this:
There is not PIT partition Table
so Ive Used a .pit file From this http://forum.xda-developers.com/showthread.php?t=2265477 Thread
and Ive retried the Process with CSB_signed_Fusion3_EUR_0325_V2.pit file But i got the Following Error:
2)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH6_I9505OXXDMH4_I9505XXUDMH6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
So I am Pretty Much At a dead end with not knowing what else to do I would appreciate if anyone can Help me With this Issue
Thank you in advance.
P.S
I am using Odin 3.07 or 3.09 and i get the same issues
my Knox_warrinty_void is at 0x1
My Phone Model is GT-9505 region unlocked
also I have tried every Usb Port on My computer and used 2 different Cables 1 from My S4 and 1 from my S1
Unfortunately i don't have access to a different computer atm, but the above Process is done to a fresh install of Windows 7 SP1 PRO (x64) Partition on my Current PC.

If i check NAND erase all in odin and then Try to Flash The.pit along with Firmware will this help or it will make it worse?

Please any ideas ? :/
EDIT: I have finally found a solution
I went to the Following site [htt]p://forum.legija.net/showthread.php/69405-Boot-repair-Samsung-galaxy-S4-%28i9505-and-similar%29-via-USB-Cable and Downloaded the Attached file
the Ive connected my phone in Download mode and then run the program from the above site.
the Ive Run odin And i Flashed the .pit file alone without the firmware, Doing it this way have fixed the boot issue and i had my 4.2.2 Firmware and S4 up and running.
Then Ive upgraded to 4.3 (I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF)
I've encountered a couple of issues and unstable boots and random restarts but ive managed to fix this by re partitioning PIT table and Flashing 4.3 firmware again. it seems Stable for the time being at least with no random crashes or reboots.

Dertheante said:
Please any ideas ? :/
EDIT: I have finally found a solution
I went to the Following site [htt]p://forum.legija.net/showthread.php/69405-Boot-repair-Samsung-galaxy-S4-%28i9505-and-similar%29-via-USB-Cable and Downloaded the Attached file
the Ive connected my phone in Download mode and then run the program from the above site.
the Ive Run odin And i Flashed the .pit file alone without the firmware, Doing it this way have fixed the boot issue and i had my 4.2.2 Firmware and S4 up and running.
Then Ive upgraded to 4.3 (I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF)
I've encountered a couple of issues and unstable boots and random restarts but ive managed to fix this by re partitioning PIT table and Flashing 4.3 firmware again. it seems Stable for the time being at least with no random crashes or reboots.
Click to expand...
Click to collapse
Can you explain in more detail as to how you use those files to resurrect your i9505? The thread's description does not explain how to use the files: (galaxy_S4_9505.exe, bootloader + pit.bl)
The bootloader file is not recognized by odin and there is no indicator as to what the galaxy_S4_9505.exe file actually does.
Thanks much

Verizon Galaxy Note 3 bricked?

I think I may have bricked my phone, possibly a softbrick? I was using Odin3 v3.09 with Root de la vega for my Verizon Galaxy Note 3, Model SM-N900V. The tutorial I was using said it was for my phone, I followed all the instructions, and I got fail the first time using the stock cord that came with it so I tried again and used a regular usb 2.0 cord and got a fail the second time.
This is the text from Odin.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Root_de_la_Vega.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> SingleDownload.
<ID:0/004> cache.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the text on my phone.
Code:
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
[COLOR="Gray"]KNOX Kernal Lock: 0x0
KNOW Warranty Void: 0x0
QualCOMM SecureBoot: Enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write Protection: Enable[/COLOR]
[COLOR="Red"]Secure Check Fail: cache[/COLOR]
I am assuming I am going to need to flash the phone back to a stock firmware but I am not sure which one I should be using, or how to go about doing that exactly as well. I have rooted/unrooted phones in the past. I have also flashed my old phones as well, but I don't remember how to nor can I seem to figure it out with this phone. If someone could point me in the right direction I would greatly appreciate the help. I am trying to put the HyperDrive ROM on my phone.

Update!
I came accross this method, http://forum.xda-developers.com/showthread.php?t=2483380
I followed the instructions on flashing to stock with Odin and I didn't have any luck in getting it to work. I downloaded the MI9 tar.md5 file, and the pit file selected them in there proper spots in the program and ran it. I got this error.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and this error on my phone
SW REV CHECK FAIL : (aboot)Fused 2 > Binary 1

This should be a easy fix. Enter recovery mode by powering down the phone then holding the home button, vol up and the power button. Hold down all three buttons until you see recovery booting on the top in blue. The phone will reboot into recovery and then scroll to wipe data/factory reset with the vol down key and then press the power button and wait until it completes the reset. Now you should be good to go again. This will wipe all data but you will have your phone back.

Misterxtc said:
This should be a easy fix. Enter recovery mode by powering down the phone then holding the home button, vol up and the power button. Hold down all three buttons until you see recovery booting on the top in blue. The phone will reboot into recovery and then scroll to wipe data/factory reset with the vol down key and then press the power button and wait until it completes the reset. Now you should be good to go again. This will wipe all data but you will have your phone back.
Click to expand...
Click to collapse
When I do that I get a screen that says,
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."

luckychalmz said:
When I do that I get a screen that says,
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Click to expand...
Click to collapse
You might need to flash MJE instead of MI9 with Odin.

Misterxtc said:
You might need to flash MJE instead of MI9 with Odin.
Click to expand...
Click to collapse
Do you know of anywhere that I can get that file, the link that is in the guide is saying its going to take like three days. It's only 1.3gbs so I don't see why.

luckychalmz said:
Do you know of anywhere that I can get that file, the link that is in the guide is saying its going to take like three days. It's only 1.3gbs so I don't see why.
Click to expand...
Click to collapse
Try this guide if you haven't already. I just tried and it said three hours not days. If it's slow try canceling and restarting it again. You might get a faster dl rate. http://forum.xda-developers.com/showthread.php?t=2528707

Misterxtc said:
Try this guide if you haven't already. I just tried and it said three hours not days. If it's slow try canceling and restarting it again. You might get a faster dl rate. http://forum.xda-developers.com/showthread.php?t=2528707
Click to expand...
Click to collapse
That one is definitely going faster. Thank you. I will try this one once it's finished.

luckychalmz said:
That one is definitely going faster. Thank you. I will try this one once it's finished.
Click to expand...
Click to collapse
No problem. Did you try to clear cache in recovery mode? If not give that a try and then the factory reset while you are waiting. You have nothing to loose at this point.

Misterxtc said:
No problem. Did you try to clear cache in recovery mode? If not give that a try and then the factory reset while you are waiting. You have nothing to loose at this point.
Click to expand...
Click to collapse
That fixed it, thank you. Appreciate your help.

luckychalmz said:
That fixed it, thank you. Appreciate your help.
Click to expand...
Click to collapse
Cool, I'm glad to help and direct you to the info that has been shared. Enjoy.

I know a much faster,simpler and less data-damaging wau
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!

technoshima said:
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
Click to expand...
Click to collapse
You my friend, are a genius!!! I was crapping my pants thinking it was over. Thanks a bunch. And yes, it is a much, much faster download than that MJE that took forever to download.
Kudos again, my friend.

Still having issue with Samsung Write Protection
fanatic4hockey said:
You my friend, are a genius!!! I was crapping my pants thinking it was over. Thanks a bunch. And yes, it is a much, much faster download than that MJE that took forever to download.
Kudos again, my friend.
Click to expand...
Click to collapse
technoshima said:
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
Click to expand...
Click to collapse
I was able to flash the PIT file with Odin like you said which enabled me to get back to recovery, but I am still having issues with the Samsung Write protection being enabled (which is preventing me from flashing anything with Safestrap including trying to fully wipe and restart). I found out after attempting to flash my verizon note 3 that the write protection was an option that needed to be unchecked on the phone before flashing. Now I can't change it without being able to login all the way into the phone. Are there any options out there to change the write feature outside of being able to actually load the phone, like ADB?

luckychalmz said:
That fixed it, thank you. Appreciate your help.
Click to expand...
Click to collapse
Hi guys
I need some help I rooted my Verizon Note 3 and is stock on:
Odin Mode Please see attached image
When I ran these files : ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit on odin3
I got this error.
Please advice.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

vampirelife said:
Hi guys
I need some help I rooted my Verizon Note 3 and is stock on:
Odin Mode Please see attached image
When I ran these files : ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit on odin3
I got this error.
Please advice.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Looks similar to what I was getting from Odin. Did you have to uncheck the write protection in your phone settings before flashing anything? Someone told me that might be the cause of what happened with mine since I didn't even hear about doing so until I had already attempted to flash my phone.

im also getting a fail just after aboot. I originally attempted to install the deodex version on kitkat and originally was still able to access safestrap.
I have tried flashing every rom i can get my hands on over odin. ive tried making a recovery from my other note 3 via safestrap and swapping the micro sd over to this one. did not show up when i went to ss recover. so i booted to recovery cleared cache. still got aboot failed(auth) so i booted to recovery again and cleared everything except data. (including system) now i cant access SS any longer. get stuck on bootload screen or get verizon sofware assistant message. still unable to flash roms via oden i have tried everything but lollipop and odin versions 3.9 3.7 3.10
im am completely lost. im almost ready to ship it to someone to fix it for me.

I'm gonna bump this in the hopes someone sees it and can help me.

luckychalmz said:
I think I may have bricked my phone, possibly a softbrick? I was using Odin3 v3.09 with Root de la vega for my Verizon Galaxy Note 3, Model SM-N900V. The tutorial I was using said it was for my phone, I followed all the instructions, and I got fail the first time using the stock cord that came with it so I tried again and used a regular usb 2.0 cord and got a fail the second time.
This is the text from Odin.
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Root_de_la_Vega.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
cache.img.ext4
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
This is the text on my phone.
Code:
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
[COLOR="Gray"]KNOX Kernal Lock: 0x0
KNOW Warranty Void: 0x0
QualCOMM SecureBoot: Enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write Protection: Enable[/COLOR]
[COLOR="Red"]Secure Check Fail: cache[/COLOR]
I am assuming I am going to need to flash the phone back to a stock firmware but I am not sure which one I should be using, or how to go about doing that exactly as well. I have rooted/unrooted phones in the past. I have also flashed my old phones as well, but I don't remember how to nor can I seem to figure it out with this phone. If someone could point me in the right direction I would greatly appreciate the help. I am trying to put the HyperDrive ROM on my phone.
Click to expand...
Click to collapse
Before you started this...what version of android were you using? You must flash the last version you had running or higher.
Get the firmware from here
http://www.sammobile.com/firmwares/database/SM-N900V/
instructions are also there
You can also try having Verizon reflash it or at the Samsung section of your local best buy
marcotheclepto said:
I'm gonna bump this in the hopes someone sees it and can help me.
Click to expand...
Click to collapse
Sent from my Note 3 via Tapatalk

donc113 said:
Before you started this...what version of android were you using? You must flash the last version you had running or higher.
Get the firmware from here
instructions are also there
You can also try having Verizon reflash it or at the Samsung section of your local best buy
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
thanks, im just jumping straight to 5.0 and hoping for the best. half hour left on the download. fingers crossed
*update* it seems the newer version was the answer for me... now to find a way to root it on lolipop... whole point was originally to get hyperdrive and get some headphone software worth using.

[Q] soft brick need help N900T

I realized I posted this on the wrong section I have just re-posted it in the tmobile galaxy note 3 section, I apologize for my mistake, Please delete thread as it is in the wrong section.
Hello, I am new here this is going to be my first post.
I installed CWM from rom manager a while ago on my rooted note 3 N900T it was on kitkat 4.4.2 then I tried rebooting into recovery mode and then it wouldn't go in it would keep restarting, then after I did a battery pull now I get: ( Firmware upgrade encountered an issue. Please select recovery mode in kids & try again)
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KEANEL LOCK: 0X0
KNOX WARRANTY VOID: 0XL
QUALCOMM SECUREBOOT: ENABLE (CSB) AP SWAREV: S2, T2, A2, A3, P2
WRITE PROTECTION: ENABLE
VDC START
So I tried connecting to kies it wouldn't detecting it would just say "connecting" I tried on my mac osX mavericks and also on VMWare windows 7.
I tried to download the stock firmware and flash it via odin to come back to stock and thought maybe that would fix it but it keeps giving me a error.
I have the usb drivers installed as it detects the device, I am sure I have downloaded the correct firmware for the phone.
this is the firmware I downloaded: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
I tried using odin 3.07 and 3.09 both and ran it as administrator.
I checked the "time reset" also the "auto reboot" as mentioned, I tried adding it in pa in 3.09 and pda in 3.07
This is the error I get while trying to flash the rom: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Unfortunately that is what I get from odin sometimes it goes further down and then stops but most of the times i get this, I've tried using the original 3.0 usb cable with different usb ports and also another normal micro usb cable, both gives me the same error, I have tried to use JODIN as well on my mac but my device doesn't detect on that therefore i used my VMware windows 7 32bit. I tried that while I had kids installed on my computer and then I read that kies doesn't go well with odin so I uninstalled kies and tried again but no difference.
Could someone please help me out, I have been trying to fix this for 2 days I am a college student and I work part time, so it is very frustrating not to have a phone to use for work and college.

malimt said:
Hello, I am new here this is going to be my first post.
I installed CWM from rom manager a while ago on my rooted note 3 N900T it was on kitkat 4.4.2 then I tried rebooting into recovery mode and then it wouldn't go in it would keep restarting, then after I did a battery pull now I get: ( Firmware upgrade encountered an issue. Please select recovery mode in kids & try again)
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KEANEL LOCK: 0X0
KNOX WARRANTY VOID: 0XL
QUALCOMM SECUREBOOT: ENABLE (CSB) AP SWAREV: S2, T2, A2, A3, P2
WRITE PROTECTION: ENABLE
VDC START
So I tried connecting to kies it wouldn't detecting it would just say "connecting" I tried on my mac osX mavericks and also on VMWare windows 7.
I tried to download the stock firmware and flash it via odin to come back to stock and thought maybe that would fix it but it keeps giving me a error.
I have the usb drivers installed as it detects the device, I am sure I have downloaded the correct firmware for the phone.
this is the firmware I downloaded: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
I tried using odin 3.07 and 3.09 both and ran it as administrator.
I checked the "time reset" also the "auto reboot" as mentioned, I tried adding it in pa in 3.09 and pda in 3.07
This is the error I get while trying to flash the rom: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Unfortunately that is what I get from odin sometimes it goes further down and then stops but most of the times i get this, I've tried using the original 3.0 usb cable with different usb ports and also another normal micro usb cable, both gives me the same error, I have tried to use JODIN as well on my mac but my device doesn't detect on that therefore i used my VMware windows 7 32bit. I tried that while I had kids installed on my computer and then I read that kies doesn't go well with odin so I uninstalled kies and tried again but no difference.
Could someone please help me out, I have been trying to fix this for 2 days I am a college student and I work part time, so it is very frustrating not to have a phone to use for work and college.
Click to expand...
Click to collapse
Known issue in vmware on Mac. Use parallels, bootcamp, or a real windows machine.
Sent from my leanKernel 3.0 powered stock 4.4.2 (NE6) SM-N900T

toastido said:
Known issue in vmware on Mac. Use parallels, bootcamp, or a real windows machine.
Sent from my leanKernel 3.0 powered stock 4.4.2 (NE6) SM-N900T
Click to expand...
Click to collapse
Thanks so much man, You were right, I un-installed VMWare and then installed parallels desktop 9 and then from then I flashed the stock rom using odin 3.07 and boom wallllla I'm back on my 4.4.2 stock rom. thanks thanks thanks

[Help] My Phone won't boot (Samsung Galaxy S4)

Hi guys, i been searching for long time to resolve my issue and nothing found i think you guys could help me.
The issue is
My phone was rooted - Samsung Galaxy S4 - GT-I9505
And then i unrooted, but nothing to do with this, it was all oK..
After that i tried to upgrade the firmware from sammobile something like that..
I downloaded the new firmware I9505XXUGNG8_I9505MAXGNG1_I9505XXUGNG8_HOME.tar for my phone
And in the end of the line using Odin i got FAILED red box.. And since that i can't boot my phone stuck at Odin Mode: Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again. And up with small text says: Odin Mode, PRODUCT NAME: GT-19505, CURRENT BINARY: costum, SYSTEM STATUS: costum, KNOX KERNEL LOCK: 0x0, KNOX WARRANTY VOID: 0x1, CS0-CONFIG-LS8: 0x30, WRITE PROTECTION: enable, eMMc BURST MODE: enable
i tried with Kies but i can't connect , because i think after i unrooted, i reset my phone so USB debugging is not checked. I think for that. So i'm trying to install new firmwares with Odin and is not working i always get fail message red box, i tried all versions.
Does anyone know what to do please.
i Appreciate it.
Thanks.

GoodMan14 said:
Hi guys, i been searching for long time to resolve my issue and nothing found i think you guys could help me.
The issue is
My phone was rooted - Samsung Galaxy S4 - GT-I9505
And then i unrooted, but nothing to do with this, it was all oK..
After that i tried to upgrade the firmware from sammobile something like that..
I downloaded the new firmware I9505XXUGNG8_I9505MAXGNG1_I9505XXUGNG8_HOME.tar for my phone
And in the end of the line using Odin i got FAILED red box.. And since that i can't boot my phone stuck at Odin Mode: Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again. And up with small text says: Odin Mode, PRODUCT NAME: GT-19505, CURRENT BINARY: costum, SYSTEM STATUS: costum, KNOX KERNEL LOCK: 0x0, KNOX WARRANTY VOID: 0x1, CS0-CONFIG-LS8: 0x30, WRITE PROTECTION: enable, eMMc BURST MODE: enable
i tried with Kies but i can't connect , because i think after i unrooted, i reset my phone so USB debugging is not checked. I think for that. So i'm trying to install new firmwares with Odin and is not working i always get fail message red box, i tried all versions.
Does anyone know what to do please.
i Appreciate it.
Thanks.
Click to expand...
Click to collapse
Hi mate ,
You have to flash an stock rom with odin , there is no other solution
Check this thread , i will give you in detail how to proceed
http://forum.xda-developers.com/showthread.php?t=2265477

MAX 404 said:
Hi mate ,
You have to flash an stock rom with odin , there is no other solution
Check this thread , i will give you in detail how to proceed
http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
That's what he's doing. It should be working.
It MIGHT be because you have non official firmware on it now and it's not accepting the flash back to stock. IF that's the case the solution is to uncheck auto reboot in Odin and run the install sequence twice in a row. That's worth a shot here, but I don't think it's the solution.
Do you still have a working custom recovery? If so you should still be able to flash a custom ROM. I might try flashing a custom TouchWiz rom then starting over.

Still fail !
ty for reply guys, ok i captured everything
this is image when i browse the file on AP / PDA odin freezed for few seconds...
And this is what i got:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNG8_I9505MBMGNG1_I9505XXUGNG8_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!

GoodMan14 said:
ty for reply guys, ok i captured everything
this is image when i browse the file on AP / PDA odin freezed for few seconds...
And this is what i got:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNG8_I9505MBMGNG1_I9505XXUGNG8_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
Hi ,
This is from the post i gave you earlier
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Check and see if it helps , did you try what Skipjacks said?

i di all
Hi, in this morning i tried again and passed.. finally
Thanks for helping.

GoodMan14 said:
Hi, in this morning i tried again and passed.. finally
Thanks for helping.
Click to expand...
Click to collapse
Great news mate
Sent from my Nexus 7 using XDA Premium 4 mobile app

Try flash stock firmware using odin

[Q] Need help recovering a bricked SM-900W8

This morning I updated my Note 3 (SM-900W8 on the Canadian Rogers network) to 5.0.
I had rooted this device before then, and had used Titanium Backup to backup all my apps/data. When the initial OTA update failed, someone pointed out that it was because the phone was rooted. So, figuring I had this backup in hand, I factory-reset my phone and went through the update - though I used the Samsung KIES app as it was quicker to download the firmware update than over my phone's WiFi.
Once the phone was on 5.0, I went to restore the backup... and found that Titanium Backup only works when the phone is rooted. Oops.
So, I figure that I need to root my phone again. I find instructions on how to root a note 3 and start to work through it. I go to the link for "Download appropriate CWM or TWRP recovery for your Note 3" and find the one that says "KitKat/Lollipop Android 4.4.2 CWM Recovery" and pick the one "SM-N900W8 Canadian Note 3 – CWM Recovery", because 5.0 is 'Lollipop' and my phone is the SM-N900W8. I attempt to use this with Odin, and Odin reports 'FAIL!' and the phone is stuck on "Downloading - Do not turn off target !!'. I give this a while just in case things take a while to happen... and nothing does, so I figure it did fail. I have no alternative but to turn off the phone now.
And restarting it, the phone comes up in "ODIN MODE" with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The messages at the top of my phone on this screen are:
Code:
ODIN MODE
PRODUCT NAME: SM-900W8
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
SECURE DOWNLOAD : ENABLE
UDC START
I connect the phone up again, select the Recovery tool in Kies... and the phone is not detected. No matter what I try.
So then I try and download the official firmware N900W8_RWC_N900W8VLU2DOC4_N900W8OYADOC4 from Samsung Updates and try to use Odin to recovery it that way.
Again, the update fails... time and time again.
The Odin messages output is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900W8VLU2DOC4_N900W8OYADOC4_N900W8VLU2DOC4_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I now have a bricked phone, and no idea how to fix it.
What can I do?

frysco said:
What can I do?
Click to expand...
Click to collapse
1. Reflash STOCK firmware 5.0 for your device: HERE. Factory reset your device when finish of boot.
2. Use TWRP (You can flash this ONE via ODIN) and root your device then.
3. Don't restore your data of android 4.4.2.

I've managed to fix things.
From other searching around, it seems that trying to use Odin via VMWare Fusion on a Mac is a 'known issue' where it gets stuck at this point.
Installed a trial version of Parallels and a basic Win XP install, re-flashed and it WORKED!