[GUIDE] [PORT] [ROM] All About Mediatek ROM Porting - Miscellaneous Android Development

HOW to Port ROMs...
For Begineers & Advanced Users
Almost Any Device to Any Device!
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-
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)
It Took Me 2Days & 5 Hours to Collect Data & Write this Thing!
I didn't Eat or Drink Water Properly,I Didn't Sleep Properly,
I Created This just for you all!
So That No ONE Ever Says Modontek Again! Its Against Humanity!
Please Value my Work & Do Not Blame me if it Doesnt Work!
I Work Day & Night to Learn More & More!
I Respect All the Developers & Modders of Android
But Some Jerks Just Dont know How to Behave like a Human!
Some Developers Behave like they are the BEST! LOL!
But It's NOT TRUE!
We Can't Be the Best! We Are All the Same!
We all are the Students of XDA-University!
We all use Others Work!
Why Not Work together? Why Not Develop our Knowledge More & More!??
I Don't think I Own any Respect from anyone!
But I Think I Own Respect for my Works & Contributions to Andoid Open Source Project!
I Believe in Humanity! Please Do NOT Copy This and Take Credits!
If This Was Helpful to you in Any Way...
Just Mention my Name in your ROM and Give me Some Credits!
Written by Xtreme Ornob
Official Developer of XVipre™
Coming Soon: Creating Your Own ROMs, Integrating ROM Info & Developer Info into ROM
Sorry for my BAD ENGLISH!!
Like my Page: XVipre ROM
Join our Facebook Group
The Index Project
Thanks to @yuweng for The Tutorial on MTK ROM Porting
Some Points are copied from his post!
Sorry if i am wrong in any way!
Click to expand...
Click to collapse

First of all, thanks for the great guide!
Im on an Alcatel One Touch Fierce OT-7024w MT6589 metropcs. Will this work across chip variations(6589m, 6589t)? Does this work from one phone with the same chipset as another(evolve to fierce)? Is a locked bootloader a problem for this process.

Great stuff. Very helpful.[emoji1]
Sent from my C2305 using Tapatalk

Nice guide tried three roms for port all booted but u should add remedy for different problems like display upside down WiFi/blutooth not switching on audio not coming out network problem etc.
Sent from my A114 using Tapatalk

gracias
he portado Xolo a 600 - i9091 clon pero aparece el logo desaparece nada mas. : Crying:
perdon por mi ingles

Thanks! You should re-arrange the OP so it is easier to read and follow.

very well done.. good information..

Yes it will work! but i dont know about alcatel as it has a "custpack" partition! well good luck!
DNRDustin said:
First of all, thanks for the great guide!
Im on an Alcatel One Touch Fierce OT-7024w MT6589 metropcs. Will this work across chip variations(6589m, 6589t)? Does this work from one phone with the same chipset as another(evolve to fierce)? Is a locked bootloader a problem for this process.
Click to expand...
Click to collapse

Glad u like it!
vneogi199 said:
Great stuff. Very helpful.[emoji1]
Sent from my C2305 using Tapatalk
Click to expand...
Click to collapse

Well glad it worked! and i already added the fix problems section! and i dont think anyone will face the "upside down display" problem! well thanks for feedback!
kuldeepraj said:
Nice guide tried three roms for port all booted but u should add remedy for different problems like display upside down WiFi/blutooth not switching on audio not coming out network problem etc.
Sent from my A114 using Tapatalk
Click to expand...
Click to collapse

Bro....i am from bangladesh! and i dont know what u r talking about! but if u could kindly speak english or something???
kasuyin said:
gracias
he portado Xolo a 600 - i9091 clon pero aparece el logo desaparece nada mas. : Crying:
perdon por mi ingles
Click to expand...
Click to collapse

I find it really hard to post on xda! u know all the work on tags! i am not good at posting! do you know someway i can see what i do when posting? i actually write all these in notepad and then copy-paste here & edit the lines & make em big & etc etc...
but i cant do it right! :'( i dont know man! its all a big mess!
iZLeeP said:
Thanks! You should re-arrange the OP so it is easier to read and follow.
Click to expand...
Click to collapse

Thnx Bro! but i hope xda makes me a senior member soon! u know i am not that junior!
AshuGite said:
very well done.. good information..
Click to expand...
Click to collapse

Xtreme.Ornob said:
I find it really hard to post on xda! u know all the work on tags! i am not good at posting! do you know someway i can see what i do when posting? i actually write all these in notepad and then copy-paste here & edit the lines & make em big & etc etc...
but i cant do it right! :'( i dont know man! its all a big mess!
Click to expand...
Click to collapse
Better do it on word so you can preview changes you made on it.

Can i port rom mt6589 to mt6572 using the process?
Sent from my A63 using xda app-developers app

bro i know how hard is to write a post.i really appreciate your work.u are best example for humanity..ya u are rigth no one is best/perferct. i truly motivated by u

Xtreme.Ornob said:
Bro....i am from bangladesh! and i dont know what u r talking about! but if u could kindly speak english or something???
Click to expand...
Click to collapse
I have a clone i9091 and I want port rom the xolo600 but only reaches the logo. : Crying:: Crying:

bro im porting mt6589soc to mt6577soc i do carefully all steps but stuck on logo then white screen again same happen.
and bro i copy and replace all ramdisk file of mt6589 to mt6577 ramdisk and compile boot.img with android kitchen
please please bro help
sorry for tag u @Xtreme.Ornob
i truly appreciate ur work... :good::good::good:
---------- Post added at 08:19 AM ---------- Previous post was at 07:56 AM ----------
sir my both stock and port rom not having such name file system/lib/libncurses.so
and sir in ramdisk int.rc i have only this line
on early_property:ro.hardware=mt6589
setprop ro.mtk.hardware mt6589
please help

no line in init.rc
There is no line named #create chip...
there is only -on early_property:ro.hardware=mt6589
setprop ro.mtk.hardware mt6589
and
there is no folder named hw in my vendor/lib
but hw folder and gralloc.mt6572 is in libs folder
I got stuck in the boot_logo

