Hey, So i was trying to root my motorola droid maybe 2 weeks ago but it didnt work, and i didnt really care enough to try again (i have a mac and it was a pain to find a windows computer). I thought everything would be fine, but for some reason when i tried to update my phone to 2.2 (i found the update.zip on androidcentral) it said that it failed, and for some reason when i restart holding down the X, it says:
Android system recover <2e>
Patched by SirPsychoS (0.00.3b)
is there a way to change that back to the regular one? or am i screwed hahaha
Also when i hit "allow update.zip installation' and then 'install /sdcard/update.zip (deprecated) i get this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Installation aborded.
What do you guys think i should do? finish rooting it (can i have directions please ) or is there a way to get it back to how i got it? I think i alreayd tried to factory reset it
Thanks
Assuming you can boot into recovery, find your original ROM on the net, if available and re-flash with that to be un-rooted and back at square-one.
Could be the ROM you flashing now is not for your network provider, or you haven't successfully rooted.
I'm HTC myself so would use a goldcard (google it) to use a generic rom with my vodafone phone. Don't know if goldcards work with motorola.
hmm i cant seem to find it, could i just stick with what i have now and receive the 2.2 froyo update when it comes through OTA?
Depends how you rooted (or tried to root) if you flashed a rooted Rom in the root process it probably won't be updating from the official Motorola servers.
Sent from my HTC Desire using XDA App
I don't think i even flashed a rom, i tried that screenshot program (i cant remember the name of it, but you need root to use it) and it wouldnt work so i dont actually have root. I think that i tried to flash it with a rooted 2.1 rom but it failed. what do you guys suggest i do?
ok so i figured out that it was because my mac unzipped the file, but when i try to install it i get this:
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:boot:25047
04:0b5ee101da4118aa026a32848f609fa4b05403e:2875
392:d104d2ev84a2d06600e786c0fb8174bfacb4079db6")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Ive tried like 4 different downloads and its just not working :S
Hello,
Today we have a new ota update for HTC One S, but I can't installed it, installation is aborted.
I have downloaded it, then I want to install it, my phone turned off then it turn on with recovery, but I have the message:
Installation aborted.
I have tried to do that manually with recovery, but I have the same message.
Do you have any idea?
Firstly, Is the OTA configured to be flashed via CWM ??
Secondly, Flashing official signed packages require the bootloader to be locked (so ive heard)
Thirdly, Check the MD5 sums match,, Its possible it was a bad download.. This is the most common cause of ''installation aborted'' messages
Here the same
I start the OTA Update for my HTC one S
this error comes on CWM Recovery
ClockworkMod Recovery v5.8.3.1
"Finding update package...
E: Can´t mount INTERNAL SDCARD...
Installation aborted. "
thanks for help
HTC One S only Root and recovery. s-on stock rom
My guess is it's a recovery problem, as the package won't install via manual either.
But I won't dive deeper into the matter now. Just backing up my phone and cleaning it out to be ready for shipping tomorrow. It's going back to retailer because of the MAO chipping issue.
After flashing the Stock Recovery with this wonderful One klick tool the Update is working just fine...
http://forum.xda-developers.com/showthread.php?t=1604677&page=6
I had my Bootloader unlocked via HTCdev... Seems like an unlocked Bootloader has got nothing to do with this issue!
To keep your Phone rooted after the update, use OTA Rootkeeper from the Playstore!
Where did you get the stock recovery? I'm having trouble finding it.. I want to install the OTA update!
eahiv said:
Where did you get the stock recovery? I'm having trouble finding it.. I want to install the OTA update!
Click to expand...
Click to collapse
I follow one of torxx's thread and it took me here, stock recovery available.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
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.
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 ?
Hi everybody, i am currently running OxygenOS 5.1.0 and i am trying to update to latest version.
1. I tried with local update inside settings but nothing the message is: unable to install system update
2. I tried unlocking bootloader, installing TWRP and trying to install update via TWRP but i get stuck in Error7, seems like the package is not recognized for my phone.
I rad a lot about removing assert rows inside update scripts in the .zip package. Unfortunately in my package there is no update-script and i don't know any possible way to force my installation. Do you have any suggestion?
I'd recommend to go back to full stock (lock bootloader) and then try to do all the OTA updates. It's not working for you this way?