yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] gerryl432:
Maybe they are referring to the series and not the version.
[Fire HD 8 and HD 10 General] DragonFire1024:
Same goes for this tablet. The .19 will need to be rolled back to just 3.18. Supposedly after that we can upgrade the kernel to a newer version. However this is tedious. We can't update incrementally without rolling back. So we'd have to pick a version, download every single patch between the current version and the version we want, then patch the kernel.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
But we're getting somewhere, nonetheless, aren't we?

Seems the Walmart Onn 10.1 Android 9 tablets run the same SoC as the Amazon Fire 8. Hmmmm....
[Fire HD 8 and HD 10 General] DragonFire1024:
Really? I looked at them briefly, but not the full specs. They also run android 9. Honestly I was thinking of buying one.

---------- Post added at 11:38 AM ---------- Previous post was at 11:30 AM ----------

The required roll back would explain the errors I get when trying to update it. I wasn't doing that so that was likely my issue.
[Fire HD 8 and HD 10 General] chivoyage:
Wow, great find!
[Fire HD 8 and HD 10 General] DragonFire1024:
Doesn't do the HD 10 any good unfortunately.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Fair enough. It's more of an observation than anything.
[Fire HD 8 and HD 10 General] DragonFire1024:
The rom I have that im trying to port has the same everything as the HD 10. CPU, architecture, etc. I just can't seem to port it properly.
[Fire HD 8 and HD 10 General] DragonFire1024:
So I've done some research it appears that the kernel version we have has reach what they call end of life status. So I have not been able to find the patch that would allow us to downgrade back to 3.18. I have tried to take the mediatek source from the Google source website and try to use the suez_deconfig to build the kernel from Google's website. However, when it comes down to building the drivers, the build errors when trying to build the USB gadget drivers. I've tried to move the gadget file from the Suez source to the Google source with no success. I may be able to move the USB folder, but haven't tried that yet. so unless we can locate the patch to allow us to downgrade back to to 3.18 then we're are stuck on this version until a kernel is built through lineage. I am still having trouble building the kernel through aosp. It fails at building the boot.img because it can't find the files, which are indeed properly placed.
[Fire HD 8 and HD 10 General] DragonFire1024:
Shhh. Its a surprise. I'm not going to say too much because I don't want to build excitement only to be disappointed.

