Kobo standalone? (never want to connect to Kobo, or activate)

[pluma]

Originally Posted by kido.resuri

The above is just the creation of the table. You need to INSERT or UPDATE.

Why would you keep the email address while the others are empty?

Anyhow, you would need an sqlite query something like this:

INSERT INTO "user" VALUES('','','','put.your@email.here','','','','', '','','','','','','','');

Yes do know is the original fields, the thing is that I did the inserting by trial and error so I pasted the original table for help. I am not a sqlite haxxor, I only copy paste :/

Any reason for using 3.20? I can think of a lot of reasons for not using it, but none for choosing it specifically.

That's the recovery firmware version after hard reset. I updated afterwards.

danke for your concerns

[PeterT]

I wonder if it would be more release independent to use the other form of the INSERT statement, ie

INSERT INTO "user" (<list of columns>) VALUES(<list of values>)

This has the benefit of being independent of schema changes.

Sent from my Nexus 7 using Tapatalk

[dragon788]

As the number of columns and their names may change over time as probably noted in this thread, it is a bit of a pain to do the registration "hack" to fill them all out.

While looking to do this from my Linux machine I installed `sqliteman` as its description offered a GUI for administrating and developing for SQLite databases.

EDIT: Use method outlined further down
One of the features I hadn't counted on was being able to right click on the "users" table and choose "populate" from the list and having the tool automatically craft a query to insert data to fill all the columns. I didn't have to modify anything and could just click "Insert" and after ejecting and unplugging (I chose register with desktop to start), it complained about the data format, but bypassed the registration screen and put me at the "Home" screen.

I may play around with it a bit and see if not choosing "autonumber" for the user column avoids the error, but this is probably the easiest way to describe to a non-technical user without creating a data map that might get outdated with every update.

EDIT:

Upon further testing having random data in all the fields was bad, but adding a new row defaults everything to <null> and then only editing the first two fields that have "NOT NULL" constraints, iirc UserName and UserKey, and "committing" the changes (you get prompted to do so if you just attempt to close sqliteman with changes) resolved the error after I unmounted and unplugged and didn't require any further messing around with the database.

[u238110]

This is the 'user' table for the Kobo I just bought (firmware 4.7.10.413). Should anything be left alone to prevent messing up the device? Also, the fourth post in this thread states that one also needs to downgrade to firmware 1.9.16 in order for this hack to work. Is that true?

Originally Posted by rashkae

The new firmware will not accept new books until it's registered.

[_twoflower_]

Has anybody had success doing this with a Libra? Got to the homepage successfully after editing KoboReader.sqlite users, but can't view the My Books page.

[anonymouscoward]

Hi,

On my brand new Kobo Libra 2 (4.31.xx) :
- UserID : 1
- UserKey : My first name
- AnnotationsMigrated : true (or 1)
- Everything else : default (null, true/false, ...)

Without AnnotationsMigrated=true a damn nag screen appears.

[Quoth]

Just turn on WiFi once.
Register with any imaginary or real email. Kobo doesn't send you email (unless you use their bookshop) nor do they pass on the email address.

Tested with five Kobos since 2017.

[anonymouscoward]

Originally Posted by Quoth

Just turn on WiFi once.
Register with any imaginary or real email. Kobo doesn't send you email (unless you use their bookshop) nor do they pass on the email address.

Tested with five Kobos since 2017.

I had to use this SQL workaround because of a really annoying bug : impossible to connect with my Google account. Each time he asked me to log in with my FNAC.com account, a site on which I connect with...... my Google account.
Same when I tried to create a Kobo account.

Anyway, I didn't know about your technique, and finally that's what made me want to tinker this reader.

So :
- The user friendly technique: activate the wifi and create an account with a fake email,
- The technique for tinkerers: modify directly the database of the reader.

[Quoth]

Originally Posted by anonymouscoward

So :
- The user friendly technique: activate the wifi and create an account with a fake email,
- The technique for tinkerers: modify directly the database of the reader.

Or a real one. I used real ones created for the purpose. No spam or emails from Kobo on them ever. The email address only matters if you use the Kobo online bookstore to buy.

[rashkae]

You don't have to include every field.. only 2 of them are needed. This SQL command has worked for a very, very long time.

INSERT INTO user(UserID,UserKey) VALUES('1','');

If using Sqlite:

sqlite3 KoboReader.sqlite "INSERT INTO user(UserID,UserKey) VALUES('1','');"


But the easy way to do this, without connecting to wifi, and without using SQL commands, is to simply copy a blank database into the .kobo directory. I've attached one to this message, unzip and copy to your kobo, then reboot.

[juliuss]

Originally Posted by rashkae

You don't have to include every field.. only 2 of them are needed. This SQL command has worked for a very, very long time.

INSERT INTO user(UserID,UserKey) VALUES('1','');

If using Sqlite:

sqlite3 KoboReader.sqlite "INSERT INTO user(UserID,UserKey) VALUES('1','');"


But the easy way to do this, without connecting to wifi, and without using SQL commands, is to simply copy a blank database into the .kobo directory. I've attached one to this message, unzip and copy to your kobo, then reboot.

That command

INSERT INTO user(UserID,UserKey) VALUES('1','');

doesn't seem to work anymore on the Kobo Clara Colour.

Also notice that the "empty" database you linked is not really empty, it contains the database structure and even some data.

Among the tables is the "DbVersion" table, with a single column "version", and a single rows which equals 125 in your dataset and 175 in my Kobo.

So I'm afraid to break it if I put it in, being a later version.

[rashkae]

Originally Posted by juliuss

doesn't seem to work anymore on the Kobo Clara Colour.

Also notice that the "empty" database you linked is not really empty, it contains the database structure and even some data.

Among the tables is the "DbVersion" table, with a single column "version", and a single rows which equals 125 in your dataset and 175 in my Kobo.

So I'm afraid to break it if I put it in, being a later version.

Thanks,, I'll be sure to re-test.. .but it's completely unecessary now.

Open the .kobo/kobo/Kobo eRader.conf file with a file editor that respects Unix Text file format, (Notepad++ recommended for Windows. Note this is something you can download, and is *not* the same the Notepad that comes with Windows.)

In the [ApplicationPreferences] section, add the line:
SideloadedMode=true

Save, eject Kobo, and reboot Kobo.

FYI, "Empty" database in this case meant a database that Kobo re-creates if it's deleted, with the blank user added. I meant only empty the sense that there was no account info and no books metadata.

[JSWolf]

The database hack to get full functionality without registering is a really bad idea to try. Two or three times Kobo has brought out a firmware update that totally broke that hack. So you lost everything. Even a backup database would not work. So don't do it. Don't ever do it unless you like starting over.

[John F]

Originally Posted by JSWolf

The database hack to get full functionality without registering is a really bad idea to try. Two or three times Kobo has brought out a firmware update that totally broke that hack. So you lost everything. Even a backup database would not work. So don't do it. Don't ever do it unless you like starting over.

When was the last time it happened?

[DNSB]

Originally Posted by John F

When was the last time it happened?

Not certain, my notes say was noted in rev 3.19 firmware by multiple users but a added note mentions a similar issue with 4.4 software though no confirmation on that.

So you are willing to setup your Kobo with a manually added fake user knowing that a new firmware revision may cause a factory reset? When current firmware makes it so easy to use SideloadedMode, it seems to be a silly choice.