Thor & 4.5.5.2 : Easy to root and Unlock Bootloader

Search This thread

kkcheong

Senior Member
Oct 20, 2009
309
32
Penang
LG V50 ThinQ
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-

1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work. Some even report success after 20 tries.
2. Flash TWRP and Unlock bootloaders. Instruction in https://xdaforums.com/kindle-fire-h...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in the thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
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
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.

Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.

Added another instructions from another forumer who think my instructions is not complete:-
1. Install the moto driver and then plug in your device while running normal
2. Run the get_code.bat (from this link)
3. once unlock.code file is created, run "adb reboot bootloader". It will show [Fastboot] with the kf logo.
4. Once bootloader comes up, change driver in device manager for "Other Android" to use the Android -> Mot Adb Composite Driver. It should say "Ready" on the KF
5. Run the stuff from this post (do the bottom steps with fastboot erase first)
6. After you are done in bulk mode, hold the power button for 15 secs to reboot. It will automatically boot into Fastboot
7. When you run the unlock command, use the "unlock.code" file.. not the "0xmmssssssss.unlock" example from that link.
8. Now unplug and hold power again to shut down. Hold VolUp + Power. About 3 secs after you see the KF logo, you can let go of the power button (possibly both buttons) and you get TWRP
From here you can flash CM and gapps (5.1).
 
Last edited:

BatmanDC

Member
May 12, 2013
22
0
Markham
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
 

DB126

Senior Member
Oct 15, 2013
15,362
10,174
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
You do not need to be on 4.5.5.2 or any specific version of FireOS for that matter. Is the device rooted?
 

kkcheong

Senior Member
Oct 20, 2009
309
32
Penang
LG V50 ThinQ
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working

As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
 
  • Like
Reactions: DB126

DB126

Senior Member
Oct 15, 2013
15,362
10,174
...it seems if you kingroot and wipe everything it negates any malware?
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
 
  • Like
Reactions: draxie

barrist

Senior Member
Apr 25, 2009
898
79
Ottawa
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.

Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.

Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
 

DB126

Senior Member
Oct 15, 2013
15,362
10,174
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
There are no bad/unstable HDX ROMs. Fire Nexus has the advantage for those needed full Bluetooth and/or LTE support. Otherwise LineageOS 14.1 is a solid choice. Regardless of direction you'll want to unlock the bootloader and wipe the device immediately after rooting if KingRoot is utilized. Also know Amazon devices have their own set of quirks and don't behave like a typical Android gizmo.
 

barrist

Senior Member
Apr 25, 2009
898
79
Ottawa
Thanks maybe I'll give lineage a shot as I don't really don't need LTE or bt .. just hoping for stable app support and wifi
 

draxie

Senior Member
Apr 20, 2014
515
642
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:

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.
 
Last edited:

xyluss0

Member
Apr 8, 2017
7
0
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-

1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://xdaforums.com/kindle-fire-h...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.

Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.

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?
 

xyluss0

Member
Apr 8, 2017
7
0
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".
 

achimbub

New member
Mar 15, 2012
1
0
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
 

bobcat131

Senior Member
Sep 15, 2013
155
15
Venice
Root fails

Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-

1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://xdaforums.com/kindle-fire-h...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.

Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.

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?
 

DB126

