https://www.nokia.com/phones/en_int/opensource
Ok so I found this link and im thinking it is the kernel source. i went through the file and found a folder called "kernel" does this mean we could develop a custom kernel with this source?
nintendobuster420 said:
https://www.nokia.com/phones/en_int/opensource
Ok so I found this link and im thinking it is the kernel source. i went through the file and found a folder called "kernel" does this mean we could develop a custom kernel with this source?
Click to expand...
Click to collapse
yeah, you could pretty much build a custom kernel using the source. keep in mind that you need the ramdisk of stock kernel with the same version to make it work (else it would pretty much not boot)
Related
It seems as if a lot of the reason people are hesitant to switch to froyo is the lack of custom kernels. custom kernels provide much better battery life as well as the ability to overclock as well as many other very useful features that create faster and more efficient operating system functions. From personal experience with froyo roms i have noticed the system to be quite slow compared to 2.1 and also i have noticed absolutely horrid battery life. We all know that these leaks may be far from complete but thats not to say that we shouldnt be making them better. It is obvious that Firon and noobnl have the correct information on this matter seeing as they have rooted all of the froyo releases inside of the zImage. If they were kind enough to share the information they have it would be very easy to either port our drivers to a i9000 froyo source or to use backported eclair libraries and use our current kernels. With this being said, I am very sure that this information could be the dealbreaker for froyo roms. With a good kernel comes a good functioning phone.
TO FIRON OR NOOBNL:
Please share your method of extracting the initramfs in order to quickly advance the development of froyo roms and to prolong the necessity for an updated source code
https://github.com/atinm/initramfs-utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
bubby323 said:
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
Click to expand...
Click to collapse
THANKS A lot man
You have tested this on froyo kernels? And technically if we used a correct froyo initramfs combined with a 2.6.29 kernel with backported eclair libraries for certain hard/software aspects we should be able to acheive an eclair kernel on a froyo rom. Ive done it before on other phones
the jump from .29 to .32 is a massive one, but all the power to ya...
shabbypenguin said:
the jump from .29 to .32 is a massive one, but all the power to ya...
Click to expand...
Click to collapse
Ive done it on evos/nexus' and i can confirm that its been done on galaxy s phones. it may be a massive jump in version number and overall base code. but as far as android and our devices go it really hasnt changed too much. actually i can almost guarantee that it will boot just by swapping the kernel inside the zimage. but to get camera and other functions requiring updated drivers we would need older libraries. or we can just patch our board specific files onto a i9000 kernel. but hey. doubting is more fun than doing
bubby323 said:
https://github.com/atinm/initramfs- utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
Click to expand...
Click to collapse
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
help
EnVolved said:
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
Click to expand...
Click to collapse
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
If you want better battery life editing the initram isn't going to do it.Your gonna need kernel source to play with to be able to do anything about battery life.
justlovejoy said:
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
Click to expand...
Click to collapse
There should be only one way to use that script to extract.
./extract_initramfs.sh zImage
and here's the header from the repack script.
usage : ./repack.sh [kernel] [initramfs_direcotry] [kernel source dir] "title of build"
example : ./repack.sh /data/android/initramfs-utils/zImage /data/android/captivate-initramfs /data/android/linux-2.6.32 "title of build"
These are fairly simple shell scripts that only appear complicated because of the use of grep.
Currently I am using a 2.2.1 rom and which the kernel does not support rndis for wired tether. I looked around and found a thread that has patch to enable it for the DI28 system. It is a zimage file 4.3 mb, there is also a zimage in the rom of 5.5 mb (located in /kernel/update/) Would it be possible to replace the 5.5 with the 4.3? Or would there be a problem because the smaller file was from a DI28 vs a DK28
warlar12 said:
Or would there be a problem because the smaller file was from a DI28 vs a DK28
Click to expand...
Click to collapse
I am going to make the assumption that you mean DI18 instead of DI28, which is a 2.1 Eclair kernel, unlike the DK28 which is a 2.2 Froyo kernel. If your currently running a Froyo rom, then you cant use an Eclair kernel. You more than likely going to have to wait til the source code is released for Froyo before it will be available, or you can Odin back to DI18 and use a custom kernel.
Koadic said:
I am going to make the assumption that you mean DI18 instead of DI28, which is a 2.1 Eclair kernel, unlike the DK28 which is a 2.2 Froyo kernel. If your currently running a Froyo rom, then you cant use an Eclair kernel. You more than likely going to have to wait til the source code is released for Froyo before it will be available, or you can Odin back to DI18 and use a custom kernel.
Click to expand...
Click to collapse
Lol yeah I meant the DI18.
I just looked up zimage and found out that it is the kernel...damn it...time to figure out how to modify it
warlar12 said:
Lol yeah I meant the DI18.
I just looked up zimage and found out that it is the kernel...damn it...time to figure out how to modify it
Click to expand...
Click to collapse
I think the only modifiable part of the z image is the init, could be wrong...please prove me wrong so we can have over clock
Sent from my SPH-D700 using XDA App
Kcarpenter said:
I think the only modifiable part of the z image is the init, could be wrong...please prove me wrong so we can have over clock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ive been staring at my computer screen and getting more and more confused...I can not find a program or a way to decompress the file. But apparently it is compressed by a zip program. And on the phone it decompresses it once you flash the rom. Other then that I have decided to call it a night on trying to find a way, (I am sure there is a way.) It is giving me a major headache lol.
The main problem so far is that the source has not been released. However I think it has in a way because it is on the rom, which means there is a way to get it off and mess with it. Just hasnt been discovered yet.
Its packaged by cpio I believe... Ill find something on it tomorrow for you...theres a dev thread that talks about it somewhere...but its probably not for the weak of heart or someone without a bit of kernel knowledge. Not sure how vast your skill set is.
Sent from my SPH-D700 using XDA App
warlar12 said:
Currently I am using a 2.2.1 rom and which the kernel does not support rndis for wired tether.
Click to expand...
Click to collapse
I haven't tried any of the Froyo leaks so I can't comment on whether the Froyo kernel has RNDIS support out-of-the-box or not. Once the Epic Froyo kernel sources are released I'll patch in proper RNDIS support if necessary.
Meanwhile, if it's the case that RNDIS can't be enabled in the stock Froyo kernel, then I'm afraid that nothing can be done to fix that without the kernel source code.
I essentially want to get into the kernel to first start seeing what each file does then making smal tweaks to see the outcomes. So once I get some more knowledge I'll be able to compile my own.
Sent from my SPH-D700 using XDA App
warlar12 said:
I essentially want to get into the kernel to first start seeing what each file does then making smal tweaks to see the outcomes.
Click to expand...
Click to collapse
The kernel isn't comprised of files but linked executable code (except the initramfs image, but that's not actually the part of the kernel, it's just included inside it).
warlar12 said:
So once I get some more knowledge I'll be able to compile my own.
Click to expand...
Click to collapse
A kernel can't be compiled without the source code, that's what we're all waiting for.
mkasick said:
The kernel isn't comprised of files but linked executable code (except the initramfs image, but that's not actually the part of the kernel, it's just included inside it).
A kernel can't be compiled without the source code, that's what we're all waiting for.
Click to expand...
Click to collapse
Ahh so really there is not a way to change it besides building a new one from source
http://forum.cyanogenmod.com/forum-462/announcement-23-cyanogenmod-72-rc1-released/
look there
FINALY! Something. I thought that they gave up!
Everyday i was checking for an update! FINALlyyy! Something.
EDIT!!!!
No 7.2 RC1 Download link. -.- Cant download cm7.2 rc1 for Shakira ( X8 ) FUUUU!! TROLLS.
Edit for Nikola -.- That is an ANNOUCMENT! Its not for Xperia x8
spevky said:
finaly! Something. I thought that they gave up! :d
everyday i was checking for an update! Finallyyy! Something.
Edit!!!!
No 7.2 rc1 download link. -.- cant download cm7.2 rc1 for shakira ( x8 ) fuuuu!! Trolls.
Click to expand...
Click to collapse
they are so big trolls
1+
NINJA EDIT i cant read AGAIN!
Cmon,no 7.2 for us!?shizz!!!
Sent from my E15i using Tapatalk
Hello.
Yesterday I tried to compile MiniCM from source, but I did not succeed.
However I compiled a vanilla Cyanogenmod from source (Github), so if someone here is brave and knows what they are doing they can try it. I use a kernel based on Alfsamsungs sources, and CM boots up and works here.
(no wifi cause my custom kernel, had to overwrite with my own modules to get it working)
I have not tested it much but I think MiniCM is a better choice.
NB: No need to post question or bugs, Im not a developer, I only compiled it.
Downloads:
cyanogen_shakira-ota-eng-24-April
gapps-gb-20110828-signed
All in one ICS layout v10-patch
All in one ICS layout v10-undo
prot_x said:
Hello.
Yesterday I tried to compile MiniCM from source, but I did not succeed.
However I compiled a vanilla Cyanogenmod from source (Github), so if someone here is brave and knows what they are doing they can try it. I use a kernel based on Alfsamsungs sources, and CM boots up and works here.
(no wifi cause my custom kernel, had to overwrite with my own modules to get it working)
I have not tested it much but I think MiniCM is a better choice.
NB: No need to post question or bugs, Im not a developer, I only compiled it.
Downloads:
cyanogen_shakira-ota-eng-24-April
gapps-gb-20110828-signed
All in one ICS layout v10-patch
All in one ICS layout v10-undo
Click to expand...
Click to collapse
You can become a dev,just try
Sent from my E15i using Tapatalk 2 Beta-5
prot_x said:
Hello.
Yesterday I tried to compile MiniCM from source, but I did not succeed.
However I compiled a vanilla Cyanogenmod from source (Github), so if someone here is brave and knows what they are doing they can try it. I use a kernel based on Alfsamsungs sources, and CM boots up and works here.
(no wifi cause my custom kernel, had to overwrite with my own modules to get it working)
I have not tested it much but I think MiniCM is a better choice.
NB: No need to post question or bugs, Im not a developer, I only compiled it.
Downloads:
cyanogen_shakira-ota-eng-24-April
gapps-gb-20110828-signed
All in one ICS layout v10-patch
All in one ICS layout v10-undo
Click to expand...
Click to collapse
i'll take a shot at it
prot_x said:
Hello.
Yesterday I tried to compile MiniCM from source, but I did not succeed.
However I compiled a vanilla Cyanogenmod from source (Github), so if someone here is brave and knows what they are doing they can try it. I use a kernel based on Alfsamsungs sources, and CM boots up and works here.
(no wifi cause my custom kernel, had to overwrite with my own modules to get it working)
I have not tested it much but I think MiniCM is a better choice.
NB: No need to post question or bugs, Im not a developer, I only compiled it.
Downloads:
cyanogen_shakira-ota-eng-24-April
gapps-gb-20110828-signed
All in one ICS layout v10-patch
All in one ICS layout v10-undo
Click to expand...
Click to collapse
Yess,there is still hope
sent from my x8
prot_x said:
Hello.
Yesterday I tried to compile MiniCM from source, but I did not succeed.
However I compiled a vanilla Cyanogenmod from source (Github), so if someone here is brave and knows what they are doing they can try it. I use a kernel based on Alfsamsungs sources, and CM boots up and works here.
(no wifi cause my custom kernel, had to overwrite with my own modules to get it working)
I have not tested it much but I think MiniCM is a better choice.
NB: No need to post question or bugs, Im not a developer, I only compiled it.
Downloads:
cyanogen_shakira-ota-eng-24-April
gapps-gb-20110828-signed
All in one ICS layout v10-patch
All in one ICS layout v10-undo
Click to expand...
Click to collapse
What did u use to compile it ? Linux mint or ubuntu ? And did you try with nAa11 instead of your own compiled kernel ??
RohinZaraki said:
What did u use to compile it ? Linux mint or ubuntu ? And did you try with nAa11 instead of your own compiled kernel ??
Click to expand...
Click to collapse
I used Ubuntu 10.04, no did not try with other kernels. But the CM is not for alfs kernel (it has an kernel.sin inside the zip file), so my guess is that it also works with other kernels, like nAn11.
prot_x said:
I used Ubuntu 10.04, no did not try with other kernels. But the CM is not for alfs kernel (it has an kernel.sin inside the zip file), so my guess is that it also works with other kernels, like nAn11.
Click to expand...
Click to collapse
I downloaded your compilation...wanna see if i can fix it up here and there...may be fun...if i do succeed, i'll pm you
Sent from my X8 using Tapatalk
Hi
I change the kernel according to cpu, audio chip spec.
I put the file in the following link.
http://forum.xda-developers.com/showthread.php?t=1834384
I only understand railway station...
eugene690922 said:
Hi
I change the kernel according to cpu, audio chip spec.
I put the file in the following link.
http://forum.xda-developers.com/showthread.php?t=1834384
Click to expand...
Click to collapse
You aren't a native english speaker, am i right? Your post is really hard to understand...
Yeah, you changed your kernel
kernel for what rom?
Have you build that kernel yourself?
What are the advantages of using this kernel?
Cheers
EDIT: Oh... i see, CM9! My Fault
But i think, no one will use your kernel unless you describe what changes were made. Also you don't give the information on which kernel your one is based of. Is it Pawitp's Stock one for CM9 - or have you modified a Devil or Semaphore Kernel?
i want to port a rom that has boot.img from galaxy mini ... each time i try it gives me bootloop ... what should i do?
try logcating it
and if it has a boot.img just delete it - thats that kernel file for another phone
marcussmith2626 said:
try logcating it
and if it has a boot.img just delete it - thats that kernel file for another phone
Click to expand...
Click to collapse
so ... its a cm7 based i can flash it over the bieltv.3's kernel ?
Omar El- Hussien said:
so ... its a cm7 based i can flash it over the bieltv.3's kernel ?
Click to expand...
Click to collapse
you need to be on an ext file system and use a cm compatible kernel
if your base rom is bieltv cm7 then you would need to use his kernel
there are plenty of guides out there that tell you how to port a rom
Delete the boot.img file no need for it..
If using Biel cm7 as base flash specific kernel
If using Percy cm7 flash CM#2 kernel.
Sent from my GT-S5360 using Tapatalk 2
marcussmith2626 said:
you need to be on an ext file system and use a cm compatible kernel
if your base rom is bieltv cm7 then you would need to use his kernel
there are plenty of guides out there that tell you how to port a rom
Click to expand...
Click to collapse
yes but i searched and i didn't find any which tells about the boot.img
mohamedrashad said:
Delete the boot.img file no need for it..
If using Biel cm7 as base flash specific kernel
If using Percy cm7 flash CM#2 kernel.
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
the have bugs ... i didnt use any of them as base xD
the guide also said that if your base rom has bugs like camera so your port will have it
Omar El- Hussien said:
yes but i searched and i didn't find any which tells about the boot.img
Click to expand...
Click to collapse
like I said boot.img is the kernel
you dont want to flash another phones kernel on your phone so you just delete it or replace it with one from your phone buts its probably better to just delete it and leave the rom kernel free as unless you have permission and the kernel source you cant post it and most people like to choose what kernel they use
you can remove the line for boot.img from the updater script if you want to
when porting a rom you are just looking at the system folder and then if there is anything extra in the updater script you can look at that
marcussmith2626 said:
like I said boot.img is the kernel
you dont want to flash another phones kernel on your phone so you just delete it or replace it with one from your phone buts its probably better to just delete it and leave the rom kernel free as unless you have permission and the kernel source you cant post it and most people like to choose what kernel they use
you can remove the line for boot.img from the updater script if you want to
when porting a rom you are just looking at the system folder and then if there is anything extra in the updater script you can look at that
Click to expand...
Click to collapse
thanks man you are really very helpful