Database Develop

Safestrap Flashable HDX Stock Images

*************************************************************
INCORRECT USE OF THESE FILES WILL BRICK YOUR DEVICE
PLEASE ENSURE YOU KNOW WHAT YOU ARE DOING AND
I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
*************************************************************
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
- Do NOT use these images to downgrade or upgrade your base firmware.
I will be uploading them as and when I have time.
Thor Images:
- 13.3.1.0 <- Flashable on Safestrap 3.7.2
- 13.3.2.6 <- Flashable on Safestrap 3.7.5
*** THESE ONES DO NOT HAVE ROOT OR BLOCK UPDATES ***
- 13.4.5.2 <- Flashable on Safestrap v4.0.1
Apollo Images:
- 14.3.1.0 <- Flashable on Safestrap 3.7.2
- 14.3.2.6 <- Flashable on Safestrap 3.7.5
*** THESE ONES DO NOT HAVE ROOT OR BLOCK UPDATES ***
- 14.3.2.8 <- Flashable on Safestrap v3.7.5
- 14.4.5.2 <- Flashable on Safestrap v4.0.1
If you want to re-enable over the air updates then do the following:
- Skip this if you are using the 4.5.2 files - As stated above this does not apply so be careful.
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk

ggow said:
Hi All,
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
I will be uploading them as and when I have time.
Thor Images:
- 13.3.1.0
Apollo Images:
- 14.3.1.0
If you want to re-enable over the air updates then do the following:
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
Click to expand...
Click to collapse
Excellent! I am able to revert back to this stock firmware after nearly bricking my device. Thank you!!

Since I"m heavily tied into the Amazon ecosystem and have other Kindle devices, installing HDX Nexus 2.01 didn't work for me.
However, thanks to @ggow, using the same upgrade guide, Iwas able to get my 3.1.0 to 3.2.6, allowing my fire hdx devices to finally be able to do screen sharing with my fire TVs! I did have to restore /data, enable xposed + hdxposed, re-install kindlefree + Google play store APKs & stucks wallpaper fix to be back at 100%...

Will you make a pre rooted 4.5.1 image for the HDX 7.0 Thor?
Can I flash this over a Stock 4.5.1 device?

D0ubl3_X said:
Will you make a pre rooted 4.5.1 image for the HDX 7.0 Thor?
Can I flash this over a Stock 4.5.1 device?
Click to expand...
Click to collapse
As of right now, it's impossible to root 4.5.1.
No, you can't flash them over a newer version just like that. If you want to downgrade, check this thread.

Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?

_Alex_ said:
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
Click to expand...
Click to collapse
Hi _Alex_, yes I'll sort one out for you.
ggow

I goofed - flashed the apollo zip over my already properly up(down)graded stock. Now of course I get a blank screen when trying to boot the stock - not that I do it that often of course. I can still get into safestrap and boot the nexus 2.01 rom with no issues so am okay for now. Would I need something like a rooted 14.3.2.6 to fix this?

aren't these roms very old? Is there any way to get the latest AMAZON STOCK apps AND keep root? I really like the FIRE OS (way more than stock Android) but I also want all apps etc.

_Alex_ said:
Since I"m heavily tied into the Amazon ecosystem and have other Kindle devices, installing HDX Nexus 2.01 didn't work for me.
However, thanks to @ggow, using the same upgrade guide, Iwas able to get my 3.1.0 to 3.2.6, allowing my fire hdx devices to finally be able to do screen sharing with my fire TVs! I did have to restore /data, enable xposed + hdxposed, re-install kindlefree + Google play store APKs & stucks wallpaper fix to be back at 100%...
Click to expand...
Click to collapse
Was screen sharing to Fire TV not available on 13.3.2.3.2? Furthermore, what exactly does 13.3.2.6 offer that's new/improved? Does anyone have the changelog for this?

OK, so the LATEST FIRE OS Version that is rootable is "13.3.2.6" for the THOR device, is that correct? Or is there any other way to root a newer OS Version?´
Oh, and how can I flash this update? My device is rooted, but I have a very old OS Version on my kindle hdx.

Hey guys.. I screwed up.
I have a fire hdx Apollo that had been properly up(down)graded and running fine with 2.01. For some reason (and my lack of understanding the correct versions of things) I thought it would be a good idea to install the Apollo update on my stock rom. This of course has now caused boot loops on my stock boot but not my 2.01 boot.
Would love to be able to restore the stock as I do use some of the fire's capabilities from time to time. Sadly I did not do a backup before the update (kicks self furiously).
I DO have a backup from before the upgrade/downgrade so maybe I could restore that then push through the upgrade steps again or something. I'm worried that I will bork my safestrap or do something worse based on my proclivity for damage and chaos.
E.

