yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Android Development] thuyrs:
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!

One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Can you get into Safestrap recovery? If so try a 'factory reset' located under the 'wipe' option and then reboot. If that does not work return to Safestrap recovery and perform an 'advanced wipe'. Check all of the partitions (Dalvik Cache, Data, Cache, System). After wiping reinstall Nexus v4 and gaps from within Safestrap and then reboot.

A few cautions/notes:

- make sure you are working with the correct slot!

- make sure you perform the 'factory reset' from safestrap recovery - not the native Amazon recovery built into your Kindle

- gaps is important for proper operation of Nexus v4. Some low level functions (eg: the home button) do not work correctly if gaps is not flashed immediately after Nexus v4

Please post the results to others can learn from your experience. Thanks!
[Kindle Fire HDX 7" & 8.9" Android Development] thuyrs:
Hi, after I wiped everything and reinstall to slot stock, it booted, and Wifi module worked correctly, thanks for your help!
[Kindle Fire HDX 7" & 8.9" Android Development] loco09:
hi

does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?

thx
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
Flash SuperSU after and you have root access.

Also you will need to block ota updates so do not enable WiFi until you have done so.

EDIT: I have just added a note to the OP about this.
[Kindle Fire HDX 7" & 8.9" Android Development] skeptic1007:
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).

Options as follows:

1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.

2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).

3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.

I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
Just to add to what Davey126. My current understanding is that a manual upgrade does indeed work. 3.2.8 only stops the OTA updates from coming through.
[Kindle Fire HDX 7" & 8.9" Android Development] ChuTeng:
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help :(
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
Can you still get into Safestrap?
[Kindle Fire HDX 7" & 8.9" Android Development] ChuTeng:
adb driver in my computer is problem, i fixed. Thanks.
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
Does that mean you are up and running again?
[Kindle Fire HDX 7" & 8.9" Android Development] Oh_wow:
Awesome job!!!!!!!!!!

Confirmation number: 67M75398MF9375820
[Kindle Fire HDX 7" & 8.9" Android Development] mrw187:
I'm on 4.5.4 7", any options for me? Can I contact amazon n hope they will roll me back? What version do I ask for?
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
Thanks for clearing up those things. :D

The reason I mentioned the unlocked bootloader was the requirement of the Nexus ROM though, not TWRP itself. ;)
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
Thanks guys appreciate all the help, few additional questions:

Do I create a partition using TWRP and then install on the partition or just install on the Fire OS drive overwriting Fire? If the latter then is Fire all gone and full reliance to be placed in the Nexus?

Does the Nexus OS auto update like Fire?‎

Once the Nexus iss installed then can updates to it be directly installed from Android or must updates always be made vis flashing ROMS that have been adapted to the Fire?

Thanks again‎
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
- Nexus is flashed to system/stock partition when using Safestrap v4 (don't create any secondary slots)

- Nexus overwrites the user accessible components of FireOS v4 effectively overwriting the OS

- Nexus does not auto-update; all updates must be flashed from Safestrap recovery (or twrp if using Nexus with an unlocked bootloader)
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
If you use TWRP it will use the existing Partition, i.e. Fire OS will be gone (you should backup the Fire OS from TWRP and copy it to your PC to be safe here, so you can restore it if required).

I don't think there's an auto update feature, and you must use the Nexus ROMs available here, created for the HDX of course.

So after the info given by Davey126 you should install TWRP, create a backup, copy it to your PC, then update to 3.2.3.2, then unlock your bootloader, may be do another backup of 3.2.3.2, and finally install Nexus - hope I got that right. ;)

If in doubt, ask first, before you brick your HDX.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Excellent recommendation from [MENTION=6815340]Cl4ncy[/MENTION] to backup FireOS from TWRP before flashing Nexus or any other rom! Restoring FireOS v3 can be challenging without a full nandroid image which is easily created in TWRP.
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
Davey and clancy thanks so much. Will follow the steps you've outlined.

Clancy thanks for the tip to backup the fireos as I was just going to ask if there is anyway I can do that.

On my PC when I've run into issues I've just formatted HD and done a fresh install of an oc, whether that be linux or windows and so long as I've had the relevant drivers it's worked without having to tweak the os for the PC isn't there a way of doing something similar with the tablets? Just format and install a stock android?

