[MOD] OTA updates - keep root, custom recovery, unlocked bootloader and Google Wallet - Verizon Samsung Galaxy S III

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.

Related

[Q] can someone make a flashable zip for latest OTA

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 -

[Q] Unable to install OTA updates in unrooted Shield tablet with original recovery

So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Saw the probable solution on another post.
mdecaminop said:
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Click to expand...
Click to collapse
In these forums somewhere I read that the unroot was done using Super su's full unroot option. However it apparently left behind a few files that caused the OTA to fail. So what he did was to uninstall Supersu, reinstall Supersu and update the binary. Then use full unroot function... Maybe it will work for you if you have unrooted using SUpersu...
Unrooting, locking the bootloader, and flashing the stock recovery doesn't allow you to take OTA's.
There is THIS thread, providing OTA files that can be flashed in TWRP or CWM. And are official files from Nvidia.
You have to flash these every time there's an OTA, or just flash a full stock image through fastboot, and never root or flash a recovery.
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
mycologik said:
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
Click to expand...
Click to collapse
Well it seems my second hand tablet has been rooted as well ... I've got the exact same problem that yours ...
Is there a way to go back as out of the box ?

Stagefright update (LMY48B->LMY48I)

I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
exhibit679 said:
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
Click to expand...
Click to collapse
You must return to stock before you attempt to install that zip. That means you cannot be rooted or have custom recovery in place
I've got a stock N5 I bought from Google on LMY48B and there's still no update for me.
Does anyone know what the roll-out timeline is for the LMY48I?
When should I conclude that I'm not going to get it OTA and resign myself to factory wipe and flashing the image?
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Nemesis02 said:
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Click to expand...
Click to collapse
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
moeREM said:
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
Click to expand...
Click to collapse
I have the same problem her as well with my nexus 5 it keeps saying error with little droid I've tried side loading manually but it didn't work also tried hard reset and wiping cache but nothing solved the problem so i just figured out the problem is the package it self
Same problem here
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
lpganesh said:
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This possibility makes me spend a lot of time, becouse i have lcd_density changed and all apps when i restore a backup are not in the main screen.
walt disney said:
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Click to expand...
Click to collapse
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Working - confirmed
cloney said:
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Click to expand...
Click to collapse
Thanks, confirmed that this method worked. Managed to update my rooted nexus 5 to LMY48I
Tried to install ota update after reverting to stock recovery using Simple Recovery Switcher app. However, also the error message, with little Android picture also appears. Please help
I assume this removed your root, though.
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Pastorelli's said:
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Click to expand...
Click to collapse
I'm with you, not going to try to flash these things, there are a few zip files out there dated a couple days ago, apparently the zips aren't tested prior to release since everyone is getting failure when flashing the zip file.
Is there really no method to apply OTA updates on rooted/modified devices (e.g. modify the update.zip itself to bypass whatever checks it performs)?
Same problem here- only had a custom recovery and root. brought back the stock recovery and did full unroot from SuperSu.
OTA update installtion stops with "Error".
Just flash the system image from the update.
Sent from my Nexus 5 using Tapatalk
Thanks, I ended up doing this http://forum.xda-developers.com/showpost.php?p=62288667&postcount=196
(flashing stock system, boot and recovery from my current version, letting OTA update install and re-rooting according to http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905)
I guess i could have flashed the new version just the same.

OTA CM13 update fails because of recovery

Hi,
I've got TWRP 3.0.2-0 recovery installed with CM12.1.1 YOG7DAS2K1 and am receiving the OTA update for CM13.0 ZNH0EAS2JK Incremental but the installation fails with an error message in recovery saying it's expecting "YOGDAS2K1" level but finds "YOG4PAS1N0". This happens whether I re-enable the CM Recovery update or not.
I found a thread here on XDA linking to all CM official updates. I flashed the recovery from "cm-12.1-YOG7DAS2K1-bacon-signed-fastboot" successfully and then tried the update again but it still failed. Again, happens whether I have CM Recovery update enabled or not.
Verifying current system...
system partition has unexpected contents
E : Failed to install @/cache/recovery/block.map
Click to expand...
Click to collapse
So now I flashed TWRP again. Does someone know what I should do to install the update ? Preferably without returning to stock first.
Solved
Feeling a bit stupid really...
Right under my post in the list was this post which deals with my problem exactly. I just updated my phone using that guide.

"Package verification failed" when trying to update Android 11

Hey all
So a while back I wanted to use a certain app on my Motorola One Hyper that required root privileges, so I rooted my phone using Magisk for it. I didn't need the app later so I unrooted my phone, but now when I try to update my phone to a newer version, I get an error message saying "Package verification failed. The update package being downloaded is not compatible with the current software version on the device".
I'm not sure if me rooting the device has anything to do with it or not, but I'm guessing it is since I never had this issue before the root. Any way to fix this? Thanks in advance!
BlobTea said:
Hey all
So a while back I wanted to use a certain app on my Motorola One Hyper that required root privileges, so I rooted my phone using Magisk for it. I didn't need the app later so I unrooted my phone, but now when I try to update my phone to a newer version, I get an error message saying "Package verification failed. The update package being downloaded is not compatible with the current software version on the device".
I'm not sure if me rooting the device has anything to do with it or not, but I'm guessing it is since I never had this issue before the root. Any way to fix this? Thanks in advance!
Click to expand...
Click to collapse
Yes, it probably is the root.
If you are trying to update the stock rom, it probably will not work. You may have to manually flash the stock rom again. Then, you may be able to upgrade to android 11. Otherwise you can just manually install android 11.
RVR said:
Yes, it probably is the root.
If you are trying to update the stock rom, it probably will not work. You may have to manually flash the stock rom again. Then, you may be able to upgrade to android 11. Otherwise you can just manually install android 11.
Click to expand...
Click to collapse
Ahh gotcha. Looks like I'm gonna have to flash the stock rom then. Thanks a lot for your help!
Does having a SafetyNet fix have something to do with it? Maybe unrelated, maybe not but when I check off the software update on the Magisk DenyList, exit and then come back, it becomes unchecked and I don't know why. Perhaps if the OTA updates werent detecting root, I could update to a security patch.
BlobTea said:
Ahh gotcha. Looks like I'm gonna have to flash the stock rom then. Thanks a lot for your help!
Click to expand...
Click to collapse
Stock updates usually can't be applied to rooted devices or devices with custom recovery, root has to be completely removed and stock recovery has to be reinstalled. If those aren't corrected before applying the update, it will fail because it checks the system partition for modifications and requires stock recovery to apply the update, whether it actually boots into recovery or not during the update process.

Categories

Resources