When I initiate a Backup Current Rom from Rom Manager Premium v4.3.1.4 the phone will:
Reboot into Android System Recovery <3e> -->
Then have this text on the screen:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
And I am left with options to:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
I end up rebooting and the phone reboots properly. I am trying to backup my current rom (stock ke7 rooted with odin instructions from: http://forum.xda-developers.com/showthread.php?t=1056334) so just incase I do something to mess up the phone I can always go back and restore.
Can anyone provide help with this issue??? Go easy on me since I am a recent convert from iOS and this is my first Android device.
I have the sam issue
rom manager isnt completely compatible with the sgs2. Thats why people use alternate methods such as cwm.
stoney73 said:
rom manager isnt completely compatible with the sgs2. Thats why people use alternate methods such as cwm.
Click to expand...
Click to collapse
Thank you!
Is CWM always included in custom roms?
BAWS said:
Thank you!
Is CWM always included in custom roms?
Click to expand...
Click to collapse
Not always, but they would state if they do or dont. From what I've seen here on the sgs2 forums, it looks like cwm is included.
The big question is, have you rooted your phone? because unless your phone is rooted, you cant back it up via recovery/cwm.
To root, follow the directions in the FIRST post of this thread.http://forum.xda-developers.com/showthread.php?t=1103399
it will root your phone, and install cwm recovery, and a cwm app (which has similar functions to rom manager) that is fully compatible with the sgs2.
yeah dats great...chainfire method...
Hi,
Where can I find an how to guide to use this utility???
Related
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.
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.
Hi guys
some help if poss, ill try and remember the steps i took
firstly UK SG2 on Three
1# Flashed XWKK5
2# Following this guide http://forum.xda-developers.com/showthread.php?t=1075278 proceeded to root
3# Downloaded KE7_insecure kernal from Odia's thread
4# Flashed and ran the only version of Superoneclick i could find named
SuperOneClick1.9.5-ShortFuse.Drivers. Root was successfull well so the software told me
5# Flashed stock XWKK5 kernal
6# Rom manager "Reboot into Recovery and ...
--Installing package...
finding update package...
opening update package...
verifying update package...
E: failed to seek in /cache/update.zip (invalid argument)
E: signature verification failed
installation aborted
help! lol
What the...
What do you want to do? Root your phone?
Find chainfires cfroot kernel thread and flash the KK5 one from there.
The other errors look like Rom manager is trying to find and access CWM but because you flashed a stock kernel back its not there. Only stock recovery.
Sent from my GT-I9100 using XDA App
It's not an issue. CWM Recoveries are installed within the kernels. If you flash back to stock kernel, you will lose CWM Recovery. Naturally, ROM manager does not work with CWM recoveries on the Samsung Galaxy S II, so let's say you clicked Install ROM in ROM Manager, it would reboot to the stock Samsung recovery, but until you reboot to CWM Recovery it would take it's effect to install the ROM you want.
I suggest you to stick to a custom kernel, I use the Void kernel, and I think it is a great kernel.
Hi Guys,
Need a bit of help here.
I bought the clockworkmod touch yesterday, I flashed it, but when I went into recovery it wasn't touch, so I wiped cache, dalvik cache etc...and then isntalled the update.zip to no avail it said "E: failed to verify whole-signature", I tweeted @clockworkmod, and he said it was because I was using SpeedMod Kernel.
So I moved over to Siyah kernel, installed that fine and restored my data/cache using CWM when it booted. I then try to flash ClockworkMod Touch through ROM Manager, the green bar fills, and then says "Succesfully downloaded ClockworkMod recovery!"
I click ok, and then go to "reboot into recovery" I'm presented with red text that says:
E:missing bitmap password_highlight (code-1),
E: missing bitmap password_confirm_45 (code-1),
E: Missing Bitmap password_retry_45 (code-1)..."
I'm then presented with:
Installing Package...
Opening Update Package
Verifying Update Package...
E:Failed to verify whole-file signature
E:Signature Verification failed.
Installation aborted
I've then gone into three button method, and tried to apply, /sdcard/update.zip and it comes up:
Finding update package
Opening update package
E: Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
I'm running the following setup:
Model:GT-I9100
Android: 2.3.5
Baseband version: I9100XXK14
Kernel Version: [email protected] #294
Build number: Gingerbread.XWKJ1
I would like it if I could get this fixed without using Odin, as i'm at work most of the time and because of some stupid drive encrytion I can't put my phone in without encrypting it, BSkyB's rules apparently. I have tomorrow off, so I can if neccesary boot my laptop up and fiddle with odin.
Just wanna get this sorted, I purchased this and wanna use it.
Any help is much appreciated.
You have to wait until devs add this to their kernels/ roms
Sent from my sgs2 running cm9 using xda app
Is there no kernel that can support it?
I actually don't really care which kernel I use, aslong as it 's Stock rom for now, then I may look at new 4.0 roms/kernels when they've been out a good few more months, and when obviously clockwork mod touch is more commonly added to kernels/roms.
A guess its Rom Manager as SGS2 does not like it .
As this is an app their is a thread in the applications section .
jje
richfreestone said:
Hi Guys,
Need a bit of help here.
I bought the clockworkmod touch yesterday, I flashed it, but when I went into recovery it wasn't touch, so I wiped cache, dalvik cache etc...and then isntalled the update.zip to no avail it said "E: failed to verify whole-signature", I tweeted @clockworkmod, and he said it was because I was using SpeedMod Kernel.
So I moved over to Siyah kernel, installed that fine and restored my data/cache using CWM when it booted. I then try to flash ClockworkMod Touch through ROM Manager, the green bar fills, and then says "Succesfully downloaded ClockworkMod recovery!"
I click ok, and then go to "reboot into recovery" I'm presented with red text that says:
E:missing bitmap password_highlight (code-1),
E: missing bitmap password_confirm_45 (code-1),
E: Missing Bitmap password_retry_45 (code-1)..."
I'm then presented with:
Installing Package...
Opening Update Package
Verifying Update Package...
E:Failed to verify whole-file signature
E:Signature Verification failed.
Installation aborted
I've then gone into three button method, and tried to apply, /sdcard/update.zip and it comes up:
Finding update package
Opening update package
E: Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
I'm running the following setup:
Model:GT-I9100
Android: 2.3.5
Baseband version: I9100XXK14
Kernel Version: [email protected] #294
Build number: Gingerbread.XWKJ1
I would like it if I could get this fixed without using Odin, as i'm at work most of the time and because of some stupid drive encrytion I can't put my phone in without encrypting it, BSkyB's rules apparently. I have tomorrow off, so I can if neccesary boot my laptop up and fiddle with odin.
Just wanna get this sorted, I purchased this and wanna use it.
Any help is much appreciated.
Click to expand...
Click to collapse
I am also waiting for a fix for your problem, I was about do the same steps you have done, to install the CWM touch from my SGS2, my kernel vesrion is Siyah-V2.6.12 instead.
lets wait for a solution,
I've used CWM quite a few times with great success but having trouble now.
Running Darkyrom 10.4.2 with semaphore kernel on a SGH-T959D, when I try to backup I get the following:
E:failed to mount /dbdata (invalid argument)
--Installing package...
Finding update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
This while trying to do a rom backup. I've just flashed the semaphore kernel the other day, not sure if this is contributing to my problem. I've also tried to reinstall the app but no love. I was able to boot into recovery and do a backup from there however.
Anyone help a brutha out? I'd be very appreciative...
Still trying to figure this out. I've tried wiping cache/data to no avail. Next I reflashed 10.4.2 with a wipe and reinstalled the original kernel. Result is that I'm now able to perform the backup in question.
I'm guessing the reason it wasn't working was because of Semaphore? Does this make sense?
sounds like your in the stock recovery and not cwm recovery.
droidstyle said:
sounds like your in the stock recovery and not cwm recovery.
Click to expand...
Click to collapse
But I'm trying to backup current rom via ROM Manager? Any idea what I can do to try and fix it? I've actually just reflashed Semaphore to see if it still happens and I'm back to where I started unfortunately.
Seems like the only way I can get to recovery mode is via the following:
Power button menu
Via ROM Manager
I cannot, with either kernel, get into recovery via the 3 button method.