Heya,
I see that a lot of people are asking about the assert problems. This one:
Installing update...
assert failed: getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/FXP116-update-cm-9.0.0-RC0-nozomi-UNOFFICIAL-signed.zip
(Status 7)
Installtion aborted
If you get this error, the fix is really simple. The thing is different roms are defined to work on a "different" device, some on LT26i and others on nozomi (which are the same device).
The thing you need to do is go to your build.prop file (/system/build.prop) and edit these lines:
ro.device.product
ro.build.product
And simply replace the LT26i to nozomi (or nozomi to LT26i) as needed. Go back to recovery and flash the wanted zip without an error.
NOTE: I highly recommend to backup the build.prop so if you accidently mess is up you'll be fine.
That's it. Enjoy flashing stuff
Sent from my LT26i using XDA
MasterLinuxer said:
Heya,
I see that a lot of people are asking about the assert problems. This one:
Installing update...
assert failed: getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/FXP116-update-cm-9.0.0-RC0-nozomi-UNOFFICIAL-signed.zip
(Status 7)
Installtion aborted
If you get this error, the fix is really simple. The thing is different roms are defined to work on a "different" device, some on LT26i and others on nozomi (which are the same device).
The thing you need to do is go to your build.prop file (/system/build.prop) and edit these lines:
ro.device.product
ro.build.product
And simply replace the LT26i to nozomi (or nozomi to LT26i) as needed. Go back to recovery and flash the wanted zip without an error.
NOTE: I highly recommend to backup the build.prop so if you accidently mess is up you'll be fine.
That's it. Enjoy flashing stuff
Sent from my LT26i using XDA
Click to expand...
Click to collapse
there is no such lines as ""ro.device.product
ro.build.product"" or may i couldnt find it.can u be more specific ?
Search better there should be this line in the build prop, if really not try to add it
Sent from my Nokia 3310 using xda premium
problem
i get this:
Installing update...
assert failed: getprop("ro.product.device") == "st25i" || getprop("ro.build.product") == "st25i" || getprop("ro.product.device") == "st25a" || getprop("ro.build.product") == "st25a" || getprop("ro.product.device") == "kumquat" || getprop("ro.build.product") == "kumquat"
E:Error in /sdcard/FXP205-cm-9-20130201-UNOFFICIAL-kumquat.zip
(Status 7)
Installtion aborted
i modified build.prop with "st25i", "st25a" and "kumquat" and i get the same problem
what do i do?
yodanny said:
i get this:
Installing update...
assert failed: getprop("ro.product.device") == "st25i" || getprop("ro.build.product") == "st25i" || getprop("ro.product.device") == "st25a" || getprop("ro.build.product") == "st25a" || getprop("ro.product.device") == "kumquat" || getprop("ro.build.product") == "kumquat"
E:Error in /sdcard/FXP205-cm-9-20130201-UNOFFICIAL-kumquat.zip
(Status 7)
Installtion aborted
i modified build.prop with "st25i", "st25a" and "kumquat" and i get the same problem
what do i do?
Click to expand...
Click to collapse
Remove assert lines out of update script from the rom
Sent from my ST25i using xda app-developers app
thanks
thanks bro!
ir worked
---------- Post added at 08:46 PM ---------- Previous post was at 08:06 PM ----------
yeah...it worked but i think my phone is bricked. i'm not sure
after i installed the rom i tried to reboot in system but it just won't
when i press and hold the power button it just vibrates and the left led turns green for a fraction of a second. that's all it does.
can i do something to bring my st25i back to live?
yodanny said:
thanks bro!
ir worked
---------- Post added at 08:46 PM ---------- Previous post was at 08:06 PM ----------
yeah...it worked but i think my phone is bricked. i'm not sure
after i installed the rom i tried to reboot in system but it just won't
when i press and hold the power button it just vibrates and the left led turns green for a fraction of a second. that's all it does.
can i do something to bring my st25i back to live?
Click to expand...
Click to collapse
Use flashtool
Go to flash mode
And. Flash stpck rom
Sent from my ST25i using xda app-developers app
Or simply change this =>
Open your rom zip file, go here => META-INF > com > google > android > updater-script and delete this line =>
assert(getprop("ro.product.device") == "MT27i" || getprop("ro.build.product") == "MT27i" ||
getprop("ro.product.device") == "MT27a" || getprop("ro.build.product") == "MT27a" ||
getprop("ro.product.device") == "pepper" || getprop("ro.build.product") == "pepper");
and save it!!! if winrar says this file changed save it again!
here you go it has been installed
why this problem accrued?! sometimes the zip updater can open your build.prop so it won't make difference even change the build.prop. It's better to change source!
SpaceCaker said:
Use flashtool
Go to flash mode
And. Flash stpck rom
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
thanks, bro! it worked
dont panic
yodanny said:
thanks bro!
ir worked
---------- Post added at 08:46 PM ---------- Previous post was at 08:06 PM ----------
yeah...it worked but i think my phone is bricked. i'm not sure
after i installed the rom i tried to reboot in system but it just won't
when i press and hold the power button it just vibrates and the left led turns green for a fraction of a second. that's all it does.
can i do something to bring my st25i back to live?
Click to expand...
Click to collapse
There is a simple solution
use flashtool
take the latest firmware
connect ur phone in fastboot
flash the firmware
and ur phone will start automatically
all ur DATA IN SD CARD (INTERNAL) WILL BE SAFE
Had dis same problem with sony xperia tipo dual (ST21i2)
Have fun
---------- Post added at 04:21 AM ---------- Previous post was at 04:11 AM ----------
palash_6670 said:
there is no such lines as ""ro.device.product
ro.build.product"" or may i couldnt find it.can u be more specific ?
Click to expand...
Click to collapse
its there its in a section
its a bit down
go bit down
and find it
Related
I was rooted a while back with CM mod and something messed up and I had to go back to stock and unroot my device. For the longest time I couldn't re-root it but now I finally did. When trying to flash I come up with this long error.
assert failed: getprop("ro.product.device") == "asies" || getprop"ro.build.product") == "aries" || getprop("ro.product.device") == "fascinate" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.product.device") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500"
E:Error in /sdcard/teamhacksung_fascinatemtd-ota-eng.BUILD5.zip
(Status 7)
Installation aborted.
Now it doesn't matter which rom I flash, it does about the same thing. I flashed a recovery just to see if it'd work and it did. I currently now have 3.x and it's still doing the same thing. I read online and people said to revert to stock, but I already am at stock. And I just rooted it today. So I have no clue what this means. Any help would be much appreciated, thanks!
Maisum said:
I was rooted a while back with CM mod and something messed up and I had to go back to stock and unroot my device. For the longest time I couldn't re-root it but now I finally did. When trying to flash I come up with this long error.
assert failed: getprop("ro.product.device") == "asies" || getprop"ro.build.product") == "aries" || getprop("ro.product.device") == "fascinate" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.product.device") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500"
E:Error in /sdcard/teamhacksung_fascinatemtd-ota-eng.BUILD5.zip
(Status 7)
Installation aborted.
Now it doesn't matter which rom I flash, it does about the same thing. I flashed a recovery just to see if it'd work and it did. I currently now have 3.x and it's still doing the same thing. I read online and people said to revert to stock, but I already am at stock. And I just rooted it today. So I have no clue what this means. Any help would be much appreciated, thanks!
Click to expand...
Click to collapse
You need cwm4 there is a link to everything you need in droidstyle's guide. Due to being on the app I cannot post links. But its in general section. Hope that clears it up.
Sent from my SCH-I500 using XDA App
Wow that worked! Thanks a lot!
Maisum said:
Wow that worked! Thanks a lot!
Click to expand...
Click to collapse
Your welcome dude
Sent from my SCH-I500 using XDA App
Hi,
I just tried to install this rom on my i9100p (the one with NFC) but failed the initial test... looks like it can be installed only on plain 9100, 9100M and T but not P... why is that? i've read that apart from the NFC it's just the same (in fact i had no problem installing CWM and after that when the phone boots it says i9100)...
i tried to search for the piece of code that it show on the screen as an error, but unfortunately I couldn't find where it is... the error is:
assert failed: getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" || getprop("ro.product.device") == "i9100M" || getprop("ro.build.product") == "i9100M" || getprop("ro.product.device") == "i9100T" || getprop("ro.build.product") == "i9100T"
so it should be matter of adding a couple ORs and voila... or maybe is there a way to change my model name somewhere?
Mmm some info. here, maybe help http://forum.xda-developers.com/showthread.php?t=1465816
GaboWinter said:
Mmm some info. here, maybe help http://forum.xda-developers.com/showthread.php?t=1465816
Click to expand...
Click to collapse
wel thank you, it did help, cause i understood that i had to modify the updater-script!
but now i get another error it just says error in .zip and (status 6), before it was status 7...
but i'm not really sure if i'm doing it correctly... when i'm in recovery mode, i go to install zip from sdcard->choose zip from sdcard and then i choose update-cm-9...zip
instructions only say "flash cm9"...
i have rooted the phone with CWS and nothing else...
Hi guys! First of all, I just wanna say I'm a complete newbie in ROM Developement...
Today I ported a ROM based in this, and when I'm trying to install it by CWM, it gives me this error:
-- Installing: /sdcard/AOSPLite.zip
Finding update package...
Opening update package...
Installing update...
assert failed: !less_than_int(1334724946, getprop("ro.build.date.utc"))
E:Error in /sdcard/AOSPLite.zip (Status 7)
Installation aborted.
PS: I already read the FAQ in the link, but I think my build.prop is right...
Link: http://pastebin.com/WRtu7zeC
PSS: I have SE Live with Walkman(WT19i) with unlocked bootloader.
Wait, why is your flashable-zip checking the time information build.prop anyway?
Someguyfromhell said:
Wait, why is your flashable-zip checking the time information build.prop anyway?
Click to expand...
Click to collapse
Don't know... As I sad, I'm a newbie... :$
If it's what I think it is, then:
go to meta-inf> com> google> android and open the updater-script with notepad++. It has to be notepad++
remove the following lining
Code:
assert(getprop("ro.product.device") == "ST15i" || getprop("ro.build.product") == "ST15i" ||
getprop("ro.product.device") == "ST15a" || getprop("ro.build.product") == "ST15a" ||
getprop("ro.product.device") == "smultron" || getprop("ro.build.product") == "smultron");
device names may vary ofc
If I'm wrong, well I tried
iONEx said:
If it's what I think it is, then:
go to meta-inf> com> google> android and open the updater-script with notepad++. It has to be notepad++
remove the following lining
Code:
assert(getprop("ro.product.device") == "ST15i" || getprop("ro.build.product") == "ST15i" ||
getprop("ro.product.device") == "ST15a" || getprop("ro.build.product") == "ST15a" ||
getprop("ro.product.device") == "smultron" || getprop("ro.build.product") == "smultron");
device names may vary ofc
If I'm wrong, well I tried
Click to expand...
Click to collapse
It doesn't have to be Notepad++, editing can be done with regular Notepad also, at least that's what I do.
Also, his ported ROM checks ro.build.date.utc in build.prop.
To OP: Mind posting your update-script here from the flashable-zip?
Someguyfromhell said:
It doesn't have to be Notepad++, editing can be done with regular Notepad also, at least that's what I do.
Click to expand...
Click to collapse
actually when I edit with notepad, I get some error. Forgot the classification number though.
and on various texts about editing updater-script, it says to use notepad++
I'm not sure for what reasons though.
but, well. if you have no problems with notepad editing. I might be wrong.
EDiT:
In these threads it says to use notepad++ otherwise you'll get a status 6 error.
just search status 6 on xda search for more info...
http://forum.xda-developers.com/showthread.php?t=936175
http://forum.xda-developers.com/showthread.php?t=840446
Hello everyone,
I wanted to try the 4.2 camera app and I changed my build.prop to have Galaxy Nexus in the device name. I did backup the original build.prop but forgot to restore it., and I think it is causing me the Status 7 error.
What can I do now to finish the FXP151 installation? Should I try to restore a previous NAND? Thanks for your time.
Installing update...
assert failed : getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" || getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" || getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
E: error in /sdcard/FXP151-cm-10-20121214-UNOFFICIAL-haida.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Edit update script..delete the assert and its sublines
bluestricker_21 said:
Edit update script..delete the assert and its sublines
Click to expand...
Click to collapse
Many thanks for the swift reply, it worked. Another question if I may, the LED lights are now brighter/stronger, is this normal?
Konosuke said:
Many thanks for the swift reply, it worked. Another question if I may, the LED lights are now brighter/stronger, is this normal?
Click to expand...
Click to collapse
yup it is normal in cm10
Hi all
Serious problem with my mini st15i
I was running cm10 fxp 211 with mesa kernel v4.2
Yesterday everything magnified by 200% on the screen and I tried reflashing cm10
But my phone didn't allow me to.
Now I have tried 4 diff ROMs and have not been able to flash any.
This is the error message I get:
"Error updating zip file (status 7)" on TWRP recovery
Similar error on CWM
SOMEBODY PLEASE HELP!
Try this,
open the zip file in pc (don't extract)
navigate to META-INF>com>google>android>updator-script
try removing the first three lines using notepad++.
something like this
assert(getprop("ro.product.device") == "SK17i" || getprop("ro.build.product") == "SK17i" ||
getprop("ro.product.device") == "SK17a" || getprop("ro.build.product") == "SK17a" ||
getprop("ro.product.device") == "mango" || getprop("ro.build.product") == "mango");
f it still doesn't work, redownload the zip file, it will work
mnishamk said:
Try this,
open the zip file in pc (don't extract)
navigate to META-INF>com>google>android>updator-script
try removing the first three lines using notepad++.
something like this
assert(getprop("ro.product.device") == "SK17i" || getprop("ro.build.product") == "SK17i" ||
getprop("ro.product.device") == "SK17a" || getprop("ro.build.product") == "SK17a" ||
getprop("ro.product.device") == "mango" || getprop("ro.build.product") == "mango");
f it still doesn't work, redownload the zip file, it will work
Click to expand...
Click to collapse
Thank you!!!
You just revived my phone!:victory:
Wish I could hit thanks a few hundred times more!
please add [solved] to your thread title,
clcik edit on first post and go advanced and add [solved]