Kobo Start Menu

[Ken Maltby]

On my Windows 7 PC, I get the following whenever I connect with USB support enabled:

"USB Device Not Recognized" "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it."

Then if you double click on the bold UNKNOWN DEVICE I see:

"Windows has stopped this device because it has reported problems. (Code 43)"

THIS is Windows not seeing the device. It is a Windows driver problem.

(As it happens I have a hatch on the back of my AuraHD and can remove the internal uSD card, so I can live without the USB connection. )

If you are not seeing some of this, if there is no response from the PC at all, then the USB support was not enabled. If you are still using XP, there are other possibilities.

Luck;
Ken

[exachillus]

Originally Posted by tshering

That means that the module is successfully loaded. Therefore, the problem is possibly on the pc. You can try open the device manager on the pc and look at the information about USB-Controller. If the device is plugged in and you select usb enable.sh or usb disable.sh on the Kobo, there should something change in the list of usb-controllers. Have a look there, maybe you can find some hint what is happening.
I just presupposed that you are a windows user. On linux it should be similar, I guess.

tshering

I can connect in nickel but not in startmenu, however I will investigate it further to see what is happening underneath.

[fanoI]

Originally Posted by Ken Maltby

On my Windows 7 PC, I get the following whenever I connect with USB support enabled:

"USB Device Not Recognized" "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it."

Then if you double click on the bold UNKNOWN DEVICE I see:

"Windows has stopped this device because it has reported problems. (Code 43)"

THIS is Windows not seeing the device. It is a Windows driver problem.

But you had always this problem or only after installing "Kobo Start Menu"?
If it is after installing it, probably is doing something wrong

Originally Posted by Ken Maltby

(As it happens I have a hatch on the back of my AuraHD and can remove the internal uSD card, so I can live without the USB connection. )

Inpraticable solution in my case, the device has suffered already to much

Originally Posted by Ken Maltby

If you are not seeing some of this, if there is no response from the PC at all, then the USB support was not enabled. If you are still using XP, there are other possibilities.

Luck;
Ken

Indeed for Windows nothing happened! USB support was disabled in Nickel too, apparently...

By the way the network problems continues the device cannot download the new firmware; it continues to get timeout errors (49 Minutes - 22% it said this morning ), I've tried the windows application but after 4 hours it did nothing!
Frack I did this restore factory 6 times yesterday and always worked and now...

[tshering]

Originally Posted by Ken Maltby

On my Windows 7 PC, I get the following whenever I connect with USB support enabled:

"USB Device Not Recognized" "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it."

Then if you double click on the bold UNKNOWN DEVICE I see:

"Windows has stopped this device because it has reported problems. (Code 43)"

THIS is Windows not seeing the device. It is a Windows driver problem.

(As it happens I have a hatch on the back of my AuraHD and can remove the internal uSD card, so I can live without the USB connection. )

If you are not seeing some of this, if there is no response from the PC at all, then the USB support was not enabled. If you are still using XP, there are other possibilities.

Luck;
Ken

Now things start getting interesting. Ken, I thougth you own two Aura HD, one that is able to connect via USB, and one that is unable to do so, independent of which application you are running (cf. this thread). Since only one of your Aura HDs was concerned, I thought this might be indicative of a hardware failure (cf. this).
Since exachillus and fanoI report USB problems on Aura HD too, I wonder what is going on. Could you confirm that one of your two Aura HD can connect to the pc? Or can any Aura HD owner confirm that the USB connection is working when enabling it from the Kobo Start Menu, or that it is not working as the case might be?

[tshering]

Originally Posted by fanoI

Inpraticable solution in my case, the device has suffered already to much



Indeed for Windows nothing happened! USB support was disabled in Nickel too, apparently...

By the way the network problems continues the device cannot download the new firmware; it continues to get timeout errors (49 Minutes - 22% it said this morning ), I've tried the windows application but after 4 hours it did nothing!
Frack I did this restore factory 6 times yesterday and always worked and now...

If you get the start menu running (but this is of course difficult if you cannot connect), there is a possibility to copy the FW update file from an external sd to the internal one, cf. this post https://www.mobileread.com/forums/sho...37&postcount=6
Since you have problems connecting to PC and wifi, you might copy a modified KoboReader.sqlite to the internal sd in order to circumvent registration.

As for changing the settings in runsettings.txt (to make the start menu run after each reboot) without opening the file with an editor, select "scripts>activate>set runmenu settings.msh".

[Ken Maltby]

Originally Posted by tshering

Now things start getting interesting. Ken, I thougth you own two Aura HD, one that is able to connect via USB, and one that is unable to do so, independent of which application you are running (cf. this thread). Since only one of your Aura HDs was concerned, I thought this might be indicative of a hardware failure (cf. this).
Since exachillus and fanoI report USB problems on Aura HD too, I wonder what is going on. Could you confirm that one of your two Aura HD can connect to the pc? Or can any Aura HD owner confirm that the USB connection is working when enabling it from the Kobo Start Menu, or that it is not working as the case might be?

Right, my backup AuraHD. I'll charge it up and see what I get, but last time I did it worked fine. (It's been a few months and the backup is still showing 85%, it shouldn't take long to top it off.) I'll start with it as it is with FW 3.1.1 and mostly stock software [both alternative readers are installed]. Then I'll make additions/updates until it matches the configuration of the one that Windows won't connect to. If the condition appears after a particular update/addition we may have a likely candidate.

