[FIX BUG] Fixing bugs when porting a Lollipop Cyanogenmod 12 Custom ROMs For Mediatek MT65xx device!

23:18 Alex 166 Comments

Never heard of such issue. can you explain more. what is your sources of port and base roms.
Use below guide to port CM12/CM13 roms to your device.
Port Lollipop/Marshmallow ROMs for MTK

The rom is originally made for dual sim mobiles so thats why it have two sims. You can turn off second sim from settings. I dont think that is a major problem. For camera have you replaced all libcam* ? also try to replace "\system\app\Camera2" folder from a working build.

Did you replaced all libs starting with "libcam".
And camera lines under
#Camera
from stock boot.img init.rc to init.mt6582_common.rc.
Also try to replace Camera2 folder from a working cm build.

About data connection dropping does that happen with calls too?
Check your APN.
Replace etc/firmware folder.
Is sim1 working perfectly?
Check if the rom itself support dual sim's many samsung rom's don't support dual sim mode.

Sometimes a factory reset do wonders.
Flash your rom > reboot > let it stuck on optimization for sometime > Reboot to recovery and do a factory reset > reboot.
If that dosent work and you are still stuck at starting apps or Android is upgrading then replace these files from stock to port. :-
- /framework-res.apk/res/xml/storage_list.xml
- /bin/vold
- /bin/sdcard

Did you tried to replace firmware folder. if it dint work.
replace these files. these are all related to network and modem.

\system\bin\rild
\system\bin\rildmd2

\system\etc\firmware [whole folder]
\system\etc\ril\oper.lis
\system\etc\agps_profiles_conf.xml
\system\etc\apns-conf.xml

\system\lib\libreference-ril.so
\system\lib\libril.so
\system\lib\librilmtk.so
\system\lib\librilmtkmd2.so
\system\lib\librilutils.so
\system\lib\mtk-ril.so
\system\lib\mtk-rilmd2.so

No problem buddy i can copy paste from anywhere. Actually some people copying contents from hear and posting on there blogs so had to disable it.

So back to your issue.
can you give more information about
your base and port rome. and which chipset?

Do you have any lollipop build ported for your device which is working perfectly. The link you have given is the rom for gionee s5.5. but from your previous comment it looks like many things are not working in that. rite?

To port LP/MM roms main magic is in boot.img, if you port boot.img correctly there are 80% chances that your rom will boot and work properly.
If nothing is working as you expected my advice is to start from the beginning with a fresh mind.
You can try to portTHIS rom.
And THIS PORTING GUIDE
if you follow the instructions properly, i am sure that you will get succeed.

Why would anyone be angry. There is nothing wrong in asking questions. We are all hear to help eachother.
-If you have already tried to replace "libaudio.primary.default.so" and it dint work then
-Try All Files starting With libaudio*
-Replacing All Files Sometimes Cause Bootloop, If you got bootloop in That Case Replace Only
-libaudio.a2dp.default.so
-libaudio.primary.default.so
-libaudiocompensationfilter.so
-libaudiocustparam.so
-libaudiosetting.so
-libaudioutils.so

Install proper drivers.
Enable the dev mode.
Enable usb debugging.
Then go to storage > usb computer connection.

What you want to replace???
Open port and stock roms zip with winrar/7zip.
Copy the files you want to replace from stock rom then paste them in port rom.
zip again. Flash new zip.

First make sure the rom you are porting also have same kernel version [ie. 3.10.54]
Second You have to extract the system.dat to view files in it and to get proper folder structure for porting
here are some guides you can try.
1. Lollipop/Marshmallow DAT files|Compression and Decompression
2. [Direct link]Tool Unpack Repack System.new.dat.zip
3. Extract System.new.dat

I've never tried these tools so i am not 100% sure but these methods should work.

And about updater.script its in META-INF folder. you can compare both port and stock roms updater.scripts
and edit them with Notepad++.

Replace

\system\lib\libfeatureo.so

Or

all libs starting with "libcam"

replace codecs*

To just replace the libs and other files make a copy of the working zip and
open it with 7zip (dont extract just double click and open) or whichever program you are using. and browse to the directory of the files you want to replace and then just drag and prop the new files.
Try to solve one bug at a time so you wont get confused.

About camera not working :
replace all libs starting with libcam.so
if that to doesnt work the also replace Camera2 folder in system > apps

I did exactly what you said, without extracting the rom I just replace inside the libaudio files (libaudio.primary.default.so, libaudiocompensationfilter.so, libaudiocustparam.so, libaudiosetting.so, and libaudioutils.so). In recovery make all wipes and install succes but when rebooting i get a bootloop. One of the .so files is causing it.

No its not possible.

replace video codecs from stock rom.

How can i do it where is the video codecs ?

Look in system\etc\ folder