How regularly are ROM updates released? Just thinking if major changes are made to the nexus/android os that require thhe update to be installed to run apps, what's the liklihood that a rom will be released/ongoing for the fire hdx? Don't want to be in a situ where can no longer us as apps require an os which no rom is available for....or in such cases is to go back to fire os using the backed up rom?

Thanks

---------- Post added at 04:14 PM ---------- Previous post was at 04:08 PM ----------

PS sorry for all the typos, sending from my phone
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Short answers:

- With an unlocked bootloader you can do just about anything but the complexity level varies depending on task. Not sure anyone really knows how much can be accomplished via fastboot on an HDX as Amazon neutered the environment. Twrp offers a fairly robust mechanism for overwriting partitions. That should suffice for most needs.

- No major worries about the legs on Nexus or CMxx given the broad support community. Your device will become obsolete before the roms.
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
thanks gents

ive downloaded the thor bootloader and the nexus rom - both are zipped. when i copy them to the sd card folder on the hdx should i do so in the zipped state or extract all the files? will twrp be able to read them in the zipped state~?

thanks

---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------

also how do i unlock the bootloader please? is this a relatively straightforward procedure from within twrp?

thank you
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Leave them zipped. TWRP works with zips and image archives. Bootloader unlocking is a different topic (difficulty depends on skill level) and is not done within TWRP.
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
bit stuck.

ive rooted the device and have all the files downloaded but i dont know how to get the twrp onto the device..any pointers please? does it need to go into the /sdcard directory and if so how do i get access to this directory to move things into it?

also can you please point me to a link that details how to unlock bootloader after i have 3.2.3.2 installed and prior to nexus rom flash

thanks
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Assuming all prerequisites are met (rooted FireOS v3.1.0-3.2.3) use Flashify or adb to install TWRP. Be very careful with these tools; they will do exactly as you ask. Note TWRP gets flashed to the recovery partition, not system. Recommend you use Flashify as it supports backing up your existing recovery before flashing TWRP. Can come in handy if things go wrong. Also recommend you verify MD5 on the the downloaded TWRP image using Hash Droid or similar tool. Flashing a bad recovery can ruin your day.

All future flashes should be done from within TWRP (although you can also use Flashify for most). Be sure to take a backup of FireOS and copy to another device before flashing Nexus.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
4120 vs 4220

I have seen several posts suggesting Safestrap v4 can not be used with FireOS 4.5.2 versions ending in 4220 (eg: 13.4.5.2_user_452004220). Can anyone definitively confirm? 4220 seems to work fine for me but my bootloader is unlocked which is not the typical usage scenario.

I'd like to substantiate or kill this rumor as it is proving to be a distraction. Thanks for your thoughts.
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
First you must have USB debugging enabled on your HDX.

You should download the minimal ADB and Fastboot here, install to e.g. c:\ADB - so you've to enter shorter commands in the DOS box/command prompt later.

I've no experience with Flashify, so I'd prefer the ADB Installation mentioned in the TWRP thread, but it's your choice.

Bootloader unlock procedure is described here. Basically you install the software mentioned (again preferable to root c:\ and not to the program files directory), then open a DOS box, change Directory (cd) to the ADB directory, and enter the commands to get the ID and serial numbers, then open another DOS box and go to the Python directory to use the script you should've downloaded by then with the ID and serial you got from your HDX, it will create the .UNLOCK file, which you copy to the ADB directory, then open another DOS box for fastboot commands (is in the ADB directory, too, but the DOS box with ADB commands is "blocked" by ADB), then enter the ADB command reboot bootloader (in the ADB prompt), and in the Fastboot prompt enter the devices, flash unlock, and reboot commands as mentioned. If you get stuck at the Fastboot prompt with "Waiting for device" and "Ready" on the HDX you have to install the correct ADB drivers, check device manager, the HDX is probably there with a yellow exclamation mark then.
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
Please could you confirm if the twrp img has to be pushed to the recovery partition or sdcard?

I was under the impression that it had to be to the recovery and as I had no idea what the recovery partition was called sideloaded es explorer using adb to try identify it but unfortunately there is no folder called recovery nor do I see a seperate partition called recovery in the root partition! I was going to enclose a screenshot but appears being. A new usr I don't have such privileges yet Thank-you
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
There are two steps that you may be confusing:

#1 Copy (or download) the twrp img file to you Kindle. It can go in any folder. I suggest 'downloads' but the choice is yours.

