• XDA Forums have been migrated to XenForo. We are aware of several issues including missing threads, logins not working, and more. To discuss, use this thread.

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

chris8189

New member
Jan 17, 2016
286
36
0
It's all a bit quiet on this thread. Guess nobody is developing anything new (Android 9 / 10) for phones that have the Helio P10 chip?

Chris
 

chris8189

New member
Jan 17, 2016
286
36
0
Nokia 3.1 is MT6750 I Think it may have been upgraded to Android 9 by now but not 100% sure :confused:
https://www.gsmarena.com/nokia_3_1-9215.php
Thanks. I've had a look and you are correct. The Nokia 3.1, which has the MT6750 SoC has been upgraded to Android 9. Scouring around on the web, however, I can't find a download link to the ROM. I can find one for the Nokia 3.1 Plus, but that uses a different MediaTek chip which is incompatible.

Chris
 
Last edited:

bigrammy

Senior Member
Apr 8, 2011
2,881
2,509
113
huddersfield
Thanks. I've had a look and you are correct. The Nokia 3.1, which has the MT6750 SoC has been upgraded to Android 9. Scouring around on the web, however, I can't find a download link to the ROM. I can find one for the Nokia 3.1 Plus, but that uses a different MediaTek chip which is incompatible.

Chris
Best I can do is Android 8.1 there are no Pie dumps that I can find. :(
TadiT7 kindly did a firmware dump and put it on github HERE:D :good:
Kernel Source code HERE

I assume you have the Kernel Source for your own phone.

Nokia are pretty good when it comes to releasing updates and the Kernel sources so I am very surprised there is so little activity around these very low budget devices. :silly:
 

chris8189

New member
Jan 17, 2016
286
36
0
Best I can do is Android 8.1 there are no Pie dumps that I can find. :(
TadiT7 kindly did a firmware dump and put it on github HERE:D :good:
Kernel Source code HERE

I assume you have the Kernel Source for your own phone.

Nokia are pretty good when it comes to releasing updates and the Kernel sources so I am very surprised there is so little activity around these very low budget devices. :silly:
That's great, thanks for that. Unfortunately I don't have the kernel source available for my own phone. I have sent emails to the various Chinese websites that sell the Vertu replicas for the source code, and stressed to them that it is a legal requirement to be able to provide the kernel source. But I don't have my hopes up.

The only way I have TWRP fully working on my device is through a ported TWRP for the BLU Pure XR phone, which @lopestom created, and with the help of @ashyx he managed to use IDA Pro software (hex editor) to modify one line within the kernel extracted from my boot.img file to get it to work. Basically there was a line of code in the kernel which disabled touch functionality in recovery mode. Once that line was edited, I was able to use the BLU Pure XR recovery, with touch functionality for my device. I stress that my device is a replica Vertu Aster P, which has the MT6755 SoC, the same as the BLU Pure XR.

So no, unfortunately I still don't have the source code for my phone.

There are, however kernel sources for other phones that have the MT6755 chip, such as the Sony Xperia XA, and the ZTE Nubia N1, which share the same Linux kernel version as the one on my phone (3.18). I also see that you have released in GitHub the device tree (with kernel) for the Nokia 3.1. Links below;

https://github.com/JonnyXDA/android_kernel_sony_tuba

https://github.com/ztemt/NX541J_M_kernel

https://github.com/bigrammy/android_kernel_nokia_3.1

Question: Is it possible to create a working kernel for my device, as well as a device tree, by analysing the kernels listed above and cross-comparing them with the kernel extracted from my boot.img in IDA Pro?

Chris
 
Last edited:

bigrammy

Senior Member
Apr 8, 2011
2,881
2,509
113
huddersfield
That's great, thanks for that. Unfortunately I don't have the kernel source available for my own phone. I have sent emails to the various Chinese websites that sell the Vertu replicas for the source code, and stressed to them that it is a legal requirement to be able to provide the kernel source. But I don't have my hopes up.

The only way I have TWRP fully working on my device is through a ported TWRP for the BLU Pure XR phone, which @lopestom created, and with the help of @ashyx he managed to use IDA Pro software (hex editor) to modify one line within the kernel extracted from my boot.img file to get it to work. Basically there was a line of code in the kernel which disabled touch functionality in recovery mode. Once that line was edited, I was able to use the BLU Pure XR recovery, with touch functionality for my device. I stress that my device is a replica Vertu Aster P, which has the MT6755 SoC, the same as the BLU Pure XR.

So no, unfortunately I still don't have the source code for my phone.

There are, however kernel sources for other phones that have the MT6755 chip, such as the Sony Xperia XA, and the ZTE Nubia N1, which share the same Linux kernel version as the one on my phone (3.18). I also see that you have released in GitHub the device tree (with kernel) for the Nokia 3.1. Links below;

https://github.com/JonnyXDA/android_kernel_sony_tuba

https://github.com/ztemt/NX541J_M_kernel

https://github.com/bigrammy/android_kernel_nokia_3.1

Question: Is it possible to create a working kernel for my device, as well as a device tree, by analysing the kernels listed above and cross-comparing them with the kernel extracted from my boot.img in IDA Pro?

Chris
The Sony Kernels are very Sony orientated and modified quite a lot. I would look for something a little closer to pure Android.
Nokia use FIH to develop their software and even these Android One ROM's seems to have quite a lot of FIH's own binarys running these usually cover things like Camera's, and Audio frameworks to name a couple.

Your best chance of bring up your own kernel would be to use the oukitel_k6000_plus (MT6750) of team mad as a base HERE and also use the device and vendor trees as a base.
This is as close to Pure Android as you will get and therefore would be the best start point in my opinion. :eek:
Use your own device ProjectConfig.mk file as a guide to what is included in your own device such as drivers etc this file should be in /system/vendor/data/misc or /system/data/misc on older roms if memory serves me correctly. :confused:

I don't know your abilities but even the best of dev's struggle to get a fully working kernel without the specific device source code so I wish you lots of luck. :eek:
If you do succeed maybe you could fix the Ril on the Sony XA Lineage 14.1 https://forum.xda-developers.com/xperia-xa/development/tuba-lineageos-14-1-t3878212 :D
 
  • Like
Reactions: chris8189

chris8189

New member
Jan 17, 2016
286
36
0
The Sony Kernels are very Sony orientated and modified quite a lot. I would look for something a little closer to pure Android.
Nokia use FIH to develop their software and even these Android One ROM's seems to have quite a lot of FIH's own binarys running these usually cover things like Camera's, and Audio frameworks to name a couple.

Your best chance of bring up your own kernel would be to use the oukitel_k6000_plus (MT6750) of team mad as a base HERE and also use the device and vendor trees as a base.
This is as close to Pure Android as you will get and therefore would be the best start point in my opinion. :eek:
Use your own device ProjectConfig.mk file as a guide to what is included in your own device such as drivers etc this file should be in /system/vendor/data/misc or /system/data/misc on older roms if memory serves me correctly. :confused:

I don't know your abilities but even the best of dev's struggle to get a fully working kernel without the specific device source code so I wish you lots of luck. :eek:
If you do succeed maybe you could fix the Ril on the Sony XA Lineage 14.1 https://forum.xda-developers.com/xperia-xa/development/tuba-lineageos-14-1-t3878212 :D
That certainly doesn't sound easy.

I had an email back from the Chinese seller who sells the replica Vertu phones, and they said that they weren't able to disclose the details of the factory who makes them. Fair enough, however I replied back asking if they could please contact the factory on my behalf asking for the kernel source code for the Aster P. I understand now why there is so little development for MediaTek phones.

Chris
 

chris8189

New member
Jan 17, 2016
286
36
0
Your best chance of bring up your own kernel would be to use the oukitel_k6000_plus (MT6750) of team mad as a base HERE and also use the device and vendor trees as a base.
This is as close to Pure Android as you will get and therefore would be the best start point in my opinion. :eek:
Use your own device ProjectConfig.mk file as a guide to what is included in your own device such as drivers etc this file should be in /system/vendor/data/misc or /system/data/misc on older roms if memory serves me correctly. :confused:
You are indeed right. On my (older) Android 6.0 ROM it was in /system/data/misc. I don't have the time to devote to this any more, as I have now have a baby which takes up all of my time (when I'm not at work), as well as the other halve's time! ;)

I have linked to my ProjectConfig.mk file from my phone below. Any chance you could have a look for me? I'm desperate to try and move away from this older ROM on my (new) phone and have a ROM that is up to date.

https://mega.nz/#!gswkWADa!nileURXPHf_ph52ixSefZTcMrxt3M7kydUR083PUSrs

I am willing to make a significant donation to someone who can manage to get a working Android 9.0 / 10.0 ROM on my phone

Chris
 

bigrammy

Senior Member
Apr 8, 2011
2,881
2,509
113
huddersfield
You are indeed right. On my (older) Android 6.0 ROM it was in /system/data/misc. I don't have the time to devote to this any more, as I have now have a baby which takes up all of my time (when I'm not at work), as well as the other halve's time! ;)

