Related
So I got my first smartphone, and being naive, I downloaded and installed the OTA update from AT&T because I wanted to be able to store my apps on my 64GB SD card instead of the limited 16gb already on my phone. A few days later, I looked into rooting, only to find out that update breaks it. (at least as far as I know).
So my question is, is there a way to root this update, or are the devs working on one? Or will they wait for 4.3 to be released? I'm not sure how this process goes, I have been jailbreaking iPods and iPads for the last 5 years, but I presume it is similar, seeing as they both gain root.
Also, is there a way to uninstall the OTA update so I can then root? I am new to all this, so any help would be appreciated. Thanks!
HeDsh0t said:
So I got my first smartphone, and being naive, I downloaded and installed the OTA update from AT&T because I wanted to be able to store my apps on my 64GB SD card instead of the limited 16gb already on my phone. A few days later, I looked into rooting, only to find out that update breaks it. (at least as far as I know).
So my question is, is there a way to root this update, or are the devs working on one? Or will they wait for 4.3 to be released? I'm not sure how this process goes, I have been jailbreaking iPods and iPads for the last 5 years, but I presume it is similar, seeing as they both gain root.
Also, is there a way to uninstall the OTA update so I can then root? I am new to all this, so any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Quick answer... You are stuck. No rollback or root for now. There are always people working on rooting and not waiting for.
4.3. Maybe someone will figure out how to restore old rom. Who knows.
All your questions have been answered in other threads.
Well a lot of people can't upgrade to MF3 so I say first thing first....what version are you on? MDL? or MF3? If you're MDL any of the rooting options should work. If you upgraded to MF3 like the previous person said you're stuck. Since you're used to iOS...think of it as upgrading to new firmware and CRAPPLE no longer signing the previous OS, and Android doesn't store your BLOBS and you can't use Tiny umbrella.
HeDsh0t said:
So I got my first smartphone, and being naive, I downloaded and installed the OTA update from AT&T because I wanted to be able to store my apps on my 64GB SD card instead of the limited 16gb already on my phone. A few days later, I looked into rooting, only to find out that update breaks it. (at least as far as I know).
So my question is, is there a way to root this update, or are the devs working on one? Or will they wait for 4.3 to be released? I'm not sure how this process goes, I have been jailbreaking iPods and iPads for the last 5 years, but I presume it is similar, seeing as they both gain root.
Also, is there a way to uninstall the OTA update so I can then root? I am new to all this, so any help would be appreciated. Thanks!
Click to expand...
Click to collapse
1) Confirm you are on MF3 and not MDL (settings/more/about device/last 3 letters in your build version). MDB is oldest, MDL is what you want to keep rooting, MF3 is the newest and unrootable for the time being.
2) You cannot root MF3. If you are on MDL and use Voodoo OTA Rootkeeper before updating to MF3, you might be able to preserve your root.
3) You can bet there are people trying to exploit this new build. Same as when a new version of ios comes out, you have to wait until someone jailbreaks it. We're waiting for someone to root MF3.
4) When 4.3 comes out they will try to root that one too...or hope that whatever root method we currently use, at that time, still works.
5) They used something called a QFUSE in the MF3 update that prevents us from downgrading once we're on MF3. Until (if) someone finds a way to exploit that, you're stuck on MF3.
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.
Will the latest OTA update to Verizon S5 break FoxFi for unlimited data users? (K0T49H.G900VVRU1ANE9)
Obviously I'm talking about using FoxFi for free wifi hotspotting.
Thanks!
I came here seeking the exact same info. Currently on 4.4.2 with foxfi working.
On a related note, anyone know how to disable the auto update feature and nag screen? This is an unrooted device.
mblanton66 said:
I came here seeking the exact same info. Currently on 4.4.2 with foxfi working.
On a related note, anyone know how to disable the auto update feature and nag screen? This is an unrooted device.
Click to expand...
Click to collapse
I searched everywhere and there have been no reports of FoxFi not working after the most recent update.... hope that's a good sign. but I'm still too chicken to take the chance.
FoxFi was too much of a pain in the arse for me forcing the pin code to open the lockscreen.... None of the methods in these forums worked for me to go back to swipe to un-lock.
Just root it and install the Xposed framework and the XTether module to acivate wifi hotspot. Works like a champ. I was running safestrap with Alliance ROM but I loaded it into the rom slot instead of stock slot before realizing there were issues there.
I Odined back to stock NGC and rooted / Xposed. Figured I'll leave safestrap alone until he figures out the bugz.
I froze Security policy updates SPD_v2_1402_4_1 to get rid of security nag and SDM 1.0 to disable the VZW OTA notifications with TiBu. But of course, you need root and have to purchase TiBu key to freeze apps. Small price to pay if you are going to be doing a lot of custom work on your phone though.
Chopstix9 said:
FoxFi was too much of a pain in the arse for me forcing the pin code to open the lockscreen.... None of the methods in these forums worked for me to go back to swipe to un-lock.
Click to expand...
Click to collapse
I have always used a 4-digit PIN to unlock my phone, even prior to using FoxFi,
so it wasn't too much trouble for me.
When I had the Galaxy Note II rooted, all I did to block OTA update was renaming
SDM.apk to SDM.bak. (as well as FWUpgrade.apk to FWUpgrade.bak)
Is it different on the Galaxy S5?
Thanks!
youphone said:
When I had the Galaxy Note II rooted, all I did to block OTA update was renaming
SDM.apk to SDM.bak. (as well as FWUpgrade.apk to FWUpgrade.bak)
Is it different on the Galaxy S5?
Thanks!
Click to expand...
Click to collapse
Same. And you might want to freeze the security policy updater also.
I'm strongly considering rooting at this point. Looks pretty simple for this phone. This is the wife's phone, didn't want to hack it up like I do my Motorolas; but we've gone through some expense to keep the unlimited plans and inadvertently losing wifi tether (though frankly we don't use that much data) would suck.
It also appears that you can root after this update by downgrading, but to get this update after root you need Odin.
I'll give it a week and decide. Thanks for the help and ideas guys.
Foxfi works with update for me with swipe to unlock. Just connected my tablet.
Sent from my SM-G900V using XDA Free mobile app
Not to be the stereotypical new user who totally hijacks other's threads, but I bit the bullet and rooted the wife's S5 and did Chopstix' mods. I added a hotspot toggle widget so it's now a one-touch operation with no PIN required. XPosed is a really neat architecture. This is making me hate my unrootable Maxx.
Phone is rooted on the NE9 update. And Foxfi does indeed start on that update (which is still Android 4.2.2) but is now redundant.
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
Hi Everyone,
I have the G2, and wanted to get rid of annoying ads. So I rooted(that's it, stock, no recovery). I only rooted it. Everything is still stock. The only thing I added was superuser and busybox. I didn't install a recovery like Twrp or cm. I hate ads, that is the only reason I rooted. I didn't delete any bloatware, only froze with Titanium. Essentially everything is factory, except it is rooted.
Question: Will I be able to take the lollipop OTA?
If so, Will I lose root?
If I cant receive OTA, what do I need to do to receive ota update?
Thanks a bunch
jimecv88 said:
Question: Will I be able to take the lollipop OTA?
If so, Will I lose root?
If I cant receive OTA, what do I need to do to receive ota update?
Thanks a bunch
Click to expand...
Click to collapse
Probably
Probably not
Flash stock .kdz
Well we are not likely to see a LP update in the near future, so no worries. As long as you haven't touched any system apps or installed custom recovery you will most likely be fine taking any OTA.
I think that OTA updates aint posible on some devices, like example mine which is 20b. I can only update via pc and lg update tool, but im kinda scared i wont brick my phone since i rooted it on stock 20b with towelroot.
Should i do the update? Can sh*t happen? I am looking over the forums atm, but wanted to ask.
Also im searching for a recovery install way on d802 with rooted 20b stock firmware.
Sent from my LG-D802 using XDA Free mobile app
If you are Stock you can still take the OTA if/when it comes out. Root has never been an issue upgrading with an OTA.
What makes the process fail is what you do with root, like changing DPI, changing the WiFi Tether App, physically deleting bloat (verse disabling it).
I'm not sure if you can root Lollipop yet. I've heard they are disabling the ability to root lollipop without a custom kernel.
player911 said:
If you are Stock you can still take the OTA if/when it comes out. Root has never been an issue upgrading with an OTA.
What makes the process fail is what you do with root, like changing DPI, changing the WiFi Tether App, physically deleting bloat (verse disabling it).
I'm not sure if you can root Lollipop yet. I've heard they are disabling the ability to root lollipop without a custom kernel.
Click to expand...
Click to collapse
Thanks,
I did few changes with xposed and g2 tweakbox, you think that could cause problems for the update?
I think i should really update 20b stock..
Sent from my LG-D802 using XDA Free mobile app
I wouldn't risk it, I've read a lot about people bricking their phone because they thought they could just uninstall xposed, uproot and update