Kobo Start Menu 08

[tshering]

Originally Posted by kobrick

Alrighty, I broke down and cracked the H20 open and reimaged the SD. Back in business. Thanks for all the help @tshering and @NiLuJe!

I am glad you were successful.

[kobrick]

Originally Posted by tshering

Reimaging seems to be the only remaining possibility. Before doing this, I would read all the relevant posts I can find on this forum to learn about the difficulties in order to minimize the risks.
Would you mind making a copy of your current sd for later inspection? Would be interesting to see what exactly might have happened. Since there is personal information contained, I would not recommend to offer public access to the image however.

Shoot, I just missed your post before I reimaged and didn't make a copy. All I can say is that I installed KSM seemingly without problem. I attempted to install the patch without going into KSM settings to change "runmenu settings.msh" > "always". The patch seemed to install, but in nickel when I tapped on 'collections' the kobo froze up.

[tshering]

Warning:
Updating mark 6 models to FW 4.6.10075 will result in serious difficulties for users of the current KSM version(s). Therefore, prevent the update. Or, better, select the full update (not the partial update) in the KSM menu in order to disable KSM!

[tshering]

I might have been overcautious with my warning in the previous post. The cpu names of the devices of concern are mx6sll and mx6ull. I have no idea which models have such cpu; or whether they are already on the market.

You can find the cpu name of your device by selecting:
scripts > tests > returntests > get platform etc new.sh

Depending on the font size, the information might be difficult to see. It is included in the first two lines of the info text, starting with "cpu:" and "platform:", which might be scrolled out of view. Scrolling might possibly not be easy on devices with high resolution because of the small scroll bar.

[Alanon]

Originally Posted by tshering

I might have been overcautious with my warning in the previous post. The cpu names of the devices of concern are mx6sll and mx6ull. I have no idea which models have such cpu; or whether they are already on the market.

I have a Kobo Aura One and it lists mx6sl (with one l) as the CPU. Your post gives two l's, and now I'm too cautious to sideload the new firmware onto my Kobo.

So does this mean it's better not to sideload the update to avoid issues? Out of curiosity, what are the potential consequences and issues with KSM and this new firmware?

[Question Mark]

Originally Posted by Alanon

I have a Kobo Aura One and it lists mx6sl (with one l) as the CPU. Your post gives two l's, and now I'm too cautious to sideload the new firmware onto my Kobo.

So does this mean it's better not to sideload the update to avoid issues? Out of curiosity, what are the potential consequences and issues with KSM and this new firmware?

The CPU on my KA1 is mx6sl (just one l). After sideloading the 4.6.10075 FW update while in Nickel, I reinstalled the KSM08 tgz file and then the KA1 extension patch. Seems to be working fine in both Nickel and Koreader.

However, just a few minutes ago after checking my CPU in KSM, I went back into Nickel and got the popup box telling me that a computer had been detected and did I want to connect to it. However, I didn't have anything plugged into my KA1. Weird.

Just repeated the process and everything worked as expected. No popup box this time.

Not sure whether I should roll back to an earlier firmware now or just continue as is.

[tshering]

Originally Posted by Alanon

I have a Kobo Aura One and it lists mx6sl (with one l) as the CPU. Your post gives two l's, and now I'm too cautious to sideload the new firmware onto my Kobo.

So does this mean it's better not to sideload the update to avoid issues? Out of curiosity, what are the potential consequences and issues with KSM and this new firmware?

mx6sl and mx6sll are different processors. It was because of the similarity of the name that I overreacted.
I think there is no problem to update to the latest fw.

[tshering]

Originally Posted by Question Mark

However, just a few minutes ago after checking my CPU in KSM, I went back into Nickel and got the popup box telling me that a computer had been detected and did I want to connect to it. However, I didn't have anything plugged into my KA1. Weird.

Just repeated the process and everything worked as expected. No popup box this time.

Not sure whether I should roll back to an earlier firmware now or just continue as is.

I think the problem is the fault-prone usage of fmon (filemonitor) to associate certain pngs with scripts. After the FW update there was evidently some need to create one or several new thumb images, or to reindex some files. This triggered the script associated with simulate_usb_connection.png to run. You can try to start nickel by selecting

• "tools" > "nickel diverse.msh" > "start nickel no fmon.sh."

This will start nickel without associating the images with scripts. Therefore you can comfortably visit these images in the library, open them, so that they appear on the home screen, also as part of a collection (if they are part of one), and give nickel a chance to reindex them and create thumb images if necessary.

If you do not need simulate_usb_connection.png, just delete it from kbmenupngs. By this is one source of error removed.

[Question Mark]

Originally Posted by tshering

I think the problem is the fault-prone usage of fmon (filemonitor) to associate certain pngs with scripts. After the FW update there was evidently some need to create one or several new thumb images, or to reindex some files. This triggered the script associated with simulate_usb_connection.png to run. You can try to start nickel by selecting

• "tools" > "nickel diverse.msh" > "start nickel no fmon.sh."

This will start nickel without associating the images with scripts. Therefore you can comfortably visit these images in the library, open them, so that they appear on the home screen, also as part of a collection (if they are part of one), and give nickel a chance to reindex them and create thumb images if necessary.

If you do not need simulate_usb_connection.png, just delete it from kbmenupngs. By this is one source of error removed.

Many thanks for that. If it happens again, I may try this, but for now all seems fine. I can switch back and forth between Nickel/KSM/Koreader without any problems.

[tshering]

I became only now aware that the FW 4.xx packages for mark 6 models do not include arcotg_udc.ko. Can somebody please tell me whether usbNet (ethernet over usb) has stopped working on these devices?

[roukah]

Originally Posted by tshering

I might have been overcautious with my warning in the previous post. The cpu names of the devices of concern are mx6sll and mx6ull. I have no idea which models have such cpu; or whether they are already on the market.

Hello,
My CPU's name is mx6sl (single l) (H2O2), does this mean it's safe to install the latest KSM/firware? I'm wondering because the names match almost perfectly.

[tshering]

Originally Posted by roukah

Hello,
My CPU's name is mx6sl (single l) (H2O2), does this mean it's safe to install the latest KSM/firware? I'm wondering because the names match almost perfectly.

There is no special reason to be worried in the case of mx6sl.

[CH23]

@Tshering i saw in another thread that the bricking was a false alarm, but post #1 in this thread still says that 4.6.10075 will brick.

[tshering]

Originally Posted by CH23

@Tshering i saw in another thread that the bricking was a false alarm, but post #1 in this thread still says that 4.6.10075 will brick.

Thank you for reminding me!

[CH23]

Originally Posted by tshering

Thank you for reminding me!

welcome

What caused you to initially think it bricked the readers though?