I have linked to my ProjectConfig.mk file from my phone below. Any chance you could have a look for me? I'm desperate to try and move away from this older ROM on my (new) phone and have a ROM that is up to date.

https://mega.nz/#!gswkWADa!nileURXPHf_ph52ixSefZTcMrxt3M7kydUR083PUSrs

I am willing to make a significant donation to someone who can manage to get a working Android 9.0 / 10.0 ROM on my phone

Chris
Sorry but I dont have the time or knowledge to do this and It would require the phone in hand to even consider an attempt at it. :eek:
I also have some very capable devices hardware wise but sadly no kernel source code for them so those are all stuck on older android versions too. :(
To be honest I find a stripped down oem stock Android 6.0 ROM better. ;)
I swap all the oem's app's such as launcher dialer messages contacts etc etc and replace them with google's own app's and associated libs after this I find most rom's work really well and I get app updates on regular basis.
A softly softly approach is best when removing the oem stuff as you don't want to lose any real functionality so this part can be time consuming...
 

chris8189

New member
Jan 17, 2016
286
36
0
Sorry but I dont have the time or knowledge to do this and It would require the phone in hand to even consider an attempt at it. :eek:
I also have some very capable devices hardware wise but sadly no kernel source code for them so those are all stuck on older android versions too. :(
To be honest I find a stripped down oem stock Android 6.0 ROM better. ;)
I swap all the oem's app's such as launcher dialer messages contacts etc etc and replace them with google's own app's and associated libs after this I find most rom's work really well and I get app updates on regular basis.
A softly softly approach is best when removing the oem stuff as you don't want to lose any real functionality so this part can be time consuming...
Fair enough. Can you recommend any devs that might be willing to have a go at reverse engineering the kernel on my phone? I'm willing to post the phone to whoever is willing to have a go. I desperately want to move on from Android 6.0.

