Thread: Touch Firmware 2.0.4
View Single Post
Old 10-06-2012, 02:22 AM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
I have posted this elsewhere, but this is a good place for it to reside.

Some of the Touch's from last year have a factory firmware that does not allow updating past 2.0.0. Kobo have investigated why and are releasing an intermediate firmware to solve this. This is 2.0.4. So, to get past firmware 2.0.0, 2.0.4 needs to be installed. Once this is done, 2.1.4 can be installed safely.

Most of these Touch's seem to have been sold in Australia late last year.

As of 05/10/2012, Kobo have released 2.0.4 to these devices. I don't know if they are doing this by information about the device, or an IP address restriction. I suspect it is the latter as there has been a report of 2.0.4 going to an Australian that had a more recent device.

From what I can find out, they will be rolling out 2.1.4 on Tuesday. That will be Tuesday in Canada, so Tuesday evening in Australia.

If you can't wait, the manual upgrade from 2.0.4 to 2.1.4 is safe, but not supported by Kobo. But, if you suspect you have one of the "problem" devices and don't have 2.0.4, don't try it. It will not work and you will probably need to do a factory reset to recover.
davidfor is offline   Reply With Quote