31 December 2014

How to Fix “E: Can’t mount /sdcard/” on Smartphone






Android is really a great operating system with immense flexibility and that is why it is the most popular platform in the world. Owning an Android device gives you access to millions of amazing apps and, if you are an adventurous user, also lets you flash custom ROMs, kernels, mods and ported apps via a custom recovery.

There is a huge custom development community that keeps toiling for giving us stuff that enhance our mobile experience. Involving in such activities might add some adventurous flair to your mobile experience but, at the same time, they might also pose issues and risk to the device. Nobody would like to turn his/her phone into a costly paperweight and that’s why one should always take utmost care while flashing custom ROMs, mods and kernels.
Anyway, if you are addicted to flashing mods and ROMs on your Android device, or even if you are a novice to such things, and happen to encounter SD card mount issue in recovery, we have come with some possible solutions to fix the problem. When the error occurs, you might see one of the following messages on the recovery screen:
  • CWM can’t mount SD
  • SD Card Not Mounted
  • Can’t mount external micro sd-card
  • SD card won’t mount
  • Can’t mount sdcard
  • Can’t mount emmc
  • Can’t mount external micro sd-card
  • E:Can’t mount /cache/recovery/command last_log emmc external micro sd-card
  • E: Can’t mount /sdcard/
  • E:failed to mount /sdcard (file exists)
  • E:failed to mount /sdcard (no such file or directory)
 
 Download this: SD Formattor
 https://www.sdcard.org/downloads/formatter_4/
 

Method 2: Update CWM or TWRP Recovery

Formatting the SD card did not help you at all? Don’t worry, this might be a recovery related issue! Just download the latest version of CWM/TWRP recovery and flash it. You can also try switching to a different recovery than installed on your device. In other words, if your device has CWM, try TWRP and vice versa.
Download ClockworkMod Recovery
Download TWRP Recovery

Flashing ROMs When SD Card is Not Mounted

If you got an urgent need to flash a ROM but after booting into CWM PhilZ recovery are not able to access the external SD storage because of E: Can’t mount /sdcard/ issue, there is still a way you can install the ROM using ADB commands. Here’s how:
  1. Set up Android SDK (ADB and Fastboot) on your computer. Alternatively, you can download the minimal Fastboot tool and unzip it.
  2. Now copy the ROM zip file to the platform-tools or mfastboot-v2 folder.
  3. Get into CWM recovery mode.
  4. Make sure that USB Debugging is enabled on your phone. Just to make sure that you device is detected by ADB, connect you phone to computer, launch a command window from the ADB and fastboot folder and type the following command:
    adb devices
  5. If you see your device’s serial number in the command window, you are good to go.
  6. Now type this:
    adb shell
  7. You should see “#” (hash) somewhere in front of your command line.
  8. Now type the following command and press Enter key:
    ls
  9. Now you should show you the folders on your device. Try to navigate to the directory /data/media using the following command:
    cd /data/media/
  10. Now push the ROM file to the above directory via the following command (replace ROM.zip with the name of your ROM file):
    adb push ROM.zip /data/media/ROM.zip
The ROM file will now be installed to your phone and it should boot properly. This tip can be helpful if your device gets into bootloop and you are not able to access your ROM backup or flashable Zip on the SD card.

25 December 2014

手机信号G、E、O、3G、H、H+、4g含义科普 你知道吗?




用过安卓手机的都知道,信号显示哪经常有手机信号G、E、O、3G、H、H+、4g的之类的数字,而经常会变,今天小编告诉你安卓手机里的G、E、O、3G、H、H+、4g之类的含义。

指GPRS,是2.5G网络(iPhone显示O);
指EDGE网络,属2.75G;
3G 指普通3G网络,速度在2-7M;
H  指3G的升级版hsdpa网络,是3.5G,速度可达14.4M;
H+ 是hsdpa的升级版hspa+,是3.75G,速度可达21M-42M。
4g 技术支持100Mbps~150Mbps的下行网络带宽。4g意味着用户可以体验到最大12.5MB/是~18.75MB/s的下行速度。

网络速度从慢到快依次是G
PS:上面说的速度都是理论速度。实际影响的因素有很多,所以一般都不会稳定在最大速度。

20 December 2014

Qualcomm Snapdragon 200, 400, 600, 800 CPUs

Source:


