yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
As far as I understand it, every time you install a ROM it has the potential to reset root access and so you need to run kingroot again after each install to get it back.

Shoog
[Kindle Fire HDX 7" & 8.9" General] Mr McBoatface:
You have to enable root from developer mode , it's the same from all CM builds as far as I know.

See my post here https://xdaforums.com/showpost.php?p=70787943&postcount=4036 . The same method should apply for you and CM11
[Kindle Fire HDX 7" & 8.9" General] usman3206:
Thanks a lot, this worked like a charm. Using kingroot is dangerous, it's a virus 100%.

---------- Post added at 12:20 PM ---------- Previous post was at 12:12 PM ----------

- my daily driver is CM 12.1...a choice based solely on Xposed dependencies which has nothing to do with HDX specific customizations or compatibility

What is this xposed thing? how can we use it? I have searched it on google but haven't found anything useful.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
this HDX has yellowish tinge in display like samsung devices unlike HTC or LGs, is there a software filter kind of software that can fix this issue. do you know a way to do so?
[Kindle Fire HDX 7" & 8.9" General] Mr McBoatface:
I think Davey had it right earlier when he said you may have a defective device. Recommend you contact the seller and see if you can return/replace it.
[Kindle Fire HDX 7" & 8.9" General] DB126:
- OMG - never use Kingroot with a custom ROM unless explicitly instructed to do so in the ROM thread OP

- SuperSU must be flashed with CM 11 to obtain root (as indicated in ROM OP)

- enable root as outlined by [MENTION=7968177]Mr McBoatface[/MENTION] for CM 12.1 and above (including LinOS 14.1)

- in my experience recent builds of SuperSU have become unreliable with CM 12.1 resulting spontaneous loss of root that requires reflashing CM to restore

- I now use the native root manager on CM 12.1; works fine

---------- Post added at 11:29 AM ---------- Previous post was at 11:25 AM ----------

Recommend staying away from Xposed until your device is stabilized. If you must ... Xposed Framework
[Kindle Fire HDX 7" & 8.9" General] usman3206:
No this tinge is usual even in samsung's earlier devices, it doesn't look like a defective screen and with cm12.1 its working flawlessly until now
[Kindle Fire HDX 7" & 8.9" General] DB126:
Not a CM 12.1 issue (log 20+ hours per week on this device/ROM). Seriously mate - gotta stop blaming HDX ROMs for all the display/panel issues you have experienced. However, there are tons of apps in the Play Store (plus a few Xposed modules) if you want to tinker with the color pallet.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
sorry if i felt like blaming ROM, i feel some displays have this natural tinge like i had 2 laptops one has screen with a little orange/yellow hue another bit towards blue; its just that i like ones with bluish white hue. Rest about this ROM is superb cool, running very smooth but no doubt the Lineage with newest android had interface that gives much better experience than the one based on jellybean.
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
The user experience between the different CM versions is almost identical. There are various under the hood optimizations but they really have little impact on the use of a device like the HDX since it has resources and processor capacity to spare.

As my wife says, she can see only minor differences between her HDX7 running CM11 and her new Xiomia Redmi 3S running CM13. If you were to choose the same theme on the different versions I daresay that you wouldn't tell the difference without delving into the settings menus.

Shoog
[Kindle Fire HDX 7" & 8.9" General] DB126:
HDX panels have lower default temps than most small displays which tend to have a comparitivly blueish cast. Guessing Amazon choose that to improve the book reading and video experience for target FireOS audience (prime members). Independent tests ranked HDX panels superior to Nexus equivalents at the time and on par with Apple's best retina displays.

Seperately, CM 12.1 is based on Lollipop (Android 5.1). Nexus 2.0.5 is the only custom HDX ROM based on Jellybean (Android 4.2). The other Nexus ROMs you sampled were based on KitKat 4.4.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
I wasn't to try that LineageOs ROM, can you kindly Surat if I should try the builds by hashcode or ggow, what I have read on that thread it seems ggow ones are better. This cm12 has been working gray without any glitch at all so wanna give that android 7a try as it was really very polished. [MENTION=5488402]Davey126[/MENTION] your input is highly desired regarding that ROM' stability
[Kindle Fire HDX 7" & 8.9" General] DB126:
Core LinOS 14.1 is quite stable (as are all HDX ROMs) and is the only custom ROM being actively developed/supported at present. However, bluetooth/LTE remain a work in progress and WiFi does not always connect/reconnect after emerging from deep sleep. The latter is easily addressed by opening the WiFi connection page which seems to 'wake' the radio. You will need to decide if Android 7.x eye candy outweighs these trade-offs. In general it is usually best to go with the most recent build for your device type. Hashcode and ggow collaborate on most builds.
[Kindle Fire HDX 7" & 8.9" General] thumper_ss:
sorry for acting like a noob

