Thread: Kobo Patcher
View Single Post
Old 05-04-2014, 07:06 AM   #700
Nick_1964
Bookworm
Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.
 
Nick_1964's Avatar
 
Posts: 975
Karma: 768585
Join Date: Aug 2010
Location: Netherlands
Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo
Quote:
Originally Posted by davidfor View Post
The calibre driver checks two things: the dbversion number and the firmware version number. If either number is to high, the driver will display the error. Setting the option to "Attempt to support newer firmware" will work as long as you are patching reasonably recent firmware.

The problem is changes in function with the versions. If something has change since the firmware version you have patched, then things might break. The two things I can think of immediately are cover images and series info. The cover image handling changed with 2.9.0, so patching an earlier firmware to a later version number will break that. It won't stop things from working, it will just mean the cover images won't be removed or will be sent to the wrong place. The series info is more serious as that affects the SQL run at various places. They would fail and prevent the driver working properly. That change was somewhere about 2.3.1, so hopefully no one is trying to patch that.

As PeterT suggests, patching the firmware check URL instead of the version number is probably safer.
Gonna try it again now.. as I used option one (it is set as default) my system didn't worked anymore, as soon as I plugin the device, windows remembered it somehow and again say that the device is not supported.
So option 2 and 3 don't work either anymore as my computer doesn't recognised the reader anymore, so option one of the patch also changes something the device presents itselfs to the computer.
So entered device management of windows 7 ( don't know the exact word,as in my language it is called apparaatbeheer ) and searched for a unknown device with red cross and removed it,there was a second screen telling me that one of the connected usb devices had stopped working and caused an error, placed the reader on a android device with host-guest mode usb cable ( there is another name for it ) and placed the right KoboRoot.tgz back ( I always save them in stead of patching and repatching )
Now the reader is recognised again as the Kobo, and Calibre works okay again ( kobo running on 3.1.1 ) so I am ready to use option 2 again.
Nick_1964 is offline   Reply With Quote