yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] draxie:
Check what device you have

If in doubt, run this command:

fastboot -i 0x1949 getvar product

(You can probably omit the '-i 0x1949' part...)

---------- Post added at 21:29 ---------- Previous post was at 21:24 ----------

Did your friend share any details with you? (-;

Oh, just in case: fastboot can be _very_ finicky with drivers.

If you can, try a different USB cable, a different USB port, or

a different host (possibly with a different OS version), or all

of the above.... then please do!
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
I'm using a fastboot cable to connect to the hdx - will try a different port and cable to see. I only have windows pc's, but will try my other pc and report back.
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
Tried other pc/port/cable with no success - same error. The kindle was passed to my friend in this state and we're trying to fix it. Are there any tools to force erase partitions? Thanks for all the help and advice so far. Neil
[Kindle Fire HDX 7" & 8.9" General] draxie:
Options...

I'm not aware of any such tools, except -perhaps- a flash programmer,

but those are not public, and the one that was leaked doesn't work on

devices that had firmware past 3.x ... (If you indeed have a fastboot cable,

your HDX should boot into download mode if that cable is tethered to

your PC and show up as Qualcomm HSUSB or some such. In that case,

you could try the methods outlined in the unbricking thread, but I'd not

hold my breath...)

Since fastboot talks to the bootloader more or less directly, it's not easy

to get more low-level than that. On the other hand, you should explore

all you can in fastboot (although that's pretty limited) and identify what

you got there and in what state as accurately as possible. Here's a list of

commands I'd like you to try, and if you don't mind, share their output.

fastboot getvar kernel
fastboot getvar version
fastboot getvar product
fastboot getvar emmc_mid
fastboot getvar emmc_size
fastboot oem device-info
fastboot oem idme \?
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
Thanks again, and output attached. IDME query 'not allowed for locked hardware'
[Kindle Fire HDX 7" & 8.9" General] draxie:
4.x series locked bootloader

Right. So, as you said, it's a THOR with a locked bootloader,

and based on the extended response to the oem device-info

command, the bootloader is from the 4.x series....

I haven't looked much into that newer series before, but it looks

like those have a few extra oem commands and related variables

that probably don't matter EXCEPT perhaps one, and I saved that

for last... (-;

fastboot getvar charger-screen-enabled
fastboot getvar display-panel

fastboot oem enable-charger-screen
fastboot oem disable-charger-screen
fastboot oem select-display-panel

fastboot oem unlock

I truly wonder what that 'oem unlock' does.

On the other hand, that won't matter too much

if we cannot erase aboot or boot into something

more intelligent than fastboot.

BTW, am I right in assuming that "stuck in fastboot"

means that the device won't boot into either system

or recovery? What are the symptoms there? Can you

get an adb connection in any state?

UPDATE: Can you also try 'format aboot' instead of 'erase aboot'?

The former doesn't work on my device with the old vulnerable BL,

but -who knows- perhaps it does on the newer series. Apparently,

erase aboot did NOT work... which I find _really_ weird, since it did

work on my device and when I got that it had 4.x series firmware...
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
I tried :

fastboot format aboot

Formatting is not supported for file system with type ' '.

It keeps rebooting into fastboot, regardless of me using fastboot continue, fastboot reboot-bootloader.

Are there any other commands you can recommend? Adb does not recognise any connected devices.

Neil

---------- Post added at 09:07 PM ---------- Previous post was at 08:49 PM ----------

And when I try to erase.....

C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot erase system

******** Did you mean to fastboot format this ext4 partition?

erasing 'system'...

FAILED (remote: failed to erase partition)

finished. total time: 0.112s

C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot erase data

erasing 'data'...

FAILED (remote: Partition table doesn't exist

)

finished. total time: 0.063s

C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot erase cache

******** Did you mean to fastboot format this ext4 partition?

erasing 'cache'...

FAILED (remote: failed to erase partition)

finished. total time: 0.054s

---------- Post added at 09:25 PM ---------- Previous post was at 09:07 PM ----------

C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot getvar partition-type:aboot

partition-type:aboot:

finished. total time: 0.061s
[Kindle Fire HDX 7" & 8.9" General] draxie:
eMMC read-only?

That's the expected behavior, unfortunately.

I wonder why erase aboot doesn't work.

Any chance of physical "intrustion" that may

have induced some HW failure mode?

That latter *should* reboot to fastboot, but

continue would normally get you into system,

which appears broken in some way on that Kindle.

Have you tried powering off completely (hold Power

button for 10+ seconds, until the screen goes black),

and booting with one of the "magic" key combinations:

Power + Volume Up for recovery

Power + Volume Down for "safe mode" (on locked HW)

Just in case you don't know, although I assume that you

do, the best way to apply those combos is to first press

and keep holding the Volume button of your choice,

and _then_ pressing and holding Power *as well* as

long as the grey Kindle Fire logo appears; and, then

release both buttons...

I'm curious what your HDX says if you enter 'fastboot oem unlock'.

I don't expect it to actually unlock, but it might display the eMMC-ID

(or some other challenge). I've never tried that command...

Wow! You seem pretty desperate, erasing partitions left and right.... (-;

BTW, *normally* all -except one- of the above erase commands should

succeed (despite the format questions); the exception being 'data', since

the partition is actually called "userdata" (that's also why the response you

get there is different).

Again, I'm wondering if *something* (and, I have no idea what, but I'm

suspecting a failed reassembly) could've gotten this HDX's eMMC into

read-only mode....
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
Let me try the magic keys - in the meantime:

C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock

...

OKAY [ 0.056s]

finished. total time: 0.057s

What about if I try to format aboot? I don't know the correct syntax - format :ext4 aboot?

---------- Post added at 10:02 PM ---------- Previous post was at 09:58 PM ----------

Both magic key combinations go back into fastboot when released - grey kindle fire logo [fastboot] underneath

---------- Post added at 10:19 PM ---------- Previous post was at 10:02 PM ----------

I think you're right - a corrupt emmc as it's read only - one to sell for spares or repair!
[Kindle Fire HDX 7" & 8.9" General] draxie:
Sounds hopeless....

That's fairly unceremonious... Nothing interesting on the HDX display either, I assume...

I've never tried to override the filesystem type; so, I have no idea

what to expect, but I wouldn't hold my breath. In any case, the

correct syntax should be 'fastboot format:ext4 aboot' (i.e. basically

what you wrote with no space before the colon). Try it just in case... (-;

NOT GOOD....

That was just a guess, of course, but I've never seen a device that didn't refuse

but still failed erase... (I mean, the command seems to be accepted just fine, but

fails during execution....)
[Kindle Fire HDX 7" & 8.9" General] j0vi:
Hi !

So far I've been able to make adb connection work and create unlock-file successfully. How ever I don't have root access to device so can't dd files.

How to root 4.5.5.2 manually? It seems that adb does not work in recovery or fastboot mode and it's not possible to install any files via stock recovery?

And another issue that might came up next is that "fastboot devices" in fastboot mode does not show my device and according Win7-x64 device manager driver for Kindle is not working in fastboot mode? I installed official Lab126 drivers from 1st post.
[Kindle Fire HDX 7" & 8.9" General] draxie:
You will want to add '-i 0x1949' on your fastboot command-line.

I don't think you need 'adb' for flashing. You should be able to do that via 'fastboot' alone.

You can certainly do so on other devices.

The following _should_ work (caveat: I haven't tested it myself, and I do NOT take responsibility if it misfires):

fastboot -i 0x1949 flash aboot aboot_vuln.mbn
fastboot -i 0x1949 flash recovery twrp_cubed.img
fastboot -i 0x1949 reboot-bootloader
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot

If you decide to try, please report back.

This approach doesn't need a rollback & root.

If you have your EMMC serialno and a [fastboot] prompt,

you're good to go. (The manfid can also be obtained from

fastboot -i 0x1949 getvar emmc_mid.)

Unfortunately, the above was just wishful thinking.

I totally forgot about the minor inconvenience

that the stock bootloader won't let you flash

anything (except an unlock code).
[Kindle Fire HDX 7" & 8.9" General] DB126:
In the event [MENTION=5828306]draxie[/MENTION]'s suggestion does not work the next best option IMO is a rollback to 3.2.8 which can be easily rooted w/towelroot. Be sure to keep WiFi off (and/or flight mode engaged) while on 3.2.8 to prevent an OTA update which is proven fatal to others. We don't yet know how to recover from this type of brick. Towelroot requires brief network connectivity; be sure to toggle off WiFi and immediately reboot (discards partial downloads) after root is obtained. Verify root before reengaging the network. Then immediately block OTA by following step #1 in this post: http://xdaforums.com/kindle-fire-hd...ota-4-5-2-install-gapps-t3043550/post59160158
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yeah, that's why I do not solicit (and politely decline nominations for) XDA title designations. Bullseye on your chest for sucker punches.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Actually, that's probably the only sensible thing to do (until someone figures out how to root 4.5.5.2).

I got a bit carried away and forgot about the stock bootloader's limitations regarding flashing...
[Kindle Fire HDX 7" & 8.9" General] DB126:
I erred as well by not reinforcing the need to block OTA updates before reengaging network services. I updated my earlier post with this important detail.
[Kindle Fire HDX 7" & 8.9" General] cwwilson08:
Hi everyone long time lurker first time poster here.

I have been working at getting my bootloader unlocked for most of the morning now. I have a THOR HDX 7 inch device. which I downgraded from newest firmware then updated to 14.5.5.1.

I finally managed to get adb working and retrieved my device id and serial

Manid - 0x000015

Serial - 0xe00ca859

I have come to part of creating the unlock file with cuber and python and I just cant seem to get it to work. I had tried to not have to do this, but is there a kind soul who could generate the unlock file for me?

Thanks in advance for anyones help in advance...
[Kindle Fire HDX 7" & 8.9" General] ONYXis:
Manid - 0x000015

Serial - 0xe00ca859
[Kindle Fire HDX 7" & 8.9" General] davidk27:
Worked, but had to change the instructions (or interpret differently).

All worked until I did:

fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock​

Just would get "Failed" - doesn't help repeating the step either.

My solution was to follow "draxie" post on cuber and just use mmssssssss.unlock. (run a new cuberHDX with mmssssssss as the input file and use mmssssssss.unlock as the fastboot file).

FYI, I was using Ubuntu 16.04 for this process.

Thanks, so much. I was ready to buy a real android tablet for the past few months.
[Kindle Fire HDX 7" & 8.9" General] cwwilson08:
Thanks this worked a treat. I am on the home stretch. currently have root and unlocked bootloader. succesfully boot into TWRP. I have transferred the rom file from this thread http://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931 to the internal storage of my HDX via adb. Here is where I get the problem.

When I push the install button and swipe to confirm Flash, I am confronted with following error.

Can't install this package (sat Aug 13 19:20:58 BST 2016) over newer build (Wed 31 AUG 10:15:02 BST 2016).

updater process ended with Error: 7

Error installing zip file 'sdcard/kk-fire-nexus-rom-thor-20160813.zip'.

I have not previously flashed any roms to this device, this was my first attempt.

Any sugestions?
[Kindle Fire HDX 7" & 8.9" General] DB126:
- reboot and try again

- if problem persists wipe system/data/cache/dalvik partitions from wipe menu prior to flash attempt
[Kindle Fire HDX 7" & 8.9" General] cwwilson08:
I attempted both with the same error code occurring. I downloaded cm 12.1 rom and installed no issue. Booted seems to be working ok. Back to TWRP tried to install the nexus rom same error. I really have no idea what the issues could other than the obvious of it saying I am trying to install an older build over a newer build. I may try to post in the official thread and see if anyone else has some ideas.

Thank you for your quick response and any other suggestions you may have.
[Kindle Fire HDX 7" & 8.9" General] DB126:
This has happened before but I can not recall (or find reference to) the definitive solution.

[MENTION=5749760]ggow[/MENTION] - any immediate thoughts? Look back a few posts for problem description...error 7, can't flash (Fire Nexus) over newer version. Wipes and reboots have been performed. Unlocked, TWRP.
[Kindle Fire HDX 7" & 8.9" General] ish.org:
Thank you very much

THank you very much!!!

My thos was successfully bootloader unlocked.

I think it is better to add the following to the Manual: of OP.

0) prepare custom ROM in sdcard.

I was very tired to transfer custom ROM to sdcard.

Thor has no OGT usb stick memory and my thos was refused to connect adb push by 'unauthorized'.

I installed custom ROM by the following procedure.

1) freebsd% split -b 500M update-kindle-13.4.5.5_user_455004220-upHDX.zip

2) freebsd# fastboot flash system xaa

3) terminal on TWRP

