Hi,
I was working on a samsung galaxt ace, but when i tried to flash cyanogenmod, i got an error about the device name not being cooper. So i tried to flash with odin, but every time the odin flash fails because of some XEN storage error. Does anybody know anything about this? Afterwards all my data and everything is still there. I will update the thread later with exact error, but they kind of flash really quickly on the screen so i'll have to look fast .
when i flash through odin error is:
Can't access to '/system/csc/XEN/system'.
Click to expand...
Click to collapse
When i try to install Cyanogenmod "CM7.2-RC3-AA-BLACKHAWK-OC.zip" trough cwm i get:
Installing update...
assert failed: getprop("ro.product.device") == "cooper" | | getprop("ro.build.product") == "cooper" | | getprop("ro.product.board") == "cooper" | | getprop("ro.product.device") == "GT-S5830" | | getprop("ro.build.product") == "GT=S5830" | | getprop("ro.product.board") == "GT-S5830"
E:Error in /sdcard/CM7.2-RC3-AA-BLACKHAWK-OC.zip
(status 7)
Installation aborted
Click to expand...
Click to collapse
edit: Flashed CWM 5, and was able to flash CM7 with that, all errors solved now
Solved.
I can not install any current ROM, Lineage 14 - Viper OS - Ressurection 5.8.4, always gives the error 7 [Patching system unconditionally
E1001: Failed to update system image. ] currently use the RR 5.8.0 android 6.0, my cell phone is the Moto G2 LTE XT1078 (THEA) image of the event> https://imgur.com/a/jRZkT
Do you have the newest TWRP? https://dl.twrp.me/thea/
yes, I tested all versions, 3.1.1-0 to 3.0.0-0, they all gave the same error
pabli24 said:
Do you have the newest TWRP? https://dl.twrp.me/thea/
Click to expand...
Click to collapse
yes, I tested all versions, 3.1.1-0 to 3.0.0-0, they all gave the same error
Are you sure you are using one for thea? If not, then do get it from here (I am using it on my XT1072):
https://dl.twrp.me/thea/twrp-3.2.1-0-thea.img.html
Reboot to fastboot (shut down, then pwr+vol up for 5 seconds then release) and plug your phone to a PC with mfastboot.
then execute in a copy of mfastboot the following command:
mfastboot flash recovery twrp-3.2.1-0-thea.img
Click to expand...
Click to collapse
Now take your phone and choose "Normal Powerup", then interrupt the boot and get again to fastboot, this time choose "Recovery".
You should be booting TWRP right now.
Now wipe /cache, /data, /storage, dalvik and /system.
Now flash CyanogenMod/AOKP/Carbon/AOSPA/LineageOS or any other custom ROM (optional: flash GApps of the same Android version afterwards to get Google support)
Now wipe /cache, /data and dalvik
Finally, reboot to system.
Not working? Make sure your bootloader is unlocked. Still not working and unlocked? Flash the stock ROM and try again.
Fixed the 7 TWRP error problem on the
Moto G2 LTE XT1078?
I'm having the same problem, I did not find a solution
Same problem. Managed to unlock bootloader, flash recovery, cannot flash any rom due to error 7. Any ideas?
Gupalupa123 said:
I can not install any current ROM, Lineage 14 - Viper OS - Ressurection 5.8.4, always gives the error 7 [Patching system unconditionally
E1001: Failed to update system image. ] currently use the RR 5.8.0 android 6.0, my cell phone is the Moto G2 LTE XT1078 (THEA) image of the event> https://imgur.com/a/jRZkT
Click to expand...
Click to collapse
So, if you're still looking for a solution, I can give you one, but stupid... You need to download the TWRP backup for XT1068 and install it.
https://forum.xda-developers.com/moto-g-2014/general/moto-g-indian-xt1068-marshmellow-6-0-t3313148
Al least the phone will work, but you'll also face some problems like laggy auto-rotation (the picture will be upside down in landscape mode) and also you'll have 2 SIM cards (XT1072 has only one sim card slot)
That means we should ask someone to make a backup of stock firmware (or at least stable LineageOS firmware) and restore it with TWRP.
Please, if anyone still has this phone (XT1072) on stock or any other firmware which WORKS make a backup and upload it to the internet.
:good::good:IT WOULD BE REALLY COOL, BECAUSE A LOT OF PEOPLE HAVE THIS PHONE AND THEY CAN'T FLASH ANY ROM WITH ERROR 7!!!:good::good:
A photo of succesfully restored device:
https://photos.app.goo.gl/shNVhtpJP4x432Sm6
Thank you.
Possible solution for error 7
in my case for moto e i opened the flashable zip with winrar, go to meta-inf/com/google/android and opened update-script with notepad++ and delete the first lines, in my case i deleted these
assert(getprop("ro.product.device") == "titan" || getprop("ro.build.product") == "titan" || getprop("ro.product.device") == "titan_umts" || getprop("ro.build.product") == "titan_umts" || getprop("ro.product.device") == "titan_udstv" || getprop("ro.build.product") == "titan_udstv" || getprop("ro.product.device") == "titan_umtsds" || getprop("ro.build.product") == "titan_umtsds" || getprop("ro.product.device") == "titan_retaildsds" || getprop("ro.build.product") == "titan_retaildsds" || getprop("ro.product.device") == "XT1068" || getprop("ro.build.product") == "XT1068" || getprop("ro.product.device") == "XT1064" || getprop("ro.build.product") == "XT1064" || getprop("ro.product.device") == "XT1063" || getprop("ro.build.product") == "XT1063" || getprop("ro.product.device") == "XT1069" || getprop("ro.build.product") == "XT1069" || abort("E3004: This package is for device: titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "0x4882" || getprop("ro.bootloader") == "0x4883" || getprop("ro.bootloader") == "0x4886" || getprop("ro.bootloader") == "0x4887" || abort("This package supports bootloader(s): 0x4882, 0x4883, 0x4886, 0x4887; this device has bootloader " + getprop("ro.bootloader") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
and rom is actually flashing
GuestD0668 said:
in my case for moto e i opened the flashable zip with winrar, go to meta-inf/com/google/android and opened update-script with notepad++ and delete the first lines, in my case i deleted these
assert(getprop("ro.product.device") == "titan" || getprop("ro.build.product") == "titan" || getprop("ro.product.device") == "titan_umts" || getprop("ro.build.product") == "titan_umts" || getprop("ro.product.device") == "titan_udstv" || getprop("ro.build.product") == "titan_udstv" || getprop("ro.product.device") == "titan_umtsds" || getprop("ro.build.product") == "titan_umtsds" || getprop("ro.product.device") == "titan_retaildsds" || getprop("ro.build.product") == "titan_retaildsds" || getprop("ro.product.device") == "XT1068" || getprop("ro.build.product") == "XT1068" || getprop("ro.product.device") == "XT1064" || getprop("ro.build.product") == "XT1064" || getprop("ro.product.device") == "XT1063" || getprop("ro.build.product") == "XT1063" || getprop("ro.product.device") == "XT1069" || getprop("ro.build.product") == "XT1069" || abort("E3004: This package is for device: titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "0x4882" || getprop("ro.bootloader") == "0x4883" || getprop("ro.bootloader") == "0x4886" || getprop("ro.bootloader") == "0x4887" || abort("This package supports bootloader(s): 0x4882, 0x4883, 0x4886, 0x4887; this device has bootloader " + getprop("ro.bootloader") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
and rom is actually flashing
Click to expand...
Click to collapse
Nope. That's just not working for me...
P.S
I'm still waiting for a proper backup for XT1072 and it will help to restore this phone. So... Please, somebody make a backup!
Hi,
I've got a Z3 Compact with TWRP 3.0.1-2 on it. As far as I can see, this is the latest version.
In my build.prop, both ro.product.device and ro.build.product are set to z3c. However, the following line in an update-script still causes the flash to abort with an assertion error:
(getprop("ro.product.device") == "D5803" || getprop("ro.build.product") == "D5803" ||
getprop("ro.product.device") == "D5833" || getprop("ro.build.product") == "D5833" ||
getprop("ro.product.device") == "z3c" || getprop("ro.build.product") == "z3c" ||
getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries") || abort("E3004: This package is for "D5803,D5833,z3c,aries" devices
this is a "" + getprop("ro.product.device") + "".");
I also tried setting ro.product.device and ro.build.product manually via adb shell and setprop. getprop on the adb shell (when in TWRP) returns the correct values.
Of course, I can always unpack the ZIP, edit update-script, repack the ZIP and flash. But doing this every time is tedious and, of course, deleting the assertion somehow beats the purpose anyway. Is there a way to fix this? Does TWRP get the properties from anywhere else than /system/build.prop?
Blessings,
Christoph
Hey Christoph,
I had the same issue.
I just tried the TWRP version (3.2.1-0) of this post: https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113 (I only tried the Lineage one)
and it is working again. (I'am running Carbon 6.1)
(No more update-script editing \o/)
i am new to custom rom flashing and while flashing lineage OS to my redmi 4 (indian variant) it came up with this error. this package is for santoni deivces, this is a "" device. can someone help me with that? thanks
if are you definitely sure that you have redmi 4x device then unzip archive, find META-INF/com/google/android/updater-script, delete first string which contains ` "assert(getprop("ro.product.device") == "santoni" || getprop("ro.build.product") == "santoni" || abort("E3004: This package is for device: santoni; this device is " + getprop("ro.product.device") + ".");" `
ucollider said:
if are you definitely sure that you have redmi 4x device then unzip archive, find META-INF/com/google/android/updater-script, delete first string which contains ` "assert(getprop("ro.product.device") == "santoni" || getprop("ro.build.product") == "santoni" || abort("E3004: This package is for device: santoni; this device is " + getprop("ro.product.device") + ".");" `
Click to expand...
Click to collapse
can i just simply unzip the rom, do the modifications as told by you and then again simply zip it. Will the zip be flashable then?
Dcentvlogger said:
can i just simply unzip the rom, do the modifications as told by you and then again simply zip it. Will the zip be flashable then?
Click to expand...
Click to collapse
Of course, besides it just code prevention to make sure you had the exact firmware. Just remove those line if you sure your phone is redmi 4x (santoni), it's safe and it'll work like a charm.
Hey Guys,
i managed to root, unlock the bootloader and install the twrp recovery.
Now i have the problem that i can't install any custom rom.
This is the code:
E3004: This package is for "D5803,D5833,z3c,aries" devices
this is a "z3"
E: unknown command [log]
Installing zip file....
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/carbon-cr5.1.zip'
I also deleted the assert commando line in the updater-script file of the carbon rom.
Still doesn't work.
How can i install a custom rom?
Am i missing something?
TWRP-Version: 3.0.2.0
Android-Version: 6.0.1 Build-Number: 23.5.A.1.291
Thank you for your help
Now i erased the getprob lines in the update-script.
These are the lines i deleted:
(getprop("ro.product.device") == "D5803" || getprop("ro.build.product") == "D5803" ||
getprop("ro.product.device") == "D5833" || getprop("ro.build.product") == "D5833" ||
getprop("ro.product.device") == "z3c" || getprop("ro.build.product") == "z3c" ||
getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries") || abort("E3004: This package is for "D5803,D5833,z3c,aries" devices
this is a "" + getprop("ro.product.device") + "".");
Now i get this error:
Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file.
I have the same problem. Not sure what to do?
Edit: Updating TWRP solved my issue. (Went from 3.0.2 to This one)
Btw, if you are on Linux and fastboot is giving you an error, check "fastboot --version" to see which you are on. I was on 29.0.2 and had to do a system update to get 29.0.4 before I could install this ROM.