Missing Ads on Fire 7 - Fire Q&A, Help & Troubleshooting

I have Fire 7 5th Gen that is rooted using SuperTool on FireOS 5.1.1. I disabled auto system updates. For some reason, Ads do not appear anymore. I tried rebooting and shutting down, but none of that helped. I have ADB setup and all, not sure what to do next.
Thanks in advance

seskanda said:
I have Fire 7 5th Gen that is rooted using SuperTool on FireOS 5.1.1. I disabled auto system updates. For some reason, Ads do not appear anymore. I tried rebooting and shutting down, but none of that helped. I have ADB setup and all, not sure what to do next.
Thanks in advance
Click to expand...
Click to collapse
Likely related to killing OTA updates. Reinstall FireOS 5.1.1 if you really want those ads.

Make double sure that it's the fireOS version that's at 5.1.1, not the generic Android one. They are easily confused, and may result in bricks. If in doubt, check the bootloader timestamp (inside the partition) - should be 20150923-180133 for your OS.
If you need to reinstall/re-root, precautions are in place. You decide whether getting ads is wirth risking root at all.

Davey126 said:
Likely related to killing OTA updates. Reinstall FireOS 5.1.1 if you really want those ads.
Click to expand...
Click to collapse
I see, but we also have an old Fire HD 7 2nd gen that is rooted and still shows ads. How can it have ads but this newer one does not? If I re-install FireOS 5.1.1, will it turn off OTA updates and/or remove root?
Where can I find the right version of FireOS 5.1.1? I do not want to lose root just for some ads.

seskanda said:
I see, but we also have an old Fire HD 7 2nd gen that is rooted and still shows ads. How can it have ads but this newer one does not? If I re-install FireOS 5.1.1, will it turn off OTA updates and/or remove root?
Where can I find the right version of FireOS 5.1.1? I do not want to lose root just for some ads.
Click to expand...
Click to collapse
The SuperTool disables a bunch of different stuff depending on FireOS build; the local ad server likely got caught up in that.
Reloading FireOS will remove root and enable OTA updates. With WiFi enabled the device would immediately be exposed to an wanted update to FireOS 5.6 which can not be rooted. You also need to be confident of the current FireOS version to avoid bricking the device; see previous post by @steve8x8.
In your shoes I'd leave things as-is. But if you really need to see those ads past FireOS builds can be found here.

Davey126 said:
The SuperTool disables a bunch of different stuff depending on FireOS build; the local ad server likely got caught up in that.
Reloading FireOS will remove root and enable OTA updates. With WiFi enabled the device would immediately be exposed to an wanted update to FireOS 5.6 which can not be rooted. You also need to be confident of the current FireOS version to avoid bricking the device; see previous post by @steve8x8.
In your shoes I'd leave things as-is. But if you really need to see those ads past FireOS builds can be found here.
Click to expand...
Click to collapse
I recall choosing the options to root and disable OTA updates, and that's all. I did not pick the one to turn off lock screen ads.
So if I root and then disable OTA updates, the ads will stop completely? What does OTA updates do with lock screen ads? If that is the case, there is really no need for me to re-install FireOS at this point. I think the FireOS builds from the link you gave are fine to use.
I do not see the benefit of ads if it breaks root or keeps OTA updates on.

seskanda said:
I recall choosing the options to root and disable OTA updates, and that's all. I did not pick the one to turn off lock screen ads.
So if I root and then disable OTA updates, the ads will stop completely? What does OTA updates do with lock screen ads? If that is the case, there is really no need for me to re-install FireOS at this point. I think the FireOS builds from the link you gave are fine to use.
I do not see the benefit of ads if it breaks root or keeps OTA updates on.
Click to expand...
Click to collapse
Never saw the benefit of ads. If you are happy with the status quo there is no need to take any action. Should you decide to reload FireOS:
- be 100% sure you have the correct build; using the 'wrong' version can have unfavorable outcomes
- you'll need to reroot and assume the risk of taking an unwanted OTA update during that process
- the SuperTool throws a lot of switches; some may do more than advertised, especially on older FireOS builds
- in most cases disabling OTA updates via the SuperTool does not block ads
- you'll need to take manual actions to block OTA updates and/or lock screen ads if you want more precise control
As the old saying goes "if it ain't broke don't fix it".

