yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] pharpe:
I just linked you to the thread with step by step instructions to install TWRP. That is the recommended way. Read and follow it. If you are having problems after that than post a question there. This thread is about Lineage-14.1 not how to unlock and install TWRP.
[Fire HD 8 and HD 10 Original Android Development] kevin71246:
Steps to go from latest Amazon FM to LineageOS

I posted this "guide" on that thread for my specific scenario (updated to latest FM): https://xdaforums.com/showpost.php?p=82264029&postcount=1102

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

It's been several months since I saw anything "camera" related so thought I'd ask again (I know its a known issue in the OP but dev work seems to have stalled): I installed LinegeOS 12.1 and the camera works. Does anyone have a fix to get it working on this LineageOS 14.1 ver? Thanks!
[Fire HD 8 and HD 10 Original Android Development] jpinzon408:
Hi Pharpe, sorry for this situation and I apologize to the forum for this. Thanks for the information, help and your time.
[Fire HD 8 and HD 10 Original Android Development] lovaduck:
I am also interested in a camera fix. I would love installing this version of Lineage OS or a newer one but I am keeping 12.1 because of the camera issue!

With many of us in lockdown it would be great to get a functional front camera as well... for Teleconferencing.

Thanks guys for the effort producing the roms!
[Fire HD 8 and HD 10 Original Android Development] sakibstark:
I remember there were patches for headphones and omx but how come they are not linked in the description. Can anyone provide me the link please?
[Fire HD 8 and HD 10 Original Android Development] tuniel:
3 pages back... summary posted
[Fire HD 8 and HD 10 Original Android Development] sakibstark:
thanks so much. One more qestion. What gapps version should I use? Arm64-7.0-pico?
[Fire HD 8 and HD 10 Original Android Development] tuniel:
yeah, that's the one i used too
[Fire HD 8 and HD 10 Original Android Development] BeniS98:
7.1 Pico, not 7.0!
[Fire HD 8 and HD 10 Original Android Development] RjGunner111:
fireos version question

what if my fire hd 10 7th gen runs on this version: 5.6.6.0, can i turn it to stock android nougat that way? or should i downgrade?
[Fire HD 8 and HD 10 Original Android Development] nikothebarber:
Can someone send a profiles section for old violper not presets.
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
If you have not unlock the bootloader and install TWRP, you need to do that first. After this, you can flash any rom you like.
[Fire HD 8 and HD 10 Original Android Development] RjGunner111:
so i'd be fine with the modifications despite what version fireos is
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
Once you unlock and install TWRP, fresh installation of any custom ROM should be fine. You will instruct TWRP to wipe clean the partitions where the previous OS occupies except you would keep the data partition. I upload the custom ROM image to the data partition and ask TWRP to install it in the other partitions. This is all done pretty automatically by TWRP. Make sure you back up whatever precious data you have in the existing OS. This LOS 14.1 is for fresh installation only.
[Fire HD 8 and HD 10 Original Android Development] pharpe:
Yes you will need to downgrade to get TWRP on there but that is out of scope for this ROM thread . Here is thread has the TWRP process. https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639

Once you get that done come back here.
[Fire HD 8 and HD 10 Original Android Development] RjGunner111:
i looked up on how to downgrade, but i couldn't find anything
[Fire HD 8 and HD 10 Original Android Development] pharpe:
It's all in that guide I linked to . There is a soft brick option and one where you have to open the case. I would suggest reading a lot more before you start. Start with that whole unlock/root thread.
[Fire HD 8 and HD 10 Original Android Development] Kramar111:
[MENTION=5749760]ggow[/MENTION]

