Hello all,
Let me first start off by explaining my problem:
So I was rooted to begin with and was running superclean 2.92vooodoo with a oc kernel. For some reason my phone wouldnt start so I ended up resetting it to the original 2.1 eclair (Kill me!).
Ok, so I have superuser access, but can't get the right clockwork recovery in there to flash over a new rom. It says I am on rom manager 3.0 whatever, I try to install 2.5 or whatever the one that I had working and it says "Could not download, try later" The other problem is that my recovery is still blue (when I boot into recovery, instead of red.) When I try to install update.zip or anything that would help it. I get the response
"E: Failed to verify whole-file signature. E: Signature verification failed installation aborted."
Any help is greatly appreciated.
Scott
Do not use Rom Manager for anything in here. You will need to flash CWM 2. through Odin.
Yup CWM ALL will do the trick through ODIN
Post 3
http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/66202-how-install-use-clockworkmod-recovery-w-screen-captures.html#post690577Thank
Thank you so much guys, I was up till 4am trying to figure this out, i had that file downloaded and thought i was trying to flash it through odin but i think since rom manager was installed it was messing things up,
Thanks a lot for the help,
Scott
hey i just updated to 2.3.3 firmware on my galaxy s 4g and i rooted it and today i tried to back up my phone using the clockworkmod recovery on rom manager so i can be read to download new rom and when i tried to i got into recovery mode and everything is ok for now then when it starts to load up i get an error saying:
E:failed to verify whole-file signature
E:signarure verification failed
installation aborted.
and then it wont back up and i dont know what to do, HELP
i also have the GINGERBREAD.VUVKF1 and my kernel version os 2.6.35.7-T959VUVKF1-CL270364
so plz help
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?
I'm sorry, but I'm confused. I got that error message(thread title) when trying to flash new ROMs onto a newly rooted/stock I777. This is in recovery without ROM Manager. It also says "can't access to /system/csc/att/system" upon booting into recovery.
Sounds like you need to install a custom kernel. If you're on stock recovery you'll get this message, it won't let you install anything.
SteveMurphy said:
Sounds like you need to install a custom kernel. If you're on stock recovery you'll get this message, it won't let you install anything.
Click to expand...
Click to collapse
Thanks. I got it working.
Hi guys, i have a Alcatel OT991 (i know i know)...so i've tried to install several custom rom's special for this phone and i get this message:E:signature verification failed
Installation aborted.
I have no root, because neither one tutorial helped me to root this phone. What can i do to bypass that error? Cheers !
Ask the developer to provide a signed zip file or disable signature verification. (preferably the first)
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
navzaRazvan said:
Hi guys, i have a Alcatel OT991 (i know i know)...so i've tried to install several custom rom's special for this phone and i get this message:E:signature verification failed
Installation aborted.
I have no root, because neither one tutorial helped me to root this phone. What can i do to bypass that error? Cheers !
Click to expand...
Click to collapse
Use VRoot English Version to root your phone.
This error may be because of flashing custom roms using stock recovery, I guess.
After rooting, google some way to install custom recovery, like TWRP, CWM.
And flash your roms again.
If you get this error "assert failed" in CWM, try TWRP. And don't forget to disable "Signature Verification".
Good day to you. :victory: