Database Users

[Q] Have I bricked this phone :( ?

ODIN MODE
Product Name GT-I9505
CURRENT BINARY:
SYSTEM STATUS:
KNOX KERNEL LOCK: 0XFFFFFFFFFC
KNOW WARRANTY VOID: 0XFFFFFFFFC
CSB_CONFIG_LSB: 0X30
Write protection: Enabled
eMMC Burst: Enabled
Set Warranty bit: cACHED
Set Warranty bit: Hidden!
Firmware update encountered an issues, Please select recover mode in kies and try again.
Above is what my phone is currently showing me, Odin seems to flash philz/twrp however I can't boot into recovery.
I can still get into download mode tho
So I thought sod my root and everything, I just really need a phone and alarm clock so I downloaded the latest firmware for this phone (I9505XXUEMJ7) and attempted to flash as PDA in odin and got the follwoing response:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505BTUEMJ8 _I9505XXUEMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have also tried the original firmware that came with the phone (XXUMBGA 4.2 UK Not locked) and many others, Still getting nothing, Just seems odin won't let me flash anything.
When philz or clockwork did run a few days ago, I could not install any zip files, It just kept giving me an error saying it can't mount /cahce or /system and the file is bad, despite me checking the MD5's and re downloading server times!
Can anyone make any suggestions? Or do I just have a new paper weight?
Thanks guys!

Nevermind, Got it back to factory setting using KIES
I highly recommend it but remember it will KNOX the device
Peace

philipkroberts said:
Nevermind, Got it back to factory setting using KIES
I highly recommend it but remember it will KNOX the device
Peace
Click to expand...
Click to collapse
What does Knox mean? I am having the same issues where odin just hangs on boot.img, my last resort will be using kies.
Can I not flash any roms after I restore using kies??

gunner05 said:
What does Knox mean? I am having the same issues where odin just hangs on boot.img, my last resort will be using kies.
Can I not flash any roms after I restore using kies??
Click to expand...
Click to collapse
If you use KIES to upgrade your phone you will get the latest firmware which contains the knox bootloader: http://forum.xda-developers.com/showthread.php?t=2447832
In that thread it says what knox is and what it means for us. But yeah, you can still flash ROMs, but you will trigger the knox warranty void flag (info is in the thread).

Can you tell me what you have done to fix it with Kies, please?
I tried to root my i9505 today and it stopped after 3 seconds when I used Odin to flash CF-Auto-Root.
And now since 7 hours I can't fix it. Kies won't recognize my smartphone and Odin always response with "Fail!".
I'm really desperate that I bricked my phone. :crying:

TStorm16 said:
Can you tell me what you have done to fix it with Kies, please?
I tried to root my i9505 today and it stopped after 3 seconds when I used Odin to flash CF-Auto-Root.
And now since 7 hours I can't fix it. Kies won't recognize my smartphone and Odin always response with "Fail!".
I'm really desperate that I bricked my phone. :crying:
Click to expand...
Click to collapse
That's almost impossible with CF-root or you yourself messed up real bad.
Try a different usb port, different cable, make sure Kies is not running, reinstall drivers.

Lennyz1988 said:
That's almost impossible with CF-root or you yourself messed up real bad.
Try a different usb port, different cable, make sure Kies is not running, reinstall drivers.
Click to expand...
Click to collapse
OMG!
I just fixed it. I flashed this PIT-File "CSB_signed_Fusion3_EUR_0325_V2.pit" and after that my smartphone rebooted normally.
Then when I was back I turned "USB-Debugging" on and went back to recovery mode and tried it again.
And now it works.:good:

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] N9005 bricked? please help me, i'm not that experienced

