Database Info

tmo sensation update

i just check for update and it tells me to download it i am on tmo us, east coast,
my question is should i do it ? i am s-off and rooted with revolutionary

You can if you want, it'll update fine, or let it download to your SD card and save the ZIP file and upload it somewhere for everyone else waiting on it

You could be the first one to test it.

I take it back - do NOT flash it if you're running a custom ROM as you'll be deodexed and it'll probably **** it all up. If you were ONLY S-OFF then you'd be OK

uploading right now will post link soon

no custom rom just stock with s off

http://www.megaupload.com/?d=0E5QQFSG

You should be OK to update it then, but do so at your own risk. Might be better to go back to 100% stock (take a nandroid) then flash the file (if it allows you) and then re-S-OFF

it fails to update, it starts and just sits on anroid guy and triangle

amorek13 said:
it fails to update, it starts and just sits on anroid guy and triangle
Click to expand...
Click to collapse
i m getting same thing...stock with s-off not rooted with custom recovery...

pulled battery and will wait to find out why stock with triangle with ! and android. waited 25 minutes nothing happen.

I have the update now as well.. Tmous.. Doesn't seem like this update is working well. I will definitely wait on updating
Sent from my HTC Pyramid

im on the fence.... should i unroot and return to s-on to get the update or should i just keep waiting for CM7....? i only really rooted because i wanted CM7 but that might take a couple more weeks.... Does anybody know if the revolutionary s-off method works after the update?

I posted this in the general forum. Maybe it will be useful here as well.
Stock Tm-US with s-off and rooted.
The update would not apply for me either.
I re-flashed stock boot.img and reovery_signed.img.
Still no OTA. Same triangle w/ exclamation point others are describing.
Apparently in stock recovery, if you press volume up & down, it brings up the recovery console.
There was an error on checking the file "HtcLocationPicker.apk"
I hade installed the htc locations app, and apparently this file gets overwritten from the stock build.
Going to try to replace HtcLocationPicker.apk & HtcLocationService.apk with the files from the stock build and see if that works.
Edit: Yep, that did it. Update applying now.
You rooted folks that can't get the update to apply, how many had installed the HTC Locations App?

installed without a hitch for me ... Stock with S=OFF. Didn't have to do anything to it.
I checked the boot screen...I still have S=OFF after updating but there is a nice pink bar at the top that says "Locked".

bobsyour said:
I posted this in the general forum. Maybe it will be useful here as well.
Stock Tm-US with s-off and rooted.
The update would not apply for me either.
I re-flashed stock boot.img and reovery_signed.img.
Still no OTA. Same triangle w/ exclamation point others are describing.
Apparently in stock recovery, if you press volume up & down, it brings up the recovery console.
There was an error on checking the file "HtcLocationPicker.apk"
I hade installed the htc locations app, and apparently this file gets overwritten from the stock build.
Going to try to replace HtcLocationPicker.apk & HtcLocationService.apk with the files from the stock build and see if that works.
Edit: Yep, that did it. Update applying now.
You rooted folks that can't get the update to apply, how many had installed the HTC Locations App?
Click to expand...
Click to collapse
im a little confused... so you basically just unrooted and s-on ?

Nope. Still s-off.
Flashing back to stock recovery & boot did not remove s-off or root.
Applying the update did remove root, but still s-off.
Once I applied the update, I reflashed CWM image. Then re-applied the superuser.zip with CWM.
Then it was a matter of restoring htc locations app with titanium back. I did back it up before restoring stock apps.
HTC Sense was force closing on me, but I cleared the data for sense and that has stopped.
Just need to set my home screen back up and I am golden.

bobsyour said:
Nope. Still s-off.
Flashing back to stock recovery & boot did not remove s-off or root.
Applying the update did remove root, but still s-off.
Once I applied the update, I reflashed CWM image. Then re-applied the superuser.zip with CWM.
Then it was a matter of restoring htc locations app with titanium back. I did back it up before restoring stock apps.
HTC Sense was force closing on me, but I cleared the data for sense and that has stopped.
Just need to set my home screen back up and I am golden.
Click to expand...
Click to collapse
aight bet,
im gonna try it.... i just gotta go search for the stock recovery and boot

Jesushasadroid said:
i m getting same thing...stock with s-off not rooted with custom recovery...
Click to expand...
Click to collapse
sorry guys...turns out i was rooted..update wont work with rooted, s-off and custome recovery...stock rooted will be out later or tomorrow...no worrres...senstation flys with Android Revolution...

just got home and updated. had to return back to stock recovery to do it though..... it seems way more snappier

