Database Users

[ROM][BOOTLOOP] CM11 Port | Need Help

hey everybody, as the zte blade was a faithful mobile phone for a Long time, i want to port Android 4.4 for this nice Little phone
i build an update.zip which was successfully installed after a lot of tries, but now i stuck on bootloop!
this is my very first port, want to learn as much as i can so i started this Little Project!
i'll give you the logcat, hopefully somebody can help me?

sn1k said:
hey everybody, as the zte blade was a faithful mobile phone for a Long time, i want to port Android 4.4 for this nice Little phone
i build an update.zip which was successfully installed after a lot of tries, but now i stuck on bootloop!
this is my very first port, want to learn as much as i can so i started this Little Project!
i'll give you the logcat, hopefully somebody can help me?
Click to expand...
Click to collapse
Do you ported from source?
I made already KitKat for Blade , but i have not enough time to upload it.
If you want i can put up the KitKat 4.4 ROM for Blade this week , and you could fix bugs

hey, that would be very cool, i'll help you as far as i can

we have a kitkat build http://www.modaco.com/topic/368013-devrom-151-cyanogenmod-110-android-442/

[Q] Alittle help From a Developer

I'm bout 80% done with building a ROM. It boots like a champ lol. Just seeing if a Dev. Could take a quick look over it before I publish it. Would be very thankful. Since this would be my first release.

Not a dev(or cook..), though I can test it.
id is d802 or maybe other variant ?

Developing Discussion | ROM & Kernel Dev./Port.

Hi Everybody
after some weeks Trying developing ROM's and Kernels i almost Give up... the kernel developing to MTK SoC is too much different compared to qualcomm SoC's (To me at least...) after compile more than 10 kernels to Run at my phone i only get Bluetooth and Radio FM not working with random reboots annoying frequently... but a real modifications to get this phone more smooth usage fail every time...(if you only compile the original source kernel it will run exactly like original kernel...)
I'm too n0#b alone to get everything running at developing process(kernel or ROM dev.).. at qualcomm phones(Xperia Acro S and Xperia L), i get more things running correctly with much more help from others Developers... but not released anything because it will be more from the same as others releases...
so if anyone here have more knowledge about that developing process things i have the Kernel Source and ROM platform to our phone...
---
i already try make CM12.1 run too.. but don't boot =#.. and if get work soon will be too much unstable to release, like my kernels =#
i will try port CM12.1 from @fire855 using that tutorial
the other possibility is try make compile the CM12.1 using our sources with modification from this ROM
but i will need help to make it compile right =#
so.. i will like have a discussion about that process with you guys... if anyone have some experience to help our phone have more custom's things to don't be locked with Original stuff/performance only.. if anyone have a useful guide, video or tutorial to compile anything to MTK SoC's it will be great too :highfive:

I appreciate your effort! I don't know much about MTK personally, but there is a thread on 4pda about porting CM 12.1 to MTK processors.
http://4pda.ru/forum/index.php?showtopic=671898
Sent from my VIVO AIR using Tapatalk

