Related
And what I mean, no android kitchen and those kind of tools. Simple from the start where you are forced to do all the work yourself.
(I have to much free time)
E-13 said:
And what I mean, no android kitchen and those kind of tools. Simple from the start where you are forced to do all the work yourself.
(I have to much free time)
Click to expand...
Click to collapse
Cyanogenmod is a great place to start since its stock, http://wiki.cyanogenmod.org/w/Development
Trozzul said:
Cyanogenmod is a great place to start since its stock,
Click to expand...
Click to collapse
Ah, thank you. I will look into that.
Small problem I (probarly) have. I also have a mediatek phone (main phone) and I heard there are a few problems when you want to make roms for those. It was due to lack of released source or something?
E-13 said:
Ah, thank you. I will look into that.
Small problem I (probarly) have. I also have a mediatek phone (main phone) and I heard there are a few problems when you want to make roms for those. It was due to lack of released source or something?
Click to expand...
Click to collapse
that is true, the kernel of mediatek has problems with Cyanogenmod so its a little hard. mediatek kinda sucks to develop for.
Trozzul said:
that is true, the kernel of mediatek has problems with Cyanogenmod so its a little hard. mediatek kinda sucks to develop for.
Click to expand...
Click to collapse
Wouldn'tv it be easier to start with vanille android then or modify the stock ROM bit by bit?
E-13 said:
Wouldn'tv it be easier to start with vanille android then or modify the stock ROM bit by bit?
Click to expand...
Click to collapse
always start with modifying the stock rom, every few changes you make you should check out if they work and repeat that process.
Trozzul said:
always start with modifying the stock rom, every few changes you make you should check out if they work and repeat that process.
Click to expand...
Click to collapse
Is there a way I can make my current ROM into a flash able zip?
E-13 said:
Is there a way I can make my current ROM into a flash able zip?
Click to expand...
Click to collapse
that i wouldnt know where to get information on, im sure there are tools for this, make a backup and unzip it and see what you can do from there, of course you can flash a backup but its a start.
Trozzul said:
that i wouldnt know where to get information on, im sure there are tools for this, make a backup and unzip it and see what you can do from there, of course you can flash a backup but its a start.
Click to expand...
Click to collapse
I was able to extract the boot.img,recovery.img and the META-INF map. If I am right, I didnt miss anything else thats important. Right?
E-13 said:
I was able to extract the boot.img,recovery.img and the META-INF map. If I am right, I didnt miss anything else thats important. Right?
Click to expand...
Click to collapse
Hmm I'm pretty sure there should be a few more things, go to CyanogenMod and download a random file for whatever phone and check out those files. Make sure its a stable and not nightlie
Trozzul said:
Hmm I'm pretty sure there should be a few more things, go to CyanogenMod and download a random file for whatever phone and check out those files. Make sure its a stable and not nightlie
Click to expand...
Click to collapse
I got one from the.. eh.. HTC one.
The main files (and I looked around already) are:
META-INF
system
boot.img
Thats it. And inside system there are the "standard" folders and build.prop.
I got this already tough.
-Now a small thing, this is a mediatek device, And from what I see/understood a pain in the everything to make roms for this.
I did find this about: http://sourceforge.net/projects/alcatel/files/
A huge file ;p. It seemed to be files about the kernel. The files:
boinic
external
kernel
mediatek
system
With a line I found in a readme in mediatek/kernel:
The "mediatek/kernel/" directory is intended for Mediatek solution kernel specific non-customization codes.
Anyway, back to the point. I got system, boot.img and Meta-inf
I think I got everything ready
E-13 said:
I got one from the.. eh.. HTC one.
The main files (and I looked around already) are:
META-INF
system
boot.img
Thats it. And inside system there are the "standard" folders and build.prop.
I got this already tough.
-Now a small thing, this is a mediatek device, And from what I see/understood a pain in the everything to make roms for this.
I did find this about: http://sourceforge.net/projects/alcatel/files/
A huge file ;p. It seemed to be files about the kernel. The files:
boinic
external
kernel
mediatek
system
With a line I found in a readme in mediatek/kernel:
The "mediatek/kernel/" directory is intended for Mediatek solution kernel specific non-customization codes.
Anyway, back to the point. I got system, boot.img and Meta-inf
I think I got everything ready
Click to expand...
Click to collapse
Looks like you do, I must have been thinking about something inside meta inf that let's you change all the icons
Trozzul said:
Looks like you do, I must have been thinking about something inside meta inf that let's you change all the icons
Click to expand...
Click to collapse
*cheers* But I dont really get this part. (probarly for advanced peeps) Why is it so hard to make roms for mediatek. I get they dont release the source code/code you guys need for that. But where is the code for you so badly need for that.
E-13 said:
*cheers* But I dont really get this part. (probarly for advanced peeps) Why is it so hard to make roms for mediatek. I get they dont release the source code/code you guys need for that. But where is the code for you so badly need for that.
Click to expand...
Click to collapse
I don't know whoever owns mediatek has the codes obviously. Mediatek CPUs are terrible anyway so I'm sure nobody will leak the codes
Well, not that terrible to be honest. Mine works pretty good. (am just kinda fed up with alcatel ;p) And alot of people have devices running on mediatek cpu's. Just someone needs to put real good effort into it. (and hope he doesnt get into problems for it xD)
E-13 said:
Well, not that terrible to be honest. Mine works pretty good. (am just kinda fed up with alcatel ;p) And alot of people have devices running on mediatek cpu's. Just someone needs to put real good effort into it. (and hope he doesnt get into problems for it xD)
Click to expand...
Click to collapse
Well i wish you good luck, and if you get to somehow release a rom please be sure to hit me up on it what Alcatel device do you have by the way? if you do get a new device in the future that has Cyanogenmod support what i recommend you should do is download the latest stable and just theme that all you want (im sure you know how to move apks to make them SYSTEM apps), and when you think your ready from building it from source jump right in.
Trozzul said:
Well i wish you good luck, and if you get to somehow release a rom please be sure to hit me up on it what Alcatel device do you have by the way? if you do get a new device in the future that has Cyanogenmod support what i recommend you should do is download the latest stable and just theme that all you want (im sure you know how to move apks to make them SYSTEM apps), and when you think your ready from building it from source jump right in.
Click to expand...
Click to collapse
Haha. Thank you I have a Alcatel One Touch Scribe HD. (8008D) Supported by nothing! (expect framaroot )
Now time to abuse my phone and hopefully not turn it into a paperweight.
Well, The rom is done. Added a few Apk's. Now need to look over it and get the guts to flash it
I have tried to compile TWRP 2.3.
It compiled with errors, but after solving a few errors, it was built successfully.
However, on flashing the zip via CWM, no effect took place, I am attaching my TWRP.
Anybody with knowledge and experience can help me compiling a successful build.
XDA:DevDB Information
TWRP 2.3, Tool/Utility for the Samsung Galaxy Y GT-S5360
Contributors
Nachiket.Namjoshi, DC07
Version Information
Status: Testing
Created 2014-06-08
Last Updated 2014-06-08
Downloads
DOWNLOADS
Removed
Go Here for working Builds: https://forum.xda-developers.com/galaxy-y/development/recovery-twrp-3-0-3-0-touch-recovery-t3550609
Reserved
Problems and Changelogs
Changelogs
latest update: Sun, Jun 8 ,2014.
v1.0a(alpha)
-Initial build (doesnt boot into twrp)
Problems and Errors(Intended for the ones who are willing and are able to help)
P.S you can read it but in case you dont understand what you are reading please refrain from posting questions about them in this thread.
If you are really curios, shoot me a PM or USE_THIS_LINK
Several errors (so cant paste) while compiling a otapackage (make -j4 recoveryzip)
Code:
Several mistakes in [B]bootable/recovery/updater/install.c[/B]
some [B]int[/B] not already declared,
some [B]arguments[/B] not appropriately passed in some [B]functions[/B] namely
[B]make_ext4fs(const char *filename, const char *directory,
char *mountpoint, int android, int gzip, int sparse);[/B]
and applypatch funtion...
all this is found on install.c
probably the reason why things arent built properly while [B]make recoveryzip[/B]
hence the size... 1mb
A few errors about the libs which are never compiled !
Code:
collective errors:
libopenaes.so, libblkid.so not a prelink map
These libs are never ever built !
Hence the errors.
Update01
After Solving and re-writing almost all of install.c and the update folder
got this stop
Code:
make: *** No rule to make target `out/target/product/totoro/obj/STATIC_LIBRARIES/libselinux_intermediates/libselinux.a', needed by `out/target/product/totoro/obj/EXECUTABLES/updater_intermediates/LINKED/updater'. Stop.
make: *** Waiting for unfinished jobs....
I think I should halt for today....
update02
recovery.img looks fine, however, there seems to be some problem
if I mount the img (dont ask me how to )
and calculate the size of all the files and folders,
it roughly comes upto 738 kb
but recovery.img is of 4.7 mb
Moreover, If i try
Code:
[B]make -j4 recoveryzip[/B]
there are still errors in install.c (make_ext4fs function errors)
Will try to dig into this again.
and update the thread with my findings :cyclops:
till then, if anyone can advice something, you can.
Update03
No progress yet...
Taking a rest now,
and i need a lil help in this... if anybody has ported before, plz post it here
Brief overview of things:
Getting a recovery.img of 4.7 mb but when executing
Code:
make -j4 recoveryzip
I get the recovery.zip to be 577.6 kb
however, by playing with the code, Its building the extra libs
but NOT adding them to the zip
so, need a proper updater-script
i think you must include it on a kernel., because the recovery of our sgy is not separated to the kernel.,
rio. said:
i think you must include it on a kernel., because the recovery of our sgy is not separated to the kernel.,
Click to expand...
Click to collapse
not really... I believe that if a flashable CWM can be created... a flashable TWRP can also be created...
Anyways, I was going to try dumping it into a prebuilt kernel...
but the issue is my odin doesnt work (in case of bricks)
and it can also hardbrick the device if dumped on to a kernel
Nachiket.Namjoshi said:
not really... I believe that if a flashable CWM can be created... a flashable TWRP can also be created...
Anyways, I was going to try dumping it into a prebuilt kernel...
but the issue is my odin doesnt work (in case of bricks)
and it can also hardbrick the device if dumped on to a kernel
Click to expand...
Click to collapse
oohh sorry i didn't wsee the zip. i thought you just build only img..
i checked the zip and there is no killrecovery.sh which is called by the updater-script..
rio. said:
oohh sorry i didn't wsee the zip. i thought you just build only img..
i checked the zip and there is no killrecovery.sh which is called by the updater-script..
Click to expand...
Click to collapse
oopss... im soo sorry, uploaded the wrong zip
EDIT:
Thread has been updated for the Devs and ppl who can help me.
Nachiket.Namjoshi said:
oopss... im soo sorry, uploaded the wrong zip
Click to expand...
Click to collapse
i checked your zip..
i guess you haven't used any theme.. there is no any images, fonts, twrp,ui.xml in res folder.. and i'm not sure if there are any 240x320 theme officailly available..
and you are missing 30+ libraries and some binaries in the sbin folder..
and mke2fs.conf,twrp.fstab in the /etc folder
and supersu folder
and selinux stuffs..
don't know why you are getting the install.c errors..
which branch are you using.. you need to use latest cm11 with twrp patches or omni branch to build twrp 2.7.x
for the not a prelink map error i think you need to add shared libraries or somethinh like that in prelink-linux-arm.map
anyways.. nice work. and keep trying... you can also ask for help in the official twrp thread here at xda..
psych.half said:
i checked your zip..
i guess you haven't used any theme.. there is no any images, fonts, twrp,ui.xml in res folder.. and i'm not sure if there are any 240x320 theme officailly available..
and you are missing 30+ libraries and some binaries in the sbin folder..
and mke2fs.conf,twrp.fstab in the /etc folder
and supersu folder
and selinux stuffs..
don't know why you are getting the install.c errors..
which branch are you using.. you need to use latest cm11 with twrp patches or omni branch to build twrp 2.7.x
for the not a prelink map error i think you need to add shared libraries or somethinh like that in prelink-linux-arm.map
anyways.. nice work. and keep trying... you can also ask for help in the official twrp thread here at xda..
Click to expand...
Click to collapse
Exactly... missing libs are the reasons, but there is absolutely no way of making these libs individually, well, I can try porting from other device as my last option..
and the most head-banging error is those install.c :/
I use twrp 2.7 branch (refer the link in the OP)
and Im building this with CM7 sources as it was GB
i tried to run your recovery file thru terminal but it doesn't show any action, can u pls upload your source?
i agree with @psych.half
some files are missing that must be call by recovery..
i don't know much about compiling a binary so pls update this thread on your progress. am willing to help
rio. said:
i tried to run your recovery file thru terminal but it doesn't show any action, can u pls upload your source?
i agree with @psych.half
some files are missing that must be call by recovery..
i don't know much about compiling a binary so pls update this thread on your progress. am willing to help
Click to expand...
Click to collapse
Yeh, Im currently updating github with todays changes...
I will now stop for today...
EDIT: Here, are the sources you asked for.
you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.
SpaceCaker said:
you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.
Click to expand...
Click to collapse
Yeah we got our mistake and reverted back to twrp2.3 and cm7 compatible build tools as Minus40 said.
He forgot to update the thread.
and the new twrp.zip in post #3 is twrp2.3,
stopped the work on this for today, will continue tomorrow,
Thanks for pointing it out anyways
Regards
recovery works on GT-S5367? (Galaxy Y TV)
EsromG5 said:
recovery works on GT-S5367? (Galaxy Y TV)
Click to expand...
Click to collapse
I doesn't work with original Galaxy y
Galaxy pocket devs
ı heard about galaxy pocket devs has finished twrp on pocket this can help you
Pocket has also new camera lib for cm9
Only proplem is Audio (On MadTeam)
SpaceCaker said:
you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.
Click to expand...
Click to collapse
Updated thread, sorry, was in a hurry yesterday, forgot to update it just like post #13 by @DC07 says...
Sorry,
So, I can smell the victory though
Good News
I am getting a recovery.zip of a larger size, and finally, the build tools are working great and building the missing libs too...
thanks anyway @Minus40 for giving me the libs, but those libs are not gonna work on this device, its a bit complicated architecture...
Anyway, this is a good break through, ill update the github by the end of the day.
I hope to have a working TWRP by the weekend
presently, build tools error is that it doesnt dump proper permissions for the extra libs, will try give them the proper permissions (which i dont really know, which perms to give), a few days more and it'll be done.
Nachiket.Namjoshi said:
I am getting a recovery.zip of a larger size, and finally, the build tools are working great and building the missing libs too...
thanks anyway @Minus40 for giving me the libs, but those libs are not gonna work on this device, its a bit complicated architecture...
Anyway, this is a good break through, ill update the github by the end of the day.
I hope to have a working TWRP by the weekend
presently, build tools error is that it doesnt dump proper permissions for the extra libs, will try give them the proper permissions (which i dont really know, which perms to give), a few days more and it'll be done.
Click to expand...
Click to collapse
Try twrp 2.2.2.0 for cm7.
Hi, I'm new in XDA so sorry if i do some error. Also sorry for my bad english.
I'm trying to port lolliop to our device with this guide but I'm encourted in two errors: First the recovery [TWRP] declare failed the flash and the other is the bootloop. Can anyone help me?
I atached the logcat and the updater-script.
android1111 said:
Hi, I'm new in XDA so sorry if i do some error. Also sorry for my bad english.
I'm trying to port lolliop to our device with this guide but I'm encourted in two errors: First the recovery [TWRP] declare failed the flash and the other is the bootloop. Can anyone help me?
I atached the logcat and the updater-script.
Click to expand...
Click to collapse
You have to build it using Ubuntu.
Its a pretty hard task so I recommend you avoiding it unless you want to become a developer.
Search tutorials about how to use ubuntu and build a ROM from scratch. Read Cyanogenmod's tutorial as well
What ROM are you porting from?
Liam D. said:
What ROM are you porting from?
Click to expand...
Click to collapse
I'm porting from the lollipop xperia u rom, the similest device that has received lollipop.
If you're talking about Xperia STOCK ROM, you would have better luck building the ROM from scratch instead of porting. Stock ROMs contain Sony-specific configurations, whereas our device needs a Samsung device tree.
I suggest looking at the GitHub profile of SpeedGroup or my GitHub profile for a working CyanogenMod 11 device tree, which can be used as a starting point to start work on Lollipop.
Keep in mind though, that Android L runs ART and has Dalvik completely removed, so unless you're willing to let most of your phone storage go for ART, we better stick with KitKat. ART uses more space, as it pre-compiles application data. While it is a ton faster, it also consumes twice, or maybe thrice the amount of data Dalvik uses.
Liam D. said:
If you're talking about Xperia STOCK ROM, you would have better luck building the ROM from scratch instead of porting. Stock ROMs contain Sony-specific configurations, whereas our device needs a Samsung device tree.
I suggest looking at the GitHub profile of SpeedGroup or my GitHub profile for a working CyanogenMod 11 device tree, which can be used as a starting point to start work on Lollipop.
Keep in mind though, that Android L runs ART and has Dalvik completely removed, so unless you're willing to let most of your phone storage go for ART, we better stick with KitKat. ART uses more space, as it pre-compiles application data. While it is a ton faster, it also consumes twice, or maybe thrice the amount of data Dalvik uses.
Click to expand...
Click to collapse
I wasn't porting from the stock rom but from this project, but thanks anyway, I think so I'll listen to your advice.:good:
Can anyone also tell me what part i need to create a rom?
Sorry I just noticed this now.
To create a ROM, you need these 3:
The kernel (android_kernel_msm7x27a or android_kernel_trebon [depending on the source])
The device tree (android_device_msm7x27a-common AND android_device_s7500)
The proprietary files from Samsung (proprietary_vendor_samsung_msm7x27a)
For references, see the local manifests I put up on GitHub: https://github.com/xenLiam/android_local_manifest_trebon
Download these as a zip and place this inside .repo/local_manifests (create a folder named local_manifests inside the .repo folder of your source directory first).
Welcome
I have started this thread for the THEORETICAL development of the mt6732/mt6752 from source if such a thing happened to exist which of course it does not.
While compiling from source is pretty well documented :good: compiling MTK is not so well documented especially the mt6732/6752.
I have tried to keep this thread as ambiguous as possible and hopefully we will be left in peace to iron out any difficulties.
DO's:
I am a Total Noob myself to compiling from source but experienced enough to use the xda search box, Google and Youtube first before asking any questions. If your still confused after using the above then by all means ask here.
DON'T s:
If your a noob who should happen upon this thread then by all means read and learn but please respect the dev's by not asking random question without searching first :fingers-crossed:
SHARING:
Please only share things of a sensitive nature with recognised members who you know and via the PM. :good:
Lets just see how far we can push this Kernel
Recommended Reading:
[GUIDE]Building a Kernel from source{Mediatek}
Build Kernel MT6577 - Can't boot after build
How To Port CyanogenMod Android To Your Own Device
XDA:DevDB Information
k01q_e k01q_h, Kernel for all devices (see above for details)
Contributors
bigrammy
Kernel Special Features: Remains to be seen
Version Information
Status: Testing
Created 2015-02-25
Last Updated 2015-02-25
I am here, reporting for duty. If anyone wants an extra "potato" because he has too much "ketchup" for use feel free to ask me
Just to be clear
I am new to compiling from source in any shape or form
I believe the kernel to be not a problem and I know dev's are working on getting our phone on cm and maybe others :fingers-crossed:
But me being me I am very curious and would like to understand how we would go about doing what @varun.chitre15 managed to do for the mt6582 Here
I have the PC all setup for building now thanks to @carliv great guide Here and the cm and android tut's I also found this useful guide on youtube by Dave Bennet Here
Our device is not on the cm or google repo so how do we add it locally.
Do we need any special commands for mediatek
Could we use the mt6582 repo and substitute or mod the files
As you can see I have more questions than answers as normal :laugh:
I dont want to tread on any toes here or take over current developing but just want to learn as said in the OP there is a lack of mtk guides regarding this.
If I missed a clear mtk guide then please post the link to it. :good:
In short your looking at manifests. http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
carliv (I think) posted the device config on github - link in your SPFlash thread somewhere.
Found it: https://github.com/carliv/device_elephone_p6000?files=1
Vendor files
I have compiled and flashed a kernel, I've been running it for 24+ hours with no obvious issues. It's honestly very easy to just get it to build if you don't try to make major changes.
I have (very lazily) tried to change a couple of things in the config to fix the known issues (OTG, compass): unfortunately I have no way to test the OTG function right now, while the compass did not magically start working. On the other hand, the notification light issue which is introduced by V8.4 is not strictly or exclusively kernel-dependent, since I am running V8.3 with my own kernel and the notification function is intact. That's all I can share at the moment.
xenonism said:
I have compiled and flashed a kernel, I've been running it for 24+ hours with no obvious issues. It's honestly very easy to just get it to build if you don't try to make major changes.
I have (very lazily) tried to change a couple of things in the config to fix the known issues (OTG, compass): unfortunately I have no way to test the OTG function right now, while the compass did not magically start working. On the other hand, the notification light issue which is introduced by V8.4 is not strictly or exclusively kernel-dependent, since I am running V8.3 with my own kernel and the notification function is intact. That's all I can share at the moment.
Click to expand...
Click to collapse
Can you switch on and post the /proc/config ?
Regarding the notification lights, I think v8.4 introduced the custom partition (might be wrong on that). Running grep -r "ro.notification.breath" /system/ the only result I got was services.odex (might have been settings.odex). I've bak(smali)ed it but couldn't see the difference between the two that would explain the change.
HypoTurtle said:
Can you switch on and post the /proc/config ?
Regarding the notification lights, I think v8.4 introduced the custom partition (might be wrong on that). Running grep -r "ro.notification.breath" /system/ the only result I got was services.odex (might have been settings.odex). I've bak(smali)ed it but couldn't see the difference between the two that would explain the change.
Click to expand...
Click to collapse
The config file is attached to the post, it's too big to paste it.
I have tried the new ROM which came out today, then flashed my kernel. I can't use either SIM card anymore. Flashed the boot.img that comes with the ROM - same. I guess I gotta go back to V8.3 for now.
The new ROM doesn't seem to be the same as the OTA: it reports as: Elephone_P6000_02_V8.0_20150206.
About the notification issues (which bothers me the most), I haven't had much time do to more experiments, but I was thinking this (which probably also led to my confusion*): there's a chance the functionality is not removed or shut down, at least in the intentions of the maker. After all, in V8.4 (and in the new ROM), when the phone is connected the light stays on, while notifications make it breath. While not a desirable behaviour (at least IMO), I wouldn't call it... a non-behaviour, so to say. So perhaps the functionality itself is intact but something is altering the way it works, for whatever reason. I also did some unpacking and grepping a few days ago, but I couldn't find anything useful.
* At some point I thought the issue was fixed because the light was breathing while connected to my PC, but it was probably because I had a notification to read.
xenonism said:
The config file is attached to the post, it's to big to paste it.
I have tried the new ROM which came out today, then flashed my kernel. I can't use either SIM card anymore. Flashed the boot.img that comes with the ROM - same. I guess I gotta go back to V8.3 for now.
The new ROM doesn't seem to be the same as the OTA: it reports as: Elephone_P6000_02_V8.0_20150206.
Click to expand...
Click to collapse
Lets not speculate too much - but perhaps there was a minor board change between the first and second preorders, notification could be a problem with granting notification access (in settings) - could this be a selinux issue? It would explain why things like Light manager work - as you grant them notification access.
For lost Imei - can you compare the custom partition to the one in the ota?
If anyone needs an easier way to grab the 'ketchup', my GitHub has it. Click on my blog link in my signature.
BachMinuetInG said:
If anyone needs an easier way to grab the 'ketchup', my GitHub has it. Click on my blog link in my signature.
Click to expand...
Click to collapse
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:
bigrammy said:
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:
Click to expand...
Click to collapse
I'm actually a noob too, and honestly I've only ever successfully built a fakeflash (temporary recovery) that didn't even work.
bigrammy said:
Thanks bro,
Nice log
I was going to try use the sprout config as this is nice and clean Here when I have worked out how to do things that is.
My eyeballs are bleeding now with all this reading but from what I can see most of files are the same names so maybe we could just replace them with ours probably 98% ish
I did see one ROM some place for the mt6732/52 that had mt6582 references I just wish I could remember where I had seen it
Like I say I am a noob to this compiling and linux stuff so I maybe talking out of my ass :laugh:
Click to expand...
Click to collapse
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
I think you can use the scripts in the root of the source code to build the kernel? make<something>.sh.
Make sure you're on Linux (Ubuntu preferred) and that you have all dependencies installed correctly. To execute the script, simply go to the Terminal, cd to the location, then type . make<something>.sh
Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
Have a look at the README.
Does make menuconfig work here?
These few simple instructions from the readme file enable you to build a working kernel (at least in a Linux environment):
Code:
How to Build
kernel
======
1. Get the prebuilt cross compiler from AOSP website:
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
2. Add required cross compiler to PATH:
$ export PATH=/YOUR_TOOLCHAIN_PATH/arm-eabi-4.6/bin:$PATH
$ export CROSS_COMPILE=arm-eabi-
3. Then use the following commands to build the kernel:
$ ./makeMtk k01q_e new k
make menuconfig can be made to work, but you need to set some parameters and I can't look into it right now.
You previously asked something about the custom partition, I need some guidance there as I am not familiar with the IMEI issue.
xenonism said:
These few simple instructions from the readme file enable you to build a working kernel (at least in a Linux environment):
Code:
How to Build
kernel
======
1. Get the prebuilt cross compiler from AOSP website:
$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
2. Add required cross compiler to PATH:
$ export PATH=/YOUR_TOOLCHAIN_PATH/arm-eabi-4.6/bin:$PATH
$ export CROSS_COMPILE=arm-eabi-
3. Then use the following commands to build the kernel:
$ ./makeMtk k01q_e new k
make menuconfig can be made to work, but you need to set some parameters and I can't look into it right now.
You previously asked something about the custom partition, I need some guidance there as I am not familiar with the IMEI issue.
Click to expand...
Click to collapse
Yea wasn't sure about menuconfig as mtk uses projectconfig rather than def_configs.
In the custom partition there are files like /custom/etc/firmware/modem.img etc. When messing with a Flyme port it was these files (and possible conflicts in /system) that caused an IMEI:nul.
FYI I opened the custom partitions on windows using an ext viewer after running the imgs through sgs2toext4.
Kernel building Mediatek
Tech N You said:
Can anyone actually make a guide noob friendly to build kernel from source? I got kernel with me locally zip file I want to build it please any help?
Click to expand...
Click to collapse
Not sure if you guys have seen or read this but it's a pretty comprehensive guide to building the mediatek kernel by @MasterAwesome and should really be compulsary for all kernel related things thread here http://forum.xda-developers.com/showthread.php?t=2754513
@HypoTurtle
Regarding the custom partition this is or could be a problem for us now and in the future and may require further investigation. The cm sprout branch has the modem.img in the (normal place /system/etc/firmware) but as you say ours is in the custom partition which is probably to protect it from bad /system flashes
Thing is I see no normal type link to it in the /system/etc/firmware so it must be linked some other way which may explain why all my port attempts failed as none of them used a custom partition (Asus_X002)
Maybe we will have to repartition the emmc to a standard config and alter the kernel (if the links are set via the kernel that is) for cm and other ports to work smoothly as I am unsure just how everything is linked up.
I have not had much experience with custom partitions so someone one know's of a good info source please link it. :good:
Hopefully Master @Santhosh M can figure out what's going on with the custom partition :fingers-crossed:
bigrammy said:
@HypoTurtle
Regarding the custom partition this is or could be a problem for us now and in the future and may require further investigation. The cm sprout branch has the modem.img in the (normal place /system/etc/firmware) but as you say ours is in the custom partition which is probably to protect it from bad /system flashes
Thing is I see no normal type link to it in the /system/etc/firmware so it must be linked some other way which may explain why all my port attempts failed as none of them used a custom partition (Asus_X002)
Click to expand...
Click to collapse
The partition is symlinked from .../by-name/custom (which is symlinked by the kernel from dev/block/mmcblk0p12) to /dev/customimg which is mouned after an e2fsck to /custom. /custom isn't linked to /system, it's just added to the global environment (init.environ.rc), will need to check on the environ, I'm on flyme and it has /custom/lib added to the library path (which doesn't exist).
HypoTurtle said:
The partition is symlinked from .../by-name/custom (which is symlinked by the kernel from dev/block/mmcblk0p12) to /dev/customimg which is mouned after an e2fsck to /custom. /custom isn't linked to /system, it's just added to the global environment (init.environ.rc), will need to check on the environ, I'm on flyme and it has /custom/lib added to the library path (which doesn't exist).
Click to expand...
Click to collapse
Haha thanks that explains a lot of weird things perfectly. :good:
What's the problem or what is the issue here.
Mediatek compiling guide ( by masterawesome ) that you have linked to is not actually practically this mtk kernel is done and is just way too complicatedly explained.
There is no defconfig stuff or pulling config.gz from phone in mtk. In this new source its just simple. Set up your toolchain path. Execute the makeMtk followed by the project no u want. Get zImage and patch it for mtk header and merge it with stock ramdisk. For this newer mtk chipsets repack has an extra stuff where u have to be careful of kernel command line parameters.
That's it the kernel stuff in mtk
I will take NO RESPONSABILITY for any damage on any device, so be really cautious about what you do with the recovery.
Here we are again!
In my last post i explained how to get in Fastboot mode, now here we are again to take advantage of that situation, and open the device to further development.
First of all, on my github ( https://github.com/Algesat/BladeApex2 ), you can download the sources, the build files and the compiled files, so not only developers with a certain level of knowledge can "play" with this files (remember to do a make distclean before recompiling it if you dont use the correct toolchain ( https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7 ), or you modify something on the sources.
In other hand, ill bring you a full version of the TWRP Recovery, (made by Dees_Troy and me).
https://dl.twrp.me/P892E10/
In Dees_Troy's github you can download the sources if you wanna compile it yourself:
https://github.com/Dees-Troy/android_device_zte_P892E10
Yours.
Algesat.
P.S: Thanks to Dees_Troy for his great help
Good job bro, finally someone works on it
I think its time to ask for a forum for this device, i suppose now the development on this device will be boosted and roms will appear.
Thanks.
Algesat
Algesat said:
I think its time to ask for a forum for this device, i suppose now the development on this device will be boosted and roms will appear.
Thanks.
Algesat
Click to expand...
Click to collapse
Yep, you right! :fingers-crossed: