Rooted my 8.9 on version 14.3.1. In order to get prime music I was considering un-rooting, letting it update to 14.3.2.4 and re-rooting. Has anyone done this?
Any risk or downside? Is there another way to get prime music?
rootnooby said:
Rooted my 8.9 on version 14.3.1. In order to get prime music I was considering un-rooting, letting it update to 14.3.2.4 and re-rooting. Has anyone done this?
Any risk or downside? Is there another way to get prime music?
Click to expand...
Click to collapse
I have an 8.9 HDX. I unrooted mine and upgraded to get Prime music and then used towel root to re-root and installed xposed. Had no issues and then I also unrooted and installed the latest update to get better wifi. However there is a rumor going around that a their is an exploit to unlock the bootloader that does not work on the latest update. Since I do not care about a unlocked bootloader I upgraded to latest firmware and re-rooted with towel root and reinstalled xposed and updated su binaries. I have had no issues and all google and amazon services work without a problem. Also, I had to leave mine connected to wifi after the firmware upgrade to get the prime music installed. I believe on mine it installed around 4 hours later.
http://forum.xda-developers.com/kindle-fire-hdx/general/warning-update-to-13-3-2-4-t2802320
BroncoAG said:
I have an 8.9 HDX. I unrooted mine and upgraded to get Prime music and then used towel root to re-root and installed xposed. Had no issues and then I also unrooted and installed the latest update to get better wifi. However there is a rumor going around that a their is an exploit to unlock the bootloader that does not work on the latest update. Since I do not care about a unlocked bootloader I upgraded to latest firmware and re-rooted with towel root and reinstalled xposed and updated su binaries. I have had no issues and all google and amazon services work without a problem. Also, I had to leave mine connected to wifi after the firmware upgrade to get the prime music installed. I believe on mine it installed around 4 hours later.
http://forum.xda-developers.com/kindle-fire-hdx/general/warning-update-to-13-3-2-4-t2802320
Click to expand...
Click to collapse
Thanks. I am in a similar position to you I don't have much interest in custom roms. Can you outline the steps you used to Un-root? Did you Uninstall exposed first and then use super su to clean up and un root? I want to make sure I get the steps correct.
All I did was root, install gapps, xposed, and play store.
rootnooby said:
Thanks. I am in a similar position to you I don't have much interest in custom roms. Can you outline the steps you used to Un-root? Did you Uninstall exposed first and then use super su to clean up and un root? I want to make sure I get the steps correct.
All I did was root, install gapps, xposed, and play store.
Click to expand...
Click to collapse
I don't know if this is the correct way but this is what I did. I just ran the system update and installed the latest firmware. After the install the HDX is unrooted. I then ran towel root. After the reboot I ran xposed and reinstalled the framework and modules and then rebooted. After that I ran supersu and updated the binaries. Everything worked for me after that. I did not have to uninstall anything. Hope this helps.
I did not reroot until after I had verified Prime Music was installed. You can either open the music store and will look different and have Prime Music on it or go to manage applications and look at the icon. If the Amazon music icon is green it is the old version if it is orange it is the new version with Prime Music.
BroncoAG said:
I don't know if this is the correct way but this is what I did. I just ran the system update and installed the latest firmware. After the install the HDX is unrooted. I then ran towel root. After the reboot I ran xposed and reinstalled the framework and modules and then rebooted. After that I ran supersu and updated the binaries. Everything worked for me after that. I did not have to uninstall anything. Hope this helps.
I did not reroot until after I had verified Prime Music was installed. You can either open the music store and will look different and have Prime Music on it or go to manage applications and look at the icon. If the Amazon music icon is green it is the old version if it is orange it is the new version with Prime Music.
Click to expand...
Click to collapse
All worked well for me. Thanks for taking the time to respond to my post. All the best to you.
I am thinking of unrooting, what about SafeStrap? Does anything need to be done first for that?
wave_sailor said:
I am thinking of unrooting, what about SafeStrap? Does anything need to be done first for that?
Click to expand...
Click to collapse
Why do you want to unroot/upgrade when you could, with a bit of work, install a different ROM which would offer all the goodness of generic Android (think google play store access) along with all prime benefits.
If you still want to 'upgrade' fire OS no need to unroot. Upgrade will handle that nicely. I would dump Safestrap. Just asking for trouble with that in the mix.
It is possible to brick with safestrap, so go back to oem rom, and uninstall it before doing anything or you could be looking for trouble.
Whoa, help me understand. I thought installing a custom rom would cause you to lose all the benefit of having a prime membership. Am I wrong about that? I could still get prime movies and download to my device? I could still download a free book per month through the middle lenders library? What rom would you recommend? I am rooted 14.3.2.6 currently and gapps no longer work since the Google play services upgrade.
rootnooby said:
Whoa, help me understand. I thought installing a custom rom would cause you to lose all the benefit of having a prime membership. Am I wrong about that? I could still get prime movies and download to my device? I could still download a free book per month through the middle lenders library? What rom would you recommend? I am rooted 14.3.2.6 currently and gapps no longer work since the Google play services upgrade.
Click to expand...
Click to collapse
Many prime benefits are available on non-FireOS devices including:
- prime video (streaming only; can't download content)
- prime music (full functionality including download)
- Kindle books/magazines (but can't loan/lend; no freebies)
- all non-electronic services (eg: free shipping)
I have great luck with the Nexus variants by @ggow. I also use CM11 on an older Fire tablet; no complaints. However, Nexus remains my favorite.
With 14.3.2.6 you have several paths:
- rollback to 14.3.2.3, unlock bootloader, install TWRP and then flash Nexus or CM (runs natively)
- upgrade to 14.4.5.2, root, install Safestrap v4 and then flash either Nexus or CM. However, once you upgrade you can no longer unlock your bootloader which carries other benefits including the ability to run custom roms natively and more robust recovery capabilities should something go wrong.
- remain on 14.3.2.6, install Safestrap v3 and then flash Nexus v1 to a secondary slot. This option gives you the best of both worlds as you can boot into FireOS (for prime content) or Nexus (for for access to all things Google). However, both roms are Jelly Bean based which is two generations back from Lollipop.
The first path is preferred but more complex. The last is easiest (and least risky) but is an older solution with aging roms. The middle choice is primarily targeted at newer devices that can not roll back or unlock the bootloader (plus reduces your future options). You'll need to decide which is best for you.
Thank you for all the good information. A couple questions. The last option seems like the most interesting to me right now since I will be able to use all the Amazon features and have a better ROM where all the google services will work. However, I'm having a couple issues right now that I'm concerned about. The first is that Amazon music crashes. The second is that I installed GAPPS and the recent update of Google Play services has caused many small issues. Given this, should I factory reset first so I have a clean slate with 14.3.2.6? I want to be sure that a reset won't brick my device. I can root with the toolkit and install safestrap from there.
Also, does the last option work if I were to upgrade to 14.3.2.8? My understanding is that this firmware fixed some bugs in 14.3.2.6.
Thanks again for you input.
Davey126 said:
Many prime benefits are available on non-FireOS devices including:
- prime video (streaming only; can't download content)
- prime music (full functionality including download)
- Kindle books/magazines (but can't loan/lend; no freebies)
- all non-electronic services (eg: free shipping)
I have great luck with the Nexus variants by @ggow. I also use CM11 on an older Fire tablet; no complaints. However, Nexus remains my favorite.
With 14.3.2.6 you have several paths:
- rollback to 14.3.2.3, unlock bootloader, install TWRP and then flash Nexus or CM (runs natively)
- upgrade to 14.4.5.2, root, install Safestrap v4 and then flash either Nexus or CM. However, once you upgrade you can no longer unlock your bootloader which carries other benefits including the ability to run custom roms natively and more robust recovery capabilities should something go wrong.
- remain on 14.3.2.6, install Safestrap v3 and then flash Nexus v1 to a secondary slot. This option gives you the best of both worlds as you can boot into FireOS (for prime content) or Nexus (for for access to all things Google). However, both roms are Jelly Bean based which is two generations back from Lollipop.
The first path is preferred but more complex. The last is easiest (and least risky) but is an older solution with aging roms. The middle choice is primarily targeted at newer devices that can not roll back or unlock the bootloader (plus reduces your future options). You'll need to decide which is best for you.
Click to expand...
Click to collapse
rootnooby said:
Thank you for all the good information. A couple questions. The last option seems like the most interesting to me right now since I will be able to use all the Amazon features and have a better ROM where all the google services will work. However, I'm having a couple issues right now that I'm concerned about. The first is that Amazon music crashes. The second is that I installed GAPPS and the recent update of Google Play services has caused many small issues. Given this, should I factory reset first so I have a clean slate with 14.3.2.6? I want to be sure that a reset won't brick my device. I can root with the toolkit and install safestrap from there.
Also, does the last option work if I were to upgrade to 14.3.2.8? My understanding is that this firmware fixed some bugs in 14.3.2.6.
Thanks again for you input.
Click to expand...
Click to collapse
Safestrap v3 does work under 14.3.2.8. However, upgrading beyond 14.3.2.6 eliminates the possibility of unlocking your device's bootloader at a future time. While that may not seem like a big deal now you may ultimately regret the decision.
Factory resets always carry the risk of disabling your device...more so if rooted. You have limited recovery options if that happens with a locked bootloader. Unless the issues with 3.2.6 are severe I wouldn't change anything. Once Safestrap is installed you have some additional options that may prove beneficial in fixing up FireOS.
Cautions:
- make sure you snag the correct version of Safestrap (here). Apollo v3.75.
- ditto for Nexus (here). Safestrap-apollo-nexus-rom-v1.0.1.zip
- get familiar with Safestrap before flashing anything. It is very easy to overwrite the stock slot containing FireOS if you're not careful.
- Nexus goes in slot #1 which you will need to create in advance.
Do you homework (read the relevant threads) before acting. Go slow and know exactly what is expected from each step. Stop and ask questions as needed or if you run into trouble. Don't panic, do a factory reset or take other rash actions. Sounds scary but it only is if you go in blind.
Good luck.
Just to add another small piece to the discussion, the only thing that does not work on nexus or cm, is the prime lending library and some (most?) Kindle comics.
Davey126 said:
Safestrap v3 does work under 14.3.2.8. However, upgrading beyond 14.3.2.6 eliminates the possibility of unlocking your device's bootloader at a future time. While that may not seem like a big deal now you may ultimately regret the decision.
Factory resets always carry the risk of disabling your device...more so if rooted. You have limited recovery options if that happens with a locked bootloader. Unless the issues with 3.2.6 are severe I wouldn't change anything. Once Safestrap is installed you have some additional options that may prove beneficial in fixing up FireOS.
Cautions:
- make sure you snag the correct version of Safestrap (here). Apollo v3.75.
- ditto for Nexus (here). Safestrap-apollo-nexus-rom-v1.0.1.zip
- get familiar with Safestrap before flashing anything. It is very easy to overwrite the stock slot containing FireOS if you're not careful.
- Nexus goes in slot #1 which you will need to create in advance.
Do you homework (read the relevant threads) before acting. Go slow and know exactly what is expected from each step. Stop and ask questions as needed or if you run into trouble. Don't panic, do a factory reset or take other rash actions. Sounds scary but it only is if you go in blind.
Good luck.
Click to expand...
Click to collapse
The main issue I have with 14.3.2.6 right now is with Amazon music. It constantly crashes. Hopefully that can be fixed because I do use it regularly. I won't upgrade to version 14.3.2.8 for now. I agree that I may regret it later. I'll follow your instructions and let you know how it goes. Thanks for the links to the proper files.
rootnooby said:
The main issue I have with 14.3.2.6 right now is with Amazon music. It constantly crashes. Hopefully that can be fixed because I do use it regularly. I won't upgrade to version 14.3.2.8 for now. I agree that I may regret it later. I'll follow your instructions and let you know how it goes. Thanks for the links to the proper files.
Click to expand...
Click to collapse
Once you have Safestrap v3 and Nexus installed you can try to 'repair' FireOS in the stock slot. Safestrap v3 has some limited recovery options should something go wrong; you don't have those now making repair attempts risky. I can provide additional detail when ready. That said, you may find Amazon Music works fine in Nexus.
Davey126 said:
Once you have Safestrap v3 and Nexus installed you can try to 'repair' FireOS in the stock slot. Safestrap v3 has some limited recovery options should something go wrong; you don't have those now making repair attempts risky. I can provide additional detail when ready. That said, you may find Amazon Music works fine in Nexus.
Click to expand...
Click to collapse
I now have safestrap and the nexus rom installed in slot 1. Seems to work well. I'd like to try to repair my stock 14.3.2.6 rom. Any insight you can provide slyly be great. Thank you.
rootnooby said:
I now have safestrap and the nexus rom installed in slot 1. Seems to work well. I'd like to try to repair my stock 14.3.2.6 rom. Any insight you can provide slyly be great. Thank you.
Click to expand...
Click to collapse
Sorry for the delayed response. The process is actually quite simple and reasonably safe given you have Nexus to fall back on should something go wrong. See this post for FireOS images that can be Flashed from within Safestrap. Make sure you grab the correct one for your device. Then flash to the stock slot (verify you have toggled back to stock in Safestrap or you will overwrite the currently selected slot which is likely Nexus). The 14.3.2.6 image is rooted with OTA blocked. However, being a belt and suspenders type I would fire up HDX toolkit and block OTA again before enabling WiFi - just to make sure. You definitely do not want to take an update while Safestrap v3 is installed.
Post back if you have any questions.
---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------
rootnooby said:
I now have safestrap and the nexus rom installed in slot 1. Seems to work well. I'd like to try to repair my stock 14.3.2.6 rom. Any insight you can provide slyly be great. Thank you.
Click to expand...
Click to collapse
Sorry for the delayed response. The process is actually quite simple and reasonably safe given you have Nexus to fall back on should something go wrong. See this post for FireOS images that can be Flashed from within Safestrap. Make sure you grab the correct one for your device. Then flash to the stock slot (verify you have toggled back to stock in Safestrap or you will overwrite the currently selected slot which is likely Nexus). The 14.3.2.6 image is rooted with OTA blocked. However, being a belt and suspenders type I would fire up HDX toolkit and block OTA again before enabling WiFi - just to make sure. You definitely do not want to take an update while Safestrap v3 is installed.
If Amazon Music still crashes after the update then you can try uninstalling/reinstalling the app. You may need some additional tools to accomplish this as FireOS will likely resist attempts to remove preinstalled or 'system' apps.
Post back if you have any questions.
Davey126 said:
Sorry for the delayed response. The process is actually quite simple and reasonably safe given you have Nexus to fall back on should something go wrong. See this post for FireOS images that can be Flashed from within Safestrap. Make sure you grab the correct one for your device. Then flash to the stock slot (verify you have toggled back to stock in Safestrap or you will overwrite the currently selected slot which is likely Nexus). The 14.3.2.6 image is rooted with OTA blocked. However, being a belt and suspenders type I would fire up HDX toolkit and block OTA again before enabling WiFi - just to make sure. You definitely do not want to take an update while Safestrap v3 is installed.
Post back if you have any questions.
---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------
Sorry for the delayed response. The process is actually quite simple and reasonably safe given you have Nexus to fall back on should something go wrong. See this post for FireOS images that can be Flashed from within Safestrap. Make sure you grab the correct one for your device. Then flash to the stock slot (verify you have toggled back to stock in Safestrap or you will overwrite the currently selected slot which is likely Nexus). The 14.3.2.6 image is rooted with OTA blocked. However, being a belt and suspenders type I would fire up HDX toolkit and block OTA again before enabling WiFi - just to make sure. You definitely do not want to take an update while Safestrap v3 is installed.
If Amazon Music still crashes after the update then you can try uninstalling/reinstalling the app. You may need some additional tools to accomplish this as FireOS will likely resist attempts to remove preinstalled or 'system' apps.
Post back if you have any questions.
Click to expand...
Click to collapse
Thank you. I was able to reinstall 14.3.2.6 in the stock partition. Worked well. Also, I uninstalled updates for Amazon music. During the process, the older version was put installed. I was able to open that and play music, however, prime music features were not available. I found the latest APK for amazon music with prime and downloaded it. All it working now, including prime music. Thanks again.
Ha! Spoke too soon! Worked for about 30 minutes. Crashing again
rootnooby said:
Ha! Spoke too soon! Worked for about 30 minutes. Crashing again
Click to expand...
Click to collapse
rootnooby said:
Thank you. I was able to reinstall 14.3.2.6 in the stock partition. Worked well. Also, I uninstalled updates for Amazon music. During the process, the older version was put installed. I was able to open that and play music, however, prime music features were not available. I found the latest APK for amazon music with prime and downloaded it. All it working now, including prime music. Thanks again.
Click to expand...
Click to collapse
With root you can attempt a complete uninstall/reinstall which may prove to be more stable. Download/sideload CCleaner which supports this capability in an easy-to-digest UI. There are more advanced tools/techniques if removal proves stubborn.
Related
Q&A for [APOLLO/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [APOLLO/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Fire HDX 8.9 vs Kindle Fire HDX 8.9
Okay, so I have noticed that Hashcode built this for both the 7" and 8.9" versions of the Kindle Fire HDX, but does the 8.9" version here: http://forum.xda-developers.com/showthread.php?t=2612772
Does this support the 3rd generation Fire HDX 8.9" version? I noticed that the download links say it supports systems earlier than 14.3.2.1 and later than 14.3.2.1, but does it support the newer Fire HDX 8.9" system 4.1.1? Judging from what I have researched, I believe that there isn't much difference between 14.3.2.1 and 4.1.1. Has anyone tried to root or install CM on this newest version of the HDX 8.9 yet?
Thanks in advance.
WickdWzrd said:
Okay, so I have noticed that Hashcode built this for both the 7" and 8.9" versions of the Kindle Fire HDX, but does the 8.9" version here: http://forum.xda-developers.com/showthread.php?t=2612772
Does this support the 3rd generation Fire HDX 8.9" version? I noticed that the download links say it supports systems earlier than 14.3.2.1 and later than 14.3.2.1, but does it support the newer Fire HDX 8.9" system 4.1.1? Judging from what I have researched, I believe that there isn't much difference between 14.3.2.1 and 4.1.1. Has anyone tried to root or install CM on this newest version of the HDX 8.9 yet?
Thanks in advance.
Click to expand...
Click to collapse
No, it's not possible to mod FireOS 4 in any way.
Safestrap apk for Kindle Fire HDX 14.3.2.3.2
Hi I'm trying to install safestrap on my kfhdx, but all the links in the forums seem to be broken. Any suggestions on where I can find this download? Thanks a lot
j1mbo83 said:
Hi I'm trying to install safestrap on my kfhdx, but all the links in the forums seem to be broken. Any suggestions on where I can find this download? Thanks a lot
Click to expand...
Click to collapse
Available here.
Although I'm not sure why you want to install safestrap as the firmware version you are running (self reported as 14.3.2.3.2) permits flashing 'native' twrp which is far more robust. From there you can flash CM11 or Nexus 2.0.5. With a bit of work you can also unlock your bootloader which opens the door to CM12 and Nexus 4.x. None of these roms work with safestrap.
Safestrap is a primary used by those who cannot flash 'native' twrp (most newer Kindles) and/or if you wish to toggle between Fire OS and Nexus 1.01. Those are the only roms that work with safestrap. Also note you must take steps to block OTA while using Safestrap or risk bricking your device. At present the only method that works reliably is HDX toolkit.
Thanks for the reply, I'm obviously new to this but I've rooted my Kindle, installed Google play, but recently Google has been forcing updates of play services and I'm afraid to mess with anything else until I can either unlock bootloader it install custom recovery, if you could point me in the right direction on how to do this I'd appreciate it. Didn't know I could install twrp. Any directions in layman's terms would help, thanks.
j1mbo83 said:
Thanks for the reply, I'm obviously new to this but I've rooted my Kindle, installed Google play, but recently Google has been forcing updates of play services and I'm afraid to mess with anything else until I can either unlock bootloader it install custom recovery, if you could point me in the right direction on how to do this I'd appreciate it. Didn't know I could install twrp. Any directions in layman's terms would help, thanks.
Click to expand...
Click to collapse
Installing a custom recovery (twrp) is straight forward given your version of Fire OS. Please confirm you really are on v14.3.2.3.2 and OTA (over-the-air) updates have been blocked and if so, via which method. Did you roll your device back from a higher firmware version? Sorry for all the questions - want to make sure the foundation is solid before taking next steps.
Outline to install custom recovery:
- side load Flashify (here). You can also find/install this from Play Store if working on your device.
- download custom twrp (here); you want Apollo v2.8.6.0
- use Flashify to backup your current recovery (don't skip this step)
- use Flashify to flash (install) the twrp recovery image previously downloaded. You must use this image; don't go downloading/flashing a generic version!
When complete you device will reboot back into Fire OS as if nothing changed. You can verify twrp was correctly installed by powering down and then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears; release the vol-up button a few seconds alter. After a few moments a blue logo should appear and you will enter twrp recovery. Have a look around but don't change anything. Reboot you device and post back for further instructions (actually information on next steps; where the fun begins!) .
Be aware that any type of flashing can render your device unusable. The steps outlined above are relatively safe if you follow directions carefully and double check each action before executing. Ask questions in advance; don't panic and start doing unscripted stuff if something goes wrong.
I am running v14.3.2.3.2, I rooted the kindle and blocked OTA updates using hdx toolkit. I did this maybe about 7 months ago and never rolled back. Will these directions still work for me?
j1mbo83 said:
I am running v14.3.2.3.2, I rooted the kindle and blocked OTA updates using hdx toolkit. I did this maybe about 7 months ago and never rolled back. Will these directions still work for me?
Click to expand...
Click to collapse
Looks good. Just go slow and double check each step. Once twrp is installed and confirmed working you can then flash either the Nexus or CM11 rom which will give you unfettered access to the Play store and all the goodness of a 'generic' android device. Effectively your Kindle looses its identity as an Amazon tablet. Nexus (what I use) has proven rock solid but is getting a bit long in the tooth. CM11 is based on KitKat and only has a minor issues with bluetooth, LTE and occasionally wifi. Most users of this rom are quite happy and can easily work around the issues.
Prior to flashing a new rom you should make a complete backup of your current system in twrp and then store that image on another device. Also keep in mind that once you flash twrp it is very difficult to restore your device to full 'stock'. Assume a one way trip.
Edit: Forgot to mention LTE. At present none of the roms support LTE but that will likely change in the near future. If you have an LTE enabled tablet you'll have to decide if that or play store access is more important.
Thanks. Ok I installed flashify, then followed your link to download and install twrp and it has a note at the top that says to unlock boot loader. I don't think it is unlocked. How do I check this? And if it isn't, how would I go about unlocking it?
---------- Post added at 09:00 PM ---------- Previous post was at 08:11 PM ----------
Ok I successfully installed twrp, created a backup, and saved it to another device. Ready for the next step. Thanks for all your help.
Congrats. If you are asking how to know if you are unlocked, chances are good it is locked. You do not need to unlock the bootloader, but it is highly recommended as once successfully unlocked it is another failsafe, and opens up other roms (like cm 12). To unlock it, I suggest grabbing Draxie's automated (slightly) script from the original dev section. Know that the act of unlocking the bootloader is difficult, and will require you to learn more about your device, but it does pay off in the end.
j1mbo83 said:
Thanks. Ok I installed flashify, then followed your link to download and install twrp and it has a note at the top that says to unlock boot loader. I don't think it is unlocked. How do I check this? And if it isn't, how would I go about unlocking it?
---------- Post added at 09:00 PM ---------- Previous post was at 08:11 PM ----------
Ok I successfully installed twrp, created a backup, and saved it to another device. Ready for the next step. Thanks for all your help.
Click to expand...
Click to collapse
Congrats!! See post from lekofraggle (here) which I fully agree with. However, I think you can defer the bootloader unlock for a little while recognizing that it provides an important failsafe should you bork your device and is a prerequisite for some roms (eg: CM12).
Next step involves flashing a rom of your choice. Recognize all aps/data will be wiped; you'll be starting clean. However, anything previously purchased in the play store can be downloaded again assuming you use the same credentials when setting up accounts on the 'new' rom.
Choices:
- Nexus 2.0.5: JellyBean based, rock solid, near AOSP (unmodified Android). Info/links here.
- CM11: KitKat based, popular across numerous Android devices with useful extensions baked in. Some minor BT/WiFi flakiness on HDX devices. Info/links here.
Both roms can also be downloaded using the ROMs tab at the top of this page. Don't go trying anything else. You want HDX Nexus or CM11-Apollo. Magic Beans will also work but carries no significant advantage over the other two and hasn't see much development in recent months.
All ROMs can be flashed from twrp. Be sure to make a backup of your current environment first. Use caution in twrp if you are new to the tool; it's easy to mess things up including a full brick of your device.
I recommend you start with Nexus. It's a great rom that will serve you well; an upgrade (KitKat) is in the works and should be released in the not-too-distant future. CM11 is also a fine choice and offers greater compatibility with some of the more recent app releases. Both are further customizable via Xposed Framework but that's another discussion.
Ok thanks, I downloaded the zips, now I have just one more question (I know, I have a lot...). Do I need to wipe my system before installing new Rom?
j1mbo83 said:
Ok thanks, I downloaded the zips, now I have just one more question (I know, I have a lot...). Do I need to wipe my system before installing new Rom?
Click to expand...
Click to collapse
Keep asking! Lots of devices have died in the hands of ignorant users (not intended to be an insult...were are all ignorant until educated).
In theory you do not need to wipe the device but there have been scattered reports of strange behaviors after performing a 'dirty' flash. My recommendation is to perform a factory reset (under wipe) from within twrp. This will clear data, cache and dalvik while leaving system and internal storage intact. If you opt for an "advanced wipe" select the previous 3 plus system; leave internal storage alone. Do not format or repair; just asking for trouble.
As always make a backup before proceeding and store a copy of that off-device. Short term keep a copy on the device along with the rom image just in case you have to redo something and can't connect via tether. Rare but it does happen.
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
Hi,
I´m on 14.1.3.0 firmware with my HDX 8.9 LTE. I rooted the device. Installed Nova Launcher, Xposed Framework, HDX Module, Safestrap, a.s.o.
Now I´m on it to clean up the device from all "kindle" and "amazon" soft. Has anyone an idea which system apps have to be on the device that i can use my services from google (gmail, calender, sync, a.s.o.). Maybe there is a list of it?
The best for me is an Gapps Rom for 14.1.3.0, but i don´t think this is available here?
Cheers
maluc said:
Hi,
I´m on 14.1.3.0 firmware with my HDX 8.9 LTE. I rooted the device. Installed Nova Launcher, Xposed Framework, HDX Module, Safestrap, a.s.o.
Now I´m on it to clean up the device from all "kindle" and "amazon" soft. Has anyone an idea which system apps have to be on the device that i can use my services from google (gmail, calender, sync, a.s.o.). Maybe there is a list of it?
The best for me is an Gapps Rom for 14.1.3.0, but i don´t think this is available here?
Cheers
Click to expand...
Click to collapse
You are playing with fire removing amazon apps from stock os. Before nexus and other roms came along I ran with a configuration similar to yours (no safestrap) and identified various amazon components that were annoying and/or aggressively ran in the background consuming resources. Many could be frozen but there were often unforeseen consequences. I had a couple scares with bootlooping and failure to boot that I was fortunate to recover from. Many 'kindle' components are baked into Fire OS and can't be easily removed/disabled.
My suggestion is to install a different rom. Nexus is very stable and gives a clean android experience. CM11/12 are great as well. Given you are on 1.3.0 I would suggest ditching Safestrap in favor of native twrp opening many more doors and, perhaps most importantly, a solid path to recovery should things go wrong. Although this is probably obvious, all remnants of Fire OS are removed with a different rom (aside from low level stuff you don't care about).
As a bonus you don't have to mess around with intalling Gapps with any of the roms currently available; it's already built in
Thanks for your really forthcoming infos. On Nexus i haven't got support for my mobile Internet (3g/LTE), right?
When i install CM11/12 i need to upgrade from 3.1.0 to 3.2.3 but i habe absolutely no idea how? I do habe a stock 3.2.3 but this is a .bin file - how do i flash this? Or can i flash the New Rom.ZIP in twrp anyway?
maluc said:
Thanks for your really forthcoming infos. On Nexus i haven't got support for my mobile Internet (3g/LTE), right?
When i install CM11/12 i need to upgrade from 3.1.0 to 3.2.3 but i habe absolutely no idea how? I do habe a stock 3.2.3 but this is a .bin file - how do i flash this? Or can i flash the New Rom.ZIP in twrp anyway?
Click to expand...
Click to collapse
To the best of my knowledge there is no explicit mobile support with nexus. If you need reliable 3g/lte then your best bet is to stick with stock until confirmed working 100% in CM11/12.
The 3.2.3 bootloader update posted here is flashable from within twrp or using a utility like flashify. However, I believe it assumes twrp (or cwm) is your primary recovery. I have no idea if it would work using flashify with stock recovery and safestrap. Perhaps someone more knowledgeable can comment on this. You might want to send a PM to ggow.
Set the 3.2.3 .bin file aside for now; you don't need it.
Last I knew (from this post) you had safestrap installed. Is that still the case? You really want to get safestrap out of the picture unless there is a good reason for retaining it. Make sure you know the correct procedure for uninstalling safestrap and restoring your preferred rom.
If you already have twrp installed *and* known good backup of your current system then you could move forward with the 3.2.3 bootloader update and then install CM11 which I believe works with a locked bootloader (recognizing it may not fully support 3g/lte). I believe the current CM12 builds do required an unlocked bootloader. You can unlock but it is not always a straight forward process.
removed safestrap, backed up my device and flashed Nexus. Works perfect...only LTE is Missing
I think I try CM11 next. Thanks for your support!
maluc said:
removed safestrap, backed up my device and flashed Nexus. Works perfect...only LTE is Missing
I think I try CM11 next. Thanks for your support!
Click to expand...
Click to collapse
There's an "unofficial" release of Nexus in the original thread with LTE compiled and it works quite well, alternatively CM11 LTE works great (on my Apollo) i'm sending and receiving SMS, haven't really tried calls yet but have used Facebook messenger to make and receive VOIP calls
EDIT: My bad, it's actually on Magic Beanz http://forum.xda-developers.com/showpost.php?p=59043532&postcount=73 which I would recommend over Nexus anyway (as long as you can get TWRP going).
I have this rooted and installed CyanogenMod 11 via safestrap v4.
I live in Minneapolis and we have citywide roaming through USI Wireless. I just signed up, but I can't see the usi wireless signal, even at the antenna. The answer from them is its a 5ghz signal, so maybe my tablet does not support it.
The 3rd gen is listed as Dual band, dual antenna (MIMO+HT40) 802.11a/b/g/n. I never learned much about WiFi specs, just enjoy it, but based on a Google search doesn't this tablet support 5ghz? Do I need ac?
Thanks.
Raymodjp said:
I have this rooted and installed CyanogenMod 11 via safestrap v4.
I live in Minneapolis and we have citywide roaming through USI Wireless. I just signed up, but I can't see the usi wireless signal, even at the antenna. The answer from them is its a 5ghz signal, so maybe my tablet does not support it.
The 3rd gen is listed as Dual band, dual antenna (MIMO+HT40) 802.11a/b/g/n. I never learned much about WiFi specs, just enjoy it, but based on a Google search doesn't this tablet support 5ghz? Do I need ac?
Thanks.
Click to expand...
Click to collapse
The tablet does support WiFi in the 5GHz band; I have used it successfully in congested areas. I'm running Fire Nexus on an unlocked device. So it's likely CM 11 or Safestrap that is hampering 5GHz access assuming the signal reaches your location. Can you see the 5GHz signal from your mobile or other wireless device?
Davey126 said:
The tablet does support WiFi in the 5GHz band; I have used it successfully in congested areas. I'm running Fire Nexus on an unlocked device. So it's likely CM 11 or Safestrap that is hampering 5GHz access assuming the signal reaches your location. Can you see the 5GHz signal from your mobile or other wireless device?
Click to expand...
Click to collapse
I have seen the signals on this tablet, but I am not sure if I saw them after started running CyanogenMod. USI Wireless tech support told me they were transitioning to 5 GHz, so that just confused the issue. I couldn't confirm that I had seen one of the 5ghz signals. I wondered if CyanogenMod was the problem, but assumed not when I didn't see it mentioned in the discussions.
Now that I know the tablet definitely supports 5ghz, I can probably figure out a resolution. I updated CyanogenMod yesterday, but that didn't help. I was contemplating trying nexus, but was holding off because it looks like I have to go back to the amazon os before installing nexus. I need to really look at all the steps, I don't want to brick.
Forgot one thing I was thinking about. Would I be able to flash the nexus 4.0.5 and its gapps over my cm11 via safestrap? That way I could test the WiFi before trying to do the more complicated steps for getting the newer version of nexus.
EDIT: I was able to successfully flash Nexus 4.0.5, and it fixed the issue! I can see and connect to the 5ghz signal. Thanks for saying it might be cyanogenmod, because I was thinking that probably wasn't the problem.
Raymodjp said:
Forgot one thing I was thinking about. Would I be able to flash the nexus 4.0.5 and its gapps over my cm11 via safestrap? That way I could test the WiFi before trying to do the more complicated steps for getting the newer version of nexus.
EDIT: I was able to successfully flash Nexus 4.0.5, and it fixed the issue! I can see and connect to the 5ghz signal. Thanks for saying it might be cyanogenmod, because I was thinking that probably wasn't the problem.
Click to expand...
Click to collapse
Nexus 4.0.5 is stable and fully functional but lacks a few key features (eg: location services support) and regular updates. Upgrading to Fire Nexus can be a bit of a pain given the FireOS 4.5.5.1 (note the trailing '1') prerequisite which is the only means for installing the updated kernel Fire Nexus requires. In your shoes I might stick with 4.0.5 for a while to make sure it meets your needs.
BTW - assume you are familiar with Safestrap v4 best practices:
- everything happens in the STOCK slot
- never create or populate secondary slots (special exceptions noted)
- best to create full backups before flashing anything
- never restore backups from secondary slots to the stock slot
- always keep a rom zip on the device for emergency recovery
- reread above line (really important with Safestrap v4)
- never access or execute actions from the stock recovery menu with Safestrap v4 installed - especially a 'Factory Reset'
Davey126 said:
Nexus 4.0.5 is stable and fully functional but lacks a few key features (eg: location services support) and regular updates. Upgrading to Fire Nexus can be a bit of a pain given the FireOS 4.5.5.1 (note the trailing '1') prerequisite which is the only means for installing the updated kernel Fire Nexus requires. In your shoes I might stick with 4.0.5 for a while to make sure it meets your needs.
BTW - assume you are familiar with Safestrap v4 best practices:
- everything happens in the STOCK slot
- never create or populate secondary slots (special exceptions noted)
- best to create full backups before flashing anything
- never restore backups from secondary slots to the stock slot
- always keep a rom zip on the device for emergency recovery
- reread above line (really important with Safestrap v4)
- never access or execute actions from the stock recovery menu with Safestrap v4 installed - especially a 'Factory Reset'
Click to expand...
Click to collapse
I have been pouring over several threads, but it never hurts to see those warnings again. It's not something to take lightly unless you want a bricked tablet.
Your comment about location services answers a problem i ran into with 4.0.5. my 7 year old had a fit because she has been playing Pokemon Go on my tablet, but with Nexus I get the "not compatible" message from Google play. Now I know why. Looks like I might have to take the plunge for the new Nexus rom.
I safestrapped this tablet about 3 months ago and backed it up, but I imagine it's wishful thinking that I could just restore the saved Amazon os via safestrap? Otherwise I need to flash 4.5.2 (the version that can then update to 4.5.5.1 after I uninstall safestrap), then reroot, (3 months ago I had to use KingoRoot instead of KingRoot) reinstall safestrap, and flash the new Nexus and supersu. I will triple-check that, it's just off the top of my head. Any warnings, instructions or suggestions appreciated. Esp. After I saw at least one user have problem with 4.5.2 updating. I am waiting and reading at least another day.
EDIT: After reading the thread again, the thing I'm not sure about is uninstalling safestrap. After wiping and flashing 4.5.2, I reboot and then will I still see safestrap? I just don't know what it will look like going back to Amazon OS, so not sure how to uninstall safestrap.
Raymodjp said:
I have been pouring over several threads, but it never hurts to see those warnings again. It's not something to take lightly unless you want a bricked tablet.
Your comment about location services answers a problem i ran into with 4.0.5. my 7 year old had a fit because she has been playing Pokemon Go on my tablet, but with Nexus I get the "not compatible" message from Google play. Now I know why. Looks like I might have to take the plunge for the new Nexus rom.
I safestrapped this tablet about 3 months ago and backed it up, but I imagine it's wishful thinking that I could just restore the saved Amazon os via safestrap? Otherwise I need to flash 4.5.2 (the version that can then update to 4.5.5.1 after I uninstall safestrap), then reroot, (3 months ago I had to use KingoRoot instead of KingRoot) reinstall safestrap, and flash the new Nexus and supersu. I will triple-check that, it's just off the top of my head. Any warnings, instructions or suggestions appreciated. Esp. After I saw at least one user have problem with 4.5.2 updating. I am waiting and reading at least another day.
EDIT: After reading the thread again, the thing I'm not sure about is uninstalling safestrap. After wiping and flashing 4.5.2, I reboot and then will I still see safestrap? I just don't know what it will look like going back to Amazon OS, so not sure how to uninstall safestrap.
Click to expand...
Click to collapse
Hang tight - not ignoring this post. Got a few irons in the fire. Look for a follow-up edit later today.
No hurry, I am still reading. Thinking now that I need to boot 4.5.2, stop updates, and remove the safestrap apk. just been so long since I did anything in the Amazon environment so I would need to play around with it.
Realizing now I should have posted this in one of the existing threads, but thought I just had a quick question about 5ghz, not flashing several ROMs.
Raymodjp said:
No hurry, I am still reading. Thinking now that I need to boot 4.5.2, stop updates, and remove the safestrap apk. just been so long since I did anything in the Amazon environment so I would need to play around with it.
Realizing now I should have posted this in one of the existing threads, but thought I just had a quick question about 5ghz, not flashing several ROMs.
Click to expand...
Click to collapse
Thanks for for your patience. Let's continue in this thread for now given where the conversation stands. Suggest the following course of action:
- verify a known good copy of cm11 or Nexus 4.0.5 (not Fire Nexus) zip is resident on the device, preferably located in the root of sdcard folder
- backup your current rom/apps/data if needed
- locate and attempt to restore your previous 4.5.2 backup
- once restored uninstall Safestrap v4 recovery using the app which should be resident in restored FireOS image
- remove OTA update block (rename the file back to otacerts.zip)
- verify network connectivity (WiFi on and connected)
- reboot and check for updates; device should attempt a 4.5.5.1 refresh within a few hours...usually much quicker
Post back results, questions and issues/problems.
Davey126 said:
Thanks for for your patience. Let's continue in this thread for now given where the conversation stands. Suggest the following course of action:
- verify a known good copy of cm11 or Nexus 4.0.5 (not Fire Nexus) zip is resident on the device, preferably located in the root of sdcard folder
- backup your current rom/apps/data if needed
- locate and attempt to restore your previous 4.5.2 backup
- once restored uninstall Safestrap v4 recovery using the app which should be resident in restored FireOS image
- remove OTA update block (rename the file back to otacerts.zip)
- verify network connectivity (WiFi on and connected)
- reboot and check for updates; device should attempt a 4.5.5.1 refresh within a few hours...usually much quicker
Post back results, questions and issues/problems.
Click to expand...
Click to collapse
OK, I have sucessfully flashed Fire Nexus ROM! Turns out I couldnt find a usable backup, but I was able to flash 4.5.2 and supersu with no problems. After updates I had to reroot with kingroot, but everything went very smoothly. Keeping my patience while it loaded 3 updates was probably the hardest part. I have my 5ghz WiFi and my daughter has her pokemon go. Now its time for me to go poke around Nexus. Thanks!
So I just acquired a used 4th gen 16gb Fire HD 7"
Im trying to look around, and I keep reading conflicting info on what OS versions can root, do/do not downgrade, use this/that etc.
This is the info i have:
Model: Fire HD 7 (4th gen)
Fire os version: 5.3.1.1
In "noob friendly terms", can someone explain how (or what tutorial to follow) so I can root my tablet, and get TWRP installed so I can load custom roms (plan on replacing this crap fire OS)
ps: If I cant root, is there a way to get the play store, and block all future updates so eventually I can root when the community behind developing those roots catch up?
cheers!
Orvis25 said:
So I just acquired a used 4th gen 16gb Fire HD 7"
Im trying to look around, and I keep reading conflicting info on what OS versions can root, do/do not downgrade, use this/that etc.
This is the info i have:
Model: Fire HD 7 (4th gen)
Fire os version: 5.3.1.1
In "noob friendly terms", can someone explain how (or what tutorial to follow) so I can root my tablet, and get TWRP installed so I can load custom roms (plan on replacing this crap fire OS)
ps: If I cant root, is there a way to get the play store, and block all future updates so eventually I can root when the community behind developing those roots catch up?
cheers!
Click to expand...
Click to collapse
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Killa8 said:
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Click to expand...
Click to collapse
I see the downgrade works with 5.3.1 but does NOT specify if it does for 5.3.1.1. (do not want to brick)
Also, So when/if I risk downgrade to 4.5.3, i can then install TWRP and flash custom roms no problem, correct?
Cheers!
Orvis25 said:
I see the downgrade works with 5.3.1 but does NOT specify if it does for 5.3.1.1. (do not want to brick)
Also, So when/if I risk downgrade to 4.5.3, i can then install TWRP and flash custom roms no problem, correct?
Cheers!
Click to expand...
Click to collapse
Exactly
But the worse brick possible for a Fire can be recoverable in most cases (maybe not yours?) Anyway all this is risk ! Try by your own and see
Just to confirm, it does work with 5.3.1.1.
olliebean said:
Just to confirm, it does work with 5.3.1.1.
Click to expand...
Click to collapse
Are you referring to downgrading to 4.5.3 from 5.3.1.1?
If so, what tutorial/files did you use?
Cheers!
Orvis25 said:
Are you referring to downgrading to 4.5.3 from 5.3.1.1?
If so, what tutorial/files did you use?
Cheers!
Click to expand...
Click to collapse
Yes, I followed the tutorial here as linked by Killa8 above. Worked perfectly. You can root 4.5.3 with KingRoot, then install TWRP using the .bat script from section 101 of post #2, then following the guide in post #1 use TWRP to flash 5.3.1.1, the 5.3.1 bootloaders, and SuperSU/Xposed/Gapps as required.
@olliebean The tutorial you linked to, in turn seems to link to a tutorial to downgrade to 4.5.3 - however, when I click that link it takes me to a thread on unbricking? I'm a bit confused. I routinely flash HTC, Samsung and Nexus phones with ease and have even rooted and installed CM on the Fire Phones I bought not too long ago, but I'll be honest - the "tutorial" provided here is extremely confusing and unclear, largely due to to all the caveats and changes that have needed to be made as more and more recent OSes have come about. Given your success, could you be so kind as to provide a bit more guidance on how you downgraded to 4.5.3?
I'm confident that once downgraded to 4.5.3, I can root via Kingroot and then run the script to get TWRP on the device and then I'm home free.
Any and all input would be GREATLY appreciated!
@Zwitterion The tutorial here should do the trick - skip step 1 assuming you're currently on v5.x. I didn't bother with JmzFireHDTool either; I just left the temporary OTA block enabled. Not sure what the difference is but it did the job considering I only had 4.5.3 installed temporarily anyway.
olliebean said:
@Zwitterion The tutorial here should do the trick - skip step 1 assuming you're currently on v5.x. I didn't bother with JmzFireHDTool either; I just left the temporary OTA block enabled. Not sure what the difference is but it did the job considering I only had 4.5.3 installed temporarily anyway.
Click to expand...
Click to collapse
Thanks so much!! I'll report back if I have any issues but I'm hoping the rest of the tutorial linked by Killa8 is straightforward. Thanks for the tip on the JMZ tool as well. I agree it doesn't make a lot of sense since we are going to upgrade manually again anyway. But perhaps it blocks OTAs even after we arrive back at 5.3.1.1?
Zwitterion said:
Thanks so much!! I'll report back if I have any issues but I'm hoping the rest of the tutorial linked by Killa8 is straightforward. Thanks for the tip on the JMZ tool as well. I agree it doesn't make a lot of sense since we are going to upgrade manually again anyway. But perhaps it blocks OTAs even after we arrive back at 5.3.1.1?
Click to expand...
Click to collapse
make_space_v02.zip, which is flashed as part of the tutorial Killa8 linked to, should take care of that.
Ahhh, perfect. Out of curiosity, did you re-upgrade to the current FireOS or go the way of CM? I want something that helps with this atrocious battery life. I'm convinced it's Amazon's OS as I saw a huge increase in battery life when I replaced FireOS with CM on the Fire phones.
Just a note that all went smoothly. I decided to flash CM after downgrading to 4.5.3 and while flashing the CM11 ROM threw a mounting error for /userdata, the flash still worked perfectly. I suspect the error was due to the ROM being built for the HD 6 with a slightly different mount point for that partition.
Thanks for the help @olliebean!
I tried CM but had problems with the headphone volume being too low. Also I didn't want to go back to KitKat after being used to Lollipop. In the end I reinstalled FireOS 5.3.1.1 along with Gapps and Xposed, and changed the default launcher to Nova, which makes it feel pretty much the same as stock Android. As far as battery life goes, I installed Greenify and AppOps and blocked the Keep Awake permissions of Amazon Metrics Service Application, Content Management Service, and Google Play Services (these being the ones that showed up most in Wakelock Detector), and my battery life is fine.
olliebean said:
I tried CM but had problems with the headphone volume being too low. Also I didn't want to go back to KitKat after being used to Lollipop. In the end I reinstalled FireOS 5.3.1.1 along with Gapps and Xposed, and changed the default launcher to Nova, which makes it feel pretty much the same as stock Android. As far as battery life goes, I installed Greenify and AppOps and blocked the Keep Awake permissions of Amazon Metrics Service Application, Content Management Service, and Google Play Services (these being the ones that showed up most in Wakelock Detector), and my battery life is fine.
Click to expand...
Click to collapse
You know, you hit it on the head. I went on a trip today and both my daughters' complained they couldn't hear the movies playing. I check it out perplexed and, sure enough, finally realized this is a known bug. Pretty catastrophic for my purposes.
Going to do exactly what you did, thanks for the specific guidance! Much appreciated.
I should probably mention, I also used Titanium Backup to freeze all the built-in Amazon apps I wasn't using, which may well have had an effect on the battery life.
can someone recommend a good ROM for my 4th gen HD 7?
Looking for a more "classic" android experience.
Orvis25 said:
can someone recommend a good ROM for my 4th gen HD 7?
Looking for a more "classic" android experience.
Click to expand...
Click to collapse
This thread literally discusses your available options.