Calibre not seeing Kobo in Windows 10 Preview builds - Page 9

DAAVIID · 08-09-2016, 11:04 AM

It does not work on a PC with w10 Home AU installed and Kobo Touch N905.

Quote:

Originally Posted by frostschutz

I've created a mod that performs the changes I described above on the Kobo. If successful it should make Kobo <-> Win10 compatible without formatting/losing any files.

Take it with a grain of salt since I've only tested with my H2O, and only with a Win10 virtual machine, not a real Win10 PC.

Just because it works for me doesn't mean it will work for you. Use at your own risk.

Backup your files first.

To install, copy KoboRoot-fatpatch.tgz » .kobo/KoboRoot.tgz

[yes you have to do that on a PC that still sees the KOBOeReader drive, or with a Linux LiveCD - someone else will have to find/write a Windows program that does this directly in Win10]

After installing the mod, the reader will reboot, display a fat clown, and reboot again. At that point the mod performed the changes and removed itself (you have to reinstall the mod to re-try), and things should just work.

If you use this, please report back whether it worked or not.

frostschutz · 08-09-2016, 11:13 AM

Quote:

Originally Posted by DAAVIID

It does not work on a PC with w10 Home AU installed and Kobo Touch N905.

Hi, thanks for your feedback.

Can you confirm some thing for me: the mod installed fine? the kobo rebooted? it did display a fat clown (the one in the attachment)? it rebooted afterwards? not factory resetting in between? And Win10 still wants to format it?

If so there goes that theory

Any others?

SailorPhil · 08-09-2016, 11:30 AM

frostschutz,
Your fix WORKED for me!
I carried it out on a PC with Windows 10, not yet updated to Anniversary. That PC mounted my Kobo Aura h2o as a USB drive. I copied your TGZ to the .kobo folder, then disconnected from the PC. It rebooted, showed the fat clown, then rebooted to the normal book tiles screen.
I plugged it into my PC, Windows 10, with Anniversary update. Kobo was mounted as a USB drive. I started Calibre which recognized it as a device and I sent books to the device successfully.

Well done!

Windows 10 Home
V 1607
OS Build 14393.10
AMD-A8-6410 APU with AMD Radeon R5 Graphics 2.00 GHz

frostschutz · 08-09-2016, 11:35 AM

Hi, thanks for your feedback,

can you also confirm something for me? You said "not yet updated to Anniversary". Did you have other PCs already updated where your Kobo was showing this problem? I'm asking because some people aren't affected so there is a chance it wasn't my mod that fixed it, if you didn't confirm the problem existed before.

JSWolf · 08-09-2016, 11:37 AM

Quote:

Originally Posted by DAAVIID

It does not work on a PC with w10 Home AU installed and Kobo Touch N905.

Are you running firmware version 3.19.5761? It's possible this doesn't work on any other firmware version.

JSWolf · 08-09-2016, 11:38 AM

Quote:

Originally Posted by SailorPhil

frostschutz,
Your fix WORKED for me!
I carried it out on a PC with Windows 10, not yet updated to Anniversary. That PC mounted my Kobo Aura h2o as a USB drive. I copied your TGZ to the .kobo folder, then disconnected from the PC. It rebooted, showed the fat clown, then rebooted to the normal book tiles screen.
I plugged it into my PC, Windows 10, with Anniversary update. Kobo was mounted as a USB drive. I started Calibre which recognized it as a device and I sent books to the device successfully.

Well done!

Windows 10 Home
V 1607
OS Build 14393.10
AMD-A8-6410 APU with AMD Radeon R5 Graphics 2.00 GHz

But what firmware is your H2O running?

SailorPhil · 08-09-2016, 11:46 AM

frostschutz:
Yes, on my PC, which was updated with Anniversary yesterday, the Kobo was assigned a drive letter, then I was prompted to "insert a disk in Drive F". Calibre did not see the device.
After putting your koboroot-fatpatch file, Calibre works with Kobo on the Anniversary-updated pc.

SailorPhil · 08-09-2016, 11:48 AM

jswolf:
Kobo software version: 3.19.5761

frostschutz · 08-09-2016, 11:53 AM

@SailorPhil: Thanks for reporting back! So we have another H2O where this works, and in real Win10, not just a VM like me.

This mod should not be specific to a model or firmware. Of course, I have no way of testing it on all kinds of device/firmware combinations myself.

JSWolf · 08-09-2016, 12:43 PM

Quote:

Originally Posted by frostschutz

@SailorPhil: Thanks for reporting back! So we have another H2O where this works, and in real Win10, not just a VM like me.

This mod should not be specific to a model or firmware. Of course, I have no way of testing it on all kinds of device/firmware combinations myself.

The reason I'm asking about firmware is so we can have information about the firmware on devices that work or don't work.

dura · 08-09-2016, 02:23 PM

Yesterday I connected my Aura to my updated Windows 10 PC, reader not visible in Kobo app nor in Calibre. I did a factory reset, that worked; the reader was seen in Calibre, re-added all my books and I could read again.
But today I reconnected the reader and again, not recognized.
Seems a reset is a one time only solution

So I submitted a ticket with Kobo. I suppose they will get a lot of them, since MS started rolling out the update 2 days ago officially.

mikeywilliams25 · 08-09-2016, 02:41 PM