US ARM-class chip maker Qualcomm produces some of the hottest ARM processors on the market and its no surprise that any smartphone maker worth its salt is lining up to get hold of Qualcomm’s Snapdragon CPUs for its products. But with so many different options available, it can be a bit of a nightmare trying to figure out what’s what.
So in this roundup, we’re going to look at the Snapdragon 200, 400, 600 and 800-class ARM processors to see what makes them tick. We won’t delve into the architecture but we will look at them in a way that makes it easier to tell them apart when you’re trying to decide between phones.

Qualcomm Snapdragon 200
The Snapdragon 200-series is the entry-level ‘newbie’ range of the new family.
So far there are six different Snapdragon 200 CPUs – the MSM8225Q, MSM8625Q, MSM8210, MSM8610, MSM8212 and MSM8612.
Rather than concentrate on each model, we’ll break them down into the differences.
The Q-series are actually older ARM Cortex A5 designs, but quad-core and clocking at 1.4GHz. They’re manufactured on a larger 45-nanometre scale so they’re cheaper to make, but not as power efficient. They use the entry-level Adreno 203 graphics core.
The 8×10 series (dual-core) and 8×12 models (quad-core) are based on the newer Cortex A7 design, all clocking at 1.2GHz with faster Adreno 302 graphics. They’re manufactured at a smaller 28nm scale, so they’re more expensive to make but more power efficient, which should help with producing good battery life.
The Snapdragon 200 series was only announced recently and will be used in entry-level smartphones.

Qualcomm Snapdragon 400
The 400-series is the most plentiful in numbers with ten on offer – we’ll keep this short and just use the basic model numbers: 8226, 8626, 8926, 8230, 8630, 8930, 8030AB, 8230AB, 8630AB, 8930AB.
The 8×26 range are quad-core Cortex A7 designs with up-rated Adreno 305 graphics cores, all manufactured at 28-nanometres and clocking at between 1.2 and 1.4GHz.
The 8×30 series are dual-core but are the first to utilise Qualcomm’s own custom Krait CPU design. Qualcomm is one of the very few ARM license holders that pumps out its own architecture. The Krait design conforms perfectly to the ARMv7 instruction set but does it differently to the reference ARM Cortex design. And this is first CPUs where the Qualcomm ‘special sauce’ comes into play. These chips are based on the entry-level Krait 200 core design, but otherwise share the 8×26 features such as 28nm manufacture and Adreno 305 GPU core.
Finally, the the four AB-series chips all use the uprated Krait 300 core design clocking up to 1.7GHz, again in a dual-core arrangement, manufactured at 28nm and with the Adreno 305 core.
The Snapdragon 400 series is expected to appear in mid-range phones in the next 12 months.

Qualcomm Snapdragon 600
For most of 2013, the Snapdragon 600 series has been the flagship Qualcomm CPU range, appearing in some top-drawer smartphones including the HTC One and Samsung Galaxy S4.
At the moment, there are only two in this series – the APQ8064T and APQ8064M. Again, these are both manufactured at up to 28nm and run the faster Adreno 320 graphics core. The main difference is the T chip runs at up to 1.9GHz, while the M model tops out at 1.7GHz. The T also includes integrated Wi-Fi and Bluetooth while the M doesn’t. Basically, these are quad-core versions of the Snapdragon 400 but include the faster Adreno 320 GPU.

Qualcomm Snapdragon 800
The Snapdragon 800 is now the new flagship ARM CPU until we see the the first 64-bit Cortex A57 chips some time in 2014. They use the new Krait 400 core design, clocked up to an impressive 2.3GHz. They all run the fastest Adreno 330 GPU core, they’re all manufactured at 28nm, they all have integrated 802.11a/b/g/n/ac Wi-Fi and Bluetooth 4.0. The difference? The modem. The 8074 comes with no data connectivity at all; the 8274 is the HSPA+ (3G); the 8674 supports CDMA networks; and the 8974 is the next-generation 4G/LTE option.
So far, the first phones announced using these chips are the Samsung Galaxy S4 LTE-A model and Sony’s Xperia Z Ultra. Reports also suggest Microsoft showed off its up-coming Surface RT tablet using a Snapdragon 800 series CPU at its recent Developer’s Conference. This will be an interesting test to see how well the Snapdragon Krait core compares with Intel’s X86-architectured Atom CPU in a Windows environment in terms of productivity speed.
So that’s a rough snapshot of the new Snapdragon series – as I said, it’s not a full-on view of the architecture difference but it should be enough for you to understand just what you’re picking up the next time you go to buy a Qualcomm-powered smartphone from your favourite brand.

18 November 2014

Jiayu S3






Jiayu G4(4.7") VS S3(5.5")









Jiayu S3
OS: Android 4.4
CPU: MT6752 Octa Core LTE CPU 64bit
RAM     2/3GB,DDR3
Storage  16GB
Sim Card: Dual SIM card (support TD-LTE and FDD-LTE)
Service Provide: Unlocked
2G: GSM 850/900/1800/1900MHz
3G: WCDMA 2100MHz

5G Wifi AC
MS mode: WCDMA/GSM
Shell Material    Plastic
Screen: Capacitive Touchscreen, 1920*1800 High-resolution Screen
Size:  5.5 Inch inch
Visible Angle: 178°
Resolution: 1920*1800 Full HD IPS
Navigation     GPS+AGPS Navigator
Daul Camera:  Front Camera 8.0M ,13.0M Pixels High definition Back Camera Auto Forcus Sony MX214 1300

Battery: 3000mAH

Size: 152 X 75.5 X 8.9 mm 

12 November 2014

价格无下限:小米或将推出399元4G手机



随着小米与联芯科技合作的落实,小米将推出搭载联芯芯片的手机似乎已经是板上钉钉的事情。而最新的消息显示,小米或将推出内置联芯芯片的399元4G手机。

今天中午,一位网友@手机晶片达人 在微博爆料:“小米准备用联芯1860芯片推出399元移动4G手机。”

根据联芯官网的信息,联芯1860芯片的全称为LC1860,使用28nm工艺制造,集成6颗主频为2GHz的Cortex-A7核心,GPU型号是 Mali-T628MP2,支持双通道LPDDR3内存,2000万像素摄像头。另外还支持GSM/EDGE/WCDMA/TD-SCDMA/LTE FDD/TD-LTE网络,最高可达5模17频,当然,如果小米售价定位在399元的话,则可能采用成本更低的三模方案,即支持GSM/TD-SCDMA /TD-LTE。

事实上,早在今年7月,安兔兔就曾在数据库中发现过一款型号为2014502的小米新机,其屏幕分辨率为720p,内存为1GB,处理器型号为联芯L1960,规格和LC1860差不多。如果该机最终配置真是这样的话,售价399元应该是很靠谱的。


  今年的双11小米手机再度创造奇迹,平面、网媒科技版今晨的头条基本都是高歌小米的战绩,官方最新公开的数字确实让人惊讶,小米双11成功售出116万台手机,总销售额高达15.6亿元,成功蝉联双11手机类销量第一的成绩,其它各类设备的销量同样不俗。

   此外最近关于小米与大唐电信旗下联芯合作的消息亦是热门关注点,业内盛传小米欲借联芯最新LC1860平台推出超低价4G智能手机,售价据说只需399元,日前业内人士手机晶片达人再度就廉价小米手机爆料,399元小米手机明年1月便面世。

   据悉这款399元的超级低价4G手机将于闻泰ODM,外观、硬件等均为闻泰设计,确认会采用联芯科技的LC1860芯片,而LC1860又分三模五模,小米廉价手机初期只支持移动4G/3G/GSM三模,并不具备支持联通4G/3G的能力,后续的升级版可能会采用五模设计。

   小米与联芯在资本层面合作,显然是想从芯片开始降低成本,欲借比红米系列更低价格的产品来提升销量。其实当前MTK平台的399元档的三模4G手机已经不少,但是小米有大家喜欢的MIUI系统,加上品牌影响力,不少业内人士都看好其销量。


11 November 2014

骁龙615/5吋FHD屏,红米二代配置再曝光



关于红米Note的升级版本,我们此前已经有了不少的曝光。但是作为红米系列最先推出的产品,千元级别的红米同样有升级的版本。近日有消息人士指出,这款红米系列的新机,或采用1080P级别分辨率屏幕。

该消息由潘九堂在昨天下午爆出,其本人透漏了更多红米新机的信息。他表示,下一代红米手机配备5.5英寸1080p的消息并不靠谱,合乎逻辑的说法是,下一代红米手机将配备5英寸FHD(1080p)显示屏。

