Hello,
I have already asked this in the CM10 SGS3 discussion but could not get any help there, so I assumed this will get more attention.
Recently, I tried updating CM10 using CM Updater but CWM failed to update, complaining about signature verification of the update package. The full error was: E:signature verification failed.
Has anyone encountered this error before? If so, how can I fix this? And also - could have been any harm done due to failing signature verification on CWM?
Thanks!
executerx said:
Hello,
I have already asked this in the CM10 SGS3 discussion but could not get any help there, so I assumed this will get more attention.
Recently, I tried updating CM10 using CM Updater but CWM failed to update, complaining about signature verification of the update package. The full error was: E:signature verification failed.
Has anyone encountered this error before? If so, how can I fix this? And also - could have been any harm done due to failing signature verification on CWM?
Thanks!
Click to expand...
Click to collapse
Not on CM, so, never encountered this error before but...does this happen every time you try and update?
Sent from my GT-I9300 using xda app-developers app
Are you sure you have CWM installed? A signature verification error in this case could result in of two possible things: either you have incompatible recovery (i.e. stock) installed or it is a bad/corrupted download. No harm was done, since failing to verify signature just does not let the zip to install.
@Oomahey, I tried this just once since I was not sure about the exact outcome of this.
@hsrars-d, Yes, I have CWM v5.4, I am not making any confusions, it says that right in the title on recovery
I'll try updating this one more time and get back to you.
Thank you for your time!
I had this yesterday on a note 2 and realised it didn't have cwm recovery installed. When I installed that worked perfectly
Sent from my GT-I9300 using xda premium
Have not tried it yet but is it possible that my CWM version is old enough not to be compatible? It is version v5.4 (dot something-something)
Also, could CM Updater be using a different software on recovery even though when booting into recovery it explicitly says "Clockworkmod"? It does not make much sense to me.
Sorry for double-posting but I had to update that I have tried flashing it again, with the nightly build of 23/11 and it failed again. (after toggling signature verification on "apply new update" and using CM Updater again to update firmware)
Any suggestions?
Well, i have CWM Touch as my recovery, u could try to flash that and then update
http://forum.xda-developers.com/showthread.php?p=27597756
Sent from my GT-I9300 using xda app-developers app
executerx said:
Sorry for double-posting but I had to update that I have tried flashing it again, with the nightly build of 23/11 and it failed again. (after toggling signature verification on "apply new update" and using CM Updater again to update firmware)
Any suggestions?
Click to expand...
Click to collapse
Install Rom Manager from market than install latest Clockworkmod recovery for i9300 and that should work , you have an wold recovery
The CM Updater has never work for me, ever.
I'm running the latest version of CWM (v6.0.1.2) and when I try to update via CM Updater I get the following:
Code:
-- Installing package…Finding update package…
Opening update package…
Verifying update package…
e:failed to open /sdcard/cmupdater/cm-10-20121124-NIGHTLY-i9300.zip (No such file or directory)
E:signature verification failed
Installation aborted
I can also say that if I manually go to "install zip from sdcard" and then select to access the internal sdcard I get the same error
Code:
e:can't mount /sdcard/
Browsing the external sdcard is no problem, only the internal.
I should also mention that my phone is encrypted, if that is the reason to why I can't access the internal sdcard in CWM, I don't know.
The encryption is the problem.
SergioTeddy said:
Install Rom Manager from market than install latest Clockworkmod recovery for i9300 and that should work , you have an wold recovery
Click to expand...
Click to collapse
Is upgrading CWM different from replacing it with the stock recovery? Since, as I previously mentioned, I already have CWM installed and am just interested in upgrading it.
I am bumping this since it is still relevant. I am about to upgrade CWM and was thinking of doing this with ROM Manager (rather than heimdall/ODIN). Is it possible doing this from ROM Manager? Is it also more reliable than heimdall/ODIN in the context of bricking your phone?
Related
Long time follower (since my G1), first time poster (I think )
My question is simple, is anyone working on or is there already an update.zip or similar one-click root for the official froyo.uvka6 that was released via Tmob/Kies?
I have searched and searched but most results take me to links for rooting 2.1 and upgrading to 2.2. but no root for the official 2.2.
Am I being impatient, have I not searched properly, has someone else already posted this question somewhere else?
Flame away, I don't care, but please answer my question or point me in the right direction if you can.
Thanks!
The old root update.zip file has worked for me on all releases including KA6
jmcghee1973 said:
The old root update.zip file has worked for me on all releases including KA6
Click to expand...
Click to collapse
Thanks for a quick response...
I have tried the old update.zip and the following happens:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Possibly corrupt update.zip file? Other thoughts?
remer13 said:
Thanks for a quick response...
I have tried the old update.zip and the following happens:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Possibly corrupt update.zip file? Other thoughts?
Click to expand...
Click to collapse
You need to toggle signature when you are in recovery before clicking update.zip. it happened to me also and that's all I did and it worked.
jun_808 said:
You need to toggle signature when you are in recovery before clicking update.zip. it happened to me also and that's all I did and it worked.
Click to expand...
Click to collapse
Could you please explain more. I no longer have CWM Recovery, just the stock 3e recovery, and am unable to locate any options to "toggle signature". Am I missing something there?
The STOCK 3e recovery from odin files DOES NOT ALLOW update.zip files, no matter what you do!
To get clockworkmod running, you either need one of the voodoo kernels (which you can only flash through odin/hiemdall, because if this recovery issue) or you need root (the onlyone that works with these releases is SuperOneClick) to mount system as rw and push a modded 3e recovery (this part is found in many roms right now).
The easiest is to flash a voodoo kernel using odin, then boot recovery and flash away.
"if you amplify everything, nothing is heard"
jun_808 said:
You need to toggle signature when you are in recovery before clicking update.zip. it happened to me also and that's all I did and it worked.
Click to expand...
Click to collapse
no clockwork
I was able to root using the superoneclick
Zylograth said:
I was able to root using the superoneclick
Click to expand...
Click to collapse
Is there a walkthrough for this method?
Thanks for the SuperOneClick worked great.
Enable usb debugging.
Launch the app and follow any directions that appear. Was super easy.
Yes, if it's the same as Samsung Galaxy S One Click Root, you install the One Click Root, plug your phone in and you have two options "One Click Root" and "One Click Unroot".
Fairly straight foreward. I was surprised how easy it was when I rooted my phone lol
Hope this helps!
drscott333 said:
Yes, if it's the same as Samsung Galaxy S One Click Root, you install the One Click Root, plug your phone in and you have two options "One Click Root" and "One Click Unroot".
Fairly straight foreward. I was surprised how easy it was when I rooted my phone lol
Hope this helps!
Click to expand...
Click to collapse
+1. Telus official froyo did the same (locked bootloader) and super one click worked fine.
Essien said:
Thanks for the SuperOneClick worked great.
Enable usb debugging.
Launch the app and follow any directions that appear. Was super easy.
Click to expand...
Click to collapse
This worked for me as well. Thanks to everyone involved for the help. This post can be closed/locked as needed.
I was able to root as well using this method, however, once i am in I install clockwork recovery. Then I try to install a rom using rom manager and it only reboots into recovery 3e not clockwork. How can i make sure I get into clockwork to install from zip?
SkeptiKSZ said:
I was able to root as well using this method, however, once i am in I install clockwork recovery. Then I try to install a rom using rom manager and it only reboots into recovery 3e not clockwork. How can i make sure I get into clockwork to install from zip?
Click to expand...
Click to collapse
try 'reinstall packages' until you get there. you may have to do it more than once
bstromberg said:
try 'reinstall packages' until you get there. you may have to do it more than once
Click to expand...
Click to collapse
It won't work. I have tried maybe 50 times. It seems to be a problem with Recovery <3e>
"E:failed to verify whole-file signature"
"E:signature verifications failed"
"installation aborted"
It will not allow me to get into clockwork. This was the reason I used superoneclick (worked) instead of oneclickroot to root my phone however clockwork is my next problem.
SkeptiKSZ said:
It won't work. I have tried maybe 50 times. It seems to be a problem with Recovery <3e>
"E:failed to verify whole-file signature"
"E:signature verifications failed"
"installation aborted"
It will not allow me to get into clockwork. This was the reason I used superoneclick (worked) instead of oneclickroot to root my phone however clockwork is my next problem.
Click to expand...
Click to collapse
+1 same here..
i trying to root the phone different way and don't let, somebody help. please
Download the One click root
Unzip it
Open the executable. Make sure your phone is in debugging mode connected to your PC.
Let it do its magic.
I had a problem with the root when I used titanium backup. It kept telling me I wasn't rooted. When I opened titanium backup and it gave me the error message, I clicked on the "problems" button and allowed it to download busybox. VIOALA! I now have access to all my back ups and am rooted.
SkeptiKSZ said:
It won't work. I have tried maybe 50 times. It seems to be a problem with Recovery <3e>
"E:failed to verify whole-file signature"
"E:signature verifications failed"
"installation aborted"
It will not allow me to get into clockwork. This was the reason I used superoneclick (worked) instead of oneclickroot to root my phone however clockwork is my next problem.
Click to expand...
Click to collapse
This is happening to me, too. Also, when I tried to boot to recovery using the volume key method, it went straight to the android with exclamation point screen, wouldn't even allow me to try to reinstall packages. Booting into recovery from Rom Manager works but I get these errors when I try to reinstall packages.
I also tried to run Fix Permissions in Rom Manager and get "An error occurred while attempting to run privileged commands!" despite that I do have root access.
Hey guys, I rooted my device with the CF-KG2 kernal and am trying to use Rom Manager with Clockwork Mod 4.0.1.5. to install Cyanogen mod.
I can't get into CWM recovery for anything after installing without getting:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I can't find a solution to this on google or anywhere on this forum.
I also tried manually wiping my data/cache and installing the cyanogen nightly 26 with the CWM 4.0 included with CF kernal. It installs fine but won't boot past the samsung logo, so I had to restore.
Any help is appreciated!
Do a fresh download of a cm7 nightly.
Put it into your internal sd card.
Boot into cwm recovery
Wipe data/cache/dalvik
Flash cm7 zip
If you get stuck at the screen flash the zip again from recovery and it should boot.
Also, don't flash it via flash update, do it via flash zip.
Sent from my GT-I9100 using XDA Premium App
Thanks a ton. Believe it or not just installing the zip twice actually installed cyanogen perfectly. Amazing.
Canadianreaper said:
Thanks a ton. Believe it or not just installing the zip twice actually installed cyanogen perfectly. Amazing.
Click to expand...
Click to collapse
It's weird, seems to be due to custom versions of cwm recovery in most kernels, the other way todo it is to flash codeworx's cwm kernel then cm7, which seems to make it work with one flash of cm, but glad to hear you got it going.
Sent from my GT-I9100 using XDA Premium App
Same Here
Canadianreaper said:
Hey guys, I rooted my device with the CF-KG2 kernal and am trying to use Rom Manager with Clockwork Mod 4.0.1.5. to install Cyanogen mod.
I can't get into CWM recovery for anything after installing without getting:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I can't find a solution to this on google or anywhere on this forum.
I also tried manually wiping my data/cache and installing the cyanogen nightly 26 with the CWM 4.0 included with CF kernal. It installs fine but won't boot past the samsung logo, so I had to restore.
Any help is appreciated!
Click to expand...
Click to collapse
I also have the same problem, errors when trying to boot CWM recovery. Did not allow me to back up anything. and now my phone is stuck on the Galaxy S 2 boot screen and keeps on looping. I think I was using lightning ROM previously. What is the next thing I should do to make the phone work again.
Once the phone works, how do I get CM7 on it? Thanks so much. I am a new user and am not really familiar with the process.
gtizon said:
I also have the same problem, errors when trying to boot CWM recovery. Did not allow me to back up anything. and now my phone is stuck on the Galaxy S 2 boot screen and keeps on looping. I think I was using lightning ROM previously. What is the next thing I should do to make the phone work again.
Once the phone works, how do I get CM7 on it? Thanks so much. I am a new user and am not really familiar with the process.
Click to expand...
Click to collapse
Pull the battery and boot to cwm again. Wipe data/factory reset, wipe cache and flash cm7 (provided u put it on ur sd card).
If not, flash a stock rom, let boot and place latest cm7 .zip on ur ad card. Flash a kernel with cwm and flash cm7 .
I also have this problem. Also I can't back up my current rom, because it gives the same message as in First post. And I want to flash MIUI -rom. What to do?
Any solutions to this? I rooted using Zedomax's Method. all went smoothly. When I went into Rom Manager to backup, it said I had to flash CWM, I said ok. Now I get the same error as the OG. Don't know if the recovery worked prior to going into ROM Manager. I'm thinking of running the Zedomax's Method again to see if it reinstalls a workable CWM.
Tried customizing a ROM the other day using dsixda's kitchen utility and after I built the ROM and signed it, I tried flashing. It would open the zip file no problem but after a few seconds while hanging on the installing update, it says error flashing update and there's a line stating "(status 0)". My guess is that I have done something wrong when customizing the ROM.
I have a Nexus S with CWM 5.0.2.3. Does anyone know what this error is and if possible help me solve it?
Thanks
FirmShark said:
Tried customizing a ROM the other day using dsixda's kitchen utility and after I built the ROM and signed it, I tried flashing. It would open the zip file no problem but after a few seconds while hanging on the installing update, it says error flashing update and there's a line stating "(status 0)". My guess is that I have done something wrong when customizing the ROM.
I have a Nexus S with CWM 5.0.2.3. Does anyone know what this error is and if possible help me solve it?
Thanks
Click to expand...
Click to collapse
I am on 2.3.4 Rooted and Made a Titanium Backup 4.8.2 update.zip and a TitaniumBackup-4.8.2.zip. Tried restoring from cwm (DroidX2 BootStrap) and it also fails with a Error In /sdcard/*.*.zip (STATUS 0). I chose to make seperate zips one to restore as a System app and the other as User app. I noticed the sign option was greyed out in titanium. I assume it is related with the dsixda's kitchen utility not being installed? It may possibly be due to a missing zip signer, which is doubtful I thought that no one could sign x2 zips?
So we are more or less in the same boat. When I searched for the error via google your post was the first link! If you have any update or suggestions please post back!
Hi People
Of some reason I can't install AOSP 4.4 on my HTC One X+. Here's what I've done.
Restarted to factory settings and wiped everything.
Sended the AOSP 4.4 zip via adb sideload
Flashed the boot.img
But I'm still getting this error when I'm trying to install it:
Installing '/sdcard/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/sideload.zip'
Error flashing zip '/sdcard/sideload.zip'
Updating partition details...
Click to expand...
Click to collapse
Anyone got an idea of what I've forgotten to do, or what I do wrong?
andreglud said:
Hi People
Of some reason I can't install AOSP 4.4 on my HTC One X+. Here's what I've done.
Restarted to factory settings and wiped everything.
Sended the AOSP 4.4 zip via adb sideload
Flashed the boot.img
But I'm still getting this error when I'm trying to install it:
Anyone got an idea of what I've forgotten to do, or what I do wrong?
Click to expand...
Click to collapse
i suggest going back and reading the thread
Lloir said:
i suggest going back and reading the thread
Click to expand...
Click to collapse
Instructions
SuperUser
BusyBox
Click to expand...
Click to collapse
SuperUser is installed. Busybox... I have no idea what it is, but its probally that. I'll just have a look at it.
Hm... I see how I install it from Google Play. But isn't it possible from a zip file or..? Since I dont have any rom currently.
andreglud said:
Hm... I see how I install it from Google Play. But isn't it possible from a zip file or..? Since I dont have any rom currently.
Click to expand...
Click to collapse
i say in the thread you NEED a different recovery which just so happens, to be in the download bit where you get the rom
Ah.. Sorry. I missed that.
I really can't find the section for HTC One X+. Are there even a version for this? I need the update.zip file, since as I said, I don't have any rom currently.
again ALL the DOWNLOADS for 4.4 are in the 4.4 downloads tab. you NEED to update recovery and re-sideload the rom.
though to be honest, i highly doubt 4.4 is for you. as it's VERY unstable
I understand. But I'll give it a try.
Now you're probably still saying that I shouldn't get that ROM, but its pretty important for me.
However, I installed the Google Apps zip thingy successfully. And I rebooted my phone into recovery again. But it was still in TW. I tried to reflash the boot.img and install the zip but it was still not working.
I got ClockworkMod Recovery installed, but it doesn't seem to be able to install it.
Installing: /sdcard/sideload.zip
Finding update package...
Opening update package...
Installing update...
Warning: No file_contaxtsset_metadata_recursive: some changes failed
E:Error in /sdcard/sideload.zip
(Status7)
Installation aborted.
Click to expand...
Click to collapse
Hi,
Unfortunately I am unable to flash another rom and I can't find a fix anywhere.
So my HTC One M7 is currently running on a snapshot of CM11 and at first I wanted to flash Paranoid Android.
When I tried to flash it it said it couldn't, it just aborted. I thought I messed something up so I restored my backup.
Yesterday I wanted to update my CM rom using the built in updater but it gave me the same error later.
The only thing I could find is to update my recovery, though I am running the latest version of CWM recovery on my phone.
Any tips?
Thanks in advance
Additional information:
Just did another one. This is the outcome:
Clockworkmod Recovery v6.0.4.3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E: Error in /data/media/0/cmupdater/cm-11-20140801-NIGHTLY-m8.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
Thomas.B said:
Additional information:
Just did another one. This is the outcome:
Click to expand...
Click to collapse
Usually status 0 is a problem with the update binary.. So I would make sure you are downlaoding the correct roms for your device
lacoursiere18 said:
Usually status 0 is a problem with the update binary.. So I would make sure you are downlaoding the correct roms for your device
Click to expand...
Click to collapse
I switched from CWM to TWRP and it seems to be working fine now, thanks nonetheless man
Corrupt package ? Just to throw that out there.