b) I bought my Touch in the Netherlands, but before it was officially released in the Netherlands. I think my supplier might have got it from Germany, but I'm not sure.

c) I've always done all my regular/official updates via Wifi. I've never done any via Desktop, except for the very first (which was 1.9.14). I updated to the unofficial/Japanese 2.0.2 manually (copying the unzipped files to .kobo), and after that to 2.1.1 the same way

d) I have had no troubles at all with any of the updates, except from 2.0.2 to 2.1.1 where the first try my Kobo started up with 2.0.0 for some reason. Putting 2.1.1 on top of that went fine. Yes, 2.0.0 gave me horribly slow page turns and wrong book covers and all the rest of the reported issues, which is why I escaped to 2.0.2 (which didn't help much) and then to 2.1.1 (which is almost perfect).

e) Yep I'm lucky

P.S. And I use a Mac... maybe that's relevant?

I've just had to do a million resets and one of them got me to my original firmware: it's 1.9.11 r32877, 9/23/11.

(Unfortunately it wasn't fully functional so now I'm stuck in the resetting game again, but at least we now know my device started with 1.9.11!)

[QUOTE=Peakcrew;2213955]On the "Kobo Touch future firmware feature request thread", a few of us have been wondering if there is a connection between device IDs and the well-known problems some have had updating since firmware update 2.0.0 came out. Obviously, to find this out we need some information from you good folks, in the form of:

a) your device ID and version number,

PID: 4136 Rev: 0326

b) an indication of the country you bought the Touch and where you did the update(s),

Purchased in Ireland (Apr 2012) ...all updates in Ireland

c) whether you did it via Kobo Desktop, wifi, or by downloading and installing yourself, and

First update via Kobo Desktop, all subsequent updates via WiFi

d) whether you have had any difficulties or changes in device behaviour not announced by Kobo as part of the updates since 2.0.0., and, if you did, what they were/are. These include, but are not limited to, failed updates, slow page turns, displaying the wrong book cover ... the list is quite long!

I have been lucky - no problems at all and successfully updated to 2.1.4 (r43710 10/1/12) last week via WiFi, only 1 update required and device going like a rocket since then

e) In addition, if you know the firmware version it came with from the factory that would be useful.

Apologies, I have not got the faintest idea what the firmware it came with was....guessing 1.9.7

f) However, reports of no problems are as useful, so if you have been lucky, please let us know, too!

Lucky,lucky, lucky happy dance (comiserations to everyone who was not so fortunate)

The problems with the Australia devices seems to be firmware related. So, the same FCC device will have or not have the update problems depending on the firmware that was loaded onto it at the factory.