Ilxaot said:
I appreciate your effort! I don't know much about MTK personally, but there is a thread on 4pda about porting CM 12.1 to MTK processors.
http://4pda.ru/forum/index.php?showtopic=671898
Sent from my VIVO AIR using Tapatalk
Click to expand...
Click to collapse
already started try port CM12.1 ... but will not work too much things... almost every sensor will not work because that cross-firmwareOS port (CM Modules Drivers have a different compilation process =#) what i can do is try upgrade our source kernel using other MT6592 Sources to can compile the CM12 to our device... but again i will need find Module Updates drivers(blob) from other phones sources... =#
and my status with that right know is fixing a lot of errors while i compiling the kernel... i don't reach the inHouse ROM Compilation to than can get more Errors on logs to fix to release a simple Almost "stable" rom to how want test if it works properly to everyone... but don't push me to get that finished.. i work everyday and when i have time i try my best to develop that :highfive:
and release a unstable ROM/kernel is a wrong because maybe can brick someone phone because my errors (ramdisk modifications, and partition table map when installing the rom)... or we can wait BLU release the Lollipop with Hope because on twitter( @ UKkazam) tell me about no lollipop updates to this phone =#

i Tweeted to [@ KazamUK] asking they about lollipop updates and receive two replays... One say about newer updates to fix bugs on OS but not about lollipop and other saying "unfortunately, not upgrades to newer Android versions will be released"... otherwise [@ BLU_Products] Replay this "Please stay tuned on our social media for future updates, thanks!"... so... we have a faith about BLU brings Lollipop to our device? i don't have sure but with lucky it will happens :highfive:
...
and the porting CM12.1 ROM don't worked with me... bootloop =# and CatLog is extremely confuse =#

Kernel source link not working

I have an opportunity to make a PORT CM12 for BLU VIVO AIR in two days. A neighbor of mine bought a VIVO AIR and I will do whatever is necessary to get the ROM on the device.
I helped the BLU VIVO IV the users to have CM12. But as the device was not mine, so I could not fix some bugs. In the same epoch I talked to a BVA User and helped the kernel issue. He had given me feedback in relation to not have phone signal and not be able to replace the IMEI. But as I had no time, and the phone in my hands, the CM12 ROM stood with him.
Currently, it is quite possible that after CM12 MT6592 to be 95% stable in most of these devices Socs, the VIVO AIR may also have.
Once I have the device in hands, I'll let you guys know if CM12 can be available for all users VIVO AIR.
But if anyone know a actually already exist a ROM CM12 for VIVO AIR and clones.... Let me know...??

That would be awesome and I'm sure as me a lot of users are going to be happy about it
Sent from my REVIVED VIVO AIR using XDA mobile app

Help from experienced Developers!

Hello devs,
I have had a Micromax Canvas 2 Colors phone since a year and a half now. Custom/Themed ROMs were uncharted territory for me till June of this year, when my warranty was about to expire. I decided to use the VionicL ROM then. One heck of a ROM that was. Later, in the span of months, so many developments came in for the device, CM11, CM12/12.1, MIUI, and so on. I was very happy to see that there are so many people working hard on providing us the very best experience on our phone. But, like most of the average mobile phone users, I used to download the ROM, install it and enjoy, nothing more than that.
Now, as the time has come for me to switch to a new phone, I am switching to Lenovo K3 Note. I have had digitizer issues with my Canvas 2 Colors and the battery back-up was a little on the poorer side. So, I'm finally giving my phone away to one of my friends and moving on. Although, I would've loved to experience the final, stable build of CM12.1. Thanks to all the devs that worked hard on that. @Al3XKOoL : Especially you, man!
Now that I'm going to be using a new phone, starting from the 28th of October as per Flipkart, I looked up the phone on xda. Unfortunately, there is no forum for the phone. I was a little disappointed, but even C2C did not have a forum a few months ago. So, I tried looking for ROMs, and I have to say, I was a little disappointed with the progress in new and variety of ROMs. I agree that it is a fairly new phone, but there are a lot of people who own that phone, so I was expecting better results. And another point that many people like me would be searching for ROMs.
The help I request from all the developers here is to teach me to develop ROMs and Porting ROMs. I am absolutely inexperienced here, but I'm eager to learn. I'm 17 years old and I am studying 12th grade at the moment. I would still love to learn about ROM development and Porting so that I can provide the people with some ROMs like you all have. Although, I will not be helping out the C2C family, I can start to help the K3 Note family in any way I can. I hope some developers are interested in having an acquaintance.
Please consider this a sincere request and if anyone can please help me learn, I would be very, very grateful to you. I know that I can't learn it overnight, and that is why I want a proper guidance.
If anyone is interested to help me learn about the things mentioned above, please contact me through a message.
Thank you and sorry for annoying you lot with a long post!
And I will be indebted forever to all the developers in the C2C community for giving me and all the C2C owners a pleasurable experience. Thank You!
Sorry for tagging you people, but I hope you don't mind and you people are the most recognized devs in the C2C community :
 @vibhu0009
 @smokerman
 @ariafan

first of all thanks for our words..im still using my WIKO RAINBOW as my second phone..ive moved on to VODAFONE SMART ULTRA 6 and im testing MIUI 7 LOLLIPOP with a ported rom already that is booting and running with TWRP ..although is very buggy its ALPHA version still, that is nice..
for developers/porters whatever is not easy to teach someone..we have our work to do and that kind of knowledge we have, it took us a few years and at least some dead phones, hard bricks and a few other bad things that could happen to our phone..so my advice to you:
read
search
talk with other users
now and then ask for help when you need it, some users know a lot
you need time and patient..be aware that many times things will not go as you expect or wish..best of luck and keep following us in my blog and youtube..RAINBOW / MMX A120 C2C still is a good phone.:good:

Is anyone developing cm 12 for lenovo k3 note

smokerman said:
first of all thanks for our words..im still using my WIKO RAINBOW as my second phone..ive moved on to VODAFONE SMART ULTRA 6 and im testing MIUI 7 LOLLIPOP with a ported rom already that is booting and running with TWRP ..although is very buggy its ALPHA version still, that is nice..
for developers/porters whatever is not easy to teach someone..we have our work to do and that kind of knowledge we have, it took us a few years and at least some dead phones, hard bricks and a few other bad things that could happen to our phone..so my advice to you:
read
search
talk with other users
now and then ask for help when you need it, some users know a lot
you need time and patient..be aware that many times things will not go as you expect or wish..best of luck and keep following us in my blog and youtube..RAINBOW / MMX A120 C2C still is a good phone.:good:
Click to expand...
Click to collapse
Hey, thanks for taking time out to read my post and replying.
Nice to hear that you've been working on a different phone and rolling out new ROMs for that phone too!
Yes, I know that everyone have their own work, family and personal stuff and everyone are developing in their free time or as a hobby. I will be doing the same too as I have my studies as a bigger priority.
I understand it is not easy to teach anyone about developing, at least guiding is possible, right? I would be glad if you could guide me in what to read and where to be careful etc. stuff like that.
I already bricked my K3 note once and revived it somehow. I know it will not be an easy road or it is just as easy as downloading a ROM and flashing it in recovery, most of the users can do that. I know it is hard work, I will try to read, but there is so much knowledge on XDA alone that it will take me forever to read, understand and be able to implement. So, what I am asking is, if you could let me know on where to begin and in which direction to go after that, I would be indebted to you.
Again, Thank you for taking some time out, I know you have loads of work, and I hope I can be as good a developer as you someday!
weaponoidindustries said:
Is anyone developing cm 12 for lenovo k3 note
Click to expand...
Click to collapse
There is a Chinese developer who has rolled out CM12.1, but the English translations are not complete, so there are some chinese fonts still left behind, and there are some bugs in that too. I would not recommend using that ROM for daily use till the bugs are sorted out and the full English support is included.
With some support, I was planning on compiling CM12.1 for the K3 note. I've noticed that major developments for this phone is on some Spanish and Russian websites and not on XDA. I was a little sad to see that, but hopefully, there are a lot of developments on XDA too!
Cheers1

Hello There!!
My Phone Is Mmx A120 Canvas 2 colours
I was trying to get back to stock rom
And Always Getting this no space error 5069 While Flashing (1st image)
After searching i found that format will fix this and i can flash like a charm
But after formatting my Device Is dead
no boot, no charging, no recovery
I'm Trying TO whole flash but I'm there is no option for that only Getting without bootloader one
Then i've checked it memory in memory test option now i'm getting
Nand Flash Not Detected
Plz!!! tell me what i can do to take my phone back to life
The Phone is out of warrenty

Cyanogenmod for P9 lite?

Because I'm bored most of the times, I decided that I will try to port the cm for our p9 lite. First of all, I wanna say that I'm not a developer and my experiences with porting aren't too big (i only ported some roms from moto g to moto g 4g version and cm11 to unbranded chinese tablet). So my question is guys, do you think that it's worth trying? I read that it's pretty hard to make custom rom for devices that have chipsets like kirin, mediatek etc... But since Huawei released their kernel sources for this device I thought that it isn't a bad idea
What do you think?

there are a few guys on p8 lite forum that are trying for a while now...i think it's just to hard and we don't have experienced devs to work on our device

snapdesign said:
there are a few guys on p8 lite forum that are trying for a while now...i think it's just to hard and we don't have experienced devs to work on our device
Click to expand...
Click to collapse
Yeah, they even ported cm13 to p8 lite thats why I started thinking about it

dc239 said:
Yeah, they even ported cm13 to p8 lite thats why I started thinking about it
Click to expand...
Click to collapse
i don't think they did it... there are 3 guys that work on the same project...

I would love to see CM on this device.
It is pretty popular as well, so maybe we will see a build one day.
If somebody understands chinese, I bet it is worth to keep an eye out on their forums
Maybe it is also worth to observe the progress on the P9...

Schlengge said:
I would love to see CM on this device.
It is pretty popular as well, so maybe we will see a build one day.
If somebody understands chinese, I bet it is worth to keep an eye out on their forums
Maybe it is also worth to observe the progress on the P9...
Click to expand...
Click to collapse
I looked on the chinese forums too (our p9 lite is named huawei g9 in china) but there are only threads about twrp recovery and roms that are based on stock. I'm now taking my time to learn how cm and the other stuff works so i will try to report some progress soon hopefully

dc239 said:
Because I'm bored most of the times, I decided that I will try to port the cm for our p9 lite. First of all, I wanna say that I'm not a developer and my experiences with porting aren't too big (i only ported some roms from moto g to moto g 4g version and cm11 to unbranded chinese tablet). So my question is guys, do you think that it's worth trying? I read that it's pretty hard to make custom rom for devices that have chipsets like kirin, mediatek etc... But since Huawei released their kernel sources for this device I thought that it isn't a bad idea
What do you think?
Click to expand...
Click to collapse
We have kernel source code, and we can start building cm13,
But first we need a device tree.
My knowledge is limited to build ROMs from source, and yes i have kernel source code and cm13, but i need device tree and I don't have time to build it from scratch

lzimbrea said:
We have kernel source code, and we can start building cm13,
But first we need a device tree.
My knowledge is limited to build ROMs from source, and yes i have kernel source code and cm13, but i need device tree and I don't have time to build it from scratch
Click to expand...
Click to collapse
But we can use a device tree from p8 lite which has similar chipset (kirin 620) and then modifiy it. Correct me if i'm wrong

dc239 said:
But we can use a device tree from p8 lite which has similar chipset (kirin 620) and then modifiy it. Correct me if i'm wrong
Click to expand...
Click to collapse
As far as I know p9 lite has kirin 650 SoC, after some quick research i found that these two are different from many points... Of course you can try it but they aren't many chances of success.
Update:
I have done more research and someone was able to build and update kernel from that source. So we have a short start. At least we know that kernel source is ok

lzimbrea said:
I have done more research and someone was able to build and update kernel from that source. So we have a short start. At least we know that kernel source is ok
Click to expand...
Click to collapse
That's some good news, so the main problem for now is to build the device tree , but I don't know where to start (for now)

Hello,
I would just like to give my support to you and say that I'd really like if you could port CM to our P9 Lite! I'd contribute and donate also

Memovic said:
Hello,
I would just like to give my support to you and say that I'd really like if you could port CM to our P9 Lite! I'd contribute and donate also
Click to expand...
Click to collapse
Just to let everyone know. I planning to start working on kernel and device tree for p9 lite.
Probably I will make a new thread on development section soon. But don't expect to be a release soon... Will take a while till first build

lzimbrea said:
Just to let everyone know. I planning to start working on kernel and device tree for p9 lite.
Probably I will make a new thread on development section soon. But don't expect to be a release soon... Will take a while till first build
Click to expand...
Click to collapse
Great news and good luck. I bought this device with 2 years of payment plan, so I don't expect on buying anything new soon haha.

i talked with @XePeleato on the p8 lite section... they have made great progress... maybe he can help if you want... seems like a great guy

snapdesign said:
i talked with @XePeleato on the p8 lite section... they have made great progress... maybe he can help if you want... seems like a great guy
Click to expand...
Click to collapse
Yeah, I don't have the device but I may be able to help you out whenever I finish CM13, since then I'll have more time. By the way, don't be too excited about the kernel sources, We also have the p8 lite kernel source but many stuff is missing.

Emm,is it a bad idea to make a sort of a chat room for those working on CM for the P9 Lite?
It would go much faster if several people worked on it together instead of working separately,right?
So far I took the P8Lite device and vendor trees,replaced the blobs/sensitive stuff with the ones from the P9 Lite and edited the config files.
I tried to make the -eng build(of course,to be able to logcat broken things),yet the build info wouldn't mention the full build name in the "CM_VERSION=" section. I must've missed something I can't locate no matter how hard I try.
I also tried to build the kernel first,but it asked for the cyanogenmod_hi6250_defconfig in /arch/arm64/configs. I then "added" it(improvised by creating a copy of the stock defconfig and just renaming it),and then the build procedure asked for "hisi_cm_hi6250_debug_defconfig" in /arch/arm/configs,and I have no clue on how to get that one.
This is the first time I tried to do a thing like this,but I wanted to try,and sharing information(even the ones which appear to be useless) might help someone...
I will sync the improvized device and vendor trees when I get back home(Sunday),hopefully it will be at least a bit helpful to everyone.
It is most likely that you guys will keep ignoring me,but we surely can make it go faster if we work together.

The Marionette said:
Emm,is it a bad idea to make a sort of a chat room for those working on CM for the P9 Lite?
It would go much faster if several people worked on it together instead of working separately,right?
So far I took the P8Lite device and vendor trees,replaced the blobs/sensitive stuff with the ones from the P9 Lite and edited the config files.
I tried to make the -eng build(of course,to be able to logcat broken things),yet the build info wouldn't mention the full build name in the "CM_VERSION=" section. I must've missed something I can't locate no matter how hard I try.
I also tried to build the kernel first,but it asked for the cyanogenmod_hi6250_defconfig in /arch/arm64/configs. I then "added" it(improvised by creating a copy of the stock defconfig and just renaming it),and then the build procedure asked for "hisi_cm_hi6250_debug_defconfig" in /arch/arm/configs,and I have no clue on how to get that one.
This is the first time I tried to do a thing like this,but I wanted to try,and sharing information(even the ones which appear to be useless) might help someone...
I will sync the improvized device and vendor trees when I get back home(Sunday),hopefully it will be at least a bit helpful to everyone.
It is most likely that you guys will keep ignoring me,but we surely can make it go faster if we work together.
Click to expand...
Click to collapse
that's what i said in the p8 lite section a while back... for devs to work together... in the end they finally started a project together and made big progress... maybe a google plus page or on Hangouts...

snapdesign said:
that's what i said in the p8 lite section a while back... for devs to work together... in the end they finally started a project together and made big progress... maybe a google plus page or on Hangouts...
Click to expand...
Click to collapse
I use Hangouts to communicate with my fellow rom builders/dev.
Hangouts is pretty good for chat groups,and is easy to establish/use.
I also asked one excellent dev for help when he gets the time.
So,theoretically,we have a decent number of capable people for this endevour.
My Hangouts mail is [email protected].
Anyone who is interested in exchanging information can freely talk to me.

The Marionette said:
It is most likely that you guys will keep ignoring me,but we surely can make it go faster if we work together.
Click to expand...
Click to collapse
I'm 100% in, but i can't help you too much, cause i'm still trying to learn about the rom developing...

The Marionette said:
I use Hangouts to communicate with my fellow rom builders/dev.
Hangouts is pretty good for chat groups,and is easy to establish/use.
I also asked one excellent dev for help when he gets the time.
So,theoretically,we have a decent number of capable people for this endevour.
My Hangouts mail is [email protected].
Anyone who is interested in exchanging information can freely talk to me.
Click to expand...
Click to collapse
I may join if you like me to, but if you are focused on CM, delete vendor.mk, I completely rebuilt it to work on CM, you can't add such a high amount of blobs.
What I may suggest, is to fork the kernel (of your device) and the P8LiteDev tree, and use it as a base, but remove the blobs from vendor.mk
It would be also a good idea to deodex your rom and upload it somewhere.