yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] DragonFire1024:
So just an update of what I've been doing. I'm trying to get us off of the current kernel we have and onto something new. I've essentially been trying to build one from scratch. Which is going well, except for a few things and errors that I can't figure out. so it still seems like I'm trying to accomplish The impossible. The latest one being something along the lines of:

"No rule to make .config needed by out/target/product/suez/obj/KERNEL_OBJ/.config"

I know it's looking for suez_deconfig which it clearly finds, and build the kernel according to that configuration, builds the said modules, then proceeds to tell me that it can't find the configuration that it just built the kernel from. so I'm assuming it has to do with where that configuration is going after the kernel is built, which is clearly not in the place it should be. So I need to know what I am missing in my BoardConfig.mk that should send that file to where it needs to go. Because at this point after all is said and done really the only thing left to do is build most of the applications. I have been able to get past all previous errors which have been errors of my own. This one isn't necessarily an error but something I am missing. not much comes up in the terms of a Google search and what I have found I have incorporated into the BoardConfig if needed or seemed a logical, but clearly did not help since I am asking this question. any guidance would be greatly appreciated so I can finally move on to the next step.
[Fire HD 8 and HD 10 General] DragonFire1024:
So I have finally surpassed all the errors and everything has continued to build. So at this point the kernel is built, and a significant portion of the applications are built and that's pretty much all that's left. now assuming I have finally got it right this time it should be just a hour or so and we'll have another ROM on nougat, with a full blown CM kernel.
[Fire HD 8 and HD 10 General] thejoker954:
Wow, if you get that kernel working that would be amazing. I like my hd 10, but Amazon's hack job of both the kernel and the os makes using it (even for basic stuff)a pain in the ass.

I'm glad you haven't gotten discouraged.
[Fire HD 8 and HD 10 General] DragonFire1024:
Hey [MENTION=5749760]ggow[/MENTION] what are the odds my kernel for cm/lineage 14 would work on your rom?
[Fire HD 8 and HD 10 General] azuremoonbeam:
DragonFire1024 any update on your rom and kernal? its like the bad critics chased you away....
[Fire HD 8 and HD 10 General] Spektre99:
If you have an Fire HD 10 (2017) what are the current options for putting a more stock Android on the tablet? I read a LineageOS version was available but the ones I've seen here in the forums specifically state not for the HD10. If a ROM exists, how is the experience? Is most everything working?

Thanks.
[Fire HD 8 and HD 10 General] Michajin:
Not sure if you are reading right in the threads here. There are 2 very stable...

Lineage 12.1

https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677

Lineage 14.1 (needs a couple tweaks and patches, but stable) No camera or disney+ though

