ICS Update Fails on Stock

I am stock and NOT rooted... I got the update to download and started the installation and after it went through the optimizing applications portion it started "updating media database" and has been stuck there for about an hour. Not sure if I should let it sit or pull the battery.

Edit: OK so I resisted the urge to pull the battery and just left it laying on my desk and came back after a couple of hours and it was all done and working fine.
 
Mine took 2 hours to finish, mostly due to updating 'media', so be sure to charger on! II do have several thousand fotos and songs, so no wonder . . .

Rp
 
i was unable to install the upgrade. Saw your post about going back to .902, then .905, then ICS. This also worked for me.
Thank you.
 
On 905 with root and update failed. Tried factory reset and still fails. My error but also lost my backup in the process. So, can someone provide links and required files to 902 so i can try that?
 
Remember how you could do a full restore using the full 905 flash file if you were on Gingerbread? ;)

That file is now available for 246.

I looked and cannot find it. Can you please link it?

Sent from my Galaxy Nexus using Android Central Forums
 
So, I looked in the /cache/ folder where the OTA is stored as "Blur_Version.5.9.905.XT875.Verizon.en.US.zip" and found a last_log file in the /cache/recovery/ folder. At the end of the log file there are these statements:
Verifying current system...
file "/system/bin/mount_ext3.sh" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": no such file or directory
failed to load cache file
script aborted: "assert failed: apply_patch_check("/system/bin/mount_ext3.sh", "1810bb2ccd607e2f6cfbeafa158bb3a89629d60b7","3a8382950bd4a6226349607d099afcbd93653d48")
E:Error in /cache/
Blur_Version.5.9.905.XT875.Verizon.en.US.zip
(Status 7)
Installation aborted.

From this I infer that a checksum is being applied to the mount_ext3.sh file and the installation is aborted if the checksum does not match. Coincidentally, that is the file that has a couple of chmod commands added to it to keep root permanent. I don't know if a factory reset will put that file back to its original state. I also don't know if it would be possible to restore root after doing so. I also don't know what other checks may fail if that one succeeds. However, it seems clear that VZW is, at a minimum, attempting to prevent rooted phones from taking the OTA to ICS by failing the installation on phones that have used the forever root method to maintain root through OTA updates.

I had the same issue with multiples fails. I reverted to the old mount_ext3.sh file and the update went through without an issues. Thanks oldguy1950
 
My phone was mostly stock, just rooted and annoying apps renamed. Woke up this morning, and saw it was ready to update. It failed. Then remembered about the apps, renamed them back to stock. Now my phone says there is no update. :(
 
Would you be so kind to provide a copy of your old mount_ext3.sh so I can get my OTA update to work. I am getting the same error. Thanks.