I'm in Philippines right now in vacation and I bought from here a brand new Samsung N9005 32G (Orange France) with 4.3 software version, and i guess the store that sold me the phone unlocked it to work on any network, because the box was opened.
The second day i received it i saw that is rooted, but i didn't saw SuperSu application (the application that i always knew you should have if you were rooted), and i decided to install it, but by installing SuperSu, this action unrooted my phone. The next thing i did is to search on web how to root it back, but i couldn't root it back, that rooting process didn't work.
Then i decided to install BoBCaTROM_EVO_v4.1, to have a newer software version and to root it back eventually, and this bricked (or soft bricked) my phone.
After i bricked my phone by trying to install BoBCaTROM_EVO_v4.1, i tryed to install at least 5 different roms through Odin (1.7, 3.07, 3.09).
no meter what room i try to install throught odin i get this error after few seconds: SW REG CHECK FAIL : [aboot]Fused 3 > Binary 2
If i need to give you more information about my problem, so that you guys can help me, please tell me.
I don't know many thing about android, i just had in the past some android phones with 2.0, 3.0 firmware and a couple of Chinese tablets but i didn't encountered any problems when i rooted them or changing their software. please help me like it's my first day on android, i would kindly appreciate.
Please, please, i hope someone can help me to get it working again.
--------------------------------------------------------------------------------------------
if i power on my phone i can see this:
--------------------------------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P1
WRITE PROTECTION: Enable
UDC START
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
----------------------------------
odin log:
-----------------------------------
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDML3_N9005FTMDML4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> SingleDownload.
<ID:0/016> sbl1.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016> aboot.mbn
<ID:0/016> FAIL! (Auth)
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

fashion22 said:
I'm in Philippines right now in vacation and I bought from here a brand new Samsung N9005 32G (Orange France) with 4.3 software version, and i guess the store that sold me the phone unlocked it to work on any network, because the box was opened.
The second day i received it i saw that is rooted, but i didn't saw SuperSu application (the application that i always knew you should have if you were rooted), and i decided to install it, but by installing SuperSu, this action unrooted my phone. The next thing i did is to search on web how to root it back, but i couldn't root it back, that rooting process didn't work.
Then i decided to install BoBCaTROM_EVO_v4.1, to have a newer software version and to root it back eventually, and this bricked (or soft bricked) my phone.
After i bricked my phone by trying to install BoBCaTROM_EVO_v4.1, i tryed to install at least 5 different roms through Odin (1.7, 3.07, 3.09).
no meter what room i try to install throught odin i get this error after few seconds: SW REG CHECK FAIL : [aboot]Fused 3 > Binary 2
If i need to give you more information about my problem, so that you guys can help me, please tell me.
I don't know many thing about android, i just had in the past some android phones with 2.0, 3.0 firmware and a couple of Chinese tablets but i didn't encountered any problems when i rooted them or changing their software. please help me like it's my first day on android, i would kindly appreciate.
Please, please, i hope someone can help me to get it working again.
--------------------------------------------------------------------------------------------
if i power on my phone i can see this:
--------------------------------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P1
WRITE PROTECTION: Enable
UDC START
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
----------------------------------
odin log:
-----------------------------------
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDML3_N9005FTMDML4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> SingleDownload.
<ID:0/016> sbl1.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016> aboot.mbn
<ID:0/016> FAIL! (Auth)
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It's failing on Boot loader, it would seem the shop have put Kitkat on it or you've tried to flash a Kitkat based ROM, go ahead and flash a Kitkat Stock ROM and it should be OK - sammobile.com grab XEO (Poland)

fashion22 said:
I'm in Philippines right now in vacation and I bought from here a brand new Samsung N9005 32G (Orange France) with 4.3 software version, and i guess the store that sold me the phone unlocked it to work on any network, because the box was opened.
The second day i received it i saw that is rooted, but i didn't saw SuperSu application (the application that i always knew you should have if you were rooted), and i decided to install it, but by installing SuperSu, this action unrooted my phone. The next thing i did is to search on web how to root it back, but i couldn't root it back, that rooting process didn't work.
Then i decided to install BoBCaTROM_EVO_v4.1, to have a newer software version and to root it back eventually, and this bricked (or soft bricked) my phone.
After i bricked my phone by trying to install BoBCaTROM_EVO_v4.1, i tryed to install at least 5 different roms through Odin (1.7, 3.07, 3.09).
no meter what room i try to install throught odin i get this error after few seconds: SW REG CHECK FAIL : [aboot]Fused 3 > Binary 2
If i need to give you more information about my problem, so that you guys can help me, please tell me.
I don't know many thing about android, i just had in the past some android phones with 2.0, 3.0 firmware and a couple of Chinese tablets but i didn't encountered any problems when i rooted them or changing their software. please help me like it's my first day on android, i would kindly appreciate.
Please, please, i hope someone can help me to get it working again.
--------------------------------------------------------------------------------------------
if i power on my phone i can see this:
--------------------------------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P1
WRITE PROTECTION: Enable
UDC START
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
----------------------------------
odin log:
-----------------------------------
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDML3_N9005FTMDML4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> SingleDownload.
<ID:0/016> sbl1.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016> aboot.mbn
<ID:0/016> FAIL! (Auth)
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Flash 4.4.2 through Odin

Bricked
I have the same problem but I didn't have any root on it, it is an original France XEF phone and first i tried to flash a stock Hungary (T-mobile) 4.4.2 firmware from sammobile. (I'm from hungary). First it failed later i tried to flash the Original France XEF 4.3 but it failed too. Now I can't flash anything on it, and KIES doesen't recognize my phone. I used Odin3 v3.09.
At boot says the binary offical, system offical, reactivation lock off, knox 0x0, knox warranty 0x0, qualcomm secure boot enabled, write protection enabled.
When falshing i got the same problem : SW REG CHECK FAIL : [aboot]Fused 3 > Binary 2
Please help!
Thanks!

sortilego said:
I have the same problem but I didn't have any root on it, it is an original France XEF phone and first i tried to flash a stock Hungary (T-mobile) 4.4.2 firmware from sammobile. (I'm from hungary). First it failed later i tried to flash the Original France XEF 4.3 but it failed too. Now I can't flash anything on it, and KIES doesen't recognize my phone. I used Odin3 v3.09.
At boot says the binary offical, system offical, reactivation lock off, knox 0x0, knox warranty 0x0, qualcomm secure boot enabled, write protection enabled.
When falshing i got the same problem : SW REG CHECK FAIL : [aboot]Fused 3 > Binary 2
Please help!
Thanks!
Click to expand...
Click to collapse
The hungary one is a carrier branded fw, it wont work for you
Take the na6 phn from sammobile, will work
Sent from my SM-N9005 using XDA Premium 4 mobile app

Killberty said:
The hungary one is a carrier branded fw, it wont work for you
Take the na6 phn from sammobile, will work
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
But I tried the Original unbranded 4.3 france firmware. Now I'm downloading an unbranded Hunagrian.
Which is the na6 phn?
Thanks

Dutch (=netherlands)
Runs fine on my phone
sortilego said:
But I tried the Original unbranded 4.3 france firmware. Now I'm downloading an unbranded Hunagrian.
Which is the na6 phn?
Thanks
Click to expand...
Click to collapse
Sent from my SM-N9005 using XDA Premium 4 mobile app

@adilrenzu
@radicalisto
 @Killberty
I guess my phone is also branded, on the box everything is writen in francais, and all the manuals are the same, and on the outside sticker from the box where it's also the imei i can see written "Orange France"... Should i still go for flashing the poland xeo kitkat firmware? Or should i choose something else like orange france kitkat firmware (if it was released) ? I didnt tried yet the poland firmware because i have some electricity problems, and i cant use my laptop yet. Thank you.

Still go for unbranded.
My phone came tmo germany branded(dtm) i unbranded (bdt) and later on flasged kitkat (phn) without probs
Sent from my SM-N9005 using XDA Premium 4 mobile app

Killberty said:
Still go for unbranded.
My phone came tmo germany branded(dtm) i unbranded (bdt) and later on flasged kitkat (phn) without probs
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The unbranded firmware Is the one from sammobile = XDA Poland? I dont want to make any mistakes. Thank you.