_Alex_ said:
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
Click to expand...
Click to collapse
Hi _Alex_,
Sorry about the long wait, I have posted a zip for 14.3.2.6. See OP.

Hey @ggow,
Thanks for your hard work. Could you possibly make an image for 13.3.2.4 (Thor)? It would be nice to have along with Nexus HDX 2.0.2.

NextDroid said:
Hey @ggow,
Thanks for your hard work. Could you possibly make an image for 13.3.2.4 (Thor)? It would be nice to have along with Nexus HDX 2.0.2.
Click to expand...
Click to collapse
Yes, I'll sort one out for you. Let you know when its up.
Sent from my Nexus 6 using Tapatalk

Looks like we're going to need it with the new bootloader bypass!
Just to clarify because someone asked, users of the HDX Nexus ROM would need it to downgrade to a firmware that the unlock works on.

ggow said:
Yes, I'll sort one out for you. Let you know when its up.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Sent from my device

recreated the error with the Symlink. Crossposting from the TWRP Thor thread
Wiped system manually
The error log is:
Code:
Wiping system...
Symlinking...
symlink: some symlinks failed
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/TWRP13.3.1.0.zip'[/COLOR]
Error flashing zip '/sdcard/TWRP13.3.1.0.zip'
Updating partition details
Interesting... Getting the same error when I try to flash the original HDX 13.3.2.3 firmware, after I renamed it from .bin to .zip

Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
aquaphun said:
recreated the error with the Symlink. Crossposting from the TWRP Thor thread
Wiped system manually
The error log is:
Code:
Wiping system...
Symlinking...
symlink: some symlinks failed
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/TWRP13.3.1.0.zip'[/COLOR]
Error flashing zip '/sdcard/TWRP13.3.1.0.zip'
Updating partition details
Interesting... Getting the same error when I try to flash the original HDX 13.3.2.3 firmware, after I renamed it from .bin to .zip
Click to expand...
Click to collapse
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !

Cpasjuste said:
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Click to expand...
Click to collapse
Hi @Cpasjuste,
Yes that's fine, I'll put your 4.5.2 image up on the same thread - no point replicating things
On 4.5.2 I wasn't sure which services needed to be disabled to prevent OTA. I'll add a note for this file to warn people to be careful when using it.

[ROM] HDX Nexus [Safestrap Version] v1.0.1

*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Introduction
I am very proud to bring you HDX Nexus Safestrap ROM. This is for both the Kindle Fire HDX 7" and 8.9" WIFI only variants and brings full AOSP functionality which are using Safestrap. You must be running stock firmware .3.2.4 - 3.2.8
Click to expand...
Click to collapse
Features
- Full Jelly Bean 4.2.2 AOSP functionality
Click to expand...
Click to collapse
Bug Reports
- Please use the Bugs section on this thread, it will make it a lot easier to to keep track.
Click to expand...
Click to collapse
Fresh Installation
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
- Then flash any addons
- If coming from any other ROM then do a factory reset.
- Reboot and enjoy.
Click to expand...
Click to collapse
Upgrading From Previous Version
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
- Wipe Dalvik Cache and Cache
- Then flash any addons
- Reboot and enjoy.
Click to expand...
Click to collapse
Changelog
- x -> v1.0.1
Code:
- Initial Release.
- Branched from mainline HDX Nexus ROM v2.0.5
Click to expand...
Click to collapse
Downloads
- Safestrap Apollo Nexus ROM
- Safestrap Thor Nexus ROM
- Gapps 1.2
Click to expand...
Click to collapse
Add-Ons
- Dolby Digital v1.2
Click to expand...
Click to collapse
FAQ
TBD
Source Code
- Kernel Source: Kindle HDX stock kernel, build number 1314.3.2.4
Finally
- Thank you to everyone for your ongoing support and to everyone that made a Donation.
Click to expand...
Click to collapse
XDA:DevDB Information
HDX Nexus Safestrap, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: .3.2.4 - 3.2.8
Based On: AOSP JDQ39
Version Information
Status: Stable
Current Stable Version: 1.0.1
Stable Release Date: 2015-02-07
Created 2015-02-07
Last Updated 2016-02-10

Reserved

Reserved

Update
Hello All,
Files are now up

Ggow much appreciated that safetrap version is coming back!
Just to clarify that this rom will work with devices that got upgraded to 4.5.2 and then downgraded by ACS to 3.2.7/8 and rooted with safetrap working.
Here are some questions that I'm sure people will be curious about:
- I'm currently on 2.0.2 and root checker says root is enabled, but couldn't find the supersu app. How does it work? Do i need to flash supersu?
- Can you install xposed with modules on this version? For example to mod notifications bar, status bar, power menu, etc.
- can I safely upgrade from the older 2.0.2 to this version?
- what about addons like the dolby digital? I assume its safe to flash too?
- current build.prop ids the device as Nexus HDX and tgere are a lot of apps on play store that are not compatible with the device, but they work just fine installed from another market (say 1mobile). Can we do something about it?
Sorry for so many questions, but i tried reading most stuff from the other thread but for some reason search in thread is disabled (no idea why).
Cheerz!

Awesome, thanks!!!

johim said:
Ggow much appreciated that safetrap version is coming back!
Just to clarify that this rom will work with devices that got upgraded to 4.5.2 and then downgraded by ACS to 3.2.7/8 and rooted with safetrap working.
Correct, yes.
Here are some questions that I'm sure people will be curious about:
- I'm currently on 2.0.2 and root checker says root is enabled, but couldn't find the supersu app. How does it work? Do i need to flash supersu?
The ROM is pre-rooted with the su binary and a daemon. SuperSU is a root manager so its up to you if want that functionality.
- Can you install xposed with modules on this version? For example to mod notifications bar, status bar, power menu, etc.
Yes you can.
- can I safely upgrade from the older 2.0.2 to this version?
Yes
- what about addons like the dolby digital? I assume its safe to flash too?
Yes
- current build.prop ids the device as Nexus HDX and tgere are a lot of apps on play store that are not compatible with the device, but they work just fine installed from another market (say 1mobile). Can we do something about it?
No matter how I modify the build.prop, google play store ends up not playing nice. So no not at the moment. Market helper used to work for this problem but seems to but patched now on googles servers.
Sorry for so many questions, but i tried reading most stuff from the other thread but for some reason search in thread is disabled (no idea why).
Cheerz!
Click to expand...
Click to collapse
See my responses above. I'll add some information to the FAQ when possible.
Sent from my Nexus 6 using Tapatalk

OK, I updated and flashed all gapps and addons. Everything works!
Then I tried installing Xposed Framework, and on reboot the result was black screen after rom bootup (right after android animation). Waited like 2-3 minutes, but nothing. Then had to force reboot it via power button. After reboot everything works again with Xposed installed. No idea what happened. Any guidelines on where I can check logs probably.
havent tried any module yet, but it would be nice if we keep a list of compatible and safe modules.
Question: can any of the xposed modules trip eFuse or break stock kernel (as rom is running on top of it) or safetrap makes it safe so any changes to system would be just to the slot rom?

johim said:
OK, I updated and flashed all gapps and addons. Everything works!
Then I tried installing Xposed Framework, and on reboot the result was black screen after rom bootup (right after android animation). Waited like 2-3 minutes, but nothing. Then had to force reboot it via power button. After reboot everything works again with Xposed installed. No idea what happened. Any guidelines on where I can check logs probably.
havent tried any module yet, but it would be nice if we keep a list of compatible and safe modules.
Question: can any of the xposed modules trip eFuse or break stock kernel (as rom is running on top of it) or safetrap makes it safe so any changes to system would be just to the slot rom?
Click to expand...
Click to collapse
Use this verison of Xposed found here.
Try Gravitybox (JB).
I don't know if any of the modules can trigger the efuse. You are correct, in theory Safestrap makes it so that any changes should only occur in that slot.

So far this ROM has been excellent. Great job and thanks a lot!

I have the problem, that there is no Play Store and I can't install downloaded applications. I downloaded applications through the browser and when I try to execute them I get the error "can't open file". So I can literally install no app. I tried to install ES File Explorer and gapps pico.
Anyone else who had this problem or knows how to solve it or has some ideas?

faulix said:
I have the problem, that there is no Play Store and I can't install downloaded applications. I downloaded applications through the browser and when I try to execute them I get the error "can't open file". So I can literally install no app. I tried to install ES File Explorer and gapps pico.
Anyone else who had this problem or knows how to solve it or has some ideas?
Click to expand...
Click to collapse
Did you flash gapps?
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
Click to expand...
Click to collapse

