mybe someone can make tutorial, how to playing with this ?
because i'm confused how to make/repack ramdisk
-sorry for my bad english-
Check my guides from my profile. One's for compiling the kernel and the ramdisk, ehile the other briefly explains the use of the contents of the ramdisk and how you can modify them.
Related
I am able to compile Kernel from source and re-use initramfs extracted from CF, Overcome and stock rom. But still it hangs when I flash.
I think I need to regenerate the /res/keys in the initramfs but I can't find details though I have read through most of the Development forum related here. I even search for some source posted to Github.
I don't want to patch the boot loader as it should be risky. Also CF and Overcome don't need to and I want to follow the same.
Please help
Thanks
I'm working on compiling a kernel for the Sprint Samsung Galaxy Tab 7. I've got source and the proper toolchain installed, but I need a rootfs. I did this for the Epic, but it's been quite a while. In the kernel config file CONFIG_INITRAMFS_SOURCE needs to be pointed to the source rootfs, if I remember correctly. Can someone lend a hand? Is there a FAQ or HOWTO?
not sure how familiar you are with irc, but if you get on fossnet and join the #gtab channel you will get some help there im sure.
Thanks for the tip!
Sorry to resurrect this thread, but I'm having issues too (having only just had time to actually compile something from the Gingerbread source).
So, I've got the gingerbread update 2 kernel source, have extracted the initramfs.cpio from the existing gb kernel and pointed the appropriate CONFIG setting of the kernel p1_defconfig at that file and then performed a build. My assumption was that this would build a kernel that would boot and be nearly identical to the vanilla kernel. But apparently not as it just hangs.
Anyone know off-hand what I'm missing?
My issue was that the script I was using to extract the initramfs from the zImage wasn't working properly and was apparently truncating the cpio file. This was causing hangs when I rebuilt the kernel using this initramfs.
Using this script all works fine: https://github.com/mistadman/Extract-Kernel-Initramfs
Hi, I'm me again.. Ok. Here's the thing. I was just searching out files from roms for alfs, nAa and stock and I found out that ramdisk.tar files is in stock kernel roms and the others not! And also, I got libs for stock kernel. First is first! I wanted to know if I add ramdisk.tar files from stock kernel rom's and paste it in the other kernels rom and flash libs would boot up that? I don't really think so but I'm just asking. Hay.. Easy on me. While other peoples creating threads that doesn't even make sense about soft bricking (They didn't use the search button I hoped (Forever Alone Search Button)) I was asking some quite well questions so easy on me please
Please
Why don't just go ahead and try it?
As I remember (I not used stock kernel and roms for this kernel since the first custom kernel out ), the separated ramdisk files needed for the recovery. Ramdisk.tar contains the stock ramdisk, cwm.tar contains the clockwormod recovery, another tar file contains the xrecovery. Examine the chargemon file in any stock kernel based rom, you can see how to work...
I don't know what is your goal with these tar files and libs. You want to use naa/alfs based roms on stock kernel? If yes, you need to revert lot of things (wifi, egl libs, sensor drivers, etc...)
Sent from my E15i using xda app-developers app
Fortun said:
Why don't just go ahead and try it?
Click to expand...
Click to collapse
pilu1978 said:
As I remember (I not used stock kernel and roms for this kernel since the first custom kernel out ), the separated ramdisk files needed for the recovery. Ramdisk.tar contains the stock ramdisk, cwm.tar contains the clockwormod recovery, another tar file contains the xrecovery. Examine the chargemon file in any stock kernel based rom, you can see how to work...
I don't know what is your goal with these tar files and libs. You want to use naa/alfs based roms on stock kernel? If yes, you need to revert lot of things (wifi, egl libs, sensor drivers, etc...)
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
Thanks for the information bros. I was just asking. I wanted to port that's all I needed.
Hi all,
First of all, I hope that is this question was not yet in the forum. At least, I have searched for it.
Well, I'm trying to compile LG P990 kowalski kernel from @pengus77 from it's github sources (github(dot)com/pengus77/lge-kernel-star)
Currently, I'm using the oldBL and I'm compiling the kernel using Linaro toolchain 4.6.2 (in Ubuntu).
I can compile the kernel without major problems, and both zImage and modules are generated. After, I used the the anykernel script (for old bootloader - oldBL), the same used by @pengus77 to distribute the kowalski.
The problem is that I can not boot the phone using the zImage compiled by myself. It always stucks in LG Logo.
Do you have hint to this? It might be a problem with environment setup and/or with Linario toolchain version?
All your possible help will be appreciated.
Many thanks!
As I cannot find any related guide while google-ing, I want to post this question on here for the purpose of learning and probably helping other people.
[Q1] How to overclock a kernel
which files are needed -> kernel source .. ?
what files need to be edited ?
is the cpufreq driver related ?
how to determine which frequencies need higher voltage and how high exactly ?
[Q2] Undervolting
which files are needed -> kernel source .. ?
what files need to be edited ?
is the cpufreq driver related ?
how to determine which frequencies can use lowered voltage and how to calculate them ?
These questions you ask, most likely would have been answered in:
https://forum.xda-developers.com/galaxy-note-8/development