Related
I tried to downgrade the ota 4.3 update, i didnt know you couldnt upgrade..
Now im stuck at the Firmware upgrade encountered an issue screen..
Kies 2 will start saying "connecting" but thats as far as it gets.. then Kies 3 says that the device thats plugged in isnt compatible with kies 3.
IDK what to do xD
Johnnysauur said:
I tried to downgrade the ota 4.3 update, i didnt know you couldnt upgrade..
Now im stuck at the Firmware upgrade encountered an issue screen..
Kies 2 will start saying "connecting" but thats as far as it gets.. then Kies 3 says that the device thats plugged in isnt compatible with kies 3.
IDK what to do xD
Click to expand...
Click to collapse
Place your cell in Download mode, then use Odin to insert the official android 4.3 package.
andyistic said:
Place your cell in Download mode, then use Odin to insert the official android 4.3 package.
Click to expand...
Click to collapse
You wouldn't happen to have a dl link for official would you?
Johnnysauur said:
You wouldn't happen to have a dl link for official would you?
Click to expand...
Click to collapse
Start up Kies (no cellphone connected), then go to Tools / Firmware Upgrade
It will ask you for the model number, so put that in.
Then it will ask you for either the serial number or MEID, so put that in, too.
Then it should download a big-ass android package (around 1.5 gigabytes).
After the package is decrypted, copy it from the temp directory to some safe place on your local hard drive.
Use Odin in Download Mode to install this package.
The package should end with .tar.md5
If you accepted the official OTA 4.3 update, and you tried to revert your bootloader back to before KNOX... you're lucky since that should have completely hard-bricked your phone. I think, given to your description and assuming you've got the KNOX bootloader now, your best bet would be to try to repair the install by doing what I think is referred to as a "dirty" flash... which basically means you don't format or wipe your data before you attempt another installation of the same version.
I don't know for sure though, so don't take my word without someone who knows more verifying or refuting this.
Good luck, I'll be interested in seeing what you wind up working out.
-Zen
FallenZen said:
If you accepted the official OTA 4.3 update, and you tried to revert your bootloader back to before KNOX... you're lucky since that should have completely hard-bricked your phone. I think, given to your description and assuming you've got the KNOX bootloader now, your best bet would be to try to repair the install by doing what I think is referred to as a "dirty" flash... which basically means you don't format or wipe your data before you attempt another installation of the same version.
I don't know for sure though, so don't take my word without someone who knows more verifying or refuting this.
Good luck, I'll be interested in seeing what you wind up working out.
-Zen
Click to expand...
Click to collapse
I downloaded the mk3 modem, and flashed it in odin, it fixed the softbrick. i rooted it with cf-auto and it went through no issue. disabled knox no problem, and now got cwm working.
Hello all,
I had my s3 rooted, and unlocked with stock ROM. And I think I've also freeze my "AT&T Software Update" a while ago, so it was stuck on 4.1.1. Now, I would like to update my firmware to 4.3 or newer, and stay stock. I tried to go to the setting and select Software update, but nothing happen. I've also tried to find that "AT&T Software Update" in Titanium Pro, but have no result. Can anyone point me to the right direction on how I can do it?
Thanks
You can't update if you're rooted
So in order to update you need to unroot or just download the 4.3 firmware and flash thru Odin
Sent from my SAMSUNG-SGH-I747 using Tapatalk
bennyc1213 said:
Hello all,
I had my s3 rooted, and unlocked with stock ROM. And I think I've also freeze my "AT&T Software Update" a while ago, so it was stuck on 4.1.1. Now, I would like to update my firmware to 4.3 or newer, and stay stock. I tried to go to the setting and select Software update, but nothing happen. I've also tried to find that "AT&T Software Update" in Titanium Pro, but have no result. Can anyone point me to the right direction on how I can do it?
Thanks
Click to expand...
Click to collapse
You can do a 2-step manual update from 4.1.1 to 4.1.2 and then to 4.3. Please go to page 300 of the thread below to see my steers to another user on exactly the same issue.
http://forum.xda-developers.com/showthread.php?t=1849043&page=300
Larry2999 said:
You can do a 2-step manual update from 4.1.1 to 4.1.2 and then to 4.3. Please go to page 300 of the thread below to see my steers to another user on exactly the same issue.
http://forum.xda-developers.com/showthread.php?t=1849043&page=300
Click to expand...
Click to collapse
Thanks Larry. That's a really helpful information. One question though, if I do these manual update, am I expecting all data will be gone? Or will it simply update the firmware, and leave everything alone?
Thanks again
Updating to a stock 4.3 ROM will install Knox too. Rooting will trip the Knox counter. If you have no warranty on your phone, this will not be a problem.
lo
You should also know that Knox can sometimes interfere with obtaining root. Once you're on a 4.3 bootloader, you cannot downgrade the bootloader.
bennyc1213 said:
Thanks Larry. That's a really helpful information. One question though, if I do these manual update, am I expecting all data will be gone? Or will it simply update the firmware, and leave everything alone?
Thanks again
Click to expand...
Click to collapse
I should have mentioned that earlier. Yes, updating can affect all your data so I would advise you first back up your data. You can install Samsung Kies on your phone and use this to back up your data, apps and everything else you want and restore afterwards. Please see also Audit's post. Updating to the latest firmware which is 4.3 could be a one-way trip and will install Knox security on your phone. The update will unroot your phone, restore to factory settings and install stock recovery. If you decide to re-root afterwards, however, there are several ways of doing this.
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
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.
Hey,
Still a bit of a noob to the whole rooting process and navigating XDA forums, so I'm having trouble finding the information *I think* I should be looking for. Basically, my phone's just begun crashing periodically, multiple times a day: anything from Camera, Process System, Touchwiz Home Launcher, or Samsung Apps have "stopped working" / "not responding" before. Of course, my phone's warranty has expired, but my contract isn't up so an AT&T Store wont re-image it for me :crying:
Even I can tell, at this point, that it's either my OS that's failing, or it's my hardware. I figured the easiest way to test this would be to put some stable CyanogenMod on it.
The information I'm looking for is: "is this possible?"
AT&T Samsung Galaxy Note 4
SM N910A UCU2DOI2
Currently @ 5.1.1
Thanks for reading,
~Vita.
No it is NOT possible to use any form of custom firmware or to root this device. It has a locked bootloader that has yet to be cracked open and the future of that happening os very bleak to non existant.
As for reimaging the device go to the note 4 at&t general section on the forum and read up on using odin and the 5.1.1 image posted there it will wipe the phone and format yhe system and data partitions and reinstall it like a new phone just like at&t would do or the manufacturer if you sent it to them.
Good luck
Thanks for the response.
Sorry for the dumb question, but isn't Odin able to flash any firmware onto a device? The "locked bootloader" means that only the stock OS may be reinstalled? Why is this...
Also, it seems unlock progress is being made on the N910V. Maybe hope?
Thanks for mentioning Odin, I'll try re-imaging the phone.
~Vita.
Ricovita said:
Thanks for the response.
Sorry for the dumb question, but isn't Odin able to flash any firmware onto a device? The "locked bootloader" means that only the stock OS may be reinstalled? Why is this...
Also, it seems unlock progress is being made on the N910V. Maybe hope?
Thanks for mentioning Odin, I'll try re-imaging the phone.
~Vita.
Click to expand...
Click to collapse
Well the problem is the kernel the bootloader prevents the devs from using an unsecure kernel (one not created and signed by at&t) on the phone if one is used the phone stops boot and says it is an unsecure non at&t kernel and to take thenphone to at&t store.
Odin can only write the firmware versiom that is currently on this phone in this case it is 5.1.1 if you flash any other note 4 versoin such as 4.2.2 it will brick.
Sm-910a flash example
Update ver Official at&t 5.1.1 / currently on phone 5.0.1 or 5.1.1 = good
Update ver (downgrade)oficcial at&t 4.2.2 / currently on phone 5.0.1 or 5.1.1 = brick not good or odin fail
Update from another carrier such as tmobile or verizon for 910t 910v 910g = fail (do not attempt)
Until oir boot loader is unlocked there is nothing we can do to mod or use custom firmware on this phone any attempt leads to a brick requiring using odin to re-flash the latest firmware (5.1.1 at this time) in order to make the phone functional again.
giga8547 said:
Until oir boot loader is unlocked there is nothing we can do to mod or use custom firmware on this phone any attempt leads to a brick requiring using odin to re-flash the latest firmware (5.1.1 at this time) in order to make the phone functional again.
Click to expand...
Click to collapse
So from what I understand, I could use Odin to flash the 4 files which correspond to the specific AT&T 5.1.1 SM-901A version of my phone (which is exactly what I have) to re-image the device and make it functional again. The problem is, I cannot find these devices on sammobile D:
Could someone direct me to these files? Or are they not out because AT&T sucks? Or, what.
~Vita.
Ricovita said:
So from what I understand, I could use Odin to flash the 4 files which correspond to the specific AT&T 5.1.1 SM-901A version of my phone (which is exactly what I have) to re-image the device and make it functional again. The problem is, I cannot find these devices on sammobile D:
Could someone direct me to these files? Or are they not out because AT&T sucks? Or, what.
~Vita.
Click to expand...
Click to collapse
Look in odin files in progress thread.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Is it possible to downdraft from 5.1.1 to 5.0.1
firebird7880 said:
Is it possible to downdraft from 5.1.1 to 5.0.1
Click to expand...
Click to collapse
I think so, I don't know for sure but we've been able to Odin from various 5.0 Lollipop releases back to KitKat so should be fine.
downgrading from 5.1.1 or 5.0.1 to kitkat is possible but with many many problem but form 5.1.1 to 5.0.1 i don't know maybe phone will stuck or boot loop
thanks finitetime for your reply
other question are there any news about root for 5.1.1 n910a
help
my att note 4 is unlocked and it still won't let me install custom rom's
mouseman1 said:
my att note 4 is unlocked and it still won't let me install custom rom's
Click to expand...
Click to collapse
I am sure that you are referring to a sim unlock. A sim unlock and unlocked bootloader are two completely different entities. To flash a custom rom you will need to have your bootloader unlocked, which is something that a few of us are currently working on. Until then, no custom roms can be flashed on the att variant Note 4s. Take care
the boot loader says Qualcom secure boot : disabled ?
in the boot loader screen ?
mouseman1 said:
my att note 4 is unlocked and it still won't let me install custom rom's
Click to expand...
Click to collapse
Your phone is SIM UNLOCKED which has NOTHING to do with root, bootloader, or custom roms.
Sent from my SAMSUNG-SM-N910A using Tapatalk
mouseman1 said:
the boot loader says Qualcom secure boot : disabled ?
in the boot loader screen ?
Click to expand...
Click to collapse
Sorry, was off the forum for the weekend. Spexwood was correct, that is sim unlock. Qualcom is for the sim IE network. Take care.
Root is possible btw
Root is possible if youre willing to dedicate 10-30 hours of repititive root fails
How?
Press Buttons said:
Root is possible if youre willing to dedicate 10-30 hours of repititive root fails
Click to expand...
Click to collapse
How is root possible? What's the process ?