yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] gobernaster:
Davey126- Thank you for the reply. I realize that the instructions are present and am not trying to be lazy / take advantage of other's generosity. I have followed the instructions, but ran into a technical limitation on my end. I was able to install all of the necessary software / tools except for Python to create the unlock file. My only machine at the current time is a Company owned laptop which has restrictions on what software I can install. If you or someone else on the forum could please do me a favor and create the unlock file I would really appreciate it.

-Scott
[Kindle Fire HDX 7" & 8.9" General] HelloMick:
I can not install gmpy2 on my notebook. Try it for many hours..... :crying:

Sorry. Thats the reason why I ask if someone can help me to create the unloch file.

Mick
[Kindle Fire HDX 7" & 8.9" General] DB126:
Fair enough; attached.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Quite an effort on gmpy2 install; unlock file attached.
[Kindle Fire HDX 7" & 8.9" General] gobernaster:
Amazing, thank you so much! Unlock file worked perfectly and I'm now running CM 14.1!!!

-Scott
[Kindle Fire HDX 7" & 8.9" General] fastbag:
bootloader

python.exe cuberHDX.py 0xmmssssssss

i get an syntax error tryed ......

mm 45

sss...309e6562

i think gimp2 dont work
[Kindle Fire HDX 7" & 8.9" General] DB126:
Try using an older build of Python (2.7.xx) and the corresponding version of gmpy2 for your OS.
[Kindle Fire HDX 7" & 8.9" General] fastbag:
worked

i got my unlock ! i did all of that to my hdx7

Code:

adb shell

su

dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot

Now you have working twrp recovery. It already works even without unlocked bootloader. You could boot into it by holding volUP during grey kindle logo. But no need to flash anything until unlock. At this point this is just emergency tool if something goes wrong =)

3. Flash unlock file.

Now, if you reboot, you will go straight into fastboot because of old aboot - newest boot.img can't load with it. If your firmware <13(14).4.1.1 you need run "adb reboot bootloader" to boot into fastboot.

Time to flash your unlock file.

Code:

fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock

But now if i reboot there comes just: Light on no Kindle writing , Adb device is detected in my device Manager !

c:\adb>fastboot devices

D0FBA0A04032018F fastboot

Thats all what can i do now ?

---------- Post added at 06:57 PM ---------- Previous post was at 06:10 PM ----------

I think i flashed the Apollo Files aboot_vuln.mbn and twrp_cubed.img ist it possible to flash them via fastboot when they don´t be on Root of the kindle ?

c:\adb>fastboot getvar product

product: APOLLO

finished. total time: 0.053s

This is the answer from fastboot

I got it all done by my self
[Kindle Fire HDX 7" & 8.9" General] ihayders:
Hi ya,

I've made the unlock file using the serial number. Before I go and mess things up proper in the bit below does 0x1949 represent the manfid?

fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock

Apologies in advance

Ian
[Kindle Fire HDX 7" & 8.9" General] Montisaquadeis:
Pretty sure I have an Apollo 8.9" Since I got it back in 2013 aka first year the 8.9" came out with the SD800 SOC. I am currently on 14.3.2.4 rooted Can I get a Step by step guide on how to get my Bootloder unlocked so I can install something other then Amazons OS on to it?
[Kindle Fire HDX 7" & 8.9" General] draxie:
Since you have root, but the wrong aboot, you'll need to overwrite aboot and recovery as instructed in step #2 in the OP.

Personally, I think that it's easiest to do the unlock as described here.

For maximum safety, I'd recommend that you do the re-flash (i.e. OP#2) not before the unlock, but just before the reboot in that sequence.

You could also try the unlock as is (without re-flashing), since it's harmless, and verify that it does indeed fail. (-;

Then, you got your EMMC-id and unlock.code and can proceed to reflash and perform the unlock.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Just follow the OP instructions. Attempting to unlock the bootloader does not pose any risk to the device. It will either work or not. The risk (albeit minor) comes with flashing core components such as bootloaders, recoveries and custom ROMs.
[Kindle Fire HDX 7" & 8.9" General] Hashcode:
Hi Guys,

Hats off to [MENTION=5594063]ONYXis[/MENTION] [MENTION=5828306]draxie[/MENTION] and [MENTION=5488402]Davey126[/MENTION] who do such a bang up job patrolling these threads.

I picked up a 64GB LTE Thor device on eBay last week and wanted to share my experience going from FireOS 4.5.5.2 to unlocked status running LineageOS (Android 7.1.1):

- Device started with a clean install of FireOS 13.4.5.5.2 and was not registered with Amazon

