Thread: Firmware upgrade scripts
View Single Post
Old 04-23-2014, 09:27 AM   #18
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 Lucas Malor View Post
@davidfor: I confirm that the "recovery" upgrade-wifi.sh does install the uImage kernel:

PHP Code:
KERNEL=/mnt/onboard/.kobo/upgrade/$PLATFORM/uImage 
Yes, that's what I am seeing.
Quote:
Furthermore it doesn't distinguish between Aura HD and the other devices. Maybe on the Auras there are different scripts? I'm too much confused.
No, it is probably a version issue. The Glo factory resets to 2.1.5. The Aura HD is 2.4, I think. The script in the 2.4.0 package looks like it handles this correctly.
Quote:
I think that renaming uImage and sideloading the firmware should be the suggested way to update the device, instead of using Kobo Desktop. My tutorial about installing Virtualbox for using Kobo Desktop on Linux will be completely useless
It doesn't matter what method you use, so long as you copy the uImage to the appropriate name for the Glo, Touch and Mini. You can do that after the desktop app downloads the firmware and before you eject.
davidfor is offline   Reply With Quote