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.
Related
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]
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
Guide to Mediatek Building(Guide 2:=boot.img)
A common misconception on XDA is that mediatek devices have boot.img similar to qualcomm.. I'll try to explain why it isn't and how to make one.
Mediatek appends a header to its Ramdisk(initramfs) and its kernel so that the board can figure out that its a ramdisk/kernel. Without these headers the boot.img you build will won't work; If you've been getting bad results when making a boot.img this could be one of the reasons
Requisite
Any Linux based system
the mkimage i've attached in the post
Adding the MediaTek header
A executable named the 'mkimage' is needed for this(attached in post). If you're one of the kernel devs or for the ones who have the mediatek kernel source, this file is present in the kernel_source/mediatek/build/tools/mkimage.
What does it do?
it appends the mediatek header to the first 512 bytes of your ramdisk/kernel
Adding the meditek header
For the kernel,
Code:
mkimage kernel KERNEL > kernel_with_meditek_header
For the ramdisk,
Code:
mkbootfs ./root/ | minigzip >ramdisk.gz
mkimage ramdisk.gz ROOTFS > ramdisk.img
Removing the MediaTek header
If you want to remove header from kernel,
Code:
dd if=kernel of=kernel_without_header bs=1 skip=512
If you want to remove header from ramdisk
Code:
dd if=ramdisk of=ramdisk_without_header bs=1 skip=512
the bs tells dd how many bytes to read and write at a time.
the skip tells it that how many bytes to skip at start. here its 512 since the mediatek header occupies 512bytes. we can use count if you want
Here's how you manually pack boot.img after adding headers
Code:
mkbootimg --kernel zImage_with_header --ramdisk ramdisk_with_header.img -o new_boot.img
You can now use this boot.img to flash to your phone
Modules!!
Modules are very important, Read previous guide(Building kernel) about how to build modules(Guide attached to signature). Modules are very kernel specific and the rom wont boot if you don't push these modules to the /system/lib/modules replacing the ones currently there.
Extra Information!
to delete parts of file from the end of file which is 100 bytes. for example:
Code:
dd if=file of=file1 bs=1 skip=10 count=85
/*count=filesize-startsskip-endskip*/
here,count=100-10-5=85.
Hope this guide helped you.
All questions are welcome in the thread
Regards and Good luck
Links to my next Guides
Building the ROM{MediaTek}
Building the Kernel{MediaTek}
Nice guide
... but that was already explained on this thread
The thread was for the MT6577, but concerning this issue (and others) its also valid for the other's MT65xx ; MT81xx ; MT83xx SoC's.
Also this thread is the best resource on @xda concerning Mediatek kernel / issues , etc.
But this should help, the users that are new on the "Mediatek" Platform.
Regards
superdragonpt said:
Nice guide
... but that was already explained on this thread
The thread was for the MT6577, but concerning this issue (and others) its also valid for the other's MT65xx ; MT81xx ; MT83xx SoC's.
Also this thread is the best resource on @xda concerning Mediatek kernel / issues , etc.
But this should help, the users that are new on the "Mediatek" Platform.
Regards
Click to expand...
Click to collapse
I'm making a guide for building an rom from source step by step for the new developers. I've started off with the boot.img. Not sure if that's the way to go, but I'll try my best to make people understand the build process and how mediatek works
Sent from my Moto G using XDA Free mobile app
MasterAwesome said:
I'm making a guide for building an rom from source step by step for the new developers. I've started off with the boot.img. Not sure if that's the way to go, but I'll try my best to make people understand the build process and how mediatek works
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Your more than welcome we are only an few working with Mediatek's.
We all know how MTK works, and their Closed Source / Anti-GPL Atittude...
Best Regards
superdragonpt said:
Your more than welcome we are only an few working with Mediatek's.
We all know how MTK works, and their Closed Source / Anti-GPL Atittude...
Best Regards
Click to expand...
Click to collapse
My aim is to increase that number
Sent from my Moto G using XDA Free mobile app
W0W its good to see more Devs started to work for MTK devices ^_^ nice guide
EnerJon said:
W0W its good to see more Devs started to work for MTK devices ^_^ nice guide
Click to expand...
Click to collapse
You're quite welcome :laugh:
Kernel Development guide coming today
MasterAwesome said:
Kernel Development guide coming today
Click to expand...
Click to collapse
i am kind of porter and developer of a110 aka micromax canvas 2 community.....
i would love to learn about making kernal and mediatek code....
waiting for it.....
thanks in advance..:laugh:
Avenger4droid said:
i am kind of porter and developer of a110 aka micromax canvas 2 community.....
i would love to learn about making kernal and mediatek code....
waiting for it.....
thanks in advance..:laugh:
Click to expand...
Click to collapse
I've added the links to my signature. Be sure to check it out
MasterAwesome said:
I've added the links to my signature. Be sure to check it out
Click to expand...
Click to collapse
thank you...Checking....
Suggestions for new guides are welcome and I'll try my best to do them.
Sent from my Moto G using XDA Free mobile app
Nice tutorial but still not clear for me. So i have built zImage, and then what? I need to use mkimage on zImage I have to produce boot.img, then push boot.img to my device?
giaur said:
Nice tutorial but still not clear for me. So i have built zImage, and then what? I need to use mkimage on zImage I have to produce boot.img, then push boot.img to my device?
Click to expand...
Click to collapse
yes you apply mkimage on the zImage and ramdisk The we mkbootimg for converting it into a boot.img and then you push to device.
MasterAwesome
Sent from my Moto G
Should I add mediatek headers to zImage and ramdisk and then pack them into boot.img?
giaur said:
Should I add mediatek headers to zImage and ramdisk and then pack them into boot.img?
Click to expand...
Click to collapse
Yes use
Code:
mkbootimg - -kernel zImage - -ramdisk ramdisk.img -o boot.img
Sent from my Moto G
Thanks, I think now it's clear. I think it would be useful for newbies if you also add this to first post. Also - don't I need any modules (.ko) also to push to device?
giaur said:
Thanks, I think now it's clear. I think it would be useful for newbies if you also add this to first post. Also - don't I need any modules (.ko) also to push to device?
Click to expand...
Click to collapse
Yes, you need to push the modules to your phones since they are kernel specific. To reduce size strip them off of unneeded assembler messages.
Regards
MasterAwesome
Sent from my Moto G
More information about pushing boot.img to phone and important stuff added to first post
Regards
MasterAwesome
WOW! good guide, I only have one problem, if I have a premade boot.img and I want to change the kernel, how do I do that? Thanks for this guide
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. So don't be an *** ****
*/
hi.. i'm already started make some modifications on ROM with other Brazilian DEV's for "Evertek S.A - SKMtek Genesis Tab GT7305"... we already found the source kernel from another Netbook or Development Board PC who uses the same SOC... but nothing already have been maked to kernel, we use the provided kernel from stock (Kernel 3.4.5+)... and about the ROM we already have two custom ROM's... One is Stock Modded (4.2.2) and another is KitKat Ported ROM from another Evertek Device... *Portuguese-Brazil Language Site/Forum
And we already make some modifications to this KK port...
- ROOT
- BusyBox
- Init.D support
- Build.Prop Mods
- SuperUser
- zipalign apps after boot
.. and other mods.
we already make too much on ROM but nothing about kernel... we want make a better kernel with optimizations and a better TCP/Clock Table, More Governors , More I/O Scheduler and maybe Overclock to 1600mhz to start after have a custom Kernel booting...
Now we need someone who understand about recovery's like CWM or TWRP and Kernel Compilation better than me to we can start make something awesome =D i think this can be used to another company's/Chinese tablets too, using the same SOC (WM8880) evidently... . . . (Found^^Working^^Recovery's)
i can't start testing here because if i flash this kernel using the Stock Recovery (WonderMedia Recovery tool) maybe i can possible brick my tablet... so if someone understand about CMW recovery to start would be nice =D
Update Progress / ChangeLog ¬
Code:
# 25/12:
- [STRIKE]Found Possible match [URL="http://forum.xda-developers.com/showthread.php?t=2305268"]CWM port[/URL] from [URL="http://forum.xda-developers.com/showthread.php?t=2216390"]Asus MeMo Pad 7{ME172V}[/URL] on XDA Forum[/STRIKE] #NOPE...
- FOUND WOKING [URL="http://blog.hadi-cpu.com/2013/09/cwm-recovery-6036-w8850-rc2.html"]CWM Recovery[/URL] from Malasya Blog from Generic WM8850 SOC tablet , Founded [URL="http://blog.hadi-cpu.com/2013/10/twrp-touch-wondermedia-wm8850-jb-version.html"]TWRP recovery[/URL] too but not tested (Thanks to #Rollidark to notify me about and #osinaldi to discover that from malasya blog) [Mirrors -> [URL="https://www.4shared.com/rar/2POyc0B0ba/CWM_WM8850_NSFAT-RC2.htm?sop=true"]CMW[/URL] -> [URL="https://www.4shared.com/rar/rJBfUTQF/TWRP-JB-NSFAT-WM8850.htm"]TWRP[/URL]] // [URL="https://www.facebook.com/groups/NewSmartFrenAndroTab/"]Facebook Group of Recovery Developers[/URL]
- Studying some way to introduce the missing Touch driver to kernel from [URL="https://gist.github.com/psachin"]psachin Github[/URL]|[URL="http://cdn.liliputing.com/wp-content/uploads/2013/01/rock_02.jpg"]apc-rock-II-[/URL]|[URL="https://github.com/psachin/apc-rock-II-kernel"]kernel[/URL] how already modded the Source to work with [URL="http://tinyurl.com/oqxmuam"]Generic Netbook[/URL] who uses the same SOC
-- Merry Christmas to #ALL
# ?? to 23~24/12:
- ROM JB and KK + ADV. Patch developed by Brazilian Dev's team
- found Source Kernel to WM8880 SoC
Brazilian Developers who already help this projects from forum - genesiseries :
Code:
# KK ROM:
- #paulomsilva2006 {KitKat ROM Port}
- #Rollidark {KitKat Patch}
- #Wcfuria
- #? - Pedro Alves
- #? - Pedro Victor
- #? - Walter Moretti
- #? - Moises Teixeira
Code:
# JB Stock ROM:
- #ylukasy {ROM Dev.}
- #Rollidark
- #paulomsilva2006
- +?
if i forget someone.. please comment below :highfive:
Reserved
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
funtikar said:
wow there's only a handful on and off development going on for this SoC, I still keep my WM8880 tablet just in case somebody made a breakthrough in doing Custom ROM or even getting real ubuntu/debian to boot natively... are you still on this?
Click to expand...
Click to collapse
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
DvDwx. said:
just a few Brazilian and Malasya Developers still make progress with this SoC... if you want to try install the custom ROM´s i have shared upper topic.. it will be by your won and I am not responsible for bricked devices...
i´m already started make progress with Custom Kernel but i need found the touch screen driver source and re-work the sound driver(Alsa Drivers...) and compile the recovery with kernel too.. to than have some trust on my work to flash it on tablet =#
:highfive:
Click to expand...
Click to collapse
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
funtikar said:
meh, its my rom testing ground anyway not really worried .. i actually have the tablet connect directly from the battery wires(the battery removed) to the adapter(usb)... anything is better than nothing for the development hehe...wait by Malasya do u mean Malaysia? whos that developer lol..
Click to expand...
Click to collapse
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
what a coincidence , I was wondering today when you will reply lol
ah I see too bad, maybe you will share it at techknowme forum, ... wow Malaysian ?, Im asking because I'm Malaysian, can you pm me the link where its shared?
DvDwx. said:
i mean Malaysia.. the country... because i don't have found the real developer.. only the Facebook's group where it have been shared... i write too fast and don't check if i write it correct too...
--
i Already compile the kernel with CMW recovery and flashed on tablet ... but i need find the Touchpad driver to make he work properly... i stay getting some other minor issues on logcat/kmsg reports...
but i already test four touch drivers and anyone works... only OTG stay working.. that is the problem on developing the kernel without the official source release by the producer company... maybe i will need close this developing project because that =/
Click to expand...
Click to collapse
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
tuyenat3 said:
please continue developing this project..i have using acer b1 740 and it dont have android 4.4 update
Click to expand...
Click to collapse
man... i just don't want blame anyone but... to we can do something to your tablet we need the kernel source and that don't stay open to developers... on this Chinese tablets we have some little configurations to can work with... but the custom kernel project i need to abandon for two reasons... first i don't have much time to can work to create a stable and functional custom kernel to everyone... second i don't have a kernel source compatible with tablets... what i found is from a electronics engineering Project computer Board ... and to it can fit on tablet is missing too much drivers compatibles with to can work smoothly and functional... someday if i found a new source maybe i can try comeback developer something to that =#
please continue developing this project
I use a genesis 7305 his kernel is very poorly optimized would like to make this usable tablet sorry for my bad English I use Google translator ;-;
2021... I tried to put a Chinese rom, but I brick the tablet, it only responds to fastboot, when I put the sudo command fastboot flash:raw boot uzImage.bin ramdisk.bin and plug in the charger and press power it appears a genesis screen.
Boot FOSSEE-OS from SCARD | FOSSEE-Laptop
laptop.fossee.in
GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
A low cost fossee-laptop based on wm8880 ARMv7 SoC - GitHub - FOSSEE/FOSSEE-netbook-kernel-source: A low cost fossee-laptop based on wm8880 ARMv7 SoC
github.com
My device is Nokia 3 TA 1032 running Android Pie rooted using Magisk and with TWRP custom recovery with kernel version 3.18.119+ ....
Is there a custom Kernel available for this device which is 3.19 or above.?.?.
If so ...can anyone provide me the link please.?.?.
And if not...does anyone know about porting/compiling kernel for this device.?.?.
please...i need some help....
https://ibb.*co/ MCBrDtC
mechano59 said:
My device is Nokia 3 TA 1032 running Android Pie rooted using Magisk and with TWRP custom recovery with kernel version 3.18.119+ ....
Is there a custom Kernel available for this device which is 3.19 or above.?.?.
If so ...can anyone provide me the link please.?.?.
And if not...does anyone know about porting/compiling kernel for this device.?.?.
please...i need some help....
https://ibb.*co/ MCBrDtC
Click to expand...
Click to collapse
I dont' know if there's a custom kernel for this device. But you can download the source code form here https://www.nokia.com/phones/en_int/opensource to compile it and add features by yourself.
Isrks said:
I dont' know if there's a custom kernel for this device. But you can download the source code form here https://www.nokia.com/phones/en_int/opensource to compile it and add features by yourself.
Click to expand...
Click to collapse
https://ibb. co/WWFxSsb
sir there seems to be multiple files...which one should i download.?.?. I am really new to this...
and I will be very grateful if you can point to any tutorials or blog posts on how to modify kernels coz i cant seem to find any...
mechano59 said:
https://ibb. co/WWFxSsb
sir there seems to be multiple files...which one should i download.?.?. I am really new to this...
and I will be very grateful if you can point to any tutorials or blog posts on how to modify kernels coz i cant seem to find any...
Click to expand...
Click to collapse
To compile a kernel from source you can follow this tutorial.
https://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
There are more threads, this is an example.
The build number in your screenshot (5_180) tells the number of the kernel version you need to download (i want think so ), in this case is the Nokia3_V5.180.tar.bz2 file.
Isrks said:
To compile a kernel from source you can follow this tutorial.
https://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
There are more threads, this is an example.
The build number in your screenshot (5_180) tells the number of the kernel version you need to download (i want think so ), in this case is the Nokia3_V5.180.tar.bz2 file.
Click to expand...
Click to collapse
Thank you very much sir....will see if i can do anything with it...
(very sorry for the late reply... )
mechano59 said:
Thank you very much sir....will see if i can do anything with it...
(very sorry for the late reply... )
Click to expand...
Click to collapse
With having a linux environment you can build a kernel from source reading the guides. Adding features is more difficult because the main reason: this device has mediatek SoC.