[Kindle Fire HDX 7" & 8.9" General] zekzekzek:
sigh.

I have a Kindle Fire HDX Thor. I went through post 1006 and thought I followed everything to the T. Looks like I messed up with the unlock code being 0 KB just like what happened to user @exokinetic. Unfortunately, I did not execute "get_code.bat" from CMD but rather directly from windows explorer. I also did not notice that "unlock.code" is 0 KB.

So here is where we are - softbricked. No unique hashes and stuck on fastboot.

I have noticed that I can see the kindle when it is turned on. It shows up as Android ADB Interface.

I can open up CMD and run unlock.bat and I see on my kindle fastboot screen that it receives the unlock code and states its incorrect. So I can somewhat communicate with the Kindle.

Looking at unlock.bat I see that this command [fastboot -i 0x1949 flash unlock unlock.code] is working in sending data to the kindle and the kindle is responding. Albeit with nothing useful from what I can tell but responding nevertheless.

Wondering if I can use the below command with some variation to get a different type of response and get out of softbrick hell. I'm very curious now.

fastboot -i 0x1949

UPDATE 1:

While thinking about the above command, I was wondering why I can't run get_code.bat and then continued to read @exokinetic in his post #1208 and figured it was worth a shot. I followed these steps:

I also specifically got TWRP 3.1.1-1.

And success at getting TWRP loaded!! There is hope after all!

UPDATE 2:

So now I have TWRP and it loads just fine with Power Button and Volume Up. I thought the next step would be to try and get a ROM that does not need an unlocked bootloader but have had no luck finding the Nexus ROM.

I did notice on a German forum (that google translated to english for me) that there were commands for people to get manfid and serial (which is the goal to be able to unlock!) and I tried them in a command prompt with ADB. No luck. (maybe I could have tried with fastboot)

However!

TWRP has a terminal option. Like on the kindle itself. So I manually typed the same commands below into TWRP terminal and voila!! It worked! Who knew. Not this guy.

cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial

So now I have my manfid and serial! Almost there! Now I just need to feed it into get_code.bat or unlock.bat so I can have a proper unlock.code file.

I did try to run get_code,bat using fastboot (and ensuring cuber was in the adb and folder) but I don't know what command to use here and the ones I tried haven't worked. Just ruling this out.

UPDATE 3: Unlock success!

Whoever said being impatient is a bad thing.

I knew I needed to manually pass the manfid and serial to be able to get a generated unlock.code file. So I was digging around in XDA and came across this thread by @yujikaido79 which was a great guiding post:

https://xdaforums.com/t/tools-creat...ck-update-bin-for-aboot.3050689/post-59383789

I did both these steps (although GMPY2 might not be needed):

I then followed the thread to get cuberHDX.py (which I realized I didn't need) over here by the great @draxie :

https://xdaforums.com/t/thor-apollo-unlocking-bootloader-with-any-firmware.3463982/post-70775571

Since I had my manfid and serial, these instructions seemed like exactly what I was searching for. Once I was done with the above instructions, I had a unlock.img file.

Since I was going to be using fastboot, I copied the unlock.img file into my adb folder and simply ran this command and it worked like a charm.

Success!

Overarching Edit: I'm going to keep editing my post as I find and have useful information in my journey so everything is in one place for my own reference.