yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] k4y0z:
What android-version are you compiling?

If you use the prebuilt kernel you probably cannot go beyond Android Nougat.

I had to patch the kernel and build from source to get Pie to boot.
[Fire HD 8 and HD 10 General] k4y0z:
I don't know what is wrong with your source.

But why do you want to build 32-bit? the SOC supports 64-bit.

You can check here, what patches I merged in the kernel:

https://github.com/chaosmaster/android_kernel_amazon_suez/commits/lineage-16.0

You probably don't need all of them though, since your kernel is already nougat-compatible.
[Fire HD 8 and HD 10 General] Kaijones23:
Well I can use 64 bit anyways but I tried cleaning out the source and repo sync it and it still doesn’t work I think that there is something wrong with my tree. And I think that file went missing during the build and I don’t know why. I had tried to rebuild the tree and look at other sources. When I build AOSP the profman error happened too. I think it’s missing a file called boot.prof
[Fire HD 8 and HD 10 General] DragonFire1024:
Anyone have a link to their working tree?

Edit: nevermind I got it.

Edit 2: I have tried every android version up to 8. I am not a fan of nougat or Oreo. marshmallow is growing on me, but if I had a choice to stick with one forever I would go with KitKat. I was really disappointed with 7 and 8 so I would like to be at least somewhat impressed with 9. I would love to see this tablet with multi window or split screen without having to use Xposed. I wish the systemui setting worked for tablet mode and the stock recent apps too. That said, I would like to see the full capabilities of the current kernel or whatever base we build from. Has anyone chosen a source?
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Pie is pretty amazeballs. I have it on my Samsung Galaxy S8+.
[Fire HD 8 and HD 10 General] tylerhole:
Yeah I'm running it on my s9+ and it's pretty killer. That would be insanely awesome to see pie on these tablets.
[Fire HD 8 and HD 10 General] DragonFire1024:
Speaking of new ROMs and etc... Has anyone grabbed the new update yet? Really would like to see what's inside it and at least offer a pre-rooted version if possible.
[Fire HD 8 and HD 10 General] Kaijones23:
I had an update and i currently have an toot for fire hd 8 and does anyone has a proper device tree for suez that I’d like to copy and use it for fire hd 8?

---------- Post added at 09:15 AM ---------- Previous post was at 09:09 AM ----------

Well I think this will solve the compilation issues and I hope it works in the morning.
[Fire HD 8 and HD 10 General] Rortiz2:
Have you found the sources? Can you share them?
[Fire HD 8 and HD 10 General] chivoyage:
Oh my! *tells self to calm down*
[Fire HD 8 and HD 10 General] DragonFire1024:
I'm going to try the tree [MENTION=7104332]k4y0z[/MENTION] has, and build from the source I tracked down a few months ago and see if I can't modify Amazon's kernel. As far as I know those are the only known and most complete sources we have right now.
[Fire HD 8 and HD 10 General] DragonFire1024:
In /system/data/misc is a ProjectConfig.mk and it has yes no values for what appear to be kernel modules? I attached a zip of it. What would it be for and can we use it to our advantage?
[Fire HD 8 and HD 10 General] Rortiz2:
This file is available for all MTK tablets and mobiles. It is usually added to the device tree.
[Fire HD 8 and HD 10 General] ggow:
Nice :)
[Fire HD 8 and HD 10 General] GuyInDogSuit:
I linked to the latest update in the amonet thread. I even tagged you.
[Fire HD 8 and HD 10 General] DragonFire1024:
Sorry I didn't see it until now. Thanks. Though no Miracast.
[Fire HD 8 and HD 10 General] phanguy:
I think I managed to find the file you were asking about if you still want it? Had to poke through some Chinese sites to get it, but it seems like it's the one.
[Fire HD 8 and HD 10 General] Legitsu:
fireos is garbage I wouldn't waste any effort on it

wait for LOS then you can go ham

I know a couple people have it booting its just a matter of time

there are kernel sources for ASOP 7.0 floating around for various MTK8176

chipsets
[Fire HD 8 and HD 10 General] DragonFire1024:
Sure. Just upload it and link it

---------- Post added at 04:01 AM ---------- Previous post was at 04:00 AM ----------