[Q] Firmware Update Not Completing

I received notice this morning that a firmware update was ready to install. I chose to install it and the tablet rebooted and start to apply the update. However, it gets to 32% on the update install, stalls, and then reboots and does the exact same thing.
Any thoughts on a solution?

rrhutch said:
I received notice this morning that a firmware update was ready to install. I chose to install it and the tablet rebooted and start to apply the update. However, it gets to 32% on the update install, stalls, and then reboots and does the exact same thing.
Any thoughts on a solution?
Click to expand...
Click to collapse
i have the same problm :crying:

Need more info than that.
For example... Are you rooted or stock?
If rooted, there are a couple of reasons off hand I can think of you could be having a problem.
If you're stock, well... All I can think of is wave your hands in the air, and wave them like you just don't care. Pretty sure that won't fix the problem though, but if it does, report back! xD

I'm rooted.
Sent from my DROID RAZR using xda app-developers app

exactly the same problem
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.

ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse
I'm in the same situation.
I'm going to try http://forum.xda-developers.com/showthread.php?t=1849994
when I get home tonight to see if this fixes it.

Is there any way I can at least access the internal storage somehow and copy my data?
There are some important job application info in S Note..
ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse

ytdong said:
Is there any way I can at least access the internal storage somehow and copy my data?
There are some important job application info in S Note..
Click to expand...
Click to collapse
you should've sync your snote data with drive or dropbox!!! any firmware update 101 is to back up all your data

