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] Installing stock ROM on S4 with Cyanogenmod

Hello,
Unfortunately, I have Cyanogenmod on my Galaxy S4 GT-I9505 (in UK on O2). I want to unlock the phone, which apparently involves going back to a stock ROM.
After much searching around, I've eventually managed to download a stock ROM that wasn't corrupt, and Odin, and USB drivers. But when I try to do the firmware upgrade thing, it fails. I now seem to have a brick. How I hate Cyanogenmod!
Here's what happens in Odin:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl2.mbn
<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)
...and all I get on the screen of my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Except I can't use Kies (or Smartswitch) because it's a stupid Cyanogenmod phone so Kies (or Smartswitch) doesn't recognise its existence! GRRRRR!
So, do I have a brick that is completely useless? I've only had this phone a month or so (I bought it, tragically, with cyanogenmod on it).
Any suggestions/help/sympathy would be GREATLY appreciated! (please!)
- Paul

hellopaul said:
Hello,
Unfortunately, I have Cyanogenmod on my Galaxy S4 GT-I9505 (in UK on O2). I want to unlock the phone, which apparently involves going back to a stock ROM.
After much searching around, I've eventually managed to download a stock ROM that wasn't corrupt, and Odin, and USB drivers. But when I try to do the firmware upgrade thing, it fails. I now seem to have a brick. How I hate Cyanogenmod!
Here's what happens in Odin:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl2.mbn
<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)
...and all I get on the screen of my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Except I can't use Kies (or Smartswitch) because it's a stupid Cyanogenmod phone so Kies (or Smartswitch) doesn't recognise its existence! GRRRRR!
So, do I have a brick that is completely useless? I've only had this phone a month or so (I bought it, tragically, with cyanogenmod on it).
Any suggestions/help/sympathy would be GREATLY appreciated! (please!)
- Paul
Click to expand...
Click to collapse
It has nothing to do with Cyanogenmod all your problems. You are putting the blame in the wrong corner. Kies not recognizing, the failure of the flash, not being sim-unlock has nothing to do with Cyanogenmod. But with you not reading enough.
You want to flash a 4.2.2 rom and you can only do that if you are not on a knox bootloader. What is the text when you boot in download mode?
And btw, as far as I know you don't need to downgrade your FIRMWARE, but only your MODEM.

Thanks for your quick reply!
Lennyz1988 said:
You want to flash a 4.2.2 rom and you can only do that if you are not on a knox bootloader. What is the text when you boot in download mode?
Click to expand...
Click to collapse
Here's the text:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled​
And btw, as far as I know you don't need to downgrade your FIRMWARE, but only your MODEM.
Click to expand...
Click to collapse
Is that an easier process?
I was using Android 5.0.2 with Cyanagenmod. I'm not sure what version the ROM I downloaded was - it actually downloaded and wasn't a corrupt .zip file, which seems to be a very very rare thing. Might attempting to install a 4.x.x firmware over a 5.x.x cause problems? Is there anywhere I can reliably download a 5.x.x ROM that actually works? I've wasted several days searching for a UK O2 ROM. I can recommend plenty of sites that CLAIM to have it, but it's corrupted or just doesn't download due to any number of errors.

hellopaul said:
Thanks for your quick reply!
Here's the text:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled​
Is that an easier process?
I was using Android 5.0.2 with Cyanagenmod. I'm not sure what version the ROM I downloaded was - it actually downloaded and wasn't a corrupt .zip file, which seems to be a very very rare thing. Might attempting to install a 4.x.x firmware over a 5.x.x cause problems? Is there anywhere I can reliably download a 5.x.x ROM that actually works? I've wasted several days searching for a UK O2 ROM. I can recommend plenty of sites that CLAIM to have it, but it's corrupted or just doesn't download due to any number of errors.
Click to expand...
Click to collapse
Here an whole post with firmwares.
http://forum.xda-developers.com/showpost.php?p=41072392&postcount=2
Try flashing a 4.4.2. firmware. If flash is succesfull, then downgrade modem to 4.2.2.
If it's not, then pick an 5.0.1 firmware and downgrade modem to 4.2.2.
4.2.2 modem:
http://d-h.st/CXx
When you are done with what you want to do ( I assume something with region away). Flash AGAIN the 4.4.2 firmware or 5.01. You cannot stay on the 4.2.2 modem.

