Thread: Glo Urgent Request
View Single Post
Old 01-28-2014, 10:20 PM   #17
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
Ken: Unless, I misunderstand what you are asking, once the device is registered, whether with a real account or a fake one by updating the database, any firmware version can be installed. And then you can manually load a newer version if you want. But, the registration will need to be redone after a factory reset or logging out on the device.

OhGodBears: I understand where you are coming from. Christmas with my father-in-law had some interesting moments because of this.

For your Grandmother, apart from the familiarity of the smiley face (which I miss as well), I think the older home screen is probably better. I think either 2.4.0 or 2.5.2 would be the best firmware. 2.6.1 would be better but I think that is the first with the new home screen.

For the database/registration, the best thing to do depends on the source of the books. If you are buying from Kobo and loading them using the Kobo desktop, you need to login with a real Kobo user. Unfortunately, each time you connect, and run the desktop, it will update the firmware. Just remember to remove the firmware files before ejecting.

If you are sideloading manually or via calibre, then using the fake registration that Ken suggests is probably a good idea. I would also suggest taking a copy of the database after doing this in case you have a similar problem later.
davidfor is offline   Reply With Quote