I searched, in every circumstance where someone was getting the following error:
E:Verification Failed
When trying to apply updates, they did not have root or there was some other issue that prevented them from su commands.
Here's the thing, I've got root, can su, can install updated roms.
Current running 1.6 / Cyanogen 4.2.15.1 / HTC-Dream / T-Mobile G1
Can apply system updates all day long. Cannot apply themes packed as update.zip, I get "E:Verification Failed" every time. Additionally CMUpdater will update ROMS, but when I add Theme Servers the theme will download and will not apply.
If this has been addressed in another thread, my apologies - I did search and every instance involved someone not having true roots on their device.
Related
The update in conventional zip format, with root options is here!
P
Works mint! I was running Modoco 1.3 ROM, heres the steps I performed:
recovery install: update-nexusone-ERE27-signed.zip
recovery install: update-nexusone-radio-32.24.00.22U_4.03.00.21_2-signed.zip
./fastboot-linux boot boot.ERE27.superboot.img
./fastboot-linux flash zimage zImage-2.6.29.6
./adb remount
./adb push bcm4329.ko /system/lib/modules/bcm4329.ko
Can I flash this manually WITHOUT being rooted?
I posted a thread on updating without root: http://forum.xda-developers.com/showthread.php?t=627533
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
I'm completely stock rom / not rooted and I just did this:
http://androidforums.com/nexus-one/41504-how-force-2-2-2010-ota-update.html#post316090
1. Get the update from Google: http://android.clients.google.com/updates/passion/signed-passion-ERE27-from-ERD79.a487b405.zip
2. Put the update on your SD card & rename it to update.zip
3. Boot in recovery mode (hold down trackball + power)
4. Go to bootloader -> recovery
5. Now there's a picture of a droid with a triangle
6. Press the power button + volume up
7. Apply sdcard:update.zip
8. Updating
9. Reboot system now
10. Enjoy the multitouch
Click to expand...
Click to collapse
Worked great.
Thanks Paul. That's what I first tried, and it failed. I posted the details here, but haven't heard anything back yet.
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Mine is ROOTED, but stock, so.....
tonyx3 said:
Modaco's page confused me a little.
Does the "Main update" include the radio update, or did he split that off and they're completely separate?
Can the main update be installed using a rooted, but stock, rom and recovery?
In other words, if I just want exactly what the OTA would give me, on my rooted (by superboot) but stock N1, what do I need to do?
Thanks!
Click to expand...
Click to collapse
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Paul22000 said:
Can I flash this manually WITHOUT being rooted?
Click to expand...
Click to collapse
yes, just did it 5 min ago
PhantomRampage said:
I'm in the same exact boat as you. I rooted my phone last week because i was eager to get multitouch working, so i followed this tutorial:
theunlockr[dot]com/2010/01/21/how-to-enable-multitouch-browsing-on-your-nexus-one-using-the-native-browser/
So now when i try to apply the OTA update manually in recovery mode i get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Browser.apk" , "68a23e4ac9d6a783b6166b24ab79d12c6544e8f4" , "4da6d3fd306ef7fc81e19147da395f13221e70307")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Does anyone know what i can do to get this OTA up and running? Im rooted but i havent flashed any custom roms or recoveries either.
This is my first android phone so i'm a bit of a noob and new to the scene. Any help would be greatly appreciated
Click to expand...
Click to collapse
http://www.nexusforum.net/nexus-one-help-forum/493-how-manually-retrieve-new-update-your-nexus-one.html#post2000
check that guide out, it was simple and easy to follow...
Thanks JHaste.
But those are pretty much the exact instructions I followed that gave me the error.
My phone is rooted, but running the stock rom.
No custom rom, no patched browser.
The only changes I've made since rooting it are to copy some Thai fonts into the fonts directory.
The exact specifics of my error are posted in:
http://forum.xda-developers.com/showpost.php?p=5528501&postcount=118
Very similar to what PhantomRampage listed, but a slightly different cause, I think... (his is an error on Browser.apk)
JHaste said:
-Removed quoted link since i cant post them yet-
check that guide out, it was simple and easy to follow...
Click to expand...
Click to collapse
Thanks for trying but as i said before, i tried that and it fails because i have an unlocked bootloader.
Sorry if my first post was confusing, ill try again.
I unlocked my bootloader and rooted my N1 the other day, i also modified and added some files to get pinch-to-zoom working on the native browser. To do that i followed some tutorial on theunlockr, i cant post direct links so google it and you'll find it easily.
So, now i want to apply the new OTA update but it fails, either because i have root access or because i tampered with the browser files im guessing.
Knowing all that, what can i do to install the new update?
Also, will i have to download patched updates from now on since i rooted my phone? I'm really hoping i dont have to; i'd prefer to install the ota updates as they come out officially.
might have found a solution
check out:
forum (dot) androidcentral (dot) com / google-nexus-one/6469-will-my-n1-receive-ota-ere27-update-cyanogen-mod (dot) html
seems to be just what i was looking for but i think i want to re-flash the stock firmware instead, i want to stay as stock as possible so i can install future OTA updates without having to go through all this trouble. Can anyone help me with that please?
Anyways, i hope my link will help some people. Sorry for the double post
Closing Double Thread (it's also at Development).
Please do not duplicate threads if not necessary.
So My Nexus 7 is simple Stock android 4.2.1 with root and i go to update to 4.2.2 and i get a error (The red triangle one)
Can anybody help i hear there are others with this same problem but yet to find somebody with a solution, do you think i should unroot and relock the nexus and try and update again or just reflash back to stock image
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
bftb0 said:
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
Click to expand...
Click to collapse
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Thanks!
MatthiasSchuetze said:
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Click to expand...
Click to collapse
Ummm... you are forcing me to guess about your situation. You are rooted, but also do not have a custom recovery installed?
What error message do you find in the /cache/recovery/recovery.log file? Please do not simply say "Status 7", report the FULL ERROR message.
As I said, the OTAs are meant to be used with pure stock ROMs, not customized/rooted ROMs. There do not exist an infinite array of OTA file variations corresponding to a fix for the exact problem you are experiencing, unless you were to create one for yourself by unpacking the OTA zip file and hand-editing the META-INF/com/google/android/updater-script file to skip over the problem you are experiencing.
And if you did that, you would certainly need to use a custom recovery to install it, as doing the operation described above would break the signing of the OTA package, so the stock recovery would refuse to install it.
The other alternative which allows you to use the unmodified OTA is to "fix up" a customized ROM by manually replacing all files that were removed or altered with their original stock versions. This process seems almost as ridiculous as the scenario described above, as now you are purposely breaking the modifications performed by root-aware apps (Stickmount? Beats Audio? Titanium Backup?)
The amount of effort this whole process will take is variable depending on how much stuff has been changed since you rooted. When the OTA performs it's checks prior to beginning it's patching operations, it halts on the first check which fails. Which might mean that you will need to iterate several to many times the process of:
- run the OTA, look at the error in /recovery/log/recovery.log
- hand patch the file involved
- re-run the OTA.
Doing the above can be problematic if you have changed multiple framework files - if you replace stuff one file at a time it is possible to wedge the OS because of dependency issues.
The only good news here is that because the OTA runs all it's checks before it patches anything, it is safe to run it as many times as you can tolerate. (On tilapia devices, though there is evidence that using custom recoveries is almost never a good idea if you want the radio firmware to be updated correctly).
A wholly better idea is to simply start over. Make a full Nandroid backup of your current ROM. If you want, you can also experiment with backup/restore apps like Titanium Backup and/or Carbon.. Then you install a pure stock ROM from the Google Factory images, and begin re-customizing all over again, as if you had just bought the tablet.
If you don't like the result, restore your Nandroid backup. That's what backups are for.**
good luck
** its a good idea to get copies of your Nandroid backups off of the device, as there are various ways that the entire /data partition can get wiped - including the psuedo-SD card containing all your precious backups. You've been warned.
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
MatthiasSchuetze said:
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
Click to expand...
Click to collapse
On both devices the files do not match the expectations (assert failed), i.e those files are not the original ones the OTA is expecting -> You need to re-apply the original files to your ROM before you can apply the OTA or you need to do flash the 4.2.2 system manually, which probably might be the easier solution.
Hi everyone, I have a rooted with stock rom nexus7 with TWRP recovery, every time I want to update to 4.3, it fails, at first it comes to install and after saying 'Verifying Package', it goes to recovery first menu, Any suggestions??
by the way, I don't want to loose any of my data.
Gosh, there are so many threads on this. Did you search or read anything? The specific error is important, but you didn't say what it was. Depending on which error you have determines how to fix it. Was it an 'Error executing updater binary in zip...' or did you get a verification failure on a file such as 'debuggerd' or a system app that you may have replaced or frozen? I was able to fix my problems for a stock rom and kernel, rooted with TWRP after reading the threads in this forum. And your data won't be 'loose' nor will you lose data with this update, but you will lose root, which can be regained easily.
ive got clean rom installed and the google update has come up....should i install it !?!?
Have you received KitKat already?
Running a custom ROM you cannot install Google updates. It will fail and you will come back here asking why it failed.
Sent from my Nexus 5
onisuk said:
ive got clean rom installed and the google update has come up....should i install it !?!?
Click to expand...
Click to collapse
Hi, onisuk...
Any particular reason why have you created two threads asking the same question?
OTA's aren't full ROM's... they are 'patches' to files the OTA update expects to find ONLY if you are currently running official Google factory stock. This is accomplished by the OTA first running checksum tests on all files in /system and elsewhere on the Nexus 7. This is to confirm/ascertain that nothing has been changed or modified from official Google factory stock. It would, after all, be impossible for a Google OTA to apply a 'patch' (ie. update) to an important system file, if that system file had already been modified by the user, as would have occurred in the event of a Custom ROM being flashed.
If just one file fails this checksum test, the OTA will abort, with no changes made. And since Custom ROMs are a departure from the official Google factory stock ROM, the OTA will fail. And thus, this is why Googles OTAs can never be successfully applied to Custom ROMs.
So the answer to your question... is 'no'. It would be pointless.
Any subsequent updates to CleanRom would have to come from the developer of that particular Custom ROM itself... and not from Google.
Rgrds,
Ged.
just installed it and didnt say it failed was just a 3.4 patch only a few mbs .... didnt realise id double posted if some mod could remove the other one please !
I have a Nexus 7 2012 Wifi only, currently with Android 4.4.4 Kit Kat. The tablet is rooted and has TWRP installed. I downloaded this OTA package: http://android.clients.google.com/p...signed-nakasi-LRX21P-from-KTU84P.4939a9ff.zip
When I try to install it using TWRP, I get this:
mount: failed to mount /dev/block/platform/sdhci-tegra3/by-name/APP at /system: Device or resource busy
Package expects build fingerprint of google-nakasi-grouper:4.4.4/KTU84P/1227136:user/release-keys or google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper:4.4.2/KVT49L/8d195fb610:eng/test-keys
I looked for this error but didn't find anything. What can I do? (Thanks in advance!)
dude the error is written in plain English: the process expects one type of thing in your system, but it finds another, doesn't like that so quits. trying to find the exact source of the error would be futile. I received an error too, not sure if it was the same since I didn't bother reading it. I just downloaded the stock 4.4.4 firmware from Google and extracted system.img and flashed it with fastboot. I'd suggest you go that route. you can try flashing from twrp again after that, personally I went the adb sideload route: http://forum.xda-developers.com/nexus-7/general/lollipop-ota-update-via-adb-data-t2941175
arimaidana said:
I have a Nexus 7 2012 Wifi only, currently with Android 4.4.4 Kit Kat. The tablet is rooted and has TWRP installed. I downloaded this OTA package: http://android.clients.google.com/p...signed-nakasi-LRX21P-from-KTU84P.4939a9ff.zip
When I try to install it using TWRP, I get this:
mount: failed to mount /dev/block/platform/sdhci-tegra3/by-name/APP at /system: Device or resource busy
Package expects build fingerprint of google-nakasi-grouper:4.4.4/KTU84P/1227136:user/release-keys or google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper:4.4.2/KVT49L/8d195fb610:eng/test-keys
I looked for this error but didn't find anything. What can I do? (Thanks in advance!)
Click to expand...
Click to collapse
You are using OmniROM. Pretty obvious you can't upgrade a custom ROM with a stock OTA.
This has nothing to do with omnirom at all, it all has to do with twrp using a custom .prop with wrong preset values. It wasn't an issue until Google decided that the 5.0 update checks more things, hence this stupid error. Btw that's exactly the 1st thing the upgrade script checks!
twrp must change its way of providing props because it's so obviously a major bug and will prevent using it to install any future updates.
What I did is use the factory image to do a custom non-wiping upgrade (there's a topic about how to do that), got incredibly slow performance and then do a wipe to get performance back and start with a clean slate with Lollipop, like I did with Kitkat.
So I think if your Kitkat was starting to be slow, better start anew and anyway Lollipop lets you choose exactly what to reinstall.