How do I do this?
I have:
a modded power.tuna.so
zImage
I always get bootloops when trying to make a boot.img
Flashing the zImage works perfectly. But as soon as I try making a boot.img with ramdisk I am screwed
I always had problems making it flashable too, I xoyks never get it. So I Always just flashed the zImage only when I built kernels. There are lots of guides though I know.
BTW what code did you change?
Related
Simple question, I can only hope the answer can be as easy as the question...
I've got a rooted rom, nand unlocked, etc...I try editing the boot scripts and it saves, but upon reboot they are reverted.
It would seem they are being generated on each boot, is there any way to (permanently) modify these scripts or stop them from being regenerated?
I do believe DamageLess has done it with his latest rom.
I asked this and the topic got moved here: http://forum.xda-developers.com/showthread.php?t=704433
Neotelos_com said:
Simple question, I can only hope the answer can be as easy as the question...
I've got a rooted rom, nand unlocked, etc...I try editing the boot scripts and it saves, but upon reboot they are reverted.
It would seem they are being generated on each boot, is there any way to (permanently) modify these scripts or stop them from being regenerated?
I do believe DamageLess has done it with his latest rom.
Click to expand...
Click to collapse
init.rc is part of the ramdisk. ramdisk which is bundled with the kernel. it gets reloaded on every boot.
i also posted an answer in the other thread linked to above before it was moved ...
like the person above me said, those files are part of the ramdisk and not the actual kernel. but, it's all packaged into a boot.img when you flash a rom. there's a method where someone created a script to split the ramdisk and actual kernel, which i've tried before. google "split ramdisk and kernel android" and you might find what you want.
problem is, when i did that for the hero, it never compiled right. maybe you'll have more luck?
In flashing roms, I notice that devs are including kernels in the .zip. It appears each dev has their favorites. Without debating which kernel is the "best", my question is can I switch a Zimage (which I assume is the kernel) with another of my liking? Or, if I'm running a particular kernel of my liking, can I flash the Rom without the included Zimage?
.....
Vegasden said:
In flashing roms, I notice that devs are including kernels in the .zip. It appears each dev has their favorites. Without debating which kernel is the "best", my question is can I switch a Zimage (which I assume is the kernel) with another of my liking? Or, if I'm running a particular kernel of my liking, can I flash the Rom without the included Zimage?
.....
Click to expand...
Click to collapse
You should be able to flash a kernel, either through CWM or ODIN without problem.
sk63 said:
You should be able to flash a kernel, either through CWM or ODIN without problem.
Click to expand...
Click to collapse
I realize that. My question was in reference to flashing a rom (which all have a kernel included). Can you switch the Zimage inside the rom .zip prior to flashing...or can I just delete the Zimage inside the rom and flash it without one? I'm trying to avoid the two steps of flashing a rom, then flashing a kernel I prefer.
Ah, I've always just flashed the ROM, then flashed the kernel then rebooted out of CWM. Be nice if there was a utility where you give it kernel and rom and tell it to go, might be a nice feature for ROM Manager to add.
I have been looking around and messing with different kernels for the SGS2E4GT (pauses for breath) and I've noticed that most of the stock kernels have directions for flashing via Odin, but I was wondering if these kernels would be possible to flash via CWM as well...I've noticed that most of these compressed flashable files have this zImage file inside (sorry about my lack of knowledge...I've been in webOS-land the last couple years and have just started learning about Android, so this is probably standard practice)...do I just need to take a stock zImage file from the .tar file and compress it in .zip form to flash it in CWM?
So I am still learning how everything functions with this new setup. My only question that I have right now, is If I want to change the kernel of a ROM prior to flashing it, do I just need to replace the zImage file with the one that I want.
ie. ROM A comes with source EG30, and ROM B comes with stock pulled EG30, Can I just take the zImage from ROM B and drop it into ROM A, sign and flash?
Khilbron said:
So I am still learning how everything functions with this new setup. My only question that I have right now, is If I want to change the kernel of a ROM prior to flashing it, do I just need to replace the zImage file with the one that I want.
ie. ROM A comes with source EG30, and ROM B comes with stock pulled EG30, Can I just take the zImage from ROM B and drop it into ROM A, sign and flash?
Click to expand...
Click to collapse
Yes, you can do that. But use 7zip because it doesn't break the signed .zip. Right click on the file after installing 7zip and choose 7zip > Open Archive and just paste the zImage you want in there.
Sorry about all the question threads I've been making lately just trying to learn...so I made CM10 for my r800x and it was working on my phone with turbo kernel but now I want to start seeing how the kernel works but when I put the boot.img that compiled with my ROM it doesn't have CWM. Can anyone tell me how to add CWM to the ramdisk or point me in the direction? I've searched for a while and can't seem to find anywhere that tells you how, only thing I can find how to do is compile the recovery.img