Database Info

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] Restore backup to get ICS OTA Update?

Before I go wiping my device again in anticipation of getting the OTA ICS update...
I made a backup of my device when I was on the original Honeycomb build after rooting. I then switched to the Prime ROM. I'm assuming that I can just restore my Honeycomb update, get Root Keeper and install the OTA update. Am I correct, or is there something that will stop me from doing this?
Edit: Also, when restoring a backup using CWM, does it automatically wipe the device before restoring, or does that need to be done manually?

I believe you also need to restore the original recovery. The last time I tried to flash an upgrade on my rooted stock image using CWM, it rebooted after downloading and rejected the (non-stock) recovery. I'm guessing the ICS update will require a reboot into the stock recovery as well.

Spookymonster said:
I believe you also need to restore the original recovery. The last time I tried to flash an upgrade on my rooted stock image using CWM, it rebooted after downloading and rejected the (non-stock) recovery. I'm guessing the ICS update will require a reboot into the stock recovery as well.
Click to expand...
Click to collapse
Indeed, no OTA update when original recovery is not installed.

I looked around a bit and saw how to unroot and restore to stock recovery... is there an easy way to just restore stock recovery? My plan was to restore my stock backup (to get off revolver) and then can go from CWM -> Stock, I just wasn't sure how to do the last part without undoing everything and fully returning to stock/no root.

It's also very possible that Root Keeper will not work since this is a new firmware form the ground up.

chadcspencer said:
It's also very possible that Root Keeper will not work since this is a new firmware form the ground up.
Click to expand...
Click to collapse
OTA Rootkeeper do not work if the system partition is formatted. Which is not the until now. Also people reported OTA rootkeeper worked to get root back after ICS update.
Otherwise use vipermod option 1 to root on ICS.

darkstar107 said:
Before I go wiping my device again in anticipation of getting the OTA ICS update...
I made a backup of my device when I was on the original Honeycomb build after rooting. I then switched to the Prime ROM. I'm assuming that I can just restore my Honeycomb update, get Root Keeper and install the OTA update. Am I correct, or is there something that will stop me from doing this?
Edit: Also, when restoring a backup using CWM, does it automatically wipe the device before restoring, or does that need to be done manually?
Click to expand...
Click to collapse
I just did exactly this. I had a nandroid backup of my original stock honeycomb so I restored the backup (I had some problems with the kernel after restoring from Revolver with some OC kernel, but flashing "plain" Revolver and then restoring the stock rom from the backup did the trick).
After that I made sure that everything is OK - I checked that I'm on the correct pieces of the software, in particular the kernel. All looked fine so I pulled OTA update, but before applying it I had to restore stock recovery. For this I used the stock recovery linked in this thread: http://forum.xda-developers.com/showthread.php?t=1154947 Just downloaded it, placed it on my SD card, rebooted into CWM recovery and flashed it (pleas note - I only downloaded this single file, not needed to download any other files mentioned n the above thread since I already been on rooted stock rom).
After booting the TF again, I made sure that my root is backed up with Supercurio's Root Keeper, then I applied the OTA and after a few minutes I was happy user of ICSed Transformer.
Please note that what worked in my case may not work in yours though. So be careful, think twice, and keep in mind that it's your decision - your risk (and if something goes wrong - your brick )
BTW, all applications, data, etc. are still in place. Root was restored via Root Keeper. Then I downloaded some updates of applications and so far I'm fine.

No OTA after Root?

I used the 1-click method to root my phone. When I do the software update it goes as far as downloading the update, then my phone reboots. And for some reason when it reboots it reboots into recovery. Then I reboot my phone and when it loads it says update failed. The update is 2.3.5 to 2.3.6 I'm assuming. The reason I make this assumption is just because my wife and I got the same phone on the same day and hers updated and mine didn't. I rooted, she didn't. I read something about having to have all your original apps installed when I did a search, but I have removed any of the bloatware or any other apps as of yet. Thanks for the help in advance!

To Take the OTA you need Stock recovery, not CWM there is a thread with the Stock recovery you can flash in Odin to get the OTA to install
Check out this link to another post on here http://forum.xda-developers.com/showthread.php?t=1360943&highlight=stock+recovery+odin
this should be what you need to take the 2.3.6 OTA (which really isn't all that worth it, so if you're happy with 2.3.5 i would stay there until an ICS OTA comes)

Would a factory reset go back to stock recovery?