Thanks,

Chris
 

bigrammy

Senior Member
Apr 8, 2011
2,881
2,509
113
huddersfield
Fair enough. Can you recommend any devs that might be willing to have a go at reverse engineering the kernel on my phone? I'm willing to post the phone to whoever is willing to have a go. I desperately want to move on from Android 6.0.

Thanks,

Chris
Sadly I don't know any and if I did I would send them some of my devices. :laugh:
My Luxury Brand Lumigon T3 (Genuine) is also stuck on MM with no Kernel Source Code available which is a real shame for a device with such great spec's.
 
  • Like
Reactions: chris8189

chris8189

New member
Jan 17, 2016
286
36
0
Sadly I don't know any and if I did I would send them some of my devices. :laugh:
My Luxury Brand Lumigon T3 (Genuine) is also stuck on MM with no Kernel Source Code available which is a real shame for a device with such great spec's.
With a phone as expensive and luxurious as Lumigon, that is indeed a shame that you can't upgrade from Marshmallow. I've always loved Lumigon's!

I might start a separate thread on this in the hope of trying to reach out to a dev on XDA who would be willing to have a go.

Chris
 

khronus

New member
Sep 23, 2012
19
4
0
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


B) The other method
links are dead... is there any thread regarding or same as this?
I want to try this porting for example i have LineageOS 14.1 for MT6750T & my Phone is Homtom HT70 MT6750T also.. :)
 
  • Like
Reactions: chris8189

khronus

New member
Sep 23, 2012
19
4
0
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
I cant understand the Step 4.??? Select all files ins ramdisk folder then edit by note++??? you mean one by one??


Edit: i think i understand now.. all files except folders.. sorry. hehe.
 
Last edited:

khronus

New member
Sep 23, 2012
19
4
0
May i request for someone here to share their MT6750T CustomROm? I will try to port to my Homtom HT70 MT6750T.. please??
I read and follow the steps here and try to port on other Phones with MT6750T but i got no luck and always bootlooped... :(

---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------

Nokia 3.1 is MT6750 I Think it may have been upgraded to Android 9 by now but not 100% sure :confused:
https://www.gsmarena.com/nokia_3_1-9215.php
look at this https://www.getdroidtips.com/lineage-os-16-homtom-s99/

HomTom S99 6750T running Lineage OS 16 Android Pie. can we get this ROM work on same MT6750T? i have HomTom HT70 MT6750T
 

abrar92167789

New member
Mar 8, 2019
7
1
0
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


B) The other method
The links of archives aren't working. Can you please fix them.

Sent from my PGN612 using Tapatalk
 
  • Like
Reactions: chris8189

chris8189

New member
Jan 17, 2016
286
36
0
I finally got round to taking the time to go through this tutorial. I am porting an MT6750 ROM to my MT6755 phone. I followed Method 2B (Other Method). I managed to get TWRP to flash the ROM, however it boot loops and goes straight back to TWRP recovery. I tried using both methods of using the stock boot image and the port boot image, doing exactly as the tutorial states. I don't think the OP is still active on these forums, given his last seen online status.

I have attached the TWRP recovery log file as well as the kernel dmesg log file in the hope that someone can please assist. @ashyx

Thanks,

Chris
 

Attachments

Last edited: