Android CyanogenMod porblems

[Ziggy Zigzagoon]

I have an Xperia Play of the R800at variety, rooted but locked. (I refuse to unlock the bootloader out of fear for my warranty.) However, I installed ClockWorkMod using the Xperia App. I attempted to install the latest CyanogenMod for my device, but, even after I formatted the cache, system, and data and doing a factory reset, I got:

Spoiler

Finding update package...
Opening update package...
Installing update...
assert failed: 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"
E:Error in /sdcard/update-cm-7.2.0-RC3-XperiaPlay-zeus-signed.zip
(Status 7)
Installation aborted.

Removing the assert check would only deliver:

Spoiler

E:Error in /sdcard/update-cm-7.2.0-RC3-XperiaPlay-zeus-signed.zip
(Status 6)
Installation aborted.

Does anyone know what is the issue?

 

[pokefloote]

All of those errors have to do with the build.prop file in the system... [it's the file that tells your phone what kind of phone it is, among other important things] Have you tried downloading the ROM a second time? It might have been corrupted somehow.

Edit: doing factory resets for cyanogenmod are usually never done, sometimes not supported. Instead, just wiping system/data and reflashing the rom achieves the same thing [a fresh start].

 

[Tom Bombadildo]

Sounds like the ROM didn't download correctly. Try redownloading and reflashing it. If it gives you an error again, bring it to the rootzwiki.com forums (a separation from xda-developers with less noobs) and ask around, they might know whats up.

 

[Tekken179]

A. CyanogenMOD requires a custom Kernel.
B. You can only get custom Kernels by unlocking your phones bootloader.
C. You can only install customized default firmware (custom firmware based on stock).
D. CyanogenMOD is useless for the Xplay as it disables the hardware buttons in many games and causes errors in them not working properly.

Hope this helps


Also: To get your phone back and working your going to have to do a complete format through SEUS or use flashtool to flash generic firmware version.

Even more Also: Some phones don't require custom kernels for CM7 mostly older phones, but i assure you custom kernels are the case for XPlay users.

 

[Ziggy Zigzagoon]

Have you tried downloading the ROM a second time? It might have been corrupted somehow.

Sounds like the ROM didn't download correctly. Try redownloading and reflashing it.

I did that multiple times with different Cyanogen ROMS, all with the same results.

A. CyanogenMOD requires a custom Kernel.
B. You can only get custom Kernels by unlocking your phones bootloader.
C. You can only install customized default firmware (custom firmware based on stock).
D. CyanogenMOD is useless for the Xplay as it disables the hardware buttons in many games and causes errors in them not working properly.

Hope this helps


Also: To get your phone back and working your going to have to do a complete format through SEUS or use flashtool to flash generic firmware version.

Even more Also: Some phones don't require custom kernels for CM7 mostly older phones, but i assure you custom kernels are the case for XPlay users.

Kehhei!
...
Thank you. (No; I was angry at the fact that CyanogenMod is useless to my Xperia Play. Thank you for informing me.)