March 2nd Update

[Lanord]

Thanks i follow your instruction and now everything is working back after the update.

Really good work.

Originally Posted by danifunker

I've created a little bit of a package, and here are some instructions:

1) Download the package ZergRush-forKobo.zip
2) Extract the files from the package
3) Make a new folder in your user profile ( %USERPROFILE% ) and call it .android
4) Copy the file adb_usb.ini to the new .android folder
5) On the Kobo: Turn on USB Debugging under the development options
6) Connect the Kobo to the Windows PC
7) Go into Device Manager, and double-click on the K080 device, it should be listed under unknown. Choose "Update Driver" and pick "Let me choose a driver for this device", point it to the usb_driver package (in my instance I extracted the package to C:\temp, so my full path name was C:\temp\ZergRush-forKobo\usb_driver ). A list of devices will appear, choose ADB Interface
8) Restart the computer
9) Open up the zergrush runme.bat script and let it do it's magic, in my instance it was C:\temp\ZergRush-forKobo\zergrush\runme.bat
10) Install OogleVox
11) Donate!

haha, had to throw in that last one I've spent more time with Kobo and MobileRead forums in the last 24 hours than I have with my partner!

[cyberjm]

Hello there,

A big thank you from France.
I have used the ZergRush-forKobo process, after figuring out how to change the drivers (tips&trick: update drivers->list. I was going straight to path, which was wrong).
Then I used OOgleVox, and went backto normal (I had rooted before the update with Gingerbreak, and installed Market).
Thanks again!

[Odieman]

Sigh...still no dice here..anybody got a shotgun

Originally Posted by Cameronpaterson

Surely that was predictable though Paul? Kobo don't really have an incentive to advertise books not bought from them

I don't know how the numbers work out for Kobo, but I really don't understand why we (as consumers) should jump in glee to be giant billboards.

Don't get me wrong: I think that giving reader the ability to share what they read with friends or discuss what they read with other readers is a great idea. But there is a huge distinction between that and being manipulated into being salesmen.

For what it's worth, I ran tcpdump on the Vox and there is an astounding flurry of network activity when the Kobo app is launched. One of these days I'm going to figure out exactly what the activity is sending. Until then, I'll stick to third party reading apps.

[ZEDenterrpizes]

Thanks so much danifunker. Worked it all out--had some trouble figuring out the the paths, but got it worked out and my Vox is back to how I like it.

[samysdad]

Cool what did you do to fix it up? Mine still thinks the driver isn't usable with win7 64bit

[samysdad]

Originally Posted by cyberjm

Hello there,

A big thank you from France.
I have used the ZergRush-forKobo process, after figuring out how to change the drivers (tips&trick: update drivers->list. I was going straight to path, which was wrong).
Then I used OOgleVox, and went backto normal (I had rooted before the update with Gingerbreak, and installed Market).
Thanks again!

I still can't seem to get the driver working on win7 64bit.

[Jesslynne]

Neither can I samy.. I get all the way up to the run the zergrush and then that never works.

[danifunker]

The adb driver needs to be loaded before you can run the zergrush or superoneclick. It seems that most people are able to load the driver up on their machines, but a few have endless problems. Can I have someone post some screenshots of everything they are doing when trying to load the driver? Also if you can take a screenshot of your about windows screen at the same time and let me know if you are on x86 or x64 hopefully we can sort all of this out.
cheers!

[Jesslynne]

I don't know if I'm setting up the adb right at all.. -totally not as much of a geek-

Originally Posted by samysdad

I still can't seem to get the driver working on win7 64bit.

Have you tried using the drivers from here:
https://dl-ssl.google.com/android/re...04-windows.zip

I had to make the following addition to android_winusb.inf:
%SingleAdbInterface% = USB_Install, USB\VID_2237&PID_2208
%CompositeAdbInterface% = USB_Install, USB\VID_2237&PID_2208&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_2237&PID_0FFF
I did it in the [Google.NTx86] section, but you would probably do it in the [Google.NTamd64] section.

I also had to uninstall the USB composite driver from Windows and let Windows reinstall that driver. But that was in XP SP3/32 bit.

[samysdad]

Kindly review my YouTube video of the common root fail issue.

http://youtu.be/zSeEkVTI60k

[samysdad]

Done please review the video posted.

[danifunker]

Are you turning on the USB storage mode on the kobo? I never had my win7 x64 machine ever show the kobo come up as a disk drive. Also, try removing any kobo installed windows drivers if you have any loaded, and let me know!

[samysdad]

I've tried turning USB storage mode on and tried it with it off... same result either way. I've also erased the installed drivers each time as well but each time I plugin Win7 automatically reinstalls the "disk" driver for Kobo and there are 3 items that appear in Device Manager labelled "Kobo Inc .K080 USB Device".