Davey126 said:
Never saw the benefit of ads. If you are happy with the status quo there is no need to take any action. Should you decide to reload FireOS:
- be 100% sure you have the correct build; using the 'wrong' version can have unfavorable outcomes
- you'll need to reroot and assume the risk of taking an unwanted OTA update during that process
- the SuperTool throws a lot of switches; some may do more than advertised, especially on older FireOS builds
- in most cases disabling OTA updates via the SuperTool does not block ads
- you'll need to take manual actions to block OTA updates and/or lock screen ads if you want more precise control
As the old saying goes "if it ain't broke don't fix it".
Click to expand...
Click to collapse
Actually the ads do suck overall I agree with you, just want to know why or how to fix it, that's all.
If I use the FireOS 5.1.1 in the link provided will that be the correct build for me?
If I disconnect WiFi, will that guarantee not being force-fed an OTA update?
Which version of SuperTool is the best or most stable one? Or that does not mess up lock screen ads when disabling OTA updates?
Do you know in which case will disabling OTA updates break lock screen ads?
What do you mean by this? Let's say I did disable lock screen ads via SuperTool by accident, is any way to undo that by chance?

seskanda said:
Actually the ads do suck overall I agree with you, just want to know why or how to fix it, that's all.
If I use the FireOS 5.1.1 in the link provided will that be the correct build for me?
If I disconnect WiFi, will that guarantee not being force-fed an OTA update?
Which version of SuperTool is the best or most stable one? Or that does not mess up lock screen ads when disabling OTA updates?
Do you know in which case will disabling OTA updates break lock screen ads?
What do you mean by this? Let's say I did disable lock screen ads via SuperTool by accident, is any way to undo that by chance?
Click to expand...
Click to collapse
Lots of questions that would take much back-and-forth to definitively answer. Many would love to be in your shoes. You have a rooted, working system with no ads or notable deficits. Enjoy your device.

Davey126 said:
Lots of questions that would take much back-and-forth to definitively answer. Many would love to be in your shoes. You have a rooted, working system with no ads or notable deficits. Enjoy your device.
Click to expand...
Click to collapse
Appreciate if you could answer the first question and any question about SuperTool. Or else, if someone can chime in that'd be fine also.

seskanda said:
Appreciate if you could answer the first question and any question about SuperTool.
Click to expand...
Click to collapse
You need to verify with 100% certainty which version of FireOS your device is currently running. Many confuse Android 5.1.1, which is the base for all FireOS v5 builds with a specific FireOS version number. The latter is all that matters and should be shown under Settings->System Updates (details).

Davey126 said:
You need to verify with 100% certainty which version of FireOS your device is currently running. Many confuse Android 5.1.1, which is the base for all FireOS v5 builds with a specific FireOS version number. The latter is all that matters and should be shown under Settings->System Updates (details).
Click to expand...
Click to collapse
I see, according to Settings-->System Updates it is FireOS 5.1.1. Does that mean the one linked here is the correct build for me?

seskanda said:
I see, according to Settings-->System Updates it is FireOS 5.1.1. Does that mean the one linked here is the correct build for me?
Click to expand...
Click to collapse
Correct. You are fortunate to be on what may view to be a 'preferred' build of FireOS. IMO the chance of taking an spontaneous OTA to an unrootable build outweighs whatever benefits might be realized given your device appears to be performing as expected sans lock screen ads. As an alternative you could simply perform a factory reset. However, the risks of an unwanted OTA sneaking in remains until the device is rerooted and updates blocked. Good luck with whatever course of action you choose.

Davey126 said:
Correct. You are fortunate to be on what may view to be a 'preferred' build of FireOS. IMO the chance of taking an spontaneous OTA to an unrootable build outweighs whatever benefits might be realized given your device appears to be performing as expected sans lock screen ads. As an alternative you could simply perform a factory reset. However, the risks of an unwanted OTA sneaking in remains until the device is rerooted and updates blocked. Good luck with whatever course of action you choose.
Click to expand...
Click to collapse
Yes, I was lucky that I rooted it quickly and disabled OTA updates at the same time. The Wifi was disconnected when I did both of that. I'm thinking If I do something similar it should end up as is now. With WiFi not connected, there is zero chance of OTA update, right? Will factory reset keep root? If not, then I might as well re-install the firmware for FireOS 5.1.1.

