Develop Bugs

[Q] assert failed getprop ro.product.device

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.

[SOLVED] Unable to install custom ROMs on Xperia S

Hey guys I've an Xperia S. I've rooted it, installed CWM recovery on it, unlocked the bootloader, then wiped cache partition and dalvik cache and also the data but im getting this error everytime I try to install a custom ROM:
-- Installing: /sdcard/MIUIv5_3.3.29_nozomi.zip
Finding update package...
I:Update location: /sdcard/MIUIv5_3.3.29_nozomi.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" ||
getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" || getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" || getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" || getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/MIUIv5_3.3.29_nozomi.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/MIUIv5_3.3.29_nozomi.zip")
Dont know whats this 'status 7' is. Please help! I've tried many ROMs many times but none working.

just delete the error text on updater-script on android floder on your zip flashable rom
I have already had this error

Cht0in3 said:
just delete the error text on updater-script on android floder on your zip flashable rom
I have already had this error
Click to expand...
Click to collapse
I've accesed the updater-script. Now can you tell me which text to remove from there?

sirius_gamer said:
I've accesed the updater-script. Now can you tell me which text to remove from there?
Click to expand...
Click to collapse
Check this
http://forum.xda-developers.com/showthread.php?t=1607135
Sent from my LT26i using Tapatalk 2

sirius_gamer said:
I've accesed the updater-script. Now can you tell me which text to remove from there?
Click to expand...
Click to collapse
The first 2 lines generally that say about get prop
Or flash advanced stock kernel then try flash
Sent from my 4.2.2 Xperia S via Tapatalk

Ben36 said:
The first 2 lines generally that say about get prop
Or flash advanced stock kernel then try flash
Sent from my 4.2.2 Xperia S via Tapatalk
Click to expand...
Click to collapse
These are the updater-script of two different ROMs. Can you tell me exactly which lines to delete?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Anyone?
Sent from my LT26i using Tapatalk 2

sirius_gamer said:
Anyone?
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
I saw your post, but really don't know.
Never had that problems, have you tried to flash different kernel then ROM?
Or extract kernel from this and tried to flash with PC.
Sent from my LT26i using Tapatalk 2

sirius_gamer said:
Hey guys I've an Xperia S. I've rooted it, installed CWM recovery on it, unlocked the bootloader, then wiped cache partition and dalvik cache and also the data but im getting this error everytime I try to install a custom ROM:
-- Installing: /sdcard/MIUIv5_3.3.29_nozomi.zip
Finding update package...
I:Update location: /sdcard/MIUIv5_3.3.29_nozomi.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" ||
getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" || getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" || getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" || getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/MIUIv5_3.3.29_nozomi.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/MIUIv5_3.3.29_nozomi.zip")
Dont know whats this 'status 7' is. Please help! I've tried many ROMs many times but none working.
Click to expand...
Click to collapse
Check the md5 hash..
Redownload. Looks like a bad download to me..
Sent from The Beauty - Xperia S

-Harsh- said:
Check the md5 hash..
Redownload. Looks like a bad download to me..
Sent from The Beauty - Xperia S
Click to expand...
Click to collapse
You're right, we forgot md5.
I'm guessing he already tried different ROM's or download again that MIUI.
If not, then you know for the future.
Always check your downloaded file, that's the first thing you need to check.
Sent from my LT26i using Tapatalk 2

Maybe you should try to wipe everything, then flash new kernel, then the rom ( clean install ). Download the file again, to make sure they are proper!

or may check you build.prop file on the current rom to see if the asserted lines match those in updater-script

Did anyone had that kind of problem on MIUI 5 thread?
If no, then you doing something wrong.
If this ROM is made for XS, then it should work without editing any file (if should OP would said).
Re-download zip, check md5 or just flash other JB kernel then flash MIUI.
Sent from my LT26i using Tapatalk 2
---------- Post added at 09:50 AM ---------- Previous post was at 09:49 AM ----------
******
And please, write results.
You opened this thread and you should "close it".
Sent from my LT26i using Tapatalk 2

