yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] Shadow Death:
You think that's something. When the HTC Thunderbolt finally got Android 4.0 people were asking for the kernel source. Keep in mind HTC promised ICS for the Thunderturd at launch... It finally came out about 1 or 2 years later. HTC told the devs that they would have to wait 90 days for the source... 90 days came and went and when they got called on it they pushed a "fix" and said they wouldn't release the code for the old kernel as it had a security flaw. 90 Days after that fix they released the kernel source and there was only 1 dev left working on the device. He spent a few hours looking at it and then made the announcement that HTC deliberately sabataged it. His reasoning was he took the code as is and tried to compile it. The kernel refused to compile. When he dug into it he noticed some pieces missing from the code. That phone was a piece of ****. Right after that phone came out Google dropped the Galaxy Nexus and out the Thunderbolt to shame. HTC tried to sweep that thing under the rug and even tried to EOL that device so they didn't have to deal with it. Lol
[Fire HD 8 and HD 10 General] TheLoonyRebel:
Oh trust me as the man who used to handle the ROM/kernel listing for the HTC Thunderbolt.... I remember that all too well. I had already ditched the phone long before that as I could tell how HTC was going to handle things.
[Fire HD 8 and HD 10 General] siochs:
So what I have now is a "/home/build/android/out/target/product/suez/lineage-16.0-20190701-UNOFFICIAL-suez.zip". It built in 2hrs. I know it is lineage and not AOSP, but a colleague recommended me to start over with something that will "probably not fail".

I don't know why, but this felt somehow "too easy". I just placed a local manifest and ruled out a few build errors... Don't know yet if it will boot. Is there a good emulator around?
[Fire HD 8 and HD 10 General] GuyInDogSuit:
Emulator? Yes. BlueStacks, NoxPlayer, Andy, and even Android x86 (though that's less of an emulator and more of a pure Android experience, on an Intel PC environment)

Ones that would allow flashing of a custom ROM? None that I know of.

The only recourse is to just flash it to your device and cross your fingers.
[Fire HD 8 and HD 10 General] Rortiz2:
Just share the zip and let people try it.
[Fire HD 8 and HD 10 General] siochs:
Yeah, right. Can't test it on my Fire currently.

https://drive.google.com/open?id=1sjAh-HsV9W3inHpqUsNLD4vllIHsK6Bj
[Fire HD 8 and HD 10 General] Rortiz2:
Pinging HD10 users for test it...
[MENTION=8165603]DragonFire1024[/MENTION] [MENTION=1464372]GuyInDogSuit[/MENTION]
[Fire HD 8 and HD 10 General] DragonFire1024:
I'll give it a shot once I get home. Hopefully I got something good out of aosp last night. We'll see soon.
[Fire HD 8 and HD 10 General] TheLoonyRebel:
Build goes to fastboot mode after flashing. Does flash successfully with ARM64 Gapps.

Also it does sit on the Amazon logo for at least a good 30 seconds before going to fastboot. I hope this info is helpful to DragonFire1024 when he tests later today.

No issues restoring my 5.6.4.0 backup I made with TWRP prior to trying. Did a clean install with just the ARM64 Gapps then did another clean install but added Magisk to see if that would change anything. No luck with either attempt.
[Fire HD 8 and HD 10 General] sakibstark:
Any success. Did the LOs boot?
[Fire HD 8 and HD 10 General] TheLoonyRebel:
As I stated in my previous post which is right before your post.... no it did not boot. It went to fastboot.
[Fire HD 8 and HD 10 General] Rortiz2:
Kernel problems then. Patches on kernel are missing..
[Fire HD 8 and HD 10 General] TheLoonyRebel:
Hopefully that's an easy fix, right? Not familiar with doing such things so I'm learning here.
[Fire HD 8 and HD 10 General] DragonFire1024:
well if you had to use arm64 gapps that's your first clue right there that it's not going to boot. I'm stuck at one single point in my build and it won't get past this: it needs a library file for hostapd. I managed to get past this point before but I just don't recall how I did it. and anywhere I put the files that are attached in any way related to that driver it still goes back to the same error. Aside from that pretty much everything else build perfectly. I have not had such a cleaner build before. I'm at work for the next several hours so I can't post the exact error.

---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------

I don't think it has anything to do with that. I can sit here all day long and pump out one custom kernel after another after another and Boot it on lollipop or fire OS perfectly even if I'm not using Amazon's actual source kernel. So I'm not entirely sure why that isn't holding. If I had to guess it has something to do with the init files in the root directory and they're telling the system to do something and therefore it does not actually boot the custom ROM. Of course that's just all speculation.
[Fire HD 8 and HD 10 General] siochs:
To find out what exactly is preventing the boot, we need logs. Sorry, but I am learning here too. How does one get kernel messages on boot? I can imagine two scenarios:

- Attach usb and try to fetch messages via adb on boot. Thir requires adb service to start?

- Attach to some kind of serial output like uart. I have all pieces for level shifting. Someone here knows of such an interface?

[MENTION=8165603]DragonFire1024[/MENTION]

Are you willing to share your makefiles and configs so that I can reproduce your build? Perhaps I have the luck and can track down the error...
[Fire HD 8 and HD 10 General] DragonFire1024:
TWRP has an option to send logs to sdcard. I can't get past one error where I need a library that I have but aosp won't acknowledge it's there. I was able to fix this last time but I don't remember how I did it. I also remember this meeting the build is nearly finished and probably has less than two minutes to complete go figure right
[Fire HD 8 and HD 10 General] siochs:
This works also with the external sdcard right? :)