Is this the only iteration of the ROM for 3.2.8?

jeryll said:
Did you flash gapps?
Click to expand...
Click to collapse
That's quite embarrassing, I forgot it and now everything works perfectly, thanks.
In case anyone else has the same problem, flash the gapps stuff in safestrap

Thank you for still supporting those of us stuck with safestrap only... lol

ggow said:
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Hi GGow, I'm a complete noob to the scene, have searched around the forums. Finally got Safestrap 3.75 and SuperSU working on my Amazon Kindle Fire HDX that was downgraded to 13.3.2.8 by ACS from 4.5.2. Utilized the TowelRoot method to get rooted.
I want to make sure the installation procedure for this ROM, since I've never done one. Currently I utilized SafeStrap 3.75 and backed up my stock 13.3.2.8 ROM on the device.
The process to install this ROM would be -
1. Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
2. Flash hdx-nexus-gapps-v1.2.zip
3. Then flash any addons
4. If coming from any other ROM then do a factory reset.
5. Reboot and enjoy.
My only issue is that do I flash all of these roms like the safestrap-thor-nexus-rom.zip onto seperate slots? Or keep re-flashing the same slot? I apologize for my noobness, but I'm really new to Android Dev and rooting.
Click to expand...
Click to collapse

All same slot.
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
Just queue them all up to flash all in one shot.

camerajunkie said:
ggow said:
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Hi GGow, I'm a complete noob to the scene, have searched around the forums. Finally got Safestrap 3.75 and SuperSU working on my Amazon Kindle Fire HDX that was downgraded to 13.3.2.8 by ACS from 4.5.2. Utilized the TowelRoot method to get rooted.
I want to make sure the installation procedure for this ROM, since I've never done one. Currently I utilized SafeStrap 3.75 and backed up my stock 13.3.2.8 ROM on the device.
The process to install this ROM would be -
1. Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
2. Flash hdx-nexus-gapps-v1.2.zip
3. Then flash any addons
4. If coming from any other ROM then do a factory reset.
5. Reboot and enjoy.
My only issue is that do I flash all of these roms like the safestrap-thor-nexus-rom.zip onto seperate slots? Or keep re-flashing the same slot? I apologize for my noobness, but I'm really new to Android Dev and rooting.
Click to expand...
Click to collapse
To add to what @gqukyo said:
1. If you intend for HDX Nexus ROM to be your main ROM and because you are on 13.3.2.8 I would make sure you take a backup of your current stock ROM.
2. Restore the backup to slot 1 . Ensure slot 1 then boots correctly
3. You can then switch back to your stock slot and follow the instructions above.
4. Otherwise if you want stock to be your main ROM then just follow the instructions as they are above after creating a new ROM slot.
Click to expand...
Click to collapse

ggow said:
camerajunkie said:
To add to what @gqukyo said:
1. If you intend for HDX Nexus ROM to be your main ROM and because you are on 13.3.2.8 I would make sure you take a backup of your current stock ROM.
2. Restore the backup to slot 1 . Ensure slot 1 then boots correctly
3. You can then switch back to your stock slot and follow the instructions above.
4. Otherwise if you want stock to be your main ROM then just follow the instructions as they are above after creating a new ROM slot.
Click to expand...
Click to collapse
Ha! I didn't even think to use the "stock rom" for any custom roms... I don't suppose it really matters does it? I did create the max 16gb for my rom slot though I did hear about people having issues installing games when it complained device didn't have enough space... if it does matter then I'd rather use the stock slot since there doesn't seem to be any other roms to try anyways.
Click to expand...
Click to collapse

I don't think he ment to replace your stock slot with custom rom.
I was wondering why would i restore stock backup to slot 1? Is this just to verify if backup works? Can i later remove it from slot 1.
It would take too much space to have a stock and slot 1 as stock and then slot 2 for nexus.
Fyi you can safely install Xposed 2.7 experimental and then activate gravitybox, and other aosp modules.
Sent from my Nexus HDX 7 using XDA Free mobile app

[ROM] [UNLOCKED BOOTLOADER] Fire OS 4.5.2

For anyone who has an unlocked bootloader and wants to update to Fire OS 4, here's a stock 4.5.2 ROM that won't overwrite your current unlocked bootloader or recovery partition.
DOWNLOAD HERE
All credit goes to Cpasjuste for the current version - I might be uploading 4.5.5 here soon.