fashion22 said:
The unbranded firmware Is the one from sammobile = XDA Poland? I dont want to make any mistakes. Thank you.
Click to expand...
Click to collapse
Go for the na6 dutch/netherlands firmware with phn as csc, runs fine on my phone
Sent from my SM-N9005 using XDA Premium 4 mobile app

fashion22 said:
The unbranded firmware Is the one from sammobile = XDA Poland? I dont want to make any mistakes. Thank you.
Click to expand...
Click to collapse
yes thats the one.

Killberty said:
Still go for unbranded.
My phone came tmo germany branded(dtm) i unbranded (bdt) and later on flasged kitkat (phn) without probs
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I managed to work it with unbranded hungarian, it changed evrything like csd pda erc. Is my warranty now void?

sortilego said:
I managed to work it with unbranded hungarian, it changed evrything like csd pda erc. Is my warranty now void?
Click to expand...
Click to collapse
Congrats!
Boot into download mode and tell me whatcha see
____
Oh well i saw your knox was 0x1 before. ..
So if you are an eu citizen, give fack about it, if not, your warranty is voided maybe, pedends on your carrier/samsung service centre
____
If you need warranty, just say u did kies emeegency recovery once and saw the "set warranty bit" thing, and that you didnt know what it was
(Play dumb)
You shd get your warranty anyway
Sent from my SM-N9005 using XDA Premium 4 mobile app

Killberty said:
Congrats!
Boot into download mode and tell me whatcha see
____
Oh well i saw your knox was 0x1 before. ..
So if you are an eu citizen, give fack about it, if not, your warranty is voided maybe, pedends on your carrier/samsung service centre
____
If you need warranty, just say u did kies emeegency recovery once and saw the "set warranty bit" thing, and that you didnt know what it was
(Play dumb)
You shd get your warranty anyway
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As is saw nothing changed here. And i have now 4.4.2... but now my signal is at minimum, and I can't connect to mobile internet :/
Mobile internet solved, set the deafults from telekom. But the sifnal still bad :/

sortilego said:
As is saw nothing changed here. And i have now 4.4.2... but now my signal is at minimum, and I can't connect to mobile internet :/
Mobile internet solved, set the deafults from telekom. But the sifnal still bad :/
Click to expand...
Click to collapse
Knox 0x0 -> warranty intact
___
For bad Signal
- do a factory reset
- flash modem.bin and non-hlos.bin from the na6 firmware from your country
Sent from my SM-N9005 using XDA Premium 4 mobile app

@adilrenzu
@radicalisto
@Killberty
Thanks for your help but my note 3 is still "dead"
i used Odin3 v3.09 to flash N9005XXUENA6_N9005OXXENA5_XEO and it failed after 5 seconds.
------------------------------------
Error on phone screen:
------------------------------------
ODIN : Invalid ext4 image
-------------------------
Odin log:
----------------------
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> SingleDownload.
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017> sbl1.mbn
<ID:0/017> rpm.mbn
<ID:0/017> tz.mbn
<ID:0/017> sdi.mbn
<ID:0/017> NON-HLOS.bin
<ID:0/017> boot.img
<ID:0/017> recovery.img
<ID:0/017> system.img.ext4
<ID:0/017> FAIL! (Ext4)
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anything else I can do to fix it?

fashion22 said:
@adilrenzu
@radicalisto
@Killberty
Thanks for your help but my note 3 is still "dead"
i used Odin3 v3.09 to flash N9005XXUENA6_N9005OXXENA5_XEO and it failed after 5 seconds.
------------------------------------
Error on phone screen:
------------------------------------
ODIN : Invalid ext4 image
-------------------------
Odin log:
----------------------
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> SingleDownload.
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017> sbl1.mbn
<ID:0/017> rpm.mbn
<ID:0/017> tz.mbn
<ID:0/017> sdi.mbn
<ID:0/017> NON-HLOS.bin
<ID:0/017> boot.img
<ID:0/017> recovery.img
<ID:0/017> system.img.ext4
<ID:0/017> FAIL! (Ext4)
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
For the 'invalid ext4 image' error, try checking out the second link in my signature.

FeralFire said:
For the 'invalid ext4 image' error, try checking out the second link in my signature.
Click to expand...
Click to collapse
I will try your way, as soon as the torrent file finishes downloading. Thank you for your prompt answer!

fashion22 said:
I will try your way, as soon as the torrent file finishes downloading. Thank you for your prompt answer!
Click to expand...
Click to collapse
Best of luck.

[Q] Bricked N9007?

Ok, so today I tried to root my Note 3 N9007 via Odin 3.07 and autoroot files from chainfire. BUT, it seems like it doesnt worked... I did everything what was said in the tutorial here in the forum but no luck... Now I am stuck in Odin mode:
Current binary: Custom
System status: Official
Reactivation lock: OFF
Knox kernel lock: 0x0
Knox varanty: 0x0
Qualcomm secureboot: Enable
Write protection: Enable
Now log the from odin:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-htdlte-htdltedi-smn9007.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks........

mkotruch said:
Ok, so today I tried to root my Note 3 N9007 via Odin 3.07 and autoroot files from chainfire. BUT, it seems like it doesnt worked... I did everything what was said in the tutorial here in the forum but no luck... Now I am stuck in Odin mode:
Current binary: Custom
System status: Official
Reactivation lock: OFF
Knox kernel lock: 0x0
Knox varanty: 0x0
Qualcomm secureboot: Enable
Write protection: Enable
Now log the from odin:
Removed!!
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CF-Auto-Root-htdlte-htdltedi-smn9007.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..
recovery.img
NAND Write Start!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Thanks........
Click to expand...
Click to collapse
You tried root made for N9007 ??? Maybe a curropt dowload .try flashing again.
Btw to get back your device to work flash your official firmware through odin.
Sent from my SM-N9005 using Tapatalk

yep, it was a direct download from chainfire... IDK, hope the reflash will work... I am going to hang myself if it wont.

There are different files for 4.3 and 4.4

but not for 9007 bcs there is just Jelly Bean, no KitKat yet...
ok update, I am stuck with writing error... tried to flash official JB but still got the same error... anyone could help?

Used Odin 1.85? And right instructions.
Wipe cache and data reset

mkotruch said:
yep, it was a direct download from chainfire... IDK, hope the reflash will work... I am going to hang myself if it wont.
Click to expand...
Click to collapse
I'm guessing you have the Australian Optus device. If so I have the same one and successfully rooted mine (SM-N9007) last night without a problem! (Been running root apps ie. Titanium Backup and xposed framework)
I jumped on 'AndroidXDA.com' and downloaded CF-Auto-Root File from their guide. If your phone is bricked then download official firmware for SM-N9007 from sammobile and install using ODIN 3.09. Hopefully you'll be able to get it working.

Thanks, I managed to reinstall the stock rom and root it - the problem was with the usb connection, my pc has got problems with usb ports from time to time. So I switched to another pc and got it working

Need a TWRP Recovery MD5/WIN.000

Hello, everyone!
I recently have run into some trouble with my (ATT) Galaxy S4 (SGH-I337). I flashed a custom rom and (idiotically) didn't make a backup. Long story short, things didn't quite work out with the new rom. I didn't like it, and I wanted to go back to the old stock firmware. So I decided I would try to do it. I tried flashing with odin, using recovery, etc. Nothing worked so far. I've been researching for about 12 hours now. I think I know what I need. I need a TWRP backup, so that I can move it to the sd, and trick twrp into thinking I backed up my system so I can restore it. Below, I will link a post to what I want. The reason I can't use the below is because it's for a different carrier. If someone would be kind enough to link me something, that would be great. Again, my phone is a ATT Galaxy S4 (SGH-I337). Please help me out!
http://forum.xda-developers.com/showthread.php?t=2506562

Before I help you I want to be absolutely sure.
Are you sure you have an i9505? Because you keep saying ATT. That's a completely different phone. That's the SGH-I337. You can't flash stuff for the i9505 on the SGH-I337.
So what model do you have? Do you have an i9505 or the SGH-I337. My guess would be that you have the SGH-I337.
ps I have no idea what the thread is what you posted. Don't use that thread because its outdated.

