Database Info

[Q] should I update to 2.3.2 and reroot?

I recently just rooted my sns and got a notification for 2.3.2 and was wondering if I should install the update and see if the root sticks or
Unroot then install the update then root my sns
Sent from my Nexus S using XDA App

I'm assuming you're on stock rom.
Go ahead and update; some people are reporting they don't even lose root. I lost root privileges when I updated on stock rom but the files were still there, they had just had their executable permissions changed by the update. They're easy enough to get back.
I made some steps to follow using Clockwork Recovery that ensure you update and keep your root without needing a computer or any reboots. They're here" http://forum.xda-developers.com/showpost.php?p=10811723&postcount=29
If you have stock recovery and don't want to use Clockwork, go to the first post in that thread, and there's a link for stock recovery updates.
Edit, if you've got the OTA notification, you can just let it do its thing, and if you do lose root, just use fastboot to flash clockwork and then re-run the su zip file from it. You're back to full root.

unroot confirmation

hey all, currently have a g2x rooted with cm7, and i've been looking to unroot;
just to make sure i dont do anything stupid, i wanna run this through with you guys:
first i would flash the stock 2.3.3 ota rom for g2x
then use the http://forum.xda-developers.com/showthread.php?t=1056847 (one click nv flasher) to get back to lg stock recovery by clicking 'flash stock recovery' (do i need to dl anything extra for this?)
then im done, correct? if i boot up, ill get all the stock rom and apps and bloatware and etc back right?
thanks!
edit: how do i know which version of clockwork mod i have installed? im not sure if i did the external sd support or not...

You've gone back to a stock ROM, you've gone back to the stock recovery, but you haven't actually unrooted.
Whichever method you used to root, you should be able to use that same method to unroot.
UPDATE:
I was originally under the assumption that your 2.3.3. ROM was rooted. If it is stock you should be fine.

sorry for bump, but i read in tga_gunmans post that ppl should flash a rooted 2.3.3 rom and use superoneclick to unroot...would my method work too?

No your way would not work because the stock OTA by xboarder is rooted. Do what tga_gunman said. Flash the rom, use my unroot zip in CWM (deletes root files) and then flash the stock recovery. Busybox will still be on the phone but nobody should be looking for that.
Unroot zip: http://www.mediafire.com/?2vr7cmgg7qcdn14

Easiest way to confirm if your not rooted would be to install Superuser from the market. It'll tell you if the phone's not rooted.

There is an app on the market called Root Checker which is free. It will tell you if you are rooted or not.

