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!
Related
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
Hi guys,
When i use ROM manager to do a backup (for example) it doesn't work.
It reboots, but then i get:
E: failed to verify whole file signature
E: signature verification failed
Installation aborted
And the backup fails. I can still do it after that of course, but i was wondering why it was doing that (i'm assuming it's trying to install CWM recovery or something)
When i tried CM i didn't have that problem and everything was going smoothly. Is it a bug with cognition or with the user?
Thanks!
Not to be rude but this has been asked numerous times every day. If you look at faqs post it says to not use ROM manager because you will experience what you're currently experiencing. So flash stock start over this time no ROM manager.
Duh, i never realized there was that FAQ thread. *bookmarked* and thanks for answering anyway
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?
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Anyone please?
rozel said:
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Click to expand...
Click to collapse
You need root access to flash apps or modify your system
pasanjay said:
You need root access to flash apps or modify your system
Click to expand...
Click to collapse
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
rozel said:
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
Click to expand...
Click to collapse
u have to first flash the 'Temporary CWM recovery .zip' then select 'reboot to recovery' option in stock recovery to enter 'temporary cwm recovery' there u select the 'Camera zip file' to flash.
PS- after flashing 'Temporary CWM recovery.zip' do not reboot ur phone the normal way by doing so u will lose ur temporary recovery.
each time before flashing any zip file u have to flash 'temporary cwm.zip' file first.
Hi thanks but I know this.
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
rozel said:
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
Click to expand...
Click to collapse
As the error indicates, it fails to verify the file's signature. You can't flash unsigned packages via stock recovery. The solution is exactly what was already mentioned to you:either root and install a custom kernel/recovery (you don't want it, that's fine), or use a temporary custom (non-stock) recovery. While I had problems with the stock recovery flashing unsigned zips (obviously), I never had an issue with flashing a temp recovery. Try redownloading and reinstalling it - it could be a corrupt file. Which recovery are you trying to use? I recommend the temp touch CWM by Phil (the dev of the PhilZ kernel; use link in his signature). Always works like a charm.
kt-Froggy said:
Try redownloading and reinstalling it - it could be a corrupt file.
Click to expand...
Click to collapse
Nice one! Thank you
It must have been a duff file (temp touch CWM by Phil) as the one I just downloaded, installed without a problem. It was the very same program file but from a different source.
Just installed the 4.2 Camera too so now going to play
Thank you again
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