I installed this rom:
http://forum.xda-developers.com/showthread.php?t=2596176
140303 release version. I can`t update with the 090310 ota release. Safestrap indicates:
error in file_contexts. Unexpected contents.
I don't modified this file. ¿Can i fix this problem or must format the phone..Again:crying:?
Thx for helping
Related
Hi folks,
And thank you for the wonderful forum
I’m an owner of a Toshiba machine as you all know the software installed is far away from good, so I tried to update with your (MOD image) however unfortunately I’m getting the error below after every attempted following your steps. Any idea
E can’t mount DEFAULT_PATH
Finding update package…
Opening update package…
Verifying update package
E: signature verification failed
Installation aborted
Formation Misc
Installing form sdcard
Finding update package…
Opening update package…
Verifying update package
E: signature verification failed
Installation aborted
Formation
After that only sign (!) showing so I have to restart my machine
Either your update.zip is corrupted or you have the latest recovery installed -> http://forum.xda-developers.com/showthread.php?p=12518067#post12518067
thank you
thank you i will try that
your problem "E: signature verification failed " is your recovery which uses signed update.zip from toshiba only..
see my FolioMod post #1 and follow link to recover a working recovery, that do not use signed update.zip.
update
Which is better?Folio mod 1.4 or folioblur 1.1?Or what is the difference betwen the two mod? I've a Huawei E169 3g modem is will be working with the 3g modem update or tried to buy Vodafone K3565 / Huawei E160 modem?
I have rooted the device some time ago and now the lollipop update finally arrived.
I've used the original system all time long but when i try to update i get error, finally i've tried a sideload update and i can see the error. Now my problem is with this error:
Package expects build fingerprint of motorola/condor-retde/condor_umts:4.4.4/KXC21.5-40/46:user/release-keys or motorola/condor-retde/condor_umts:5.1/LPC23.13-34.8/10:user/release-keys this device has motorola/condor-retaildsds/condor_umtsds:4.4.4/KXC21.
Instalation aborted.
Now i believe i understand why i get this error, but my question is how to make it work. And what's the best method, by modifying the current software or by modifying the update.zip
PS. I'm an sysadmin not an android developer so please keep it simple.
Hi. My Moto E is giving me the same error as yours. Using Team Win Recovery Project, it says:
"Installing '/cache/Blur_Version.21.12.40.condor_retla_ds.retla.en.01.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Package expects build fingerprint of motorola/condor_retla_ds/condor_umtsds:4.4.4/KXC21.5-40/47:user/release-keys or motorola/condor_retla_ds/condor_umtsds:5.1/LPC23.13-34.8/9:user/release-keys; this device has Motorola/omni_condor/condor:4.4.2/KOT49H/eng.bigbiff.20140616.171951:eng/test-keys.
E:Error executing updater binary in zip '/cache/Blur_Version.21.12.40.condor_retla_ds.retla.en.01.zip'
Error flashing zip '/cache/Blur_Version.21.12.40.condor_retla_ds.retla.en.01.zip'
Updating partition details..."
Thanks!
I have an ascend mate 2. I have unlocked the bootloader, installed TWRP 3.1.1 and have updated my bios via Huawei site and currently have Android 5.1. I have tried uploading CyanogenMod 13 and lineage 14. Both times I get error 7 when uploading. Does anyone have any suggestions?
Batk138 said:
I have an ascend mate 2. I have unlocked the bootloader, installed TWRP 3.1.1 and have updated my bios via Huawei site and currently have Android 5.1. I have tried uploading CyanogenMod 13 and lineage 14. Both times I get error 7 when uploading. Does anyone have any suggestions?
Click to expand...
Click to collapse
You may want to provide your detailed procedure so others could help.
Batk138 said:
I have an ascend mate 2. I have unlocked the bootloader, installed TWRP 3.1.1 and have updated my bios via Huawei site and currently have Android 5.1. I have tried uploading CyanogenMod 13 and lineage 14. Both times I get error 7 when uploading. Does anyone have any suggestions?
Click to expand...
Click to collapse
I am experiencing the same issue. I did the advance wipe from TWRP 3.1.1 and install lineage 14. It stucks and gave this error message "This package supports bootloader(s) MSM8226C00B322_BOOT; This device has bootloader unknown. ". I had B322 built and Android 5.1.1 Lollipop on my Huawei Ascent Mate 2. I read from other forum and even tried to modify the line "assert(getprop("ro.bootloader") == "MSM8226C00B322_BOOT" || abort("This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader " + getprop("ro.bootloader") + ".");" in the file updater-script under META-INF\com\google\android directory and still not working. Please help
I am getting the same error. Full wipe of the device except for internal storage as I do not currently have a microSD card inserted (it's being used in my new phone, an S7 edge). I bought a new microSD card and used that to restore the stock ROM.
Exact text, copied from recovery.log:
Code:
Installing zip file '/sdcard/Download/lineage-14.1-20170302-nightly-mt2-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader unknown.
This package supports bootloader(s): MSM8226C00B322_BOOT; this device has bootloader unknown.
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/sdcard/Download/lineage-14.1-20170302-nightly-mt2-signed.zip'
Edit: So, I just reinstalled the stock ROM, B322, with no problems. Then I flashed TWRP 3.1.0, again, with no problems.
But I keep getting error 7, and it keeps saying that "this device has bootloader unknown". What gives? I can't stand the ridiculously large UI elements of the stock ROM, so I'm not going back to that.
EDIT: Alright, so I think I fixed it. Simply remove the "asserts" line from update-script in the ROM zip that deals with the bootloader (leave the device line if you wish) and it should work.
I used the instructions in this thread.
I've got the "Your device is corrupt" message appear on my Swift 2. In the summer my wife had the same issue with hers and I fixed it by downloading the TOS163B Signed Recovery zip and applying update from SD card but it won't install on mine because it is older than the installed version. So I found TOS249H Signed Fastboot zip and I am getting a signature verification error.
What file do I need to fix this? I'm guessing a later Recovery zip file but I can't find it.
Thanks in Advance
hi..
recently i have flashed twrp recovery after that max m2 pie update recd, unfortunately after downloaded uodate its ending up error 7... is there any way to update to pie... some other post says i need to edit update.script but there is no "assert" line.... pls help me guys
Problem fixed... Just deleted first three lines in update script...