[3ndymion]

fuser-invent, on 26 January 2013 - 01:00 PM, said:

@ 3ndymion - I'm like 99% sure that you can not decompile a kernel, you have to build it from source. You can unpack a uImage or boot.img and edit the ramdisk though. If you find out otherwise let me know.

With all the studying I've been doing, I understand why you say that now. Too bad we don't have the source code yet. If we were to take the kernel source code from one of the other similar tabs, extract the proprietary drivers from the batch 3, & compile them, that should work, & even solve the problem of the screen, g-sensor, & camera, no???

[3ndymion]

fldc, on 28 January 2013 - 06:04 AM, said:

It's pretty clear actually, I have two devices, the only difference is the nand chip(s) used, I've tried booting older kernels on the device which this doesn't work on, it just doesn't find any nand, so the problem here is it needs an updated driver.

I'm still learning about this... when the bootloader first sets up, doesn't it autodetect the NAND chip & information on it, like how big it is??? Then, it's supposed to pass that information to the kernel when it loads it up so the kernel can use it, no??? Or does this work differently???

[fuser-invent]

I think your description of the bootloader makes sense. You can use the ELF2 Kernel source code to compile a kernel for the Crystal, it just takes some work.