seskanda said:
With WiFi not connected, there is zero chance of OTA update, right? Will factory reset keep root?
Click to expand...
Click to collapse
- OTA updates are delivered via WiFi which typically must be enabled to root
- Root may or may not survive a factory reset

Davey126 said:
- OTA updates are delivered via WiFi which typically must be enabled to root
- Root may or may not survive a factory reset
Click to expand...
Click to collapse
It's been awhile since I rooted this, but do not recall needing WiFi to root, why would that be required?
Well, then I should definitely try a factory reset first before re-loading the firmware.

seskanda said:
It's been awhile since I rooted this, but do not recall needing WiFi to root, why would that be required?
Well, then I should definitely try a factory reset first before re-loading the firmware.
Click to expand...
Click to collapse
Unless using the desktop (tethered) varient KingRoot receives/retrieves 'instructions' from the cloud.

Davey126 said:
Unless using the desktop (tethered) varient KingRoot receives/retrieves 'instructions' from the cloud.
Click to expand...
Click to collapse
I use SuperTool, which is desktop (tethered) so do not internet to root. Do you know if SuperTool retains root after a factory reset?

Davey126 said:
Unless using the desktop (tethered) varient KingRoot receives/retrieves 'instructions' from the cloud.
Click to expand...
Click to collapse
I use SuperTool, which is desktop (tethered) so do not need internet to root. Do you know if SuperTool retains root after a factory reset?

seskanda said:
I use SuperTool, which is desktop (tethered) so do not need internet to root. Do you know if SuperTool retains root after a factory reset?
Click to expand...
Click to collapse
Last I knew the version of KingRoot included with the SuperTool is the standalone build which DOES need internet access. As for your second question the SuperTool has nothing to do with retaining root following a factory reset.

Related

Unable to root tablet running 5.1.2

I have a Fire 5th gen tablet running v5.1.2 and am very much looking to root it with the aim of installing stock Android. Most of the resources I found online suggest the best rooting tool is KingRoot., however after several attempts and reboots it always fails to root the tablet. Although, now that I think about it, I've come across references on this site of people who were only successful on the 4th reboot; don't think I tried that many times in a row.
Unsure if this is useful information but the tablet was bought from UK Amazon store and it states a software version has been downloaded but not yet applied.
What options do I have to root the tablet? If there is a better tool out there for the job, please let me know. Likewise, if all I need to do is downgrade the software, I'll try it. I'll do anything to rid it of Amazon's-branded version of Android.
miguelg_ said:
I have a Fire 5th gen tablet running v5.1.2 and am very much looking to root it with the aim of installing stock Android. Most of the resources I found online suggest the best rooting tool is KingRoot., however after several attempts and reboots it always fails to root the tablet. Although, now that I think about it, I've come across references on this site of people who were only successful on the 4th reboot; don't think I tried that many times in a row.
Unsure if this is useful information but the tablet was bought from UK Amazon store and it states a software version has been downloaded but not yet applied.
What options do I have to root the tablet? If there is a better tool out there for the job, please let me know. Likewise, if all I need to do is downgrade the software, I'll try it. I'll do anything to rid it of Amazon's-branded version of Android.
Click to expand...
Click to collapse
There are two different FireOS versions that report 5.1.2 and only one of them is rootable (542168620). Many user reported that the rooting process works best if the device is not yet registered to Amazon.
fmc000 said:
There are two different FireOS versions that report 5.1.2 and only one of them is rootable (542168620). Many user reported that the rooting process works best if the device is not yet registered to Amazon.
Click to expand...
Click to collapse
Yep. Also be weary of the downloaded update which will likely push your tablet to 5.3.x which is not rootable.
You can rollback FireOS 5.1.2.1 to version 5.1.2 which can be rooted. Everything you need can be found in the forum index.
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Davey126 said:
Yep. Also be weary of the downloaded update which will likely push your tablet to 5.3.x which is not rootable.
Click to expand...
Click to collapse
So how would I avoid that? Kingroot insists on internet access, and given that it often requires multiple tries, I am afraid it will give Amazon plenty of time for OTA update.
railshot said:
So how would I avoid that? Kingroot insists on internet access, and given that it often requires multiple tries, I am afraid it will give Amazon plenty of time for OTA update.
Click to expand...
Click to collapse
Partial FireOS downloads are discarded each time the device reboots. Kingroot reboots with sufficient frequency during the rooting process to prevent a full OTA update from being downloaded with a typical 'home' connection (say <50 Mbps). Another option is the desktop/tether version of Kingroot that does not require the device have a network connection. Downside is the desktop UI is in Chinese but is pretty easy to follow.
Thank you. I blocked the amazon update domains on my router (what I could find at least) and managed to root it. Good to know that it was probably not needed
railshot said:
Thank you. I blocked the amazon update domains on my router (what I could find at least) and managed to root it. Good to know that it was probably not needed
Click to expand...
Click to collapse
For the benefit of future readers: blocking domains usually does not work long term to prevent OTA updates as Amazon (or their agents) rotate sources on a regular basis. I suspect this a for load balancing and other housekeeping, not an effort to circumvent user 'blocks'.

