yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Humm...too similar to be mere coincidence. Will try to duplicate your findings on a spare HDX. Unfortunately, I won't be able to execute for 12-24 hours due to other RL obligations. Will get back to you with results. Sorry for delay ...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Impatient?

I'm starting to seriously wonder if all these people

with a "hang" on **OS logo** (including [MENTION=4823934]futu[/MENTION]508

on CM13) are simply impatient... The first boot after

flashing a new ROM (wiping cache, data, everything)

takes considerably longer (on the order of minutes,

sometimes in excess of 5, although rarely over 10 )

than a normal boot. And, guess what you see in the

meantime: the OS boot logo...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Yep, had the same thought overnight; literally woke thinking about this issue (note to self: get a life!). I hope to verify today with a clean flash of the latest AEX, GAaps and SuperSU builds on a virgin device.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] fufu508:
Hi [MENTION=5828306]draxie[/MENTION] [MENTION=5488402]Davey126[/MENTION] mine was an actual broken cm13 installation from 2016. My cm13 splash screen stayed that way all night :eek:

I'm grateful I was able to get recovery working with your help so I could get this nice new OS on here. I'm typing this reply using Google Voice typing with Hacker's Keyboard) in my Kindle. A huge improvement over fire OS and cm13!

I'm also going to post a hardware hack for the volume control cuz I got that working finally...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] notjoken958:
[MENTION=5488402]Davey126[/MENTION], [MENTION=5828306]draxie[/MENTION] and [MENTION=8790220]fufu508[/MENTION], I left kindle fire logo on all night also. I figured a good long wait was better than my messing something else up.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Well...first round of testing was unrevealing. Flashed AEX 20171119, GAaps nano, SuperSU 2.82 SR5 and Xposed Framework 88.2 in one operation followed by a successful reboot. The only immediate difference that comes to mind is aboot. All my HDX devices have the original bootloader installed with FireOS 13.3.1.0; I never had to 'downgrade'. Perhaps there is some subtle difference when coming from 4.5.5.x. Although many/most have traveled this route w/o incident. Have to think on this one a bit more.

Curious - have either of you (@lvnambg97; [MENTION=5863414]notjoken958[/MENTION]) tried a different Android 7.1 based custom ROM such as LOS 14.1, Slim 7 or Resurrection Remix? If you are able to flash GApps and/or SuperSU on those builds then it's an issue with AospExtended. Sorry if you have already commented on this point; my brain has the consistency of peanut butter at the moment; synapses are having a hard time making connections across the sludge pit.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] notjoken958:
This is only Rom flashed after coming back from boot loop.

After reviving tablet, flashing aboot and twrp, tried to run [MENTION=5828306]draxie[/MENTION]'s 1 click unlock.

I had forgotten to run get code.bat, so unlock did not happen. Fastboot said "OK", not "unlocked". I don't remember the exact phrase.

That is where I WAS, I figured it out the next day.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Got it this time - you're all set after bootloader unlock. Yep - you already said that; little slow on the uptake. Enjoy your liberated HDX!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] lvnambg97:
I tried many roms (Slim7, CM14, CM13) but all have the same error.

