I took the JB OTA update. Which works great except the phone wont allow me to access my dialpad mid-call sometimes...weird. Anyway, I used Voodoo OTA Root keeper and took the update and restored...all check marks there, but no root. So i decided to wait for an exploit for a lil while and then i got my wish! Which using ubuntu and the terminal and not windows seemed easier to me so i set it up.
Did all the steps and it worked! or so i thought...phone vibrated and came back on with the superuser apk etc. Check with root checker...no root. Not sure where my conflict is coming from now? Not sure if I should Fxz JB 4.1.2 or what, I've been reading some things on that thread, different problems people have had seemingly with the firmware. I didn't think it should matter as far as rooting the phone goes, but one person was saying that using it would stop the exploit from working? Never thought that would be the case, am i missing something?
Also, my phone after i tried both of these keeps asking me to update my superuser binary. First with one superuser app and now with the one that was with the exploit package and i can't seem to do it. Feel like i'm missing something simple here but i'm not sure what it is?
Did you wait for the vibrations and then press a hardware button, like vol up or dn? Others have reported having to go through the exploit more than once to get it rooted. Give it another try. I was able to get root on the second try, but I royally messed up the process the first time.
Embarrassing, but no I forgot the hardware button. Worked like a champ second time lol my advice don't do this late when your not awake, follow all the steps!
Sent from my XT875 using xda premium
Related
Just did the software update today and it all went smooth after unfreezing all original apps I had originally froze with TiBu. I noticed that I lost root after the update, which I thought was no big deal until I tried to re-root. I tried the ADB method, SuperOneClick, and also thecubed's way with no success. Don't know if it is just me or if lg/verizon changed something in the update. When doing the ADB method I am stuck at pushing rageagainstthecage. I get the "Permission failed to copy..." message, but doing "adb usb" and "adb root" no longer fixes this. Also, "adb root" shows "adbd cannot run as root in production builds". Anyone else having trouble after the new software update?
I lost root, too. I've only been able to try SuperOneClick so far, but I haven't been able to get root back yet either.
Sent from my VS910 4G using XDA App
I am on the same boat...
I cant root either with SuperOneClick version 1.7 or 1.9.5
Am going to try with the latest and greatest version today
Yeah, I'd suggest no one update if they want to keep root. I've seen this on my last phone (Eris) and it took the devs literally months to figure it out.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
I have tried the newest version of SuperOneClick and it does not work either. Hopefully someone will figure this out soon as I really miss having root.
Daaaamn that sucks y'all. **** could be months before ifs fixed depending on how secure they made it.
Sent from my VS910 4G using XDA App
Oh no. .. I lost root too... on dyin
Sent from my VS910 4G using XDA Premium App
majorpay said:
Yeah, I'd suggest no one update if they want to keep root. I've seen this on my last phone (Eris) and it took the devs literally months to figure it out.
Click to expand...
Click to collapse
An Eris user!
OT: I never had root to begin with, I've downgraded to V4 yet it discontinues to let me have root.
i never did the update, but have you tried the gingerbreak app?
Lost Root after OTA too using superoneclick 2.1.1 failed
I know probably lots are in the same boat by browsing the forums and I'm assuming the following data has already been provided but on the off chance it has not :: here was my failure (see attachments screenshots) :: and specs::
Phone LG Revolution
Model :: VS910 4G
Android version : 2.2.2
Baseband version :
VS910ZV6-M7X30-AABBQMLYM
Kernel Verion
2.6.32.9-perf
[email protected] #1
Build Number
VS910ZV6
SW Version
VS910ZV6
Interesting note is that after the update, my inductive charging stopped working properly on the rooted phone. It was working fine prior to the update. I have two phones, one rooted one not. It would state that I have removed my phone off the charging pad as the phone is sitting there on the charge pad. the pad states that it is still in charging mode but all charging stopped on the phone. I also notice that the USB port is behaving strangely too. Unrooted the LG but it still behave the same from the update. I haven't been able to root it again yet.
Yup Software Update Loses Root and R/W File System
I restored back down to v4 (from the v6 update), wiped the phone. And still cant mount the File System as R/W
Tried Super One Click 2.2.1, Z4 1.3.0 both failed for the same reason (both exploits)
Super User and Root Explorer both crash whenever they try to remount the File System.
If anyone finds a way to unlock, let me know.
I am personally gonna put back v6 for now, but i dont like feel inhibited.
Sleepykat said:
Interesting note is that after the update, my inductive charging stopped working properly on the rooted phone. It was working fine prior to the update. I have two phones, one rooted one not. It would state that I have removed my phone off the charging pad as the phone is sitting there on the charge pad. the pad states that it is still in charging mode but all charging stopped on the phone. I also notice that the USB port is behaving strangely too. Unrooted the LG but it still behave the same from the update. I haven't been able to root it again yet.
Click to expand...
Click to collapse
My USB was acting strangely too, until I lost it totally (as posted in another thread). I used to be able to do an extended battery pull and it would come back...now nothing. I hope this isn't happening to yours too.
I backed up my data then did a hard reset. The USB restarted again. I noticed a few apps that VZN has triggers this so I testing it from that point. Those apps shouldn't/ didn't affect the USB prior to the update.
So http://forum.xda-developers.com/showthread.php?t=1211295 explains how to downgrade after the update to then root, but since this has been figured out has all progress on developing a way to root the phone after the update stopped? I still like some of the features with the stock rom after the update and am wondering if anyone is working on a new exploit still, or if downgrading is the only fix on the horizon?
bjjryan said:
So http://forum.xda-developers.com/showthread.php?t=1211295 explains how to downgrade after the update to then root, but since this has been figured out has all progress on developing a way to root the phone after the update stopped? I still like some of the features with the stock rom after the update and am wondering if anyone is working on a new exploit still, or if downgrading is the only fix on the horizon?
Click to expand...
Click to collapse
A little birdie told me that someone is working on a fix. No time frame and no guarantees, but one is being worked on.
Sent from my VS910 4G using xda premium
mtmichaelson said:
A little birdie told me that someone is working on a fix. No time frame and no guarantees, but one is being worked on.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Oh snap
I tossed my Crap, Revolted and moved out of my Home.
root
Wish I could root, got my phone when the update was already on it
I had another thread about rooting my Bionic and I was getting help. I did have more questions and was hoping that as the process went on, I would get answers. I guess it just kinda died since no one is answering my last questions. If anyone wants to check it out, it's in this section and the only one I have posted.
Anyway, the main question I have, and I figured it would be better to start it's own topic, is about updating to JB on a rooted phone. I have read many threads and lots of people either messed up root or bricked and had to start over. I guess it's not so much a question, more like directions on doing it properly. Like I said, I have read posts with instructions and a bunch of people chime in saying they did everything but still lost root. So there could be something unclear in those instructions and I don't want to take a chance. I will tell you what I have so far and what I have done.
I rooted my phone using this method
http://droidbionicroot.com/droid-bionic-root/how-to-root-ics-on-droid-bionic-and-motorola-android/
The root process I used gave me SuperSU and didn't tell me the version for the SU binaries. I searched around and all I could find was info on SuperUser in regards to backing up root. I uninstalled SuperSU, kinda. I just told it to use a different SU cuz when I used SuperUser and updated the binaries, SuperSU wanted to update them, then I opened SuperUser and the binaries reverted back. I was worried so I just told SuperSU to use a different SU. Was that ok?
SuperSU is no longer there, just disappeared. SuperUser is still on my phone.
Got safestrap tho still not updated to 3.11, got TBU (free), got Voodoo.
I have not made a backup with TBU.
I did do protect root with Voodoo but that was a week or so ago.
I have not made any major changes. BUT, I do have Hide It Pro and the apps I have hidden appear in TBU as frozen. Well at least it is highlighted and the option defrost is there.
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Don't be afraid....
The worst that can happen is you brick your phone and have to redo EVERYTHING. And chances are that won't happen if you're considering this and have done things in the past.
I only keep one SU app on my phone, but I have heard about being careful if you do have more than one not to confuse the binaries, so maybe if you can uninstall one and just use the one you kept to do everything, I'd say do that, but again I don't know.
I would also be careful about anything frozen especially if it's a system app or bloatware in the system...
See my other thread [Trifecta] Jelly Bean Update...I had all kinds of issues and made it thru, I'm sure you could too.
Cheers.
Ok, but what exactly do I do? I haven't modded anything, just rooted and "froze" apps. I know that after reading that I should take my phone back to where I had it right after root with no changes. Like I said, my phone has no mods and nothing has really changed. So what is the best way to update and keep root? Only reason I want to keep root is because it was easy and I don't want to do it again but more complicated (don't know Linux) If someone wants to type it out, step by step, or link to instructions that you followed exactly and succeeded in updating and keeping root, please do so.
As far as the GSM hack, not sure if I really need that.
Sorry....wasn't leaving you hanging...
You can try an app called OTA RootKeeper by Voodoo, it seems to work most of the time. But from what I understand once you start the update to JB even if it fails you can't go back. So if you update and lose root...
Go HERE
Read thru it, then follow the links to all info, tools & instructions.
Cheers.
Thanks. Hopefully everything goes ok with the update. I really don't want to spend a day learning and updating programs I never used. But if the update fails I guess I have no choice. I will wait till I know I have time, probably this weekend.
CycoPuppet said:
Thanks. Hopefully everything goes ok with the update. I really don't want to spend a day learning and updating programs I never used. But if the update fails I guess I have no choice. I will wait till I know I have time, probably this weekend.
Click to expand...
Click to collapse
I was chiming in for what little help I could offer on your other thread, and then I ran into an unexpected glitch myself. You can read all about it here. Basically, if you do an FDR for any reason on the stock ROM in SafeStrap, you are probably going to run into problems. It's happening to a ton of other people.
CycoPuppet said:
I had another thread about rooting my Bionic and I was getting help. I did have more questions and was hoping that as the process went on, I would get answers. I guess it just kinda died since no one is answering my last questions. If anyone wants to check it out, it's in this section and the only one I have posted.
Anyway, the main question I have, and I figured it would be better to start it's own topic, is about updating to JB on a rooted phone. I have read many threads and lots of people either messed up root or bricked and had to start over. I guess it's not so much a question, more like directions on doing it properly. Like I said, I have read posts with instructions and a bunch of people chime in saying they did everything but still lost root. So there could be something unclear in those instructions and I don't want to take a chance. I will tell you what I have so far and what I have done.
I rooted my phone using this method
http://droidbionicroot.com/droid-bionic-root/how-to-root-ics-on-droid-bionic-and-motorola-android/
The root process I used gave me SuperSU and didn't tell me the version for the SU binaries. I searched around and all I could find was info on SuperUser in regards to backing up root. I uninstalled SuperSU, kinda. I just told it to use a different SU cuz when I used SuperUser and updated the binaries, SuperSU wanted to update them, then I opened SuperUser and the binaries reverted back. I was worried so I just told SuperSU to use a different SU. Was that ok?
SuperSU is no longer there, just disappeared. SuperUser is still on my phone.
Got safestrap tho still not updated to 3.11, got TBU (free), got Voodoo.
I have not made a backup with TBU.
I did do protect root with Voodoo but that was a week or so ago.
I have not made any major changes. BUT, I do have Hide It Pro and the apps I have hidden appear in TBU as frozen. Well at least it is highlighted and the option defrost is there.
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Click to expand...
Click to collapse
You were trying to use two different superuser apps (superuser and SuperSu) to control the su binary - each comes with its own binary, so when you used one to update su, then the other is naturally going to complain.
Clean Install
CycoPuppet said:
So yeah, I want to make sure I update correctly. And I know some of you will either think or actually post that I should search. I assure you that I have. I just want to make sure it's not the instructions and it's just the person's mistake for not following instructions. I did see a post that had a bunch of people saying it didn't work and then 3 pages in a person said "oh you were supposed to do that" which was never made clear.
Click to expand...
Click to collapse
I highly suggest that before you try anything, you make a backup of your device with TBU and then copy the TBU file to your PC.
From what i've heard the cleanest way to keep root and get to JB is to backup everything, flash the ICS fxz, root, backup root with Voodoo and then take the ota update. This should put your phone on stock rooted JB. From there you can download TBU and restore your apps and data.
This is a bit excessive but it should in theory fix any issues that could arise from having frozen apps or otherwise changed the system.
ian_mcxa said:
I highly suggest that before you try anything, you make a backup of your device with TBU and then copy the TBU file to your PC.
From what i've heard the cleanest way to keep root and get to JB is to backup everything, flash the ICS fxz, root, backup root with Voodoo and then take the ota update. This should put your phone on stock rooted JB. From there you can download TBU and restore your apps and data.
This is a bit excessive but it should in theory fix any issues that could arise from having frozen apps or otherwise changed the system.
Click to expand...
Click to collapse
DO NOT ATTEMPT TO FXZ TO 246 ICS NOW. You've already updated to JB, and you will brick your phone if you attempt to go back.
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
linux minimal screen shot, and unbuntu hang up
DanRyan85 said:
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Well, not to be insulting, but it was my understanding that moto chopper would only work if temp rooted or had gained root acess previously? I may be wrong. Anyways, the prob. with unbuntu is thing i guess froze (but still ran) after patiently running it like six hours. Last screen at was installing-reinstalling previous "somethings" but I figured need a system clean and would try again. gotta be easier way. so here is my linux minimal screenshot attempt. running root bionic jb ovf file. noticed where it starting going wrong is
chmod: pwn: operation not permitted.
rooting phone...
phone may appear to.......
/system/bin/sh: /storage/rfs0/pwn: not found <-------Right here i noticed the file path on the phone and it's ---> storage/rfs1 Would that have something to do w/ it?
nothing ever vibrates and reboots in flash. got bad flash or something?
MotoChopper works on non TI (OMAP) CPus that are in Motoroal devices.
Coincidentally, it also works on ASUS Tranformer Infinity (and the Prime as well, IIRC).
It does not work on the BIONIC.
The method that works on rooting the JB build on the BIONIC is one that is based upon the older RAZR method - see http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/
Bionic and JB OVA flash superuser binary outdated
Naughtybutbritt said:
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
Click to expand...
Click to collapse
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
To Naughty: Sorry about the mix up that was what I meant to say Moto share 2 NOT Motochopper. I had all the same problems as you after some number of tries with motoshare2 I was in business.
To martin: have you already tried the motoshare 2 on Ubuntu?
Sent from my XT875 using xda premium
toddmartin- you're gonna love me...i gotcha
toddmartin said:
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
Click to expand...
Click to collapse
Ok so using virtual box the ova Root_Bionic_JB_20130501-4 the fourth ubdate of the orginal release. Now i suggest erasing all superuser apps installed your self and anything to do with them. When it's done right, it will appear on it's own and work flawlessly. No uncertianties about it. Then i've posted a screen shot of the commands with notes to help understand easiest. The instant the command to press hardware key or power/or each volume itself is the instant you want to press it. Now the reboot is instantious kinda itself and gotta be noticing phone unless have ungodly long boot up let me know if the screen shot helped what you were asking.
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.
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.