Thank you for your help with this!
I managed to un-brick my phone (hooray!) using 'Philz Touch' and some of the advice here: http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
I just re-downloaded that firmware from the site you suggested - that's where I managed to download the (exact same) firmware before. I've just tried installing it again, but got exactly the same error in Odin. I've currently got another ROM downloading from one of the dodgy 'teenage-hacker' sites (Rapidgator.net). I assume that it won't even unzip, but it will be tomorrow before it's completed the download.
I'm guessing that I need to download firmware that's UK and O2 (I'm in the UK and my phone's locked to O2). This rather limits my options - there only seem to be a couple of places on the net with this ROM (neither of which work). If I installed, say, a Vodafone ROM, then unlocked the phone, should that (in theory) then work with my O2 (or any other) SIM? I plan to switch to BT Mobile (running on the EE network) shortly - hence wanting to unlock the phone.

hellopaul said:
Thank you for your help with this!
I managed to un-brick my phone (hooray!) using 'Philz Touch' and some of the advice here: http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
I just re-downloaded that firmware from the site you suggested - that's where I managed to download the (exact same) firmware before. I've just tried installing it again, but got exactly the same error in Odin. I've currently got another ROM downloading from one of the dodgy 'teenage-hacker' sites (Rapidgator.net). I assume that it won't even unzip, but it will be tomorrow before it's completed the download.
I'm guessing that I need to download firmware that's UK and O2 (I'm in the UK and my phone's locked to O2). This rather limits my options - there only seem to be a couple of places on the net with this ROM (neither of which work). If I installed, say, a Vodafone ROM, then unlocked the phone, should that (in theory) then work with my O2 (or any other) SIM? I plan to switch to BT Mobile (running on the EE network) shortly - hence wanting to unlock the phone.
Click to expand...
Click to collapse
You are not reading what I wrote. You CANNOT flash the firmware you tried before. It's impossible because that version is to old. You are downloading a 4.2.2 and you need need 4.4.2 minimal (possible even 5.0.1 minimum).

I have no way of telling which version that firmware was - it was listed under United Kingdom and had O2 in the filename. No version number.
So - back to my previous question - should I be able to use, say, a Vodafone 4.4.2 firmware without risk of bricking my phone? Or maybe the BTU 5.0.1 version? And then be able to do the standard Samsung S4 process to unlock it? I guess I'll just try it and see if it works.

No. You need to download the latest ROM for your carrier, here. Once you have installed that firmware, you must install through Odin a 4.2.2 modem found at the link Lennyz1988 provided. Only then can you use the service menu method or RegionLock Away to unlock the S4. After that, extract the modem from the firmware package you downloaded and flash it through Odin.
Honestly, spend the money and unlock the phone, if O2 won't do it. An unlock code is virtually guaranteed to work, unlike the unlock methods in the forums.

Unfortunately that firmware you linked to is one of the many corrupt .zip files out there, and will not decompress at all.
I've got another firmware downloading (very very slowly) from Rapidgator. It will probably also be corrupt.
I've called a couple of local phone unlocking shops, and they don't have a clue what Cyanagenmod is, and whether it will affect the unlockability of the phone. I'll just pay an ebayer to give me an unlock code, in the hope that it might unlock it, despite what I've read. Most people say I must go back to a stock ROM before unlocking.
Ugh. Awful Cyanogenmod.

hellopaul said:
Unfortunately that firmware you linked to is one of the many corrupt .zip files out there, and will not decompress at all.
I've got another firmware downloading (very very slowly) from Rapidgator. It will probably also be corrupt.
I've called a couple of local phone unlocking shops, and they don't have a clue what Cyanagenmod is, and whether it will affect the unlockability of the phone. I'll just pay an ebayer to give me an unlock code, in the hope that it might unlock it, despite what I've read. Most people say I must go back to a stock ROM before unlocking.
Ugh. Awful Cyanogenmod.
Click to expand...
Click to collapse
The archives are not corrupt. Something is wrong at your end.
And again, CM has nothing to do with your issues. If you were on the stock rom you would just have had the same problem.

