[CLOSED] Flash fails due signature error - Android General

Hello all,
im trying to flash magisk to my android device. Therefore i only have the update function from the manufacturer inside the settings menu and wireless adb access with full root priveleges. No fastboot, no USB debug.
What i´ve tried yet: patching the boot.img from original update.zip on the device with magisk app. Than repack and sign with SignApkv2.jar and the testkeys. The device loads the update.zip and boot into recovery but than the update fails.
This is the log from the failed update:
Spoiler: Log
[ 0.401828] Verifying update package...
[ 0.424111] I:comment is 1840 bytes; signature is 1720 bytes from end
[ 9.515415] I:signature (offset: 71e19400, length: 6b2): 308206ae06092a864886f70d010702a082069f3082069b020101310b300906052b0e03021a0500300b06092a864886f70d010701a08204ac308204a830820390a003020102020900936eacbe07f201df300d06092a864886f70d0101050500308194310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e20566965773110300e060355040a1307416e64726f69643110300e060355040b1307416e64726f69643110300e06035504031307416e64726f69643122302006092a864886f70d0109011613616e64726f696440616e64726f69642e636f6d301e170d3038303232393031333334365a170d3335303731373031333334365a308194310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e20566965773110300e060355040a1307416e64726f69643110300e060355040b1307416e64726f69643110300e06035504031307416e64726f69643122302006092a864886f70d0109011613616e64726f696440616e64726f69642e636f6d30820120300d06092a864886f70d01010105000382010d00308201080282010100d6931904dec60b24b1edc762e0d9d8253e3ecd6ceb1de2ff068ca8e8bca8cd6bd3786ea70aa76ce60ebb0f993559ffd93e77a943e7e83d4b64b8e4fea2d3e656f1e267a81bbfb230b578c20443be4c7218b846f5211586f038a14e89c2be387f8ebecf8fcac3da1ee330c9ea93d0a7c3dc4af350220d50080732e0809717ee6a053359e6a694ec2cb3f284a0a466c87a94d83b31093a67372e2f6412c06e6d42f15818dffe0381cc0cd444da6cddc3b82458194801b32564134fbfde98c9287748dbf5676a540d8154c8bbca07b9e247553311c46b9af76fdeeccc8e69e7c8a2d08e782620943f99727d3c04fe72991d99df9bae38a0b2177fa31d5b6afee91f020103a381fc3081f9301d0603551d0e04160414485900563d272c46ae118605a47419ac09ca8c113081c90603551d230481c13081be8014485900563d272c46ae118605a47419ac09ca8c11a1819aa48197308194310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e20566965773110300e060355040a1307416e64726f69643110300e060355040b1307416e64726f69643110300e06035504031307416e64726f69643122302006092a864886f70d0109011613616e64726f696440616e64726f69642e636f6d820900936eacbe07f201df300c0603551d13040530030101ff300d06092a864886f70d010105050003820101007aaf968ceb50c441055118d0daabaf015b8a765a27a715a2c2b44f221415ffdace03095abfa42df70708726c2069e5c36eddae0400be29452c084bc27eb6a17eac9dbe182c204eb15311f455d824b656dbe4dc2240912d7586fe88951d01a8feb5ae5a4260535df83431052422468c36e22c2a5ef994d61dd7306ae4c9f6951ba3c12f1d1914ddc61f1a62da2df827f603fea5603b2c540dbd7c019c36bab29a4271c117df523cdbc5f3817a49e0efa60cbd7f74177e7a4f193d43f4220772666e4c4d83e1bd5a86087cf34f2dec21e245ca6c2bb016e683638050d2c430eea7c26a1c49d3760a58ab7f1a82cc938b4831384324bd0401fa12163a50570e684d318201ca308201c60201013081a2308194310b3009060355040613025553311330110603550408130a43616c69666f726e6961311630140603550407130d4d6f756e7461696e20566965773110300e060355040a1307416e64726f69643110300e060355040b1307416e64726f69643110300e06035504031307416e64726f69643122302006092a864886f70d0109011613616e64726f696440616e64726f69642e636f6d020900936eacbe07f201df300906052b0e03021a0500300d06092a864886f70d01010105000482010099e456c0ecdb178abe470462040e5c0752f6fba4d888dcd95ab39b3a72c3a42d7627824d4ffea8830c3ad32c2739cb485826c4dbb4072c13013c23f05a2d3c5e213336be8e72eb33f452a3a96f7af9fa7233bc92af0bc2d5b9d521661d509c0e693e603cbdac5e58c00a01a27e05bdb6cec80fc9a8ce3de22ae1104f6308be8e06f7f9f00133c2738d8c268983da3b33c13efcd163aceb53656826f0b87b58059c0a383cb1651e00d4e90b354429789fbfbfc80f1824b90d249f0dc308f5f841a53d8d9b28b84712c4a4c0bffe2f40c111f237f1dddd0ac52f13178fc65c357cc4c8b033c3d44dffbf906d37cb827053017b99ffb696f15f8afd6e9519129cbf
[ 9.515704] I:failed to verify against RSA key 0
[ 9.515721] I:SHA-256 digest: 0af57a569628abf43e0cb2ba4316da9a0fb47150217255413d0574d3a10dafc6
[ 9.515729] E:failed to verify whole-file signature
[ 9.535726] Update package verification took 9.1 s (result 1).
[ 9.563312] E:Signature verification failed
[ 9.577467] E:error: 21
This is the log from a succesful update with the original update.zip:
Spoiler: Log
[ 0.350442] Finding update package...
[ 0.393154] I:Update location: @/cache/recovery/block.map
[ 0.393354] Opening update package...
[ 0.413638] I:mmapped 2 ranges
[ 0.414972] I:1 key(s) loaded from /system/etc/security/otacerts.zip
[ 0.414988] Verifying update package...
[ 0.436744] I:comment is 1578 bytes; signature is 1560 bytes from end
[ 9.442515] I:signature (offset: 71e1be37, length: 612): 3082060e06092a864886f70d010702a08205ff308205fb020101310f300d06096086480165030402010500300b06092a864886f70d010701a0820403308203ff308202e7a003020102020900e98c7b3de8706cb3300d06092a864886f70d01010b0500308195310b300906035504061302434e3112301006035504080c094775616e67446f6e673116301406035504070c0d5368656e5a68656e2056696577310b3009060355040a0c0251463111300f060355040b0c0852657365617263683114301206035504030c0b6c69756875616c69616e673124302206092a864886f70d01090116157169616e66656e67407169616e66656e672e636f6d301e170d3232303130383038333635325a170d3439303532363038333635325a308195310b300906035504061302434e3112301006035504080c094775616e67446f6e673116301406035504070c0d5368656e5a68656e2056696577310b3009060355040a0c0251463111300f060355040b0c0852657365617263683114301206035504030c0b6c69756875616c69616e673124302206092a864886f70d01090116157169616e66656e67407169616e66656e672e636f6d30820122300d06092a864886f70d01010105000382010f003082010a0282010100b29877a044433c5e55eef1d900b4ff257e7fc54ab7a4c7914837af0765f35c3db4f8de39831b9c76304f365f4537f5aec31f3ccf83f8744bcfcf9be4c40fe92e36edf4a0d50799e07cd3a3dfb17ce13e970de7b2d57aa1a5bc4109fe800c3f97976e077387a99cfa57a0f0252fa0fa4ef5203e098dbaf600fa5ded6e35eba8c2150ad858daf29dda5064ca881d46a2a20492258c4f20d26615f618aa334404a5198c4440292f751553eceb7cb3f0b4b7e4ddba4891f0ebfc1a7894f692300d1575ef4367f8508a24e72b6aaccd0dea8dbefb54e2b48658f939988a8bf117e3fa12d18971d48c8bcad9f80aa215602bd8dfc53946e320e32dbef09fe278a9bdbd0203010001a350304e301d0603551d0e04160414d9c898e436cc674380bf1eb3325629d87cd4eb81301f0603551d23041830168014d9c898e436cc674380bf1eb3325629d87cd4eb81300c0603551d13040530030101ff300d06092a864886f70d01010b0500038201010036bcd486a789ae6ab4d7166e50cfadcdcf6a0232e329f0b5117bda3f4ebd1b8e6d3fa7f37f7e25cdc830816b95b05b59f47c4db469af6741c0081e21f0033f74869bb2a34cac9364942cb8f7b0759f9b007aed92a655eb00fb1ba0bfa3ed663d80346417a4a96f56068d972e07fba6daee389bdbab0e46b88e9026eddce3c50dfb8f47a2f0604ebb4d0f8abe67673476303e3a4693a0db5ca1081c8c1179330cca5b01c7be0fd431bfa292ca9b6e1f56e6eea8a4aba1d43c71973b43bb82d9bff36d38413a45ae731286ba02aabe14cf5c0437b155b287d1623045df6cef6652347a252af4719b50da4b3d11ab7241c2a4b876043158c159271b5322c5a5eef9318201cf308201cb0201013081a3308195310b300906035504061302434e3112301006035504080c094775616e67446f6e673116301406035504070c0d5368656e5a68656e2056696577310b3009060355040a0c0251463111300f060355040b0c0852657365617263683114301206035504030c0b6c69756875616c69616e673124302206092a864886f70d01090116157169616e66656e67407169616e66656e672e636f6d020900e98c7b3de8706cb3300d06096086480165030402010500300d06092a864886f70d010101050004820100339e68dcbca8358da77d66f3431891c68e0600dbf95f0f609b7c3c1de7df356103c9fb3b1cda8596bd247339cef1c51abc912189bd662f8b79cfc46933b388f5a8d3e3216a89acd7cc09a9b5567547027eb7c75e63216ea4a9b1a72acdac49ca52c11461016ec275a551cda67944cb6de3d5274fccd33f21794181a22bfb1d58cc603f61603e416c9da99b8aae015d9747ee3a9265709e5236601ff0bd981cefb03f538ace162e10721d1bfbc2716c94b28e2f42b0ef9472f188929c7b4fa8625e7b1a4df35d267b6706f62d66ec0d55a2b7db8049065871720ba4ff0d98d829c09ecac2d4533d187f22f4523bddddf344f4524e1c57f447f44516c1d4a8b00d
[ 9.442825] I:whole-file signature verified against RSA key 0
[ 9.442863] Update package verification took 9.0 s (result 0).
[ 9.448867] I:Verifying package compatibility...
[ 9.466881] Installing update...
I also replaced the releasekey.x509.pem inside /system/etc/security/otacerts.zip with the testkey certificat from the signapkv2 folder. But that did not work too.
Any ideas how i can update my device with the modified update.zip?
Cheers
blue_one