I also do not know if this is because of the bug version of FireOS as you said or not because when I bought it was already in Android 4.4 :( (2rd Kindle)

---------- Post added at 02:41 AM ---------- Previous post was at 02:38 AM ----------

Is there a problem with the bootloader? I have already installed a recovery, so can I using your click bootloader to solve the problem?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Clearly not AospExtended related. That narrows the possibilities:

- whacked bootloader (unlikely for a number of reasons)

- hardware issue (equally unlikely with no other symptoms)

- procedural (gotta toss that one in there; human is often the weakest link)

- lingering detritus

Let's try to eliminate the last one. Use the Advanced Wipe options in TWRP to select all partitions including Internal Storage. Note this will obliterate all content on the device; make sure you can establish an adb connection to the device (and push content to it) BEFORE taking this step. After the wipe completes you MUST reboot to reestablish critical directories. Use ADB to push a ROM, root solution and GApps package to the device. Install all packages on one operation and then reboot system. Hopefully no hang ...

If the device does hang you may need to format (vs simply wipe) one or more partition. See commentary here.

N.B. I'm running out of ideas so the above may seem a bit radical. Grasping at straws would not be an unfair characterization.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] BOFH2k:
Am I correct in assuming that for switching from LOS 14.1 to AEX 7.1 I must wipe my device completely?

Have installed AEX and GApps after wiping cache, Dalvik and system partitions in TWRP 3.0.3 Advanced Wipe (with reboot before install) and now suffer from regular android.process.acore close popups.

Don't have a PC with adb at my disposal right now, so I didn't touch TWRP nor internal storage... I wonder why retaining the data partition would cause such issues, as my understanding was that the ROM fully resides in the system partition?

---------- Post added at 09:23 AM ---------- Previous post was at 08:28 AM ----------

OK, finally figured out that the contacts storage had to be wiped (and the storage of the clock app, incidentally)...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
Anyone have any ideas why magisk and SuperSU prevent this from from booting? Every time I flash them, the HDX won't boot.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Yousucks2:
Are you using lastest versions of both apps?

I dont have any problems with SuperSU, installed from TWRP recovery, i used superSU oficial site ZIP.

Try other version compactible with nougat.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
Yeah I'm using the most recent version of both... Let me give super super another try.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You are the 3rd or 4th member to report this in recent weeks. To the best of my knowledge root cause has yet to be identified along with a universal solution. The only 'fix' is a comprehensive device wipe (including Internal Storage) and explicit format of the system partition. PiTA.

The problem seems to be related to rebuilding the device from 'bulk mode' vs the normal method of replacing/unlocking the bootloader. You did unlock the bootloader, correct?

FWIW - I'm penning this from a HDX Thor rocking AEX with SuperSU 2.82 SR5 unlocked using the 'original' method dating back to 2015. Device has seen at least a dozen different custom ROMs. Never experienced this problem.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
I honestly don't know if my bootloader is unlocked. Huge cluster to do it and like earlier... I came from a brick so... Just happy to be flashing ROMs that are working. Would be nice to have root access though.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You will need to unlock the bootloader. The weirdness experienced trying to secure root is representative of future problems that will crop up without warning using custom ROM (Android 5+) with a locked HDX bootloader. It's easy to unlock; simply follow steps #1 and #3 in OP of the unlock thread previously referenced. There is zero risk in trying; failure is non-destructive.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
That's how I bricked it earlier... I'll try again.

---------- Post added at 11:48 PM ---------- Previous post was at 11:24 PM ----------

yeah i cant flash the vulnerable aboot because i dont currently have su. I'm not going back to stock just to start all over again. There has to be a better way to do this.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Well you didn't brick it via unlock attempt as the process is completely benign from a device usability/stability perspective regardless of success/failure. I suspect the 'brick' resulted from other related activity such as flashing aboot.

Err...who said anything about flashing aboot? Reread my previous post - steps #1 and #3 only. Device already has a vulnerable aboot as evidenced by the installation of TWRP. The only challenge you might face is entering fastboot which will prevent the unlock script from completing. In that case head into TWRP, boot to bootloader and manually apply the unlock code generated in step #1.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Are those reports on this thread? (I was too lazy to check, sorry...)

I'm wondering what implicates bulk mode, since my Thor was liberated

using 1-Click (which does bulk mode) and it works just fine with Magisk.

Never skipped a beat...

---------- Post added at 02:04 ---------- Previous post was at 01:56 ----------

You could always try 1-Click (on MacOS or Linux),

although I cannot guarantee that doing so will solve

your problem, since at the moment I'm not even sure

what that problem really is...

---------- Post added at 02:11 ---------- Previous post was at 02:04 ----------

If you can boot any of the Nougat based ROMs,

your bootloader should be unlocked. Last I checked,

[MENTION=5749760]ggow[/MENTION] does NOT fake-sign boot.img, which means

that the ROM couldn't boot, unless the bootloader was

unlocked. TWRP is different, though; so, if you only

flashed, but never successfully booted a new ROM,

then the jury is still out...s just fine even if the bootloader is still locked.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
A couple different threads. Still trying to connect the dots with limited clues but all appear to be "liberated" devices brought back from the brink. Quite possible other factor(s) are in play.

Another coincidence is the use of aboot images from alternate sources since [MENTION=5594063]ONYXis[/MENTION] went dark. I really hesitate to go that route without further evidence as one would think other symptoms would pop-up.

Yet another theory is patched vs unpatched aboot. You may recall [MENTION=5749760]ggow[/MENTION] posted a xx.3.2.3 update to address various display and audio anomalies in earlier builds. That worked great for many months (years!) then suddenly began to brick devices when flashed. At the time no one understood why as the universal 'bulk mode' rescue procedure was not well defined. Non-booting devices were presumed toast with no further forensics possible. Hence the question on what .bin the various aboot images were sourced from.

Keep in mind those bootloaders/kernels never advanced past xx.3.2.6 as the ability to successfully flash a backleveled aboot was as yet unknown. Today we are typically overwriting bootloaders from the FireOS 4.5.x era. Makes you wonder if something gets left behind.

---------- Post added at 02:24 AM ---------- Previous post was at 02:20 AM ----------

Safe to assume 'locked' unless one explicitly unlocks after flashing/reflashing a vulnerable aboot?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
Yeah, well you flash the older version of aboot coming from 4.5.5.2 which inhibits boot, and mine wouldnt boot past a black screen, so I literally sat here executing fastboot commands all night by trial and error without ADB until you came to the rescue this morning...

I've tried steps one and three and I consistently get the "NOT CORRECT" message. There is no issue entering fastboot mode, that's actually the easy part. I am also using the batch commands from the post in that thread, I'm not sure how I could do it manually?

I mean I've booted every nougat ROM currently available throughout the dev threads without issues, I just have no root and when I flash magisk or superSU Thor does not boot past the gray KF watermark.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Yousucks2:
Just for curiosity Which version of TWRP you have installed in your Kindle? if you can install nougat ROMs you have a TWRP

Say that becasue, i had issues installing GAPPS ZIP's on version 3.1.10 of TWRP , always returned error# 7, with all version of gapps (normal/pico/nano ,etc) on Nougat builds, i tried plenty of modded gapps, some shows "installation completed" but play store never appears after reboot.

Before open a new thread i downgraded to TWRP version 3.0.0.0, using Flashify and the issues gone, im not saying this resolve your problem ,i just want to share it as a possibility.

I remeber FireNexus 6 has SuperSU integrated if you want to try

Hope you get a solution.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
I'm on the latest twrp 3.1.1.1. Finally, after like 100 tries, I got the code is correct message and an unlocked bootloader. Just flashed magisk and Thor proceeded to boot all the way - I'm assuming I'm up 100% now.

Also, I've never had an issue with gapps, I started out flashing mini, but it took too long so I swtiched to nano. they work perfectly every time I install a ROM, no matter which one it is - I am only flashing nougat based roms anyways, since thats what my S8 is running. Just easier to have both things running the same android version when possible. It only took me two days to get the HDX finally working 100% and out of the terrible FireOS. Not bad for a free tablet!!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Yousucks2:
Glad to see you got working magisk

Yeah i had that issue too, in my case probably the cause was windows 10 incomptibility issue, i got "unlock code isnt correct" on my laptop many times before got frustated, when i tried again on my old vista desktop all the procedure runs witout errors,dont know why.

I like FireOS, but hey, its better you have the chance to choice between systems,AOSP runs very well on this tablet.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
Yeah my laptop is windows 10 so who knows what the issue was, glad it finally worked out and honestly wouldn't be able to do it without you guys helping. I know enough to be dangerous and actually thought I was going to have to throw out my hdx haha - was up till 5a last night panicking in fastboot trying everything. Fire os isn't terrible I guess, but definitely caters to readers. The hdx tabs have too high of specs to be dedicated readers IMO...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Glad everything worked out in the end. I could respond point-by-point to the various issues and speculations encountered during your (and others) journey as there are telling clues to what really happened. But I suspect no one is interested at this point. Enjoy your fully liberated HDX!

[MENTION=5828306]draxie[/MENTION] - note root cause it this case was the bootloader lock state. I have questioned this before and often receive assurances unlocking was successful. Probably time to start asking for validation (idme print or similar).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
When I was trying unlock I was running the get code.bat then the unlock.bat each time. I even figured out the formula for the generated code and just ran the unlock command with the code manually a few times. Oh well, it finally worked in the end...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
REALLY?

OK. That's good to know. In that case, 'get_code.bat' is

the more likely culprit, I'd say.

Now, that sounds a bit suspect. The unlock code is a 256-byte

binary string. Granted, the first 160+ bytes are normally zeros,

but you'd still need that "formula" (whatever you mean by that;

BTW, there *is*, of course, a formula, but it's not entirely trivial

to operate on those large numbers) to work on 80+-*byte* binary

