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
Hi folks,
I got a used I337 S4 and have been using it on ATT no problems. I rooted it (towelroot), initially just to make it easier to back up some application data but eventually I plan to debloat the thing. Probably will stay on stock ROM unless I have a compelling reason to switch.
My question is, now that I have a rooted device, do I have anything to fear from possible OTA updates to 4.4.3 or 4.4.4, updating the OS and making me loose root. And if I do need to be concerned, what is the best way to block such updates from happening, until such time as a new root is (hopefully) developed.
Sorry if this is a basic question... I'm still learning my way around these things.
Thanks
Marc
Frankenscript said:
Hi folks,
I got a used I337 S4 and have been using it on ATT no problems. I rooted it (towelroot), initially just to make it easier to back up some application data but eventually I plan to debloat the thing. Probably will stay on stock ROM unless I have a compelling reason to switch.
My question is, now that I have a rooted device, do I have anything to fear from possible OTA updates to 4.4.3 or 4.4.4, updating the OS and making me loose root. And if I do need to be concerned, what is the best way to block such updates from happening, until such time as a new root is (hopefully) developed.
Sorry if this is a basic question... I'm still learning my way around these things.
Thanks
Marc
Click to expand...
Click to collapse
Read the section about "Block the AT&T OTA update" in the post 1 here.
Thanks. Perfect info.
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
I used towelroot a while back to unlock my Note 3, and I love everything about it...except of course for the fact that I doesn't install OTA updates. I've shrugged off most of them, but it's downloading one right now that's over a gig in size, so I'm guessing it's a whole new version of Android. Two questions:
1) Is it Android 5 yet?
2) If so, I know I want to do the update, but as always our pesky friend the OTA root checker will undoubtedly get in the way. Do we have a way to get around the problem? Is the only answer to flash a stock ROM or can we fool the check process somehow?
tnpir4002 said:
I used towelroot a while back to unlock my Note 3, and I love everything about it...except of course for the fact that I doesn't install OTA updates. I've shrugged off most of them, but it's downloading one right now that's over a gig in size, so I'm guessing it's a whole new version of Android. Two questions:
1) Is it Android 5 yet?
2) If so, I know I want to do the update, but as always our pesky friend the OTA root checker will undoubtedly get in the way. Do we have a way to get around the problem? Is the only answer to flash a stock ROM or can we fool the check process somehow?
Click to expand...
Click to collapse
1) Depend of the model of your device. Install this APP for know more info about.
2) Flashing again the stock rom is best solution for unroot completely your device.
I am currently rooted with MM on my S7-Edge, SM-G935A and yesterday I got the notification from AT&T that it wanted to update my phone to the newest version of Android, Version 7 (Nougat).
I thought about UN-Rooting my phone and let the OTA finish the process and complete the upgrade. But after looking around there isn't a stable version for Root on Nougat yet for the AT&T Phone, so I think I going to wait.
But my question is if I just let OTA update the phone without Un-Rooting it, what would happen to the phone. Would it just become Un-Rooted and be an Updated Android 7.0? Or would there be problems? I can say for sure that I would not do this as I like having Root Access and I don't think I would like living without Root. But I was just curious what would really happen?
I only have one phone and don't want to mess it up, but there are a lot of people on these forums that experiment with phones all the time.
Anyway, just a question for all of you in the know.
Judging from what happened with a minor update on my at the time rooted s6e, it'll just error out before anything is done due to the engboot not being what it expects.
It checks the hashes of that file and a lot of others before applying the update from what I can tell
dragynbane222 said:
Judging from what happened with a minor update on my at the time rooted s6e, it'll just error out before anything is done due to the engboot not being what it expects.
It checks the hashes of that file and a lot of others before applying the update from what I can tell
Click to expand...
Click to collapse
Thanks for the reply. That is what I expected. I am not going to try this but like I said just curious. And you answered my question.
Again thanks.
Yup it wouldn't update.
Sent from my SM-G935V using Tapatalk
[Deleted]