Develop Bugs

[Q] My arc has changed to LT18a? Can't apply new update :(

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

CyanogendMOD 10 FXP Neo V haida

Installing: /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
Opening update package...
Installing update...
script aborted: 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"
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/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
(Status 7)
Installation aborted.
What steps will reproduce the problem?

bt4777 said:
Installing: /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
Opening update package...
Installing update...
script aborted: 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"
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/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
(Status 7)
Installation aborted.
What steps will reproduce the problem?
Click to expand...
Click to collapse
dude go to META-INF/com/google/android and extract updater-script of the zip file (u downloaded i.e ROM )and open extracted updater-script with Notepad++(for download notepad++ google it) there after delete first three line and save.there after zip it to the rom(META-INF/com/google/android) from where u extracted
Press thank if i helped u

cyanidekiller said:
dude go to META-INF/com/google/android and extract updater-script of the zip file (u downloaded i.e ROM )and open extracted updater-script with Notepad++(for download notepad++ google it) there after delete first three line and save.there after zip it to the rom(META-INF/com/google/android) from where u extracted
Press thank if i helped u
Click to expand...
Click to collapse
which are the first three lines? begins and ends where

bt4777 said:
which are the first three lines? begins and ends where
Click to expand...
Click to collapse
assert(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");
delete these 3 lines
Press thanks if i helped u

cyanidekiller said:
assert(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");
delete these 3 lines
Press thanks if i helped u
Click to expand...
Click to collapse
trying this now. will get back with the results in 5 mins
edit: didnt work:
symlink: some symlinks failed
E:Error in /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
(Status 7)
Installation aborted.

Did you try with CWM 6?
I had this problem with CWM 5 so i used the boot.img in the RAR of the cyanogenmod i.e. extracted it to android tools folder
then used the command
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
So it booted on CWM 6 and installation was done without any issues.
If you want to reproduce the problem, try installing CM10 with CWM 5.

What version of CWM to use so i can install FXP137?
5.0.2.7 , 5.5.0.4 or 6.0.1.0 and from where to download it and install it for Neo V (MT11i - haida)? I understand that 5.0.2.7 is for GB, 5.5.0.4 works with ICS and now i see that 6 is recommended for JB... Please advise me, it will be helpfully if you give me a link, i have search on a lot of threads and read all this NoobGuide but the version presented is 5.0.2.7 also i have rooted and unlocked my bootloader using testpoint method. Thanks in advance.

[Q] Mk16 Cannot Flash ROM

Hi, today I received the SE Xperia PRO, I successfully rooted the device using DooMLoRD_v4_ROOT. However, I am unable to install the CM 10 from the official CM website for this device, I keep getting this
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device")=="MK16i" || getprop("ro.build.product") == "MK16i" || getprop("ro.product.device") == "MK16a" || getprop("ro.build.product") == "iyokan" || getprop("ro.build.product") == "iyokan"E:error in /sdcard/FXP138-cm-10-20130811-NIGHTLY-iyokan.zip
(Status 7)

Pride4u said:
Hi, today I received the SE Xperia PRO, I successfully rooted the device using DooMLoRD_v4_ROOT. However, I am unable to install the CM 10 from the official CM website for this device, I keep getting this
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device")=="MK16i" || getprop("ro.build.product") == "MK16i" || getprop("ro.product.device") == "MK16a" || getprop("ro.build.product") == "iyokan" || getprop("ro.build.product") == "iyokan"E:error in /sdcard/FXP138-cm-10-20130811-NIGHTLY-iyokan.zip
(Status 7)
Click to expand...
Click to collapse
Did you flash the kernel in the ROM zip?
僕のLT18iから送られてきた

Nope, I'll try that and see if it helps.
UPDATE:
Thanks, the installation works now.

[Q] Assert Failed - What does it mean literally?

Code:
-- Installing: /sdcard/cmupdater/cm-10.1.3-d2att.zip
Finding update package...
I:Update location: /sdcard/cmupdater/cm-10.1.3-d2att.zip
I:using /data/media for /sdcard/cmupdater/cm-10.1.3-d2att.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1"
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG2" || getprop("ro.bootloader") == "I747MVLDLK4" || getprop("ro.bootloader") == "I747MVLDMF1" || getprop("ro.bootloader") == "I747MUMBLK3" || getprop("ro.bootloader") == "I747MUMBLL1"
E:Error in /sdcard/cmupdater/cm-10.1.3-d2att.zip
(Status 7)
Installation aborted.
for my understanding, does an "assert failed" error mean that the script was looking for one of any of the property values (ie I747UCDMG2), didn't find it, and then failed?

Angry Black Man said:
Code:
-- Installing: /sdcard/cmupdater/cm-10.1.3-d2att.zip
Finding update package...
I:Update location: /sdcard/cmupdater/cm-10.1.3-d2att.zip
I:using /data/media for /sdcard/cmupdater/cm-10.1.3-d2att.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1"
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG2" || getprop("ro.bootloader") == "I747MVLDLK4" || getprop("ro.bootloader") == "I747MVLDMF1" || getprop("ro.bootloader") == "I747MUMBLK3" || getprop("ro.bootloader") == "I747MUMBLL1"
E:Error in /sdcard/cmupdater/cm-10.1.3-d2att.zip
(Status 7)
Installation aborted.
for my understanding, does an "assert failed" error mean that the script was looking for one of any of the property values (ie I747UCDMG2), didn't find it, and then failed?
Click to expand...
Click to collapse
Yes it was looking for "I747UCDMG2" and down but failed to find the proper bootloader on your phone. The status 7 error can easily be fixed. just google it.

If you are installing via CWM make sure it's up to date (easy way is to install Rom Manager from the playstore) also why not install the latest version of CM?
get.cm/?device=d2att
Make sure you do a factory wipe/reset and clear cache/daelik

james2432 said:
why not install the latest version of CM?
Click to expand...
Click to collapse
because i'm following this wiki exactly, and it's not working exactly.
removing the asserts hasn't fixed the problem. first i got status 6, and when i did it a second time, repackaging the files with 7zip into zip format, i got no error at all, the installation just failed and aborted.

Angry Black Man said:
because i'm following this wiki exactly, and it's not working exactly.
removing the asserts hasn't fixed the problem. first i got status 6, and when i did it a second time, repackaging the files with 7zip into zip format, i got no error at all, the installation just failed and aborted.
Click to expand...
Click to collapse
Also here's how to update the bootloader via odin:
http://forum.xda-developers.com/showthread.php?t=2321310

Downgrade Baseband...can be done?

My question is simple I hope someone can helpme to figure this out.
Is there a chance to downgrade from UVUENC2 to UVUEMJC on T999 from T Mobile?
I have a lots of problems to Install CM11 on One Click and Manual. And this is fault of the new baseband.
Thanks a lot!

Yes there are certainly ways to go back to prior Modem. I don't believe that can cause issues to CM. Can you try some other KitKat Rom ?

Perseus71 said:
Yes there are certainly ways to go back to prior Modem. I don't believe that can cause issues to CM. Can you try some other KitKat Rom ?
Click to expand...
Click to collapse
Yep
If use the manual installation method of any custom ROM I get the Assert Failed: getprop error no matter if use TWRP 2.6.3.1 or CWM 6.0.4.5 or the newer version of those two, and if use the Auto Installer just ask me at the end of the installation "Root is missing. Root this device?." No matter if I choose YES or NO still returning to stock ROM, with a lots of errors by the way.
Updating partition details.....
Full SELinux support is present.
Running boot script...
Finished running boot script.
Installing '/external_sd/d2tm0/system.zip...
Checking for MD5 check: no MD5 file found
assert failed: getprop (ro.bootloader) == "T999UVDLJA"
getprop ("ro.bootloader") == "T999UVDLJA"
getprop ("ro.bootloader") == "T999UVDLJC"
getprop ("ro.bootloader") == "T999UVDMD5"
getprop ("ro.bootloader") == "T999UVUEMJC"
getprop ("ro.bootloader") == "T999UVVLDLL1"
getprop ("ro.bootloader") == "T999LUVAMB7"
getprop ("ro.bootloader") == "T999VVLDMF2"
getprop ("ro.bootloader") == "T999VVLUEMK5"
getprop ("ro.bootloader") == "T999LUVUBMK4"
E: Error excecuting updater binary in zip '/external_sd/s2tmo/system.zip
Error flashing zip '/external_sd/d2tm0/system.zip
Those errors are on CM Rom
What can I do?

Put a hash Symbol (#) in front of each of these assert lines.

Perseus71 said:
Put a hash Symbol (#) in front of each of these assert lines.
Click to expand...
Click to collapse
Where or when?!

Please edit the Rom Zip file with Winzip on the pc. Do not extract the file. Make sure to open the updater script with Notepad. Its located under
/META-INF/com/google/android/
Once opened, you are looking for lines
getprop (ro.bootloader) == "T999UVDLJA"
getprop ("ro.bootloader") == "T999UVDLJA"
getprop ("ro.bootloader") == "T999UVDLJC"
getprop ("ro.bootloader") == "T999UVDMD5"
getprop ("ro.bootloader") == "T999UVUEMJC"
getprop ("ro.bootloader") == "T999UVVLDLL1"
getprop ("ro.bootloader") == "T999LUVAMB7"
getprop ("ro.bootloader") == "T999VVLDMF2"
getprop ("ro.bootloader") == "T999VVLUEMK5"
getprop ("ro.bootloader") == "T999LUVUBMK4"
You want to put a # at the beginning of each line. Or delete them out all together. Close notepad and save the file when prompted. Winzip will immediately prompt you for updating the archive. Do so. Then try flashing the zip.
If errors occur, attach the updater-script file to a post here.

Would using odin back to stock work for their issue? Maybe a full wipe off of original recovery with that?

Perseus71 said:
Please edit the Rom Zip file with Winzip on the pc. Do not extract the file. Make sure to open the updater script with Notepad. Its located under
/META-INF/com/google/android/
Once opened, you are looking for lines
getprop (ro.bootloader) == "T999UVDLJA"
getprop ("ro.bootloader") == "T999UVDLJA"
getprop ("ro.bootloader") == "T999UVDLJC"
getprop ("ro.bootloader") == "T999UVDMD5"
getprop ("ro.bootloader") == "T999UVUEMJC"
getprop ("ro.bootloader") == "T999UVVLDLL1"
getprop ("ro.bootloader") == "T999LUVAMB7"
getprop ("ro.bootloader") == "T999VVLDMF2"
getprop ("ro.bootloader") == "T999VVLUEMK5"
getprop ("ro.bootloader") == "T999LUVUBMK4"
You want to put a # at the beginning of each line. Or delete them out all together. Close notepad and save the file when prompted. Winzip will immediately prompt you for updating the archive. Do so. Then try flashing the zip.
If errors occur, attach the updater-script file to a post here.
Click to expand...
Click to collapse
Will trie this I hope this works was a miskate update the T999, in the old baseband I haven't any problem to install custom ROMs now CM can't be installed by any way no matter if use CWM, TWRP; Goo, etc.....

jmberumenb said:
Will trie this I hope this works was a miskate update the T999, in the old baseband I haven't any problem to install custom ROMs now CM can't be installed by any way no matter if use CWM, TWRP; Goo, etc.....
Click to expand...
Click to collapse
CM and others have not yet changed their updater scripts to include this new bootloader. Not your fault. They need to catch up. You may want to post on the thread where you got the rom.

Perseus71 said:
CM and others have not yet changed their updater scripts to include this new bootloader. Not your fault. They need to catch up. You may want to post on the thread where you got the rom.
Click to expand...
Click to collapse
:crying: So there will be no CM for me for now :crying:

Not unless you can comment out the Asserts in the updater script.

Perseus71 said:
Not unless you can comment out the Asserts in the updater script.
Click to expand...
Click to collapse
Working on it

Perseus71 said:
Please edit the Rom Zip file with Winzip on the pc. Do not extract the file. Make sure to open the updater script with Notepad. Its located under
/META-INF/com/google/android/
Once opened, you are looking for lines
getprop (ro.bootloader) == "T999UVDLJA"
getprop ("ro.bootloader") == "T999UVDLJA"
getprop ("ro.bootloader") == "T999UVDLJC"
getprop ("ro.bootloader") == "T999UVDMD5"
getprop ("ro.bootloader") == "T999UVUEMJC"
getprop ("ro.bootloader") == "T999UVVLDLL1"
getprop ("ro.bootloader") == "T999LUVAMB7"
getprop ("ro.bootloader") == "T999VVLDMF2"
getprop ("ro.bootloader") == "T999VVLUEMK5"
getprop ("ro.bootloader") == "T999LUVUBMK4"
You want to put a # at the beginning of each line. Or delete them out all together. Close notepad and save the file when prompted. Winzip will immediately prompt you for updating the archive. Do so. Then try flashing the zip.
If errors occur, attach the updater-script file to a post here.
Click to expand...
Click to collapse
This just works great!!!
Thanks a lot! Now we are using CM again!! :laugh:

Glad it all worked out.

Perseus71 said:
Glad it all worked out.
Click to expand...
Click to collapse
I dont get what to do
Like this?
#getprop("ro.bootloader") == "T999UVDLJA" ||
#getprop("ro.bootloader") == "T999UVDLJC" ||
#getprop("ro.bootloader") == "T999UVDMD5" ||
#getprop("ro.bootloader") == "T999UVUEMJC" ||
#getprop("ro.bootloader") == "T999VVLDLL1" ||
#getprop("ro.bootloader") == "T999LUVAMB7" ||
#getprop("ro.bootloader") == "T999VVLDMF2" ||
#getprop("ro.bootloader") == "T999VVLUEMK5" ||
#getprop("ro.bootloader") == "T999LUVUBMK4");

Androidn00b22 said:
I dont get what to do
Like this?
#getprop("ro.bootloader") == "T999UVDLJA" ||
#getprop("ro.bootloader") == "T999UVDLJC" ||
#getprop("ro.bootloader") == "T999UVDMD5" ||
#getprop("ro.bootloader") == "T999UVUEMJC" ||
#getprop("ro.bootloader") == "T999VVLDLL1" ||
#getprop("ro.bootloader") == "T999LUVAMB7" ||
#getprop("ro.bootloader") == "T999VVLDMF2" ||
#getprop("ro.bootloader") == "T999VVLUEMK5" ||
#getprop("ro.bootloader") == "T999LUVUBMK4");
Click to expand...
Click to collapse
Yes, or just delete that whole section

It didnt work for me, it failed. Did I mess something up?
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo" || abort("This package is for \"d2tmo\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(#getprop("ro.bootloader") == "T999UVDLJA" ||
#getprop("ro.bootloader") == "T999UVDLJC" ||
#getprop("ro.bootloader") == "T999UVDMD5" ||
#getprop("ro.bootloader") == "T999UVUEMJC" ||
#getprop("ro.bootloader") == "T999VVLDLL1" ||
#getprop("ro.bootloader") == "T999LUVAMB7" ||
#getprop("ro.bootloader") == "T999VVLDMF2" ||
#getprop("ro.bootloader") == "T999VVLUEMK5" ||
#getprop("ro.bootloader") == "T999LUVUBMK4");

Just delete them then or write down your own bootloader without the hash