- Went into Settings -> Device Info (I think) -> Tapped on whatever the equivalent to "Build" was in that list or a sub menu of that list to unlock "Developer Settings"

- Enabled ADB and made sure I could install unsigned APKs

- Downloaded KingRoot Android APK (5.0.1) -- NOTE: this is a personal choice. KingRoot via the Android APK on an unregistered / wiped device is probably an "OK" method for rooting. But not as safe as say TowelRoot which is tried and true but presents a risk involved with downgrading to 3.2.8.

- on my PC I loaded KingRoot with "adb install KingRootV***.apk" (sub the "***" with the full filename -- it's long)

- Now, it took me no less than 10-15 minutes of trying KingRoot over and over again to root the device using this method. I think it rebooted the device about 5-6 times total and eventually worked. So at this step: BE PATIENT.

- I downloaded the aboot_vuln.mbn for Thor from the OP. USERS: PLEASE DOUBLE CHECK YOUR MD5 ON THIS FILE!! -- I know it's somewhat hidden in the 1st page of posts but the MD5 sum is: 66b7df0db97c7c2905d1d61199c816a5. To check yours, run: md5sum aboot_vuln.mbn

- I have my own compiled version of TWRP but normally users would download twrp_cubed.img as well.

- Generated my unlock code with cuber-HDX.py after getting my mmcid/serial information via the adb commands in OP.

- Pushed both the aboot_vuln.mbn file and my TWRP image to /sdcard/ with adb and then ran the commands to dd them to the recovery and aboot partitions (in the OP)

NOTE: dd'ing aboot_vuln.mbn from the *.3.2.3.2 release to the aboot partition is with out a doubt the most risky step in this procedure and there may be some combination of FireOS / device status where this *might* cause an irrecoverable brick. It didn't for me -- but it's been mentioned that this step is under scrutiny.

- From there: adb reboot bootloader

- and then: fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock # with my unlock filename there

- And then "fastboot -i 0x1949 reboot" while holding down Volume Up to enter recovery so that I could flash Android 7.1.1

So to sum up: I did not roll back from 4.5.5.2 to 3.2.8 but instead flashed the vulnerable aboot from 13.3.2.3.2 directly (after rooting) and then unlocked.

Advice to users: PLEASE be sure you have read all of the instructions, know what device you have and are comfortable with the procedure in the OP. This is a 1-way trip and if done incorrectly, your device can be permanently unusable. HOWEVER, the rewards of being unlocked and tailoring the software on your device to suit your personal needs are well worth the efforts :)

- Hash
[Kindle Fire HDX 7" & 8.9" General] Mr McBoatface:
This is near exactly what I done earlier in the week bar unlocking the bootloader which I couldn't do until I fixed my faulty USB connection.

I used kingroot 4.9.7, downloaded the apk and installed it. I actually downloaded all the files I needed including in the rom nexus KK. My HDX had been restored to factory setting using kingroot it rebooted just once and took just over a minute to root.

Personally I've found kingroot to take a lot longer to root while USB cables are attached and in the case of my other fire tablets the Fire 5th gen when there was an SD card inserted. This is just an observation on my part can't say for certain it's definitely true for all.

I followed the adb procedure to push the twrp and aboot files. Rebooted to twrp done an advanced factory wipe, cleared all but the internal SD. I installed NEXUS KK , the latest gapps and supersu. All in all it took me less than 10 minutes to go from untouched up to date amazon stock to custom recovery and custom ROM.
[Kindle Fire HDX 7" & 8.9" General] DB126:
How can I not 'like' this post being mentioned with such distinguished members as [MENTION=5594063]ONYXis[/MENTION] [MENTION=5828306]draxie[/MENTION]! Nor can I take issue with the path you pursued. Rolling back to 3.2.8 is a personal call based on the experience level of the member and rootability of the version of FireOS currently installed. AFAIK FireOS 4.5.5.3-4.5.5.5 are not vulnerable to any version of KingRoot - yet.

One final caution: recommend not flashing 3.2.3 bootloader 'update'. There is no indication that it is needed and several users have reported hard bricks after updating having apparently doing everything correctly (including validating MD5 values). I suspect the issue lies with the highest version of FireOS that was on the device prior to unlocking via this method. Unfortunately, I don't know were the line is given bootloader unlocks for devices running versions of FireOS > 3.2.6 is relatively new.
[Kindle Fire HDX 7" & 8.9" General] Hashcode:
Ah interesting. I can edit my post to mention that flashing the *.3.2.3.2 aboot which is a known to be vulnerable to the cuber exploit may still be a step with some risk involved depending on what FireOS the user is currently on.

