Hey, I'm pretty new to xda so feel free to point out anything I did wrong when creating this post...
I downloaded the Evervolv 2.1.0 build added March 1st on a thread started by jaybob413, and have been able to flash it fine and use it, but that thread has been closed and redirected to MattCrystal's thread using the same build.
I have downloaded the rom from the link that was posted, but haven't been able to flash it. I'm using Amon Ra recovery 1.6.2.
This is the error I get when verifying update package:
E:Wrong digest:
system/build.prop
E:Verification failed
Installation aborted.
When doing some research, I saw that people were saying to "toggle signature verification" under the "other" menu of recovery in the event it's unsigned, but all I see is "Fix apk uidmismatches", "Move apps+dalv", and "Move recovery.log"
I'm S-ON, is that a potential problem?
desertfox154 said:
Hey, I'm pretty new to xda so feel free to point out anything I did wrong when creating this post...
I downloaded the Evervolv 2.1.0 build added March 1st on a thread started by jaybob413, and have been able to flash it fine and use it, but that thread has been closed and redirected to MattCrystal's thread using the same build.
I have downloaded the rom from the link that was posted, but haven't been able to flash it. I'm using Amon Ra recovery 1.6.2.
This is the error I get when verifying update package:
E:Wrong digest:
system/build.prop
E:Verification failed
Installation aborted.
When doing some research, I saw that people were saying to "toggle signature verification" under the "other" menu of recovery in the event it's unsigned, but all I see is "Fix apk uidmismatches", "Move apps+dalv", and "Move recovery.log"
I'm S-ON, is that a potential problem?
Click to expand...
Click to collapse
The option to toggle signatures is in clockworkmod recovery.
There's a thread with the latest recoveries by dastin. That should fix it.
Sent from my HERO200 using XDA
I flashed CWM and didn't need to toggle signature verification, but flashed the ROM fine. Now I just have to look into the red border bug... Thanks!
Related
Ok, I had auto nootered my 1.1 and had set it up with dual booting to HC preview v.4 prior to this. to get back to stock I had used CWM to remove the dual boot (using the ZIP the dual boot thread provided) then I had interrupted the power on 8 times to wipe the data, then used the built in data wipe in the settings menu.
I then followed BN's instructions for manually installing the 1.2 update and when it reboots, it goes to a CWM screen, then fails the update complaining that the install failed: "e: failed to verify whole-file signature verification" I attempted to update it manually from SD in CWM and it's saying the same thing...
Any reason why CWM is coming up and how I can get rid of it to allow the nook to update the stock way?
***EDIT***
Search was my friend:
http://forum.xda-developers.com/showthread.php?t=931720&highlight=CWM-compatible+stock+1.2
AANND this:
http://forum.xda-developers.com/showthread.php?t=914690&highlight=cwm
So I have been trying to flash another ROM into my bionic which is on .246. I go into safestrap and activate another rom slot, I wipe the system, davlik, cache, then got into install and I choose a rom (I have tried eclipse, and Icarus) it then says install failure, and zip could not be opened. What I am I failing to do correctly? I have tried Safestrap 3.4 and I still get the same error. I have tried placing the zip on internal and external memory.
What is the error it is giving you?
Travisdroidx2 said:
What is the error it is giving you?
Click to expand...
Click to collapse
It just says, it cannot open the zip file, nothing else.
smgrajeda said:
It just says, it cannot open the zip file, nothing else.
Click to expand...
Click to collapse
i'm having the same problem. it says the following:
-- Install /sdcard/Download/Bionic-Eclipse ICS-v1.2.1 (
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/Download/Bionic-Eclipse ICS-v1.2.1 (
(Status 4)
Error flashing zup '/sdcard/Download/Bionic-Eclipse ICS
I receive the same error message for every zip rom I have tried
I see myself possibly having same problem. When i download zip do i put it on int or external sd? When im creating slot do i use int or ext memory. Noob if u cant tell.
Sent from my DROID BIONIC using xda app-developers app
---------- Post added at 10:09 AM ---------- Previous post was at 10:04 AM ----------
Oh yeah.....i have 6.2 gigs free on int mem. And 1.92 free on ext.
Sent from my DROID BIONIC using xda app-developers app
smgrajeda said:
So I have been trying to flash another ROM into my bionic which is on .246. I go into safestrap and activate another rom slot, I wipe the system, davlik, cache, then got into install and I choose a rom (I have tried eclipse, and Icarus) it then says install failure, and zip could not be opened. What I am I failing to do correctly? I have tried Safestrap 3.4 and I still get the same error. I have tried placing the zip on internal and external memory.
Click to expand...
Click to collapse
I know I'm resurrecting an old thread, but I had this problem yesterday and never did find a solution. Here's what worked for me: I removed safestrap 3.5 and went to 3.11. ROM install worked perfectly the first time on 3.11.
GTOMEX09 said:
I know I'm resurrecting an old thread, but I had this problem yesterday and never did find a solution. Here's what worked for me: I removed safestrap 3.5 and went to 3.11. ROM install worked perfectly the first time on 3.11.
Click to expand...
Click to collapse
Can confirm.. just installed cm10.1 via safestrap 3.11 a day or two ago.
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
LG Optimus 4X HD P880 (p880)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Definitely will test your advanced recovery tomorrow Thanks for your work!
Sent from my LG Optimus 4X HD
Capable of flashing KK?
Sent from my Nexus 5 using Tapatalk
^most probably as it will be based on latest CWM sources and thanks gonna flash this now
Sent from my LG-P880 using Tapatalk
Looks really good but when I install a kernel I get always status 7 error. Only with kernel zip. Rom and gapps install work without any problem..
everything seems to work but I didn't flashed anything yet
Sent from my LG-P880 using xda app-developers app
Triads123 said:
Looks really good but when I install a kernel I get always status 7 error. Only with kernel zip. Rom and gapps install work without any problem..
Click to expand...
Click to collapse
FAQ N°10
Ah OK sorry that I not read the faq correctly it's the update binary. Iodak must changed it or we do it by ourselves to flash kernel
Dear Philz,
The issue is specific to the recovery bcz Iodak v9 can be flashed through the cwm touch recovery 6.4.4, no status 7 error.
I have tested this with both your recovery and cwm.
Regards,
Kanad
Kanad said:
Dear Philz,
The issue is specific to the recovery bcz Iodak v9 can be flashed through the cwm touch recovery 6.4.4, no status 7 error.
I have tested this with both your recovery and cwm.
Regards,
Kanad
Click to expand...
Click to collapse
FAQ N°10
Posts above yours...
I can't upgrade my cm through cmupdater. I get this:
HTML:
Finding update package...
I:Update location: /data/media/0/0/cmupdater/cm-11-20140106-NIGHTLY-p880.zip
Opening update package...
I:read key e=3 hash=20
I:read key e=65537 hash=20
I:2 key(s) loaded from /res/keys
Verifying update package...
E:failed to open /data/media/0/0/cmupdater/cm-11-20140106-NIGHTLY-p880.zip (No such file or directory)
I:verify_file returned 1
E:signature verification failed
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
E:Can't open /data/media/0/0/cmupdater/cm-11-20140106-NIGHTLY-p880.zip
(No such file or directory)
Installation aborted.
I red the FAQ but I didn't understand what I've ti do
-Raffa- said:
I can't upgrade my cm through cmupdater. I get this:
HTML:
Finding update package...
I:Update location: /data/media/0/0/cmupdater/cm-11-20140106-NIGHTLY-p880.zip
Opening update package...
I:read key e=3 hash=20
I:read key e=65537 hash=20
I:2 key(s) loaded from /res/keys
Verifying update package...
E:failed to open /data/media/0/0/cmupdater/cm-11-20140106-NIGHTLY-p880.zip (No such file or directory)
I:verify_file returned 1
E:signature verification failed
I:setting up /data/media(/0) for /sdcard/clockworkmod/.no_confirm.
I:using /data/media/0 for /sdcard
I:setting up /data/media(/0) for /sdcard/clockworkmod/.many_confirm.
I:using /data/media/0 for /sdcard
E:Can't open /data/media/0/0/cmupdater/cm-11-20140106-NIGHTLY-p880.zip
(No such file or directory)
Installation aborted.
I red the FAQ but I didn't understand what I've ti do
Click to expand...
Click to collapse
/data/media/0/0
Follow instructions to use CM Updater in FAQ N°5
Y, you need to change default storage path.
Sent from my LG-P880 using Tapatalk
Manage to flash anykernel optimus prime 2.7 in PhilZ touch recovery after changing few lines in updater-script file
Sent from my LG-P880 using XDA Premium 4 mobile app
Has anyone tested this on KitKat I been stuck on beanstalk a while and found no use for this recovery yet but I do have installed ok it works well but yes it doesn't flash kernels but thats not to much of a big deal
Sent from my LG-P880 using Tapatalk
i'm using this kernel with Official Cm11
danny19901 said:
Has anyone tested this on KitKat I been stuck on beanstalk a while and found no use for this recovery yet but I do have installed ok it works well but yes it doesn't flash kernels but thats not to much of a big deal
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
i'm also failed in flashing kernel with this recovery ,
ruznik said:
i'm also failed in flashing kernel with this recovery ,
Click to expand...
Click to collapse
I believe you need to edit updater script to flash the kernel
Sent from my LG-P880 using Tapatalk
Had to install this recovery cause of latest official wasn't working with cyandelta. So far so good. Love all the interface options. It really takes recovery to another level. Great work!
Sent from my LG-P880 using Tapatalk
works very well for me
Flash this but couldn't restore my backup with it. Keeps saying that it couldn't find my backup on /sdcard. My backup is on the internal SD Card and it seems that this recovery is looking somewhere else. Can this be fixed? Thanks.
Error message during failed install of CM zip: assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
Solved: See below.
When I first got my HD+, I did an SD "install" of CM 11. Then I installed CM 11 to the emmc, via CWM, per all the instructions on the xda website.
Once CM 11 was installed, I changed to TWRP 2.6.3.0. (I like being able to name the backups.)
Then I did a wipe and dropped down to CM 10.2.1. (More stable.) I did the install from TWRP.
Then I installed the fuzz kernel from TWRP.
Last, I updated to TWRP 2.6.3.0a when I couldn't get Succulent's CM 11 to install.
Okay, so tonight I wanted to do a clean install of CM 10.2.1, without gapps this time.
So I booted to recovery, did a wipe, and tried installing CM 10.2.1.(The build came direct from Cyanogen mod's website for the Ovation.)
I get an error similar to what I got when I tried to install Succulent's CM 11. Here's the error message:
assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
I dropped back to CWM and tried installing the ROM from three different versions: CWM 6.0.4.5, 6.0.4.5b, and CWM 6.0.4.6.
I tried installing CM 10.2.1 from the internal and the external SD card.
No joy. Fortunately, a Nandroid backup beforehand and I've restored to where I was.
Any ideas what's wrong? It shouldn't be this hard. It doesn't seem that a ROM install should be Recovery Dependent . But maybe it is?
==========
Solved. leapinlar, in the thread where I originally posted this question, said to use an older version of CWM to install. Apparently some incompatibility between versions of CWM (and TWRP) and the ROM zip.
Another solution was alluded to by King200 in another forum, but it sounded arcane and hard to do. It wasn't.
Here are Windows instructions:
++++++++++
Note: This method removes the "sanity check" built into the recovery image which checks to make sure the ROM you're installing is compatible with your tablet. Obviously, flashing the wrong ROM can/will brick your tablet.
So be warned.
Since I only have one tablet that I flash CM 10.2.1 on, no problem for me. If you have more than one tablet, perhaps you should delete your hacked zip after you install, to be safe.
Okay?
But for educational purposes, here's what I did to work around the problem.
++++++++++
You do this with 7-Zip. (So install 7-Zip if you don't have it already.)
Right click on the ROM that you're trying to install.
A 7-Zip context menu opens.
Select "Open Archive."
Drill your way down to
/META-INF/com/google/android/updater-script
Right click on the updater-script and select "Edit."
Open updater-script with Notepad.
Delete the first line of code, all the way up to the first semicolon. And delete the first semi-colon as well.
Save the edited file in Notepad. You'll get a 7-zip message asking if you want to incorporate your changes back into the archive. "Yes."
Now the ROM will install with later versions of CWM or TWRP.
Note: I had to do with this with the "fuzz" kernel too.
P.S. I don't know how to read code, so I don't understand exactly what the problem here is. I peeked at the scripts. I have an "ovation" tablet. Both the ROM and the Recovery image mention "ovation" in their updater scripts. Seems like they ought to talk to each other.
Please don't do this procedure. It is dangerous. It could brick your device. And the issue is not whether you have more than one tablet, it is if you accidentally download a hummingbird (HD) zip when you have an ovation (HD+) and try to flash it to an HD+. If you remove that assert statement the HD zip will merrily install to an HD+. And you will have a real mess.
A real case happened where a Nook Color user tried to flash a Nook Tablet ROM to his Color. The assert statement which was designed to prevent that did its job and prevented it. However, another user recommended he remove the assert statement, which he did, and thus flashed the Tablet ROM to his Color. His Color ended up bricked.
NEVER REMOVE AN ASSERT STATEMENT!
There are two more safe procedures.
One, use an older version of CWM to flash the older zips.
Two, do as the procedure says by opening the archive, but don't edit the updater-script file to remove the assert line. Look in a newer zip like CM11 and extract the file 'update-binary' and copy it to the old zip replacing the old update-binary file there. Then the old zip is flashable with the newer CWM/TWRP recoveries.
Sent from my BN NookHD+ using XDA Premium HD app
Hello,
Im pretty new to this kind of stuff. So forgive me. I've Nexus 4 device, and got tired of mobile radio active bug.
Android verions 5.1.1
Looked everywhere for the fix and cried on gogole bug report page.
Now i found information about this xposed module, and mobile radio active fix on this forum.
Ive rooted my device. (confirmed with root checker app)
I had custom recovery: clockworkmod recovery v6.0.4.7 (later switched to openrecovery-twrp-2.8.5.2-mako to test and stayed on it )
From this page http://forum.xda-developers.com/showthread.php?t=3034811
i have installed XposedInstaller_3.0_alpha4.apk
App requires (red text) to flash the package, so i am putting this .zip (xposed-v75-sdk22-x86.zip) on my device and trying to flash it through recovery.
chosing it, process starts, and ill write you everything it says
(that is clockworkmod recovery log)
-- Installing /sdcard/0/xposed-v75-sdk22-x86.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /data/media/0/xposed-v75-sdk22-x86.zip
(Status 255)
Installation aborted
tried many times, redownloading the file, renaming it to a.zip
same message every time.
I have also switched to
openrecovery-twrp-2.8.5.2-mako
Tried to flash it using this.
Also error:
updating partition details...
.. done
Full SELinux support is present
MTP Enabled
Installing '/sdcard/xposed-v75-sdk22-x86.zip'...
Checking for MD5 file...
Skipping MD5 check: No MD5 file found
E: Error executing updater binary in zip " /sdcard/xposed-v75-sdk22-x86.zip'
Error flashing zip ' /sdcard/xposed-v75-sdk22-x86.zip'
Updating partition details...
... done
Comment below box "FAILED" (red color)
clicked wipe cache/dalvik
reflashed and getting same error
Am i doing something wrong? Ive no idea what to do, whats the problem. Or maybe some of you had same issue and figured out how to deal with it?
Any answer appreciated.
Thank you.
~~~~~~~~~~~~~~
Out of topic question:
Does Cyanogenmod have this mobile radio active fixed? I'd just switch to it if theres no way installing xposed on my nexus 4 with stock adroid)
The Nexus 4 has an ARM processor, and you're trying to flash the zip for an x86 processor. The flash is failing in order to stop you from putting the wrong software on there.
Try again with the xposed-v75-sdk22-arm.zip file. This was explained repeatedly in the first two posts of the official discussion thread.
I can see now where i've done it wrong after re-reading that post knowing what you just told me.
Must've been some weird article about nexus 4 and its processor that led me to think my processor is 32bit and i thought its ok to use x86 file even tho it says ARM everywhere. And trusted it more over the chart in the main discussion topic.
Everything comes down to my lack of knowledge.
Thank you for your patience and help.
flashed ARM file and it worked perfectly
Topic to be closed.
Thanks again!