sumnerm1 said:
Would a factory reset go back to stock recovery?
Click to expand...
Click to collapse
No a Factory reset just resets the user data not the recovery or system information

scubamikejax904 said:
To Take the OTA you need Stock recovery, not CWM there is a thread with the Stock recovery you can flash in Odin to get the OTA to install
Check out this link to another post on here http://forum.xda-developers.com/showthread.php?t=1360943&highlight=stock+recovery+odin
this should be what you need to take the 2.3.6 OTA (which really isn't all that worth it, so if you're happy with 2.3.5 i would stay there until an ICS OTA comes)
Click to expand...
Click to collapse
My understanding was that 2.3.6 implemented a new modem that improved the performance of the phone. I personally have great service compared to my Tmobile that I just bought out my contact on. Just wondering how much better that update would make my phone.
Sent from my SAMSUNG-SGH-I727 using XDA

If your rooted you can just flash the 2.3.6 radio in cwm... Or even a 2.3.6 ROM (MHX superlite 3.1 final was my GB ROM of choice)
There is a radio thread and also info in the all in one sticky thread.
Sent from my SAMSUNG-SGH-I727R on Alien ICS #8

[Q] issues after root and soft brick

Phone: Verizon galaxy s3 I535 US version
(/i53.photobucket.com/albums/g71/JlSmall/Screenshot_2012-10-01-08-27-33.png[/url]
Sorry can't post full link yet
To make a long story short, I wanted to receive the Verizon ota update so it would go away. I found the firmware update for rooted galaxy s3 I535 and flashed it. After I rebooted it did the yellow triangle and said software not allowed by Verizon.
Assuming it was a soft brick, I downloaded the Verizon galaxy s3 stock Rom software ,flashed and cleared data sync cache.
It rebooted but still showed open lock and said custom ( not sure what that means) since I set it back to factory out the box format.
After it booted I placed in usb debuging and flashed the stock root software which included su and adb.
It restarted the phone normal with superuser.
As I was downloading the busybody, Rom manager, titanium backup, apps
Verizon downloaded the new ota update and went into there flashing mode. It finished update and restarted.
But now I can not gain root permission to flash cwr Rom to recover phone. This is where I need help please
I will try to update with file names when I get home tonight.
What is wrong?
And last question after I get permission, can I go back to recovery send use my last back up and recover all my apps, data and user files with out going back to before ota update.

it showed the custom unlock because your rooted. ota breaks root and yes you can restore your backup. although you will be prompted for the OTA again. I would advance restore data and not your full backup.

droidstyle said:
it showed the custom unlock because your rooted. ota breaks root and yes you can restore your backup. although you will be prompted for the OTA again. I would advance restore data and not your full backup.
Click to expand...
Click to collapse
How is it still rooted after flashing complety stock software. Firmware and Rom
And how do I get su permisson

rtrip9 said:
How is it still rooted after flashing complety stock software. Firmware and Rom
And how do I get su permisson
Click to expand...
Click to collapse
oops i read your post wrong...it shouldnt be unless you used the odin file root66.

droidstyle said:
oops i read your post wrong...it shouldnt be unless you used the odin file root66.
Click to expand...
Click to collapse
I believe I used the stock root I'll have to see when I get home. But that ringes a bell. I know I used the stock then flashed a stock root to regain root. It said su and adb was with it. It's the one in a YouTube video. But I stoped at min 3:30 bc I have Rom manager to flash cwm
Should I Just try another root or do you have unroot. First then flash another. Usually I run into issues like this.
The other question is should I upgrade to jelly bean

rtrip9 said:
I believe I used the stock root I'll have to see when I get home. But that ringes a bell. I know I used the stock then flashed a stock root to regain root. It said su and adb was with it. It's the one in a YouTube video. But I stoped at min 3:30 bc I have Rom manager to flash cwm
Should I Just try another root or do you have unroot. First then flash another. Usually I run into issues like this.
The other question is should I upgrade to jelly bean
Click to expand...
Click to collapse
Here is the su page. Are the things in red the issue.
//i53.photobucket.com/albums/g71/JlSmall/Screenshot_2012-10-01-14-19-34.png[/IMG]

problem solved
rtrip9 said:
Here is the su page. Are the things in red the issue.
//i53.photobucket.com/albums/g71/JlSmall/Screenshot_2012-10-01-14-19-34.png[/IMG]
Click to expand...
Click to collapse
i solved the issue, I ended up completly re rooting and not using oden. this fixed everything

[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.