https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-14-1-t3973703
[Fire HD 8 and HD 10 General] HagardoVesrozy98:
Is this project still on-going or hiatus(somehow dead but nope)?
[Fire HD 8 and HD 10 General] DB126:
Look at recent post dates (especially from the OP) and draw your own conclusion
[Fire HD 8 and HD 10 General] azuremoonbeam:
any chance that the original pie rom that was being worked on could be fixed with the help of https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-17-1-t4134829?
[Fire HD 8 and HD 10 General] DragonFire1024:
There are than just a few little things wrong with it. A lot of things don't work like the camera and the headphone jack, video issues with codecs, animation issues, rendering issues which in some cases make up look like the screen is messed up when it really isn't. So far as I know there was only one version made of pie for this device. If anyone tried to work on it or update it on their own, I don't know. In regards to some of the hardware issues, in order to see why some things don't work you have to go on order and do the process of elimination and figure out what's compatible and what's not in terms of the code. For example on this very tablet I am replying to you on, the Google Nexus 10, NFC and the camera cease to function after Android 6 (marshmallow) because of incompatibilities in the hardware code which have not been updated for several years so I am hunting down each error and attempting to correct them as I go.Unless you have a quick fix this could be a very tedious and long process, assuming it can even be fixed.
[Fire HD 8 and HD 10 General] azuremoonbeam:
i was thinking if people waaaaay smarter than me was to look at the new pie rom i linked for hd8 and could see where amazon moved stuff to work in there version since i think that hd8 is based on a fire version of pie that was how the where able to update it to los 17.1... specially you DragonFire1024 since you where trying to figure out where to code files to work where amazon put them so you could succsefully compile your rom and kernal.... like reverse engenier... (i suck at spelling)...
[Fire HD 8 and HD 10 General] DB126:
It's all about the kernel which generally isn't open source and always hardware specific unless packaged otherwise (which it usually isn't). As Dragon pointed out, high effort with good chance of poor outcomes. Best suited to someone with waaaay too much time on their hands.
[Fire HD 8 and HD 10 General] DragonFire1024:
The kernel in which Amazon did a good job at butchering. Nonetheless, the hardware code on devices especially lower end ones often is neglected and isn't regularly updated. Therefore hardware code becomes "incompatible" with the software code. This isn't so much about smarts as its More of we weren't given the entire source code by Amazon. I don't understand why given as far as I can tell, and I have pretty much dissected the HD 10 as much as it can be which reminds me to post an image of a piece of computer board I found underneath one of the severely busted monitors on the HD-10s I own, Amazon doesn't own any of the hardware on these devices. so why they're fiddling around with removing bits of source code that's not theirs I will never begin to understand and don't really want to in this case. In this specific case, unless somebody like [MENTION=5749760]ggow[/MENTION] Can figure it out just by chance, and buy a lot of time of just reading code over and over and seeing the same things across your screen until it makes sense, Android 9 is going to be way too far out of reach for these tablets. At least in my opinion too far out of reach to make even the average person happy enough.

I am just finishing some work on a Walmart tablet that I inherited. It's a shame that we can't find some way to activate treble on these HD 10s or any of the Amazon tablets. Is that what allow us to modify and flash a generic system image or GSI with virtually no hardware problems. Those Walmart tablets are also MediaTek, and I have been flashing this tablet with dozens of system images over the past week trying to get just a couple to work (when I say work I mean boot) before I finally had success with everything workingincluding the camera and headphone jack and audio and video. That would make life so much easier for developers and with a lot less chance of having broken things.
[Fire HD 8 and HD 10 General] DB126:
Amazon customizes for the target audience which is decidedly not Android enthusiasts looking for an all purpose gizmo to hack. They have no obligation to release source code other than FireOS which is a Android fork. Walmart Onn series is a better fit for tinkers; very workable within the confines of code base which is largely generic. Oh yeah, no source code there either.
[Fire HD 8 and HD 10 General] DragonFire1024:
Yes I know I know. My point is if you're not going to release the entire code why release part of it? Just don't release any of it. And if you're going to release some of it, don't butcher it otherwise there's just no point. Treble would do wonders for these devices. And would solve almost all of those hardware issues we have on newer ROMs for these. But I digress and onwards we move.
[Fire HD 8 and HD 10 General] DB126:
Unfortunately, that's not the way the world works.
[Fire HD 8 and HD 10 General] FireSlayer_SD10:
Apparently linux kernel version 5.8 fixed the mediatek mt8173 display bug. What is the chance that we could base a new build for the hd10 on Android 11 and linux 5.8? https://www.collabora.com/news-and-blog/news-and-events/kernel-5.8.html
[Fire HD 8 and HD 10 General] ffstudios:
I will listen to the people who have not yet bricked their device :p There are other people trying to do this that seem to think AOSP is close at hand and I support their efforts to make it happen
[Fire HD 8 and HD 10 General] GuyInDogSuit:
I haven't even attempted the bootloader unlock yet because of the risk of bricking at this point. I'm honestly freaked out at the thought.
[Fire HD 8 and HD 10 General] bibikalka:
This is hard to believe. I flashed system bunch of times in the past, using only FlashFire (pre-unlock) !!! In fact, there is a thread about that:

https://xdaforums.com/hd8-hd10/general/hd-10-2017-prerooted-xposed-image-t3772022

Btw, if you need to do a bunch of stuff, you could just write a shell script, so you don't type it manually ...

Yep, there is hope! And, there is a similar device with Oreo Lineage - so that could be a nice example to follow!

The unlock procedure is benign, and fairly light in terms of user involvement (other than getting Ubuntu set up properly!). Also, there is no need to go into BootRom, which was one of the trickier parts. A bit of a downside is the unavoidable factory reset - but that's not a big deal. Btw, I have not seen before such a high quality of instructions as those provided by [MENTION=7104332]k4y0z[/MENTION] ;)
[Fire HD 8 and HD 10 General] DragonFire1024:
You know how long I've been trying to get this to work? You know how many times I've had to reset the tablets? On the 3 years I've been at it, I've lost 2 tablets to my tests. When you literally have to assemble a rom from scratch, while assuming you even have the entire source, you risk losing a device every single test flash and it has nothing to do with how smart you are. I can literally hack the framework on pretty much any Android. Stuff like this comes at a cost. That's a heck of a good track record After 3+ years and bricking only 2 of the dozen or more devices ive modded in that time. A lot Better than some Ive met.

---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------

Some people are. And that's perfectly normal. For me, this has been nothing but fun. I knew the risks when I started all this and it didn't bother me because if I were to ever to achieve my goals when I came to xda, the fact was and is, you're going to eventually run out of luck.

---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------

Flash fire only fashes the partitiona with imgs. Basic flash zips are only flashed at the /system level.
[Fire HD 8 and HD 10 General] k4y0z:
I haven't heard of any bricks that were the result of the unlocking.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Maybe I'm just paranoid. There were two people that reported being bricked or otherwise stuck, one being DragonFire1024 and the other... forgot his name. But maybe I misread into it.
[Fire HD 8 and HD 10 General] k4y0z:
I don't know how DragonFire1024 got bricked, but it wasn't the result of unlocking.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Is there any way I can back up my internal storage app data? I've downloaded/synced a bunch of stuff (anime/TV episodes and comics/manga) and don't want to have to do it all again.
[Fire HD 8 and HD 10 General] k4y0z:
I suppose something like Titanium, FlashFire or just creating a tar.gz from /data would work.

But I haven't tried any of these.
[Fire HD 8 and HD 10 General] tylerhole:
If you're able to install it and have it work, Samsung smart switch is pretty solid for backing up internal storage.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Wouldn't that require something with root access, though? The /data/data folder isn't usually easily accessible to non-root applications.
[Fire HD 8 and HD 10 General] k4y0z:
Yes it would:

https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595/
[Fire HD 8 and HD 10 General] GuyInDogSuit:
I've already got perma-root, though, for now.
[Fire HD 8 and HD 10 General] tylerhole:
Oh my bad, totally had misread what you were backing up.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 General] Dan_firehd:
If you have root, then Titanium Backup Pro will easily backup all user APP+DATA and restore them later on to a brand-new-factory-reset system.