If I was on a stock ROM I wouldn't have to go through all this, and could presumably just unlock my phone very easily, as outlined on many sites, such as giffgaff (I cannot post links in this forum yet).
I cannot get that ROM to unzip, using 7-zip, WinRAR, Mac OS X Finder, Mac OS X Terminal. I've downloaded it at least 3 times, and it's always corrupt. Mac OS X Terminal reports "bad zipfile offset (local header sig): 0".
Uh?? Update: I've just tried 7-zip again...and it's decompressed it! How utterly bizarre.
I just tried it with Odin and it did not work - the usual result:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl2.mbn
<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 have to turn off the phone, and use Philz Touch to bring it back to life.

hellopaul said:
If I was on a stock ROM I wouldn't have to go through all this, and could presumably just unlock my phone very easily, as outlined on many sites, such as giffgaff (I cannot post links in this forum yet).
I cannot get that ROM to unzip, using 7-zip, WinRAR, Mac OS X Finder, Mac OS X Terminal. I've downloaded it at least 3 times, and it's always corrupt. Mac OS X Terminal reports "bad zipfile offset (local header sig): 0".
Uh?? Update: I've just tried 7-zip again...and it's decompressed it! How utterly bizarre.
I just tried it with Odin and it did not work - the usual result:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl2.mbn
<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 have to turn off the phone, and use Philz Touch to bring it back to life.
Click to expand...
Click to collapse
Yes ofcourse it fails. You are not following my instructions.
You are flashing a 4.3 rom which is IMPOSSIBLE for you. Your bootloader is at least a 4.4.2 version, probably even a 5.0.1 version. So you can only flash those stock roms.

Lennyz1988 said:
Yes ofcourse it fails. You are not following my instructions.
You are flashing a 4.3 rom which is IMPOSSIBLE for you. Your bootloader is at least a 4.4.2 version, probably even a 5.0.1 version. So you can only flash those stock roms.
Click to expand...
Click to collapse
Sorry if I'm not following you. How can you tell what version the firmware file is? The site I downloaded it from claimed it was 5.0.1.
My phone's Android version is 5.0.2
I've been putting the firmware file into Odin's AP slot.
I haven't done anything with the BL (presumably bootloader) slot.
Isn't there a way I can completely wipe the phone, then install whatever firmware I want, regardless of what was previously installed?

alright let's try something else.
Flash this rom with Philz. Perform a full wipe first form within the recovery.
http://forum.xda-developers.com/showthread.php?t=2283194
It's a 4.4.2.
Then flash a 4.2.2. modem and then try the things you want to do.

So I guessed that I should copy the .zip file of that WanamLite Rom onto the SD card, which I did.
I then did:
Recovery mode reboot, and booted into the Philz thing.
Wipe Data/Factory Reset.
Install Zip > Choose zip from /storage/sdcard1, and located the .zip file...
Installing...
Finding update package...
Installing update...
Welcom to WanamLite XXUGNH7 3.1
Formatting system...
System mounted!
data mounted!
Cleaning cache...
Installing system...
Symlinking...
Setting permissions...
set_metadata: some changes failed
E:Error in /storage/sdcard1/GT-I9505_WanamLite.XXUGNH7.V3.1.NO-WIPE.zip
(Status 7)
Installation aborted.
press any key to continue.​
So now I'm wondering how to get around a Status 7 error. Searching that forum thread about Wanamlite gives no help - at least not in a language a human can understand. Someone suggested:
"after spending several hours on this ... i made it
How to flash this ROM on old NON-Knox bootloader:
1. flash XXUEMJ5 modem via odin to prevent lags and call problems
2. flash a TWRP recovery to bypass the "status code 7"-error while flashing this ROM
3. flash this ROM
4. install your prefered recovery"​
I have absolutely no idea what any of that that means.
I have rebooted the phone, and it will only boot into the Philz thing - presumably because there is no operational firmware installed at all.

