Database Develop

[Q] Assert failed whenever trying to flash zip

Im getting this error when trying to flash any zip files..
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"
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"
Click to expand...
Click to collapse
things i do before:
- flashing The Ultimatum ROM and edited the build.prop to change the density to 140..
- updating my recovery to CMW 6 and got these error..
what should i do??
please help..
EDIT :
Today it's getting worse, my phone is bootloop now, and i can't flash any zip files, so i can't use my phone at all...
so guys, how to fix it??
(yes, this is my first time posting a thread, sorry for my bad english and thank you for viewing)

What does the last line say it is usually something like status 7 or status x
Sent from my LG-D802 using xda app-developers app

lingarajug said:
What does the last line say it is usually something like status 7 or status x
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
yes, it says "Installer Error (Status 7)"

Maliivers said:
yes, it says "Installer Error (Status 7)"
Click to expand...
Click to collapse
2 options
1. Your sdcard is corrupted >>> back up your data and format it in fat32 file system (use an USB adapter e.g.)
2. The file downloaded is corrupted >>> try to download it again
I advise you to use CWM 5.0.2.6 Fixed insted of CWM 6.x... but... it should work too

Viper The Ripper said:
2 options
1. Your sdcard is corrupted >>> back up your data and format it in fat32 file system (use an USB adapter e.g.)
2. The file downloaded is corrupted >>> try to download it again
I advise you to use CWM 5.0.2.6 Fixed insted of CWM 6.x... but... it should work too
Click to expand...
Click to collapse
- already format my sdcard, still result in error
- already redownload, still error
i'm using CWM 6.0.4.6 and can't flash to CWM 5, because any zip files i flash will result in error.. (oh,except for aroma filemanager, but what can i do with that?)

edit updater.script from rom.zip meta inf folder.
its a problem wich happens on lots of devices.
simply remove the 1/3 first lines from assert and rezip the rom
Sent from my S500 using xda app-developers app

SpaceCaker said:
edit updater.script from rom.zip meta inf folder.
its a problem wich happens on lots of devices.
simply remove the 1/3 first lines from assert and rezip the rom
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
hmm.. it looked like advanced tips.. haha
but i'll try, will post the result later

SpaceCaker said:
edit updater.script from rom.zip meta inf folder.
its a problem wich happens on lots of devices.
simply remove the 1/3 first lines from assert and rezip the rom
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
WOAH, IT WORKED ! THANKS !
(just in case someone else face the same problem) so this is what i did:
edit updater.script in META-INF\com\google\android folder
it looked like this:
assert(getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/stl12", "0", "/system");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
blahblahblah...
Click to expand...
Click to collapse
just delete this line on any zip:
assert(getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830");
Click to expand...
Click to collapse
and you're done.
----------------------------------------------------------------------------------------------------
but, just for fulfill my curiosity, why this error can occur? i used the same zip file days ago and it worked just fine.

SpaceCaker said:
edit updater.script from rom.zip meta inf folder.
its a problem wich happens on lots of devices.
simply remove the 1/3 first lines from assert and rezip the rom
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Win!
Thanks, this worked a treat for me too. I'd installed the CWM 6.0.4.6 for the Gio so i could install KitKat and buggered up my phone, but this has fixed it.

[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.

TWRP: Prevent assertion error when flashing rom

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/)

Can't install Custom Rom over TWRP [Error 7]

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.