Database Users

[Q] stock rom flash fail

Hello,
-sorry for my english I dont speak well but...
phone: I9505
I was testing cyanogemod 10.1.3 for a while but then I decided get back to stock rom, did full wipe and put this ROM I9505XXUBMF8 into Odin and start flashing but he said this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-then I couldnt go to system, recovery just to download mode so I flashed TWRP.
(I tried another stock rom, odin, PC but always same problem.)
-then i tried get back CM 10.1.3 via TWRP and it flashed and work without problem.
-then I tried flash omega rom via TWRP and it flashed without problem but booting is very slow and during the logo Samsung it takes about 10mins to boot into system and device is very hot.
-Everything about Kies and antivirus is off.
-Using just original USB cable.
-what says download mode:
ODIN MODE
PRODUCT NAME: gt-i9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLED
START [224, 1440]
SW REV, CHECK FAIL : FUSED : 2 , BINARY : 1
Any ideas how to resolve this?
Thank you

you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue

samersh72 said:
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
Click to expand...
Click to collapse
Thank you so much, I was looking for something all day but i didnt sure what Im really looking for

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.

Note 3 SM-N9005 Firmware Issue & Device Recognised As 'Samsung GT-S5690'

Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> aboot.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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> aboot.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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
hello. have you tried another version of odin? im sure someone can help you revive your phone

Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..

hypnodaz said:
Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..
Click to expand...
Click to collapse
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?

Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
Have you tried using Odin V3.09 to flash 4.4?

hey_joe said:
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
Click to expand...
Click to collapse
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?

Mamba25 said:
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?
Click to expand...
Click to collapse
Don't follow that one.
Go here and download the right file for your phone's model, put phone in download mode and flash using odin in ap/pda slot.
Btw, have you tried flashing 4.4 using odin v3.09?

When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..

hypnodaz said:
When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..
Click to expand...
Click to collapse
I don't think this is the case because when I first tried flashing from 4.3 to 4.4.2 it tried for a few seconds then failed and been stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“ despite resetting Odin and going back into download mode, tried reflashing but keep getting the 'FAIL' (logs posted in original first post).
Is there any reason why my phone is being detected as 'Samsung GT-S5690' in MobileGo? I'm thinking if Kies could detect it as the Note 3 again my problems would be solved.
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone

Mamba25 said:
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone
Click to expand...
Click to collapse
No it's not.

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> aboot.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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
looks like u r trying to flash 4.3 & 4.4 one after one, now dont try 4.3 at all, make sure kies is not running in baground, disable antivirus if any.

I had the the same issue with kies myself, tried every trick in the book before I tried the method I mention above.. maybe it's an issue with the phone itself, or a certain batch of phones?

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
...
Click to expand...
Click to collapse
The writing of stock 4.3 fails since your bootloader was updated by your failed attempt. You will probably never be able to write a 4.3 stock image.
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).

xclub_101 said:
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).
Click to expand...
Click to collapse
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks

Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
There is AP in 3.09 in place of PDA.

Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.

xclub_101 said:
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.
Click to expand...
Click to collapse
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.

madsus said:
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.
Click to expand...
Click to collapse
I've taken the phone to a repair shop recommended by Samsung themselves, they've had it a week now and I rang yesterday and they said it is the first Hong Kong Note 3 they've received and are waiting to hear from Samsung as to how to repair it. BIG YAWN!
Will keep you posted - miss my phone

Note 3 SM-N9005 firmware upgarade issue
Hi , i am having the same problem in my Note 3 i upgraded phronesis rom and after the phone was not detected in computer. so tried to flash custom kitkat rom again then it got disconnected and then showing error as firmware upgrade issue,
tried to download firmware and update by Odin, tired cmw recovery and tried many firmwares, Odin shows Failure and Kies dosent shown code or phone in emergency recovery , all ways failed, is it possible to make the phone work normal.

[Q] Soft brick on Samsung S4 but cant write stock rom?

Hey guys,
I had succesfully rooted my device. a few weeks ago. because i wanted cyanogenmod rom on it i tried to flash CWM recovery menu.
now my device gives the following message:
firmware upgrade encountered an issue. please select recovery mode in kies and try again.
Now i tried to reflash the stock rom with odin.
i downloaded the stock rom for my area (i guess)
i also downloaded a europe .pit file (someone said that on a tutorial how to remove soft brick)
Tried flashing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNA1_I9505OXAFNA1_I9505XXUFNA1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have an dutch galaxy s4. i have the provider T-mobile but the phone is not provider specified.
how can i fix this problem?
after trying with odin my downloading mode show's the following.
Odin mode
product name: GT-I9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection: enable
emmc burst mode: enabled
start (224, 1440)
sw. rev. check fail : fused : 4 , binary : 3
what can i do to get my phone to start up normally, now i keep getting the firmware fault message.
Thanks in advance.
Edit: i cant open recovery mode. but i can open download mode.

