Quote:
Originally Posted by jackrandom
I already read this earlier and have to disagree. 
Kindle firmwares in Germany are exactly the same, downloaded from exactly the same servers.
i.e. look at the official (german) firmware download page for voyage:
https://www.amazon.de/gp/help/customer/display.html?nodeId=201630670
download URL there is https://s3.amazonaws.com/firmwaredownloads/update_$foobar.bin
I also checked with wireshark and I'm using a firewall to block these specific paths (not blocking whole amazon universe) for months, successfully.
So, this is wrong information. Firmware is not specially modified in Germany.
To make an educated guess: I think people are doing things wrong, not RTFM, have no idea what they are doing actually, and end up trying to explain weird behavior through wack theories.
My Kindle was on 5.8.7.0.1 (bought in April '17, Germany) and I successfully JB - I mentioned earlier in this thread - and I'm now on 5.8.9 and never got a single problem, neither with KUAL or anything else, using it everyday. |
They have in the past.
It is included in the posts here, where the Germany firmware build was approximately 30Mbyte (IIRC) larger than the USA build.
And the device we where working on at the time did not work as expected until (the user) installed the German build.
There have been several firmware builds released since then.
IIRC, that was before Amazon changed the download URL structure.
You can spot at where in the release series they re-organized the download servers, just highlight the links listed in step #7 with a browser that will display the target URL (Firefox does).
Amazon does not provide any assurance that they will not change something that has 'always been that way' at any time, without notice.
But you can read in the directions that nothing was added about regional variations.
It just seemed to me not something that could be depended upon in firmware that was otherwise install time localized.
Edit: Well my memory was wrong, I did add a comment on regional variations.
But I have just edited it to include (hopefully) a better description of what has been reported.
Ref: Step #7, second bullet.
- - - -
The other thing subject to recent discussion - the subject of registration . . . .
That was added as a result of my own experience, confirmed by others, that you can not reach UYK menu until the device is registered.
But that was only on one device/firmware combination (both mine and the people confirming), so it remains a recommendation not a requirement.
- - - -
I realize that it is probably hard to imagine that a post as long as the first one in this thread has been minimized.
But I can assure you it has been, only the show-stopper exceptions to the general rule(s) has been included.