strings. Personally, I'm having trouble remembering the 5-byte

(10 hex characters) EMMCid for my device that forms the input

to the fake signature calculation, but perhaps you have that rare

talent of being able to toss around huge numbers in your head...

(BTW, I do realize you never said the formula was in your head,

but given the amount of detail provided, that _could_ still be

a scenario compatible with your description... ;^))

Right. That's all that matters to you (I'm glad it worked,

don't get me wrong), but to be able to help others, it's

useful to know what didn't work and WHY. (-;
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
Haha, so what I did was take the last two digits from the first number that only really had two digits at the end preceded by a bunch of zeros, ie 0x0000015, and added them to the beginning of the next set of alpha-numeric numbers I got after running get code.bat. I then ran fastboot -i 0x1949 flash unlock 0x15413dgpe4134.unlock - I got code not correct every time I did it but I was desperate... Lol
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Huh?!? (-;

Aha... interesting... The 'get_code.bat' script should run a few adb commands to generate a 256-byte file named 'unlock.code' in the directory you run it from, which 'unlock.bat' in turn takes and flashes to the Kindle in fastboot mode...

Something in that chain was apparently broken, if you had to resort to inventing filenames (that likely didn't even exist) for your unlock code...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
Hahahahaha A for effort?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Appreciate the confirmation details; nothing surprising (nor interesting) there. :)

He did pull the ZIP and associated new 'bricks' of course ceased. What I did not know for sure (until now) is whether the aboot images that you posted had that patch 'applied' (loose language). So this path also becomes relatively uninteresting beyond historical curiosity.

What I was driving at was a possible distinction between devices that never saw a build of FireOS newer than xx.3.2.6 vs those that updated to some build of FireOS v4 before flashing the v3 generation vulnerable aboot. Yes, looking for highly unlikely connections but the lack of hard evidence tends to extend one's curiosity. In hindsight (and with the benefit of information posted in the past 12 hours) seems a little silly. I have re-stowed my tin-foil hat for another day.

This, of course, is the missing clue to several partial successes where Android 5+ ROMs and other flashables went in ok but attempts to secure systemless root failed. I do wonder if system root would work...something SuperSU is still capable of if feed the correct parameters. That said, unlocking the bootloader is clearly the preferred path!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Non-systemless root managers SHOULD work fine

Normal SuperSU _should_ work fine, since it doesn't touch the boot partition

(that is, 'boot.img' _not_ the bootloader, of course). The newer "systemless"

approach seems to work by modifying the boot partition (the flashed version

of boot.img, essentially), which breaks signature validation, resulting in failed

boot... not much fun...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jlbrown1:
[MENTION=5488402]Davey126[/MENTION],

I have been running this since it was released on 11/19. Just last week and this week my device has started rebooting frequently. Any ideas on how to troubleshoot?

I am thinking of trying Slim. I know you like it too.

Thanks!

Jason
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You really can't go wrong with any of the Nougat ROMs for HDX. :)

As for uncommanded reboots suggest reloading AEX or trying a different ROM to rule out a potential hardware problem. Spontaneous reboots can also be triggered by an aging battery that suffers voltage sags under modest to heavy loads.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] cmonty14:
Hi,

is encryption working with this ROM?

I have enabled encryption and rebooted the device.

However the device is not booting, means I don't reach the phase where I enter the decryption password.

Instead the display is showing "kindle" on and off.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jlbrown1:
[MENTION=5488402]Davey126[/MENTION], can the battery be replaced?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Yes with caveats:

- replacements from reputable suppliers are becoming scarce and pricy

- cracking open device w/o cracking screen or causing other damage is difficult due to copious use of unyielding glue during assembly
[Kindle Fire HDX 7" & 8.9" Original Android Develop] sunapeelakers:
[MENTION=5488402]Davey126[/MENTION] - how do you flash ROMs based on older versions of Android?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
General procedure is the same for all custom HDX ROMs (Android 4.4.4-7.1.2) listed in this section. Be sure to read ROM OP for important flashing details and recommended inclusions. Also review recent posts in associated thread for known issues. An unlocked bootloader is a soft prerequisite for flashing most ROMs; required for rooting (systemless).

Highly generalized procedure:

- gather items recommended in ROM OP

- if a GAaps package is suggested/required go with 'full' or smaller (stock is too large; recommend nano)

- if a root solution is needed recommend SuperSU 2.82 SR5 or above (2.76 for 4.4.x based ROMs)

- boot into TWRP

- {recommended} backup existing config and copy folder (not individual files) to host