Partial success:
I followed the instructions given here: https://www.youtube.com/watch?v=np_nlFALMbQ
...to install firmware via PhilZ Touch, and I can successfully install Cyanogenmod (argh!) or WanamLite (yeah!). But I still cannot access the service menu in WanamLite. At least typing *#0011# does get some kind of menu up, but not the ServiceMode main menu.
And at least I now have a fully operational phone (with WanamLite), but still locked to O2.
Lennyz1988 suggested I "flash a 4.2.2. modem" - might doing that unlock the ServiceMode menu? Are those at all related? To flash the modem (presumably using Odin) which slot do I put it in? CSC?
I tried installing the O2 UK firmware using the exact same technique, using both the ROMs I downloaded, but neither would work. It failed at the very start, saying [bad]. I then reinstalled WanamLite successfully.

It wasn't just Lenny who mentioned flashing the 4.2.2 modem. I mentioned it as well. In fact, in the thread on the topic - which you really should be reading - the last few pages are peppered with posts from me telling people that you have to downgrade the modem (at minimum) before you can use either unlock method. For the record, I know downgrading works, because I had to do it myself after losing a SIM unlock that was done through the service menu. I ended up using RegionLock Away and couldn't be happier.
With that said, you cannot use a custom ROM of any kind to perform the unlock. I tried accessing the service menu on Imperium ROM, which is based on stock, and failed. You must be completely stock, which means you need to install a stock ROM to your device, using Odin. Download a new copy of the ROM, and if necessary use a totally different computer. Just one question however. If flashing the ROM through Odin doesn't work this time, will you then blame WanamLite for it?

Thank you for all your help with this, Strephon and Lennyz1988.
So, I tried flashing the modem (I put this file: I9505ZHUFNB3_MODEM.tar into Odin's CP slot - it seemed to work). I rebooted and tried to get to the service menu, but as Strephon predicted, there was no service menu.
So, again using Odin, I tried to put this firmware (I think it might be 4.2.2) on the phone:
I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5
...and, predictably, it failed.
So then I tried doing them both at the same time, with the modem file in the CP and the firmware in the AP slot. But it failed again:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> 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)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
I also tried to re-install the various other stock ROMs I'd downloaded (and re-downloaded, on a different computer), with no success.
So, I got back in touch with O2 - they'd previously said they wouldn't unlock the phone because they say the phone and number need to have been used together for 12 months. I only bought the phone about 6 weeks ago. But after much pleading (and £15) they've agreed to send me an unlock code! So when this arrives, I'll try it out (the phone is currently still running WanamLite) and see if it works. If not, to save my sanity, I'll just cut my losses and sell/give away the bloody phone as "locked (forever) to O2, with WanamLite or Cyanogenmod".
And no - I don't blame WanamLite (or Cyanogenmod now) for the stock ROM installations working - I can only assume that there's a problem with the ROMs. I can install WanamLite and Cyanogenmod fine, and it just so happens that they're not downloaded from some dark, dodgy server, unlike most of the supposedly stock ROMs. It's just really annoying that the phone's previous owner thought it was a good idea to install Cyanogenmod in the first place, without first unlocking the phone.

It's only annoying because the phone wasn't unlocked beforehand, meaning you have to put the stock ROM on the device in the first place to be able to unlock it using those methods. I can understand that. However, you still have the issue of why Odin keeps on failing when you try running it. That's one that perplexes me as I've had no issues with Odin whatsoever.

Well, my problems are over! O2 have already emailed me an unlocking code which WORKED! I now have an unlocked phone. I'm still interested in tweaking it, so may well install a more interesting firmware in future.
Thanks for your help and suggestions!

[HELP] Trying to root,can't turn on wifi...