bmccoy11 said:
For anyone who has an unlocked bootloader and wants to update to Fire OS 4, here's a stock 4.5.2 ROM that won't overwrite your current unlocked bootloader or recovery partition.
DOWNLOAD HERE
All credit goes to Cpasjuste for the current version - I might be uploading 4.5.5 here soon.
Click to expand...
Click to collapse
Any feedback on this ROM?
Can this be installed on its own? Can I wipe /system and install? Downloading now but figured I'd ask here.

riggsandroid said:
Any feedback on this ROM?
Can this be installed on its own? Can I wipe /system and install? Downloading now but figured I'd ask here.
Click to expand...
Click to collapse
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.

bmccoy11 said:
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
Click to expand...
Click to collapse
Right so when I borked my previous rom (ooooops) without a backup, this will give me stock Amazon rom back.
Thanks.
@bmccoy11
Ok so it flashed fine and I noticed you already did otacerts.old in /system/etc/security and I don't see the dcp apk in /system/app, however it tried DL'ing an update right away.
How do you recommend stopping OTAs?
Trying this method - http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550 - seems to work
Thanks.

bmccoy11 said:
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
Click to expand...
Click to collapse
Is the 4.5.5 build far away? Might give it a crack over the weekend if it will be up.

Yes, the 4.5.5 is available here, already OTA blocked. I had to do a factory reset after flashing it (use ONLY the factory reset within TWRP, NOT the native factory reset) to get it to work, but after that, clear sailing, works great.

Ok, I'm a little confused about the process. My kindle fire is sitting at 4.5.4. I have refused to turn it on, because I don't want it to take 4.5.5. I want to re-establish root. I understand there is a downgrade process that allows you to move back to 4.5.2, then you can install root.
My question is, how do I unlock the boot loader at this point? Do I need to have an unlocked boot loader to install new images. I really want to be able to root and have the google play store installed, and not have all the bull**** errors like before with the playstore crashing.
Thanks to all you guys that have the answers and knowledge.

rlkellyjr said:
Ok, I'm a little confused about the process. My kindle fire is sitting at 4.5.4. I have refused to turn it on, because I don't want it to take 4.5.5. I want to re-establish root. I understand there is a downgrade process that allows you to move back to 4.5.2, then you can install root.
My question is, how do I unlock the boot loader at this point? Do I need to have an unlocked boot loader to install new images. I really want to be able to root and have the google play store installed, and not have all the bull**** errors like before with the playstore crashing.
Thanks to all you guys that have the answers and knowledge.
Click to expand...
Click to collapse
You can not unlock the bootloader on that device as it can not be rolled back to a version of FireOS (3.2.3.2 or below) containing the vulnerability that the unlock procedure exploits. The lowest you can go is 3.2.8. Any attempt to go further will result in a brick.
To get to 4.5.2 you rollback to 3.2.8 first using the procedure in this thread. Follow instructions precisely or you can damage/brick your device. Understand there are risks involved; this is not a task for the uninformed. There are no step-by-step guides or slick videos. Copious reading is your best friend along with the community servicing HDX forums.
Once on 3.2.8 you can upgrade to 4.5.2, block OTA, root, install Safestrap v4 and then Nexus v4 or cm11 both of which give full access to the Google Play Store. I strongly advise against attempting to install the play store under FireOS. Amazon and Google components do not play nice. Best use a different rom.
Do some reading and decide if you are up for the adventure. Ask questions before acting. Make sure you fully understand the relevant tasks, expected outcomes and things you should never do (like enable WiFi while on 3.2.8 - instant brick).
Edit: Fixed typos...

Thanks! but i have a question, why CM ROM the sound quality is very bad, even i install Dolby.

a442509097 said:
Thanks! but i have a question, why CM ROM the sound quality is very bad, even i install Dolby.
Click to expand...
Click to collapse
Search the HDX LineageOS 14.1 thread; many claim Viper4 is a better solution. Seems a bit complicated to obtain/install but that may be a faux impression. I am satisfied with Dolby but don't demand much from my device from an audio performance perspective.

how to delete this reply…

a442509097 said:
Viper4 is same too, i think this is about audio drive problem, because i try 4.22 or 4.4.4 system(however custom) sound quality has enough bass.
Click to expand...
Click to collapse
Might reach out to those who have installed (and presumably customized) Viper4 for this device. They claim sound quality is equal to if not superior to stock FireOS v4 (4.4.x base). I did notice a mild degradation going from Fire Nexus KTU84Q (4.4.4) to Android 5+ but not enough to warrant additional actions beyond installation of Dolby for noise reduction (random pops during quiet passages) and extended volume range. The builds were heavily customized when development resources were heavily focused on ROM enrichment. Things are different now; you'll likely have to roll your own if you believe this issue is with core binaries. Third gen devices have been out of production for 2+ years.

