Database Users

Software upgrade for 3 UK

Yesterday afternoon there was a notice on my phone for an OTA update. When I tried to install the phone said "no upgrade available".
Later in the evening I connected my phone to Kies, I was again offered the upgrade, but it would not install because my battery was too low.
Having had the phone on charge overnight I tried again this morning, and the upgrade was successful.
The details are,
PDA LH3
Phone LH1
CSC LH2
As I've only just finished the update, I can't tell what the changes are, but if I find any important differences I will update this thread.
Please Note: As far as I know, this update is for 3UK only.

Was already reported multiple times ... it's just an ICS update. Update is also showing up for other countries/providers.

I got this update this morning , I believe it was about 57Mb. The few changes I noticed were brightness slider in the pull down notification bar and I think a bit better battery life than I normally get. A few minor tweaks I noticed were when adding something to a home screen, before the update it used to say Add from Apps, whereas now it says add from Apps and Widgets. I think I also noticed that in the battery graph, before I could refresh by tapping the left hand menu button, but now the refresh is in the top right corner. In the power menu there are 3 buttons at the bottom too. Im guessing a lot of other carriers will have this or similar update too. I lost Root in the process of updating but that didn't matter much, just a 2 minute job to re-root so it was okay.
Hopefully Official Jelly Bean will build on this good start and be even better for our great phone ;D

I go for unlocked phones whenever I can, so I get stock updated asap, rather than waiting for bloatware, it's the only reason.
I think only my first phone was a network locked phone, and it was a dumbphone so I didn't mind, not to mention young, about 11 or 12 at the time.
Now unlocked phones are important to me so I can get stock updates faster, unless I flash custom, then it won't matter

Geryatrix said:
Yesterday afternoon there was a notice on my phone for an OTA update.
Please Note: As far as I know, this update is for 3UK only.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6 September

I have SGS3 on 3UK.
My Rom is IMM76D.I9300XXBLH3
How can I root/flash this.
Kies won't update says I have latest Rom (lies)
Odin doesn't detect phone.
SGS3 root tools doesn't have my firmware listed.
How do I do this?
Read loads, tried allsorts of random connection variations, still stuck.
First Samsung after 2 years with HTC Desire HD (first smartphone) which I found easy to root with 1.32 RUU and visionary+
Please help

Jumvah said:
I have SGS3 on 3UK.
My Rom is IMM76D.I9300XXBLH3
How can I root/flash this.
Kies won't update says I have latest Rom (lies)
Odin doesn't detect phone.
SGS3 root tools doesn't have my firmware listed.
How do I do this?
Read loads, tried allsorts of random connection variations, still stuck.
First Samsung after 2 years with HTC Desire HD (first smartphone) which I found easy to root with 1.32 RUU and visionary+
Please help
Click to expand...
Click to collapse
1st, your on the latest firmware that's why kies won't update further?
2nd Close kies first or Odin won't see your phone.
3rd Get cf root and flash with Odin.
Sent from my GT-I9300 using xda premium

Tried with only kies installed.
Tried with only odin installed.
Tried with either set of drivers individually installed.
I believe that the Rom is latest from 3uk, but I want to get rid of all that crap and use latest unbranded Rom.
Still does not tell me how to root with this ****ty Rom.
Quick response, thanks, but not helping get round the 3uk crap.

Jumvah said:
Tried with only kies installed.
Tried with only odin installed.
Tried with either set of drivers individually installed.
I believe that the Rom is latest from 3uk, but I want to get rid of all that crap and use latest unbranded Rom.
Still does not tell me how to root with this ****ty Rom.
Quick response, thanks, but not helping get round the 3uk crap.
Click to expand...
Click to collapse
If kies can see your phone the connection/drivers is/are fine. Just close (not uninstall) kies, open Odin and it should see your phone.
Try enabling usb debug under developer options on your phone.
If you want rid of 3's crap you need to flash a stock (unbranded) rom. Kies will only find an update for whatever your running. If you have a 3 rom, you'll only get 3 updates.
You could always flash a rom with root already built in, just search for one you like the look of.
Sent from my GT-I9300 using xda premium

