[Kindle Fire HDX 7" & 8.9" General] exokinetic:
Okay friends!

keyword: cuber

Now that I have a nice fresh instance of Lineage-16 running on my HDX, thanks to the brilliant and helpful minds floating around here...

A huge thank you to Draxie for holding my hand through this, and a big thank you to everyone who has worked on this development.

I thought I would share how I managed to make it through!

So, to begin; the orriginal instructions that most people will find referenced for "unlocking the bootloader" on your Kindle Fire HDX 8.9 are -almost- perfect;

Step 1.

This line:

1. Install the adb-setup-1.4.3 into a folder (for example: C:/adb), extract dd-0.5.zip + unlock.zip + aboot-xxx.zip, put dd.exe + get_code.bat + unlock.bat + twrp image (for your device) + aboot_vuln.mbn (for your device) into that folder.

Is missing one file (cuber) that needs to be placed "into that folder" (the folder you install adb into, from the example C:\adb )

The line SHOULD READ:

1. Install the adb-setup-1.4.3 into a folder (for example: C:/adb), extract dd-0.5.zip + unlock.zip + aboot-xxx.zip, put dd.exe + get_code.bat + unlock.bat + cuber + twrp image (for your device) + aboot_vuln.mbn (for your device) into that folder.

(can a Moderator please edit post #1,006 to reflect the above change? as in, ADD "+ cuber" -so no one else has to get stuck here)

Cuber -must- be in the adb folder you use for this set of instructions, or you will encounter an.... ERROR!

So, lets say you fell into the n0-cuber trap...

How do you get out of your now softbrick state?

Well, you had BETTER HOPE you still have your console open where you attempted to complete the instructions.

(I dont know if a log-file of command prompt history gets saved anywhere in Windows, if it does, you are in luck, and you MUST find this in order to follow my particular set of bread crumbs)

The information you are going to need (hash text) actually came back as a return in the command prompt window you were working in when you attempted step 3.

Specifically:

Step 3.

3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.

When you do that WITHOUT cuber in your adb folder, you will get a return that look SIMILAR to this:

C:\adb>get_code

cannot stat 'cuber': No such file or directory

Unable to open /data/local/tmp/cuber: No such file or directory

0x000045 0x251b3b67

/system/bin/sh: /data/local/tmp/cuber: not found

rm failed for /data/local/tmp/cuber, No such file or directory

Press any key to continue . . .

(coloring/ bolding added for clarity, your console will display all this text as the same color/formating)

That bold/green text is your key out of softboot purgatory, this is why you MUST have the console you orriginally attempted the instructions in still open, or have a backup/ log-file history saved somewhere

(I have no idea if windows does this automatically -I would assume not...)

You WILL generate a file called "unlock.code" -EXCEPT, it will have a size of 0kb (exceedingly useless)

-your unlock.code -should- have a filesize of: 256 Bytes

Unsuprisingly, when you get to the last step:

Step 8.

8. Run the "unlock.bat" in the folder and you should get a green line: "unlock code is correct". Congrats your Kindle now has an unlocked bootloader.

You will NOT receive "unlock code is correct" (you will not pass go, and you will not collect $200)

-sad face

What you WILL receive will look SIMILAR to this:

C:\adb>unlock

error: device '(null)' not found

target reported max download size of 1073741824 bytes

sending 'unlock' (0 KB)...

FAILED ()

finished. total time: 0.003s

Press any key to continue . . .

And you will be a sad panda.

So, how did I make out of this epic fail?

Enter @draxie

I let draxie know I needed a little help, and after reading my orriginal post, they spotted the necessesary information to generate a GOOD unlock.code file:

This is the response I got from @draxie:

I saw the relevant info printed in one of your recent

very detailed forum posts: 0x000045 0x251b3b67.

That's really _all_ you need and a version of `cuber` that runs on _some_ HW

you have access to. Both C and Python implementations have been posted.

BUT, the attachment should save you the trouble of searching and compiling...

So, Draxie was a champ, and compiled the unlock.code file FOR ME :D -thank you Draxie!

But, if you have been following along;

You need:

-The two hash's YOU got from the first time you attempted get_code.bat

(I believe these will absolutely be unique to your individual device, no one elses unlock.code will work for your device -someone please correct me if I am wrong here)

-Any version of cuber and hardware (like, a laptop) to run it on in order to compile the unlock.code

-The understanding of how to tell cuber to use YOUR hash text to compile a new unlock.code file

(if anyone that knows how to do this wants to provide exact instructions for the above, it would probably help someone)

Once you generate the new /GOOD unlock.code using cuber and your hash text (and replace the /BAD one in your /adb folder), boot the device back into fastboot and fire off the unlock.bat again.

-GOOD LUCK!-

--------------------------------------------------------------------------------------------------------------------------------------

Alternatly: (I have no idea how to do this from the current fastboot bootloop state you will be stuck in) you need to get a stock factory Kindle Fire HDX image (actually, -any- ROM you can get flashed and boot in to will work) flashed back onto your device so you can boot into the OS.

If you can get it to boot back into -ANY- OS (I read that some custom ROM's wont require an unlocked bootloader in order to flash onto the Fire HDX, for example) then, while the device is booted into the OS, you can run get_code.bat again (with cuber in your adb folder this time!) in order to generate a good unlock.code.

--------------------------------------------------------------------------------------------------------------------------------------

Once you have you unlocked bootloader, (gasp!)...

I followed the instruction found here -EXACTLY- in order to install a rather stable version of LineageOS-16 onto my Fire HDX.

Call me one happy camper.

In case I haven't done it enough in this post... -THANK YOU DRAXIE!

/Exo