Database Info

[ROM][Development/Experimental][Micromax A70][CyanogenMod from Source]

Hi All.
I am Abhisek and I am trying to build CyanogenMod from source for our Micromax A70.
Micromax A70 is quite popular in India as a budget phone, but this device is stuck with Froyo. No more updates from Micromax as well as no kernel source from Micromax. So I am trying to build CyanogenMod from source for Micromax A70.
I am choosing CyanogenMod over AOSP as CyanogenMod supports more devices and have many patches over AOSP. So building CyanogenMod will be easier than AOSP. If successful, I will port a Oxygen/AOSP build.
I was about to give up hope until I found out how to enable ADB on Micromax A70. So I have successfully enabled ADB & obtained the system dumps. Now I can start on this project.
Current Status:
1. ADB is working perfectly.
2. System dump obtained.
3. Hardware info obtained.
4. Firmwares obtained.
5. CyanogenMod sources download in progress.
6. Currently creating the device & vendor folders.
I will keep the progress updated here. Lets hope for best.
P.S. Mods if this thread is inappropriate or in wrong forum, please do the needful. Couldn't find a better place to post this.

Reserved for future use

Reserved for future changelogs

I will provide the adb tutorial in case anyone is interested ( that is how I got the system dump ). All credits go to mastermind1024 of androidforums.com. It's not my work, so if you have to thank, thank him. He is the one did all the adb working stuff. You can read the original post Here.
Update:
mastermind1024 is here on XDA. You can see the tutorial Here.
For me, I have to manually run /sbin/adbd from Android terminal emulator to get a working adb connection. You also have to give permission for adbd in SuperUser. FYI I use ubuntu.
If you need the boot.img & recovery.img You can follow the tutorial Here

abhis3k said:
Hi All.
I am Abhisek Mukherjee and I am trying to build CyanogenMod from source for our Micromax A70.
Micromax A70 is quite popular in India as a budget phone, but this device is stuck with Froyo. No more updates from Micromax as well as no kernel source from Micromax. So I am trying to build CyanogenMod from source for Micromax A70.
I am choosing CyanogenMod over AOSP as CyanogenMod supports more devices and have many patches over AOSP. So building CyanogenMod will be easier than AOSP. If successful, I will port a Oxygen/AOSP build.
I was about to give up hope until I found out how to enable ADB on Micromax A70. So I have successfully enabled ADB & obtained the system dumps. Now I can start on this project.
Current Status:
1. ADB is working perfectly.
2. System dump obtained.
3. Hardware info obtained.
4. Firmwares obtained.
5. CyanogenMod sources download in progress.
6. Currently creating the device & vendor folders.
I will keep the progress updated here. Lets hope for best.
P.S. Mods if this thread is inappropriate or in wrong forum, please do the needful. Couldn't find a better place to post this.
Click to expand...
Click to collapse
you mean this rom is under development? I don't have a70 just asking. And you are on right place. Also microsoft needed to open kernel source.

cips gokhle said:
you mean this rom is under development? I don't have a70 just asking. And you are on right place. Also microsoft needed to open kernel source.
Click to expand...
Click to collapse
You meant Micromax right
Yes the ROM is under development. The repo sync is taking forever. I have a pathetic BSNL BB Connection here.

abhis3k said:
You meant Micromax right
Yes the ROM is under development. The repo sync is taking forever. I have a pathetic BSNL BB Connection here.
Click to expand...
Click to collapse
sorry yes i mean micromax. and best for your rom. i think it's first 2.3 a70 rom?

Good!
How much % is the sync complete?
Moreover who are u on androidforums?

varun.chitre15 said:
Good!
How much % is the sync complete?
Moreover who are u on androidforums?
Click to expand...
Click to collapse
I have same userid abhis3k. Sync seems to be complete at 70%, I can only see the directory size, Fetching projects is showing 89%

cips gokhle said:
sorry yes i mean micromax. and best for your rom. i think it's first 2.3 a70 rom?
Click to expand...
Click to collapse
Yes AFAIK if I succeed, this will first GB ROM for A70.
------------ edit -------------
I have tried to run ADB with root permissions. It works, but somehow adb remout does not work.
P.S.: I found the problem, the system was already r/w.