I was under the impression that Amazon fixed the cuber vulnerability in aboot versions > *.3.2.3.2. We're still using that exploit in a slightly different manner when attaching the unlock information for aboot. So I figured it was required. Unless I'm totally misunderstanding your post :)

- Hash
[Kindle Fire HDX 7" & 8.9" General] DB126:
I think [MENTION=5594063]ONYXis[/MENTION] needs to weigh in on specifics/assumptions for the aboot linked in this thread. From a user assist perspective some members noted graphical anomalies with various ROMs after unlocking. Standard solution was to flash 3.2.3.2 bootloader "update" which usually addressed the problem. This worked reliably until recently when a few users reported hard bricks after flashing the update. Others get through it just fine. Seems to have started with those that followed the path you did vs rolling back to FireOS v3 before unlocking. But that's speculation with no hard data to back it up. For now I am no longer recommending the 3.3.2.3 update for obvious reasons. Tough to score an unrecoverable brick after everything else worked well.
[Kindle Fire HDX 7" & 8.9" General] Hashcode:
I agree that avoiding unrecoverable bricks should be the top priority on any devs agenda.

However, the downside to the 3.2.8 rollback is that if the device *ever* gets an Amazon update that is earlier than the original version, its hard bricked.

If we can make sure flashing the vulnerable aboot doesn't cause bricks, the advantage to this method is that the device could still accidentally take an Amazon update and the worst that happens is that you're stuck on the latest unrootable FireOS.

Kind of a toss up until we get more information and/or testing.

- Hash
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yep - many a device has met it's demise taking an OTA update to v4.x while on the rollback variant of 3.2.8. Standard guidance involves maintaining strick network isolation until rooted, unlocked and FireOS v3 replaced with a custom ROM. Can also block OTA updates once rooted. Most members seem to handle the rollback well when guided through the procedure. It's the self-starters that don't read through the cautions that end up getting burned.
[Kindle Fire HDX 7" & 8.9" General] billybob24:
k im on 4.5..5.2 im trying to unlock the bootloader so i can get a rom on this thing. but having no luck. tried python keep geting invalid sayntax. is there any easier way to do this i got my serial number and everything need but cant get past step 1.2 to get unlock code
[Kindle Fire HDX 7" & 8.9" General] DB126:
Assuming you are rooted which is a prerequisite. Two thoughts for creating an unlock file:

- use an older version of Python (2.7) and a corresponding gmpy2 package

- can also try a standalone C++ unlocker tool documented here: https://xdaforums.com/kindle-fire-hdx/development/pure-c-implementation-cuber-using-t3241011

Failing that post your codes and wait for someone to generate an unlock file on your behalf.
[Kindle Fire HDX 7" & 8.9" General] Rebel4206:
I have a kindle fire hdx 7" on 4.5.5.2 would unlocking the bootloader let me remove the stock rom and replace it with a custom rom and place the recovery rom on a server/pc to maximize the local storage on my kindle fire hdx since its the 16GB model (around 11 GB free user space)?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yep - solid 'yes' to all questions. Only caveat is transfers of large backup files must (should) be done via USB tether. No OTG support on HDX devices.
[Kindle Fire HDX 7" & 8.9" General] chin_bone:
Requesting help. Just got another hdx 7 thor after seeing bootloader was unlockable. I am running 4.5.5.2, already rooted with kingroot. got my manid and serial and using python 2.7+gmpy2 to create unlock code. However, keep failing to unlock. I am on a usb3 port so I will move to laptop and use usb2 port but to make sure I am not missing something in the unlock file can someone create one for me? Appreciate any help. I know you guys do great work and it is much appreciated by most here.

manid 45

serial f0c049ff
[Kindle Fire HDX 7" & 8.9" General] billybob24:
OK ONE LAST QUESTION HOW TO DO I SEE WHAT BOOTLOADER I GOT AND IF IT IS UNLOCKABLE CANT FIND THAT INFO ANYWHERE? sorry for the caps lol
[Kindle Fire HDX 7" & 8.9" General] DB126:
All bootloader builds/versions for 3rd gen HDX devices are unlockable. Root is the only prerequisite.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Avoid KingRoot if you don't want to wipe everything