This library you are talking about, did it come from an external repo or did it come from your host system you are building on? I am asking because I used a dockerized environment for build and the container included everythin required (so far)...
[Fire HD 8 and HD 10 General] Rortiz2:
Dude, it's a kernel problem. I already experiencied that in the HD8 2018 and it was a KERNEL PROBLEM. If you're using prebuilt kernel, you only can boot cm12.1.
[Fire HD 8 and HD 10 General] siochs:
The kernel I included was the one on chaosmaster's repo, branch lineage16.0.
[Fire HD 8 and HD 10 General] DragonFire1024:
I can't even get the damn thing to build a lollipop ROM because I can't figure out where that library file goes and this isn't making it any easier now I'm looking at the source it appears that we are missing some WiFi firmware files to. And that's even on the fire OS ROM that we are currently on where they're gone. and I can pump out my own kernels all day long so that's not going to be a problem and I'm also using chaos source as well
[Fire HD 8 and HD 10 General] DragonFire1024:
Alright. Past that hurdle and a few others. Just have a few more things to do that I couldn't finish before work and we should be good to go tomorrow for real.
[Fire HD 8 and HD 10 General] tylerhole:
Just getting caught up on this thread and I have to say way to go [MENTION=8165603]DragonFire1024[/MENTION] and everyone else contributing! Can't wait to try out what you throw at us next, hopefully it'll be a working ROM! [emoji16][emoji16]keep up the killer work everyone!

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 General] DragonFire1024:
On a less complicated note, I may have just been able to bypass Amazon's lockscreen or at least the wallpaper settings for it and have possibly been able to reactivate the main Android 'wallpapermanager'. a couple of the benefits of having downloaded the entire Android source code is also having the ability to look at additional 'extras' as they call it. And some of those include additional framework settings. A few of those settings happen to be for the wallpapermanager did Arie inserted into the framework but I did not remove anything when I did this and at most times then I click lock screen the wallpaper I said as a test shows up almost all the time for a second though. So my next test will be to try and remove the settings in the framework for Amazon's stock wallpapers. I have had the same effect when setting a lock screen background in gravity box. The only thing I see blocking a custom wallpaper now, is the preset Amazon ones. The problem here is getting a bootable framework out of removing the settings. I somehow have to do that without apktool freaking out. I've done it a few times but I have not been able to get the framework to boot after such. So now it's just a game of playing around and figure out what works and what doesn't.
[Fire HD 8 and HD 10 General] siochs:
Don't flash this build, this is basically a complete messup.

