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?
Related
*** 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
***PLEASE UNLOCK YOUR BOOTLOADER INSTEAD. ***
*** IF ANY OF THE INFORMATION ON THIS THREAD IS MISUSED IT CAN RESULT IN A BRICKED DEVICE ***
Introduction
- BEFORE PROCEEDING READ THROUGH CAREFULLY, IF THERE IS ANY DOUBT THEN ASK BEFORE PROCEEDING
- Safestrap provides TWRP like recovery capabilities for locked devices.
- This is based on the original work of Hashcode.
- This is for Apollo and Thor devices only.
Known Issues
- Secondary slots boot, but the WiFi module does not load
- Since the secondary slots work but have no WiFi, you will need to flash Nexus v4 to the stock slot for now
Compatible ROMS
- HDX Nexus ROM v4
- CM-11
- Fire Nexus ROM
Prerequisites for Installation
- You must be on FireOS stock firmware 4.5.2, 4.5.3, 4.5.4, 4.5.5 or 4.5.5.1 <- Please confirm this before proceeding <-
- You must have root access
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
- You should eventually end up in safestrap recovery.
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Thanks to my Testers
- Davey126
- kudoz83
- lekofraggle
- zamtang
- paul26rem
XDA:DevDB Information
Safestrap KK, Device Specific App for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Current Stable Version: 4.0.1
Stable Release Date: 2015-06-18
Created 2015-06-18
Last Updated 2019-10-02
Reserved
Is there a possibility of running cm 12 in this recovery?
paul26rem said:
Is there a possibility of running cm 12 in this recovery?
Click to expand...
Click to collapse
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
ggow said:
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
Click to expand...
Click to collapse
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Davey126 said:
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Click to expand...
Click to collapse
I agree. Don't get me wrong, I love cm, but If you want a stable Rom, Nexus is where it's at.
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
thuyrs said:
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
Click to expand...
Click to collapse
Can you get into Safestrap recovery? If so try a 'factory reset' located under the 'wipe' option and then reboot. If that does not work return to Safestrap recovery and perform an 'advanced wipe'. Check all of the partitions (Dalvik Cache, Data, Cache, System). After wiping reinstall Nexus v4 and gaps from within Safestrap and then reboot.
A few cautions/notes:
- make sure you are working with the correct slot!
- make sure you perform the 'factory reset' from safestrap recovery - not the native Amazon recovery built into your Kindle
- gaps is important for proper operation of Nexus v4. Some low level functions (eg: the home button) do not work correctly if gaps is not flashed immediately after Nexus v4
Please post the results to others can learn from your experience. Thanks!
Hi, after I wiped everything and reinstall to slot stock, it booted, and Wifi module worked correctly, thanks for your help!
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
loco09 said:
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
Click to expand...
Click to collapse
Flash SuperSU after and you have root access.
Also you will need to block ota updates so do not enable WiFi until you have done so.
EDIT: I have just added a note to the OP about this.
Sent from my Nexus 6 using Tapatalk
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
hfpop said:
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
Click to expand...
Click to collapse
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Davey126 said:
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Click to expand...
Click to collapse
Just to add to what Davey126. My current understanding is that a manual upgrade does indeed work. 3.2.8 only stops the OTA updates from coming through.
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
ChuTeng said:
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
Click to expand...
Click to collapse
Can you still get into Safestrap?
ggow said:
Can you still get into Safestrap?
Click to expand...
Click to collapse
adb driver in my computer is problem, i fixed. Thanks.
ChuTeng said:
adb driver in my computer is problem, i fixed. Thanks.
Click to expand...
Click to collapse
Does that mean you are up and running again?
Awesome job!!!!!!!!!!
Confirmation number: 67M75398MF9375820
I'm on 4.5.4 7", any options for me? Can I contact amazon n hope they will roll me back? What version do I ask for?
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.
Hello out there I looked for a thread on this subject and I didn't see one so I apologize to the mods if this has been covered.. Anyways today I received a notification for a System update on my Turbo. I haven't tried to install it yet. Right now my bootloader is unlocked via the Sunshine apk I have TWRP installled as my custom recovery and I have root. Basically I'm running stock but rooted. What is the upgrade procedure. I'm pretty sure the update will fail with twrp installed. Is there a set procedure everyone is using... Thanks in advance
tombaldwin6 said:
Hello out there I looked for a thread on this subject and I didn't see one so I apologize to the mods if this has been covered.. Anyways today I received a notification for a System update on my Turbo. I haven't tried to install it yet. Right now my bootloader is unlocked via the Sunshine apk I have TWRP installled as my custom recovery and I have root. Basically I'm running stock but rooted. What is the upgrade procedure. I'm pretty sure the update will fail with twrp installed. Is there a set procedure everyone is using... Thanks in advance
Click to expand...
Click to collapse
Backup apps via titanium backup, and save off the phone. Backup all personal files, pics etc, off the phone. Flash a stock ROM in TWRP, wipe dalvik & cache. Then flash stock '49' recovery using ADB. Power up normally & take update. It should execute flawlessly. You could also flash the stock firmware for marshmallow via RSDlite, but that will wipe your data off the phone. Bootloader will still remain unlocked so you can Flash TWRP back on afterwards. Root can only be restored by flashing a particular beta version in TWRP. Better details and download links in the XDA forum thread for droid turbo.
USE THE TWRP-FLASHABLE VERSION OF UPDATE
tombaldwin6 said:
today I received a notification for a System update on my Turbo. Right now my bootloader is unlocked via the Sunshine apk I have TWRP installed as my custom recovery and I have root. Basically I'm running stock but rooted. What is the upgrade procedure.
I'm pretty sure the update will fail with twrp installed. Is there a set procedure everyone is using... Thanks in advance
Click to expand...
Click to collapse
Congratulations on having an unlocked bootloader! No need to do all that above, unless you really want. There's also a TWRP-flashable version on that update already posted in this forum. Just flash it in TWRP. It's the full update, minus stock recovery so you can keep TWRP and also flash it in TWRP!
@TheSt33v, who wrote the guide in this forum about unlocking the Droid Turbo bootloader is who posted it, so you can trust it.
[ROM] MCG24.251-5 100% Stock
https://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
All updates like that will ALWAYS be posted here in various formats. Never any need to take an OTA. That's one of the great things about XDA.
____________
Also, there's a TWRP-flashable stock-based Verizon Marshmallow ROM by @computerfreek274. It's basically this Verizon Marshmallow update but tweaked, optimized, debloated.
Computerfreek274_MM_1.0.4 Marshmallow 6.0.1 Stock rooted VOLte Debloated
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
1.0.4 Change Log
Native Tether. (Tested and Working)
Audio Boost In call volume. "Fixed in 1.0.4 Lowed down from 94 to 90 Stock is 84 to avoid echo when volume was up to full."
Audio Boost Media Audio.
De-Bloated.
Removed Some Google apps like YouTube ,books,games,videos,Google Photos, Slacker radio, NFL Game,Verizon Cloud, Google pay and and some Verizon apps. Plus the demo stuff and mp4's also removed all amazon junk.
init.d Support.
Tweaks for speed.
Tweaks For battery life
.
Click to expand...
Click to collapse
Before rooting/removing ads etc, I want to use the phone for a week or so stock so Ill have a baseline to compare it to.
Would it be OK to let the phone update fully while using it? I know with some devices (Amazon kindle) if you update it to a certain point, then there is no going back and the bootloader gets locked.
Lemme know what you think.
lourivellini said:
Before rooting/removing ads etc, I want to use the phone for a week or so stock so Ill have a baseline to compare it to.
Would it be OK to let the phone update fully while using it? I know with some devices (Amazon kindle) if you update it to a certain point, then there is no going back and the bootloader gets locked.
Lemme know what you think.
Click to expand...
Click to collapse
If you allow it to update, you will not be able to unlock bootloader, so if you want to root do not update.
The latest update has been posted in this forum, so you are not missing any of the update by rooting either.
mrmazak said:
If you allow it to update, you will not be able to unlock bootloader, so if you want to root do not update.
The latest update has been posted in this forum, so you are not missing any of the update by rooting either.
Click to expand...
Click to collapse
Is the root junky method still good?
https://youtu.be/KMobKWfZbJg
Or should I follow a different guide? I know some of his files on his website are outdated.
I also am having a problem when trying to use the flashtool. When I plug my phone in powered off, at first it says the battery is low no matter what, then disconnects, then says 95% or whatever it is. This is preventing me from using flashtool when in download mode.
Any idea why this is happening? My r1 hd is on 6.0 btw
lourivellini said:
Is the root junky method still good?
https://youtu.be/KMobKWfZbJg
Or should I follow a different guide? I know some of his files on his website are outdated.
I also am having a problem when trying to use the flashtool. When I plug my phone in powered off, at first it says the battery is low no matter what, then disconnects, then says 95% or whatever it is. This is preventing me from using flashtool when in download mode.
Any idea why this is happening? My r1 hd is on 6.0 btw
Click to expand...
Click to collapse
All the R1-HD line is on Android 6.0
The Blu release version is what changes.
I believe this was the order
6.1
6.4
6.5
6.6
7.4.2
8.3
8.4
The flashtool stopped working at v6.6
The new method was the use dirty cow. There is a tool thread for directions.
This new method stopped working at v8.3
mrmazak said:
All the R1-HD line is on Android 6.0
The Blu release version is what changes.
I believe this was the order
6.1
6.4
6.5
6.6
7.4.2
8.3
8.4
The flashtool stopped working at v6.6
The new method was the use dirty cow. There is a tool thread for directions.
This new method stopped working at v8.3
Click to expand...
Click to collapse
So the phone is brand new from Amazon, haven't touched it or even connected it to the internet. Not home right now, but I remember seeing software version 6.0 not Android 6.0.
Anyways, I guess I should look into the dirty cow method. Do you have the link?
Sent from my Moto G (5) Plus using Tapatalk
lourivellini said:
So the phone is brand new from Amazon, haven't touched it or even connected it to the internet. Not home right now, but I remember seeing software version 6.0 not Android 6.0.
Anyways, I guess I should look into the dirty cow method. Do you have the link?
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
mrmazak said:
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
Click to expand...
Click to collapse
Thanks
Sent from my Moto G (5) Plus using Tapatalk
mrmazak said:
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
Click to expand...
Click to collapse
Is there a ROM i should flash afterwards?
I just installed twrp using the dirty cow method (steps 1-4), and then also did step 5-1 (install supersu).
At this point, in the past Ive always just flashed a brand new rom and gapps. Is there a "stock" rom that I should flash with twrp - which is just the stock rom with no ads? And which build should I? Im on 6.6 right now.
Ive read that lineage has some problems with the camera - no big deal ill roll will the stock non-ad rom for now.
Thanks again!
lourivellini said:
Is there a ROM i should flash afterwards?
I just installed twrp using the dirty cow method (steps 1-4), and then also did step 5-1 (install supersu).
At this point, in the past Ive always just flashed a brand new rom and gapps. Is there a "stock" rom that I should flash with twrp - which is just the stock rom with no ads? And which build should I? Im on 6.6 right now.
Ive read that lineage has some problems with the camera - no big deal ill roll will the stock non-ad rom for now.
Thanks again!
Click to expand...
Click to collapse
So the non-prime ROMs latest is v21 it comes with none of the prime ads.
Or v8.4 that came with the ads but they were removed. .some have said n-ify not working on 8.4 but does on 21. I do not know first hand.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
You will have to do SuperSU again after the rom
mrmazak said:
So the non-prime ROMs latest is v21 it comes with none of the prime ads.
Or v8.4 that came with the ads but they were removed. .some have said n-ify not working on 8.4 but does on 21. I do not know first hand.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
You will have to do SuperSU again after the rom
Click to expand...
Click to collapse
Last question(s):
So I installed V21, supersu, removed ALL amazon with dirtycow.
1. Is my phone now disabled from receiving OTA updates? Or do I have to do something else to make sure auto updates are OFF.
2. Is there a way to remove this stupid blu app (blu help) that keep requiring me to register my device? Every time I power on I have to force stop the app or I have a constant notification to do it.
Thanks again!
lourivellini said:
Last question(s):
So I installed V21, supersu, removed ALL amazon with dirtycow.
1. Is my phone now disabled from receiving OTA updates? Or do I have to do something else to make sure auto updates are OFF.
2. Is there a way to remove this stupid blu app (blu help) that keep requiring me to register my device? Every time I power on I have to force stop the app or I have a constant notification to do it.
Thanks again!
Click to expand...
Click to collapse
The debloat done with the tool supposed to have disabled the ota checker program.
And as a second method of not getting ota, having twrp and root will also make the ota fail even if it was to download.
The Blu app is called warrenteer. What I do is belete the whole folder.
/system/priv-app/warrenteer
You can take baby steps and just rename the apk inside that folder to add "-" or "_" to end of it's name
This can be done with a root explorer app or with recovery file manager. Either way.