• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Verizon] Verizon forced update I535VRLG7

xliderider

Android Expert
Jan 28, 2010
1,232
192
Where Diamond Head Stay
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.
 
Upvote 0
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...
 
Upvote 0
This is where I rejected the update
, I hope this stops it
 

Attachments

  • uploadfromtaptalk1347754409990.jpg
    uploadfromtaptalk1347754409990.jpg
    82.2 KB · Views: 232
Upvote 0
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.
 
Upvote 0
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.

SH
 
Upvote 0
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? ;)
 
Upvote 0
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.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones