I noticed the new OTA updated on my phone today and decided not to install it. Once I got home, I plugged my phone into my computer to charge it and it installed the OTA update without even asking. So with that being said, what do I have to do now to get back to where I was which was stock with root access?
I did a backup this morning with Titanium, could I do a factory reset and restore with Titanium?
Nick James said:
I noticed the new OTA updated on my phone today and decided not to install it. Once I got home, I plugged my phone into my computer to charge it and it installed the OTA update without even asking. So with that being said, what do I have to do now to get back to where I was which was stock with root access?
I did a backup this morning with Titanium, could I do a factory reset and restore with Titanium?
Click to expand...
Click to collapse
I believe you are stuck like me! I was using a jailbroken iphone which would block any update from apple and I got used to that. I forgot to freeze the updater and it automatically updated my brand new s4 that I had just rooted and tweaked to my liking just a few days ago :crying::crying::crying:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
You guys are on hold right now.
I don't understand how you guys are getting OTA updates with a rotted phone. When mine was rooted, it said updating was disabled because my device was modified.
scream_clarity said:
I don't understand how you guys are getting OTA updates with a rotted phone. When mine was rooted, it said updating was disabled because my device was modified.
Click to expand...
Click to collapse
some are seeing, even if they are rooted, it will say official and do the update, lose root after, but it has been seen.
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
Avoid all updates by flashing custom roms. You can always go back to factory stock, unrooted and untouched. But this way, you can see what updates do what, and then decide.
The Ax says, just a helpful tip.
I tried to avoid the update but lost the battle when I plugged my phone in to charge and walked away! I should have froze those services listed in another thread. I had no idea. Its only time... Hopefully
Sent from my SAMSUNG-SGH-I337 using xda premium
I don't mean to make matters worse for you, but stories like these are really depressing. I sincerely hope that some of our advanced Devs will find a solution for MF3 root soon.
And now for the potentially helpful part: AT&T typically has a 14 "buyers remorse" policy. They'll take back the handset (so long as it is in perfect condition) for ANY reason and exchange it for another (or same one, as far as I know). Two caveats:
You will likely be forced to pay a $35 re-stocking fee. Might be worth it for root/ROMs though!
You can only do this once per purchase.
Otherwise, you'll need to wait until a solid root is found for MF3. Even still, keep in mind that your "aboot" has been patched, and now Loki will not work for you (it means no custom roms/kernels, and no custom recovery). This might be permanent, as the bootloaders are locked-down TIGHT. The Loki exploit was just a workaround, but even it is gone in MF3.
I just posted this in another thread, so here you go again:
For future reference, or for someone else, you could have avoided this easily!
1) When it tries to update, don't hit "remind me later"! You can only do that so many times before it forces the update automatically. INSTEAD, you can just hit the home button and force your way out, not making any decision. You can do this indefinitely...but it's annoying so you should just 2) Get Titanium Backup and freeze the OTA update apps so they don't bother you! It's right at the top of the sticky beginner's info aka noob helper thread:
http://forum.xda-developers.com/showthread.php?t=2301762
You probably already knew this but maybe it will help someone else who's not prepared to avoid this OTA!
jeffreii said:
I just posted this in another thread, so here you go again:
For future reference, or for someone else, you could have avoided this easily!
1) When it tries to update, don't hit "remind me later"! You can only do that so many times before it forces the update automatically. INSTEAD, you can just hit the home button and force your way out, not making any decision. You can do this indefinitely...but it's annoying so you should just 2) Get Titanium Backup and freeze the OTA update apps so they don't bother you! It's right at the top of the sticky beginner's info aka noob helper thread:
http://forum.xda-developers.com/showthread.php?t=2301762
You probably already knew this but maybe it will help someone else who's not prepared to avoid this OTA!
Click to expand...
Click to collapse
I did that exactly. I just ignored it. I have no idea what triggered my phone to do the update. I checked just now and even when I plug my phone in, Kies doesn't even open. I'm not sure what I did... Its really annoying though.
I'll keep my fingers crossed.
I'm hearing sim unlock will not work now? Is that true?
Sent from my SAMSUNG-SGH-I337 using xda premium
xamadeix said:
I'm hearing sim unlock will not work now? Is that true?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I'm not sure but if I had to guess I would think not.
Related
is this happening to everyone? Wasn't going to install or even acknowledge that there was an update, because of the boot loader. But i plug it into a charger and 5 minutes later, it is like the phone is giving me the middle finger and accepting the update on it's own, without any question on if i want to or not.
My phone feels violated.
:thumbup:
Sent from my Transformer Prime TF201 using xda app-developers app
Same thing happened to me. O well not ready just yet to brick my s4 lol
Sent from my SAMSUNG-SGH-I337 using xda premium
tried everything i could to stop it, even removed battery as it started the update. was hoping for a brick, don't know why. lol, also not to worried about bricking mine, i am fairly confident in my ability to read, unless the thread is in some language other than english, but then again, now i got s translate!
Sent from my Transformer Prime TF201 using xda app-developers app
You would of had to freeze the ota update apps before hand not to be forced to get it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Could you please let me know which services to freez with TB on At&t S4 as to avoid forced updates, is it At&T Software Update V 42_1_1303_5_1?
Alos please excuse my noobiness, this is my first android and coming from apple jailbreaks, I of coarse was not happy with closed phone policy so i was researching root options (which i know very little about since its my first android platform). Anyways long story short I rooted using motochopper exploit and got superuser. My questions are:
1. Is motochopper a real root or just tricks the phone into thinking its root?
2. Read about a bootloader hack soon to be released...what exactly is that and what will it give us? also what would be the difference between the motochopper "root" i have on my S4 now and the bootloader hack to be released?
3. Got Ram Manager but was unable to create backup recovery since clockwork mod is not yet released for S4, is that true or is there other ways to use Rom manager?
4. And the last but not least, what should a noob user like myself do, or how can we avoid bricking our phones now that we rooted (with motochopper) or will use the boot-loader hack?
5. is Samsung.Cloud Data Relay 2.1.4 responsible in anyways for forced updates?
Please if you can answer any or all questions I would be so grateful, as im sure many other noobs like myself would be. Please don't think I don't research the subject, its just when you are new to something, you always want to be sure. I am sure logic is to be used and common sense also as to not mess with software service or delete stuff you don't know as to avoid bricking but is there something else to watch out for?
Thnks a million guys
Stokem
unlocking the bootloader will allow us to flash an alternate recovery such as clockwork or twrp and then flash a rom. best bet to avoid a brick is to read everything you can about what you want to do. make sure you read any instructions several times before doing anything to make sure you understand.
sent from my black at&t sgs4
p1gp3n said:
unlocking the bootloader will allow us to flash an alternate recovery such as clockwork or twrp and then flash a rom. best bet to avoid a brick is to read everything you can about what you want to do. make sure you read any instructions several times before doing anything to make sure you understand.
sent from my black at&t sgs4
Click to expand...
Click to collapse
thank you, will there be some custom roms developed for S4 once the bootloader is unlocked or is there some good once already?
also, i read that since AtT can force updates it might patch the bootloader unlock in the future, which processes do we have to freeze in order to avoid it on Att S4. I couldn't find any SDM processes as explained for other S4 carriers. Is it At&T Software Update V 42_1_1303_5_1, do you know by any chance?
I would imagine that roms will be developed & released, but can not say they definitely will.
sent from my black at&t sgs4
Once the bootloader is unlocked Roms will come fast and furious.
To avoid future updates freeze in TB:
AT&T software update
FWUpgrade
LocalFOTA
thank you for your replies. much appreciated
I recently got a new S4 at the store, and of course, it came with MF3.
My question is, if I choose to root it, which I would really like to, would this potentially block my ability to utilize a future exploit in the bootloader or otherwise negatively impact the phone?
I know I can't un-root the phone for the time being, which is fine, but I would like to root it if there won't be any future issues.
Why would you think there would be issues with a future bootloader exploit?
Root has nothing to do with the bootloaders. If there were ever to be issues, it would be addressed and fixed before it goes public.
Sent from my SAMSUNG-SGH-I337 using xda premium
just remember that if you root, and your device takes a poop, you wont have odin as option to fix it nor will you have a backup to restore it since you wont have a custom recovery. dont root if you dont think you'd know how to get it back up and going again. read up. cheers.
graydiggy said:
Why would you think there would be issues with a future bootloader exploit?
Root has nothing to do with the bootloaders. If there were ever to be issues, it would be addressed and fixed before it goes public.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Yeah, as you can see I'm not very knowledgeable about the way the phones work and how these exploits deal with the phone software. But I appreciate the info that rooting won't mess with that kind of thing.
xBeerdroiDx said:
just remember that if you root, and your device takes a poop, you wont have odin as option to fix it nor will you have a backup to restore it since you wont have a custom recovery. dont root if you dont think you'd know how to get it back up and going again. read up. cheers.
Click to expand...
Click to collapse
I guess I'm wondering what could cause my device to take a poop if I simply root it and install Titanium Backup and some other root apps. Yeah, I've been trying to read up ever since I became a member a couple days ago.
I appreciate the advice, guys. Thanks!
there's a hundred threads spread out over the last couple weeks of people asking what they can do to fix their devices. people that were on MF3, rooted, and suddenly there was a glitch somewhere. whether they deleted something they shouldnt have, installed something they shouldnt have, some random misc unforeseen error, etc.
if i were a user that had a very introductory-level of android knowledge, it would be a no brainer for me: having no root on my device vs having no way to backup/restore via a custom recovery and no odin. i choose stock/unrooted. just keep your eyes peeled. when there is finally an exploit, you'll see it here on xda.
I cannot enable wifi since I updated to 4.3 today. I've tried everything I know and wifi will not toggle on.
I am so frustrated!
I was rooted before the update and lost root afterwards FYI for anyone who has root using 4.2.2
Is anyone else experiencing this?
I did see a message saying something about it not finding something on my SD card but not sure if the message (that flashed briefly) had anything to do with this issue or not.
Restarting the phone doesn't help.
My S4 is useless to me without wifi.
I have done a factory data reset and wiped all data. Still having the same issue.
gbarrett71 said:
I cannot enable wifi since I updated to 4.3 today. I've tried everything I know and wifi will not toggle on.
I am so frustrated!
I was rooted before the update and lost root afterwards FYI for anyone who has root using 4.2.2
Is anyone else experiencing this?
I did see a message saying something about it not finding something on my SD card but not sure if the message (that flashed briefly) had anything to do with this issue or not.
Restarting the phone doesn't help.
My S4 is useless to me without wifi.
I have done a factory data reset and wiped all data. Still having the same issue.
Click to expand...
Click to collapse
I know this doesn't help you, but it may help others.....
Don't EVER take an OTA while rooted. Jeez, I thought that was the cardinal rule when deciding to root ones phone.....
smizak said:
I know this doesn't help you, but it may help others.....
Don't EVER take an OTA while rooted. Jeez, I thought that was the cardinal rule when deciding to root ones phone.....
Click to expand...
Click to collapse
People just assume they will fine. This guy/girl, I'm sure wasn't that patient and flashed the zip. The main thread for the update shows that members have been having problems with WiFi while flashing the update zip on stock rooted.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
People just assume they will fine. This guy/girl, I'm sure wasn't that patient and flashed the zip. The main thread for the update shows that members have been having problems with WiFi while flashing the update zip on stock rooted.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I'm familiar with rooting somewhat and figured for sure I'd lose root. I didn't know about the wifi issues though. I'm really not a dumb butt (and I'm not suggesting that's what you're saying exactly), it's just that after searching and searching for a primary thread and not finding one on the issue, I went ahead and did the update being fine with potentially losing root temporarily till another root option came out.
I feel like a dumb butt because I still cannot find the thread that you're talking about. Maybe I'm just overwhelmed. I have no idea why but my continued searches are still turning out fruitless for finding any info on wifi troubles at all except for people in Germany on different carriers.
Will someone kindly point me in the right direction for the thread you're referring to and in the right direction as to how I can flash my phone back to stock/unrooted?
I was just excited to get this update and have never ran into issues like this before with updating OTA on other devices, except for losing root.
I really do appreciate any help and I'm sorry for having a putz moment.
Garry.
gbarrett71 said:
I'm familiar with rooting somewhat and figured for sure I'd lose root. I didn't know about the wifi issues though. I'm really not a dumb butt (and I'm not suggesting that's what you're saying exactly), it's just that after searching and searching for a primary thread and not finding one on the issue, I went ahead and did the update being fine with potentially losing root temporarily till another root option came out.
I feel like a dumb butt because I still cannot find the thread that you're talking about. Maybe I'm just overwhelmed. I have no idea why but my continued searches are still turning out fruitless for finding any info on wifi troubles at all except for people in Germany on different carriers.
Will someone kindly point me in the right direction for the thread you're referring to and in the right direction as to how I can flash my phone back to stock/unrooted?
I was just excited to get this update and have never ran into issues like this before with updating OTA on other devices, except for losing root.
I really do appreciate any help and I'm sorry for having a putz moment.
Garry.
Click to expand...
Click to collapse
If you already updated to mja update, you went to the path of no return; well for awhile. You can odin or anything or go back to other firmware. Its like apple's ios firmwares now. Being stuck when you upgrade and cant downgrade sucks really.
Sent from my SPH-L720 using xda app-developers app
I am currently on system version 9.30.1 and I am rooted. My boot loader isn't unlocked and I don't have a custom recovery installed. I am wondering if being rooted will cause issues once the 4.4 update is released. And if so how do I remove root?
Sent from my XT907 using XDA Premium 4 mobile app
Well, since you are rooted, chances are you have probably removed some of the bloat that was installed on your phone by your provider. If this is so, you won't even be able to update to 4.4 unless you first return your phone completely to stock, ie add all the bloat back in. If your phone is not stock, you can remove updater.apk and you won't even be prompted for the update.
If you are completely stock and rooted, when you accept the update to 4.4, once the upgrade completes, you simply will not be rooted anymore. This is true whether you have a locked or an unlocked bootloader. With the unlocked bootloader and a custom recovery, it may be possible to have root if the one in the recovery works with 4.4 Otherwise, we will all have to wait until if/when root becomes available for Android 4.4 and our phone. This is why it is often recommended that you wait to update until the devs have a chance to tear the update apart and look for usable exploits.
Some what on the same topic... I made a back up after unlocking before doing anything... Could I restore said back up flash stock recovery voodoo my root and ota... Or would I still have to rsd then ota?
Sent from my XT907 using xda app-developers app
ezknives said:
Some what on the same topic... I made a back up after unlocking before doing anything... Could I restore said back up flash stock recovery voodoo my root and ota... Or would I still have to rsd then ota?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes, you can flash your backup and then take the OTA, but you don't need voodoo if you're unlocked. Re-flash recovery and then flash root.
netizenmt said:
Well, since you are rooted, chances are you have probably removed some of the bloat that was installed on your phone by your provider. If this is so, you won't even be able to update to 4.4 unless you first return your phone completely to stock, ie add all the bloat back in. If your phone is not stock, you can remove updater.apk and you won't even be prompted for the update.
If you are completely stock and rooted, when you accept the update to 4.4, once the upgrade completes, you simply will not be rooted anymore. This is true whether you have a locked or an unlocked bootloader. With the unlocked bootloader and a custom recovery, it may be possible to have root if the one in the recovery works with 4.4 Otherwise, we will all have to wait until if/when root becomes available for Android 4.4 and our phone. This is why it is often recommended that you wait to update until the devs have a chance to tear the update apart and look for usable exploits.
Click to expand...
Click to collapse
Thanks, I am rooted and didnt touch any of the bloatware. I bought the phone in an non-unlockable state, 9.30.1, so I just want some form of kit-kat on this. In an un-xda like fashion im probably going to just take the update ASAP.
AKShotgun said:
Thanks, I am rooted and didnt touch any of the bloatware. I bought the phone in an non-unlockable state, 9.30.1, so I just want some form of kit-kat on this. In an un-xda like fashion im probably going to just take the update ASAP.
Click to expand...
Click to collapse
Being locked & rooted you will lose root perhaps forever.
aviwdoowks said:
Being locked & rooted you will lose root perhaps forever.
Click to expand...
Click to collapse
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?
theemaster said:
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?
Click to expand...
Click to collapse
I have 442 already and boy is it fast!
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
But I cannot root on the X that is.
aviwdoowks said:
I have 442 already and boy is it fast!
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
But I cannot root on the X that is.
Click to expand...
Click to collapse
You don't say....
theemaster said:
A lot of guess work.. considering first off that 4.4 hasn't been provided. If it was provided will you be the first to jump?
Click to expand...
Click to collapse
Take a look in the S5 and X forums to get the proof you need about KK being hard to root.
AK, I would seriously wait until the devs get hold of the update. Let the devs take the OTA and pull it apart so they can start providing ROMs for SafeStrap. Then, update to KK via SS.
My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.
netizenmt said:
My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.
Click to expand...
Click to collapse
As long as your bootloader is unlocked, all you need to do after you update to the OTA is re-flash recovery and then superuser to regain root.
netizenmt said:
My plan is to go all stock and accept the update IF it ever actually gets released. As my bootloader is unlocked, I always have the option of reflashing recovery on it, make a backup of 4.4, and then run it or some other rom backup as I choose. Also, I'm curious to know, if there is supposed to be superuser built into TWRP, will that allow 4.4 to be rooted anyway, or not?
As you can see, I know just enough to be dangerous, lol, but as long as I can make calls, it's all good.
Click to expand...
Click to collapse
I don't think there is an "if" in it. The executive posted on google+ about receiving the update in the next couple weeks.
Sent from my XT907 using XDA Premium 4 mobile app
AKShotgun said:
I don't think there is an "if" in it. The executive posted on google+ about receiving the update in the next couple weeks.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well its been a few weeks since he said that. Having had a similar situation with Sony and the Xperia Play and ICS, I can tell you the average executive's word isn't worth spit. And then there's the whole Verizon involvement which always adds another level of delay. I'm hoping I'm wrong, but I would be surprised if we get KK in a few Months, never mind weeks.
Sent from my DROID RAZR M using Tapatalk
netizenmt said:
Well its been a few weeks since he said that. Having had a similar situation with Sony and the Xperia Play and ICS, I can tell you the average executive's word isn't worth spit. And then there's the whole Verizon involvement which always adds another level of delay. I'm hoping I'm wrong, but I would be surprised if we get KK in a few Months, never mind weeks.
Sent from my DROID RAZR M using Tapatalk
Click to expand...
Click to collapse
Sorry if it seems like it im not trying to fight you here but he commented on his google+ post saying Razr M and HD KitKat is already at Verizon labs. So im guessing about a month.
I look forward to being wrong. I really hope we get it in the next few months. I've noticed that each revision of Android has made the need to develop custom ROMs less necessary for many phones. Of course that won't lessen our desire or enthusiasm to push the envelope. But when I think how far we have come from my first Android, the LG Ally and Eclair... There was a phone that was crap stock, but once unlocked and customized, it was a very decent phone for its time and price point. Today, its harder to see the need or difference between stock and custom ROMs, other than removal of bloat and occasionally some new bell or whistle. Still, I can't seem to resist their siren's call any more than the rest of you. Which is why I'm running CM11. Lol!
Sent from my DROID RAZR M using Tapatalk
Hey guys,
Great site. I have the lag problem with my S7 edge after root. Downloaded fix file from link in other in (Rooting Problem). Not sure what to do now. Do I flash zip with Flashfire? Leave it in the zip state? I realize this is elementary to most, just been a very long time for me. Hated to ask the question again. Wouldn't let me ask it in the thread I mention.
Never mind, figured it out. Thanks for the 37 views without advice.
Well what file did you download and did you use flashfire to install? I don't have root just curious
Sent from my SAMSUNG-SM-G935A using Tapatalk
Jnewell05 said:
Well what file did you download and did you use flashfire to install? I don't have root just curious
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
There's a file on the Verizon forum that helps most if not all the issues with root. Just flash it once and you're good to go. OP just doesn't understand people here aren't obligated to help him, self entitled privilege at it's best.
Sent from my SM-G935U using Tapatalk
buckmaster1967 said:
Never mind, figured it out. Thanks for the 37 views without advice.
Click to expand...
Click to collapse
"Figured it out."
Doesn't explain anything. Nice.
falkon114 said:
"Figured it out."
Doesn't explain anything. Nice.
Click to expand...
Click to collapse
Sorry guy. You are right. I should of explained. I followed directions from this youtube video ( https://www.youtube.com/watch?v=Kqb-p2JO5I4 ). Worked , but was lagging and wifi issues. Came here, found and flashed with Flashfire., the wifi fix file , which I can't seem to find here now. Everything worked great. Until next morning it was stucked on AT&T logo. Only could get it into download mod. Had to do a factory rest. Want to youtube to look for a different way to root. Found this ( https://www.youtube.com/watch?v=QcFEcycZZnU ) followed directions and seem to work great right now. But time will tell. Sorry for the rushed details, busy day. Thanks.
Update. Yesterday got stucked on AT&T logo AGAIN. I decided the heck with this root, 4th time I had to set phone up from start. I did a factory reset. Set my phone back up. Lost my root according to Root Checker. But I am getting security warning, and when it reboots. It still shows custom and unlocked. Any ideals? As so, I tried to do the AT&T update, but it fails.
If it is showing custom & unlocked, you might have a custom recovery and/or unlocked bootloader. Just got the S7 edge, so I haven't really messed around with the internals yet (or anything dealing with rooting or unrooting), but that's usually what that means in my experience. The fix is usually an odin flash to the stock image, but as I said, I haven't really gotten too involved with it yet. A factory reset will set the system back to stock, but I don't think it does anything with the other partitions. Good luck and if I can find anything out that might help, I'll come back by.
So far as the update, do you have all the prerequisite stock bloatware installed? There are apps that are required for an update to work. If you uninstalled any it will freeze you out of getting updates.
And my signature is so out of date it is funny.