[jlark]

Originally Posted by daniele_dll

I was able to extract the kernel configuration from the running android system and, after searching around, i found the same kernel version 3.0.35 (but obiviously without onyx patches).

I recompiled the kernel 1 milion of times but I am not able to see the console on the framebuffer (device mxcepdcfb), probably because I don't have the right device tree.

@daniele_dll hi, I see you haven't posted in more than a year. Did you manage to get any progress with this project? Are you still interested in it?

I have the Boox Max which is pretty much the same platform, and whatever effort was spent into this would apply to all their recent devices as well.

I was thinking to approach this from another direction: use the kernel as it is, replace the android init with busybox init or whatever, and build up from there and see what can be achieved.

Originally Posted by daniele_dll

However i discovered that when the kernel panics I can access the internal iMX6 rom to replace uboot (but I will not do the test because this can fully brick the e-book reader)

Did you figure out where the boot process could be intercepted from uboot to the kernel to be able to set up dual boot? Without fear of bricking?

Originally Posted by daniele_dll

I asked to onyx boox for kernel sources, device tree and some other informations, hope that they give a positive answer

Any results for you? I asked them too, they answered back nicely, they mentioned github, but I'm not sure yet what their position is with regards to the code. If they don't want to be nice I'll remind them of the GPL, and if needed I'll talk to the vendor, which is from Germany, and that's a country known for enforcing the GPL.