Quote:
Originally Posted by Lee3
NotebookSyncToken had changed, I would say it wasnt NULL anymore after you synced.
Quote:
Originally Posted by Quoth
I think that doesn't make it work, no matter what value it is.
|
|
Sorry but your wrong to assume this, Especially in OTA/API type systems, as Tokens are required for authentication/Identification.
There is a strong possibility here that a token implies royal licence fee accounted for.
a NULL means no contact with server as of yet.
Quote:
|
Originally Posted by Quoth
What I'm saying is I've 20+ years SQL experience, a gazzillion years experience UNIX, Linux and embedded systems, built gadgets. Literally have the greybeard. AND I had a working one beside a new one that could register Kobo, could download dictionaries but couldn't download the Notebook resources because the server was off-line.
My opinion is the four zip files and whatever database settings might be needed isn't enough. Unless Kobo changes the FW I can't see how a manual setup can work.
|
Well that maybe the case, but your giving up rather easy.
For example, one cannot say "we dont know whats going on, but loads of stuff in the firmware is being changed"
Using this approach, we can also say "we dont know whats going on, but 1 simple flag needs to be set to give access"
Quote:
|
Originally Posted by Quoth
I had in the end to copy EVERYTHING, and it took WiFi being on and 2 extra reboots to get it working.
|
This is only good news, because you copied tokens, serial data, configs, etc from another device, and it worked on a device with different hardware serials, which shows that there validation checks are not so secure.