yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] draxie:
No problem.

Given that you wipe 'data' (which I prefer not to, because I'm too lazy to make backups),

you should be fine with KingRoot, it just takes much longer, but that's your choice.

The real risk is making a mistake when flashing aboot and TWRP, which is the same on both paths.
[Kindle Fire HDX 7" & 8.9" General] xyluss0:
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
[Kindle Fire HDX 7" & 8.9" General] kkcheong:
Have you put both file in the adb directory?
[Kindle Fire HDX 7" & 8.9" General] xyluss0:
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
[Kindle Fire HDX 7" & 8.9" General] kkcheong:
Please print screen. Did you cd to ADB directory?
[Kindle Fire HDX 7" & 8.9" General] achimbub:
Root hdx 7 (3rd Gen.), FireOS 4.5.5.2 with towelroot

Hi,

I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.

Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.

Do i need working internet connection during rooting process with APKs ?

Thx in advance

Achimbub
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Root fails

I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
[Kindle Fire HDX 7" & 8.9" General] DB126:
- TowelRoot is ineffective on FireOS v4

- recommend desktop version of KingRoot for 4.5.5.2 (still may not work)

- device does not need an active internet connection with desktop version

---------- Post added at 04:58 AM ---------- Previous post was at 04:55 AM ----------

KingOroot is the only other tool that reportedly works on 4.5.5.2. It also has a reputation for screwing up devices. Risky choice.
[Kindle Fire HDX 7" & 8.9" General] draxie:
As I've said before, you do NOT need to root your device

in order to flash the vulnerable aboot and unlock...

(link to alternative "daunting" instructions in post #5)
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Ok, but when I try to flash aboot_vuln.mbn I get error. "flashing not allowed for locked hw)" I have no su yet.:(
[Kindle Fire HDX 7" & 8.9" General] DB126:
So you followed the instructions linked in post #5? Seems unlikely given the error message.
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
I can't even find post #5 in this OP. Is it at the very begining?
[Kindle Fire HDX 7" & 8.9" General] DB126:
- OP = Original Post (1st post in this thread)

- count forward five posts; that's the one!

- if the tasks seem daunting STOP; good chance you'll brick your device
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
post #5 has no link. Can you relink here please.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yes, it does. Here's a link to post #5 which contains an embedded link to other posts: https://xdaforums.com/showpost.php?p=71610680&postcount=5
[Kindle Fire HDX 7" & 8.9" General] draxie:
Please don't try this at home!

Yes, it does. See how the last "not" has a different color? That's a link.

In any case, I'd strongly advise against clicking on that link, since based

on your contributions to this thread the likelihood that you'll be able to

follow the instructions without bricking your device feels very very low.

Of course, you're more than welcome to prove me wrong! ;-P
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Thank you so much. Have a great day!
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
I did it easily using the instructions and fastboot. Flashed legacy 14.1 ROM and Open GAPPS and all works well. Love it!

Unfortunately I still do not have root (su) to use certain root apps. Is root coming or not.

I thank you for the great job you and others did to unlock the boot loader. Keep up the good work.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Great! In LineageOS root is usually exposed (toggled) under developer options. A quick Google search will reveal how to enable developer options if you are unfamiliar with the procedure. Enjoy your liberated HDX!
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Oh yes, got root now. Thanks again. You're the man!:good:
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
TWRP 3.1

I flashed TWRP 3.1.0 with Flashify today and all went well.

Question: A friend wants me to mod hers, but she may want to go back to stock. Is it possible to go back to full

Amazon stock after this mod?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Not with common skills, effort and tools. Primary issue is restoring stock recovery which is not easily accomplished. Stock recovery is essential for OTA updates to function. There are workarounds/remediations that yield a 95+% stock experience which may be adequate. Just be cognizant if the opening sentence.

Technical footnote: it may be possible to restore a stock recovery captured with Flashify or extracted from an Amazon image ('.bin'). Both should theoretically work but are unproven in the wild TTBOMK.
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Sounds daunting to say the least. What is "TTBOMK"?
[Kindle Fire HDX 7" & 8.9" General] DB126:
To The Best of My Knowledge :)
[Kindle Fire HDX 7" & 8.9" General] draxie:
Hmm... If one really wants FULL stock, simply renaming a .bin to .zip

and flashing from TWRP as usual should work (and requires minimal

skillz ;^)). Of course, that will also completely negate the "mod" to

begin with, which leads me to the question: why bother?

For "almost full" stock (and, then you most assuredly do NOT want

OTA updates to work), I'd recommend my upHDX script.

The .bin route is a little more involved (since the update only includes

boot.img and a binary patch with a corresponding script to generate

the recovery image from the boot image), but it's decidedly doable.

I'm living proof ;^)))
[Kindle Fire HDX 7" & 8.9" General] DB126:
This has proven disastrous (bricked at bootloader logo) for the few who have tried. I don't immediately recall the details, whether a bootloader downgrade was attempted or some other procedural detail. I simply made a mental note to stay away as the full stock request, until recently, was rare. Gotta decide where to invest limited resources (my time!). :)
[Kindle Fire HDX 7" & 8.9" General] draxie:
Interesting... I could see, or even expect, this happening

when attempting to roll back after rollback protection

has been activated (was it 1x.3.8?), but I'd be surprised

if it happened when using the same or newer version of

FireOS that was last installed on the device....

BUT, it's certainly better to play it safe.

I'm still busy trying to recover an HDX I bricked [via another

glitch], and I can say that Lab126 was diligent. They made sure

