Thread: Preventing upgrades
View Single Post
Old 05-19-2015, 05:51 AM   #14
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 Ken Maltby View Post
So, " So, I put an earlier firmware on, " doesn't include rebuilding the database? Including the user table?
No. What I was testing was whether I needed to be logged into a real Kobo account to get firmware updates. Just changing the entry in the user table should be enough for that.

But, maybe that isn't enough. So I removed the database, let the device create an empty one and used one of your inserts to add the user row. Again, it checked for a firmware updated when I started the sync.
Last edited by davidfor; 05-19-2015 at 05:53 AM. Reason: Clarifying the original test.
davidfor is offline   Reply With Quote