yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Android Development] hoobyjuice:
ah double poo. well looks like i got an expensive paperweight.
[Kindle Fire HDX 7" & 8.9" Android Development] spoondoom:
I think I misinterpreted your instructions.

I thought the Safestrap flashable stock roms in your first post were to get the stock OS to the correct version to install the new Safestrap, consequently I flashed it on the old version of Safestrap.

Now all I get is the grey Kindle Fire logo.

Is there anything at all I can do from this point?

---------- Post added at 01:54 PM ---------- Previous post was at 01:31 PM ----------

I can get into a recovery screen by holding the power and volume up buttons for a while. There I get the options "Reboot your Kindle" returns me to grey logo loop) and "Reset to Factory Defaults" (haven't tried it because i think it might make it worse).
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
At this point Rest to Factory Defaults is your only choice. But It probably won't help as your device is now rocking two different versions of FireOS which were never meant to play in the same sandbox. Amazon's factory reset is limited in scope and assumes the 'core' of your device remains in a known state ... which it is not.

Sorry this happed. For others who find this post: Ask questions BEFORE FLASHING if not 100% certain of the prerequisites, procedure and outcome (including recovery options if things go bad). This applies to both native twrp and Safestrap which offers no real protection against incompatible overwrites. A rooted device is at the mercy of it's owner.
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
Unfortunately, the amazon stock recovery (ironically) has no features for recovering the system.

I think if your stuck at the grey logo or looping then you have no options left - sorry.
[Kindle Fire HDX 7" & 8.9" Android Development] loco09:
hi

i try to install the 4.5.2 stock which is posted on first page.

now i get only the kindle fire boot screen but nothing happens.

also the safestrap recovrey doesnt appear anymore.

is it bricked???? :crying:
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Your choices are:

1) unlock the bootloader and gain access to a wide variety of HDX compatible roms including three flavors of KitKat, two Lollipop and one Marshmallow

2) allow device to upgrade to FireOS 4.5.5.1, install Safestrap v4 and be limited to a couple KitKat roms (which aren't bad...newer isn't always better).

The first option requires more effort and technical expertise. The second is easier yet still yields a highly serviceable device that is far superior to what you have now. FWIW - I still use a KitKat rom on this device (Nexus) despite having the ability any of the other variants.

There is copious (albeit disorganized) documentation throughout the forum for the first choice; not going to rewrite what has already been said. For the second option you simply need to reenable OTA and allow your device to automatically update to FireOS 4.5.5.1. It's pretty brainless and relatively low risk - but may take several days to complete as some updates are incremental.

Good luck.
[Kindle Fire HDX 7" & 8.9" Android Development] sandman512:
Ok, so I am trying to install this on a 3rd. Generation Kindle Fire. The device is rooted and I installed Safestrap. Just attempted to boot into recovery as to flash my ROM(CM) and it looks like it is stuck at the KINDLE FIRE boot screen. Any thoughts? Thanks!

EDIT: It just reboots to the home screen.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
So it behaves as if Safestrap v4 is not installed? Did you install Safestrap recovery after installing/launching the Safestrap app?
[Kindle Fire HDX 7" & 8.9" Android Development] sandman512:
It seems so, I downloaded the file, installed it. When I hit boot into recovery, it boots to the home screen. The device is rooted. Thanks!
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Try removing recovery and then reinstalling from within Safestrap app. Also verify device status with a root checker app (like this one). If all appears well you may have a device that simply refuses to run Safestrap v4. Not common by any means but there have been a few. Likely due to damaged/missing FireOS components.
[Kindle Fire HDX 7" & 8.9" Android Development] sandman512:
Ok, Used root checker basic, all good.