to disable memory debug in their "Sahara" (QHSUSB_BULK DL)

implementation also. Oh well....
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Being that there are HDX's going cheap on EBAY, one could experiment without too much $ investment.
[Kindle Fire HDX 7" & 8.9" General] Practically:
I unlocked succesfully and downloaded lıneage .zip how can i install that to my tablet
[Kindle Fire HDX 7" & 8.9" General] kkcheong:
Put the zip in your ADB directory in PC.

In twrp in your tablet, select ADB sideload

In PC, execute ADB sideload zipfilename

This will take a long time
[Kindle Fire HDX 7" & 8.9" General] Vanb85:
I did a quick search of this thread and didn't see anything addressing this, but has anyone figured out how to root with Kingroot and then substitute it with Super Su? I don't really have a need to unlock the bootloader and would prefer to avoid flashing anything, as I recently hard bricked a tablet doing just that. So, I'm a bit gun shy on that front right now. I would just like to maintain root without keeping Kingroot on my tablet. I can easily root with Kingroot 4.8.1, and I have done that temporarily to accomplish a few things, but I have not been able to swap it out with Super Su, which is my preference for maintaining root access. I have an HDX 7 (Thor) on version 4.5.5.2.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Why this complicated approach? With device tethered (TWRP active) internal storage will be exposed on the host, typically within Windows Explorer or the equivalent. Simply drag and drop. Transfer rates progress at the rate of USB2; most ROM zips will transfer in under a minute.
[Kindle Fire HDX 7" & 8.9" General] kkcheong:
I didn't know it's possible to access root directory of Kindle with Windows Explorer during twrp. Thus the complicated approach. I feel stupid already lol.
[Kindle Fire HDX 7" & 8.9" General] kkcheong:
It's hard to brick if you follow exactly my steps. I am noob also didn't brick my Kindle . You can Google about how to replace kingroot. It's all over the internet but not all method works.
[Kindle Fire HDX 7" & 8.9" General] DB126:
XDA is a community; we learn from each other. I have had many a humbling experience at the hands of others and thank them for sharing their time and knowledge. :)

---------- Post added at 02:07 PM ---------- Previous post was at 01:46 PM ----------

In addition to home-brewed methods of varying effectiveness and quality you can use the Super-Sume app available in the Play Store. Just be sure to try it immediately (within 2 hours) so you can secure a refund if it doesn't work. Unfortunately, the author doesn't offer an alternative purchase method if you don't have access to Google Play on the target device.

Alternatively, you can update (but not unlock) the bootloader and then boot a recovery that will permit replacing KingUser with SuperSu. More importantly it provides a method for reviving your device should something go wrong with FireOS. HDX models are famously unrecoverable when FireOS takes a dump as the native Amazon recovery environment offers no options for resetting the operating system (the misnamed "factory reset" simply deletes user data).
[Kindle Fire HDX 7" & 8.9" General] Practically:
Guys you are really hero. I bought my 8.9 inch for 60£ and my only purpose was browsig web watching videos and streams. But with fire os tablet was ultra slow even in its own stock browser. Now I installed nexus 4.4.4 room by using your instructions and you helped me lot patiently. I cannot express how my experience changed. I have a last question on youtube I can just watch up to 720p firstly I thought it was because the hardware is not powerful but i can watch 1080p 60fps streams on twitch without any problem do you have any suggestion for 1080p or higher resolution youtube videos
[Kindle Fire HDX 7" & 8.9" General] Vanb85:
Thanks, but I don't have any real reason to flash my device. The only reason that I asked about replacing kingroot is because I had tried it already without success. I was actually using instructions from this site, but for whatever reason the combination of HDX with Kingroot makes the swap out more difficult. So, I thought someone here might have some insight as to how to overcome that. I figured that swapping out Kingroot must be easier than unlocking the bootloader, but perhaps not in this case.