Both complete backup and restore of all user APP+DATA are easily done in Titanium Backup Pro.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
So you're saying that it will backup the 2 GB+ files I have downloaded via VRV and whatnot?
[Fire HD 8 and HD 10 General] Dan_firehd:
I have used Titanium Backup Pro to transfer 6GB+ of user APPS+DATA from one tablet to another, as long as both are rooted.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
I mean 2+ GB from a single app.
[Fire HD 8 and HD 10 General] Dan_firehd:
No experience about such a large file. However, I don't see why Titanium Backup Pro would not work on such a big data file.
[Fire HD 8 and HD 10 General] DragonFire1024:
Ok so there's Hope in using a system.img. I've finally been able to add files/folders to a img, after looping it on Linux and setting proper permissions, but you can't use the desktop interface. Files and folders can only be copied, and it has to be done in the terminal. Tedious I know, but the good thing is, you can use the desktop interface to delete files/folders in the mounted img. Now there's a question I have. On the Fire 7, there's hacked fastboot. I assume that can be used to flash imgs too? I'm going to be getting a replacement HD 10 today this afternoon.

So I don't have to reply to a dozen threads, it's unclear why I bricked. I didn't get a chance to recover any logs before it just shut off and defaulted to preloader mode. It definitely was not a result in unlocking the device which went really smoothly for me once everything was in order.

