"Signature verification faild" while installing custom ROM - XPERIA X10 Q&A, Help & Troubleshooting

hello,
i have doomkernel V6, and stock 2.3.3, while i am trying to install custom ROM ( ZIP) i got the follow:
Signature verification faild
installation aborted.
Please help

hafezs said:
hello,
i have doomkernel V6, and stock 2.3.3, while i trying to install custom ROM ( ZIP) i got the follow:
Signature verification faild
installation aborted.
Please help
Click to expand...
Click to collapse
which rom you are trying to flash?

techdevilisnowmonster said:
which rom you are trying to flash?
Click to expand...
Click to collapse
this ROM:
http://forum.xda-developers.com/showthread.php?t=1661242

but i think the problem is not in the ROM,
here i am writting what i got:
installing: /sdcard/myfirstrom_v1.0.zip
finding update package...
opening update package...
installing update...
amend scriting (update-script) is no longer supported.
amend scripting was deprecated by google in android 1.5.
it was necessary to remove it when upgrading to clockworkmod 3.0 gingerbread based recovery.
please switch to edify scripting (update-script and update-binary) to create working update zip packages.
installing aborted.
then i press on : toggle signature verification & toggle script asserts:
signature check: enabled
script asserts: enabled
and try again to install the ROM:
installing: /sdcard/myfirstrom_v1.0.zip
finding update package...
opening update package...
verifying update package...
E:signature verification faild
Installation aborted
i hope now it is clear, waiting your help.

i found the reason here:
http://forum.xda-developers.com/showthread.php?t=897026
it is because of CWM, i have CWM 5, it seems it should be CWM 2 to work with this custom ROM, i will try to flash other ROM.

hafezs said:
i found the reason here:
http://forum.xda-developers.com/showthread.php?t=897026
it is because of CWM, i have CWM 5, it seems it should be CWM 2 to work with this custom ROM, i will try to flash other ROM.
Click to expand...
Click to collapse
doomkernel v6 does not have cwm 5 ,i guess you have installed cwm auto installer,so you are getting error,doomkernel v6 has already recovery compiled,just try hitting back button when blue light turns on

techdevilisnowmonster said:
doomkernel v6 does not have cwm 5 ,i guess you have installed cwm auto installer,so you are getting error,doomkernel v6 has already recovery compiled,just try hitting back button when blue light turns on
Click to expand...
Click to collapse
thank you too much i did not know that i should hit the back button, i was hitting the volume up button and i was going to CWM recover.
by the way i installed CWM 5 via flashtool, but it seems it is useless.
I succeeded in installing the custom ROM.
thanks for your help.

hafezs said:
thank you too much i did not know that i should hit the back button, i was hitting the volume up button and i was going to CWM recover.
by the way i installed CWM 5 via flashtool, but it seems it is useless.
I succeeded in installing the custom ROM.
thanks for your help.
Click to expand...
Click to collapse
cwm 5 is not useless,the thing is that you are trying to install a rom based on old scripting(amend) to new cwm so you were getting error coz for cwm 5 you need to flash a rom with edify script..
cheers:laugh:

Related

[MOD][4.21.11] New Superuser package Root your Fascinate

