Database Users

Flashing custom clock with CWR

Im trying to flash a custom clock skin from cwr but It keeps saying "failed to verify whole-file signature ,signature verification failed ,Installation aborted" I can install roms fine

faizan445 said:
Im trying to flash a custom clock skin from cwr but It keeps saying "failed to verify whole-file signature ,signature verification failed ,Installation aborted" I can install roms fine
Click to expand...
Click to collapse
it is probably a bad updater-script. Send me the .zip and i will take a look at it

[Q] CM10 error when applying latest nightlybuild

The error I've got is:
E: Failed to verify whole-file signature
E: Signature verification failed
installation aborted.
Any tip on how to fix it?
- Yes, I've downloaded the file again 3 times.

Help!
paulimbr said:
The error I've got is:
E: Failed to verify whole-file signature
E: Signature verification failed
installation aborted.
Any tip on how to fix it?
- Yes, I've downloaded the file again 3 times.
Click to expand...
Click to collapse
I'm having the same issue - and it's been happening when I try to use the built-in updater to flash the latest ROM. Happened with each of the nightlies from 10-08 to 10-12, including the "experimental" one. Does the built-in update feature just not work?
Please help if you can! Btw, I have AT&T's Samsung Galaxy Note i717.
Thx
-AJ Leight

paulimbr said:
The error I've got is:
E: Failed to verify whole-file signature
E: Signature verification failed
installation aborted.
Any tip on how to fix it?
- Yes, I've downloaded the file again 3 times.
Click to expand...
Click to collapse
Good evening. Did you use CWM or the official recovery for the installation? It can't be done with the official recovery.
Best regards
Enviado desde mi A953 usando Tapatalk 2

Alpo27 said:
I'm having the same issue - and it's been happening when I try to use the built-in updater to flash the latest ROM. Happened with each of the nightlies from 10-08 to 10-12, including the "experimental" one. Does the built-in update feature just not work?
Please help if you can! Btw, I have AT&T's Samsung Galaxy Note i717.
Thx
-AJ Leight
Click to expand...
Click to collapse
Hi, I've fixed this doing the following steps:
1. Download the latest build;
2. Shutdown the phone;
3. Power on and wait for a blue led blinking so press VOL Down;
4. Select to update using sd card and be happy =]
As you can see on the CWM page there is a bug on OTA updater that not update by itself.
Wish it helps..

[Q] Update Nexus 7 to 4.2 using ClockwordMod Recovery - "assert failed" (Status 7)

[Q] Update Nexus 7 to 4.2 using ClockwordMod Recovery - "assert failed" (Status 7)
Can anyone help.
I am updating my Nexus 7 to 4.2. I am using customer recovery "ClockwordMod v6.0.1.0"
After its Verifying the current system......
I get an error
assert failed: apply_patch_check("/system/bin/gzip", "52721e60f8823587e11849ce524854559b88e7de", "afdda757b22b444f41726d2c1a83012869")
E:Error in /sdcard/094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
(Status 7)
Installation aborted.
Not clear what this means.
I got a simular error when I tried to update normally with Stock recovery. When I tried it this way earlier it did not work and I got to the Android on his back with the Red Triangle. I then got in to Stock recovery but the error above was simular.
Any help appreciated.

Count Magnus said:
Can anyone help.
I am updating my Nexus 7 to 4.2. I am using customer recovery "ClockwordMod v6.0.1.0"
After its Verifying the current system......
I get an error
assert failed: apply_patch_check("/system/bin/gzip", "52721e60f8823587e11849ce524854559b88e7de", "afdda757b22b444f41726d2c1a83012869")
E:Error in /sdcard/094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
(Status 7)
Installation aborted.
Not clear what this means.
I got a simular error when I tried to update normally with Stock recovery. When I tried it this way earlier it did not work and I got to the Android on his back with the Red Triangle. I then got in to Stock recovery but the error above was simular.
Any help appreciated.
Click to expand...
Click to collapse
Believe it means that files checksum doesn't match what they think it should, meaning it was modified. So if it doesn't match, no flashy. Had the same issue with my build.prop, fixed it. Then it failed on the file for the 720p camera mod. Tried fixing it.... but that's a no go. Basically if you can find a stock rooted ROM, then copy over the file that fails....u should be good.

I downloaded and tried an unmodified file and got the same error upgrading from 4.2 to 4.2.1

[Q] Error when upating

Hi guys, i have been trying to update my Nexus 7 3G for awhile now, i had stock 4.2 and i unlocked bootloader and rooted teh device using CF-Auto-Root and it worked, i than received OTA update to 4.2.2 and i applied(i have custom recovery TWRP) and it applies update and it restarts and when i click on about tablet its still on 4.2 and after some time i get a notification saying system upate, repeat the same thing and again im stuck on 4.2.
So i decided to do a manual update and i took theupdate from http://forum.xda-developers.com/showthread.php?t=1745781 and used JDQ39 from JVP15S since i am on JVP15S and i get an error 7 and so i tried JOP40C from JVP15S and same error 7.
"assert failed: apply_patch_check ("/system/app/applicationsprovider.apk", "435f87
E: Error in /sdcard/513ad3dbbd6b/signed-nakasig-JOP40C-from-JVP15S.513ad3db.zip (status 7)
error flshing zip "......."
updating partition details..'
Than says failed in red.
Can someone help me out here?
Thanks

Flash failed, assert failed loki.sh?

I'm having trouble flashing CM12, I have the latest TWRP, bumped.
I recieve this error:
"assert failed: run_program ('/system/bin/loki.sh"
Tried an older nightly, same problem.
Anyone can help me out?
Thank you!

joq3 said:
I'm having trouble flashing CM12, I have the latest TWRP, bumped.
I recieve this error:
"assert failed: run_program ('/system/bin/loki.sh"
Tried an older nightly, same problem.
Anyone can help me out?
Thank you!
Click to expand...
Click to collapse
You have the wrong bootloader. You need to have the JB bootloader.