This is the boot log: https://drive.google.com/open?id=1vwxIVCXh_6g3IdG-GNOAg4Sly7vKGSki
[Fire HD 8 and HD 10 General] DragonFire1024:
A ROM is all I have been putting whatever free time I have, to create. I recall [MENTION=5749760]ggow[/MENTION] saying how hard it is to setup a device to build in AOSP. I thought to myself it can't be that hard. How very wrong I was. The issue with this lies the matter of, 1) I was originally working blind, off makefiles for lineage. so I had to basically rewrite several files just to get anything started. 2) the source we have for 7.0 varies ever so slightly from our stock firmware. It wasn't until reading those makefiles that I found that out and it's something that is very easily unnoticed. There are differences in some of firmware versions for things like wifi and etc. The 7.0 source also contains additional firmware files that were previously unknown/not present in out current firmware. So now I have to decide which to do first. Build with or without them. 3) some of Android's makefiles override the ones we set. That was the issue with the library files. Because we aren't building a direct mediatek ROM, Android overrides certain makefiles and redirects the script to build from your tree...so I have/had to track down those individual sources. Even though this chipsets makefiles were made for AOSP building, Amazon screwed us by putting lollipop on these. A lot of the files in the 7.0 are made for 7.0. so that was another issue. 3) we can't flash a system image that isn't a twrp backup. So I am relying on AOSP to build a sparse image to lessen the likelihood of errors converting an ext4 image to .dat. for some reason the system is very picky when it comes to this part.
[Fire HD 8 and HD 10 General] tylerhole:
Wow you definitely have taken on quite the project in all this while learning how to do it all along the way. Kudos to you sir.

Sent from my SM-G9650/DS running stang5litre Pie ROM
[Fire HD 8 and HD 10 General] k4y0z:
Since you guys seem to be desperately trying to reinvent the weel, I have uploaded my last build (Lineage 16) from April here:

http://www.mediafire.com/file/tt7yxy1bjo7unqn/lineage-16.0-20190423-UNOFFICIAL-suez.zip/file

I haven't had any time to do further work on it, and I probably wont till mid August.

It has WiFi working and audio partially.
[Fire HD 8 and HD 10 General] TheRealIntence:
Thank you for sharing this!

Can you explain further what you mean by partially working audio?
[Fire HD 8 and HD 10 General] k4y0z:
It does work, but sometimes still crashes.
[Fire HD 8 and HD 10 General] TheRealIntence:
So I tried lineage 16 on this device. I experienced some bugs:

- navigation buttons have weird texture

- notification panel does not use full display size (width and height)

- WiFi is not working for me (I cannot even turn it on)

-> same for Bluetooth

- auto rotate doesn't work

- audio is bugged

- device response slowly

- animations are laggy

I have not proceed further...
[Fire HD 8 and HD 10 General] k4y0z:
The graphics glitches appear in the navbar and in the recent apps drawer, haven't figured out how to get rid of them yet.

I think the notification panel is normal like this in pie, but not sure.

If wifi isn't working I may have uploaded the wrong build, I will have to check later.

Yes, bluetooth isn't working, I had a build, where it was disabled completely, so it doesn't constantly crash.

Yes, audio is bugged as mentioned.

Haven't noticed laggy animations, will have to check
[Fire HD 8 and HD 10 General] DragonFire1024:
Not reinventing anything really. No one else seems to have the enthusiasm to do it.
[Fire HD 8 and HD 10 General] Rortiz2:
Well at least his build BOOTS.
[Fire HD 8 and HD 10 General] Shadow Death:
Stop throwing shade.......
[Fire HD 8 and HD 10 General] DragonFire1024:
Really? This isn't a pissing contest. At least not for me. I've put in more than enough time and effort around here to deserve a tiny bit of respect. I'm trying. And if we aren't going to help each other then I'll keep on the sidelines like I have been and eventually we'll have a ROM but who knows how long that will be if we don't keep stopping for the bathroom every 5 minutes.
[Fire HD 8 and HD 10 General] oliver853:
DragonFire1024! You are doing a tremendous job. I hope you complete and give us a bootable rom. Don't care about what others comment. Your work has helped me understand so much about this tablet and in general ROM building! Kudos.....:good:
[Fire HD 8 and HD 10 General] j0hnnie:
DragonFire1024: Your job is very appreciated! Respect! Greetings from Germany.
[Fire HD 8 and HD 10 General] siochs:
Guys, guys, once again don't let this get emotional.

Unfortunately, you picked the wrong post. By "reinventing the wheel", c4y0z pointed to my garbage-build I shared, because I tried to build lineage from scratch with the sources I found on the web. I think the reinventing-the-wheel-issue is by all means not related to your research activities. Keep going :good:

This is not entirely true. I offered to reduce build time with hardware I have, there is no reason to wait over night. Perhaps we can setup something like a continuous integration? I asked you twice if you are willing to share your code. But I can't find anything in your GitHub repos. In software development it is quite common to make a "dev" branch where you commit and push what you are currently working on. Merge this branch to something releasable (like "aosp-<version>-master") when you are convinced it is done. What will happen when your ubuntu dev-machine dies? And there will be no more "I can't recall how I built that library...". Sharing your code will bring you benefit.