Odin still not showing my phone.
Can I use adb like on HTC? And if so what would be the command line to flash, say, cwm or a stock Rom?
Also just realised that Odin won't help if I can't click start button anyway, darned stupid software is mostly offscreen at my max resolution.(1024*768)
Thanks again folks.

Are you in download mode ?
Sent from my GT-I9300 using xda premium

Or is there equivalent of RUU.exe ?
---------- Post added at 09:36 AM ---------- Previous post was at 09:32 AM ----------
Tried to run kies/Odin in both android and download mode.
No dice. Think it must be something to do with 3uk roms.
---------- Post added at 09:48 AM ---------- Previous post was at 09:36 AM ----------
Just wondering if everyone else on 3 is just happy with their phones and hasn't tried flashing or rooting their phones?

Jumvah said:
Odin still not showing my phone.
Can I use adb like on HTC? And if so what would be the command line to flash, say, cwm or a stock Rom?
Also just realised that Odin won't help if I can't click start button anyway, darned stupid software is mostly offscreen at my max resolution.(1024*768)
Thanks again folks.
Click to expand...
Click to collapse
You can use adb but if your pc can't see the phone its not going to help.
I doubt very much that having a 3 phone is the problem. You need to look again at your drivers. When you plug your phone in does windows start installing a driver? Does it suceed or give an error?
What about if you enable usb debugging?
Either find the separate Samsung drivers and install them, OR run kies, choose troubleshoot connection, try plugging phone in again. Once kies can see your phone close kies *** you must close kies ***, run odin. Pull cable and plug in again. Odin should light up if it sees your phone.
Kies is a pile of crap, odin isn't. I don't understand what you mean about max resolution and not clicking start button, you mean of odins start button or Windows???
Sent from my GT-I9300 using xda premium

Kies can see phone. USB debugging is enabled. Windows has Samsung drivers installed and working.
It's Odins start button I can't see (off bottom of screen)
So adb should work fine if I can have command line for it.
Once I've got cwm touch flashed I can stick a stock Samsung Rom on and root it.
If I can do that with adb will be awesome.
Thanks for all help so far, and in future.

Jumvah said:
Odin doesn't detect phone.
Click to expand...
Click to collapse
Try downloading another copy of Odin. I had a version that would not detect my phone for some reason, tried another download source and everything fine. It was nowt to do with drivers in my case
Sent from my GT-I9300 using xda app-developers app

Try Odin v1.85, you can then see the start button on 1024x768.
Sent from my GT-I9300 using xda premium

Thanks guys. Will try ans find a source for that version of Odin.
Definitely going to try to find the commands for adb still as I am much happier with command line stuff, as I am an old school coder at heart.
If I can get the adb commands I might even knock together a win7 front-end for it.

[Q] att galaxy s 4 cant get into recovery

I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!

That sounds more like download mode. There are a bunch of quick boot/recovery apps in the play store. Those would be easiest.
Sent from my TARDIS

0p3nsrc said:
That sounds more like download mode. There are a bunch of quick boot/recovery apps in the play store. Those would be easiest.
Sent from my TARDIS
Click to expand...
Click to collapse
But the thing is I can get into download mode but not my recovery

swaggsexy said:
But the thing is I can get into download mode but not my recovery
Click to expand...
Click to collapse
0p3nsrc actually answers this.
Two steps: #1. Download an app like Quickboot and then #2. start that app and use it to reboot either recovery or download mode (your choice). It should work.
I have had the same problem of the "unauthorized software" in the past and got around it by doing the manual process to get into recovery.
That is #1. turn off phone
#2. hold Volume up and keep holding it while pressing power button to start the phone
#3. Keep holding power+Volume UP button until you see the recovery indications (small print on top left part of screen).
#4. RElease the power button but DONT let go of the volume up button until you're actually in recovery. . .
you may have to try it a few times in a row to get it going, but it eventually WILL get you into recovery!