Nothing's working. If anyone can tell me how to convert a zip file to ftf then I can try flashing through Flashtool. I've also tried renaming the file from .zip to .ftf using Total Commander but Flashtool is giving error while preparing files. The only ROM that I've managed to flash successfully is this: http://forum.xda-developers.com/showthread.php?t=2102798 The one with build '6.1.A.2.55'

sirius_gamer said:
Nothing's working. If anyone can tell me how to convert a zip file to ftf then I can try flashing through Flashtool. I've also tried renaming the file from .zip to .ftf using Total Commander but Flashtool is giving error while preparing files. The only ROM that I've managed to flash successfully is this: http://forum.xda-developers.com/showthread.php?t=2102798 The one with build '6.1.A.2.55'
Click to expand...
Click to collapse
You cannot convert a zip into a ftf file. Only Sony can build .sin files

sirius_gamer said:
Nothing's working. If anyone can tell me how to convert a zip file to ftf then I can try flashing through Flashtool. I've also tried renaming the file from .zip to .ftf using Total Commander but Flashtool is giving error while preparing files. The only ROM that I've managed to flash successfully is this: http://forum.xda-developers.com/showthread.php?t=2102798 The one with build '6.1.A.2.55'
Click to expand...
Click to collapse
You can't do that, what could you do and I already said that.
Find different kernel and flash that or just extract boot.img and flash that via fast boot.
Command:
fastboot flash boot boot.img
Then flash ROM
Sent from my Xperia S using Tapatalk 2

funky0308 said:
You can't do that, what could you do and I already said that.
Find different kernel and flash that or just extract boot.img and flash that via fast boot.
Command:
fastboot flash boot boot.img
Then flash ROM
Sent from my Xperia S using Tapatalk 2
Click to expand...
Click to collapse
Problem solved! I was missing the step in which we have to flash boot.img Thanks alot bro :')

sirius_gamer said:
Problem solved! I was missing the step in which we have to flash boot.img Thanks alot bro :')
Click to expand...
Click to collapse
Sent from my Xperia S using Tapatalk 2

sirius_gamer said:
Hey guys I've an Xperia S. I've rooted it, installed CWM recovery on it, unlocked the bootloader, then wiped cache partition and dalvik cache and also the data but im getting this error everytime I try to install a custom ROM:
-- Installing: /sdcard/MIUIv5_3.3.29_nozomi.zip
Finding update package...
I:Update location: /sdcard/MIUIv5_3.3.29_nozomi.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" ||
getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" || getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" || getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" || getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/MIUIv5_3.3.29_nozomi.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/MIUIv5_3.3.29_nozomi.zip")
Dont know whats this 'status 7' is. Please help! I've tried many ROMs many times but none working.
Click to expand...
Click to collapse
Hello,You need to upgrade you cwm recovery.Then try to flash ok!

tania247260 said:
Hello,You need to upgrade you cwm recovery.Then try to flash ok!
Click to expand...
Click to collapse
Thanks but the problem has been solved already
Sent from my Xperia S using Tapatalk 2

[Q] How install PAC-MAN ROM error with assert build & device m7

Hi,
I'm trying to install PAC-MAN ROM on my mobile but i'm a little bit lost with build versions m7, m7att, m7spr, m7tmo, m7ul, m7vzw, m7wls. On my mobile informations with adb ro build project is :
ro.build.project=M7_UL_JB43_SENSE55_MR:338159
So i took the m7ul version. Wipe data/factory reset is okay bit when i flashing, I have an assert failed when he check two properties at the installation. But if i seach this two properties on my mobile information, they seem correct :
It fails at: assert(getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" ||
getprop("ro.product.device") == "m7ul" || getprop("ro.build.product") == "m7ul");
ro.product.device=m7
ro.build.product=m7
I don't know why it dosen't work.
ClockworkMod recovery v6.0.4.6
HBOOT-1.55.000
Here is a solution (sorry but i haven't 10 posts, i can't write an url on my question): androidgadgematic. com/2012/12/fix-custom-rom-installation-status-7.html
But before i want be sure that i must use m7ul version.

This is the HTC one X forum....not the ONE forum !!!

MarvelC incorrectly identifies as Marvel (Virgin Mobile USA)

