Related
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.
H,
You might have seen here http://forum.xda-developers.com/kindle-fire-hdx/general/success-downgrading-t3047619/post59263205#post59263205 I managed to relatively seamlessly get my HDX rooted, adds removed and Nova Launcher installed - also using a different lock-screen.
All good, but I am now concious that I should back it up - I know there are scores of threads re TWERP and Safestrap - but can someone offer me a quick bit of advice and I'll run with that?
Is TWERP safe - would defeat the object to risk my machine installing something that has been described in a thread in here as DANGEROUS?
Is there a safe way to backup/restore my current rooted device?
Thanks...
First, what OS version do you have?
Second, you don't need to backup, you can do it in case you mess around alot!
Third, TWRP and SafeStrap are completely different, if you can unlock bootloader then install TWRP and you are good to go, if you cannot unlock you could install SafeStrap (only up to 3.2.5 if im not wrong) and you can make a backup to your Stock rom slot.
Using Stock 3.2.8
No other Mods and to be honest not interesting in tweaking anymore - but would like to have a back-up and the ability to restore if needed.
aaronkatrini said:
First, what OS version do you have?
Second, you don't need to backup, you can do it in case you mess around alot!
Third, TWRP and SafeStrap are completely different, if you can unlock bootloader then install TWRP and you are good to go, if you cannot unlock you could install SafeStrap (only up to 3.2.5 if im not wrong) and you can make a backup to your Stock rom slot.
Click to expand...
Click to collapse
TWRP is out of the question, because to install it you need to have an unlocked bootloader (version below 1x.3.2.3).
Safestrap could be possible, I need a moment to check.
But i repeat no need to backup since not interested in tweaking anymore.
So, I am not sure if you can install safestrap, but I think twrp is not compatible.
aaronkatrini said:
TWRP is out of the question, because to install it you need to have an unlocked bootloader (version below 1x.3.2.3).
Safestrap could be possible, I need a moment to check.
But i repeat no need to backup since not interested in tweaking anymore.
Click to expand...
Click to collapse
Nope, safestrap up to 1x.3.2.5 check out here http://forum.xda-developers.com/showthread.php?t=2782159&page=28 post #278
Does this mean that there is no option to back up?
@myotai: There are several apk for backup...
@aaronkatrini
don't confuse people
Safestrap works on 3.2.8
(For proof, i quote from ggow's safestrap Rom for 3.2.8)
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
http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-rom-t3024526
futzmaster said:
@myotai: There are several apk for backup...
@aaronkatrini
don't confuse people
Safestrap works on 3.2.8
(For proof, i quote from ggow's safestrap Rom for 3.2.8)
http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-rom-t3024526
Click to expand...
Click to collapse
So...does this mean that I can use it on the HDX using 3.2.8 (Safely)?
futzmaster said:
@myotai: There are several apk for backup...
@aaronkatrini
don't confuse people
Safestrap works on 3.2.8
(For proof, i quote from ggow's safestrap Rom for 3.2.8)
http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-rom-t3024526
Click to expand...
Click to collapse
Mea Culpa, I did not read that, very good to have that cleared...
aaronkatrini said:
Mea Culpa, I did not read that, very good to have that cleared...
Click to expand...
Click to collapse
No no, everything is good, you tried to help :good:
The informations are spread almost randomly on several threads... hard to keep them together
So given that I am currently using 3.2.8 with Nova Launcher etc etc...what would be the advantage of using the ROM in the link previously posted?
myotai said:
So...does this mean that I can use it on the HDX using 3.2.8 (Safely)?
Click to expand...
Click to collapse
Hi Myotia - just an opinion here; others may have a different view. If your risk tolerance is low, device stable as-is, OTAs blocked (default on 3.2.8) and you won't be tinkering with other HDX builds then I wouldn't install SafeStrap. There is nothing fundamentally wrong with SafeStrap but the installation itself introduces some risks and opens 'opportunities' that many not always be beneficial. Downside is you can't reliably create a FULL system backup of all partitions using tools that run from within Android. Many do a fine job with data and other components but I have been screwed too many times trying to execute a full system restore from a dataset that wasn't created from recovery (TWRP) or via tether. Maybe others have had better luck.
If your main objective is to protect data then there are many fine tools in the Play Store that do that well.
Davey126 said:
Hi Myotia - just an opinion here; others may have a different view. If your risk tolerance is low, device stable as-is, OTAs blocked (default on 3.2.8) and you won't be tinkering with other HDX builds then I wouldn't install SafeStrap. There is nothing fundamentally wrong with SafeStrap but the installation itself introduces some risks and opens 'opportunities' that many not always be beneficial. Downside is you can't reliably create a FULL system backup of all partitions using tools that run from within Android. Many do a fine job with data and other components but I have been screwed too many times trying to execute a full system restore from a dataset that wasn't created from recovery (TWRP) or via tether. Maybe others have had better luck.
If your main objective is to protect data then there are many fine tools in the Play Store that do that well.
Click to expand...
Click to collapse
Thanks for that!
What about Titanium Back Up Pro? Seems to have been a good friend in the past? Is it not as functional without a custom ROM?
myotai said:
What about Titanium Back Up Pro? Seems to have been a good friend in the past? Is it not as functional without a custom ROM?
Click to expand...
Click to collapse
Titanium Backup is a great tool! As mentioned, just sharing my own experiences. I have yet to have a restore fail that was captured from recovery (assuming a healthy system). Once you find something that works you tend to stick with it. I haven't tried Titanium on an HDX. Others?
Davey126 said:
Titanium Backup is a great tool! As mentioned, just sharing my own experiences. I have yet to have a restore fail that was captured from recovery (assuming a healthy system). Once you find something that works you tend to stick with it. I haven't tried Titanium on an HDX. Others?
Click to expand...
Click to collapse
Titanium backup works great on CM11 for apollo, or nexus 2.0.5 for TWRP or Magic beanz 1.0.1 :good::highfive:
I'll try it on a rooted Stock with 3.2.8 then
myotai said:
I'll try it on a rooted Stock with 3.2.8 then
Click to expand...
Click to collapse
You certainly can try, but consider also that rooted stock isnt fully android compatible, there are several parts of real android system missing, removed by Amazon (or replaced by Fire OS "equivalent"), so is possible something will not work correctly.
I have similar experience with Lightning Launcher, which crashed when I try to add widget on stock rom - response from developer was clear - FireOs is not fully compatible with Android, therefore not supported.
Safestrap works on 3.2.8
Sent from my KFTHWI using XDA Free mobile app
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.
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Timmetjuh said:
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Click to expand...
Click to collapse
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Davey126 said:
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Click to expand...
Click to collapse
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Timmetjuh said:
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Click to expand...
Click to collapse
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Davey126 said:
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Click to expand...
Click to collapse
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Timmetjuh said:
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
Click to expand...
Click to collapse
Timmetjuh said:
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Click to expand...
Click to collapse
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Davey126 said:
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Click to expand...
Click to collapse
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Timmetjuh said:
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Click to expand...
Click to collapse
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It's not that I don't like the Nexus ROM, I just like to experiment with these things..
So I just installed TWRP with Flashify (started Flashify from NEXUS) and now I seem stuck at the grey Kindle fire logo. I'm just going to leave it alone for a few hours, hopefully it boots later today.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Timmetjuh said:
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Click to expand...
Click to collapse
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Davey126 said:
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Click to expand...
Click to collapse
I'm stuck at the grey Kindle logo..
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Timmetjuh said:
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Click to expand...
Click to collapse
Congrats! Had a bad feeling after your earlier post; glad that was misplaced. Enjoy CM11 and all the goodness that comes from a liberated HDX.
At some point you should consider unlocking the bootloader. That will provide an important fail safe should things go wrong and opens the door to newer roms. Unlike previous flashes there is little/no risk in unlocking. It will either work or not with no adverse consequences. Unlocking can be a frustrating ride as the process involves multiple steps in unfamiliar territory but ultimately the benefits outweigh the effort IMO. Nothing that needs to be tackled right away but keep it on your radar ... especially if you plan to experiment with other roms.
Unlock bootloader
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
No. You can NOT unlock the bootloader! You can NOT downgrade to 3.2.4 and then further to 3.1.0/3.2.3.2! DON'T attempt to do so, you will brick your HDX!
Your only available option is to stay on 4.5.2 and use Safestrap v4 with either Nexus and/or CM11.
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Davey126 said:
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Click to expand...
Click to collapse
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
slothdabski said:
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
Click to expand...
Click to collapse
I actually just got it working by running the following as SU in terminal emaulator
# ip route add default dev tun0 scope link
Not sure yet if I have to do this every time I tether, but if so, i think i can just make a script to execute automatically?
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!