[Kindle Fire HDX 7" & 8.9" General] exokinetic:
Hello Friends!

Some specs:

Kindle Fire HDX 8.9 (3rd Generation)

Device: Apollo

Model: KFAPWI

Current OS: Fire OS 4.5.5.3

So, I also followed the instructions found on page #51 of this thread: https://xdaforums.com/t/thor-apollo-unlocking-bootloader-with-any-firmware.3463982/post-75284993

I followed them EXACTLY...

Which means I had the same error as TheZenGuy above, but I ignored the cuber fails, and moved through the rest of the steps.

>.<

This is what I saw:

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 . . .

This definitely seemed "off", but the instructions said that step should generate a file:

"unlock.code"

...and it would be in the folder you had just created.

And that file WAS generated, so I assumed all was good, and moved on (**** me...)

I have attached the unlock.code that was generated by the above get_code.bat

I have now opened this unlock.code with notepad++ and it is blank, no text.

I am pretty sure a blank entry is NOT going to unlock the bootloader...

spoiler alert: it doesn't

So I continue;

c:\adb>adb reboot bootloader

c:\adb>fastboot -i 0x1949 erase aboot

erasing 'aboot'...

OKAY [ 0.052s]

finished. total time: 0.054s

...GULP...

c:\adb>fastboot -i 0x1949 reboot

rebooting...

finished. total time: 0.022s

Well, that looks right...

c:\adb>dd of=\\?\Device\Harddisk1\Partition6 if=emmc_appsboot-14.3.2.3.2_user_323001720.mbn

rawwrite dd for windows version 0.5.

Written by John Newbigin <jn@it.swin.edu.au>

This program is covered by the GPL. See copying.txt for details

Error reading file: 87 The parameter is incorrect

677+1 records in

677+1 records out

c:\adb>dd of=\\?\Device\Harddisk1\Partition18 if=apollo-twrp-3.5.0_9-1.img

rawwrite dd for windows version 0.5.

Written by John Newbigin <jn@it.swin.edu.au>

This program is covered by the GPL. See copying.txt for details

19128+0 records in

19128+0 records out

And that also appears to go as planned, I got the predicted Error reading file: 87 The parameter is incorrect, smooth sailing...?

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 . . .

Fuuuuuuuuuuuuuuuuu

/fail

[fastboot] - bootloop - softbricked

Power Button + Volume Up will NOT boot in to TWRP (unsuprising given the bootloader is still locked)

For reference, this is what I see on the Kindles screen:

getvar:partition-type:unlock...Ok.

getvar:max-download-size...[[ 0x40000000 ]].

Ready.

Firstly;

error: device '(null)' not found

???

This is what I see in device manager;

Secondly;

I noticed that there was a file in the attached archives that I was NOT instructed to move to the working adb folder that had a name I had seen when doing the cmd line operations:

CUBER

So, I searched this thread for 'cuber' and my suspicions were confirmed, cuber was SUPPOSED to be copied into the working adb folder (for future reference, are any of the OTHER files in the attached archives ALSO supposed to be in the working adb folder? like get_code.sh and unlock.sh?)

-it would just seem like common sense that ALL the files on those attached archives should have been placed into the working adb folder, but you know, the intructions were pretty explicit about what files should be copied into the folder

"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."

Install the adb-setup-1.4.3 into a folder (for example: C:/adb)

Okay, folder C:\adb\ created and it contains:

adb.exe

AdbWinApi.dll

AdbWinUsbApi.dll

fastboot.exe

extract dd-0.5.zip + unlock.zip + aboot-xxx.zip

Okay, extracted to folders with the same name, waiting for further instructions (it does not say WHERE to extract them TO)

put dd.exe + get_code.bat + unlock.bat + twrp image (for your device) + aboot_vuln.mbn (for your device) into that folder.

Okay, 5 explicitly referenced files are placed into THAT folder. (it seems impled that ONLY THOSE files should be copied into THAT folder)

In my case the folder now contains:

adb.exe

AdbWinApi.dll

AdbWinUsbApi.dll

fastboot.exe

dd.exe

get_code.bat

unlock.bat

apollo-twrp-3.5.0_9-1.img

emmc_appsboot-14.3.2.3.2_user_323001720.mbn

As a last attempt to save my ass, after reading the quoted post about cuber, I moved cuber into my adb folder and tried to fire off another get_code.bat:

c:\adb>get_code

error: device '(null)' not found

error: device '(null)' not found

error: device '(null)' not found

error: device '(null)' not found

error: device '(null)' not found

Press any key to continue . . .

/EPIC FAIL

^^^Kindle is booted into fastboot bootloader, device manager correctly seeing the fire device and with the right driver assigned as per the screenshot above

additionally, the command:

fastboot -i 0x1949 reboot

works perfectly fine and re-boots the device, suggesting the device is absolutely not '(null)'

So, currently soft bricked, and stuck in a fastboot bootloop.

Theoretical ideas:

Is it ridiculous to think I could attempt to use someone elses unlock.code file? (it seems to me this was going to be some kind of a uniquely generated hash, but I certainly dont know)

If I could get out of this bootloop and load back into FireOS it would seem like I could fire off another get_code.bat (with CUBER in the adb folder!) and get this baby flashing like TheZenGuy thankfully managed...

So, from my current position, do I try re-installing the "vulnerable" aboot from the instructions attachments and see if I can get it to boot into FireOS so I can start over again? (seem unlikely given theOS version mis-match)

Do I try re-installing some other aboot file that is relative to my apollo hardware and current 4.5.5.3 Fire OS?

^*scratching cheek* anyone got any links?^

Does anyone have any ideas for me to get back into FireOS so I can start over?

And as an asside;

I messaged Draxie earlier today for a link to their "1 Click Bootload Unlock" VM Script; and it is suggested over there that it has worked on fire devices that were in a soft brick state, so perhaps, even if I can not make any progress from here, all is not lost?

Thank you for reading this wall of a post, any help would be greatly appreciated!

/Exo