http://goo.gl/4G5Fs
Verizon Samsung Galaxy S3 modified OTA updates
Released: October 30, 2012
Last update: March 6, 2013
Download:
v1
MD5 (unsigned-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALF2-ota-goo.gl-4G5Fs-v1.zip) = 476f0b25b4244743dd7b8559db2f91e4
MD5 (unsigned-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALG1-ota-goo.gl-4G5Fs-v1.zip) = e17739a0614c5fd69ef5d176546851ae
MD5 (unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip) = 28b22ba5189ab46e39bb9841b648e128
MD5 (unsigned-d2vzw-JRO03L.I535VRBLK3-from-IMM76D.I535VRALHE-ota-goo.gl-4G5Fs-v1.zip) = a41dfa86a8201f3641ac52ffd5f157e5
MD5 (SGS3-TW-US_variants-lib_nfc-fix-jellybean_4.1-goo.gl-4G5Fs-v1.zip) = 2a65ab4545538b2905cea6b879587683
MD5 (unsigned-d2vzw-JZO54K.I535VRBMB1-from-JRO03L.I535VRBLK3-ota-goo.gl-4G5Fs-v1.zip) = 367c422abdf00db4311d0759267144b8
Original OTA updates (just mirroring them here, don't apply these):
MD5 (signed-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALF2-ota.zip) = 6755655c06048808e6f91b3589027f32
MD5 (signed-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALG1-ota.zip) = b4dc0238718c8f4320e19c31ba37e906
MD5 (signed-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota.zip) = 3f1cb228b624ab93af8bf3ae9dd4974d
MD5 (signed-d2vzw-JRO03L.I535VRBLK3-from-IMM76D.I535VRALHE-ota.zip) = 82f73037919666c72fc4d94afa1dc82f
MD5 (signed-d2vzw-JZO54K.I535VRBMB1-from-JRO03L.I535VRBLK3-ota.zip) = 3ee54dedd48f8f2e47717fbf3e9d7ec0
If you are upgrading to Jelly Bean and have Google Wallet installed, you should upgrade Google Wallet to the latest modified version first before applying the modified OTA. Immediately after applying the modified VRBLK3 OTA, apply the SGS3 Jelly Bean NFC libraries for Google Wallet. The US variant libraries are mirrored here, see the original thread for other variants.
These updates are for Verizon Samsung Galaxy S3’s that have been rooted, custom recovery flashed, bootloader unlocked, and have Google Wallet and the associated NFC libraries installed. If you did all those things to your S3 and want to apply the stock OTA updates, this is for you.
Restore your stock build.prop if you have modified it to activate Google Wallet. Make sure you are running the latest version of your custom recovery software and apply the modified update for your software version. The recommended recovery to use is ClockworkMod Recovery 6.0.1.2 (or greater) which can be installed using ROM Manager.
To create the modified updates, I took a stock Verizon SGS3 running IMM76D.I535VRALF2, rooted it, flashed a custom recovery, unlocked the bootloader and installed Google Wallet using known methods. Then, I downloaded each OTA update in turn and unpacked it, edited the updater-script to remove references to aboot, recovery and the stock NFC libraries and added a line to correct the permissions for the superuser binary, then repacked the update and applied it. This successfully updated the device without affecting the aboot or recovery partitions or failing due to NFC library checks and maintained root access.
Only the updater-scripts have been modified. The original OTA updates are provided for comparison.
Can you fix your link for (unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip)
i got a status 7 error when trying to install.... failed getprop ("ro.product.device") == "d2vzw" II get prop ("ro.build.product") == "d2vzw"
guyd said:
Can you fix your link for (unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip)
Click to expand...
Click to collapse
Got it, thanks.
Seanzle said:
i got a status 7 error when trying to install.... failed getprop ("ro.product.device") == "d2vzw" II get prop ("ro.build.product") == "d2vzw"
Click to expand...
Click to collapse
This only works on Verizon SGS3 with stock ROM. Revert your build.prop back to stock if it is still modified from when you activated Google Wallet.
I dont have google wallet
Seanzle said:
I dont have google wallet
Click to expand...
Click to collapse
What update are you trying to apply? What are you currently running (ROM, recovery)? You may need to update your recovery. See the last FAQ question on this post:
Q: It's not working by flashing via recovery! I get something like this:
assert failed: getprop("ro.product.device") == "d2vzw" || getprop("ro.build.product") == "d2vzw"
E: error in /emmc/VRLHD.modem.zip
(status 7)
A: It's failing the assert. These check what device you have and older versions of clockworkmod didn't have the proper device in there. Update your recovery first. EZ Recovery can do this for you or you can grab something from here: http://goo.im/devs/invisiblek/i535/recoveries then try again
Click to expand...
Click to collapse
OTA still asking me to install update
I successfully installed the rooted unsigned-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALF2-ota-goo.gl-4G5Fs-v1.zip. However, my phone is still bugging me to install an "Important Update" I have been deferring it because I am worried that if I let it go, it will remove my root and prevent me from using Google Wallet.
Is it safe to allow the phone to install the update and I can re-apply root and Google wallet later?
If not, where did the update's files download to, so that I can delete them manually?
Thanks in advance
I have tried stock and CWD recovery on my GS3 and still getting failed update. Any ideas?
Besides being rooted for Google Wallet I haven't done anything else to the phone.
when using the stock root it comes up with "e:signature verification failed" on both files
ouray770 said:
I successfully installed the rooted unsigned-d2vzw-IMM76D.I535VRALG7-from-IMM76D.I535VRALF2-ota-goo.gl-4G5Fs-v1.zip. However, my phone is still bugging me to install an "Important Update" I have been deferring it because I am worried that if I let it go, it will remove my root and prevent me from using Google Wallet.
Is it safe to allow the phone to install the update and I can re-apply root and Google wallet later?
If not, where did the update's files download to, so that I can delete them manually?
Thanks in advance
Click to expand...
Click to collapse
It is safe to allow the install. The update won't do anything because the updater binary will check the signature on your NFC libraries and prevent it from happening. After the update fails, SDM (Samsung's updater app) will behave as if the update completed successfully. Recommend you freeze SDM using Titanium Backup after letting the update fail.
(edit) You won't need to reroot or reinstall Google Wallet. Just wanted to make that clear. Also, since you're talking about applying the VRALG7 update, SDM will prompt you to install the next OTA update VRALHE (which will also fail) so after applying the modified VRALG7 update you should install the modified VRALHE OTA update and then let SDM try to install the official VRALHE OTA update. Then SDM will act normal.
solidage said:
I have tried stock and CWD recovery on my GS3 and still getting failed update. Any ideas?
Besides being rooted for Google Wallet I haven't done anything else to the phone.
when using the stock root it comes up with "e:signature verification failed" on both files
Click to expand...
Click to collapse
What do you mean by both files? What is the current software version on your phone?
Any modifications to your phone from stock may cause the updates to fail. I have only disabled a few signature checks related to Google Wallet (NFC libraries) and nothing else. If there are *any* other files on your system partition that are not stock, that may cause the signature verification to fail.
If you can include any other logging info, that would be helpful.
(edit) You *must* use a custom recovery to flash the modified OTA. Try using the latest version ClockworkMod recovery, install it using EZ Recovery.
Happen to have the OTA from VRALF1?
control1110 said:
Happen to have the OTA from VRALF1?
Click to expand...
Click to collapse
Do you mean VRALG1? If I have some time tonight I can see about it.
NFC Service keeps stopping and it's locking my phone
cj64 said:
It is safe to allow the install. The update won't do anything because the updater binary will check the signature on your NFC libraries and prevent it from happening. After the update fails, SDM (Samsung's updater app) will behave as if the update completed successfully. Recommend you freeze SDM using Titanium Backup after letting the update fail.
(edit) You won't need to reroot or reinstall Google Wallet. Just wanted to make that clear. Also, since you're talking about applying the VRALG7 update, SDM will prompt you to install the next OTA update VRALHE (which will also fail) so after applying the modified VRALG7 update you should install the modified VRALHE OTA update and then let SDM try to install the official VRALHE OTA update. Then SDM will act normal.
Click to expand...
Click to collapse
THANKS!! After a tiresome update of clockworkmod recovery (touch-6.0.1.2) via terminal emulator, I was able to flash both of the modified update zip files and I will approve the OTA install at noon today. If anything breaks after that, I will reply again.
---------- Post added at 12:15 PM ---------- Previous post was at 11:57 AM ----------
---------- Post added at 12:24 PM ---------- Previous post was at 12:15 PM ----------
I spoke to soon. Now I continually get "Unfortunately the NFC service has stopped" and it will not go away!
cj64 said:
Do you mean VRALG1? If I have some time tonight I can see about it.
Click to expand...
Click to collapse
Yes, Thank you
cj64 said:
What do you mean by both files? What is the current software version on your phone?
Any modifications to your phone from stock may cause the updates to fail. I have only disabled a few signature checks related to Google Wallet (NFC libraries) and nothing else. If there are *any* other files on your system partition that are not stock, that may cause the signature verification to fail.
If you can include any other logging info, that would be helpful.
(edit) You *must* use a custom recovery to flash the modified OTA. Try using the latest version ClockworkMod recovery, install it using EZ Recovery.
Click to expand...
Click to collapse
Baseband Version
I535VRLF2
Kernel Version
3.0.8
Android Version
4.0.4
Build
IMM76D.I535VRLF2
The only thing I have done to this phone was rooted it, then edited the build.prop for google wallet, then reverted back to the old build.prop (Google wallet was disabled)
When I attempt to install via EZ-REcovery and CWM I get the following error
with the file ending zmh.zip
installing update...
assert failed: getprop("ro.product.device") =="d2vzw
getprop("ro build.product") =="d2vzw
E; Error in /sdcard/FILENAME.zip
Status 7
Installation aborted
with the file ending QXM.zip
Assert failed file_getpropr ("/system/build.prop" ."ro.build.fingerprint") == "Verizon/d2vzw/d2vzw 4.0.4/imm76D/i53VRALG7.user/release-keys"
Error in /sdcard/FILENAME.zip
Status 7
ouray770 said:
THANKS!! After a tiresome update of clockworkmod recovery (touch-6.0.1.2) via terminal emulator, I was able to flash both of the modified update zip files and I will approve the OTA install at noon today. If anything breaks after that, I will reply again.
---------- Post added at 12:15 PM ---------- Previous post was at 11:57 AM ----------
---------- Post added at 12:24 PM ---------- Previous post was at 12:15 PM ----------
I spoke to soon. Now I continually get "Unfortunately the NFC service has stopped" and it will not go away!
Click to expand...
Click to collapse
Recommend you reflash the latest modified Google Wallet. There may be some mixed NFC libraries on your device (some Verizon, some Sprint). Let us know if that solves it.
solidage said:
Baseband Version
I535VRLF2
Kernel Version
3.0.8
Android Version
4.0.4
Build
IMM76D.I535VRLF2
The only thing I have done to this phone was rooted it, then edited the build.prop for google wallet, then reverted back to the old build.prop (Google wallet was disabled)
When I attempt to install via EZ-REcovery and CWM I get the following error
with the file ending zmh.zip
installing update...
assert failed: getprop("ro.product.device") =="d2vzw
getprop("ro build.product") =="d2vzw
E; Error in /sdcard/FILENAME.zip
Status 7
Installation aborted
with the file ending QXM.zip
Assert failed file_getpropr ("/system/build.prop" ."ro.build.fingerprint") == "Verizon/d2vzw/d2vzw 4.0.4/imm76D/i53VRALG7.user/release-keys"
Error in /sdcard/FILENAME.zip
Status 7
Click to expand...
Click to collapse
You cannot apply the 2nd update until you have successfully applied the 1st update. That is why the file ending QXM.zip, which I assume is unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip, fails. You aren't running VRALG7, yet. You are still on VRALF2.
Please try installing ROM Manager from the Google Play store and flashing the latest ClockworkMod Recovery (6.0.1.2) from there. Use that to apply the updates. I tested applying the modified OTA updates using that version of ClockworkMod Recovery.
cj64 said:
You cannot apply the 2nd update until you have successfully applied the 1st update. That is why the file ending QXM.zip, which I assume is unsigned-d2vzw-IMM76D.I535VRALHE-from-IMM76D.I535VRALG7-ota-goo.gl-4G5Fs-v1.zip, fails. You aren't running VRALG7, yet. You are still on VRALF2.
Please try installing ROM Manager from the Google Play store and flashing the latest ClockworkMod Recovery (6.0.1.2) from there. Use that to apply the updates. I tested applying the modified OTA updates using that version of ClockworkMod Recovery.
Click to expand...
Click to collapse
just purchased and installed ROM Manager (required a $2 purchase to flash to the 6.0.1.2 recovery) will report back.
as a side note today I noticed my email application is totally missing (the stock one) The only thing I've done in the last 2 days is attempt to install this update. Any ideas how I can get that .apk back?
---------- Post added at 08:19 PM ---------- Previous post was at 07:39 PM ----------
No dice
updated to the latest CWM recovery
select the 1st zip file, and tried installing it (via Rom manager GUI and through recovery)
get the following
assert failed: apply_patch_check9"/system/SW_Configuration.xml", "2b7f (really really long string of numbers and letters), "a7f5d (really really long string again) Error in /sdcard/Download/FILENAME ending in 1ZHM.zip
Status 7
Installation aborted
hu? upon rebooting, I get the message Android is upgrading and it still is not updated.
solidage said:
just purchased and installed ROM Manager (required a $2 purchase to flash to the 6.0.1.2 recovery) will report back.
as a side note today I noticed my email application is totally missing (the stock one) The only thing I've done in the last 2 days is attempt to install this update. Any ideas how I can get that .apk back?
Click to expand...
Click to collapse
Not sure what would cause that app to disappear. Check your PMs. Didn't know it cost $2 just to flash the recovery, sorry.
i would like to install the latest OTA update for 4.4.2 but it keeps failing.
i flashed stock recovery and i have stock kernel.
when i apply the update it just states that the update was unsuccessful.
any idea on how to solve this? i have tesco moto g on which i flashed stock UK firmware. it is only rooted. i do not think that i have deleted system apps and i tryed disabling xposed modules.
could someone make a flashable zip if it is possile?
i would really appreciate it :victory:
I use the latest TWRP as my recovery and it updates the OTA files fine, so I would suggest trying that.
Atomix86 said:
I use the latest TWRP as my recovery and it updates the OTA files fine, so I would suggest trying that.
Click to expand...
Click to collapse
i installed TWRP and disabled all xposed modules. the update went fine. the only thing is when it booted i got: an unexpected error has occured. please try again later.
should i worry about it? system version is now 176.44.1.
ManBearrrPig said:
i installed TWRP and disabled all xposed modules. the update went fine. the only thing is when it booted i got: an unexpected error has occured. please try again later.
should i worry about it? system version is now 176.44.1.
Click to expand...
Click to collapse
I didn't get that error so I can't answer that I'm afraid, sorry.
Sent from my Google Nexus G -
So, I was trying to Install CM13 on OnePlus One without Root or unlocking the bootloader(using Stock CM Recovery).
When I tried to update it shows the following on the cyanogen recovery screen
"Install failed.
Finding update...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted."
Current operating system.
12.1.1-YOG7DAS2K1
Trying to install:
Download: cm-13.0-20160310-NIGHTLY-bacon.zip (328.14 MB)
sha1: f08287b6884e6e465ec46eaaa1291488678dd2e9
From: https://download.cyanogenmod.org/?device=bacon
Solution? Please advise. Thanks
sowad9 said:
So, I was trying to Install CM13 on OnePlus One without Root or unlocking the bootloader(using Stock CM Recovery).
When I tried to update it shows the following on the cyanogen recovery screen
"Install failed.
Finding update...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted."
Current operating system.
12.1.1-YOG7DAS2K1
Trying to install:
Download: cm-13.0-20160310-NIGHTLY-bacon.zip (328.14 MB)
sha1: f08287b6884e6e465ec46eaaa1291488678dd2e9
From: https://download.cyanogenmod.org/?device=bacon
Solution? Please advise. Thanks
Click to expand...
Click to collapse
Seriously what made you think you can flash custom software without unlocking your bootloader? Either stick to stock OS or if you wanna enjoy CM13 you have to unlock and install a custom recovery
Sent from my A0001 using Tapatalk
Renosh said:
Seriously what made you think you can flash custom software without unlocking your bootloader? Either stick to stock OS or if you wanna enjoy CM13 you have to unlock and install a custom recovery
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
You sound like a bit of a ****
He is right though.
The way op describes it, it sounds as if he actually knows that the bootloader
should be unlocked. But at the same time he is amazed that it does not work.
Then this "solution?"... Seriously?
There are guides on xda for unlocking and flashing for a reason.
Pretty dumb and useless thread if you ask me.
update verification failed while trying OTA updates. Pls give me a solution for it
If device is a Samsung one, look inside here:
How to solve "Verification Fail" in Samsung devices | The TechRim
While rooting and changing stock rom of android there may arise different problems ..... while rooting or changing Rom is "Verification Fail".
thetechrim.com
anirban197 said:
update verification failed while trying OTA updates. Pls give me a solution for it
Click to expand...
Click to collapse
The cause of this problem depends on whether your device was rooted or had a custom recovery installed before you tried applying the OTA update.
If you were rooted or had custom recovery installed, first, you have to remove root and/or any other system modifications that you made and you have to restore stock recovery instead of having custom recovery installed. Stock OTA updates require an unmodified system partition and they also require stock recovery because the OTA update process checks the system partition to verify whether it is stock or not and the OTA process has to boot into stock recovery in order to install the OTA update before it can boot into the new system.
If you were not rooted or had custom recovery installed then the update may have failed due to one of your partitions being corrupted.
Either way, the solution is to manually download the update to your PC and then use Odin to flash the update. After the update, you can root the device again and/or install TWRP again. But be warned, if the update comes with a locked bootloader that can not be unlocked then you will not be able to install TWRP and you may not be able to root the device if certain aspects of the software have been patched to prevent rooting exploits.