---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------

Thanks. I do have Google Play on my device. I'll try out Super-Sume. It might be the missing component that I need. It'll be well worth the $3.99 if it can solve this small issue.
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Return to stock
[Kindle Fire HDX 7" & 8.9" General] DB126:
At present there is no packaged method for restoring stock recovery. There are other options (eg: extracting recovery payload from an appropriate stock .bin) but the process is untested and has the potential to generate more headaches than benefit. Be aware that FireOS can not be naturally updated without stock recovery; a repackaged build must be flashed from TWRP. This should not be a problem as 4.5.5.2/4.5.5.3 are the terminal releases for this device (3rd gen HDX) with no significant changes over 4.5.5.1. Primary a security update.

---------- Post added at 02:57 AM ---------- Previous post was at 02:32 AM ----------

I don't believe the official YouTube app supports 1080p streams on KitKat (Android 4.4.4) which Fire Nexus 4.x is based on. 1080p playback is selectable on Android 5.1 builds and above. You will need to unlock the bootloader to run those ROMs.

Fire Nexus is a great ROM. Stick with it unless YouTube 1080p playback is a show stopper.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Not that simple; if it were I would have offered the simple solution. Suggest you abandon the idea of restoring stock recovery. If fact your last experiment would have ended badly if TWRP wasn't available.

As for error 7, use Flashify (available in the Play Store or via APKMirror) to downgrade TWRP to 3.0.0-1 which can be obtained from the TWRP thread. Repackaged stock ROM should the flash fine.

Ask if you can't located the referenced files; don't make any assumptions.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Are you referring to the repacked Amazon update as 'twrp-stock bin'?

In that case, in addition to copying the recovery folder, you'd also need

