yashsingh1/xdaforums huggingface dataset:
[Android General] justsoso:
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！:o:o:o
[Android General] justsoso:
How do you fix huawei emui fingerprint bug？I tried all the methods, but it was still not work。
[Android General] Nonta72:
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.
[Android General] Nonta72:
See here http://www.nontastik.com/emui-4-1-marshmallow-doogee-y6-mt6750/

The EMUI4Fix.zip fixes fingerprint.
[Android General] Anstonfern:
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
[Android General] Anstonfern:
Mega links aren't working anymore
[Android General] Anstonfern:
[MENTION=5193140]Nonta72[/MENTION] 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 [MENTION=5193140]Nonta72[/MENTION] Sir,Can You please reupload the Simplified process(A) mega link plox....
[Android General] dhanuj:
update mega links

please update mega links or provide gdrive links .:eek::eek:
[Android General] aljoscha81:
Can You please reupload all the mega links they are all down
[Android General] moda20:
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.
[Android General] jellybean13:
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?
[Android General] jellybean13:
Problems porting boot image:

Files not found.

Tool: Image Factory.
[Android General] ProjectMullins:
can you please make a rom for leagoo t5?

mt6750t
[Android General] xdamodded:
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?

:confused:
[Android General] chris8189:
Is there a list of Android 9 ROM's available for devices that have the Mediatek Helio P10 chip?

Chris
[Android General] chris8189:
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
[Android General] bigrammy:
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
[Android General] chris8189:
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
[Android General] bigrammy:
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:
[Android General] chris8189:
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 [MENTION=4939713]lopestom[/MENTION] created, and with the help of [MENTION=4899305]ashyx[/MENTION] 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
[Android General] bigrammy:
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. :o

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://xdaforums.com/xperia-xa/development/tuba-lineageos-14-1-t3878212 :D
[Android General] chris8189:
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
[Android General] chris8189:
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
[Android General] bigrammy:
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...
[Android General] chris8189:
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
[Android General] bigrammy:
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.
[Android General] chris8189:
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
[Android General] khronus:
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.. :)
[Android General] khronus:
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.
[Android General] khronus:
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 ----------

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
[Android General] chris8189:
[MENTION=5193140]Nonta72[/MENTION] - The Mega links in your guide on the first page are broken. I'm trying to follow your guide but need working links. Would you mind reposting them?

Thanks,

Chris
[Android General] sinedoke:
Need them too
[Android General] abrar92167789:
The links of archives aren't working. Can you please fix them.
[Android General] chris8189:
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. [MENTION=4899305]ashyx[/MENTION]

Thanks,

Chris
[Android General] chris8189:
Anyone?
[Android General] bigrammy:
Is mobicore in your ROM or the one your porting?

What is your Device?
[Android General] chris8189:
I don't actually know the answer to that. I can see it mentioned in my kernel dmesg.log file but unsure if it's my stock ROM or the port ROM.

The device is a Vertu Aster P Chinese clone. This one - https://www.luxuryvertu.cn/ProID473.html
[Android General] bigrammy:
I would of thought such a device would not use mobicore :confused:

Look in your stock boot.img ramdisk for trustonic.rc and see if it mentions mobicore
[Android General] chris8189:
I've had a look at the init.trustonic.rc of my stock unpacked boot Ramdisk folder and yes it does use Mobicore.
[Android General] bigrammy:
Hmm that may make it difficult to port as there is very little info regarding mobicore. It does use keys etc so you may need those from the stock ROM also.

All my Sony Mediatek devices and I think the Mediatek HTC's also use mobicore and None of these devices have fully working Port ROM's mostly broken Ril even if you manage to fix sound etc etc and to do that the kernel needs re compiling. :(
[Android General] chris8189:
Firstly, what exactly is Mobicore, what does it do, and can it possibly be 'edited out' of the init.trustonic.rc script?
[Android General] bigrammy:
See here when the site is working properly as it seems to be down just now. https://www.trustonic.com/solutions/asset-lifecycle-protection-service-for-mobile-operators/

From what I understand mobicore is a intermediate between the Arm code and user world code allowing or not allowing access based on some sort of key system.

ALP's = asset life cycle protection make of that what you will I guess it depends on what level of protection the OEM set eg block some things or block everything. :confused:

So to get rid of it completely you would need to do a top down rebuild of the ROM.
[Android General] chris8189:
Thanks for that explanation. Interesting! What is intriguing is the fact that the ROM I wish to port is from another Chinese replica Vertu; namely the 'Constellation X'. Now I would have thought that if they have bothered building Mobicore into the ROM on my phone, they would have done the same with the (very similar, albeit Android Nougat) ROM on the Constellation X. However there is no Trustonic file in the Ramdisk on the port ROM.
[Android General] bigrammy:
They (OEM's) pay extra for trustonic/mobicore which is why I very was surprised they used it in your ROM most just use Mediatek's tee trust implementation.

Maybe they fully cloned Vertu's ROM too some how :laugh:

What SoC do Genuine Vertu phones use.?
[Android General] chris8189:
The genuine Vertu Aster P has a Qualcomm Snapdragon 660 SoC.

The Chinese manufacturers of replica Vertu's (there's only 3) obviously buy the genuine Vertu and then reverse engineer absolutely everything. From the outer housing to the software, even the weight. So having the genuine and the replica side by side; it's very hard to tell the difference. Unless you know what you're looking for. Like I do, being a Vertu enthusiast for many years, having owned both genuine Vertu's and replica's.

Chris
[Android General] bigrammy:
Ok

Maybe the faker's tried to stop other fakers faking their phones :laugh: :laugh:

It's a mad world we live in nowadays. :eek:
[Android General] chris8189:
Certainly is!

I'm gutted that I can't port a Vertu clone ROM to a Vertu clone. Absolutely nuts. I honestly thought it would have worked without much hassle.

Chris
[Android General] bigrammy:
Is the stock rom google certified ie you can use playstore and install google app's without issues?

If so then it would be better to make your own AOSP based custom Stock ROM which is what I do with my Sony Devices.

So I remove all the Sony stuff which I do not use and does not break the ROM and add google's replacments like launcher, messages, dialer, wallpapers, keyboard, file manager, etc, etc

Sadly the MM 6.0 Dialer is not supported (Updated by Google) where as on my XA with 7.0 the Dialer gets updated by google as well as those above. :D

This keeps the ROM updated and looking fresh in my experience.

I did this for my XA (mt6755) and my XA1 (mt6757)

https://xdaforums.com/xperia-xa/development/7-0-n-stock-rom-f3111-modded-android-t4020987
[Android General] chris8189:
Yes, the stock ROM is Google certified. I have the Playstore and can install apps no problem at all.

What I do have an issue with though is the fact that this is a new phone and should be running Android 9.0 Pie, much the same as the genuine Aster P. I was lied to about the specs of this phone.

I thought it would be relatively easy to port over the Vertu Constellation X (replica) ROM which happens to be Android 7.1 Nougat.

Why they didn't just make the software replica identical to the genuine phone, I have no idea.
[Android General] bigrammy:
Ok can you break down what you want to achieve.

1. Which device and specs you have and it's firmware version.

2. Device, specs & firmware version of the ROM you wish to use. (Port to your's)
[Android General] chris8189:
1. I have a Vertu Aster P replica which has an MT6755 SoC. I don't have the firmware file name version that's on my phone, but I have the build ID: alps-mp-m0.mp7-V1_gionee6755.66.m_P143

From googling the firmware build of my phone, it appears that what the Chinese replica masters have done is take the ROM from a 'Gionee S9', and then customise it with the Vertu themes, boot animation, Vertu's own apps etc. Both the Gionee S9 and my Vertu replica have the Marshmallow Android 6.0 ROM and have the words 'gionee6755_66_m' in their build. Too much of a coincidence I'd say. This might also explain why my ROM has Mobicore, with it being a Gionee ROM (i.e. a legit manufacturer).

2. The device that I want to port a ROM from is a Vertu Constellation X replica with an MT6750 SoC. Firmware version is Vertu_Constellation_X_MT6750_01152018_7.0

Both my stock ROM and the port ROM have 'alps' in their firmware build ID by the way.

Chris
[Android General] bigrammy:
Hi Chris,

Ok 7.0 > 6.0 wont work I am afraid :( There is just too much of a step up.

Gionee is interesting though and searching it seems you have already hunted around.

Gionee and BLU share devices it seems and the closest match I could find was the Vivo 6 and Pure xr but I cannot find the kernel source for these phones :(

This folder has a lot of BLU kernel source code HERE Note the Vivo Air is a Gionee kernel too but the devices that would be of most interest are missing. Maybe you could do a bit more google time to see if you could track them down even email BLU for them.

If we can find the Kernel source there maybe a chance of upping it N 7.0
[Android General] chris8189:
Thanks very much for this! At least now I know it wouldn't have worked anyway!

I've emailed Blu this morning, asking if they could provide the kernel sources for the Pure XR and Vivo 6. From looking around on XDA, as well as that Mega folder you linked to, it appears that they are pretty forthcoming with providing kernel source code for their devices.

Interestingly, the TWRP that I have on my phone is for the Blu Pure XR.

When I first got this device, I was desperate to get TWRP recovery on, and knowing fine well that there wouldn't be a TWRP already made for this phone, I thought the Blu Pure XR TWRP would be near enough. So with some help, I ended up with a ported TWRP for my phone!
[Android General] bigrammy:
Hi lets hope they give you something. :fingers-crossed:

I noticed that this Aster reports to have Android 8.1 :confused: HERE not sure how true that is or if it's the same as yours.
[Android General] chris8189:
Yeah, all of the Aster P replicas state they have Android 8.1, when in fact they don't. They have Android 6.0 which they have spoofed in the Settings>About Phone>Android version to say 8.1.0

That's what really winds me up with the clone manufacturers.
[Android General] bigrammy:
Yes just spotted yours ROM on needrom :laugh:

I noticed your kernel version says 3.10 also and that's a old kernel too I thought most if not all mt6755's were 3.18
[Android General] chris8189:
Yes, that is indeed my ROM ;)

My kernel is actually 3.18.22 from the Device Info HW app (see attached screenshot), so the screenshot of the settings menu showing that kernel version of 3.10 is actually spoofed (duff) info as well.

You are most likely correct with most mt6755's being 3.18. Mine actually is, just not in my settings menu!!! Lol
[Android General] bigrammy:
It's in your screenshot.

Similar to this HERE

I have to go offline now got some stuff to sort out. :o
[Android General] chris8189:
See my edited post above :)
[Android General] chris8189:
I've had an email reply from BLU, however it was only to provide instructions for logging in to their FTP server, which has neither the Pure XR or the Vivo 6 kernels listed.

I've replied to their email stating that, so hopefully they can help!

Chris
[Android General] chris8189:
Update:

Received another reply from BLU stating that they have sent the request to their software department, and to allow 7-10 days for the kernels to be uploaded.

Great news so far!

Chris
[Android General] bigrammy:
Cool let's hope one of them is the same as yours :fingers-crossed:
[Android General] rowzes:
Who successfully ported a custom ROMs for Helio p10?
[Android General] rowzes:
How to unlock bootloader of you phone? I have a phone with the same chipset (Helio P10) but unlocking bootloader always failed.
[Android General] Anonymous V:
you can easily unlock it using mtk client
[Verizon Samsung Galaxy S6 Edge+] Senerade:
Need help with removing frp on an unlocked s6. I've tried using an otg cable to bring up a few methods but I think the os it's using has that patched. I'm not used to this kind of thing because all of the phones I've bought in the past never gave me this kind of trouble and I'm looking to use this to replace my fire phone. Any suggestions on what I can do like if I can flash an older version of android or something?
[Verizon Samsung Galaxy S6 Edge+] jacobvsmith:
Same here. Almost every single method online is bad.
[Verizon Samsung Galaxy S6 Edge+] mmac532:
So the quick shortcut realterm dialer and google account manager solution didnt work?
[Honor 8 Questions & Answers] Asmund:
Hi,

I'm considering buying a SDCard for my Honor 8.

I think I'll go for a 128 gb.

What brands do you suggest, what speed/class and so on?

Looking on Ebay there a huge price differences.
[Honor 8 Questions & Answers] pijes:
There's a lot of fake sd cards out there, especially if the price difference is huge from the standard price. I recommend buying it from local reputable stores (online or offline), it's easier to do warranty claim if anything happens to the card.
[Honor 8 Questions & Answers] PalakMi:
Go with samsung, it has the best sd cards :)
[Honor 8 Questions & Answers] SharxX8:
I might be incorrect since it's been a while but i believe that the H8 doesn't support the highest speeds for SD cards.

I went for the Samsung Evo+ (the red one), not the best one i believe but it's worked well so far. Haven't really tested speed yet but i could if requested.

Obviously i can't really compare it though.

And yeah as for cheap prices, If it sounds to good to be true it usually isn't. Don't do it. Especially when you're going to store your precious data on it
[Honor 8 Questions & Answers] pijes:
I'm using the same card. I think it has the best price to performance ratio so far.
[Honor 8 Questions & Answers] PalakMi:
I will get a 256gb one, once I get my honor 9, I can't wait
[Honor 8 Questions & Answers] venugopalu007:
Go for Samsung they are best.
[Honor 8 Questions & Answers] PalakMi:
It is my choice from the beginning
[Honor 8 Questions & Answers] venugopalu007:
I bought a 32 GB class 10 , 2 years approximately back no issues at all ,but some times it is corrupted, i had to format again to use.