New su.zip. Just changed updater-script and update binary to work with mount.wrapper we are using on our custom kernels. Will work from stock phone as well. Script is edify but will work with cwm2.5 as well.
Directions
Download su-2.3.6.1.x.zip and place on your sdcard.
Odin cwm if you do not have it.
Boot into cwm recovery.
Flash zip
Reboot
Profit
Fantastic and easy!
Stellar! Thank you Nemesis, very handy to have atm.
Nemesis2all - worked perfectly.. Thanks man for this and the help in IRC..
Murd0ck
How would I install this on a stock phone?
DirgeExtinction said:
How would I install this on a stock phone?
Click to expand...
Click to collapse
By following directions. Place zip on sdcard, odin cwm recovery, boot to cwm recovery, flash zip in cwm recovery.
nemesis2all said:
By following directions. Place zip on sdcard, odin cwm recovery, boot to cwm recovery, flash zip in cwm recovery.
Click to expand...
Click to collapse
I finally got it. Thanks for this new su.
I must be blind
Can someone point me to an Odin package for CWM3? or is 2.5 all I can use? want to flash this after OTAu. Thanks.
xvoorheesx said:
Can someone point me to an Odin package for CWM3? or is 2.5 all I can use? want to flash this after OTAu. Thanks.
Click to expand...
Click to collapse
As far as I know there is no ODIN package for CWM3. I have seen instructions in other threads on how to get it through rom manager, but I am drawing a blank at which specific thread.
nemesis2all said:
New su.zip. Just changed updater-script and update binary to work with mount.wrapper we are using on our custom kernels. Will work from stock phone as well. Script is edify but will work with cwm2.5 as well.
Directions
Download su-2.3.6.1.x.zip and place on your sdcard.
Odin cwm if you do not have it.
Boot into cwm recovery.
Flash zip
Reboot
Profit
Click to expand...
Click to collapse
So I did all the above and then when I try to boot in recovery using CWM I get the below message...
-- Install from package...
Finding update package...
Opening update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
It brings me back to the blue recovery screen.
jimmy2179428 said:
So I did all the above and then when I try to boot in recovery using CWM I get the below message...
-- Install from package...
Finding update package...
Opening update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
It brings me back to the blue recovery screen.
Click to expand...
Click to collapse
Odin cwm 3-30 fix all with battery pulled
After odin is completed insert battery and give phone three finger salute to make it cwm.
Flash su zip I provided above.
jimmy2179428 said:
So I did all the above and then when I try to boot in recovery using CWM I get the below message...
-- Install from package...
Finding update package...
Opening update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
It brings me back to the blue recovery screen.
Click to expand...
Click to collapse
nem's post above this one is exactly correct on how to fix the problem, but in case you (or others reading this) aren't clear as to the WHY...
It's the "blue recovery screen" above. Stock recovery is blue. It requires signatures and non-test keys, and is therefore useless for us. Our standard Clockwork is red, and is what you Odin in with the 3-30 package. This is what you want, and need to put on the phone before anything else. There's also orange, which ROM Manager installs -- it's still buggy, so don't flash it.
If im not being lazy later today i'll go ahead and create an odin package for the latest CWM 3.x with voodoo options.
Sent from my SCH-I500 using XDA App
Originally Posted by jimmy2179428
So I did all the above and then when I try to boot in recovery using CWM I get the below message...
-- Install from package...
Finding update package...
Opening update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
It brings me back to the blue recovery screen.
had the same thing happen to me,all i did was odin cwr again and it worked
If anyone wants to take the time and use the settings I changed for mounting system and create a signed zip to alleviate issues people have on stock recovery feel free to do so. If not I might get around to it Monday. I am not sure if the mount options will work on stock recovery tho so please make sure you test before hand. I suppose sometimes I think for the most part almost everyone will be using a custom kernel or cwm. Sorry that when I did the zip I didn't take into account all possible situations.
I cannot get busy box to stick. Any ideas?
Bump.
10chars
xvoorheesx said:
Can someone point me to an Odin package for CWM3? or is 2.5 all I can use? want to flash this after OTAu. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1046905
(yeah I know this is old news, but the thread might as well have this link)
joe_knowitall said:
I cannot get busy box to stick. Any ideas?
Click to expand...
Click to collapse
Rumor is stock rom our kernel wipes root. Stock kernel definitely wipes CWM, but there is a patched stock kernel here on XDA.
If you are desperate, you could try doing it manually?
http://forum.xda-developers.com/showthread.php?t=1045615
joe_knowitall said:
I cannot get busy box to stick. Any ideas?
Click to expand...
Click to collapse
I'm currently on stock ED03 and I was only able to get busybox to stick by using adb to push busybox to /system/xbin while in CWM 3.x. I forgot the link, but there was a download that had the rage.bin, Superuser.apk, su and busybox files with the instructions to manually root. I ignored all that.. used this Superuser zip in CWM and pushed busybox manually.

ROM manager failing to backup current rom?

I am running stock ROM, however if I try to backup it up, It goes in recovery and say:
Installing packages...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I am running the latest version, from the market.
Thanks
if youre rooted, you should have CWM in your app. Do a nandroid backup with that, not rom manager.
I rooted manually, not with CF-root.
You need a cf-root kernel to do a backup since it gets rid of the verification check.
Thanks guys
IIIPowerIII said:
if youre rooted, you should have CWM in your app. Do a nandroid backup with that, not rom manager.
Click to expand...
Click to collapse
x-cimo said:
I am running stock ROM, however if I try to backup it up, It goes in recovery and say:
Installing packages...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I am running the latest version, from the market.
Thanks
Click to expand...
Click to collapse
I am having the same issue. I am rooted factory froyo 2.2. How to do a nandroid backup with CWM? Where do I find this CWM?
Thanks, NEWB
IMPORTANT:
If you flash a cf root kernel you will get CWM to use manually or via the CWM manager app (chainfire's app) BUT you wont be able to use ROM Manager.
To use ROM manager you will have to flash a kernel with an unmodified version o CWM (cf root gives a custom CWM). THat kernel would be this one: http://forum.xda-developers.com/showthread.php?t=1118693
Then you will be able to use ROM manager.
Now I'm confused. What is the best way to root a SGS2?
Any one?
Sent from my GT-I9100 using Tapatalk
Flash a cf-root kernel.

[Q] Problem with CWM 4.0.0.2

Hi there,
recently got my S2 and was looking to put the Cyanogen mod on it. I found the thread to install it but when I get to "step 2, reboot your phone to get into recovery"
I get the text
ClockworkMod Recovery v4.0.0.2
Finding update package...
Opening update package...
Verifying update package...
E:failed to veriy whole-file signature
E:signature verification failed
Installation aborted.
Any ideas whats wrong? I googled it and found...
The famous ROM Manager that is usually used to install ClockworkMod Recovery tool is not compatible with the updated Galaxy S due to new kernel Recovery 3e that needs signature verification for flashing external files.
The solution is to replace the kernel based on Recovery 2e that permits installing unverified signature files. Thanks to developer of XDA ‘Chainfire’ who has come up with working tools that lets you install ClockworkMod Recovery on the Samsung Galaxy S I9000 running the Android 2.3.3 Gingerbread (XXJVK) ROM.
Link to this example is: http://www.dkszone.net/install-clockworkmod-recovery-on-samsung-galaxy-s-running-android-2.3.3-gingerbread-xxjvk
Anyone know if this is the ONLY way to install CWM properly or is there another fix?
Signature related error appears when you haven't flashed the zImage of your rooted kernel via CWM. Flash it and it will disappear.
Regards.
how would I accomplish this? I flashed my ROM at the moment by using Odin tools
Your rom lite-ning rom 6.1 should have the proper cwm built in, sounds almost impossible that you're getting this error. Are you booting into cwm through rom manager? Or with Vol up+home+power?
I was trying both methods to get into CWM and got these errors everytime.

[HELP] ClockworkMod & CM9 => Problem with signature check

Hi,
I'm a noob with CM9, after a lot of months reading posts (since august), i try to install it following the steps. I install the resurrection edition from Odin, gapps, and then i update it to the last nightly...
But i have a problem with CWM and CM9.
When i reboot into recovery to install some zip signed (as modems or gps patch), i can't install it, i have a signature error.
I try to install it with and without signature verification, but it's the same:
HTML:
toggle signature verification
Signature Check: Enabled
GPS_patch_CM9.zip
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
========================
toggle signature verification
Signature Check: Disabled
GPS_patch_CM9.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/xxx/GPS_patch_CM9.zip (bad)
Installation aborted
I have ROM manager 5.0.0.6 that comes with CM9, but if i try reboot into recovery in rom manager, it runs ClockworkMod Recovery v4.0.15, and if i try to reboot into recovery using the CM9 option (hold button->reboot->recovery), it runs CWM-based Recovery v5.5.0.4.
The md5sum of the signed zips files are ok.
Someone can help me?
Thansk
P.S.: Sorry for my english
might be a problem with the current build you are using, update to the latest build it will be solved.
bala_gamer said:
might be a problem with the current build you are using, update to the latest build it will be solved.
Click to expand...
Click to collapse
Hi,
i think so, but it's strange, because i only flash my phone with the resurrection (includes a full flash) and a nigthly (and this nightly is ok).
I'll re-flash with the latest resurrection edition of CM9, and i hope it'll be solved, because i don't know what can i do...
Hi,I try now to reinstall the resurrection CM9, and i put now the zip files in the internal SD.
All ok.
Maybe the problem was install zip files from internal memory?
Regards

[Q] Unable to flash

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.

Categories

Resources