Special thanks for your note on KingRoot! (-;

I agree that using KingRoot might give a (somewhat) faster path

(depending on how many attempts/restarts it needs before it gets root),

and it's probably OK if you're going to wipe /data as part of the process,

but I'd generally advise against it for two main reasons:

BrickRisk

KingRoot needs network access, and I've gotten an update pushed

to a device (granted, that was an HD7 not an HDX) while KingRoot

was doing its magic. Luckily, I noticed this and deleted the update in time,

others didn't fare as well...

EvilWare

A quick search on XDA will turn up volumes of warnings about KingRoot.

AND, once it gets installed, I haven't managed to find any other way

than wiping everything, inlcuding /data, to get rid of it. I'm convinced

that more intelligent/nuanced methods must exist. I just haven't had

the time (or interest) to research those. And, KingRoot tries hard to

keep its foothold.
[Kindle Fire HDX 7" & 8.9" General] billybob24:
when i try the c++ on e hers what i get

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\server>adb push cuber /data/local/tmp

cannot stat 'cuber': No such file or directory

C:\Users\server>cd

C:\Users\server

C:\Users\server>c;

'c' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\server>cd\

C:\>unzip cuber.zip

'unzip' is not recognized as an internal or external command,

operable program or batch file.

C:\>adb push cuber /data/local/tmp/

2601 KB/s (506072 bytes in 0.190s)

C:\>adb shell chmod 0755 /data/local/tmp/cuber

C:\>adb shell 'id=$(cat /sys/class/block/mmcblk0/device/{manfid,serial}); echo "

$id"; echo 0x${id:6:2}${id:11:8} | /data/local/tmp/cuber > /sdcard/unlock.code'

The system cannot find the path specified.

C:\>adb pull /sdcard/unlock.code

remote object '/sdcard/unlock.code' does not exist

C:\>adb shell 'id=$(cat /sys/class/block/mmcblk0/device/{manfid,serial}); echo "

$id"; echo 0x${id:6:2}${id:11:8} | /data/local/tmp/cuber > /sdcard/unlock.code'

The system cannot find the path specified.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Have you seen these instructions for using an ARM version of 'cuber' that you can run on your very own Kindle?
[Kindle Fire HDX 7" & 8.9" General] billybob24:
here is my my tablet info anyway you could help me with getting the code then i can flash it. i been trying this for weeks

C:\>adb shell

shell@thor:/ $ cat /sys/block/mmcblk0/device/manfid

0x000011

shell@thor:/ $ cat /sys/block/mmcblk0/device/serial

0x4650b1f8

shell@thor:/ $
[Kindle Fire HDX 7" & 8.9" General] draxie:
I hope you pardon my pedantry, but while it appears that the bootloader

on all 3rd generation HDX _devices_ can be re-flashed to a vulnerable

version that accepts fake signatures, bootloaders above 3.2.3.2 cannot be

unlocked (using the fake signature method, in any case), they need to be

replaced. Of course, this makes no practical difference if what your after

is not the information, but an actual unlock... (-; ;-P
[Kindle Fire HDX 7" & 8.9" General] chin_bone:
I will give it a shot when I get home, thanks draxie!
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yes - I am fully aware and intentionally opt for a more streamlined response given the positioning of this thread ('General' section) and the communities seeking assistance. The same inquiry posted in a 'true' development thread would yield a more granular response. :)
[Kindle Fire HDX 7" & 8.9" General] billybob24:
Here is the error i get with python

Python 2.7.12 (v2.7.12:d33e0cf91556

AMD64)] on win32

Type "help", "copyright", "credits"

>>> python.exe cuberHDX.py 0X114650

File "<stdin>", line 1

python.exe cuberHDX.py 0X114650

^

SyntaxError: invalid syntax

>>> python.exe cuberHDX.py

File "<stdin>", line 1

python.exe cuberHDX.py
[Kindle Fire HDX 7" & 8.9" General] DB126:
This error is typically produced with higher (or invalid) versions of Python. Try version 2.7 with the corresponding build of gmpy2 2.0.8
[Kindle Fire HDX 7" & 8.9" General] draxie:
LOL... (sorry, I couldn't resist)

I updated the instructions (spelled out that you need to download and extract 'cuber.zip')

Actually, I renamed the ZIP file to 'unlock.zip' and put the code into two batch files you should be able to click and run.

I don't think I can make it any simpler than that....
[Kindle Fire HDX 7" & 8.9" General] billybob24:
thats what im running. im stuck

---------- Post added at 11:19 AM ---------- Previous post was at 11:14 AM ----------

ahahha its ok im slacaking been awhile since i done any of this for sure. bu where are those files for the unlock zip. a batch file sounds amazing and needed badly by me. thanks for getting back so fast and keeping this tablet alive. i just got it from my mom and want to use it for my kids but this amazon rom sucks
[Kindle Fire HDX 7" & 8.9" General] draxie:
Have you already forgotten where you cut & pasted that code from? (^;
[Kindle Fire HDX 7" & 8.9" General] billybob24:
lol on it now

---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------

ok now the fire says ready. then has fastboot up top but cmd says waitng for device. i unplugged ebafter some time said offline. then went back to ready. but cmd. says waiting. is there new drivers i should have may
[Kindle Fire HDX 7" & 8.9" General] draxie:
Possibly... that seems to be a common issue. Or, just try a different port, or a different machine/OS, if you happen to have more than one option.

Have you successfully run any 'fastboot' commands before? (E.g. 'fastboot -i 0x1949 devices' or some such?)
[Kindle Fire HDX 7" & 8.9" General] billybob24:
ok switched computers back to my mac and this is what happened with the unlock .zip

[100%] /data/local/tmp/cuber

0x000011

0x4650b1f8

[100%] /sdcard/unlock.code

Thes-MacBook-Pro:unlock Smith$ /Users/Smith/Desktop/unlock/unlock.sh

< waiting for any device >

target reported max download size of 536870912 bytes

sending 'unlock' (0 KB)...

OKAY [ 0.084s]

writing 'unlock'...

FAILED (remote: Unlock code is NOT correct)

finished. total time: 0.142s

Thes-MacBook-Pro:unlock Smith$
[Kindle Fire HDX 7" & 8.9" General] draxie:
Unless you have a vulnerable bootloader from the get-go (i.e. .3.2.3.2),

or you had already flashed such a bootloader as described in step#2

in the OP, that looks just about right.
[Kindle Fire HDX 7" & 8.9" General] billybob24:
ok is there anyway to test it out then to see? this is teh first tiem i got this far to even coming close to flash soemthing to it. i used kingroot to root it
[Kindle Fire HDX 7" & 8.9" General] chin_bone:
STEP 2 STEP 2 STEP 2, DID I MENTION STEP 2. Sorry for the caps billybob, i did the same thing, kept getting failed as i did not do STEP 2. Once i did it, bootloader unlocked first shot, rebooted into TWRP recovery, good to go!!!

Draxie, thank you for the guidance and the work you and the others have put into figuring this out. These HDXs are still the best once you get the crappy amazon software off of them.:D
[Kindle Fire HDX 7" & 8.9" General] billybob24:
lol caps suck ok not to sound crazybut what was step two i didnt see it like what part didnt you do exactly

thanks
[Kindle Fire HDX 7" & 8.9" General] DB126:
Dude - go back and read the first post in this thread. Unlocking steps are clearly defined. Step #2 is mandatory.
[Kindle Fire HDX 7" & 8.9" General] ttlog:
Thank you! You helped breathe new life to this "aging" hardware
[Kindle Fire HDX 7" & 8.9" General] zacharias.maladroit:
To be fair,

the steps were not 100% clear (e.g. the cuber failing with different python version)

I'll gotta post a few clarifications later if there still anything that comes up

(will have to re-read it again and see what I exactly did)

when cuberHDX.py is complaining about wrong argument (or similar)

try running it after

export EPYTHON=python2.7

from console

seems it's NOT compatible with python 3.x
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yep - room for clarification/expansion on execution detail; more than happy to assist on those and other points. Omitting steps while shotgunning questions will draw a different response. Post history matters.
[Kindle Fire HDX 7" & 8.9" General] slvr32:
I didn't have any trouble rolling back an unmodified HDX 7 (w/LTE connectivity) tablet from 4.5.5.2 to 3.2.8, manually updating to 4.5.2, rooting 4.5.2 with the cve20147911.apk mentioned elsewhere, unlocking the bootloader, etc... and I'm currently running cm-13 w/TWRP, rooted, w/Xposed, etc...

So, I realized after the fact that GSM/LTE on the HDX isn't functional w/CM-13, and having a wifi-only HDX is a bit disappointing, albeit obviously my fault for not digging a bit further into CM-13 caveats, specific hardware support, etc..

In any case, I've tried flashing the 4.5.5.2 package in the first post of this thread, as well as a different thor TWRP zip ( https://xdaforums.com/showpost.php?p=62690126&postcount=1 ) mentioned in an earlier post in this thread, but both flash attempts result in symlink errors... attached.

Any suggestions?
[Kindle Fire HDX 7" & 8.9" General] Mr McBoatface:
Can't answer as to why the repacked stock ROM failed but you could try flashing the lastest Nexus KitKat ROM - https://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931. I don't have LTE but I believe it works on this ROM.

Edit :- flash with the latest gapps nano for KitKat , it helps to improve battery life. Screen brightness is very high by default . It can be reduced, still look great and increase battery life further