Related
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 am not very much familiar with all intricacies of Android system but i have played around rooting and putting customer firmwares on few devices.
I have AT&T Galaxy S3 with following detals:
Baseband: I747UCUEMJB
Version: 4.3
I had the device rooted in the past but recently un-rooted it and reset the flash counter as well and did factory reset. Did all that since i wanted to use ISIS and couldn't make it work on a rooted S3. Seems it used to work before till they updated ISIS app to patch it.
Now AT&T got 4.4 update and my phone detects it, downloads it but while installing fails at 32%. I have seen many threads where people faced similar issues due to their phones being rooted. Seems something on my phone didn't reset to default.
I found one post which mentions that i can download UCUEMJB_to_UCUFNE4_Firmware_update.zip and load it to phone using TWRP. As i understand, this will update the baseband but android version still remains at 4.3 (?). Is that the path i should be looking for or i am shooting in wrong direction? I want to stay on default firmware since i like to use ISIS till they keep running those cashback promos
Would appreciate some feedback.
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
DocHoliday77 said:
Download MJB firmware (thread in General) and flash with Odin. You can stop there or try the ota again.
Click to expand...
Click to collapse
Thanks for the reply.
Just to confirm so that i don't mess up, i will apply the following(is modem same as firmware?) and then try OTA.
I747UCUEMJB: modem_CWM_I747UCUEMJB.zip
No. The modem is only one part of the firmware. Firmware includes bootloaders, kernel, system, modem and more.
hey guys I'm on 4.2.2 still. Rooted it and deleted the galaxy walking app, so haven't been able to do legit update, and with working alot just haven't fooled with it. Anyway I'm off and have time, want to come up to kitkat, am I not able to update my LTE radio? I'm reading and searching before turning to asking, but all I'm seeing is if I update it my sound will act up. Am I stuck on an old radio now? Was hoping for improved signal, can I go stock, update and reroot and everything will be current?? Anyway any help is appreciated.
If you don't care about tripping Knox counter, just flash the NB4 firmware with Odin and you'll be good.. I recommend fenny's fixed firmware
Edit: well it will only trip if you flash custom recovery or kernel, other than that there is root method without tripping if you plan to stay stock
serio22 said:
If you don't care about tripping Knox counter, just flash the NB4 firmware with Odin and you'll be good.. I recommend fenny's fixed firmware
Edit: well it will only trip if you flash custom recovery or kernel, other than that there is root method without tripping if you plan to stay stock
Click to expand...
Click to collapse
im not staying stock, just want the updated lte radio on it. thinking of going lg g3 since sammy become such a pain in the ass. I've flashed stock and am updating official kitkat now, i guess that will update my modem and lte radio also, i'll reroot after that and throw something on there
If you are updating officially there shouldn't be a reason to manually update anything
i was just trying to save time, my home internet is crappy ( 100.00 bucks a month for 5mb, more like 1-3 mb) and you have to use wireless to update. I'm on kit now, abut to root and find a rom
sleekgreek said:
i was just trying to save time, my home internet is crappy ( 100.00 bucks a month for 5mb, more like 1-3 mb) and you have to use wireless to update. I'm on kit now, abut to root and find a rom
Click to expand...
Click to collapse
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.
lordcheeto03 said:
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.
Click to expand...
Click to collapse
i've been searching here for years on everything. Unless you stay in the loop everything is just cluttered. Even rooting, I'm looking and reading threads from pre 4.4.2 where chainfire link was last updated in 2013, it sucks searching here. And I thank you guys for the help. I'm rooted now and didnt want to ota, but everything I found to read said I could update the modem but not the LTE radio without sound issues... I must of missed something. LOL, I had a ton of tabs open from searches before posting. Been rooting since iden on nextels in early 2000's so it's just basic info I need thats hard to find here , tons of threads I guess. Anyway lets a get rom on this thing..
sleekgreek said:
Unless you stay in the loop everything is just cluttered. Even rooting
Click to expand...
Click to collapse
I totally agree and understand. I've pretty much been tinkering around the S4 forums since a few weeks after release (before I even purchased my S4) and have followed pretty well everything from square one so it's pretty easy to remember THAT I've read something but not remember WHERE I read it... Looking back through the Q&A and General threads, I couldn't imagine just now getting into the S4.
lordcheeto03 said:
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.
Click to expand...
Click to collapse
I would be interested in that thread... I have updated my GSM modem (modem.bin) to NB4 but as I understood it, the LTE part is tied to the bootloader. So, those of us with MDL have to retain the MDL LTE radio. If it is possible to update the LTE radio, without the sound/wifi problems, and retain MDL bootloader and thus no Knox, I'd love a link!
Frankenscript said:
I would be interested in that thread... I have updated my GSM modem (modem.bin) to NB4 but as I understood it, the LTE part is tied to the bootloader. So, those of us with MDL have to retain the MDL LTE radio. If it is possible to update the LTE radio, without the sound/wifi problems, and retain MDL bootloader and thus no Knox, I'd love a link!
Click to expand...
Click to collapse
Ahh, you got me on that one. It didn't even register to me that the LTE modem is unaffected by that method. My apologies.
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.
Hello all, it's been a while since I understood the S3 firmware situation but I appreciate the advice.
I recently received a ATT S3 which is at OTA firmware 4.3 (MJB) and carrier SIM unlocked. I would like to arrive at CM12 with Philz recovery. I would appreciate suggestions on my best firmware upgrade route given the situation.
I understand the bootloader has been Knox'ed, so I may only upgrade (never downgrade) my Bootloader. However, I do not know the implications of KNOX on modem updates. I hear flashing a custom Recovery or Firmware will cause Knox to go to 0x1. Is it true or false that a tripped Knox (0x1) will PREVENT any further Modem or Bootloader updates? If this is true, it means I cannot use the upgraded 4.4.2 OTA modem (or later updates, if they are ever made) if I attempt flashing Cyanogenmod now (at 4.3 MJB). Is the new 4.4.2 modem worth it? Can 4.4.2 OTA still be rooted/custom recovery'd?
I am considering inserting an ATT SIM and allowing the the 4.4.2 OTA update to occur. Then I plan to use TowelRoot to apply Root from the phone itself. Then using EZ-Recovery (I used this on my VZW S3? But current seems to be Flashify?), I plan to flash Philz custom recovery from the phone itself. Then I plan to reboot into custom recovery and Clean install CM12 from the phone itself.
Does my planned approach have any issues? And what is this I hear about using Terminal commands to unlock the AWS1700 band (T-Mobile) semi-permanently? (I have a SGH-i747, not 747M. Posts seems to imply it only works semi-permanently on 747M?) I would like to keep my options open if possible. And is the ATT Knox 4.3 (MJB) firmware bootloader-locked? I was under the impressions all ATT S3 (d2att) were bootloader unlocked. (Answer here?: http://forum.xda-developers.com/galaxy-s3-att/help/bootloader-locked-t2990174 )
Thanks again for offering your opinions, there are many ways to skin a cat but I've been having a hard time matching the old methods I am aware of with the new tools. Thank you.
Edit: This thread has been helping explain the bootloader/modem pairing issues I can't understand. I am just unsure if newer = better.
http://forum.xda-developers.com/showpost.php?p=61782091&postcount=3
Regarding Stagefright bug, which is why I want to update to CM:
http://forum.xda-developers.com/showpost.php?p=62116470&postcount=6
My suggestion would be to run ota updates until you are running the latest modem and bootloader.
Flash Philz using Odin, perform a full wipe, install rom, install gapps.
Knox will not prevent installing roms, recovery, modems, or bootloader. Once on the latest kit kat, there is no need to install alternative bootloaders or b modems.
Hi, I doubt towelroot would work, as it's most likely been patched. (the exploit towelroot used). I believe the 0x1 is the warranty bit. I wouldn't think stock OTA update wouldn't be possible after, however. I'm not the one to verify this I'm on the I747M and I know the ATT stock images for the later releases are not available. So I cannot advise you there.
I'd say either use odin to flash cf autoroot.
or odin to flash recovery then supersu zip install to gain root.
I did search for ways without tripping the counter but like usual I was too late to the party to use towel root. But my warranty is out anyways.
Thank you for the insight. I think I will do just that, there are some ODIN-flashable 4.4.2 images provided by a helpful member here, but I do not want to do them out-of-order and potentially brick the device.
Since this phone has been completely abandoned by Samsung and ATT, I see no harm in voiding the Knox bit. If any applications complain, I can always use Xposed to fake it I suppose.
I will keep my fingers crossed that Towelroot will work. The last update ATT permitted was back in 2014, so there is a slim chance it may work. I will see when I do the OTA update.
Thank you! :good:
Hey all, as a followup I used OTA updates on stock combined with the procedure described here to achieve what I wanted. Knox has been tripped, of course.
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/
Some caveats:
I had to use a weird debug menu to get the unlock code ATT gave me to work. If I tried it as instructed by ATT as soon as the phone turned on it rejected the code. The #* instructions in the first post here worked and I was able to use the code ATT provided.
https://forums.att.com/t5/Samsung-D...code-for-galaxy-s3-does-not-work/td-p/3963728
I had to pull the battery after ODIN said "PASS" (as described in the video) to prevent the custom recovery from immediately being reverted to stock on reboot. When running SuperSU for the first time I had to try once, get stuck, then reboot and try again to "Remove Knox" properly.
I had to visit TWRP's site to download the newest Odin flashable TWRP TAR. The TWRP Installer Play Store app did not work when I had the CWM installed that was linked in the tutorial. The reason for needing TWRP is that CWM did not allow proper installation of the CM12.1 TK_Gapps "stock" version. I suggest anyone else in my position simply use TWRP Odin flashable TAR from the get-go. Also, simply hold down the Recovery mode button combo as soon as Odin forces a reboot rather than pull the battery.
For the record, Google Wallet Tap-And-Pay does not show up as an option in the app on the latest CM12.1 nightly (8-7-2015). Everything else seems to work. (CM12.1 for d2att recommends having the NJ1 bootloader/modem combo anyway.)
The TowelRoot method would have worked if I stopped at the 4.4.2 NE4 OTA update.... and theoretically would have preserved Knox. (At least until I flashed a custom recovery.) The OTA updates I received were a really big 4.3 MJB => 4.4.2 NE4 update (~500mb) then another, very small 4.4.2 NE4 => 4.4.2 MJ1 update (~20mb). I set my phone's clock ahead 24 hours to force the ability to immediately update.
Thank you @audit13 and @serathe for the tips. I hope this is instructional for anyone else in my position.