Database Develop

[Q] Installation aborted - P990

Hi, i can't install the Slick 2x ROM (and the CM7 nightly builds) on my P990.
I got the newest Clockworkmod.
It says:
Installing update...
assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990" || getprop("ro.product.board") == "p990"
E: Error in /sdcard/cm_p990_full-13.zip
(Status 7)
Installation aborted.
Why?

Are you using Paul's old 3.0.1.4 recovery? If so update to 3.0.2.8 via ROM Manager.

I said i got the newest, its 3.0.2.8 i guess.

Don't guess, check
Just that it can cause what you're describing.

3.0.2.8-2x-clockworkmod
no wait i installed it yesterday but it shows 3.0.1.4 in the Recovery App wtf..
ok it's working now..

Help me please ^^
audioph1le said:
Hi, i can't install the Slick 2x ROM (and the CM7 nightly builds) on my P990.
I got the newest Clockworkmod.
It says:
Installing update...
assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990" || getprop("ro.product.board") == "p990"
E: Error in /sdcard/cm_p990_full-13.zip
(Status 7)
Installation aborted.
Why?
Click to expand...
Click to collapse
Hi everyone, Im new on this forum.
Im experiencing more or less the same problem.
Issues with Installing CM9 (ICS) Paranoid Andriod and WIUI v4 (ICS)
below a list of the phone's info/specs:
Phone: LG P990
Android Version: 2.3.4.
Basebandversion: 1035.21_20110725
Kernel version: 2.6.32.9
Build: GRJ23
LGE version: LGP990-V20r
I have rooted my phone using SuperOneClick v2.3.3.0, my phone was rooted succesfull, after that I gained superuser access to my phone. Checked it by downloading Root Checker Basic, which was also positive.
Downloaded Rom manager with CWM v5.0.2.0, made a recovery flash having the same version. I manually rebooted my phone, followed several
tutorials doing the full wipe, clearing cache partition and wiping Dalvik Cache. After that I selected 'choose zip from interal sdcard'
As soon as I select my zip the following happens:
-- Installing /emmc/ROM/WIUI_v4_S2_2_8_10.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /emmc/ROM/WIUI_v4_S2_2_8_10.zip
(status 0)
Installation aborted.
Someone please help me =(

[Q] Problems with Clockwork Mod Recovery on Gingerbread XWJVZ

Hi guys
i have a prety strange problem with clockwork mod recovery on a phone i was trieng to flash for a freind. INstalling zips on the recovery always fails. I tried diffrent versions of Cyanogenmod, none worked. Also the gapps packet fails.
I do get the following error message:
script aborted: assert failed: run_program("/tmp/updater.sh") == 0
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted.
What is the actualy strange thing about that problem is that i seam to have two diffrent recoverys. Starting the recovery over the buttos fails and if i start it through rom manager i sometimes end up on clockworkmod recovery and sometimes end up in samsungs galaxy s recovery
Let me tell you how I got to were I am now. I folowed the instruktion on Cyanogenmod but after flashig the root kernel over heimdall the phone was stuck in a bootloop. The recovery was gone but download mode was still working. So no real brick. After a while strugeling with odin, I was able to get back to stock rom with a Heimdall image. Thanks for those images aorth
After flashing a diffrent root kernel i did get root and was able to install ROM Manager and Clockwork Mod Recovery. But the recovery doesent realy work. I did uninstalled and reinstalled clockwork mod recovery and reied diffrent version of it, but nothing did help...
Anybody has an idea what went wrong and what i could do to fix it?

Hilmy said:
After flashing a diffrent root kernel i did get root and was able to install ROM Manager and Clockwork Mod Recovery. But the recovery doesent realy work. I did uninstalled and reinstalled clockwork mod recovery and reied diffrent version of it, but nothing did help...
Anybody has an idea what went wrong and what i could do to fix it?
Click to expand...
Click to collapse
flash a semaphore kernel for root and CWM from here http://forum.xda-developers.com/showthread.php?t=1112908

xsenman said:
flash a semaphore kernel for root and CWM from here http://forum.xda-developers.com/showthread.php?t=1112908
Click to expand...
Click to collapse
I did flash that kernel now, Flashing with Odin worked well, but after the reboot i was stuck in a bootloop again.
Is this Kernel maybe only compatible with a specific version of the original Samsung ROM? Or ist the a specific setting in Odin i have to use?

Hilmy said:
I did flash that kernel now, Flashing with Odin worked well, but after the reboot i was stuck in a bootloop again.
Is this Kernel maybe only compatible with a specific version of the original Samsung ROM? Or ist the a specific setting in Odin i have to use?
Click to expand...
Click to collapse
Semaphore and CF Root kernels have a specific ROM kernel, use solutions in My Android Solutions link below to resolve boot loop problems

xsenman said:
Semaphore and CF Root kernels have a specific ROM kernel, use solutions in My Android Solutions link below to resolve boot loop problems
Click to expand...
Click to collapse
Fixing the Bootloop problem isent realy a problem. Did that allot in the last days while tryeing difrent kernels
I did find a matching CF Root kernel now. No more boot loop but still two recoverys. The clockwork mod recovery, which can be enterd over the kernels CWM App, and the Android system recovery which apears when i boot to recovery over Rom Manager.....
I still cant install any ROMs over any of those recoverys. When i try over clockwork mod recovery I get an error and the process gets aborted. The error message looks like that again:
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does anybody know what that means and what i could do to fix it?
The full recovery log from clockwork mod recovery looks like that:
Starting recovery on Fri Sep 14 17:52:35 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v3.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 (null)
2 /system rfs /dev/block/stl9 (null)
3 /cache rfs /dev/block/stl11 (null)
4 /data rfs /dev/block/mmcblk0p2 (null)
5 /datadata rfs /dev/block/stl10 (null)
6 /boot bml boot (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Checking for ext4 partitions...
Checking /system...
Checking /data...
Checking /datadata...
Checking /cache...
Done!
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=herring
ro.revision=48
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWJVZ
ro.build.version.incremental=XWJVZ
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Fri Nov 25 16:47:47 KST 2011
ro.build.date.utc=1322207267
ro.build.type=user
ro.build.user=root
ro.build.host=DELL145
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=GT-I9000
ro.build.description=GT-I9000-user 2.3.6 GINGERBREAD XWJVZ release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.6/GINGERBREAD/XWJVZ:user/release-keys
ro.build.PDA=I9000XWJVZ
ro.build.hidden_ver=I9000XWJVZ
ro.build.changelist=762604
ro.flash.resolution=720
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
ro.opengles.version=131072
persist.service.usb.setting=0
ro.config.ringtone=01_Minimal_tone.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r8
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.secdevenc=true
ro.error.receiver.default=com.samsung.receiver.error
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=10
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientidbase=android-samsung
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
init.svc.setup_fs=stopped
init.svc.tvout=stopped
ro.radio.noril=yes
ro.bt.bdaddr_path=/efs/bluetooth/bt_addr
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.telephony.call_ring.multiple=0
ro.nfc.port=I2C
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/cm-9.1.0-galaxysmtd.zip
Finding update package...
I:Update location: /sdcard/cm-9.1.0-galaxysmtd.zip
Opening update package...
Installing update...
package_extract_file: no updater.sh in package
set_perm: chown of /tmp/updater.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/updater.sh to 777 failed: No such file or directory
about to run program [/tmp/updater.sh] with 1 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/updater.sh") == 0
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does anybody understand anythong in that log?

Hilmy said:
Does anybody understand anythong in that log?
Click to expand...
Click to collapse
Status 7 means you may have improper radio/spl requirements for CM 9, try to Flash JVU ROM + Root ( from My Androids Collection link below )
Do the wipes before flash, suggest you re download the CM 9 zip file, could be reason for update.sh getting 0

Thank for your help xsenman. Your collection of Galaxy S files is amazing :good:
xsenman said:
Status 7 means you may have improper radio/spl requirements for CM 9, try to Flash JVU ROM + Root ( from My Androids Collection link below )
Click to expand...
Click to collapse
I tried the JVU radio from your collection. But still the same error...
When i was googleing my problem i found something else that could be the problem. It was a post about an other phone, but it had the same error like i have. Im useing CWM 3.0.0.5 which isent realy the newest one. They said the problem could be fixed by installing a newer version of CWM. But since the recovery in my case is baked in to the Kernel, i dont seam to be able to update it. When i open the newer update.zip in the old version i can open it, but it doesent realy install. I still get the Status 7 error and not eaven wipes are working. When I do the diffrent wipes it says finished after a second, but when i rebot the system I still get in the non wiped system. And when i reebot to recovery im in CWM 3.0.0.5 again...
I googled, but i dident find a way to update a CWM recovery that was installed by flashing a root kernel. Do you maybe know how that could work?
Or doesent that make any sense at all?
xsenman said:
Do the wipes before flash, suggest you re download the CM 9 zip file, could be reason for update.sh getting 0
Click to expand...
Click to collapse
I did allot of factory resets, cache wipes and dalvik cashe wipes already. Felt like 100 times already
Does anyboday have any good ideas? Would realy like to return my friends phone back to him running a nice custom ROM, after all those months i was pushing him to give it a try :silly:

Hilmy said:
I googled, but i dident find a way to update a CWM recovery that was installed by flashing a root kernel. Do you maybe know how that could work?
Or doesent that make any sense at all?
Click to expand...
Click to collapse
That is the problem your recovery (CWM) needs to be changed (not the modem) , the JVU CF root kernel should have done the job (if you had flashed it) , since it did not, flash the semaphore kernel from here http://forum.xda-developers.com/showthread.php?t=1112908

The problem is soleved It was something i dident eaven know its possible...
Since it wasent my phone, i never tried running it with a simcard. Today i was about to give up and give the phone back to my freind with stockrom. But stockrom dident get a network connection. So i rememberd seeing something about a deleted IMEI Number in xsenmens Android Solutions. I cheked the IMEI and found out the phone doesent have one anymore. That was the problem couseing the Status 7 error in the recovery
Xenmen your Android Solutions are amazing. If you have any problems with your I9000 have a look here: http://forum.xda-developers.com/showthread.php?t=1841250
Thanks for your suport Xenmen and thanks for your Android Solutions :good:

I agree, I've not had to use any of them yet, but I did have a little browse and xsenman's guides look very well written and laid out. A lot of effort gone to there, well appreciated by many.
GT-I9000 / SEMA / SLIMBEAN2.3

Update hellybean
Hi Guys,
I try to update my firmware to jellybean 4.1.2 and i tryed also to update te hellybean
This is what i get on my screen.
assert failed: run_program("/tmp/updater.sh") == 0 assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/jellybean 4.1.2/cm-10.1-20121222-NIGHTLY-galaxysmtd.zip (Status 7)
Who can help me please for to update me samsung galaxy GT I9000 to hellybean

[Q] Why can't I install other ROMs than CM11?

Hello folks. Today I managed to S-OFF my HTC One using firewater on CyanogenMod 11 from April, but now I have a problem... I can't update to the newer CM11 nor install any other ROM because it gives me an error in TWRP. I tried installing ParanoidAndroid to see if it works but the same After this I tried to install MIUI 4.8.8 and it gave me this error in TWRP:
assert failed: getprop ("ro.product.device") ==
getprop ("ro.build.product") == "m7"
E:Error executing updater binary in zip
Error flashing zip '/sdcard/xiaomi.eu_multi_m7_
Updating partition details...
I don't know what to do... Can you please help me? :crying:
EDIT:
I flashed CWM instead of TWRP and it works like a charm :cyclops:

Stachura5 said:
Hello folks. Today I managed to S-OFF my HTC One using firewater on CyanogenMod 11 from April, but now I have a problem... I can't update to the newer CM11 nor install any other ROM because it gives me an error in TWRP. I tried installing ParanoidAndroid to see if it works but the same After this I tried to install MIUI 4.8.8 and it gave me this error in TWRP:
assert failed: getprop ("ro.product.device") ==
getprop ("ro.build.product") == "m7"
E:Error executing updater binary in zip
Error flashing zip '/sdcard/xiaomi.eu_multi_m7_
Updating partition details...
I don't know what to do... Can you please help me? :crying:
EDIT:
I flashed CWM instead of TWRP and it works like a charm :cyclops:
Click to expand...
Click to collapse
newer CM roms must be flashed with twrp 2.7.1.1 and other sense roms with 2.6.3.3

[Q] LT25i (XV) flashing error - "this is a mint"

Hi guys, please take a minute to help a fellow Sony fan out...
I managed to unlock bootloader via flashtool, root and install recovery as on istux's guide http://forum.xda-developers.com/showthread.php?t=2798411
But when I try to flash DirtyUnicorns_Unofficial_Tsubabsa_build2, it tells me..."This package is for LT25i Tsubasa devices; this is a mint."!
I don't know if this is related at all, but when I try to wipe the cache, it says "failed to unmount /cache"
Why does it think it is a "mint" (whatever that is) and how do I fix this?
From being stuck in recovery after wiping data, the only thing I can do is flash stock 4.3 FTF (9.2.A.2.5) again using flashtool. Is there a better way out of this?

swe.rider said:
Hi guys, please take a minute to help a fellow Sony fan out...
I managed to unlock bootloader via flashtool, root and install recovery as on istux's guide http://forum.xda-developers.com/showthread.php?t=2798411
But when I try to flash DirtyUnicorns_Unofficial_Tsubabsa_build2, it tells me..."This package is for LT25i Tsubasa devices; this is a mint."!
I don't know if this is related at all, but when I try to wipe the cache, it says "failed to unmount /cache"
Why does it think it is a "mint" (whatever that is) and how do I fix this?
From being stuck in recovery after wiping data, the only thing I can do is flash stock 4.3 FTF (9.2.A.2.5) again using flashtool. Is there a better way out of this?
Click to expand...
Click to collapse
If you're completely sure you're installing the correct ROM for your phone, then you need to use 7zip to open the ROM zip file (Open Archive) and navigate to "\META-INF\com\google\android\" and extract the "updater-script" file. Edit it with Notepad++ (or use Linux, do not use Windows notepad) and delete the first command:
Code:
assert(getprop("ro.product.device") == "lt29i" || getprop("ro.build.product") == "lt29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" ||
getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" || abort("This package is for \"lt29i,hayabusa,LT29i\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
The example above is from a ROM for a TX. Yours should similar.
The first line of the script should start with:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "/system");
Save the file and re-add it to the ROM zip file, replacing the previous updater-script, then you can connect your phone to your PC and use ADB to push the file back to the sdcard on the phone.
Also, if you only wiped /data, then you could just reboot, wait for Android to start up and copy the file normally. Then reboot back to recovery and reflash. On the other hand, if you wiped /system, ADB is your only option, unless you want to reflash a stock FTF.
I'm pretty sure this is because the command checks the phones build.prop to see if the device/product matches certain strings that identify your device, but apparently they don't always match.

Antiga Prime said:
If you're completely sure you're installing the correct ROM for your phone, then you need to use 7zip to open the ROM zip file (Open Archive) and navigate to "\META-INF\com\google\android\" and extract the "updater-script" file. Edit it with Notepad++ (or use Linux, do not use Windows notepad) and delete the first command:
Code:
assert(getprop("ro.product.device") == "lt29i" || getprop("ro.build.product") == "lt29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" ||
getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" || abort("This package is for \"lt29i,hayabusa,LT29i\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
The example above is from a ROM for a TX. Yours should similar.
The first line of the script should start with:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "/system");
Save the file and re-add it to the ROM zip file, replacing the previous updater-script, then you can connect your phone to your PC and use ADB to push the file back to the sdcard on the phone.
Also, if you only wiped /data, then you could just reboot, wait for Android to start up and copy the file normally. Then reboot back to recovery and reflash. On the other hand, if you wiped /system, ADB is your only option, unless you want to reflash a stock FTF.
I'm pretty sure this is because the command checks the phones build.prop to see if the device/product matches certain strings that identify your device, but apparently they don't always match.
Click to expand...
Click to collapse
Antiga, thank you very much, I actually succeeded by following your advice from post #10 here http://forum.xda-developers.com/showthread.php?t=2581336
I wiped everything but just restored a nandroid backup I made in recovery before wiping and that worked when i needed to copy different files after things went wrong with the flash.
Would there be any problem caused by not being able to unmount /cache during wiping?

swe.rider said:
Antiga, thank you very much, I actually succeeded by following your advice from post #10 here http://forum.xda-developers.com/showthread.php?t=2581336
I wiped everything but just restored a nandroid backup I made in recovery before wiping and that worked when i needed to copy different files after things went wrong with the flash.
Would there be any problem caused by not being able to unmount /cache during wiping?
Click to expand...
Click to collapse
You're welcome. It's happened to me before, never known why, but after flashing a different ROM you can always try wiping /cache again; it generally works.

[Q] Flashing CM11-M12 to my Sprint M7 fails

I'm tired of the 'System Update' notifications on my M7, so I finally decided to flash CM11 to it (CM Was all I used on my Samsung phones as the Samsung ROMs SUCK, but the HTC ROMs aren't horrible for stock).
I downloaded the 'm7spr' version of CM11 M12 and GApps, then transferred them to my M7 and rebooted to TWRP. When I tried to flash it, I got 'This Package is for device: m7wls, m7spr; this device is m7.'
I downloaded and was able to flash the 'm7' version of CM11 M12, but while it booted, it was not able to find the network, probably because the 'm7' build is for GSM phones and mine is a Sprint phone.
Any ideas why the phone shows 'm7' as phone type when it's a *Sprint* m7, or a way to override that check and flash the ROM?

SubnetMask said:
I'm tired of the 'System Update' notifications on my M7, so I finally decided to flash CM11 to it (CM Was all I used on my Samsung phones as the Samsung ROMs SUCK, but the HTC ROMs aren't horrible for stock).
I downloaded the 'm7spr' version of CM11 M12 and GApps, then transferred them to my M7 and rebooted to TWRP. When I tried to flash it, I got 'This Package is for device: m7wls, m7spr; this device is m7.'
I downloaded and was able to flash the 'm7' version of CM11 M12, but while it booted, it was not able to find the network, probably because the 'm7' build is for GSM phones and mine is a Sprint phone.
Any ideas why the phone shows 'm7' as phone type when it's a *Sprint* m7, or a way to override that check and flash the ROM?
Click to expand...
Click to collapse
Well I'm not a fan of Cyanogenmod roms. Not that I'm saying you shouldn't use it (each to there own and all that) but normally when I see issues like this I tend to first of all think it's a Rom issue.
Are you sure your version of TWRP is compatible with Cyanogen mod roms. Check the the CM11 m12 thread see what recovery and version is recommended.
If you found my posts helpful, no need to say thanks. There's a button for that