Can you also give some love here? :)
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
There's not much to update on the ROM aside from the security patch, unless the camera is fixed as well as the headphone jack without having to modify any other additional files or flash any other zips. He has already put a commit towards fixing and enabling the automatic brightness, courtesy of me, I having found it in the Android framework. I suspect the camera has something to do with the kernel and using it as a platform camera rather than a separate driver. I have noticed this in a few other kernels I have been working with lately and they're listed as platform cameras and without selecting that option in the kernel the camera(s) will not work.
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
This exactly what I did to unlock and install TWRP my Fire 10HD 2017 according to that thread. I had to do a soft brick to downgrade to 5.6.0.0 before I could unlock and install TWRP. I did not install LOS 14.1 but installed LOS12.1 because I need the camera to work.
[Fire HD 8 and HD 10 Original Android Development] pharpe:
I installed LOS 14.1 but went down to 12.1 because of the camera and some streaming apps not working. LOS 14.1 was much better in terms of usability and battery life so I'm holding out hope that those might one day get resolved. It's a shame because the HD10 2017 is the best hardware with an unlockable bootloader. I don't understand why there is so little interest in development.
[Fire HD 8 and HD 10 Original Android Development] TonytheEE:
So, does that mean there is a fix if the ROM setup selects that option? Point is, is the 14.1 capable of using the cameras if it's a config thing, or would using the cameras require writing or adopting a whole other driver?
[Fire HD 8 and HD 10 Original Android Development] dasbooter:
Migrated from this ROM to lineage 12 because I couldn't game stream with an app called Moonlight with this ROM I guess because of the partial OMX support. Thanks again to the developer for giving a really worth it purpose to my old Suez. It kind of seems there are other cheaper tablets with similar specs that can have the boot loader unlocked easier so they make a better target for the devs. I'll keep checking back to see of this gets updated though so hopefully [MENTION=8165603]DragonFire1024[/MENTION] and [MENTION=5749760]ggow[/MENTION] continue in there free time to improve these ROMs and apply what they learn from other devices

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

Migrated from this ROM to lineage 12 because I couldn't game stream with an app called Moonlight with this ROM I guess because of the partial OMX support. Thanks again to the developer for giving a really worth it purpose to my old Suez. It kind of seems there are other cheaper tablets with similar specs that can have the boot loader unlocked easier so they make a better target for the devs. I'll keep checking back to see of this gets updated though so hopefully [MENTION=8165603]DragonFire1024[/MENTION] and [MENTION=5749760]ggow[/MENTION] continue in there free time to improve these ROMs and apply what they learn from other devices
[Fire HD 8 and HD 10 Original Android Development] pharpe:
Care to share what those are? I've been searching for a while and have come up empty.
[Fire HD 8 and HD 10 Original Android Development] n3wt:
I'm guessing the Onn tablets from Wally World.
[Fire HD 8 and HD 10 Original Android Development] sakibstark:
This Os is great. However there are a few known bugs as mentioned by everyone but there's also another issue with the split screen view, everything on the left gets blacked out from time to time, maybe related to the Omx issue? Because when I play YouTube video and go full screen landscape mode and split screen, the video playing on the right will be blacked out.
[Fire HD 8 and HD 10 Original Android Development] cachiputi:
No video any app

Hi [MENTION=5749760]ggow[/MENTION]

Yesterday I managed to install the ROM of LinageOS 14 for Fire 10 HD Gen7 (2017)

But I run into a problem, it is not capable of playing any video, neither in the national TV APPS, nor in YouTube, both by APP and via WEB, or VLC.

It is normal?

Could it be because I installed the GAPPS for ARM64 and this tablet is 32bits?

What could I have done wrong or where is the fault?

I put LinageOS 14 to my Fire 7 Gen7 (2017) and it works perfectly (Except for the WebCam).

one thousand Thanks for your help.
[Fire HD 8 and HD 10 Original Android Development] Michajin:
Post 248 for OMX video fix

https://xdaforums.com/hd8-hd10/orig-development/rom-lineage-14-1-t3973703/page25
[Fire HD 8 and HD 10 Original Android Development] cachiputi:
THANKS

Thanks friend.

Ten points!!
[Fire HD 8 and HD 10 Original Android Development] pharpe:
Do the new Onn tablets have unlocked bootloaders? The previous generation Onn specs are not close to the 2017 HD 10. There isn't even a development forum for them on XDA.
[Fire HD 8 and HD 10 Original Android Development] v0id7:
Why is my device rooted?

First of all, many thanks to [MENTION=5749760]ggow[/MENTION] - great rom - smooth, with great battery life!