OK, it's over 90% so I'll connect the USB cable to my PC while on the Nickel home page and see what I get. Computer detected message. Connect working, with Windows7 showing it as "eReader-3.1.1" with KOBOeReader (K in windows explorer. So, working as expected.

(I have a clone image of the internal uSD card for the device as it is, so I can return it to this state, no matter what.) Hmm... perhaps I should try that image on the malfunctioning AuraHD? I'd better try that first. OK, I tried that and I am getting the same error messages when connecting with Nickel.

So, not likely a matter of the firmware or software, not much point to continuing with this.

Luck;
Ken

[tshering]

Thank you for helping!

Originally Posted by Ken Maltby

(I have a clone image of the internal uSD card for the device as it is, so I can return it to this state, no matter what.)

I hope this will not be necessary. Opening the Aura HD seems to be a little bit risky. Or is there a hatch on the back up device too?

Originally Posted by Ken Maltby

Hmm... perhaps I should try that image on the malfunctioning AuraHD? I'd better try that first.

Do you think replacing the image is much different from factory resetting? I guess you did factory reset the device already several times and the USB connection did not start working.

[Ken Maltby]

Originally Posted by tshering

Thank you for helping!
I hope this will not be necessary. Opening the Aura HD seems to be a little bit risky. Or is there a hatch on the back up device too?

Do you think replacing the image is much different from factory resetting? I guess you did factory reset the device already several times and the USB connection did not start working.

No hatch on the backup, would rather not have to, as well. The only real risk is that the clips holding the bezel onto the rest of the case can break so that the touchscreen becomes a little flaky, you sometimes need to squeeze the bezel to the case, to get a response on certain parts of the screen. Usually only an issue after many openings and closings.

I even tried it with the original factory uSD card, and still get the error messages, with that AuraHD.

Luck;
Ken

[Cyphox]

THANKS for the tipps regarding showing an image when the device is powered off via startenu. i like!

[tshering]

Originally Posted by Ken Maltby

So, not likely a matter of the firmware or software, not much point to continuing with this.

Right, your case seems to be quite different from exachillus'.

[tshering]

Originally Posted by Cyphox

THANKS for the tipps regarding showing an image when the device is powered off via startenu. i like!

I would like to mention that you can show this image also when powering off from nickel. Select "scripts" > "activate" > "x install power off.sh". This will be redone by the next FW update. Then one has to repeat "scripts" > "activate" > "x install power off.sh".

Edit: Don't do it! I just activated it myself after a long time. Several FW updates have happened since I tried it the last time. The image shows now 90 degrees turned. I will fix it in the next version.

[tshering]

Originally Posted by exachillus

tshering

I can connect in nickel but not in startmenu, however I will investigate it further to see what is happening underneath.

The start menu and nickel use the same module to connect to the pc. Therefore, it should work with the start menu too. One difference is that the start menu sends different identification data. Could be that windows is blocking the usb connection when receiving the start menu identification data for some reason. If you like you can try the following. Open .kobo\kbmenu\usb\enable_usb.sh and replace

VERSION=0.0.0

with

VERSION=0.0.1

If you are lucky, windows will establish a new usb connection.

You have to use a unix-style editor, cf. this page.

[Ken Maltby]

Notepad++ is a great free editor that does a great job with the formatting of programming/scripting languages. Those note files that appear as one continuious stream of characters in Windows Notepad, are much easier to read in Notepad++. It handles the end of line properly.

Luck;
Ken

[WS64]

Got my Kobo Aura now, everything is working (Start Menu/Koreader), all books are on a .hidden folder on the SD card.
My question, can it be that Start menu boots so fast that the SD card is not ready until after a few seconds?
I always have to wait a few seconds after rebooting until it is save to start Koreader to access the books on the card.
Same goes for USB enabled, does this unmount the reader from its SD card (but not from the internal memory)?
I can't read any book on my SD card while USB is enabled, the SD card seems not to be there until I disable USB and wait a few seconds.

On my Mini I could not test this since it does not have any external SD card.

[tshering]

Originally Posted by WS64

Got my Kobo Aura now, everything is working (Start Menu/Koreader),

Congratulations!

Originally Posted by WS64

all books are on a .hidden folder on the SD card.
My question, can it be that Start menu boots so fast that the SD card is not ready until after a few seconds?
I always have to wait a few seconds after rebooting until it is save to start Koreader to access the books on the card.

I also have the impression that it takes the system quite a time to recognize the external SD card.

Originally Posted by WS64

Same goes for USB enabled, does this unmount the reader from its SD card (but not from the internal memory)?
I can't read any book on my SD card while USB is enabled, the SD card seems not to be there until I disable USB and wait a few seconds.

You are right, the start menu unmounts the external SD when it enables USB storage. This is to prevent data corruption, which could occur if the pc and the reader try to access the same file.
As you say,the start menu does not unmount the user partiton. The reason for this is to keep the start menu accessible. Therefore, there is a risk of data corruption, and the user is responsible for taking care that the pc does not access files that might be used by any application on the reader. To eliminate this risk by unmounting the user partition, I would have to move the whole start menu folder to the system partition. But then it would be more difficult for the user to access it.