Did exactly what you said, uninstalled it, then reinstalled it from the app, no luck:(.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Baring another suggestion your best option IMO is to rollback FireOS to 3.2.8, upgrade to 4.5.2 (manual process) then allow your device to OTA back to 4.5.5.1. That will insure a clean FireOS v4 install and likely resolve the Safestrap launch on boot issue. However, this path is not without risk including the potential for a hard brick with no possible recovery. Give it some thought. I do not have time to detail the process now although it is documented elsewhere in the forum.
[Kindle Fire HDX 7" & 8.9" Android Development] sandman512:
I live on the edge, if I can find how to accomplish this, I will give it a shot. If you have the time to link me to it, I would appreciate it. Thanks!
[Kindle Fire HDX 7" & 8.9" Android Development] zxcv888:
The OP did said

"- You must be on FireOS stock firmware 4.5.2, 4.5.3, 4.5.4, 4.5.5 or 4.5.5.1 <- Please confirm this before proceeding <-"

but, Can I install this Safestrap *again* after installing nexus rom 4.0.5?
[Kindle Fire HDX 7" & 8.9" Android Development] sandman512:
[MENTION=3544649]zxcv888[/MENTION], if that was aimed for me, yes, I am on 4.5.5.1.

Thanks!

---------- Post added at 07:50 PM ---------- Previous post was at 06:58 PM ----------

@Davey, my kindle is already rooted via Kingroot, would that make a difference? Can I unroot? Thanks!
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Don't understand the question. Unless your device is unlocked Safestrap v4 recovery must be installed/operational to run HDX Nexus 4.0.5 or Fire Nexus ROM.

---------- Post added at 11:43 PM ---------- Previous post was at 11:42 PM ----------

Must be rooted to install Safestrap.
[Kindle Fire HDX 7" & 8.9" Android Development] sandman512:
Davey,

Ok, so I am rooted, can't install Safestrap. FWIW, I am rooted via Kingroot. Also, cannot roll back to an older Fire OS version. Getting error message for that. Any other advice. Thanks!
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Things are not as bad as they seem! Quick responses:

- The "despondent robot" and "Safestrap is DISABLED" message are both expected an normal. It will remain this way with Safestrap v4 even after flashing CM11. I'll dispense with the explanation for now; just know it's OK.

- Rolling back to 3.2.8 followed by a 4.5.2 upgrade is risky and should be considered a last resort option. It is also not the best long term path as newer rom builds assume a 4.5.5.1 foundation.

- You don't need to be mounting volumes or doing other advanced tasks in Safestrap v4 recovery. The most important options to flash a rom are 'install', 'backup' and 'wipe'. Can you access any of these? If not what happens?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
{see previous post for details}

Yes - it's interesting looking around. That said, don't mess with anything (especially fixes and partition management) other that what is required to get the job done. Which in your case is flashing a custom rom. Tinkering with the other options is inviting a brick. Two things to keep in mind:

- Safestrap is not a true recovery environment; it is a twrp emulator that lives on top of locked down device with limited recovery capability

- Kindles in general and HDX models in particular are easy to trash and nearly impossible to recover. Safestrap will not protect your device from being rendered unbootable nor provide a path to recovery

Based on your early findings I believe your device is not fully rooted. Many believe root access is binary which might be true at some level but not always from a user/app perspective depending on which root manager is installed. I suspect you still have Kingroot manager and associated bloat on your device. Super-sume will remove that and install SuperSU which is the preferred root manager. See this video (or this video) for details which also has links to the associated XDA forum. Downside is the app MUST be purchased/installed from the Play Store which you likely don't have installed on your device. Catch 22.

The other option is to unroot using the KingUser app, reboot and then root again using the desktop version of Kingroot which sometimes does a better job vs the stand alone apk. Also possible a second root attempt will clear up the problem.

Regardless of which route you take be sure to uninstall Safestrap v4 recovery (double/triple check) and reboot your device before attempting further action. If you see the Safestrap robot the recovery component is still installed.

Also, make sure you downloaded the correct Safestrap v4 apk (there are separate versions for Apollo and Thor) and validate the MD5 before installing. You initial post suggested the correct file was downloaded but it never hurts to double check.
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
Understood

I will go this route and report status. I did see several references to Super-sume in the forums, and I have it downloaded to my PC ... Supersu-me-v6.7.apk ... So, I will uninstall recovery within Safestrap and then uninstall Safestrap itself before then running Supersu-me, removing KingRoot and associated bloatage.

If (when?) I am successful and still have root, I'll re-download Safestrap and verify MD5, reinstall Safestrap and recovery ... and give it another go.

I should have something new to post here shortly.

** and yes I was careful to be sure I had the Apollo versions of downloads wherever there were multiple versions provided; I did not (however) verify the MD5 hashes despite explicit advice to do so ... I just hope my laziness isn't the cause of all my pain LOL.

Thanks again!

---------- Post added at 07:51 PM ---------- Previous post was at 07:25 PM ----------

UPDATE ...

I was able to remove recovery from within Safestrap, no issues. I was also able to uninstall Safestrap using ES System Mgr ... rebooted using the long-hold power button method (40 second hold isn't it?) Anyway, I'm back into FireOS and am about to re-download Supersu-me and verify distribution MD5 ... then install.

One thing, I have encryption enabled ... that wouldn't be an issue would it? From what I can tell I'd have to do a factory reset from device to remove encryption and I've read a LOT of postings which explicitly warn against factory resets post root ... device death ... brickage ... bad mojo.

I'll proceed with the prescribed steps to re-root with Supersu-me and see where I land ... thanks.

---------- Post added at 08:07 PM ---------- Previous post was at 07:51 PM ----------

UPDATE 2 ...

I have replaced KingRoot with Supersu-me ... and I have re-verified root access post install. It did NOT prompt me to update binaries which I thought was odd. However, within the Supersu-me app settings it says I could upgrade to PRO ... I'm currently using SuperSU Free v2.46.

Questions:

Do I have to be on Pro to continue with installing Safestrap and then flashing a custom ROM?

I'll need to figure out how to do that without Google Play store if so.​

Should I choose to "Enable su during boot" from within settings?

Should I choose to "Install SuperSU into /system" from within settings?

Should I choose to "Trust superuser app" from within settings?

I know these are probably noobish questions ... but maybe there are others out there wondering the same thing and this info could help them too.

Thanks again!
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Possible - I have no experience with FireOS encryption and whether Safestrap v4 dependencies involve low-level components that may be encrypted. If so you'll need to back that out (unroot first). Obviously carries some risk as does any operation that touches system files in mass.

Answer to all the above is 'NO'. Stated another way SuperSU in its default configuration is just fine. It will be overwritten anyhow with a successful rom flash.
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
Ok thanks, I'll try it with encryption enabled first.

Ahhh yeah I guess that makes sense :p

---------- Post added at 11:06 PM ---------- Previous post was at 11:00 PM ----------

Hmmmm .... bummer issue which I need to try and nail down.

As previously stated, I was able to replace KingRoot with Supersu-me ... I verified after it finished installing that I still had root access using my installed Root checker app. However, I decided to see if root would "stick" before installing "Safestrap" so I rebooted. The device rebooted just fine, but my root checker app now says that my device does not have proper root access.

Should I remove and reinstall supersu-me, reboot, check, rinse and repeat until root finally sticks? Or is there some other tried and tested method I should use?

Previously you mentioned running the PC based version of KingRoot via USB tether, but wouldn't I need to then run Supersu-me again anyway?

Thanks
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
Since I lost root with a reboot after replacing KingRoot with SuperSU-me I went and did some additional research on KingRoot ... the version of KingRoot that I used (and just removed with Supersu-me) was 4.1 ... the current version is apparently 4.8 ... so, I'm going to try and root again using KingRoot 4.8, then replace with supersu-me 7.6. I'll reboot after replacing KingRoot with Supersu-me to see if I retain root access after a reboot and update.

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

Here is what I've done to get my device re-rooted (persistent with reboot) and ready for a custom ROM via Safestrap, after removing recovery, safestrap, kingroot, supersu, and supersu-me:

I re-rooted using KingRoot v4.8 (APK using ES Explorer since I cannot read Chinese characters and have little patience for guessing what strange symbols mean on buttons I'm supposed to click on during an application install ... and because I like my PC).

I re-installed my Root Checking app and verified that I once again have root access.

I rebooted the device.

I verified that my device retained root access post reboot using my Root Checking app.

I installed Supersu-me v7.6 (APK using ES Explorer).

I verified that my device retained root access post Supersu-me installation.

I rebooted the device.

I attempted to verify that my device retained root access post reboot using my Root Checking app ... FAIL ... Lost Root Access.

Back to square 0 ... for some reason I can retain a persistent root but only with KingRoot installed. SuperSU (Free version at least) does not retain root after reboot on my device. Is this a concern? Or should I just not reboot after running Supersu-me?

Should I instead just install Safestrap 4.0.1 after running Supersu-me, followed by installing Recovery, and go into recovery without rebooting? Don't I have to boot into recovery? I wonder if this isn't the problem.

Any thoughts on why KingRoot won't work with Safestrap? Is there something about SuperSU that allows Safestrap to function which KingRoot does not provide? I can maintain root with KingRoot installed so it's not just "root access". SuperSU must unlock something, but apparently that does not persist through a reboot (or is not provided with the free version of SuperSU).

So then, is this a PRO vs Free issue? I certainly don't mind purchasing the PRO version of SuperSU if it will work ... but I'm not a fan of throwing money away.

Thank you again, and again, and again, and once more for good measure!
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Kingroot is continually evolving and tries to apply the 'best' (or perhaps first successful) method to achieve root based on perceived device type. Possible different methods were used at different times yielding different outcomes (eg: root surviving reboot). There are numerous reports of running Kingroot multiple times before achieving a successful/durable/robust root.

Your objective is to secure a durable root that survives a reboot. Whether that be with Kinguser or SuperSU installed is irrelevant. Recall I suggested Super-sume as it appeared your device was not properly rooted which now appears to have been the case. If Kingroot sticks that go with it.

Think about what you wrote in the 2nd paragraph (above). You can not "go into recovery without rebooting" as entering recovery involves a reboot. Slow down a bit before you make a mistake.

No need to purchase anything. Clear out everything (looking for clean start), consider removing device level encryption and then start fresh with Kingroot verifying root survives a couple reboots before continuing with Safestrap.
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
Thank you ... I got the impression that KingRoot was the exploit and SuperSU would then take advantage of the "hole" KingRoot provided (so to speak) allowing for the use of code/apps like Safestrap etc... but that Safestrap would not function properly when coexisting with KingRoot, which is why it was necessary to use SuperSU-me to first remove KingRoot; however, it seems as though KingRoot (in my case at least) needs to remain in control "of the hole" in order to provide SuperSU with what it needs to give code/apps like Safestrap their functionality ... at least that is my cartoonish mental view of it. Clearly, I've lost my ever-loving mind. As I re-read what I've typed it's hard to follow, so I doubt anyone else will either *sigh*.

Ok, I will do as suggested and see if I can get Safestrap working with the latest KingRoot but without removing it with SuperSU-me. I've had consistent success with a persistent "root" using just KingRoot so far. Correct me if I'm wrong in my thinking, but if I start fresh, keep KingRoot and then add SuperSU (not using SuperSU-me) I should then be able to Safestrap and then flash a custom ROM ... does that sound about right?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
No need for SuperSU. Kingroot, reboot, check, reboot again, verify root access once more, then proceed with Safestrap.
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
Even better ... trying that now.

---------- Post added at 01:47 PM ---------- Previous post was at 01:15 PM ----------

I backed-off everything but encryption ... trying to avoid factory reset just in-case it utterly destroys my device, seems like an absolute last resort (and even then I may not choose to risk it)

I re-rooted with KingRoot 4.8 ... verified root ... rebooted ... verified persistent root

Now I am going to install Safestrap v4.0.1, reboot, verify root, install recovery, reboot, verify root, and then boot into recovery.

---------- Post added at 02:17 PM ---------- Previous post was at 01:47 PM ----------

I have Safestrap v4.0.1 installed, recovery installed, and after rebooting I have verified I still have root ... I am booted into recovery.

What should I do now? Everything "looks" the same as it did when I first posted here. I have not tried to perform a backup, wipe, or install.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Try creating a backup from within Safestrap. You will want that (just in case) and will demonstrate read access to partition data. Note you'll need at least half the available user space to store the backup. Can be moved/removed later.
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
The "Data" partition still shows 0MB and Backup still fails ... with the same terminal output as before. "Unable to mount ..."

---------- Post added at 07:53 AM ---------- Previous post was at 07:42 AM ----------

Any other thoughts? Besides risking a factory reset to remove encryption?
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
I removed recovery, safestrap, kingroot, rebooted.

I am in the process of performing a factory reset ...

---------- Post added at 09:28 AM ---------- Previous post was at 09:20 AM ----------

As expected ... it appears as though the device is bricked. It erased, rebooted, displayed the Kindle Fire animated logo and then the swipe to enter screen... when I swipe to enter I am asked to chose my language and select "Continue" ... whenever I select "Continue" it just returns to the "Select your language" screen.

FML

---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------

It does however, briefly display the home screen with the scroll bar (showing silk browser and other apps) but that lasts about 0.0002 seconds before returning to the select a language screen ...

if that means anything.

---------- Post added at 09:39 AM ---------- Previous post was at 09:30 AM ----------

Apparently I still have the ability to push files to the device from my PC via USB... I was able to upload an .APK file to the device's SD Card.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
There is a solution but I don't have time to document now. Involves pushing a different launcher to the device (suggest Nova) to get past the language select screen. You can't use the home key nor set the other launcher as default. However, if you can get past the language screen (and one or two other set up screens) you should be good. Look for related posts in the HDX forums. Post progress; will check back in a day or two.

Hint: You'll need to use adb install <apk> vs push for the launcher.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Thanks for the detailed updates. Two paths:

- can continue with efforts to address language select loop in FireOS; others have overcome this so probably more trial/error

- since your ultimate goal a custom ROM it may be more expeditious to see if Safestrap recovery functions properly now that device level encryption has been disabled

My preference leans toward the latter as I believe the lockup risk is low (not zero). Using Nova and/or adb commands you should be able launch the Safestrap app and install SS Recovery - hopefully with better results.
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
I've re-enabled the ability to install from unknown sources, and enabled developer options within settings. Re-installed ES File Explorer, Re-rooted with KingRoot, re-enabled Root explorer within ES, and verified root with Root checker.

I have also installed a screen capture utility to take snapshots of root checker data ... to post here. Maybe it will contain some information that looks "off" to someone more knowledgeable of such data; I'll post those captures shortly.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
What is your objective posting screen shots? Have you attempted to reinstall Safestrap v4 recovery and run into further difficulties?
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
screen capture data from root checker app

Here are the screen captures taken from within my root-checker app:
[Kindle Fire HDX 7" & 8.9" Android Development] craigs_lv:
Yes, I essentially cannot use Safestrap to flash a custom ROM for some reason. Pages 8 and 9 of this thread should fully document everything I've tried and the results.

Right now, I'm left with a crippled device after attempting to remove encryption (performed as a last resort) to try and get Safestrap to work. For some reason, with root, I go into recovery and am unable to perform a backup or anything else necessary to flash a custom ROM.

The goal / end-result which I've been trying to achieve is to simply flash the CM-11 custom ROM onto my KF Apollo device. And have been met with utter failure for the past several days / weeks.