However, today when I enabled ADB, I suddenly got root access!

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:su:s0

How come? I haven't rooted this LineageOS installation - haven't flashed Magisk and haven't applied any other rooting hack after installing Lineage?
[Fire HD 8 and HD 10 Original Android Development] DB126:
Most Lineage builds include native root via slider under developer options.
[Fire HD 8 and HD 10 Original Android Development] dasbooter:
Sorry I remember one of the devs in this forum mentioning and this is my take on what he said "Walmart had a cheaper model very similar in specs, might of been rca or something and much easier to unlock the bootloader and get control and no cat and mouse with Amazon" but your preaching to the quire I couldn't find that tablet where I'm from and this Suez had served me pretty well. Wish I could get the plug in headphones to work... For trips my gf likes to watch a movie "together" so she thinks my tablet is junk bc it's broken for one thing literally 120 mins out of the year or whatever. By the way I had tried flashing the omx fixes from awhile ago on the lineage 14.1 but that wouldn't fix moonlight streaming.
[Fire HD 8 and HD 10 Original Android Development] v0id7:
Thanks.

Under Developer Options I see Rooting access is set to Disabled, so most probably this is not the case.

Anything else I should check?
[Fire HD 8 and HD 10 Original Android Development] DB126:
IDK - do not own this device so can't comment on capabilities baked into the ROM or tools used to unlock the bootloader. Root doesn't magically appear.
[Fire HD 8 and HD 10 Original Android Development] v0id7:
I’m trying to build this rom from source and I need some help.

I successfully checked out:

kernel/amazon/mt8173-common

device/amazon/mt8173-common

device/amazon/suez

Then I extracted proprietary blobs (both mt8173-common and suez) from my tablet (already running this rom).

The issue I’m hitting is that all suez combos offered by lunch are prefixed with “cm_“ instead of “lineage_”.

Any idea how to fix this?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Browse your make files and scripts in device/amazon/Suez and look for the "cm_" calls and change it to "lineage_".It's just a matter of going into the make files and correcting for lack of better terms typos. In other words the device tree has not been updated since it was moved from CyanogenMod over to lineage. Yes it can be a really big headache. Especially if you miss one or happened to duplicate one in the same makefile.
[Fire HD 8 and HD 10 Original Android Development] drdtyc:
This fix will rectify your headphone problem.

Just flash the zip file using TWRP and you are good to go.

https://xdaforums.com/showpost.php?p=81494297&postcount=515

It works for me using LOS 12.1.

But the fix is for both LOS 12.1 and LOS 14.1.
[Fire HD 8 and HD 10 Original Android Development] :
hello! I tried mtk and kingoroot but both of them dont work, I have fireos 5.6.6.0 is there any way left to unlock the bootloader and install lineageos? can't stand fireos.
[Fire HD 8 and HD 10 Original Android Development] tnthd2:
Unlocking bootloader and installing TWRP is in this thread: https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639/. Follow post #1152 and #1148 for Kingoroot steps.
[Fire HD 8 and HD 10 Original Android Development] FireSlayer_SD10:
Any progress on android >7?

Did you ever get any 4.x or 5.x kernels to build? All mt8173 devices I've seen have kernel 3.18... Can android >7 run on older kernels?

---------- Post added at 04:51 AM ---------- Previous post was at 04:30 AM ----------

