Hi guys,
I can not seem to find the links to where I can checkout the latest available kernel sources.
Anyone has some gits where I can checkout the latest hero kernel sources?
Thanks in advance,
Unfortunately there are no recent Kernel sources :/ The latest version HTC released is for 1.5 but here you go man
http://member.america.htc.com/download/RomCode/Source_and_Binaries/kernel_hero_0078c992.tar.bz2
Yea I got this one. This is the 2.6.27.. I see a lot of roms using the 2.6.29 sources.
I am having issues flashing my kernel.
These do not work:
These give me a Failed, not allowd:
Code:
fastboot flash boot newBoot.img
fastboot flash zImage zImage
These give me a kernel panic or something as the phone keeps rebooting at Hero boot screen.
Code:
adb push newBoot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
flash_image boot /sdcard/newBoot.img
I have followed a lot of different guides but all are the same.
If someone could give me some pointers on how this is exactly being done please do.
Thanks in advance,
http://forum.xda-developers.com/showthread.php?t=551711
all you need is in there. try with a working kernel first, so you are sure that you rebuild the boot.img correct. then try your own kernel.
Thanks. Will try that one out.
Are you sure you're flashing a kernel appropriate for your device?
If you're using a GSM Hero, you can't flash a kernel from, for example, sprint hero.
If you compiled your kernel by hand, check if you have the proper modules enabled (check against someone else's config).
You can also try getting the running kernel's config by:
zcat /proc/config.gz > /sdcard/good_kernel_config
and load this into your kernel tree (provided the chef enabled export kernel config by config.gz)
Hi,
Yeah I did take the config out of the default htc hero. I kept it before to try other roms out
I am sure I have been using the correct 2.6.27 hero kernel to compile, I just can not find the 2.6.29 hero sources anywhere.
Anyone has a clue where I can find those?
is not released yet , only a early build of 2.6.29 is leaked...
I just checked 2.6.29 out. Compiled it correctly and testing it out now
Only problem at the moment is the wlan module is not being build correctly.
may i ask what sources you used?
goldfish sources
you do know that these are sources for the kernel for the emulator?
bet you a case of beer that you won't boot these on the hero!
kendong2 said:
you do know that these are sources for the kernel for the emulator?
bet you a case of beer that you won't boot these on the hero!
Click to expand...
Click to collapse
Ah too late with this thread. Is the bet still on?
Related
Decadenc3 as you all know has been working on some kernel stuff for us. Tonight he took my kernel source(which wasn't much past htc's) and added his patches too it. I have not flashed this one but did compile from the same source and kernel seems to be working good so I thought I would put it up for others to try out since there seemed to be some interest in his work from an earlier thread about his kernel. This kernel package is flashable through recovery.
V2
Ok I added BFS to 318 and changed default governer to ondemand. I have flashed this and am running it now.
v3
BFS to .330
update script now wipes davlik/cache automatically for you
sorry for the back to back updates there(was planning to stop after first one lol)
V4
Undervolted to try and improve battery life
V5
Gps stable with bfs now thanks to Decad3nce
Some scheduling updates
Check commits on github here.
V6
CIFS support added
BFS reverted to 318 for stability
Camera freezing bug fixed
Other things updated from .32 and .34 backports
More thanks to Decad3nce and all the other great kernel guys that i can pull commits from to put this together.
Download BFSv6 here.
2.6.29.6 BFS v4
2.6.29.6 BFS 330 Kernel for Eris
2.6.29.6 BFS 318 Kernel for Eris
Also you can check out my Froyo rom here.
My kernel source for those who want it.
Has anyone tested this
Exciting I'm doing a nandroid right now and I'll test it.
Im about to. By the way, ive sported your eris lightning roms almost since the beginning of my eris root adventures, even tho im running tazz now. Your work is awesome, thanks for everything!
Sent from my Tazz Froyo 2.0 using XDA App
You sure it's flashable from recovery?
I get
E:Wrong Digest:
meta-in/com/google/android/updater-script
e: verification failed
???
Hungry Man said:
You sure it's flashable from recovery?
I get
E:Wrong Digest:
meta-in/com/google/android/updater-script
e: verification failed
???
Click to expand...
Click to collapse
Same here.
Sent from my Tazz Froyo 2.0 using XDA App
I decided to be brave and try this also, I get the same error here too.
I'm not sure if I should try to fastboot it?
wilshyre said:
Same here.
Sent from my Tazz Froyo 2.0 using XDA App
Click to expand...
Click to collapse
maybe i broke the sig on it while uploading it...try fastbooting this one or putting it into the anykernel flashable zip if you have that...2.6.29.6 BFS
Not familiar with too many flashboot commands.. can you tell me the command I would use? I know everything else, don't need a step by step.. just a command please.
Sent from my Tazz Froyo 2.0 using XDA App
Just to clarify, the BFS version in this is only at .302
I'll push the rest of my BFS patches tonight(to .316).
The main changes in this kernel really are the patch up to 2.6.29.6, the addition of the bfq i/o sched, the addition of the interactive cpu governor, the backport of the bluetooth(from .34), and other things you can notice in the commits.
It's more of a, 'getting you guys up to date' type of thing.
I was hoping kaos would do this before he applied my BFS patch, but I'm guessing he's having compilation problems(or from what I've read); and the missing stuff(the stuff I just patched in) is probably why.
Developer Notes:
I had some trouble with the serial drivers, choosing instead to revert a few changes from the bluetooth backport so I could get a clean compile. If anyone is willing to test bluetooth capability and function, please let me know how it goes.
wilshyre said:
Not familiar with too many flashboot commands.. can you tell me the command I would use? I know everything else, don't need a step by step.. just a command please.
Sent from my Tazz Froyo 2.0 using XDA App
Click to expand...
Click to collapse
ok i resigned the first one so hopefully that will fix it...if you want to fastboot it you can just do
fastboot boot zImage (will revert to previous kernel on reboot) or
fastboot flash zimage zImage (will replace old kernel)
Conap said:
ok i resigned the first one so hopefully that will fix it...if you want to fastboot it you can just do
fastboot boot zImage (will revert to previous kernel on reboot) or
fastboot flash zimage zImage (will replace old kernel)
Click to expand...
Click to collapse
You could just use the anykernel update.zip that I provided the last time I compiled a kernel here.
It'll work with ANY rom regardless of ramdisk changes.
The only conflicts you'll see is something that was 'froyorized' in 2.1 ROMs.
Conap said:
ok i resigned the first one so hopefully that will fix it...if you want to fastboot it you can just do
fastboot boot zImage (will revert to previous kernel on reboot) or
fastboot flash zimage zImage (will replace old kernel)
Click to expand...
Click to collapse
Thanks again! If the sig verification fails again I will flash via fastboot.
Decadence.. you rock. Thanks much.
Sent from my Tazz Froyo 2.0 using XDA App
wilshyre said:
Thanks again! If the sig verification fails again I will flash via fastboot.
Decadence.. you rock. Thanks much.
Sent from my Tazz Froyo 2.0 using XDA App
Click to expand...
Click to collapse
i tested it this time and it flashed fine lol..sorry about that guys....and thanks decadenc3...
Just flashed.
lol, my Eris has been Deca Fuct
Running perfect so far! Going to do some testing and playing around. Will report back later. Btw, setcpu now has interactive governor!
Thanks again guys!
Sent from my Tazz Froyo 2.0 using XDA App
Conap said:
i tested it this time and it flashed fine lol..sorry about that guys....and thanks decadenc3...
Click to expand...
Click to collapse
You guys are awesome, thanks for all the hard work you guys put into all this, brilliant!
Wifi works.
Can't test bluetooth I have literally no devices to attempt to pair with lol
GPS works.
Interactive is on my setcpu profiles.
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.
Hello all, and befor all, sory for my poor english.
I just want to ask you for some help. I was trying to build my oun kernel for the nexus 7 (ba dum tsss) and want some information about this, since I never compile anithing for android.
I have knowledge about programming, and if I fin something I don't know, learn about it and try, like everyone I assume
I have readed a lot of guides here and there, but I can't find anything specific about how to create a custom kernel, mod voltages, frequencys, and the most important, create a recovery flashable zip.
So, if somebody can point me with some instructions on how to do it, I will be very thankful.
Thx for the help and have a nice day
Download the source and a toolchain in a Linux distro. Unpack the source, and navigate to the folder in Terminal. Type this:
Code:
export ARCH=arm
export CROSS_COMPILE=/path/to/toolchain/bin/arm-xxx-xxx (figure this part on your own)
Edit your defconfig from arch/arm/configs. Then type in
Code:
make xxx_defconfig (where xxx is the name of your defconfig)
make -j# (where # is the number of cores + 1)
This will take some time. Patiently fight out errors, and I'd recommend you start with a vanilla build.
After it's done, grab the zImage from arch/arm/boot/. Grab a flashable kernel that does not use boot.img. Delete the zImage from there and rpaste in your zImage. It should be flashable now.
Let me know if you need more help.
Thx for the info, I have some questions
How or where can I download the kernel source? (Yeah, I want to work with the google vainilla one for the stock rom)
Do you recomend the linaro toolchain or the google original one?
Sory, I work with eclipse and svn repos for years, never work with other programs or source code sistems xD
Sent from my Nexus 7 using xda app-developers app
http://source.android.com/source/building-kernels.html
This link's got much more details. Plus if it supports Linaro, go with Linaro toolchain.
Im stuck in the defconfig making part, how can i know the name of my defconfig file?
Sent from my Nexus 7 using xda app-developers app
If I rember correctly to build the kernel its
make grouper defconfig
But its been a few months since I've touched my source codes
But the defconfig is just the codename of the device your building for (aka WiFi nexus 7 is grouper gsm is tilapia)
Sent from my Nexus 7 @1.60 GHz on Stock 4.2.2
Ok, when I try to run the make grouper command, it say defconfig not found or something like that (sory, I am not om the dev ,achine right now xD).
Apart, any help about adding frequency to cpu steeps and gpu steeps (oc support for 1,7 single core, 1.6 quad and 520 gpu with 1.7 default frequency).
Yeah, I know, it's a lot of information, but I never touch linux kernel on the past, and don't know anything about it some directory info will be great xD
Sent from my Nexus 7 using xda app-developers app
All of it is found in the /arch/arm/mach-msm directory. Some files are linked so you'll have to update both. And for the defconfig, navigate to the /arch/arm/configs directory (not in Terminal) and note down the name of the defconfig you want to use. It varies with different kernel sources.
THX for all, I viewthe faux123 kernel source for reference, and found the files I need to edit to allow cpu and gpu oc, and the defconfig for nexus 7 are the tegra3_android_defconfig, strange name jaja
I am installing ubuntu x64 12.04 LTS because of compatibility things over 13.04 Thx for all the info and all the help guys
Sent from my Nexus 7 using xda app-developers app
Actually for faux kernel it's better to use faux_grouper_defconfig if you want your kernel to have features that faux-kernel has.
When I load the latest cyanogenmod nightly and flash the ktmanta 4.4 kernel upon setup I get error android phone something has stopped responding in all the other ROMs such as omni it doesn't do that.
If anyone has a solution please tell
zachdees said:
When I load the latest cyanogenmod nightly and flash the ktmanta 4.4 kernel upon setup I get error android phone something has stopped responding in all the other ROMs such as omni it doesn't do that.
If anyone has a solution please tell
Click to expand...
Click to collapse
There have been some changes in the CM ramdisk, This is mostly the cause of your issues....
Thx Josh
lj50036 said:
There have been some changes in the CM ramdisk, This is mostly the cause of your issues....
Thx Josh
Click to expand...
Click to collapse
Is there a fix ktmanta is the only kernel that has undervolting I've tried every kernel and not one except this one has undervolting I'm on omni ROM currently which sucks because when I apply voltage or clock settings they don't stick they reset to default
zachdees said:
Is there a fix ktmanta is the only kernel that has undervolting I've tried every kernel and not one except this one has undervolting I'm on omni ROM currently which sucks because when I apply voltage or clock settings they don't stick they reset to default
Click to expand...
Click to collapse
The solution would be to repack the boot.img with the updated ramdisk from CM... To get a new boot.img and flash it and see what it does..
Just a FYI
Kernel + ramdisk = boot.img
If you get me this kernel you are flashing I could make you a new boot.img...
Let me know
Thx Josh
lj50036 said:
The solution would be to repack the boot.img with the updated ramdisk from CM... To get a new boot.img and flash it and see what it does..
Just a FYI
Kernel + ramdisk = boot.img
If you get me this kernel you are flashing I could make you a new boot.img...
Let me know
Thx Josh
Click to expand...
Click to collapse
It's the latest ktmantsn4.4.2 kernel over in mantas thread
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)