Database Users

[Q] Rom Manager- Not able to verify whole-file signature

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?

[Q] HTC MyTouch 3G 32B Updating to Froyo Problems

Hello, at first my HTC MyTouch died after OTA update to 2.2.1 version. So I reinstalled android OS, updated it to 1.6 version DMD64, downloaded all 3 updates to Froyo, installed the fist one (~300kb), and then trying to install second (~53mb) it comes out this this error:
-- Install from sdcard...
Finding Update package...
Opening Update package...
Verifying Update package...
Installing update...
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/update.zip
(Status 7)
Installion aborted.
Maybe anyone knows how to fix this? Please help
P.S. I downloaded the update several times, and from several places, but allways it ends with same problem.

I also tried to install CM 4,5 even 6 but everytime I get the same error with BOOT, like this - assert failed: write_raw_image("/tmp/boot.img", "boot")
It would be good if I could at least turn off the update to 2.2.1 version and stay at 1.6 version, but the update reminder is so annoying

Eona said:
I also tried to install CM 4,5 even 6 but everytime I get the same error with BOOT, like this - assert failed: write_raw_image("/tmp/boot.img", "boot")
It would be good if I could at least turn off the update to 2.2.1 version and stay at 1.6 version, but the update reminder is so annoying
Click to expand...
Click to collapse
what do you mean the phone "died" is this your second phone?
You can try rooting the phone and putting a custom recovery and just install CM 6.

"died" I mean it stuck on green booting screen.
Yes I can install random recovery, but the phone don't install CM6 it installs about half and then it comes with error about boot.img and aborts installion. I get the same error installing CM4, CM5 and even official Froyo update.

Also I wanted to ask, what is the Perfected SPL?

Cant Boot
Same Problem wid my Htc magic 32B can anybody solve it??

[Q] 3.2 update issues

Hi,
I am trying to upgrade from rooted 3.1 to 3.2. I downloaded the 3.2 zip
file ( 19dea2ba1ae5.signed-trygon-HTJ85B-from-HMJ37.19dea2ba.zip)
and copied it to the xoom. When I try to upgrade with clockwork recovery,
I get a strange error:
...
Verifying current system ...
assert failed: apply_patch_check("EMMC:/dev/block < lots of text, see attached pic >")
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Any ideas/suggestions how to work around this ?
Thanks,
rudi

For some reason, some of the stock HMJ37 boot.img files don't pass the SHA1 check. So, I used the patch tool to create the "Official" HMJ37 boot.img from HRI66:
http://dl.dropbox.com/u/12011163/MZ600-HMJ37-stockboot.img
flash this boot image with fastboot, and that'll fix your issue. Glad this can help someone else- I had the same problem too (even after backing out all my files).

[Q] OTA ICS on SC failed

I'm trying to update over OTA to ICS on my 39_0089_SC device.
The update.zip will be downloaded completed.
If a start the update installation (CWR -> install zip from sdcard) I get the following failure message:
assert failed: getprop("ro.product.device") =="Indigo" || getprop("ro.build.product")== "Indigo"
E:Error in /sdcard/update.zip (status 7)
What wrong? I have only tried to flash a ROW image... no success.:crying:
device config:
CWR 5.0.2.7 installed and rooted
original SC image

Pls read the other threads on the forum. This was solved yesterday. Anyway the error is because you have Cwm instead of the normal android recovery. The solve this, comment out the lines of the updater-script that check for "indigo".

another Problem...
now I have comment out the "indigo" lines at the updater-script and made a signed update.zip (fokke.org/site/content/howto-create-android-updatezip-package).
If a try to install the upater.zip from SD card, i get a new failure message:
Installing update...
E:Error in /sdcard/updater.zip (Status 6).....
Have Imade somthing wrong?? Problems with system apps or OTA Rootkeeper?

http://www.thinkpadtabletforums.com...lopment/guide-to-installing-ota-3-(ics-4-03)/
Go here, this is a guide to upgrading to ICS.

solved - ICS Update is working now!
Below the steps what a have done:
1) Download OTA over wifi
2) modified update.zip (indigo update failure messages)
Error 6 was coming from updater-script -> not use notepad to edit!!!
3) generate new update.zip (fokke.org/site/content/howto-create-android-updatezip-package)
4) install OTA RootKeeper (protect root)
5) update "busybox" file from lenovo image (website, system/xbin/busybox)
6) install update.zip over CWR
that's it! now I'm rocking on ICS.....
(CWR is overwritten by the ICS update )
Thanks you guys for help!!!

Good to hear you sorted out your problem. And also thanks for posting the solution that worked for you. That will help the rest of us.

[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