Database Users

[Q] Flashing Modem - Odin mode error: "Secure Check Fail: mdm"

Hey guys,
I'm trying to flash an updated modem on my i337. Right now its modem is AMDB. I've tried to flash both the AMDL, AMDL_U, and AMF3 modems but I keep getting the following error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on three different machines (all w/ the updated samsung drivers). Two Win7 and one Win8. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDL modem still shows.
What's going on w/ this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.

You're a brave soul. Have you tried this in recovery http://forum.xda-developers.com/showthread.php?p=42418958

jd1639 said:
You're a brave soul. Have you tried this in recovery http://forum.xda-developers.com/showthread.php?p=42418958
Click to expand...
Click to collapse
Well... That was much easier than I thought it would be. Thanks. Might I ask, why say I'm a brave soul?

Trying to flash those modems with odin. Where did you get them? You can brick your phone flashing the wrong stuff.

jd1639 said:
Trying to flash those modems with odin. Where did you get them? You can brick your phone flashing the wrong stuff.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2324667

Is there an actual fix to this issue? The CWM flashable zips don't have the latest baseband.

Blaze9 said:
Is there an actual fix to this issue? The CWM flashable zips don't have the latest baseband.
Click to expand...
Click to collapse
The mf3 cwm flash able zip is the latest modem/baseband for our i337. Its in the thread linked.
Sent from my SGH-I337 using Tapatalk 2

Febby said:
The mf3 cwm flash able zip is the latest modem/baseband for our i337. Its in the thread linked.
Sent from my SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
The zip for MF3 located here is CWM flashable?
http://forum.xda-developers.com/showthread.php?t=2324667
**Edit***
Just tested it. Yeah, they worked. I dunno why the instructions said to use Odin for the Zips as well.
Thanks

