yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Rollback to the previous (28 May) build; works fine.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Not seen that issue, post a log at and I'll take a look.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
Hey folks if you want use magisk on July Apollo Rom you need flash this patched boot img after you flashed the rom. Have fun

The latest Rom works fine and fast. Thanks for the update [MENTION=5749760]ggow[/MENTION] very good upstream. Clean many files.

How to flash the latest rom without bootloop.

Wipe all cache and system partition.

Flash rom

Flash gapps (pico or nano) i recommend pico

Flash my patched boot file I create for both

Reboot and enjoy magisk

The patching process in recovery fails because it thinks there is some force encryption.

[MENTION=5749760]ggow[/MENTION]

I checked your kernel config.

Bfq is not set as default still cfq

Interactive is not set still on demand

Maybe upstream this can help to fasten the device

Maybe its possible to add adreno idle 133 mhz to save some juice

Live display option low energy on display cause flickering. Should be disable by default

Basic integrity is lost now. Can't fix with other fingerprint. Netflix and other apps not compatible anymore
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Thanks for the info, I had trouble with some of those configurations. Need a bit more work and testing. Will investigate more. Adreno idler crashes our kernel. Will take me some time to figure out.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] pxrave:
I thought you already tried this. Bad drivers make it very hard to debug all these stuff. If you know how to add scheduler for example zen or upstream all Available. You can compile just new kernel to test. Don't need to invest the time to rebuild the whole rom. ?. I will help where I can. Great work you did.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
I would love to see limited resource focus on bringing Lineage 15/16/17 to the table as KitKat based ROMs will soon be obsolete. Adding schedulers and GPU tweaks is just tinkering around the edges with no meaningful gain.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] zswielder:
I'm sorry that yours died. Before it did though, was your LTE working with this ROM?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cl-i:
As far as I understood the development history of our HDX, ggov reached the limit of the binary-only ROM components and they made it inpossible to jump to LOS 15 and beyond.

So we should be happy that he dind't left us alone. Check the other ROMS for the HDX and there is nothing left up-to-date.

For me the latest ROM is doing well, so please please go ahead, ggov !!

By the way, LTE is also working.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Not my understanding but may have missed a post. If Android 7.1 is indeed the terminal version for HDX then whatever enthusiast enhancements/tweaks come in future builds are more than welcome.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] zswielder:
Are you on Thor or Apolo? And, which sim are you using? My Thor's LTE isn't working.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cl-i:
I have both versions running with LTE. Using with german providers O2 and vodafone.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] zswielder:
Did you have to do anything special to make LTE work? I was running CM11 on my thor, and LTE was working (granted it would take forever for it to kick in after powering on the device). I then moved onto the latest LineageOS in this thread. Even after giving it a ton of time, LTE never works now. It eventually recognizes the sim, but it doesn't establish any connection. If you have any advice, I would very much appreciate it.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cl-i:
Well, let's try to sort out the problem.

In which country and with witch provider are you trying to bring the LTE to life ?

To you tried to reduce LTE down to 3g?

I'm used to operate the tablet in airplane-mode and than activate the LTE on demand.

And last but not least: My SIM was not working first, so I deactivated the PIN. Perhaps this is the trick I didn't recognized as **IT**
[Kindle Fire HDX 7" & 8.9" Original Android Develop] zswielder:
What did you mean by deactivated the pin?

I am in US. I have a T-mobile sim and Google Fi Data sim. Both sims worked just fine on CM11, but they are not working in Lineage. I tried selecting 3g without any success.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
@cl-i is right

Try the following:

1. ensure PIN number on sim card is disabled.

2. If you cold boot your device, sometimes LTE does not come up first time, a reboot or two then it normally comes up

3. If it still doesn't work, post a logcat of your boot sequence, dmesg and I'll take a look.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I have only one show stopper for lineage-15.1+ on our HDX's and that's WiFi. Some of the legacy API's needed were deprecated in these newer versions. Just need the bandwidth to complete the work. Since Covid hit, work has been exceptionally busy.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cl-i:
Perhaps we can find another Tablet / Phone with fresher libraries on the same wifi chipset ?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I've looked, there just isn't anything relevant using this wifi chipset.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cl-i:
I had wikidevi.com in mind, but the site doesn't respond at the moment :(

Is the snapdragon-800 (msm8974) what makes us trouble?

https://www.kimovil.com/de/liste-smartphones-nach-prozessor/qualcomm-snapdragon-800-msm8974

Because according to this list, the Samsung Galaxy Note 3 could be a good companion.

https://wiki.lineageos.org/devices/hlte/

Otherwise sorry to waste you time..
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
These msm8974 devices are irrelevant to the issue.

The HDX uses a different SoC which is the APQ8074 and not msm8974.

Also there is a separate wifi/bluetooth chipset, QCA6234

See the attached block diagram

I know what needs to be done, just need to complete the work.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
For lineage-15.1, in all the focus getting wifi working, I didn't notice that audio isn't working either :(
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Fallingwater:
I have a Thor HDX. I was on this rom with an old 2017 version. Decided to update, so I flashed the latest TWRP (which worked fine), then wiped DATA, flashed the latest Lineage 14.1 for Thor, wiped cache/dalvik, and now it's stuck in the boot animation (edit: while getting pretty toasty). I've waited half an hour and it's still doing the little blue dot smile thing, so I'm fairly sure it's actually stuck and not just sloooowly booting.

Edit: I rebooted it. Predictably, it changed nothing.

Is it mandatory to flash gapps for it to work? I didn't want them this time around as I intended to stay off the Google framework and just use the Aurora store to load my apps, but perhaps it needs them to boot?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cl-i:
Well, that's what I call a DIRTY flash :)

If you are about to loose too much by a clean flash, try to flash the old rom your way first to recover.

At the end you will have to make a more clean install.

ROM and GAPPS for sure if the old ROM version wasn't 14.1. Clean SYSTEM too.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Fallingwater:
I didn't do a dirty flash; I forgot to mention it in the previous post, but I did wipe DATA - I edited the post to show that. I did not wipe SYSTEM though - but I never found that to be necessary in the past to boot the device.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
No gapps required. Try a factory reset. Works fine here.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Fallingwater:
Turns out my volume buttons are broken and I can't access TWRP anymore. I did a reboot recovery from terminal when I flashed and didn't notice this problem.

I read that you can use a modified microUSB cable to get the tablet to boot into fastboot. I could make the cable easily; can I get it to reboot into TWRP recovery with a fastboot command?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cl-i:
fastboot -i 0x1949 reboot-bootloader
[Kindle Fire HDX 7" & 8.9" Original Android Develop] void555:
Have you tried to wait for at least 5 minutes (that's timeout value for blacklisted APs) - does it connect then?

"10 times a day for me" - do you mean you reboot your router 10 times a day or tablet disconnects on its own and fails to reconnect?

In my environment I can reproduce occasional (not 100%) "do not connect for 5 minutes after router reboot" and it happens due to blacklisting AP after 3 unsuccessful connection attempts. Not sure this is what happens in your case.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cl-i:
Thanks god my wifi is very solid and stable. I switch off the WIFI router at night and turn it on in the morning.

When I restart the tablet after that, it will operate fine with my regular going to airplane mode and back online again.

Not restarting the tablet results in non of my wifi reconnects will have success.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] nguyenlucky:
The Sony Z2 Tablet also has APQ8074 and got an AICP Q build, maybe you can take a look at that?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
this rom seems more stable, well with the the wifi anyways. was using the last one and my wifi kept on disconnecting. flashed this one and has been up for 36 hours and hasn't dropped out yet. other rom was dropping out about every couple of hours.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Unfortunately no, I have the newer roms booting. It's the HDX's weird wireless chipset that's the problem. The Z2 uses a broadcom chipset which would have been much easier to work with.

However I have the wifi module now working under lineage-15.1 in prototype, however needs more work.

Then onto figuring out audio which doesn't work at all yet, which is funny because it was working on a very old build of lineage-15.1 that I initially was working on.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Let me know how you get on over time. Also what model router are you connecting too etc.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
No problem, up to now still no drop in WiFi, also I'm running the rom without magisk and xposed which I was using on the other rom, so not sure if that might of been causing an issue, will test this rom with magisk and xposed at some point and will let you know. I'm using the Asus dsl-ac68u and tablet is connected via 5ghz channel. Thanks
[Kindle Fire HDX 7" & 8.9" Original Android Develop] hwwof:
Did you end up being able to update successfully? I am on TWRP 3.1.1.1 with an old version of lineage and now I am afraid to update cuz of your story, and others takling about magisk, which I have installed x)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
I just ordered a kindle fire hdx 8.9 3rd gen tablet on ebay that had a broken touch screen so hoping to repair my current tablet. I will need help hacking it once I get it all up and running again.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
which magisk works with this rom, my bootloader is unlocked, but every time i flash magisk the tablet just keeps going into fastboot mode. restoring the boot.img fixes it but still no root. any help would be great, thanks

note: ive manged to get it sorted. found the other post that i needed the magisk thor boot patch.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
Thanks for this, I was having issues with my tablet booting into fastboot mode after flashing magisk. worked a treat. thanks
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
Well its just been over a week and the WiFi has not dropped once. With and without magisk and xposed installed there is no problem with WiFi at all. :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Have you powered down yet? My HDX (have three) can go for long stretches behaving as you describe only to adopt a different personality after a power cycle. After a few days I'll just reboot and things will be different once again. Kind of get used to it.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
Yes I had to power it down after 5-7 days of testing without magisk and xposed, its been powered down a fair few times, the WiFi hasn't dropped yet, I was trying to see if the WiFi issue was because of the rom or with magisk or xposed. But still working fine, when I was on the other lineage until it got updated I had wifi issues constant. Dropping out every 30 minutes to an hour, and that was after a clean install. Fingers crossed it lasts. Will update if it happens
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Great! I also load latest builds of Xposed and Magisk (although used SuperSU 2.82 SR5 for years w/o issue). At present I'm experiencing a prolonged period with no dropouts but lazy AP acquisition after exiting airplane mode. Simply opening settings usually resolves with a quick connection to a known AP. Not a big deal.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
Powered it down 8 hours ago to test WiFi, boots up fine connects to WiFi without a problem and been running to now without an issue. Bluetooth still a bit hit and miss, im using my tablet for xyo crypto collecting and needing constant connection. Which is what I tried to use before and thats when the wifi starting doing my head in. Constant disconnections and wouldn't reconnect. So thats I can tell its way better then before.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Cl4ncy:
Does anyone else have hard crashs/reboots with the latest Firefox?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] player594:
Well damn. I'm stuck in fastboot after flashing latest rom from TWRP. Stupidly tried to dirty flash over older version. Any fix?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Cl4ncy:
If you have the actual TWRP you should be able to access it when turning on the device. Are you sure it was TWRP and not SafeStrap?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] void555:
Everyone has. I have sent working patch to ggow, still waiting for reply and/or new build.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] player594:
Well I got back into TWRP and flashed the old version I had. Now I'm stuck at the endless boot animation.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
I just got my device (replaced the screen it had that was cracked with the one from my dead tablet). I got 32gb model. I need help unlocking the boot loader and getting lineage os on it. Can some one help me.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
https://xdaforums.com/kindle-fire-hdx/general/how-to-root-unlock-hdx-noobies-t3916167

https://xdaforums.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
Thank you.

so should i stop following this one?

https://xdaforums.com/showpost.php?p=75284993&postcount=1006

I got to the fastboot part but windows says no device attached and fastboot not saying ok
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
The thread you referenced is fine and serves as a definitive source for most other guides. You are likely experiencing a fastboot connectivity issue which is very common on HDX devices. Try a different USB cable and /or port, preferably USB2. Avoid USB hubs. Make sure the correct driver is selected in Windows device manager after attempting a fastboot connection. You may have to reboot the host if it refuses to connect. Finally, I have had the best luck with Moto drivers which you will find linked in the thread you referenced. Good luck.

https://support.motorola.com/us/en/solution/MS88481
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
I am at a real loss. I tried what you suggested and even tried another pc but fastboot wont connect to the pc. Driver keeps saying no device and i tried 64 bit motorola drivers but nothing happened.

My fire tablet on 4.5.5.2 if that needed. Should I factory reset it and try again?

I do not have it connected to wifi. I tried my original 3rd gen hdx cable and kept getting failed usb device something so switched to my 4th gen cable and detected fine in normal boot mode.

https://media.discordapp.net/attachments/685472623898918922/749669529868828762/unknown.png

is the issue I am stuck on.

Factory reset did not fix the issue.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You should probably try the 1-click tool referenced in a previous post. HDX devices are devilishly difficult to unlock; communications issues are common. Unfortunately, I have moved on from this device and not really in a position to provide detailed assistance. Good luck, mate.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
Sadly that not a solution for me since I run windows and it not windows compatible
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Perhaps consider a different device that is easier to root. If not an option spend some time in the thread you originally referenced. Others have experienced similar issues. Perhaps a clue (or collection of clues) will surface a solution.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
I installed lineage os on my pixel xl (verizon model) gen 1 and a samsung tablet so i do have experience and thought i would fix my dead hdx 3rd gen tablet and try lineage os.

I also found out just now that the ready sign does appear when booting the pc but right when windows loads it goes to offline.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Those devices were relatively easy to unlock/root. 3rd gen HDX presents some different challenges.

The symptoms you most recently observed point to a Windows driver program. The Moto drivers I previously referenced work best on this device although you are certainly welcome to try those mentioned in other threads. Note you will likely need to switch drivers when toggling between adb and fastboot modes.

Pay attention to the drivers installed with Moto Device Manager (which does not need to be running). Believe there are three. Forget which one works best with fastboot but isn't hard to figure out. Also know Windows can be quit stubborn about switching drivers for devices it has already seen. A reboot may be needed between attempts when switching.

I assume your device (FireOS 4.5.x) is already rooted. That is a prerequisite in the manual bootloader unlock thread that thread you are following.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
Ya I am on 4.5.5.3 (just updated last night so i could use the wifi). I got google stuff installed (found a xda thread with a video on doing it for this os version). I do not have root as I not gotten to that step yet due to fast boot. I will try those Motorola drivers again.

I got root :). Just side loaded installed kingroot and worked fine. No bloatware was installed either it seems.

The Motorola drivers fail for me. I tried loading the driver and says none exist to select. (installed 64bit)

Should i ignore fastboot and continue through adb command parts?

I also pmed the 1 click utility person for a link to download just in case there a windows version.

I am extremely close. I got all the files needed, got root and the ones required on the fire device. I just am missing fastboot so hoping to see how to fix that with this utility.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You need to solve the fastboot communication problem; bootloader unlocking can only take place at the level (must be tethered). Windows drivers are the likely culprit as previously noted. There is no reason the Moto Device Manager install should fail nor drivers not being available/selectable after installation. Please post a screen shot of the error dialog so I can understand the context.

Edit: You're not close at all; many more (often difficult/challenging) steps ahead. Not trying to be a wet blanket. Is what it is.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Progress

Hi all, what little time I have is going into getting audio working on lineage-15.1 +...

will keep you posted.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
Should I pm you to continue this conversation in helping me? I dont want to fill this thread up with a ton of stuff that might be better said in a pm so bloat doesnt happen. (might be sending a ton of picture links of the screenshots i got of my current situation or a video idk yet)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Nah - keep it public. Others may benefit from the conversation (obviously keep it concise/relevant whenever possible).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
Ok. Here are the pictures I thought were needed to help show my situation.

https://media.discordapp.net/attach...2753045585/unknown.png?width=2403&height=1351

https://media.discordapp.net/attach...2720447547/unknown.png?width=2883&height=1190

https://media.discordapp.net/attach...9905533015/unknown.png?width=2883&height=1142

So I tried a different driver from some website listing all the drivers (downloaded moto g6 driver). (it was the same one you linked earlier but for some reason this driver let me see the drivers this time). I tried that driver shown in the picture. It says ready now but fast boot still now showing my device id.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You have to drill down to the desired driver in Windows device manager, sometimes trying a few variants to identify one that works. Simply installing the Motorola Manager package won't automatically select the correct driver for fastboot operations. Often the one used for ADB won't work with fastboot despite being labeled composite. As previously mentioned, this can be a frustrating exercise as Windows sometimes refuses to connect w/o a reboot even when a compatible driver is selected.

These issues seems specific to HDX devices connected to Windows hosts. I have never experienced this with other Android gizmos. Not alone; most other first time users experience the same thing.

Glad you got to "Ready" with the G6 driver (probably several) which is likely the same as those installed by the Motorola device manager. Lack of a device ID means communication still isn't taking place. Try a couple different drivers within the Moto folder, swap cables, USB ports, etc.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
I will try that once i take a break some :). It exhausting trying to get this to work but I think I made progress.

WHOOOHOOO.

I removed fire drivers and Motorola ones. Rebooted pc and was planning to reinstall them but decided lets first see if the google or Samsung ones i tried before that did not work work this time. The 2019 drivers failed but the 2010 Samsung ones (idk how i got them) worked!

https://media.discordapp.net/attachments/685472623898918922/751121275782561852/unknown.png

I unlocked the bootloader (there a mistake in the document i found). The command to aboot it not typed right first time but second time it mentioned it worked fine.

I installed twrp and lineage build newest one done here (july 5th 2020 i think) and gapps. How do I get magisks working or flashed with this tablet? (I remember some one said there was a patched boot image or something but I can no longer get that since the link dead).

https://media.discordapp.net/attach..._20200903_134825_01.jpg?width=760&height=1351
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Dragon Kumera:
Taming Master crashes on app load. Also where the black theme for settings and stuff?

Disney+ crashes after login. Evertale lags majorly. (just thought to let you know in case fixes can be made in the new build your working on.