VeryStealth said:
Hey guys,
I had succesfully rooted my device. a few weeks ago. because i wanted cyanogenmod rom on it i tried to flash CWM recovery menu.
now my device gives the following message:
firmware upgrade encountered an issue. please select recovery mode in kies and try again.
Now i tried to reflash the stock rom with odin.
i downloaded the stock rom for my area (i guess)
i also downloaded a europe .pit file (someone said that on a tutorial how to remove soft brick)
Tried flashing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNA1_I9505OXAFNA1_I9505XXUFNA1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have an dutch galaxy s4. i have the provider T-mobile but the phone is not provider specified.
how can i fix this problem?
after trying with odin my downloading mode show's the following.
Odin mode
product name: GT-I9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection: enable
emmc burst mode: enabled
start (224, 1440)
sw. rev. check fail : fused : 4 , binary : 3
what can i do to get my phone to start up normally, now i keep getting the firmware fault message.
Thanks in advance.
Edit: i cant open recovery mode. but i can open download mode.
Click to expand...
Click to collapse
Try flashing a custom recovery through odin if u succeed u may have access to recovery nd if it doesnt work try flashing firmware without using pit file nd unchecking repartition option
Sent from my GT-I9500 using Tapatalk
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Which version is this which u r trying to flash via odin 4.3 or 4.4 2
Sent from my GT-I9500 using Tapatalk

aayushkhajuria2842 said:
Try flashing a custom recovery through odin if u succeed u may have access to recovery nd if it doesnt work try flashing firmware without using pit file nd unchecking repartition option
Sent from my GT-I9500 using Tapatalk
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Which version is this which u r trying to flash via odin 4.3 or 4.4 2
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I thought it were a test version of 4.4.2 kitkat
though i now downloaded a netherlands version from this tread no idea wich version.
http://forum.xda-developers.com/showthread.php?t=2265477
and then the second one. also downloaded the .pit here. im gonna try it now.. youll hear in a few minutes

VeryStealth said:
I thought it were a test version of 4.4.2 kitkat
though i now downloaded a netherlands version from this tread no idea wich version.
http://forum.xda-developers.com/showthread.php?t=2265477
and then the second one. also downloaded the .pit here. im gonna try it now.. youll hear in a few minutes
Click to expand...
Click to collapse
I just want u 2 confirm it is 4.4.2 as u were trying to install cyanogenmod
Sent from my GT-I9500 using Tapatalk

aayushkhajuria2842 said:
I just want u 2 confirm it is 4.4.2 as u were trying to install cyanogenmod
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
leaked official version of 4.4.2
Why did i overlook that cyanogenmod recovery isnt compatible with 4.4.2 yet?

VeryStealth said:
leaked official version of 4.4.2
Why did i overlook that cyanogenmod recovery isnt compatible with 4.4.2 yet?
Click to expand...
Click to collapse
U can flash It if it is 4.4.2 ....nd I dont get your last line ???
Sent from my GT-I9500 using Tapatalk

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505PHNEMK5_I9505XXUEMKF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
following happend with the downloaded version of stock rom.
now trying with .pit file
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
so i guess its not the pitt file?
is anything damaged? or do i have a faulty rom combo?

so your saying basicly that i should just try to reflash cyanogenmod? do you have a link to the version i can use. just to make sure i use the right one and don't screw it up more..
thanks for your help already btw.
I downloaded the newest CM i can find? CM 11-20140327? also i have the newest gapps i can find.. though its 20130813.
but how do i flash the recovery menu?
NVM i gave you a lot of false information< i had the firmware fault while installing clockworkmod recovery menu< not cyanogen< both with C im sorry.. i needed a recovery menu to install cyanogen. thats why i had problems.. i tried flashing to get the recovery menu and that failed. that gave the issues.. not cyanogen
Need to go puppy training with my dog< back in an hour or so

VeryStealth said:
so your saying basicly that i should just try to reflash cyanogenmod? do you have a link to the version i can use. just to make sure i use the right one and don't screw it up more..
thanks for your help already btw.
I downloaded the newest CM i can find? CM 11-20140327? also i have the newest gapps i can find.. though its 20130813.
but how do i flash the recovery menu?
NVM i gave you a lot of false information< i had the firmware fault while installing clockworkmod recovery menu< not cyanogen< both with C im sorry.. i needed a recovery menu to install cyanogen. thats why i had problems.. i tried flashing to get the recovery menu and that failed. that gave the issues.. not cyanogen
Need to go puppy training with my dog< back in an hour or so
Click to expand...
Click to collapse
Problem solved.. downloaded a new stock rom.. and used a 2.0 usb. I only have 3.0 stock an i could flash without problems on 3.0.. 2.0 were a first time hit.
Thanks again

VeryStealth said:
Problem solved.. downloaded a new stock rom.. and used a 2.0 usb. I only have 3.0 stock an i could flash without problems on 3.0.. 2.0 were a first time hit.
Thanks again
Click to expand...
Click to collapse
Glad u sovlved ur prblm bt from nxt tym read before flashing any custom rom u may hav flashed some wrong one
Sent from my GT-I9500 using Tapatalk

[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