This is misplaced. We have research going on here. There is no guarantee that any of that builds shared will work smooth and sound. There is no right of "get-it-done".
[Fire HD 8 and HD 10 General] k4y0z:
My comment about "reinventing the weel" was in no way meant to discourage anyone from working on this.

I just thought it might be appreciated if I shared what I had, given that I currently don't have much time to work on it.

I will see to push my local commits to github, when I get a chance, so they might be useful for others.
[Fire HD 8 and HD 10 General] DragonFire1024:
A few have asked and 8ve just been too consumed with my real life job, or too focused on trying to get this to work. Now that I think I have at least a working device tree, make files that build a ROM, and an actual ROM (no boot). It just finished as I was getting ready to leave for work and I managed to grab it. Unfortunately I didn't have time to build a kernel for AOSP to build so it's just system and I took the stock boot image and made a sparse zip and a meta zip. Both systems flashed, permissions all set properly everything looks in order. It's gotta be the kernel.

Anyways I will upload everything when I get home later. I didn't want to give anyone anything that at lest didn't build.
[Fire HD 8 and HD 10 General] Rortiz2:
Guys, It was not my intention to offend. If I have offended someone, I'm sorry. I had understood DragonFire's sentence wrong.

Sorry!
[Fire HD 8 and HD 10 General] DragonFire1024:
I'm not offended. I know we are all anxious and excited and some of us have been waiting for this for a very long time. But even for a device that already has ROM support (fire 7) it's still not easy and in some cases is even more so difficult. It would just be easier if we all shared what we know instead of trying to be first in line.

On that note, I just found out I am likely beating a dead horse building in AOSP. I had an impression of something that I ended up being wrong about and may have prevented me getting a lot of headaches the past few weeks. So with that said, I'll upload what i have in the next several hours. But I'll probably have to switch branches a CM AOSP instead of direct AOSP.
[Fire HD 8 and HD 10 General] siochs:
Full ACK :)

That was something I was about to wonder. I have seen a few posts and youtube videos changing a working a lineageos build to AOxP. Is this an option to go?

Note the following video is about AOKP and not AOSP, but the procedure is maybe similar? https://www.youtube.com/watch?v=T1IOe5QwYJs
[Fire HD 8 and HD 10 General] Shadow Death:
Honestly I'm just happy to see people showing interest in this device. I would help if I could but I'm not a mobile person. I can flash and test but I'm not a rom builder or anything of the sort.
[Fire HD 8 and HD 10 General] k4y0z:
I have uploaded a new build here:

https://www.androidfilehost.com/?fid=6006931924117909028

This one should have wifi working.
[Fire HD 8 and HD 10 General] DragonFire1024:
I've never built one either, but this is all about learning, at least for me. All right I fix the issues that apparently did not cause the vendor files to be set in with the ROM. So I'm running a build right now and I'll see how it goes and I'll upload that build once it's done. I am uploading the rest of my pieces for the device tree to github right now so I also link that once I'm done too.
[Fire HD 8 and HD 10 General] TheRealIntence:
WiFi is fixed.

Google services are not usable right now because of missing device certification which is obvious.

Cannot register it either because I'm not able to retrieve the Google services framework Android id.

Gonna stick with microG for now.

Can you upload your tree in GitHub so we are able to work and improve it?

---------- Post added at 08:43 PM ---------- Previous post was at 07:51 PM ----------

I've found another interesting bug.

Files cannot be downloaded.

I tried it in several apps such as fdroid, magisk manager and even jelly (browser) but an attempt just results in an app crash or download failure.
[Fire HD 8 and HD 10 General] k4y0z:
May have to change device fingerprint then.

I will have to do some cleanup on my local build-tree and push the changes to github.

Will see, when I get around to do that.

I think I know what's causing this, the internal sdcard/storage isn't mounted to the proper location.
[Fire HD 8 and HD 10 General] k4y0z:
The fstab has nothing to do with it, and everything goes to EMMC (Embedded Multi Media Card).

The partitions that go with a ROM usually are boot and system.

What the fstab is telling you is that the partitions marked as "EMMC" are "RAW"-partitions like boot/recovery images.

While the ones marked with "EXT4" contain a mountable filesystem.
[Fire HD 8 and HD 10 General] TheRealIntence:
Installation failed.

