Develop Bugs

[Q] Install MiUi for LT18i on LT15i

Hi y'all!
I'm trying to install Miui V4 for LT18i on my LT15i. Thing is I have upgraded it with Stock ICS so it is already recognized as LT18i, and if I look at build.prop it says LT18i.
When trying to install I get error messages in CWM.
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i"
What to do??

just replace LT18I with LT15I with any text editor manually before insalling .... and try to flash it maybe it works

hemo1001 said:
just replace LT18I with LT15I with any text editor manually before insalling .... and try to flash it maybe it works
Click to expand...
Click to collapse
I don't see the benefit of doing that since my build.prop already says LT18i.

Is this development ?
Wrong thread, post in right section Q/A
Sent from my Xperia Arc using xda premium

chiefy009 said:
Is this development ?
Wrong thread, post in right section Q/A
Sent from my Xperia Arc using xda premium
Click to expand...
Click to collapse
Sorry, my bad. Thread can be deleted or just move it.

just replace the updater-script with the one I attached in MetaINF folder.. it will flash without probs..

jjdoctor said:
just replace the updater-script with the one I attached in MetaINF folder.. it will flash without probs..
Click to expand...
Click to collapse
Can't unpack file. Can you just tell me what to change in updater-script?

just post next time in QnA.. dont want to bump.. but zdzune has already posted a fix... cant u read whole post?
LT15i download: (files to replace over miui_LT18i_2.4.13_5104119657_4.0.zip before installation)
http://speedy.sh/h6VWm/updater-script
http://speedy.sh/nrzer/build.prop (EN + Mass Storage Enabled)

The Dev section is only for threads in which development is taking place - there is a Q&A section for asking questions in

jjdoctor said:
just post next time in QnA.. dont want to bump.. but zdzune has already posted a fix... cant u read whole post?
LT15i download: (files to replace over miui_LT18i_2.4.13_5104119657_4.0.zip before installation)
http://speedy.sh/h6VWm/updater-script
http://speedy.sh/nrzer/build.prop (EN + Mass Storage Enabled)
Click to expand...
Click to collapse
I have already tried that one, it only gives me installation aborted.
*Edit*
Problem solved.

K1ngLouie said:
I have already tried that one, it only gives me installation aborted.
*Edit*
Problem solved.
Click to expand...
Click to collapse
Could you tell me how you fixed the problem? I have the same issue. It would have been handy if you posted more information instead of just "problem solved", as your thread is the first one that google displays when googling for "miui lt15i failed".
Thanks in advance.

Hey guys, I'm totally new here.
Could someone please help me with choosing the right MIUI and kernel? Because last time I almost bricked my phone using wrong kernel. My phone is Sony xperia Arc (Lt15i) with 4.1.B.0.431 Firmware and I'm using ICS 4.0.4...
I will love you for giving me answers

K1ngLouie said:
Hi y'all!
I'm trying to install Miui V4 for LT18i on my LT15i. Thing is I have upgraded it with Stock ICS so it is already recognized as LT18i, and if I look at build.prop it says LT18i.
When trying to install I get error messages in CWM.
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i"
What to do??
Click to expand...
Click to collapse
Hi, this is the solution for your problem
http://miuiandroid.com/community/threads/guide-install-miui-on-locked-bootloader-lt18i-lt18a-lt15i-lt15a.17850/
Hope it solves the issue

No body interested to CM7? but it's possible !