ytdong said:
I have the exact same problem.
GT-N8013, rooted, stock rom with root injected.
I called Samsung tech service and they said I should send my device to them.
The only way I can get out of this "update->reboot->update->reboot->..." infinite loop is to get into ODIN mode. (I can't turn off the device)
I decided to re-flash my rom (stock rom with root injected) in ODIN mode, but it does not have any effect and the device is still on this infinite loop. I'm worried if I messed up the device even more by doing that.
Click to expand...
Click to collapse
Try using Odin to flash the high on android cwm recovery. Once I did that I could restore a backup and boot to android.

Thank you! but I've been on stock recovery so I never flashed cwm or made a cwm backup. How can I restore to a backup after I flash the cwm recovery?
Nefariouss said:
Try using Odin to flash the high on android cwm recovery. Once I did that I could restore a backup and boot to android.
Click to expand...
Click to collapse

if you've never flash CWM, that means you never backed up via CWM, which means you can't restore to a back up. You have to use ODIN and flash a stock firmware on your note to recover it

Yes I'm trying to find a stock firmware for N8013 (UEALGB) but no luck. There is only "root injected" stock firmware, which is causing the problem right now...
Has anyone resolved this problem?
khanh1289 said:
if you've never flash CWM, that means you never backed up via CWM, which means you can't restore to a back up. You have to use ODIN and flash a stock firmware on your note to recover it
Click to expand...
Click to collapse

ytdong said:
Yes I'm trying to find a stock firmware for N8013 (UEALGB) but no luck. There is only "root injected" stock firmware, which is causing the problem right now...
Has anyone resolved this problem?
Click to expand...
Click to collapse
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.

This worked for me as well. Thanks a lot, Vincent9756!:good:
Vincent9756 said:
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.
Click to expand...
Click to collapse

Vincent9756 said:
I have a N8013 and was running the stock, root injected firmware (UEALGB). Today I got the update notification. I tried to install and it kept looping. This is what I did:
1. Flashed the stock firmware with ODIN. You'll find the stock firmware here:
http://forum.xda-developers.com/showthread.php?t=1847706
2. When my tab rebooted, I got another update notification. I installed it and it worked. I'm now running UEALI3.
I didn't lose any data. I just lost root.
Click to expand...
Click to collapse
Worked for me. Thanks!

rrhutch said:
Worked for me. Thanks!
Click to expand...
Click to collapse
What if i didn't do Root Injected, but the Second Method of Flashing the Root.zip with CWM? which recovery do i download and flash in odin?
would that work?

Kikoshi said:
What if i didn't do Root Injected, but the Second Method of Flashing the Root.zip with CWM? which recovery do i download and flash in odin?
would that work?
Click to expand...
Click to collapse
Flash the recovery version for your firmware. If you have stock, flash the GB recovery. If you have LH2, flash that.
If you want to save root, use OTA RootKeeper before doing anything.

Z a p i x said:
Flash the recovery version for your firmware. If you have stock, flash the GB recovery. If you have LH2, flash that.
If you want to save root, use OTA RootKeeper before doing anything.
Click to expand...
Click to collapse
Im sorry but what do you mean GB Aaah that was the primary stock recovery before i updated to LH2 lol, now i get it.?The one that i have is the CWM HighonAndroid which was used for the Method 2 to obtain root, so then i jus tdownoad the stock LH2 Recovery, and use OTA rootkeeper before Odin LH2 Stock Recovery right? Will there also be a stock kernel and recovery for UEALI3 ? was thinking of possibly using the Triangle Away after this, possibly might be needed. Though maybe not.
Just want to make sure that everything is normal after this lol
ok... giving it a shot now, and using the OTA RootKeeper, lets see if this works
Everything Got updated !!! OTA seems to have worked which was awesome.
Testing everything to make sure that Root is fully funtional .
Used RootChecker, and things seems fully working!
Thank you loads for the help!

Kikoshi said:
Im sorry but what do you mean GB Aaah that was the primary stock recovery before i updated to LH2 lol, now i get it.?The one that i have is the CWM HighonAndroid which was used for the Method 2 to obtain root, so then i jus tdownoad the stock LH2 Recovery, and use OTA rootkeeper before Odin LH2 Stock Recovery right? Will there also be a stock kernel and recovery for UEALI3 ? was thinking of possibly using the Triangle Away after this, possibly might be needed. Though maybe not.
Just want to make sure that everything is normal after this lol
ok... giving it a shot now, and using the OTA RootKeeper, lets see if this works
Everything Got updated !!! OTA seems to have worked which was awesome.
Testing everything to make sure that Root is fully funtional .
Used RootChecker, and things seems fully working!
Thank you loads for the help!
Click to expand...
Click to collapse
Yeah, there will most certainly be kernel and recovery uploads.
the only issue you might run into is CWM not sticking. If it doesn't reflash CWM in ODIN with reboot unchecked. Then after you flash it, boot into CWM. When you select reboot, it should offer to prevent stock recovery from replacing it.
and you're welcome, glad to help

Guys u might think this is a dumb question but how do i flash stock recovery with odin like were do insert the file i know how tp put in dl mode and get my comp to see my tab in odin and i did flash the prerooted injected stock uealgb recovery to get root i just dont know were to put the files in odin some help would be greatly appreciated, cause i need to flash this first before i do the ota update correct ? If not i will bootloop ? So rootkeeper alows me to keep root acess after ota? Thanks guys
Sent from my GT-N8013 using xda app-developers app / jelly powered samsung infuse 4g

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.

Jelly Bean OTA

FOTA ripped for your enjoyment.
https://mega.co.nz/#!xoZigSqS!YHUa5Umv-8qjyFV1dtHs4lDQXMIn1q7plTz3zWeYSwY
That's completely unmodified. (I tried just installing it in CWM. Think I probably bricked doing something silly...)

I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?

gee one said:
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
Click to expand...
Click to collapse
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...

bigleague4040 said:
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
Click to expand...
Click to collapse
I have a modified boot.img- perhaps that blocks the ota?

My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?

I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors

gee one said:
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
Click to expand...
Click to collapse
OMG, I would like to do it with no hassle.
I just want something to work ... grrr.

Option 2 would probably be the most straightforward. Essentially, you are unrooting. I just remembered, Samsung has Kies which might restore it to stock. You can download it from their website.
sent while running with scissors

mazak23 said:
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
Click to expand...
Click to collapse
the update in this thread is only about JB 4.1.2 that is officially the latest and the last one for our mobile. your message box is normal, there is no need for the usage of the OTA anymore since then. if u want to update to JB 4.3 follow this unofficial image:
http://forum.xda-developers.com/showthread.php?t=2463661

Holy thread resurrection Batman!!!
Oh boy. Here we go. Having troubles here.
I am trying to re-flash my phone to stock so I can return it under the protection plan. I firmly believe my radio might be on the fritz.
Anyway, I used the directions here:
http://theunlockr.com/2013/04/25/how-to-unroot-the-samsung-galaxy-s-relay-4g-sgh-t699/
Now it all completed successfully, and the phone is chilling at the SAMSUNG screen trying to boot. Not sure what to do at this point. Its been sitting there for a good 5 minutes.
Please help!!
UPDATE: Went into stock recovery, cleared Cache and Data, then rebooted it again, and it booted!

Which JelyBean Version...!!!
After installing this update what will be my os (JB 4.X.X) version???

saurabhsaurabhrai said:
After installing this update what will be my os (JB 4.X.X) version???
Click to expand...
Click to collapse
it is just from stock, will be updated to JB 4.1.2