Quote:
Originally Posted by elimisatailor
But what finally worked for me: creating a network issue to encourage the kindle to use the cached version of the store (the winterbreak page). For me, this was setting my pi-hole (custom home DNS) to block all .*amazon.* DNS requests, but I realize most people won't have this setup available. Here's a potential list of things to try, from easiest to hardest. If anyone gets these to work, please reply so other users can know the quickest path:
- Unplugging the internet connection from your wireless router (so the router is still running and producing a wifi network, but it can't actually talk to the internet)
- Moving the kindle to the very edge of the wifi range, to make the network flaky
- Saturating the network by running speed tests (or some other heavy download) on as many devices as possible when you open the kindle store and turn off airplane mode
- Connecting to a phone hotspot in a location with bad phone service
- Setting your router's DNS server to an invalid address, like 0.0.0.0, which would hopefully break all DNS (obviously set this back afterwards)
- Setting up pi-hole on your computer, setting your router's DNS server to your pi-hole/computer, then blocking .*amazon.* like I did (this is an advanced setup, and if this doesn't make sense to you, please don't attempt it)
|
I created an account just to say thank you!
I got stuck at the Kindle store too. It always loaded the store instead of the JB HTML file. If I haven't found your post, I never would have thought this was because our internet is too fast!
Blocked
||amazon.com^ with AdguardHome and it worked.
I'm going to install the hotfix now.
FYI, my model is Oasis 10th gen, firmware 5.14