Kobo Patcher

[GeoffR]

Originally Posted by booklover6

Does mz_koboreaderpatch_11.exe (self-extracting archive) which contains kpg.exe work for any firmware? Like can I use it to build the patch for 3.3.0?

Apparently so, since it worked for me, using the files in post #668. Thanks for those, Geoff!

Yes it is okay to use the older kpg.exe, just don't use the older libnickel.so.1.0.0 or kpg.conf files that are included with it.

[Nick_1964]

It would be great if there would be a simple patch not to autoupgrade the firmware.
I erased the PC software, Calibre is much better and in my country Kobo is the most expensive bookshop there is so I don't use the koboshop. There is a perfect kepub plugin for Calibre, but the firmwareupdate by wifi... man if that could easy to be shut off...

[PeterT]

@Nick: See this post https://www.mobileread.com/forums/sho...8&postcount=44

[Nick_1964]

Originally Posted by PeterT

@Nick: See this post https://www.mobileread.com/forums/sho...8&postcount=44

Thanks friend !

[Nick_1964]

Originally Posted by PeterT

@Nick: See this post https://www.mobileread.com/forums/sho...8&postcount=44

I tried the patch to disable the auto updates and the patching itself worked fine.
But like the picture shows, the software version changes into 99.10.0
All the books work great but when using Calibre, it says:
"kobo database version unsupported" and calibre stopped working (Calibre 1.35.0 )
Tried the alternative strings, they all patched okay, but changes the software version into one Calibre doesn't recognise and refused to transfer books to or from the reader.
So after all, it doesn't seem such a good idea to use this patch.
Need to repatch all over again with the right libnickel.

[PeterT]

Calibre does NOT care about the f/w release level; rather it goes by the database version # from the database itself.

99% of the time there are no changes in the database itself, and configuring the driver in calibre to "attempt to support newer f/w levels" is all that is required.

[Nick_1964]

Originally Posted by PeterT

Calibre does NOT care about the f/w release level; rather it goes by the database version # from the database itself.

99% of the time there are no changes in the database itself, and configuring the driver in calibre to "attempt to support newer f/w levels" is all that is required.

Tried the patch yourself ?
Because then you must have noticed that after some reboots of the reader after the patch, when you attach it to usb again, windows doesn't even recognised the Aura HD anymore, say that a new device is detected, tries to install new drivers for the kobo 99.10 like when you use a new usb stick that never attached to the system,then Calible doesn't recognise the patched reader and say that it has no driver for the "kobo 99.10" and can't recognise the database.. Alternative 2 and 3 does similar things and tried to sync 3 times but that didn't work also anymore.. , tried it several times but Calibre keeps saying that it doesn't know the type of Kobo attached and therefore can't support it, the database can be the same,but Calibre doesn't even bother try to read it.
Tried configuring the driver the way you say.. but nope...
Just thinking as a noob it almost look like the new firmware is injected in the place that the reader uses to identify itself,like it is not changing the firmware version,but the model version,possible during reboot and implementing the changes you made.

[PeterT]

Which option did you use?

Also, I don't have 3.1.1 but will waste time later and see what happens. And FYI I will use either alternative 2 or 3; NOT 1.

[davidfor]

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.

[Nick_1964]

Originally Posted by davidfor

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.