markbc01 said:
0p3nsrc actually answers this.
Two steps: #1. Download an app like Quickboot and then #2. start that app and use it to reboot either recovery or download mode (your choice). It should work.
I have had the same problem of the "unauthorized software" in the past and got around it by doing the manual process to get into recovery.
That is #1. turn off phone
#2. hold Volume up and keep holding it while pressing power button to start the phone
#3. Keep holding power+Volume UP button until you see the recovery indications (small print on top left part of screen).
#4. RElease the power button but DONT let go of the volume up button until you're actually in recovery. . .
you may have to try it a few times in a row to get it going, but it eventually WILL get you into recovery!
Click to expand...
Click to collapse
It won't work its saying. In Lil orange writting on top left kernel fail don't know what to do!

swaggsexy said:
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
Click to expand...
Click to collapse
Hay "sexy" what base are you?
MDL or MF3
your profile lacks your phone and its base
Sent from my SAMSUNG-SGH-1337 using xda app-developers app

No matter which galaxy I had (s i9000, s2 i777, or my current s4), I've always has issues with the button combo for recovery. The safest/easiest had always been the quickboot app.
To the OP: black box ROM is ONLY meant for the international s4 (i9500). Major difference in hardware from the att s4 is the octocore processor. You are most likely getting kernel failure due to the ROM/kernel combo. Not 100% sure, though. Aside from kernel fail, any other parts to the error message? Post a screenshot of your "about device" under system settings > more..
For example, mine:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my TARDIS

that is what im getting is kernel fail on the top left hand corner

andriod system erased
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4

swaggsexy said:
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
Click to expand...
Click to collapse
Explain.... How did you erase your system? Furthermore, are you talking about: your whole phone, the /system directory, or your internal sdcard? I've seen some people on the xda forums using 'system' a little too open-endedly.
If you mean /system, you're only option is flashing a ROM, unless you had a nandroid backup, in which case, depending on your recovery, you'd be able to do an advanced restore of the backup.
The same holds true if the whole phone has been wiped.
Sent from my TARDIS

swaggsexy said:
that is what im getting is kernel fail on the top left hand corner
Click to expand...
Click to collapse
swaggsexy said:
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
Click to expand...
Click to collapse
swaggsexy said:
It won't work its saying. In Lil orange writting on top left kernel fail don't know what to do!
Click to expand...
Click to collapse
swaggsexy said:
But the thing is I can get into download mode but not my recovery
Click to expand...
Click to collapse
swaggsexy said:
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
Click to expand...
Click to collapse
Since you can't get into recovery, based on what you've described, this means that you 1) flashed a recovery that was NOT loki'd 2) flashed a boot.img that was NOT loki'd.
This is most definitely something that can be fixed, depending on what Firmware your device is on.
If you know FOR A FACT that you have the MF3 bootloader, then I can walk you through how to use Heimdall to flash the phone back to an "out-of-the-box" state with MF3 firmware on it.

Is the Heiman method good to bring bacc to stock

jakew02 said:
Since you can't get into recovery, based on what you've described, this means that you 1) flashed a recovery that was NOT loki'd 2) flashed a boot.img that was NOT loki'd.
This is most definitely something that can be fixed, depending on what Firmware your device is on.
If you know FOR A FACT that you have the MF3 bootloader, then I can walk you through how to use Heimdall to flash the phone back to an "out-of-the-box" state with MF3 firmware on it.
Click to expand...
Click to collapse
If u can that would be appreciated. And the only thing I did was out a new room black box rom and root nothing going else done to the phone

swaggsexy said:
If u can that would be appreciated. And the only thing I did was out a new room black box rom and root nothing going else done to the phone
Click to expand...
Click to collapse
are you 100% positive that you were on MDL firmware? as in, you DID NOT take the OTA update for MF3? if you are on the wrong bootloader then this will brick your device.
honestly it's safer, you could just take it to BestBuy and tell them it "turned off during an update" or that you just want it reset