mount: failed to mount /dev/block/mmcblk0p6 at /system:
Invalid argument
-- ApplyParsedPerms: removexattr of /system/xbin/tcpdump to 0 failed: Operation not supported on transport endpoint
set_metadata_recursive: some changes failed
[Fire HD 8 and HD 10 General] DragonFire1024:
The 10 doesn't support metadata. I know there is one metadata line in the stock Amazon script, but I don't know if it actually does anything. You will have to go the other route, and use perm. it took me forever to get that.
[Fire HD 8 and HD 10 General] Rortiz2:
So amazon ****ed up set_metadata?

Enviado desde mi Mi A2 mediante Tapatalk

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

Its 6.0.1

---------- Post added at 07:02 PM ---------- Previous post was at 06:49 PM ----------

Try test 2 please:

Removed

There are some problems in the updater-script of the test1 and I changed set_metadata to set_perm like [MENTION=8165603]DragonFire1024[/MENTION] said.
[Fire HD 8 and HD 10 General] k4y0z:
I have just taken a look at your update-script.

It looks very convoluted and does a lot of strange things.

/dev/block/mmcblk0p6 isn't even the correct partition for system, that's tee1.

Also the partitions should be referenced by name, not by partition number.

The command for flashing the boot-image is also overly convoluted.

I would not recommend anyone flashing this in this state!
[Fire HD 8 and HD 10 General] Rortiz2:
Yes yes, it has been my fault .. The system path is:

/dev/block/platform/mtk-msdc.0/by-name/system

I solved it.

By the way, what is wrong with the boot-image command?
[Fire HD 8 and HD 10 General] k4y0z:
Why are you extracting it to /tmp/boot.img and then call a script /tmp/flash_kernel.sh that tries to parse /etc/recovery.fstab to find the boot-partition and then flash with dd.

This should be all that is needed:

package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
[Fire HD 8 and HD 10 General] TheRealIntence:
So have you already fixed this error?

set_perm_recursive: "/system" is not a valid uid
[Fire HD 8 and HD 10 General] Rortiz2:
I have taken the boot.img script from another rom. Anyway, I'll change it as you say.

Thank you

---------- Post added at 07:50 PM ---------- Previous post was at 07:41 PM ----------

No.. It seems that you have to replace the whole script because amazon does not let you use set_metadata so I'm going to see what I can do.
[Fire HD 8 and HD 10 General] DragonFire1024:
I have hopes it will be fixed. I am picking up one tomrrow if it can't be fixed. I had already planned on getting another.

---------- Post added at 09:01 PM ---------- Previous post was at 08:54 PM ----------

Yes set metadata will error out. I've tried it every which way. If this is for the hd 10, you also can't put "EMMC" in the beginning of the script when you mount system. It too will error. Also can't put a data call in or '0,0' as that too will error. It seems they did a lot to stop the conventional way of flashing. The only time I got a room through was when I repacked the system directory as another .dat. then I bricked.
[Fire HD 8 and HD 10 General] Rortiz2:
So, the only way to flash a ROM is in format system.new.dat and if you do it wrong, you will brick the tablet.

I do not understand what amazon has done to block set_metadata. In the fire os updater-script there is nothing weird ..

getprop("ro.product.device") == "suez" || abort("This package is for \"suez\" devices; this is a \"" + getprop("ro.product.device") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/mtk-msdc.0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
show_progress(0.200000, 10);
package_extract_file("images/lk.bin", "/dev/block/platform/mtk-msdc.0/by-name/lk");
package_extract_file("images/tz.img", "/dev/block/platform/mtk-msdc.0/by-name/tee1");
package_extract_file("images/tz.img", "/dev/block/platform/mtk-msdc.0/by-name/tee2");
package_extract_file("images/preloader.hdr0", "/dev/block/platform/mtk-msdc.0/by-name/boot0hdr0");
package_extract_file("images/preloader.bin", "/dev/block/platform/mtk-msdc.0/by-name/boot0img0");
package_extract_file("images/preloader.hdr1", "/dev/block/platform/mtk-msdc.0/by-name/boot0hdr1");
package_extract_file("images/preloader.bin", "/dev/block/platform/mtk-msdc.0/by-name/boot0img1");
package_extract_file("META-INF/com/amazon/android/target.blocklist", "/cache/recovery/last_blocklist");
set_metadata("/cache/recovery/last_blocklist", "uid", 0, "gid", 0, "mode", 0444, "capabilities", 0x0);