If you are running a stock rom, rooted, unlocked/locked bootloader with stock recovery, you will lose the ability to unlock the bootloader if you accept the update.
If you haven't received the update you can do several things to prevent the update from flashing successfully:
1) Load an alternative recovery like TWRP on your device. Having an alternate recovery on your device practically guarantees any stock OTA software will fail to install.
2) Disable the following system file (SDM 1.0) via Titanium Backup's Freeze option, or use Root Explorer to rename the file name in /System/App to SDM 1.0.bak
FYI, received the OTA update last night and woke up to TWRP recovery's main screen. I was nervous about rebooting the device because I hadn't disabled the SDM 1.0 file prior to the forced update, so I was going to restore my backup from 8/30/12 to be safe.
However, I took the chance that having TWRP as an alternate recovery would cause the backup to fail. So I rebooted the device and it booted up fine, and immediately displayed a pop-up window that the update failed. Then I immediately froze the SDM 1.0 file with Titanium Backup.
I haven't even got a notification for it, I'm stock unrooted... Used to root all my Motorola phones... Don't want to lose my warranty yet, by rooting and unlocking but I wanted to retain the option to do so in the future.. I checked for updates just now and it's there but it hasn't tried to download/or install itself yet...Is there anything I can do to keep my stock phone from automatically taking it...
If you are running a stock rom, rooted, unlocked/locked bootloader with stock recovery, you will lose the ability to unlock the bootloader if you accept the update.
If you haven't received the update you can do several things to prevent the update from flashing successfully:
1) Load an alternative recovery like TWRP on your device. Having an alternate recovery on your device practically guarantees any stock OTA software will fail to install.
2) Disable the following system file (SDM 1.0) via Titanium Backup's Freeze option, or use Root Explorer to rename the file name in /System/App to SDM 1.0.bak
How do you know it'll block your ability to unlock the bootloader? I haven't seen this anywhere else. Maybe I'm just not looking correctly :-p.
Device(s): Viewsonic G-Tablet, Droid X,
LG Voyager (retired), Galaxy S III, Nexus 7
Carrier: Not Provided
Thanks: 10
Thanked 11 Times in 7 Posts
Busy weekend, Received the update prompt early Saturday as I was preparing to leave for a camping weekend. Some quick research proved I needed more time. I delayed the update and of course forgot about delaying it again. It failed multiple times and gave up. I'm still at I535VRLF2 and have root. I check for software update and it says I'm up to date. My guess is I froze a few bloatware apps with Titanium Backup and it caused the permanent failure. Now what am I missing from this small update and how will I update to Jelly Bean? I guess I'll wait and eventually flash a stock JB ROM when available. No hurry for me, this is all just a FYI. Good luck out there.
How do you know it'll block your ability to unlock the bootloader? I haven't seen this anywhere else. Maybe I'm just not looking correctly :-p.
I think it was mentioned on xda. Do you really think Verizon would release an update, a really sneaky one at that, and not plug the exploit used to unlock the bootloader?
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 244
Thanked 178 Times in 155 Posts
Running stock rooted ROM. Got the notification moments ago. The phone rebooted, and because I have CWM Touch Recovery installed the update stalled because it said the file was unsigned, and Recovery asked whether I wanted to go ahead and flash the unsigned file. I tapped No, and then the reboot button, and once rebooted the phone reported the update failed. I am renaming the SDM files (mine don't say SDM 1.0 either) in Root Explorer to prevent further attempts to update until the devs look at this update and offer it safely rooted.
I was updated and also lost root. I was able to run Adam's Casual Root applet (Verizon-GS3-CASUAL-Revision131a.jar) and all is well again. I'm rooted with the update.
Device(s): VZW Galaxy S3, Transformer Prime, Droid X (ret)
Carrier: Not Provided
Thanks: 17
Thanked 400 Times in 322 Posts
Quote:
Originally Posted by Shogun_X
I was updated and also lost root. I was able to run Adam's Casual Root applet (Verizon-GS3-CASUAL-Revision131a.jar) and all is well again. I'm rooted with the update.
Bought the phone on Saturday, came with this update already installed. Phone is rooted, and bootloader is unlocked just fine, currently running Jelly Bean atm.
Anyone know where this update is stored when it's downloaded?
The update was downloaded onto my phone, but I've denied the installation. Where can I navigate to (using root explorer) to delete the OTA update? I'd like to delete it off my phone altogether.
Wow, is this true that the update will break the encrypted bootloader workaround? I haven't had the chance to unlock the bootloader yet and my 6 year old niece must have accepted the update or something because it's on my phone. What can I do at this point??
If you are running a stock rom, rooted, unlocked/locked bootloader with stock recovery, you will lose the ability to unlock the bootloader if you accept the update.
I was stock, unrooted (as such, stock recovery) and the update went off when I wasn't paying attention to it. I've since flashed AOKP and different kernels without problem. The bootloader is fine post-update.
If your baseband is G7 and giving you difficulty, you can just flash back to G2 in Odin
Last edited by ascottsman333; September 19th, 2012 at 04:32 PM.
I was stock, unrooted (as such, stock recovery) and the update went off when I wasn't paying attention to it. I've since flashed AOKP and different kernels without problem. The bootloader is fine post-update.
If your baseband is G7 and giving you difficulty, you can just flash back to G2 in Odin
I was stock rooted and unlocked. Flashed stock recovery then locked, took the update then used debugfs root method to root again and then was able to unlock again. No problems.
The Following User Says Thank You to Rick2179 For This Useful Post:
Device(s): Galaxy S iii, Incredible1, Incredible2, Galaxy Tab 7inch, Touchpad(Androidified), Moto Xoom
Carrier: Not Provided
Thanks: 74
Thanked 59 Times in 39 Posts
I have just been deferring the update. I have still not rooted because I have not had the time and I was pleasantly surprised by how content I am with this phone as is. That being said, I do not trust Verizon at all--so I never install updates without further research.
Is there anyone out there who can provide clear instructions on fixing the root. after getting the update from verizon, which took my root away. Its says in QTA that I have rooted device but when I try to use superuser it wont let me at all. it keeps saying that everything has been "Denied Root"
Please can someone help me out with this, I have tried everything that everyone has said to do in this thread. but nothing worked for me.
Update: Sept 23 2012, 1pm
I have found my own answer, and if anyone else has this problem, I hope that this will help you,
All I did to Fix my Problem was to
Uninstall all of my superuser apps and my busybox apps and then just re install them back in. once I did that the phone gave me back full root again.
I hope this will help someone else.
Last edited by Marknderm; September 23rd, 2012 at 12:01 PM.
Device(s): Samsung Galaxy S3, stock JellyBean rom, rooted and unlocked!
Carrier: Not Provided
Thanks: 10
Thanked 36 Times in 32 Posts
Quote:
Originally Posted by Taylored
I have just been deferring the update. I have still not rooted because I have not had the time and I was pleasantly surprised by how content I am with this phone as is. That being said, I do not trust Verizon at all--so I never install updates without further research.
I am actually very satisfied with this phone stock after coming from Moto phones where root was required in order to make them workable. However, one thing I learned with the OG Droid is that after support for the phone stops, if you are rooted and unlocked, support continues from the devs and assure you that you continue getting all the awesome updates for as long as they can make it happen! For that reason alone, I rooted and unlocked the bootloader while I still can. I'll just wait for the rooted stock image of JB to appear from the dev community and install that when its available. Until then, I, like you, am very content.
I was satisfied, but wanted to check out google now. I was waiting for the right time to root, and this update kind of forced my hand. Better to root / unlock before they force something on me!
Device(s): Samsung Galaxy SIII,
ASUS Transformer TF101
Carrier: Verizon
Thanks: 127
Thanked 365 Times in 252 Posts
Quote:
Originally Posted by cp1
I was satisfied, but wanted to check out google now. I was waiting for the right time to root, and this update kind of forced my hand. Better to root / unlock before they force something on me!
You can root after the update. I did it yesterday, no problems following Section 2 instructions at this XDA thread.
__________________
Apps on my SIII
OK, I admit it, I'm a Twit Dropbox! 2Gb free cloud storage
SIII - CleanROM 6 R2 / TF101 - Stock
I'm still not updated, and I'm not rooted and not unlocked yet... Really haven't had the need to thanks to Foxfi and a good ui stock.. I used to root for tether and screen shots mainly, this phone is great can do both without root, keeping my warranty is nice.
I was able to re-root my GS3 using the method posted by AdamOutler after the IMM76D.I535VRALG7 installed automatically on my phone. I had originally rooted on the previous build and was eventually going to flash a custom rom but got lazy and the update auto-installed. I lost root, but as I said, I was able to re-root using the same method here: xda-developers - View Single Post - [R&D] Unlock Bootloaders and also was able to unlock the bootloader. All is good!
The Following User Says Thank You to deejayfai For This Useful Post:
I rooted my phone and had clockwork installed. I didn't freeze any apps, but when I tried to do the update it failed on its own. Any idea what's causing this and how can I get my phone to be like it was stock?
I rooted the phone and had clockwork installed. I didn't freeze any apps, but when I tried to do the update it failed on its own. Any idea what's causing this and how can I get my phone to be like it was stock?
Thanks
If you want the update, you must reinstall/flash the OEM recovery back. The alternate recovery, CWM, is what is causing the update to fail.
If you want the update, you must reinstall/flash the OEM recovery back. The alternate recovery, CWM, is what is causing the update to fail.
I figured it was cwm that was causing it to fail, but I recently got a "like new" replacement s3 from verizon for my s3 that I experimented on. No matter how I tried to mess up the phone, it still would pull and install the update. I even tried to replicate what I did to my original phone. Currently, I used ODIN and loaded the original software called: "HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low _ship.tar.md5". After doing so, when I try to do the update it says there is no update. I would prefer to keep my original phone instead of the replacement because the replacement has other hardware issues (screen has a yellowish tint at angles, home button seems loose). Please let me know if I can fix this and receive the normal Verizon updates.
Thanks
UPDATE - Somehow after talking with tech support, my phone mysteriously does the update the following day. Prior to this it would never pull the update.
Last edited by turbon50; September 28th, 2012 at 01:22 PM.
I was unlocked and rooted. I've flashed a few builds of CM10, but kept going back to stock via clockwork mod's backups. My stock image has never received an OTA update (clockwork always made it fail), and is the same exact version that came on the phone (never factory reset).
For various reasons I decided to take this OTA. Here's how:
1. Did a titanium backup and clockwork backup (just in case something went wrong, it didn't)
2. Re-enabled all disabled apps (disabled via ICS, not titanium)
2. Re-locked the bootloader using ez-unlock
3. Backed up root using voodoo rootkeeper
4. Using ODIN 3.04 and the Verizon S3 stock recovery image I flashed the original recovery.
(see How to Re-install Stock Recovery and Update OTA on Galaxy S3! | GalaxyS3Root.com) Note I used the newer 3.04 vs what they linked to.
5. Rebooted. Accepted the update. It installed fine.
6. Used voodoo to restore root.
I have not tried to unlock the bootloader. I don't see the point until I want to flash another ROM.
Edit: fixed typos and misspellings
Last edited by _Aardvark; September 28th, 2012 at 11:13 AM.
Device(s): Samsung Galaxy S III , Acer Iconia A500 Tablet, Wife's Kindle Fire, Moto Droid X - Retired
Carrier: Verizon Wireless
Thanks: 244
Thanked 178 Times in 155 Posts
Quote:
Originally Posted by _Aardvark
Just some info that some may find useful.
I was unlocked and rooted. I've flashed a few builds of CM10, but kept going back to stock via clockwork mod's backups. My stock image has never relieved an OTA update (clockwork always made it fail), and is the same exact version that came on the phone (never factory reset).
For various reasons I decided to take this OTA. Here's how:
1. Did a titaniumn backup and clockwork backup (just in case something went wrong, it didn't)
2. Re-enabled all disabled apps (disabled via ICS, not titaniumn)
2. Re-locked the bootloader using ez-unlock
3. Backed up root using voodoo rootkeeper
4. Using ODIN 3.04 and the Verizon S3 stock recovery image I flashed the original recovery.
(see How to Re-install Stock Recovery and Update OTA on Galaxy S3! | GalaxyS3Root.com) Note I used the newer 3.04 vs what they linked to.
5. Rebooted. Accepted the update. It installed fine.
6. Used voodoo to restore root.
I have not tried to unlock the bootloader. I don't see the point until I want to flash another ROM.
Thanks, _Aardvark, I am sure this information will be very useful when someone wants to update, or restore their S3 to its original condition. To round out the information for me, what method did you use to unlock the bootloader, originally?
Root, if it matters, was done using the non-odin way. "debugfs-based Root for Galaxy S III" by "Noxious Ninja".
Thanks. All I have done so far on my S3 is flash the rooted version of the stock ROM (root66, I believe the procedure was called), and then modified the files discussed above, to block updates from VZW. But your info may come in handy down the road, especially if I were ever to decide to flash custom ROM.
Still no auto update for me . The only reason maybe is I have every possible system app that I can without root, disabled.
is there a list of these apps out there somewhere? i have had the phone for 4 days and i see a ton of bloatware stuff that i will never use, but i don't necessarily want to root yet while i get my bearings with touchwiz.
i came over from a rooted HTC Evo 4G and i do love tinkering with Android, but i want to ease my way into it (plus i wouldn't mind waiting for a JB update in the next month or two).
Device(s): VZW Galaxy S3, Transformer Prime, Droid X (ret)
Carrier: Not Provided
Thanks: 17
Thanked 400 Times in 322 Posts
Quote:
Originally Posted by boofer
is there a list of these apps out there somewhere? i have had the phone for 4 days and i see a ton of bloatware stuff that i will never use, but i don't necessarily want to root yet while i get my bearings with touchwiz.
i came over from a rooted HTC Evo 4G and i do love tinkering with Android, but i want to ease my way into it (plus i wouldn't mind waiting for a JB update in the next month or two).
You only need to be careful if you are freezing/removing apps with root. Without root, it's not going to let you remove anything that will break it.
3Likes
Verizon forced update I535VRLG7
. The only reason maybe is I have every possible system app that I can without root, disabled.
