[ROM][WIP][Quad-MX][HK] MIUI V4 & ICS 4.0.3

koaaN · Oct 26, 2012

MIUI V4

CAN ANYONE HELP ME PORT CWM? SEND ME A PM!

Working:
Camera (Cant take pictures without SD)
Sound
WIFI
DATA
Calls & SMS

Not Working:
Internal SD (Not mounted)

Download: Comming Soon

Vanilla ICS

Working:
Camera (Cant take pictures without SD)
Sound
WIFI
DATA
Calls & SMS

Not Working:
Internal SD (Not mounted)

Download: Comming soon

DO YOU THINK YOU CAN HELP ME? SEND A PM!

Sources:
Kernel Source: https://github.com/lvchaqiu/meizu-mx-kernel
MIUI Recovery Source: https://github.com/MiCode/patchrom_mx/tree/ics/bootable/recovery

More to come soon...

koaaN · Oct 26, 2012

For later use

ernmin · Oct 26, 2012

wasnt MIUI V4 imported?

koaaN · Oct 26, 2012

ernmin said:
wasnt MIUI V4 imported?

Not for the quad-core model

eliaztheone · Oct 26, 2012

Is there a way to build the MIUI V4 on the Flyme Base and not the buggy Stock ICS ??

datagutt · Oct 26, 2012

eliaztheone said:
Is there a way to build the MIUI V4 on the Flyme Base and not the buggy Stock ICS ??

It is probably possible, but there is no good miui device rom to start from, because Nexus S and Galaxy Nexus is based on JB. I would not base on touchwiz-based MIUI for GalaxyS 2 and 3.

koaaN · Oct 26, 2012

Im trying to port CM9, im stuck at cm9 bootanimation, and logcat not working :s

zxf8665905 · Oct 27, 2012

just for HK.
Sent from my M032 using xda app-developers app

xboxfanj · Oct 28, 2012

As far as cwm, either use koush's builder at builder.clockworkmod.com and put the recovery.img in and recovery.fstab, or unpack stock recovery using a ramdisk unpack (aka boot.img unpacker) tool and copy over recovery.fstab and default.prop to cwm and repack.

Sent from my SPH-D700 using Tapatalk 2

koaaN · Oct 28, 2012

xboxfanj said:
As far as cwm, either use koush's builder at builder.clockworkmod.com and put the recovery.img in and recovery.fstab, or unpack stock recovery using a ramdisk unpack (aka boot.img unpacker) tool and copy over recovery.fstab and default.prop to cwm and repack.

Sent from my SPH-D700 using Tapatalk 2

The MX uses recovery-uboot.img and is not packed the same as a normal recovery.img

TwoPointZero · Oct 28, 2012

It's not an issue. As I reckon, CWM recovery imgs lack the 64-byte u-boot header (IH_MAGIC) for the ramdisk, they are the ones that are not "the norm".

Code:

# mount point   fstype          device

/sdcard		vfat	/dev/block/mmcblk0p1
/system		ext4	/dev/block/mmcblk0p2
/data		ext4	/dev/block/mmcblk0p3
/cache		ext4	/dev/block/mmcblk0p4
/misc		emmc	/dev/block/mmcblk0p9
/recovery	emmc	/dev/block/mmcblk0p10

Code:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mass_storage
# begin build properties
# autogenerated by buildinfo.sh
ro.build.cta=noncta
ro.build.id=IML74K
ro.build.display.id=Flyme 1.0.3
ro.build.mask.id=4.0.0-7929_zh-HK
ro.build.version.incremental=eng.mobileapp.20120725.003030
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012年 07月 25日 星期三 00:30:53 CST
ro.build.date.utc=1343147453
ro.build.type=user
ro.build.user=mobileapp
ro.build.host=mobileapp
ro.build.tags=test-keys
ro.product.model=M03X
ro.product.brand=Meizu
ro.product.name=meizu_mx
ro.product.board=mx
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Meizu
ro.product.locale.language=zh
ro.product.locale.region=TW
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=meizu_mx-user 4.0.3 test-keys 7929_zh-HK
ro.build.fingerprint=Meizu/meizu_mx/mx:4.0.3/IML74K/eng.mobileapp.20120725.003030:user/test-keys
ro.build.characteristics=phone
# end build properties
#
# system.prop for mx
#

rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyACM0

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.sf.lcd_density=320
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.config.ringtone=Crystal.ogg
ro.config.notification_sound=VideoRecord.ogg
ro.config.mms_sound=Ripples.ogg
ro.config.email_sound=VideoRecord.ogg
ro.config.calendar_sound=Jump.ogg
ro.config.alarm_alert=Morning_Dew.ogg
ro.telephony.default_network=0
persist.sys.timezone=Asia/Hong_Kong
persist.sys.meizu.region=hk-tw
persist.sys.meizu.codepage=big5
ro.meizu.setupwizard.flyme=false
ro.meizu.setupwizard.setlang=true
ro.meizu.region.enable=true
ro.meizu.contactmsg.auth=false
ro.meizu.customize.pccw=false
ro.meizu.autorecorder=true
ro.meizu.visualvoicemail=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

koaaN · Oct 28, 2012

TwoPointZero said:

It's not an issue. As I reckon, CWM recovery imgs lack the 64-byte u-boot header (IH_MAGIC) for the ramdisk, they are the ones that are not "the norm".

Code:

# mount point   fstype          device

/sdcard		vfat	/dev/block/mmcblk0p1
/system		ext4	/dev/block/mmcblk0p2
/data		ext4	/dev/block/mmcblk0p3
/cache		ext4	/dev/block/mmcblk0p4
/misc		emmc	/dev/block/mmcblk0p9
/recovery	emmc	/dev/block/mmcblk0p10

Code:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mass_storage
# begin build properties
# autogenerated by buildinfo.sh
ro.build.cta=noncta
ro.build.id=IML74K
ro.build.display.id=Flyme 1.0.3
ro.build.mask.id=4.0.0-7929_zh-HK
ro.build.version.incremental=eng.mobileapp.20120725.003030
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012年 07月 25日 星期三 00:30:53 CST
ro.build.date.utc=1343147453
ro.build.type=user
ro.build.user=mobileapp
ro.build.host=mobileapp
ro.build.tags=test-keys
ro.product.model=M03X
ro.product.brand=Meizu
ro.product.name=meizu_mx
ro.product.board=mx
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Meizu
ro.product.locale.language=zh
ro.product.locale.region=TW
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=meizu_mx-user 4.0.3 test-keys 7929_zh-HK
ro.build.fingerprint=Meizu/meizu_mx/mx:4.0.3/IML74K/eng.mobileapp.20120725.003030:user/test-keys
ro.build.characteristics=phone
# end build properties
#
# system.prop for mx
#

rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyACM0

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.sf.lcd_density=320
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.config.ringtone=Crystal.ogg
ro.config.notification_sound=VideoRecord.ogg
ro.config.mms_sound=Ripples.ogg
ro.config.email_sound=VideoRecord.ogg
ro.config.calendar_sound=Jump.ogg
ro.config.alarm_alert=Morning_Dew.ogg
ro.telephony.default_network=0
persist.sys.timezone=Asia/Hong_Kong
persist.sys.meizu.region=hk-tw
persist.sys.meizu.codepage=big5
ro.meizu.setupwizard.flyme=false
ro.meizu.setupwizard.setlang=true
ro.meizu.region.enable=true
ro.meizu.contactmsg.auth=false
ro.meizu.customize.pccw=false
ro.meizu.autorecorder=true
ro.meizu.visualvoicemail=true
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

I have a cwm build but its not uboot, so its not working

datagutt · Oct 29, 2012

The recovery-uboot.img file from Meizu does NOT have a ANDROID header. The CWM one i built does. We need to convert it to a valid uboot image.

darycs2006 · Oct 30, 2012

useless

koaaN · Oct 30, 2012

darycs2006 said:
useless

Your post is useless

sirhaxalot · Oct 30, 2012

instead of useless I will be more than happy beta testing for this project

count me in.:laugh:
from norway

MrColdbird · Nov 14, 2012

As for CWM - is a kernel rebuild really necessary?

Shouldn't a normal ramfs mod of the original recovery be plenty given that the required modules are loaded by the original recovery kernel image?

ykker · Nov 14, 2012

thank you for your work about MX-4core，I am a user of this phone from china，I can't help you with android development,But I wish I can help you somewhere~~~

leo321 · Nov 15, 2012

ykker said:
thank you for your work about MX-4core，I am a user of this phone from china，I can't help you with android development,But I wish I can help you somewhere~~~

Hit the thanks button, if nothing else

Ri0z · Nov 23, 2012

Can someone pick this up again? I'll donate cash if it takes.. Really sick of Flyme, want to go back to MIUI..

[ROM][WIP][Quad-MX][HK] MIUI V4 & ICS 4.0.3

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Member

Senior Member

New member

Senior Member

Member

Similar threads

Top Liked Posts