stuck at no such file or directory im not sure what it is that i have missed i can upload my comand window if needed
[Kindle Fire HDX 7" & 8.9" General] jaesky:
Hello,

I just got a refurbished HDX 7" 3rd Gen (Thor) device with the following ROM:

HDX Nexus ROM v4.0.5 [MENTION=5749760]ggow[/MENTION]

Kernel 3.4.0-perf-gbfccc1e

The fact is I thought the bootloader would be unlocked since it has no FireOS from Amazon, but entering the following command, says it is not:

C:\WINDOWS\system32>fastboot -i 0x1949 oem device-info

...

(bootloader) Device tampered: false

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

OKAY [ 0.087s]

I have been reading several guides in this forum but I'm still confused. Should I still follow the step #2 of this post to unlock the bootloader even though I don't have a FireOS firmware or should just skip to step #3 (flash unlock code)?

I want to change the ROM to the last LineageOS version.

Thanks in advance!
[Kindle Fire HDX 7" & 8.9" General] DB126:
Welcome to the HDX forums. FireOS presence/status is irrelevant. Follow the unlock guidance in posts 550-560 including step #2 that involves flashing an updated aboot and recovery. Be cautious with step #2; be sure to grab the correct files and verify the signature (MD5) before flashing.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
one of my friend has HDX 7 with 64GB with SIM, will this method of bootloader unlock work for his device too?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yes w/caveats:

- device must be rooted (various ways to accomplish depending on current firmware)

- SIM data (no voice) support is only available in KitKat based ROMs: FireOS v4; CM11 or Fire Nexus

- All of the above ROMs are discontinued; they work fine but will not be receiving further updates

- If SIM support is not crucial then any HDX ROM may be installed (once bootloader is unlocked)
[Kindle Fire HDX 7" & 8.9" General] usman3206:
He doesn't use sim at all, he just wants to install newer ROMs based on android 7.x. So he can give it a try?

Thanks [MENTION=297200]Davey[/MENTION], you have always been very helpful.
[Kindle Fire HDX 7" & 8.9" General] DB126:
LinOS 14.1 (based on Android 7.x) should work fine.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
I have this 64GB hdx, it has kingo root and a kingoroot supersu already installed, i will try doing bootloader unlock. I think this kingo root is better than king root which definitely is a virus, what do you think should i keep this root method and its supersu?
[Kindle Fire HDX 7" & 8.9" General] usman3206:
ok, i was able to unlock bootloader of this kindle hdx easily but it's stuck in fastboot mode and powering off and on keeps it in fastboot mode, pressing vol up with power boots TWRP and rebooting into system inside TWRP makes it boot into fastboot again. How can i get into booting normal system?
[Kindle Fire HDX 7" & 8.9" General] unhappybirthday:
That happened to me. I had to flash a ROM to fix this. I was using Fire Nexus ROM which works with safestrap and non-safestrap so I was able to keep my data.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
I was able to reboot in system after wiping system, cache etc and reinstalling nexus-hdx (kitkat) onto it.

---------- Post added at 01:18 PM ---------- Previous post was at 12:58 PM ----------

Thanks a lot [MENTION=5488402]Davey126[/MENTION], i could install any ROM of my choice on this device too, i searched your previous posts and fixed almost everything. Bundle of thanks
[Kindle Fire HDX 7" & 8.9" General] haitinhvuong:
Sorry for a noob question, but what is the OP and where is it in the post?
[Kindle Fire HDX 7" & 8.9" General] DB126:
OP (Original Post) is the first one in this thread.
[Kindle Fire HDX 7" & 8.9" General] carnell:
I'm sorry to ask this, but my thor enters twrp using <power> + <vol+> combo and enters fastboot mode using <power> + <vol->. Would this indicate an unlocked bootloader? Thanks for any help.
[Kindle Fire HDX 7" & 8.9" General] draxie:
More than likely, yes.

You can easily verify from either fastboot or adb

(assuming you have FireOS) by running idme.

fastboot -i 0x1949 oem idme ?

adb shell su -c "idme print unlock_code"
[Kindle Fire HDX 7" & 8.9" General] KilgoreTrout71:
The above quote is just an example. Nobody here that I can see seems to have trouble generating the unlock.code file, but I do for some reason.