So basically,got phone last night,tried regular rooting,didn't work,read up some more,tried the whole "Root AT&T Galaxy S4 SGH-I337 on I337UCUFNJ4 Firmware" even though my firmware is I337UCUFNJ5 and not 4,anyway,thread told me to flash I337_NC1_Stock_Kernel using the Odin firmware flashing tool.
I did....used towelroot app 3.0,didn't work,needed internet access (yes I got it straight from their site) fond a 2.0 version,used it,says "you should have root,no reboot required" so since I didn't have wifi on the phone,I went right back into odin and tried to use I337_NJ4_Stock_Kernel and flash it using the Odin tool to get back to the stock NJ4 kernel. Didn't work,failed,now I'm STUCK on nc1 kernel with no wifi access... help? please? this is my first rooting and I am legit clueless to most of this.. also how do I even find my boot loader etc?
EDIT: This might not be in the right thread,if so,please move to appropriate thread moderator.

SageNightmare said:
So basically,got phone last night,tried regular rooting,didn't work,read up some more,tried the whole "Root AT&T Galaxy S4 SGH-I337 on I337UCUFNJ4 Firmware" even though my firmware is I337UCUFNJ5 and not 4,anyway,thread told me to flash I337_NC1_Stock_Kernel using the Odin firmware flashing tool.
I did....used towelroot app 3.0,didn't work,needed internet access (yes I got it straight from their site) fond a 2.0 version,used it,says "you should have root,no reboot required" so since I didn't have wifi on the phone,I went right back into odin and tried to use I337_NJ4_Stock_Kernel and flash it using the Odin tool to get back to the stock NJ4 kernel. Didn't work,failed,now I'm STUCK on nc1 kernel with no wifi access... help? please? this is my first rooting and I am legit clueless to most of this.. also how do I even find my boot loader etc?
EDIT: This might not be in the right thread,if so,please move to appropriate thread moderator.
Click to expand...
Click to collapse
Here is the link for the NJ5 kernel.
If you still have problem go here and following the steps to start every thing from NB1.

sway8966 said:
Here is the link for the NJ5 kernel.
If you still have problem go here and following the steps to start every thing from NB1.
Click to expand...
Click to collapse
so I tried all of this,but odin fails no matter what sigh.. Odin tells me this:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any clue what's wrong? cause I'm really lost here

SageNightmare said:
so I tried all of this,but odin fails no matter what sigh.. Odin tells me this:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any clue what's wrong? cause I'm really lost here
Click to expand...
Click to collapse
Try with different version of odin (the latest is 3.10 I think), use different usb port, use different usb cable.
Did you load your file in the AP (auto partition) slot?

sway8966 said:
Try with different version of odin (the latest is 3.10 I think), use different usb port, use different usb cable.
Did you load your file in the AP (auto partition) slot?
Click to expand...
Click to collapse
Yup I tried all of that except a different odin version,but long story short,I managed to go into town and a friend of mine used a different version of odin and got me nice and sorted out,thanks for help btw

Latest Firmware for Galaxy Note 4 (N910TUVS2EQB1 AND N910T3) New N910TUVU2EQC1

This is the latest firmware for Tmobile Galaxy Note 4. Flash it at your own risk
I am not responsible if your phone blowup or sing the national anthem.
Samsung Galaxy USB Driver
New N910TUVU2EQC1
MDSUM: f86917e3e1763e9fb59bba6ca642fb22
How to root this:
1. Odin TWRP "uncheck auto reboot in odin" pull battery out put back in.
2. Boot to TWRP by holding Volume up Power and Home key together.
3. Flash SuperSu or flash this by PVSGH rooted rom
Enjoy
"Install Xposed Framework"
Install this first as apk XposedInstaller_3.1.1.apk
Go this this thread and flash xposed framework
I install this Qb1 stock RomControl. you guys can try it
For SM-N910T
MDSUM: 0b38870b792e37de28d1c6de721f5543
Odin 3.1.1
TWRP 3.0.2.0
Use this guide for root HERE
MDSUM: 29358c76fd6de55c086eb67bb1bff418
New firmware for SM-N910T3 (N910T3UVS3EQB1) Download HERE

Thanks for sharing, is the bootloader locked? are we able to downgrade? Thanks1