I assume my brick has to do with the rom testing I was doing, however I would think that rebooting after a flash in TWRP would have started the brick. Not after the tablet rebooted and was working fine given the circumstances. It also could've been a combination of my hacks. I did have a few su.d scripts in place that could've contributed to it. Such as my device_unlocked and selinux permissive boot scripts. If anything, given all the testing I constantly do, a lot of it on device, I should've reflashed to stock before I unlocked.
[Fire HD 8 and HD 10 General] DragonFire1024:
Update: so it's not the HD 10 (mine arrives tomorrow) but this is the best results I've had for the fire 7 ford. I have been able to deodex, root and add busybox to the stock Amazon update.bin (changed to zip). Successfully created a flashible zip and flashed it. Guess what....it booted ???

I was able to do all of that, including other things, using SuperR's kitchen. It's still being developed so that's a huge plus. Now I don't know the extent of it's capabilities in terms of building an actual rom. I imagine I can simply add few things from the stock rom like the system.prop and partition details to the build templates in AOSP, run a basic build without a kernel, and use the output like apps and framework to build a basic rom for whatever Android version, in SuperR kitchen.

It also creates a system.img.
[Fire HD 8 and HD 10 General] bibikalka:
Cool ! [MENTION=7104332]k4y0z[/MENTION] will be happy to hear this - otherwise unlock+bricking in the same post may scare some noobs :D

Awesome to see you getting back in the groove!!! Don't brick the new HD10 too fast ;) Take your time !!! :D
[Fire HD 8 and HD 10 General] tylerhole:
I know a few ROM devs who rely heavily on SuperR's Kitchen because of how powerful of a tool it is. And yes, it is still being developed, he pushes out updates rather frequently.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 General] bluedisc:
any chance of lineage os on this tablet?
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Not likely any time soon. Amazon borked so much in their sources that we'd have to dig really deep and risk bricks to get it working. That said, it's not impossible. Just not as soon as we'd all hoped.
[Fire HD 8 and HD 10 General] Rortiz2:
Up for this thread!

I do not know if it will help but I'm working on compiling Lineage13 for a tablet with MT8163B. The processor is very similar to the HD10 2017. I leave the device tree in case it helps: (It is not finished yet)

https://github.com/R0rtiz2/android_device_freezerfhd

Regards!
[Fire HD 8 and HD 10 General] DragonFire1024:
I've tried so many, and the vast majority of ROMs for mediatek chips, are almost as annoying as they are. Some are straight up questionable and am glad I never owned a 4 dollar China phone, but have been begged to fix a few. With that said, it's not the mediatek ecosystem I'm having trouble with. It's getting away from Amazon's that's proving even more difficult. Some things they implemented their "own features" where as most of the time leech off android. So their configs for everything are spread from one end to the other. Some of it doesn't make any sense at all. That said, it also looks like a lot of the basic modules like step counter, compass etc, all have driver support, just nothing is loaded. I'm looking at the list now and nothing is selected. I never knew a kernel had so many modules and options. if we really can rebuild this, it looks like a really sweet kernel. Looks pretty loaded. Despite the frustration, this really is fascinating.

---------- Post added at 01:13 AM ---------- Previous post was at 01:03 AM ----------

I already suspected as much and so far really, I haven't been surprised at the kernel. There are a lot of options. I just got done recovering from a weird half brick. Somewhere I got boot images mixed up between this tablet and the two sources I was playing with. If it weren't for the weirdness like I had adb in recovery not during boot. Would only charge on PC not outlet. I think it was [MENTION=7104332]k4y0z[/MENTION] that said something about a boot img... just flash the stock one if you're unsure. Sure enough...

---------- Post added at 01:20 AM ---------- Previous post was at 01:13 AM ----------

Ok and update on my work: I finally got meta data to flash the device in a few rom tests. It's not pretty and to be honest, I was surprised it even booted. Amazons ecosystem bites the dust. However everything goes with it eventually. Anything tied into the Android system, follows with amazon. Whatever they did to the system, meta data will not work. The tool won't let me use perm. So the only options at the moment are ext4 image and sparse image, or sparse data. The latter is what amazon uses. Meta only works on earlier tablets.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
I'm not sure what that means for us, but it doesn't sound good. Any progress with the other methods?
[Fire HD 8 and HD 10 General] DragonFire1024:
I am not sure if its a script within the tool or what, but when I go to actually rebuild the ROM into a zip, the tool readds some of the removed files and removes some of the files/folders I added. I've tried to track down the reason without having to post to their help forum here, but I have no choice. That's one of the causes of my issues the past day or two.

Second, I can confirm if you go back to stock, you have to go back to the most recent fireOS. It took me hours to figure this out. I was trying to go back to complete stock and everything worked up until I would get done reflashing firmware only to be stuck at the infinite black screen. Half that time was spent thinking the battery died (it was very low at this point). I imagine if you totally go back to it, you can downgrade brick and run the other unbrick tool to repair it and get to still be on the older version? I really do not like 5.6.3.0. Also when you have tons of ROMs laying around, for various devices of very different nature, don't get boot images mixed up while trying to fix the system you broke again. I really have to thank you guys for all this. I never hesitate to put a device up to potentially sacrifice and most of the time that's what happens. So its very cool to see them come back to life after taking one for the team while seeing how its all done. Its because of xda I've never managed to permanently brick a device I have owned. To that end I've been lucky.

One more note. Not sure if this matters, but inside the kernel, amazon left a readme on how to build it. They used libraries from aosp_flo-userdebug which is supported in the repo. What would be the chances of us being able to use anything from that branch (aosp_flo)?

---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------

Also I saw a post you made about an optimized stock ROM LVY48F. I thought I've seen you before https://xdaforums.com/nexus-6/development/rom-lvy48f-stock-rooted-decrypted-kernel-t3199075 what are the chances you still have it? The HD 10 system image base is LVY48F. The only ones google has it a Motorola image. I need something closer to aosp with little OEM mods.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
I don't have that phone anymore, so that file is long gone, sorry.
[Fire HD 8 and HD 10 General] DragonFire1024:
Damn. Could've been a find. What was the phone?
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Nexus 6, I think?
[Fire HD 8 and HD 10 General] DragonFire1024:
Lol nice. Yes that's the base system image of our FireOS, the Nexus 6, project fi. Funny choice for amazon given something is just not right with their wifi. I just wish I could find an image that wasn't so destroyed by a carrier or what not.
[Fire HD 8 and HD 10 General] Kaijones23:
There’s the tree on googlesource. https://android.googlesource.com/device/asus/flo/
[Fire HD 8 and HD 10 General] k4y0z:
Just dropping this here...
[Fire HD 8 and HD 10 General] phanguy:
go on... how usable is what you have so far?
[Fire HD 8 and HD 10 General] k4y0z:
Not usable at all :p

It's more a POC right now.
[Fire HD 8 and HD 10 General] phanguy:
well still congrats on the progress! i'm down to do some testing if that is helpful to you.
[Fire HD 8 and HD 10 General] DragonFire1024:
Ha. I was just talking about this and the fact amazon used some of the code from Flo. Hell now I wonder if we can just try and get a LVY48F (Nexus 6) system image that hasn't touched a carrier or other OEM, we might get something built out of the two.
[Fire HD 8 and HD 10 General] phanguy:
https://androidmtk.com/download-google-nexus-stock-rom-models

does this help?
[Fire HD 8 and HD 10 General] Kaijones23:
How would you successfully compile this rom? I’m having a hard time compiling it for fire hd 8 2018. Sorry if it is not in this topic
[Fire HD 8 and HD 10 General] Mahmud92:
:fingers-crossed::fingers-crossed:
[Fire HD 8 and HD 10 General] k4y0z:
Compiling it wasn't really the issue.

It was getting it to boot and show something on screen that took me a while.

On the HD8 it should actually be easier, since it is an android nougat device, while the HD10 is still on lollipop.
[Fire HD 8 and HD 10 General] Kaijones23:
Well I keep getting compling issues like KERNEL_MAKE_FLAGS and generated_kernel_includes with a patch. I’m having a problem compiling :/. And I’m using prebuilt kernel because this device has an kernel based on arm and my tree is on github and I successfully compiled an AOSP rom for it

---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------

I’m having problems with lineage
[Fire HD 8 and HD 10 General] Rortiz2:
LOL.