#2 Install (flash) the image file using either of the methods discussed in previous posts. You need to tell the tool (adb or Flashify) where to find the img to flash (folder in prior step). I like Flashify as it offers a friendly UI and does not require a tether and the associated prerequisites. But the OP recommends ADB commands as does [MENTION=6815340]Cl4ncy[/MENTION] and many others. In the end they both get the job done. Your choice.

You can't 'see' your device's partitions using ES File Explorer or similar tools. Those are only exposed after installing a tool like TWRP or via adb commands (no need to get into those here as you should never mess with partitions).

Hope this helps!

p.s. If unsure don't flash anything! Keep asking questions until you are comfortable. [MENTION=6815340]Cl4ncy[/MENTION], myself or other forum participants are happy to help.
[Kindle Fire HDX 7" & 8.9" Android Development] johim:
Hey,

Im thinking of upgrading my hdx 7 to hdx 8.9 lte. I was wondering if it came with latest firmware, could i do something about it to install safetrap 4? I assume the 3.2.8 image will work, but i wasnt sure about the lte part. What about lte support - Does it work with cm or nexus rom? On a side note, does the hdx device have a sim slot or something?

Any ideas?

BTW, just noticed that there are two HDX gens (apollo gen3 and, not sure if I'm wrong saturn gen4). I assume the only way to tell the difference is the cpu/gpu types?
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
- If you manage to get a brand new 3rd Gen device from amazon then it should come with old firmware which will allow you to unlock the bootloader.

- 4th gen I'm not sure about.

- cpu/gpu type is a good way to tell.

- Nexus ROM v4.0.3 will work with LTE

- CM-11 for Safestrap already has LTE support
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
If you want to use the ADB flash the TWRP img must be copied to the root of the sdcard, as it's mentioned in the TWRP thread, i.e. if you connect your HDX to your PC you just select the HDX and copy it right to that (root) directory, don't open any other directory. So the img will be on the sdcard, and the flash command will flash it to the recovery partition then.

Otherwise you have to correct the path to the directory where the TWRP img is stored, but why make it even more complicated? ;)

Do you want to use ADB flash method or Flashify?
[Kindle Fire HDX 7" & 8.9" Android Development] johim:
Unfortunately brand new device not always means older firmware - I've already confirmed this with amazon during my battle for downgrade on my HDX 7. They periodically boot they devices and upgrade them.

BTW, todays deal of the day (co.uk site) for 3rd gen, 32GB with LTE is very tempting - 140 GBP if anyone is interested.

Do you know if the hdx has a sim slot or something? Can I use a simple HSPDA+ data simcard with it?
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
davey and clancy, thanks for all the help so far. ive flashed twrp, backed up, upgraded to 3.2.3.2 (had to re root and reflash twrp after this - didnt think id have to) and now trying to get the device recognised in fastboot mode by the comp so that i can go through the unlock bootloader procedure using python before backing up again and then doing the final upgrade to nexus.

will let you know how i get on, thanks again, much appreciate your kindness

---------- Post added at 06:21 PM ---------- Previous post was at 06:09 PM ----------

ps. i used adb with the commands on the twrp thread
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
Thanks for the infos. So may be the suggestion should be to install 3.2.3.2 first, root, and install TWRP then, if the 3.2.3.2 update removes TWRP. I'm not sure why this happened. I installed TWRP with 3.2.3.2 installed on my Thor device though.
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
if this removal of twrp by 3.2.3.2 was not an isolated case then yes i think like you say teh suggestion would be to move to 3.2.3.2 before root and twrp. however saying that to err on the side of caution by backing up 3.1.0 seems sensible - rooting and flashing twrp isnt that much effort once an individual knows what theyre doing
[Kindle Fire HDX 7" & 8.9" Android Development] jeryll:
The thing is, if you let FireOS handle the update, recovery will be updated/owerwrited in the process, so TWRP gets overwrited, you on the other hand, having flashed TWRP can use it to update required bootloader etc. by flashing 3.2.3.2 amazon.bin update file renamed to zip - and this will preserve TWRP so you don't have to flash it twice...
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
clancy/davey still trying to get the fastboot working., what are the key advantages of unlocking the bootloader? can it be done after the nexus rom is installed? will it be locked again after nexus is installed?

thanks
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Yup - once installed TWRP it should be the go-to choice for all future flashes. Specific to 3.2.3.2, if you used the customer version from here then it should have only updated the bootloader (as noted in the OP) not the other partitions.
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
What exactly is the problem? Did you install the correct drivers? Check device manager, is the HDX there with a yellow exclamation mark?

