Thread: Aura HD Corrupt database?
View Single Post
Old 01-05-2014, 08:04 PM   #9
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
Quote:
Originally Posted by hoichi View Post
Skipping to 3.1.1 seems to be inevitable now, for the startup wizard updates the reader to the latest firmware before letting you do anything else (like turning off sync, for instance).
Any particular reason you should think the problem is introduced by 3.0.1?
I think Ken is referring to some issues that seem to be happening after upgrades. Some of them are probably because the 3.0.x firmware was intended only for the Touch and the 3.1.x firmware for the Glo, Aura and Aura HD. Some Touch users who have installed 3.1.1 are seeing problems. But, I can't think of anything specific for the Glo etc uses who installed 3.0.1 and then upgraded to 3.1.x. One thing is that if the upgrade path caused a problem, then doing the factory reset and letting the device update itself to 3.1.1 would have avoided this. This is less likely to result in problems than stepping through the upgrades.
davidfor is offline   Reply With Quote