yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] Plektrum:
confused noob

Hello,

Davey126 was kind enough to link me to this thread but I still just can't figure out how to proceed. I have read all the posts here and downloaded all the files and yet I have no idea what to do.

I own a Kindle Nexus HDX 7 (2013, 32 GB) and currently the Nexus Rom (Android 4.2.2) and Safetrap 3.75 (TWRP v2.7.1.0) are installed. Dave126 sent me 2 links - one to this thread, the other to Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox). However, as it is stated within the text of the second link that it "Does NOT work on Windows" I guess there is no use in following the instructions there. So I guess I have to follow the steps described in this thread. Do I have to uninstall Safetrap/the custom rom first? If so, how do I do that? I'm super sorry for being such a noob. Any kind of constructive feedback is welcome. Thanks a lot - also for making this thread in general. =)
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
I would like to help you out, but it would be better for Davey to answer where you should start from. I don't remember much about Safestrap and don't want you to get started off wrong. I may be able to help later on, if you need it. Wasn't there slots for a custom rom and Amazon stock? Do you have root access? Do you have adb access?

No matter where you start from, you can still get the necessary files organized, get adb and fastboot working and get the unlock code ready.
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
I briefly looked at the Safestrap thread and I don't see any reason to uninstall anything. Just start from where you are. Safestrap is just a modified twrp recovery image over which you will flash the latest twrp recovery image, so that shouldn't be a problem. Any slots you may have created and the modified boot image will be over written when you flash a custom rom after unlocking the bootloader. I don't see a problem there either.

Your biggest challenge will be to get adb and fastboot working correctly, should be fairly easy after that. Start with Task 1 and work through the other Tasks, skipping through those you don't need (should have root access already, if I understood the Safestrap thread correctly).
[Kindle Fire HDX 7" & 8.9" General] DB126:
Guidance is spot on. Just a minor clairification: Safestrap lives in the system and emulates TWRP - but isn't a true recovery. Stock recovery remains intact and can be invoked in the usual manner.

If FireOS remains in slot 0 SafeStrap can be uninstalled. However, there really isn't a need as bootloader unlock procedure is agnostic to currently installed ROM.
[Kindle Fire HDX 7" & 8.9" General] paoxayla:
first, thanks for the guide and for the time

i have a simple question, when i get to the adb command state, where it says ready after step 1, when i type anything including adb devices, it doesnt recognize any devices even tho it says ready

but if i run the "unlock" batch file in my adb folder i can see something happening in the hdx
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
I need more details before I can help you out. Step 1 is from where? Ready where? On your computer or the HDX? Are you sure adb and fastboot are working correctly? Have you replaced aboot and recovery before trying to unlock the bootloader ( i run the "unlock" batch file in my adb folder)? I have no idea where you are at in this process. Help me out a little. Lol.
[Kindle Fire HDX 7" & 8.9" General] player594:
When I run get_code.bat I get this in cmd

adb: error: failed to get feature set: no devices/emulators found

error: no devices/emulators found

error: no devices/emulators found

adb: error: failed to get feature set: no devices/emulators found

error: no devices/emulators found

Press any key to continue . . .

And if I open cmd and run >adb get_code I get a 7kb file named get_code in the adb folder with no text in cmd. The file has no ext what so ever.

Any ideas?
[Kindle Fire HDX 7" & 8.9" General] paoxayla:
sorry i didnt gave much details, i'll try to explain better what happened.

i followed exactly what it said in steps 1

i created a folder with files from "thor unlock files" and "adb and fastboot", using windows tool a started the cmd of this folder and the device was recognized using "adb devices" command(i also installed the drivers), after that i initiated fatboot mode but it didnt said "ready" on the device like it's supposed to be, than i updated the drivers like it said in the word file and the ready line was in the hdx device, everything good so far.

after that the device don't recognize any commands from cmd anymore, when i type "adb devices" it dosn't say anything basically, not even that the device is not recognized.

"Have you replaced aboot and recovery before trying to unlock the bootloader", maybe i missed this step, how should i do this? sorry