I installed the latest version of TWRP. I tried the unofficial CM12 ROM that I found floating around here and had the same thing.
Finally, after finding a post from someone on the CM forums that had the same issue (but never got an answer) that had a little info from the update script, I took a chance and added 'getprop("ro.build.product") == "m7spr" ||
getprop("ro.product.device") == "m7" ||' to the 'updater-script' file and zipped it back up. I was then able to flash the ROM and have a normally functioning phone.

SubnetMask said:
I installed the latest version of TWRP. I tried the unofficial CM12 ROM that I found floating around here and had the same thing.
Finally, after finding a post from someone on the CM forums that had the same issue (but never got an answer) that had a little info from the update script, I took a chance and added 'getprop("ro.build.product") == "m7spr" ||
getprop("ro.product.device") == "m7" ||' to the 'updater-script' file and zipped it back up. I was then able to flash the ROM and have a normally functioning phone.
Click to expand...
Click to collapse
I have the same issue, wish it would get fixed.

JudgeFutta said:
I have the same issue, wish it would get fixed.
Click to expand...
Click to collapse
Bump, I have the same issue as well. Do I need to update the script as described above?
Rl

krakora said:
Bump, I have the same issue as well. Do I need to update the script as described above?
Rl
Click to expand...
Click to collapse
If you edit it, you can get it to flash.

I'm also having trouble with this, can you post exactly what you changed? I am trying to flash from stock to the latest Sprint m7 nightly and get the same compatability message, that my phone is "m7" and that the rom is for "m7spr."
If I understand correctly, you went in and changed:
META-INF\com\google\android\updater-script <- is that the right location?
Here is what I see when I open that up in notepad:
assert(getprop("ro.product.device") == "m7wls" || getprop("ro.build.product") == "m7wls" || getprop("ro.product.device") == "m7spr" || getprop("ro.build.product") == "m7spr" || abort("This package is for device: m7wls,m7spr; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", "");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
Click to expand...
Click to collapse
So something in those top lines needs to change. I tried setting them all to m7 but that didn't work. Which ones did you change exactly?

OK - updating to the latest version of TWRP fixes this issue.