thor# mkdir /sdcard/Download

thos# cd /sdcard/Download

thor# dd if=/dev/block/mmcblk0p22 of=xaa bs=524288000 count=1

4) freebsd# fastboot flash system xab

5) terminal on TWRP

thos# cd /sdcard/Download

thor# dd if=/dev/block/mmcblk0p22 of=xab bs=357284839 count=1

thor# cat xaa xab > update-kindle-13.4.5.5_user_455004220-upHDX.zip

thor# md5sum update-kindle-13.4.5.5_user_455004220-upHDX.zip

6) freebsd% md5 update-kindle-13.4.5.5_user_455004220-upHDX.zip

Confirm the md5 checksums are same.

7) install update-kindle-13.4.5.5_user_455004220-upHDX.zip by TWRP
[Kindle Fire HDX 7" & 8.9" General] ONYXis:
but in TWRP mode your kindle seen as MTP device...
[Kindle Fire HDX 7" & 8.9" General] ish.org:
Thank you for reply.

I installed fuse mtpfs and can mount MTP now.
[Kindle Fire HDX 7" & 8.9" General] cwwilson08:
I still have had no luck with this :(. Thanks again for your help.

I do have a different question now though. (lol do they ever stop?)

After playing with cm 12.1 there were several apps that wouldn't work properly, so I flashed a cm 11 rom which resolved most of my issues. However I realized I had lost root along the way. Not sure exactly where either. I was able to restore a backup I made immediately after I got root working (root, bootloader unlock, twrp recovery installed and device in automatic fast boot due to the aboot command issued earlier.).

I found cm 11 to do everything I wanted reasonably well and would like to use this rom. It will not install after I restore said backup. I get an error saying there must be a working os or some such.

I flashed cm 12.1 and root remained. - I should add that I used kingroot - which I from reading these threads is not a good thing. Is there a way for me to get to supersu at this point. I attempted to download from play store and run and got errors that It could not uninstall kingroot and failed to install supersu. It also said to update binaries, which looks like a very complex process.

Would the process be easier in fire os? Is it a matter of me figuring out how to update the binaries? Do I need a specific version of superSU?

Can the aboot process in OP be undone to boot me back into my stock os?

I would also like to end on the cm 11 rom, I have tried different combinations of installing the roms after restoring my back up with root..... sheesh that was a lot.

Any Ideas?
[Kindle Fire HDX 7" & 8.9" General] DB126:
You should make use of the OP for each ROM you are trying to flash as each has a different suite of prerequisites, suplemental packages and limitations that are usually spelled out in the first few posts of the relevant thread. While root is integrated into CM 12.1 SuperSU (or equivalent) must be

flashed

to obtain root on CM 11. Simply installing the SuperSU apk won't do it.

Suggested path (some if this is going to seem like rehash):

- download a fresh copy of CM 11, SuperSU zip and a Open GAaps nano (links provided)

- from TWRP verify you can see the device via tether and copy files to/from your preferred host (fall back if files need to be reloaded onto device)

- from TWRP go to Wipe->Advanced, select system/data/cache/dalvik and execute

- reboot device (it won't have a system so you may have force TWRP to boot via <power>+<vol-up> from a cold start

- flash CM 11, SuperSU and GAaps in one operation

- flush cache and dalvik again (should pop up as a recommendation after flash operation)

- restart

How's it look? If the above didn't work we may need to get more aggressive and flush the entire tablet.
[Kindle Fire HDX 7" & 8.9" General] cwwilson08:
Well now if I wasn't overthinking the entire thing. Followed steps exactly as laid out. Rebooted without issue, supersu stated success and es file explorer was able to gain root access. Everything working as hoped.

Thank you so much Davey126 for your help and your patience in getting me where I needed to be.
[Kindle Fire HDX 7" & 8.9" General] Luxen:
I hope someone is able to shed some light on this. I am stuck at the part where I have to use fastboot. I've disabled signature drivers requirement and installed the x64 drivers as recommended. ' adb reboot bootloader' does send me to fastboot but none of the commands seem to be working. I am using Windows 8.1. I would like to avoid using Linux if possible, and I've already successfully created my 0xmmssssssss.unlock
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot format:ext4 aboot

Warning: aboot type is , but ext4 was requested for formatting.

Couldn't parse partition size '0x'.

Should I be using a partition size?
[Kindle Fire HDX 7" & 8.9" General] draxie:
Why not.... (-;

This is a fairly small partition, BTW: only 2MB in size.

You could try with 1MB just to be on the safe side (if it

happens to work for some odd reason). Assuming the

size needs to be in bytes expressed in hexadecimal, the

following should overwrite the first 1MB of aboot:

fastboot format:ext4:0x100000 aboot
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
I thought we'd got there!

C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot format:ext4:0x100000 aboot

Warning: aboot type is , but ext4 was requested for formatting.

Warning: aboot size is , but 0x100000 was requested for formatting.

Creating filesystem with parameters:

Size: 1048576

Block size: 4096

Blocks per group: 32768

Inodes per group: 64

Inode size: 256

Journal blocks: 1024

Label:

Blocks: 256

Block groups: 1

Reserved block group size: 7

error: ext4_allocate_best_fit_partial: failed to allocate 784 blocks, out of space?

target reported max download size of 536870912 bytes

sending 'aboot' (0 KB)...

FAILED ()

finished. total time: 0.004s

C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot format:ext4:0x100000000 aboot

Warning: aboot type is , but ext4 was requested for formatting.

Warning: aboot size is , but 0x100000000 was requested for formatting.

Creating filesystem with parameters:

Size: 4294967296

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 16384

Label:

Blocks: 1048576

Block groups: 32

Reserved block group size: 255

Created filesystem with 11/262144 inodes and 34891/1048576 blocks

target reported max download size of 536870912 bytes

sending 'aboot' (68937 KB)...

OKAY [ 2.438s]

writing 'aboot'...

FAILED (remote: flashing not allowed for locked hw)

finished. total time: 2.501s

---------- Post added at 11:52 PM ---------- Previous post was at 11:42 PM ----------

On screen getvar:max-download-size = 0x200000000 which is why I tried the larger number in the format.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Try with 2MB? And, perhaps, vfat?

Right... but that size is way to big and likely stretches over

other partitions (as I said, aboot is only 2MB). I'm wondering

if the flashing not allowed crap is due to that or also applies

to aboot (it really shouldn't). I'd suggest you try with 0x200000

for size (i.e. just change 1 to 2). Perhaps, my cautious 1MB was

just too small to create an ext4 filesystem to start with.

Another option if to try another filesystem type. I know for a

fact that the modem firmware lives on a FAT partition; so, that

should also be supported, meaning that swapping ext4 for vfat

might be worth a try....

/dev/block/mmcblk0p1 on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
C:\Users\sandneil58\AppData\Local\Android\sdk\platform-tools>fastboot format:vfat aboot

Warning: aboot type is , but vfat was requested for formatting.

Formatting is not supported for file system with type 'vfat'.
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
Hi Draxie, Thanks again for all your help. I've given this one up as a lost cause, but all your help has been appreciated.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Last question

I saw your post about vfat not working.

Did you also try ext4 with 2MB?

fastboot format:ext4:0x200000 aboot

I know that 1MB didn't work, and neither did 4GB,

but the errors were different, which leaves a "maybe?" (-;

Of course, if the eMMC is defective, nothing will work.
[Kindle Fire HDX 7" & 8.9" General] sandneil58:
Yes, I did try 2mb, same issues so believe the memory is defective.
[Kindle Fire HDX 7" & 8.9" General] webby2018:
HDX Apollo 4.5.5.3 Unlock

Hi,

I'm following this process to try and unlock a "new" device I just purchased. I can get it to the point of Fastboot running and 'ready' on the HDX when connected to a Windows 10 PC but when I try to run the wmic commands I get 'No Instance(s) Available'.

I've searched for similar posts/problems but haven't found anything with a solution so I get stuck at this point.

I've also been able to get to the same point using a Linux (Ubuntu) host but stall as I don't know how to identify the target partitions for the aboot and TWRP steps and not able to find any references to a Linux based unlock process.

I'm seriously impressed with all the detail that's in this thread so hopefully someone can help me with this one roadblock.

BTW, I've successfully run the get_code.bat and retrieved the unlock.code. The device is un-rooted as I read that it isn't necessary now with this process.

I hope I'm making sense :)
[Kindle Fire HDX 7" & 8.9" General] iksel:
Did you root first of all?