thanks for the help!
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
Still not sure where you are or doing. Will make some guesses. Task 1 was to get adb and fastboot working correctly. It appears that you accomplished that. You state the HDX is recognized when you issue the command adb devices. If the get_code.bat was issued while in adb mode it should get you the unlock.code. I assume in the previous post you were not in adb mode but perhaps fastboot mode.

adb commands only work in adb mode (and sometimes in recovery mode)

fastboot commands only work in fastboot mode

It appears you has accomplished Task 1 and 2. Have you rooted the HDX as per Task 3 or other means? I can only suggest you follow through each Task and not skip around. You look to be close, especially if adb and fastboot are working correctly.
[Kindle Fire HDX 7" & 8.9" General] player594:
Are you saying that the get_code should be done before going into fastboot mode or after? Because following the guide reads like doing it in fastboot mode.
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
I recommend you get the unlock code as soon as you have adb and fastboot working correctly on your computer. Now to confuse you some more perhaps.

C:\adb>adb devices

List of devices attached

D072A0A0347706B4 device

Indicates adb is working

C:\adb>get_code

cuber: 1 file pushed. 7.7 MB/s (506072 bytes in 0.062s)

/system/bin/sh: cat: /sys/class/block/mmcblk0/device/manfid: Permission denied

/system/bin/sh: cat: /sys/class/block/mmcblk0/device/serial: Permission denied

/data/local/tmp/unlock.code: 1 file pulled.

Press any key to continue . . .

Indicates the unlock.code file has been created and should be in the C:\adb> directory

Before doing this

C:\adb>unlock

you should have rooted the HDX and replaced the aboot and recovery partitions

I guess I didn't answer your question. Before. Run get_code in adb mode, it will not work in fastboot mode.
[Kindle Fire HDX 7" & 8.9" General] player594:
Ok I got the unlock.code now but I can't get it to root
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
Sorry about the last post, I thought I was answering someone else. The last sentence would have answered your question. I guess you should start with Task 1 and work through the rest of the Tasks. Best I can do for now as I have no way of knowing what you are doing or have done already.
[Kindle Fire HDX 7" & 8.9" General] player594:
I got it rooted the the bootloader unlocked. Twrp is installed. Now I'm stuck in fastboot.
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
In fastboot mode with it saying ready. in bright white on the HDX you can go directly to recovery mode

fastboot boot thor_3.2.3-1_recovery.img

replace thor_3.2.3-1_recovery.img with the applicable recovery image (thor or apollo) you used to replace the original recovery image that is in the same directory as fastboot.exe.

once in recovery you can follow Task 5 if need be to flash a custom rom
[Kindle Fire HDX 7" & 8.9" General] player594:
Ok I got lineage os flashed, gapps and rooted. Tnx for the help.
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
Awesome. It's good to know we are able to help some of you guys.
[Kindle Fire HDX 7" & 8.9" General] Frederisk:
Any plans for 4 Gen?

I noticed that 4 Gen is not supported due to some technical problems.

But I still want to consult, is there any plan or goal for 4 Gen? Will it be unlocked in the future?

Thanks.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Highly unlikely. No one is working on these EOL 2014 vintage gizmos.
[Kindle Fire HDX 7" & 8.9" General] RemusW:
Could Pie run on the Fire 7 HDX ?

Hi guys,

I have the fire 7 HDX 3rd gen. Great tablet but think it could easily run android Pie. I have built a few roms for my phones an am still learning how to build.

My question is before i expend a lot of wasted time trying to port Pie to the HDX is it even a possibility ? Obviously the device drivers and kernel will need to be updated.

I have a few ideas on the kernel perhaps use an updated kernel from a current Pie port from a device running Pie.

The drivers am not sure if they could be coaxed into running under Pie or if I'd need to also find updated drivers again from a Pie ported device.

Am I wasting my time even considering trying this ?

Any advice or feedback on this would be much appreciated so thanks in advance.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Please don't cross post in multiple threads within the same forum. Annoys the residents. Response here.
[Kindle Fire HDX 7" & 8.9" General] ludotaku:
Hi,

first of all, I wanted to say thanks as I have a fully working Android 7 on my "Apollo" tablet thanks to you. :)

I just wanted to add something to this tutorial as this was made for noobies like me. ^^

I actually got lost between ADB and fastboot modes and it was not really clear in your doc files but maybe it's because English is not my native language. However, player594 and I got the same problems.

