Hi, I managed to build a kernel from Samsung's sources, but it doesn't work (boot loop). It also seems to be much smaller than the official builds (4.6 MB vs 8 MB). Here's exactly what I did, I wonder if someone could tell me where I'm going wrong:
1. Download & extract the kernel sources from here : https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=I9100
2. Download and install the old code sourcery GCC as recommended in Samsung's readme from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release298
3. Move the code sourcery install to /opt/toolchains/arm-2009q3
4. Edit kernel/Makefile and change CROSS_COMPILE to
CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-eabi-
(it was arm-linux-gnueabi- I think).
5. In kernel, make c1_rev02_defconfig && make
6. It worked, and I got a zImage. I flashed it using heimdall like this:
heimdall flash --kernel zImage
(That worked when I went back to stock so it is obviously correct, but using my kernel I get a reboot loop.)
Anyone have any idea what's so different with my build compared to Samsung's that results in it not working, and being so much smaller?
Timmmmmm said:
Hi, I managed to build a kernel from Samsung's sources, but it doesn't work (boot loop). It also seems to be much smaller than the official builds (4.6 MB vs 8 MB). Here's exactly what I did, I wonder if someone could tell me where I'm going wrong:
1. Download & extract the kernel sources from here : https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=I9100
2. Download and install the old code sourcery GCC as recommended in Samsung's readme from here: http://www.codesourcery.com/sgpp/lite/arm/portal/release298
3. Move the code sourcery install to /opt/toolchains/arm-2009q3
4. Edit kernel/Makefile and change CROSS_COMPILE to
CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-eabi-
(it was arm-linux-gnueabi- I think).
5. In kernel, make c1_rev02_defconfig && make
6. It worked, and I got a zImage. I flashed it using heimdall like this:
heimdall flash --kernel zImage
(That worked when I went back to stock so it is obviously correct, but using my kernel I get a reboot loop.)
Anyone have any idea what's so different with my build compared to Samsung's that results in it not working, and being so much smaller?
Click to expand...
Click to collapse
you will be missing the initramfs. See supercurio's threads for compile scripts and info
You are using the wrong toolchain too!
http://www.codesourcery.com/sgpp/lite/arm/portal/release1039
also, check out this thread
http://forum.xda-developers.com/showthread.php?t=1123643
Hmm but the readme says "Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI." not ARM GNU/linux.... Is that just wrong? And what exactly is the difference?
(I actually did get the 2009 version, not the 2006 one I linked to.)
Thanks for the supercurio hint; very useful. I wish this stuff was in the wiki rather than in random forum threads though. Forums don't make for a good reference or learning format.
Timmmmmm said:
Hmm but the readme says "Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI." not ARM GNU/linux.... Is that just wrong? And what exactly is the difference?
(I actually did get the 2009 version, not the 2006 one I linked to.)
Thanks for the supercurio hint; very useful. I wish this stuff was in the wiki rather than in random forum threads though. Forums don't make for a good reference or learning format.
Click to expand...
Click to collapse
Well, based on what is in the make file you should use the one I linked
CROSS_COMPILE ?= /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-
I just compiled modules not whole kernel but the linux-gnu toolchain was the one which compiled a usable result and not the one that is in readme. That is sure.
richyy74 said:
I just compiled modules not whole kernel but the linux-gnu toolchain was the one which compiled a usable result and not the one that is in readme. That is sure.
Click to expand...
Click to collapse
Figured that would happen, I am trying the recommended one right now to see if it works, guessing I will have the same outcome.
edit: boots up just fine actually...
so, what is the right one ?!
Maybe both work? I dunno, anyway the linux one worked for me, and the kernel is over a MB smaller than the samsung one... weird.
Timmmmmm said:
Maybe both work? I dunno, anyway the linux one worked for me, and the kernel is over a MB smaller than the samsung one... weird.
Click to expand...
Click to collapse
Samsung only uses gzip, guessing you enabled LZMA.
I wouldn't use samsung recommended on, I am getting sleep death with it.
No I'm using gzip (or possibly even no compression, I can't remember). It booted fine but wifi and the vibrator didn't work. Weird 'cause the modules are definitely in there. Maybe it has something to do with the CONFIG_DEBUG... options that shouldn't be set.
Timmmmmm said:
No I'm using gzip (or possibly even no compression, I can't remember). It booted fine but wifi and the vibrator didn't work. Weird 'cause the modules are definitely in there. Maybe it has something to do with the CONFIG_DEBUG... options that shouldn't be set.
Click to expand...
Click to collapse
Read that thread I link above, that is the fix...
Code:
HOW TO BUILD KERNEL 2.6.35 FOR GT-I9100
1. How to Build
- get Toolchain
Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
Extract kernel source and move into the top directory.
$ toolchain\arm-eabi-4.4.0
$ cd kernel/
$ make c1_rev02_defconfig
$ make
After looking at this a bit closer. Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI is 4.4.1, not 4.4.0.. I think we should send an email and ask them what is correct.
hello guys!i'm asking for your help if it is possible!i am from the galaxy Y forum.i saw that you are good developers and i was wondering if anyone of you can make a custom kernel for our device with just a few mods.someone tried but with not succes and we dont have devs to do that.please help!!!!thanks
Related
NEW:
Working .34-rc3 kernel available at http://forum.xda-developers.com/showpost.php?p=6290443&postcount=45
OLD:
Code:
This is an experimental .34-rc2 kernel for the Nexus One.
Provided in the zip file is a folder (2.6.34-rc2-termana-nexusone) and the kernel (zImage).
It is extremely experimental, so only follow this if you [B][I][U]really[/U][/I][/B] know what your doing and know how to reflash another kernel back to make it boot again if it doesn't boot. I'm not responsible if your device curls over and dies.
Use adb to push the folder into /system/lib/modules/ and then use fastboot to flash the kernel.
The kernel is a rebase of cyanogen's .33.1 kernel to the latest .34-rc2 kernel. So nothing particularly new about it, besides the satisfaction that not many people would be running this kernel version on devices.
Zip file: bit.ly/94Oo6m (To download it click the link next to the text "Save file to your PC:")
Edit: Being a new member of xda-developers forum, it wouldn't let me post the link properly, but just copy and paste it and you'll be fine.
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
I just flashed the zimage, and the phone went into a boot loop. Do I have to install anything else?
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Will give it a go nad logcat it
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
thanks, thought it was a mistake that you said push that folder, glad you clarified it for me
thanks again
jlevy73 said:
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
Click to expand...
Click to collapse
damn, that is long; won't bother reading that thing
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
I used this:
adb push 2.6.34-rc2-termana-nexusone /system/lib/modules/2.6.34-rc2-termana-nexusone
Click to expand...
Click to collapse
...and it still went into a boot loop for me.
hotweiss said:
I used this:
...and it still went into a boot loop for me.
Click to expand...
Click to collapse
You sure that wouldn't create a folder within a folder?
Not really sure just saying...
So is this working for you Termana?
I tried both have the subfolder and just pushing all the files to /modules and both produced a bootloop
i pushed the folder to /system/lib/modules/ and flashed zimage, but just get bootloop
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
I seriously thought, you tested it on your Nex before posting it....was a missunderstanding.
Termana said:
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
Click to expand...
Click to collapse
Did you cross compile the source against the ARM source?
hotweiss said:
Did you cross compile the source against the ARM source?
Click to expand...
Click to collapse
You might need to rephrase your question as the way you've said it doesn't let me know exactly what you mean by "ARM source". Do you mean using the Android ARM toolchain or what?
To anyone that is willing to help me test:
New build available at - bit.ly/c1tFqg (just the zImage, don't worry about pushing the modules for now)
Info:
This is a .33.1 kernel not a .34-rc2 kernel HOWEVER, I wanted to get the source that I'm rebasing off tested to make sure it boots, because if the source I'm pulling from doesn't boot, then obviously my rebases aren't going to either. So, please test it and tell me if it boots, if it does, I'll have another .34-rc2 kernel build up shortly after. If it doesn't, I may have to try rebasing from the official .32 kernel rather than the current source I'm rebasing from at the moment (which is .33.1).
Booted for me.
Code:
2.6.33.1-cyanogenmod
[email protected] #1
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Justin241982 said:
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Click to expand...
Click to collapse
I wouldn't post it yet. The first one he posted doesn't boot and the second one he posted I don't believe has any optimizations.
Both VPNC (e.g. get-a-robot-vpnc) and OpenVPN require tun.ko kernel module to work. The module is included in most popular ROMs but obviously not a part of SE kernel which we have to live with now.
Loading a tun.ko compiled for other kernels fails with a following message, for example:
adb shell dmesg
"tun: version magic '2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7' should be '2.6.29-rel preempt mod_unload ARMv7".
I tried to see if I could compile the module myself from the posted SE kernel source and using this post as a reference - forum.xda-developers.com/showpost.php?p=5692491&postcount=12, but I'm lost in git and cross-compile toolchain. I also tried changing "2.6.29-01117-g4bc62c2" to "2.6.29-rel" in the existing module with a hex editor, but that made the module invalid.
So, I wonder if someone could help?
Thanks.
crimper said:
Both VPNC (e.g. get-a-robot-vpnc) and OpenVPN require tun.ko kernel module to work. The module is included in most popular ROMs but obviously not a part of SE kernel which we have to live with now.
Loading a tun.ko compiled for other kernels fails with a following message, for example:
adb shell dmesg
"tun: version magic '2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7' should be '2.6.29-rel preempt mod_unload ARMv7".
I tried to see if I could compile the module myself from the posted SE kernel source and using this post as a reference - forum.xda-developers.com/showpost.php?p=5692491&postcount=12, but I'm lost in git and cross-compile toolchain. I also tried changing "2.6.29-01117-g4bc62c2" to "2.6.29-rel" in the existing module with a hex editor, but that made the module invalid.
So, I wonder if someone could help?
Thanks.
Click to expand...
Click to collapse
you need to recompile the kernel module (luckily kernel sources are available)
Please help
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
pepouwek said:
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
Click to expand...
Click to collapse
luckily for you, I made a guide in this board about how to recompile the kernel
Also in this topic about recompiling the kernel and there's infos about openvpn there too (search button will help).
And don't talk about inferior people, I really wish it was very easy to add all those stuffs but unluckily it's not. I can help you even if you're lost about kernel recompiling but I can't do all the stuffs for you.
how about searching instead of opening new thread......
http://forum.xda-developers.com/showpost.php?p=7054292&postcount=17
someone close this useless thread....
pepouwek said:
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
Click to expand...
Click to collapse
We can't use a different kernel to the stock one yet, and there's no point in recompiling the 2.6.29 kernel again, as the devs are trying to run the 2.6.32 one instead for froyo - tun.ko probably should be compiled with this instead. (in fact, I think froyo is able to be run already)
I think the custom spl/bootloader now needs to be tweaked by goroh_kun, Bin4ry, jerpelea etc. to:
- Be autobooted or flashed safely
- To be stable when run
- To be able to boot to a recovery partition and/or bootloader with a key combination
Also, I think they need to:
-Sort out phone partitioning to be used with the new bootloader and recovery image.
-Then try to fix bugs in the CyanogenMod 6 rom, if there are any 'major' ones.
I think that's what the devs are trying to do.
@hunteron you are not completely right even though you can't boot a complete kernel image you can insert your own modules
Sent from my X10i using XDA App
sim-value said:
@hunteron you are not completely right even though you can't boot a complete kernel image you can insert your own modules
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm sorry; you're right.
Mod. edit: reuse existing thread pls; CLOSED
Hello,
I believe a lot of us would like to do it, so let's please describe here how-to:
1. Linux
2. Mac os Leo
3. Windows
Gurus, please contribute!
Excellent initiative, I could write a short howto for Arch Linux later.
But one thing though, it might be a good idea to mention in the first post that you can't actually boot a custom kernel yet.
ddewbofh said:
Excellent initiative, I could write a short howto for Arch Linux later.
But one thing though, it might be a good idea to mention in the first post that you can't actually boot a custom kernel yet.
Click to expand...
Click to collapse
Indeed agree, but to try we need to have it!
My topic about compiling kernel sources has already many infos so do you think another similar topic is really necessary ?
alx5962 said:
My topic about compiling kernel sources has already many infos so do you think another similar topic is really necessary ?
Click to expand...
Click to collapse
Your thread is excellent but I'd guess that this thread would be more oriented towards "hand-holding", really basic guides. Your topic was very broad requiring going to the android developers site and reading their docs on cross-compilation. Gathering that info into easier guides could be beneficial, if not to demystify the process.
As it stands right now just compiling modules seems almost insurmountable. But if the information needed could be condensed into simple guides it could show that while it takes considerable time and effort it's not an impossible task even for developers not familiar with cross-compiling kernels.
And information information on setting up cross-compilers for Win, Mac and popular Linux distros is nice to have available in an easy to find topic anyway.
IMHO, the easiest way to make modules would be a virtualbox image already set up with arm gcc, kernel sources and X10 kernel config. It's a long process to set everything up; virtualbox makes this easier and cross platform.
maxrfon said:
Hello,
I believe a lot of us would like to do it, so let's please describe here how-to:
1. Linux
2. Mac os Leo
3. Windows
Gurus, please contribute!
Click to expand...
Click to collapse
Sources are here :
http://developer.sonyericsson.com/cws/download/1/823/877/1278570405/X10_mini_Donut_100630.tar.gz
Rest can be done in same way as for "big" X10.
alx5962 said:
IMHO, the easiest way to make modules would be a virtualbox image already set up with arm gcc, kernel sources and X10 kernel config. It's a long process to set everything up; virtualbox makes this easier and cross platform.
Click to expand...
Click to collapse
Do you have such virtual box image or whatever it is?
maxrfon said:
Do you have such virtual box image or whatever it is?
Click to expand...
Click to collapse
yep but can't share it as everything is set up in french and I'm sure you'll not like this
anyway, i'm sure the owner of this thread will enjoy to create one.
alx5962 said:
yep but can't share it as everything is set up in french and I'm sure you'll not like this
anyway, i'm sure the owner of this thread will enjoy to create one.
Click to expand...
Click to collapse
Yes, french for me is a bit difficult
Ok i managed to make Ubuntu on my Parallels, just finished with the gcc. Let's see how it works.
Maybe i will share it.
kernel config is included in the /etc folder if I remember well, hope it's the same for the mini X10
It's actually in /proc
zdzihu said:
It's actually in /proc
Click to expand...
Click to collapse
Hi zdzihu,
I managed somehow install arm gcc on my Ubuntu. Now it's time for the tools.
So i would like to ask what config should i use arm v4? V5?
I am so tired with this linux things, but finally at least the demo busybox compiled well
So i tried to compile with arm-v5te config but for flash read (which is normaly working) it says
Code:
# ./dump_image system /sdcard/tt.bin
error reading system: Inappropriate ioctl for device
My task it not to run flash tools available, but my own, to compile all myself, to try to do the trick with the CPU to accept kernel, that i compiled.
Thanks.
The Snapdragon is armv7 compliant, so that should be your target.
ddewbofh said:
The Snapdragon is armv7 compliant, so that should be your target.
Click to expand...
Click to collapse
http://jackytw.blogspot.com/2009/11/howto-run-native-linux-application-on.html
This tut i was using.
I can't find v7 .. Should i consider the V as the CPU ver?
Then its 1136 if i am not wrong?
maxrfon said:
http://jackytw.blogspot.com/2009/11/howto-run-native-linux-application-on.html
This tut i was using.
I can't find v7 .. Should i consider the V as the CPU ver?
Then its 1136 if i am not wrong?
Click to expand...
Click to collapse
Are you using that tool to build the toolchain? In that case it might not have the option to build for that arch. The best way to make sure you get the correct one is to build it manually from scratch.
ddewbofh said:
Are you using that tool to build the toolchain? In that case it might not have the option to build for that arch. The best way to make sure you get the correct one is to build it manually from scratch.
Click to expand...
Click to collapse
Looks like there is no other tut to build the toolchain. I searched days and nights to find something working.
I even compiled bysybox with it and it works on my x10!
But i found some sources of flash backup, called nandtools, compiled them well, no errors but the exec files are 4x bigger than the precompiled ones... And it makes the IOControl error..
the NDK won't compile, it requires Makefile or Android.mk and those are real headache to learn.
The Makefile from the archive is not compatible with NDK's make system and so on...
And so 2 weeks..
Pufff.. I am so tired if just linux things
Any hand?
Hi there, ARM is backward compatibile so compiled for v5 should run just fine. Problem must be somewhere else... I'm at work at the moment so I can't help much
By the way, there was some kind of dedicated flash tool posted already HERE, maybe you could check with jerpelea for re-upload?
zdzihu said:
Hi there, ARM is backward compatibile so compiled for v5 should run just fine. Problem must be somewhere else... I'm at work at the moment so I can't help much
By the way, there was some kind of dedicated flash tool posted already HERE, maybe you could check with jerpelea for re-upload?
Click to expand...
Click to collapse
You see, i need to compile mine, i have enough tools here already working, but my task is to compile my own and that's why i need a toolchain.
NDK is ok for the kernel, i compiled it already. But the native applications are not supported fully. Like write is deprecated and you can't use this function, and lot other limitations. So independent toolchain would help.
That's the point.
maxrfon said:
So independent toolchain would help.
Click to expand...
Click to collapse
PM sent =)
I decided to make my first custom rom. The main difference over klin1344's klassic is the fact that we can customize what we want with the aroma installer. As of now, there's no customised interface (and there will not be. Consider this like WT Ho's rom for the 5.0).
I stop working on it because I want to try something other than stock. Also thanks for your consideration for this rom. (I will continue the maintenance of it though)
Features:
- Stock 2.3.6 XXKPQ
- Rooted
- Busybox
- Deodexed
- Zipaligned
- Aroma installer: An interactive installer
- Multiple bootanimations.
- Choice between TW 3.0, TW 4.5, Go launcher EX, Xperia S launcher
- Possibility to install DSP manager and voodoo app (for sound enchance)
- Features the CWM 5.0.2.7 (Intl Only. Kernel based from steve's 3.0) (V.1.0)
- US users will recieve the latest klin's R2 custom kernel* (V.1.0).
- Intl and US compatibility in a single zip. (v.2.0)
- SuperSU (v.3.0)
Changelog:
Code:
[B]V.3.0 (Vita) FINAL [/B]
- Deodexed and Zipaligned
- SuperSU is used instead of SuperUser
- Updated Google Play Store, Maps and Youtube app (Can play 720p) (It's real this time)
- Possibility to add Antutu Cpu Master Free (For Overclock)
[B]V.2.0 (Radiance)[/B]
- Name changed only to Renaissance
- Possibility to chose the device type (Thanks to dark_valor's Terra Silent)
- New Honeycomb bootanimation
- Possibility to add terminal to the rom
[B]v.1.0 (Etincelle)[/B]:
- Initial Release.
Download:
1.0
Intl: Intl Renaissance 1.0 Download
US: US Renaissance 1.0 Download
2.0: Renaissance 2.0 Download
3.0: Renaissance 3.0 Download
If you want there's the Xperia S Wallpapers: Xperia S Wallpapers Download
If there's a problem with antutu, install the apk here: Cpu Master Apk Download
If there's a problem with terminal reinstall it.
Instructions:
1. Boot into Cwm
2. Backup
3. Wipe data (BEFORE IT IS MANDATORY)
4. Run renaissance-device.zip
5. Follow the instructions.
6. Reboot
7. Enjoy!
If you do like please hit thanks button. If you have problem with installation, Send me .log file in aroma. If it's problem with the rom please let me know.
Thanks to:
amarullz: for Aroma installer
Klin1344, SteveS and stratosk for the kernel related things.
WT Ho for his base for aroma installer. (and help too )
GO Dev Team , Fr4gg0r and ra3al for their launcher
Dark_balor for his kernel (terra silent)
Jackpal for the terminal emulator
Antutu for the CPU Master
As this is the last version, If you want to use something in the rom (porting) ask me first.(Mostly for Aroma)
These are the possible implementations (suggestions)
- Deodex
- Performance tweaks
- More customisation options
- Better compatibility with apps (Like deviceID hack)
reserved again
screenshots please?
EcHoFiiVe said:
screenshots please?
Click to expand...
Click to collapse
Oh sorry about that. I will put them tomowrrow. (that depends which screenshots you want?)
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Wheatly said:
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Click to expand...
Click to collapse
Well I didin't enable ext4 so data and dbdata will be stuck at rfs. Sorry about that.
Does the CWM 5 in the kernel I gave you work well? Because when I gave it to you there seemed to be a lot of errors... But if it does, I'll probably apply those changes back to my kernel again and update to cwm 5 because it allows easier converting to ext4. Also, did stratosk give you permission because I used his cwm recovery files from his sources. (just making sure, so he doesn't come and flame me for porting cwm5 from his sources without permission)
Sent using Tapatalk
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so everyone will have justice.
Click to expand...
Click to collapse
Ok thanks. But how exactly did you fix it? I didn't flash the kernel you gave me but where are your sources? (the Linux kernel is GPL licensed, so it's mandatory to have a source )
Sent using Tapatalk
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Dark_Balor said:
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Click to expand...
Click to collapse
He based it off stock rom. Tomorrow I'll figure out how he fixed cwm 5.0.2.7 from his initramfs.
Sent using Tapatalk
klin1344 said:
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
Click to expand...
Click to collapse
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
zaclimon said:
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
Click to expand...
Click to collapse
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
klin1344 said:
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
Click to expand...
Click to collapse
I made some changes to the init.rc and lpm.rc I think.
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
EcHoFiiVe said:
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
Click to expand...
Click to collapse
Because it is a stock rom (with multiple apps) I won't put screenshots. Once 2.0 will be released (UI modifications) I will put them. You can backup and try it?
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
Click to expand...
Click to collapse
zaclimon said:
I made some changes to the init.rc and lpm.rc I think.
Click to expand...
Click to collapse
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . I'm really discouraged and very tempted to just take down all my work for the Galaxy Player and just keep all the development to myself. Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
klin1344 said:
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
Click to expand...
Click to collapse
ok don't go blaming me BECAUSE IT GOT ERRORS when YOU sent it to me. I corrected some errors but I can't remember which ones is it. I can't get lucky if EVERY of my backups works(Because I got errors for md5 mismatch as well too). It is sure that your init files are the same because I used some of the text you used when you were building YOUR R1 kernel. (so basically I used some of your sources) but you were always complaining about ext4 not working so you gave up on CWMR5.0. and when I said I've fixed them you didin't tested it. DON'T GO COMPLAINING IF YOU DIDIN'T EVEN TESTED IT. (also check all the init files to be sure and also check the thanks it is `kernel related things`.) -___-
EDIT: If you want all the credits. You can have them. I should have said that you made all the changes but the problem was that you gave up on CWMR5.0 so I was like (The kernel works now but I won't release it because you already have your custom kernel with CWMR3.)
Hey does anybody have a TUT in how to decompile an existing kernel so i can make some changes and then recompile it?
Sent from my GT-I9001 using XDA
Hey did you ever get your answer? I am also looking to do the same thanks.
EternalFame said:
Hey does anybody have a TUT in how to decompile an existing kernel so i can make some changes and then recompile it?
Click to expand...
Click to collapse
This is not the way it's done.
You'll have to get your kernels configuration. This is done either by see if there's a /proc/config.gz using the running kernel, or using the extract-ikconfig script shipped with the kernel source to extract the configuration from the kernel file.
Code:
$ extract-ikconfig kernel.img-kernel
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.9
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_GENERIC_GPIO=y
CONFIG_GENERIC_TIME=y
[...]
This configuration you supply to the kernel source. If the vendor got some specific patches (they do), you'll have to get the kernel source from them, patches included. They must supply you the source, or be in violation of the GNU General Public License.
Building the Android boot image using mkbootimg, you'll also have to get the base address from this config.
Code:
$ extract-ikconfig kernel.img-kernel | grep PHYS_OFFSET
CONFIG_PHYS_OFFSET=[B]0x00200000[/B]
Now you have everything you'll need to build a correctly configured kernel and making the Android boot image. Detailed build instructions are included in the kernel source as well.
Wow thank you
Sent from my SGH-T989 using xda premium
Can we extract kernel with dsixda kitchen?
Edward Cullen
Kernel can be extracted, rename to *.zip
purrungo said:
Kernel can be extracted, rename to *.zip
Click to expand...
Click to collapse
it kernel.lz or etc format when use extractor it say corrupted archive
why manufacturers have to provide kernel to users when they don't want users to modify their products?. Many manufacturers just sell devices, and strangely there are many dev.er who CaN overclock or patch, modify the kernel with boot.img, HOW did they do thAt??? Kernel source code sometimes is their devevloper source code, not from manufacture stock source code.
i want to de and recompile kernel file for WSA
(windows subsystem for android)
any help?
foxhackerr said:
Any help?
Click to expand...
Click to collapse
Depending on what/how much you want to modify it can be easier to patch an existing kernel than to build from scratch. Me? I'm lazy. I never build anything.
Get boot image
Extract kernel
Decompress kernel
Extract kallsyms
Disassemble kernel
Come up with a patch and patch it
Put it back together
(Steps 4 & 5 may be combined depending on your tools. I do them separately.)
Renate said:
Depending on what/how much you want to modify it can be easier to patch an existing kernel than to build from scratch. Me? I'm lazy. I never build anything.
Get boot image
Extract kernel
Decompress kernel
Extract kallsyms
Disassemble kernel
Come up with a patch and patch it
Put it back together
(Steps 4 & 5 may be combined depending on your tools. I do them separately.)
Click to expand...
Click to collapse
How to do this??
kxrma said:
How to do this??
Click to expand...
Click to collapse
Use dd if rooted or EDL or extract from update
I use my imgutil.exe
I use my imgutil.exe
I use my kallsyms.exe or cat /proc/kallsyms on a running system
I use the stock objdump processed afterward with my own findref.exe (not really released yet). You could use Ghidra.
Use any hex editor. I also use my own kpatch.exe (not really released yet).
I use my imgutil.exe