Thread: Direct Links to Kobo Firmware
View Single Post
Old 10-19-2012, 07:46 PM   #45
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by thp1017 View Post
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.
davidfor is offline   Reply With Quote