Database Users

Problems installing new ROM

I have just tried updating my Hero with 2.1, but I am having problems loading the new ROM. Not sure if my rooting was successful, as I get E:Cant open/cache/recovery/command when I do a wipe. But I now cant access Market to download a file manager to check what files I have!
When loading the ROM, I get E: No signature (504 files) E:verification failed
Files used
recovery-RA-hero-v1.5.2.img
flashrec-1.1.3-20091107-2.apk
Hero_21_v12-signed
Any ideas??

Where have you got Hero_21_v12-signed from?
Use BTDAG's guide linked in my signature,... and one of the ROM's from the Development section,... Many are recommending the 2 villian ROMs, Villian 5.5 and the Villian Slide one.

you should update your recovery. 1.6.2 is the latest.

[Q] white rabbit 1.4.1 installation error

Hi, i have a problem during the installation of the rom i have this error message :
file_getprop: failed to stat
"/tmp/aroma-data/tweaks.prop": No such file or directory
when the phone reboot, he stay blocked on the ics animation boot
someone can help me ?
( i installed the cm7 kernel before launching the rom flashing)

It seems that is a integrity problem in the zip you flashed, did you checked the MD5 sum? If the sum is ok, reflash the zip
Sent from my MB525 using XDA

I already check, md5 are equal

same problem for me....

I have the same issue. Have been using 1.3 successfully but can't get 1.4 to install.

[Q] Installation of CyanogenMod 7.2.0-RC1 aborts with (Status 7)

Hi all,
I am having difficulty installing CM 7.2.0-RC1 on my Droid 2. I have been using the official CyanogenMod wiki guide at
wiki.cyanogenmod. com/wiki/Motorola_Droid_2:_Full_Update_Guide
-phone was originally v2.3.3
-as per guide, downgraded to 2.3.2
-verified phone ok running android version 2.2
-successfully rooted with rageagainstthecage
-installed Droid 2 recovery bootstrap & ClockwordMod recovery
-verifed ClockworkMod recovery working - booted into CWM recovery and created backup
Then I tried to apply the CM7.2.0-RC1 zip update:
-put the .zips (CM7.2.0... and gapps) on my sdcard
-bootstrapped into clockworkmod via droid 2 bootstrapper
-apply update from .zip > choose zip on sdcard > chose update-cm-7.2.0-RC1-droid2-signed.zip
everything seems to go fine, then it pops the status 7 error:
Checking kernel version...
If install aborts here
make sure you are on
the OTA and not the
original GB leak!
assert failed: run_program("/tmp/check_kernel") == 0
E:Error in /sdcard/update-cm-7.2.0-RC1-droid2-signed.zip
(Status 7)
Installation aborted.
The part of the error message where it says "make sure you are on the OTA and not the original GB leak" has me confused... I was on the OTA as far as I knew, but then the wiki guide had me downgrade to 2.3.2. I assume that downgrade is a stock OTA update - am I right?
I've done quite a bit of searching, but can't figure out where I've gone wrong. Is there something else I've missed?

So are you on 2.2 or 2.3.3?

Where did you get your release candidate .zip? I would like to check the integrity of the file.
Sent from my DROID2 using xda premium

I keep banging my head against the exact same set of circumstances. I downloaded all of my files directly from the cyanogen wiki. I rooted my device first with SuperOneClick. Assuming that this might be the problem, I then SBFed it back to stock, and rerooted it verbatim per the instructions on the wiki and the cyano build... and continue to get the same results.

It took a bit of digging around in the CyanogenMod forums, but you have to be on the latest .sbf (2.3.3?). CyanogenMod 7.2 is based on the Gingerbread kernel and won't work over the top of a Froyo installation. Though I hear that you can't just flash nightlies (or any update, for that matter) over the top of it. You'll have to .sbf either way. This really sucks for me because I've got to re-flash my phone back to cricKet wireless (an hour process; manual flashing sucks) every time I .sbf as it sets everything back to the VZW defaults.
Sent from my DROID2 using xda premium

gapps-jb-20120711 continues to fail

Hey guys, I've recently successfully flashed Jelly Bean onto my Kindle Fire, but when I try to flash the gapps that hashcode linked with his rom of JB, it fails. When I try to install, it says:
"-- Verify md5 for /sdcard/gapps-jb-20120711.zip
-- No md5 file found, ignoring
-- Install /sdcard/gapps-jb-20120711.zip ...
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip 'sdcard/gapps-jb-20120711.zip
FAILED"
I can boot into Jelly Bean, but without the gapps, there really isnt anything there besides the browser and a few programs I had on the device, like evernote and bacon reader.
I searched for threads having this same problem and I couldn't find anything to help, but trust me posting a new thread was a last resort, any help will be extremely appreciated. I really want JB to work correctly, but without the play store it's hard to really get much use out of it. Thanks!

Make sure that if you are in TWRP to uncheck "md5 signature" or something like that on the flash .zip screen.
Sent from my XT894 using Tapatalk 2

I think that did the trick! I had to uncheck the Verify .zip signatures. I probably should have tried that in the first place, but didn't think about it. Thank you so much Hashcode! You're a GENIUS!!!

For anyone else having this problem, I fixed mine by reinstalling the jelly bean ROM, so if has code's trick didn't work for you, try this.

CWM recovery signature verify bug?

I have had a strange problem that when i turned the signature verify function on and install a zip in CWM recovery, But all package failed the verifying at the same percent (about 20% or less). What's worse, the package will be destroyed!
I've tried several recoveries (official 5020, snapit 6011,6015) and several roms （including gb, ics, jb and gapps for all above). All roms will get broken while gapps can't get through the verification but don't get broken. And I used md5 and sha1 hash to convince my guess. Before verification, all packages have the same hash with them in my hard disk. After verification, though, all roms' hash changed but gapps remains the same.
Strange, uhu?
Is there anyone that have found the same problem? I'd appreciate your replies.