This is mt8173. Yes I know they are nearly identical.
[Fire HD 8 and HD 10 General] Legitsu:
typo I meant mt8173

and any of the MT81xx kernel trees should boot its just a matter of board config/drivers

or for that matter anything in the android-mtk trees

if you wanna peek at kanging commits these trees are a good place to start

https://github.com/Goayandi/mediatek_mt8176_development

between the leaked GPD+ sources and the amazon sources eventually we will have LOS

its just a matter of backporting hacking and kanging our way to freedom

fireos is so badly hacked up it will never be a sane android os ever again
[Fire HD 8 and HD 10 General] DragonFire1024:
I have that source already. Unfortunately I think most of it it out of order. I've even downloaded Google's mediatek source and it's pretty sad https://android.googlesource.com/kernel/mediatek/+/refs/heads/android-3.18 not to mention the fact new releases of ndk don't use gcc to compile anymore so I have to setup a new environment with clang. There's also a meditek kernel 3.18 for nougat https://android.googlesource.com/ke...ndroid-mediatek-mooneye-3.18-nougat-mr1-wear. I also don't get why I can't port a full rom (I do get it as the kernel restricts us). I even have a firmware file of another mt8173 rom running lollipop.
[Fire HD 8 and HD 10 General] Legitsu:
you should be asking WHY you would want to port a full rom from another device to a device that has NO vanilla ASOP tree

that is going to go very badly and be very broken,the solution and the best thing for everybody not just this device is to get linage booting and semi-functional. we have the booting part handled now we just need to get the rest of the bits working

altho I would really like to see everybody thats working on it use a public git ahem ahem

media tek sources are messy its gonna take some following the rabbit down the hole

it is not a fun day chasing that particular rabbit but everything we need IS there just a matter of finding it

mainline linux has 8173 support if needed we can kang from there, so does chromeos

also have the heli x20 ASOP sources no its not the same but its a good window into how MediaTek royally ****s **** up err I mean does things
[Fire HD 8 and HD 10 General] DragonFire1024:
We are all working on different aspects of this. I'm not a fan of lineage (loved it when it was CM) and would much rather see AOSP on this than anything else. Porting generally is easier than building from scratch. Im playing around with both options. I find no fun in waiting the few hours for a build only to have most of it fail flashing. From writing the exploit and everything up to this point is a rabbit hole. No one has ventured to this level on these devices in a few years. For now, I enjoy reverse engineering FireOS. With my mods and hacks, the only thing really noticable of Amazon anymore is the visual aspect. God awful colors.
[Fire HD 8 and HD 10 General] phanguy:
pm'd you the link
[Fire HD 8 and HD 10 General] DragonFire1024:
So someone has managed to build a tree of mt8173 for Linux 4.2. I just got done downloading all the necessary resources packages excetera and we have a completed build so we're going to see if this works.https://github.com/ibanezchen/linux-8173. It built a zImage (bzImage)

I did not try going through the whole thing and selecting a bunch of modules and whatnot so I just wanted to see if I could get it built. Now the question I shall I ask is what would I do from here to test it?

---------- Post added at 10:31 PM ---------- Previous post was at 10:29 PM ----------

So I looked at it and it actually looks pretty promising as a system image. it's the same version code/id and I can't believe Amazon didn't actually make an effort to change that. It could work out in our benefit. It's still lollipop, but if it works, at least it gets us off FireOS.
[Fire HD 8 and HD 10 General] DragonFire1024:
Ok so this could or could not be something. For the first time, and I've tried more time is than I can count, I have been able to decompile edit recompile an APK on the tablet itself...and it installed :D I am using apktool x which is the Android version of apktool for Windows/Linux. Now the Android version has a feature which is not really included in any of the other versions. It actually will extract the META-INF from the original APK and then insert it into the newly recompiled one. now on Windows you had to go through a few more steps in order for the APK to properly recompile without it crashing when you install it. So I did something different. Usually you would port over the necessary files from the newly built APK, to the old one. Because you didn't want to disturb the signature. This time I extracted the META-INF and used it in the newly built APK. Before this would almost guarantee you are going to crash. Much to my surprise it was the exact opposite. Why is this important? Because this means I can extract the signature from an Amazon system app to use in a modified one. This can potentially be applied to non system apps. If so, this could be a big open door to install non system apps to system. If you can just reinsert the signature, you can do the same with the manifest.

