Hi...I m trying to donwload cm-14.1-20161111-UNOFFICIAL-n7100.zip from Tilak TWRP but the error saying that
E3004: This package is for device: t03g.n100,GT-N7100: this device is t01teatt.
E:unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file '/external_sdcard/cm-14.1-20161111-UNOFFICIAL-n7100.zip'
Please help me how to solve this problem. Thank you.
Related
help me, in dsixda I have an error when making update.zip -
scripts / build_rom: line 363: cd: META-INF/com/google/android: no such file or directory
Error: update zip not created
I step after creating the "aroma", anyone know how I can fix this?
if I want install it on the CWM me says installation Aborted.
While trying to patch I get the following error message:
"error: failed android/app/Activity.smali in framework.jar cannot be remedied"
Autopatcher v2.9.9313
Rom: cm-10.1-20130725-NIGHTLY-i9300.zip
What's wrong?
Hi All
i have radxa Rock2 device - http://radxa.com/Rock2
i try to make update.zip for it.
I use "testkey" certificate from rock2 sdk(ROM is open source) to sign in update.zip but i get error when try to apply my update from recevory
Error message:
E: Footer is wrong
E. Signature Verification Failed
i used this article to create update.zip - http://www.londatiga.net/it/how-to-create-android-update-zip-package
Could you help me to understand why it doesn't work?
my update script has just one line - ui_print and one empty end line
thanks,
My device is Micromax q355 (MT6582, android 5.0, kernel-3.10.54+) and i am using twrp recovery v3.0.* to flash a custom rom...but i am getting the following error----------
----------------------------
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/external_sd/s6customrom.zip'
----------------------
Also i have checked my updater script and there is nothing like
"assert" in it........also using this recovery backup /restore not working properly.............
Please help
Which ROM?
Hey, I have Micromax q355 and I've been trying to install a custom ROM in it. I have installed twrp successfully but so far I've not found a ROM that is flashed without any errors. Which ROM are you using? Can you share a link to it please?
Can you please give me the link of xposed installer for q355.
Flashing update.zip signed w/OEM keys returns “failed to verify whole-file signature"
I have an update.zip which include an APK in the system/priv-app/ folder, a boot and shutdown animations and an SSH server among other things. I have the private and public keys of the OEM who sold me tablet so I used sigapk.jar to sign the update.zip file. The command I used is the following:
Code:
java -jar signapk.jar -w certificate.x509.pem key.pk8 update.zip update-signed.zip
Then after trying to flash this file via stock recovery using sideload (
Code:
adb sideload update-signed.zip
) I get the following error:
Code:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Restarting adbd...
Installation aborted.
Previously, I was trying to flash the update.zip without signing it and the result was the following:
Code:
Verifying update package...
E:footer is wrong
E:signature verification failed
Restarting adbd...
Installation aborted.
Actually I do not know if the difference in the error (footer is wrong --> failed to verify whole-file signature) is because the keys are working or not, or maybe because the file didn't have any signature at all. Can someone help me with this and tell my why is it not working if I am using the OEM's .pem and .pk8 keys?
EDIT:
I also tried adding the certificate.x509.pem file inside the META-INF/com/android/otacert folder inside the update.zip file and then sign it, but that also didn't work.
Really, no one has any idea of how to solve this issue?
sebastiantoro84 said:
Really, no one has any idea of how to solve this issue?
Click to expand...
Click to collapse
Yeah Cuz almost No One Has the private OEM Key
If you just Link the private OEM Key I can fix it! Or someone just fix it!