[Nexus 10 Android Development] DragonFire1024:
I honestly do not know. I'm sure if you can unpack the boot images from both ROMs, and switch out the zimage, the worst that would happen is it wouldn't boot into anything other than a black screen or the device will reboot to recovery or just get stuck in a bootloop. Just make sure to backup your current image in case you need to reflash it.

I have looked into building a Android 7.0 ROM for the device and based off of what I've read in various threads throughout the years on this tablet, the camera or audio jacks will not work. I want to confirm that to be the case. I've spent the better part of my two days off from work trying to come up with the solution of some sort and so far I've been unsuccessful. But all hope may not be lost. I just don't understand much of the coding to fix it, or at least all of it. I did manage to fix several errors but not enough that doesn't break the build without moving the libraries for the hardware files it is trying to build. by the looks of the code, and I'm not in front of my pc at the moment oh, it seems they tried to update it at one point in time but the update did not work and seemingly looks to have never been fixed or at least was commented out in a way that they weren't going to ever fix it. I think it can be fixed if the code is re-written properly but as of the moment it does not look like any ROM past marshmallow will work on the device fully until the hardware composer is fixed which seems to be the main issue. Everything else seems to be good to go and builds as properly as can be except for those two items and on this device I really do think that is a buzz killer.

with that having been said I don't understand how it would not be possible to place such files into vendor and have them brought over during the build and put into their proper places at the right time. Does the hardware composer really need to be recompiled in order for them to be moved over to 7.0? Couldn't I just take the library files that are required to continue the building process off of the current 6.0 tablet and place them into the vendor area where they can be brought over later on? Or at least make a system folder in the vendor area where they can be brought over during the bill process later on?

Issues may or may not be: will not accept AOSP files to build main sensor grid. That doesn't seem to be an issue because AOSP will automatically build it as it is a official device. Secondly the hardware composer seems to break the camera the gallery and some parts of the audio. Until that is fixed, that takes away most of the pleasure of the device given that for a tablet of its age it was rare to have such a good camera. third I'm not sure the colonel can be updated to 3.5. I have to do some more research to find out what I am doing wrong or figure out by hand which of the commits I have to take out of the patch in order to continue and that may take some time because this patch is very large. And in order for me to figure out what's broken I have to apply the patch get the errors, take out the commits, delete the kernel source and extract it again and start over from the very beginning LOL. That's the whole tedious process about updating an incremental kernel. There is no real easy way to do this without cherry-picking the commits that don't work but in order to figure out which ones don't work you have to first break it.