Blaze9 said:
The zip for MF3 located here is CWM flashable?
http://forum.xda-developers.com/showthread.php?t=2324667
**Edit***
Just tested it. Yeah, they worked. I dunno why the instructions said to use Odin for the Zips as well.
Thanks
Click to expand...
Click to collapse
Glad I helped. Lack of proper instructions in that thread.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Please help, I flashed a rom and dont have any signal,
I am using a samsung sgh-m919 and My baseband version is m919uvufok3. I tried installing i9505xxuhpf3 through odin cp but it fails. please help.... ;(

Flash the stock m919 ROM from sammobile.com in Odin. The S4 forum for the m919 is here: http://forum.xda-developers.com/galaxy-s4-tmobile

[Q] Can't Odin soft brick Getting Fail on Auth. How to fix?

I took my S4 from MF3 down to MK2. Then I stupidly installed TWRP and it got stuck on:
"FIrmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I tried using kies to fix this but that doesn't work either. The recovery says at the top:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
KNOX KERNEL LOCK:0x0
KNOX WARRANY VOID:0x0
CSB-CONFIG-LSB:0x30
WRITE PROTECTION:Enable
eMMC BURST MODE:enable
KIES goes to emergency recovery and gets as far as decompressing binary files. After that it sits at "Firmware emergency stopped due to Galaxy S4(SGH-I337)error. If the prolblem persists, please contact the Samsung service centre.
Odin errors like this:
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
How do I fix this?
*EDIT: With ODIN, it writes:
START [224,140]
BAR [248,1440]
SW REV. CHECK FAIL : FUSED 4, BINARY:2

You should be able to get your phone working with Odin. Read this thread http://forum.xda-developers.com/showthread.php?p=49687770
Sent from my Nexus 5

jd1639 said:
You should be able to get your phone working with Odin. Read this thread http://forum.xda-developers.com/showthread.php?p=49687770
Sent from my Nexus 5
Click to expand...
Click to collapse
Interestingly, I get the startup sound, and I get it to be recognized in windows, but no display. What happened?

kruuth said:
Interestingly, I get the startup sound, and I get it to be recognized in windows, but no display. What happened?
Click to expand...
Click to collapse
There's no display on the phone? If Odin recognizes your device I would go ahead and try to flash the tar.
Sent from my Nexus 5

First you didn't go down. You went up to mk2. And you need to Odin the mk2 stock tar. The boot loader will block you from trying to Odin mf3 or any thing before mk2.
Future reference you are on a locked boot loader. U cannot flash a custom recovery or use anything other than stock kernel.
Look into safe strap If you get your phone working again

D'oh. You're correct. Thanks.
SelfElevated2 said:
First you didn't go down. You went up to mk2. And you need to Odin the mk2 stock tar. The boot loader will block you from trying to Odin mf3 or any thing before mk2.
Future reference you are on a locked boot loader. U cannot flash a custom recovery or use anything other than stock kernel.
Look into safe strap If you get your phone working again
Click to expand...
Click to collapse

[Q]Flashing Lollipop help

i have been trying to install stock Lollipop on my device. i have followed both http://www.androidpit.com/how-to-get-android-5-0-lollipop-on-the-galaxy-note-3 and http://techbeasts.com/2015/02/14/update-galaxy-note-4-n910f-android-501-lollipop-official/ to the letter. This is also my fourth or fifth time using Odin. Every attempt has failed. i have tried Odin 3.10, 3.09, and 3.07 and got the same results:
Code:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone's download screen gave thisd message:
Code:
Secure Check Fail : sbl1
until i switched from "N9005XXUGBOB6_N9005XEOGBOA4_XEO" to "N9005XXUGBOA5_N9005XEOGBOA4_XEO" and also freezing any anti-theft app that may be locking my device somehow. Now the screen says:
Code:
Secure Check Fail : aboot
i am rooted (running Omega 24) and to be sure, i re-flashed auto-root
i have tried 4 different USB cables
No USB hubs, i am connected directly to my PC
Firewall, AntiVirus, and Anti Malware software are all off.
i have run Odin as admin
Reactivation Lock is not ticked
Some other things me screen says that may be of some help are:
Code:
QUALCOMM SECUREBOOT: ENABLE
followed by some coupling of letters and numbers and:
Code:
Write Protection: Enable
i am hoping that a factory reset can be my very last resort. i am contemplating reflashing my current Omega ROM and then retrying this.
Any ideas?
EDIT: Factory Reset did not change anything

Is your device unlocked or branded?

Joku1981 said:
Is your device branded or unlocked?
Click to expand...
Click to collapse
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...

billybag said:
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
Click to expand...
Click to collapse
Odin gave you fail in the NAND. This mean that you have lost plenty of files in EFS. Try to restore your OMEGA backup.

Joku1981 said:
How you unlocked it? By IMEI or other method?
Click to expand...
Click to collapse
Damn, i don't remember. It seemed so long ago. i don;t suppose there is a way to check...
EDIT: while attempting a restore of a nandroid backup, i noticed something. The following backup files were missing:
.android_secure.vfat.tar and
.android_secure.vfat.tar.a

i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
Do you have any EFS backup?

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.

Journyman16 said:
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Click to expand...
Click to collapse
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10

billybag said:
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
Click to expand...
Click to collapse
Do you know your original firmware? I'm wondering because some versions have different sized partitions and flashing another type causes fails. i.e. I had a HK S3 and had to flash a PIT file before I could use European firmware. Might it be something along those lines?

Have practically the same situation...
The furthest I've got is the following
Code:
<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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
But again, with any version of odin and any firmware (lollipop or kitkat) i'm trying to flash, it stucks with
Code:
<ID:0/003> Complete(Write) operation failed.
PS I also have
Code:
QUALCOMM SECUREBOOT: ENABLE
Write Protection: Enable
and my phone was originally locked to spanish vodafone.

Sorry for the delay. i just got around to giving it another shot and it worked. i found an official, made for TMOBILE, version of the firmaware.
Code:
N900TUVUFOB6_N900TTMBFOB6_TMB
for anyone else that may be having trouble. You can find it here: http://www.sammobile.com/firmwares/download/43850/N900TUVUFOB6_N900TTMBFOB6_TMB/
i was using n9005 firmwares, which is usually fine except int his case i needed a tmo one.
Thanks again for everyone's input. Hopefully this post can help someone else out now.

[Q] bricked note 3 n900v

ok we all know how this happens and some of us actually try everything and read everything before posting...
i have a 900v
i can get it into download mode
i cant get any stock roms to flash
i have run a pit file with odin 3.07 and that worked to get my phone to be able to go into the screen by power vol up and home
so when i power vol down and home i get the odin mode / download screen and i continue and odin recognizes the phone
now when i load odin 3.09 and stock roms from sammobile it errors.
one thing i noticed is the wait time when loading the stock rom to odin. it hangs for a while. odin when flashing in the past was quick at loading its roms.
ive tried mje rom
nc2, nc4 non of which are working with odin at this time.. where did i go wrong.?
here is the log;
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<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)
i posted some screen shots..
also i am using the 3.0 cable to a 3.0 slot so it should be proper connections
samsung returned my phone without fixing it because it didnt have an IMEI sticker behind the battery. AHHSOLES it was in warranty.