Lennyz1988 said:
Before I help you I want to be absolutely sure.
Are you sure you have an i9505? Because you keep saying ATT. That's a completely different phone. That's the SGH-I337. You can't flash stuff for the i9505 on the SGH-I337.
So what model do you have? Do you have an i9505 or the SGH-I337. My guess would be that you have the SGH-I337.
ps I have no idea what the thread is what you posted. Don't use that thread because its outdated.
Click to expand...
Click to collapse
Yes, then I have an SGH-I337.

Lennyz1988 said:
Before I help you I want to be absolutely sure.
Are you sure you have an i9505? Because you keep saying ATT. That's a completely different phone. That's the SGH-I337. You can't flash stuff for the i9505 on the SGH-I337.
So what model do you have? Do you have an i9505 or the SGH-I337. My guess would be that you have the SGH-I337.
ps I have no idea what the thread is what you posted. Don't use that thread because its outdated.
Click to expand...
Click to collapse
Since I did in fact flash the wrong ROM, could I just reflash a new ROM that's compatible with my phone?

dillondonnelly1 said:
Since I did in fact flash the wrong ROM, could I just reflash a new ROM that's compatible with my phone?
Click to expand...
Click to collapse
Yes. You can flash a stock rom for your device.

Lennyz1988 said:
Yes. You can flash a stock rom for your device.
Click to expand...
Click to collapse
Alright, but for some reason I get an error in Odin. It says "SECURE CHECK FAIL". Do you have any idea what might cause this?

dillondonnelly1 said:
Alright, but for some reason I get an error in Odin. It says "SECURE CHECK FAIL". Do you have any idea what might cause this?
Click to expand...
Click to collapse
You need to give way more details.
- Post the complete log here.
- What are you trying to flash?
- What is your bootloader?

Lennyz1988 said:
You need to give way more details.
- Post the complete log here.
- What are you trying to flash?
- What is your bootloader?
Click to expand...
Click to collapse
- Post the complete log here.
Odin Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response from boot-loader
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone Log:
Product Name: SGH-I337
CURRENT BINARY: Samsung Official
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
Write PROTECTION: Enable
eMMC BURST MODE enabled
START [224,1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1
- What are you trying to flash? I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 (Stock ROM)
-What is your bootloader? (Safestrap)
Also, the firmware came with a SS_DL.dll file. Do I do anything with this file?

Odin won't flash?
Here are the logs. I'm trying to flash the stock firmware with odin, because currently, there is no rom on my device. I have an ATT SGH-I337. Please help.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response from boot-loader
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone Log:
Product Name: SGH-I337
CURRENT BINARY: Samsung Official
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
Write PROTECTION: Enable
eMMC BURST MODE enabled
START [224,1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1

Its probably because you are flashing an old firmware on your new bootloader. What version where you previously on? 4.4.2? Then you can't flash a 4.2.2 rom.
ps stop opening new threads for this. You already got this thread.

Lennyz1988 said:
Its probably because you are flashing an old firmware on your new bootloader. What version where you previously on? 4.4.2? Then you can't flash a 4.2.2 rom.
ps stop opening new threads for this. You already got this thread.
Click to expand...
Click to collapse
Please tell me exactly what to do. I have to get my phone fixed by tonight.

dillondonnelly1 said:
Here are the logs. I'm trying to flash the stock firmware with odin, because currently, there is no rom on my device. I have an ATT SGH-I337. Please help.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response from boot-loader
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Phone Log:
Product Name: SGH-I337
CURRENT BINARY: Samsung Official
KNOX KERNAL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
Write PROTECTION: Enable
eMMC BURST MODE enabled
START [224,1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1
Click to expand...
Click to collapse
Hi mate ,
check if
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
Thanks to @samersh72
what software a re you flashing ? if you try to flash an older bootloader Odin will not allowed