I am furious. I did not realized that Fire HDX 8,9, (3rd generation) v4.5.5.1 is totally different OS from "normal Android OS" and now I wonder what can I do about it.
How can I uninstall Amazon Android OS and replace it with normal Android OS.
Can that be done? If yes HOW?
I have been searching and reading here, but I am even more confused (yes I am Fire HDX newbie). I would really appreciate if I can get clear and logical instructions HOW can I do that for my unit.
I managed to install Kingroot and was able to login to my Google Play account as I have 2 Android phones (Samsung S2 and Leagoo Lead 1), but when I login and tried to download RootChecker, Google Play does NOT show (recognize) my FireHDX, it only shows my other 2 phones. So that's not good for me.....
Any help will be greatly appreciated as the way is my Fire now is useless.
TIA
Ivone said:
I am furious. I did not realized that Fire HDX 8,9, (3rd generation) v4.5.5.1 is totally different OS from "normal Android OS" and now I wonder what can I do about it.
How can I uninstall Amazon Android OS and replace it with normal Android OS.
Can that be done? If yes HOW?
I have been searching and reading here, but I am even more confused (yes I am Fire HDX newbie). I would really appreciate if I can get clear and logical instructions HOW can I do that for my unit.
I managed to install Kingroot and was able to login to my Google Play account as I have 2 Android phones (Samsung S2 and Leagoo Lead 1), but when I login and tried to download RootChecker, Google Play does NOT show (recognize) my FireHDX, it only shows my other 2 phones. So that's not good for me.....
Any help will be greatly appreciated as the way is my Fire now is useless.
TIA
Click to expand...
Click to collapse
Likely find what you need in the following thread (one of several btw). Read, go slow, reread to confirm understanding, ask if unsure, ignore internet/youtube guidance from 'experts' not familiar with this device. HDX devices are easy to brick and tough/impossible to recover if you stray off the beaten trail.
http://forum.xda-developers.com/kin...artially-fire-os-to-proper-rom-t3421623/page4
fwiw - I am penning this on a 3rd gen HDX thor (7") running Fire Nexus which is my primary device (3-4 hours per day) despite having access to numerous other computing gizmos with far better headlines. Yep, lowly kitkat on a 2+ year old (unlocked) tablet. Go figure. You can duplicate that 98% of that config with minimal effort.
Thanks Davey, I am reading all the post in that thread you posted. Looks like I am on the right path.
I have 4.5.5.1 and Kingroot installed already on my Fire and working. Installed ES File Explorer and tested. I am rooted. !
Next step is to install Safestrap 4.0.1 - right?
After that I will go with HDX Nexus ROM v4 (as I red it's the best for my Fire HDX)
Then will proceed with HDX Nexus ROM installation ...
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery (HOW do I do that?)
- You should eventually end up in safestrap recovery
Once I do that the instruction is: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-safestrap-v4-0-1-t3137840
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Which one do I download THOR or APOLLO? (little confused here)
Also, should I delete any or all aplications that I downloaded and installed from Amazon?
Will everything work normal such as: Wifi, AGPS etc? Any known issues with my FireHDX?
TIA
Ivone said:
Thanks Davey, I am reading all the post in that thread you posted. Looks like I am on the right path.
I have 4.5.5.1 and Kingroot installed already on my Fire and working. Installed ES File Explorer and tested. I am rooted. !
Next step is to install Safestrap 4.0.1 - right?
After that I will go with HDX Nexus ROM v4 (as I red it's the best for my Fire HDX)
Then will proceed with HDX Nexus ROM installation ...
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery (HOW do I do that?)
- You should eventually end up in safestrap recovery
Once I do that the instruction is: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-safestrap-v4-0-1-t3137840
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Which one do I download THOR or APOLLO? (little confused here)
Also, should I delete any or all aplications that I downloaded and installed from Amazon?
Will everything work normal such as: Wifi, AGPS etc? Any known issues with my FireHDX?
TIA
Click to expand...
Click to collapse
Response to questions:
- HDX 7" = Thor; HDX 8.9" = Apollo (you want Apollo)
- reboot to recovery: you will be prompted (or just shutdown & restart)
- no need to delete existing applications
- everything works in Nexus - WiFi, Bluetooth, location services (no GPS unless you have LTE model), Play Store, etc. No significant issues.
Davey126 said:
Response to questions:
- HDX 7" = Thor; HDX 8.9" = Apollo (you want Apollo)
- reboot to recovery: you will be prompted (or just shutdown & restart)
- no need to delete existing applications
- everything works in Nexus - WiFi, Bluetooth, location services (no GPS unless you have LTE model), Play Store, etc. No significant issues.
Click to expand...
Click to collapse
Davey, I have not abandon the OS changing process, I am just VERY scared. Since my post, I have been reading and reading like crazy hundreds pages trying to understand between all the info what exactly is related to only my FireHDX, but did NOT found exact instruction. A lot for HD, HDX 7 etc. It looks like that my Fire is not very popular
I will write again my setup.
Fire HDX 8,9, 4.5.5.1, (3rd generation), 16GB, 4G/LTE, free space left 6.86GB, all stock. Only extra apps I installed are: Opera, GPS Test, KingRoot that I used to Root (working), ES File Explorer that I used to change the permissions like this > Root Explorer>Mount R/W>changed permission to RW in: /system and /mnt/sqfs
I have Windows 7, 32
I am a complete chicken to proceed further.
I imagine next step is to install Safestrap but I am not sure what is the latest version for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE
(it looks like Safestrap 4.0.1 is the one I should use - correct?) If yes should I follow your instruction BELLOW from other thread?
Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. You can snag the app from here (got the URL - np), be sure to select the appropriate format (APOLLO). Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. From home screen go into the backup section. Take a backup of your current FireOS installation (selection all partitions). You will want this should you every want to restore you device to it's current configuration. The resulting files will be quite large and should be copied to another device for safe keeping (will transfer to my PC.). Exit Safestrap and reboot into FireOS. Tether your device and copy the files to a suitable host. You seem to be familiar with ES File Explorer so should have no problem finding them. Should be in the TWRP directory located within sdcard (or just browse internal storage from the host machine).
What is the correct slot that I should use? I just found the answer = Stock slot!
Do I have to download some drivers to my PC for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE and transfer them to Fire directory? If yes, what drivers and where should I place them. (found the answer - installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard)
Apollo Nexus ROM will be my prefer choice, but wonder if everything will work.
I know that you answer that, but then you mention 4G/LTE, is that mean it will work as well or my SIM/phone/data will not work.
Is there any known issue (what will NOT work) on my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE once I change to Apollo Nexus ROM?
Also I like to ask you if CM11 will have any advantage over Nexus on MY Fire HDX. Just wonder (as you said it has nice GUI etc.)
I red tons and tons of yours and other people posts and I am VERY great full for all your time and help you offer to newbie like me. Your dedication is awesome.
UPDATE
I took the plunge and installed Safestrap and all is fine (checked few times)
I downloaded Nexus Apollo and placed it into folder that I created in the FireHDX Internal Storage. I don't see or know how I can create folder in the root directory in
my Fire sdcard.
I am trying to follow your instructions from your other post:
Nexus Apollo installation zip. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. (HOW) It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
That's exactly my concern - will my Apollo Nexus folder get deleted when I install it Nexus on the Stock Slot. Does it wipe ALL the folders in the Internal Storage?
Can I/ should I move the ApolloNexus folder using ES File Explorer 3.0.5 in to Fire Device directory or Root and will I be able to access it after the wipe.?
I am stuck..................!
TIA
Attaching image where is the folder now - is it safe there?
Ivone said:
Davey, I have not abandon the OS changing process, I am just VERY scared. Since my post, I have been reading and reading like crazy hundreds pages trying to understand between all the info what exactly is related to only my FireHDX, but did NOT found exact instruction. A lot for HD, HDX 7 etc. It looks like that my Fire is not very popular
I will write again my setup.
Fire HDX 8,9, 4.5.5.1, (3rd generation), 16GB, 4G/LTE, free space left 6.86GB, all stock. Only extra apps I installed are: Opera, GPS Test, KingRoot that I used to Root (working), ES File Explorer that I used to change the permissions like this > Root Explorer>Mount R/W>changed permission to RW in: /system and /mnt/sqfs
I have Windows 7, 32
I am a complete chicken to proceed further.
I imagine next step is to install Safestrap but I am not sure what is the latest version for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE
(it looks like Safestrap 4.0.1 is the one I should use - correct?) If yes should I follow your instruction BELLOW from other thread?
Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. You can snag the app from here (got the URL - np), be sure to select the appropriate format (APOLLO). Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. From home screen go into the backup section. Take a backup of your current FireOS installation (selection all partitions). You will want this should you every want to restore you device to it's current configuration. The resulting files will be quite large and should be copied to another device for safe keeping (will transfer to my PC.). Exit Safestrap and reboot into FireOS. Tether your device and copy the files to a suitable host. You seem to be familiar with ES File Explorer so should have no problem finding them. Should be in the TWRP directory located within sdcard (or just browse internal storage from the host machine).
What is the correct slot that I should use? I just found the answer = Stock slot!
Do I have to download some drivers to my PC for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE and transfer them to Fire directory? If yes, what drivers and where should I place them. (found the answer - installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard)
Apollo Nexus ROM will be my prefer choice, but wonder if everything will work.
I know that you answer that, but then you mention 4G/LTE, is that mean it will work as well or my SIM/phone/data will not work.
Is there any known issue (what will NOT work) on my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE once I change to Apollo Nexus ROM?
Also I like to ask you if CM11 will have any advantage over Nexus on MY Fire HDX. Just wonder (as you said it has nice GUI etc.)
I red tons and tons of yours and other people posts and I am VERY great full for all your time and help you offer to newbie like me. Your dedication is awesome.
UPDATE
I took the plunge and installed Safestrap and all is fine (checked few times)
I downloaded Nexus Apollo and placed it into folder that I created in the FireHDX Internal Storage. I don't see or know how I can create folder in the root directory in
my Fire sdcard.
I am trying to follow your instructions from your other post:
Nexus Apollo installation zip. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. (HOW) It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
That's exactly my concern - will my Apollo Nexus folder get deleted when I install it Nexus on the Stock Slot. Does it wipe ALL the folders in the Internal Storage?
Can I/ should I move the ApolloNexus folder using ES File Explorer 3.0.5 in to Fire Device directory or Root and will I be able to access it after the wipe.?
I am stuck..................!
TIA
Attaching image where is the folder now - is it safe there?
Click to expand...
Click to collapse
Looks like you made some progress (good!) but have the following questions/concerns:
>> Nexus zip location: fine where it is (as shown in your screen shot)
>>Compatibility: no rom is perfect including FireOS. While Fire Nexus is time proven and stable some issues remain:
- 4G/LTE voice does not work
- 4G/LTE data can be finicky; depends on your carrier
- Some Play Store apps (especially games and social media) show as 'incompatible' but typically can be sideloaded without further issue
- Some apps rotate screen 90/180 degrees from 'features' orientation; easily fixed using one of several methods
- Native spell checker crashes foreground application if a replacement word is selected (keyboard spell checkers work fine)
- some browsers/sites mistake big, beautiful, high-res HDX for desktop and do not automatically present mobile version (not a big deal)
- no OTG (external dongle/storage) support...nor is there on FireOS or any other rom for this device; hardware limitation
- GPS is slow and can not be used for driving guidance or games like Pokémon. Same with FireOS. However, static mapping apps are fine.
Yikes - seems like a long list!! Yet an equivalent FireOS manifest would consist of dozens of bullets and take up multiple pages. My wonderful mobile 'issue' list is 3-4x longer. Pick your poison.
Davey126 said:
Looks like you made some progress (good!) but have the following questions/concerns:
>> Nexus zip location: fine where it is (as shown in your screen shot)
>>Compatibility: no rom is perfect including FireOS. While Fire Nexus is time proven and stable some issues remain:
- 4G/LTE voice does not work
- 4G/LTE data can be finicky; depends on your carrier
- Some Play Store apps (especially games and social media) show as 'incompatible' but typically can be sideloaded without further issue
- Some apps rotate screen 90/180 degrees from 'features' orientation; easily fixed using one of several methods
- Native spell checker crashes foreground application if a replacement word is selected (keyboard spell checkers work fine)
- some browsers/sites mistake big, beautiful, high-res HDX for desktop and do not automatically present mobile version (not a big deal)
- no OTG (external dongle/storage) support...nor is there on FireOS or any other rom for this device; hardware limitation
- GPS is slow and can not be used for driving guidance or games like Pokémon. Same with FireOS. However, static mapping apps are fine.
Yikes - seems like a long list!! Yet an equivalent FireOS manifest would consist of dozens of bullets and take up multiple pages. My wonderful mobile 'issue' list is 3-4x longer. Pick your poison.
Click to expand...
Click to collapse
Thank you Davey for the detail explication.
Wow, what a disappointment with all the Nexus rom issues. Oh well, that will scrap my Vodafone appointment today. In that case I will research alternatives (if they exist). Basically I was going to use it MAINLY for Waze or Sygic navigation and calls. I am not in to games, music, movies etc.
Co you have any idea how is CM11 behave with my type of Fire? Or what would you suggest?
Thanks again for your time and help.
One more time my apologies rambling about the setup request. I have read about so many problems and bricking that put me in the panic mode.
Ivone said:
Thank you Davey for the detail explication.
Wow, what a disappointment with all the Nexus rom issues. Oh well, that will scrap my Vodafone appointment today. In that case I will research alternatives (if they exist). Basically I was going to use it MAINLY for Waze or Sygic navigation and calls. I am not in to games, music, movies etc.
Co you have any idea how is CM11 behave with my type of Fire? Or what would you suggest?
Thanks again for your time and help.
One more time my apologies rambling about the setup request. I have read about so many problems and bricking that put me in the panic mode.
Click to expand...
Click to collapse
You will not be able to use a HDX for dynamic navigation regardless of app or rom - including FireOS. The integrated GPS 'chip' is has proven unreliable and is too slow to keep up with rapidly changing locations. It is also slow to acquire satellites (minutes) and often needs a reboot if the GPS appears unresponsive. Works fine for static location apps/maps using Google's fused location services. Static mapping/location apps are less reliable on FireOS; many will not work at all. Sorry for the bad news ...
Davey126 said:
You will not be able to use a HDX for dynamic navigation regardless of app or rom - including FireOS. The integrated GPS 'chip' is has proven unreliable and is too slow to keep up with rapidly changing locations. It is also slow to acquire satellites (minutes) and often needs a reboot if the GPS appears unresponsive. Works fine for static location apps/maps using Google's fused location services. Static mapping/location apps are less reliable on FireOS; many will not work at all. Sorry for the bad news ...
Click to expand...
Click to collapse
What can I say, big disappointment and dumb decision to buy Kindle.
I may try to sell my Kindle that I used once or twice (just playing around ) and buy something else.
BIG thanks again Davey and sorry wasting your time.
Ivone said:
What can I say, big disappointment and dumb decision to buy Kindle.
I may try to sell my Kindle that I used once or twice (just playing around ) and buy something else.
BIG thanks again Davey and sorry wasting your time.
Click to expand...
Click to collapse
Not a waste of time if useful knowledge was exchanged. Despite the disappointment HDX tablets are wonderful devices that can perform many tasks better than contemporary high-end alternatives. Unfortunately, navigation is not one of them.
Davey126 said:
Not a waste of time if useful knowledge was exchanged. Despite the disappointment HDX tablets are wonderful devices that can perform many tasks better than contemporary high-end alternatives. Unfortunately, navigation is not one of them.
Click to expand...
Click to collapse
Oh well, your right. I am also believer that everything is good for something....
BTW: is it complicated to bring my KF back to stock with out any negative consequences?
Can I just delete Safestrap?
Ivone said:
Oh well, your right. I am also believer that everything is good for something....
BTW: is it complicated to bring my KF back to stock with out any negative consequences?
Can I just delete Safestrap?
Click to expand...
Click to collapse
Assuming you have not installed a custom rom simply uninstall Safestrap recovery from the within Safestrap app and then close and uninstall the Safestrap app itself.
Davey126 said:
Assuming you have not installed a custom rom simply uninstall Safestrap recovery from the within Safestrap app and then close and uninstall the Safestrap app itself.
Click to expand...
Click to collapse
Ok, thanks a lot... (no rom installed)
Just checking if there is any news on that matter. Or maybe any new stable Android I can install. As of now I'm just using my HDX 8.9 to watch movies when travelling. Thx!
antonioroc said:
Just checking if there is any news on that matter. Or maybe any new stable Android I can install. As of now I'm just using my HDX 8.9 to watch movies when travelling. Thx!
Click to expand...
Click to collapse
Your question is not entirely clear but it is now possible to install a wide array of high quality custom ROMs on any 3rd (not 4th) gen HDX representing Android 4.4 (KitKat) to 7.1 (Nougat). All offer full access to Google Play along with the amenities that come with native Android and a well stocked app store. That said, if you are only using your HDX to watch movies FireOS remains a solid choice
Thanks for replying. Do you have a tutorial on how to install 7.1 (Nougat) into 8.9 3rd Thor?
antonioroc said:
Thanks for replying. Do you have a tutorial on how to install 7.1 (Nougat) into 8.9 3rd Thor?
Click to expand...
Click to collapse
You have to root FireOS (or pursue a somewhat more complex alternative) and then unlock the bootloader to enable installation of Android 7.x based ROMs on this device. The prep work can be a bit daunting for those new to tinkering with Android devices. The following thread is a good starting point.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
I'm just not getting there
I've been following this post for some time trying to do the same with my 3rd Gen fire HDX 8.9. I'm on OS version 4.5.5.3 and can't seem to get into the system by doing any of the turn-on procedures (turn-on, wait then hold power button, power and volume up, etc.). Has Amazon locked us out with the latest update? Did I buy this and get stuck with a useless (nearly) box of rocks? I have ES File manager, Safestrap 4.01 and Kingroot installed and I'm able to get to the root directory, but I'm lost after that.
Bobkuwait said:
I've been following this post for some time trying to do the same with my 3rd Gen fire HDX 8.9. I'm on OS version 4.5.5.3 and can't seem to get into the system by doing any of the turn-on procedures (turn-on, wait then hold power button, power and volume up, etc.). Has Amazon locked us out with the latest update? Did I buy this and get stuck with a useless (nearly) box of rocks? I have ES File manager, Safestrap 4.01 and Kingroot installed and I'm able to get to the root directory, but I'm lost after that.
Click to expand...
Click to collapse
Not sure what you are trying to do but sounds like the wrong procedure. You can follow along in this thread as I assist another Apollo user with a similar configuration unlock the bootloader in preparation for installation of a custom ROM. Please note you will NOT be able to use this device for dynamic navigation regardless of ROM.
Just not getting there
Davey126 said:
Not sure what you are trying to do but sounds like the wrong procedure. You can follow along in this thread as I assist another Apollo user with a similar configuration unlock the bootloader in preparation for installation of a custom ROM. Please note you will NOT be able to use this device for dynamic navigation regardless of ROM.
Click to expand...
Click to collapse
I want to put a full version of Android on my Kindle Fire HDX 8.9 3rd generation. I've followed along on the website. and cannot seem to get a bootloader to open on my Kindle. Running OS 4.5.5.3. I have downloaded several ROMs (CM 12.1, CM 14.1 KK Nexus for fire, but cant get to the bootloader to run any of them. Is there a step-by-step guide anywhere? I was able to get my Nook to the CM 12 platform quite easily.
Related
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Well said buddy.
I consider myself a fairly advanced android and linux user and I've customised the heck out of my n4 but I'm leaving my hdx as it is for now.
Good advise there.
Now if only mayday had a pro feature to help with rooting... haha
Can we set jcase up with a webcam? Lol
Sent from my Nexus 4 using Tapatalk
GSLEON3 said:
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
Click to expand...
Click to collapse
Safestrap! Safestrap!
http://forum.xda-developers.com/showthread.php?t=2556677
Firstly, this was posted before SafeStrap. Plus, I highly doubt even Hashcode would recommend new users mess with SafeStrap right now. I'm by no means a master developer, but I've been around a long time & I've participated in some pretty cool low level hacking with some of the old timers & I'll be the first to say that there is some funky stuff going on in the HDX. Amazon has not exactly gone out of their way to make modding safe or easy. Plus there's not a whole lot out there yet that requires an custom recovery. It may be fine for you or I, but it can open a whole other host of issues if used improperly.
Sent from my KFJWA using XDA Premium HD app
Hey there I am new to this forums! Got a kindle yesterday (as a gift) and moved straight to xda to see what's cooking unfortunately I was a bit disappointed because there is no "cooking" at all. I hope this has to do with the fact that it's a new device and nobody has tried to make some roms for it yet... Nevertheless I am quite happy with it, although this fire os is a pretty pain in the eyes. Thank God I have managed to get the YouTube app sync with my Google account, plus some other gapps like drive. Well that's it for the moment, I just didn't want to make a new thread so I posted in here. So what do you think, will there be some good roms for this device? And/or maybe we could use those for the kindle fire hd?
Sent from beneath my cloak of magic
Thanks for the info I'm super new at this but was thinking buying one of these. But now that I am acquainted with Flashing ROMs and stuff it's sort of a deal breaker if it's not being done. If I can't modify it, whats the point?
HDX rooting?
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
Patience good people. Each day a few qualified devs get a little closer ... all on their own free time. A crack might be right around the corner.
Well, it's almost June and development for the Kindle tablets seem to still be very slow, what's the story?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
You can get root and the Google Play Store on an older firmware, just not any of the newest couple. Yet (I hope).
Good to go: I was able to use hdx-toolkit with my router blocking
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
sabasc said:
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
Click to expand...
Click to collapse
I'm sorry I missed this. Great advise though.
A default Microsoft driver was blocking the Amazon ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install. --Win8/Win8.1
Click to expand...
Click to collapse
The toolkit needs to be run locally because well the adb connection won't go through your share to your computer.
GSLEON3 said:
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Click to expand...
Click to collapse
Is this still the case? Just wondering if this thread needs to be updated because some of what's written here seem to contradict what I've read people are doing with their hdx.
my 8.9HD ver. 8.5.1
Is my kindle an HDX?
ant17 said:
Is my kindle an HDX?
Click to expand...
Click to collapse
No, you can find anything related to your kindle here
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
hfpop said:
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
Click to expand...
Click to collapse
to an extent yes,most custom roms cannot be installed but if you rolled back you can still root and instal the hdx nexus 2.0.2 rom which is pretty much most of what the device needs
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
hfpop said:
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
Click to expand...
Click to collapse
i have it on 3.2.7 on my device and this here lists what you can do with a 3.2.8
http://forum.xda-developers.com/kin...o-13-3-2-7-t2993089/post58150015#post58150015
@Davengerr: Thank you. All worked out greatly.
Hi I just bought a new Kindle fire hdx , after root it. I am unable to access photo gallery and Kindle appStore:crying:. Would like to know , is anybody can provide 8.9" original rom of Kindle fire hdx 8.9". Thanks a lot.
Missing here as well ...
By the way, awesome work all!!!
Like the OP, I too am missing my "Photo Gallery" post root from last night. My device is a kindle fire hdx 8.9 appears to have rooted ok but with a couple curiosities .... I will continue to try and fix what I can or at least get a better understanding of what went awry and share what I find. However, if any of you experts have some insight into these "issues" I would very much appreciate your constructive feedback / input.
The first issue is the missing "Photo Gallery". Oddly, no apps which rely on it for loading / saving image data are able to find it ... I see a partial folder structure in DCIM (a couple sub-folders are gone when browsing to the DCIM folder inside "internal storage" via my USB to PC connection through Windows explorer); however, when browsing to the DCIM folder located inside of "emulated/0" via ES Explorer local to the device, I see an apparently complete (or more complete) list of folders and files than those seen from Windows in "internal storage/DCIM/". I was thinking about copying data from "emulated/0" to the "internal storage" location to see if that makes any difference. But im not sure what's an actual folder and what's just a symbolic link to a folder some place else in storage... and would prefer to not further "Bork" the device if possible.
Also, I think the "Photo Gallery" app itself is completely gone from the device ... I was hoping to find a way to restore it or find an alternative solution that allows my other apps, which need the "missing" Photo Gallery for normal operations, to function again. The error messages I get from apps trying to access photo data or that need to save new data don't state that they can't locate or save files, they state that they can't locate "Photo Gallery".
Second issue, also post root from last night ... I was not successful in removing the advertisements which appeared on the lock screen pre root. The root tool / method I followed seemed to work without error but the option to remove the ads didnt effect any noticeable change. I was going to try some apps that modify wallpaper etc to see if that wgorks ... but again, any insight or assistance with getting this resolved would be most helpful too.
Many thanks in advance!
Stock Rom
The Kindle App store is a known issue after rooting. If you are trying to get back to stock you can follow this http://forum.xda-developers.com/showthread.php?t=2582773 I did it on my HDX 8.9 and it worked without issue.
My Kindle Fire HDX 8.9" becomes a brick after replace the build.prop file
BroncoAG said:
The Kindle App store is a known issue after rooting. If you are trying to get back to stock you can follow this http://forum.xda-developers.com/showthread.php?t=2582773 I did it on my HDX 8.9 and it worked without issue.
Click to expand...
Click to collapse
Unfortunately, after I edit and replace the file in /system , my Kindle Fire HDX 8.9" becomes a brick now.:crying:
chen1911 said:
Unfortunately, after I edit and replace the file in /system , my Kindle Fire HDX 8.9" becomes a brick now.:crying:
Click to expand...
Click to collapse
How did you do it? I have had zero issues & I can pretty well GARUNTEE I have had more bricks, bootloops & soft bricks than any other HDX owner.
Did you edit on desktop & just copy over? If you edit on desktop instead of the live build.prop, you need to move it to another folder first, then chown/chmod before using adb to cp it.
Otherwise with root explorer & a few other explorers, it works fine, all of the billion times I have done it. Once again, since we are dealing with a Linux-ish OS, even then I always check the permissions (chmod) & ownership (chown).
Either that, or like a few others, you grabbed the wrong build.prop.
GSLEON3 said:
How did you do it? I have had zero issues & I can pretty well GARUNTEE I have had more bricks, bootloops & soft bricks than any other HDX owner.
Did you edit on desktop & just copy over? If you edit on desktop instead of the live build.prop, you need to move it to another folder first, then chown/chmod before using adb to cp it.
Otherwise with root explorer & a few other explorers, it works fine, all of the billion times I have done it. Once again, since we are dealing with a Linux-ish OS, even then I always check the permissions (chmod) & ownership (chown).
Either that, or like a few others, you grabbed the wrong build.prop.
Click to expand...
Click to collapse
I did not chown/chmod before using adb to cp it. I guess the file build.prop has corrupted. The problem is , I didn't backup my rom. Would like to have backed up original rom of kindle fire hdx 8.9". Anybody can help me that?
if someone can help me get root back, I may be able to help.
GSLEON3 said:
How did you do it? I have had zero issues & I can pretty well GARUNTEE I have had more bricks, bootloops & soft bricks than any other HDX owner.
Did you edit on desktop & just copy over? If you edit on desktop instead of the live build.prop, you need to move it to another folder first, then chown/chmod before using adb to cp it.
Otherwise with root explorer & a few other explorers, it works fine, all of the billion times I have done it. Once again, since we are dealing with a Linux-ish OS, even then I always check the permissions (chmod) & ownership (chown).
Either that, or like a few others, you grabbed the wrong build.prop.
Click to expand...
Click to collapse
I put an old build.prop at / folder, but I can't access adb shell and Windows 7 can't recognize the device, any suggestion for the issue? Once I can access the device , then copy original build.prop to /system, I guess the device will boot properly.
No no no, root doesn't mess with the app store on Thor. I'm rooted with Amazon appstore working. Changing some system files and blocking some ip's will do it (if you have android firewall disable it to use appstore). If you want to unroot just do it in supersu settings. btw I have the 7" model. Also safestrap is now on Apollo (the 8.9").
All Current rooting options appear to not be compatible with Fire OS 4.1.1. The most recent option I have found was Root_with_Restore_by_Bin4ry_v35. This contains a .bat file that is not consistent with the current file structure of the OS 4.1.1. It appears to be moving the file Special.ab (as part of the restore procedure) to a location on the fire that is no longer a valid path. Attepmting to back up/restore the file com.android.settings, which is not a file on the Fire Hd.
Also, all instructions regarding the process to Root, discuss Endabling ADB via settings>security. There is not a Security selection under Settings; there is Security and Privacy selection.
And the option to enable installation from unknown source is not under Settings>Device, it is located under Settings>Applications.
I seem to get very close but Amazon seems to have it so locked down that I may be buying a new REAL tablet soon.
Has anyone found a viable solution to rooting this Fire Hd?
AFAIK the last gen HD tablets weren't rootable either. I wouldn't get your hopes up. Having CM/PA would be nice but using the Google apps/Launcher hacks you can at least make it much closer to a custom ROM.
Root_with_Restore_by_Bin4ry_v35 is for the 2012 Kindle HD (tate). Using this on our 2013 soho Kindles will result in a permabrick.
Fire HD 6 Under OS 4.1.1 and USB Debugging
I have seen people saying that they 'removed USB Debugging' from Fire HD 6 and 4.1.1.
That is not true.
You go to Settings->Device Options and click 7 times on the Serial Number.
You will find that USB Debugging is already turned on when it comes from the factory; how to turn USB Debugging OFF is the problem for some people with their Fire HD 6 under OS 4.1.1.
And, as someone else said, "Apps From Unknown Spaces" should be checked and that is in Settings->Applications
Have not found a method, yet, of rooting the device. However, you can get to what is not rooted. To install APK files, for example, just go to the Amazon App Store (go to Silk, search for 'Amazon App Store' and create a bookmark. Then you will be able to install free apps such as ES Explorer.
You can plug your Fire HD 6 into your computer, open up a folder and go to the Download folder. Then, using ES Explorer you can double-click on the Download folder and install APK files that you have put there.
In that manner I installed a program I had created and it ran perfectly on the Fire.
Thus, if you have the APK for an App; you can install it.
Do you know if there's a way to install the Google Play Store? Isn't it just another APK? Also, I'm trying to install some google apps (gmail, music, youtube etc) and it's not working since I don't have the google services .apk installed. I tried installing the google servies .apk but just get an parcing error
Sthornton71 said:
All Current rooting options appear to not be compatible with Fire OS 4.1.1. The most recent option I have found was Root_with_Restore_by_Bin4ry_v35. This contains a .bat file that is not consistent with the current file structure of the OS 4.1.1. It appears to be moving the file Special.ab (as part of the restore procedure) to a location on the fire that is no longer a valid path. Attepmting to back up/restore the file com.android.settings, which is not a file on the Fire Hd.
Also, all instructions regarding the process to Root, discuss Endabling ADB via settings>security. There is not a Security selection under Settings; there is Security and Privacy selection.
And the option to enable installation from unknown source is not under Settings>Device, it is located under Settings>Applications.
I seem to get very close but Amazon seems to have it so locked down that I may be buying a new REAL tablet soon.
Has anyone found a viable solution to rooting this Fire Hd?
Click to expand...
Click to collapse
Fire OS 4.1.1 IS NOT Android 4.1.1! It's 4.4.4 renamed
taylooor said:
Do you know if there's a way to install the Google Play Store? Isn't it just another APK? Also, I'm trying to install some google apps (gmail, music, youtube etc) and it's not working since I don't have the google services .apk installed. I tried installing the google servies .apk but just get an parcing error
Click to expand...
Click to collapse
There is a great tutorial on how to get GAPP's working on the HD 6 which only requires a little bit of ADB knowledge.
http://forum.xda-developers.com/fire-hd/themes-apps/how-to-install-gapps-fire-hd6-hd7-t2933523
Unfortunately, the Play Store will not work as it needs root to perform the hack which isn't possible on this device yet (if ever).
No root, but still usable.
Just got three for my kids assuming we would be able to re isntall a decent version of an os on here.
Unfortunately looks like that is not the case.
I had purchesed minecraft from the play store, and when I went to load it up I was being charged the 7 bucks again from the amazon store. Not cool with that.
Fortunately as WowSoftware stated you can still side load any apk you want with out a problem.
Here is what I have been doing:
1) on a device that is linked to google play store:
Install titianum backup, es file explorer
use titanium backup to backup your application
go into the titatium backup folder and find your apk.gz file
move this to a network storage device (jsut for ease, you can copy to your computer if you like)
un .gz the file into a folder.
2) on the fire hd
go to settings and check the box that says allow unkown softwtware to be installed (cant remember the exact wording)
open es file explorer
browse to network store and click on the apk
This will load up what you need (you may need to do the gapps installation if you get no network connectivity issue).
You will need to manually run updates this way.
It's a hack but it works. I'm confident that there will be a root for this device some day, in the mean time I would suggest not running any updates fore fire os.
I have actually been thinking that there may be a way to block the advertisement feed at my router. Just to stick it to the man. If I do this I'll post some info on that.
And the Google play works with this method?
Ado40 said:
And the Google play works with this method?
Click to expand...
Click to collapse
AFAIK no.
PS: There is an ongoing discussion about a possibility of rooting new devices here - h**ps://plus.google.com/communities/115612726860884592519
I have been doing a lot of indepth reading regarding the whole process of loading Lollipop on a Kindle Fire HDX 7.
I thought I had the process understood but have realised I might have a problem. It seems that there is a loop where you need to ROOT the Kindle in order to rollback the ROM, but all the rooting methods seem to rely on having a 13.3.2 or earlier ROM in order to ROOT it.
It seems that the vulnerabilities which allowed the zergRush root method have been fixed, as have the TowelRoot vulnerabilities. These are the only two methods I have found so far after extensive searching.
I am not certain which ROM my Kindle will have since I have ordered it as present for my wife off of Ebay. It maybe that its got an old ROM and all will be OK, but I would rather not waste my time and possibly brick the Kindle by trying outdated fixes.
I have loaded Android-SDK and Android-Tools onto my Opensuse system, but I understand that I can only "adb push" a rollback ROM if I have already ROOTed the Kindle.
Any guidance to avoid a horrible mistake would be much appreciated.
Stephen
What version of FireOS are you on?
EncryptedCurse said:
What version of FireOS are you on?
Click to expand...
Click to collapse
Wont know until it arrives at the weekend. Will post details then.
Looking at Kingroot as a possible option.
Stephen
Shoog03 said:
Wont know until it arrives at the weekend. Will post details then.
Looking at Kingroot as a possible option.
Stephen
Click to expand...
Click to collapse
Make sure that you don't connect to WiFi.
Your tablet may very well come with an older firmware that'll allow you to unlock the bootloader and install TWRP (allowing access to Lollipop or Marshmallow ROMs).
EncryptedCurse said:
Make sure that you don't connect to WiFi.
Your tablet may very well come with an older firmware that'll allow you to unlock the bootloader and install TWRP (allowing access to Lollipop or Marshmallow ROMs).
Click to expand...
Click to collapse
Yep, will switch off WIFI first thing and then try pushing out the mod-update-kindle-thor-13.3.2.8_user_713328020.bin rollback ROM using adb or gMTP (a Linux utility).
Definately want to go down the TWRP route. Am I to assume that if its a later ROM then accessing the bootloader and installing TWRP is permanently blocked ?
Fingers crossed that this has been sat lingering in a cupboard for the last year and a half.
Stephen
Shoog03 said:
Yep, will switch off WIFI first thing and then try pushing out the mod-update-kindle-thor-13.3.2.8_user_713328020.bin rollback ROM using adb or gMTP (a Linux utility).
Definately want to go down the TWRP route. Am I to assume that if its a later ROM then accessing the bootloader and installing TWRP is permanently blocked ?
Fingers crossed that this has been sat lingering in a cupboard for the last year and a half.
Stephen
Click to expand...
Click to collapse
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
EncryptedCurse said:
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
Click to expand...
Click to collapse
Thats good to know.
There are so many redundant instruction sets out there that it is very confusing.
Will post the OS when I get it and hopefully get a good pointer to the right strategy.
Stephen
EncryptedCurse said:
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
Click to expand...
Click to collapse
Further elaboration: If the device arrives with FireOS 3.2.6 or lower you can rollback and unlock the bootloader. The exact path depends which version is on the device. 3.2.7 (rare) is effectively the same as 3.2.8. As noted keep WiFi off (or airplane/flight mode engaged) as an OTA can push and unwanted update and further restrict your options.
Davey126 said:
Further elaboration: If the device arrives with FireOS 3.2.6 or lower you can rollback and unlock the bootloader. The exact path depends which version is on the device. 3.2.7 (rare) is effectively the same as 3.2.8. As noted keep WiFi off (or airplane/flight mode engaged) as an OTA can push and unwanted update and further restrict your options.
Click to expand...
Click to collapse
Great.
Is the OTA switch off method where you delete the DeviceSoftwareOTA.apk file still working ?
Stephen
Shoog03 said:
Great.
Is the OTA switch off method where you delete the DeviceSoftwareOTA.apk file still working ?
Click to expand...
Click to collapse
Depends on FireOS version. Renaming (don't delete) DeviceSoftwareOTA.apk works fine on v4. FireOS v3 seemed to have a more elaborate mechanism. Best use HDX Toolbox to kill OTA and related services.
You may not need to kill OTA at all if your intent is to root, rollback, unlock and flash a custom ROM. Depends on the version of FireOS on the device.
Davey126 said:
Depends on FireOS version. Renaming (don't delete) DeviceSoftwareOTA.apk works fine on v4. FireOS v3 seemed to have a more elaborate mechanism. Best use HDX Toolbox to kill OTA and related services.
You may not need to kill OTA at all if your intent is to root, rollback, unlock and flash a custom ROM. Depends on the version of FireOS on the device.
Click to expand...
Click to collapse
There is another one of those Catch 22 situations going on here. Assuming I cannot start by rolling back the first thing I will need to do is load up a version of ES File Manager. However this is available through the Amazon App store, but in order to install it I will have to enable the WIFI to download it - which runs the risk of a OTA kicking in at the same time. So I would rather use adb to push the APK of ES File manager out to the Kindle - but here is the second catch I need a file manager to install the pushed APK. I have been digging into using adb install but what I have found so far suggests that it wont install the ES File Manager. See this for a person asking a similar question (and not getting an answer):
http://forum.xda-developers.com/kin...help-installing-es-file-explorer-adb-t3018469
It seems the only way to get started is to engage WIFI, and that runs the distinct risk of taking me to a bad place through OTA.
Stephen
Shoog03 said:
There is another one of those Catch 22 situations going on here. Assuming I cannot start by rolling back the first thing I will need to do is load up a version of ES File Manager. However this is available through the Amazon App store, but in order to install it I will have to enable the WIFI to download it - which runs the risk of a OTA kicking in at the same time. So I would rather use adb to push the APK of ES File manager out to the Kindle - but here is the second catch I need a file manager to install the pushed APK. I have been digging into using adb install but what I have found so far suggests that it wont install the ES File Manager. See this for a person asking a similar question (and not getting an answer):
http://forum.xda-developers.com/kin...help-installing-es-file-explorer-adb-t3018469
It seems the only way to get started is to engage WIFI, and that runs the distinct risk of taking me to a bad place through OTA.
Click to expand...
Click to collapse
No catch 22 - "adb install app.apk" works fine for ES File Explorer. Skip the Amazon store; grab a copy from here.
Bigger challenge will be rooting if it arrives with FireOS v4 as the most popular tool (Kingroot) requires a brief internet connection to perform its magic. But the process is manageable if carefully monitored; dozens/hundreds have done it.
Again - let's see what version of FireOS is on the device. That will determine next steps and clarify any obstacles you may face.
Davey126 said:
No catch 22 - "adb install app.apk" works fine for ES File Explorer. Skip the Amazon store; grab a copy from here.
Bigger challenge will be rooting if it arrives with FireOS v4 as the most popular tool (Kingroot) requires a brief internet connection to perform its magic. But the process is manageable if carefully monitored; dozens/hundreds have done it.
Again - let's see what version of FireOS is on the device. That will determine next steps and clarify any obstacles you may face.
Click to expand...
Click to collapse
OK thanks, so all I have to do is
adb install <path to app on kindle>app.apk
In my specific case the full instructions will go:
adb kill-server
adb start-server
adb devices <confirm kindle present>
adb push /home/stephen/Desktop/Fire_HDX_7/ES-File-Explorer-4.0.4.1.apk /sdcard/Download/
adb install /sdcard/Download/ES-File_Explorer-4.0.4.1.apk
adb kill-server
Cheers
Stephen
Shoog03 said:
OK thanks, so all I have to do is
adb install <path to app on kindle>app.apk
Click to expand...
Click to collapse
adb install <path to app on PC>app.apk
I find it easier to copy the apk into the directory where minimal adb and fastboot lives. Streamlines installs/pushes as no path is needed. (I actually employ symlinks to an apk repository but that's another topic).
Davey126 said:
adb install <path to app on PC>app.apk
I find it easier to copy the apk into the directory where minimal adb and fastboot lives. Streamlines installs/pushes as no path is needed. (I actually employ symlinks to an apk repository but that's another topic).
Click to expand...
Click to collapse
So it finally arrived (only took about 3 weeks thanks to Ebays ****ty GSP delivery fraud).
It looks brand new, so might be a reconditioned unit. Its a third generation Thor running OS 4.5.5.1 with a Build date of 13 November 2015 (which seems very late and may present an issue in itself).
The roll back thread seems to indicate that it is possible to roll-back the 4.5.5.1 using the mod-update-kindle-thor-13.3.2.8_user_713328020.bin image. I have plugged the Kindle into my Linux box and it appears as an android device, and I dragged and dropped the rollback image to the Download folder. However it will not allow me to check for updates since it requires a working Internet connection to proceed.
I have attempted to place the bin file straight into the sd card next to the Internal Storage folder, but this is root privileged and I have not yet rooted the device.
So its seems it back to the situation that the first step has to be rooting - which means switching on the WIFI to run Kingroot.
So wanting to be extremely cautious at this stage is there any advice as to how to proceed.
I also pushed out a copy of ES_File manager and tried to install using adb install but got this
[email protected]:~> adb devices
List of devices attached
D0FBA0A034530BHD unauthorized
[email protected]:~> adb install /sdcard/Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: /sdcard/Download/ES-File-Explorer-4.0.4.1.apk
[email protected]:~> adb install /Internal storage/Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: storage/Download/ES-File-Explorer-4.0.4.1.apk
[email protected]:~> adb install /Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: /Download/ES-File-Explorer-4.0.4.1.apk
Click to expand...
Click to collapse
Stephen
OK, I didn't follow the instructions for the rollback precisely. I placed the rollback file into the internal storage folder and it found it straight away and is currently installing and doing its first reboot.
Stephen
So i am now running the rollback 13.3.2.8
What next ?
Best root method and then install safestrap and Kitkat and call it a day ?
Stephen
Managed to sideload ES_File_explorer by copying the file into my adb folder and running adb install.
Now I am downloading the update ROM 4.5.2
Will then sideload cve20147911.apk
Stephen
Successful upgraded to 4.5.2
So I installed Superuser and unlocked the root, but when I try to use ES_File_explorer to access the root it prompts with needs ES-permissions manager plugin. It offers to download it but that means switching on WIFI. I have tried to get the .apk file but don't find a good candidate, does anyone have any pointers.
Don't want to switch on the WIFI until OTA is disabled for which I need the permissions manger plugin.
Stephen
Shoog03 said:
Successful upgraded to 4.5.2
So I installed Superuser and unlocked the root, but when I try to use ES_File_explorer to access the root it prompts with needs ES-permissions manager plugin. It offers to download it but that means switching on WIFI. I have tried to get the .apk file but don't find a good candidate, does anyone have any pointers.
Don't want to switch on the WIFI until OTA is disabled for which I need the permissions manger plugin.
Stephen
Click to expand...
Click to collapse
Took the long rollback/upgrade road - 4.5.5.1 can be directly rooted with Kingroot. Assuming you secured root there is no need to tweak permissions. Simply rename DeviceSoftwareOTA.apk (details).
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Mcfinnipoop said:
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Click to expand...
Click to collapse
Appears you have done your homework and have tried most of the solutions I might have suggested. FireOS is intolerant of component name/permission changes (aside from one file dealing with OTA). Best option is to contact Amazon for a one time courtesy exchange if still in warranty.
As a last ditch effort you could try installing Safestrap v4 via adb. If you can get the recovery component installed (requires launching the installed Safestrap app) you *might* be able to flash another rom or repair FireOS. Long shot at best that could leave you with a brick. If you go this path know a factory reset/restore from the native recovery menu *will* brick the device (so don't do that).
Sorry for the bleak prognosis.
Davey126 said:
Appears you have done your homework and have tried most of the solutions I might have suggested. FireOS is intolerant of component name/permission changes (aside from one file dealing with OTA). Best option is to contact Amazon for a one time courtesy exchange if still in warranty.
As a last ditch effort you could try installing Safestrap v4 via adb. If you can get the recovery component installed (requires launching the installed Safestrap app) you *might* be able to flash another rom or repair FireOS. Long shot at best that could leave you with a brick. If you go this path know a factory reset/restore from the native recovery menu *will* brick the device (so don't do that).
Sorry for the bleak prognosis.
Click to expand...
Click to collapse
Thanks man. Yeah, I'm not new to the whole rooting/linux thing, however KINDLE FIRE OS IS The most garbage version of Android I've ever dealt with. I read numerous warnings about bricking, but decided to try anyways.
I tried many more things last night and actually had some luck with pushing commands through ADB to start ES File Explorer from the settings screen, I was able to open apps through ES and manged to get a lot done, however I couldn't get the softkeys/ui keys to appear no matter what I did.
I could power the screen down and it would open back up to ES or whatever App I had opened before "locking" the screen, but Once again I hit a Wall. I checked it this morning, and somehow I got stuck at a black screen when I hit the power button, and now Im stuck in recovery with no option to fastboot.
The Fire is recognized as "Fire" in Device Manager, however I can't seem to get it recognized in ADB to use a Recovery tool or push the Stock OTA rom to the system.
Is there any way of accessing ADB, or enabling USB via Recovery screen?
OR is there a tool similar to ODIN I can use to rebuild, fix up my current OS using adb or usb as mentioned above?
Mcfinnipoop said:
Thanks man. Yeah, I'm not new to the whole rooting/linux thing, however KINDLE FIRE OS IS The most garbage version of Android I've ever dealt with. I read numerous warnings about bricking, but decided to try anyways.
I tried many more things last night and actually had some luck with pushing commands through ADB to start ES File Explorer from the settings screen, I was able to open apps through ES and manged to get a lot done, however I couldn't get the softkeys/ui keys to appear no matter what I did.
I could power the screen down and it would open back up to ES or whatever App I had opened before "locking" the screen, but Once again I hit a Wall. I checked it this morning, and somehow I got stuck at a black screen when I hit the power button, and now Im stuck in recovery with no option to fastboot.
The Fire is recognized as "Fire" in Device Manager, however I can't seem to get it recognized in ADB to use a Recovery tool or push the Stock OTA rom to the system.
Is there any way of accessing ADB, or enabling USB via Recovery screen?
OR is there a tool similar to ODIN I can use to rebuild, fix up my current OS using adb or usb as mentioned above?
Click to expand...
Click to collapse
Sorry - afraid I can't be of much help. The latest situation is not uncommon after a reboot on a borked device. There is no way to enable adb via stock recovery; would be a security risk even if available. Amazon devices are unique beasts; many common recovery tools/techniques don't work due to component selection and a restrictive bootloader. Even if you did regain limited control pushing an OTA image via ADB would not cause it to be processed as you would need a higher version of FireOS than what's already on your device (4.5.5.1); none exist at present aside from v5. With one exception lower (rollback) versions are summarily dismissed.
Mcfinnipoop said:
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Click to expand...
Click to collapse
ok this may sound silly but there were 2 things i did to fix a friends kindle stuck on the settings screen as u describe, I went to applications and under that went to the default silk web browser then to most visited , and yahoo link which allowed me to get to the internet and download and install custom notification apk can be found here https://globalapk.co/apk/1/9085-custom-notification-ex-v221 from there it opened and i was able to place the alternate launcher i had adb installed as a shortcut in notification area which allowed me to navigate, and open the alternate launcher and had some control on device, I also think that simply going to an apk site you trust and installing an alternate launcher like that should also work it should pop right up after install depending on how bad your situation is or what was done with the specific kindle, just thought id give some suggestions for alternate way to perhaps fix it gain control over system again it may not work though, hope that helps.
Hopefully this will work
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
This is a nice write-up that will likely help someone in a similar situation. Thanks for posting
You can help me?
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
I try to do what you write in this tutorial. But when i reboot in recovery after i installed the safetrap, my kindle go reboot, and display kindle fire for a long, and nothing happen.
Another problem, when i instal de supersu, after i try to remove kingroot and not work, i have only force stop, clear data and clear cache allowed to press.
Thank you
Hello Mcfinnipoop,
I encountered the same problem as you, have you resolved the problem yet? I would appreciate it if you could tell me how to fix it.
Thanks!
VoadekS said:
I try to do what you write in this tutorial. But when i reboot in recovery after i installed the safetrap, my kindle go reboot, and display kindle fire for a long, and nothing happen.
Another problem, when i instal de supersu, after i try to remove kingroot and not work, i have only force stop, clear data and clear cache allowed to press.
Thank you
Click to expand...
Click to collapse
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
It works for me. Thanks!