I would say NO bcoz i m from a secret team and we had ported GB to A70 and touch doesn't work in any of the Ports
Moreover u will wonder that touch doesn't work in Android 1.5,1.6 which i had ported from HTC G1 also it doesn't work in 2.1 which i ported from Micromax A60
So we need to build ROM from source which u r doing. Moreover that is not enough because as soon as sync completes then we need to enable touch drivers in BoardConfig.mk

varun.chitre15 said:
I would say NO bcoz i m from a secret team and we had ported GB to A70 and touch doesn't work in any of the Ports
Moreover u will wonder that touch doesn't work in Android 1.5,1.6 which i had ported from HTC G1 also it doesn't work in 2.1 which i ported from Micromax A60
So we need to build ROM from source which u r doing. Moreover that is not enough because as soon as sync completes then we need to enable touch drivers in BoardConfig.mk
Click to expand...
Click to collapse
Great!! I had no idea A70 had a GB port. If you can share the details It would be easier to compile for A70.

abhis3k said:
Great!! I had no idea A70 had a GB port. If you can share the details It would be easier to compile for A70.
Click to expand...
Click to collapse
I think akshay is uploading that port now.he has made a thread n uploading right now.i dont know if it's the same that varun is talking abt but mostly it is.
http://forum.xda-developers.com/showthread.php?t=1540104

mastermind1024 said:
I think akshay is uploading that port now.he has made a thread n uploading right now.i dont know if it's the same that varun is talking abt but mostly it is.
http://forum.xda-developers.com/showthread.php?t=1540104
Click to expand...
Click to collapse
Sure I will check it out. It will speed up the development.
--------- edit ------------
This seems like a binary port using kitchen. Right?

Binary port?
Its ported using kitchen which involves replacement of kernel.
And when sync completes, inform us here,a we will make two roms.
One with unchanged boardconfig.mk and second with modded boardconfig.mk
Sent from my Micromax_A70 using Tapatalk

Replacement of kernel includes replacing binary files including so ko and firmware files. Which are all binary. Only recompile includes a output which is not binary replacement.
Download is still at 93%. I will come back when its finished.
Sent from my LG-P500 using XDA

I am also at 91% since a week..i am getting fatal errors on sync now n then..project downloads upto abt 86%(abt 650mb) n then I get error...i had to do all again..still no luck.i wish i can finish it tonight.we (me,varun,akshay) eager to lunch rom from cm source as we have hope that changing boardconfig will give us working touch.let's see.

extract-files.sh
I have completed sync & also made extract-files.sh
I want others to examine & complete it if I have missed something.

mastermind1024 said:
I have completed sync & also made extract-files.sh
I want others to examine & complete it if I have missed something.
Click to expand...
Click to collapse
@mastermind I have checked the file. Seems so good so far. I hope my sync will also complete by tonight. I am going crazy with these BSNL broadband problems
Have you started the build? Let me know the boardconfig.

mastermind1024 said:
I have completed sync & also made extract-files.sh
I want others to examine & complete it if I have missed something.
Click to expand...
Click to collapse
the script doesnt have adb pull for the binary akmd2.without which sensors wont work .
and in a70 there is also a file called Focal touch.kcm and this is used by the kernel at boot i checked in dmesg .
so add this two files two ..
akmd2
focaltouch.kcm [from usr/keychars]

>> **Devs using cygwin** <<

how many dev of galaxy fit or other devices have used Cygwin ?
If u have used then please post reply "step by step" method of creating rom by which u created ur rom succesfully!!
»»»»Mind --- only commands in cygwin not the system extraction part««««
___As many guys want to create rom but no one supports or reply clearly leaving some ____
***So please post as this will be helpful for every one who ever wants to create rom ***