OK, I'm very confused here.
I have a MarvelC. I know this because it's a Virgin Mobile phone and i just installed, successfully, cm-9.1.0-CRYPTOMILK-ALPHA9-marvelc.zip then cm-10.1-20130622-EXPERIMENTAL-marvelc-A0.zip
The strange part is, I had to edit the first line of
Code:
\META-INF\com\google\android\updater-script
from
Code:
assert(getprop("ro.product.device") == "marvelc" || getprop("ro.build.product") == "marvelc");
to
Code:
assert(getprop("ro.product.device") == "marvel" || getprop("ro.build.product") == "marvel");
Has anyone seen this or know how to fix it?
Thanks,
Peter

Bootloader Error while flashing LineageOS from Stock Nougat

I'm trying to flash LineageOS unofficial (actually i'm trying to flash LineageOS for MicroG it gives me same errors) with twrp but it tells me my bootloader (0xC113) isn't supported (only 0xC105, 0xC106, 0xC107 and 0xC112 are supported). It was suggested in this forum to flash nougat firmware, but I already have the latest nougat stock rom (7.1.1 security patch level 1. Nov Build number NPNS26.118-22-2-8). What should I do?

figured it out by myself. search in the zip for all files containing 0xC112 and replace them with 0xC113. here Are the files, line numbers and the line content to modify for lineageOS for Microg. Normal LineageOS may vary in Line numbers:
Code:
[B]META-INF/com/android/metadata[/B]:5:pre-bootloader=0xC105|0xC106|0xC107|[B]0xC112[/B]
[B]META-INF/com/google/android/updater-script[/B]:2:assert(getprop("ro.bootloader") == "0xC105" || getprop("ro.bootloader") == "0xC106" || getprop("ro.bootloader") == "0xC107" || getprop("ro.bootloader") == "[B]0xC112"[/B] || abort("This package supports bootloader(s): 0xC105, 0xC106, 0xC107, 0xC112; this device has bootloader " + getprop("ro.bootloader") + "."););
[B]system/build.prop[/B]:197:ro.build.expect.bootloader=0xC105|0xC106|0xC107|[B]0xC112[/B]

I followed this guide and worked for me .
https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91

tiago1966 said:
I followed this guide and worked for me .
https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91
Click to expand...
Click to collapse
Did you just flash the files from that build over the already installed NPNS26.118-22-2-8 build?

Mr_prfssnl said:
Did you just flash the files from that build over the already installed NPNS26.118-22-2-8 build?
Click to expand...
Click to collapse
Hello,
Yes, i did accoding to guide and was in the build mentioned for you.
Best regards,

Didn't work for me
mewn1 said:
figured it out by myself. search in the zip for all files containing 0xC112 and replace them with 0xC113. here Are the files, line numbers and the line content to modify for lineageOS for Microg. Normal LineageOS may vary in Line numbers:
Code:
[B]META-INF/com/android/metadata[/B]:5:pre-bootloader=0xC105|0xC106|0xC107|[B]0xC112[/B]
[B]META-INF/com/google/android/updater-script[/B]:2:assert(getprop("ro.bootloader") == "0xC105" || getprop("ro.bootloader") == "0xC106" || getprop("ro.bootloader") == "0xC107" || getprop("ro.bootloader") == "[B]0xC112"[/B] || abort("This package supports bootloader(s): 0xC105, 0xC106, 0xC107, 0xC112; this device has bootloader " + getprop("ro.bootloader") + "."););
[B]system/build.prop[/B]:197:ro.build.expect.bootloader=0xC105|0xC106|0xC107|[B]0xC112[/B]
Click to expand...
Click to collapse
I didt exactly that way. but it says - Invalid zip format ! -

yosoykarim said:
I didt exactly that way. but it says - Invalid zip format ! -
Click to expand...
Click to collapse
Upgrate to Oreo and try again, your firmware is outdated
Follow this guide: https://forum.xda-developers.com/mo...m-official-fastboot-stock-oreo-image-t3786537
Edit: Seems like the latest firmware link on that thread is down, instead download it from HERE and follow the instructions in the guide to flash