Related
Hi all
I just have a massive question. I own the n7105 with the latest of omnirom running on it, but I would want to upgrade to the new official 4.4 firmware released.
I tried installing the deknoxed rom:
http://forum.xda-developers.com/showthread.php?t=2747783
But after I get to the system, I have no wifi, so I'm guessing its a bootloader issue. I have looked around for a good 3 or 4 days now and I'm close to giving up on any info that I find, I would really want to know how to upgrade the bootloader.
Also, the warranty on my phone has already run out so i do not care if knox is triggered.
If anyone could help me with this I would be very thankful
Flashing a stock rom (Sammobile.com) will upgrade your bootloader. Choose a 4.3 or greater rom. Remember: this cannot be undone.
Samsung are obliged to release kernel source so eventually we'll get a wifi fix anyway.
Firstly, I am not new to flashing or searching on XDA! I have installed custom roms/recoveries on at least 10 different android devices and have been a member here for some time. I'd like to think that I have helped more people out than I've asked for help....
but my new (to me) Note 2 has me stumped!!!
I have recently traded in my much loved Note 1 (running a rock solid AOKP KIT KAT rom) for a SGHi1317m (I believe originally from Rogers). It was unlocked and I am able to get full LTE service from my carrier (Bell Mobility) after setting the APN.
I originally upgraded in order to get greater functionality out of my Gear 1 smartwatch (better battery life with BT 4.0, among other benefits)
24 hours in and I am dieing to get back to some form of KitKat! The question is How?
I have searched this forum and have come away with the impression that because of the different variations on this phone, Knox, differing bootloaders with differing recoveries, there are many ways to brick this phone!!
I have already found out that one cannot easily update the recovery via the simple solutions offered on the playstore for CWM or TWRP. I am familiar with ODIN and have multiple versions of it running on different laptops in my house ready to try. The question is which package will give me a recovery that will allow me to flash roms and persist through a reboot?
According to my phone info, I am on bootloader i317MVLUCMK5 ( a version I have not seen in any of the tutorials) My KNOX counter reads 0x0 but when I try to search for updates ( I am presently on stock android 4.3 rogers), it says that I will not receive any as my phone has been modified (i suspect it can tell that the phone is unlocked as I am using a Bell sim in a Rogers phone).
As I have no warranty, and don't really care if my Knox counter is tripped, I am hoping someone can help me get started in flashing this phone.
i think if you look in the cwm thread you'll find instructions. mostly everything i see is a soft brick meaning it just doesnt boot into rom. i suggest cwm as it seems more maintained than twrp, and twrp gave me issues.
download a stock modem because the international roms will overwrite your modem and you'll get no signal bars and need to reflash after a upgrade. check out the n7100 form, sub forum n7105 and look for roms there. this forum is really dead. i'm running international rom nc3 with my at&t mk6 modem. mj5 bootloader because its 4.3 but unlocked from downgrading.
i too didn't care about knox or warranty, but most of the good stock roms have it stripped. i can't find anything as good as 4.3 tw stock roms and the custom roms i've tried seem to have fc's and whatnot.
i also used devil kernel and got tons of fc's so i'm using the stock kernel for now. might try agni. but back on topic your best bet is to try and find cwm odin package for philz touch. really once you get past all the noobs here you find it works just like any other samsung. you can flash a recovery via odin, cf auto root, and you're done.
Hi folks,
I'm the happy owner of a T-Mobile M919 with MDL firmware, GSM modem upgraded to NB4, running Dirty Unicorns ROM (a weekly of 7.8, from August...). DU ROM is awesome but this version has a few quirks that I'd like to exorcise, and mostly I'm just itching to try something different. When (or if) DU goes to Lollipop I'll probably go back to it but I'm feeling like trying something else out for a while, just for a change. At the moment I'm torn between going to Slimkat (I have a tablet on this, works great) or simply the GPE ROM for the S4. Either way I'll probably go with Themer and play around with different themes.
Anyway, my unit is on MDL bootloader (and thus MDL LTE modem). I've had zero "modem issues" so far. But I've heard the latest ones seem to do a better job, so I've thought of doing a firmware upgrade to NH7 (stock) before reflashing the latest TWRP and putting either Slimkat or GPE ROM on.
Doing so of course puts on Knox stuff, which will be tripped when I flash the recovery. But it won't actually mean anything for my use of the device. And I'm the second owner of this thing so I probably can't claim Samsung warranty service anyway, should I need it... (though, on a prior second hand unit, I did get Samsung service, as they weren't very strict in that instance).
I'm caught between the logical side of my brain saying: go to NH7 bootloader... there's literally no downside for you, other than perhaps slightly lower resale value.... and the emotional side of me saying: you've got a knox-free handset... why soil it with knox when you aren't having modem problems?
Can you guys/gals help me decide which way to go? Friday or Saturday after Thanksgiving is probably "flashing day" either way.
Thanks in advance for all your input.
Marc
Frankenscript said:
Hi folks,
I'm the happy owner of a T-Mobile M919 with MDL firmware, GSM modem upgraded to NB4, running Dirty Unicorns ROM (a weekly of 7.8, from August...). DU ROM is awesome but this version has a few quirks that I'd like to exorcise, and mostly I'm just itching to try something different. When (or if) DU goes to Lollipop I'll probably go back to it but I'm feeling like trying something else out for a while, just for a change. At the moment I'm torn between going to Slimkat (I have a tablet on this, works great) or simply the GPE ROM for the S4. Either way I'll probably go with Themer and play around with different themes.
Anyway, my unit is on MDL bootloader (and thus MDL LTE modem). I've had zero "modem issues" so far. But I've heard the latest ones seem to do a better job, so I've thought of doing a firmware upgrade to NH7 (stock) before reflashing the latest TWRP and putting either Slimkat or GPE ROM on.
Doing so of course puts on Knox stuff, which will be tripped when I flash the recovery. But it won't actually mean anything for my use of the device. And I'm the second owner of this thing so I probably can't claim Samsung warranty service anyway, should I need it... (though, on a prior second hand unit, I did get Samsung service, as they weren't very strict in that instance).
I'm caught between the logical side of my brain saying: go to NH7 bootloader... there's literally no downside for you, other than perhaps slightly lower resale value.... and the emotional side of me saying: you've got a knox-free handset... why soil it with knox when you aren't having modem problems?
Can you guys/gals help me decide which way to go? Friday or Saturday after Thanksgiving is probably "flashing day" either way.
Thanks in advance for all your input.
Marc
Click to expand...
Click to collapse
I'd go with the emotional side. If it ain't broke, don't fix it. If you're not having problems with LTE reception, why update? There is literally no real advantage other than POSSIBLY better LTE reception... which you apparently don't actually require. Just my $.02
I think the NH7 bootloader and modem combo works best with an NH7 rom. Since you're not even gonna use that, no real reason to fully update, except for maybe the modem
OK, for now I'll leave my bootloader at MDL. Building up the energy to document current settings that I like and catalog what I need to backup before wipe/new ROM....
Just update it. As you said the stupid Knox warranty doesn't Matter since you're the second owner, but besides that everyone that bought the s4 on mdl your warranty is officially expired.
I bought mine on mdl, didn't give a crap about Knox so tripped it immediately on purpose on mk2, and have seen nothing but data and service improvements with each up.
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,
I know this information is probably available somewhere, but I have spent hours of reading, and still having some trouble getting my head around things. So I will try to be clear here as to what my issues are.
Firstly... I have Samsung Galaxy S-III, SGH-i747M, with virgin mobile canada. It started with android 4.1.2. I wanted to unlock it, and there was a way to do it with 4.1.1 (http://forum.xda-developers.com/showthread.php?t=2176719), so I used odin, with firmwares (found at SamMobile.com I think) to flash a 4.1.1 ROM, did the unlock procedure, and then used odin to flash stock firmware for 4.1.2 again. Seems to have all worked out ok.
Anyway, I want to try some custom roms, like cyanogenmod, as they are purported to improve battery life, speed, clearing off bloatware, giving me more control, etc.
However, I really want to maintain the ability to go back to how it is now, if I don't like the custom roms. (or if I need warranty help, though there's not much of that left).
The main thing that's concerning me is that while I was playing with this phone before, I read in a number of places that if I had updated to Android 4.3 or 4.4.2 when those had become available from my carrier, I would not have been able to downgrade to 4.1.1 (which I needed to be able to do to use the built-in unlock method). This is because of Knox, which would be installed, and gets "tripped." So now I'm scared: if I did that upgrade, I wouldn't have been able to revert; so now, if I flash a CGM ROM, will I also be unable to revert?
I think there are a few pieces of android to sort out in my mind... If I'm not mistaken, there's bootloader, there's recovery, and there's the ROM. Flashing a ROM with Odin apparently would restore recovery and the ROM? But not the bootloader (that's where knox is? though I still don't understand, if an upgrade can modify the bootloader and put knox there, where it wasn't before, shouldn't there be a way to put a pre-knox version back there?)
Oh, there's also EFS, which some say should be backed up before doing anything (though you need to root first, which in my mind counts as doing something before backing it up).
Anyway, please let me know if you can help clarify these issues, thanks!!
There is a lot to cover to address all that you bring up.
Regarding EFS, there are a number of ways to back it up. Use several. This thread is an excellent place to start for more info and several ways to make the backup. I was rooted, so I used A2 and B. I believe you can use A1 without being rooted, probably B as well. Long after that post was written wanam came out with two backup apps available in the PlayStore. One was specifically for EFS, but I do not think it is still supported. The other is a more comprehensive app, both require root.
As a rule, bootloaders and modems are not installed with custom ROMs. If you are flashing a stock ROM from these forums that is installed from within a custom recovery it probably does not install a bootloader and modem either, but read the relevant thread to be certain. Full stock ROMs flashed from with Odin, or Heimdall, almost certainly install a bootloader and modem.
Prior to 4.3 there was an ability to downgrade bootloaders and modems, nor were they required to match - be at the same version. Once you upgrade to the official 4.3 bootloader you can no longer downgrade it. Once you have upgraded to 4.4.x the bootloader and modem versions must always match. If they are mismatched you risk soft bricking your phone at a minimum. For the i747 there was an unofficial 4.3 release; ROM, bootloader, and modem. I do not recall seeing mention of an unofficial release for the i747M, so I will not go into the exceptions on the above the unofficial bootloader/modem introduced.
For TouchWiz ROMs, custom or stock, the bootloader (and modem) version should match or be more current than the ROM Android version. (One of the unofficial 4.3 release exceptions applies here, I make use of it.)
For CyanogenMod, CM based ROMs, AOSP ROMs, and their derivatives the bootloader and modem version can lag behind Android version of the ROM. With your 4.1.2 bootloader and modem you could run the earlier releases of 4.4.x CM and AOSP ROMs. Later in the 4.4.x development, around Oct or Nov 2014 IIRC, I began reading reports of needing to be on 4.3 or later, there were a few said the 4.1.2 firmware still worked for them. For the 5.x.x LP releases of CM and AOSP most report that they must be on a 4.4.x bootloader and modem.
Knox is in the ROM, not the bootloader and modem. It was introduced with the official 4.3 releases. It is not present in CM/AOSP nor most of the custom TW ROMs. It will be present in stock ROMs from official sources or sites like sammobile. Many of the stock ROM images/dumps have Knox disabled, especially those from enewman17, but read to make sure what you are getting.
I don't feel qualified to discuss tripping the Knox counter, I am still on the unofficial 4.3 bootloader, which has not kept me from running 4.4.x ROMs. I am not the only Luddite, but I feel we will all be updating bootloaders and modems due to the Stage Fright bug. I am long out of warranty so there is no loss.
ABOVE ALL, read thoroughly before taking any action. Keep in mind that I am on the i747 and not the i747M as you are, I am not be correct on all comments for your device. @audit13 should be able to clear any gaffs I have made.
@dawgdoc is correct about everything said.
It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.
Ok, starting to feel a bit more comfortable with the whole system and relationships, thanks!
audit13 said:
@dawgdoc is correct about everything said.
It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.
Click to expand...
Click to collapse
Thanks for verifying that. There could have easily been small, but very important, differences in the devices that had slipped my mind since I don't have the i747M.
This is the way xda should be. Good questions from a concerned user & great answers from @dawgdoc. Nice job guys!
canodroid15 said:
This is the way xda should be. Good questions from a concerned user & great answers from @dawgdoc. Nice job guys!
Click to expand...
Click to collapse
I would like to extend similar praise and thanks to @mrrocketdog and @audit13
more uncertainty
Hi,
I'm a lot more experienced now, having rooted (I flashed root66_BMC_I747MVLDMF1 by MrRobinson, since CF-autoroot just made the phone show "booting recovery" then blank screen indefinitely), I backed up EFS by a couple methods, flashed TWRP, did a nandroid backup, and flashed a couple versions of CM. Still a few things I want to clarify though.
Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem. In general, I see a lot of posts simply saying "update the modem." From what you've said though, that will create problems, unless I update the bootloader as well, correct? Just feels like the phrase "update the modem" is said so casually, without also mentioning the bootloader, and the inability to go back.
(an older CM 11 worked with data just fine)
(a big issue is that S3 is over 3 years old, so there are over 3 years of posts, so there's a lot of conflicting information, likely due to different versions, new discoveries, etc. )
I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" There are a lot of "Never update to 4.3 (or above) because of knox!" comments. But also in general, it seems the only real issue with knox is that warranty bit, otherwise it doesn't have too big an impact on our lives? Seems the consensus is that we can still root, install custom roms, and everything else. (Do you know if this remains true with latest bootloaders and modems (OB3 for i747M). There are also "My battery life became way worse after the upgrade" or "more FCs" or other issues, which is a significant concern if my phone which currently comfortably lasts a day starts to not last a day after updating. Though it's likely a small percent noting that, while the quieter majority are fine. Meanwhile, by not updating, we may be missing out on features and security improvements (and maybe actually improved performance). What do you guys think? (I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).
As for updating, I think somewhere one of you suggested the better (or at least safer) way is to use odin to flash stock ROM, then do the OTA updates, or, directly flash the latest stock ROM, rather than trying to flash modems and bootloaders directly?
Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)
Thanks again!
I almost wish I'd just taken the blue pill at the start of all this
For XDA members that are new to rooting, flashing, etc., I always recommend the safest route which is to flash back to a completely stock ROM and just upgrade to the latest bootloader and modem via OTA updates. There's always a risk of something going wrong when flashing anything, be it a custom ROM, recovery, or OTA update.
If the phone still had warranty, I recommend not flashing any non-Samsung software until the warranty has expired. Once expired, flash away
Knox should not interfere with root if supersu is flashed from a custom recovery, regardless of the bootloader. I have used supersu to root the latest s3, s4, Note2, and Note3 ROMs without a problem.
Restoring old nandroid backups should not cause a brick as TWRP does not change the modem or bootloader.
sacrawfo said:
....Still a few things I want to clarify though.
Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem.....
(an older CM 11 worked with data just fine)
I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" ....(I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).
Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)
Click to expand...
Click to collapse
I think the change date for CM11 requiring the newer bootloaders, at least NE4, is Nov 2014. Releases prior to that date would run fine on older bootloaders.
I have since updated to NE4 in order to run ROMs patched with the StageFright fixes, specifically CM11 20150831. Knox isn't installed on this ROM or even the newer custom TouchWiz based ROMs. I am not concerned about Warranty Bit being triggered. My device is long past being covered by any warranty and I have no intentions of using Knox features on this phone in a corporate environment.
Keep the EFS backups, those are from partitions not changed by flashing roms; stock or otherwise.
Finally went through the OTA updates, surprised how long it took but all done, at OB3.
Ok makes sense, restoring an old Nandroid would effectively result in a 4.1.2 OS with a 4.4.2 bootloader/modem, which != brick.
Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.
Thanks,
Restoring a nandroid backup should not brick the phone brick the phone as twrp does not restore the modem or bootloader.
sacrawfo said:
...
Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.
Thanks,
Click to expand...
Click to collapse
There are quite a few partitions not affected by flashing, not only the EFS partitions. IIRC there are secondary modem partitions, more than two extra bootloader partitions, etc.