Edit: this may benefit my framework hacks greatly. I've always suspected there was a way to slowly replace or remove code in an APK and faking out the system at the same time. This may save me from having no other choice built to build from source.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Lollipop or not, it's still better than this ****e called Fire OS.
[Fire HD 8 and HD 10 General] DragonFire1024:
So I don't know why but I can't get a complete build from Amazon's kernel, unless I compile it the way they want, using their script. As such the configs and stuff I made change to, aren't reflected in the build I don't think. However. There is some news. At least I know it can be resigned and installed.
[Fire HD 8 and HD 10 General] DragonFire1024:
Sweet. I've been able to integrate my hacked framework and settings apks into firmware builds. Which means, things work and feel a lot better. Ive read before that stuff like my mods should be flashed with a rom. We don't have one yet but nice to know I can use the superr tool to get a little closer to something. When I release it, the best part is, you'll never have to look at the ****ty stock Amazon desktop wallpaper again.
[Fire HD 8 and HD 10 General] tylerhole:
Woohoo can't wait for you to release it!

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 General] DragonFire1024:
Ok so there are a few errors in the scripts that have to do with the way the files are extracted. sometimes things get moved or things are put into the scripts that just make no sense. I did a few hours of reading and have managed to bypass those errors without issue. I also decided to use another toolchain. Instead of the ndk, I went with linaro. Finally something built without using the included build_kernel.sh script Amazon provides.

Secondly, I spent many of hours trying to add some of or all of the sources we've gathered, into the build. So I started to throw in a few of the modules from the available sources. Some worked, and some didn't. Actually it was 50/50 exactly. Another surprise was resetting the defaults Amazon set. Anytime I removed some of them, it would error the build. maybe it was addidng and overwriting some of the files with the sources reset something because when I went to configure the _defconfig, everything was reset to mediatek factory. I left off going though recusomizing the features, reading the help menu with every single one lol. Hopefully in a few days we'll be looking at our first custom kernel. There's a catch though. We're stuck with what we have until a compatible rom is built. If I build anything from something other than 5.1, it doesn't boot. So the modules that were accept were probably stock mediatek. The other half were excluded because they were "incompatible". I still have a lot more to do though, but I'm closer to this than i've been to building a rom. So far I haven't gotten a build that hasn't booted.
[Fire HD 8 and HD 10 General] k4y0z:
TWRP has been using a custom kernel for a while now.

And I am obviously using a custom kernel for LOS16 as well, since it needs features that aren't available in the amazon sources.
[Fire HD 8 and HD 10 General] DragonFire1024:
Obviously...
[Fire HD 8 and HD 10 General] k4y0z:
Well, I have pointed you to my kernel-source before.
[Fire HD 8 and HD 10 General] Rortiz2:
k4y0z I have a question. Why have you disabled the selinux flags on your device tree?

I mean this flags:

# SELinux
#BOARD_SEPOLICY_DIRS += \
# $(DEVICE_PATH)/sepolicy-mtk/basic/non_plat \
# $(DEVICE_PATH)/sepolicy-mtk/bsp/non_plat \
# $(DEVICE_PATH)/sepolicy-mt8173/basic \
# $(DEVICE_PATH)/sepolicy-mt8173/bsp \
# $(DEVICE_PATH)/sepolicy

#BOARD_PLAT_PUBLIC_SEPOLICY_DIR += \
# $(DEVICE_PATH)/sepolicy-mtk/basic/plat_public \
# $(DEVICE_PATH)/sepolicy-mtk/bsp/plat_public

#BOARD_PLAT_PRIVATE_SEPOLICY_DIR += \
# $(DEVICE_PATH)/sepolicy-mtk/basic/plat_private \
# $(DEVICE_PATH)/sepolicy-mtk/bsp/plat_private

Could you compile with the flags activated?

Regards.

EDIT: [MENTION=9605864]Kaijones23[/MENTION] and me we are getting selinux permissions errors with LineageOS 16.0 for karnak.

I think that we need to set selinux permissive adding this line in BoardConfig.mk no?:

BOARD_KERNEL_CMDLINE += androidboot.selinux=permissive