So in as few words as I can: I'm going to be testing what looks to be a successful ROM build ;) if it boots, I'll post the link for alpha testing. But its looking pretty good. We've had some great assistance in building this, and theyll get the credit, so I'm fairly confident they've got it this time. So if all goes well...nougat will be available tomorrow afternoon.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Yasssssss!
[Fire HD 8 and HD 10 General] massimo727:
Looking forward to testing.
[Fire HD 8 and HD 10 General] DragonFire1024:
I too was looking forward to testing. Here is an update. So it appears the system flashes however it appears the kernel does not. Not sure why but there are bunch of errors in the logs. I've tried numerous things such as flashing a stock boot image the latest Amazon update. That did not work. Then I try flashing my modified boot image / custom kernel and that didn't work either. Then I went to the lineage operating system site and downloaded the zip that removes their superuser from the system and flashed regular super user and that didn't work either. restored the boot image and tried magisk and that didn't work either. I have posted the logs in a couple of zip files just extract them and open them and in a text editor.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Awww crap. That's a bummer.
[Fire HD 8 and HD 10 General] DragonFire1024:
The system definitely flashed. It's there. I'm putting my money on the ramdisk or kernel.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
All we need is a way to determine which it is, and then figure out how to solve that issue. We're close, I can feel it.
[Fire HD 8 and HD 10 General] GS2Giova:
Set up a fundraiser and you will have my money (mine and many others too, I'm sure)
[Fire HD 8 and HD 10 General] Rortiz2:
We're looking at the logs, let's see what we can do..
[Fire HD 8 and HD 10 General] DragonFire1024:
Indeed. The wrong CPU part, that's simply one of the values in the scripts needs tweaked. About a year ago I installed Kali Linux inside termux on the HD 8. It too had a similar error in regards to cpu. All the dev had to do was change a couple of values in the script. I'll look for it. Maybe it has at least one answer.

Secondly, when I went to flash gapps, it required 64bit. That definitely isn't right. So it is either the build scripts or one of the .mk files where at least this issue is located.

---------- Post added at 05:11 PM ---------- Previous post was at 05:06 PM ----------

Also, I've gathered all the basic vendor mediatek files for this api (5.1.1). This doesn't include the proprietary blobs.
[Fire HD 8 and HD 10 General] DragonFire1024:
OK so this is the thread where I ran into a similar fight with these tablets regarding whether some programs think its a 32 or 64 bit. I'm not sure what was changed but I think it was arm-v8x to arm64 idk https://github.com/Hax4us/Nethunter-In-Termux/issues/85
[Fire HD 8 and HD 10 General] DragonFire1024:
I cannot get aosp to build the kernel. The source files are in the right spot (Android build dir)/kernel/amazon/suez but no matter what I do, it won't build the boot.img. it won't even build mkbootimg. I even tried to place the already built binaries in the same directory. So I just changed the value to false for making the kernel. I uncommented the configuration for a prebuilt kernel, and same results.

So onto the rom...I can't get it to build either. Though I think it's due to the wrong blobs in the wrong directory, but I didn't have a chance to remove it and try again before I had to go to work.
[Fire HD 8 and HD 10 General] sakibstark:
any updates?
[Fire HD 8 and HD 10 General] DragonFire1024:
From the optimized firmware thread I posted earlier.

https://xdaforums.com/hd8-hd10/development/rom-t3929969/post79762195

@GuyInDogSuit This is really cool. Kinda like the successor to @DragonFire1024's ROM. Only the WiFi works.

Me: Only because we had figured out the problem. I haven't continued because without most of my hacks aren't working anymore. I've been hard at work trying to build a rom. One of us is building lineage while I've been trying to setup aosp. The issue doesn't appear to be the rom itself, but the kernel that's built with it. This kernel has us stuck on lollipop indefinitely unless the amazon eco system can be replaced in the boot image. That's what I suspect our problem is. Without a new rom, it can't be removed or no boot. We can't remove it with fireos or no boot. And since we haven't been able to build a kernel that doesn't have Amazon's ecosystem, that boots, were really have no where to go yet. Rest assured we are working on this daily. We have what we need. It'd just a matter of getting it all to work together.

Add: if there's any way to repartition anything or we can build a ramdisk from scratch, I still have the kit that allows us to do just that. Other issues stem from Amazon not sticking to the plans so to speak. Their diversion and placement of key files and directories is also a huge problem.

---------- Post added at 12:46 PM ---------- Previous post was at 12:34 PM ----------

The thing is, we can build a standalone kernel, from source (Amazon's and the other source we have for nougat) but neither lineage or aosp will build a proper boot.img and or kernel. In my case, it won't build one at all. No matter where I put the files, or modify the script, aosp refuses to build mkbootimg, recognize the kernel image and won't build it. So after painstakingly going through numerous .mk files of various devices for several hours, I think I have the system built for 5.1.1. im just waiting for it to finish. It's not Pie or nougat yet, but if it works, it's something.

The nougat lineage build flashes the system but either doesn't flash the boot.img or the img is not built right. So as soon as we can figure out what in the ramdisk is freaking out, we'll be golden. I just hope it can be done an Amazon didn't do too much damage that we can't rebuild it otherwise we may be **** out of luck on this.
[Fire HD 8 and HD 10 General] DragonFire1024:
I have a good feeling about this build. It's going to actually finish this time....the rom that is. I have no idea how long it has left to build but it's not long.
[Fire HD 8 and HD 10 General] x8LHiiIB:
You can do it!!
[Fire HD 8 and HD 10 General] DragonFire1024:
I spoke way way too soon. So now I've run into a problem of it doesn't seem like we have the entire source. There are clearly some library files missing including one in the shared libraries called roughly libandroid_runtime.so. now that file seems to be one of the only ones that don't pop up where it's supposed to towards the very end of the build. Now it's supposed to be brought over from the source files I assume. But I can't find the reference to it in any of the make files. So the question is is where is it being called from and since I have the entire source code downloaded why isn't it being pulled up? I have a build about the finish up quite soon which will most certainly fail with the same error. so I will just do a copy and paste in a little bit when it's done and hopefully somebody will know what it means cuz I can't find anything about it and anything I've tried doesn't seem to fix the problem.
[Fire HD 8 and HD 10 General] DragonFire1024:
So after many hours of searching it seems that a few library files did not make its way into the bunch. After searching the internet for what seemed like hours I finally was able to find the solution that is allowing the build to continue. Whether or not it will flash is an entirely different story. For now until we can get a workable kernel we will still be stuck on lollipop, but if it works it's better than what we have now.
[Fire HD 8 and HD 10 General] TheLoonyRebel:
If this at least let's us finally get rid of that awful Amazon theme.... bring it on!
[Fire HD 8 and HD 10 General] DragonFire1024:
I had to head to work before it finished or broke, so won't be able to see what happened until tomorrow.

Also I'm looking over the device source make files here https://github.com/Goayandi/device_mediatek-mt8173/tree/aosp-7.0/mt8173 and they are practically identical (some things are missing from my make files). Looking at the BoardConfig.mk, you can see why GPS isn't working. The order to build the source components was removed from makefile. Because I've already built a kernel, I already know the connectivity chip combo etc match what I've already been saying. The link also shows we maybe missing a few more configs too. Also I have come down to realizing a lot of my errors, that I know aren't missing files, are missing dependencies. There are no recent guides that contain an updated list of them (not even aosp site lists all of them). So we'll see what happened when I get home
[Fire HD 8 and HD 10 General] DragonFire1024:
Well we have a build. But it didn't flash. I don't have the logs with me right now so I can't post any. That'll have to wait until tomorrow. No at this point I'm a deer in the headlights but aren't the files you spread and vendor supposed to expand out into the system folders? Because none of those files made it into system/bin or /lib etc.
[Fire HD 8 and HD 10 General] TheRealIntence:
/system/lib should contain a lot of shared objects files and other sub directories. There should also be a /system/lib64 folder with .so files Beside the /system/lib folder for 64bit libraries. The lib folder should exist in the mounted system root directory but not in the root directory itself.

I'm waiting for the logs :)
[Fire HD 8 and HD 10 General] DragonFire1024:
So I just made this discovery I don't know how significant it is if at all. I was looking through the hardware profile of my xt907 Droid razr when I noticed a familiar set of numbers.

xt907: ak8963

HD10: akmd8963

Magnetometer

They are the same drivers in both devices. So why does fire OS contain some kernel drivers/modules in system/bin? if you try and execute similar ones including that one from a terminal or command line it does nothing not even a single line of code of anyting. So they're not even executable now the question is are they even binaries to begin with OR are the drivers themselves actually binaries and why the heck are they in the system bin

This could explain a great deal about why I get so many driver errors while building the kernel. Anyone have input?
[Fire HD 8 and HD 10 General] TheRealIntence:
Why do you even try to execute it?

I don't know the exact reason why Amazon pulled it in the bin directory since it's a library but I'm sure they have their reasons. Here is the actual source of the driver: https://github.com/andr3jx/MTK6577/tree/master/mediatek/source/hardware/sensor/lib/akmd8963

This one might be useful for your driver problems:

https://9roms.blogspot.com/2017/01/guide-system-base-cross-chipset-mt675x.html?m=1
[Fire HD 8 and HD 10 General] DragonFire1024:
Because I've been trying to get it to work for months and couldn't figure out why it wouldn't. Nonetheless it explains a lot about why I can't get those sensors or the sensor hub to work or even get anything to detect them.
[Fire HD 8 and HD 10 General] TheRealIntence:
I appreciate your efforts but you should really start learn how things work instead of just tinkering around. It safes you a lot of time and will make your life easier.
[Fire HD 8 and HD 10 General] DragonFire1024:
I appreciate honesty, but that is how I learn. That's how everyone used to learn. You think Einstein became who he was by NOT "tinkering around?" Someone once said you never fail at something. You just learn X amount of ways NOT to do something. If I hadn't of tinkered around these past 4 years or so here, I wouldn't have accomplished all I have thus far. Not everyone learns on the same level. I learn a lot quicker and faster and can accomplish so much more by tinkering around than I ever will sitting down in a classroom.
[Fire HD 8 and HD 10 General] TheRealIntence:
Don't wanna make this too OT but you misunderstand the concept.

You don't have the base to try anything. If you have little or no idea of basic concepts, such as file systems in Linux and Android, or to understand configurations for compiling roms, there is no point in wildly trying around. I'm sorry to have to say this, but you haven't used your 4 years well when I see what you're failing or what you're trying to do. Get away from blind trying and sit down at the computer and read through some articles or books. Learn something about the Linux kernel, the Android architecture, and anything else that might help you.

Of course, trying is more fun than torturing yourself with any text, but learning by doing should not be the first and especially in your case not the only phase of learning.
[Fire HD 8 and HD 10 General] TheLoonyRebel:
Jesus Christ on a pogo stick. DragonFire is taking his time to learn how to do all this and shares his hard work with us for free and all you can do is criticize how he learns how to do developer work. SMH.
[Fire HD 8 and HD 10 General] violentx:
[deleted]
[Fire HD 8 and HD 10 General] Rortiz2:
You're right, but TheRealIntance is not like Legitsu. He has said it very well but Legitsu said it insulting.

AND PLEASE (IT GOES FOR ALL NOT FOR YOU): STOP DOING OFF-TOPIC AND STOP DISCUSSING
[Fire HD 8 and HD 10 General] TheRealIntence:
A few words to end the discussion. I don't criticize DragonFire because I'm ungrateful or have bad intentions. Instead, I want to help him. But I'm sure he knows that too. I see him trying harder than anyone else and he has more than potential. But I also see his supposed weaknesses and his gaps in knowledge, which can't all be fixed by just fiddling around. I can't understand why someone criticize me for this.
[Fire HD 8 and HD 10 General] Rortiz2:
I understand you and I think more or less the same as you. In the world, people can misunderstand many things and take them badly, believe me, it has happened to me more than once. At no time neither you nor I, nor any other person (except legitsu) have disparaged the work of DragonFire at any time nor have we insulted it. (Well, Legitsu done it). I liked your way of answering since you said it very clearly and without insulting. Unfortunately, not everyone knows how to respond in a normal way ..
[Fire HD 8 and HD 10 General] DragonFire1024:
Anyone on XDA who has done a significant amount of work on devices, knows the 'failures' greatly exceed the accomplishments. 4 or 5 yeas ago I didn't even know what the framework was. Now I can modify it and most android applications on a level most people don't even bother with anymore. Whatever time isn't spent tinkering is spent reading. I have so many bookmarks. I would estimate the amount, but you wouldn't believe me unless you saw it. I spend hours, sometimes days reading and trying to find solutions. Sometimes those solutions take less than a few seconds. It's quite hard to critique someone in the positions we are in (divided by electronics), having no knowledge or insight of the individual(s). We as humans have become so reliant on electronics, books and what not, we forget none of those assisted us in our early evolution. The early human inventions all came about by tinkering.
[Fire HD 8 and HD 10 General] c6z06vette:
Dragonfire1024

Keep doing your thing your way. I agree 100% that tinkering is the engine of success. Don't let those who just criticize stop you from doing your thing your way!

I've read and appreciate your hard work:cowboy::good:
[Fire HD 8 and HD 10 General] TheLoonyRebel:
I'm sorry if my previous post was harsh towards you. I've seen way too often around here on XDA where devs gets criticism for stupid things so I finally lost it a bit after seeing your post. I'm trying to learn how to do a few basic things like building an kernel but so far not having much luck. I'm stumbling towards getting the kernel source for the Nexus Player (Fugu) to download to the directory I want it to go to. From there I want to add Exfat and NTFS support as the stock kernel on the last OTA released is lacking both of these.

Eventually I'll figure it out. Eventually.
[Fire HD 8 and HD 10 General] siochs:
Guys, I am following this thread for quite a while and I have the feeling it is getting somewhat emotional now.

From my point of view, "learning" is something totally individual so please do it the way it suits you best :)

I am impressed of all the time and passion DragonFire puts into this project, so please keep going :good:

By the way, I am willing to contribute somehow. I would like to reproduce your build, but some things are not clear to me or are scattered around this thread. It would be nice to have a compilation of what your have right now:

- Which kernel source(s) did you use and did you merge them to upstream?

- Which module(s sources) did you enable/use for build?

- Which environment options or arguments did you use for build?

- Any further steps to bring the kernel into the ROM.

I have some good hardware around and some really nice collegues which might support me to reproduce your build.

If this question is out of scope or just too much to answer, please ignore this post.
[Fire HD 8 and HD 10 General] DragonFire1024:
Here are the sources I have. If anyone can expand on them...

TWRP device tree for Amazon Fire HD10 (2017) https://github.com/chaosmaster/android_device_amazon_suez

Kernel source https://github.com/chaosmaster/android_kernel_amazon_suez and https://www.amazon.com/gp/help/customer/display.html?nodeId=202194760

MT8173 Source https://github.com/Goayandi/mediatek_mt8176_development

Device tree https://github.com/488315/android_device_amazon_suez/tree/cm-14.1

Proprietary https://github.com/488315/android_vendor_amazon_suez

Kernel patches https://github.com/488315/Linux-Patches

Possible portable ROM, stock Hi9 tablet (nearly identical to our build) android 7.0 https://drive.google.com/file/d/1mneBbR8eYceXrqxgVbBa6bBLZm7J7NTp/view?usp=sharing

MT8173 Kit to make an LK, bootloader, preloader and boot.img https://drive.google.com/file/d/1i_xcl1RQwHJVLBvX3uDVFlcddcaLp8mf/view?usp=sharing

I'll upload to github what I have been working on in terms of a ROM. I am reformatting my make files (they were bad) and it will take a hot minute.
[Fire HD 8 and HD 10 General] DragonFire1024:
Just giving a general update. I am almost done reformatting the makefile(s). There's a lot we have to import from the vendor area. and again because a profile to this extent has not existed for this device I'm stuck with making it all from scratch.

There were some other things that I wanted to see if I can add in terms of mediatek proprietary applications that will allow for certain features to exist on a possible lollipop ROM that would not otherwise exist on a lollipop ROM. For some reason, in all the sources we have for this particular mediatek device, they do not seem to contain their proprietary applications, aside from ones that would normally be in the LK (fastboot et Al). That will take a minimum amount of time to add the device make file. The longest process is just simply adding all the lines of all the enormous amount of stuff we have to import from the rest of vendor. It weren't for that this would have been done long ago.

Now that I have the next few days off I can focus on finishing that up and and making sure everything is in place to try another build.
[Fire HD 8 and HD 10 General] TheLoonyRebel:
Best of luck [MENTION=8165603]DragonFire1024[/MENTION] it sounds like trying to clean up and fix the Amazon kernel source and the rest is a bit tiresome but I'm not shocked either. Reminds me a lot of the Hisense Sero 7 Pro tablet which had some really badly compiled kernel sources provided by Hisense.
[Fire HD 8 and HD 10 General] DragonFire1024:
Well here in lies another problem. most of the sources that I've seen for a mediatek device have their system layout quite a bit different. For example the proprietary binaries and files in their more 'common' ROMs sit in the vendor directory. This is literally the only OS I've come across that puts those files in the system directory. Not sure how that effects a ROM build for other versions of Android (I have looked at 7 and 8 and older ones too) as those files are in system/bin or system/etc (the files mirror the system directory so if binary A is in vendor/etc, on the HD 10, file A is in system/etc and so on). Of course that's just speculation since I can't get a ROM built yet. One could go about it manually and place those files from system to vendor. I had previously done that with a few of the sensors and I don't recall the results/effect if any, but the tablet was still booting so that's definitely a plus.