Hoping someone can help?
I successfully installed Lineage 16.0 (version Nightly-20200711) for Android 9 on to my YTX703F.
All went smoothly and running like a dream - love it.
I received notification of new update (25 July version).
I assumed that the install would work OK, but when I downloaded this, and try to install it I get the following error:
"E: failed to verify whole-file signature.
E: signature verification failed.
Installation aborted."
I'd consider myself reasonably tech savvy and managed to do the initial install OK but I'm stuck with this one.
I'm sure someone will be familiar with this and know how to get around it?
Thanks.
Related
Hey guys,
I am pretty new with the android OS but I am trying my hardest to read up on it and wrap my head around it. so please bear with me.
I have a verizon fascinate that was purchased a week ago and I rooted it.
I have the Rom Manager installed and the OS is running smoothly. I was going to install a custom Rom on my phone but when I tried to back up the current Rom using the Rom manager. it will boot into the Android system recover (2e) and this is what shows up on my phone:
-- Install from Package...
Finding update package...
Opening update package...
verifying update package...
E:faield to verify whole-file signature
E:signature verification failed
Installation aborted.
with that massage I dont think that I have my current Rom backed up any where...
does any one know how I can get passed this step?
I dont have much knowledge about the android operating system so if some one can help me out with this it would be freaking awesome!
---
I have not installed anything crazy, Rooted with the One click root. and Used the Titanium back up software.
You have to flash the Clockwork kernel/recovery onto it to run the update.zip that activates the backup stuff. See here.
MAKE SURE YOU FLASH INTO THE "PDA" SECTION OF ODIN AND NOT THE "PHONE" PART. "Phone" will brick your device.
Works perfect now!
Thank you very much!
i'm having the same problem, but i've already flashed clockwork? did i miss something?
fail fail
E:faield to verify whole-file signature
E:signature verification failed
Installation aborted.
Runing pt Litening_Rom_v1-5.rar tried Litening_Rom_v3-2.rar same isue .
Rom Manager (pro) fails to backup every time. When useing CWM (comeing with Litening_Rom no probelem at all)
And today I tried Litening_Rom_v4.1 same problem
jesterdallas said:
i'm having the same problem, but i've already flashed clockwork? did i miss something?
Click to expand...
Click to collapse
Which version of cwm are you using, and what are you trying to flash?
Hey. I am very new to the Droid X. I just got it as a replacement phone because I lost my HTC Incredible. I was so used to my Incredible that I only know how to half-way use this phone. I rooted this phone as soon as it was in my home. However, while trying to install GB on it, I realized I used the wrong Bootstrap Recovery. So now my phone just gets stuck on the "M" Logo. I'm not some fool that didn't do any research about this before coming here. But nothing has worked for me.
I tried re-installing to the stock rom 2.2.1 (2.3.340)
But whenever I try installing from the STOCK RECOVERY (because I can't seem to access Clockworkmod Recovery) The bar fills about 25% and cancels leaving the message :
"E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
.E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Please help. Thank you ><
Nevermind!!! DD FIXEDDDDDDDDDDD
When u fix a problem please post how you did it.not just nvm fixed it
Hi, i am from the philippines. just a while ago, i received a firmware update notification via my galaxy tab 2 10.1 (running a rooted stock rom [ICS 4.0.3 EXWALE2]. I succesfully downloaded the whole package, about 259mb, and did the installation afterwards. however, got the following errors in recovery mode:
CWM-based Recovery 5.5.0.4
E: Invalid command argument
Finding update package…
Opening update package…
Verifying update package…
E: failed to verify whole-file signature
E: Signature verification failed
Installation aborted.
has anybody here had experienced the same problem? the fix, if there is?
Another thing: I could not find the downloaded update package in my phone or just do not know where find it.
reywal said:
Hi, i am from the philippines. just a while ago, i received a firmware update notification via my galaxy tab 2 10.1 (running a rooted stock rom [ICS 4.0.3 EXWALE2]. I succesfully downloaded the whole package, about 259mb, and did the installation afterwards. however, got the following errors in recovery mode:
CWM-based Recovery 5.5.0.4
E: Invalid command argument
Finding update package…
Opening update package…
Verifying update package…
E: failed to verify whole-file signature
E: Signature verification failed
Installation aborted.
has anybody here had experienced the same problem? the fix, if there is?
Another thing: I could not find the downloaded update package in my phone or just do not know where find it.
Click to expand...
Click to collapse
I suppose CWM blocks any OTA updates, I've tried download the update twice only to get those message on CWM.
Try download the update via Kies, I just successfully did it.
However the update size it's a lot bigger than 250MB and you're gonna lose your root privileges.
cliffflip said:
I suppose CWM blocks any OTA updates, I've tried download the update twice only to get those message on CWM.
Try download the update via Kies, I just successfully did it.
However the update size it's a lot bigger than 250MB and you're gonna lose your root privileges.
Click to expand...
Click to collapse
thanks, ill try out what you said.
EDIT: (fixed)
1. I updated my tab by flashing the stock firmware (JB 4.1.1) here-->> http://forum.xda-developers.com/showthread.php?t=1704668
2. Then regained my root privileges here -->> http://forum.xda-developers.com/showthread.php?t=1957165
running via update.zip method
recovery mode reads
installing update....
package expects build fingerprint of sausung/ jflterefreshpr/jflterefreshpr: 4.4.2/KOT49H/L720TVPUBOA3: user/release- keyes or samsung/ jflterefreshpr/ jflterefreshpr: 5.0.1 /LRX22C/L720TVP UCOD2: user/release-keys/;
this device has samsung /jflterspr/jfltespr : 4.2.
E: Error in /storage/sdcard1/update (1).zip
(status 7)
E: installation aborted
can anyone help with this? i even unrooted to update this.
model version is SPHL720T
http://forum.xda-developers.com/galaxy-s4-sprint is where you want to go. This was originally posted in the International S4 forum.
[solved] "Footer is wrong" error after updating to 5.0 - can't flash (workaround)
I just decided to upgrade my Note 3 (N9005) from 4.4.2 to Lollipop - I was holding off until Xposed for TW seemed nice and stable - and used this guide to do it. The intention was to go up to 5.0 and then put on a custom 5.1 rom on with xposed.
Since putting 5.0 on, however, I appear to be able to flash almost nothing - everything comes up with the...
"Finding update package...
Verifying update package...
E: footer is wrong
E: footer is wrong
E: signature verification failed
Installation aborted"
...error, then reboots. I tried changing from CWM to TWRP, and discovered that anything which uses the Aroma installer won't run either - if I turn off verification it starts then quits back to TWRP. I tried a whole bunch of other update threads but ended up with a device that wouldn't boot.
At this point I decided to push the 5.0 ROM from Sammobile back on via Odin and try to start afresh. My device is currently working with 5.0 (and CWM) on it but I still cannot flash anything - with the one exception of arter97's kernel, which flashes fine!!!
I'm stumped. I've read various threads about the "Footer is wrong" error and am none the wiser. It cannot be the files, I've pulled a number of them numerous times (various machines too) and checked the hashes and they're all good, but I can't fined anything conclusive to give me a way forward.
Can anyone suggest a next step? Please?
After another day of fruitless searching I finally found a thread (in this forum, ironically) which discussed the problems with TWRP 3 and Aroma.
I installed TWRP 2.8.7 - still no joy with the verification - but with verification disabled (I'd checked the hashes) I finally managed to install a 5.1 custom ROM. So while I'm none-the-wiser as to the source of the "Footer is wrong" error, at least I've been able to work round it.
Hope this helps someone else.