jakew02 said:
are you 100% positive that you were on MDL firmware? as in, you DID NOT take the OTA update for MF3? if you are on the wrong bootloader then this will brick your device.
honestly it's safer, you could just take it to BestBuy and tell them it "turned off during an update" or that you just want it reset
Click to expand...
Click to collapse
I fixed everything I just took of the Md5 off the tar file and put into Odin and it flashed just fine. Thanks for the input guys

swaggsexy said:
I fixed everything I just took of the MF3 or the tar file and put into Odin and it flashed just fine. Thanks for the input guys
Click to expand...
Click to collapse
awesome, sounds good.
as long as you have a bootloader from any firmware PRIOR to MF3, then you can just flash loki-doki as a precaution, otherwise you'll need to use SafeStrap, and I have not looked into that as I personally have no need to

[Q] So I bricked my girlfriends phone

Hello all!
I have been a long time lurker, since the release of the Galaxy S3. I thought I had an account here but when I tried logging in I was told my credentials were invalid. Here is the situation. I tried to root my girlfriends phone and forgot to enable USB Debugging. Now it's stuck on the message that says; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I have been scouring this forum for 2 days just about and I can't seem to find a situation like mine, a little like mine but not exactly like mine. I never really posted because any issue I've had, I have been able to fix by scouring the forums but this one is different.
I've downloaded Kies and tried to do an emergency recovery but it keeps saying the phone isn't recognized. I've tried every step but it keeps failing on me near the end. I've used Odin and it fails every time and I don't think I can boot into recovery mode. I can boot into the screen with the big droidbot where it say "DO NOT TURN OFF TARGET" but I can't boot into the actual recovery mode where I can use the volume keys to wipe cache or anything else.
Any help will be appreciated. Sorry I haven't engaged in the customary 4play before diving right in but we are on vacation in Puerto Rico and check out is in an hour. I want to get it up and running before that. I'm glued to my laptop so any thing you need to know that might help you to help me, please ask.

Squarez said:
Hello all!
I have been a long time lurker, since the release of the Galaxy S3. I thought I had an account here but when I tried logging in I was told my credentials were invalid. Here is the situation. I tried to root my girlfriends phone and forgot to enable USB Debugging. Now it's stuck on the message that says; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I have been scouring this forum for 2 days just about and I can't seem to find a situation like mine, a little like mine but not exactly like mine. I never really posted because any issue I've had, I have been able to fix by scouring the forums but this one is different.
I've downloaded Kies and tried to do an emergency recovery but it keeps saying the phone isn't recognized. I've tried every step but it keeps failing on me near the end. I've used Odin and it fails every time and I don't think I can boot into recovery mode. I can boot into the screen with the big droidbot where it say "DO NOT TURN OFF TARGET" but I can't boot into the actual recovery mode where I can use the volume keys to wipe cache or anything else.
Any help will be appreciated. Sorry I haven't engaged in the customary 4play before diving right in but we are on vacation in Puerto Rico and check out is in an hour. I want to get it up and running before that. I'm glued to my laptop so any thing you need to know that might help you to help me, please ask.
Click to expand...
Click to collapse
Can you give us a little more information on the model of the phone? And what firmware she was currently running with the problem occurred?

Squarez said:
Hello all!
I have been a long time lurker, since the release of the Galaxy S3. I thought I had an account here but when I tried logging in I was told my credentials were invalid. Here is the situation. I tried to root my girlfriends phone and forgot to enable USB Debugging. Now it's stuck on the message that says; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I have been scouring this forum for 2 days just about and I can't seem to find a situation like mine, a little like mine but not exactly like mine. I never really posted because any issue I've had, I have been able to fix by scouring the forums but this one is different.
I've downloaded Kies and tried to do an emergency recovery but it keeps saying the phone isn't recognized. I've tried every step but it keeps failing on me near the end. I've used Odin and it fails every time and I don't think I can boot into recovery mode. I can boot into the screen with the big droidbot where it say "DO NOT TURN OFF TARGET" but I can't boot into the actual recovery mode where I can use the volume keys to wipe cache or anything else.
Any help will be appreciated. Sorry I haven't engaged in the customary 4play before diving right in but we are on vacation in Puerto Rico and check out is in an hour. I want to get it up and running before that. I'm glued to my laptop so any thing you need to know that might help you to help me, please ask.
Click to expand...
Click to collapse
Sounds like you borked your stock recovery. Dependening on which firmware you were on flash the stock recovery in PDA slot in Odin:
MK2:https://mega.co.nz/#!E0kmzJLJ!Ftv1rwI68IU847kxATj9MF45ykUPlmyCUOF6OXs0HdY
NB1:https://mega.co.nz/#!M9EQBT5A!ri4QeMYpgi-JjmUGZ3FY2gtogDBWPEL7zRCjASIcVe8

Download latest firmware and use Odin to flash said firmware. Should fix the problem
Sent from my HTC6600LVW using xda app-developers app

It's a Samsung Galaxy S4 SGH-I337 and she was running KitKat 4.4.2 when it went brick. I'll try the steps outlined and let you guys know how it goes.

So I tried flashing using Odin and here is what I got. I said PIT file was missing so I loaded a PIT file and what you see is what I saw.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

NB1 = 4.4 firmware
Just flash the NB4 stock recovery.
---------- Post added at 01:01 PM ---------- Previous post was at 01:00 PM ----------
Meant NB1

muniz_ri said:
NB1 = 4.4 firmware
Just flash the NB4 stock recovery.
---------- Post added at 01:01 PM ---------- Previous post was at 01:00 PM ----------
Meant NB1
Click to expand...
Click to collapse
I removed MD5 from the end of the file and it worked flawlessly. I was able to get into recovery mode and from everything I've learned here over the years I got it from here. Thank you guys so much, the knowledge that's here is amazing.

Squarez said:
I removed MD5 from the end of the file and it worked flawlessly. I was able to get into recovery mode and from everything I've learned here over the years I got it from here. Thank you guys so much, the knowledge that's here is amazing.
Click to expand...
Click to collapse
Glad you got it figured out buddy. :good:
She can stop slapping you in the back of the head now because you will have her back to playing her games and socializing in no time.

Yup, knowledge acquired from borking my phone every which way. I'm glad it worked out.

Maribou said:
Glad you got it figured out buddy. :good:
She can stop slapping you in the back of the head now because you will have her back to playing her games and socializing in no time.
Click to expand...
Click to collapse
Not so fast lol. I had to leave our rented house and now we are at her parents house before we leave in the morning. I shouldn't have rushed out but we were out of time. Now the screen stops at the AT&T logo and it turns orange. It won't start up to the actual OS. Any help with that? I can get to recovery mode and download mode but nothing more.
On a side note, while I was driving over here this situation made me want to learn more and the fact that you guys love helping so much makes me want to learn more about my phone and taking advantage of it. I'm going to find a profile picture to customize my profile because once I hit the states I think I'm going to participate a lot more. I just saw some custom themes that blew my mind!

Just noticed it gets extremely hot when it let it sit on the frozen orange logo screen.

Squarez said:
Just noticed it gets extremely hot when it let it sit on the frozen orange logo screen.
Click to expand...
Click to collapse
Here is the 4.4 full odin tar file: http://forum.xda-developers.com/showthread.php?t=2674223

muniz_ri said:
Here is the 4.4 full odin tar file: http://forum.xda-developers.com/showthread.php?t=2674223
Click to expand...
Click to collapse
Thank you! All I have are the MK2 files. I'll wait until I get to an actual wifi spot to download that because I've almost chewed up most of my cell bandwidth for the month. A 1.5GB hit won't help.
Also I just noticed the thank you button so I'm going to give thanks for everyone that has helped. It's appreciated!

Wait, I have the rooted NB1 image V2.0. Can I use that? Problem is, every time I try and use it, Odin crashes.

These are the last steps I was following before it bricked it accidentally. I have all these files.
http://forum.xda-developers.com/showthread.php?t=2663545

Squarez said:
These are the last steps I was following before it bricked it accidentally. I have all these files.
http://forum.xda-developers.com/showthread.php?t=2663545
Click to expand...
Click to collapse
I recommend you flash the 4.4 NB1 full odin tar to get your back up and running. From there you can take your time and do some reading and make sure you understand before flashing anything else. As long as newbies make an attempt to search and read most people here are glad to answer questions. Good luck

muniz_ri said:
I recommend you flash the 4.4 NB1 full odin tar to get your back up and running. From there you can take your time and do some reading and make sure you understand before flashing anything else. As long as newbies make an attempt to search and read most people here are glad to answer questions. Good luck
Click to expand...
Click to collapse
Yeah so I'll look for a good connection that wont kill my data plan. What funny is, I can root in my sleep, been doing it for a few years. With hers I just screwed up and now it's giving me problems. There is a plethora of data here that I mine through every few weeks. Up until this newest update my phone has been rooted since I got it with SU, Titanium Backup etc but I guess I have to keep up with what's new. You live and you learn I guess. Thanks for all your help, I really appreciate it.

Squarez said:
These are the last steps I was following before it bricked it accidentally. I have all these files.
http://forum.xda-developers.com/showthread.php?t=2663545
Click to expand...
Click to collapse
I think it's going to take a lot of cunning linguistics to fix this little mess with your girlfriend dear fellow!

adomol said:
I think it's going to take a lot of cunning linguistics to fix this little mess with your girlfriend dear fellow!
Click to expand...
Click to collapse
lol, i was thinking the same thing. Would not like to be him right now.

Softbricked my Phone

Tried factory reset through safestrap like and idiot and wiped system data and started the phone up with nothing. Now, I get as far as the Samsung with the unlocked padlock and that's it. I've tried Odin back to NB1 but can't seem to find any NC1 Odin files. I was on NC1 Hyperdrive 18.1 i am clueless and about to throw the computer along with the phone out the window. Please tell me what i need to do. Thank you much.!!

Also Knox says it is 0*1 which I think is bad

In download mode it says that

tmac42 said:
Tried factory reset through safestrap like and idiot and wiped system data and started the phone up with nothing. Now, I get as far as the Samsung with the unlocked padlock and that's it. I've tried Odin back to NB1 but can't seem to find any NC1 Odin files. I was on NC1 Hyperdrive 18.1 i am clueless and about to throw the computer along with the phone out the window. Please tell me what i need to do. Thank you much.!!
Click to expand...
Click to collapse
There is no odin file for NC1. You have to odin back to NB1 and then update to NC1. http://forum.xda-developers.com/showpost.php?p=53431153&postcount=1944 has details about the update file.
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
tmac42 said:
Also Knox says it is 0*1 which I think is bad
Click to expand...
Click to collapse
Dont worry much about the knox flag. It could become an issue only if you take your phone for warranty replacement and they check that. Also, knox enabled apps cannot be installed. Otherwise, your phone will function normally.

I've tried to Odin back countless times and it always fails at set partition

jmjoyas said:
There is no odin file for NC1. You have to odin back to NB1 and then update to NC1. http://forum.xda-developers.com/showpost.php?p=53431153&postcount=1944 has details about the update file.
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
Dont worry much about the knox flag. It could become an issue only if you take your phone for warranty replacement and they check that. Also, knox enabled apps cannot be installed. Otherwise, your phone will function normally.
Click to expand...
Click to collapse
I've tried to Odin back countless times. It always stops at "Set Partition" and then fails 5 minutes later.

Do you have re-partition option selected in Odin? If so, unselect and try? The phone is in download mode right?

jmjoyas said:
Do you have re-partition option selected in Odin? If so, unselect and try? The phone is in download mode right?
Click to expand...
Click to collapse
Yes. It's in download mode. And reparation is unchecked. Only thing checked is "auto reboot" and "F. Reset Time"

jmjoyas said:
Do you have re-partition option selected in Odin? If so, unselect and try? The phone is in download mode right?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is as far as it gets

The picture shows that you have re-partition selected. If it still doesnt work even after unselecting, can you try with Odin 3.09?

jmjoyas said:
The picture shows that you have re-partition selected. If it still doesnt work even after unselecting, can you try with Odin 3.09?
Click to expand...
Click to collapse
Did both of those. You think if I flash the nb1 kernel, it might have a better shot?

I'm honestly losing hope

Change your cable and the USB port it's plugged into between flash attempts. Odin seems to be pretty sensitive about this on "Set PIT File..."
It'll almost always show up in Odin, but sometimes the connection isn't solid enough to actually start the flash.

jdisco1 said:
Change your cable and the USB port it's plugged into between flash attempts. Odin seems to be pretty sensitive about this on "Set PIT File..."
It'll almost always show up in Odin, but sometimes the connection isn't solid enough to actually start the flash.
Click to expand...
Click to collapse
I will try that. What if I take it to Best Buy? You think they could do anything?

tmac42 said:
I will try that. What if I take it to Best Buy? You think they could do anything?
Click to expand...
Click to collapse
Use the nb1 tar and don't check re-partition checked. It'll work
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Use the nb1 tar and don't check re-partition checked. It'll work
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I've been using the all at nb1 tar

tmac42 said:
I will try that. What if I take it to Best Buy? You think they could do anything?
Click to expand...
Click to collapse
If you're lucky enough to have the guy not notice the "KNOX WARRANTY VOID: 0x1" they'll flash it to stock for you. He will most likely notice because checking that is one of the 1st things they look for.
Doesn't hurt to try if you're out of options though.
I would keep at it if I were you. Switch cables, computers, and 2.0/3.0 USB ports. I'll go through eventually.
Also, see if you can flash just the PDA slot and no PIT

jdisco1 said:
If you're lucky enough to have the guy not notice the "KNOX WARRANTY VOID: 0x1" they'll flash it to stock for you. He will most likely notice because checking that is one of the 1st things they look for.
Doesn't hurt to try if you're out of options though.
I would keep at it if I were you. Switch cables, computers, and 2.0/3.0 USB ports. I'll go through eventually.
Also, see if you can flash just the PDA slot and no PIT
Click to expand...
Click to collapse
No idea what it did. Switched the cable though and the port. So weird that that actually works. Thank you so much everyone!!!

tmac42 said:
No idea what it did. Switched the cable though and the port. So weird that that actually works. Thank you so much everyone!!!
Click to expand...
Click to collapse
Odin is finicky. Changing ports and cable usually works
Sent from my Nexus 5 using XDA Free mobile app

Thanks again both of you!!

New Firmware QA1 released 1/26/2017...Security update

January 1 Security update. Everything else seems to have stayed the same.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Another update! Cool.

These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.

Could anyone installed this update, confirms that the bootloader still unlocked, plz?
Sent from my SM-N910P using Tapatalk

tx_dbs_tx said:
These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.
Click to expand...
Click to collapse
I agree. I never update until i have an Odin file!

aaron74 said:
I agree. I never update until i have an Odin file!
Click to expand...
Click to collapse
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?

anees02 said:
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?
Click to expand...
Click to collapse
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!

aaron74 said:
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!
Click to expand...
Click to collapse
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?

anees02 said:
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?
Click to expand...
Click to collapse
On all firmwares. The middle listing is the csc version, and its always got a different numbering than the others.
There's 3 version numbers here. 1st is the PDA (which is the actual rom firmware) 2nd is CSC (which is region) 3rd is the PHONE (which is the modem)
So this one is still #4 so it should be alright to still downgrade.
Now the last 3 digits just rep the date. Q=2017 A=January 1= 1st revision.
https://forum.xda-developers.com/showthread.php?t=1356325

wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?

linhnd2000 said:
wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?
Click to expand...
Click to collapse
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk

samep said:
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
works perfectly. thanks. I went back to PK1 so I can use the debloated rom.