I'm using Minimal ADB & Fastboot, and I unpacked the contents of unlock.zip into that folder. Running get_unlock.bat prints the two hex codes, but no unlock.code file is generated anywhere.

If someone could offer some guidance, I'd be grateful. I've been trying to get this thing unlocked for some time now on my own. Now I'm throwing up my hands and hoping someone knows what the crap I'm doing wrong.

BTW, my device is Apollo on 4.5.2 firmware, rooted. Thanks!

KT71

Edit: Solved own problem, eventually. Noob mistake. Had to run batch file as administrator.
[Kindle Fire HDX 7" & 8.9" General] mliyy:
it is all my fault.my device is apollo,nexus4.4.4. when unlocking bootloader,i put the wrong file into interstorage,that is thor's aboot vuln and twrp cube.and then my hdx8.9 cannot enter recovery,bootload and system,only display background light.i can still see its storage in computer,but shows do not find device in adb .so what should i do to save my apollo?i am appreciating for you help..
[Kindle Fire HDX 7" & 8.9" General] draxie:
BULK MODE

Here's a set of instructions that _SHOULD_ work to recover your device.

We had two recent successful cases, and I've only managed to brick

one of my test devices experimenting with this.

Nevertheless, the standard disclaimer still applies: your device, your risk.

If anything goes wrong, I'm not responsible.

Open a command window (cmd, NOT PowerShell!!) and run the following commands:

wmic partition where index=22 get diskindex
wmic partition where (index=17 and numberofblocks=20480) get diskindex
wmic partition where (index=5 and numberofblocks=4096) get diskindex

All three of the above commands should return the same DiskIndex.

Let's call that index X.

Download and extract http://www.chrysocome.net/downloads/dd-0.5.zip.

In the command window, change to the directory with the extracted dd.exe

and run the following two commands with the right aboot&twrp files for your device

(you will need to substitute the DiskIndex X from above in place of the red X):

dd of=\\?\Device\Harddisk[COLOR="Red"]X[/COLOR]\Partition6 if=aboot_vuln.mbn
dd of=\\?\Device\Harddisk[COLOR="Red"]X[/COLOR]\Partition18 if=twrp_cubed.img

This error message on the first command seems normal: "Error reading file: 87 The parameter is incorrect"

NB: make sure you run both commands! Without TWRP, you'll get a brick.

Wait a few minutes for good measure; then, keep holding Power + VolUp until your device enters TWRP.

[MENTION=8087953]bluecoyote[/MENTION], [MENTION=7968177]Mr McBoatface[/MENTION] (or anyone else starting from fastboot)

I have all the ingredients for a script, but haven't had time to put it all together.

The above instructions work, once you put your device into "bulk mode".

To do so, you'll need to run these two fastboot commands:

fastboot -i 0x1949 erase aboot
fastboot -i 0x1949 reboot

NB: this will be scary as you'll lose 'fastboot' and only see a black screen.

Your device should reboot into "bulk mode" resulting in a number of pop-up

windows asking to format all the partitions that get exposed (at least, on Windows 10).

DO NOT format anything! Follow the above instructions instead.

Oh, and YES: this should also work on any unrooted & locked 3rd gen HDX device.

You need to enable ADB and run the following command to enter fastboot:

adb reboot bootloader

This is arguably faster (and less malware-ridden) than trying to root with Kingroot,

but it's easy to make a small mistake and end up with a brick.
[Kindle Fire HDX 7" & 8.9" General] Mr McBoatface:
So followed the instructions, all seemed to go well but at the end it just boots to into fastboot. Then I try to manually load twrp using the "fastboot boot twrp_cubed.IMG" I get a Fail : boot not allowed for locked hw

Can erase the aboot and return to bulk mode and repeat the steps but get same result

EDIT: Forget the above, I can boot into twrp. Needed a long press power down and the time it took to make a cup of coffee before restarting.

The device was not unlocked but I was able to install the nexus KK rom which I had left on the internal SD card. From there I unlocked the hardware

Totally excellent :)
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
Had to upgrade my wifes other Kindle which had been running CM11 on safestrap for a year and a half. Went fine.

We migrated her google account and apps to the Kindle I had previously set up using the instruction found in this thread - this went without a hitch and fairly much cloned her setup from the CM11 to the CM13 (fantastic feature).

Anyhows, what I wanted to say is that the guide at the start of the thread has been cleaned up and the new batch files work much better than previously. I managed to get CM13 loaded onto the old safestrap running kindle in about an hour (and most of that time was involved in re-rooting the kindle). The batch files are a simple two step solution which automatically launches the Kindle into Fastboot mode and flashes the unlock code. So so easy.

Shoog
[Kindle Fire HDX 7" & 8.9" General] DB126:
Great! You may want to consider CM/LineageOS 14.1 over CM 13 as the latter had been depreciated and is no longer receiving updates. Only downside is the lack of Xposed support which may never come to Nougat based ROMs.
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
I was looking at that - but have all issues with the camera been resolved ?

Shoog
[Kindle Fire HDX 7" & 8.9" General] DB126:
Works fine for some; others claim images are dark. Haven't noticed a common thread. Thinking this is probably low on the fix-it priority list given the queue of other issues (every ROM has issues) and limited developer resources.
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
Which probably means we will stick with the CM13 for the moment. The only reason we upgraded was because Facebook and a few other apps are starting to go buggy on CM11.

Shoog
[Kindle Fire HDX 7" & 8.9" General] moonsoo:
I used the script get-code and it seemed to work.

But when starting the unlock batch file it went to fastboot but then it says waiting for device.

Am I missing something?
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
Your fastboot driver is undoubtedly wrong. Trawling back through this thread should provide a link to where you can get the correct driver. It the most common issue that seems to occur with this procedure.

Stephen
[Kindle Fire HDX 7" & 8.9" General] moonsoo:
Hi all,

I have a question regarding repacked latest 4.5.5.2 rom.

Finally I returned back to stock ROM as it is the only ROM to play prime video in Full HD.

And I use this device mostly for video playback...

But the player looks different as it used to be and also only indicates HD and not full HD any more.

Some know where to get a 'real' repacked ROM flashable with TWRP?

BTW is there a chance that youtube plays also in full HD?

Many thanks in advance!

Greetz
[Kindle Fire HDX 7" & 8.9" General] DB126:
The last TWRP flashable FireOS ROM is 4.5.5 available here. It's possible to roll your own from a stock 4.5.5.2 image. If interested I'd have to do some digging for the link/instructions and you'd face a moderate learning curve as not many have gone down this path.

See this page for list of available formats. I don't see "full HD" listed as one of the available formats. Also note the following caveat from the linked page:

"Note: At this time, Amazon Video titles play in SD on Android devices."
[Kindle Fire HDX 7" & 8.9" General] draxie:
upHDX

You can use upHDX from my tools thread.

That's what I do. Lately, I had to delete some FireOS components I don't need to leave enough room for GAPPS.

I chose not to include that in the script, as it's impossible to tell who wants to keep what. I just perform the rites

from TWRP (reboot, once the ROM is flashed, and remove stuff before flashing GAPPS). Here's what I delete:

86M system/tts
19M system/priv-app/FireflyAppFireOS-release.apk
76K system/priv-app/FireflyIdentifiesSDK-release.apk
104M total

The script is originally for Linux, but it also works on Windows (via Cygwin).

Newer versions of Windows are supposed to have native support for 'bash',

but I haven't had a chance to test that...
[Kindle Fire HDX 7" & 8.9" General] Finners:
Hoping you can help me, Im trying to follow your guide as i cant root my thor with kingroot it seems but im stumbling at the first hurdle .

Im getting "no instance(s) available" when running the any of the first commands to find out the disk index. Any idea why this is?

Tried in fastboot and just with the tablet on
[Kindle Fire HDX 7" & 8.9" General] draxie:
https://xdaforums.com/showpost.php?p=71718405&postcount=199
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
HELP! I did this without a glitch on my HDX 8.9 but when trying to mod my friends HDX 8.9, I am stuck in a bulk mode loop where it keeps connecting asking to format various disks, then disconnects, etc. etc. Never stops this loop. I must pull the adb cord. Any way to fix this or did I brick it?:crying:
[Kindle Fire HDX 7" & 8.9" General] draxie:
I haven't encountered this behaviour, but I don't think it's bricked.

If I understand correctly, you haven't used the numbered steps yet,

due to those unexpected disconnections. We need to figure out

why those happen and prevent them. One way to get such a loop

would be to keep the power button pressed. Can you check that

the button isn't stuck or pushing against something by accident?

I suppose, the computer (including installed drivers) could also

make a difference... Are you using the same host to fix your friend's

HDX that you used to fix your own?
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Yes I am using the same host windows 10 pc. It just was upgraded by windows once, not completely but one of their normal upgrades. I do not get a screen on the hdx so I can't tell if it is off or on. When connected to the host it starts the on /off loop so I can never give it a command via adb now. I think I gave it all the right commands in your steps in this post. Any ideas?
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
UPDATE: It finally stopped boot looping and is on but in device manager there is this:

Other devises = QHSUSB_BULK (has yellow error triangle)

Portable devices = E, G, H, I, J, K, L, M, N

all nine have same driver "WPD FileSystem Volume Driver"

There is not adb/fastboot connection.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Great! Then you should be in business to start with the numbered steps.

Not having adb/fastboot connection in bulk mode is expected/normal.
[Kindle Fire HDX 7" & 8.9" General] jakko13:
I can get my device into bulk mode, but when running the dd command:

dd of=\\?\device\harddisk1\partition18 if=twrp_cubed.img
dd: failed to open '\?deviceharddisk1partition18': Permission denied

I am on Win 10 have tried using both CMD/Powershell and Cygwin.

UPDATE: I found a file system error and have booted into twrp!
[Kindle Fire HDX 7" & 8.9" General] bonya1423:
Has anyone got ERROR 7 when trying to flash the rom from TWRP?
[Kindle Fire HDX 7" & 8.9" General] DB126:
"The ROM"? Which one of the half dozen available for this device might that be? As for ERROR 7, yes this has been reported in several threads along with various solutions. The easiest is to downgrade TWRP to 3.0.0-1 which can be secured from the OP in this thread. You can either flash to recovery partition or boot from fastboot using command: fastboot -i 0x1949 boot recovery <recovery-image>
[Kindle Fire HDX 7" & 8.9" General] bonya1423:
Thnx for reply.

Just any rom, I've tried repacked 4.5.5.2, CM14, Linage 14 and so on.

I've just flashed 3.0.0.1 over 3.1.0.0 and it gave no result, I'm still getting ERROR 7 when trying to flash any rom via TWRP.

Exact error message is:

Previously I've had stock 4.5.5.2 and followed instructions in start post of this topic.

Not sure about flashing boot, which boot should I flash? Am I right that there's no way to flash custom rom via fastboot?
[Kindle Fire HDX 7" & 8.9" General] DB126:
- be sure to wipe system and data partitions after launching TWRP 3.0.0-1, power down device and restart; sometimes fixes ERROR 7s

- CM 12.1 (assuming bootloader is unlocked) or KitKat build of Nexus should flash fine if you are just looking to get a ROM installed for temporary work

- another workaround for LinOS 14.1 (there is no CM 14.1 for this device) is to remove the first line in updater-script as documented here; read back a few posts for further context

- not sure where you are going with "flashing boot"; can't do that; if referring to step #2 of the OP just follow the instructions

- the system partition can be populated from fastboot but you don't want to go there; no reason to not use TWRP for flashing ROMs
[Kindle Fire HDX 7" & 8.9" General] bonya1423:
Thanks a lot! this one worked out with TWRP 3.0.0.1

But the best option would be

can you suggest any ways to flash this one? I hope GSM and GPS work there.
[Kindle Fire HDX 7" & 8.9" General] DB126:
You can flash this from TWRP. GSM (data only) will probably work; GPS will not...at least for navigation. GPS chip sucks in this device and is only good for approximate (largely static) location identification. Both KitKat based custom ROMs also support LTE/GSM: CM 11 and Fire Nexus (recommend the latter).

Also believe you can flash repackaged 4.5.5.2 from your previous post. Don't have any direct experience with those images; you'll need to confirm with [MENTION=5828306]draxie[/MENTION]
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
YES! Much joy now. Got it back going full bore with Lineage 14.1 and TWRP.

Thank you so much [MENTION=5828306]draxie[/MENTION].

Your instructions are easy if they had combined post two also.

Can this bulk mode be used for other kindle fires or is the aboot device specific as is TWRP?
[Kindle Fire HDX 7" & 8.9" General] draxie:
I'm glad it worked out in the end.

I'm not sure what you mean by post two...

AFAIK, similar modes exist for most Qualcom devices, but there are at least

2 different bulk modes for the HDX, and there are surely variations among

different devices/OEMs. I have no idea if Fire devices based on other chipsets

with different bootloaders have similar safeguards (e.g. MediaTek with uboot),

but I wouldn't be surprised. Having said that, I'd not normally experiment with

erasing the bootloader, only as a last resort when nothing else works.

Now, that we have this tested and working on the HDX, this case is OK. (^;