Yup, just reroot. If you want to go back restore your nandroid.

 

I'm not entirely sure on that one.

I've always flashed the latest updates as soon as they come out. I've never been in the situation of wanting to stay on the older stock ROM.

Hopefully someone else can chime in. :thumbup:

 

I am rooted, but I'm also on sprint and currently running an AOSP ROM

 

Why do some folks get the option to update or have it forced upon them? Is it because they run the stock rom as the op has?
I have never had an update pushed, or asked of me, but that could be because I run a custom rom?
Also, question to the OP...is your bootloader unlocked? Just trying to get my info correct as to the ability for an update to successfully install.

 

It does seem weird that the ota installed of you had twrp installed. Usually having custom recovery installed prevents otas from installing.

 

Ah that's it I wasn't sure if it was a custom recovery or an unlocked bootloader that should prevent an OTA

 

hmmm, very odd
Well, I would do as Rxpert suggested and reroot ...what method did you use before?

 

Was this the update that fixed all the radio issues from the prior one?

Big red may have forced that as it was a critical fix

 

Yes...you think that update could override root etc? Kinda sounds like it eh?

 

No clue

Custom recoveries can usually handle an ota file, they just usually fail on the system checks.

They may not have done the normal system checks. Hard to know what happened without delving into the file.

 

That image indicates that your bootloader is unlocked

 

Running stock 4.1.2 rooted on S3.

VZ pushed an update that fixed the earlier release that enabled multi-window that was bad and broke many things, the radio being one.

Had root before they pushed out the "fix" . So naturally I can't get TI backup to run or any other program that needs root .

Do I just re-do the entire 3 step process using ODIN as before to get root back?

Or do I just need to do 2 of the 3 steps (let me know which ones) since I already have unlocked the bootloader before VZ pushed the fixed update out. Thanks

 

@ bucknasty--Hmm, yours is the 3rd post about this happening--Verizon pushing out the update that is breaking root for folks...something odd is going on I think..not sure.

But anyways, if I were you, I would try to get root back by going to this guide:
http://forum.xda-developers.com/showthread.php?t=2046439

since your bootloader is already unlocked, I would download the SU file in step 1 (prep)/#3/bullet point 1.
I would assume you have no custom recovery either?

Then do all the steps except #5 (restoring the bootchain)--because the MF1 bootchain is not up and running yet there.

I surmise that would work...it will install SU and a recovery.

Now like I said the MF1 bootchain is not posted there yet...I know he, (open1your1eyes0) is looking for it to post in his guide there.

My best educated guess is that will get your root back and your custom recovery.

 

Breaking root isn't uncommon for otas. The su binary installs to a place that is generally overwritten when an ota is installed. Hence, if it's overwritten, it's no longer there and thus no root. That's why it's nice to use one of the root protection methods, provided by either Voodoo rootkeeper, SuperSU root protection, etc because it creates a backup of it in another part of the root directories that isn't touched by otas, generally only factory image flashes. Then when root is broken by the otas, you can use the program to copy the backup back to it's proper location.

 

Ha, I just responded in this thread about the same thing...I may merge these two threads as they deal with the same issue:
http://androidforums.com/verizon-ga...ked-bootloader-no-root-after-mfr1-update.html

 

Merged threads...

 

Thanks! I will wait for the MF1 bootchain to appear and a couple of others to "go first" and see what happens.

 

Someone else may have a better idea, as my idea is not gospel truth, but my best guess