This ROM is amazing by the way! Just fired this back up after awhile of neglect and flashed the headphone and OMX fix. The only (small) issue is that webvr crashes the ROM http://chromatic.funktroniclabs.com that's a example site that uses webvr.
[Fire HD 8 and HD 10 Original Android Development] :
I am getting an error with something like java illegal state error with kingoroot, why?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I actually tried to update it at least a couple of incrementals, but there was some weirdness involved with the drivers in which the screen would flicker on and off and I could not figure out how to fix it so I had to abandon it until I can find out what it was.I'm almost certain it's a driver issue but it may also be the fact that CyanogenMod / lineage OS doesn't usually play nice with new kernel builds that was not built in line with the ROM. I have significantly upgraded the kernel version on my Nexus 10 but I have not been able to update it out of the 3.4 incremental range. Mostly because I'm not sure how to do so as none of the patches I applied seem to work.
[Fire HD 8 and HD 10 Original Android Development] v0id7:
I successfully rooted my device many times (including 5.6.6.0) by following the these steps.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
So I think I managed to get this ROM to allow the SU binaries to be updated. The process was pretty ridiculous, but so far it's working. it will take me a little bit of time to explain the steps but it involves using several of the methods we used to root these prior to being unlocked. In fact it's a combination of a little bit of several of them. In case you're wondering what this means I'm hoping it will mean being able to use other root managers like SuperSU. I made you a write-up on it, but it won't be for a few days because it's going to take me a bit to try and explain it in as few words as possible. It also involves editing an init script in etc, which I think was one of the main culprits stopping any other root Managers from taking hold aside from Magisk.
[Fire HD 8 and HD 10 Original Android Development] dcxx20:
I have tried this rom with the OXM patch. Really like it better than 12.1 and appreciate the work by OP and others. The only missing part for me is hardware decoding. Can't run game streaming without it, and the battery life took a bit hit when playing video. Is it possible to borrow modules from 12.1 and copy to 14.1?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
In some cases yes you can do that and codecs don't necessarily pose a problem when doing so. With that having been said, in some cases there are a significant number of them. Unfortunately mediatek is one of those cases. Sometimes generic common codecswork and sometimes they don't just like proprietary blobs in a lot of cases things won't function properly without the originals. That also having been said, I'm working on a Nexus 10 on both upgrading the kernel and it's ROM and I have found that with older devices it isn't necessarily a matter of the modules or hardware being too old to work with modern day stop, but the fact that a lot of the hardware code itself has not been updated. So one compilers change you can't use various other modules as you did before. so I will cut to the Chase and say that I've already tried that on my 10in from 12.1 to 14 and with no success however you probably need to end up doing this at the same time you're flashing the ROM if we were ever get all the files.

---------- Post added at 08:40 AM ---------- Previous post was at 08:33 AM ----------

okay so I have some weirdness going on with the whole super user issue and trying to at least eradicate lineage super user from the ROM. I've been able to successfully achieve it twice for a prolonged period using two different root manager options. The thing is you cannot update the superuser binary if you do when you reboot the device it goes into a boot loop every single time except for when you use kingroot. Now I don't have time to get into how I got to that level and managed to get it to root, but the point I'm trying to make is that it actually did take over the superuser binary and updated successfully and the root held. That was of course until you wiped or did some performance maintenance like wipe the cache and root vanishes again and you have to start over and luckily you can replace the binary with the original and you're okay to go. So discovering two things you can do with this one don't ever update the super SU binary is ever. You will still get to use SuperSU, but not without being spammed by warnings every time the application is opened but everything functions as normal otherwise for the most part but the downside to that is don't reboot.

I have also discovered the three main files in question that control the built-in root manager.simply removing them does not fix the problem which means there's got to be another configuration somewhere I have not yet found which tells the device not to boot when the super user is removed. I've looked through and I will look through again, all the boot image files and I can't find anything that says anything like that, but that doesn't mean it's not in something like the sepolicy.now I know that SuperSU works on lineage 14 because I have a fire 7 with lineage 14 on it and I have SuperSU. This is the only device from 7 under that I have been able to conjure up that will not for whatever reason allow SuperSU to take control of the binaries. didn't seem to have a problem letting kingroot do it which was a little weird and offsetting to me.
[Fire HD 8 and HD 10 Original Android Development] HagardoVesrozy98:
Please update the mirror OP, it throttles the DL speed up to 80KBps.

---------- Post added at 08:58 AM ---------- Previous post was at 08:54 AM ----------

Please update the mirror OP, it throttles the DL speed up to 80KBps and even worse drops the connection.

I thought it was internet going bad but its just the file host.

Added this comment since I can't find the delete option from my reply above.
[Fire HD 8 and HD 10 Original Android Development] Shadow128:
It is now possible to watch HD Streams with the Amazon Prime App?

