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!

(GUIDE)(PORT CM 12.1 ) MTK6592 CM 12.1 PORTING GUIDE (Only For Porters) :)

MT6592 CM 12.1 PORTING GUIDE
Lots of people asked me how i ported cm 12.1 from @fire855's compiled rom for kingzone k1 Turbo
First of all huge thanks to @fire855 and other Dev who helped him for bringing cm 12.1 on mt6592
Give support to him via pressing thanks or Donate , here is it's Link : http://forum.xda-developers.com/and...od-12-kingzone-k1-turbo-t3119908#post61000671
Requirements :
1. Stock Rom KK
2. Working Good Custom Recovery
3. Good Porter and Mind
Lets Start This Short Guide :
1. Download Latest Cm 12.1 from above link
2. Extract in a new folder
3. Use this tool LInk : http://forum.xda-developers.com/android/development/tool-convert-folder-to-ext4-format-t3099237
unpack .dat file and copy extracted system folder in new folder as stated in step 2.
4. Using @michfood's tool (link : http://forum.xda-developers.com/showthread.php?t=2036528)
change Kernel and Do necessary changes acc. to your stock's ramdisk
5. Copy new boot.img that created in step 4 and replace in new folder as stated in step 2.
6. From stock kk rom ...........extract libaudio.primary.default.so (system/lib) and modem.img (system/etc/firmware) nd replace in cm 12.1 's rom ................ in the same location
7. Delete meta-inf folder of cm 12.1's rom and extract this (link : https://www.sendspace.com/file/vnf0gi)
8. Open meta-inf's updater-script in notepad++ and change mountpoint of system acc. to your's phone
9. Pack the folder as in zip format and flash via recovery
( meta-inf, install ,system, boot.img, file context these files must there in zip )
10. Voila Rom booted .............if not comment
If Rom Booted ..............Follow this steps :
1. Download this apk (link : http://forum.xda-developers.com/showthread.php?t=2524485)
2. Go to Settings>developer>enable root and install apk from step 1
3. Open app and Set as permissive ,reboot Your device
4. Voila your wifi,bluetooth etc will start working, even Dual Sim
5. If you faced basedband unknown that mean restore your imei
6. For Home Key Bug , Edit generic.kl and mtk-kpd.kl (system/user/keylayout)
7. For Storage Bug, Edit Framework-res.apk and set sdcard1 as primary and edit boot's ramdisk MT6592.rc, fstab
8. For Other Bugs, Let Me Know
Notice : Always give thanks and link of @fire855's Rom Link
Credits : everyone (who's name i added in this guide and there's tools )
​

@[email protected] Thanks for a great guide, I was able to succesfully port the rom and it booted as well and after setting the selinux to permission my sims also started working but mic is not working, my device is MT6582 (Intex Aqua Speed). I have a working CM11 already ported for my device which is working perfectly fine. Also the soft keys (capacitive keys are not working nor even the power button). Please advise...

contactwajeeh said:
@[email protected]. . . . but mic is not working . . . .
Click to expand...
Click to collapse
The microphone is also not working in all apps (except Telephone where it work's fine) in the original CM12.1 by fire855 for the Kingzone K1. (The Rom this Porting Guide is based on).
That could be part of the problem.
Dominic

G-GFFD said:
The microphone is also not working in all apps (except Telephone where it work's fine) in the original CM12.1 by fire855 for the Kingzone K1. (The Rom this Porting Guide is based on).
That could be part of the problem.
Dominic
Click to expand...
Click to collapse
But its not working in calls as well. BTW I am using @moonrotation build as my base. I haven't asked for permissions to port it yet. But that should be fine as far as I dont do the public release of it.

What necessary changes i must do in ramdisk?help

contactwajeeh said:
But its not working in calls as well. BTW I am using @moonrotation build as my base. I haven't asked for permissions to port it yet. But that should be fine as far as I dont do the public release of it.
Click to expand...
Click to collapse
currently mic problem is there ....wait for fixes

contactwajeeh said:
@[email protected] Thanks for a great guide, I was able to succesfully port the rom and it booted as well and after setting the selinux to permission my sims also started working but mic is not working, my device is MT6582 (Intex Aqua Speed). I have a working CM11 already ported for my device which is working perfectly fine. Also the soft keys (capacitive keys are not working nor even the power button). Please advise...
Click to expand...
Click to collapse
edit keylayout's genric.kl etc

mirrr46 said:
What necessary changes i must do in ramdisk?help
Click to expand...
Click to collapse
like some some extra lines der in urs .

Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: No such file or directory
m_file:s0 failed: Operation not supported on transport endpoint
Error flashing Zip : Failed
Updating partition details...
Click to expand...
Click to collapse
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550

Traace said:
Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550
Click to expand...
Click to collapse
1. don't touch kernel header....change only kernel
2. u should try other recovery like philz
3. delete lost and found folder if present
4. use my meta-inf only....just change mountpoint of system........it seems u need good recovery with lp supported or philz recovery :fingers-crossed:

Thanks for guide.
My camera does not work and gallery does not see SD card.
How to fix it?

mirrr46 said:
Thanks for guide.
My camera does not work and gallery does not see SD card.
How to fix it?
Click to expand...
Click to collapse
1. camera icon in launcher is issue (for mt6592)
2. for storage...fixes r from mt6592.rc in this file read proper sysmlink and do changes acc. to it ,decompile framework-res.apk....set sdcard1 as primary ,fstab changes also needed

Enforcing to Permissive
Does anyone know how to make selinux permissive without any app,I tried to change ro.build.selinux and set it to 0 but it didn't work...does anyone know what to edit in ramdisk to make selinux permissive.?

Traace said:
Tried to port this, Device reboots right after vendor logo
I compare stock Ramdisk with CM12. There are no diff. At end both have same values. I changed Kernel and Kernel Header
I changed the updater script so it fits to my partition. It gave me strange errors:
Also @michfood's tool just ain't work here, i took the v4 for my x64 win8.1. The Program is unable to extract the Ramdisk path, so i was forced to use "MTK Firmware Adapter Tool"
Recovery:TWRP 2.8.1.0
SoC:MT6592
Device: Doogee DG550
Click to expand...
Click to collapse
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.

ADev_28 said:
Does anyone know how to make selinux permissive without any app,I tried to change ro.build.selinux and set it to 0 but it didn't work...does anyone know what to edit in ramdisk to make selinux permissive.?
Click to expand...
Click to collapse
/system/bin/setenforce 0
From any root terminal.
Thanks,

1. But i did port for mtk6582 (camera unfortunelty has stop)

chanaka89 said:
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.
Click to expand...
Click to collapse
Please let us know if u can let it boot
Ramdisk sBin shoudn't be a problem, if they really cause trouble, try copy the missing files from base dg550 kk to cm12

[email protected] said:
1.
Click to expand...
Click to collapse
Thank you very much... Your guide was very appreciated... Work like a charm..
I used the device MT6592 - BLU VIVO IV of the my friend for port CM12.1
Sent from my LIFE PLAY X KK using XDA Free mobile app

lopestom said:
Thank you very much... Your guide was very appreciated... Work like a charm..
I used the device MT6592 - BLU VIVO IV of the my friend for port CM12.1
Sent from my LIFE PLAY X KK using XDA Free mobile app
Click to expand...
Click to collapse
congo
Traace said:
Please let us know if u can let it boot
Ramdisk sBin shoudn't be a problem, if they really cause trouble, try copy the missing files from base dg550 kk to cm12
Click to expand...
Click to collapse
mirrr46 said:
1. But i did port for mtk6582 (camera unfortunelty has stop)
Click to expand...
Click to collapse
seems storage bug...u need to fix storage .............check guide and comments
chanaka89 said:
I'm still struggling to port this rom to DG550.
1. The tool you used to extract the kernel does not work in Windows 8.1 and Windows 10 (I got empty RAMDISK folder). So I switched back to Windows 7 and it worked well.
2. Compared both Ramdisk folders in Stock DG550 Kitkat and Stock Kingzone K1 Kitkat boot.img's.
There is no difference except in ueventd.rc file. I tried to mix DG550 kernel and Kingzone Z1 stock Ramdisk with DG550 Kitkat rom. It didn't boot at first. The problem was in ueventd.rc file. See line 152 (Mali Node). After replacing ueventd.rc file from DG550 ramdisk it booted and worked well (stock kitkat rom). So both the stock ramdisks are identical if ueventd.rc file is replaced.
3. But it fails when porting the boot.img for CM12.1. Theoretically CM12.1 ramdisk should work with DG550 kernel for CM12.1 rom without any changes (except ueventd.mt6592.rc). It does not pass the boot logo.
4. Also I noticed that there's some issue in sbin folder in ramdisk.
Click to expand...
Click to collapse
i don't think so....again try and don't touch ramdisk

[email protected] said:
congo
seems storage bug...u need to fix storage .............check guide and comments
i don't think so....again try and don't touch ramdisk
Click to expand...
Click to collapse
How to solve storage bug??
Device booted.Not able to mount/access storage. ??

[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

How to Port Samsung Rom to other Samsung devices (Small Update as of 10/13/2018)

{
"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"
}
(Success Stories)
jonathanmohamed said:
I have successfully ported s7 and n7 firmware using this guide.
Awesome guide!. 9/10
Click to expand...
Click to collapse
corsicanu said:
@malbert16442 this is pure GOLD. Gave you all my thanks for today. I'll try it myself today. Also waiting patiently for updates [emoji28] . Cheers!
Click to expand...
Click to collapse
armaowl said:
is the reason i was allowed me to port my own Rom!
Click to expand...
Click to collapse
1. Kernel is second most important because it determines if rom boots or whether
we could access a log.
2. Since we are trying to boot a rom not meant to be on our device, it could be alittle hard getting this thing to run.
3 Contact a kernel dev and ask them for adb insecure kernel or a kernel with usb debugging enabled at boot. This will help us obtain those logs at boot.
4. In some rare cases Logs might show that specific kernel services are not accessible.
In this case we only change the init.environ.rc. Which has the frameworks needed to boot.
5. If you can't get kernel logging at boot use this in recovery after 2 mins of booting.
Code:
adb pull /data/tombstones
6.Update
DaKillaz98 said:
Hello All! I am posting this fix because on my Note Edge, I wasn't able to get logcat or adb access at boot, no matter what property I set, it didn't work. I finally figured out a way to get true logcat right as the boot animation comes up.
First off, you NEED Notepad++ if you don't want garbage clumped up editing.
1. In Android Image Kitchen, depack the Boot image.
2. Then, go to split image and modify boot.img-cmdline and add
Code:
buildvariant=userdebug
.
3. Save that file, then go to the ramdisk folder and edit your default.prop. change these values.
Code:
ro.secure=1 > ro.secure=0
ro.adb.secure=1 > ro.adb.secure=0
ro.debuggable=0 > ro.debuggable=1
4. Save that file, then go to init.rc, and use find to search for adbd to jump to this.
Code:
# adbd is controlled via property triggers in init.<platform>.usb.rc
5. Change the original code from
Code:
service adbd /sbin/adbd --root_seclabel=u:r:su:s0
class core
socket adbd stream 660 system system
disabled
seclabel u:r:adbd:s0
TO:
service adbd /sbin/adbd --root_seclabel=u:r:su:s0
disabled
socket adbd stream 660 system system
seclabel u:r:adbd:s0
6. Change this to new code.
Code:
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
TO:
# allows adbd at boot with property trigger below
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04E8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/functions adb
write /sys/class/android_usb/android0/enable 1
start adbd
7. Rebuild the kernel and install in TWRP or however you install kernels, ADB will be accessible right at boot so nothing is lost during logging. If your kernel doesn't need this, don't bother, but if like me, you couldn't get anything, this will fix your issues.
In some cases, you will still need to push adb_keys to /data/misc/adb/, however.
@malbert16442 Please consider putting this in OP for those who have issues getting logcat at boot.
Click to expand...
Click to collapse
Part 2
Adb is key in any port. Adb is the secret. It gives us the ability to access logs be able to debug issues in our ROM.
1. Download adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Thanks Member @Snoop05
2. Test adb by using 'adb devices" in cmd
You should see online
3. If offline try using adb kill-server and repeat step 2.
4. When making a loging for these ports we use the phrase adb logcat *:E > filename
this ensures that we filter the logs by errors and remove the long set of lines like thermal updates ...etc
Part 3
In order to port firmware
1. Download Stock firmware extract it with tool
Websites to get stock firmware are
http://updato.com/firmware-archive-select-model
or https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
2.We will deodex our rom using Fulmics or similar deodexer
Either a kitchen like "http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296/page26" or similar.
Thanks @SuperR
https://forum.xda-developers.com/android/software-hacking/tooll-03-12-fulmics-deodexer-1-0-t3512081
Thanks @xpirt
3. Learn how to use APK DECOMPILE TOOLS SUCH AS TICKLEMEANDRIOD
http://forum.xda-developers.com/showthread.php?t=1633333
Thanks @Ticklefish
4. Remove Apps Priv-app and Framework of base. In a new folder use Fulmics to deodex this. Store somewhere safe.
5. Deodex Port and copy the Apps, Framework and Priv-app into the Base of stock rom.
6. In Ticklemeandriod you notice we have 6 work Areas. For our Roms we will only need two. The most common files we will use are services.jar, and framework.jar.
7. Take the services and framework our our Port and decompile in work area 1.
8. Take the services and framework of our Base and decompile in work area 2.
9. We will Perform a quick Step to help if App signatures become corrupt or cannot be read.
Follow this guide by @ikrom
http://forum.xda-developers.com/showpost.php?p=62496153&postcount=2957
10. After this lets move to debugging our apps and frameworks.
Part 4 (Tools and debugging)
My favorite tools to use include WinMerge and FileSeek
1. Winmerge enables us to compare two files. For example a stock jar and one of our port.
2. File seek allows us to search for a specific references.
I use file seek to search for weird terminology I see on my log.
3. Terminology
Part 5 ( Terminology)
1. In a logcat we are looking for three things when debugging. "E JavaBinder:", "E art", "E AndroidRuntime: FATAL EXCEPTION:"
2. The order to debug we search in logcat. When beginning it is not specific but, I usually search for Art errors first.
3. So for example if I get in my logcat
Code:
"01-01 01:26:25.169 5599 7183 E JavaBinder: java.lang.NoSuchMethodError: No virtual method activityPauseTrigger(Landroid/content/Intent;Landroid/content/pm/ActivityInfo;Landroid/content/pm/ApplicationInfo;)V in class Lcom/android/internal/app/ActivityTrigger; or its super classes (declaration of 'com.android.internal.app.ActivityTrigger' appears in /system/framework/framework.jar:classes2.dex)"
I got the location which is framework jar Class2
Code:
activityPauseTrigger(Landroid/content/Intent;Landroid/content/pm/ActivityInfo;Landroid/content/pm/ApplicationInfo;)V is the missing info in the port smalis and
log says it is somewhere in
Code:
Lcom/android/internal/app/ActivityTrigger; or the files with idential names to Activity trigger
4. In this case missing method could be found in stock smali. This is where we use win merge to cleanly copy new method from stock to port.
5. But Mike what if The logcat doesnt tell me location. We will then use fileseek in this instance.
Example: Log tells me
Code:
"01-01 00:24:17.509 7524 7539 E JavaBinder: java.lang.UnsatisfiedLinkError: No implementation found for void com.android.internal.app.ActivityTrigger.native_at_pauseActivity(java.lang.String) (tried Java_com_android_internal_app_ActivityTrigger_native_1at_1pauseActivity and Java_com_android_internal_app_ActivityTrigger_native_1at_1pauseActivity__Ljava_lang_String_2)
"
No implementation means that we must remove this file as it is not found in the libs. What location? We dont know yet ?
Code:
com.android.internal.app.ActivityTrigger.native_at_pauseActivity(java.lang.String
is what we are looking for
According to fileseek I would look for pauseActivity because it is a keyword
According to file seek I may get 100 references but I see one that says
Code:
.method ActivityTrigger.native_at_pauseActivity
I would then use winmerge to cleanly delete/copy the file from my stock smali to the new one. From the location I found in Fileseek.
6. Let me give a example of a Runtime error.
Code:
"07-25 09:17:08.975 16379 16379 E AndroidRuntime: java.lang.NoSuchMethodError: No interface method setDataFromNSFLP(ILandroid/os/Bundle;)V in class Landroid/location/ILocationManager; or its super classes (declaration of 'android.location.ILocationManager' appears in /system/framework/framework.jar)
So log told us to look in framework for a file with
Code:
setDataFromNSFLP(ILandroid/os/Bundle;)V
Boot up file seek and repeat steps above.
Part 6
So we booted now what.
Lets now work on fixing local errors.
Use logcat to possible fcs and reboots.
All firmware edits are different so this guide will help if you are learning the way android works.
What to look out for
Remember the Base folder we deodexed. We will use this to help fix issues in our rom.
1. Take the McRegistry Folder and ffffffff0000000 File move this to our booted rom.
2. Now in the Ported firmware copy the Fonts folder and the files named font in /etc to our booted rom.
3. Delete these folders - " preloadedmdm ", " sipdb " and " tts from booted rom and replace with that from ported firmware.
4. Open " Media " folder in booted rom
Delete Audio folder
Replace with Ported firmware audio folder.
5. In /etc/permission add the missing software permissions not hardware like slocation or camera-flash.
6. In build-prop
Replace these values with that of port.
Code:
ro.build.scafe.size=
ro.build.scafe.shot=
ro.build.scafe.cream=
ro.build.scafe.version=
ro.com.google.gmsversion=
ro.build.version.sdl=
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.config.media_sound=
ro.config.ringtone_2=
ro.config.notification_sound_2=
7. Add this code to build-prop
Code:
wlan.wfd.hdcp=disable
Let's Fix Messages and Phone FCS on first boot
1. From ported from take the libselinux.so to fix message fcs
2. To fix Phone fcs take the mapconprovider.xml from port
64 bit firmware to 32bit
1. Replace 64 bit libs with 32 bit alternatives.
2. You could find 32 bit libs in 32 bit firmware.
32bit all that could be found will be attached here for all users
Fix location problems in Rom
With our services.jar decompiled take these smalis from base and use Winmerge to copy to Port jar.
Code:
services.jar\smali\com\android\server\location folder to that of port
also take the
Code:
services.jar\smali\com\android\server\LocationManagerService$xxx
Smalis and move from base to port location.
1. Take NFC.apk and Bluetooth.apk from base and move to new Rom folder.
OR A more complex NFC fix would be to look in PackageManagerService.smali
of services.jar
look for the NFC model of the device you are porting from
1. So use FileSeeker
to search for method with "supportNfc"
2. Replace it with your model number.
Example the NFC number of Note 7 is S3FWRN5
I would replace it with the NFC number of S5 which is NXP_PN547C2
Blur
https://forum.xda-developers.com/showpost.php?p=69547250&postcount=10031
AOD FRAMEWORK FIX
Credits :
@Patrick.H (NX Team)
@karkasss (NX Team)
@Develoid ALT and F4 (AOD touch / Bluelight filter fix)
@asc1977, @DaOldMan (AOD brightness control)
(Please copy & paste when you add our credits)
Download this file extract to services.jar
https://mega.nz/#!KgMxwQDR!g0yy7a6Izk8U8szRsggaZAXLaF4pjSMYAc8p6kOjIs4
Compare the PowerManagerService Smails.
then recompile
OR
thanks @oluwaponmile
follow this guide
https://forum.xda-developers.com/showpost.php?p=69594939&postcount=8139
Lets fix ported Cameras
Code:
[SIZE="3"]GUIDE IS IN PROGRESS[/SIZE]
Debug solution not fix:
This will be a hard thing to accomplish. Also make sure that Camera is recompiled using New signatures.
First lets find the native resolutions of your camera. For this we look in native camera apk.
Find the native resolutions in arrays or strings xml.
Save resolutions found in port apk for later reference. These are the values we are going to replace with stock hexadecimal values.
Use a Decimal to Hexadecimal Converter to find the values for the resolutions in smali.
For example 1080 would be 438 and 1920 would be 780.
For this value we will intrepid the hexadecimal value as 0x438 and 0x780 respectively in andriod.
When we are looking for the resolutions in port apk we grep the values based on the hexadecimal.
So in an example if resolution of port camera is 1920x1080 and stock is 1080x1920, then in smali we might get a value of 0x438, 0x780 in assortment. Simply replace 0x438 with 0x780 and 0x780 with 0x438.
Replace these values in port apk with the stock equivalent. Recompile.
Keep this open in one window.
Now open up camera and take log.
Most likely you would get a error saying missing resolution
KNOX STATUS REVERT (Kernel)
@topjohnwu for reset prop
The reset prop source was removed from topjohnwu thread however you could use the prebuilt binary in his magisk release zips.
1. Pick your device arch and remove binary from zip
2. Now download a tool to extract boot images.
3. Navigate to sbin and drop your resetprop binary.
4. Get back to root directory and add this file http://www106.zippyshare.com/v/AzldZO7A/file.html
5. Now in init.rc add this code
Code:
# Call Knox Reset
service knox-daemon /system/bin/sh /init.knox.sh
class main
user root
oneshot
Device Specific Section
(Section will detail device specific edits for particular devices once users post.)
mitko7411 said:
So I haven't really made a new list of smalis for porting roms, but here's the ones just to boot ANY 6.0.1 firmware on J5 2015.
Debug
GpsLocationProvider
KnoxVpnPacProcessor
TADriver
SchedPolicyManager
Click to expand...
Click to collapse
No Pm type message below.
Also I will post below all the logs I used to boot Note 7 firmware on my s5

All the edits used to boot Note 7 firmware on S5 it is different for every device.
https://mega.nz/#!8ZtzWCJR!rqTrvD5K3pUvHOAMq_540L_z7Hx0LFZawSzpobFDF98

Thanks for this guide..

A nice guide. Thanks! :highfive:

Ticklefish said:
A nice guide. Thanks! :highfive:
Click to expand...
Click to collapse
Thanks
Sent from my SM-A810S using Tapatalk

Great Extremely helpful, time for noobs to port now

Thanks mate you finally did it big help

Thanks manYou helped me.

Well ,,
Malbert , im sure 100% , too much things missed in ur guide mate , this way how u do it isn't an how to ported rom from different devices , or high end to previous years device's , sorry to say this but this isn't a full guide & its just a point for drop app/prev/fram to ur stock base then try to booted then with bootloop logcat u will got what's the missing things well ,
Sorry to say it but this isn't a Full guide for HOW TO PORT Roms , ....
Edit ::
Next time try to be more specific & gives more details & which files / jars / smali / apks / libs / xml / config & which we can use & got from ported base to stock base ,

thereassaad said:
Well ,,
Malbert , im sure 100% , too much things missed in ur guide mate , this way how u do it isn't an how to ported rom from different devices , or high end to previous years device's , sorry to say this but this isn't a full guide & its just a point for drop app/prev/fram to ur stock base then try to booted then with bootloop logcat u will got what's the missing things well ,
Sorry to say it but this isn't a Full guide for HOW TO PORT Roms , ....
Edit ::
Next time try to be more specific & gives more details & which files / jars / smali / apks / libs / xml / config & which we can use & got from ported base to stock base ,
Click to expand...
Click to collapse
Thanks assaad will fix when I get time I get what you are saying but this is a intro. I can't explicitly state which jars apks or libs are needed because they are all different for different devices. XML and permissions I could elaborate on but you can't expect me to possibly give a overview of everything right. Hope you understand thanks. I never explicitly stated this was a full guide and you shouldn't treat it as such.
Sent from my SM-A810S using Tapatalk

Well my friend , i never do ,,
For example without editing systemserver.smali the rom will never booted & u know this very well , i just means to be very static for some useful tips for such framework / & well known smali that need to be our eyes on them .. that's all my point means ..
Good luck my friend

thereassaad said:
Well my friend , i never do ,,
For example without editing systemserver.smali the rom will never booted & u know this very well , i just means to be very static for some useful tips for such framework / & well known smali that need to be our eyes on them .. that's all my point means ..
Good luck my friend
Click to expand...
Click to collapse
Ohh I understand what you are saying. I will expand on this guide when I get time hopefully you also could help support and add to this guide as XDA is a community. ? Over time we could help many users thanks for your advice.
Sent from my SM-A810S using Tapatalk

@malbert16442 Can you help me with my S5 which is G9008V China Mobile variant?
I can't boot on Thunderbolt A8 rom...
What should I Fix?

I have successfully ported s7 and n7 firmware using this guide.
Awesome guide!. 9/10
I have one small issue, in your log n79 you have "E SQLiteDatabase: " How did you fix this error? I am having the same issue, with one of my builds.
Solved:
FileSeek ftw!

jonathanmohamed said:
I have successfully ported s7 and n7 firmware using this guide.
Awesome guide!. 9/10
I have one small issue, in your log n79 you have "E SQLiteDatabase: " How did you fix this error? I am having the same issue, with one of my builds.
Solved:
FileSeek ftw!
Click to expand...
Click to collapse
Thanks happy for you. How would you rate your level of expertise so I could set a difficulty level for this
Sent from my Pixel XL using Tapatalk

Learned new debug problems in Sammy Roms updating guide soon, making it more appealing too. Happy that one person actually made a port from this guide.

thnx alot @malbert16442 .... but i have 2 bugs i didnt manage to fix
1-wifi work and i can see available network but when i try to connect i get 'failed to connect' .. I tried to use my stock wifi-service.jar but the device not boot)
2-Camera work (back and front) and i can take photos...but when i try to record video i get 'Recording faield' fixed

Allooosh98 said:
thnx alot @malbert16442 ...using this guide i ported S7e, G532F to j7.....but i have 2 bugs i didnt manage to fix
1-wifi work and i can see available network but when i try to connect i get 'failed to connect' .. I tried to use my stock wifi-service.jar but the device not boot)
2-Camera work (back and front) and i can take photos...but when i try to record video i get 'Recording faield' fixed
Click to expand...
Click to collapse
When you add wifi serivce jar you have edits to make in framework you will see in your log
But don't work I have a fix for stock files too. I work on this guide this weekend make it look better

Okay so alot of people are pming me about fixing camera will post solution or debug solutions here soon

hey @malbert16442 bro can u help me to fix the problem?? there is a E art error in logcat that i cant fix it :
E art : No implementation found for int android.os.storage.sensitive.SecureStorageLSM.lsmInitialize() (tried Java_android_os_storage_sensitive_SecureStorageLSM_lsmInitialize and Java_android_os_storage_sensitive_SecureStorageLSM_lsmInitialize__)
i checked smali files but its as same as stock,i attached the log,if its ok look at it and tell me what should i do

Mediatek Helio P10 Development (Porting guides, bug fixes and more)

{
"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"
}
​Welcome to my all in one thread for Meditake Helio P10 thread.
The thread contains porting guides, bug fixes, general informations about the Helio P10 Chipset.
It goes on 3 parts:
Part 1: General Information
Part 2: Normal Porting guides, go to post #2
Part 3: Crossporting guides, go to post #3
Part 4: Bugs fixes (all in one place), go to post #4
Part 1: General information
Helio P10 is a SoC manufactured by MediaTek Inc. in the Q3 of 2015. It has 8 Cortex-A53 Cores clocked between 1.5 GHz and 2.0 GHz depending on the manufacturer. It supports the big.LITTLE technology and is an improved version of the MT6752. In the 8 cores, 4 are clocked at either 1.5 GHz, 1.8 GHz or 2.0 GHz. The other 4 cores are clocked between 1.0 GHz and 1.5 GHz.
It integrates the Mali-T860 GPU with 2 cores clocked between 500 MHz and 700 MHz. The Chipset supports LTE and other various technologies we could find on the MT6752. Compared to the MT6753, the Helio P10 is way faster but still appears to be somewhat slower than some MT6752. The fact is that the latter has all the 8 cores clocked at 1.7 GHz. That gives it the advantage in benchmarks for the price of the battery, however.
Currently, the following processors are built-on Helio P10 hardware:
MT6738 = 1.5 GHz + 1.0 GHz (Mali-T860MP2 - 500 MHz)
MT6750 = 1.5 GHz + 1.0 GHz (Mali-T860MP2 - 500 MHz)
MT6750T = 1.5 GHz + 1.0 GHz (Mali-T860MP2 - 700 MHz)
MT6755 = 1.8 GHz + 1.2 GHz (Mali-T860MP2 - 700 MHz) or 2.0 GHz + 1.2 GHz (Mali-T860MP2 - 700 MHz)
MT6755T (Helio P15) = 2.2 GHz + 1.2 GHz (Mali-T860MP2 - 800 MHz)
So, it's clear now that:
MT6738, MT6750 and MT6750T are the same. Just called differently ...
MT6750 is an underclocked version of MT6755. Both use the same hardware which is Helio P10 board. It is like MT6735 & MT6753; both use MT6735 board.

Normal Porting guides
Now that you know your hardware, let's move on with porting.
I will not tell you how to get your stock ready. I assume you already how to do that.
I will instead go straight with the porting guides.
There are: normal porting and crossporting.
Before you start, understand that:
These guides have been tested on a MT6750 device i.e Doogee Y6. The software is AOSP with a slightly modified frameworks. Devices with custom skins are usually known to be hard to handle. AmigoOS based devices are always hard to manage when it comes to rom porting. Same way, it is hard to port AmigoOS to another device.
I take no responsiblility if anything go wrong. Your device, your choices, your responsibility.
Normal Porting guides
Note: By normal, I meant MT6755 to MT6750 and vice-versa.
Method 1: Port just the kernel
Unpack it with carliv image kitchen and copy boot.img-kernel from stock unpacked boot to port unpacked boot folder and repack. Use the modded boot.img. If the rom doesn’t boot, then move to crossport method. Bug fixing is after that method.
Method 2: Files replace method
Note: Go with either A or B.
A) Simplified process
Download this archive from here mega.nz
Unpack it. Replace its files with those from your stock rom. You can delete those that aren’t in your stock rom but present in the archive.
Repack the archive. And name it for example Cross6.0_device-name.zip (Cross6.0_Y6.zip)
Now, download any rom for 6750 or 6755. Port kernel as stated in the beginning of this guide. Flash the ROM and the ported boot.img. You can use SPFT or TWRP.
Boot to TWRP if you flashed with SPFT.
Flash the patch you made in step 3. Reboot and test. You can also on step 4 copy the contents of your patch and paste them into the unpacked ROM that you want to port. And then port the kernel and make the flashable ROM directly. I have also attached a file having the files you need to make the patch. You can download it if you don’t like the step 2 of this guide. Here is the file mega.nz
Click to expand...
Click to collapse
B) The other method
Download or clone this repo https://github.com/Deepflex/android_vendor_elephone_p9000
Unpack it (if you’ve downloaded it instead of cloning).
Make your own vendor folder by referring to the files in the unpacked p9000 repo. If a file is in p9000 repo but isn’t in your stock rom, then skip it. You can also download this file mega.nz
Refer to the files stated inside it to make your own repo folder. Remember: file names in lib/hw and lib64/hw will differ according to your CPU. For MT6750, it will be for example audio.primary.mt6750.so. It is the same as audio.primary.mt6755.so
After making your own repo as stated in step 3, copy files from this repo folder to your port rom and replace when prompted. You can also make a flashable zip file so that you can flash that zip on every rom you want to port without unpacking its system.img. Download the META-INF from this link mega.nz , move it in a folder called PATCH. Make another folder inside that one alongside META-INF and name it system, copy folders from your own repo (bin, etc, lib, lib64 and vendor), paste them in system folder of PATCH. Zip both META-INF and system folders.
It is important to edit the build.prop IF YOU ARE CROSSPORTING 6755 to 6750 and vice-versa! Edit it and change these values: ro.board.platform=mt6750 (or MT6755, depending on your CPU). ro.sf.lcd_density=320 (or your stock or preferred DPI, 320 for HD displays; 480 for FHD displays)
Port the kernel as stated in the first method. But you’ve to also copy this file from ramdisk: fstab.mt6755. Some roms will refuse to boot with this method, like EMUI 4.1. So instead, do this: Copy these files from port ramdisk to stock ramdisk: default.prop; init.environ.rc; sepolicy; services_contexts. Repack stock boot.img and use it. Some roms will still bootloop even with that. So instead, copy these from stock ramdisk to port ramdisk: all files with mt6755 in their name in your stock ramdisk. Replace when prompted. Repack port boot.img and flash it.
Click to expand...
Click to collapse

Crossporting guides
Before you start, note that this part is intended for advanced users. Expect least support in this section as it's all about experimenting. If it works, horray! Great! Else, I ... DON'T ... KNOW, MAN;
Here I will share how to port ROMs from MT6735 and MT6753 to MT6750 and MT6755.
Since MT6735 and MT6753 use the same hardware e.g MT6735 and also MT6750 and MT6755 use the same hardware MT6755 ; it’s possible to port ROMs from MT6735 and MT6753 to MT6750 and MT6755.
The guide goes on four parts:
Part 1: System Folder patching
Part 2: Boot.img patching
Part 3: Additional steps
Part 4: Bug fixes
All steps are important. You cannot skip one of them.
Before you start, note that the guide has been tested on a MT6750 device. It should work on any MT6750 or MT6755 device, technically. CyanogenMod/LineageOS based ROMs may not be ported using this guide.
Part 1: System Folder patching
Notes :
If the name is in italic it means it’s a folder and you have to copy it entirely.
If you have MT6755, you should copy the files having MT6755 in their names in lib/hw & lib64/hw i.e camera.mt6755.so
If you can’t find a file in your stock ROM, skip it.
1) Now, copy these from your stock rom to the port one:
Code:
*** BIN ***
6620_launcher
akmd8963
akmd8975
akmd09911
ami304d
applysig
audiocmdservice_atci
bmm050d
ccci_fsd
ccci_mdinit
emdlogger1
factory
fuelgauged
geomagneticd
gsm0710muxd
gzip_static
kpoc_charger
mc6420d
md_ctrl
mdlogger
memsicd
memsicd3416x
meta_tst
mobile_log_d
msensord
mtk_agpsd
mtkrild
muxreport
netdiag
nvram_daemon
orientationd
pq
s62xd
slpd
terservice
thermal_manager
vold
wifi2agps
wmt_loader
*** ETC ***
audio_param (whole folder)
firmware (whole folder)
fmr (whole folder)
mddb (whole folder)
ecc_list.xml
factory.ini
mtklog-config.prop
*** PERMISSIONS ***
android.hardware.bluetooth.xml
android.hardware.bluetooth_le.xml
android.hardware.camera.xml
android.hardware.faketouch.xml
android.hardware.location.gps.xml
android.hardware.microphone.xml
android.hardware.sensor.accelerometer.xml
android.hardware.sensor.light.xml
android.hardware.sensor.proximity.xml
android.hardware.telephony.gsm.xml
android.hardware.touchscreen.multitouch.distinct.xml
android.hardware.touchscreen.multitouch.jazzhand.xml
android.hardware.touchscreen.multitouch.xml
android.hardware.touchscreen.xml
android.hardware.usb.accessory.xml
android.hardware.usb.host.xml
android.hardware.wifi.direct.xml
android.hardware.wifi.xml
android.software.live_wallpaper.xml
android.software.managed_users.xml
android.software.sip.voip.xml
android.software.sip.xml
android.software.webview.xml
com.android.location.provider.xml
com.android.media.remotedisplay.xml
com.android.mediadrm.signer.xml
com.google.android.maps.xml
com.google.android.media.effects.xml
com.google.widevine.software.drm.xml
handheld_core_hardware.xml
media_codecs.xml
platform.xml
*** FRAMEWORK ***
com.google.widevine.software.drm.jar
*** LIB ***
lib3a.so
lib3a_sample.so
libacdk.so
libaed.so
libaudiocompensationfilter.so
libaudiocomponentengine.so
libaudiocustparam.so
libaudiopolicymanager.so
libbessound_hd_mtk.so
libblisrc.so
libblisrc32.so
libbluetooth_mtk.so
libbluetooth_mtk_pure.so
libbt-vendor.so
libbwc.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.device1.so
libcam.device3.so
libcam.exif.so
libcam.exif.v3.so
libcam.hal3a.v3.dng.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.metadata.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcam.utils.cpuctrl.so
libcam.utils.sensorlistener.so
libcam.utils.so
libcam_hwutils.so
libcam_mmp.so
libcam_platform.so
libcam_utils.so
libcam1_utils.so
libcam3_app.so
libcam3_hwnode.so
libcam3_hwpipeline.so
libcam3_pipeline.so
libcam3_utils.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libccci_util.so
libcustom_nvram.so
libcvsd_mtk.so
libdngop.so
libdpframework.so
libdrmmtkutil.so
libdrmmtkwhitelist.so
libfeatureio.so
libfeatureiodrv.so
libfgauge.so
libfile_op.so
libfmcust.so
libgas.so
libged.so
libgpu_aux.so
libgralloc_extra.so
libHEVCdec_sa.ca7.android.so
libhwm.so
libimageio.so
libimageio_plat_drv.so
libion_mtk.so
libJpgDecPipe.so
libJpgEncPipe.so
libm4u.so
libmal.so
libmatv_cust.so
libmdfx.so
libmdloggerrecycle.so
libmemoryDumpEncoder.so
libmhalImageCodec.so
libMiraVision_jni.so
libmmprofile.so
libmmsdkservice.so
libmnl.so
libmp4enc_sa.ca7.so
libmrdump.so
libmsbc_mtk.so
libmtcloader.so
libmtk_drvb.so
libmtk_mmutils.so
libmtkcamera_client.so
libmtkjpeg.so
libmtklimiter.so
libMtkOmxCore.so
libMtkOmxVdecEx.so
libMtkOmxVenc.so
libmtkshifter.so
libn3d3a.so
libnvram.so
libnvram_daemon_callback.so
libnvram_platform.so
libnvram_sec.so
libnvramagentclient.so
libperfservicenative.so
libpq_prot.so
libpqservice.so
librilmtk.so
libshowlogo.so
libSonyIMX230PdafLibrary.so
libspeech_enh_lib.so
libstagefrighthw.so
libSwJpgCodec.so
libvc1dec_sa.ca7.so
libvcodec_oal.so
libvcodec_utility.so
libvcodecdrv.so
libvp8dec_sa.ca7.so
libvp9dec_sa.ca7.so
mtk-ril.so
mtk-rilmd2.so
*** LIB/EGL ***
egl.cfg
libGLES_mali.so
*** LIB/HW ***
audio.primary.mt6750.so
audio_policy.default.so
bluetooth.default.so
camera.mt6750.so
gps.mt6750.so
gralloc.mt6750.so
hwcomposer.mt6750.so
lights.mt6750.so
memtrack.mt6750.so
sensors.mt6750.so
*** LIB/SOUNDFX ***
libdownmix.so
*** LIB64 ***
lib3a.so
lib3a_sample.so
libacdk.so
libaed.so
libaudiocompensationfilter.so
libaudiocomponentengine.so
libaudiocustparam.so
libaudiopolicymanager.so
libbessound_hd_mtk.so
libblisrc.so
libblisrc32.so
libbluetooth_mtk.so
libbluetooth_mtk_pure.so
libbwc.so
libcam.camadapter.so
libcam.camnode.so
libcam.camshot.so
libcam.client.so
libcam.device1.so
libcam.device3.so
libcam.exif.so
libcam.exif.v3.so
libcam.hal3a.v3.dng.so
libcam.hal3a.v3.so
libcam.halsensor.so
libcam.iopipe.so
libcam.metadata.so
libcam.metadataprovider.so
libcam.paramsmgr.so
libcam.sdkclient.so
libcam.utils.cpuctrl.so
libcam.utils.sensorlistener.so
libcam.utils.so
libcam_hwutils.so
libcam_mmp.so
libcam_platform.so
libcam_utils.so
libcam1_utils.so
libcam3_app.so
libcam3_hwnode.so
libcam3_hwpipeline.so
libcam3_pipeline.so
libcam3_utils.so
libcamalgo.so
libcamdrv.so
libcameracustom.so
libccci_util.so
libcustom_nvram.so
libcvsd_mtk.so
libdngop.so
libdpframework.so
libdrmmtkutil.so
libdrmmtkwhitelist.so
libfeatureio.so
libfeatureiodrv.so
libfile_op.so
libfmcust.so
libgas.so
libged.so
libgpu_aux.so
libgralloc_extra.so
libhwm.so
libimageio.so
libimageio_plat_drv.so
libion_mtk.so
libJpgDecPipe.so
libJpgEncPipe.so
libm4u.so
libmal.so
libmatv_cust.so
libmdfx.so
libmdloggerrecycle.so
libmhalImageCodec.so
libminiui.so
libMiraVision_jni.so
libmmprofile.so
libmmsdkservice.so
libmrdump.so
libmsbc_mtk.so
libmtk_drvb.so
libmtk_mmutils.so
libmtkcamera_client.so
libmtkjpeg.so
libmtklimiter.so
libMtkOmxCore.so
libmtkshifter.so
libn3d3a.so
libnvram.so
libnvram_daemon_callback.so
libnvram_platform.so
libnvram_sec.so
libnvramagentclient.so
libperfservicenative.so
libpq_cust.so
libpq_prot.so
libpqservice.so
librilmtk.so
libSonyIMX230PdafLibrary.so
libspeech_enh_lib.so
libstagefrighthw.so
libterservice.so
libvcodec_oal.so
libvcodec_utility.so
libvcodecdrv.so
mtk-ril.so
*** LIB64/EGL ***
libGLES_mali.so
*** LIB64/HW ***
audio.primary.mt6750.so
audio_policy.default.so
camera.mt6750.so
gps.mt6750.so
gralloc.mt6750.so
hwcomposer.mt6750.so
lights.mt6750.so
memtrack.mt6750.so
sensors.mt6750.so
*** LIB64/SOUNDFX ***
libdownmix.so
*** VENDOR/LIB ***
libwvdrm_L3.so
libwvm.so
libWVStreamControlAPI_L3.so
*** VENDOR/LIB/DRM ***
libdrmwvmplugin.so
*** VENDOR/LIB/MEDIADRM ***
libwvdrmengine.so
*** XBIN ***
mnld
2) After that, remove the files with 6735 or 6753 in their names from Port rom’s lib/hw and lib64/hw.
3) Edit build.prop and change all instances of 6735 or 6753 to 6750 or 6755. And change the DPI to the one that matches your stock DPI as well as the rotation line value (usually 0).
Click to expand...
Click to collapse
Part 2: Boot.img patching
You can patch boot.img using various methods. Try them all if needed!
Method 1: Stock boot.img directly
Use stock boot.img directly (will likely cause bootloop)
Method 2: Patch the Stock boot.img
Unpack Stock and Port boot.img
Copy these from port: default.prop, init.environ.rc, sepolicy, services_contexts.
Paste them in stock boot.img and replace the existing ones.
If there is a proprietary rc file (for example: init.huawei.rc, init.miui.rc, init.flyme.rc etc), copy it from port to stock and then open the stock init.rc file and add import /init.proprietary_file_name.rc at the beginning. Note that the proprietary_file_name corresponds to the name given by the OEM to the file (init.miui.rc for instance, miui is the name here).
Pack the boot.img
The ROM should boot, but chances are that few things will force close. if so, add the extra files from port ramdisk. This step is too sensitive! Apply with care. Some proprietary files in the ramdisk can cause the device to bootloop or worst stuck on the kernel logo.
Method 3: Patch the port boot.img
Open your unpacked stock boot. Copy these files from stock boot to port boot:
Code:
boot.img-base
boot.img-board
boot.img-cmdline
boot.img-kernel
boot.img-kernel_offset
boot.img-pagesize
boot.img-ramdisk_offset
boot.img-ramdisk-compress
boot.img-tags_offset
Open stock ramdisk and copy all the files with 6755 in their names.
Paste them in port ramdisk. Delete any file in port ramdisk that has 6735 in its name.
Select all the files in port ramdisk folder. Click edit with Notepad ++ (you need to have installed Notepad ++ of course).
In Notepad ++, click “Ctrl + H”. In “Find what” column, write 6735. In “Replace with” column write 6755. Click “Replace All in All opened documents”.
Now, right click on a file name in Notepad ++ (on the top), choose “Close all BUT this”. You’ll be prompted if you want to save the changes to the files modified. Always choose “Yes”.
Pack the boot.img
At this point, your ROM should boot but you’ll eventually suffer wifi and bt switches problems (or even the camera opening). If those happen, copy init.project.rc and meta_init.project.rc from your stock ramdisk to port ramdisk. Replace existing ones and pack the boot.img
Click to expand...
Click to collapse
Part 3: Additional steps
Note: Because it says additional doesn’t mean it’s expandable!
After copying the files in part 1 to the port ROM, your ROM should boot (80% of the cases). But you will need this step to fix the bugs like camera, audio and everything else.
Open your Stock ROM and the Port ROM side by side.
Go to stock/bin and copy everything, paste the files in port/bin. When prompted, DO NOT REPLACE!
Repeat the same process for these folders: ETC, PERMISSIONS, LIB, LIB/HW, LIB64, LIB64/HW, VENDOR, XBIN.
Click to expand...
Click to collapse
That’s it for now. Enjoy it!

Bug fixes (all in one place)
So, you've booted your ROM?
Awesome! But I'm 100% sure that everything doesn't work. So, we need to try to fix the things that don't work.
This part contains fixes for Fingerprint, Audio, Camera, RIL (network) and more.
Fingerprint bug fix
This guide is intended to be used on MT6750 and MT6755 devices. It might work on other MT67xx devices like MT6797, MT6753 and MT6735. You’ll have to try and find out!
THE FIXES
Please follow these steps. All of them!
Open your stock ROM and port ROM side by side.
Go to system/lib/hw in both ROMs.
Compare the files in both hw folders.
Check your stock ROM for these files:
For MT6750
gatekeeper.mt6750.so
gatekeeper.device_name.so
keystore.mt6750.so
libMcGatekeeper.so
For MT6755
gatekeeper.mt6755.so
gatekeeper.device_name.so
keystore.mt6755.so
libMcGatekeeper.so
Note: device_name depends on the device you’re porting the ROM from. For Meizu U10 Flyme ROM, it was gatekeeper.u10.so
5. If stock ROM DOES NOT HAVE the above files and Port ROM also DOES NOT HAVE them. Then it’s fine! Move to step 8.
If your stock ROM DOES HAVE the above files, copy them and paste them in port. If they are in port, replace them. If they are not in port, just add them.
If Stock ROM DOES NOT HAVE them but Port ROM DOES HAVE them; then remove them from port. THIS IS IMPORTANT.
Copy fingerprintd from sotck system/bin and paste it in port system/bin. REPLACE when prompted.
Copy all files from stock system/bin and paste them in port system/bin. DO NOT REPLACE anything when prompted. The goal is to have stock extra files in port ROM.
Repeat the above step with lib, lib64 (and their subfolders), etc root directory files, permissions, vendor/lib & vendor/lib64 and xbin.
Repack the ROM and test it!
Notes
I did not need to patch boot.img. But if you need it, you can do it. I just don’t know how to help you here ... The best solution would be to replace mt675x files in port ramdisk with stock ones.
Common sense is required to properly understand this guide. For instance, if you’re porting an MT6755 rom to an MT6750, you should be looking for files like gatekeeper.mt6755.so in port ROM and gatekeeper.mt6750.so in stock ROM.
After everything, you MUST remove all mt6750 or mt6755 files from hw folders if you’re doing a crossport (6755 to 6750 or vice-versa).
Sometimes the fingerprint works but the fingerprint option in settings still force close. So, you might want to set up fingerprint for the first time the ROM boots.
If everything fails, open Terminal Emulator and type fingerprintd. If the terminal then appears to be stuck, then your fingerprint is initialized, something else is wrong. Recheck the steps above then.
Fingerprint bug is hard to fix. Each device has its own fingerprint drivers. You have to identify your fingerprint drivers and copy them to the appropriate locations. After that, you MUST remove the other fingerprint files for the port device to avoid conflict between the files.
For my device, the fingerprint files are:
bin/fingerprintd
lib64/hw/fingerprint.default.so
lib64/fprint-x64.so
Most of the time, you will need to remove or add all the files that start with fp or goodix or gx from lib, lib64 and bin folders.
Click to expand...
Click to collapse
RIL (network signal and IMEI issue) fix
Literature
RIL bug is a minor bug that can normally be fixed by using firmware and mddb folders from your stock rom. Sometimes, it doesn’t help. You’ll still face RIL issue like network drop, no 3G/4G/LTE, no VOLTE etc. This happens when you try to port a chinese ROM. Chinese roms mostly use a different kind of VoLTE called SrLTE (sometimes ViLTE). I’m not sure what’s the difference, but they are apparently not the same. So, this is the report of my research.
Click to expand...
Click to collapse
FIXES
To fix RIL. You have to try one or all of these methods:
I assume you’ve already replaced firmware and mddb from stock to port! If not, start with that! And then follow one or all of these steps.
Build.prop method
Compare your stock build.prop to port build.prop
Remove the extra lines that are related to RIL from port build.prop
Add extra lines from your stock build.prop to port one
Make sure to remove any line where ViLTE or SrLTE has been mentioned unless your stock build.prop does have such lines.
Use the edited build.prop
Click to expand...
Click to collapse
Boot.img method
Unpack your stock boot.img and port boot.img
Copy init.modem.rc and meta_init.modem.rc from stock to port ramdisk.
Compare your stock ramdisk to port ramdisk (the ramdisk folder contents themselves).
If your stock ramdisk has files like init.volte.rc, go to B), otherwise, go to A). You SHALL NOT follow A) and B) for the same device at the same time. It will not make sense.
A) Remove any extra file from port ramdisk that is related to RIL. These, mostly, are:
- init.mal.rc
- init.volte.rc
B) If the above files are in your stock ramdisk, then copy them to port ramdisk.
Open init.mt6755.rc and make sure that these lines are defined in the very first section:
import /init.volte.rc
import /init.mal.rc
Repack boot.img and flash it.
Click to expand...
Click to collapse
Binary replace method
Open init.modem.rc of your stock ramdisk
Scroll down until you see “start service”
For example:
service gsm0710muxd /system/bin/gsm0710muxd -s /dev/ttyC0 -f 512 -n 8 -m basic
class core
user root
group radio cache inet misc
disabled
oneshot
Here, we take note of gsm0710muxd
Take note of the files mentioned in this section. Keep taking note until you reach the end of the file.
Copy the mentioned files from stock system/bin. If you can’t find a file in stock but it has been mentioned in init.modem.rc; just skip it!
Paste them in port system/bin and replace.
Hint: You do not need to make a flashable zip every time. Just copy these files with Root explorer (use v3.8.8 for easy use), create a folder in system/bin and name it “ril”, paste the files in that folder, select all of them and change permissions to “755” or “rwxr-xr-x”. Copy them to system/bin, paste them and replace if prompted.
Go to your stock system/lib and copy these files (skip those that don't exist):
libradio.so
libradio_metadata.so
libradioservice.so
libreference-ril.so
libril.so
librilmtk.so
librilmtkmd2.so
librilutils.so
mtk-ril.so
mtk-rilmd2.so
volte_imsm.so
Paste them in port system/lib and replace
Repeat the previous step for system/lib64
Reboot and RIL should be good now.
If RIL still has issues. Then go to stock system/lib and check if there is any file with volte and/or viarild in its name. If not, then check port system/lib for the same files, if they’re there; remove them.
Repeat the same for system/lib64.
Click to expand...
Click to collapse
That's it for RIL!
If you don’t read the entire guide, please don’t ask why, what or how!
Audio Bug fix
Normally Audio works if the ROM is properly ported! But if for some reasons it does, then try these:
Copy audio.primary.mt6750.so from lib/hw and lib64/hw of your stock ROM and paste them in port one.
If it still doesn’t, then you can copy libaudio*.so (meaning all files with audio in their names) from your stock rom’s lib and lib64 to port rom. Use with care, some audio files can cause bootloop.
You might also need to copy all the files starting with audio from etc folder of your stock rom to the port rom. That should fix Bluetooth Headset Audio bug as well.
Click to expand...
Click to collapse
Camera bug fix
Camera bug is the most irritating of all them, yet the hardest one to fix! The following steps allowed me to fix the camera on various ROMs on my Doogee Y6. It might definitely not work on your phone because each device has its own camera files. Here are the steps:
Copy camera.mt6750.so and camera.default.so from lib/hw and lib64/hw of your stock ROM to port ROM.
Copy all camera files from your stock rom’s lib and lib64 folders except libcameraservice.so, libcamera_client.so, libcamera_metadata.so
If camera still doesn't work, try using another camera app. This is important especially when you crossport a MT67xx ROM to another MT67xx! Due to platform differences, the MT6735/MT6753 camera apps for instance are mostly incompatible with MT6750/MT6755. So, the stock camera apps in these roms will likely not work in your ported ROM. There is no solution to that besides using another camera app.
Click to expand...
Click to collapse
Settings Force, Security Settings force bugs fix
If you get settings app for close or security settings force close, remove these from port rom’s lib/hw and/or lib64/hw:
libGatekeeper.so
gatekeeper.mt67xx.so
gatekeeper.mt67xx.so
gatekeeper.device_name.so (device_name refers to the device codename).
libMcGatekeeper
keystore.mt67xx.so
keystore.mt67xx.so
Click to expand...
Click to collapse
That's all for now. Thanks for reading!

Very educative in a way.
Well scripted.
Thumbs Up buddy .

iykeDROID™ said:
Very educative in a way.
Well scripted.
Thumbs Up buddy .
Click to expand...
Click to collapse
Thanks buddy,
I hope it helped

Very educative in a way.
Thumbs Up buddy .
I‘m ported all doogee y6 rom to my huawei enjoy6 (it is MT6750 device),but fingerprint and c2k not work,expect this post is helpful to me, thank you！

How do you fix huawei emui fingerprint bug？I tried all the methods, but it was still not work。

justsoso said:
Very educative in a way.
Thumbs Up buddy .
I‘m ported all doogee y6 rom to my huawei enjoy6 (it is MT6750 device),but fingerprint and c2k not work,expect this post is helpful to me, thank you！
Click to expand...
Click to collapse
Requires that you remove incompatible files from the rom and put the compatible ones.
Of course, for that you need to identify files responsible for C2K and fingerprint.

justsoso said:
How do you fix huawei emui fingerprint bug？I tried all the methods, but it was still not work。
Click to expand...
Click to collapse
See here http://www.nontastik.com/emui-4-1-marshmallow-doogee-y6-mt6750/
The EMUI4Fix.zip fixes fingerprint.

will this working on YU YUNICORN(MTK-6755)? which rom should i choose to port from elephone p9000(which would make porting easier)?
can we port 7.1.2 nougat using base rom as 6.0 mm (using this guide ) help me bruh....i'm newbie

Mega links aren't working anymore

@Nonta72 Sir,Can You please reupload the Simplified process(A) mega link plox....
---------- Post added at 04:55 PM ---------- Previous post was at 04:55 PM ----------
[/COLOR @Nonta72 Sir,Can You please reupload the Simplified process(A) mega link plox....

update mega links
please update mega links or provide gdrive links .

Nonta72 said:
​Welcome to my all in one thread for Meditake Helio P10 thread.
The thread contains porting guides, bug fixes, general informations about the Helio P10 Chipset.
It goes on 3 parts:
Part 1: General Information
Part 2: Normal Porting guides, go to post #2
Part 3: Crossporting guides, go to post #3
Part 4: Bugs fixes (all in one place), go to post #4
Part 1: General information
Helio P10 is a SoC manufactured by MediaTek Inc. in the Q3 of 2015. It has 8 Cortex-A53 Cores clocked between 1.5 GHz and 2.0 GHz depending on the manufacturer. It supports the big.LITTLE technology and is an improved version of the MT6752. In the 8 cores, 4 are clocked at either 1.5 GHz, 1.8 GHz or 2.0 GHz. The other 4 cores are clocked between 1.0 GHz and 1.5 GHz.
It integrates the Mali-T860 GPU with 2 cores clocked between 500 MHz and 700 MHz. The Chipset supports LTE and other various technologies we could find on the MT6752. Compared to the MT6753, the Helio P10 is way faster but still appears to be somewhat slower than some MT6752. The fact is that the latter has all the 8 cores clocked at 1.7 GHz. That gives it the advantage in benchmarks for the price of the battery, however.
Currently, the following processors are built-on Helio P10 hardware:
MT6738 = 1.5 GHz + 1.0 GHz (Mali-T860MP2 - 500 MHz)
MT6750 = 1.5 GHz + 1.0 GHz (Mali-T860MP2 - 500 MHz)
MT6750T = 1.5 GHz + 1.0 GHz (Mali-T860MP2 - 700 MHz)
MT6755 = 1.8 GHz + 1.2 GHz (Mali-T860MP2 - 700 MHz) or 2.0 GHz + 1.2 GHz (Mali-T860MP2 - 700 MHz)
MT6755T (Helio P15) = 2.2 GHz + 1.2 GHz (Mali-T860MP2 - 800 MHz)
So, it's clear now that:
MT6738, MT6750 and MT6750T are the same. Just called differently ...
MT6750 is an underclocked version of MT6755. Both use the same hardware which is Helio P10 board. It is like MT6735 & MT6753; both use MT6735 board.
Click to expand...
Click to collapse
Can You please reupload all the mega links they are all down

Hey ! I am trying to port a rom for my device and I couldn't understand exactly the kernel porting method. my stock rom is on the left and the port rom is lineage Os made for a same chipset (MTK6755) device (Vernee Mars). I can't figure out if I need to copy boot_verified.img from stock and replace with it boot.img on port or should I go by unpacking ( which I did try but didn't work while I am on osx 10.13 ) and packing. please help me here.

I tried to port MT6735 to MT6797 several days ago, but I failed (When the device showed boot logo, after 5 seconds, the device rebooted automatically).
Info:
Base (MT6797):
Android version: 6.0 MRA58K
OS: MIUI
Kernel version: 3.18.22+
Port (MT6735):
Android version: 7.1.1 NMF26O
OS: MediaTek AOSP
Kernel version: 3.18.35
What should I do?
How to port boot image when base ROM and port ROM have different Android version and kernel version?
Sent from my nikel using XDA Labs

Problems porting boot image:
Files not found.
Tool: Image Factory.
Sent from my nikel using XDA Labs

can you please make a rom for leagoo t5?
mt6750t

HTC Desire 10 Pro Dual Sim ...
Just a thought - I am no developer, but it seems my HTC Desire 10 Pro Dual Sim fits same Chipset
Wondering if possible to do Porting on it too!
I checked and re-checked before buying this phone [used almost new!] and the only thing I did NOT check was if there was a Qualcomm in it!
I trusted HTC - this is last time I do!
Mind it is a great phone and I am super happy and passed my old M8s to my partner!
Shall I get it back?