I have SE X Play with Doomkernel with android 2.3.4 and build no .42 and baseband version -56.
When i try to flash Darkforest RC2 rom via recovery i get following error.
asset failed: getprop ro. product. device
I have ClockWorkMod Recovery 5.0.2.6 installed
Please help me
YES I AM A NOOB
Either flash a stock rom first or open the .zip, find the update script and delete the get prop line
Sent from my R800i using Tapatalk
stock rom??
Sorry for stupid question but what exactly is a stock rom? I mean my play shipped with android 2.3.2, then i got 2.3.4 on OTA update.
So to install this rom i shoud go back to 2.3.2??
Also where to find stock roms for X play? I searched android dev forum but could only find latest firmwares.
Could you please provide a link for stock rom
Thanks in advance.
AndroHero said:
Either flash a stock rom first or open the .zip, find the update script and delete the get prop line
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
startherecca said:
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
Click to expand...
Click to collapse
I'm having the same problem on my r800x. Some help would be greatly appreciated!
I just recently unlocked my bootloader, and I can still flash kernels in fastboot. It's just that every time I try to install a custom rom I get either the Status 7 "getprop." error, or when I remove the .prop lines from the update script I get installation aborted. I also can not get into recovery from any of the custom kernels. I have had to boot into CWM using fastboot every time.
startherecca said:
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
Click to expand...
Click to collapse
What did you use to edit the update script? Try notepad+ if you use windows, the script has to be formatted for linux.
Sent from my R800i using Tapatalk
AndroHero said:
What did you use to edit the update script? Try notepad+ if you use windows, the script has to be formatted for linux.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Tried this, and it still doesn't work. Maybe I did it wrong? :/
PandaPropaganda said:
Tried this, and it still doesn't work. Maybe I did it wrong? :/
Click to expand...
Click to collapse
Just to clarify that I think he meant use notepad++ the + wasn't a typo. So don't use notepad but instead use notepad + +
Sent from my R800i using Tapatalk
fma965 said:
Just to clarify that I think he meant use notepad++ the + wasn't a typo. So don't use notepad but instead use notepad + +
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I know. Still doesn't work.
EDIT: I fixed it! Not only do you need notepad++, but you also have to EDIT the archive and not extract it then re-zip it. The archive software I had (PeaZip) wouldn't let me do this so I had to install 7zip. I'm uploading my edited update.zip for r800x's (based on fxp054) right now.
PandaPropaganda said:
I know. Still doesn't work.
EDIT: I fixed it! Not only do you need notepad++, but you also have to EDIT the archive and not extract it then re-zip it. The archive software I had (PeaZip) wouldn't let me do this so I had to install 7zip. I'm uploading my edited update.zip for r800x's (based on fxp054) right now.
Click to expand...
Click to collapse
um is this for a update.zip yh? i always extract them and repack them and it works fine. although this was on my old phone. are you sure you didn't do something different?
fma965 said:
um is this for a update.zip yh? i always extract them and repack them and it works fine. although this was on my old phone. are you sure you didn't do something different?
Click to expand...
Click to collapse
Sorry your right i did mean notepad++ there should be no issue unpacking the rom, as long as you repack it as a .zip, i use winrar and never had issues
Sent from my R800i using Tapatalk
AndroHero said:
Sorry your right i did mean notepad++ there should be no issue unpacking the rom, as long as you repack it as a .zip, i use winrar and never had issues
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
When I made .zip archives with PeaZip they never worked. I had also tried previously with the archiving utility IZArc to no avail. I installed 7zip and after making the .zip using that it fixed the problem. I'm just saying that may help for some who have has the same problems as me. Particularly with the r800x users. The .zip I put on my other post (and now this one --- in the reason for editing) has all the .prop lines removed from the update script and should work for anybody who has a r800x with an unlocked bootloader (providing you've installed the custom kernel, of course).
PandaPropaganda said:
When I made .zip archives with PeaZip they never worked. I had also tried previously with the archiving utility IZArc to no avail. I installed 7zip and after making the .zip using that it fixed the problem. I'm just saying that may help for some who have has the same problems as me. Particularly with the r800x users. The .zip I put on my other post (and now this one --- in the reason for editing) has all the .prop lines removed from the update script and should work for anybody who has a r800x with an unlocked bootloader (providing you've installed the custom kernel, of course).
Click to expand...
Click to collapse
Cool nice work
Sent from my R800i using Tapatalk
You can find the file in ./META-INF/com/google/android/updater-script
Thank you so much, you fixed my Galaxy Note with the simple deletion of a few lines.
startherecca said:
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
Click to expand...
Click to collapse
I am having the same issue on my Xperia Arc, where can i find the update script to remove the equivalent lines?
Thanks
Andrew
Do not do this!
I am not sure how other people are having success with this suggestion, but please do not do it. This code must be doing a proper check because I followed the advice and removed the assert. Next thing you know the installation proceeded and messed up. I hard bricked my phone. Yes hard brick, not a soft brick that you can recover from, the hard brick that makes your phone a brick. Just a warning.
startherecca said:
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
Click to expand...
Click to collapse
It searches for specific lines onto build.prop, but having that check after wiping /system, and so erasing your build.prop will result into an error. Deleting those lines in the updater-script will only let you skip that check, but there's no way to brick unless you flash a rom that wasn't meant for your phone or a different kernel.
Hi guys...
I was trying to install a new update (the cm7.2 fxp 116) but it failed and now my phone won't boot...
i've tried to install the fxp113 image and then apply that update, but I keep getting this message:
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" ||...
It continues to write a lot of these, all with == "LT18i" and "LT18a", but then a couple of lines down, it starts to write == "LT15i" instead...
Finally, it gives me an error saying "E:Error in /sdcard/A-IMAGES/cm72fxp113/update-cm-7.2.0-RC1-anzu-KANG-signed_fxp113.zip"
(status 7)
installation aborted
Please help me...
hjalte81 said:
Hi guys...
I was trying to install a new update (the cm7.2 fxp 116) but it failed and now my phone won't boot...
i've tried to install the fxp113 image and then apply that update, but I keep getting this message:
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" ||...
It continues to write a lot of these, all with == "LT18i" and "LT18a", but then a couple of lines down, it starts to write == "LT15i" instead...
Finally, it gives me an error saying "E:Error in /sdcard/A-IMAGES/cm72fxp113/update-cm-7.2.0-RC1-anzu-KANG-signed_fxp113.zip"
(status 7)
installation aborted
Please help me...
Click to expand...
Click to collapse
open the cm7.zip file, and go META-INF/com/Google/android/
and open update-script file with notepad++
delete the line
assert(getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" ||
getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" ||
getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" ||
getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" ||
getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu");
save and replace it
install with cwm
Sent from my Xperia Arc
Hi Kes,
The problem was that the file I had downloaded was corrupted :/
I restored from an older backup, downloaded the file again (and again...) and got a working file.
Thanks anyway
I've tried flashing with CWM and TWRP and I systematically get this error:
Installing '/external_sdcard/cm-10.2-20131119-NIGHTLY-n5100.zip'...
Checking for MD5 file...
I:Cannot find file /external_sdcard/cm-10.2-20131119-NIGHTLY-n5100.zip.md5
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
script aborted: assert failed: getprop("ro.product.device") == "kona3gxx" || getprop("ro.build.product") == "kona3gxx" ||
getprop("ro.product.device") == "n5100" || getprop("ro.build.product") == "n5100" ||
getprop("ro.product.device") == "GT-N5100" || getprop("ro.build.product") == "GT-N5100" ||
getprop("ro.product.device") == "kona3g" || getprop("ro.build.product") == "kona3g"
assert failed: getprop("ro.product.device") == "kona3gxx" || getprop("ro.build.product") == "kona3gxx" || getprop("ro.product.device") == "n5100" || getprop("ro.build.product") == "n5100" || getprop("ro.product.device") == "GT-N5100" || getprop("ro.build.product") == "GT-N5100" || getprop("ro.product.device") == "kona3g" || getprop("ro.build.product") == "kona3g"
E:Error executing updater binary in zip '/external_sdcard/cm-10.2-20131119-NIGHTLY-n5100.zip'
Error flashing zip '/external_sdcard/cm-10.2-20131119-NIGHTLY-n5100.zip'
Click to expand...
Click to collapse
Any help?
Solved.
I followed these steps: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/182438-solved-assert-failed.html
I basically deleted the assert lines from the rom and reflashed. Worked.
Guys any idea what this error is?
Start at : Sat Jan 4 13:36:05 2014
-- Checking model ID
script aborted: assert failed: getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru" || getprop("ro.product.board") == "endeavoru"
assert failed: getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru" || getprop("ro.product.board") == "endeavoru"
Installer Error (Status 7)
End at : Sat Jan 4 13:36:05 2014
Any time I try to flash anything through recovery I get that error and abort. I'm using Philz Recovery 6.17.9
Sent from my HTC One X using Tapatalk
Disregard this, sorry...It's due to the new recovery....reverting back to an older version fixed everything
Hi!
I just aquired a Samsung Galaxy S4 Mini GT-9195 this week and got stuck at installing CyanogenMod 12.1.
TWRP 2.8.7.0 samsunggalaxys4mini64bit is up and running.
Next i tried to install the official builds serranoltexx (first stable, then nightly) and i got this error message:
This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is serranoveltexx.
E: Error flashing zip 'cm-12.1-*.zip'
I'm not quite sure what is going on right now. Did the devs just forget to add this deviceName to their updater-script, or is there a reason for this?
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" || getprop("ro.product.device") == "serranoltebmc" || getprop("ro.build.product") == "serranoltebmc" || getprop("ro.product.device") == "serranoltektt" || getprop("ro.build.product") == "serranoltektt" || getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || abort("This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is " + getprop("ro.product.device") + ".");
If there's no chance or it's at least veary unlikle the smartphone gets damaged i'll just try to add this rule manually.
Any help appreciated
Nuke
Nukesor said:
Hi!
I just aquired a Samsung Galaxy S4 Mini GT-9195 this week and got stuck at installing CyanogenMod 12.1.
TWRP 2.8.7.0 samsunggalaxys4mini64bit is up and running.
Next i tried to install the official builds serranoltexx (first stable, then nightly) and i got this error message:
This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is serranoveltexx.
E: Error flashing zip 'cm-12.1-*.zip'
I'm not quite sure what is going on right now. Did the devs just forget to add this deviceName to their updater-script, or is there a reason for this?
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" || getprop("ro.product.device") == "serranoltebmc" || getprop("ro.build.product") == "serranoltebmc" || getprop("ro.product.device") == "serranoltektt" || getprop("ro.build.product") == "serranoltektt" || getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || abort("This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is " + getprop("ro.product.device") + ".");
If there's no chance or it's at least veary unlikle the smartphone gets damaged i'll just try to add this rule manually.
Any help appreciated
Nuke
Click to expand...
Click to collapse
Your phone is the new GT-I9195I ''serranoveltexx''
Currently, there is no custom ROMs for this device because of its different specs.
Please refer to this thread for more explanations : http://forum.xda-developers.com/galaxy-s4-mini/general/galaxy-s4-mini-plus-t3041208