Try with the 2.0 usb cable.
what rom are you flashing? And what rom you coming from?

Hi.
I had Jasmin room 2.4 I think. I tried to flash back to stock rom. To sell the phone

puchodog1977 said:
Hi.
I had Jasmin room 2.4 I think. I tried to flash back to stock rom. To sell the phone
Click to expand...
Click to collapse
I'm with israfm on trying a usb 2.0 cable and try different usb ports on your computer too (try to stick with usb 2.0 ports because I've read before that Odin doesn't play as well with usb 3.0 for some reason) .
If you're not flashing the pit file together with the stock Firmware, I would try that too. Also, make sure KIES is not running in the background if you have it installed on the computer, and disable any antivirus programs.

I'll report back soon. I switched to a Samsung note 4 USB cord but was still plugged into a 3.0 port I'll move it to 2.0 and try to flash the pit file and stock kit kat verizon rom . The pit file only worked on Odin 3.07 and I thought I needed to use Odin 3.09 for Samsung. Is that right?

puchodog1977 said:
I'll report back soon. I switched to a Samsung note 4 USB cord but was still plugged into a 3.0 port I'll move it to 2.0 and try to flash the pit file and stock kit kat verizon rom . The pit file only worked on Odin 3.07 and I thought I needed to use Odin 3.09 for Samsung. Is that right?
Click to expand...
Click to collapse
The pit file will work with Odin 3.0.9 as well, just load it into PIT file slot and load the firmware into the AP slot.
In Odin, you should have Auto Reboot, Re-partition, and F. Reset Time checked, but all other options should be unchecked. Another important thing I forgot to mention was to Run Odin as Administator.
If you want, you could also try it on Odin 3.10.0, which you can find at this link: Odin 3.10.0.
I've been using Odin 3.10.0 with good results and it might work for you too. (Recognized Contributor -CALIBAN666- uploaded this Odin version on this thread, so hit the thanks but for him if it helps you).

ok. i just needed to flash VZW\N900VVRUDNJ6 apparently the earilier versions wouldnt work. i just worked my way up from the earliest update to this NJ6
thanks guys.. oh btw i used 3.10 odin. worked like a charm

puchodog1977 said:
ok. i just needed to flash VZW\N900VVRUDNJ6 apparently the earilier versions wouldnt work. i just worked my way up from the earliest update to this NJ6
thanks guys.. oh btw i used 3.10 odin. worked like a charm
Click to expand...
Click to collapse
It's good to hear that the phone is working again. I'm not sure if you know, but since you flashed 4.4.4 onto the phone, you won't be able to root it any longer. There's no current root method for anything above 4.4.2. It's possible that a root method may be developed one day, but for now, all you can do is run stock.

trying to uninstall cyanogen mod to go to stock

Hey I am trying to uninstall cyanogen mod on my galaxy s4 so that I can return it to stock to sell it. I was following this guide techbeasts.com/how-to-unroot-samsung-galaxy-s4-all-versions/
I downloaded my firmware off of samsungs site the newest firmware available for my phone. I tried to restore it and it gave me an error about xmitdata fail so I had to unplug the phone and try again. Now if I try and boot up the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. If I try and reflash it in odin I get this far now and it freezes...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOH1_I337MOYAGOH1_I337MVLUGOH1_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
any ideas please? and thankyou!

Your phone is the i337 or i337m?
The firmware you are flashing looks like it is for the i337m.

audit13 said:
Your phone is the i337 or i337m?
The firmware you are flashing looks like it is for the i337m.
Click to expand...
Click to collapse
Sorry should have put that behind my battery it says sgh-i337m

Are you using the original Samsung USB cable?
Odin errors when trying to flash aboot.mbn file? If it does, the firmware may not be for the phone.
Boot into download to confirm model number.

audit13 said:
Are you using the original Samsung USB cable?
Odin errors when trying to flash aboot.mbn file? If it does, the firmware may not be for the phone.
Boot into download to confirm model number.
Click to expand...
Click to collapse
yes original cable, it doesn't error it just freezes there. in Download mode it says this:
Odin Mode
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-Config-Lsb: 0x30
Secure Download: Enable
Write Protection: Enable
eMMC Burst Mode enabled
I downloaded my firmware from sammobile.com and looked up the SGH-I337M and chose the one for Fido Canada as that is what I have

Maybe try different USB ports or USB cables?
Bell, Telus, and Rogers use the same forwards with slightly different customized applications.

audit13 said:
Maybe try different USB ports or USB cables?
Bell, Telus, and Rogers use the same forwards with slightly different customized applications.
Click to expand...
Click to collapse
I have tried different port and I don't have another cable, and does that mean I could download like a bell firmware and try that instead?
or is there a way that reinstalling cyanogenmod would fix it and somehow wipe my personal info? that's all I really need to do

Yes, you can try bell or Telus firmware but that should not make a difference.
Odin is freezing when trying to flash aboot.mbn?

audit13 said:
Yes, you can try bell or Telus firmware but that should not make a difference.
Odin is freezing when trying to flash aboot.mbn?
Click to expand...
Click to collapse
Ok downloading now to try, but ya its freezes the progress bar on phone doesn't move and the Odin app just sits there at aboot.mbn

I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.

audit13 said:
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
Click to expand...
Click to collapse
ya I downloaded latest firmware.... and phone encrypted I don't no....

Well, if Odin fails again, I suggest flashing twrp via Odin, boot into twrp, factory wipe, and flash a custom ROM to ensure the phone still functions.

audit13 said:
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
Click to expand...
Click to collapse
audit13 said:
Well, if Odin fails again, I suggest flashing twrp via Odin, boot into twrp, factory wipe, and flash a custom ROM to ensure the phone still functions.
Click to expand...
Click to collapse
I will try this now and post back...
I don't think this is good stuck with this....
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img

Weird, before it got stuck at aboot.mbn or is the latest error when trying to flash twrp?
You're only unzipping the file once from sammobile.com and flashing the tar.md5 file in the pda box?

audit13 said:
Weird, before it got stuck at aboot.mbn or is the latest error when trying to flash twrp?
You're only unzipping the file once from sammobile.com and flashing the tar.md5 file in the pda box?
Click to expand...
Click to collapse
yes, that was while trying twrp, I managed to borrow another cable and got the firmware installed it said passed but phone gets stuck during boot up, I installed twrp now what shall I do install cyanogen again?

If you successfully flashed stock rom, boot into recovery and perform a factory wipe and reboot. The first boot make take a while but the led should pulse blue as it is booting the rom.

audit13 said:
If you successfully flashed stock rom, boot into recovery and perform a factory wipe and reboot. The first boot make take a while but the led should pulse blue as it is booting the rom.
Click to expand...
Click to collapse
I did a factory wipe and rebooted and it froze ive tried 3 or 4 times now it is upgrading 29/89 will post back if it works..
got it booted up and now its asking for set up, I appreciate your patience and help very much

Flash stock again but do not check anything except f.reset time, flash stock rom, when you see the word pass in the status window, remove USB cable, remove battery and wait 5 seconds, replace battery, boot into recovery, factory wipe, reboot.

thanks ill do that if I have a problem, for now phone is up and running and ready for use

That's great news. I guess all you needed was a different USB cable. I find the s4 to be very picky about USB cables when using Odin.