Thanks!
[Fire HD 8 and HD 10 General] wilmafingerdo:
I appreciate everyone's efforts working on getting a custom ROM built for the HD10... been following it for a while now and have learned a lot tinkering with the device. GREAT WORK! Its a good tablet for the price and could be GREAT once everything is figured out!
[Fire HD 8 and HD 10 General] DragonFire1024:
Yes that is what you add to the cmdline to set it permissive on boot. You can also set it to disabled.

---------- Post added at 11:38 PM ---------- Previous post was at 11:34 PM ----------

Yes which is about precisely all you did do. now as much as I comment here and posting these forms that doesn't mean I follow 24/7. However I don't recall you ever saying that it was actually working in the few times that I've mentioned building a kernel in the last few days.
[Fire HD 8 and HD 10 General] Kaijones23:
[MENTION=7104332]k4y0z[/MENTION] [MENTION=8165603]DragonFire1024[/MENTION] here is the log during the rom boot-up but all it does shows amazon's logo and i have adb access with modified stock boot.img
[Fire HD 8 and HD 10 General] Legitsu:
I have avoided writing this post for a while because it always falls on deaf ears and the mods don't like it when I speak my mind

this is directed at NOBODY in particular

if you don't understand kernel development you should not be building a kernel (or a rom for that matter)

we are not here to school you in basic kernel compilation and rom modification

if you have trouble with basic concepts such as SELinux and build scripts then you have some studying todo

SELinux is disabled because it's easier to debug with it off

contrary to some very faulty assumptions you do not need any super special sauce to bring a kernel up so its compatible with later android revisions

(well you do but it's really not a huge deal just time-consuming) most of the patches exist and the ones that don't can be pulled from official sources we have. the biggest problems are usually vendor drivers not playing nice most of the time a generic image will at least get your intramfs up

and I said superSU is not a thing because chainfire is done with it thus its now dead yes it still works on android <6.0 but magisk is better
[Fire HD 8 and HD 10 General] k4y0z:
Well, selinux is one of the last things on the list to get working.

During development it will only cause problems.
[Fire HD 8 and HD 10 General] DragonFire1024:
We are all here to learn. Not everybody is a genius like you guys are.so not everybody is going to be up speed as much as you guys are and if you guys aren't willing to help anybody then there's no need to insult anyone. If you don't want to help then just don't say anything. I get really sick of seeing everyone moan about having to help people. We're all here for the same goals. so I'm not sure why you guys have so much trouble helping anyone. Unless it's because your ego is so big.

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

Which at the time I did bookmark and now mysteriously I cannot find it. Would you mind read linking me please and thank you
[Fire HD 8 and HD 10 General] Legitsu:
https://github.com/chaosmaster?tab=repositories
[Fire HD 8 and HD 10 General] DragonFire1024:
Thanks. I did have it bookmarked. I was just searching the wrong terms. Anyway not bad at all. I'll compare it to mine and see what I need to add. I am on my way to get a new mouse so I can't look this second. But I would say I was pretty damn close to yours.
[Fire HD 8 and HD 10 General] DragonFire1024:
Got rid of parental controls without causing anything to go nuts. Somehow the guest user became active on my device and I couldn't uninstall anything. I had to remove it via shell pm and then deactivated it in the framework. If it kept going it would've gathered a mirror of the system, doubling on the used space and memory.
[Fire HD 8 and HD 10 General] GuyInDogSuit:
What the...? How did that happen?
[Fire HD 8 and HD 10 General] DragonFire1024:
I'm not 100% sure, but close, but I think it was a permission I 'corrected'. I've been dissecting the account and parental control linkages for quite sometime. I figured out how Amazon stopped the use of managed profiles/accounts. All they did was comment out a permission in platform.xml. so I commented it back into it's rightful spot. Well I didn't take into account the persistent guest account. So when I rebooted and nothing was amiss I continued on. I uninstalled an app I didn't need anymore and it kept reappearing. I looked at the logs and it said 'uninstalled for user 0 of 2.' so I hacked an aosp settings app to install and looked at the storage data: guest had 138mb of app data and copies of the apps so far. I read The only way to disable it after it's been activated is pm disable/delete it and the data and hopefully you have root to just stop the process altogether in the build prop, (or skilled enough to edit the framework) or you need to reset.
[Fire HD 8 and HD 10 General] DragonFire1024:
Edit: I just started to figure out the status bar. This will take a lot of time, but I'm getting close...close enough it responds a little bit to gravity box now.
[Fire HD 8 and HD 10 General] DB126:
While I agree with your general position on spoon feeding this thread is titled "[CHAT]" and thus should tolerate open dialog regardless of perceived ignorance. Those intent on reinventing the wheel will do so regardless of available resources. Story telling has (complete with imagined villains, insurmountable hurdles and self-proclaimed heros) always been a 'thing' and remains alive and well on XDA. Sit back and enjoy the show.

Let's set the record straight:

- Chainfire is indeed "done" with SuperSU as is the current owner; EOL by definition

- SuperSU 2.82 SR5 works fine with Android <8.0

- Magisk is neither superior nor inferior to SuperSU without context

- like any other tool one must be knowledgeable around application and limitations

- personal preference does not constitute fact
[Fire HD 8 and HD 10 General] Legitsu:
superSU does not support hiding its self which is basically a requirement now if you wanna use your device for anything useful

and Context hrmmm well that IS what makes it inferior if you don't care about passing safety net or the ability to use your device todo banking/play games then, by all means, supersu is perfectly fine

but Unfortunately way too many apps simply refuse to work if they can determine you have root (banking apps, most popular games video streaming apps ect ect)

and switching between SuperSU and magisk CAN be a bit of a pain depending on if you have a clean backup of either the entire boot.img or the ramdisk

so by default, if somebody asks what to use I tell them magisk because Magisk is actively maintained and can pass safety net(Most of the time anyway =/)

I love chainfire to death but he has openly said he no longer has an interest in maintaining it(nearly 3 years ago I might add) or playing the endless cat and mouse with Google and other vendors that do not want us to have control over our hardware

times change and so must software :)
[Fire HD 8 and HD 10 General] DB126:
Valid points, although the severity/significance of each is situational. I do not use my handhelds for games and all of my financial apps run fine on rooted devices. Streaming apps are a different story; I typically use Magisk on those gizmos or leave them unrooted.

