[Fire HD 8 and HD 10 General] DragonFire1024:
The the thing is they make files were designed to be built through AOSP. Specifically designed as such at least that's according to the source that I am working off of. but because some of the hardware profiles are ever so slightly different I believed it would have taken more time to go through and change the tiny or things rather than going through and just doing a brand new one and I may perhaps have been wrong about that. so I'm not quite sure what the problem is again aside from it being something on the kernel. now I have had a couple of inklings to say that if anyone has actually been successful like I have it building one perhaps try and remove the Amazon specific drivers and other details that are stocked into it when it's built and perhaps that may fix any problems we have I do not know I have not been able to try that part yet or have been brave enough to do so any given reason maybe just haven't had time and it's been on the back burner. But it's just an idea. Also we do have the sources we can work off of a kernel that's non-amazon.

On a side note I have been trying to look through the init files for anything specific that would stop something from booting and I can't find anything but I have been able to remove some of the configurations and still be able to boot after removing them from the boot image. I also wouldn't have put it past Amazon to have placed some of the stuff they removed from the system image into a different partition somewhere just to move it or brush it out of the way like they do with most of the other stuff on here. Which code Paul is another significant problem given the fact that we have no idea what are in these partitions or what they even are if I'm not mistaken. I've looked at all of them and I do not recall off the top of my head any of the partitions containing anything extraordinary but again I could be wrong and it's been awhile since I've looked at any of them. I still think there's something going on here where it seems weird that the fs tab files all add up except for one given partition so I don't know. This is all speculation but again we're also in another boat where Amazon used a bass system image of LVY48F. which some cases may or may not be a problem but again that's system image wasn't even designed for a device like this. It was actually designed to run on a device as part of project fi. so presuming that we can even build off that branch which I can't I have not downloaded that one I have been working off the last and final release of the lollipop source from AOSP.

---------- Post added at 11:27 AM ---------- Previous post was at 10:43 AM ----------

ROM 1: set_metadata version: aosp_suez_lollipop.zip https://drive.google.com/file/d/1QPyWaNT4IZGzVQUmJGoqu0FbHNUNtHt8/view?usp=sharing

Rom2: sparse_data https://drive.google.com/file/d/1uWfoRhAbT2v_wMTR9pe8OenDQxeIfHkh/view?usp=sharing

Warning these do not boot.

---------- Post added at 11:48 AM ---------- Previous post was at 11:27 AM ----------

looking it over and it appears the reason why I didn't go anywhere is because none of the proprietary files were copied over where they were supposed to be. Which is weird because I saw those exact steps be completed. So I'm not entirely sure what happened there. Not all of them weren't copied over. Some of them weren't especially a lot of the binaries and I'm not even sure where they are because they're not in the ROM it appears. Some of vendor files also didn't copy over. So I'm going to have to look back and see what happened.