A little extra help for me?
jboxer said:
No your way would not work because the stock OTA by xboarder is rooted. Do what tga_gunman said. Flash the rom, use my unroot zip in CWM (deletes root files) and then flash the stock recovery. Busybox will still be on the phone but nobody should be looking for that.
Unroot zip:
Click to expand...
Click to collapse
Thanks for your help jboxer. Forgive my noob-like understanding of rooting/unrooting terminology. Hopefully you'll be able to understand what I did.
Last night I went ahead with the unrooting process on my G2X which was running Gingerbread & CM7 following this youtube video (can't post link due to noobiness: watch?v=ryGIv8KQVIE), the order that this guy goes in is:
1. Wiping all cache/user data/formatting in CWM recovery
2. Restore to a barebones stock data in CWM recovery
3. Flash to go back to Stock using OneClickRecovery
4. SuperOneClick to unroot phone
What I ended up doing was restoring my phone to the backup that I created on my sd card when first rooting my phone rather than download that zip file in the video description which is a completely fresh start.
However, whenever I flashed to go back to stock using OneClickRecovery, it gave me that total barebones fresh start where I had to completely set up my Android from the first start screen and I lost my backup. Also, when I go to unroot the phone with that zip file, I don't know how to 'install from zip' after I've lost CWM Recovery menu. So, I flashed back to CWM so I could recover my backup from my SD Card again and install the 'unroot.zip' that you linked and it ran alright and I restarted, but I still had 'SuperUser' in my App drawer telling me that I was still rooted.
I ended up calling it good last night after spending two hours on it. I left my phone rooted, with CWM recovery still on my phone, but I at least I had my backup Gingerbread image with no CM7 mod. So, my phone is functional, but I would like to complete this process of unrooting completely.
Could you perhaps give a little guidance and clarity to what I'm missing or not understanding? I'd love to unroot/flash back to stock recovery/remove all evidence of rooting AND keep my recovered backup that I have before I even started rooting my phone.
Thank you so much for all your help, everybody.

[Q] Upgrading to new OTA update with rooted phone and TWRP

Hello everyone. I'm somewhat of a noob still and I would appreciate any help you could give me.
I'm trying to install the new OTA update that came out today but I'm having issues. I have a rooted One S with TWRP recovery, and everytime I try to install the OTA update it brings me to the TWRP recovery screen. I'm pretty sure this is because I don't have stock recovery. I've even tried "unrooting" with Voodoo Over the Air root, but it keeps bringing me to the TWRP recovery screen.
I rooted my phone with the All-In-One root kit, and I really don't want to lose everything on my device (or have the pain in the butt of restoring everything). Is there another way? Or is there an easy way to reinstall the stock recovery with the AIO kit? I know the AIO kit has the option to install other recoveries, but I'm not sure where to get the stock one.
Please help! I really want to upgrade.
Thanks so much for your help!

fsustrength said:
Hello everyone. I'm somewhat of a noob still and I would appreciate any help you could give me.
I'm trying to install the new OTA update that came out today but I'm having issues. I have a rooted One S with TWRP recovery, and everytime I try to install the OTA update it brings me to the TWRP recovery screen. I'm pretty sure this is because I don't have stock recovery. I've even tried "unrooting" with Voodoo Over the Air root, but it keeps bringing me to the TWRP recovery screen.
I rooted my phone with the All-In-One root kit, and I really don't want to lose everything on my device (or have the pain in the butt of restoring everything). Is there another way? Or is there an easy way to reinstall the stock recovery with the AIO kit? I know the AIO kit has the option to install other recoveries, but I'm not sure where to get the stock one.
Please help! I really want to upgrade.
Thanks so much for your help!
Click to expand...
Click to collapse
I personally had to flash stock recovery and you can get it from here: http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
Use second "Download" link, which is ville_recovery_signed.img

Thank you so much! Trying it now.
Sent from my HTC VLE_U using xda app-developers app

Charkatak said:
I personally had to flash stock recovery and you can get it from here: http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
Use second "Download" link, which is ville_recovery_signed.img
Click to expand...
Click to collapse
Check this out
http://forum.xda-developers.com/showthread.php?t=1907564
Scroll half way down and you get a list of different steps you may have to do in order to get it done.
Most include installing "OTA RootKeeper" from GooglePlay
Steps vary from how your phone is setup. Stuff like do you have Root, Custom or stock Mod, or CWM or stock recovery. Check it out. I'm trying it now.
(adding more to it so I don't double post.)
I tried the method with Root Keeper, it doesn't seem to work for me. It also seems as though a few others are having the same issue. Someone recommended use an RUU to go completely stock, therein losing all your data unless you back all that stuff up.
I'm going to avoid an RUU at all costs, I hate having to reset up my phone. Plus I just got a XOOM I need to work more on and get setup so I don't want to put more time on the phone than I have to as to take away time from my XOOM.
Let me know if you run into any success! PM if you need to.

Hello. Any stock recovery for Ville C2 (One S s3)? I'm looking everywhere and I cannot find. I want to update to JB with OTA

Today's (03/05/13) OTA

Haven't seen anyone post about this (even after doing a Google search), but Verizon has started sending out the OTA today. My question is this: since my bootloader in unlocked, and I'm rooted, can I restore back to my stock ROM and take the update? Is there a possibility that I'd completely lose root? Obviously I'd lose superuser and such, but would it replace my bootloader and custom recovery?
Thanks in advance for any helpful replies. I've been around android for a while now, but I'm new to Samsung phones, and how the bootloaders work. (I'm used to HTC where you S-OFF and you're good to go)

tylerlawhon said:
Haven't seen anyone post about this (even after doing a Google search), but Verizon has started sending out the OTA today. My question is this: since my bootloader in unlocked, and I'm rooted, can I restore back to my stock ROM and take the update?
Click to expand...
Click to collapse
Yup, you can restore back to stock (via nandroid or Odin) and take the update. You should switch back your recovery if you restore a stock nandroid though.
Is there a possibility that I'd completely lose root? Obviously I'd lose superuser and such, but would it replace my bootloader and custom recovery?
Thanks in advance for any helpful replies. I've been around android for a while now, but I'm new to Samsung phones, and how the bootloaders work. (I'm used to HTC where you S-OFF and you're good to go)
Click to expand...
Click to collapse
You answered your question, if you lose SU, you lose root. Verizon OTA's will replace your bootloader and custom recovery if you force the install to take through your custom recovery. It should fail initially but I've read around that folks installed the OTA in recovery.

I'll check my wife's phone tonight. If she gets the ota I will pull it from the cache and extract the boot loader and recovery and rezip it and see if it will flash via twrp

SlimSnoopOS said:
Yup, you can restore back to stock (via nandroid or Odin) and take the update. You should switch back your recovery if you restore a stock nandroid though.
You answered your question, if you lose SU, you lose root. Verizon OTA's will replace your bootloader and custom recovery if you force the install to take through your custom recovery. It should fail initially but I've read around that folks installed the OTA in recovery.
Click to expand...
Click to collapse
Ok thanks for the reply. What do you mean by switch back my recovery? I'm currently on TWRP which is what I rooted with, and I've been using it since. I just want a completely untampered stock OTA of the latest OTA.

tylerlawhon said:
Ok thanks for the reply. What do you mean by switch back my recovery? I'm currently on TWRP which is what I rooted with, and I've been using it since. I just want a completely untampered stock OTA of the latest OTA.
Click to expand...
Click to collapse
I mean, the OTA will fail if you just try to accept it right now. It would also fail if you switched back to your stock nandroid because you still have TWRP installed too. That's how its always been. Switching to the stock recovery, you could use EZ Recovery to do so, would resolve that.
I've read that you can still have a custom recovery installed and successfully take the OTA with a custom recovery installed but idk the exact steps to take to make this happen. Since I have no need for accepting OTA's I try to learn from what people post here.
Edit: Seems my OTA/custom recovery inquiry has been answered pretty thoroughly here (post #10). You could try those steps if you desire too.

SlimSnoopOS said:
I mean, the OTA will fail if you just try to accept it right now. It would also fail if you switched back to your stock nandroid because you still have TWRP installed too. That's how its always been. Switching to the stock recovery, you could use EZ Recovery to do so, would resolve that.
I've read that you can still have a custom recovery installed and successfully take the OTA with a custom recovery installed but idk the exact steps to take to make this happen. Since I have no need for accepting OTA's I try to learn from what people post here.
Edit: Seems my OTA/custom recovery inquiry has been answered pretty thoroughly here (post #10). You could try those steps if you desire too.
Click to expand...
Click to collapse
Hmmm sounds interesting. I doubt I'd be able to use EZ unlock like I did on ICS... I guess I'll wait for a recovery flashable file.

What OTA?

cammykool said:
What OTA?
Click to expand...
Click to collapse
4.1.2 ota being pushed starting today. According to Google+

Is this basically the same thing as the VRBMA2 leak?

pettigrew95 said:
Is this basically the same thing as the VRBMA2 leak?
Click to expand...
Click to collapse
Yes, it's a final version of VRBMA2 leak which is VRBMB1

Damn.... on the day i root... oh well glad i did!
vzw probably blocked our current methods.

The OTA de-odexed is already posted courtesy of beanstown over here:
http://forum.xda-developers.com/showthread.php?t=2177798

I'm rooted, unlocked and custom recovery w/stock ROM (odex).
How do I get this update installed and keep root/unlocked/custom recovery in place?
Also want to keep Google Wallet working correctly.

lexluthor said:
I'm rooted, unlocked and custom recovery w/stock ROM (odex).
How do I get this update installed and keep root/unlocked/custom recovery in place?
Also want to keep Google Wallet working correctly.
Click to expand...
Click to collapse
Download this and flash it through recovery once beanstown posts the links:
http://forum.xda-developers.com/showthread.php?t=2177798

pettigrew95 said:
Download this and flash it through recovery once beanstown posts the links:
http://forum.xda-developers.com/showthread.php?t=2177798
Click to expand...
Click to collapse
I'd rather have the odex version though. You think someone will post that?

OK I took it from cache. Does anyone remember what all I need to delete after I extract it so it doesn't update boot loader. Recovery for sure...here's where I am before i rezip

[Q] Verizon Galaxy S3 OTA after root?

I'm really confused about something and before I get flamed for not searching before posting, let me preface by saying that I have and still can't find a definitive answer given that nobody seems to reference the problem I'm having - at least it doesn't show up in my attempts to search.
My Question: Once I'm rooted, what is the process for accepting an OTAs (over the air updates) from Verizon? Whenever I download and install them, I get the "Custom" Lock Icon during bootup.
Here are the steps I've followed:
1. Flashed back to stock 4.1.1
2. Flashed the VRALEC bootchain
3. Flashed CWMR
4. Booted into CWMR recovery and ran the SuperSU_Bootloader_FIXED.zip (Note: no message appeared asking me about locking
5. Flashed the 4.1.1 bootchain
6. Downloaded and it auto rebooted to install the OTA (I wanted to see what it's like the NEXT time verizon pushes out an OTA so I know what the process is once all my apps are installed)
7. When finished applying the update it asks me: A. Do I want to Disable recovery flash? and B. Do I want to preserve root?
At first I tried answering both questions with yes and yes since I saw the message about that here: http://forum.xda-developers.com/showthread.php?t=2046439
My Problem: As soon as I rebooted, I get the custom lock icon message during bootup. So then I repeated the entire process and answered No and No to those questions. And again, I get the custom lock icon message during bootup.
Yes, I realize, I can and probably should install the OTA and then root the device. But that's not my point. I want to understand what to do the NEXT time Verizon pushes out an OTA. Do I have to flash back to stock every time I install the OTA and root the device only after installing the OTA just to avoid getting the custom lock icon? If not, how do I accept the OTA without getting the custom lock icon? (Obviously I can't seem to figure out how to do it now, so I won't be able to do it the next time an OTA rolls around - thus the reason for my question).
Thanks,
Jonathan

you might have to flash a custom ROM to block Verizon from pushing OTA.

http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Honestly, if you want the new feature just wait a day or two after the release. There is always a lovely developer waiting to debloat, deodex, and optimize the official OTA update for your use without breaking root access.
Have I helped with your question? Or have I misinterpreted your needs?

First, thanks for the replies!
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
Click to expand...
Click to collapse
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Click to expand...
Click to collapse
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?

jkrueger2020 said:
First, thanks for the replies!
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
Click to expand...
Click to collapse
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
Click to expand...
Click to collapse
I'll say this, most custom roms block Verizon OTA's from installing so you'll just have to accept that you need to flash back to stock to accept an OTA OR just stick to a rooted OTA based rom. There's at least seven of these, one per OTA or leak that we've seen to date.
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
Click to expand...
Click to collapse
Absolutely correct. Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's? Cuz you're inquiring an awful lot about OTA's for someone who would be using custom roms. That said, XDA devs have posted a rooted version of each OTA available. Each is in the dev section, they'll be titled something like "Stock Root JB 4.1.2 - I535VRBMB1 Official Update". You could easily just flash any one of these then pull down an OTA since these are left untouched with the only addition being SuperUser. Even still, you would need to re-root after accepting an OTA since OTA's wipe out root so you'll be doing this for as long as we see updates on this phone.

If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
Click to expand...
Click to collapse
Yes! That removed the lock icon. So my next question is, when my phone booted back up and said the OTA failed (yet still shows the incremented version number making it appear like the update actually was successful) was there anything that got messed up as part of the upgrade? Or would I be better off going the route of another person's reply which said I should lock the bootloader and flash back to stock recovery first before accepting the OTA?
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2
Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's?
Click to expand...
Click to collapse
Currently I'm not really looking for custom ROMS - my experience with ROMS with my original Galaxy S was just a buggy experience (i.e. call volumes that kept reverting to max for every call, etc) and was not very enjoyable. As long as I stay rooted and current with Android I'm happy at this point (of course that could change down the road).

mav3rick478 said:
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!

jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Almost worked flawlessly... I had to reboot from SuperSU to get root again.

I found the sdm thing to freez
smalrus said:
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
Click to expand...
Click to collapse
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.

joker66599 said:
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
Click to expand...
Click to collapse
Re-read the thread to find EZ Unlock, I'm fairly certain someone posted a link. I will say it's been removed from the Play Store for awhile now.
Freezing sdm 1.0 is all you really need to do. That's normal that it errors out now. You froze that setting so it won't be polling for an OTA nor allow you to manually search for an OTA. Whether you want the OTA or not is on you, there isn't much present that we do not already have in custom roms plus the OTA has already been rooted.
Sent from my SCH-I535 using xda app-developers app

This is what worked for me except I reversed step 5 and 6 (I edited the quote below to match what I did). Thanks!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse

Stock rooted MB1 here w/ TWRP. Tried to update earlier and completely soft bricked my phone. Had to do some fancy work to get it back and restore.
Now I tried this process:
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
and when I get to the step of actually installing the OTA - it reboots into stock recovery - and about 15 seconds in it fails and shows the android guy on his back. lol
It actually boots back into the phone properly & says that the update failed. Status page shows the baseband got updated, but not the ROM. Any ideas?
thanks
Edit: Bah. It's the stupid 'E: Error in /tmp/sideload/package.zip error.' According to my searches there's no easy fix.
Edit #2: I just wound up dirty flashing the full stock root package from Scott & Beans. That worked.

I'm running the MD3 on the stock ROM and rooted. Now when I originally rooted my phone (using this guide: http://forum.xda-developers.com/showthread.php?t=2046439), I'm fairly confident that I did NOT unlock the bootloader and also installed the CWM Touch recovery. After the process was over I had an unlocked padlock image show up on my phone every time it booted.
Now, I tried to install the new update via OTA (I defrosted all apps I had frozen) and when the phone re-booted to start the update, I received the warning message "System software not authorized by Verizon...." and in the upper left hand corner it says in red, "Secure: Kernel". The phone will continue to boot to this message. When I try to boot into recovery, it goes to this message, not the CWM recovery. The only way to get out of that message is to boot into Odin mode and hit Vol DOWN to cancel.
SO.....what do I need to do in order to install this new update?
UPDATE: I unlocked via EZ Unlock and rebooted into recovery and this time I was able to get into my CWM recovery and updated the zip file posted on another thread in the general forum. All is well now.

Can I upgrade OTA after root but on STOCK ROM?
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks

mandar_h said:
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
Click to expand...
Click to collapse
As of this moment, yes to both. The newest ota is VRBMF1 and you can still root/unlock that version just as easy as any other.