The kernel is quite old for a fully stable lollipop or newer rom.
but there are some roms that you can try.
These links might help you. sadly the links for the roms i found are dead.


Alcatel OneTouch 7047D POP C9 - 4pda

Custom roms for alcatel one touch pop c9 - XDA

Try the fixes mentioned in above guide. and port boot image again.
generally boot loops caused because of faulty boot.img.

Your NVRAM is wiped. View this topic to fix it

[Tutorial][Fix] Permanently IMEI Fix for MTK Device

Its already mentioned in the guide above. please read before requesting
by the way this if the fix.

Replace sensor.default.so and rename it to sensor.mt65xx.so and replace from stock to port ROM.
replace xx with 82 or 92 depending on your chipset.
and also replace
- /system/bin/akmd*
- /system/bin/servicemanager
- /system/lib/libsensors- so
- /system/etc/firmware (whole folder)
- /system/lib/libms3c_yamaha- so

I have already read... I said I am on sc7731 chipset, not mediatek. Do you have any idea how to fix it on spreadtrum chipset ?

Ohh sorry i missed that. well i have no experience in spreadtrum.
still you can try to replace all libs and files related to sensors.
if still not work send me logcat.

https://drive.google.com/file/d/0B377TLFOgWdsRUd4UnBuQlpTaWM/view?usp=drivesdk

Logcat is here...

there is some problem with your permissions. system is not able to get correct permissions to access sensors and some modules are missing.
check your stock rom again.

First try the fixes mentioned in above guide if it dont work then re-port boot.img.
Boot image is the main part in cm12.1 porting.
Use other methods/tools to extract and repack boot image.(android kitchen is best tool to do this)
sometimes its the fault of the tools that your use and sometimes it just dont work for no reason. If you have a working cm12.1 boot image then you can use that too.

To fix bootloop all you can do is
1. check mountpoints in updater script.
2. port boot.image again from start.
3. replace storage.xml in 'system\framework\framework-res.apk\res\xml\' (open framework-res.apk with 7zip or winrar and drag drop replace file)
4. replace 'vold' and 'sdcard' in "system\bin\"
5. replace libs
-libandroid_runtime.so
- libandroid_servers.so
- libmedia_jni.so
6. Factory reset > flash zip > boot > if stuck in bootloop > reboot to recovery > factory reset again then boot.

Can you take a logcat and send me.

How To Logcat - XDA

There are some files missing from etc and bin folders.
so check those folders again. dont delete any file in the folder. just copy from stock then paste and replace.

Check your IMEI (*#06#) if it shows null then restore it with following method.
Permanently Fix IMEI for MTK Device

Have you tried the fixes from above guide?
there could be many reasons for a bootloop.
But seance it is stuck on boot.logo i suggest you to re-port boot.img.

This comment has been removed by the author.

Tried everything you suggested me, but still having the problem. I already tried to get catlog, but adb doesn't find my device. Do you know what can cause the problem?

To take catlog you need to install all Adb and mtk vcom drivers(including your device drivers) and revoke usb debugging.
Download drivers from Adb and mtk vcom drivers

Adb can find my device when I'm on the stock rom, but when I flash my ported rom not. I think that's because my phone stucks on the boot logo. So I want to know if there is a way to solve the bootloop? Or can I a make a catlog from it when it's in bootloop?

You can take logcat when device is in bootloop.
Read this topic on XDA - How to get & read a logcat (3rd post)

I succeeded to make a catlog, but I'm not capable of reading that. Can someone find the bug? I will post it on mega: https://mega.nz/#!OwB1zYAC!aZWZKnugZxla4p08NGoDB1xpDSwgQ6ov4LdptxeGuXk

Thank you very much by advance!

Are you sure the rom you are trying to port is of same chipset and kernel version?
there are errors in firmware and lots of wrong permissions.
i will suggest you to find some other rom with correct chipset and kernel version.

I think I used a correct rom. Do you know if there is a difference between kernel 3.18.19 and 3.18.19+? Maybe that's the problem.

No, 3.18.19 roms should work on 3.18.19+.
do check if the chipset is same because most of the roms available for 3.18.19 kernel uses mt6580

You do know your phone number right? :/ You dont need any stupid box to tell you, your own phone number. :p

Well jokes apart, No Number Assigned and empty Phone Number is completely normal.
Generally all roms/devices are not capable to read sim card number stored on it.
so no number assigned is ok. check if you can write your number there manually.

Now about sim contacts not showing up, Do check if you have enabled it in settings.
Go to 'Contacts > Contact Settings > Contacts to display > and there choose show all or sim contacts.
And remember that you can not store new contacts on sim card anymore; in CM.

Mediatek have 3 variants for there chipset. M, Stranded and T.
For example MT6589M - MT6589 - MT6589T
where M - you can say it a minor version of standard chipset
and T - Is for Turbo, which is superior then stranded.
So obviously minor version have low specifications and turbo have grater,
generally M have low screen resolution and low camera. other specs are same for all. View this comparison chart for batter understanding.

Although there are minor difference between both but still there is no guaranty that 6582 rom will work for 6582m,
And no you can not flash directly by just changing mount points.

So i'll suggest you to batter search for a rom which have same SoC.
As far as i know Wiko mobile and Micromax uses similar hardware/software so try to search a model from wiko.

Dont trust a custom rom's Build.prop,
Build.prop just contains information about your device.
And most of it is either non-important or you can say android firmware don't need much information from build.prop to work. there IS some imp stuff but not most of it is just info.
And you can alter many aspects of build.prop without breaking anything.

So the guy who have ported the rom for your device might have used a rom from the device which had mt6582 or he just forgot to change or maybe he changed it purpously.
(maybe you should ask the guy, from which device he ported the rom so if that device got working mm then you can port it easly)


To explain more about build.prop:

1. ro.build .version.release=7.0.1 by changing this value you get it to show any android version you want like 7 is for Nougat but you can change it to any number like 10, 11, 15, or 389253503257, and it will show like you are using android version'389253503257' (which is quite imposiable).

2. ro.product.brand=OnePlus > this shows of which brand your smartphone is, You can change it to even Apple, so it will show that you are using an Apple device.

3. ro.product.name=OnePlus3 > this shows device model name, you can change it to Apple iPhone10, so it will show that you are using Apple iPhone 10.

4. ro.board.platform=msm8996 or ro.board.platform=mt6582 > you can change it to applea9 so it will show your phones processor is Apple A9.

and
So this is just for example to show you that system dont relay much on build.prop,
ofcorce it is a very importent file in android system and wrong, incomplete or courrepted build.prop could lead to bootloop,
but it not imp the way you are thinking.

Build.prop just tells (you, Others, Google servers, websits you surf on internet and apps you are using) that, what device you have, what android version you are on, what kind of processor your device using, and many other things.

We've already wrote about build.prop tweaks which help you to increase your device performance,
Read about it here: Best Build Prop Tweaks

Try Your luck and just port a mt6582 cm12(same kernel version) rom, there is no harm in trying. make sure you know how to go stock if something goes wrong.

No, Its not possible, well it is, but only in case if you have kernel sources.

No you wont be able to restore nandroid backup in major failure, or upgrading from kitkat to lollipop, so Get stock firmware which you can restore with SP Tool or if there is any other tool for your device.

Grate, i think now you can go for marshmallow too. its not much different then LP.

FM radio is still not stable in cm12 roms, though in some cases it worked for some people.

Offline charging also was a bug in earlier builds but it was fixed in later builds.
So just try to find latest cm12 build and port that.(cm12.1_beta 7 was the most stable, you can try others too but later builds).

Umm.. sorry but i dint get what do you exactly mean by "reversed Stereo through headphones."

Ohh okk, Well i've never seen such problem before.
I'll try to find a fix for it asap.

Yes it is. If you see android versions market share graph you can find that Lollipop is still leading the market. And there's very few devices out there which are running nougat. So dont get disappointed.

FM is still not stable on CM12 roms, so most i can suggest you to use latest build.
About Camera, fixes are already been covered, also change camera lines in boot.img init.rc to your socks appropriate init.rc...

1. To fix Green Camera Problem :
Replace first libcamdrv.so, libdpframework.so and check, if not success then replace libcameraservice.so from/lib.

2. To fix Camera Focus Problem :
replace system/lib/libcameraservice.so
system/lib/libfeatureio.so

3.If not work : also replace Camera2 Folder in system apps with your stock or from a working CM rom including all libs mentioned in above guide.

IF a file not present just skip it,
Replace xxxx with your soc,

I am sorry porting rom's for specific devices each is not possible for us. because it takes time and without physical access, porting bugless rom's is quite impossible/very hard that's why we have provided guides here.

Referring to your below comment, please do not post your mobile number publicly, I will delete your below comment to remove your number, while quoting your message-

"I don't know about boot.img porting so u can send the ported boot img as rename it a txt file than send me to whatsapp "removed" All other work i know and i will replace other files than i will maje compressed zip and flash Plz reply me Fast pl plz plz"

As i mentioned earlier, porting roms for each device specific is not possible, most i can help you with how to decompile/extract Boot.img which is explained in this guide How to Port Boot.img This guide will show you how to extract/decompile boot.img rest you can read in this guide to know how to port lollipop/marshmallow roms

IF you still face any bugs or errors while flashing rom you can feel free to ask.

Explain More about bugs.
Is camera not working at all?
And what do you mean by sound bug? Plug in your headphone and check if you can here sound through your headphones.

1. About fixing Camera:- This issue already been covered in guide and also in comments. so read comments too. you will surely get it fixed.

2. To Fix No Sound:-
First try to replace only libaudio.primary.default.so
If still dont work then replace all system/lib/libaudio...
Also try to replace soundfx folder.

Sorry We dont have any group on whatsapp or anywhere else.

Yes.
If your port rom have bugs you will have same bugs in your ported rom.

But If the port rom is bugless and you got some bugs after porting, you can easily fix them.

How To Create TWRP/CWM flashable Zip - From Sock ROM Or Backup

Actually I havnt any META-INF folder or update script.... so how can i port rom?? Can i put file(from port rom)into twrp backups file??? Backup have system folder in... So can i put into it??

You can use PORT Rom's META-INF folder, you'll just have to edit system mount points in updater-script according to your stock.

1. Connect your device to pc View Your system mount points with the help of MTK Droid Tools,
2. And then Edit the mount points in PORT rom.s updater-script.

3. Then use system and boot.img from TWRP Backup of your stock rom.

4. Replace files in PORT roms system folder from the system folder you got from your stock TWRP backup.

5. and META-INF Folder from port rom which contain your edited updater-script.
6. if you are porting LP or MM rom, port boot.img

Thats it.

Thanks but i havnt any pc

You can view mount moints in your mobile:
Read This:
How To View Android System Mount Points In Phone Without PC

I changed update script but when i flashing it in twrp, i get an error 6

Status error 6 means your text editor have messed up the updater script.

Try 920 Text Editor

Take a new untouched copy of updater-script from port rom and edit it again

Replace
– /framework-res.apk/res/xml/storage_list.xml

also replace
– /bin/vold
– /bin/sdcard
if you haven't already

Do a full wipe/factory reset then flash rom. if still stuck reboot to recovery and wipe/factory reset one more time then reboot. remember some roms take time on first boot so be patient and wait atleast 1/2hr+.

Replace \system\lib\libfeatureo.so

when i do that
can't connect to camera
is there any file i should try it ?

From a working rom, replace all files related to camera, mentioned in the Above guide and This Guide

Also replace Camera2 Folder From /system/apps

If you are porting marshmallow rom then also replace lines under #Camera in boot.img - look under files starting with init.***
look at this image for reference.

Does your device have external storage? Or only internal?
Does your device allow to install apps on external storage?

.Clean up junk with SD maid
.Remove unnecessary files.
.Your last option is to resize system partition(risky).

What is your roms build number. this bug was in earlier builds of CM for MTK devices. So maybe try an earlier build or a different rom.

Replace all Aud And Audio Related files In Lib Folder and Hw Folder also...It will fix Vibration...

Also try libhardware_legacy.so.

This was a bug in old cm builds. Try a newer build it has been fixed now.

Did you flashed the correct Gapps? Sometime that is a Trouble.

do a full wipe and flash rom, this time without gapps and see if the problem persist.

That could be a video codec problem. try to fix that. or try a different video player.

Thanks for the nice words Zedkeil

First i want to say if you have a kitkat stock than first you should port a lollipop rom. because it will be easier and if you directly try to port nougat you might face bugs which could be very hard to solve.
and if its your first time porting an rom. I will suggest you start from basics by porting a kitkat to kitkat rom.
You can read our guides for basic under standing of rom porting.

mtk-rom-porting-guide-series

Here is the guide for porting lollipop rom

Port Lollipop/Marshmallow ROMs

If you read the guides i've posted. (including all other guides from this blog) and understand the basic concept of porting.
it will help you to understand which files are critical for system to boot and which are not.
This will reduce the chances of bugs and will also help you to eliminate bugs.

If you want to cut the crap and just get to porting ,here is the guide to port Nougat roms

How to port Linage OS 14.1 Nougat MT65xx 3.4.67+

And This guide will help you to port boot.img

How to port boot.img


And lastly about bootloops, bootloops are normal, i dont think there is someone who have ported his rom in the first go without any bootloops.
even the most experience developers face bootloops, so its just fine.

Most of the times there are some roms which just wont boot no matter what you do, but if you port another rom with the same method it boots fine.
So it all just depends on experience and trial and error. The more you read and experiment, the more you will learn.

Thanks Mr. Alex
It works perfectly, I successfully ported the Nougat Rom and a CM12.1 lollipop Hyperiod Custom Rom...

But I face VPN and Storage Bug...

My internal memory is unmounted, i cant see or access it but in recovery mode (Philz recovery) It can be mounted.

Any help pls?

Some earlier roms had this bugs. try to find a later cm12 build. Later cm12 builds are bugless and very easy to port.

Can you show some screenshots. how small is it. and also share stock and port roms build.props

Which method you followed for porting. as far as i remember you were porting mt6735 with 3.10.45 kernel right. if the guide is from this blog. you can share the link so it will help other users.

And of course the screenshot doesn't show up.