Works perfectly on my Glo hd on
Kobo software version: 3.19.5761
Windows 10 Anniversary update.

mikeywilliams25 · 08-09-2016, 02:42 PM

The frostschutz patch I forgot to say.

Hypernova · 08-09-2016, 02:49 PM

I'm sad to report that the newly released 14393.51 does not fix this issue.

Now let me go back and read the thread. Seem like we have a workaround!

Marlenio · 08-09-2016, 03:31 PM

Quote:

Originally Posted by frostschutz

I've created a mod that performs the changes I described above on the Kobo. If successful it should make Kobo <-> Win10 compatible without formatting/losing any files.

Hi frostschutz,
i have just installed your patch on my Aura H20 with last firmware (3.19.5761 ) and it works without any problems on Windows 10 PRO AU.

Thank you!

08-09-2016, 11:46 AM	#127
SailorPhil Junior Member Posts: 3 Karma: 10 Join Date: Aug 2016 Device: Kobo Aura h2o	frostschutz: Yes, on my PC, which was updated with Anniversary yesterday, the Kobo was assigned a drive letter, then I was prompted to "insert a disk in Drive F". Calibre did not see the device. After putting your koboroot-fatpatch file, Calibre works with Kobo on the Anniversary-updated pc. Last edited by SailorPhil; 08-09-2016 at 11:49 AM.

08-09-2016, 02:23 PM	#131
dura Groupie Posts: 174 Karma: 1062434 Join Date: Oct 2006 Location: Netherlands Device: Kobo H2O (2th edition), Kindle PW11	I wish I saw this threat before Yesterday I connected my Aura to my updated Windows 10 PC, reader not visible in Kobo app nor in Calibre. I did a factory reset, that worked; the reader was seen in Calibre, re-added all my books and I could read again. But today I reconnected the reader and again, not recognized. Seems a reset is a one time only solution So I submitted a ticket with Kobo. I suppose they will get a lot of them, since MS started rolling out the update 2 days ago officially.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Unofficial 32-bit Legacy Windows Build	DiapDealer	Sigil	104	03-21-2019 12:15 AM
Windows 8 preview now available...	VaporPunk	General Discussions	88	07-08-2012 10:45 PM
Touch Kobo Touch not ejecting cleanly with Calibre OR Kobo Desktop - Windows 7	JBlyth	Kobo Reader	11	08-03-2011 05:38 PM
Kobo Touch not disconnecting properly from Calibre OR Kobo Desktop - Windows 7	JBlyth	Devices	1	08-03-2011 06:50 AM
Idea for Consideration in Future Builds of Calibre	Fi3ryPh03n1x	Library Management	40	04-08-2011 05:12 PM

08-09-2016, 11:30 AM	#123
SailorPhil Junior Member Posts: 3 Karma: 10 Join Date: Aug 2016 Device: Kobo Aura h2o	frostschutz, Your fix WORKED for me! I carried it out on a PC with Windows 10, not yet updated to Anniversary. That PC mounted my Kobo Aura h2o as a USB drive. I copied your TGZ to the .kobo folder, then disconnected from the PC. It rebooted, showed the fat clown, then rebooted to the normal book tiles screen. I plugged it into my PC, Windows 10, with Anniversary update. Kobo was mounted as a USB drive. I started Calibre which recognized it as a device and I sent books to the device successfully. Well done! Windows 10 Home V 1607 OS Build 14393.10 AMD-A8-6410 APU with AMD Radeon R5 Graphics 2.00 GHz

08-09-2016, 11:35 AM	#124
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	Hi, thanks for your feedback, can you also confirm something for me? You said "not yet updated to Anniversary". Did you have other PCs already updated where your Kobo was showing this problem? I'm asking because some people aren't affected so there is a chance it wasn't my mod that fixed it, if you didn't confirm the problem existed before.

08-09-2016, 11:48 AM	#128
SailorPhil Junior Member Posts: 3 Karma: 10 Join Date: Aug 2016 Device: Kobo Aura h2o	jswolf: Kobo software version: 3.19.5761

08-09-2016, 11:53 AM	#129
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	@SailorPhil: Thanks for reporting back! So we have another H2O where this works, and in real Win10, not just a VM like me. This mod should not be specific to a model or firmware. Of course, I have no way of testing it on all kinds of device/firmware combinations myself.

08-09-2016, 02:41 PM	#132
mikeywilliams25 Enthusiast Posts: 48 Karma: 10 Join Date: Aug 2008 Location: London Device: Kobo GloHD and Aura h2O	Works perfectly on my Glo hd on Kobo software version: 3.19.5761 Windows 10 Anniversary update.

08-09-2016, 02:42 PM	#133
mikeywilliams25 Enthusiast Posts: 48 Karma: 10 Join Date: Aug 2008 Location: London Device: Kobo GloHD and Aura h2O	The frostschutz patch I forgot to say.

08-09-2016, 02:49 PM	#134
Hypernova Hyperreader Posts: 130 Karma: 28678 Join Date: Feb 2009 Device: Current: Boox Leaf2 (broken) Past: H2O, Kindle PW1, DXG;Pocketbook 360	I'm sad to report that the newly released 14393.51 does not fix this issue. Now let me go back and read the thread. Seem like we have a workaround!