avilove4u said:
...
»»»»Mind --- only commands in cygwin not the system extraction part««««
Click to expand...
Click to collapse
I`m no experienced dev (if it all a dev, have build and compiled kernels for my notebooks with linux) , but could build a good rom for s5670 with cygwin as a little game / playing. I have read a part of your endless Quest., try to learn by doing, e.g. comparing sometimes diffent resultats and the beginning. There is e.g. to compare the update/r.scripts with notepad++, you will see the difference and then you can run cygwin correct (with a boot.img of your own s5670).

martin_s5670 said:
I`m no experienced dev (if it all a dev, have build and compiled kernels for my notebooks with linux) , but could build a good rom for s5670 with cygwin as a little game / playing. I have read a part of your endless Quest., try to learn by doing, e.g. comparing sometimes diffent resultats and the beginning. There is e.g. to compare the update/r.scripts with notepad++, you will see the difference and then you can run cygwin correct (with a boot.img of your own s5670).
Click to expand...
Click to collapse
some new dev and i am having problems in "boot.img and script part" .. !!
rom flashes but reboots into previous rom ...

O sry
hmm yes full tutorial later

is there anyone to help us .. ??

Request to ALL DEVs.................. Request for Guide for ROM Porting

Dear all Dev
I am a noob. but i want to learn.
I want create a ROM for myself, and like me there must be many user with the same desire of building there own ROM but the problem is lack of information.
I tried many guides but want's successful.
So i request all the Devs to create a Tutorial for porting different ROM to our device, this tutorial should be device specific and OS specific.
There are many Dev who could contribute to this like
 @SuperDroid-BOND, @ibshar, @sagarwep could contribute in guiding the rom porting from MTK6589 device to MTK6577 device.
 @mufti.arfan, @anand_mmx could highlight on porting Lewa ROMs
@Akhilendra Gadde, @Ak****banta on porting Miui ROMs
@Dark4Droid, @khan_frd2002, @jigarmpattani, @dhiarya, @bsuhas and other great dev could help also in their respective field of specialization.
This would be the greatest contribution for our section if we could create a thread like this.
This just a thought and a request.......

Using windows is advised as you need to download a program called notepad++ on it. But you can use Ubuntu too.
First of all, make sure that you have two rom.zips that are
Base
The rom that was originally developed for our canvas 2 . Basically cm roms
Port
The rom that you want to run on our phone. That is developed for other phones. The android version of base and port roms have to be same.
Must have
Notepad++, base rom, port rom
Step 1
After you're done downloading both base and port roms, extract them into two different files and rename them as base and port.
Step 2
Open system folder in the base rom folder and delete
App
Fonts
Framework
Media
Open system folder in the port rom folder and copy
App
Fonts
Framework
Media
Then paste the copied files into system folder of base
Step 3
Open system-etc-permissions in both port and base folders. Delete every permission in base EXCEPT platform and handheld_hardware.
Copy all permission except platform and handheld_hardware and paste the copied files into the permission folder of base rom.
Step 3b (if there is an tweaks in port rom)
Go into system-etc-init.d in both port and base rom folders.
Copy everything from init.d in port EXCEPT banner and paste them into init.d in base
Step 4
Go to META-INF-com-google-android and open updater script using notepad++
(In both port rom and base rom folders)
Delete all the lines that has set perm or setperm recursive in base rom updater script
Copy all the lines that have setperm or setperm recursive in port rom updater script. Paste the copied lines into base rom updater script, where the original setperm lines of base rom was.
Step 5
Save the updater script and zip the contents of base rom.
Step 6
Flash and test
If Rom is having a bootloop then go into lib folder of port Rom and copy these files
Libandroid_runtime.so
Libandroid_servers.so
Libandriod_driod.so
BEST OF LUCK (Y) :good:

dhiarya said:
Using windows is advised as you need to download a program called notepad++ on it. But you can use Ubuntu too.
BEST OF LUCK (Y) :good:
Click to expand...
Click to collapse
Thanks for the info, but i want devs to develop a device specific Tutorial / guide.
I tried the procedures to port ColorOS ROM from A116 to our device but stuck on boot. i dont known which files do i need to edit to get it boot.

Porting is basically very much same for most of the devices,and there are many threads for that ...
[GUIDE] Porting Guide - How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs
This one is most basic and easy.
[GUIDE]How To Port Different ROMS to Your Device (Simplest and Fastest)
If I can make a guide for LeWa , I surely would.
:good:

subhashdas said:
Dear all Dev
I am a noob. but i want to learn.
I want create a ROM for myself, and like me there must be many user with the same desire of building there own ROM but the problem is lack of information.
I tried many guides but want's successful.
So i request all the Devs to create a Tutorial for porting different ROM to our device, this tutorial should be device specific and OS specific.
There are many Dev who could contribute to this like
@SuperDroid-BOND, @ibshar, @sagarwep could contribute in guiding the rom porting from MTK6589 device to MTK6577 device.
@mufti.arfan, @anand_mmx could highlight on porting Lewa ROMs
@Akhilendra Gadde, @Ak****banta on porting Miui ROMs
@Dark4Droid, @khan_frd2002, @jigarmpattani, @dhiarya, @bsuhas and other great dev could help also in their respective field of specialization.
This would be the greatest contribution for our section if we could create a thread like this.
This just a thought and a request.......
Click to expand...
Click to collapse
+1
I like this idea. This is a great idea. There should be a nice guide which describes the steps, methods, exceptions etc. that are involved in ROM porting.
Maybe a more MTK oriented guide since there are already many generalized porting guides. A guide that acknowledges do's and don'ts, a guide that informs what we can and can't do.
However, this guide should also, preferably, detail on the "why's" and the "why not's" and not just provide a copy-paste tutorial seen in profound quantities throughout xda...
Now, this is a theoretical idea and not possibly/necessarily a one-man job. Therefore, the devs could perhaps collaborate on this hypothetical guide also giving their personal experiences on android development (tips, tricks, pointers, notes and stuff).

How about a guide on porting mtk 6589 Rom to mtk 6577..
Sent from my A110 using XDA Premium 4 mobile app

subhashdas said:
Thanks for the info, but i want devs to develop a device specific Tutorial / guide.
I tried the procedures to port ColorOS ROM from A116 to our device but stuck on boot. i dont known which files do i need to edit to get it boot.
Click to expand...
Click to collapse
All Guide are Some How Same Bro.... You can port MT6589 AOSP easily but other one like color os, sony etc are hard you can only port it by debugging...

I am trying to port A110Q Rom to canvas 2 but I don't have the cwm flashable zip .All I have I'd the sp flashable Rom . I know how to extract the Rom from it . But how do I make the meta inf folder that had the updater script .
Sent from my A110 using XDA Premium 4 mobile app

Matthew_Farrell said:
I am trying to port A110Q Rom to canvas 2 but I don't have the cwm flashable zip .All I have I'd the sp flashable Rom . I know how to extract the Rom from it . But how do I make the meta inf folder that had the updater script .
Sent from my A110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
use any custom rom meta folder of same version

Very Helpful
Thank u .. very helpful guides

[Q]Porting MT6582 to MT6572

Hello Guys,I searched for Lewa Os 5 for MT6572 but I didn't find any.So,I thought to download MT6582 as these chips are in combination like MT6589 to MT6577.I downloaded Wiko darkmoon . @superdragonpt created or ported it.I want it for my use,If got successful then I will take permission from him.I patched the rom with my stock files.The updater-script was just fine with exactly same mount points as in my Xolo A500s.I unpacked boot.img with michfood's packing and unpacking tools ,but the thing that I am worried is the boot.img of 6 mb shrinked to 4 mb!I just edited init.rc and added bootclasspath of lewa.
But,it didn't boot.I think I need to replace my ram disk in my boot with wiko dark moon's boot ram disk.Could I port this way?
Is it possible to port MT6582 to MT6572?It's my first time of cross-porting.
Please,I need some help on this!