to restore the relevant lines in the updater-script that perform the work. (-;

(Search for the word 'recovery' in META-INF/com/google/android/updater-script)

Alternatively, you can just copy these three files to your HDX:

system/etc/recovery-resource.dat
boot.img
recovery/recovery-from-boot.p

And, perform these steps to generate stock recovery:

adb shell
# cd /directory/where/you/copied/said/files
# touch recovery.img
# applypatch -b recovery-resource.dat boot.img recovery.img [COLOR="DarkOrange"]f3895b2c29badf911e44bd1ec2b59eec113ee862[/COLOR] [COLOR="Red"]9590784[/COLOR] [COLOR="Orange"]7a3496bfbf6029990640982b9ee6639650c17aaa[/COLOR]:recovery-from-boot.p

The hashes and the size come from recovery/etc/install-recovery.sh

(the specific numbers above correspond to update-kindle-13.4.5.5_user_455004220.bin,

which is probably not what you need, since IIRC you have an Apollo not a Thor; and,

you may be using a different version of the update package for all I know).

If you still have root, you could just 'dd' the resulting 'recovery.img', or copy the file back

and flash from fastboot (assuming your HDX is still unlocked).

On the other hand, if you're experiencing instability, perhaps this is NOT what you

(or your potential buyer) want(s). I don't really know, but I'm thinking that the resale

value of an unlocked device with TWRP + CM14 may be _higher_ than what you can

get for a "restored to stock" HDX.
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Stock

Thanks for the info here. I am on Thor with your twrp-thor-13.4.5.5 rom, rooted with Kingroot, flashify installed, and unlocked. I have the stock bin extracted on the host pc.

Most of these used Thor buyers, don't know the first thing about what unlocked and custom roms are, etc. They buy for the Amazon style for their kids, grandmas, etc. Me, I love to hack them and learn new things.

I am not sure what you mean by "just dd the resulting recovery.img or copy the file back and flash from fastboot"

Flashify should flash as does fastboot, right?

My Apollo is fantastic now thanks to your and Davey126.
[Kindle Fire HDX 7" & 8.9" General] draxie:
There's a specific button for saying "thanks!" (-; ;-P

I've never released any ROM; so, there must be a bit of a misunderstanding somewhere.

Perhaps, someone else did and credited me for the upHDX script. Dunno...

In any case, I'm _very_ surprised that you'd need to root a ROM with KingRoot...

BUT, I may just be reading that wrong.

I'm sure Flashify works as well. I've never used it. I prefer the basics.

FireOS (or Android/Linux/BSD, for that matter) has a 'dd' command,

but if you have to ask, it's safer not to use that (as it's easy to make

grave mistakes, that's why some expand 'dd' as DiskDestroyer...)
[Kindle Fire HDX 7" & 8.9" General] derpilgerer:
pls delete this sorry
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
dd a noob

I know I am not the sharpest knife in the drawer, but I can follow most clear instructions.

Let me try to be clearer with my situation and questions.

1. I am on HDX Thor, unlocked and when I flashed twrp-thor-13.4.5.5._user_455001320.zip (which I mistook you as the releaser, sorry for that). I lost root I guess because its similar to the stock update rom from Amazon . Anyway I used Kingroot to root, not that I like Kingroot, but it rooted quickly on first try with the apk.

So I am trying to return to full stock and thought I was following your latest instructions, but I ran into a snag when I gave adb shell #

applypatch -b recovery-resource.dat boot.img recovery.img

f3895b2c29badf911e44bd1ec2b59eec113ee862 9590784 7a3496bfbf6029990640982b9ee6639650c17aaa:recovery-from-boot.p

It gave this: failed stat "recovery-resource.dat" : no such file or directory

failed to load bonus file recovery-resource.dat

I tried several times but no joy.

That led to my question about the dd. I should have asked where is the "resulting system image" to dd.

I do look at some dd commands, here : http://www.linuxnix.com/what-you-should-know-about-linux-dd-command/
[Kindle Fire HDX 7" & 8.9" General] draxie:
Although this has nothing to do with your problem,

I'd recommend installing the "flashable ZIP" version

of SuperSU from TWRP (next time when you are ready

to wipe everything and reinstall; no point now,

with an ongoing Kingroot "infection").

That error seems to indicate that you either did not copy the 3 files

to your Kindle, or forgot to change to the directory (on your device,

in the shell/adb) holding the files you copied.

Right... when run in the right directory with all the necessary files present,

that 'applypatch' command generates a file called 'recovery.img' (no "system

image", mind you) in the very same directory.
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Ok so I push all three files to the sdcard, and I have adb in my host path, so I open cmd window in the

directory with all three files and give the two adb shell commands. The last command applypatch -b recovery-resource.dat boot.img recovery.img f3895b2c29badf911e44bd1ec2b59eec113ee862 9590784 7a3496bfbf6029990640982b9ee6639650c17aaa:recovery-from-boot.p

Returns: /sbin/sh : applypatch: not found

Now what should I do to applypatch?

Here is the ls ./ where I noticed a recovery.img but not in the /sdcard/

C:\Users\Bobby\Desktop\THOR\recovery>adb ls ./

C:\Users\Bobby\Desktop\THOR\recovery>adb ls ./

000041ed 00000000 59067ebd .

000041ed 00000000 59067ebd ..

000081b6 00000000 59067bf3 recovery.img

000041f8 00001000 59067e13 sdcard

000041ed 00000000 00015c29 sideload

000041f8 00001000 51f70209 cache

000041ed 00000000 00015c29 recovery

000041ed 00000000 00015c29 boot

000081a4 000011f0 00000000 ueventd.rc

000081a4 0000267c 00000000 ueventd.qcom.rc

000041ed 00000000 00000000 twres

000041fd 0000003c 00015c2e tmp

000041ed 00000000 00000000 system

0000416d 00000000 00015c28 sys

000081a4 00003c15 00000000 service_contexts

000081a4 0003f917 00000000 sepolicy

000081a4 0000003f 00000000 selinux_version

000081a4 00000986 00000000 seapp_contexts

000041e8 00000000 59067337 sbin

000041ed 00000000 00000000 res

000081a4 000019c9 00000000 property_contexts

0000416d 00000000 00000000 proc

000041ed 00000000 00000000 oem

000041ed 00000000 00000000 license

000081e8 0000052f 00000000 init.recovery.usb.rc

000081e8 00000047 00000000 init.recovery.qcom.rc

000081e8 00000b1c 00000000 init.rc

000081e8 00002547 00000000 init.qcom.usb.sh

000081e8 000011d1 00000000 init.qcom.ssr.sh

000081e8 00001b8e 00000000 init.qcom.sh

000081e8 00000f84 00000000 init.qcom.sensor.sh

000081e8 000030b2 00000000 init.qcom.factory.sh

000081e8 00001cce 00000000 init.qcom.class_core.sh

000081e8 00000bb6 00000000 init.class_main.sh

000081e8 000a9438 00000000 init

000081a0 000005ec 00000000 fstab.qcom

000081a4 0000c63e 00000000 file_contexts

000041ed 00000000 00015c2f etc

000081a4 00001523 00000000 default.prop

000041f9 00001000 590603f5 data

0000a1ff 0000000d 00000000 charger

000041c0 00000000 57c6a054 root

000041ed 00003b38 00015c29 dev

When I adb pull ./recovery.img it pulls but size is 0

Strange don't you think?
[Kindle Fire HDX 7" & 8.9" General] draxie:
Please use pastebin!

My instructions have 3 commands to run in the adb shell

The first, which you seem to be missing, is "cd /sdcard",

assuming you pushed the 3 files directly to /sdcard ...

Since you say you have adb in your path, it makes no difference

in which directory on your (Windows?) host you run 'adb shell' from.

Now, THAT is strange. You were posting output from that

exact command in your previous post. What did you change?

(Are you testing with a ROM that is not FireOS based?

Or, are you possibly running Linux [or cygwin] and trying to

execute 'applypatch' in the host instead?)

Actually, I don't think that's strange, since the 'touch' command

(the 2nd adb shell command in my instructions) does exactly that:

it creates a zero-sized file if it doesn't exist (or updates it's access

time if it does). The fact that your listing shows 'recovery.img' in

the root directory of your Kindle further supports my theory that

you jumped over the 'cd' command...

If you still cannot get this to work, please upload your entire session

to pastebin and post a link here to ease troubleshooting.
[Kindle Fire HDX 7" & 8.9" General] DB126:
...or leave TWRP installed in the recovery partition and call it a day.
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Pastbin link

Thank you,

Here is my pastebin link:

https://pastebin.com/embed_js/7CkDzWLT
[Kindle Fire HDX 7" & 8.9" General] draxie:
LOL :good:

---------- Post added at 20:42 ---------- Previous post was at 20:32 ----------

Oh, boy... Plus points for using pastebin!

That shows that you were at least listening to half of what I asked. (^;

What you uploaded there, on the other hand, is just a regular forum post

with selected parts of your session and a lot of unsubstantiated claims.

That doesn't really help. The output from the 3 commands (in the adb shell)

looks reasonable, but you say the resulting recovery.img has zero size.

Very fishy... Are you sure you're looking at the right file?

Can you post the output of 'adb shell ls -l /sdcard'?
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Here it is:

https://pastebin.com/embed_js/FVdSqVMQ

I don't understand the recovery.img I pulled has 0 size, but on the sdcard it has exactly what you said.- 9590784 bytes.

Pulled it again and it is 65535 bytes WTF?

Ahha! Pulled it on ubuntu laptop and it is exactly the right size. Windows 10 host sucks. :laugh:
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
Seems like I can flash the new recovery.img to the recovery partition, but not 100% sure. What about the boot.img?
[Kindle Fire HDX 7" & 8.9" General] draxie:
Are you sure?

If you REALLY want stock recovery instead of TWRP,

then you should flash the generated 'recovery.img'

to your recovery partition. You may want to sha1sum

that file to doublecheck your whacky transfers...

The repacked ROM should have the stock 'boot.img'

(you can easily check if that's indeed the case); so,

flashing that one shouldn't be necessary (but neither

should it hurt).
[Kindle Fire HDX 7" & 8.9" General] bobcat131:
No joy! I flashed the new recovery.img to the recovery partition with fastboot, but when I gave

fastboot -i 0x1949 reboot, it rebooted to the fastboot mode. Also tried power + volume + keys

and it booted into fastboot mode. So now what sir? Only fastboot available, no adb.

Oh, the sha1sum gives ok. :crying: