Unlocking bootloader with HDX Nexus ROM - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.

yoyohoho said:
Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.
Click to expand...
Click to collapse
HDX Nexus 4.0.5 was likely rooted. Regardless, it's an older/discontinued build that should be updated.
You can install TWRP on any rooted 3rd gen HDX by following step #2 (only) in the OP in this thread; steps #1 and #3 pertain to unlocking the bootloader.
Please note that while the above procedure has been sucessfully executed by dozens of HDX owners there is risk involved that could easily lead to a bricked device. Basically if anything goes wrong the device is toast.
Once TWRP is available you can flash the HDX builds of CM 11 or Fire Nexus HDX (successor to v4.0.5). Be sure to follow the flashing instructions in the relevant ROM thread OP. You will need to unlock the bootloader to install any other custom ROM.

Unlocking bootloader
Thank you, thank you, your simple instructions worked liked a charm. Only took about 10 minutes to complete, yet I spent 4 hours searching forums for an answer....ackkk.
Anyhow, at some point I'd like to upgrade to CM12 since there are a couple apps that require Android 5.1 or later. So I need to get my bootloader unlocked. I followed the posting by ONYXis, but it kept saying that unlock code is incorrect. My question is: Would the procedure work if I installed FireOS (maybe 4.5.2)? Or am I missing some other step?
Thank you, thank you again

yoyohoho said:
Thank you, thank you, your simple instructions worked liked a charm. Only took about 10 minutes to complete, yet I spent 4 hours searching forums for an answer....ackkk.
Anyhow, at some point I'd like to upgrade to CM12 since there are a couple apps that require Android 5.1 or later. So I need to get my bootloader unlocked. I followed the posting by ONYXis, but it kept saying that unlock code is incorrect. My question is: Would the procedure work if I installed FireOS (maybe 4.5.2)? Or am I missing some other step?
Thank you, thank you again
Click to expand...
Click to collapse
Unlock code and application procedure works on any rooted 3rd gen HDX with a vulnerable bootloader regardless of installed ROM, recovery, etc. Most likely you have a typo in one of the input values or the concatenated string fed to the code generator is not in the proper format. Look carefully at required format in the OP along with your manfid and serial to insure everything is to spec.
If still no joy post your manfid and serial in the other thread (referencing this discussion) and request someone generate an unlock code on your behalf. I am travelling this weekend with no access to my Windows box until Monday.
Be aware unlocking poses no risk to your device; it will either work or not. Also try a different USB port and/or cable. I know it sounds far fetched but amazing how many times that "fixes" fastboot weirdness.

Solved
Davey126 said:
Unlock code and application procedure works on any rooted 3rd gen HDX with a vulnerable bootloader regardless of installed ROM, recovery, etc. Most likely you have a typo in one of the input values or the concatenated string fed to the code generator is not in the proper format. Look carefully at required format in the OP along with your manfid and serial to insure everything is to spec.
If still no joy post your manfid and serial in the other thread (referencing this discussion) and request someone generate an unlock code on your behalf. I am travelling this weekend with no access to my Windows box until Monday.
Be aware unlocking poses no risk to your device; it will either work or not. Also try a different USB port and/or cable. I know it sounds far fetched but amazing how many times that "fixes" fastboot weirdness.
Click to expand...
Click to collapse
Many, many thanks to you, Davey126, for your encouragement and patience with my noobness.
I knew my unlock file was OK since I verified with OpenSSL... cable, ports and drivers were OK too.
The solution for ME was to switch over to a WinXP box from a Win10 box, and it worked flawlessly. I admit though that I still use XP as my main system so I'm very familiar with it, however, when I started this endeavor things like Android SDK needed a 64-bit box.
Anyways, thanks again for your support and score one for WinXP

yoyohoho said:
Many, many thanks to you, Davey126, for your encouragement and patience with my noobness.
I knew my unlock file was OK since I verified with OpenSSL... cable, ports and drivers were OK too.
The solution for ME was to switch over to a WinXP box from a Win10 box, and it worked flawlessly. I admit though that I still use XP as my main system so I'm very familiar with it, however, when I started this endeavor things like Android SDK needed a 64-bit box.
Anyways, thanks again for your support and score one for WinXP
Click to expand...
Click to collapse
Glad you got everything working! Sometimes good old XP still shines bright.

I too have got the same device as yours with the same HDX nexus ROM installed which has glitches like you mentioned (automatic startup of apps etc), managed to root it and managed to install twrp but just can't make fastboot execute unlock probably windows fastboot driver issues. I am working on it, may be i will try with win xp on a virtual machine. By the way, i wanted to know which ROM did you try and which one did you find to be working well with this device with buttery smooth experience and no glitches and that all those glitches were settled after bootloader unlock and flashing of a ROM? kindly do suggest some ROM and if possible the drivers that you used to unlock or any other details necessary. thanks

Same here, but i can't to root my device
I tried kingroot and towelroot, but didn't works

ybridos said:
Same here, but i can't to root my device
I tried kingroot and towelroot, but didn't works
Click to expand...
Click to collapse
same here, refubrished device from ebay, Nexus Rom, stock recovery, and unable to root it, kinroot didn't work :crying:
---------- Post added at 10:43 AM ---------- Previous post was at 10:11 AM ----------
Hey, im just rooted it! All what needed were Factory reset and mobile Kingroot. Hope this will work for other preople!

xob0t said:
same here, refubrished device from ebay, Nexus Rom, stock recovery, and unable to root it, kinroot didn't work :crying:
---------- Post added at 10:43 AM ---------- Previous post was at 10:11 AM ----------
Hey, im just rooted it! All what needed were Factory reset and mobile Kingroot. Hope this will work for other preople!
Click to expand...
Click to collapse
I have tried with Kingoroot and it is worked on first try. May be helpful to you, good luck

I have same device with #Davey126
I wanna install TWRP and then root my KF,
so, Is this step below is good for me?
2. Flash old vulnarable aboot and cubed twrp (just in case). Check that all these commands executed without errors. If you'll get one - read second post below. If your firmware <=13(14)3.2.3.2 skip this step.
Download aboot and twrp for Thor (Kindle Fire HDX 7) https://drive.google.com/open?id=0B2...GxXMUZPZTlZTUk or for Apollo (Kindle Fire HDX 8.9) - https://drive.google.com/open?id=0B2...zJDQkczNzRLaHM - and put this two files (twrp_cubed.img and aboot_vuln.mbn) into root of your kindle internal storage.
Run:
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 =)
Click to expand...
Click to collapse
Quoted from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982

yoyohoho said:
Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.
Click to expand...
Click to collapse
Can anyone help me unlock bootloader?
my KF HDX 7 ís same #yoyohoho with 4.4.4 installed.
I searched few days, but cant find exactly way, because my english is so bad
Hey yoyohoho, can u help me?

Mark2014 said:
Can anyone help me unlock bootloader?
my KF HDX 7
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993

Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
I read it before but not sure. tks

Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
i'm follow your link but stucked after go into [fastboot]
image attached below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KF screen alway show Ready without step:
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
it shows "waiting for device" and I wait a half of hour but nothing happen.
Iam using win7 64b, and usb driver already installed.
What should I do next?

hi there, i have similiar situation, yet a little bit different. from Fire OS (don't remember version number) i went to this ROM: https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931 and i have Bootstrap on my device. it means, that my BL is locked. may i use this steps https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006 to unlock BL?

miguelm75 said:
hi there, i have similiar situation, yet a little bit different. from Fire OS (don't remember version number) i went to this ROM: https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931 and i have Bootstrap on my device. it means, that my BL is locked. may i use this steps https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006 to unlock BL?
Click to expand...
Click to collapse
Yes. Linked procedure does not care how the device is currently configured.

Davey126 said:
Yes. Linked procedure does not care how the device is currently configured.
Click to expand...
Click to collapse
thanks. i have one problem - where should I look for drivers to change drivers to "Fire Devices - Android Adb Composite Driver"? because when i try to change to drivers installed to c:\Program Files (x86)\Amazon.com\Fire_Devices\, system says "I cannot install Android device".
my operation system is Windows 10

miguelm75 said:
thanks. i have one problem - where should I look for drivers to change drivers to "Fire Devices - Android Adb Composite Driver"? because when i try to change to drivers installed to c:\Program Files (x86)\Amazon.com\Fire_Devices\, system says "I cannot install Android device".
my operation system is Windows 10
Click to expand...
Click to collapse
Install the Motorola Device Manager (here) which contains compatible drivers for HDX devices that work on a wide variety of platforms. You don't need to run the manager, just install it. One click goodness that actually does something userful.

Davey126 said:
Install the Motorola Device Manager (here) which contains compatible drivers for HDX devices that work on a wide variety of platforms. You don't need to run the manager, just install it. One click goodness that actually does something userful.
Click to expand...
Click to collapse
still no luck
this is strange - when Kindle is powered on, is visible in "Device Manager" as "Android Adb Composite Driver", but when i reboot it to BL, it's "Other devices"/"Android" and it cannot be changed
and i installed Motorola drivers. should i restart system?

Related

[Help Thread][ Fire HD 6 and 7 ](4th Gen-2014) Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Fire HD 6 - 2014
&
Fire HD 7 - 2014​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@sd_shadow
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible of posting there, you may post here. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
Fire Index: Which Amazon (Kindle) Fire Do I have? There are several Amazon Fires. Be sure you know which one you have
[Index] Fire HD 6 and 7 (2014)
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
​
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Amazon Fire HD 6 and 7[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: How do I know if i have a Fire HD 7 (2014) ?[/SIZE]The Fire HD 7 has Power and volume buttons on the side, VGA front-facing camera, Rear-facing HD camera.​
[SIZE=+1]Q2: How do I know if I have a Fire HD 6?[/SIZE]The Fire HD 6 has Power and volume buttons on the side- VGA front-facing camera - Rear-facing HD camera.​
[SIZE=+1]Q3: How Do I root and install Twrp?[/SIZE][Guide Finder] Root, Upgrade, Back to Stock + More by DoLooper​*​Forum Rules | New Users Guide | XDA Tour | Report Posts​A special thanks to everyone who contributed to the production of this FAQ​
Help
I blocked the kindle fire hd six lock ads using com.amazon.kindle.kso . Then an Ota update started I didn't think anything about it applied the update then went to a bootloop does com.amazon.kindle.kso have anything to do with this ?
Jddiaz said:
I blocked the kindle fire hd six lock ads using com.amazon.kindle.kso . Then an Ota update started I didn't think anything about it applied the update then went to a bootloop does com.amazon.kindle.kso have anything to do with this ?
Click to expand...
Click to collapse
You blocked or used ?
adb hide com.amazon.kindle.kso
Should haven't caused a problem? Root?
May need to do a factory reset.
Maybe @DoLooper has suggestion?
Jddiaz said:
I blocked the kindle fire hd six lock ads using com.amazon.kindle.kso . Then an Ota update started I didn't think anything about it applied the update then went to a bootloop does com.amazon.kindle.kso have anything to do with this ?
Click to expand...
Click to collapse
sd_shadow said:
You blocked or used ?
adb hide com.amazon.kindle.kso
Should haven't caused a problem? Root?
May need to do a factory reset.
Maybe @DoLooper has suggestion?
Click to expand...
Click to collapse
It wouldn't be from disabling com.amazon.kindle.kso. It sounds suspiciously like what's happening here, though. Jddiaz, were you rooted? Did you try to downgrade or do anything else after the upgrade was installed, or did it go into loop as soon as it rebooted at end of upgrade?
i rooted and updated the HD 6 no problem, but when i launch the play store, it shows Play Store | Work, There are no apps to install, since your administrator hasn't made any available to you yet
now, i can still search and install apps no problem, but can't get the default homepage. any idea why?
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
Hello,
I am currently running a rooted Fire HD 7 on update 4.5.3 and I would like to edit the build information so that it isn't seen as a kindle by apps and the market. I have been searching for solutions but I can't seem to find anything that made sense to me. I have no clue on how to go about doing this (how to change it and what to change it to) so any help would be greatly appreciated.
Thanks,
Revolve
Rooted, factory reset, now bricked
Hi,
I hope someone can help me. I had my mom's Fire HD 7 rooted running 4.5.4. I don't know what happened, but she factory wiped it. After that, the launcher's gone, I think, because all we saw was the settings menu. And here comes the stupid part...without knowing what I am doing, I used TWRP to restore a file called 2015-08-06--14-57-17_KTU84M_test-keys, and ended up with error 255!
And now when I boot the Fire up, I'm stuck with the amazon logo (doesn't even get to the Fire logo).
However, I can still get into TWRP. I hope there's still hope.
And oh, I can't ADB either.
Please help this idiot newbie out.
TIA
Emerald9 said:
Hi,
I hope someone can help me. I had my mom's Fire HD 7 rooted running 4.5.4. I don't know what happened, but she factory wiped it. After that, the launcher's gone, I think, because all we saw was the settings menu. And here comes the stupid part...without knowing what I am doing, I used TWRP to restore a file called 2015-08-06--14-57-17_KTU84M_test-keys, and ended up with error 255!
And now when I boot the Fire up, I'm stuck with the amazon logo (doesn't even get to the Fire logo).
However, I can still get into TWRP. I hope there's still hope.
And oh, I can't ADB either.
Click to expand...
Click to collapse
Wow! The only thing to try is to see if the device can be detected in TWRP's sideload mode: Plug into computer and go to "adb sideload" in TWRP. (You should be prompted to type "adb sideload...") Look at device manager and see if the tablet shows up anywhere (like under Other?). If you can find the device in device manager, update/install drivers and post back. If tablet doesn't show up in device manager, AFAIK you're out of luck.
Thank you DoLooper. I followed your advice and the device showed up as ariel with no drivers installed for it. Please advice.
Another thought I have is this...Under the Install option in TWRP, I can see the following files:
454_update.zip
pa_gapps-modular-pico(uni)-4.4.4-20150308-signeed.zip
UPDATE-superUS-v2.46.zip
Can I install any of the files here?
TIA
DoLooper said:
Wow! The only thing to try is to see if the device can be detected in TWRP's sideload mode: Plug into computer and go to "adb sideload" in TWRP. (You should be prompted to type "adb sideload...") Look at device manager and see if the tablet shows up anywhere (like under Other?). If you can find the device in device manager, update/install drivers and post back. If tablet doesn't show up in device manager, AFAIK you're out of luck.
Click to expand...
Click to collapse
Emerald9 said:
Thank you DoLooper. I followed your advice and the device showed up as ariel with no drivers installed for it. Please advice.
Another thought I have is this...Under the Install option in TWRP, I can see the following files:
454_update.zip
pa_gapps-modular-pico(uni)-4.4.4-20150308-signeed.zip
UPDATE-superUS-v2.46.zip
Can I install any of the files here?
TIA
Click to expand...
Click to collapse
probably need to manually select drivers in Device manager
similar to these instructions
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
Sent from my XT1060 using Tapatalk
Thank you so much. I now have ADB sideload. Now I'm clueless as to what to do next? Please give me step-by-step instructions or if there a thread already covered this issue please let me know.
Thanks so much for the help
Emerald9 said:
Thank you so much. I now have ADB sideload. Now I'm clueless as to what to do next? Please give me step-by-step instructions or if there a thread already covered this issue please let me know.
Thanks so much for the help
Click to expand...
Click to collapse
you need to set up adb
then
Code:
adb sideload filename
basic instructions in my
Fire Index: Which Amazon (Kindle) Fire Do I have?
Sent from my XT1060 using Tapatalk
sd_shadow said:
you need to set up adb
then
Code:
adb sideload filename
basic instructions in my
Fire Index: Which Amazon (Kindle) Fire Do I have?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Please bear with me, but what file or files am I supposed to sideload? I'm really clueless as to where to go from here. At this point, I just want the Fire to be just as the day Mom bought it. I'll think about rooting it later. Thanks
Emerald9 said:
Please bear with me, but what file or files am I supposed to sideload? I'm really clueless as to where to go from here. At this point, I just want the Fire to be just as the day Mom bought it. I'll think about rooting it later. Thanks
Click to expand...
Click to collapse
When you sideload an update bin you'll lose root, so I suggest you install the rootable 4.5.3 update, which was probably on there originally. Get it at step 3 here: [http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351]
Put the 4.5.3 update into the folder where you have adb.exe, turn off wifi and open a CMD window from the folder with the update. While in TWRP sideload mode, type adb devices. You should see "serialnumber . . . SIDELOAD".
On PC type: adb sideload <update bin name>. Be sure the sideload is complete, then reboot. If it reboots, type "adb devices" and make sure drivers are working. If not, install them again for this regular "OS" mode. Then type "adb reboot recovery" and be sure you can get into recovery. (I think this will be stock recovery now.)
Look at the root guides for commands to block OTA update so device doesn't update to 4.5.5. (Then you can easily root later if you want to.)
EDIT: @Emerald9 FYI: The reason you can't use that 4.5.4 update on the device is that it was modified to NOT update the bootloaders, so user would still have 4.5.3 bootloaders, which are the only ones that can boot TWRP. When you installed that strange-name file you overwrote the 4.5.3 bootloaders and when the new bootloaders found the unsigned TWRP in recovery, they refused to continue. This may not be the only problem caused by that file, but I'm hopeful that the sideload will fix things.
DoLooper said:
When you sideload an update bin you'll lose root, so I suggest you install the rootable 4.5.3 update, which was probably on there originally. Get it at step 3 here: [http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351]
Put the 4.5.3 update into the folder where you have adb.exe, turn off wifi and open a CMD window from the folder with the update. While in TWRP sideload mode, type adb devices. You should see "serialnumber . . . SIDELOAD".
On PC type: adb sideload <update bin name>. Be sure the sideload is complete, then reboot. If it reboots, type "adb devices" and make sure drivers are working. If not, install them again for this regular "OS" mode. Then type "adb reboot recovery" and be sure you can get into recovery. (I think this will be stock recovery now.)
Look at the root guides for commands to block OTA update so device doesn't update to 4.5.5. (Then you can easily root later if you want to.)
EDIT: @Emerald9 FYI: The reason you can't use that 4.5.4 update on the device is that it was modified to NOT update the bootloaders, so user would still have 4.5.3 bootloaders, which are the only ones that can boot TWRP. When you installed that strange-name file you overwrote the 4.5.3 bootloaders and when the new bootloaders found the unsigned TWRP in recovery, they refused to continue. This may not be the only problem caused by that file, but I'm hopeful that the sideload will fix things.
Click to expand...
Click to collapse
Thanks so much. I will find some time to sit down and proceed as instructed tonight.
Emerald9 said:
Thanks so much. I will find some time to sit down and proceed as instructed tonight.
Click to expand...
Click to collapse
I'm in trouble. I got an error message saying "This package is for "full_ariel" products; this is a "omni_ariel". This message appears after I ran the adb sideload command on the 4.5.3 update. Please help.
Emerald9 said:
I'm in trouble. I got an error message saying "This package is for "full_ariel" products; this is a "omni_ariel". This message appears after I ran the adb sideload command on the 4.5.3 update. Please help.
Click to expand...
Click to collapse
Did a little searching and came upon a similar issue. He solved by following this:
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Can I rename the file (from step #1) from zip to bin and adb sideload as before?
Emerald9 said:
Did a little searching and came upon a similar issue. He solved by following this:
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Can I rename the file (from step #1) from zip to bin and adb sideload as before?
Click to expand...
Click to collapse
Hang on. I'm writing up steps for you right now.
EDIT: @Emerald9 No, leave filenames as "zip." What I was writing:
OK. I'm assuming it's correct that you know you can't get to the OS (where you could dowload files onto the device or install adb drivers).
I've not done this but I think(hope) it will work. Go here[http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449] and follow the steps beginning with step 1, except instead of flashing in TWRP use the TWRP sideload.
After step 1, manually reboot to recovery/TWRP. (Power off, then hold down power button and volume+)
At step 2a, you can sideload either the 4.5.3 or 4.5.5 update. Be sure to do step 2b. Skip Gapps. DO wipe cache and dalvik in TWRP.
Tap Reboot and System and look for prompt at top of TWRP "install super su?" and swipe the slider to say yes.
Let's hope you boot into OS!!! Post back for more info. Good luck!
EDIT2: @Emerald9 After step 1, you can do Reboot and then Recovery button in TWRP. Don't have to do manually

Root Kindle Fire HDX

Hi. I'm new here & registered in the hopes of finding a working solution since I've been trying for days.
I'm trying to root my Kindle Fire HDX 7" that's running OS 4.5.5. I've read a lot about needing to downgrade or rollback to version 3.2.8 first to be able to root. I downloaded the Thor bin file on my Kindle, but am not sure what to do with it or where to go from here. So I haven't gotten very far in the process & am stuck. Any help would be greatly appreciated!! And when responding, please bear in mind that I know very little about doing this sort of thing.
Thank you!!!!
gr8fuldee said:
Hi. I'm new here & registered in the hopes of finding a working solution since I've been trying for days.
I'm trying to root my Kindle Fire HDX 7" that's running OS 4.5.5. I've read a lot about needing to downgrade or rollback to version 3.2.8 first to be able to root. I downloaded the Thor bin file on my Kindle, but am not sure what to do with it or where to go from here. So I haven't gotten very far in the process & am stuck. Any help would be greatly appreciated!! And when responding, please bear in mind that I know very little about doing this sort of thing.
Thank you!!!!
Click to expand...
Click to collapse
My suggestion is you keep reading through the HDX forums to increase your knowledge of techniques, procedures and potential pittfalls that can permanently cripple your device (bricking). This is exceptionally easy to do. I understand you are new and seeking guidance but everything you need to know is here. The lack of responses reflects the reluctance of experienced contributors to pen yet another custom response. Post specific questions as they arise. You'll typically get a prompt response provided you have done your homework.
Thank you for your reply. I feel like I have spent a huge amount of time trying to root my kindle by researching and dowloading this or that. So, here's where I'm currently at. I have been following the directions on gizmag. I backed everything up & am using a computer running Windows 8. I enabled the ADB & downloaded the ADB files (from this site, I believe). When I ran the .exe file, the installation wizard gave me this error: "The device driver installation wizard did not update any of your software for your hardware devices because it was not better than the software you currently have installed".
That's as far as I've gotten. I hope the additional information will help users to assist me.
Thank you!
gr8fuldee said:
Thank you for your reply. I feel like I have spent a huge amount of time trying to root my kindle by researching and dowloading this or that. So, here's where I'm currently at. I have been following the directions on gizmag. I backed everything up & am using a computer running Windows 8. I enabled the ADB & downloaded the ADB files (from this site, I believe). When I ran the .exe file, the installation wizard gave me this error: "The device driver installation wizard did not update any of your software for your hardware devices because it was not better than the software you currently have installed".
That's as far as I've gotten. I hope the additional information will help users to assist me.
Thank you!
Click to expand...
Click to collapse
Regarding adb you can obtain the highly regarded 'Minimal ADB and Fastboot here:
forum.xda-developers.com/showthread.php?t=2317790
Install and make sure you can access your device via adb before proceeding. Use Google to learn basic adb commands as needed.
Take the gizmag article with a grain of salt. While there is good content much of the material is dated and likely not applicable to your device. HDX forums on XDA are your best resource for the most current info.
I managed to get the first 2 steps done from a thread I found on here, which were to downgrade to 3.2.8, then upgrade to 4.5.2. The next step says to "use Kingroot or another method". Does Kingroot work for the kindle hdx 7, do you know? I've tried downloading it & keep getting an error that says "Failed - Network error". What are the other methods available? Thanks again!
gr8fuldee said:
I managed to get the first 2 steps done from a thread I found on here, which were to downgrade to 3.2.8, then upgrade to 4.5.2. The next step says to "use Kingroot or another method". Does Kingroot work for the kindle hdx 7, do you know? I've tried downloading it & keep getting an error that says "Failed - Network error". What are the other methods available? Thanks again!
Click to expand...
Click to collapse
Kingroot works with all HDX models running FireOS v4.5.2. You can grab it from here. A brief network connection is required during the rooting process. Be prepared to flip WiFi on; run Kingroot and then immediately disable WiFi. Leave it on too long an you will likely receive an OTA update that will plug the vulnerability that permits rooting. If that happens you'll have to redo the rollback/upgrade procedure.

[Q] HDX 7 13.3.1.0_user_310079820 - Help Needed

As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
PariahNine said:
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
Click to expand...
Click to collapse
Given your firmware level:
- verify device is still rooted (use towelroot if needed)
- flash twrp recovery
- update bootloader to v3.2.3.2
- unlock bootloader (try 1-click method)
- flash rom of choice (Nexus, CM 11/12/13), SlimLP)
Search through the forums for relevant threads. Ask questions along the way. You have some work ahead (hours) but a nice reward at the other end.
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
PariahNine said:
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
Click to expand...
Click to collapse
Thoughts:
- moving roms between slots (specifically stock) via backup/restore is generally a bad idea in Safestrap; consider yourself lucky if you used this technique
- if the rom in the stock slot (assuming FireOS 13.3.1.0) boots properly then you can safely remove Safestrap v3 via the uninstall option in the apk
- do not wipe anything in Safestrap nor execute a 'factory reset' from the native Kindle recovery menu (bad outcomes)
- keep WiFi off / airplane mode engaged unless you are 100% sure the OTA block is working
- snag a copy of Flashify to install twrp and the 3.2.3 bootloader update
- check MD5 checksums with ES File Explorer or another tool before flashing; especially important for bootloader update!
- backup your existing recovery with Flashify before flashing twrp; leave a copy on the device
- enable USB debugging in Kindle settings (optional but offers additional recovery options should something go wrong)
- flash twrp first and make sure it works (reboot to recovery; have a look around but don't change anything)
- reboot FireOS and then use Flashify to update bootloader. Did I mention you should check MD5?
Post when above tasks are complete or if you have questions. Cover bootloader unlock next. Be aware the above steps carry some risk including permanently bricking the device. Make sure you have a clear understand on what is suppose to happen; double/triple check everything before committing changes. Good luck.
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
PariahNine said:
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Click to expand...
Click to collapse
- use the original apk to remove (uninstall) Safestrap v3 recovery; you do not need to uninstall the apk itself
- uninstalling Safestrap will not impact root
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
PariahNine said:
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
Click to expand...
Click to collapse
The FireOS version number will not change following bootloader update. It is a separate 'component' whose version can not be independently queried or verified. Typically the system (what you see, ie: FireOS) and bootloader are updated together and share the same version identifier. In this instance are only flashing the bookloader update as FireOS will soon be replaced by a different ROM. No need to update it and assume the associated risks.
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
PariahNine said:
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
Click to expand...
Click to collapse
Hum. Best handled by @draxie who developed 1-click. Generally pretty responsive to forum posts. If 1-click doesn't do it can always try the manual approach (a LOT more involved but not risky). Let's see what shakes out.
This is what I'm getting from the batch cmd window:
VirtualBox does not appear to be installed
Downloading 'https://www.virtualbox.org/wiki/Downloads' to 'C:\Users\Pariah\Down
loads\1-Click\1-Click\dwnlds'
Download complete.
Downloading 'http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-
104815-Win.exe' to 'C:\Users\Pariah\Downloads\1-Click\1-Click\VirtualBox-5.0.12-
104815-Win.exe'
Download complete.
Launching the VirtualBox installer momentarily
Please complete the installation with USB support enabled
Installation complete.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine '1-Click' is created and registered.
UUID: 6b44be97-c931-47a5-8eeb-b780f5783b78
Settings file: 'C:\Users\Pariah\VirtualBox VMs\1-Click\1-Click.vbox'
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xf
fffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\Syste
m32\acaptuser64.dll: None of the 1 path(s) have a trust anchor.: \Device\Harddis
kVolume2\Windows\System32\acaptuser64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\ac
aptuser64.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.
Click to expand...
Click to collapse
And the 1-click instance in Virtual Box is showing "Booting the kernel."
Here is the method I used to block OTA updates.
Originally Posted by berndt_toast
Yeah, I agree. Staying rooted is difficult, but doable. I am still on the rootable version (13.3.1.0) and have stayed on it even through the OTA updates that have been released. I have stopped them from auto-applying (and from even being seen as updates) by doing the following:
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
Doing those prevent OTA updates from working and if you check for updates from the device, it says none are found (at least it has worked for me).
Click to expand...
Click to collapse
Do I need to undo this before proceeding with the bootloader update and unlocking?
PariahNine said:
Here is the method I used to block OTA updates.
Do I need to undo this before proceeding with the bootloader update and unlocking?
Click to expand...
Click to collapse
No - tasks ahead have no dependence on Amazon's update engine.
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
PariahNine said:
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
EncryptedCurse said:
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
Click to expand...
Click to collapse
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Davey126 said:
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Click to expand...
Click to collapse
If you want to give manual unlocking a try:
- use these drivers; you likely need to reinstall when flipping between adb and fastboot
- detail procedure
- suggest browsing this thread for additional info/tips. Lots of noise but some diamonds in the rough too
- careful not to go down a rabbit hole; some solutions are one offs that worked great for the poster due to their familiarity with a particular too, platform or technique
- unlike almost everything else with HDX you can not harm your device with bootloader unlock attempts. It will either work or not with no adverse consequences either way
There are a few excellent posts by @Cl4ncy, @jerryl and others (possibly one of mine) in different threads; unfortunately I wasn't able to surface them in a quick search. Nature of the HDX forums. A gold mine if information that is a bxxtch to access.
Before diving in you may want to flash CM11 or Nexus v4 which can be done with a locked bootloader. Both are rock solid KitKat based roms that will expose the full capabilities of your device and offer continuity to CM13 once unlocked.
Good luck.
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
PariahNine said:
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
Click to expand...
Click to collapse
Happy to hear you were sucesfull. Thanks also for sharing your experiences and insights. Should be helpful to others as they navigate through the process. Every nugget of new information helps!

Kindle HDX Stuck in Boot Loop - TWRP and connection to PC working

Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Aldaris001 said:
Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Click to expand...
Click to collapse
TWRP or Safestrap (version)? They are not the same thing. Makes a big difference in the potential solution set.
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Aldaris001 said:
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Click to expand...
Click to collapse
Strongly recommend unlocking bootloader with 1-click utility (here). Otherwise you run the risk of permanently bricking your device if the recovery partition holding TWRP becomes damaged/unbootable. Once unlocked you can flash a modified build of FireOS 4.5.5 from here
Of course, once unlocked you could flash a higher version of Nexus, CM 11 (both KitKat based), CM 12.1 (Lollipop), CM 13 (Marshmallow) or several other rom variants. Each is a heck of a lot better than Stock FireOS v4.
At some point you should also consider moving to the latest version of TWRP (here).
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Aldaris001 said:
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Click to expand...
Click to collapse
Drivers are always a PiTA with Windows and Amazon devices. You'll need to fight through it taking clues from various posts on the topic. Some tips:
- nothing needs to be enabled in TWRP
- drivers need to work in both ADB and Fastboot modes
- cleanest approach IMO:
>> launch windows device manager, tether device, see what shows up in device manager, uninstall those device(s), disconnect, reboot both devices (important), reconnect and then guide windows to the drivers of your choosing
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Aldaris001 said:
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Click to expand...
Click to collapse
Thanks for the update. Glad you got things sorted; manual unlocking isn't that bad with a little patience. CM 12.1 is solid (probably my next stop; still rocking Nexus) but keep an eye on CM 13 as the dev team hammers out a few final issues. Enjoy your liberated HDX!

Trouble with the fast boot.

hello i am using fire hdx 3rd gen, I am on fire os 4.5.5.3, I am trying to install TWRP, i can do adb devices and find my device, when I use 'fastboot flash recovery twrp.img, the kindle restarts and goes to a screen showing fastboot ready, but I still see 'waiting for device' on my pc. Please help.
bluejaysrs said:
hello i am using fire hdx 3rd gen, I am on fire os 4.5.5.3, I am trying to install TWRP, i can do adb devices and find my device, when I use 'fastboot flash recovery twrp.img, the kindle restarts and goes to a screen showing fastboot ready, but I still see 'waiting for device' on my pc. Please help.
Click to expand...
Click to collapse
There are so many things unstated/wrong it's hard to know where to start.
- rooted?
- vulnerable aboot/bootloader installed?
- using twrp image w/forged signature?
- experience dealing with windows driver issues?
Transforming this Amazon device into a generic Android gizmo is technically challenging and not for the faint of heart. You'll need to so your homework (likely hours of reading) as no one here is going to handhold as you stumble through the basics.
Start here; follow suggested links:
https://forum.xda-developers.com/kindle-fire-hdx/help/bootloader-unlock-twrp-guides-t3802443
I recommend these drivers:
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
Davey126 said:
There are so many things unstated/wrong it's hard to know where to start.
- rooted?
- vulnerable aboot/bootloader installed?
- using twrp image w/forged signature?
- experience dealing with windows driver issues?
Transforming this Amazon device into a generic Android gizmo is technically challenging and not for the faint of heart. You'll need to so your homework (likely hours of reading) as no one here is going to handhold as you stumble through the basics.
Start here; follow suggested links:
https://forum.xda-developers.com/kindle-fire-hdx/help/bootloader-unlock-twrp-guides-t3802443
I recommend these drivers:
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
Click to expand...
Click to collapse
Thanks for guiding me through the required documentation. I have successfully followed the below link and did bootloader unlock and did get twrp and flashed a custom ROM, could you please guide me to any Oreo based custom ROM for my device? Thanks.
https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
bluejaysrs said:
Thanks for guiding me through the required documentation. I have successfully followed the below link and did bootloader unlock and did get twrp and flashed a custom ROM, could you please guide me to any Oreo based custom ROM for my device? Thanks.
https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Click to expand...
Click to collapse
Nougat only at present. My preference is AEX but many like Lineage. Can't go wrong with either choice.

Categories

Resources