Amazon Appstore Network Error

Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
scooter1979 said:
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
elementalcobalt said:
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
Click to expand...
Click to collapse
This won't work:
- the version of Amazon's app store is different on FireOS; I don't believe it's available for download
- I did not see the OP had wiped his data; the OS info problem is related to blocking OTA updates
---------- Post added 02-12-2017 at 12:12 AM ---------- Previous post was 02-11-2017 at 11:56 PM ----------
scooter1979 said:
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
Best solution is to install a custom ROM; however you seem satisfied with FireOS.
Next best solution IMO is to reload FireOS (which includes Amazon's app store) but you will probably want to stick with version 5.0.1 if that's what is currently installed. Obvious problem is you can't determine that through normal means. Have to be careful here; if you attempt to reload 5.0.1 and your device is currently on 5.1.x or above it will brick. You would also need to reroot, reblock OTA updates, etc. In short, everything you did before. With no guarantee it will fix your original problem (although I think it will).
One way to test for 5.0.1 is to see if it will boot TWRP. However, that can be messy if you are unfamiliar with fastboot and/or have never established a connection with the device in question.
@steve8x8 - I seem to recall you wrote a tool that can query current component/system levels. Thoughts?
p.s. You could also go with FireOS 5.3.1 which is the last build that can be rooted at present. No brick risk as 5.3.1 is >= the current version of FireOS on the device.
elementalcobalt said:
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
Click to expand...
Click to collapse
It's not the clock, that's as it should be.
Davey126 said:
This won't work:
- the version of Amazon's app store is different on FireOS; I don't believe it's available for download
- I did not see the OP had wiped his data; the OS info problem is related to blocking OTA updates
---------- Post added 02-12-2017 at 12:12 AM ---------- Previous post was 02-11-2017 at 11:56 PM ----------
Best solution is to install a custom ROM; however you seem satisfied with FireOS.
Next best solution IMO is to reload FireOS (which includes Amazon's app store) but you will probably want to stick with version 5.0.1 if that's what is currently installed. Obvious problem is you can't determine that through normal means. Have to be careful here; if you attempt to reload 5.0.1 and your device is currently on 5.1.x or above it will brick. You would also need to reroot, reblock OTA updates, etc. In short, everything you did before. With no guarantee it will fix your original problem (although I think it will).
One way to test for 5.0.1 is to see if it will boot TWRP. However, that can be messy if you are unfamiliar with fastboot and/or have never established a connection with the device in question.
@steve8x8 - I seem to recall you wrote a tool that can query current component/system levels. Thoughts?
p.s. You could also go with FireOS 5.3.1 which is the last build that can be rooted at present. No brick risk as 5.3.1 is >= the current version of FireOS on the device.
Click to expand...
Click to collapse
You are correct, I am happy with the FireOS.
I've played in fastboot before, and given EXACT instructions, I can regurgitate results, but it's not my native tongue. I don't know if the appstore version is locked to the OS version, but according to Appstore Settings under the manage Amazon apps section, I'm rocking release-9.1011.5.1.39.0_2000145010, last updated 2/12/15. Any way to link that with OS version?
If no more info can be gleaned from my device, either from the appstore version or something steve8x8 may have, I may just load 5.3.1 on and run from there. Kinda rather not, but I'd kinda rather not not have appstore access.
scooter1979 said:
... I've played in fastboot before, and given EXACT instructions, I can regurgitate results, but it's not my native tongue. I don't know if the appstore version is locked to the OS version, but according to Appstore Settings under the manage Amazon apps section, I'm rocking release-9.1011.5.1.39.0_2000145010, last updated 2/12/15. Any way to link that with OS version?
If no more info can be gleaned from my device, either from the appstore version or something steve8x8 may have, I may just load 5.3.1 on and run from there. Kinda rather not, but I'd kinda rather not not have appstore access.
Click to expand...
Click to collapse
To my knowledge there is no direct correlation of appstore version to FireOS version. Obviously there's a range but we'd need a 1-1 match to draw a comfortable conclusion.
You can test TWRP bootability by following the guidance in this post. If TWRP boots you can safely sideload FireOS 5.0.1 from here using instructions in this thread (posts #1 and #2). That said, if you have no intention of every installing a custom ROM there really isn't any advantage to retaining an older bootloader. If that's the case might as well sideload FireOS 5.3.1. Be aware there is no going back if you take this step.
Davey126 said:
To my knowledge there is no direct correlation of appstore version to FireOS version. Obviously there's a range but we'd need a 1-1 match to draw a comfortable conclusion.
You can test TWRP bootability by following the guidance in this post. If TWRP boots you can safely sideload FireOS 5.0.1 from here using instructions in this thread (posts #1 and #2). That said, if you have no intention of every installing a custom ROM there really isn't any advantage to retaining an older bootloader. If that's the case might as well sideload FireOS 5.3.1. Be aware there is no going back if you take this step.
Click to expand...
Click to collapse
Ahhhh nuts. I'm getting "FAILED (remote: unknown command)" return on my Win7 machine trying to boot TWRP, and just simple USB transmission OK output on the device. Looks like I'm over 5.0.1.
Guess it's 5.3.1 for me. I'm assuming I can just follow the directions from sd_shadow's unbrick stock recovery ADB sideload thread, yes? Thanks for all of your help, I really appreciate it.
There's a guide to find bootloader version: https://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Sent from my Amazon Fire using XDA Labs
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
scooter1979 said:
Ahhhh nuts. I'm getting "FAILED (remote: unknown command)" return on my Win7 machine trying to boot TWRP, and just simple USB transmission OK output on the device. Looks like I'm over 5.0.1.
Guess it's 5.3.1 for me. I'm assuming I can just follow the directions from sd_shadow's unbrick stock recovery ADB sideload thread, yes? Thanks for all of your help, I really appreciate it.
Click to expand...
Click to collapse
Just be sure that you don't accidentally update. Don't connect to WiFi until you have KingRoot, and be sure not to let the os update finish downloading. Once you connect, it will start. Some tips I found on how to avoid updates:
Davey126 said:
- use Kingroot 4.92 or lower; avoid v5.x (nearly impossible to remove)
- partial OTA update files are erased each time the device reboots
- KingRoot reboots frequently
- find a slow AP (library, coffee shop, etc) to thoddle the pace of downloads
- enable WiFi only after KingRoot starts and kill it when run completes
- force reboot device if KingRoot hangs for a prolonged period
- you may have to repeat the process multiple times
- there are trickier approaches (eg: IP/domain blocking) with variable results; the above playbook has worked well for most
- good luck
Click to expand...
Click to collapse
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
Just be sure that you don't accidentally update. Don't connect to WiFi until you have KingRoot, and be sure not to let the os update finish downloading. Once you connect, it will start. Some tips I found on how to avoid updates:
s
Click to expand...
Click to collapse
Along with not hooking up wifi immediately, I was thinking of using rootjunky's supertool for root & update blocking, as the tool says it's now compatible with 5.3.1. Should be good enough, as long as I don't connect to a network until ALL of the supertool fun is done (I hope).
scooter1979 said:
Along with not hooking up wifi immediately, I was thinking of using rootjunky's supertool for root & update blocking, as the tool says it's now compatible with 5.3.1. Should be good enough, as long as I don't connect to a network until ALL of the supertool fun is done (I hope).
Click to expand...
Click to collapse
You need WiFi to root. That's why you need to be careful, since update starts quickly. Here's the thread the quote was from: https://forum.xda-developers.com/amazon-fire/help/dilemma-t3545062
If you can block the domains linked to in that thread, that'll help. It's not necessary, but it's a good idea.
EDIT: here's the post with them:
HughJeffner said:
Using stock 5.3.1 fresh install here are the domain names used in the update process:
softwareupdates.amazon.com
amzdigital-a.akamaihd.net
The first one is the actual update check, blocking DNS lookup of this domain effectively disabled auto-updates for me YMMV
The second domain name is where the firmware is actually downloaded from (not verified but seems probable). Note that this could change depending on how the update check is implemented.
I recommend blocking DNS resolution of softwareupdates.amazon.com if practical in your situation
Click to expand...
Click to collapse
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
You need WiFi to root. That's why you need to be careful, since update starts quickly. Here's the thread the quote was from: https://forum.xda-developers.com/amazon-fire/help/dilemma-t3545062
If you can block the domains linked to in that thread, that'll help. It's not necessary, but it's a good idea.
Click to expand...
Click to collapse
Ohhhhh, I didn't realize Kingroot needs internet access... Besides that, I saw in the tool's changelogs that it even removes Kingroot & puts the normal supersu in the system, so I thought everything was more or less a "normal" rooting procedure. Whoops. Thank you, I'll be DNS blocking before anything.
scooter1979 said:
Ohhhhh, I didn't realize Kingroot needs internet access... Besides that, I saw in the tool's changelogs that it even removes Kingroot & puts the normal supersu in the system, so I thought everything was more or less a "normal" rooting procedure. Whoops. Thank you, I'll be DNS blocking before anything.
Click to expand...
Click to collapse
It removes KingRoot after using it to root. AFAIK, KingRoot is the only thing that can root these tablets. Personally, I'd recommend finding your bootloader version and flashing that, but it's just a personal preference, and has no practical difference unless you have 5.0.x, which you don't. I just like having oldest I can in case a downgrade method is ever found.
Also I may have an updated appstore apk from my brother's 5.3.2.1 tablet, let me check.
EDIT: Nope, I don't. I do, however, have an (old) apk from the Amazon website. See if installing this version helps. Just out of curiosity, could you attach the apk from your current appstore? I'm wondering if it will install on Fire Nexus. The UI looks much better than the version I have downloaded.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
Just out of curiosity, could you attach the apk from your current appstore? I'm wondering if it will install on Fire Nexus. The UI looks much better than the version I have downloaded.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
I'll be happy to if you give me the path, or even the full name of the apk so I can search via root explorer.
scooter1979 said:
I'll be happy to if you give me the path.
Click to expand...
Click to collapse
If you have a file manager, search /system/app and /system/priv-app for com.amazon. venezia. Or, use an app like titanium backup to back it up.
It's taking forever to upload the apk I'm using, so here's the link if you want to test if it works: https://www.amazon.com/appstore_android_app
If not, I think you will need to reflash, unfortunately.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
There's a guide to find bootloader version: https://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Click to expand...
Click to collapse
Used this method, I'm on 5.1.1 (5.4.1_112720 5.1.1). Dagnabbit, missed it by that much.
scooter1979 said:
Used this method, I'm on 5.1.1 (5.4.1_112720 5.1.1). Dagnabbit, missed it by that much.
Click to expand...
Click to collapse
Then I'd recommend flashing 5.1.1. Like I said, if a downgrade method is found, it will probably be for older versions. Plus it's harder to brick, since only one or two versions are below it.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
It's taking forever to upload the apk I'm using, so here's the link if you want to test if it works: https://www.amazon.com/appstore_android_app
If not, I think you will need to reflash, unfortunately.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
No go. Got a "Application Not Installed" error.
PorygonZRocks said:
Then I'd recommend flashing 5.1.1. Like I said, if a downgrade method is found, it will probably be for older versions. Plus it's harder to brick, since only one or two versions are below it.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
The thing there is, if the issue is indeed related to the age of the appstore, which doesn't look like it has been updated since the OS was, sideloading the same version would put me in the same boat I'm in now. If I drop 5.3.1 on there, that should fix me, assuming the age of the store is the underlying issue. Unless there's something I'm missing.
Ok, my venezia is attached.
scooter1979 said:
No go. Got a "Application Not Installed" error.
The thing there is, if the issue is indeed related to the age of the appstore, which doesn't look like it has been updated since the OS was, sideloading the same version would put me in the same boat I'm in now. If I drop 5.3.1 on there, that should fix me, assuming the age of the store is the underlying issue. Unless there's something I'm missing.
Click to expand...
Click to collapse
A while back, I found a tutorial on how to upgrade system, but keep bootloader the same. Let me look...
Also, if it isn't the age of the app store, it has no effect. You could also try Amazon Underground app. It has a different package name, so it will install alongside the Appstore you have. This way, you can see if it has to do with the store or if it's just not working.
EDIT: Having trouble finding the link. I think what it was is you can download an update file, rename it from *.bin to *.zip, extract system.img, put it on the device, flash it, root, and disable ota immediately. I'll keep looking.
Sent from my Amazon Fire using XDA Labs
Umm, you guys?...
Ya wanna hear something wacky? Just for the fart of it, I ran the apk I just uploaded on my own device, and, um, the store works now. Zero problems. Connects just fine.
Now don't I feel like a horse's patoot?
Well, if nothing else, I learned what DNS to block if I upgrade to 5.3.1, how to check my bootloader via hex editor, and to rely on the kindness of strangers to fall bassackwards into an easy solution. Yeesh.
scooter1979 said:
Ya wanna hear something wacky? Just for the fart of it, I ran the apk I just uploaded on my own device, and, um, the store works now. Zero problems. Connects just fine.
Now don't I feel like a horse's patoot?
Well, if nothing else, I learned what DNS to block if I upgrade to 5.3.1, how to check my bootloader via hex editor, and to rely on the kindness of strangers to fall bassackwards into an easy solution. Yeesh.
Click to expand...
Click to collapse
Oh. Well, I found the thread, if you want. It gives instructions for FlashFire as well.
https://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Sent from my Amazon Fire using XDA Labs
---------- Post added at 07:37 AM ---------- Previous post was at 07:32 AM ----------
scooter1979 said:
Ok, my venezia is attached.
Click to expand...
Click to collapse
Was there a .odex in the folder, and/or a lib folder? If so, could you also upload that? If not, then it appears it will not work. Shame. Thanks for the apk.
Sent from my Amazon Fire using XDA Labs

Running rooted 5.1.1, how to upgrade to 5.3.2 for Alexa (5th gen Fire tablet)

Hi! I have a 5th gen Fire tablet running 5.1.1, rooted with the Supertool, lock screen ads turned off.
I'd like to get Alexa. I understand that Alexa is available in firmware 5.3.2.
I see here that 5.3.2 can't be rooted but can be downgraded to 5.3.1, which can be rooted. So I think 5.3.2 is the version that I want, rather than 5.3.2.1, to preserve the option to root in the future.
What is the process to upgrade my tablet to 5.3.2? Based on experience with other devices, I would expect that I'd need to do some combination of unrooting, factory reset, clear data and cache, etc.
But I'm reading the instructions for restoring stock firmware here, it looks like all I need to do is an adb sideload in stock recovery. Is it really that simple? No need to do anything else?
I'm assuming the result of that will be a fresh install of 5.3.2 with Alexa, and then I'll want to use the Supertool to install the Play Store.
Can anyone just provide a quick confirmation that I have this right? Thanks for any help!
5.3.2 isnt rootable, OTA updates will probably be an issue unless you can block auto updates.
discman017 said:
Hi! I have a 5th gen Fire tablet running 5.1.1, rooted with the Supertool, lock screen ads turned off.
I'd like to get Alexa. I understand that Alexa is available in firmware 5.3.2.
:
I'm assuming the result of that will be a fresh install of 5.3.2 with Alexa, and then I'll want to use the Supertool to install the Play Store.
Can anyone just provide a quick confirmation that I have this right? Thanks for any help!
Click to expand...
Click to collapse
krsmit0 said:
5.3.2 isnt rootable, OTA updates will probably be an issue unless you can block auto updates.
Click to expand...
Click to collapse
Yep. You'll probably want to hold off if retaining root option (and ability to flash a custom ROM) is more important than Alexia. Might also consider grabbing a refurb Fire 7 from Amazon (<$30 USD) and running Alexia on that pup. Best of both worlds...albeit with additional cost and hassle of dealing with 2 devices.
Thanks for the heads up about OTA updates. I figured I could just ignore OTA updates and stay on 5.3.2. But is that not the case? Will Amazon automatically update 5.3.2 to 5.3.2.1 without my approval?
Sorry for the very basic questions. I've been happily running 5.1.1 (rooted, OTA updates disabled by Supertool), so I hadn't considered the problem of a forced update.
Or is there another way to get Alexa (custom ROM, for instance)?
Thanks again!
discman017 said:
Will Amazon automatically update 5.3.2 to 5.3.2.1 without my approval?
Click to expand...
Click to collapse
Yes, it will automatically update as soon as it can. And unfortunately, updates can't be disabled without root, so 5.3.1 is the newest you can safely obtain without locking into the terrible 5.3.2.1 situation we're in now.

Block already downloaded OTA update on Fire 7" 5th gen

Hello dear XDA members out there. I just found my Fire tablet again, after months (in a backpack I don't use anymore). It is currently running FireOS 5.4.0.0, it already downloaded the update to, Probably, 5.6. Is there any way to stop the update in this state? Because AFAIK, they changed bootloader stuff 5.4.0.1, which I don't want on my device, just in case this fxckers built in another bottle to lock people out by preventing downgrades. A firewall won't help anymore if course. So what else could be an option?
Blackhawk2306 said:
Hello dear XDA members out there. I just found my Fire tablet again, after months (in a backpack I don't use anymore). It is currently running FireOS 5.4.0.0, it already downloaded the update to, Probably, 5.6. Is there any way to stop the update in this state? Because AFAIK, they changed bootloader stuff 5.4.0.1, which I don't want on my device, just in case this fxckers built in another bottle to lock people out by preventing downgrades. A firewall won't help anymore if course. So what else could be an option?
Click to expand...
Click to collapse
FireOS 5.6 can be safely downgraded to 5.4.
How da you know? Did someone already test it?
For now, I installed Netguard, since no root firewall kept blocking EVERYTHING, even allowed apps, blocked forced update, DeviceSoftwareOTA(or whatever I us called), and system update, force stopped them, and cleared app data, working
Blackhawk2306 said:
How da you know? Did someone already test it?
For now, I installed Netguard, since no root firewall kept blocking EVERYTHING, even allowed apps, blocked forced update, DeviceSoftwareOTA(or whatever I us called), and system update, force stopped them, and cleared app data, working
Click to expand...
Click to collapse
Interesting challenge; I'll leave the research to you.
As for blocking I use AdGuard pro which got the job done on every Amazon device I have used (3rd-7th gen) with FireOS present.

hey. i messed up an update to my fire and now i'm stuck...

hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
havikx said:
hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
Click to expand...
Click to collapse
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Davey126 said:
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Click to expand...
Click to collapse
now that you mention, thats probably exactly what i forgot to do. Also, i'm on 5.1.1. My bad. As far as i know, 5.1.1 system still has that locked bootloader preventing android upgrades. Though I havent kept up with development too much. Ill get started on returning to stock and rerooting. Hope this little tablet get a breakthru in the near future!
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
havikx said:
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
Click to expand...
Click to collapse
Agreed. The technique you used doesn't work for everyone; hence my generic 'return-to-stock and redo everything' guidance. Glad you are back in business with minimum fuss.

Categories

Resources