I know you can update you PRL & PROFILE. But is it ok to update firmware on a stock rom that is rooted?
Depends. Usually, you'll lose root if you do so. That was the case with the MDL firmware, for example. I'd just come over here when you start to get update messages and see what folks have to say that have installed it. If you want to keep root, you'll have to wait for some friendly dev to come up with a version that gives you the update w/o loosing root. Doesn't seem to take long at all for that happen on the Samsung Galaxy line.
jejb said:
Depends. Usually, you'll lose root if you do so. That was the case with the MDL firmware, for example. I'd just come over here when you start to get update messages and see what folks have to say that have installed it. If you want to keep root, you'll have to wait for some friendly dev to come up with a version that gives you the update w/o loosing root. Doesn't seem to take long at all for that happen on the Samsung Galaxy line.
Click to expand...
Click to collapse
MDL is the current right?
Yes, MDL is the latest and greatest.
Related
Anyone knows if I can update to official 4.3 TW whenever it becomes available after rooting MF3?
Or would I have to unroot (which I think is not possible for now)?
I am pretty happy with TW 4.2 and would like to root it to use greenify and other root required apps, but not at the cost of losing
the ability to update to stock 4.3.
I'd imagine you could update but it would make you lose root.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
HiTideBlastoise said:
I'd imagine you could update but it would make you lose root.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
That would be fine with me as long as I can get to official 4.3 since I know sooner or later root would be achieved again,
and even if it could not, I'd rather have the update.
poncespr said:
That would be fine with me as long as I can get to official 4.3 since I know sooner or later root would be achieved again,
and even if it could not, I'd rather have the update.
Click to expand...
Click to collapse
I don't think there's any guarantee about it, unfortunately. Sometimes you do have to unroot in order for the OTA to go through...and if there is still no possible way to unroot when the OTA comes around, you risk having that issue. I do wonder whether the temp unroot feature in Voodoo OTA Rootkeeper would work on MF3 right now...maybe someone rooted on MF3 can test it and see if their device shows no root.
Anyways, I personally recommend everyone stay away from MF3 rooting...especially if you are not very aware of exactly what the consequences are. The fact that there is no unroot should be enough to keep most people away, but I think most don't even realize that fact.
jeffreii said:
I don't think there's any guarantee about it, unfortunately. Sometimes you do have to unroot in order for the OTA to go through...and if there is still no possible way to unroot when the OTA comes around, you risk having that issue. I do wonder whether the temp unroot feature in Voodoo OTA Rootkeeper would work on MF3 right now...maybe someone rooted on MF3 can test it and see if their device shows no root.
Anyways, I personally recommend everyone stay away from MF3 rooting...especially if you are not very aware of exactly what the consequences are. The fact that there is no unroot should be enough to keep most people away, but I think most don't even realize that fact.
Click to expand...
Click to collapse
That is exactly the reason why I have not rooted yet and thus the question just in case any one here knew for sure.
For now I will noot root and I may even switch to a Tmo or international S4 if I get the chance.
The way most updates are, if you have root then you'd have to unroot (flash stock or temp unroot) and if you've modified system files it won't go through, meaning MF3 root is risky if you want to still update until they put out firmware.
Could not resist all the bloatware, and not being able to use greenify and all the root requiring goodies. Soooo....:silly:
I rooted and removed bloatware, greenified, and very happy.
I guess sooner or later we will be able to install custom roms, including TW 4.3, even if it is not an official version.
I purchased my S4 shortly after its release...around the beginning of the summer.
I immediately rooted it and, at the advice of these forums, froze with Titanium Backup the service that calls for OS updates (so I wouldnt loose the ability to roor, custom backup and ROM). I am running stock ROM on a rooted phone and for now dont intend to put anything custom on.
I know since then there have been a number of updates, none of which I have received as I have frozen my update service.
Im totally unaware of what improvements, if any, these updates may have brought and am wondering whether I should allow AT&T to update my phone (and get whatever benefits come from 4.3, etc.) or whether I should stick to my 4.2.2 which (I think) is the MF3 that people recommended Id want to preserve.
Advice?
Thanks.
lirong said:
I purchased my S4 shortly after its release...around the beginning of the summer.
I immediately rooted it and, at the advice of these forums, froze with Titanium Backup the service that calls for OS updates (so I wouldnt loose the ability to roor, custom backup and ROM). I am running stock ROM on a rooted phone and for now dont intend to put anything custom on.
I know since then there have been a number of updates, none of which I have received as I have frozen my update service.
Im totally unaware of what improvements, if any, these updates may have brought and am wondering whether I should allow AT&T to update my phone (and get whatever benefits come from 4.3, etc.) or whether I should stick to my 4.2.2 which (I think) is the MF3 that people recommended Id want to preserve.
Advice?
Thanks.
Click to expand...
Click to collapse
If you really have no interest in roms then you can go ahead and update. I'm on mf3 on a rom, so am not 100% sure on root, but it looks like some people have been able to upgrade and keep root, you might want to look more into that. But if you have no interest in roms and you can update and still root then I would say go for it.
However, if you are pre mf3 that's when it becomes tricky. If you are pre mf3 and update you lose a lot of freedom with ROMs. So if you have interest in other roms and are currently pre mf3, I would stick with pre mf3 and not update.
lirong said:
I purchased my S4 shortly after its release...around the beginning of the summer.
I immediately rooted it and, at the advice of these forums, froze with Titanium Backup the service that calls for OS updates (so I wouldnt loose the ability to roor, custom backup and ROM). I am running stock ROM on a rooted phone and for now dont intend to put anything custom on.
Click to expand...
Click to collapse
I'm kind of in the same position, and I've been wondering the same thing.
I got my S 4 in May 2013. It came with 4.2.2 on MDL. I immediately rooted and froze the update service. I installed a custom recovery with the intention of exploring newer roms at some point, but I'm not sure what I'm missing by staying on 4.2.2 vs. 4.3. So much of the activity now surrounds the capabilities of 4.3, that I am feeling a bit left out!
mikew99 said:
I'm kind of in the same position, and I've been wondering the same thing.
I got my S 4 in May 2013. It came with 4.2.2 on MDL. I immediately rooted and froze the update service. I installed a custom recovery with the intention of exploring newer roms at some point, but I'm not sure what I'm missing by staying on 4.2.2 vs. 4.3. So much of the activity now surrounds the capabilities of 4.3, that I am feeling a bit left out!
Click to expand...
Click to collapse
Youre one of the few that actually still have a custom recovery! Use it to your advantage to flash a MK9 rom, as I think thats the latest software version from samsung
Sent from my GT-I9505 using Tapatalk 2
bennyboy78 said:
Youre one of the few that actually still have a custom recovery! Use it to your advantage to flash a MK9 rom, as I think thats the latest software version from samsung
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
All Canadian variants can run custom recovery. No locked bootloaders in canada. However doing so, does trip knox. If you don't care about knox, and have an sgh-i337m then custom recovery away. This includes latest mk6 jb4.3
Sent from my SGH-I337M
Here's my $.02
If you STILL have MDB or MDL bootloaders that CAME on your phone keep the same bootloaders and DO NOT UPDATE with the OTA's.
You can find Roms JUST LIKE YOUR ON that are PURE STOCK 4.2.2 MF3 or PURE STOCK 4.3 MK2 without losing any of the functionality of those on the 4.3 or 4.2.2 stock firmwares.
OR you can use some STOCK BASED Roms Like ShoStock-MF3 that has some added benefits WITHOUT sacrificing anything. Or try even NEWER 4.3 Roms Like ShoStock-i 4.3 MK8 with all the added benefits of stock firmwares with some slight added benefits as well. Basically if you keep your original bootloaders you CAN DO anything you WANT without sacrificing what those users lost by upgrading or buying with MF3 or newer already installed.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
And like "RockRatt" +$.02
I know for myself I haven't been on MDL for a long time so until this nut gets cracked I'm up to date .those that are pre MF3 should hold on to what you have. cause like I tell most normal people that don't mess with there phones like we at XDA do that have a problem with there stock phone.Samsung devs do the same thing as XDA devs do minus the mad improvements/mods , so expect bugs of any sort from either. What I'm getting at is pre MF3 you have the option to find perfection using "Loki".
I will add that the newest update (MK2) runs pretty good
ROOTED ATT MK2 using Tapatalk
My Sprint Samsung Galaxy S4 (rooted with CF-Auto-Root) has been repeatedly downloading and notifying me of a 398.8MB update. It comes up every couple of weeks and I have allowed it to install several times.
I maintain root after the reboot, but it keeps coming back. I'm currently on Android version 4.3 (MK2 build).
Is there anything I can do to get past this update and hopefully get 4.4?
Thanks in advance.
Krosscheck NYC said:
My Sprint Samsung Galaxy S4 (rooted with CF-Auto-Root) has been repeatedly downloading and notifying me of a 398.8MB update. It comes up every couple of weeks and I have allowed it to install several times.
I maintain root after the reboot, but it keeps coming back. I'm currently on Android version 4.3 (MK2 build).
Is there anything I can do to get past this update and hopefully get 4.4?
Thanks in advance.
Click to expand...
Click to collapse
I am not sure you can stop the update box from going away (short of a custom rom).
I believe you just have to deal with it, if you want to stay on 4.3
VandyCWG said:
I am not sure you can stop the update box from going away (short of a custom rom).
I believe you just have to deal with it, if you want to stay on 4.3
Click to expand...
Click to collapse
Hi Vandy. Sorry if I wasn't clear in my question. I don't want to stay on 4.3...I want to get to 4.4 (Kit Kat), but it seems like I'm stuck on this 389.8MB update that keeps coming back even after I have allowed it to install.
I'm hoping that someone else has experienced this "repeated" update and can tell me how I can go about moving past it so that I can get to some newer updates.
Thanks - Chung in NYC
Your best option is to install the full NAE stock tar file with Odin. The update is failing because you either have a custom recovery installed, modified system files, or deleted something. OTAs can't complete unless your stock. Look for a thread from random45 in the android development thread and download the NAE stock tar from there. You won't lose any of your data, but you will have to reroot your phone afterwards.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Your best option is to install the full NAE stock tar file with Odin. The update is failing because you either have a custom recovery installed, modified system files, or deleted something. OTAs can't complete unless your stock. Look for a thread from random45 in the android development thread and download the NAE stock tar from there. You won't lose any of your data, but you will have to reroot your phone afterwards.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Thanks a lot - I will try that now!
- Chung in NYC:good:
I have a Verizon Note 3 SM-900V MJE that's on stock Android 4.3 and Kernel 3.4.0
Its been rooted with Kingo v1.1.2.1770 and has downloaded Kitkat 4.4 Software version N900VVRUCNC4
Is it safe for me to take the upgrade with the phone rooted?
If not, should I attempt to un-root with the same version of Kingo, a later version of it or something else before letting the phone take the upgrade?
Do the problems with not being able to write to an SD card still exist?
Is there currently any way around this?
Thanks for all advice
stonypass said:
I have a Verizon Note 3 SM-900V MJE that's on stock Android 4.3 and Kernel 3.4.0
Its been rooted with Kingo v1.1.2.1770 and has downloaded Kitkat 4.4 Software version N900VVRUCNC4
Is it safe for me to take the upgrade with the phone rooted?
If not, should I attempt to un-root with the same version of Kingo, a later version of it or something else before letting the phone take the upgrade?
Do the problems with not being able to write to an SD card still exist?
Is there currently any way around this?
Thanks for all advice
Click to expand...
Click to collapse
If you want to keep root and have the ability to flash back to MJE use this method. If you take the OTA you might be able to keep root but you will not have the option to go back to MJE if you don't like KK. Also if something goes wrong after taking the OTA and you need to Odin back to stock you will most likely loose root because there is no known root method for KitKat 4.4.2 except by the leaked NC2 that I linked you to.
Added: With NC2 you can roll back to MJE and regain root if needed. Also the SD card write is fixed in NC2.
So, if I let the phone take the upgrade I'll still be rooted?
Any chance the upgrade will brick the phone since I'm rooted?
Thinking of taking the upgrade the installing SDFix so I can still write to my SD card.
stonypass said:
So, if I let the phone take the upgrade I'll still be rooted?
Any chance the upgrade will brick the phone since I'm rooted?
Thinking of taking the upgrade the installing SDFix so I can still write to my SD card.
Click to expand...
Click to collapse
From what I have heard the OTA will either install or not, no bricking. There is a big possibility you will loose root taking the OTA. Trust me you are WAY better off with the NC2 leak but that's your choice if you want to take the risk of having root or not. KK 4.4.3 or 4.5 is coming soon and from what I am hearing it's locked down tight. That is all these "updates" are doing is locking the phones down so we can not achieve root anymore. This is the way Verizon, AT&T and Google want it and from the looks of things they will get it sooner than everyone thinks.
Misterxtc said:
From what I have heard the OTA will either install or not, no bricking. There is a big possibility you will loose root taking the OTA. Trust me you are WAY better off with the NC2 leak but that's your choice if you want to take the risk of having root or not. KK 4.4.3 or 4.5 is coming soon and from what I am hearing it's locked down tight. That is all these "updates" are doing is locking the phones down so we can not achieve root anymore. This is the way Verizon, AT&T and Google want it and from the looks of things they will get it sooner than everyone thinks.
Click to expand...
Click to collapse
That's what I hear also... this is no good for us power users...
Sent from my SM-N900V using XDA Premium 4 mobile app
A week ago, I got a prompt to update to the most recent Android version. I have a Galaxy S5 SM-G900F. Had rooted it with Towelroot in July and everything was smooth, haven't done any major changes other than SuperSU and titanium. After I ok'ed the software update, it got to like 30% or something until it crashed and rebooted. Everything seems fine, just the update didn't get installed, I'm still 4.4.2. When trying to update it, it says that my operating system has been modified in an unauthorized way (towelroot) and that I should try to download updates using Kies.
So I looked a bit for solutions, I checked the SuperSU survival mode AFTER failing the update, and now my question is, what is the best way to update whilst retaining root and all my settings, in the fastest way? Or just what is the best solution to update? Don't really want to download Kies just for this. Sorry for noobness. Thanks for any help, appreciate it.
tempest22 said:
just what is the best solution to update?
Click to expand...
Click to collapse
The best thing to do is always search first. Most questions have been asked and answered before, so a quick search gives you an immediate answer, not to mention a larger number of replies and accumulated wisdom. And if any aspect remains unanswered, you are in a much better position to pose informed questions.
Of course that is a pipe dream, because most people aren't sensible enough to take 30 seconds to search, expecting someone else to gift wrap the answer for them.
Anyway, the best approach is arguably to never be first to accept an update. Instead wait a few days and then see what early adopters are posting about any given new update. Every update is different and that will quickly tell you if there are any issues regarding root and inevitably how to deal with them. OTA updates will usually break root and often fail to install properly as well. It's better to wait and install an update via Odin IMO.
Some apps, notably mobile odin pro and super su pro have root survival modes that will attempt to regain root after an update. But there are no guarantees and you should not rely upon them. Instead treat it as an emergency plan B.
.
Did you change from dalvik to ART. I got the same message after changing to art and going back to dalvik sorted it for me.
Sent from my Galaxy S5 running NeatRom 0X1
fffft said:
The best thing to do is always search first. Most questions have been asked and answered before, so a quick search gives you an immediate answer, not to mention a larger number of replies and accumulated wisdom. And if any aspect remains unanswered, you are in a much better position to pose informed questions.
Of course that is a pipe dream, because most people aren't sensible enough to take 30 seconds to search, expecting someone else to gift wrap the answer for them.
Anyway, the best approach is arguably to never be first to accept an update. Instead wait a few days and then see what early adopters are posting about any given new update. Every update is different and that will quickly tell you if there are any issues regarding root and inevitably how to deal with them. OTA updates will usually break root and often fail to install properly as well. It's better to wait and install an update via Odin IMO.
Some apps, notably mobile odin pro and super su pro have root survival modes that will attempt to regain root after an update. But there are no guarantees and you should not rely upon them. Instead treat it as an emergency plan B.
.
Click to expand...
Click to collapse
Thanks for the answer. I'm not technically well versed, I just know that this forum is the best for people like me who need advice from the pros lol. I would rather just have the most recent update because I don't want any vulnerabilities or whatever. I haven't ever used Odin, just Towelroot and done. I don't use any roms, just factory plus root through towelroot and supersu, that's it for now. So again, how would a noob like me go about safely getting an update and having the reassurance that Towelroot will either still be there, or if an unroot is necessary, that towelroot will be able to root again? Kies? Also, is an actual OTA update still possible (I'm getting that error message) or is a computer update the only thing left?
Prof Peach said:
Did you change from dalvik to ART. I got the same message after changing to art and going back to dalvik sorted it for me.
Sent from my Galaxy S5 running NeatRom 0X1
Click to expand...
Click to collapse
nope, just towelrooted it 2 months ago and that's that. no roms. still have 4.2.2, wanted to update. I got a failed update a week ago when I got an OTA update prompt. That failed, root is stil there, S5 working fine but can't do OTA since it gives me that error message. What could I do to safely get the most recent software update but retain root, OR be able to update and reroot again with towelroot if I need to unroot to update...
can anybody help please?
Why not find a stock rooted rom for your model and flash it?
tempest22 said:
nope, just towelrooted it 2 months ago and that's that. no roms. still have 4.2.2, wanted to update. I got a failed update a week ago when I got an OTA update prompt. That failed, root is stil there, S5 working fine but can't do OTA since it gives me that error message. What could I do to safely get the most recent software update but retain root, OR be able to update and reroot again with towelroot if I need to unroot to update...
Click to expand...
Click to collapse
Just downgrade to an older rom like NE2 and root with Towelroot, after that flash the new rom with Mobile Odin Pro and keep root with Everroot and the other 2 options enabled. Or flash an older kernel on your updated rom now and reroot with TR, look here for how to http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044. Or as posted above a pre-rooted stock rom like Alexander rom.
metalfan78 said:
Why not find a stock rooted rom for your model and flash it?
Click to expand...
Click to collapse
I'm sorry but I really don't know what that means in this context for an update. I used Towelroot 2 months ago to root and still haven't gotten myself anx root aps or mods (but was planning on it right when the update failed). Is there not a simple way to make this update work while either 1)unrooting, then updating then rerooting with Towelroot, or 2) updating whilst retaining Towelroot?
and ecniqu
gee2012 said:
Just downgrade to an older rom like NE2 and root with Towelroot, after that flash the new rom with Mobile Odin Pro and keep root with Everroot and the other 2 options enabled. Or flash an older kernel on your updated rom now and reroot with TR, look here for how to http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044. Or as posted above a pre-rooted stock rom like Alexander rom.
Click to expand...
Click to collapse
I don't think you understand what I'm asking for, or I'm just way too much of a noob, probably that. but I'd just like to update to the most recent Android version. I'm 4.4.2, got an update prompt 1 week ago, have an SM-G900F, and have Towelrooted 2 months ago. All I want is to update. How can I do this, since I'm getting the failure message that it can't be updated due to my device being modified. If I unroot with supersu, then update, then (if the update works) try to Towelroot again, will Towelroot work? Or does the new update **** with it? Or an I update with Samsung Kies, while retaining Towelroot? Ahhhh I'm so sorry for this stupid question but I really don't know
no halp?
I'm really sorry for bumping this again, but I just honestly have no clue what to do to get it updated and either retain Towelroot or be able to install it again after updating. somebody help a noob out please.
my samsung galaxy s5 , it is rooted but I would like to upgrade, I can't do the OTA upgrade so I should proceed with Kies , I would like to know whether I have to unroot my phone (how do I do that? via kies? it does not matter if it'll lose the root, I just want to be sure I would still be able to use my samsung without creating any damage)or just directly proceed with the upgrade,furthermore, my phone was a sumsung galaxy s5 tmobile but I managed to unlock it in order to use it with other carriers, if I install the original firmware and then upgrade to the newest version, can I still use it with other carriers or will return locked? thank you in advance for your help