SuperSU can and will remain the 'right' solution for those who simply need a reliable (and often easier to implement) root manager on Android platforms <8.0. That community is quickly shrinking but is not an insignificant minority.

Just because something isn't supported/maintained doesn't make it useless.

I do agree Magisk is the better choice for most noobs in the absence of other considerations.
[Fire HD 8 and HD 10 General] DragonFire1024:
So as far as a custom rom goes, I can get it built, zipped, flashed and it boots...to the custom boot logo and it animates for a few seconds and freezes. Then nothing. That's as close to getting one to flash as I have gotten. So i know the system was flashed in some capacity.
[Fire HD 8 and HD 10 General] Shadow Death:
WOOT! Progress! :D
[Fire HD 8 and HD 10 General] yuera:
Excuse my ignorance, what does a "custom rom" mean in a amazon device?

Would it mean replacing the whole operational system to a fully android system without the amazon things?
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Pretty much exactly what it means.
[Fire HD 8 and HD 10 General] DragonFire1024:
Not really. This has been beyond frustrating. If that's progress, then of the 2 days I spent trying, I've gotten no further.
[Fire HD 8 and HD 10 General] borissprat:
Please provide links to this "wheel" so the re-invention can cease.

Much obliged.
[Fire HD 8 and HD 10 General] DragonFire1024:
So I have a kernel. I made modules of what wasn't already built in, according to the suez_debug_deconfig. Everything built, but it appears the only modules working is the accelerometer. From what I have studied over the past week or so, the modules should just need to be pushed to /system/lib/modules and given 644 permission. I did that, rebooted to recovery, flashed the new img and rebooted. None of my tools say anything is active except the forementioned. Would they have to be added via the boot image? That's my next try. If not, what am I doing wrong? If nothing, then are we even able to add anything at all? If not, then is it possible to rebuild the ran disk at all?
[Fire HD 8 and HD 10 General] DragonFire1024:
No one eh?
[Fire HD 8 and HD 10 General] pocketrussian:
Did you try to load the module manually using insmod? You can check with lsmod.
[Fire HD 8 and HD 10 General] DragonFire1024:
I did not. I'll try that tomorrow when I have a few days to work on it.