Database Develop

[Q] Cannot flash .zip files with CWM

I am currently running Stock JVH with Fugumod kernel 3.8. My problem is that I am unable to install ANY .zip file from CWM. I have tried supercurios hacked kernel also, but I got the same error:
Chose install zip from SD card:
Finding update package...
Opening update package...
E:Can't open /sdcard/XXXXXXXXXX.zip
(bad)
Installation aborted.
I have redownloaded every rom I have tried to flash several times, in case it was corrupted or something, also reflashed stock rom via Heimdall twice, nothing has worked. I have been using custom roms via cwm and heimdall for months, this has never happened before.
What could be the problem? Any help would be greatly appreciated.

bandiBp said:
I am currently running Stock JVH with Fugumod kernel 3.8. My problem is that I am unable to install ANY .zip file from CWM. I have tried supercurios hacked kernel also, but I got the same error:
Chose install zip from SD card:
Finding update package...
Opening update package...
E:Can't open /sdcard/XXXXXXXXXX.zip
(bad)
Installation aborted.
I have redownloaded every rom I have tried to flash several times, in case it was corrupted or something, also reflashed stock rom via Heimdall twice, nothing has worked. I have been using custom roms via cwm and heimdall for months, this has never happened before.
What could be the problem? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi, not sure if it's possible but maybe your data cable is corrupting the files during transfer. I have had this message before and it was due to the file being corrupted. If you try and open the .zip file on your computer you can see if it is corrupted (if it opens it isn't).
Suppose away of testing if the data cable is corrupting your files during transfer would be to try and open the .zip file on your phone using thinkfree office or something similar. Again if it opens then it is not corrupted and I have no other thoughts.

[Q] Clockworkmod wont install

I just flashed back to stock (apparently a new version) which is 2.2. My problem is that i cant install clockworkmod. Ive tried two different methods
1. Using rom manager, and just downloading it then flashing it.
2. Downloading the clockworkmod file, putting it in the root directory, and using adb to go into recovery and install it.
Both times i got this error
Finding update package..
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
How can i fix this?
Thanks

Check out the third sticky in captivate general. The one about 3e signature verification. May be what you are looking for.

yeah, i just tried that. Didnt work. Im not sure if i did it right though...
I did..
1) copy the recovery file onto my phone
2) download terminal emulator
3) type su (to get it root access)
4) enter the command (nothing happened after i entered it... it just entered)
5) open file expert and put the file in the right directory
6) use adb to reboot into recovery
then i tried flawshing update.zip... same signature problem

[Xposed] Error Executing Binary Updater (on ZTE Grand X Max+) ?

I tried flashing the [sdk 22 arm] zip for lollipop (5.1) on my phone, but every time i tried, I got an error saying "error executing binary updater in {zip file}". Occasionally, when i tried, i also got an error about low storage space. What is a binary updater error? How do I fix it? I know for sure i'm using the right zip. Please help me out here. Is it just incompatible with my phone, or there's something I can do about it?

Unable to install frameworks, ZTE Blade Q Lux

Hi,
Here a brief of my phone
ZTE Blade Q Lux
Android 5.0.2
MSM8916
Installed exposed
Try to flash sdk21, all version but encounter error failed to update, file corrupted
Then I tried copy manually to root/system and root/meta-inf
Xposed detected SDK v80 installed but not activated
Checked the log but log error
What should I do? Please assist me
Thanks

Here what shown when flashing the SDK 21 v80 ARM
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Update failed, package corrupt
installation aborted

Lex-ON said:
Here what shown when flashing the SDK 21 v80 ARM
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Update failed, package corrupt
installation aborted
Click to expand...
Click to collapse
Use a recovery that allows disabling signature verification, for example TWRP.

TWRP Manager 3.0.0 on playstore? I tried it, there are no option to disable signsture. Or I'm doing it wrong. If there's a specific link to download or use it, highly appreciated
Thanks

Lex-ON said:
TWRP Manager 3.0.0 on playstore? I tried it, there are no option to disable signsture. Or I'm doing it wrong. If there's a specific link to download or use it, highly appreciated
Thanks
Click to expand...
Click to collapse
TWRP Manager only downloads the TWRP for your device (if any is available). You have to flash it either manually by using ADB or use an app like ROM Installer or Flashify. Best way is via ADB. If you don't know how to do this, search for "your device name TWRP ADB flash"

orville87 said:
TWRP Manager only downloads the TWRP for your device (if any is available). You have to flash it either manually by using ADB or use an app like ROM Installer or Flashify. Best way is via ADB. If you don't know how to do this, search for "your device name TWRP ADB flash"
Click to expand...
Click to collapse
Checked it. the stock ROM I downloaded from ZTE.com does not contain *.bin files. is it able to use adb flash? I was unable to do so
attached the file contents

Error 255 Xposed Install

I am trying to install Xposed via TWRP but it simply says Updater process ended with error 255.
Error installing zip xxxx.zip
I've searched but can't find a solution?
Thanks

Anyone?

matt09 said:
I am trying to install Xposed via TWRP but it simply says Updater process ended with error 255.
Error installing zip xxxx.zip
I've searched but can't find a solution?
Thanks
Click to expand...
Click to collapse
Seems to be an issue with TWRP itself. Search for either a newer version or a different version of TWRP.