so i tried to port CM7 with this guide
http://forum.xda-developers.com/showthread.php?t=1598713
using rebel ROM (thanks to bpear96 , sorry i didn't ask your permission because i want to try it first)
http://forum.xda-developers.com/showthread.php?t=1673875
and CM7 from galaxy S plus
http://forum.xda-developers.com/showthread.php?t=1639421 (credit to mazen912 )
but i don't know about editing updater-script
so i got error in installation
can somebody help me?
or maybe interested to port CM7 to our phone while we waiting for CM9 (even CM10) ?
PS: i'm not a dev, just want to try .... sorry for my bad english

montahchos said:
so i tried to port CM7 with this guide
http://forum.xda-developers.com/showthread.php?t=1598713
using rebel ROM (thanks to bpear96 , sorry i didn't ask your permission because i want to try it first)
http://forum.xda-developers.com/showthread.php?t=1673875
and CM7 from galaxy S plus
http://forum.xda-developers.com/showthread.php?t=1639421 (credit to mazen912 )
but i don't know about editing updater-script
so i got error in installation
can somebody help me?
or maybe interested to port CM7 to our phone while we waiting for CM9 (even CM10) ?
PS: i'm not a dev, just want to try .... sorry for my bad english
Click to expand...
Click to collapse
What exactly did you face in errors? It will definitely help if you can post the updater-script here.

mkcy said:
What exactly did you face in errors? It will definitely help if you can post the updater-script here.
Click to expand...
Click to collapse
some error about assert
here's updater script from rebel rom
https://docs.google.com/open?id=0BwdDVAt3R4SLZm9GcGVEZXpvb0E
and here from S+ CM7
https://docs.google.com/open?id=0BwdDVAt3R4SLNXFYUGxhblFOSjA

montahchos said:
some error about assert
here's updater script from rebel rom
https://docs.google.com/open?id=0BwdDVAt3R4SLZm9GcGVEZXpvb0E
and here from S+ CM7
https://docs.google.com/open?id=0BwdDVAt3R4SLNXFYUGxhblFOSjA
Click to expand...
Click to collapse
assert() in the CM7 script determines expressions and stop the installation if it returns false. In this case:
getprop("ro.product.device") == "ariesve" || getprop("ro.build.product") == "ariesve" || getprop("ro.product.board") == "ariesve" ||
getprop("ro.product.device") == "GT-I9001" || getprop("ro.build.product") == "GT-I9001" || getprop("ro.product.board") == "GT-I9001" ||
getprop("ro.product.device") == "GalaxySplus" || getprop("ro.build.product") == "GalaxySplus" || getprop("ro.product.board") == "GalaxySplus"
is the "asserted" condition. since our device is not galaxysplus it will not run. Simply delete the assert command and try again.

mkcy said:
assert() in the CM7 script determines expressions and stop the installation if it returns false. In this case:
getprop("ro.product.device") == "ariesve" || getprop("ro.build.product") == "ariesve" || getprop("ro.product.board") == "ariesve" ||
getprop("ro.product.device") == "GT-I9001" || getprop("ro.build.product") == "GT-I9001" || getprop("ro.product.board") == "GT-I9001" ||
getprop("ro.product.device") == "GalaxySplus" || getprop("ro.build.product") == "GalaxySplus" || getprop("ro.product.board") == "GalaxySplus"
is the "asserted" condition. since our device is not galaxysplus it will not run. Simply delete the assert command and try again.
Click to expand...
Click to collapse
okey i'll try

Updated : stuck in galaxy W logo
i think i can't make it
btw thanks for helping me

finger crossed.
Sent from my GT-I8150 using xda premium

I hope there will be an official or even unofficial CM7 for our Galaxy W.

just wondering how cyanogen team pick device that get their official support.
anyone have idea?

terifish said:
just wondering how cyanogen team pick device that get their official support.
anyone have idea?
Click to expand...
Click to collapse
for example device should be not listed as 'legacy and low activity' on xda

montahchos said:
Updated : stuck in galaxy W logo
i think i can't make it
btw thanks for helping me
Click to expand...
Click to collapse
i've tried this before, but have so many bugs..still trying to port cm7..
we need some dev from our forum to give some tutorial..

dimaka1256 said:
for example device should be not listed as 'legacy and low activity' on xda
Click to expand...
Click to collapse
Then, we must develop many rom that updated in a short period with a lot of beta tester
Sent from my GT-I8150

Honestly, I see many more users of W than some non-legacy devices in HK :O

I hope that we should have a cm 7 in our community..

Maybe I'll work on it when my pc will come back...xD It's broken :l

CM7 would be nice but to be honest wouldn't it be better if more devs concentrate in CM9 and others that use it as a base?

eventhough i think cm7 can expand our choice for custom rom, still i agree with "Just Another★Gamer". cm9 already exist for our device, so maybe it better for us to focus on developing it to be perfect

terifish said:
eventhough i think cm7 can expand our choice for custom rom, still i agree with "Just Another★Gamer". cm9 already exist for our device, so maybe it better for us to focus on developing it to be perfect
Click to expand...
Click to collapse
we're all know that our devs in cm9 works hard for the camera and kernel and other things for cm9..
but we still need cm7 for our device..it's not complete if we dont have that rom

sparta20 said:
Maybe I'll work on it when my pc will come back...xD It's broken :l
Click to expand...
Click to collapse
what have you done with it making it broken for so long?

dimaka1256 said:
what have you done with it making it broken for so long?
Click to expand...
Click to collapse
I've problems with some chip

I get this error whenever I try to install a new ROM!

HeyMates,
I've downloaded many ROM's from here and tried to install them via Clockwork Mod Recovery...but this error comes up whenever I try to flash a new ROM
Whats interesting is I'm already on a Custom ROM Wildchild 3..and now I cannot change and the error I'm getting is
Installing Update..
assert failed: getprop("ro.product.device") == "marvel ||getprop("ro.build.product") == "marvel"
E:Error in /sdcard/EnviROM_marvel_signed-05313-?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D
?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D?[D
?[D?[D?[D?[D?[D?[D?[D[CV4_marvel_signed_053013_195348.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Androider's help me out please!

iPriDvI said:
HeyMates,
I've downloaded many ROM's from here and tried to install them via Clockwork Mod Recovery...but this error comes up whenever I try to flash a new ROM
Whats interesting is I'm already on a Custom ROM Wildchild 3..and now I cannot change and the error I'm getting is
Androider's help me out please!
Click to expand...
Click to collapse
You have a ROM for a different model of WFS. Check if it's a marvel, marvelc or marvelct
Sent from my ST25i running 4.1.2

Strike_Riku said:
You have a ROM for a different model of WFS. Check if it's a marvel, marvelc or marvelct
Sent from my ST25i running 4.1.2
Click to expand...
Click to collapse
I assume my one's is "marvel" and not "marvelc" as I've already installed Wildchild 3.0 which was made for "Marvel"
Care to explain to find out my exact model?

See my post here and ur problem is solved
hit thanks http://forum.xda-developers.com/showthread.php?t=2180017
Sent from my Wildfire S A510e using Tapatalk 2

iPriDvI said:
HeyMates,
I've downloaded many ROM's from here and tried to install them via Clockwork Mod Recovery...but this error comes up whenever I try to flash a new ROM
Whats interesting is I'm already on a Custom ROM Wildchild 3..and now I cannot change and the error I'm getting is
Androider's help me out please!
Click to expand...
Click to collapse
if you are on windows then using winrar open your rom zip then naviate to META-INF -> com -> google ->android then open updater script with your editor , notepad or notepad++ , delete this line from top
Code:
assert(getprop("ro.product.device") == "marvel" || getprop("ro.build.product") == "marvel");
save the file and reflash rom , this will just basically bypass the checking the device model and flash the rom

cyb3r.pr3dat0r said:
if you are on windows then using winrar open your rom zip then naviate to META-INF -> com -> google ->android then open updater script with your editor , notepad or notepad++ , delete this line from top
Code:
assert(getprop("ro.product.device") == "marvel" || getprop("ro.build.product") == "marvel");
save the file and reflash rom , this will just basically bypass the checking the device model and flash the rom
Click to expand...
Click to collapse
Yeah..this one worked out..but there's one problem again..
I'm unable to install few ROM's using TWRP and some using CWM...why is it?
The trouble they are making is the bootscreen says there forever..
Any explaination to think of?

iPriDvI said:
Yeah..this one worked out..but there's one problem again..
I'm unable to install few ROM's using TWRP and some using CWM...why is it?
The trouble they are making is the bootscreen says there forever..
Any explaination to think of?
Click to expand...
Click to collapse
depends , you will have to give me logcat

cyb3r.pr3dat0r said:
depends , you will have to give me logcat
Click to expand...
Click to collapse
Sorry...what is logcat?Sorry if I'm dumb

iPriDvI said:
Sorry...what is logcat?Sorry if I'm dumb
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2141817
read

[Q] Slim Bean Install

I'm trying to install to Slim Bean and the installation is being aborted
assert failed:get(prop"ro.bootloader") == "1.28.0000" || get(prop"ro.bootloader") == "1.31.0000" || get(prop"ro.bootloader") == "1.33.0000" || get(prop"ro.bootloader") == "1.36.0000" || get(prop"ro.bootloader") == "1.39.0000"
(Status 7)
My device:
One X
HBoot: 1.73.0000
What to do with this?

1) Open the rom zip with an archiver, go to /META-INF/com/google/android/ and open updater-script using notepad or similar.
2) Edit the line checking the HBOOTs and add
Code:
|| getprop("ro.bootloader") == "1.73.0000")
Change 1.73.0000 to whatever your new HBOOT is. Make sure the ; is behind the part you've added.
3) Save the file and update it in the zip. You should be able to flash it now.

Mr Hofs said:
1) Open the rom zip with an archiver, go to /META-INF/com/google/android/ and open updater-script using notepad or similar.
2) Edit the line checking the HBOOTs and add
Code:
|| getprop("ro.bootloader") == "1.73.0000")
Change 1.73.0000 to whatever your new HBOOT is. Make sure the ; is behind the part you've added.
3) Save the file and update it in the zip. You should be able to flash it now.
Click to expand...
Click to collapse
my onex has d same config n d same problem. its jus dat i hav entered a bootloop. how shall i fix it? plz reply ASAP.

utkarshaqua said:
my onex has d same config n d same problem. its jus dat i hav entered a bootloop. how shall i fix it? plz reply ASAP.
Click to expand...
Click to collapse
Flashed the boot.img ?

Mr Hofs said:
Flashed the boot.img ?
Click to expand...
Click to collapse
i hadn't. but nw that i hav its workin fine
thanx 4 d advice:good:

utkarshaqua said:
i hadn't. but nw that i hav its workin fine
thanx 4 d advice:good:
Click to expand...
Click to collapse
flashing the boot.img is no advice.....its mandatory hahahaha
good it's working now ! enjoy

[Q] Downgrade to CM10.2 TeamCanjica from CM11 Mclaw

Hi guys,
I am trying to downgrade to CM10.2 TeamCanjica from CM11 Mclaw version but I get Status 7 error. I've installed CM11 over CM10.2. I never had problem flashing CM10.2 from TeamCanjica before. I guess something in CM11 is different and does not allow me to downgrade.
I've searched on forums but found nothing that works.. Even checked the build.prop file. Under ro.product.model i have GT-I8160.
Any solutions?
Thank you!

Which status 7 error?
Have you tried deleting assert lines?
Sent from my GT-I8160 using Tapatalk

I tried to upload screenshot of error but XDA forums prevented me.
I'll try to retype it:
assert failed: getprop("ro.product.device") == "codina" || getprop("ro.build.product") == "codina" || getprop("ro.product.device") == "i8160" || getpro("ro.build.product") == "i8160" || getprop("ro.product.device") == "GT-I8160" || getprop("ro.build.product") == "GT-I8610"
E: error in /storage/sdcard1/cm-10.2-20131208-UNOFFICIAL-codina.zip
(Status 7)
Instalation aborted
Click to expand...
Click to collapse
Sorry, what are assert lines and where can I delete them?

kokynator said:
I tried to upload screenshot of error but XDA forums prevented me.
I'll try to retype it:
Sorry, what are assert lines and where can I delete them?
Click to expand...
Click to collapse
Rom zip-META-INF-com-google-android-updater-script
Open as text
Delete all BEFORE
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
Or something like that. It should have a [mount("ext4"]
Sent from my GT-I8160 using Tapatalk

Nice! Thank you it works now! :good:

Glad . You can ask in Q & A next time too, no need for new thread
Sent from my GT-I8160 using Tapatalk

I have a problem with restoring to CM10.1. I deleted these lines, but I have error: "status 6 instalation aborted". What should I have to do?

Did you accidentally delete a punctuation that isnt supposed to be removed?
OR
Did you not delete some punctuation?
Sent from my iPhone

What? Can You explain?

str3tch72 said:
What? Can You explain?
Click to expand...
Click to collapse
Perhaps you deleted less then what you had to/you deleted more
Sent from my iPhone

I deleted three lines which I get error.

As well as bad EOL delimiters, this may also be due to a problem in the script itself. There could be a missing ";" at the end of a line, or you have opened a quoted string " or brackets ( without closing.
(From @hawkerpaul)
Sent from my iPhone

Can You give me working one?

Try
https://docs.google.com/file/d/0B6rm7amiSi_QS05vdUZMck5WU1U/edit?usp=docslist_api
Sent from my GT-I8160 using Tapatalk

Is it modified?
---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------
I need permission to download it xD

str3tch72 said:
Is it modified?
---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------
I need permission to download it xD
Click to expand...
Click to collapse
?? Hold on i upload to db
E: sorry
https://www.dropbox.com/s/lrulqrja9szqbtc/updater-script yes its modifeid
Sent from my GT-I8160 using Tapatalk

Try it ASAP, thanks my friend :3

^^
Sent from my GT-I8160 using Tapatalk

Still same...

str3tch72 said:
Still same...
Click to expand...
Click to collapse
Sorry bro
Maybe cm11-cm10.2-cm10.1?(ik its a long procedure but i prefer it over odin
Sent from my iPhone