MobileRead Forums - View Single Post

cantaro · 01-20-2016, 04:13 PM

Yesterday I found that, after a very long time, Kobo has once again released new firmware for my ancient Kobo Touch (the original N905). So I upgraded, and—shockingly—the fake registration I had been using for years no longer worked, the device threw a 'Critical error' message.

All the usual tips for bypassing the registration no longer seem to work with the newest firmware (3.19.5761). But today I found a website in German (http://allesebook.de/anleitung/anlei...erwenden-67990) with instructions that do work!

To sum it up, after connecting the Kobo to my Linux system, I ran the following command to update the SQLite database:

Code:

sqlite3 /media/cu/KOBOeReader/.kobo/KoboReader.sqlite "INSERT INTO user(UserID,UserKey) VALUES('1','');"

After unmounting and disconnecting, the Kobo was fully usable.

If you have a working reader with progress saved and all, and want to avoid logging off the reader, surely the above instruction has to be modified to change the existing database row instead of adding a new one. I leave that as an exercise to someone else.

01-20-2016, 04:13 PM	#1
cantaro Junior Member Posts: 4 Karma: 10 Join Date: Feb 2012 Device: Kobo Touch	Bypass registration with latest firmware Yesterday I found that, after a very long time, Kobo has once again released new firmware for my ancient Kobo Touch (the original N905). So I upgraded, and—shockingly—the fake registration I had been using for years no longer worked, the device threw a 'Critical error' message. All the usual tips for bypassing the registration no longer seem to work with the newest firmware (3.19.5761). But today I found a website in German (http://allesebook.de/anleitung/anlei...erwenden-67990) with instructions that do work! To sum it up, after connecting the Kobo to my Linux system, I ran the following command to update the SQLite database: Code: sqlite3 /media/cu/KOBOeReader/.kobo/KoboReader.sqlite "INSERT INTO user(UserID,UserKey) VALUES('1','');" After unmounting and disconnecting, the Kobo was fully usable. If you have a working reader with progress saved and all, and want to avoid logging off the reader, surely the above instruction has to be modified to change the existing database row instead of adding a new one. I leave that as an exercise to someone else.