The-Accountant said:
Thanks for sharing, is the bootloader locked? are we able to downgrade? Thanks1
Click to expand...
Click to collapse
I have N910t and its not lock. I don't know about t3. You can use the guide posted by Deexii HERE just find the latest supersu if you will. Its has a good battery life. Always full wipe after and before odin. Good luck

boot loader and modem parted out
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.

Screenshots
I know I'm kinda late but I thought I would throw up some screenshots of the description of the update for anyone interested.

I have t3 and I can i use the BL and CP from T build rather than the T3. thanks

I have a n910t and update it for odin but on startup it stays on the T-mobile screen. any ideas
**Forget it and start 10 minutes the first start

razholio said:
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.
Click to expand...
Click to collapse
Just tried the modem alone not HLOS and not the bl stuff and it seems to work okay w/cm14. LTE works and a call went through anyway. Thx for doing this I hate having to download 2 gigs just to get like 100K of files.. I'll probably update the bl and such soon..
(updated via heimdall not odin fwiw)

razholio said:
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.
Click to expand...
Click to collapse
I've since flashed bq1 bl&cp and everything is working fine, though I'm on emotion 14.1 which hsbadr keeps updated with the latest proprietary blobs.

razholio said:
I've since flashed bq1 bl&cp and everything is working fine, though I'm on emotion 14.1 which hsbadr keeps updated with the latest proprietary blobs.
Click to expand...
Click to collapse
Cool. I'll give it a try in the next day or two and report back.
Update: Got impatient.. Tried the rest:
$ sudo heimdall flash --ABOOT aboot.mbn --APNHLOS NON-HLOS.bin --RPM rpm.mbn --SBL1 sbl1.mbn --DBI sdi.mbn --TZ tz.mbn
....
Uploading ABOOT
100%
ABOOT upload successful
Uploading APNHLOS
100%
APNHLOS upload successful
Uploading RPM
100%
RPM upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading DBI
100%
DBI upload successful
Uploading TZ
100%
TZ upload successful
Ending session...
It auto-rebooted. SEEMS to be working, but it's been about 30 seconds of testing
BTW, for anyone reading this who wants to also flash to modem, just add --MODEM modem.bin to the list of files above.
I see Baseband version N910TUVS2EQB1 listed in About Phone so that's good too.
(also-- I notice that it unfortunately didn't fix the timezone thing-- I still have to manually set it to keep it from jumping back to GMT)
Also, quick question-- I notice that NON-HLOS seems to always be grouped with modem.bin-- although I flash the modem as a standalone by itself (and used an older one for months alone) and it never had an issue.. is there a reason those two are treated as a group? I think (but am not 100%) that the NON-HLOS stuff contains the key stuff in /vendor. It's been a while tho since I did it so maybe it's muddled in my brain
Edit: Also, for the record, I'm using the Heimdall from here: link... No wait, actually that's gone. I pushed my working Heimdall source to here. It may be fixed better upstream but this works on Note 4 for me.

Thanks for the upload. Much faster than Sammobile's download.

Thank you for posting the ROM, I appreciate it.

Anybody has the md5sum for the sammobile firmware?

rajil.s said:
Anybody has the md5sum for the sammobile firmware?
Click to expand...
Click to collapse
Look again @ the first page

Installing this gives me 2 phone shortcuts and 2 broken Knox container apps? What is this

fattire said:
Also, quick question-- I notice that NON-HLOS seems to always be grouped with modem.bin-- although I flash the modem as a standalone by itself (and used an older one for months alone) and it never had an issue.. is there a reason those two are treated as a group? I think (but am not 100%) that the NON-HLOS stuff contains the key stuff in /vendor. It's been a while tho since I did it so maybe it's muddled in my brain
Edit: Also, for the record, I'm using the Heimdall from here: [email protected]:SaburoJiro/Heimdall.git... No wait, actually that's gone. I pushed my working Heimdall source to here. It may be fixed better upstream but this works on Note 4 for me.
Click to expand...
Click to collapse
Wish I had something intelligent to say on NON-HLOS, but I suspec the components of CP and BL are grouped together because of possible interdependencies, not that they necessarily have to break when out of sync, but the possibility exists. I've worked on build systems, and that's how I would define build artifact units.
Thanks for the heimdal links. I'd prefer not to ever have to fire up my aging winxp VM, but in the past, my heimdal attempts have always failed to identify my samsung products. I'll give this one a try.

Uh is anyone else's phone shortcut missing from the lockscreen?

I can't get this to flash, I have an N910T. Odin does recognize my phone, it shows the blue indicator. I'm using the AP box in Odin. The blue bar moves a bit, then stops cold. I checked the MD5, it matches what OP posted.
Samsung USB driver v1.5.45.0 (downloaded from Samsung's website)
Odin v3.11
Odin log:
<ID:0/005> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried different cables, different USB ports, no go. I bought this phone brand new in factory-sealed box from a reputable seller on Amazon. I'm pretty sure it's not a fake/clone.
Please help, I don't want to be stuck with a brick that I've only had for less than 24 hrs!

AnonVendetta said:
I can't get this to flash, I have an N910T. Odin does recognize my phone, it shows the blue indicator. I'm using the AP box in Odin. The blue bar moves a bit, then stops cold. I checked the MD5, it matches what OP posted.
Samsung USB driver v1.5.45.0 (downloaded from Samsung's website)
Odin v3.11
Odin log:
<ID:0/005> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried different cables, different USB ports, no go. I bought this phone brand new in factory-sealed box from a reputable seller on Amazon. I'm pretty sure it's not a fake/clone.
Please help, I don't want to be stuck with a brick that I've only had for less than 24 hrs!
Click to expand...
Click to collapse
Download this and unzip use Odin N910TUVS2EQB1_N910TTMB2EQB1_TMB-v6.0.1.zip

@gmenik6: Thanks, but I got the issue fixed without your zip. I got my file from SamMobile, the only source I really trust. It had the same MD5 as what OP posted.
I had to use a cable from my LG v10, it looks like all my other cables are shot. I'm just surprised that the cable that came with this new phone couldnt cut it, but it charges fine. The ROM flashed and booted fine. But now I'm running LineageOS.
Thanks again!

I9505 bootloader flash odin complete(write) error (SOLVED)

Okay so I was trying to update my bootloader and modem using the tutorial I found here. But odin refused to install it and left me with a softbricked device. Now I have tried to flash the new bootloader again, the old bootloader, changed pc, changed usb cord and port, tried heimdall but still not working. Now it starts to install the bootloader and odin log goes like this
<ID:0/005> Odin engine v(ID:3.1203)..
<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> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Any help?

It's possibly because the bootloader you are trying to flash is not compatible with your S4 model.
If you can't flash the bootloader separately, flashing a stock ROM package may work. Also, try a different Odin version and also another Windows.

Yeah I tried to flash the stock rom but the same thing happened. I have tried 3 different odin versions and 2 windows.

Could this be because I've changed my usb port? Odin seems to always disconnect my phone after failing and then reconnects again.

Google and download PIT file GT-I9505
Flash bootloader with pit file selected

@4shared: Nice advertising. PIT files are a weapon of last resort, thus we want to make sure there is no alternative before recommending it.
@varvainenkalas: Return to download mode and read the model number in the upper left corner. We need to make sure you don't have a Frankenphone before continuing.

Strephon Alkhalikoi said:
@4shared: Nice advertising. PIT files are a weapon of last resort, thus we want to make sure there is no alternative before recommending it.
@varvainenkalas: Return to download mode and read the model number in the upper left corner. We need to make sure you don't have a Frankenphone before continuing.
Click to expand...
Click to collapse
It says Product name: GT-I9505

Good. The USB port on the device could cause this if it's damaged or defective. You want to check its connections in the device and also clean the port with a bit of rubbing alcohol to be safe.

Yes I got it solved. I don't know how but I think that the problem was that both usb cables I tried were damaged though they worked before. I tried third usb cable and the same error came up then I tried again and it flashed the stock succesfully. How can I mark this solved?

Go to your first post and change the title. If you can't do that, add a line to the post noting that the problem was resolved.