MobileRead Forums - View Single Post - Glo Memory Upgrade Mod Guide (With Pictures)

tigran · 11-30-2014, 04:33 AM

Interesting, I never get that message. Yes, Nickel works fine, no complaints and even shows the storage space in the Settings/Device information tab correctly.

Ah, maybe because I am using 3.8.0 firmware and your firmware is a different version? I.e. maybe they fixed the problem you describe in a later firmware...

One curious thing I discovered is this: you should ALWAYS go through Factory Reset after installing a newly cloned card. I don't know why --- maybe the FAT32 label "KOBOEREADER" is not close enough to the desired value of "KOBOeReader" (mkfs.vfat doesn't support case-sensitive labels, so I can't create it)? If you use your own FAT32 filesystem (as opposed to what the device creates) then you will run into some problems, like false "disk errors" (they are not real, as I've verified the whole card with badblocks and previously with h2testw). But if you let the device format the data filesystem then everything works fine. But I have no explanation for this strangeness.

11-30-2014, 04:33 AM	#159
tigran Zealot Posts: 140 Karma: 23528 Join Date: Nov 2009 Location: London Device: Kobo Aura One,HD,H2O,Touch,Mini,Kindle 3+DXG,Nook Simple Touch	Interesting, I never get that message. Yes, Nickel works fine, no complaints and even shows the storage space in the Settings/Device information tab correctly. Ah, maybe because I am using 3.8.0 firmware and your firmware is a different version? I.e. maybe they fixed the problem you describe in a later firmware... One curious thing I discovered is this: you should ALWAYS go through Factory Reset after installing a newly cloned card. I don't know why --- maybe the FAT32 label "KOBOEREADER" is not close enough to the desired value of "KOBOeReader" (mkfs.vfat doesn't support case-sensitive labels, so I can't create it)? If you use your own FAT32 filesystem (as opposed to what the device creates) then you will run into some problems, like false "disk errors" (they are not real, as I've verified the whole card with badblocks and previously with h2testw). But if you let the device format the data filesystem then everything works fine. But I have no explanation for this strangeness. Last edited by tigran; 11-30-2014 at 04:40 AM.