Database Info

[TUTORIAL] [arm-MTK-only] MT65xx Firmware Porting Thread | Guidelines | The Easy Way

Hello Viewers! I am Rohan Taneja, here with completely re-written guide to Port MTK65xx Roms.
I had left MTK development since a year and I finally got another MTK device to carry with it again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, Many Of You May be MTK Device User than you are at right place to fill your device with many awesome roms!
Note: Android ONE devices (MT6582 SoC) use Google's device tree, meaning they differ on everything with all the other MediaTek devices (even the ones with the same SoC , MT6582), as per @superdragonpt told us
Requirements:
A MTK powered device
USB Cable
Usable Brains :cyclops:
Knowledge about Flashing & Taking Logs :angel:
Stock Firmware (from manufacturer) & Port Firmware (matching specification of your device)
Custom Recovery installed on device
Porting Tips
Choose Custom ROM from a device matching same resolution to reduce App Size related bugs
This Guide Applies to
MT6577 to MT6577, vice-versa
MT6589 to MT6589, vice-versa
MT6572 to MT6572, vice-versa
MT6582 to MT6582, vice-versa
Note: Try it at your own risk, and don't complaint any developer or XDA if any mishap takes place. :good:​
TUTORIAL:​Starting with the tutorial, I request you to follow every single step written below to prevent any kind of problem in flashing and causing bootloop. I also dare you to take a nandroid backup of your current rom you are using.​
Get. Set. Go.
Step 1 : Patching System Folder for the port patch.​First of all make a folder named "Port_Patch" and setup all the folder as shown in the images below.
Now, in Port_Patch make system folder in which make folders, "bin" "etc" "lib" "usr" "vendor" "xbin" (without ")
In folder "bin" copy pq & vold from your stock rom
In folder "etc" copy "bluetooth" "firmware" "wifi" "apns-conf.xml" "vold.fstab" "vold.fstab.nand"
In folder "lib" copy files as shown in the image
In folder "usr" copy usr/keylayout/Generic.kl
In folder "vendor" all the files
In folder "xbin" copy "libmnlp_mt662x" (x - '0' or '8') from stock
System has been patched, copy this /system to patch the /system of port ROM.​
Step 2: Patching the boot.img of the port rom.​This is bit tricky but can be done easily.
So, first of download this little tool, to unpack & repack your boot.img - MTKbootimg.zip - tested on Windows 7 & above platform
Extract the Tool and you will get two folders named "stock" & "port"
Copy boot.img's respectively from stock rom in "stock" folder & from port rom to "port"
Unpack both boot.img repectively and they may look like this.
From stock copy "kernel" to port folder and just replace it.
Now, repack it, new file named "boot-new.img" will be generated.
Copy "boot-new.img" to port Rom Folder.
Delete existing "boot.img" and rename "boot-new.img" to "boot.img"
Now, your boot.img is patched, proceed to last step.​
Step 3: Modifying updater-script to install ROM accordingly.​
So, it's the last step before flashing the rom. Now lets fix it.
First, you have to know your device mount points, that can be tracked using MTKDroid Tool or check them in stock rom updater-script.
I have my flashable stock rom so I will get mount points from it.
As show in the image, my stock updater have different mount point for system & data while port have different.
Now, replace "mmcblk0pX" (X - no. for the mount) from stock to port as designated for the partition.
Now Save the updater-script.
Finally, the ROM is ready to flashed.​
Step 4: Compressing & Flashing the ROM.​
Now, the rom is ready to be packed and flashed.
Simply get to the main directory with META-INF, system, boot.img, etc files.
Select all the files and compress them to zip. Select the compression ratio as you want.
After compressing copy the ROM into root of sdcard
Enter Custom Recovery, wipe data & Cache
Flash the ROM.zip wait till it completes.
Wait till it boots, or else take log using ADB logcat. (Hint: If LED light blinks, the rom is booting)
FOR Fixes Proceed to next post and find out the way to tackle and fix the bugs. ​

Fixing ROM issues
Finally Ported a Custom ROM. Now, time to kill out some bugs.
Its all about making the build stable for personal as well as others to use it.
Leave the files if not there in your System
Let's get started:
Bootloop? :crying:
Replace following files(from stock to port):
Code:
[LIST]
[*]libandroid_runtime.so
[*]libandroid_servers.so
[*]libmedia_jni.so
[*]libsync.so
[*]If possible try modifying framework.jar "\smali\com\android\server" (copy from stock)
[/LIST]
Camera Not Working?
Replace following files(from stock to port):
Code:
[HIDE][LIST]
[*]lib3a.so
[*]liba3m.so
[*]libacdk.so
[*]libaudioflinger.so
[*]libc.so
[*]libcam.camadapter.so
[*]libcam.campipe.so
[*]libcam.camshot.so
[*]libcam.client.so
[*]libcam.paramsmgr.so
[*]libcam.utils.so
[*]libcam_camera_exif.so
[*]libcamalgo.so
[*]libcamdrv.so
[*]libcamera_client.so
[*]libcamera_jni_eglfence.so
[*]libcamera_metadata.so
[*]libcameracustom.so
[*]libcameraservice.so
[*]libgn_camera_feature.so
[*]libexif
[*]libfeatureio.so
[*]libfrsdk.so
[*]libft.so
[*]libgcomm_jni.so
[*]libgoggles_clientvision.so
[*]libgui.so
[*]libimageio.so
[*]libja3m.so
[*]libjni_mosaic.so
[/LIST]
Thanks To [I]Shikar A[/I][/HIDE]
[B]Init.rc Fix:[/B]
[HIDE]Init.rc(present in the ramdisk of boot.img), find for code #Camera in stock boot.img. Copy it and replace from stock init.rc and replace in the port init.rc
[IMG]http://s27.postimg.org/4ucj34cwj/initrc_cam.png[/IMG][/HIDE]
Wlan not working properly?
Code:
Check wlan.chip in stock like:
[HIDE][IMG]http://s30.postimg.org/myaya0sxt/Untitled.png[/IMG]
fmradio.driver.chip=x (if mt6620 then x=1, if mt6628 then x=3)
Change the above codes accordingly in updater-script
Replace the version in port from the one in stock[/HIDE]
(Replace from stock to port)
libbluetooth_mtk.so
libbluetoothem_mtk.so
GPS, unstable or not working?
(Replace from stock to port)
Code:
xbin/libmnlp
Media Player problem?
(Replace from stock to port)
Code:
libdpframework.so
libcodecvdrv.so
Sensors not working properly?
(Replace from stock to port)
Code:
libsensorservice.so
SD Card not working or mounting?
Code:
In the framework-res.apk of your port, replace /res/xml/storage_list.xml from stock one.
USB not mounting your device?
Code:
Unpack your boot.img replace init.usb.rc from ramdisk by stock boot.img init.usb.rc
This tutorial worked for porting MIUI, Baidu, Vibe UI, LeWa OS, AOSP based rom from different device to my MT6589 of same hardware.
Credits:
Special Thanks to @yuweng (for starting his main MTK porting thread and his great works)
XDA-Developers being one of the best place for Android Development
Other Developers for helping in fixing most the issues.​

just wanna ask..is it ok if i dont copy the srec folder cause i cant find it..also yhe meta-inf folder as i only have the system.img of my base rom

iel0000 said:
just wanna ask..is it ok if i dont copy the srec folder cause i cant find it..also yhe meta-inf folder as i only have the system.img of my base rom
Click to expand...
Click to collapse
If You Don't Have "srec" folder no need to worry but for system.img you need to extract the img by ext4 method:
http://forum.xda-developers.com/showthread.php?t=2285831

A N D Y said:
If You Don't Have "srec" folder no need to worry but for system.img you need to extract the img by ext4 method:
http://forum.xda-developers.com/showthread.php?t=2285831
Click to expand...
Click to collapse
how about theses files?
CERT.RSA
CERT.SF
MANIFEST.MF
i dont have them cause i dont have a flashable stock rom..

iel0000 said:
how about theses files?
CERT.RSA
CERT.SF
MANIFEST.MF
i dont have them cause i dont have a flashable stock rom..
Click to expand...
Click to collapse
Don't Worry Try The one in the Ported Rom!

cant also find these
com.google.android.media.effects.jar
com.google.android.media.effects.xml
sorry for the noob questions..i just want to port a rom to my device as we dont have developers

it worked!
i ported an miui from newman n1, the ics 4.0.4 with no bugs to my cherry mobile blaze / Ming Ren A2 clone.
btw, this is not a dual sim display miui, i need to go to settings anytime i wan to use the other sim.
anyone who knows where to get a dual sim display miui?

xjammetx said:
it worked!
i ported an miui from newman n1, the ics 4.0.4 with no bugs to my cherry mobile blaze / Ming Ren A2 clone.
btw, this is not a dual sim display miui, i need to go to settings anytime i wan to use the other sim.
anyone who knows where to get a dual sim display miui?
Click to expand...
Click to collapse
what boot.img did you use? stock from cherry mobile?

iel0000 said:
what boot.img did you use? stock from cherry mobile?
Click to expand...
Click to collapse
Don't Try boot.img(Kernel) from the port rom or you'll brick your device!

iel0000 said:
cant also find these
com.google.android.media.effects.jar
com.google.android.media.effects.xml
sorry for the noob questions..i just want to port a rom to my device as we dont have developers
Click to expand...
Click to collapse
Those Files You Can't Find In port just leave that!

A N D Y said:
Don't Try boot.img(Kernel) from the port rom or you'll brick your device!
Click to expand...
Click to collapse
can i use stock boot.img from my phone?or do i have to modify it?

Very nice thread, for beginners that want to learn

tried porting miui v5 base on jb 4.1.2
always stock on boot animation

iel0000 said:
can i use stock boot.img from my phone?or do i have to modify it?
Click to expand...
Click to collapse
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz

A N D Y said:
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
Click to expand...
Click to collapse
i give up porting miui to my phone and tried porting another rom from amoi n820..it boot but the home key is not working..i already used Generic.kl from my device stock rom but it still dont work can you help me plss?
edit : i finally got it working..thanks for the tut it really help me....

iel0000 said:
what boot.img did you use? stock from cherry mobile?
Click to expand...
Click to collapse
Yep. Dont worry, ill upload it sometime.

A N D Y said:
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
Click to expand...
Click to collapse
how to use the tool?

How to from STOCK
iel0000 said:
how to use the tool?
Click to expand...
Click to collapse
Do you know procedure to Port a STOCK ROM(SP Flash tool format not a CWM) of X device to Y device?
Both are mostly same in specifications except the resolution.
I read in some threads that we can not port a rom from a device which has different resolution ?
Thanks in Advance

iel0000 said:
i give up porting miui to my phone and tried porting another rom from amoi n820..it boot but the home key is not working..i already used Generic.kl from my device stock rom but it still dont work can you help me plss?
edit : i finally got it working..thanks for the tut it really help me....
Click to expand...
Click to collapse
what phone do you have btw?
yo kumpare!

[Completed] [Q] pot a chinese tablet

hello, try to compile cm kk, on a Chinese tablet, the vendor doesnt give the sources, and I will have to create my own device, the main board is a k8028-v4 sun7i, I will not change the kernel, but I need to create mk's files , Where I can find how to do it?, I have the partitions, i extracted the boot.img from thetablet with dd, I extracted /system whit push, I have the build.prop from the tablet, information processor a20, I have a generic kernel suni7 3.3, compatible with stock, but when I build, I havent support for my tablet, so how I can create the device and vendor to compile, i must create mk files, but cannt find a detailed guide to do it, it's like port a new device, help
Tablet is a TechPad C981, sun7i allwinner a20 mp3 mali-400 gpu
a7 cortex 1Ghz dualcore cpu, vpu cedarx simd neon, hdmi cec
k8028-v4 mainboard. Extracted / system boot.img
when execute mkvendor.sh TechPad C981 ~ / boot.img in cm11
I do not work, only if I run mkvendor.sh techpadc981 ~ / boot.img
and creates the directories linux
as the device port
step by step guide

Olintonatiuh said:
hello, try to compile cm kk, on a Chinese tablet, the vendor doesnt give the sources, and I will have to create my own device, the main board is a k8028-v4 sun7i, I will not change the kernel, but I need to create mk's files , Where I can find how to do it?, I have the partitions, i extracted the boot.img from thetablet with dd, I extracted /system whit push, I have the build.prop from the tablet, information processor a20, I have a generic kernel suni7 3.3, compatible with stock, but when I build, I havent support for my tablet, so how I can create the device and vendor to compile, i must create mk files, but cannt find a detailed guide to do it, it's like port a new device, help
Tablet is a TechPad C981, sun7i allwinner a20 mp3 mali-400 gpu
a7 cortex 1Ghz dualcore cpu, vpu cedarx simd neon, hdmi cec
k8028-v4 mainboard. Extracted / system boot.img
when execute mkvendor.sh TechPad C981 ~ / boot.img in cm11
I do not work, only if I run mkvendor.sh techpadc981 ~ / boot.img
and creates the directories linux
as the device port
step by step guide
Click to expand...
Click to collapse
I see that you have already asked this in Cgef Central forum (http://forum.xda-developers.com/chef-central/android/help-help-compile-kernel-make-manifest-t2894423).
That's a good place to ask IMO.
You can find some general guides for porting CM ROM here:
1. Android Development and Hacking > Android Software Development > [GUIDE]How to port roms to your Device
2. Android Development and Hacking > Android Software Development > [GUIDE] How To Port Different Roms to Your Device - For CM, AOSP & AOKP
And there are some instructions on the CM website itself.
Maybe that can help you to port CM for your device.
Thread closed and thank you !

[guide][how to] port miui 7 to any mt6582 device

Many porters are not able to port MIUI Rom to MT6582.... I will give a guide to port MIUI 7 ROM to any MT6582 With Kitkat firmware... This guide is for porters only and works for MIUI 6 also...Noobs Try at ur own Risk...
REQUIREMENTS:
- Basic Knowledge about porting and boot.img editing using android kitchen.
- Use onli TWRP/CTR Recovery.
- YOUR STOCK MT6582 ROM(KK FIRMWARE ONLI)
- ANDROID KITCHEN
- PORT MT6582 MIUI 7 ROM ( use my rom for A104 or Gionee M2 Rom by ARGN Devs... We keep our roms updated)
Canvas A104 MIUI 7 ROM: DOWNLOAD
Gionee M2 MIUI 7 ROM: DOWNLOAD
STEPS:
1: PREPARING:
-Extract both roms to different folder... Setup Android Kitchen.
2: SYSTEM EDITING:
-Bin Folder: Replace vold,sdcard from stock to port.
-Libs Folder: Open port libs folder and delete /hw folder.... Now replace /hw folder libcameracustom.so, libcameraservice.so, libfeatureio.so, libMali.so and libshowlogo.so from stock to port.
-etc Folder: Open port etc folder and delete /firmware and /mddb folder... Replace /firmware & /mddb from port to stock... if u dont have mddb folder in stock leave it...
-Vendor Folder: Open port vendor folder and delete /lib and /media folder...replace /lib and /media folder from stock to port.
-Xbin Folder: Replace libmnlp_mt6582 and mnld from stock to port rom.
- Build.prop : Open build.prop and edit device name with urs .... Finding the correct lcd density is a big problem ... Try 210 first ... change it if u have dpi issues (Dont set below 210).
3: UPDATER-SCRIPT:
- Open updater script and change mountspace id (mmcblkpxx) as per ur device.. U can find it using MTK Droid Tool.
4: BOOT.IMG EDITING:
- Unpack boot.img of both stock and port rom using kitchen... We have to recombile port rom boot.img so unpack boot.img of port rom from working folder.
- Copy ZImage from Stock and replace in port.
- Copy sepolicy from stock ramdisk to port.
- Open uevent.rc of both roms in notepad+ and copy any additional lines from port to stock... use any text compare tool to find additional lines.. dont delete any lines onli add lines from port... Now replace uevent.rc from port with stock rom uevent.rc(The one u added lines from stock)
- Repack port rom boot.img and move it to port folder.
- Replace #camera lines of init.rc from stock to port if u get camera error/ green camera.
- If u Get Sdcard /Internal memory not mounting issue.... Rename init.no_ssd.rc of stock boot.img to init.ssd.rc and replace it in init.ssd.rc of port boot.img.j v
5: FINISHING UP:
- Now compress the port rom into .zip and flash on your device. Njoy!!!
BUG FIXING:
- Same as Other KK Roms... If u have any issues comment below...
CREDITS:
-Geo Baby for all his help.
[email protected] for his excellent Crossporting guide.
[email protected]
-Many xda MTK devs for their guides.
Please Hit Thanks if u find this post useful ...

Can this guide work for porting from mt6582 to mt6572 after porting to mt6582? Another crossport if you will

Please tell me how to fix camera error? i replaced #camera line in my stock rom but it can't slove

awesome

bro this gives me error seven even i change the products name......n also it failed to mount / system gives ivvalid argument

Mediatek to Snapdragon porting guide

Porting guide Credits to Dragos Andrei . facebook post credit to IACOB IONUT
You can port from MTK to MSM or from MSM to MTK
For LP :
MSM : Kernel - 3.10.54 to MTK : Kernel - 3.10.65
For MM
MSM : Kernel - 3.10.48 to MTK : Kernel - 3.18.19
First part Boot.Img
1.Replace kernel from stock to port
2.From init.rd all files need compared-named need to be same from stock bootimg and use your brain to change Mount points in init.rc(also init.qcom.rc)
3.Compare all and need to have some knowledge for this.No noobs or beginners.
Second part System
1.Apps.only if is something from mtk or snapdragon replace and delete all which is not for your chipset
2.Bin folder.Delete and replace with Stock.This is need because is different from mtk or snapdragon
3.Etc folder.Delete Firmware Wifi Bluetooth all folders which is like from aosp(for example amigo ui use special folders to boot their rom).Files for custom os need to be not changed.only which is for your soc.
4.Framework.For Snapdragon delete all which begin with mediatek-..... and replace from stock with qc... or qcom... and compare all which is from stock with port.Also fromm framework replace from framework-res.apk(res/xml)-storage.xml
5.All mtk...libs deleted and replace all which have same name in lib...so All which is not for porting os from port need to be deleted and not replaced from stock.(can cause bootloop)
6.Usr.Delete and replace this folder with stock.
7.Vendor.Nothing not need to be changed.Only lib need to be compared and changed if is needed.
8.Rfs.Delete and replace from stock
9.Build.prop.Change especially for your chipset
Final part.Meta Inf
Change only mount points.
For final you need to have some knowledge about all files from your socs......Also a second porting guide will be released for noobers.
Second porting guide
1.From stock delete only app priv-app media fonts tts build prop and framework(move to another dir)
2.Replace from port folders but framework delete mediatek or qc files but copy from
stock missing files and delete files which is in plus.
3.Lib.Delete qc or mtk and replace all which is desired from stock.
4.And all folders like from three step.
This guide is desired for devs which have some experience for porting.Also is not a officially guide can be unstable and not work but need to be tried.For mine worked to port amigo ui from mtk to msm & color os
Credit : DragosAndrei , IACOB IONUT
 @jashiovan

first of all i thought it was impossible !
thanks man for hope and tutorial <3
but i want to ask what about nougat kernel ?
am on redmi note 4 SD MIUI 8 N

[Guide] AIO PORTING GUIDE [MTK-QUALCOMM-RECOVERY-BUGFIX-VOLTE]

ALL IN ONE PORTING GUIDE
by @kuberrocks96
Code:
/*
* 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.
*/
INDEX:
GUIDE FOR MTK
MTK BUG FIXING
RECOVERY PORTING
QUALCOMM BUG FIXING
Update:-
Code:
*Updated Bug Fix Guide for MTK
*Added SNAPDRAGON Bug fix guide.
*Guide to port TWRP also updated.
*Improved the thread.
*Added more fixes.
*Qualcomm porting guide added.
This is for all those users who want to port roms and use them in their devices.
But , before porting any rom,here are some of the main things you should keep in mind.
1)Base Rom :-
What is a Base Rom?
Code:
Base Rom is reffered to the Stock rom or the Default Rom of your device or sometimes the rom from which you will take base files(libs,apns,modem etc).
2)Port Rom
What is a Port Rom?
Code:
Port Rom is the rom which you will port for your device.
like if you are working a rom of another device having similar specifications and porting it for your device then it is called PORT ROM.
3)Kernel
What is a Kernel?
Code:
The kernel is a computer program that is the core of a computer's operating system, with complete control over everything in the system.
the central or most important part of something
In easy words kernel acts as the middle man between the Software and the Hardware
When porting a rom , you should check the Kernel version of the Port Rom and the Base Rom
They both should be similar,
like you can port from :
3.18.xx to 3.18.xx only
3.10.xx to 3.10.xx only
BUGS IN THE BASE ROM OR IN THE PORT ROM.
Yes , our Base Rom and the Port roms may contain bugs,
Those bugs will exist in our final Ported Rom also so , fixing those is not possible - Its always recommended to use a Stable or near to Stable Roms but hi, Custom Roms are made for pleasure only and these roms can't take place of stock roms.
Many users don't like Stock Rom (i.e Default Rom) so , they look for a Custom Rom.
Now let's talk about the main topic for which YOU ARE HERE!
PORTING A ROM!
In this Guide, i will tell one of the most easy way to BOOT UP THE ROM.
So, lets begin,
This guide will focus on MT6735/MT6753 porting.
Device i used is Coolpad Note 3 Lite
CPU:MT6735
But, it will work mostly on all MT675X SoCs , this can also be useful for MT67XX series but , My main focus is on MT675X
Without any delay let's talk about how you should port a ROM and what should be your focus at
YOU SHOULD FOCUS ON BOOTING THE ROM INSTEAD OF BUG FIXING AND DOING OTHER THINGS.
WHEN YOU PORT A ROM CHANGE FILES WISELY
DONT JUST COPY PASTE
PORTING A ROM CAN GET TOUGH ACCORDING TO THE ROM, LIKE PORTING AN AOSP BUILD CAN BE EASY BUT PORTING A MIUI BUILD IS CONSIDERED ONE OF THE MOST TOUGHED AND IRRITATING THING.
RESPECT THE EFFORTS BY THE PREVIOUS DEV.
CREDITS, WHEN YOU PORT A ROM THAT ROM WAS MADE BY SOMEONE , PORTED BY SOMEONE or BUG FIXED BY SOMEONE - SO BY ANY MEANS IF YOU KNOW THE SOURCE AND THE DEV OR TEAM WHOSE BUILD YOU ARE PORTING PLEASE GIVE CREDIT.
THANKS.
NOW , FINALLY. LET'S TALK ABOUT THE PORTING GUIDE WHICH YOU ALL ARE WAITING FOR.
What you guys need:-
Code:
1)Base Rom
2)Port Rom
3)Any good Notepad
4)Any Boot.img repack or unpack tool
5)Brain
Now , if you have all the above mentioned things , Lets proceed.
BOOT.IMG :-
BOOT.IMG contains all the magic , it has the KERNEL inside which is one of the main thing.
Porting from Same CPU & GPU:-
NOTE:- When you are porting from a Similar device having same chipset like porting from:-
MT6753 TO MT6753
MT6735 TO MT6735
Use this method (95% times working ):-
System/lib & lib64 :-
Code:
libaudiocomponentengine.so
libaudiocustparam.so
libnvram.so
libnvramagentclient.so
libnvram_platform.so
libnvram_sec.so
libcustom_nvram.so
System/etc :-
Code:
/Firmware folder
/apnconfig
/spnconfig
/agps_profile_conf2
/media_codecs.xml
BLACK SCREEN AFTER LOGO???
REPLACE THIS LIB:- libcam.paramsmgr
To Fix Camera ( sometimes bootloop so try one by one ) :-
from System/lib & lib64 replace all libs starting like this:-
Code:
libcamera.mt6735 (mt6735 is according to my CPU )
libcameracustom.lib etc
libcamalgo.lib
Unpack Boot.img of both Base & Port Rom
Code:
replace kernel
and init.mt6735.rc ( not recommended always)
and Fstab.mt6735
System/Lib(/64)/HW*
Done , Now zip em and flash.
90% Rom will boot with BUGS! ( NO ROM IS THERE WITHOUT BUGS, LOL)
==>READ BUG FIX METHOD ALSO{Later in this Guide}<==
For Cross Porting Like:-
MT6752 etc to MT6753/MT6735
DO REMEMBER TO CHANGE :-
Code:
System/xbin/mnld
System/mddb
System/etc/firmware
System/etc/Apnconf
System/etc/spnconf
In lib(/64)/HW :- add files accordingly to your CPU or rename them.
BLACK SCREEN AFTER LOGO :-
Code:
libcam.paramsmgr
BOOT.IMG PORTING:-
UNPACK both Base Rom and Port Rom Boot.img
In PORT ROM BOOT.IMG:-
Code:
replace the boot.img-kernel
and in ramdisk folder add these files from Base Boot.img to Port Boot.img
Code:
fstab.mt6735
init.mt6735.rc
init.mt6735.usb.rc
Note:- Name may differ a little according to your CPU
REPACK THE BOOT IMAGE
NOTE:- If u get WIFI AND BLUETOOTH NOT SWITCHING ON OR BATTERY PERCENTAGE THEN REPLACE
Code:
init.project.rc
Done , You have succesfully ported Boot.img
Now , Lets focus on BUG FIXING
Bug Fixing isnt easy as it seems.
Replacing any wrong file or not supported file can easily give you bootloops.
It depends from ROM to ROM.
BUG FIXING[MTK]
Let's Begin.
If any lib missing in Base leave that - DONT WORRY
NOTE:- CHANGE LIB FILES FROM BOTH lib & lib64 folders
If you face "This rom is for Coolpad Note 3 Lite and your device is "K4Note"
To remove this delete the assertlines in Updater-script
ALWAYS CHANGE DPI IN BUILD.PROP ACCORDING TO YOUR STOCK ROM
Bootloop when porting
Code:
*libandroid_runtime.so
*libandroid_servers.so
*libmedia_jni.so
*Repack boot.image (properly)
RadioFM
Code:
\system\bin\fmradio
\system\etc\firmware\mt6620_patch_e3_hdr.bin
\system\etc\firmware\mt6620_patch_e6_hdr.bin
\system\etc\firmware\WMT.CFG
\system\lib(/64)\libfmcust.so
/system/lib(/64)/libfmjni.so
Sensors
Code:
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so ( acc. To device)
/system/etc/firmware (folder)
/system/bin/servicemanager
/system/bin/sensorservice
System/bin/msensord
system/etc/permissions/:-
android.hardware.sensor.xxxxx.xml
FIX Offline charging:-
Code:
In Boot.img -> sbin/healthd
System/Lib(/64):-
Showlogo
System/bin:-
Kpoc_charger
Bluetooth\Wifi not turning On\Off(old)
Code:
\system\lib\module\mtk_stp_wmt
Wifi
Code:
/system/etc/wifi (folder)
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
/system/lib(/64)/libhardwarelegacy.so
Hotspot:-
Code:
/system/bin/netd
*follow Wifi fix also*
Camera
Code:
firstly try one by one:
\system\lib(/64)\libcameracustom.so
\system\lib(/64)\libcameraservice.so
System/lib(/64)/camalgo
/system/etc/media_profiles.xml
/system/lib(/64)/libcamera.so
/system/lib(/64)/liboemcamera.so
\system\lib(/64)\hw\camera.default.so
\system\lib(/64)\libcamera_client.so
\system\lib(/64)\libcamer aprofile.so
\system\lib(/64)\libmhal.so
\system\lib(/64)\libmhalcontent.s o
\system\lib(/64)\libmhaldrv.so
\system\lib(/64)\libmhalmdp.so
\system\lib(/64)\libmhalpipe.so
\system\lib(/64)\libmhalscenario.so
\system\lib(/64)\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
Other cam files if any
*try one by one*
CamCoder/HwDecoder
Code:
\system\lib\libOmx*.so
system/etc/media_codecs
[SIZE="3"][B]Green/pink Camera / video lagging[/B][/SIZE]
system/lib(/64)/libdpframework.so
SD card/Memory
Code:
mt67**.fstab in boot.img
/system/bin/vold
/System/bin/pq
System/bin/sdcard
WhatsApp Media Fix:-
Code:
from System/bin/ replace these files:-
Media
mediaserver
netd
service
servicemanager
surfaceflinger
GPS
Code:
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen(Haptic)
Code:
/system/usr
/system/usr\keylayout\Generic.kl ->fix HomeKey
NFC ( experimental)
Code:
System/etc/: Nfc files
System/etc/permissions/ nfc files
System/lib/libnfc****** ( all starting from nfc )
Sim1/2 (RIL)
((Trustbin.bin flash it accordingly to LP or MM etc of stock rom))
Code:
\system\etc\firmware\modem.img
\system\etc\permission (RIL)
Try these aswell if ( you may suffer Bootloop )
/System/bin/mtkrild
/System/bin/mtkrildm1
/system/bin/stmd
EXPERIMENTAL FIX for ril:-
Code:
System/ Lib(/64)/ :-
Nvram
Nvram_sec
Nvram_platform
Nvrammagentclient
System/bin:-
Gsm***
System/etc/trustzone
Lib(/64):-
Libril
Libc2k***
Librilmtk
Audio/Sound:-
Code:
\system\lib\libaudio* .so
system/lib(/64)/libaudiocustomparam
system/lib(/64)/libaudiopolicymanager
system/lib(/64)/libaudiopolicyservice
system/etc/audio_effects
system/etc/audio_policy
System/lib(/64)/soundfx
Sometimes if Sound isn't working fully :::::
Code:
System/lib(/64)/hw/audioxxxxxxxxx (audio files)
Bluetooth:-
Code:
system/etc/bluetooth
System/etc/permissions/android.hardware.bluetooth.xml
/system/bin/uim*
/system/bin/bluetooth*
/system/lib(/64)/libbluetooth_mtk.so
/system/lib(/64)/libbluetoothem_mtk.so
Ads
Code:
/system/etc/hosts ->replace with new files or use tweak.
=====>>ADVANCE BUG FIXING:-
Volte Fixing
( Will only work if your Base Rom , Port Rom and Kernel supports VOLTE )
Code:
Boot.img:-
Zimage ( kernel - volte supported )
init.volte.rc
==THIS SHOULD NORMALLY FIX but if it doesn't try :- ==
Code:
System Folder:-
bin/volte_stack
bin/volte_imcb
bin/volte_ua
lib(/64)/volte_imsm
build.prop(Not always required):-
ro.mtk_volte_support=1
persist.mtk.volte.enable=1
FingerPrint:-
[Try one by one][If any file missing leave it]
Usual way to fix :-
Code:
System/etc/permissions/android.hardware.fingerprint.xml
System/lib(/64)/libgatekeeper.so
System/lib(/64)/hw/gatekeeper.mt6735.so
System/(/64)/libmcgatekeeper.so
System/lib(/64)/hw/fingerprint.default.so ( can break FP in some devices)
Advanced ( if usual doesn't work ):-
Code:
System/bin/:-
fingerprintd
Gx_fpd
tee_deamon
Lib64/lib:- ( if any missing leave that)
Fpclient
Fpalgorithm
Fphal
FPservice
IF ROM DOESNT BOOT TAKE LOG ( From ADB)
adb shell logcat > log.txt
and check what is causing issue
REFERENCE LINKS :-
Carliv Image Kitchen :-
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
Cross Port and Porting Guides:-
https://forum.xda-developers.com/k3-note/development/guide-porting-64bit-mtk-roms-cross-t3310605
Unpack and Repack without PC guide:-
https://youtu.be/qTe9XofT5VE
Meta-INF Info:-
http://www.mtkroms.com/2015/06/make-stock-rom-mtk-easy.html?m=1
Meta-Inf generator:- ( Not tested try but its worth a look)
https://forum.xda-developers.com/showthread.php?t=1221003
Sample Recovery flashable zip:-
https://forum.xda-developers.com/android/development/sample-custom-recovery-zip-t3552916
Assert Failed ?check this:-
http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/182438-solved-assert-failed.html
BUG FIXING FOR SNAPDRAGON
Compare the PORT FILES FROM BASE FILES:
Code:
uneventd.qcom.rc ( will fix sensor )
uneventd.rc
Copy and replace the following files from Base (ROM-PORTING/BASE) to Port (ROM-PORTING/PORT) to solve the given issues:
No sound bug:
Code:
system/lib/hw/
audio.primary.msm****.so
audio.primary.default.so
system/lib64/hw/
audio.primary.msm****.so
audio.primary.default.so
Sound working in speaker but not working through headphones or vice-versa:
Code:
system/etc/
mixer_paths.xml (you can also try patching it with the base)
[B]Distorted Outgoing Sound during Phone call or [/B]Partial Sound:
system/etc/acdbdata/MTP/
MTP_***.acdb (all files)
Home or any other button not working:
Code:
system/usr/keylayout/
goodix.kl
gpio-keys.kl (important)
Generik.kl
Video hw encoding/decoding not working:
Code:
system/etc/firmware/
venus.*** (all files starting with ‘venus’)
Sensors not working:
Code:
system/lib/hw/sensors.msm****.so (or sensors.lsm6db0.so)
system/lib64/hw/sensors.msm****.so (or sensors.lsm6db0.so)
system/lib/libsensorservice.so
system/lib64/libsensorservice.so
Led notification not working:
Code:
system/lib/hw/lights.msm****.so
system/lib64/hw/lights.msm****.so
Vibration not working:
Code:
system/lib/libhardware_legacy.so
system/lib64/libhardware_legacy.so
FM not working:
Code:
system/lib/qcomfm_jni.so
system/lib64/qcomfm_jni.so
Wifi not working:
Code:
system/lib/modules/wlan.ko
[Note: In MIUI, wlan.ko is renamed as pronto_wlan.ko and is also kept in system/lib/modules/pronto/ folder, so you have to replace in both the places.]
In some phones you may not find wlan.ko file. In that case you may try replacing these files
Code:
system/lib/libwcnss_qmi.so
system/lib64/libwcnss_qmi.so
For slow WiFi network and other WiFi related issues replace these files:
Code:
system/etc/wifi/ -- all files
system/etc/firmware/wlan/ -- all files
Camera and flash not working:
Code:
system/vendor/lib/ :-
libactuator_***.so (all files starting with ‘libactuator’)
libchromatix_***.so (all files starting with ‘libchromatix’)
libmmcamera_***.so (all files starting with ‘libmmcamera’)
system/lib/:-
libmm-qcamera.so
libmmcamera_interface.co
system/lib/hw/
camera.msm****.so
[Note: If such files are also available in your BASE/system/vendor/lib64/ then you have to copy those files also to their respective place in PORT]
GUIDE TO PORT RECOVERY
PORT TWRP RECOVERY
Things You are Required ::-
Code:
1.Android Image Kitchen
2.Notepad++
3.Base Recovery
4.TWRP to Port
5.Brain
First of All , You Guys need to unpack Recovery.img i.e both Stock Recovery or TWRP Recovery.
After this :-
You need to Copy these files from your Stock Recovery to the TWRP Recovery ( which you want to port ) :-
Lets Divide Step by Step ::--
*REPLACE FROM STOCK TO PORT*
STEP1:
Inside Ramdisk Folder ::::::
Code:
1.meta_init.modem.rc
2.meta_init.project.rc
3.meta_init.rc
STEP2:
Now replace your Kernel usually named as zimage-kernel
STEP3
Inside Ramdisk Folder(boot.img):::::::
Code:
1.fstab
2.ueventd.rc
3.ueventd.goldfish.rc.
STEP4
INSIDE RAMDISK/ETC
Code:
recovery.fstab
STEP5
Open Default.prop
and Compare it with stock Default.prop or your Build.prop ( add values from build.prop )
=============>>>>>>>
DONE!!!!! EVERYTHING IS IN PLACE
NOW REPACK IT AND FLASH.
YOU HAVE PORTED A RECOVERY....
WARNING: Do not replace any file unnecessarily, because it may give rise to new bugs in place of solving it. Always be specific!
Now Mostly its the end of the Guide / Tutorial / G.K on porting or whatever you call it.
Once again , i (Kuber Sharma) hope you guys succesfully learn porting and making roms soon.
You guys have my Best Wishes.
Thank You.
I couldn't have done this without the help of :-
Amit Kumar (A.M.T)
Sam Grande (A.M.T)
Special Thanks to @sandeep.sethi
Special Thanks to @Yousef Algadri
Special thanks to @mohancm
You can find me here:-
@kubersharma
Want to buy me a coffee or wanna donate me for my cause!!
https://paypal.me/kubersharma
DO HIT THANKS BUTTON IF YOU LIKE MY GUIDE
THANK YOU

not lib64 files?
http://cloud.tapatalk.com/s/58a1efb476118/IMG_20170213_183928.jpg
Odesláno z mého VFD 700 pomocí Tapatalk

Great work, Really appreciated!
Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
Adreno306™ said:
not lib64 files?
http://cloud.tapatalk.com/s/58a1efb476118/IMG_20170213_183928.jpg
Odesláno z mého VFD 700 pomocí Tapatalk
Click to expand...
Click to collapse
I think op have missed while typing, both lib and lib64 should be considered.

Reserved...

Thank you
mohancm said:
Great work, Really appreciated!
Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
I think op have missed while typing, both lib and lib64 should be considered.
Click to expand...
Click to collapse
Couldn't have done without your support.
Thanks

Awesome work
Great job man.. Awesome and best guide for 64 bit devices.. Great thing... Expecting more guides.. ?

Is there a method for fixing the NFC to?o

Adreno306™ said:
Is there a method for fixing the NFC to?o
Click to expand...
Click to collapse
Follow sensor fix and replace libnfcxxxx in lib folder

kuberrocks96 said:
Follow sensor fix and replace libnfcxxxx in lib folder
Click to expand...
Click to collapse
nfc service has stopped working
Odesláno z mého VFD 700 pomocí Tapatalk

Adreno306™ said:
nfc service has stopped working
Odesláno z mého VFD 700 pomocí Tapatalk
Click to expand...
Click to collapse
Take a log

trying to port for teclast t98 4g mt8752
I've trying to port following a lot of guide ever bootloop only one time boot but no touchscreen
what i'm wondering my stock rom is kitkat so with a 32bit kernel ,i think, can i mix it with 64bit rom?
in my stock rom there isn't lib64 directory so what can I do to follow your guide?
thanx

Sorry to post it here as i thought probably you could help me but this method should also work for 32 bit roms .. Right?? I was porting a lollipop nexus look rom to my lenovo tab.It boots to the android is optimising screen and finishing bootbthen goes into a soft reboot. Can you help me with that? And please do confirm whether this method would work for 32 bit rom.

Hello!
I have a problem with the port I made for the Redmi Pro (MTK6797T). The ROM is booting and working quite well but the problem comes when i try to use my headphones.
The ROM recognises the headphones, when i plug them the headphones icon appears and the buttons are working to stop-play a song, however the sound comes out of the headphones and the speaker at the same time.
Any idea to solve this?

thanks A LOT for bugfixing guide portion... i was searching for that for a long time

@kuberrocks96
Camera gets crashed whenever I try to take HDR ......what is needed to fix this?

hi bro, Thanks for the guide, just like crossposting from a mt6753 to a mt6735? Or similar?
Now I would like to leave a solution for the nvram problem that has already happened to me several times
1.- edit the build.prop looking for gemini lines, in my case being a single sim would have to be disabled this function and any other line related to the sim ... if in your case you have 2 sim as you have to activate The gemini function and specify that it is dual sim looking for this line in the build.prop "persist.radio.multisim.config = ss" (for single sim) and change it to "= dsds" for dual sim
2.-In the libraries you have to change this
Libnvram.so
Libnvramagentclient.so
Libnvram_platform.so
Libnvram_sec.so
Libfeatureio.so
Libfeatureiodrv.so
Libhardware_legacy.so
Libcustom_nvram.so
3.- also have to change the firmware and mddb folders
And finally in the boot.img it is necessary to replace in ramdisk these files
Fstab.mt6735.rc
Init.mt6735.rc
Init.mt6735.usb.rc
And added a fourth file
Init.modem.rc
With that you should have running the imei and remove the nvram error in the configurations of the wifi
Greetings from Mexico and apologies for my English, but I'm using google translator

i couldnt fix modem problem even with firmware nor mddb nor modem file in boot image. w/o sim inside baseband imei works but w sim inside its showing no baseband no imei no service.
mt6752 to mt6752. base is c5 e5553 single sim port is k3 note dual sim.
wifi bluetooth sound works, didnt try camera fix

Please can you help solve the BLU R1HD camera MT6735 in Nougat from this ROM: https://forum.xda-developers.com/r1-hd/development/cm14-1-r1hd-t3518202

Yes , it will
YuZaGa said:
Sorry to post it here as i thought probably you could help me but this method should also work for 32 bit roms .. Right?? I was porting a lollipop nexus look rom to my lenovo tab.It boots to the android is optimising screen and finishing bootbthen goes into a soft reboot. Can you help me with that? And please do confirm whether this method would work for 32 bit rom.
Click to expand...
Click to collapse
Check wht files you replaced.
While booting the rom just don't replace all files.
Kernel ( and other boot.img part)
Firmware
Apn & spn
Amd sometimes mddb is enough

Hi , thanks
2909luboy said:
hi bro, Thanks for the guide, just like crossposting from a mt6753 to a mt6735? Or similar?
Now I would like to leave a solution for the nvram problem that has already happened to me several times
1.- edit the build.prop looking for gemini lines, in my case being a single sim would have to be disabled this function and any other line related to the sim ... if in your case you have 2 sim as you have to activate The gemini function and specify that it is dual sim looking for this line in the build.prop "persist.radio.multisim.config = ss" (for single sim) and change it to "= dsds" for dual sim
2.-In the libraries you have to change this
Libnvram.so
Libnvramagentclient.so
Libnvram_platform.so
Libnvram_sec.so
Libfeatureio.so
Libfeatureiodrv.so
Libhardware_legacy.so
Libcustom_nvram.so
3.- also have to change the firmware and mddb folders
And finally in the boot.img it is necessary to replace in ramdisk these files
Fstab.mt6735.rc
Init.mt6735.rc
Init.mt6735.usb.rc
And added a fourth file
Init.modem.rc
With that you should have running the imei and remove the nvram error in the configurations of the wifi
Greetings from Mexico and apologies for my English, but I'm using google translator
Click to expand...
Click to collapse
Yes , no worries we all are humans and language shouldn't be a bearer.
And yeah , thanks for your little guide.
Cheers