Direct Links to Kobo Firmware

[Mrs_Often]

Taming mentions here: https://www.mobileread.com/forums/sho....php?p=2252198 that she has been told the factory reset on the glo works the same as with the touch, only with the light on/off button instead of the home button...

But, she also states she hasn't tried it herself.
I wonder....

[mdclements]

Originally Posted by Mrs_Often

Taming mentions here: https://www.mobileread.com/forums/sho....php?p=2252198 that she has been told the factory reset on the glo works the same as with the touch, only with the light on/off button instead of the home button...

But, she also states she hasn't tried it herself.
I wonder....

This is correct. Holding the light button while powering on the device will put the device into factory reset mode.

[Mrs_Often]

Thanks for the confirmation mdclements.

I'm confused though, how come you told semhoun that his device was broken instead of mentioning the reset like he asked https://www.mobileread.com/forums/sho...php?t=194206#9

[mdclements]

Originally Posted by Mrs_Often

Thanks for the confirmation mdclements.

I'm confused though, how come you told semhoun that his device was broken instead of mentioning the reset like he asked https://www.mobileread.com/forums/sho...php?t=194206#9

Because the hard reset will not work if you load the wrong firmware.

[Mrs_Often]

Okay, thanks for clarifying!

[SeigneurAo]

Preposterous.

[Mrs_Often]

Originally Posted by SeigneurAo

Preposterous.

I'm afraid I have to agree.

[george.talusan]

Originally Posted by murg

Having to have Linux to undo this is so far beyond being reasonable that I'm having a hard time believing that Kobo understands that it is selling consumer grade electronic devices.

You're free to use Windows if you want to write directly to the micro SD card. I just will not provide instructions on how to do it.

The same instructions above will work for OS X.

[murg]

Originally Posted by george.talusan

You're free to use Windows if you want to write directly to the micro SD card. I just will not provide instructions on how to do it.

The same instructions above will work for OS X.

Huh? You'll provide the instructions for operating systems that a small minority of your customers use, but not for the operating system that a vast majority of your customers use?

[george.talusan]

Originally Posted by murg

Huh? You'll provide the instructions for operating systems that a small minority of your customers use, but not for the operating system that a vast majority of your customers use?

I'm sure the vast majority of users don't follow this thread on MR.

Answering this question is really taking the fun out of watching this developer forum thrive. But if you insist:

1. Install CYGWIN.
2. Use instructions above.

Now you'll be able to actually use this knowledge with the rest of the threads on this sub-forum. Amazing!

[murg]

Originally Posted by george.talusan

Answering this question is really taking the fun out of watching this developer forum thrive.

This was a specific request for information on how to restore a broken Glo. It has nothing to do with a developer's forum on MR.

[met67]

Originally Posted by george.talusan

I'm sure the vast majority of users don't follow this thread on MR.

Answering this question is really taking the fun out of watching this developer forum thrive.

Please don't abandon us

[DNSB]

Originally Posted by george.talusan

I'm sure the vast majority of users don't follow this thread on MR.

Answering this question is really taking the fun out of watching this developer forum thrive. But if you insist:

1. Install CYGWIN.
2. Use instructions above.

Now you'll be able to actually use this knowledge with the rest of the threads on this sub-forum. Amazing!

Takes all the fun out of it.

Personally, I feel that you've gone above and beyond in supplying the instructions that you have.

Perhaps some of the people in this forum should take a quick trip through the wireless router third party firmware forums. Nothing like locating and using a JTAG connnector in the hope of being able to recover a bricked router for sheer fun compared to booting your PC from a Linux live distribution CD and typing a few lines.

On the flip side, I would have to comment that having the firmware loader do a check before flashing to ensure the correct device is being flashed should not be all that hard. Most PC BIOS upgrades for a few decades now have implemented that functionality.

On yet another hand, is there a reason that when I sideloaded books onto my new Glo, I had to power cycle it before the cover images would work?

Regards,
David

[thp1017]

Hmm, well, I now see /bin/kobo_config.sh in both the Glo and Touch v2.1.5 firmware releases, which returns the product name of the device (mentioned here).

I'm hoping that means for future release, a file will be added (say, required_product), that lists the product it works for... With those two things, it shouldn't take more a few additional lines of bash code in /etc/init.d/upgrade-wifi.sh to prevent the firmware from being applied to the wrong device...

I did see that the kobo_config.sh script was not in 2.0.0.c, so checking may not have been possible with the factory Glo - but hopefully from now on out?

[davidfor]

Originally Posted by thp1017

Hmm, well, I now see /bin/kobo_config.sh in both the Glo and Touch v2.1.5 firmware releases, which returns the product name of the device (mentioned here).

I'm hoping that means for future release, a file will be added (say, required_product), that lists the product it works for... With those two things, it shouldn't take more a few additional lines of bash code in /etc/init.d/upgrade-wifi.sh to prevent the firmware from being applied to the wrong device...

I did see that the kobo_config.sh script was not in 2.0.0.c, so checking may not have been possible with the factory Glo - but hopefully from now on out?

Your looking at code that is executed a long time after the problem that is being discussed occurs. The issue is the image and bin files in the upgrade directory of the downloaded file. These are executed or loaded or whatever during the upgrade. If any checking can be done, it has to be when this is being loaded.

Of course, there already is code that checks if the right firmware is being loaded. It is the code in the desktop app or WiFi download or maybe on the download server that makes sure the right firmware file is downloaded. Personally, I am happy with this mechanism. And I am happy that if I want to bypass this and take the risk I can try something else. But, that is my decision.