Thread: Kobo Glo HD
View Single Post
Old 05-26-2015, 09:17 PM   #1174
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 Nick_1964 View Post
Hmm.. transfer the device.xml file from another device will not work before setup I guess, read early that it can be transferred from one to another... that is a thing I can try when I have it.
But, a good point..
My "problem" is that when it arrives here, somewhere in june, I can have it for 14 days, then I have to send it back.
If there is no new firmware before that date or the new firmware doesn't fix the problems people called earlyer, I am stuck with it..
But then on the other hand, if it does upgrade to 3.15 after installation, the 3.14 firmware can be installed over 3.15 and then the setup doesn't have to be performed again, so just let wifi off must prevent it from again upgrading to 3.15... or do I again miss something ??
If you are a Windows or Mac user, you can easily prevent the initial upgrade of firmware. You use the Kobo desktop app to do the setup and remove the firmware upgrade files before disconnecting the device. I did do this after a factory reset to see the differences. I can't remember if it was closer to 3.13.0 or 3.15.0. But, I didn't see the performance problems that others are reporting with 3.15.0, so I wouldn't choose to go back.
davidfor is offline   Reply With Quote