Database Users

[Q] OTA Root on ATT? (Or Downgrade?)

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.

[Q] assistance for an android caveman user

Ok so having just come into the world of android i have done some digging on the site before i created a post because i honestly felt absolutely lost. I have a I337 MDL 4.2.2 galaxy S4 in my posession. I previously was not interested in any custom ROMs or rooting in particular,however i ended up rooting my phone using the motochopper tool a while back. since the release of jellybean 4.3 i have been desperately searching for a way to get the upgrade,however my OTA updates don't work because I'm always told to try again in 24 hours,even though i know full well the update is available. I am not sure if this is due to me using the phone in the caribbean where i live,or it being rooted. However,since the MDL baseband seems to be some sort of software gold,I would like to install a custom rom,and i really really need instructions so simple that an idiot would get it,cause I seem to not be getting this at all. Any redirections to other threads would be appreciated,such as GoldenEye which seems to be a decent ROM based on my internet travels lol. Also if there is a way to bypass all the drama and simply do the OTA update to 4.3,it would be greatly appreciated. I apologize for any rules broken or annoyances created and appreciate any help I can get.

http://forum.xda-developers.com/showthread.php?t=2314494
do not take the ota.
cheers

saba243 said:
Ok so having just come into the world of android i have done some digging on the site before i created a post because i honestly felt absolutely lost. I have a I337 MDL 4.2.2 galaxy S4 in my posession. I previously was not interested in any custom ROMs or rooting in particular,however i ended up rooting my phone using the motochopper tool a while back. since the release of jellybean 4.3 i have been desperately searching for a way to get the upgrade,however my OTA updates don't work because I'm always told to try again in 24 hours,even though i know full well the update is available. I am not sure if this is due to me using the phone in the caribbean where i live,or it being rooted. However,since the MDL baseband seems to be some sort of software gold,I would like to install a custom rom,and i really really need instructions so simple that an idiot would get it,cause I seem to not be getting this at all. Any redirections to other threads would be appreciated,such as GoldenEye which seems to be a decent ROM based on my internet travels lol. Also if there is a way to bypass all the drama and simply do the OTA update to 4.3,it would be greatly appreciated. I apologize for any rules broken or annoyances created and appreciate any help I can get.
Click to expand...
Click to collapse
As xBeerdroiDx said, do not take the update. The easiest thing to do is use the CASUAL root method, and then you can use the custom recovery it installs to flash StockUp MK2 if you want the 4.3 update as that way you can get it and still keep your custom recovery to change at any time. You may need the MK2 modem from the thread if your cell and data service stops working right but it should be good.

[Q] Need help with updating to recent version after ****ing up update while rooted.

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

OA8 Upgrade

I've read a lot of posts, and there are multiple instructions and people having different issues concerning upgrading to OA8 and keeping root.
1) At this time, do we have a set of instructions all in one place that works for almost everyone?
2) Anyone experiencing issues with the upgrade that would keep people from waiting until a better system is made?
Currently running NK2
Android 4.4.4
Kernel 3.4.0
Model SM-G900V
I do not use SafeStrap or KeepRoot. I can't play around at this time, because I'm using my phone for work, and can't be out of commission for an afternoon if I run into any problems. Thanks everyone!

I hate to be the guy to say this but if you can't risk the device or have the ability to recover from a bad flash you should probably leave well enough alone.

Yeah, I get it, thanks. Anyway, has anyone had any luck with the upgrade to Lollipop? Namely, can we upgrade and keep root without setting up Safestrap?

essenceofveles said:
Yeah, I get it, thanks. Anyway, has anyone had any luck with the upgrade to Lollipop? Namely, can we upgrade and keep root without setting up Safestrap?
Click to expand...
Click to collapse
The only way to flash roms or even restore a backup rom on 900V is with safestrap, because of the locked bootloader.
terrigan said:
I hate to be the guy to say this but if you can't risk the device or have the ability to recover from a bad flash you should probably leave well enough alone.
Click to expand...
Click to collapse
Agreed.

Very NOOBy, but I would like some things cleared up.

I currently have an S5 G900A on 5.0.
Am I able to root this phone as is?
If not, am I able to root it by downgrading it to say 4.4.2?
How would I got about doing either of these?
I'm sorry that I'm a big noob at this, but I would like to root my phone and I'm having issues right now.

Edit: Deleted
JarheadHME said:
I currently have an S5 G900A on 5.0.
Am I able to root this phone as is?
If not, am I able to root it by downgrading it to say 4.4.2?
How would I got about doing either of these?
I'm sorry that I'm a big noob at this, but I would like to root my phone and I'm having issues right now.
Click to expand...
Click to collapse

With an AT&T branded device, you will find things difficult at best......
You have zero chance of downgrading successfully due to a locked bootloader and security measures put in place by AT&T........
Some XDA members have given favourable mention to a process called (I think) safe strap, but as I have never had to use it, I haven't needed to research it.
One thing is for certain though.....
While you *might* be able to attain root, you won't be able to flash a custom recovery to your device.......blame AT&T and their almost apple like desire to retain control over your device........
http://i.imgur.com/rVnFwJM.jpg