10-18-2012, 01:23 AM | #16 |
Connoisseur
Posts: 78
Karma: 165868
Join Date: Jan 2012
Device: Nook Touch
|
What about the Glo? Is there any update for it?
|
10-18-2012, 01:39 AM | #17 |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
The Glo, Mini and Touch use the same firmware.
Edit: Well, I've since been proven wrong. Last edited by davidfor; 10-18-2012 at 07:42 PM. |
Advert | |
|
10-18-2012, 01:53 AM | #18 |
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
murg,
The "Going forward" comment should be above the 2.0.4 firmware. That firmware is the first of the version specific ones. |
10-18-2012, 03:11 AM | #19 | |
Member
Posts: 19
Karma: 124040
Join Date: Apr 2012
Location: Antananarivo, Madagascar
Device: Kobo Touch
|
Quote:
|
|
10-18-2012, 12:25 PM | #20 |
Connoisseur
Posts: 78
Karma: 165868
Join Date: Jan 2012
Device: Nook Touch
|
This doesn't seem to be true:
https://www.mobileread.com/forums/sho....php?p=2269562 |
Advert | |
|
10-18-2012, 12:49 PM | #21 |
Junior Member
Posts: 4
Karma: 44
Join Date: Oct 2012
Device: Kobo Glo
|
Kobo Glo 2.1.5 r43939 (Why the same rev as the touch?)
http://download.kobobooks.com/firmwa...date-2.1.5.zip md5sum: 66e28ab31af8361e7223bfe48f926001 Touch md5sum (/kobo3/) 9a826451c1114e88fca23cf55a75b0ef Looks like different uboot at least. |
10-18-2012, 12:53 PM | #22 |
Zealot
Posts: 137
Karma: 10
Join Date: Feb 2010
Device: none
|
2.1.5 sideload update
Hi fellow Mobilereaders,
I'm fed up with waiting for the 2.1.5 update for my Kobotouch (now on 2.0.0, or more precisely r41166) so I downloaded 2.1.5. Now I have a whole lot of goodies on my Mac, including - Koboroot.gbz - Manifest.md5sum - Update file The latter contains: - ulmage - u-boot.bin - NTX508 file The latter contains: - u-boot.bin - ulmage I wonder if some charitable soul, familiar with the Mac, could help me to the next step, that is, the actual sideloading? What do I put where on the Kobo touch device? I am well aware that sideloading is wicked Thanks for all advice, Rojofo. |
10-18-2012, 05:53 PM | #23 |
Kobo Developer Intern
Posts: 84
Karma: 253043
Join Date: Apr 2010
Location: Toronto, ON
Device: Kobo Touch, Kobo Mini, Kobo Glo
|
|
10-18-2012, 06:35 PM | #24 |
No Comment
Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
This is why the onboard Firmware Update Management Firmware should confirm that the presented firmware update package is for the device being updated.
This isn't very hard. It can be done with a single file containing the device the firmware is for. And the FUMF should be able to determine which device it is operating on fairly easily. Code:
if (DeviceCodeInFirmware != DeviceCodeOnDevice) { // firmware for wrong device DeleteFirmwareFiles(); } else { // firmware for this device UpdateFirmware(); } |
10-18-2012, 07:03 PM | #25 |
Zealot
Posts: 137
Karma: 10
Join Date: Feb 2010
Device: none
|
Surpisingly or amusingly, after my post yesterday, having decided to sideload the 2.1.4 update, come what may, my Kobo touch updated itself by wifi to 2.1.5 !!!
All I can suggest to those (particularly Australians apparently) who are stuck on version 2.0.0 of the firmware, is to threaten to sideload on this forum! They may suddenly get lucky! Best, Rojofo. |
10-18-2012, 09:30 PM | #26 | |
Kobo Developer Intern
Posts: 84
Karma: 253043
Join Date: Apr 2010
Location: Toronto, ON
Device: Kobo Touch, Kobo Mini, Kobo Glo
|
Quote:
How does the e-reader actually know that these files are the correct ones? There's an MD5 manifest to verify that the files are not corrupt but there is no way to validate that the kernel or bootloader are actually targetted for that device's particular hardware, moreover this doesn't actually prevent tampering or DIY'ing. This is why we rely on the backend server to serve out the correct files for the device's firmware during a Wi-Fi update or desktop update. Locking down the firmware update mechanism has been proposed, but why would we want to stifle hacking? It really wouldn't accomplish anything in the end. Put it another way: what happens when you use fastboot to flash a new ROM on an Android phone or tablet? Does it do any validation? Nope. If you flash the wrong bootloader then you're pretty much on your own. Last edited by george.talusan; 10-18-2012 at 09:38 PM. |
|
10-18-2012, 09:49 PM | #27 |
Kobo Developer Intern
Posts: 84
Karma: 253043
Join Date: Apr 2010
Location: Toronto, ON
Device: Kobo Touch, Kobo Mini, Kobo Glo
|
Here's some actual code for the guy that bricked his Glo:
sudo dd if=u-boot_mddr_256-E60610D-K4X2G323PC.bin of=/dev/<your sdcard> bs=1K seek=1 skip=1 sudo dd if=uImage of=/dev/<your sdcard> bs=512 seek=2048 You will need to remove the back from Kobo Glo using an exacto knife or plastic prying tool. Be careful to not mar the finish. 1. Boot your computer into Linux (I hope you or a friend have it installed) and plug your Kobo Glo's micro SD card into your computer. 2. Note the dev node of your card, let's call it "sdX" for the time being. Use 'df' to figure it out. 3. Replace <your sdcard> with sdX while typing out those two commands above into a terminal. 4. Safely eject the card and plug it back into your Kobo Glo. You can get u-boot_mddr_256-E60610D-K4X2G323PC.bin and uImage from the Kobo Glo firmware at the top of this thread. |
10-19-2012, 06:05 AM | #28 | |||
No Comment
Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
Quote:
This allows people who want to tamper to tamper, but protects non-tamperers from harming their device. Quote:
Quote:
Also, there is some presumption that the firmware acquired is for a specific device, not like Kobo's latest release where the two different firmware files have exactly the same filename. ----- And another thing, are you willing to guarantee that the Kobo PC software will NEVER get confused and load the wrong firmware onto the device? Before you answer that, you may want to consider that Kobo doesn't have a very stellar reputation for releasing bug-free software. Last edited by murg; 10-19-2012 at 06:10 AM. |
|||
10-19-2012, 06:07 AM | #29 | |
No Comment
Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
Quote:
I almost forgot... Not having a Glo, is it true that Kobo has removed the ability to do a hardware factory reset from the Glo? That you have to have a functioning Glo in order to do a factory reset? What recent experience could possibly lead Kobo to believe that this was a good idea? The square-dancing bug? Last edited by murg; 10-19-2012 at 06:13 AM. |
|
10-19-2012, 06:16 AM | #30 | ||
Connoisseur
Posts: 62
Karma: 31414
Join Date: Sep 2012
Location: France
Device: Kobo Glo
|
Quote:
Quote:
It's quite different from a user willingly sideloading such firmware. |
||
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
SD card firmware (1.4) image links for AU/NZ | sabredog | Kobo Reader | 42 | 03-27-2015 03:11 AM |
Kobo Writing Life now open (New direct self-pub program) | MMHaven | Writers' Corner | 12 | 08-08-2012 10:25 AM |
Firmware Links | Montebello | Andere Lesegeräte | 0 | 12-20-2009 03:58 PM |
Updating firmware without direct Internet connection | KillerRabbit | iRex | 1 | 01-08-2007 11:08 AM |