You sure about that? Wikipedia page for the series is under the impression they're still producing and selling the 7 inch HDX (which never got a 4th gen release), at least for LTE users.

Insidious622 said:
You sure about that? Wikipedia page for the series is under the impression they're still producing and selling the 7 inch HDX (which never got a 4th gen release), at least for LTE users.
Click to expand...
Click to collapse
LOL - since when did Wikipedia become the definative resource for Amazon devices? 3rd gen HDX is definitely out of production and has been for quite some time.

Fair enough, I just wasn't sure. Sometimes it's accurate, sometimes it isn't

Hi guys i need a zip or a backup. fore the orginal apollo room. i delet the backup fore safetrap and now i stuck at cm 4.4.4 and i will unlock my bootloader and install a other room but i need a orginal apollo backup or a zip to flash.

Serbest955 said:
Hi guys i need a zip or a backup. fore the orginal apollo room. i delet the backup fore safetrap and now i stuck at cm 4.4.4 and i will unlock my bootloader and install a other room but i need a orginal apollo backup or a zip to flash.
Click to expand...
Click to collapse
Bootloader can be unlocked while using CM 11 (KitKat 4.4.4) under Safestrap. Just follow the instructions. No need to reload FireOS.

Davey126 said:
Bootloader can be unlocked while using CM 11 (KitKat 4.4.4) under Safestrap. Just follow the instructions. No need to reload FireOS.
Click to expand...
Click to collapse
I need help while I understand the service not quite? How do I create this unlock file?
i follow this instruktion https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 and i have now install twrp and need now the unlock file.

texmexdud said:
Yes, the 4.5.5 is available here, already OTA blocked. I had to do a factory reset after flashing it (use ONLY the factory reset within TWRP, NOT the native factory reset) to get it to work, but after that, clear sailing, works great.
Click to expand...
Click to collapse
Links to that one are dead, could you please give up to date links?

Xposed on SlimLP?

Has anyone managed to get it working? I just tried to install via FlashFire and wound up getting an animation loop on the SlimLP boot logo. I applied the 5.1.1 firmware through the "apply update through adb" option in the recovery, can anyone confirm Xposed even working on SlimLP?

I'd like to know this also. Have not tried it yet.

I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.

Thanks! Think I found an easier solution than installing Xposed for what zip needed though (just needed YouTube to play in the background). That will come in handy if I want it later for any reason though.

Yes, xposed works fine. Big thanks to csolanol!
You must use the xposed compatible SlimLP 0.13 build + the correct xposed version (see the howto xposed thread in Fire General forum).

Anybody had success with getting .013 build running successfully with eXposed.. I've tried the ' Slim-ford-5.1.1.beta.0.13-UNOFFICIAL-20151221-0949.zip ' build from root junkies tutorial i think in section 4 or something if i remember vaguely, but with no luck... The Flash just proceeds as expected then reboots while opening/loading .zip.. But the standard release 'non-eXposed' runs without any problems.

Need to include more information. You're flashing with twrp or flashfire? If you used flashfire, what are you coming from? Stock 5.1.1 or another rom.
Do you mean after flashing the rom your Fire will not boot / start up?
I flashed SlimLP 0.13 via twrp without a problem on two different Fires. Xposed runs fine.

thanks for your reply, I'm flashing with flashFire from a r00ted fresh clean stock fire-os 5.1.1 on Amazon Fire 7" 5th Gen. i execute flash after selecting wipe all partitions except sd and then load .zip via ota then push button to commence flash, it proceeds to blank screen and then flashing screen and begins to attempt rom install i see rom info and 'char pic' of rom then it self terminates and reboots to existing r00ted fire-os, i do this exact same process with the rom not currently supporting Xposed from rootjunkie download site, and everything completes successfully spending a slightly longer period at the rom install/upload stage completing successfully with slimlp running nice... minus a few almost irrelevant bugs i noticed...
Twrp via adb doesn't work with 5.1.1 right? only works on 5.0.1&2? .. unless im mistaken.. any ideas?

Yep, we can't use twrp on 5.1.1.
So you select to wipe, system data, 3rd party apps, dalvik cache, cache partition, correct? I'm afraid I have no suggestions.