In the past I tested it with switching from original FireOS to Lineage (I think Lineage 12). In FireOS everything was fine, but at Lineage i could only watch in SD
[Fire HD 8 and HD 10 Original Android Development] toybits:
You can try kodi repo for amazon prime video. They were saying that in Kodi prime repo play more like HD quality in LOS 12. I think it will be SD only on root or unlock bootloader devices when using prime video app.
[Fire HD 8 and HD 10 Original Android Development] djdave37:
Fix partially working

I've installed this fix on Fire HD 10 2017 + LOS 12.1.

Headphone is now working, but if volume if more than 75%, sound is on headphone AND tablet speaker (with loud music). Very strange.
[Fire HD 8 and HD 10 Original Android Development] superdragonpt:
Sorry for asking, but could you explain in detail what is exactly the hw dec issue?

I'v been waiting for this device to arrive, and I would like to know in detail the issues.

Cheers ;)
[Fire HD 8 and HD 10 Original Android Development] lovaduck:
Hi, is there any fix for the camera issue? I remember some comments here about the possibility of compiling the ROM with different parms to make it work. D
[Fire HD 8 and HD 10 Original Android Development] dcxx20:
I tried to use moonlight and Xbox streaming apps. Either the moonlight or the Xbox streaming app refused to run. Forgot which one though since I tested a bunch of the streaming clients. Moonlight streaming works fine with 12.1 but Xbox streaming app won't run since it requires >5 android version. The screen and price of the tablet make it perfect for streaming...
[Fire HD 8 and HD 10 Original Android Development] karldonteljames:
I would also be interested if there is currently a fix available for the camera please. Trying to set it up for motion detection in fully browser.

Many thanks.
[Fire HD 8 and HD 10 Original Android Development] gobracket:
Hi,

OMX fix works for YouTube but not on vanced. Any idea?
[Fire HD 8 and HD 10 Original Android Development] TheDevil259:
Try reinstalling Vanced. That did the trick for me.
[Fire HD 8 and HD 10 Original Android Development] sakibstark:
I may be wrong but the last time i used this rom with the omx patch from Ziona, it ran YouTube videos perfectly. this time it struggles to run 1080p while running it in the browser works well.

Am i missing something?
[Fire HD 8 and HD 10 Original Android Development] TheDevil259:
1080p @ 30 fps videos work relatively fine. However 1080p @ 60 fps videos do not.
[Fire HD 8 and HD 10 Original Android Development] gobracket:
Solved. I enabled the vp9 codec from the setting and its working now
[Fire HD 8 and HD 10 Original Android Development] HagardoVesrozy98:
Has anyone managed to get streaming or screen record working on this ROM?
[Fire HD 8 and HD 10 Original Android Development] wanderso:
Clean install - Google Assistant install looping...

OK, I followed the OP's installation flow: boot into TWRP, wiped data, flashed LOS 14.1, gapps-arm64-7.1-nano, and Magisk. When the system starts up, I go through the usual Google/Android account setup OK, then I get to a window entitled "Voice search any time." No matter my choice therein, the app crashes and sends me back to the previous app (selecting various Android account options: backup, monitoring, etc.) I'm in an account set-up loop.

What did I do wrong, and how can I fix it?

PS - Is this a GAPPS problem? I used open_gapps-arm64-7.1-nano-20200721.zip. Do I need a different build?
[Fire HD 8 and HD 10 Original Android Development] wanderso:
Got it working. My workaround was to avoid setting up my Android account, get into the system and go from there. Installed the rest of the mods (Magisk, headphones, OMX). All good.

I suspect this is a bad interaction between this version of LOS 14.1 and the latest nano GAPPS 7.1. If I had used pico GAPPS , I would have probably been OK the first time.
[Fire HD 8 and HD 10 Original Android Development] bfink:
so how did that experience end? because i just did the same and even though it says it will reboot for a long time, i get doubt's it will actually ever end :(
[Fire HD 8 and HD 10 Original Android Development] bfink:
turns out it was a boot loop, had to re-format and re-setup. should have tried this before setting up everything ;)

i'm a bit sad now, knowing that if someone steals my device he gets access to all my data, so it's either encryption with the stock rom or using a mod at this point. or did the lineage 12 build work with encryption?