Thread closed!
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com

Related

how do i debug (system ui crash, stopped)

hi everyone, i'm trying to mod some apk's (systemui and frameworkres)
i get no errors in apktool but when i flash the apk's in cwm, i get systemui has stopped and i have no ui.
i wipe cache and wipe cache partion with no help.
i'm trying to get a logcat but it's pretty much empty, one message about about heapsize.
so my question is whats the best way to find the cause of the errors?
Thanks
my logcat
Code:
--------- beginning of /dev/log/main
[ 05-12 09:25:40.243 4361: 4361 E/Trace ]
error opening trace file: No such file or directory (2)
[ 05-12 09:25:40.243 4361: 4361 D/ActivityThread ]
setTargetHeapUtilization:0.25
[ 05-12 09:25:40.243 4361: 4361 D/ActivityThread ]
setTargetHeapIdealFree:8388608
[ 05-12 09:25:40.243 4361: 4361 D/ActivityThread ]
setTargetHeapConcurrentStart:2097152
any help would be much appreciated.

[Q] Help - Cyanogen Nightly won't flash in CWM

Hey! So last little while I have been unable to properly flash the Cyanogen Rom's. I have no idea what the issue is. I manually go into Recovery Mode, CWM and when I go to flash I am getting the following errors...
-- Installing: /storage/sdcard0/Download/cm-11-20140625-NIGHTLY-ville.zip
Finding update package...
I:Update location: /storage/sdcard0/Download/cm-11-20140625-NIGHTLY-ville.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...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
about to run program [/tmp/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 11
run_program: child exited with status 127
unmount of /system failed; no such volume
error: make_ext4fs: open: No such file or directory
longjmp botch.
E:Error in /storage/sdcard0/Download/cm-11-20140625-NIGHTLY-ville.zip
(Status 0)
Installation aborted.
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.1/mmc_host/mmc0
Click to expand...
Click to collapse
I can't figure out what is up. I am just doing what the instructions have said, but ever since installing the current version I am on, 11-20140505-SNAPSHOT-M6-ville, I have been unable to install nightlies through the Cyanogen updater, and also through CWM manually.
Can anyone help me out??
RESOLVED: Issue was needed to update CWM for Cyanogen,
Beginning with nightly 20140501 (and eventually Milestone7), an updated recovery that has kernel support for by-name partitions is required to install/update CyanogenMod on this device. The following devices are affected:
evita - HTC One XL
fireball - HTC Droid Incredible 4G LTE
jewel - HTC EVO 4G LTE
m4 - HTC One Mini
m7 - HTC One [GSM]
m7spr - HTC One [Sprint]
m7vzw - HTC One [Verizon]
ville - HTC One S
Click to expand...
Click to collapse

[Q] No longer able to get Custom Rom (Cyanogen) to install in CWM

So I've been dealing with a rather unstable ROM for the past little while and have been struggling to install the newest nightly or stable build through CWM.
For some reason I am getting an error, and while at first I thought it was a bad .zip, or the location of it on my device - it has turned out to be a problem regardless of my many attempts to troubleshoot those possibilities. I have tried to toggle verification on/off, I have wiped all the data/cache/dalvik.. nothing is doing the trick.
Here's a dump of the log.
Code:
-- Installing: /storage/sdcard0/Download/cm-11-20140625-NIGHTLY-ville.zip
Finding update package...
I:Update location: /storage/sdcard0/Download/cm-11-20140625-NIGHTLY-ville.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...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
about to run program [/tmp/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 11
run_program: child exited with status 127
unmount of /system failed; no such volume
error: make_ext4fs: open: No such file or directory
longjmp botch.
E:Error in /storage/sdcard0/Download/cm-11-20140625-NIGHTLY-ville.zip
(Status 0)
Installation aborted.
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.1/mmc_host/mmc0
I searched around for some of those log descriptions and also haven't come across many solutions. I have an HTC One S if that matters, but I think the problem is general enough that device is not the issue.
I had been able to flash a rom before with no issue, I went from a nightly Cyanogen to a Stable which ironically was much more buggier.
I am hoping that there is something I can do to resolve this that doesn't rely on me having to use a PC - since I am at work without my personal computer and I have all the files on my phone at the moment along with access to the file manager.
Thanks in advance!
RESOLVED: Issue was needed to update CWM for Cyanogen,
Beginning with nightly 20140501 (and eventually Milestone7), an updated recovery that has kernel support for by-name partitions is required to install/update CyanogenMod on this device. The following devices are affected:
evita - HTC One XL
fireball - HTC Droid Incredible 4G LTE
jewel - HTC EVO 4G LTE
m4 - HTC One Mini
m7 - HTC One [GSM]
m7spr - HTC One [Sprint]
m7vzw - HTC One [Verizon]
ville - HTC One S
Click to expand...
Click to collapse

[Q] ADB Install apk Failed

hello try to install an apk with adb
Is there any way to avoid this Failure [ INSTALL_PARSE_FAILED_NO_CERTIFICATES ]

Help unable to install AT&T GS8+ Beta 2

Please help I have installed December security update, don't know if this is the cause. I am also using an 8GB older microsd as I do not normally use a sd card(64gb is enough for me). I am using beta 2 because that is the only thing I can find for AT&T. Here is what I get:
Manual Mode v1.0.0#
-- Appling Multi-CSC...
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
Applied the CSC-code : ATT
Successfully applied multi-CSC
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
--Deleting RSU selective file
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
Successfully verified for dmverity hash tree
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
--Install /sdcard/update.zip ...
Finding update package...
Opening update package...
erifying update package...
Update package verification took 87.1 s (result 2)
mount: failed to mount /dev/block/by-name/system at /system: Permission Denied
E3001: Package expects build fingerprint of samsung/dream2qltesq/dream2qltesq: 7.0/NRD90M/G955U1AQGL:user/release-keys or samsung/dream2qltesq/dream2qltesq:8.0.0/OPR1.170623.026/G955USQU1ZQK1 user/release-keys; this device has samsung/dream2qltesq:7.0/NRD90M/G955USQSBQL1 :user/release-keys.
E:Error in /sideload/package.zip
(Status 7)
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
Successfully verify for dmverity hash tree
Installation aborted.#1
Please help, let me know if this post is in violation of rules. I am new here.
E3001: Package expects build fingerprint of samsung/dream2qltesq/dream2qltesq: 7.0/NRD90M/G955U1AQGL:user/release-keys
Your MUST be on AQGL firmware for it to flash, you are on BQL1
I'm on G955U1UES2AQL1 CAN'T FLASH ANY AP FILE IN ODIN JUST EVERYTHING ELSE WHEN I USE THE UPDATE ZIP IN STOCK RECOVERY I GET THE SAME ERROR 7 . I THINK I'LL WAIT TIL THE OFFICIAL OREO TRYING TO GET THE BETA ON MY PHONE CONSUMED TOO MUCH OF MY TIME.
Sent from my [device_name] using XDA-Developers Legacy app

Categories

Resources