[Q] Xoom Loading Custome Kernel

---

I have a xoom wifi with android 3.2 on it. Kernel 2.6.36.3-00042-g3c1a41ea7301c@il93lnxdroid47 #1

I'm rooted and my bootloader is unlocked. I downloaded the Timate kernel (Tiamat-Kernel-2.0.0-Katana-stockgpu.zip) and loaded it with clockwork recovery. I saw anykernel run when I applied the zip. But after I reboot the xoom still has the same kernel version on it.

Did I miss a step somewhere? How does it keep loading the stock kernel after I load the new one? The only thing I can think of is that there is a failsafe mode that loads the "last good" kernel if the current one fails.

Originally Posted by njdevi11

I have a xoom wifi with android 3.2 on it. Kernel 2.6.36.3-00042-g3c1a41ea7301c@il93lnxdroid47 #1

I'm rooted and my bootloader is unlocked. I downloaded the Timate kernel (Tiamat-Kernel-2.0.0-Katana-stockgpu.zip) and loaded it with clockwork recovery. I saw anykernel run when I applied the zip. But after I reboot the xoom still has the same kernel version on it.

Did I miss a step somewhere? How does it keep loading the stock kernel after I load the new one? The only thing I can think of is that there is a failsafe mode that loads the "last good" kernel if the current one fails.

Do a manual Flash from recovery. or - Upgrade to ICS with -Download the EOS ICS 1.0.0 (good stable ROM/kernel)

http://forum.xda-developers.com/show....php?t=1484770

SOLVED:

---

So for whatever reason I absolutely CAN NOT get an anykernel zip to work for me and i've tried it on a few devices (xoom, nexus s, atrix, nook off the top of my head). Here is what I had to do to get my own kernel on the xoom:

(1) make a backup with CWM, and copy the boot.img to my computer.
(2) extract boot.img with unpack-bootimg.pl
(3) this gives me the boot-img-ramdisk.cpio.gz file and boot.img-kernel.gz
If you want to recpio because you changed the ramdisk/added ko's run:
cd boot.img-ramdisk/
find . | cpio -o -H newc | gzip > ../bootimg-ramdisk.cpio.gz
cd ..
(4) use command:
mkbootimg --cmdline 'androidboot.carrier=wifi-only product_type=w' --kernel zImage --ramdisk boot.img-ramdisk.cpio.gz -o boot-new.img --base 0x30000000 --pagesize 4096
adb reboot bootloader
fastboot flash boot boot-new.img

Adendium:

---

I figured out what the command= should be by opening a working boot-img in a hex/text editor (vi) and just copied what should be in there. That seems to do that trick for the last few devices i've tried compiling kernels for. All the "tutorials" on the internet I've seen get really sketchy when it comes to actually repacking a kernel and there is a lot of bad or just lazy information that's outdated or copied about one device for another that doesn't actually work like that.