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.
My KF HDX 7 is in 13.3.2.1, I had tried to up Gapps rom v2 but it don't work, I must factory reset and go back to stock rom.
Is there any rom that can my kindle can up???
Sory for my bad English
none.
tuilakhang said:
My KF HDX 7 is in 13.3.2.1, I had tried to up Gapps rom v2 but it don't work, I must factory reset and go back to stock rom.
Is there any rom that can my kindle can up???
Sory for my bad English
Click to expand...
Click to collapse
Do a manual upate to 13.3.2.2 ,root then the new thor rom will work with safestrap 3.75b02
jimyv said:
Do a manual upate to 13.3.2.2 ,root then the new thor rom will work with safestrap 3.75b02
Click to expand...
Click to collapse
Can you give me a link of 13.3.2.2 cause I had searched around but can't saw any link but 13.3.2.4
ok
tuilakhang said:
Can you give me a link of 13.3.2.2 cause I had searched around but can't saw any link but 13.3.2.4
Click to expand...
Click to collapse
There are multiple pages to these forums, for example if you open up the general section and you look at the bottom of the page it gives you option to go to the next page several pages worth of information there same goes with each subsection. There is also a( search this thread) option in the right upper of your page. If you are still reading by chance and you will find that updates you need for either Apollo or Thor on the bottom of page four in the general section.
Didnt already bricked one of your devices here? If you are one of the fellows that bricked I would advise you to learn how to use these forums efficiently before you break another device. If not then at the very least you need to do more homework at least figure out how to use this site efficiently into everyone's benefits. Most of us are here to help those that first at least are trying to help themselves. Good luck and enjoy.
Apparently pressing "ESC" in this window deletes all the text without being able to undo this.... so here goes again....
Sorry for the late reply, but i just saw your post in the developer's forum (Cpasjuste's Thor Gapps), where i cannot post due to my lurker nature.
i'm on the same FireOS version as you: 13.3.2.1
i had trouble getting Cpasjuste's ROM to work, because i was trying to use thor-gapps-13.3.0.0-v2. i didn't dare using thor-gapps-13.3.2.4-v1, because of the several warnings.
i then saw someone else having success with thor-gapps-13.3.2.4-v1 on an earlier version and thought i'd give it a try after all. i took the risk of closing the door to an unlocked bootloader, i took the risk of bricking my device. i decided to do this, because of my year long experience with custom ROMs, also on devices that were not intended to have them (Nook HD+, Kindle Fire...). i'm not sure, if the kernel is touched during the flash process, but i assum(ed) it isn't. i can boot into FireOS which still shows 13.3.2.1 as version, but who knows what has happened under the hood.
The ROM feels stable so far for such an early version. i haven't tested much, but the few apps I've been using regularly worked well. Ironically the amazon appstore crashed after about 20 seconds. Makes me think they are trying to block the "freed" devices, but it might just be a bug after all.
So, again, if you feel like risking to lose the possibility of an unlocked bootloader, if you want to risk or can afford to brick such an expensive device, you can try using thor-gapps-13.3.2.4-v1.
All i did, was to follow the instructions provided in Cpasjuste's thread exactly as they were.
Don't hold me accountable, it's already been a week, but if i recall correctly, these were my steps:
DIsable WiFi / Enable Airplane mode in FireOS (just to prevent automatic OTA updates)
Root device (i used towelroot)
Install Safestrap (i had to use Safestrap-Thor-3.75-os3.2.4-B02.apk, despite the instructions in the safestrap thread telling to use 3.72 on our version - another risk i took)
Boot into Safestrap
Backup Original ROM
Create ROM Slot (keep this new slot active/activated)
Restore Original ROM backup, but only the DATA partition
Wipe Cache + Dalvik Cache
Flash thor-gapps-13.3.2.4-v1.zip
Wipe Cache + Dalvik Cache
Boot into system
I'm happy to say I will be an owner of a Kindle Fire HDx 7in.- lte/4g- 32 gb tablet. A Thor? Unless that is just the wireless one. I was contemplating an ipad for weeks, but what I wanted was easily $550- So when I saw the specs on this tablet at half the price, I pushed the button! Picked it up at Amazon's $100 off sale tuesday. $285 with tax. Minus $78 in amex points- grand total of $200 and change
My past modding was on the old white PDN e-reader that was turned into a touch tablet. lol. That had cupcake on it or was it donut??:silly: That's where I learned the basics of adb (I'm pretty bad at it but can follow directions and get the job done, at least 7-8 years ago. I'm pretty rusty at adb now. The toolkits that you guys put together spoiled me- but I did at one time do it the old fashioned way. I hope never again!!! I went cross eyed. Oh, forgot the huawei hs7 too- That took some doing too. That was after the PDN.
I graduated to the TF 101- rooted and rom'd that till it was replaced by the Nexus 7 original-I will never buy a new-never before released- product again after that one, Still have it, passed it to my daughter and she loves it. 3 months after I was one of the first owners, they dropped the price, doubled the storage space to 32 gb, and gave compensation to everyone in the world but us here in the USA. My relationship with Asus products is over. Somewhere along the way I got a nook wifi and hacked that too.
I moved next to samsung, modded the galaxy nexus, the orig. Note, a Note 8 wifi, have a Mega att version ( locked bootloader, and now unrootable on kitkat 4.4 2 so far. TR v. 1-2-3 does not work for it) Love the Note 8, but the screen is a bit fuzzy- so it was the ipad or the kindle hdx. The bargain won. With similar specs, I 'm giving it a try.
Along my history- Never had any trouble or lossed a phone or tablet due to bad flashing or modding. I read 3-4 times or more, and I follow directions pretty well to the letter.
Here is my question. Sorry if I bored you. ( Looked for an intro thread, but didn't find one.) When I get this tablet on Friday, I don't want it to auto update. I don't want to change the build prop. So after I make my adjustments, I want to make sure it doesn't update on me. Does it update over internet data connection, or just wifi?
Here is what I want to do. I Will not connect to wifi. Will check the build number I am on. If I have to, I will manually update to the best safest build by putting it in the root of the sd card, and going to update tool- not connected to the internet, and install. I have been reading all the threads here. What is the safest build if I want to possibly unlock the bootloader when it is released?? and of course root, and install google playstore?
Using the toolkit( v.0.94) I will:
1. Install driver.
2. Use TR v1 and root. Probably with the toolkit. @Faznx92- great job pulling it all together in one place. Thank you. Will by using Toolkit v.0.94.
3.. Install supersu.
4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
5. Block OTA updates with #4- Does this still work on the latest, safest build?
6. Install the exposed framework, and modules, and check appropriate boxes, Reboot in between installs.
7. Install the 4 google apks in the instructions- manager, services, store, framework- and reboot.
8. Check if OTA updates are indeed blocked looking for the OTA update failed!! :
9. turn on wifi and get tmobile free data started.
Is there any way to BU original firmware before installing HDxposed stuff and google apps? Without safestrap? ( I never used that before and it intimidates me a little I also understand it is a little iffy to remove it safely. Can you just re-install a manual update to recover if things go south? After reversing all the apks, modules, root, etc. after a factory reset?
To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
Does this sound like a good plan? It's what I picked up after reading for the last 24 hrs.- not straight of course!!:silly: Did I miss anything important?? Do I have anything backwards?? Would love some feedback. My first preference would be to leave it alone for a few weeks, but my priority is to avoid the updates, but be able to use and set up my tablet the way I want.
If the bootloader is ever cracked and released- Yes I have read the deed is done, but in testing- I would like to install a stable custom recovery, make good backups, and be able to reinstall if things go south any stable rom I have tucked away.
Thank you for your time if you read this whole post!!
sashusmom said:
I'm happy to say I will be an owner of a Kindle Fire HDx 7in.- lte/4g- 32 gb tablet. A Thor? Unless that is just the wireless one. I was contemplating an ipad for weeks, but what I wanted was easily $550- So when I saw the specs on this tablet at half the price, I pushed the button! Picked it up at Amazon's $100 off sale tuesday. $285 with tax. Minus $78 in amex points- grand total of $200 and change
My past modding was on the old white PDN e-reader that was turned into a touch tablet. lol. That had cupcake on it or was it donut??:silly: That's where I learned the basics of adb (I'm pretty bad at it but can follow directions and get the job done, at least 7-8 years ago. I'm pretty rusty at adb now. The toolkits that you guys put together spoiled me- but I did at one time do it the old fashioned way. I hope never again!!! I went cross eyed. Oh, forgot the huawei hs7 too- That took some doing too. That was after the PDN.
I graduated to the TF 101- rooted and rom'd that till it was replaced by the Nexus 7 original-I will never buy a new-never before released- product again after that one, Still have it, passed it to my daughter and she loves it. 3 months after I was one of the first owners, they dropped the price, doubled the storage space to 32 gb, and gave compensation to everyone in the world but us here in the USA. My relationship with Asus products is over. Somewhere along the way I got a nook wifi and hacked that too.
I moved next to samsung, modded the galaxy nexus, the orig. Note, a Note 8 wifi, have a Mega att version ( locked bootloader, and now unrootable on kitkat 4.4 2 so far. TR v. 1-2-3 does not work for it) Love the Note 8, but the screen is a bit fuzzy- so it was the ipad or the kindle hdx. The bargain won. With similar specs, I 'm giving it a try.
Along my history- Never had any trouble or lossed a phone or tablet due to bad flashing or modding. I read 3-4 times or more, and I follow directions pretty well to the letter.
Here is my question. Sorry if I bored you. ( Looked for an intro thread, but didn't find one.) When I get this tablet on Friday, I don't want it to auto update. I don't want to change the build prop. So after I make my adjustments, I want to make sure it doesn't update on me. Does it update over internet data connection, or just wifi?
Here is what I want to do. I Will not connect to wifi. Will check the build number I am on. If I have to, I will manually update to the best safest build by putting it in the root of the sd card, and going to update tool- not connected to the internet, and install. I have been reading all the threads here. What is the safest build if I want to possibly unlock the bootloader when it is released?? and of course root, and install google playstore?
Using the toolkit( v.0.94) I will:
1. Install driver.
2. Use TR v1 and root. Probably with the toolkit. @Faznx92- great job pulling it all together in one place. Thank you. Will by using Toolkit v.0.94.
3.. Install supersu.
4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
5. Block OTA updates with #4- Does this still work on the latest, safest build?
6. Install the exposed framework, and modules, and check appropriate boxes, Reboot in between installs.
7. Install the 4 google apks in the instructions- manager, services, store, framework- and reboot.
8. Check if OTA updates are indeed blocked looking for the OTA update failed!! :
9. turn on wifi and get tmobile free data started.
Is there any way to BU original firmware before installing HDxposed stuff and google apps? Without safestrap? ( I never used that before and it intimidates me a little I also understand it is a little iffy to remove it safely. Can you just re-install a manual update to recover if things go south? After reversing all the apks, modules, root, etc. after a factory reset?
To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
Does this sound like a good plan? It's what I picked up after reading for the last 24 hrs.- not straight of course!!:silly: Did I miss anything important?? Do I have anything backwards?? Would love some feedback. My first preference would be to leave it alone for a few weeks, but my priority is to avoid the updates, but be able to use and set up my tablet the way I want.
If the bootloader is ever cracked and released- Yes I have read the deed is done, but in testing- I would like to install a stable custom recovery, make good backups, and be able to reinstall if things go south any stable rom I have tucked away.
Thank you for your time if you read this whole post!!
Click to expand...
Click to collapse
Most of your questions have been answered before but I will try my best to re-answer them. I will try to clear up any misguided understanding you may have.
-Does it update over internet data connection, or just wifi?
+It updates over a internet connection.
-What is the safest build if I want to possibly unlock the bootloader when it is released??
+We don't know yet. Stay on the version you're on for now.
-4. I don't want to mess with safestrap for now, so I will pass on that. Is that OK to do??
+If you don't know much about what it does it's best for you not to worry. Yes, it's fine to leave safestrap alone.
-5. Block OTA updates with #4- Does this still work on the latest, safest build?]
+Yes, it works. The only time it may change up is if Amazon pushes a update with different package names or functions.
-Is there any way to BU (Back-up?) original firmware before installing HDxposed stuff and google apps without safestrap?
+No. I'm not aware of any other way to backup the stock rom.
-Can you just re-install a manual update to recover if things go southafter reversing all the apks, modules, root, etc. after a factory reset?
+You can't re-install a update. You can factory reset it.
-To undo the install of the play store, you just uninstall all of the above and unroot via supersu? And reverse the OTA blocking?
+There is no need to uninstall play store before a factory reset because the reset wipes it out. You should un-root via SuperSU and remove my ota block. (I reset while root but was unsure how safe it was. It did work out in the end without issue.)
Keep the wifi off once you undo the ota block and then factory reset so you don't update. Once the reset is done, re-install the blocker. I'm not sure if you need to remove safestrap before a factory reset.
To make clear:
If you install a ota blocker it's good to check that it works by being connected to the net and then going to Settings->Device->System Updates->Check now. If it says Last update failed it is working else it is not.
The current roms for the hdx require Hashcode's safestrap. But to get the rom's working you need a backup of the stock rom or you could use the backup he provided. Once a slot is made you would install the rom zip to the slot.
I believe safestrap works be emulating a new system/data/cache partition in a file as a full rom to the bootloader. I recommend blocking ota before you make a backup or installing a basic stock rom. If you create and install the stock rom to a rom slot without blocking ota, the amazon system files are still in place to call for a update and hand it off to the system and bootloader.
Safestrap is safe as long as you do not touch the stock rom but only to make a backup of it.
If you don't feel comfortable using safestrap then don't.
Quick word of advise, you should include the version of your device when asking questions for that version. I'm guessing your on 13.3.2.4, the current latest.
Also I highly recommend staying on your current version and not moving forward.
Last thing, give this a read.
I hope I answered your questions as clear as possible.
Anybody else please clear up anything I missed.
Also good luck with your device and play safe.
Thank you so much Faznx92 for reinforcing all that I read ( lots in a short time period). I didn't want to mix up the info I read from the beginning of the year to where this tab is now. You did clear up anything I was unsure about. Thank you! And safestrap- I am not comfortable with it at all- there is no safestrap for my Mega, all my other tech toys have unlocked bootloaders. So I have absolutely no experience with this custom recovery. I am used to CWM and TWRP. Totally comfortable with them, although I have to admit kitkat twisted my arm to try TWRP since that was the only way to flash those roms on a lot of tablets and phones. Now I am partial to that. So I won't say no to safestrap, just now when an unlock is so close. If a safestrap was released for my Mega, I would definitely give it a try.
Oh, I know to report what build I am on when asking questions- that's just polite and informative, right?? But I am not getting this tab till tomorrow, at least that's what tracking says. So I don't know yet. When I check the build I will post back and let you know what they are shipping now with. Hopefully it is still rootable and eligible for unlocking the bootloader when that is released. That is very exciting!
I give you credit for reading my epic long post, and thank you for taking the time to address my concerns. I appreciate it! I'll check back in tomorrow afternoon. Mail comes late where I am.
Your link was the First thing I read on this forum!!!! Which is why I am sticking with what I am comfortable with. Also, in my case I only learn by doing. But I have always realized that hacking leads to problems sometimes. My motto is stay calm, and reach out for help. Panic doesn't solve anything. And if you are hacking your only phone that you rely on, be prepared to go buy a cheap prepaid phone to bail you out till you straighten out your expensive semi brick! lol. I've gone from holding my breath when hitting go, to just being curious on how to do stuff and finding out how things work. I guess I'm living life backwards!! I can afford it at this point in my life.
Just received my kindle HDx 7 from Amazon.
So, I placed this order 1 am Wed. morning- the sale must have been on PST. Took free shipping- non prime. Received on Friday around noon. Way ahead of the promised date.
The build received was 13.3.2.1. Sim chip was installed and connected to the internet, so I took it out as a precaution even though it is not yet asso. with an account. Skipped wifi set up till I get OTA updates halted. Now it's time to play!
I Really like the size of this tablet.
@Faznx92, now that I know I am on build 13.3.2.1 do you recommend I update manually to 13.3.2.4 or can I stay on this one?
Thanks for your advice and help. Rooted, OTA blocked and confirmed, superuser installed, binary updated. I will hold off on google stuff for now and see how this OS works.
sashusmom said:
@Faznx92, now that I know I am on build 13.3.2.1 do you recommend I update manually to 13.3.2.4 or can I stay on this one?
Thanks for your advice and help. Rooted, OTA blocked and confirmed, superuser installed, binary updated. I will hold off on google stuff for now and see how this OS works.
Click to expand...
Click to collapse
I'm still on 13.3.1.0 and not moving any time soon.
13.3.2.1 is fine.
Stay on your version!
Also you will need to registered your device.
Faznx92 said:
I'm still on 13.3.1.0 and not moving any time soon.
13.3.2.1 is fine.
Stay on your version!
Also you will need to registered your device.
Click to expand...
Click to collapse
Thank you! I will hold where I am then. I guess since I bought it from amazon- an account I already had there- when I connected to wifi it sort of registered itself and associated it with my amazon account by Magic!!:silly:
I do have to say just using the native kindle OS, I am not a fan. I will be installing the HDxposed modules and google stuff. :fingers-crossed:
Yeap, magic brick lol Hopefully not for you though, you seem to have done a little homework. I would be thorough with your own research at least skim the threads of the modifications you wish to do just to see what problems other people have had may save you a lot of trouble. Good luck
jimyv said:
Yeap, magic brick lol Hopefully not for you though, you seem to have done a little homework. I would be thorough with your own research at least skim the threads of the modifications you wish to do just to see what problems other people have had may save you a lot of trouble. Good luck
Click to expand...
Click to collapse
Thanks jimyv Everything went as planned, couple hiccups that I solved by all the info posted here in this forum
The only thing I seem to have a problem with is sideloading apps now. It worked prior to downloading the google platform, but I can't seem to install from my sd card, app installers, or dropbox. I went back and checked that unknown sources is checked, and adb is turned on.
I had this same problem on my Note 8 on totally stock with just root applied and philz touch recovery. I fixed it by installing a stock hacked kitkat rom and that solved the problem.
Anyone have any ideas? Not too much of a problem since the play store/ market is up and running. I wanted to install samsung milk music that did install on my note 8 (not approved for that tablet). When sideloading was working for the hdx 7 I could load that apk, but it refused to install.
Now nothing will happen when I try to install any apk from dropbox or app installer. The buttons don't respond. If that's my only problem I can live with that!!
too much
sashusmom said:
Thanks jimyv Everything went as planned, couple hiccups that I solved by all the info posted here in this forum
The only thing I seem to have a problem with is sideloading apps now. It worked prior to downloading the google platform, but I can't seem to install from my sd card, app installers, or dropbox. I went back and checked that unknown sources is checked, and adb is turned on.
I had this same problem on my Note 8 on totally stock with just root applied and philz touch recovery. I fixed it by installing a stock hacked kitkat rom and that solved the problem.
Anyone have any ideas? Not too much of a problem since the play store/ market is up and running. I wanted to install samsung milk music that did install on my note 8 (not approved for that tablet). When sideloading was working for the hdx 7 I could load that apk, but it refused to install.
Now nothing will happen when I try to install any apk from dropbox or app installer. The buttons don't respond. If that's my only problem I can live with that!!
Click to expand...
Click to collapse
If you are trying to install into system it may be too crowded
Personally I use titanium back up and it shows the size of the ROM I only have like 34 MB left of room after installing gapps. And if you are using safestrap by chance you need to remake your slot delete the slot first then go to remake it it will show available space. I increase that cache by 200 MB then use the rest of my available space up in the data partition then create slot .
jimyv said:
If you are trying to install into system it may be too crowded
Personally I use titanium back up and it shows the size of the ROM I only have like 34 MB left of room after installing gapps. And if you are using safestrap by chance you need to remake your slot delete the slot first then go to remake it it will show available space. I increase that cache by 200 MB then use the rest of my available space up in the data partition then create slot .
Click to expand...
Click to collapse
No safestrap. I have a 32 GB. Is the internal partition for installing apps tiny on this tablet? I got the 32 gb so I wouldn't have this problem. Stock other than being rooted and having the HDxposed modules with google market installed. That might be taking up the room.
I have 1.1 GB of apps, system apps are close to 397 mb. I have 21 GB free.
************************************************************************
Must have been a space problem. I deleted AngryBirdsSpace and was able to install Adobe flash and Cerberus. Milk music still will not install, so don't think that is the issue with that one. It did install last week on my Note8 and my Mega so maybe because it's a samsung app??
Will Titanium BU work for moving apps to the sd card on this device? And free up space that way?
I can't seem to find the move to sd card on a long press with tit.BU, so I guess not.
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.
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.