Quote:
Originally Posted by vernel1008
THEN THE KOBO TEAM SHOULD CREATE A MORE STABLE AND CENTRALIZED WAY OF GIVING OUT UPDATES!
Background:
My Kobo Glo is stucked with the 2.4.0 update since February.
So I'm wondering why it doesn't update until yesterday even though I sync it both thru Wi-Fi and Kobo Desktop.
Last 05/30/2013 03:49 PM, I asked the customer service team on how can I update it. By 06/04/2013 02:50 PM, instructed was been made and as follows:
1. Ensure your device is completely powered off.
2. Press the light button at the left of the power button.
3. While holding the light button, slide the power button until the power light starts flashing and you see "restoring" on your Kobo Glo screen
4. Connect your device to your computer when prompted
5. Set it up using Kobo Desktop.
Does your device update? If not, please let me know and I will send the steps to sideload the update. For this, we require some additional information:
- What kind of computer do you have and what operating system does it run? (if you know the version and any applied service packs that would be helpful)
- If it’s Windows, is it a 32bit or 64bit system?
- If it's a MAC is it Intel Based or a Power PC?
I did instructions 1 to 5.
But before that, I make sure that the Kobo Desktop is synced with my Kobo Glo (as a backup) and I did recopy the memory of the Glo to my PC (for last resort because I don't trust the way Kobo Team does the update)
On a very very very unfortunate event, the Kobo Glo was wiped (I expected this since it's restoring). Then suddenly the Kobo Desktop automatically synced with the device. A Rakuten prompt asked to input my Email and Password so I did. Then, everything is gone. 
To Mr. SameerH, the Kobo product manager
If you want to treat regarding sideloading, then make sure your team can create a centralized update. Also, make sure that your database is write protected. If an email is used for a particular device, it should be restricted for that device or the data contained on that email should never be tampered. Although you have a sync feature for Kobo, but due to this incident, it is a pretty stupid feature you put right there.
Sincerely in a bad mood,
Vernel |
The wiping of the device on a restore is pretty much normal for any device. As it says in the Settings => Device Information, "Reset Device" and "
FACTORY RESET". Since the Kobo account information is now missing (see Setting => Account after finishing the restore), when you connect to the desktop app, it must ask for the username (email address) and password used for your Kobo account. This lets Kobo's servers know which books you have purchased from Kobo and which shelves you added on the Glo that will need to be restored. Since the Glo comes from the factory with no account information, this should be an expected side effect of the factory reset process. You will also find that you will either need to copy the authorization.xml file back to the .adobe-digital-editions folder or use ADE to re-authorize your device to allow reading Adobe ADEPT DRMed ebooks. You will also need to restore any sideloaded fonts in the fonts directory.
Sideloaded books will
not be restored. As has been discussed to death in this forum, Kobo does not back up your sideloaded books so it makes no sense to expect them to be automatically restored. The only place I've notice any information about sideloaded ebooks being stored by Kobo is in the reading stats where they are included in the number of books and number of hours read.
So now the real question is if your Kobo updated its firmware after the factory reset and sync using the desktop application? Since you stated that you backed up your Glo before the factory reset, you should have all your sideloaded books in that backup so restoring them should not be that big a problem. Great Ghu knows I've done it often enough to now keep all my ebooks on an uSD card that I can remove while experimenting to prevent any need to recopy a few thousand books.
If, as seems likely, you are not setting your ereader to English, use the equivalents for Settings, Account, Device Information, etc. as appropriate to the interface language.
Regards,
David