Will it help with Pics & Text Sizes & Text Colors??
iZLeeP said:
Better do it on word so you can preview changes you made on it.
Click to expand...
Click to collapse

Related

[GUIDE] How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs [Update: Sept.25.2012]

Code:
/*
* ~ Please READ ME ~
*
* I do not guarantee any successful porting. I am not responsible
* for bricked devices, dead SD cards, or a broken device. [B]YOU[/B] are
* choosing to make these modifications, and if you point the finger
* at me for messing up your device, I will laugh at you. But I will try
* my best to explain all the necessities, so you won't mess up your Device.
*
* ~ END OF AGREEMENT ~
*/
Before we start, let's read the Title of this Guide. Notice it says: based
This means, if you do not have a GB/ICS/JB already compiled for your device, then this Guide is useless for you.
Android Source | Compile GB | Compile ICS | Compile JB ~ Thanks dastin1015 |- Building/Compiling - Durations
Before you a port a ROM, make sure you asked permission from the Developer!
This Guide applies the same principle for porting the following: Sense, Lewa OS, JoyOs, MIUI, LiGux OS, etc...
What you'll need:
WinRAR/7zip
Notepad++ (When developing, always use this)
Android SDK (For Logcatting & DDMS)
Some basic knowledge about Android
If you are on Linux/Unix/BSD use your favorite Archiving Tool & Text Editor.
Notes:
I will be referring to the following:
BASE = The GB/ICS/JB ROM made for your Device only.
PORTED = The ROM you are trying to port from.
BASE and PORTED must be the same CPU. e.g. ARMv7, ARMv6, ARMv5
You must have the same settings in Notepad++ like mine.
Ignore the procedure, if the file or folder is not present!
BASE & PORTED should be the same Android version.
If you are porting a custom GB ROM, then use a GB BASE, the same goes for ICS and JB
Make sure both BASE & PORTED are deodexed (It's hard to port an odexed ROM)
Final ROM is inside PORTED Folder
(Don't get confused! This is a Major change from the previous Guide because this method is a lot faster and easier)
Inside PORTED:​
Remove kernel:
boot.img | zImage | kernel.sin | etc...
Remove the following inside /system:
cameradata
tts
usr
vendor
firmware
modules
wifi
Now you get 2 options:
Delete bin & xbin & lib folder, but keep libandroid_runtime.so inside /system/lib
Keep bin & xbin & lib folder
Explanation:
If PORTED has no tweaks or addons to those folders.
If PORTED has tweaks and addons.
Remove every folder inside /system/etc except:
init.d
permissions
license
Remove the following inside META-INF:
CERT.RSA
CERT.SF
MANIFEST.MF
Remove: META-INF/com/google/android/update-binary​
Inside BASE:​
Move kernel to PORTED:
boot.img | zImage | kernel.sin | etc...
Delete libandroid_runtime.so inside /system/lib
Move the following inside /system to PORTED:
(If prompted, select YES to copy and Replace all)
cameradata
bin
lib
tts
usr
vendor
firmware
modules
wifi
xbin
(If prompted, select YES to copy and Replace all)
Move everything inside /system/etc
To: PORTED's /system/etc
(If prompted, select YES to copy and Replace all)
Move: META-INF/com/google/android/update-binary
To: PORTED's META-INF/com/google/android/
For ICS & Newer:
Move the following inside /system/media to PORTED's media:
LMprec_508.emd
PFFprec_600.emd
build.prop​
Inside PORTED:​Open /system/build.prop
Copy & Replace the following:
ro.modversion
ro.cm.version
ro.config.ringtone
ro.config.notification_sound
ro.config.alarm_alert
ro.config.sms_received_sound
ro.config.sms_delivered_sound
persist.sys.themeId
persist.sys.themePackageName
and anything similar to that, to: BASE's build.prop
For MIUI:
Add & Make sure the following values are like this:
ro.build.id=MIUI
ro.build.display.id=MIUI x.x.x
ro.build.version.incremental=x.x.x
ro.config.ringtone=MI.ogg
For Lewa OS:
Add & Make sure the following values are like this:
ro.build.display.id=LeWa_ROM_DeviceNickname_xx.xx.xx
ro.lewa.version=LeWa_ROM_DeviceNickname_xx.xx.xx
ro.lewa.device=DeviceNickname
ro.lewa.swapper.part_path=PORTED's_Value
ro.lewa.swapper.flash_swappiness=PORTED's_Value
ro.lewa.swapper.sd_swappiness=PORTED's_Value
ro.error.receiver.system.apps=com.lewa.fc
ro.error.receiver.default=com.lewa.fc
Make sure the following is for your Device:
rild.libpath=
rild.libargs=
Inside BASE:​Open /system/build.prop
Highlight from: ro.build.tags=
to: # ADDITIONAL_BUILD_PROPERTIES
Shown in this picture
Copy & Replace that highlighted part to: PORTED's build.prop's highlighted part
Copy everything from: # ADDITIONAL_BUILD_PROPERTIES
To: the end of the file
Paste it to PORTED's build.prop
Shown in this picture
For XPERIA devices:​The whole build.prop is untidy and filled with tweaks and addons.
To edit an XPERIA build.prop you really just need to use your common sense.
Make sure you follow the above and just decide on your own on what to do
For HTC devices (Sense):​The whole build.prop is filled with tweaks, addons and extra libs values.
To edit an HTC build.prop you really just need to use your common sense.
Make sure you follow the above and just decide on your own on what to do ​
updater-script​
Inside BASE:​Move the following, to PORTED:
(If prompted, select YES to copy and Replace all)
META-INF/com/google/android/update-binary
META-INF/com/android/metadata
META-INF/com/android/otacert
Open: META-INF/com/google/android/updater-script
Replace the following values, to PORTED:
mount("xxxxxx");
format("xxxxxx");
retouch_binary
The installation of the kernel (Something like: assert(package_extract_file("boot.img",)
Take note of the added set_perms & set_perm_recursives that PORTED added. Then replace all set_perm and set_perm_recursive from BASE to PORTED. Put back in the noted set_perms & set_perm_recursive you wrote down, to PORTED's updater-script
For ICS & Newer itself:​
If the updater-script in PORTED is modded to have tweaks & addons do the set_perms procedure above
Now use BASE's entire META-INF Folder. Copy it to PORTED
For MIUI v4:​Add the following values to PORTED:
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
For AROMA Installer:​It's actually too hard & time consuming to explain on how to make the script work on your Device when it came from another.
So it's best to use BASE's META-INF folder, rather than try to make the AROMA Installer work on your Device. (Becuase it will be time consuming)​
Porting from a different Manufacturer​
If you are porting from a different manufacturer like, HTC or Sony, you have to check the kernel from them.
Unpack the kernel from PORTED
Unpack your Device's kernel
Open PORTED's init.rc
Replace the BOOTCLASSPATH from PORTED's init.rc to BASE's init.rc
Compare the two files, and addon to your Kernel's init.rc
Packup/Repack your Kernel
Porting Wallpapers | Lockscreen Wallpapers | bootanimation​
Usually you get a wallpaper/bootanimation that doesn't fit your device. Here's a quick tutorial on how to port it to your device.
Download & Install FreeImageConverter then launch it.
For Wallpapers & Lockscreen Wallpapers:​
Click Add Folder... and add the folder were the wallpapers are
Then click Advanced Convert...
Select Exact Size and set the image quality to 100
Set your Width and Height resolutions for your device.
Uncheck Add "Converted by www.freeimageconverter.com"
Select Leave the same file name and leave the Postfix & Prefix empty. Then set your output in a folder.
For bootanimation:​
Extract /system/media/bootanimation.zip OR /data/local/bootanimation.zip OR /system/customize/resource/bootanimation.zip (For Oxygen ROM, the bootanimation is built into the framework-res)
Do the steps above
Move the new resized folder(s) into your bootanimation workspace
Edit the desc.txt to match your device resolutions
Zip the contents ( folder_name desc.txt )
Set compression method to Store
Delete the extracted bootanimation files
Make sure this new bootanimation.zip is in PORTED
Logging & DDMS​
This is very important if your a developer in the Android world. These tools help you debug your device to search for errors or see which processes are running.
Android Debug Bridge (ADB)​Tutorial - How to Logcat
Dalvik Debug Monitor Server (DDMS)​Tutorial from Android
If you want me to help you, don't give me a Logcat from ADB. Instead, give me a screenshot of your DDMS.​
Review
Make sure you did everything inside PORTED first, then work your way up/down to BASE.
Did you replace Kernel?
Is libandroid_runtime.so from PORTED?
Did you edit the updater-script, format & mount values?
Make sure dalvik.vm.heapsize is BASE's value inside build.prop
Make sure build.prop is mostly for your Device
If the Port doesn't boot, try using your own META-INF folder. But backup the previous
Sources
[GUIDE] How to port MIUI v4 to your Device - proxuser
[GUIDE] How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs - Peteragent5
Credits & Thanks to
proxuser
nims11
dhk.-
Lens_flare
SpaceCaker
fundoozzz
Delanoister
TeamCooper
Happy porting! :laugh:
Frequently Asked Questions
Q: How do you port a higher CPU ROM to my lower CPU device?
A: P.M me or any big-name developers. You must already know what to do. The person you P.M will give you extra info...
Q: Is it possible to port a lower CPU ROM to my higher CPU device?
A: I think it'll work (But why would you do this). If it doesn't boot try changing the DPI values in the build.prop
Q: How do I make a bigger DPI ROM work on my smaller DPI device?
A: Resize all PNGs in every app & framework-res using Android Resizer Tool
Q: Can I Port a smaller DPI device to my device?
A: Yes. It probably won't run & it wouldn't look good if you did. The icons would be small or if you resized it, the icons would be blurry.​
You say that we can use any ROM as BASE but you don't specify what to use as PORT.
Can you please clarify that?
there is no /data folder in cyanogen mod from galaxy mini.. wat to do now??
i m porting cyano from mini to galaxy y
Peteragent5 your arm7 port rom problem solve from this way?
FeralFire said:
You say that we can use any ROM as BASE but you don't specify what to use as PORT.
Can you please clarify that?
Click to expand...
Click to collapse
You can port any Rom as long as it's based on CM7/GB/Stock Rom, the same CPU (Armv6, Armv7, Armv5) as your BASE, and it's best to port a Rom from the same manufacturer, if not, you can still do it, just change BOOTCLASSPATH
hell_lock said:
there is no /data folder in cyanogen mod from galaxy mini.. wat to do now??
i m porting cyano from mini to galaxy y
Click to expand...
Click to collapse
If there is no data then it's fine to not include it
cips gokhle said:
Peteragent5 your arm7 port rom problem solve from this way?
Click to expand...
Click to collapse
Lol. No not yet
I want to port CM7 from LG O2X to Samsung Galaxy R (They both have the same CPU- Tegra 2).
Can I use the official LG O2X CM7 ROM and the stock Galaxy R ROM?
Or should I use the Galaxy S2 CM7 ROM?
Can we port Sense to Gio using this guide?
I have a galaxy tab p1010. That have ARM8.
This means that wont work?
Peteragent5 said:
Now open Notepad++ and open the build.prop in PORTED
Also open the build.prop in BASE, so now you have them side by side in the tabs
In PORTED, edit the build.prop to match with your device!
NOW This is very important!
Your
ro.build.description=
and
ro.build.fingerprint=
must be the same same as the build.prop in BASE!
If not, your Rom will not boot!
Save the Build.prop in PORTED and close NotePad++
Click to expand...
Click to collapse
Why are we editing the build.prop in the PORT, shouldn't we edit it in BASE?
I finished this and the ROM won't boot.
I tried the Base as a Sense 3.0 (2.3.4 Gingerbread ROM)
porting a Sense 4.0 (4.0.3 IceCreamSandwich ROM)
FeralFire said:
I want to port CM7 from LG O2X to Samsung Galaxy R (They both have the same CPU- Tegra 2).
Can I use the official LG O2X CM7 ROM and the stock Galaxy R ROM?
Or should I use the Galaxy S2 CM7 ROM?
Click to expand...
Click to collapse
They must both be CM7
ulasates said:
Can we port Sense to Gio using this guide?
Click to expand...
Click to collapse
Sense is quite hard, to be honest. I'm still trying to figure out how I should do it
samcortez said:
I have a galaxy tab p1010. That have ARM8.
This means that wont work?
Click to expand...
Click to collapse
As long as both PORTED and BASE is the same CPU, this guide will work.
FeralFire said:
Why are we editing the build.prop in the PORT, shouldn't we edit it in BASE?
Click to expand...
Click to collapse
Because. The build.prop in PORTED has more values than than the one in BASE. So if we use BASE's Build.prop, you'd have to copy over everything that was in the PORTED (The extra values, like tweaks and some more stuff)
Adjust said:
I finished this and the ROM won't boot.
I tried the Base as a Sense 3.0 (2.3.4 Gingerbread ROM)
porting a Sense 4.0 (4.0.3 IceCreamSandwich ROM)
Click to expand...
Click to collapse
Sense is hard to port is you are from a different Manufacturer.
But if you are not, this is what you need to do:
Your BASE needs to be an ICS Base in order to port the Sense 4.0
Peteragent5 said:
Sense is hard to port is you are from a different Manufacturer.
But if you are not, this is what you need to do:
Your BASE needs to be an ICS Base in order to port the Sense 4.0
Click to expand...
Click to collapse
I have a Sense 3.6 4.0.3 Base.
or Should I use a pure 4.0.3 Base?
Which is better?
Adjust said:
I have a Sense 3.6 4.0.3 Base.
or Should I use a pure 4.0.3 Base?
Which is better?
Click to expand...
Click to collapse
Try sense 4.0.3 first then pure
unwritten sentance
spacecaker said:
Try sense 4.0.3 first then pure
unwritten sentance
Click to expand...
Click to collapse
I want a 100% answer if possible don't have time to waste.
Thanks for posting though.
Adjust said:
I want a 100% answer if possible don't have time to waste.
Thanks for posting though.
Click to expand...
Click to collapse
You should use 4.0.3 as base
Peteragent5 said:
You should use 4.0.3 as base
Click to expand...
Click to collapse
Sense 3.6 (4.0.3) base?
or Pure 4.0.3 base.
Woulden't using Sense 3.6 as a base be good since it's Sense and ICS so is Sense 4.0
Peteragent5 said:
Because. The build.prop in PORTED has more values than than the one in BASE. So if we use BASE's Build.prop, you'd have to copy over everything that was in the PORTED (The extra values, like tweaks and some more stuff)
Click to expand...
Click to collapse
Then when you finish your edit on ported you should replace build.prop from PORTED to BASE, isnt¿?
BTW excellent guide!
Adjust said:
Sense 3.6 (4.0.3) base?
or Pure 4.0.3 base.
Woulden't using Sense 3.6 as a base be good since it's Sense and ICS so is Sense 4.0
Click to expand...
Click to collapse
Yup. Sense 3.6. As long as both BASE and PORTED are same (4.0.3)
ocovarr112 said:
Then when you finish your edit on ported you should replace build.prop from PORTED to BASE, isnt¿?
BTW excellent guide!
Click to expand...
Click to collapse
Yup when you finished build.prop in PORTED, you copy that build.prop into BASE
And your final Rom is BASE

[DEV][Kernel]Porting kernel 3.0.8

!!!FIRST READ THEN POST!!!​
I am not a programmer so do not shout at me , I try to help you gather as much information as possible. Of course, I trying port kernel by myself but is going very slowly.
I decided to start this thread and share with you information that I managed to collect. Topic applies to porting the kernel 3.0.8 for i9001.
I found a phone that has the same motherboard, CPU and GPU as the i9001 and already got an official kernel 3.0.8.
Why this kernel is good for us? - because has already almost all drivers needed by i9001 so porting will be easier.
Why we need it - better battery life, better cooperation with ICS/JB, better speed, new possibilities? And why not?
- What needs to be done?
- include and port file from 2.6.35.X - arch/arm/mach-msm/board-ariesve.c
- include/find missing drivers for i9001
- Links:
i9001 spec - Samsung Galaxy S Plus
U8860 spec - Huawei Honor
Kernel sources
Thread - Huawei U8860 Honor / Honour / Glory - Index
How to build kernel:
This howto is working only with 2.6.35.X kernel, when this project will be finished will add HOWTO for 3.0.8
You need linux machine, i don't know it is possible on Windows and if so i don't help you with that!!!
1. Download toolchain.
Download toolchain and extract it to /opt/ directory.
Should looks like:
Code:
/opt/arm-eabi-4.4.3/
2. Set up evn.
Edit your:
Code:
~/.bashrc
file and add at the end of file this two rows:
export CROSS_COMPILE=/opt/arm-eabi-4.4.3/bin/arm-eabi-
export CCOMPILE=/opt/arm-eabi-4.4.3/bin/arm-eabi-
Click to expand...
Click to collapse
3. Download kernel - 2.6.35.14.
You can download kernel sources from Arco, Skywalker01 or Vitaliy_y repo, and extract to ~/kernel/, this kernels has already needed drivers etc.
4. Compile kernel:
When i'm compiling kernel i'm doing it in this way:
make ARCH=arm mrproper -j3
make ARCH=arm clean -j3
adb pull /proc/config.gz ./
gzip -d ./config.gz
mv ./config ./.config
make ARCH=arm oldconfig -j3
make ARCH=arm menuconfig -j3
make ARCH=arm -j3
Click to expand...
Click to collapse
5. Output files.
mkdir -p ../kernel-out/modules
cp arch/arm/boot/zImage ../
find ./ -name "*.ko" -exec cp {} ../kernel-out/modules \;
Click to expand...
Click to collapse
6. Create boot.img
split_bootimg.pl boot.img
mkdir ramdisk
cd ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i
Click to expand...
Click to collapse
- Swap kernel and modules and then:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Click to expand...
Click to collapse
- Creat boot.img
mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz --base 0x00400000 -o boot.img
Click to expand...
Click to collapse
Download: split_bootimg, mkbootimg
Extract files here /usr/local/bin and set permissions to 755.
What i have done:
1. Added board-ariesve.c here:
arch/arm/mach-msm/board-ariesve.c
2. Included Ariesve board to Kconfig and Makefile.
3. Added missing files:
include/linux/fsa9480.h
arch/arm/mach-msm/include/mach/msm_reqs.h
Compilation error:
arch/arm/mach-msm/board-ariesve.c: In function 'pm8058_gpios_init':
arch/arm/mach-msm/board-ariesve.c:329: error: variable 'sdcc_det' has initializer but incomplete type
arch/arm/mach-msm/board-ariesve.c:330: error: unknown field 'direction' specified in initializer
arch/arm/mach-msm/board-ariesve.c:330: warning: excess elements in struct initializer
error, forbidden warning: board-ariesve.c:330
make[1]: *** [arch/arm/mach-msm/board-ariesve.o] Error 1
Click to expand...
Click to collapse
Cool ! Thank you !
oisis said:
I am not a programmer so do not shout at me , I try to help you gather as much information as possible. Of course, I trying port kernel by myself but is going very slowly.
I decided to start this thread and share with you information that I managed to collect. Topic applies to porting the kernel 3.0.8 for i9001.
I found a phone that has the same motherboard, CPU and GPU as the i9001 and already got an official upgrade to ICS.
Why this kernel is good for us? - because has already almost all drivers needed by i9001 so porting will be easier.
What needs to be done?
- include board-ariesve.c - Board spec.
- include missing drivers for i9001
Links:
i9001 spec - Samsung Galaxy S Plus
U8860 spec - Huawei Honor
Kernel sources
Thread - Huawei U8860 Honor / Honour / Glory - Index
Click to expand...
Click to collapse
page not found - Huawei U8860 Honor / Honour / Glory - Index
What advantages will kernel 3.x have for us?
Sent from my GT-I9001 using XDA
chasemyass said:
page not found - Huawei U8860 Honor / Honour / Glory - Index
Click to expand...
Click to collapse
Fixed.
EternalFame said:
What advantages will kernel 3.x have for us?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
New drivers, better cooperation with ICS?
Awesome project!
What's the current status? How far does your current compile boot?
oisis said:
Fixed.
New drivers, better cooperation with ICS?
Click to expand...
Click to collapse
Kay
Just asked out of interest
Does it also bring some speed?
Sent from my GT-I9001 using XDA
EternalFame said:
Kay
Just asked out of interest
Does it also bring some speed?
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
Not to much but can bring some. Also maybe bring better battery life, new possibilities.
hey about the jelly bean thing,i sent you the nexus boot.img with modified init.rc and init.traces .rc. did you try comparing them with some tool? like winmerge.
Doomsday94 said:
hey about the jelly bean thing,i sent you the nexus boot.img with modified init.rc and init.traces .rc. did you try comparing them with some tool? like winmerge.
Click to expand...
Click to collapse
First we need kernel then boot.img and init.rc scripts.
oisis said:
First we need kernel then boot.img and init.rc scripts.
Click to expand...
Click to collapse
you mean the 3.0 kernel?
Good luck, oisis. I do not know if this will help with something, but the dev tom3q, wrote kernel 3.0 for i5700 spica. Maybe he has some tips .....
Doomsday94 said:
you mean the 3.0 kernel?
Click to expand...
Click to collapse
Yes.
drummer1839 said:
Good luck, oisis. I do not know if this will help with something, but the dev tom3q, wrote kernel 3.0 for i5700 spica. Maybe he has some tips .....
Click to expand...
Click to collapse
Thanks for link.
PDK
Good to see progress.. By the way, you guys might already know this, but Google release a "Platform development Kit" in Google IO 2012, to help developers and manufacturers port new Android OSs (like Jelly Bean) to their devices.
I found the link below, maybe it can help bringing Jelly Bean to our device in the future :silly:
http://www.kandroid.org/online-pdk/guide/index.html
Thanks
So guys a quick review.
Oisis and me are both working on kernel now.
We are using parts of the Huawei honor kernel to make ICS camera work. But please be patient that it will take a while till we finish. and we dont give guarantee that ALL will work CORRECTLY then.
But for you guys, to see the status of developement and we are not bluffing ^^
Here you see the drivers which we'll use in new kernel.
https://github.com/dzo/kernel_huawei/tree/master/drivers
****Update Status****
Will be new in kernel:
- Changing drivers for radio (maybe will work then) -> https://github.com/dzo/kernel_huawei/tree/master/drivers/media
- Changing wifi drivers for better wifi thetering performance
- Changing Audio/Video drivers for ICS Camera -> https://github.com/dzo/kernel_huawei/tree/master/drivers/video
- And other little things will be changed (better battery usage -> new drivers/ better performance ... )
- Will change GPU drivers too -> https://github.com/dzo/kernel_huawei/tree/master/drivers/gpu
As i see those drivers of huwai are the same as Samsung galaxy s plus?
Sent from my GT-I9001 using xda app-developers app
Raimon93 said:
As i see those drivers of huwai are the same as Samsung galaxy s plus?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Its mostly the same Hardware, so we can use many things of that device, because it got official ICS with everything working!
Keinbockwurst said:
Its mostly the same Hardware, so we can use many things of that device, because it got official ICS with everything working!
Click to expand...
Click to collapse
That's true, because that device got a official ICS update and the hardware Is nearly the same we can use its drivers and we think it will work.
Kernel will be finished to try in this week I think...
Sent from my GT-I9001 using xda app-developers app

[DEV] How to build cm7 for galaxy y (GT-S5360) ! Ubuntu 32 bits !

Requirements :
OS linux Ubuntu 12.04 32bits
2Gb RAM with 3Gb swap or above
Processor dual core or above
120Gb Harddisk or above
Fast internet connection ( i have no this )
First download this file
Installer SDK and Build packages by squadzone modified for me
you will get installerBuildRomGalmin.sh , run this file via Terminal on Ubuntu!
Code:
chmod a+x ~/installerBuildpackages.sh
installerBuildpackages.sh
Create the Directories
You will need to set up some directories in your build environment.
To create them:
mkdir -p ~/bin
mkdir -p ~/android/system
Install the Repository
Enter the following to download make executable the "repo" binary:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
NOTE: You may need to reboot for these changes to take effect.
Now enter the following to initialize the repository:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j16
Device repo !
clone its
choose branch master
put on device tree or replace totoro folder on device tree
(/device/samsung/totoro)
Vender folder clone its
pu on vendor folder !
(/vendor/samsung/totoro)
Download RomManager
NOTE: This only needs to be done when an update to RomManager is released. If you are-up-to date, you may skip to Building CyanogenMod.
Download RomManager which is needed by the build:
~/android/system/vendor/cyanogen/get-rommanager
Configure Build & Compile
Now, the environment must be configured to build and the ROM compiled, from code, for the Galaxys2.
. build/envsetup.sh && brunch totoro
Notes :
based on tutorial for galaxy mini by squadzone
the device repo created for me ( add credits if you use its )
sorry bad english !
changelog :
1.0
-initial tutorial for cm7 galaxy y ( may need some modifications! )
reserved for more updates if necessary !
Thanks for this buddy :good:
OFF : Any news about CM9 ?
wow.. reserved sir whitexp.. long time no post? D
I WIIL TRY IT BOR
By SOMKLL
But this Cyanogen has the same bugs,right?
whitexp what about cm9 ? when will u continue xD
and great guide
This message is COPYRIGHTED to me and stolen from:My post
Cyanogen 7/9 only get developed again when the gpu driver become released
Awesome tutorial sir...
Just one question...if we still have GPU restrictions while compiling CM7/9/10, then what is the use of the tutorial? Is there any update I should be aware of?
I'm not at all disrespecting OP's efforts...I respect him...he is doing commendable job for this device..hat's off! this question is just out of curiosity!
everyone needs brodcom drivers,without it nothing is possible.
PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Well it's still possible to boot it, so yeah. It's a handy tutorial, LEARN to appreciate guys! That's the reason why SGY devs are leaving, 1 by 1, because of you people that whine! Thank them for the effort!
PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Without this kind of tutorial and with gpu drivers will you make cm7 for sgy????
Awesome tutorial sir!!
Tutotial is good.no doubt.I said drivers are a stumbling block.
PREMOLIKES said:
Tutotial is good.no doubt.I said drivers are a stumbling block.
Click to expand...
Click to collapse
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Mohamed.Anwar said:
Thanks for this buddy :good:
OFF : Any news about CM9 ?
Click to expand...
Click to collapse
what gaming rom r using
Exellent tut buddy.:thumbup::thumbup:
sent while doin' some burnouts
hell_lock said:
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
cosminx13 said:
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
Click to expand...
Click to collapse
A suggestion from me.you can use both os like dualboot.for info about this try google
MANY GREEEEETZ!!!

[wip] mtk6577 alps sources and kitkat dev

first off all i dont know where to start such thread so moderate can move it to whatever place they thought of
now i had some good news and not some good news
good news is i had found complete mtk sources and compiled rom out of it succesfully
and not so good news is
sources are of 4.1.2 and im new to this so i need developers help
i'm posting the steps that i had followed for compiling
DOWNLOAD
1. download and install ubuntu if not installed already
2. download sources http://pan.baidu.com/wap/link?uk=2869617224&shareid=4195729301&third=0
3. download jdk-6u29-linux-x64.bin (this worked for me)
SETTING UP MACHINE
1. open terminal and type
2.
Code:
sudo apt-get install flex bison gperf build-essential curl zlib1g-dev g++-multilib g++-4.4-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z1-dev wine mingw32 tofrodos libxml2-utils
3. after it finishes installation of required pakages type
Code:
cd /usr/bin
sudo mv gcc gcc.bak
sudo ln -s gcc-4.4 gcc
sudo mv g++ g++.bak
sudo ln -s g++-4.4 g++
4. now setup java change to directory where jdk-6u29-linux-x64.bin resides and extract using
Code:
./jdk-6u29-linux-x64.bin
cammand in terminal
make sure permission of jdk-6u29-linux-x64.bin is executable
5. type following in terminal
Code:
gedit ~/.bashrc
and following lines to bashrc in gedit
Code:
#java Settings
export JAVA_HOME=~/toolchain/jdk1.6.0_29
export JRE_HOME=JAVA_HOME/jre
export CLASSPATH=$JAVA_HOME/lib:$JRE_HOME/lib:$CLASSPATH
export PATH=$JAVA_HOME/bin:$JRE_HOME/bin:$PATH
make sure to setup up path correctly in my case java is exracted in toolchain folder yours may differ
6 type follwing in terminal
Code:
sudo mv /bin/sh /bin/sh.bak
sudo ln -s /bin/bash /bin/sh
BUILDING ROM
1. extract sources( in my case in alps folder at home)
2. open mbldenv.sh in root directory of extracted folder and edit java path as done before
3. open terminal emulator
and type
Code:
./mk -h for all commands
and type
Code:
./mk -o=TARGET_BUILD_VARIANT=user mbk77_tb_jb n
(for a complete new build of mbk77_tb_jb project)
###########################################################
now i request all developers to colabrate and make kitkat possible
im trying my bit but new to all this and mtk sources are complete mess
if you got any problem or error im here to help to best of my possibilities
screenshot of out folder and generated build.prop is attached
and dont ask me to upload anything as my net speed is slow it takes 7 days to download sources
Great Initiative Buddy
All the best :good:
got all imgs compiled without any errors ??
Sent from my XOLO A700 using Tapatalk
AnoopKumar said:
got all imgs compiled without any errors ??
Sent from my XOLO A700 using Tapatalk
Click to expand...
Click to collapse
Yes buddy no error sources are complete but a big mess too
Sent from my NeXus using xda app-developers app
I don'y have the device but my neighbour has since i can't use his phone all day i can just help by making device tree for CM11 and try and add patches which were made for MT6589
I an not sure if this can work the only thing is @bindassdost you sync the sources and try we can make a organisation on Github and submit the patches
GuneetAtwal said:
I don'y have the device but my neighbour has since i can't use his phone all day i can just help by making device tree for CM11 and try and add patches which were made for MT6589
I an not sure if this can work the only thing is @bindassdost you sync the sources and try we can make a organisation on Github and submit the patches
Click to expand...
Click to collapse
brother i cant sync sources my net is slow (256kbps) only it took me 7 days to download 2.7gb compressed souorces i dont know how long it will take to sync 9gb sources to github thats why i wrote everything that i did so that someone with good speed do the task
thats the reson i cant procede further as cm sources are also huge arround 10gb but i can help if someone else do this
bindassdost said:
brother i cant sync sources my net is slow (256kbps) only it took me 7 days to download 2.7gb compressed souorces i dont know how long it will take to sync 9gb sources to github thats why i wrote everything that i did so that someone with good speed do the task
thats the reson i cant procede further as cm sources are also huge arround 10gb but i can help if someone else do this
Click to expand...
Click to collapse
GuneetAtwal said:
I don'y have the device but my neighbour has since i can't use his phone all day i can just help by making device tree for CM11 and try and add patches which were made for MT6589
I an not sure if this can work the only thing is @bindassdost you sync the sources and try we can make a organisation on Github and submit the patches
Click to expand...
Click to collapse
i can help u with that i have downloaded the synced sources..and will upload if the phone boots up...
i am just thing of how to build it as it is not supported...
just help me with that and the recovery which will reqire selinux..
,[email protected]
also i have cloned the kernal sources of your bindassboost..is it ok..i did not have any other souces of kernal..
well my cm 11 sorce downloading is complete around 13.54 gb..
plus my net speed is 2 mbps..
Avenger4droid said:
i can help u with that i have downloaded the synced sources..and will upload if the phone boots up...
i am just thing of how to build it as it is not supported...
just help me with that and the recovery which will reqire selinux..
,[email protected]
also i have cloned the kernal sources of your bindassboost..is it ok..i did not have any other souces of kernal..
well my cm 11 sorce downloading is complete around 13.54 gb..
plus my net speed is 2 mbps..
Click to expand...
Click to collapse
First try the build output coming from these sources as they will be 4.1.2 so you don't require any special Recovery for now so try that
GuneetAtwal said:
First try the build output coming from these sources as they will be 4.1.2 so you don't require any special Recovery for now so try that
Click to expand...
Click to collapse
i havent made the output file yet...
cause i dont know..
i have cloned the sources ....but i m confused how to build ???
is there a folder called "protect" in "source/mediatek/"
Sent from my XOLO A700 using Tapatalk
probably yes...cause i had one when i downloaded the sources...
also is there a vender folder in mediatek...???
So now Can WE Expect Kitkat For CAnvas2 ... Don't know When Micromax Gonna Release It .. @bindassdost
I think these are MT8377 sources :/
Can't work on it without a device to test.
Sent from my C2105 using Tapatalk
varun.chitre15 said:
Can't work on it without a device to test.
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
Hi sir, its good to see you back.....:victory:if you are sure(i mean undertaking cm development) we shall start a fundraiser thread if you wish to have a device
varun.chitre15 said:
Can't work on it without a device to test.
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
Nice See You varun.chitre15 Buddy........
hello sir..
varun.chitre15 said:
Can't work on it without a device to test.
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
thank you sir for returning sir...i am very grateful to you...
i have downloaded cm 11 sources and also made the evironment for developing...
all i need is ur help to compile it as i dont have complete device trees..and kernal sources...
also i have not made cm for unsupported device..
your help is very important and gratefull to me..
regards
Avenger4droid
Avenger4droid said:
thank you sir for returning sir...i am very grateful to you...
i have downloaded cm 11 sources and also made the evironment for developing...
all i need is ur help to compile it as i dont have complete device trees..and kernal sources...
also i have not made cm for unsupported device..
your help is very important and gratefull to me..
regards
Avenger4droid
Click to expand...
Click to collapse
tHATS fANTASTIC bROTHER... =
bindassdost said:
(...)
good news is i had found complete mtk sources and compiled rom out of it succesfully
(...)
Click to expand...
Click to collapse
Hi
You do know that those sources aren't for MT6577 ?
They are for MT8377, a Tablet SoC , and there are a lot of diffs between MT6577 and MT8377 (mainly GPU; max RES; etc, etc )
So, just imagine the mess it would be, by working on some sources that aren't exaclly for your SoC.
Even with full sources for MT6589, the CM Builds required alot of work, and the build status are still WIP. And with a lot of things to be fixed...
B.Regards
Check these sources
mxrootrom.blogspot.in/2014/02/mediatek-mtk-kernel-source-code-leaked.html?m=1
Sent from my MICROMAX CANVAS 2 using XDA Premium 4 mobile app

[CM11]Beta[BT/GPS/Storage/Vibrator][WIP][Booting]

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
Current status: rom is booting, BT/GPS/Vibrator/Storage Working fine but hardware composer is not working at all (wifi,camera,audio not working) but hey i'm working on it
device tree will be updated soon (currently having problem with my internet)
device tree https://github.com/bindassdost/6577_cm11_tree
reserved for future
Good bro, can you also provide the sources, maybe I can help.
Sent from my GT-I9082 using Tapatalk
Forgot to add sources link to op
Updated op you can check
And to others going to test this build
Ignore logcat error regarding libnetcmdiface.so as suggested by dr shadow
bro is the rom booting..??
Doing great work man!
Stuck with error while flashing.
This package is for a 110 devices. this is a hwu8836D.
E:Error in /sdcard/bm-11.zip (status 7)
Installation aborted.
[email protected] said:
bro is the rom booting..??
Click to expand...
Click to collapse
i dont know buddy last time i tried it stuck at bootanim
now as i cant try it on my canvas 2 due to touch screen problem i had uploaded it for testing
Jazzy_1 said:
Stuck with error while flashing.
This package is for a 110 devices. this is a hwu8836D.
E:Error in /sdcard/bm-11.zip (status 7)
Installation aborted.
Click to expand...
Click to collapse
it is because your build prop has hwu8836d as product name
either edit your build.prop to a110 or edit updater script in zip and delete initial assert lines
bindassdost said:
i dont know buddy last time i tried it stuck at bootanim
now as i cant try it on my canvas 2 due to touch screen problem i had uploaded it for testing
it is because your build prop has hwu8836d as product name
either edit your build.prop to a110 or edit updater script in zip and delete initial assert lines
Click to expand...
Click to collapse
Delete script lines . Using latest cwm now its install okay.. But stuck on boot animation.
Did you deleted hwcomposer.mt6577.so file inside zip/system/lib/hw
Try after removing above
If it still stucks on bootanim then provide me logcat
bindassdost said:
Did you deleted hwcomposer.mt6577.so file inside zip/system/lib/hw
Try after removing above
If it still stucks on bootanim then provide me logcat
Click to expand...
Click to collapse
It could be worth a try to use hwcomposer from g pro lite dual (mt6577) kitkat is leaked.
I managed to extract it, was not easy...
see attached file.
A question - it could work to use your rom/kernel as base to port the g pro lite rom... ?
Should be easy... or seeing something wrong?
NOTICE: sorry guys forgot to add some patches before building rom so previous one wont boot
ill provide new one soon
cyclon1978 said:
It could be worth a try to use hwcomposer from g pro lite dual (mt6577) kitkat is leaked.
I managed to extract it, was not easy...
see attached file.
A question - it could work to use your rom/kernel as base to port the g pro lite rom... ?
Should be easy... or seeing something wrong?
Click to expand...
Click to collapse
just checked this one using ida pro and it too contains some undefined function but can you provide me complete rom as i may need some more files from the stock or ill send you a list and youll provide me those files
you can always give it a try at porting if lg hadnt changes much at kernel level
bindassdost said:
NOTICE: sorry guys forgot to add some patches before building rom so previous one wont boot
ill provide new one soon
just checked this one using ida pro and it too contains some undefined function but can you provide me complete rom as i may need some more files from the stock or ill send you a list and youll provide me those files
you can always give it a try at porting if lg hadnt changes much at kernel level
Click to expand...
Click to collapse
I am actually sending you the file via FilePost service, will be valid for 3 days; feel free to upload and share for other developers.
---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------
my port is not installable because i have no selinux enabled recovery...
can you help me building one? Is it enough to extract recovery image, exchange kernel and repack?
Or.. do i really need one? the install script failes at
set_metadata_recursive("/system", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "ubject_r:system_file:s0");
i have no a110 but a 99% identical device; recovery is not identical
cyclon1978 said:
I am actually sending you the file via FilePost service, will be valid for 3 days; feel free to upload and share for other developers.
---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------
my port is not installable because i have no selinux enabled recovery...
can you help me building one? Is it enough to extract recovery image, exchange kernel and repack?
Or.. do i really need one? the install script failes at
set_metadata_recursive("/system", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "ubject_r:system_file:s0");
i have no a110 but a 99% identical device; recovery is not identical
Click to expand...
Click to collapse
okay send me the rom file i'm waiting
kitkat requires selinux enabled recovery and with that you need to add selinux to kernel too to get it work and that is why you are getting error
follo chris bro's commit here to enable selinux in your kernel after that you can repack my recovery with your kernel or build a recovery from sources both will work
https://github.com/chrmhoffmann/android_kernel_wiko_stairway/commits/cm-11.0
bindassdost said:
okay send me the rom file i'm waiting
kitkat requires selinux enabled recovery and with that you need to add selinux to kernel too to get it work and that is why you are getting error
follo chris bro's commit here to enable selinux in your kernel after that you can repack my recovery with your kernel or build a recovery from sources both will work
https://github.com/chrmhoffmann/android_kernel_wiko_stairway/commits/cm-11.0
Click to expand...
Click to collapse
great, my kernel is already selinux enabled, so i will only exchange kernel and try again...
ROM is at 75% uploaded...
---------- Post added at 02:49 PM ---------- Previous post was at 02:25 PM ----------
cyclon1978 said:
great, my kernel is already selinux enabled, so i will only exchange kernel and try again...
ROM is at 75% uploaded...
Click to expand...
Click to collapse
selinux recovery is not working... i got a "defect" screen (the flash to white effect you also get if m4u.ko is not matching kernel) and immediate reboot.
is there any way to get the cause? recovery log is not written, adb is not working...
uupps... i removed binder patch with upstream merge...
I have added selinux but missed something, wont boot.... Config i got, source also but the.selinux binaries do not get build.
Is there a change to build process?
Gesendet von meinem Cynus F3 mit Tapatalk
cyclon1978 said:
I have added selinux but missed something, wont boot.... Config i got, source also but the.selinux binaries do not get build.
Is there a change to build process?
Gesendet von meinem Cynus F3 mit Tapatalk
Click to expand...
Click to collapse
Check to see weather all chris commits are correctly applied + modify fstab in recovery according to yours
Else you can build one using my device tree
Sent from my Cynus T2 using XDA Free mobile app
Kitkat original from G Pro lite:
Part 1: (all except system/apps and system/app)
http://d-h.st/asl
Part 2: the apps:
http://d-h.st/VzR
For Rom porters:
- install selinux recovery
- use bindassdost CM11 as base rom
- make a standard porting process and see whats failing... start with framework + libs + apps
cyclon1978 said:
Kitkat original from G Pro lite:
Part 1: (all except system/apps and system/app)
http://d-h.st/asl
Part 2: the apps:
http://d-h.st/VzR
For Rom porters:
- install selinux recovery
- use bindassdost CM11 as base rom
- make a standard porting process and see whats failing... start with framework + libs + apps
Click to expand...
Click to collapse
buddy the files r in two parts...so we have to combine them and if we will do so then it will be more than 800mb which will be unable to install...so how can it be ported
[email protected] said:
buddy the files r in two parts...so we have to combine them and if we will do so then it will be more than 800mb which will be unable to install...so how can it be ported
Click to expand...
Click to collapse
Just strip down optional files, apps for example
Gesendet von meinem Cynus F3 mit Tapatalk

Categories

Resources