[Closed Cyanogen Port Thread.] Looking for help with the Umi eMax!

J.Naw

\n\nPost is now Irrelevant. New and improved post: New



Okay, So. First thing: I AM NOT A TOTAL EXPERT. I've just got some knowledge on how computers work.. and a seemingly good "reverse engineering" skill.. So Yes I am a beginner to Building android Operating Systems. Secondly: I've decided to take on a daunting task... Port Cyanogenmod 12 over to the eMax.. The only issue? No source code.. So, I came up with an idea. Hack around with the phone, gather as much info as possible, and try to port it over. Now, The only thing that would "theoretically" be able to copy/paste over is the kernel.. (If I got my ideas all sorted correctly) and it should theoretically work?
Here is all the info i've found so far:

System Specs:
SoC:   MediaTek  MT6752
CPU: ARM Cortex-A53
GPU: ARM Mali-T760 MP2
ARCHITECTURE VARIANT: Armv8-a
Partitions:
Turns out Emmc_p* and mmcb1k0p* is basically the same thing, just different "formats"
/boot        =     /dev/block/mmcb1k0p7
/cache      =     /dev/block/mmcb1k0p17
/data        =     /dev/block/mmcb1k0p18
/misc        =     Not Found Yet
/recovery  =     /dev/block/mmcb1k0p8
/sdcard     =     /dev/block/mmcb1k0p1   OR   /dev/block/mmcb1k0
/system    =     /dev/block/mmcb1k0p16
/sd-ext     =     /dev/block/mmcb1k0p2

BoardConfig Stuff (DUNNO WHAT ITS CALLED)

1. BOARD_KERNEL_BASE := 0x40000000
   
2. BOARD_KERNEL_PAGESIZE := 0x001FB000
   
3. 
   
4. OARD_BOOTIMAGE_PARTITION_SIZE := 0x00004400
   
5. BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00004400
   
6. BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x60000000
   
7. BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x082BEB85
   
8. BOARD_FLASH_BLOCK_SIZE := 1000000

Copy the Code

THINGS TO BE/BEING DONE

• Extract Kernel From Working Rom (Something that allows me to edit Ramdisk?) FOUND! Android Kitchen Extracts Ramdisk for once. SUCESS.
• Figure out how to get the darn CyanogenMod "make Recoveryimage" command to work, It keeps skipping all the files, then asks for a Kernel Config file?
• Turns out MT6572 doesn't have a fastboot mode, managed to install TWRP through Rootjoy though.
• Learn more stuff
  

NEW FOUND STUFF FROM RESEARCHING:

• Possible Media Tek Kernel to allow kernel config in building. CyanogenMod 12.1 (also includes 13 in Branches) 5.1.1 Kernel MT6572 Kuronosan's 4.4.2 Kernel Mt6572
• Thanks to ec8or for the finding of porting: http://www.mtkroms.com/2015/10/cyanogenmod-lollipop-blisspop-for-mt6572.html
• Seems the eMax's close brother is the TCL M2M
• TWRP does not work on Umi eMax (atleast the one I found) so I will be flashing ROMS through Rootjoy... Maybe if I get time I will try to port TWRP properly?
  

If anyone can confirm my findings, that'd be great! If there is anything I am doing wrong, I'd also like some input on it.

Would like any help possible as well, If I need to setup a Git repo, I can easily do that, or some file sharing account to easily allow helpers to, well, help!

J.Naw

\n\n

ec8or replied at 2015-10-12 12:02
http://androidurdu.net/download-mtk-multi-port-flash-download-mediatek-phones/
Check this pls.

Ah yes, May need incase I do screw up! Thankyou.

EDIT: I feel the kitchen should work with the MT6752.. Unless all the programs and such are hardware specific, I'll dig abit deeper..
EDIT2: Hmm, It seems like the M2M is a MT6752. But the kitchen sees it as a 6572.. This may actually work out..

plasticbomb1986

I think you missed something. CPU : not mt6572, its MT6752.

ec8or

I think this is awesome.
I hope you get any help u need.
https://wiki.cyanogenmod.org/w/Doc:_porting_intro

bencebacsi

I'm afraid you ask trivial questions here.
1. The kernel and ramdisk can be extracted from the boot image. The kernel itself cannot be extracted. That's the reason because developers need the source code. The ramdisk is just a gzip compressed folder that you can extract easily and edit its content. Just google for it.
2. You want to develop a compete firmware but don't know how to flash a recovery image ()twrp or anything, that doesn't matter) on your phone?
3. The kernel stands for the unique hardware. How could you build it without knowing all hardware parts and owning their resources?

I wish you to be successful but can't see a real chance. UMI developers with (probably) expert skills and better resources already tried it but failed.

J.Naw

\n\n

bencebacsi replied at 2015-10-10 05:51
I'm afraid you ask trivial questions here.
1. The kernel and ramdisk can be extracted from the boot  ...

1. Yes I have tried taking the Kernel and ramdisk from a boot.img, but anable to successfully do it. The way it was packaged almost resembles an issue someone had with loki-fied.. but it aint.
2. I do know how to flash, I have installed cyanogen 12.1 onto my Note 2, and even had to do repairs due to myself being dumb and putting it onto the bootimage partition. (I have spent numerous hours researching and such)

I am looking at the possibility of creating a brand new kernel DUE to the command "make recoveryimage" not correctly being ran, most likely due to #1. So either I find a way around that or create the Kernel.config files.
3. I know the kernel stands for the hardware only, which is why I am wanting to rip it from a current Rom, But anable to due to Question 1.  

EDIT: Re-read your post, You do have totally correct statements.. But, I'm just wanting to try, all the research I have done shows that the Kernel is in a file called "boot.img-zimage" or just "kernel.file" depending on the method of extraction...

J.Naw

ec8or replied at 2015-10-9 17:55
I think this is awesome.
I hope you get any help u need.
https://wiki.cyanogenmod.org/w/Doc:_portin ...

Thankyou! I have/am using that link to currently build it, but having problems extracting the kernel from the rom..

I think you missed something. CPU : not mt6572, its MT6752.

Yes.. I will fix that

plasticbomb1986

Ahh.. i guess, we have to forgot Lollipop on eMax. Now im thingking about eMax Mini, Snapdragon 615 maybe will be better for the future. Now its will be sold at 75 $ on CooliCool, so i guess, i wanna try it.

J.Naw

plasticbomb1986 replied at 2015-10-10 13:03
Ahh.. i guess, we have to forgot Lollipop on eMax. Now im thingking about eMax Mini, Snapdragon 615  ...

Well, To be honest, I am not gonna give back the Umi after spending 2 months of fighting from coolicool (wouldn't send the product due to "needing a photo id" and such) and finally having to put a dispute against them.. So, I am gonna see if this is even remotely possible (it should be) and, who knows? Maybe Umi will release lollipop, making the conversion a tad bit easier..

bencebacsi

plasticbomb1986 replied at 2015-10-10 13:03
Ahh.. i guess, we have to forgot Lollipop on eMax. Now im thingking about eMax Mini, Snapdragon 615  ...

I suggest you to think it twice.
eMax vs. eMax mini comparison

plasticbomb1986

\n\n

bencebacsi replied at 2015-10-11 03:22
I suggest you to think it twice.
eMax vs. eMax mini comparison

I will think of it, till 15..... there is pros and contras between the two device, (And there is one biggest thing, i have eMax), but i wanna buy a phone what is future proof, not a dead phone like eMax now.  Snapdragon means to me, maybe its can get CM12 really, because the CM group have other Snapdragon 615 SoC based phone already on CM12.1. So i dont know yet, what is will be the end result, but i think, i will buy eMax Mini too, maybe i will use both of it... ( And for 65 € its not price for a try...., eMax was almost 200 when i bought it, so....)