Database Develop

Question about ROOT access?

I figured, I would get the best response here... If you ROOT an Android phone, will downloading OTA updates through your phone brick it? I read an article about the new OTA for the EVO and it will brick rooted devices.

Misinformation. It would brick it if you applied it twice in sequence, not if you were rooted. You need the stock recovery to apply updates anyway, if you do get one it will not harm the phone because it can't be applied.

In the thread when the final OTA was coming out, lots of people that were rooted, said they installed it, it worked fine, but they lost root. So then they have to obtain root again.
So, I'd assume it would work fine if everything else was stock... you just might loose root.

So your saying, that if I were to install an OTA update through a rooted Android device running stock firmware, it would go through successfully without bricking it. But, if I ran the update a second time it would brick it. Correct?

If you're on a rooted stock rom, assuming you haven't flashed a custom recovery, the phone's recovery utility will not allow you to flash an OTA update because of a signature mismatch. I'm not sure what happened with the evo, but I don't believe it can happen with the nexus.

Okay, thanks? But I would still like some more input on this situation.

Pay attention
PurpleLlamaLover said:
Okay, thanks? But I would still like some more input on this situation.
Click to expand...
Click to collapse
If your not rooted you can still flash OTA update leaks, there are plenty out there. If you want custom roms then you have to root. The stock recovery only flashes stock updates, not rooted updates. If your not getting it by reading the forums, then I suggest you stay on stock, and wait for OTA update.

efishta said:
If you're on a rooted stock rom, assuming you haven't flashed a custom recovery, the phone's recovery utility will not allow you to flash an OTA update because of a signature mismatch. I'm not sure what happened with the evo, but I don't believe it can happen with the nexus.
Click to expand...
Click to collapse
No, this only happens with this specific update with the EVO.

Alright, great! Thanks guys. So since I believe the nexus one already got the offical OTA, did any of you lose ROOT access?

You WILL loose root when you update from an OTA update.

I had a rooted FRF50 and went to the FRF83 update and lost root/custom recovery, everything else was fine though.

I ask that you all forgiveth the newb nature of my question in advance, but if my phone has been rooted, and is currently running FRF50, is there anything I can do to the phone to have it automatically update using OTA? I ask because I received the notice for the OTA update the other day, but being rooted, got a signature mismatch error. (The only reason my phone is rooted is bc I bought it used that way-I wish I could've had it bone stock instead!) I know I can somehow do a manual update, but I'm trying to figure out for further future OTA updates if there's a way that I can have my phone simply automatically apply them.

Well, first off, thanks for hijacking.... AND, I have been doing a bunch of research. You should find the official build of froyo (FRF85B correct?) and manually update it. Just use it unrooted and it'll be easier when an OTA update comes along

OTA 139.15.1 keep root

All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?

First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X

Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...

You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X

The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X

mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.

dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X

mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk

juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.

MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191

will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.

MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!

boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.

will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.

jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.

will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.

jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being

OTA updates with rooted att GN3?

So I've been rooted on my ATT GN3 for awhile now and I have a custom ROM(UrDroid stock 4.3) installed using Safestrap.
For the last several weeks, periodically when I'm on wifi, I get a prompt that there is an OTA update. I can't decline it and it reboots the phone into recovery mode. I just choose to reboot again and it says the update did not complete.
I'm worried about loosing my root or worse. What do I need to do?

You can freeze the system app called "at&t software update".

Yeah, I could do that. But I would like to keep my phone updated if possible. Maybe it's better to wait for the official release of KitKat?
I would still like to get familiar with the process of updating while rooted though.

The irony in this is killing me...
If you update, you will lose root, but can just as easily get it back. And that is if the update even Installs with you rooted. It will normally fail. And since it is a custom ROM you should not even be getting a notification.
What bothers me is that you say you want to keep the phone updated, but continue to cancel the update.
I suggest you use a custom KK ROM. It is the most up to date.
Be it KnoxRaid based off of the leak for our device, or one of the few ported ROMs we have available.
Sent from my SM-N9005A using XDA Premium 4 mobile app

graydiggy said:
The irony in this is killing me...
If you update, you will lose root, but can just as easily get it back. And that is if the update even Installs with you rooted. It will normally fail. And since it is a custom ROM you should not even be getting a notification.
What bothers me is that you say you want to keep the phone updated, but continue to cancel the update.
I suggest you use a custom KK ROM. It is the most up to date.
Be it KnoxRaid based off of the leak for our device, or one of the few ported ROMs we have available.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I should explain that I'm still very new to the Android platform, having been a long time iPhone user. I've managed to figured out how to get my GN3 rooted and even install a custom ROM, but there are many things I still am unclear about on this platform.
Jailbreaking the iOS was relatively simple and straightforward. New iOS version comes out, wait for jailbreak, backup phone in iTunes and other apps like PKGBackup. Run jailbreak utility and restore everything the way it was.
Maybe I'm not quite understanding the process, but it seems hard to find direct step-by-step instructions for what I want to do. Maybe it's because there are so many different devices and ROMs, etc.
I don't want to lose all the apps/settings for my phone if I don't have to. I just don't know the best course of action to take in order to ensure that I am able to keep my phone updated and then rooted without losing everything.

I would also recommend the Knoxraid ROM. It's a great ROM and Drakey is constantly updating it. As of version 5.5 released today it's based on the latest OTA update. There is a step by step guide in the Knoxraid post that explains how to do everything. Take a look. It is pretty easy really.
As for backing up, you can backup all your apps/app data pretty easily with Titanium Backup. If you haven't already give it a look. There are tons of guides and how-to's available for how to use it. I know how overwhelming switching from iOS to android can be at first, but once you get the hang of things you will be so glad you switched. Good luck!

[Q] Lollipop OTA question

I recently upgraded my phone to an AT&T S5 (I decided I didn't like the S6 specs). Currently, the phone is 100% stock, unrooted. I know that previous Samsung phones had problems with OTA updates when they were rooted. Now, with the possibility that the Lollipop OTA is coming soon, I'm hesitant to root until the OTA comes out. Here are my questions:
1. Should I wait to root until after the OTA hits the streets, or is there a strategy to root and still safely apply the OTA?
2. I don't want to be one of the first to get the OTA since it may be buggy. Is there a way to delay the OTA if I'm not rooted?

So, nobody has any thoughts about this?

I can't tell you what you should do but I can tell you what I would do. I would root now, load Titanium backup, and wait for 5.0 to come out. With TBU I freeze the OTA so it's not pushed without my permission. Additionally TBU will backup everything going forward so I can easily move up and restore my apps.
I believe the current process to root will work so be patient.

woody1 said:
So, nobody has any thoughts about this?
Click to expand...
Click to collapse
I wouldn't even take the OTA. Lots of issues with it. I am pretty sure LP will be the same.
I rooted mine, installed SafeStrap, and installed the XDK ROM, which eliminates all updates. My phone works great, does everything I want it to. Don't need problematic upgrades to downgrade my system.

cmerlyn said:
I wouldn't even take the OTA. Lots of issues with it. I am pretty sure LP will be the same.
I rooted mine, installed SafeStrap, and installed the XDK ROM, which eliminates all updates. My phone works great, does everything I want it to. Don't need problematic upgrades to downgrade my system.
Click to expand...
Click to collapse
Thanks to both of you for your suggestions. I think I'm going to go ahead and root and stay on the stock rom for a while. If the OTA shows up soon and looks worthwhile, I'll give it a try. Otherwise, I'll install SafeStrap and try a custom ROM.

Sure. Here's an easy answer: if you search for S5 AT&T and lolipop, you'll find lots of things that will say that AT&T will be taking its SWEET time putting an ota upgrade for lolipop out.
It is available from Samsung thru Kies, and I think I am personally going to take a new rom, and try and upgrade and unlock this piece of junque (and I upgraded from a Galaxy SII! )
Sigh

[Q] Information Overload!

OK, I've read so much that things are just getting jumbled in my brain now. There's so much information in these threads that I don't know where to start. The world of Android apparently moves too fast for me to keep up. I've got a Verizon LG G2 that is stuck on 4.4.2, software version 24A. Right after I took the OTA KK upgrade I rooted with IORoot25. I don't think I've done anything other than root, however I have somehow can create the mobile hot spot without permissions. Not sure if there was an .apk that was put on when I rooted or how I did it because it was over a year ago.
Ever since I rooted, my phone tries to push OTA updates but they are always unsuccessful. Every morning I have to hit "Install Later" becasue it tried over night and failed. Besides this being a bit annoying, I haven't been concerned becasue the only OTAs since I got 4.4.2 was supposedly some small patch that didn't really do much (from what I read). But, the other day it notified me that it wanted to push Lollipop and needless to say, I want it.
My problem: I don't know what the hell to do! Besides rooting, I'm pretty sure the only thing I've done is download Flashify and backup my stock recovery. Flashify doesn't show that I have a custom recovery, nor do I ever remember installing one. Just whatever came with the IORoot25. Oh, and it looks like I Quarantined LGSetupWizard using App Quarentine. Pretty sure that's it. So, where do I go from here?? I'm wanting to move to Lollipop, then possibly de-bloat it, and would like a custom recovery so that I can create nandroid backups and possibly start trying out other custom ROMs.
I had an OG Droid for years and would flash ROMs frequently until I upgraded to a RAZR MAXX. Once I got the MAXX, and now the LG, all I've really done is root and hack the wifi, so I'm REALLY out of the loop now! Everything seems so complicated becasue there's just too much info out there. Could somebody please guide me in the right direction to make this as smooth as possible??
Thanks for reading and helping a NooB out. Ugh...can't believe I have to start calling myself that again!!

You could 'freeze' the update so it doesn't pop up every morning. IF you want to update- you can unroot it and then take the update and re-root it and fix the hotspot thing. I'm in the same boat, I'm about to do the same myself.

caecusscius said:
You could 'freeze' the update so it doesn't pop up every morning. IF you want to update- you can unroot it and then take the update and re-root it and fix the hotspot thing. I'm in the same boat, I'm about to do the same myself.
Click to expand...
Click to collapse
Thanks for the response. Hoe do I "freeze" the update? If I do decide to take the update and re-root, and especially if I start loading custom ROMs, I know I'm going to want to do this in the future. I've been getting theses OTA update notifications everyday for months now!!
Also, what's the easiest way to unroot?

AS long as you are running stock I believe you can accept the OTA without unrooting: I haven't done it yet as I haven't had a few free hours, but I'm going to try it tonight.
there are plenty of apps that allow you to freeze apps- titanium Backup Pro is one that comes to mind.