Senior Member
Oct 15, 2013
15,362
10,174
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
- 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 ----------

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

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-

    1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work. Some even report success after 20 tries.
    2. Flash TWRP and Unlock bootloaders. Instruction in https://xdaforums.com/kindle-fire-h...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in the thread. The step is:-
    a) install ADB driver and install Kindle Fire USB driver
    b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
    b) create unlock.code with get_code.bat
    c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
    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
    d) make sure check the Android ADB Composite driver is properly install in Device Manager
    e) execute unlock.bat
    f) reboot, press UP + power to boot into TWRP
    g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.

    Tips:-
    1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
    2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
    https://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
    3. Safe Strap is not supported in 4.5.5.2
    4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
    5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.

    Added another instructions from another forumer who think my instructions is not complete:-
    1. Install the moto driver and then plug in your device while running normal
    2. Run the get_code.bat (from this link)
    3. once unlock.code file is created, run "adb reboot bootloader". It will show [Fastboot] with the kf logo.
    4. Once bootloader comes up, change driver in device manager for "Other Android" to use the Android -> Mot Adb Composite Driver. It should say "Ready" on the KF
    5. Run the stuff from this post (do the bottom steps with fastboot erase first)
    6. After you are done in bulk mode, hold the power button for 15 secs to reboot. It will automatically boot into Fastboot
    7. When you run the unlock command, use the "unlock.code" file.. not the "0xmmssssssss.unlock" example from that link.
    8. Now unplug and hold power again to shut down. Hold VolUp + Power. About 3 secs after you see the KF logo, you can let go of the power button (possibly both buttons) and you get TWRP
    From here you can flash CM and gapps (5.1).
    3
    ok i tried my laptop and got further. I changed the driver to "Android Bootloader Driver".. and got "Ready" showing. Also tried with "Android Composite ADB Driver" and that also showed me Ready.
    I now have "Ready" showing up on my KF in fastboot
    But that's all. Still can't run the wmic commands as they say "No instance(s) available) ... and "fastboot devices" doesn't show any devices. So I still cannot communicate with it even though it appears to be ready.
    Download the Motorola Device Manager from here and install. Then place HDX in fastboot mode and update Win driver to "Mot Composite ADB Interface" (if successful will show under Android heading in Device Manger). Also make sure you are using the latest Minimal ADB and Fastboot (here). Combination should do the trick assuming cable is ok.
    3
    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.
    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 ----------

    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.
    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.
    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).
    3
    THANK YOU!!!
    This was it! The Mot driver makes it work as expected.
    So the full process
    1. Install the moto driver and then plug in your device while running normal
    2. Run the get_code.bat (from this link)
    3. once unlock.code file is created, run "adb reboot bootloader". It will show [Fastboot] with the kf logo.
    4. Once bootloader comes up, change driver in device manager for "Other Android" to use the Android -> Mot Adb Composite Driver. It should say "Ready" on the KF
    5. Run the stuff from this post (do the bottom steps with fastboot erase first)
    6. After you are done in bulk mode, hold the power button for 15 secs to reboot. It will automatically boot into Fastboot
    7. When you run the unlock command, use the "unlock.code" file.. not the "0xmmssssssss.unlock" example from that link.
    8. Now unplug and hold power again to shut down. Hold VolUp + Power. About 3 secs after you see the KF logo, you can let go of the power button (possibly both buttons) and you get TWRP
    From here you can flash CM and gapps (5.1).

    Thanks everyone for all the help!! I did all 4 of my KF HDX 7's with perfect success on each.
    It's amazing how much faster CM12 runs on these babies! I was about to give up and buy some Tab S2's but these things are so fast now.
    Well done. @draxie is a great resource who knows the ins and outs of HDX devices better than just about anyone.

    Note CM 12.1 is no longer supported and does not play nice with Bluetooth peripherals. There are a handful of well regarded custom ROMs for this device including LineageOS 14.1 which is a descendant of CM 12.1. I use the latter on one of my primary HDXs mainly for Xposed compatibility. It's quite stable and responsive but isn't the most power efficient in some states and consumes 15-20% more memory for 'core' processes vs MM/Nougat successors. Slim 7 is a promising new comer along with LineageOS 13.0 which demonstrate excellent BlueTooth compatibility if that's important to you.

    Enjoy your liberated devices!

    ---------- Post added at 01:21 PM ---------- Previous post was at 01:05 PM ----------

    If the device finally *connected* in fastboot mode (ready prompt is showing), I see no need to mess with drivers any further...
    Unfortunately, the presence of a "Ready" prompt does not always equate to a functional fastboot connection on this device...at least w/Windows. Typically corrected with a different driver although I have personally experienced flaky USB cables exhibit the same behavior. Issuing fastboot "devices" command (adding vendor flag as needed) usually validates connection viability. Lucky Linux users generally don't have to jump through these hoops assuming the USB cable is up to snuff.
    2
    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:
    Yep - recall that recommendation to leave well enough alone. Been down this path before. I'm certain @draxie will get things cleaned up. Reflashing stock recovery has never been a clean procedure...although that may change in the future based on learnings from this go-around.

    As an aside, you can reinstall and/or boot TWRP from fastboot (assuming an unlocked bootloader) which is the likely the path @draxie will take to revive your device. Good chance whatever ROM was previously installed remains intact; same for contents of the data partition. See TWRP thread for related fastboot commands.