Related
How to SIM unlock and/or roll back firmware on Samsung Note 2 N7105.
This is how I did it. It worked for me. That's all I can say. It may or may not work for you. I'm no 'expert' so I can't answer any tech question. I found this by trial and error. None fatal. ( So far) I will take it for granted you know how to Root and use Odin. I'm also assuming you have installed the Samsung USB Drivers.
http://uploaded.net/file/xdloq4jw
If you are using one machine to do this remember to disable Kies before using Odin.
My phone was updated to 4.3 using Kies. I did this on my laptop as I didn't want Kies messing up anything on my computer that I was going to use for the rest of the process.
So stating with a stock phone.
Using Odin
http://uploaded.net/file/o2xcp01n
I rooted my Phone with
CF-Root
http://download.chainfire.eu/255/CF-Root/CF-Auto-Root/CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip
I then downloaded SuperSu from the market and ran that. It runs a fix to stop Knox.
I then installed ES File Explorer from the market.
Then I downloaded My Phone Explorer. I like this program and use it a lot.
http://www.fjsoft.at/en/
Using ES I backed up my EFS folder to my Sd Card
Using MyPhoneExplorer I backed it up again to my computer.
Better safe than sorry.
I then used Odin again to install the 4.1.1 Firmware.
I got it from here. There's 4.1.2 there as well for those that asked.
http://www.sammobile.com/firmwares/1/?model=GT-N7105&pcode=EVR#firmware
I then installed 4.1.1 by unzipping the file and using Odin.
I then use CF-Root again.
Using the *#Codes as below
Step 1. Insert a SIM on your Note 2, you should find the familiar “SIM network unlock PIN” window.
Step 2. Dial “*#197328640#” on your Note 2 to enter special menus.
Step 3. Choose “UMTS”.
Step 4. Next choose “Debug screen”.
Step 5. Choose “Phone Control”.
Step 6. Choose “Network Lock”.
Step 7. Choose “Perso SHA256 OFF” and wait about 30 seconds.
Step 8. Press the Menu button then choose “Back”.
Step 9. Choose “NW Lock NV Data Initiallize” and wait about 1 minute. *Then reboot your Note 2.
Step 10. Once rebooted, you should no longer get the Network Lock window any more and you should be able to get signal and data. *If you have trouble getting 3G/HSPA+ data, try setting the APN to your carrier’s settings although it should set automatically.
I did try this using 4.1.2 but Step 7 was missing.
I then updated back to 4.3 using Kies on the laptop and then CF-Root again through Odin on my computer. Fixing Knox by re downloading SuperSU and running that.
One SIM unlocked phone.
I then used Titanium to freeze all the Samsung and Google stuff I didn't want and also froze Knox.
MY phone is running stable and good. Auto update though says it has been modified so now it will not OTA. Which isn't a bad thing.
Thank you to the respective developers of the software I used.
I hope this helps others.
BorgCymru said:
How to SIM unlock and/or roll back firmware on Samsung Note 2 N7105.
This is how I did it. It worked for me. That's all I can say. It may or may not work for you. I'm no 'expert' so I can't answer any tech question. I found this by trial and error. None fatal. ( So far) I will take it for granted you know how to Root and use Odin. I'm also assuming you have installed the Samsung USB Drivers.
http://uploaded.net/file/xdloq4jw
If you are using one machine to do this remember to disable Kies before using Odin.
My phone was updated to 4.3 using Kies. I did this on my laptop as I didn't want Kies messing up anything on my computer that I was going to use for the rest of the process.
So stating with a stock phone.
Using Odin
http://uploaded.net/file/o2xcp01n
I rooted my Phone with
CF-Root
http://download.chainfire.eu/255/CF-Root/CF-Auto-Root/CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip
I then downloaded SuperSu from the market and ran that. It runs a fix to stop Knox.
I then installed ES File Explorer from the market.
Then I downloaded My Phone Explorer. I like this program and use it a lot.
http://www.fjsoft.at/en/
Using ES I backed up my EFS folder to my Sd Card
Using MyPhoneExplorer I backed it up again to my computer.
Better safe than sorry.
I then used Odin again to install the 4.1.1 Firmware.
I got it from here. There's 4.1.2 there as well for those that asked.
http://www.sammobile.com/firmwares/1/?model=GT-N7105&pcode=EVR#firmware
I then installed 4.1.1 by unzipping the file and using Odin.
I then use CF-Root again.
Using the *#Codes as below
Step 1. Insert a SIM on your Note 2, you should find the familiar “SIM network unlock PIN” window.
Step 2. Dial “*#197328640#” on your Note 2 to enter special menus.
Step 3. Choose “UMTS”.
Step 4. Next choose “Debug screen”.
Step 5. Choose “Phone Control”.
Step 6. Choose “Network Lock”.
Step 7. Choose “Perso SHA256 OFF” and wait about 30 seconds.
Step 8. Press the Menu button then choose “Back”.
Step 9. Choose “NW Lock NV Data Initiallize” and wait about 1 minute. *Then reboot your Note 2.
Step 10. Once rebooted, you should no longer get the Network Lock window any more and you should be able to get signal and data. *If you have trouble getting 3G/HSPA+ data, try setting the APN to your carrier’s settings although it should set automatically.
I did try this using 4.1.2 but Step 7 was missing.
I then updated back to 4.3 using Kies on the laptop and then CF-Root again through Odin on my computer. Fixing Knox by re downloading SuperSU and running that.
One SIM unlocked phone.
I then used Titanium to freeze all the Samsung and Google stuff I didn't want and also froze Knox.
MY phone is running stable and good. Auto update though says it has been modified so now it will not OTA. Which isn't a bad thing.
Thank you to the respective developers of the software I used.
I hope this helps others.
Click to expand...
Click to collapse
I got the same problem,after updating to 4.3 version my phone asking for Sim network unlock PIN.
You mean flashing 4.1.1 from 4.3 got no failure?
Currently downloading 4.1.1 version..after attempting to flash 4.1.2 it failed in Odin,due to a new bootloader
Edit:
Confirmed I successfully flashed 4.1.1 and successfully unlock network.
Tnx dude!
cz4r3n said:
I got the same problem,after updating to 4.3 version my phone asking for Sim network unlock PIN.
You mean flashing 4.1.1 from 4.3 got no failure?
Currently downloading 4.1.1 version..after attempting to flash 4.1.2 it failed in Odin,due to a new bootloader
Edit:
Confirmed I successfully flashed 4.1.1 and successfully unlock network.
Tnx dude!
Click to expand...
Click to collapse
any update on that process.
would this work on a sgs3 t999 4.3? will downgrading to 4.1.1 result in a brick like on the att i747?
BorgCymru said:
How to SIM unlock and/or roll back firmware on Samsung Note 2 N7105.
Click to expand...
Click to collapse
n0013z said:
would this work on a sgs3 t999 4.3? will downgrading to 4.1.1 result in a brick like on the att i747?
Click to expand...
Click to collapse
Absolutely no idea mate. I only tried it on my phone.
ive been looking for this
im having the same problem and hopefully this fixes it.
but about the updating to 4.3 using Kies, wont it trigger the SIM network Unlock Code again?
Hi, what android PDA did you have before doing the downgrade. I have read some posts that say that you can not downgrade if you have MK4 or later... I have a Galaxy note 2 GT-N7100 and I would like to test what you did with mine, but I'm not sure if its possible
Regards
maggr91 said:
Hi, what android PDA did you have before doing the downgrade. I have read some posts that say that you can not downgrade if you have MK4 or later... I have a Galaxy note 2 GT-N7100 and I would like to test what you did with mine, but I'm not sure if its possible
Regards
Click to expand...
Click to collapse
4.3 and then went back to 4.3
butirog said:
im having the same problem and hopefully this fixes it.
but about the updating to 4.3 using Kies, wont it trigger the SIM network Unlock Code again?
Click to expand...
Click to collapse
It didn't on mine.
It doesn't seem to work on SG Note 2 N7100.
Tried all the 4.1.1 fw from sammobile for all carriers here in PH (Globe, Smart, Sun and Open Line)
The menu code doest lead me to the Perso SHA256.
After the Network Lock menu it says Command don't exist or something like that.
Help me what to do please.
Zyrele said:
It doesn't seem to work on SG Note 2 N7100.
Tried all the 4.1.1 fw from sammobile for all carriers here in PH (Globe, Smart, Sun and Open Line)
The menu code doest lead me to the Perso SHA256.
After the Network Lock menu it says Command don't exist or something like that.
Help me what to do please.
Click to expand...
Click to collapse
All I can comment on is how I did it on mine. I don't have any other phone. Sorry.
Maybe try the UK one that I used. Once it's SIM unlocked you can put a local to you ROM on.
BorgCymru said:
All I can comment on is how I did it on mine. I don't have any other phone. Sorry.
Maybe try the UK one that I used. Once it's SIM unlocked you can put a local to you ROM on.
Click to expand...
Click to collapse
Hi,
I followed the instructions properly. I rooted my 4.3 with CF auto root, and then I tried to flash the 4.1.1 firmware onto my phone.
Now it is stuck at the boot screen, and I'm so shocked because I did everything correctly.
I can still get to "ODIN Mode" by holding volume down, home and power, and it says:
Current Binary: Custom
System Status: Custom
Knox warranty void: 1
What have I done wrong?
Thank you.
help me !
i have a Note 2 N7105.i did the exact steps.on the notification bar, i can see that i have signal, the phone is unlocked, but still, i cant use the network. it says NOT REGISTERED ON NETWORK. what do you think is the problem ?
cz4r3n said:
I got the same problem,after updating to 4.3 version my phone asking for Sim network unlock PIN.
You mean flashing 4.1.1 from 4.3 got no failure?
Currently downloading 4.1.1 version..after attempting to flash 4.1.2 it failed in Odin,due to a new bootloader
Edit:
Confirmed I successfully flashed 4.1.1 and successfully unlock network.
Tnx dude!
Click to expand...
Click to collapse
I must say.... you are my SUPER STAR..... I have search everywhere and looked every corner of the website..... apart for paying around £20 to 40 to unlock the phone from someone... you have made my day.... I have been trying to unloack a phone that I have bought from ebay... it was locked to EE network in UK, your way of downgrading the firmware to 4.1.1 and use the code “*#197328640#” had worked... the phone has been upgraded wot 4.3 Jellybean, and the code does not work at all. However after down graded to 4.1.1 (as you have done) , I was able to use the code “*#197328640#” and unlock the phone, then I upgrade it back to 4.3 and now doing a firmware upgrade to 4.4..... the network block has ceased... so I guess the phone is now completely utterly unlocked forever....REALLY Thanks to your logical trial and error...
I must say, it took me some trial and error to reinstall the stock ROM, whick I had to use Philz recovery to completely clean up the device before I reinstall the stock rom.....
Any thanks again, and when I get a chance, I'll post my steps which had worked.
Cheers Mate,
Dave
Am glad to hear that
works great
Big thanks to BorgCymru for the how-to.
Just got a n7105 that was locked on EE/Orange (UK) that had KitKat 4.4.2 installed. Followed all the instructions but used cwmrecovery (to make backup rom) and it worked great for me. Tested with tesco, 3, o2 sim and all work.
Only thing to add that after installing firmware 4.1.1, the phone went to reboot but the screen became locked on the 'Samsung' logo. I removed the battery and booted into recovery to wipe partition and wipe cache. Rebooted and all was fine.
i been having issues unlocking with running 4.4.2 indeed to downgrade was the correct step, i am now unlocked
I know you posted the original post a while back, however I purchased a note 2 7105t off eBay and it was locked to Vodafone Australia. I actually got a code off their unlocking site and of course it did not work. I then contacted their customer service and waited 4 days for a call back with a unlock code and master reset code, once again did not work and I was told to take it to a Vodafone shop and they will send it away. One again, brick wall, as the shop said, "have you a proof of purchase from Vodafone". Nope I do not so they refused to send away and told me I was,"stuck with Vodafone".
Now I want to thank you for assisting me in unlocking my galaxy note N7105T 4.2.2 with your information. It worked like a charm.
The only question I have is if I now put an update firmware from 4.1.1 will the lock come back on? I see here a couple of members said they were fine, can I get verification on this please.
Hi Tamate. Once you unlocked it is permanent.
vadimo said:
Hi Tamate. Once you unlocked it is permanent.
Click to expand...
Click to collapse
No so... Did that way back, and last it while travelling, it locked itself! Still trying to find a way to unlock it (I'm now on Marshmallow!) Afraid downgrade back to 4.1.1 will do more damage (bricking the phone for good!)
BTW, how can I tell if my bootloader ever got upgraded?
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/
absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.
GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!
absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.
Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649
Check for OTA Update in your settings.
Is it Lollipop?
I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
Update the Software for the Samsung Galaxy Note II (i317)
Update summary
AT&T released a new software update for the Samsung Galaxy Note 2 (SGH-i317) via Firmware Over the Air (FOTA) over Wi-Fi on November 11, 2014.
Software Update Includes
Android OS Enhancements
User-Initiated Software Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
Tap Software update.
Tap Check for updates, and then follow the subsequent prompts.
Verifying the Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
The following information displays:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Kernel version: 3.0.31-1728680 [email protected] #1 Wed Oct 1 22:38:36 KST 2014
Build number: KOT49H.I317UCUCNJ1
File size: 93.2MB
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?
keplenk said:
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?
Click to expand...
Click to collapse
I wouldn't. I just posted this in the other thread about the OTA:
a042349 said:
Same thing happened to me. Rooted but otherwise stock GN2. Got the update, rebooted and it got stuck at the boot logo. I tried everything. Flashed CWM, then tried a couple different ROM's. Then went to TWRP recovery, and tried the Team Elektron ROM, that got a little farther, boot logo with sound, but it still hung. Tried a modem update, and even the bootloader - nothing worked.
Luckily I had just bought mine ($300 on Amazon right now) so I just sent it back as defective and ordered a new one. Gonna be real careful of the ATT update and maybe even skip it and go right to a custom ROM.
Click to expand...
Click to collapse
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
kabinoff said:
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
Click to expand...
Click to collapse
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
melvinaury said:
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
actually flashed CF with Odin and it worked.
kabinoff said:
actually flashed CF with Odin and it worked.
Click to expand...
Click to collapse
Did it really work?
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
toshik1 said:
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
Click to expand...
Click to collapse
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
Zen Arcade said:
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
Click to expand...
Click to collapse
Yes the SIM card has normal active service on it.
Other reasons OTA won't work:
1 - Location (if you are not in an area where OTA updates are provided, then...
)
2 - AT&T Update apk disabled on phones (seems unlikely that this would be the case on two phones but a factory reset might clear this as it is set on the data side)
3 - Identity issues (could be any number of things related to IMEI, efs partition scrambling, etc - just spitballing)
As far as suggestions go, I'd say try a factory reset and clear cache from recovery. If that doesn't work, maybe go back to AT&T and see if they can figure it out - the phones are stock and it's their OTA process. If that doesn't work, you can pursue the path I suggested previously - same firmware update, minus the script that pushes stock recovery every time you boot. You will trip the knox flag though...only an issue for warranty repair really. Others here have intentially or unitentionally received the NJ1 OTA with the knox flag tripped on their phones.
DroidTuner said:
I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
Click to expand...
Click to collapse
Which process did you freeze?
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5
toshik1 said:
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5
Click to expand...
Click to collapse
Glad to hear it. Wait a day (or disable network time and the set the time on the phone forward at least a day) and try again - you should get NJ1. (If that's what you want). Approx. 93MB security and minor enhancement update.
Just to follow-up - it took the second update with T-Mobile SIM card even without waiting for 24 hours.
I guess in order to take the updates the phone's IMEI MUST re-register on AT&T network with the valid AT&T SIM card first.
It's now I317UCUCNJ1
Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.
The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/
I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.
Hi. A few months ago I received a phone for my daughter from my mom. I reset the phone back to factory settings and it's working fine. I had to reset it back to factory again after locking myself out recently but other than that there hasn't been any issues until now. I picked up an activity tracker for my daughter recently and it wasn't connecting to the phone like it should even though it was listed as a compatible device.
Turns out the phone is at Android 4.1.1 and when I try to update it OTA it says there are no updates to download. So I tried updating through Kies and it isn't connecting the phone. At this time I started to do some more research.
The knox counter is at 2 and the device status is modified, which I have never rooted the phone and my mother can't even set up her wifi printer and most certainly can't root a phone. I installed triangle away but the phone needs to be rooted in order to do it's magic.
Do I need to root the phone in order to get the knox counter back to 0? Will this put the phone back where I can get android updates for it? I don't know where to start.
Boot into download mode. Do you see anything about warranty bit? If you do, the updates are working because it sounds like the phone has a stock 4.1.1 rom on a 4.3 or newer bootloader.
sarie15 said:
Hi. A few months ago I received a phone for my daughter from my mom. I reset the phone back to factory settings and it's working fine. I had to reset it back to factory again after locking myself out recently but other than that there hasn't been any issues until now. I picked up an activity tracker for my daughter recently and it wasn't connecting to the phone like it should even though it was listed as a compatible device.
Turns out the phone is at Android 4.1.1 and when I try to update it OTA it says there are no updates to download. So I tried updating through Kies and it isn't connecting the phone. At this time I started to do some more research.
The knox counter is at 2 and the device status is modified, which I have never rooted the phone and my mother can't even set up her wifi printer and most certainly can't root a phone. I installed triangle away but the phone needs to be rooted in order to do it's magic.
Do I need to root the phone in order to get the knox counter back to 0? Will this put the phone back where I can get android updates for it? I don't know where to start.
Click to expand...
Click to collapse
If you would to reset the knox counter to 0x0... yes, you have firstly to root your phone, then install triangle away.
delete
Knox cannot be reset to 0x0 once it has been changed to 0x1.
Since the word "modified" appears in download mode, this leads me to conclude that the phone may be rooted and cannot receive ota updates.
It is strange that the phone is running 4.1.1 with Knox as Knox was not introduced until 4.3.
Before flashing anything, you need to confirm the phone's current bootloader and modem.
audit13 said:
Knox cannot be reset to 0x0 once it has been changed to 0x1.
Since the word "modified" appears in download mode, this leads me to conclude that the phone may be rooted and cannot receive ota updates.
It is strange that the phone is running 4.1.1 with Knox as Knox was not introduced until 4.3.
Before flashing anything, you need to confirm the phone's current bootloader and modem.
Click to expand...
Click to collapse
How do I confirm the bootloader and modem? I literally am learning all the language and how all of this works as I go. All I know is I have a phone that is running 4.1.1 and won't update and when I went to the download odis (I think that's what it is called) said it was tripped 2 times where I was supposed to read the knox number.
I ran to the mobile store it's connected to and they said the T Mobile Galaxy S3 phone that I-Wireless puts out was never given an update past 4.1.1 Not sure how true that is. If that's the case, I probably need to root the phone anyway to force an update (Is that what I would need to do to get it at least to 4.3?
there is an app in the playstore called samsung info. download it and it should tell you bootloader and modem.
pretty sure it is true that 4.1.1 was the last.
heres the link to the xda thread , which of course will lead you to the playstore ; but will tell more detail about the app :
http://forum.xda-developers.com/showthread.php?t=2609045
[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
Bootlegger version: T999UVDLJA
Modem Board: MSM8260A
Some other info that might help
Root Existence: No
Latest Firmware: Not Found
Knox Warranty Void: Warranty bit not found
Try flashing the stock lja firmware from here: http://www.sammobile.com/firmwares/database/SGH-T999/
way way off topic. @audit13 , is your avatar your cat & is its name audit13.
[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
Avatar is a cat named Arthur.
I've never flashed something. Sorry if I ask a hundred questions as I go through this.
So you want me to flash the 4.1.1 that's already on the phone? Is that correct? Can I ask why? (I'm just wanting to know the meaning behind the action so understand what your thought process is so I can understand for next time.)
Just follow the directions underneath?
Is this what we're doing?
[GUIDE] How-To Completely Unroot Your Galaxy SIII |Zero Flash Counter|"Normal" Status http://forum.xda-developers.com/showthread.php?t=2136921
if i'm guessing right about what @audit13 & @ arthur (lol) are asking you to do is flash that firmware since the samsung info app said "firmware not found".
you might be confusing firmware version with android version. you say your on 4.1.1 which is the android version.
also if i'm not mistaken that firmware will match your bootloader which is a good thing.
[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]
Ah! That makes sense. In the process of it now. We'll see what happens and if I'm successful with it.
Success. It has auto updated to Android 4.3 after this. Thanks for your help.
good to hear.
that @ arthur (a.k.a. @audit13) knows his androids/tech/uhh...stuff.:good:
[tp_noparse]W2NlbnRlcl1baW1nXWH0dHBzOi8vZGwuZHJvcGJveHVzZXJjb25OZW50LmNvbS91LzlzNjl3OTl3L0ltYWdlcy9TaWduYXR1cmVzL3ZhcmlvdXMvcmRiLmdpZlsvaW1nXVsvY2VudGVyXQ==[/tp_noparse]