So if ADB mode is needed, the tablet must show its regular OS screen whereas fastboot mode is only in boot mode when it shows "ready".

Actually, I thought that everyting could be done when the tablet was showing fastboot whereas it was not possible.

I spent hours trying to solve the "get_code" error (adb: error: failed to get feature set: no devices/emulators found...) because I was not at the right place at the right time.

Hope this helps. :)
[Kindle Fire HDX 7" & 8.9" General] jeffersonx:
I somehow missed the step with getting the "unlock.code" (my device was previously rooted). After executing unlock I am stuck in fastboot - how can I boot in normal system now and get unlock.code now?
[Kindle Fire HDX 7" & 8.9" General] gwardsc65:
Get the HDX in twrp recovery mode. Attach the HDX to your computer, run get_code.bat from your adb folder, then the unlock.bat file.
[Kindle Fire HDX 7" & 8.9" General] jeffersonx:
How can I do this? Now it always starts in fastboot
[Kindle Fire HDX 7" & 8.9" General] Reverse-anastomosis:
There's a lot of good info in the thread already.
[Kindle Fire HDX 7" & 8.9" General] jeffersonx:
I can not boot any image from fastboot because the bootloader is still locked
[Kindle Fire HDX 7" & 8.9" General] Reverse-anastomosis:
Sorry for my attitude last night....crying infant gets to a guy after a while.

OK, I have never used this method. I have always done draxies 1-click. I have read a lot of the threads on manual procedure, and thought I had seen a similar problem in another thread.

This is what I found

---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------

This is the thread where I found that info...its a big thread, but lots of good info there too.

https://xdaforums.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982/page115
[Kindle Fire HDX 7" & 8.9" General] DB126:
You did fine; didn't detect a hint of "attitude". Little ones (family) first and always.
[Kindle Fire HDX 7" & 8.9" General] Kakuncio:
So I'm also at this stage of being stuck on fastboot and recovery after following this guide, however I'm just trying to boot back to stock and not install a custom rom yet; just wanted root and an unlock the bootloader. I got the "Unlock code is correct" message without issues.

I'm unsure as to where do I obtain this so called "thor_3.2.3-1_recovery.img" file since it's not in the downloaded files. Is this what I need to boot back to stock?

I'm also understanding that the "applicable recovery image (thor or apollo) you used to replace the original recovery image that is in the same directory as fastboot.exe" refers to thor_twrp-3.2.3-1.img (which does come in the downloaded files).

Any advice on how to proceed? Thanks in advance!
[Kindle Fire HDX 7" & 8.9" General] DB126:
Assuming the bootloader is truly unlocked try flashing TWRP from this post via fastboot. if successful you can use adb/mtp from twrp to transfer the ROM of your choice to the device for installation. You might not be able to boot the previously installed build of FireOS as it may have been compromised/erased during the unlock procedure.
[Kindle Fire HDX 7" & 8.9" General] Kakuncio:
OK I understand now. I do have TWRP working fine so I'll go ahead and flash a ROM then, thank you for your time.
[Kindle Fire HDX 7" & 8.9" General] HDXnoob:
HDX not listed as an ADB Device

Hey Guys,

As my name implies, I'm a noob. I've read through the walkthrough a couple of times before committing. I'm stuck at a pretty early spot, and I feel a bit of an idiot:

I was able to get the ADB.exe going fine. Went through it's:

C:\> adb > adb devices

* daemon not running; starting now at tcp:5037

* daemon started successfully

But I can't for the life of me get it to the next step to read the device or SN#. It just keeps returning blank:

C:\> adb > adb devices

*blank line*

Notes on what I've already done below.

*Running CMD as admin.

*Installed the ADB USB drivers included in the Zip

*Enabled Developer Mode on HDX

*Clicked prompt on HDX that "allowed USB access" to my computer

Any help would be greatly appreciated! Thanks again.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Symptoms suggest driver issues on the host, although a bad usb cable/port can yield similar results. Troubleshooting:

- try a different USB port, direct connect (no hubs), preferably usb2

- if available try a few different cables; amazing how often this is the issue

- verify the installed USB drivers are being used when the device is plugged

I recommend Moto drivers for HDX devices which have proven reliable both with ADB and Fastboot communication. Simply install Moto device manager to get the drivers; you don't need to launch or use the accompanying app.

https://support.motorola.com/us/en/drivers

Also consider using the '1-click' method to unlock the bootloader:

https://xdaforums.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
[Kindle Fire HDX 7" & 8.9" General] itek:
I just wanted to say thanks to [MENTION=5035172]gwardsc65[/MENTION] for writing this guide up. I struggled my way through it and was eventually able to root a new-to-me HDX 7 and install Lineage 14.1. Not exactly the easiest process, but definitely doable following this guide. Much appreciated. :good:
[Kindle Fire HDX 7" & 8.9" General] HDXnoob:
Thanks for the help, DB! 1-click seems badass, unfortunately my host machine is Windows :(

I've tried using a different port. . . . Same result. Interestingly, I can get it into fastboot using the console commands, so it's for sure communicating with the device (just not sure if it's using ADB protocol or whatever). Also, when I look in the device manager I show that Fire Devices > Android Composite ADB Interface is listed (and seemingly functioning correctly). I should have another micro USB laying around somewhere to try as well. . . .

There's another thing that I think is worth mentioning. . . . There's another device in device manager listed under Portable Devices > Fire. It appears that that device is utilizing a Microsoft driver. Maybe that's taking precedence over the ADB Driver and not allowing it communicate? I could totally be wrong--just spit balling!
[Kindle Fire HDX 7" & 8.9" General] DB126:
ADB and fastboot utilize different protocols. A cable or port issue is less likely given fastboot (bootloader) communication works.

Be sure to install the previously suggested drivers (via Moto Device Manager) and manually reselect "ADB Composite..." in Windows device manager after connecting device if necessary. Also insure you have the latest ADB/Fastboot toolset; link below.

https://xdaforums.com/showthread.php?t=2317790

Device should be unlocked and USB debugging enabled when communicating via ADB.

Note: A bad cable could still be the culprit; only priorities in the troubleshooting sequence change based on latest info.
[Kindle Fire HDX 7" & 8.9" General] HDXnoob:
Thanks, DB! With your help, I got it to work! Flashing my first custom ROM *woot* :good:

For other noobs out there, please see DBs responses above. I found his links for ADB / Fastboot Console to be winners + using the Moto ADB drivers instead.

Step 5 was a bit confusing for a noob, so here are a couple of links that helped me navigate the process a bit better:

This link discusses the benefits of AOSP Extended and a couple of helpful steps.

Make sure to take note of GAPPS. *When choosing which version of GAPPS, I went with what was in the guide pen_gapps-arm-7.1-pico*:

https://xdaforums.com/kindle-fire-hdx/help/whats-best-stable-custom-rom-fire-7-hdx-t3721422

This link discusses the general steps (with pictures) of the flashing process:

https://www.getdroidtips.com/install-custom-rom-using-twrp-recovery/

Not talking smack by any means on the OP and creator of this guide, just a couple of extra noob-friendly tips from one noob to another! Thanks again folks! My old HDX has a new breath of life :)
[Kindle Fire HDX 7" & 8.9" General] DB126:
Congrats on making it through the manual unlock procedure! It's a tough hoe for some but lots of helpful tips archived in the HDX forums to help with the rough patches. Unfortunately, most of the past contributors have moved on to other devices...as have I. Still enjoy the HDX form factor but it's no longer my daily driver.

Note Lineage is the only custom ROM for 3rd gen HDX devices that receives semi-regular updates. My fav was AEX but over time glitches emerged that pushed me over to LOS. Don't recall the details; likely documented in the AEX thread.

Enjoy your rejuvenated device!
[Kindle Fire HDX 7" & 8.9" General] HDXnoob:
Thank you, sir! I plan on just making this a little "on-the-go" SNES emulator; no heavy lifting for this dino. Thanks again for the help and the tip on Lineage. You rock dude :cool:
[Kindle Fire HDX 7" & 8.9" General] RoyaLFlesH:
Hello All,

Thank you for the helpful information. I am attempting to root my apollo. I have completed all until the end of task 3. I can successfully enter shell mode, but when requesting to initiate root it returns "/system/bin/sh: su: not found." However, other shell commands work (i.e. du, date, ls). Any thoughts on what the issue might be?

I am assuming I have to push the su commands to my apollo as that is why it cannot initiate root, but that was not in the provided step by step. Unless, there is something I am missing. Was there a file provide in the everything zip file? Please advise.

Thanks much.
[Kindle Fire HDX 7" & 8.9" General] thomsalter:
Thank you very much, worked a treat!
[Kindle Fire HDX 7" & 8.9" General] HDXnoob:
Sorry for the late response!

It sounds like you were not successful in rooting your device. Please note that KingRoot doesn't always work the 1st time you run it, it took me like 6 tries using KingRoot to successfully get root access to my device. As it notes in the guide:

"

testing for root

C:\adb>adb shell

thor:/ $ su

you needed to type su after the $ sign above to get this:

thor:/ #

# indicates root waiting for instructions

"

If you don't receive the above message, you don't have root access. Run KingRoot again until you receive a "Root successful" message.
[Kindle Fire HDX 7" & 8.9" General] burnface:
Hey all!

I started this this morning after being denied a link for the one-click due to my avatar :D

It's been going well for the most part, but I'm a little stuck I think. I completed task 4, and was able to get into TWRP, but if I try to restart from there, it just goes back to bootloader. Sometimes it says "ready", other times I have to fix drivers again. I've tried doing

fastboot reboot

and

fastboot reboot recovery

, but the both go back to bootloader/fastboot.

I flashed the TWRP image again and it went back to recovery after that, but if I try restart from there, it's back to bootloader/fastboot again.

Should I do that to get into recovery again and try install a ROM?

(this is on a gen 3 8.9" HDX btw)

Thanks!

Shaun

[edit] Actually, might be working now... update coming shortly..

[edit 2] It's working!
[Kindle Fire HDX 7" & 8.9" General] duskwind:
After overcoming a couple of hurdles I managed to successfully root my HDX 7 and flash Lineage 14.1

The guide is really great, but there are a couple of things that were not immediatly obvious to me.

Task 1:

The content of [adb_AND_fastboot] is to be copied into a new [adb] folder on C:/

[kindle_fire_usb_drivers] are to be installed.

After checking adb and fastboot communication: Exit from Fastboot via pressing the Power button for 20s. get_code (from Task 2) is ans adb command and does not work while Fastboot is active ( Fastboot Ready signal on Fire screen)

Task 4 (after successful Root):

type/paste after #:

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

NOT:

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

Before adb command 'unlock':

"exit back to c:\ prompt" means closing and reopening the command window.

These may be obvious to some. But I don't do these kind of things regularly and English is also not my native tongue...

After I figured these points out, everything else worked like a charm!

PS: Power Button and +Volume Button doesn't work on my device, but it is possible to enable Extended Restart Menu in Lineage OS under Developer Options. Afterwards Recovery can be started with just the Power Button.
[Kindle Fire HDX 7" & 8.9" General] schwinn8:
Finally got around to rooting/unlocking our ancient apollo. The instructions were very good, though part of it is because I am familiar with many of these steps having rooted various phones and devices before. Still, it was AWESOME to have everything in one place, as you have done, so thank you!

Note, I apparently had rooted my device before using towelroot... so while I followed the Kingroot instructions, it didn't succeed... but I saw I had SU installed so I was all set. Is there anything I need to do to completely uninstall KingRoot?

Now that the device is ready for a ROM, which ones are recommended. I don't need anything super fancy or super new, but I do want something STABLE. Any recommendations?
[Kindle Fire HDX 7" & 8.9" General] DB126:
- Kingroot remnants will be eraticated with the installation of a custom ROM

- Only one custom ROM in play: Lineage 14.1
[Kindle Fire HDX 7" & 8.9" General] schwinn8:
What if I don't install a custom ROM? How do I ensure I got rid of all of Kingroot?

Only option is Lin 14.1? There's no older option that may be more stable, but less updated? I don't need something "new".

Or, better yet, is Lin 14.1 stable these days, or are there missing features and capabilities? The thread seems to say there are rotation issues, Wifi issues, and BT issues... that's a lot of instability isn't it? That's why I don't mind being on an older release if these types of things are not present, you know?