Hi
A: Rom was built from scratch ( not an port ), i used LeWa patchroom ( just like MIUI's patchroom).
LeWa patchroom is Closed Source (proprietary) so i can't help you with that
B: You should be able to "port" it to your device, concerning kernel:
- Use ( mandatory) LeWa's ramdisk
- If your kernel after repack is smaller, thats rather normal , its just an question of compression %.
Also since we are talking about port of diff SoC's there are other things that you'll need to fix:
- SoC ID on updater-script; ramdisk: build.prop; etc.
- Also keep in mind that LeWa itself its an themed rom, so its uses an 2nd framework ( lewa-res) that works under the main one, you may need to patch other things in the process.
--> For this, check the MT65xx porting thread, its very usefull.
Regards

superdragonpt said:
Hi
A: Rom was built from scratch ( not an port ), i used LeWa patchroom ( just like MIUI's patchroom).
LeWa patchroom is Closed Source (proprietary) so i can't help you with that
B: You should be able to "port" it to your device, concerning kernel:
- Use ( mandatory) LeWa's ramdisk
- If your kernel after repack is smaller, thats rather normal , its just an question of compression %.
Also since we are talking about port of diff SoC's there are other things that you'll need to fix:
- SoC ID on updater-script; ramdisk: build.prop; etc.
- Also keep in mind that LeWa itself its an themed rom, so its uses an 2nd framework ( lewa-res) that works under the main one, you may need to patch other things in the process.
--> For this, check the MT65xx porting thread, its very usefull.
Regards
Click to expand...
Click to collapse
Thanks for your infomative reply.Ok,I done most the things.Rather than replacing ram disk,I added bootclasspath in init.rc
How can I make lewa from scratch?I haven't heard it before.

Give a try to This
nightwalker said:
Thanks for your infomative reply.Ok,I done most the things.Rather than replacing ram disk,I added bootclasspath in init.rc
How can I make lewa from scratch?I haven't heard it before.
Click to expand...
Click to collapse
Using unpack tool by Michfood unpack your stock boot.img and boot.img of the rom u want to port ... then only replace kernel and kernel header from base to port and repack the image ... and try to flash the rom

navneetasnavi said:
Using unpack tool by Michfood unpack your stock boot.img and boot.img of the rom u want to port ... then only replace kernel and kernel header from base to port and repack the image ... and try to flash the rom
Click to expand...
Click to collapse
I knew it won't work,as I knew that we need to replace ram disk.I did it and I have managed to come till boot anim.

So what ?? At least give a try to the way i suggested It booted up the oppo rom for my device. :/

navneetasnavi said:
So what ?? At least give a try to the way i suggested It booted up the oppo rom for my device. :/
Click to expand...
Click to collapse
Sorry,you were right too.

nightwalker said:
Sorry,you were right too.
Click to expand...
Click to collapse
Did it worked??????
if yes then please press thanx : )

navneetasnavi said:
Did it worked??????
if yes then please press thanx : )
Click to expand...
Click to collapse
Haven't tried it not yet

There were actually lewa OS5 for MT6572. Even OS6 also existed today.
I ported it myself from different SoC.

How to port rom from HTC sensation?

I have an One s with S3 processer(villeC2).
Its specs are similar to sensation(with same cpu and screen resolution),but sensation has Android 7.1 ROM and one s only 4.4......
I would like to port a ROM for it from sensation.
Does anyone know how to do that?
Or if it is possible ?
(sorry for my bad english)
(my first post)

Some info !
Hi,
Actually I'm new in building roms and kernels, too. But i can share some info with you.
For starting this tutorial may be helpful: [Guide] Compile 4.2 & 4.3 & 4.4 Roms for villec2
As you can see, you will need "device", "vendor" and "kernel" source to build a rom.
Usually you can find source code of roms and kernels in xda threads and can start from those.
For example for Android 7.1 you can use RROS vendor and VilleC2 device and kernel sources. (Note: i don't know are these examples compatible or not?!)
And for kernel, maybe you has to upstream the kernel source to be compatible with new version of android that you want to build.
Good luck.
-----------------------------------
Edit:
After Compiling for myself, i figured out Vendor files for choosed rom (Lineage, RR, ..) will be included by their manifest files automatically. so for "Vendor" part in "local_manifest.xml" (or newer "local_manifests/roomservice.xml") we need to assign "proprietary_vendor" files related to our devices. "proprietary_vendor" files can be extracted manully if there isn't any online source.
one more useful guide: [GUIDE]Building any ROM from source for HTC One S aka ville!