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

bencebacsi

1. If you get shorter than 10 secs loops, you can power off the eMax by long pressing all the 3 buttons together. Removal of the battery is still not necessary.
2. Without a working preloader the phone could not even power on. So that's obviously intact.
3. I wouldn't waste my time on this "development" (better to say experimenting) without the kernel source.

LoLaTiOn

I have already crushed this phone several times to try to operate lollipop
you support my friend, good luck

J.Naw

\n\n[

bencebacsi replied at 2015-10-13 05:56
1. If you get shorter than 10 secs loops, you can power off the eMax by long pressing all the 3 butt ...

Yeah, Its more of an experiment. But I believe I am coming closer.. I suppose you are correct tho, Without the kernel source its near impossible.
EDIT: it seems something is wrong with all the pre-loaders I have tried, as the phone IS NOT turning on. *Sigh*
EDIT2: OKAY, FIXED! Had to flash multiple times but, WE ARE BACK IN ACTION. XD

My question now is, was this caused by a wrong mount point? (Because I set it to the p16 block, But all the other configs i have seen set it to the p6.. Even when the /proc checks where p16?

LoLaTiOn

patience friend there is no reason that you are unable to use the flash tool
it is true that removing the battery is good for this problem but you will get there

LoLaTiOn

was this caused by a wrong mount point? (Because I set it to the p16 block, But all the other configs i have seen set it to the p6.. Even when the /proc checks where p16?

if you made the development of m2m
you must leave all block as you are and concenter only the problem of network signal

J.Naw

\n\n

LoLaTiOn replied at 2015-10-13 06:20
if you made the development of m2m
you must leave all block as you are and concenter only the prob ...

Ah alright.. Though it doesn't make sense that the system calls for a different mount point then it is showing when ran by both busybox and mtkdroid tools..
EDIT: Just put it into another bootloop... Maybe I am not going to be the "Savior who brought everyone Lollipop"

LoLaTiOn

\n\n

I think that the partition table is readable by mtk development tools and busybox
Rom TCL_M2M_5.0_official_ROOT_2015.7.16_update works fine also recovery M2M_TWRP2.8.7.0_2015-07-18_5.0
you just fix the network signal rild

currently it is possible to make any android rom 5 but all have the same problem

a phone that can not make calls is not fair

After fix this you can open the world for happy rom 5

J.Naw

LoLaTiOn replied at 2015-10-13 06:35
I think that the partition table is readable by mtk development tools and busybox
Rom TCL_M2M_5.0_of ...

Alright. Whats the link for the Roms? I will try flashing.

LoLaTiOn

\n\n
ok bro happy flash

Rom 5.0 lollipop
TCL M2M 5.0 ROOT 2015.7.16http://www.mediafire.com/downloa ... .0_FlashtoolROM.zip

Recovery 5
M2M_TWRP2.8.7.0_2015-07-18_5.0
https://drive.google.com/file/d/ ... 2s/view?usp=sharing

enjoy...


also look this topic please http://community.umidigi.com/forum.php?mod=viewthread&tid=628


edit > change link rom flash link tool

J.Naw

LoLaTiOn replied at 2015-10-13 06:48
ok bro happy flash

host on my G drive

Thankyou! And I have taken a look at the given link, it does make sense the UMI is a "copy" of the M2M..

Anyways, About the partitions. cat /proc/emmc still brings up as /system being mounted on emmc_p16. So I am completely confused... emmc_p6 is linked to "lk"