潘九堂表示5英寸是最广泛使用的标准尺寸,也是此次红米2代屏幕提升的基本原因。当然了,和Note系列进行区分也是很重要的一个因素。不过问题来了,以目前红米全线低于1千元的水准,1080P真的靠谱么。
根据此前的消息,红米下一代产品正在准备,其搭载了骁龙615处理器。此外,有消息称该机配备了5.5寸1080p屏,1300万像素摄像头,2GB内存等等,整体来看依旧是一款中端配置级别的产品。

具体到发售方面,目前小米其实还在酝酿一款旗舰配置级别的红米Note新机,整体价格也有所提升。不知道屏幕升级以后的红米2代,会否在价格方面做出调整。

08 November 2014

Jiayu F2 Leakage










F2 similarity to G3

Jiayu F2 4G LTE Features:

OS: Android Kitkat
CPU: MT6582 LTE CPU
RAM     2GB,DDR3
Storage  16GB
Sim Card:  Dual SIM card (Support Dual 4G Network)
Service Provide: Unlocked
Brand:
2G: GSM 850/900/1800/1900MHz
3G: WCDMA 2100MHz
MS mode: WCDMA/GSM
Shell Material    Plastic
Screen: Capacitive Touchscreen, 1280*720 High-resolution Screen
Size:  5 Inch inch
Visible Angle: 178°
Resolution: 1280*720 Full HD IPS
Navigation     GPS+AGPS Navigator
Daul Camera:  Front Camera 8.0M ,8.0M Pixels High definition Back Sony CMOS Camera Auto Forcus

Battery: 3000mAh

小米年底或推联芯LC1860六核红米手机,价格跌破500元


近期消息显示,小米已经成立了自己的芯片公司,将布局手机芯片业,并且该公司目前已经获得了联芯LC1860芯片的授权许可,也就意味着小米将推出搭载这款芯片的手机。

根据联芯之前公布的信息,联芯LC1860芯片采用28nm制程工艺,内置Cortex A7架构六核处理器,大型游戏及多任务,均运行流畅无阻。支持 TD-LTE/LTE FDD/TD-SCDMA/WCDMA/GGE 五模,支持全球漫游,最高下行速度可实现150Mbps,同时支持VoLTE/CSFB/单卡双待,多种语音通话方案。

联芯LC18601860具备领先的LTE SoC芯片架构设计,集成AP与Modem,能大幅提升芯片集成度并降低功耗及成本。同时,1860芯片平台支持Trustzone技术,全面支持 GP和银联的TEE标准,能积极应对日益增长的移动安全需求,配合国家安全战略。

根据业内人士的消息,小米将会与年底前推出搭载这块芯片的新红米手机,价格可能在300—500元之间,将为小米明年冲击1亿出货量效力。

05 November 2014

Jiayu S3/佳域S3








CPU:MT6752 1.7Ghz 八核64bit
Ram:2GB
Screen:5.5"
Display:1920x1080 1080P

30 October 2014

Porting To Mediatek Device

Source: Written by Xtreme Ornob

Official Developer of XVipre™


Tutorial:

ONLY FOR MEDIATEK SoCs
In This Guide You'll Learn..
How to Port ROMs of the Same CPU
And Also..
HOW TO PORT ROM FROM A DIFFERENT SoC
Works for-

MT6589 to MT6577
MT6582 to MT6572
MT6577 to MT6575
Only ICS to ICS & JB to JB
May also work with 4.1 to 4.2
No Need of Source Code

No Need of Kernel Source

No Need of **ANDROID KITCHEN

No Need of LINUX...

Requirements:
* A Brain
* Patience
* Windows XP/7/8
* 7-Zip
* Notepad++
* Bootimg Unpack/Repack Tools for Windows!
* Stock ROM
* And a Little Respect!!

So now Lets Begin...
PORTING For Same SoCs ( Ex: MT6572 to MT6572)
* Replace these from your Stock ROM to the ROM u want to PORT!! Lets Call it "PORT"
FILE LIST FOR REPLACING:

Code:
 *system/vendor
 *system/usr
 *system/lib/modules
 *system/lib/hw
 *system/lib/libncurses.so
 *system/etc/firmware
 *system/etc/vold.fstab
 *system/etc/vold.fstab.nand
 *system/etc/bluetooth
For Fixing Problems...

Code:
 *system/etc/permissions
 *system/etc/security
 *system/etc/audio
 *system/etc/wifi
 *system/lib/drm
 *system/lisystem/lib/soundfx
* Now Replace the Stock Boot.img to Port ROM!
* Now Open The Port ROM folder and go to META-INF/google/android and open updater-script in Notepad++
* Do the same for the Stock ROM
* Now In the Port ROM's Updater Script, find a line that starts with this...
format(".......
and only replace the mmcblk0p.. with the stock one!
* Do the same for this line...
mount("...

Example:
This is the PORT one!!!

Code:
 format("ext4", "EMMC", "/dev/block/mmcblk0p5", "0", "/system");
 mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system");
This is the Stock one!!

Code:
 format("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
 mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");

Now just Replace the "mmcblk0p3" from STOCK to PORT!!
It should look like this:

Code:
 format("ext4", "EMMC", "/dev/block/mmcblk0p3", "0", "/system");
 mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
DO NOT REPLACE THE WHOLE LINE!
* Now go back to the Folder of Port ROM and You'll see 2 folders & 1 file named
-META-INF
-system
-boot.img

* Now Select these three and Click Right Mouse Button and Click on 7-Zip ->> Add to Archive
* Now a dialouge box should appear!
* Configure the Format like This:
Archive format: ZIP

Compression Level : Normal

Compression Method: Deflate

Dictoioany Size: 32k

Word Size 32

* Now Start Zipping and Push the ZIP to your Memory Card
* Go to Recovery >> Install ZIP & Wipe Data
Finished!!
Now was that so hard?? Its a Really Easy thing to d0!!
Now Come to the Hard Part!!
Porting From Different SoCs ( Ex: MT6582 to MT7572 )
Read this carefully & apply the way i say!
* Take the ROM u want to port & name it PORT!
* Take your Stock ROM & Name it Stock
* Now Replace These files from Stock to PORT--

Code:
 *system/vendor
 *system/usr
 *system/lib/modules
 *system/lib/hw
 *system/lib/libncurses.so
 *system/etc/firmware
 *system/etc/vold.fstab
 *system/etc/vold.fstab.nand
 *system/etc/bluetooth
* Now Open build.prop in notepad++ & Search for this line

Code:
ro.mediatek.platform=MT65xx
Now Replace this (MT65xx) with your CPU!!
For Example

Code:
ro.mediatek.platform=MT6572
* Now Go To META-INF/google/android and open updater-script in notepad++
* Add this line between the lines of "set_perm"

Code:
set_perm(0, 0, 0644, "/system/vendor/lib/hw/gralloc.mt65xx.so");
[Replace the mt65xx with your cpu]
Example:

Code:
set_perm(0, 0, 0644, "/system/vendor/lib/hw/gralloc.mt6572.so");
* Now Go back to the Rom folder and Take the boot.img and decompile it with any bootimg-unpack tool!
* Now delete the zimage and rename boot.img-ramdisk to PORT-Ramdisk
* Now Do the Same for Stock boot.img and open the folder named PORT-ramdisk and copy all the fil PORT-[QUOTE]ramdisk to boot.img-ramdisk of your Stock boot.img
* Now Go to boot.img-ramdisk and open init.rc
* Now find these lines and replace with your cpu

Code:
 #Create Chip Property
 on early_property:ro.hardware=mt6582
  setprop ro.mtk.hardware mt6589
  
 on early_property:ro.hardware=mt6589
  setprop ro.mtk.hardware mt6589
example :

Code:
 #Create Chip Property
 on early_property:ro.hardware=mt6582
  setprop ro.mtk.hardware mt6572
  
 on early_property:ro.hardware=mt6589
  setprop ro.mtk.hardware mt6572
* Now Compile your New boot.img and Pack your New ROM and Flash!!
Cheers!!!!
Porting Lewa OS5 ROM:
* Replace These files from Stock to LeWa OS5 ROM

Code:
 *system/vendor
 *system/usr
 *system/lib/modules
 *system/lib/hw
 *system/etc/firmware
 *system/etc/vold.fstab
 *system/etc/vold.fstab.nand
 *system/etc/bluetooth
* Replace Stock boot.img to Lewa OS5 ROM
* Unpack boot.img
* Open init.rc
* Find these lines

Code:
 on early_property:ro.build.type=user
  write /proc/bootprof "INIT: user build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar

 on early_property:ro.build.type=userdebug
  write /proc/bootprof "INIT: userdebug build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar


 on early_property:ro.build.type=eng
  write /proc/bootprof "INIT: eng build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar:/system/framework/emma.jar
* Now Add this line in the end of 1t and 3rd line
:/system/framework/lewa-framework.jar

Example:

Code:
 on early_property:ro.build.type=user
  write /proc/bootprof "INIT: user build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar:/system/framework/lewa-framework.jar

 on early_property:ro.build.type=userdebug
  write /proc/bootprof "INIT: userdebug build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar


 on early_property:ro.build.type=eng
  write /proc/bootprof "INIT: eng build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar:/system/framework/emma.jar:/system/framework/lewa-framework.jar
* Now Compile the new boot.img and Repack your New Lewa OS5 ROM
Porting MiUI ROM
Replace These files from Stock to MiUI ROM


Code:
 *system/vendor
 *system/usr
 *system/lib/modules
 *system/lib/hw
 *system/etc/firmware
 *system/etc/vold.fstab
 *system/etc/vold.fstab.nand
 *system/etc/bluetooth
* Replace Stock boot.img to Lewa OS5 ROM
* Unpack boot.img
* Open init.rc
* Find these lines

Code:
 on early_property:ro.build.type=user
  write /proc/bootprof "INIT: user build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar

 on early_property:ro.build.type=userdebug
  write /proc/bootprof "INIT: userdebug build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar


 on early_property:ro.build.type=eng
  write /proc/bootprof "INIT: eng build setting"
  export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar:/system/framework/emma.jar

* Do the Same as Lewa and add this line in the end of 1st and 3rd line.

Code:
:/system/framework/miui-framework.jar

* Compile the New Boot.img and Repack your new ROM and FLash!!
Cheers!!
Enjoy your New ROM and Give Credits to me for if I Helped you!
For Advanced Users:
PORTING FIX:
Framework:
* decompile framework.jar
* Go to

Code:
\smali\com\mediatek

* Replace All Files from STOCK to this Folder
* Now go to

Code:
\smali\com\android\server

* Replace All Files from STOCK to this Folder
* Compile framework.jar and Push to Device!
* This Should FIX Bootloop, Mms.apk, Phone.apk, Settings.apk, Contacts.apk Force Close
* Fixing Other Problems:
Files related to Specific hardware:
* Replace if Not Working!!
* Camrea:

Code:
\system\lib\libcamalgo.so
\system\lib\libmhaldrv.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcameraprofile.so
\system\lib\libcameraservice.so
* GPS:

Code:
/system/xbin/libmnlp
* Bluetooth & Wifi:

Code:
/system/lib/libbluetooth_mtk.so
/system/lib/libbluetoothem_mtk.so
* Radio:

Code:
\system\lib\libaudio.a2dp.default.so
\system\lib\libaudio.primary.default.so
\system\lib\libaudiocompensationfilter.so
\system\lib\libaudiocustparam.so
\system\lib\libaudioeffect_jni.so
\system\lib\libaudioflinger.so
\system\lib\libaudiosetting.so
\system\lib\libfmar1000.so
\system\lib\libfmcust.so
\system\lib\libfmjni.so
\system\lib\libfmmt6616.so
\system\lib\libfmmt6620.so
\system\lib\libfmmt6626.so
\system\lib\libfmmt6628.so
* For Fixing Wifi & FM-Radio do this!
(NOT NEEDED IN MT6572)

Code:
fmradio.driver.chip=1
(Change it to 3 if yours is MT6628)

Code:
mediatek.wlan.chip=MT6620
(Replace mediatek.wlan.chip=MT6620 to your WLAM Chip Type Ex: mediatek.wlan.chip=MT6628 for MT6628)

Code:
mediatek.wlan.module.postfix=_mt6620
(Replace mediatek.wlan.module.postfix=_mt6620 to your WLAM Chip Type Ex: mediatek.wlan.module.postfix=_mt6628 for MT6628)
* Now open updater-script and Find this line or ADD a New one(If Not Found)!!
symlink("wlan_mt6620.ko", "/system/lib/modules/wlan.ko")
(Replace wlan_mt6620.ko to your WLAM Chip Type Ex: wlan_mt6628.ko for MT6628)