- if switching between similar android builds (x.x.x) wipe system/cache/dalvik; include data partition if backleveling

- be sure to flash ROM and GAaps in the same TWRP session; don't try to add GAaps later without reflashing ROM

- if ROM doesn't boot return to TWRP, wipe all partitions (internal storage optional) and try again
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Apollo Hartigan:
Will this ROM be updated because of spectre and meltdown?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I have been monitoring the aosp extended nougat branch since the last update that I released. I have not seen an update to nougat branch yet.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] webby2018:
New AospExtended Install issues

Hi, I've just installed 7.1.2 AospExtended ROM onto my HDX 8.9 and have a few strange, and possibly unrelated, issues that I wanted to see if anyone had some insight into before I revert to my previous Fire Nexus ROM build.

Install of AospExtended and Gapps nano (within the same TWRP session) went smoothly and I appeared to have no issues until I found that the home button doesn't work within an app. I have to use the back key repeatedly to get out of an app. In Chrome even this doesn't work as it just goes back to the previous page and I can't get out - I have to shutdown and restart.

Also, despite installing SuperSU via 'adb sideload' from TWRP, it doesn't appear on the desktop.

Finally, when I try to enter Developer Options it says 'Developer options are not available for this user'.

Anyone had any experience with these?

TIA
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ReichMann:
Hi,

I have not faced anythings like that. I installed this Rom on 2 different devices HDX 7 Thor with Gapps Nano. Everything works very smooth.

Maybe you should try to download Rom file and Gapp again.

Good luck!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Clearly a local sw issue. I have not experienced anything like this with AEX nor heard of anything even remotely similar over the lifespan of this device dating back to jellybean based Fire Nexus. Almost sounds like the prerequisite wipes were not done or didn't complete successfully. Or the wrong file(s) were used. Double check the OpenGapps package is correct (use the latest nightly build).