The advantages are basically to be able to use a wide range of available ROMs, you can NOT use with a locked bootloader.

Nexus Installation will leave the bootloader unlocked, only the Installation of an official Amazon ROM would lock it again, you should NOT do that anyway.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Unlocking your bootloader permits flashing unsigned images to your device. It also offers more robust recovery capability should should something go wrong and you loose access to the recovery partition. In the case of Nexus, v2 binaries are signed so the rom can be flashed onto a device with a locked bootloader. Nexus v4 (and most HDX compatable versions of CM 11/12) binaries are unsigned which means you either have to unlock the device bootloader or use an emulator such as Safestrap.

Try this:

- Tether your device and remove (uninstall) all related devices in Window device manager. Look for an ADB entry near the top of the list and/or "Kindle" under portable devices. Then power down your HDX.

- Reboot windows and allow it to stabilize

- Enter fastboot mode on your HDX by pressing power + vol-down together. You should end up at a fastboot ready prompt

- Retether your device. Once Windows gets done installing drivers issue the following command from a Windows command prompt (you generally need to be in the same folder where adb is installed):

"fastboot -i 0x1949 devices"​

If working your device ID will be returned. If not then you will need to install additional drivers on the Windows side. What version of Windows? 32 or 64 bit? Win 8.1 64-bit presents some unique challenges which I can get into if you are using that environment.

Additional info here (expand thread to see related posts). It can be a frustrating experience as Windows will sometimes refuse to connect even with the proper drivers. A reboot often needed. The good news is once you unlock your bootloader there will rarely be a need to access Fastboot. It's a one-and-done deal. :)

---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------

Dang! Now I owe [MENTION=6815340]Cl4ncy[/MENTION] a cup of java. lol!

---------- Post added at 04:04 PM ---------- Previous post was at 03:32 PM ----------

If you get a 4 gen (faster cpu) hdx 8.9 then there's not much you can do with alternative firmware until a root exploit is found for whatever version of FireOS your device happens to be on. Saturn (4th gen) devices can not be rolled back even if rooted. At present Safestrap does not work with Saturn but a compatible version is planned (timing TDB).

Your best best is to seek out a 3rd gen Apollo, ideally with FireOS 3.2.6 or below which can be fully exploited (bootloader unlocked). Otherwise gen 3 w/FireOS 4.5.2 or below.
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
Davey/Clancy thanks for the tips. Issue is (as Davey alluded to) that windows is just not recognising the device at the fastboot ready stage. I thought it was due to lack of correct drivers so I downloaded the madb and 15 second adb/fastboot packages but these didn't fix the issue. I then resorted to downloading the android sdk kit to get a full installation to ensure all appropriate drivers were installed but this hasn't helped either. I get kindle with an exclamation mark but then the exclamation mark dissapears and the device gets recognised. I get a 'fastboot device' in device manager aswell this has an exclamation mark next to it which does not go.

I'm going to continue trying as it seems from daveys post that getting windows to recognise it at the fastboot ready prompt is a case of trial and error with a bit of luck thrown in!
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
You should not need the full sdk although it is admirable you went that route. If you have not done so already try the driver package from the post I previously linked as many have had good luck with it. Also note Win 8.1 x64 will block unsigned drivers (you'll get a message). There are workarounds to that which you may already know.

Also try a different cable. Amazing how many times that fixes connection errors. I have had variable luck with the cables that come with HDX devices. Some work well and have survived the test of time. Others are only good for charging. Amazon must use different suppliers and/or quality control is lacking.

Other options:

- try a different windows host (perhaps a friend's machine)

- Linux connects easily; it may be worth standing up a virtual machine if you can't get Windows to work
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
thanks Davey. Will try switching cables and windows hosts to see if that makes a diff. If not then il have access to a linux machine at the weekend and I'll just use that instead. To answer q's in your original post I'm using 32 bit windows 7. Wish me luck!
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
Did you try these drivers? IIRC those were the ones which worked for me. I unlocked with Win 7 x64 though.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
FYI - same drivers that worked for me (and many others).
[Kindle Fire HDX 7" & 8.9" Android Development] Tapeinos:
yep those are the drivers i have installed and the android adb interface shos up in device manager but the device is still not recognised at the ready prompt in fastboot mode. i think ive tried all the combos i can with this windows 7 32 bit device so im just going to wait until the weekend now when i have access to a diff windows machine - 64 bit - and also linux.

appreciate all your assistance so far gents. thankyou