exactly that's correct , then i select rom, then i select gapps. then press flash button and it halts on the next screen as it begins to flash rom and quits to a reboot .. everything still unchanged as it was.. i have tried this process installing from stock os fire 5.1.1 & slimlp 5.1.1 with unsuccessful results.. but hey at least i have a SlimLp non-Xposed edition installed that beats Fire-BS#"*t any day. guess I'll have to wait for a new build to be released. bummer.
---------- Post added at 12:32 ---------- Previous post was at 12:25 ----------
in the future i guess more concentration is needed on the 5.1.1 Xposed edition skimlp rom to be flashed from 5.1.1 stock, for the true android custom eXperience .. i have also seen a fw roll back to 5.0.1or5.0.2 is not possible from any 5.1.1 os. never mind.

What I find is odd is that you've selected to wipe first. Flashfire should be wiping before trying & failing to flash SlimLP 0.13, leaving your Fire wiped & unable to boot back into the stock FireOS (you would then need to restore FireOS 5.1.1 via adb sideload in the amazon recovery). FlashFire is in beta & I think it's currently a bit buggy.

Bib_x said:
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
Click to expand...
Click to collapse
Sorry, I feel I joined the conversation mid-way but, which SlimROM thread are you talking about?

There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.

Bib_x said:
There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.
Click to expand...
Click to collapse
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge

marcolorenzo said:
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge
Click to expand...
Click to collapse
Maybe try looking in the Note Edge forum not the Amazon Fire one?

Pond-life said:
Maybe try looking in the Note Edge forum not the Amazon Fire one?
Click to expand...
Click to collapse
Maybe you shouldn't presume, with no information, that people are imbeciles? Don't you think I would've have done that at the beginning? Anyway, I may be wrong but I presumed that whether or not Xposed worked was more dependent on the ROM and not the phone? So if people here, who are discussing Xposed on SlimROM can help me, why not ask?

Bib_x is correct, i confirm Xposed working on slimlp build 0.14 beautifully for Fire 7 5th Gen.. be wary of modules you install other wise you'll have to start everything from scratch when you reach a boot hang because of a not yet compatible module.. you have no custom recovery remember so no quick fix, can always fresh install everything lol., which is good training lol.

Has anybody seen this "incompatible data" error when installing rom using Flashfire?

Has anybody seen this "incompatible data" error when installing rom using Flashfire?
I recently purchased a fire 7 which came with fireOS 5.1.4 on it which I downgraded to 5.1.2 (verified version in settings). I used KingRoot to get root and have verified that apps require root are working. I installed Flashfire and everything appears to work fine until I select flash. I can see it does the wipes fine, but when it tries to install cyanogenmod I receive an error that says "can't install package on top of incompatible data."
Has anybody seen this issue before in flashfire? I've been looking for some time now and I seem to be alone.
Things I have tried so far (which have not changed the error is see when flashfire is flashing CM and GAPPS):
Reset device to factory defaults (in settings and through recovery; loaded into 5.1.2 like it was new however it still had root)
Sideloaded Fireos 5.1.2 again and rerooted using kingroot.
Used a different version of CM.
Used different versions of Flashfire (0.5 and 0.51)
Went through the process start to finish again using the Supertool
I've been stuck on this for the last 5 hours... Any hints would be appreciated.
Update: I've had success at flashing the Fire Nexus ROM by ggow (http://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/). I have tried to flash the latest CM and the stable release from November without success. I suppose I might be satisfied with the nexus rom. It seems sexy enough.

LazyTurtle said:
I recently purchased a fire 7 which came with fireOS 5.1.4 on it which I downgraded to 5.1.2 (verified version in settings). I used KingRoot to get root and have verified that apps require root are working. I installed Flashfire and everything appears to work fine until I select flash. I can see it does the wipes fine, but when it tries to install cyanogenmod I receive an error that says "can't install package on top of incompatible data."
Has anybody seen this issue before in flashfire? I've been looking for some time now and I seem to be alone.
Things I have tried so far (which have not changed the error is see when flashfire is flashing CM and GAPPS):
Reset device to factory defaults (in settings and through recovery; loaded into 5.1.2 like it was new however it still had root)
Sideloaded Fireos 5.1.2 again and rerooted using kingroot.
Used a different version of CM.
Used different versions of Flashfire (0.5 and 0.51)
Went through the process start to finish again using the Supertool
I've been stuck on this for the last 5 hours... Any hints would be appreciated.
Update: I've had success at flashing the Fire Nexus ROM by ggow (http://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/). I have tried to flash the latest CM and the stable release from November without success. I suppose I might be satisfied with the nexus rom. It seems sexy enough.
Click to expand...
Click to collapse
Quick post to verify you are including a wipe action in FlashFire 0.51 with System, User Data, Dalvik and Cache ticked positioned *above* the rom flash action.

Same problem
Davey126 said:
Quick post to verify you are including a wipe action in FlashFire 0.51 with System, User Data, Dalvik and Cache ticked positioned *above* the rom flash action.
Click to expand...
Click to collapse
I am not OP, but I am having a similar problem after a failed ROM installation. I can verify that when I tried the steps listed, it did not work. The Nexus build, while quite nice, doesn't support loading apps onto the SD card yet, so it's not a long term solution for me.

SimonHova said:
I am not OP, but I am having a similar problem after a failed ROM installation. I can verify that when I tried the steps listed, it did not work. The Nexus build, while quite nice, doesn't support loading apps onto the SD card yet, so it's not a long term solution for me.
Click to expand...
Click to collapse
Lollipop based support for installing/migrating apps to SD cards is sketchy regardless of rom. Recommend using a tool that leverages 'symbolic links' which is both reliable and robust. Link2SD is one example.

I am having this exact same problem.
I've successfully downgraded from 5.1.3 to 5.1.2.
ROOT
Now using fireflash I am using the newest CM12 build and Google apps but get the same problem.
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Very frustrating....
Havent tried the Nexus rom yet, but any suggestions as the best alternative to CM as i also do not like the fireOS at all.

ratbrain said:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Click to expand...
Click to collapse
Did you add a wipe action (system/data/dalvik/cache) *above* the installation action in FlashFire? Pretty important going to/from FireOS.

Davey126 said:
Did you add a wipe action (system/data/dalvik/cache) *above* the installation action in FlashFire? Pretty important going to/from FireOS.
Click to expand...
Click to collapse
Yes. made sure to drag wipe action to top of the queue.
THis puts my fire into boot loop/ amazon logo stuck status

ratbrain said:
Yes. made sure to drag wipe action to top of the queue.
THis puts my fire into boot loop/ amazon logo stuck status
Click to expand...
Click to collapse
Obviously CM is not flashing correctly. You will need to reload FireOS 5.1.2 (or 5.3.1) via stock recovery to recover your device.
CM flash failures are not common suggesting a procedural or image integrity problem. Be sure to verify CM file md5 on the device. Use the SuperTool to root and perform other house keeping tasks. Grab the latest FlashFire build from APKMirror or another trusted source. Accept all defaults...some early guidance advised flipping various FF options which is no longer needed. You'll also want to flash GAaps (nano) concurrent with ROM; adding later is problematic. No need for SuperSU; can add later.

Davey126 said:
Obviously CM is not flashing correctly. You will need to reload FireOS 5.1.2 (or 5.3.1) via stock recovery to recover your device.
CM flash failures are not common suggesting a procedural or image integrity problem. Be sure to verify CM file md5 on the device. Use the SuperTool to root and perform other house keeping tasks. Grab the latest FlashFire build from APKMirror or another trusted source. Accept all defaults...some early guidance advised flipping various FF options which is no longer needed. You'll also want to flash GAaps (nano) concurrent with ROM; adding later is problematic. No need for SuperSU; can add later.
Click to expand...
Click to collapse
I've confirmed the files.
Using latest CM 12 ROM
Using FlashFire 0.53
Only difference Ive used is PICO Gapps.
All after restoring back to 5.1.2
Then ROOT with SuperTool
Note: per the OP, I am also successful in loading the NEXUS ROM. However, the CM Rom always ends up with the error.

ratbrain said:
I've confirmed the files.
Using latest CM 12 ROM
Using FlashFire 0.53
Only difference Ive used is PICO Gapps.
All after restoring back to 5.1.2
Then ROOT with SuperTool
Note: per the OP, I am also successful in loading the NEXUS ROM. However, the CM Rom always ends up with the error.
Click to expand...
Click to collapse
If you're happy with Nexus stick with it. It is my favorite rom for Amazon tablets and the one I prefer as my daily driver. I run CM on this device (5th gen Fire) as it is secondary and contains some nice usability enhancements that take time to apply on Nexus.
As for CM have to see what shakes out over time. Others are not reporting issues; send 3-4 reports of successful installations in the past 24 hours. At least one was on a 5.1.2 base (bootloader/kernel).