Kobo E_Reader wifi upgrade gone bad

[flyboy320]

Originally Posted by Spode

Just out of curiosity. Most Kobo readers have a 1gb internal microSD card. Why are the images. so generously provided here, almost 2gb in size? Is it a Linux conversion issue?

I just got a great deal on an N647. Could someone send me an N647 image? I'd like to have it as a backup. (I'd rather not open the eReader to make by own image. If I decide to do this at some point, would the image copied off a 1gb microSD card be larger than 1gb? Thanks for all your help and patience.

The image I sent you is from an N647 device, my apologies if you were looking for a different image. It is about 2GB in size as that's the size of the SD card in the N647 (at least all the ones I've seen).

[DNSB]

Originally Posted by Spode

Just out of curiosity. Most Kobo readers have a 1gb internal microSD card. Why are the images. so generously provided here, almost 2gb in size? Is it a Linux conversion issue?

The internal uSD card is 2GB. It has multiple partitions with two Linux partitions and a FAT32 partition. The only partition that is visible using the USB port is the FAT32 partition. On a WiFi N289, the Linux partitions are 256MB & 512MB while the FAT32 partition is ~1.1GB.

Some people have used Linux systems to generate images, others such as myself use a Windows system with software that allows copying the uSD card to an image and restoring from that image. Add in a partition management utility to resize the FAT32 partition when you move to a larger card and you're in business.

There has been some items published on creating images of the entire card without having to open the unit up using various methods but restoring the image requires opening the unit.

[Spode]

Originally Posted by flyboy320

The image I sent you is from an N647 device, my apologies if you were looking for a different image. It is about 2GB in size as that's the size of the SD card in the N647 (at least all the ones I've seen).

I have an N289 image. I got a great deal on an N647 and went for it. I don't have an N647 image. It'd be great if you could send me one.

Thanks for the explanation. What I still don't understand, even if the internal card is a 2gb microSD, since the image is almost 2gb, how can anything be left over for personal downloads? The Kobo Wifi is always advertised as having a full Gigabyte for storing books. Where is that storage space coming from? This isn't an urgent issue obviously. I'm just curious.

I haven't burned a new image yet. Waiting for an eReader so I can connect to my computer. One thing I did do is hook my n289 to my computer to see if I could overstore the image directly onto the internal microSD. I got the message that there wasn't sufficient space on the card to continue. However, I could overstore a truncated image if I chose to. The math just doesn't add up. A standard 2gb internal card should have fully accommodated the 1.9 (or thereabouts) image.

Many of you may not find this confusing. I'm baffled. Something's going on that is beyond my penetration. None of this is important. I'd like to figure this out purely for personal gratification. Don't need an answer, would simply like one.

Thanks again.

[flyboy320]

PM sent Spode...

[DNSB]

Originally Posted by Spode

Thanks for the explanation. What I still don't understand, even if the internal card is a 2gb microSD, since the image is almost 2gb, how can anything be left over for personal downloads? The Kobo Wifi is always advertised as having a full Gigabyte for storing books. Where is that storage space coming from? This isn't an urgent issue obviously. I'm just curious.

The image is a bit image of the entire uSD card. It doesn't care if the space is empty or used, all the bits are copied. That is one of the reasons why the image compress so well.

Originally Posted by Spode

I haven't burned a new image yet. Waiting for an eReader so I can connect to my computer. One thing I did do is hook my n289 to my computer to see if I could overstore the image directly onto the internal microSD. I got the message that there wasn't sufficient space on the card to continue. However, I could overstore a truncated image if I chose to. The math just doesn't add up. A standard 2gb internal card should have fully accommodated the 1.9 (or thereabouts) image.

As mentioned in a previous message, the USB connection only exposes the FAT32 partition on the uSD card. The other partitions are not accessible over the USB connection. You will need to open up the WiFi, extract the uSD card and connect it to your computer to see the entire card. DO NOT FORMAT the card if prompted when you connect it to a Windows system. The tools used by quite a few under Windows are mentioned elsewhere but for completeness:

For creating an image from a SD card:
VConsole USB Image creator

For writing an image to a SD card:
VConsole USB Image writer

For resizing partitions after moving to a larger SD card:
MiniTool Partition Wizard Free edition

Information on opening up the Kobo WiFi to get at the uSD card:
Kobo_WiFi_Hacking

Originally Posted by Spode

Many of you may not find this confusing. I'm baffled. Something's going on that is beyond my penetration. None of this is important. I'd like to figure this out purely for personal gratification. Don't need an answer, would simply like one.

Good luck, Grasshopper!

And yes, I do consider this fairly simple -- the advantage of more years playing with electronics and computers than I care to think about.

[Spode]

Originally Posted by DNSB

Good luck, Grasshopper!

And yes, I do consider this fairly simple -- the advantage of more years playing with electronics and computers than I care to think about.

Thank you. I finally understand. I'm embarrassed to say I did format the uSD. I have an image of the n289 which I got here. Hoping I can simply write (flash?) it using the software you suggest. I may have created an irreversible problem by formatting it. It's now a 2gb FAT32 partition. I dove right in, unprepared, uninformed and may have a dead fish for my rashness. (But maybe not. If all I can see is my FAT partition via my computer, maybe that's all I formatted. I hope so.)

Grasshopper? That's very funny. My younger brother we called cricket when he was a kid. Guess it cycled its way back to me.

Do you have an image of the N647? Someone sent me one, but I could never get it to successfully download. After a couple of hours and a third of the way complete the connection would sever and leave me with nothing. Tried it several times. Same thing happened again and again.

I congratulate you on your many years of electronic exploration. Knowledge, whatever form it takes, is invaluable.



Thanks again. One more mystery solved.

denis

[Spode]

Originally Posted by DNSB

The internal uSD card is 2GB. It has multiple partitions with two Linux partitions and a FAT32 partition. The only partition that is visible using the USB port is the FAT32 partition. On a WiFi N289, the Linux partitions are 256MB & 512MB while the FAT32 partition is ~1.1GB.

Some people have used Linux systems to generate images, others such as myself use a Windows system with software that allows copying the uSD card to an image and restoring from that image. Add in a partition management utility to resize the FAT32 partition when you move to a larger card and you're in business.

There has been some items published on creating images of the entire card without having to open the unit up using various methods but restoring the image requires opening the unit.

Very interesting. Read this after your later response, further down. I think I've pretty much got it now.

You've been very helpful. Many thanks.

denis

[DNSB]

Originally Posted by Spode

Grasshopper? That's very funny. My younger brother we called cricket when he was a kid. Guess it cycled its way back to me.

Going back to a TV series in the early 70's (Kung Fu) where in flashbacks to his training, the Shaolin master referred to his student as Grasshopper.

Originally Posted by Spode

Do you have an image of the N647? Someone sent me one, but I could never get it to successfully download. After a couple of hours and a third of the way complete the connection would sever and leave me with nothing. Tried it several times. Same thing happened again and again.

Sorry but I don't have a N647 image. The WiFi I have is a N289.

Originally Posted by Spode

I congratulate you on your many years of electronic exploration. Knowledge, whatever form it takes, is invaluable.

True, but did it have to come with progressive lenses?

[theruns]

Hi - wondering if anyone would be able to share a copy of the kobo wifi image with me?

I ran into this problem on my kobo a while back and it has been on the shelf since, would love to revive it though. After reading this forum, I'm assuming it occurred during an update.

Thanks!

[flyboy320]

Originally Posted by theruns

Hi - wondering if anyone would be able to share a copy of the kobo wifi image with me?

I ran into this problem on my kobo a while back and it has been on the shelf since, would love to revive it though. After reading this forum, I'm assuming it occurred during an update.

Thanks!

PM sent.

[Spode]

Originally Posted by flyboy320

PM sent Spode...

Thanks for sending the image. Unfortunately, the download is never successful. Tried downloading from your drop box. Went through the paces several times, but every effort was for whatever reason aborted.

Don't understand it. I downloaded the n289 without a hiccup, fast and easy. But the N647 grinds along for an hour or more but never finishes. Tried downloading it off my laptop. Same thing.

Appreciate your help. Wish it hadn't been for nothing.

[davidfor]

@Spode: I have completely forgotten if I have sent you a link to my image for the WiFi. In any case, I have now. The server should allow resuming a failed download. If you use a client that will retry/resume, it should download OK.

[Spode]

Grand Sorcerer - davidfor

It worked. Came through slowly but completely. Thanks for your persistence.

Don't mean to tout my own horn. Just added 1 point of karma to your mountain. 5 million way plus. The world is at your feet apparently. i am impressed.

[Spode]

Originally Posted by DNSB

The internal uSD card is 2GB. It has multiple partitions with two Linux partitions and a FAT32 partition. The only partition that is visible using the USB port is the FAT32 partition. On a WiFi N289, the Linux partitions are 256MB & 512MB while the FAT32 partition is ~1.1GB.

Some people have used Linux systems to generate images, others such as myself use a Windows system with software that allows copying the uSD card to an image and restoring from that image. Add in a partition management utility to resize the FAT32 partition when you move to a larger card and you're in business.

There has been some items published on creating images of the entire card without having to open the unit up using various methods but restoring the image requires opening the unit.

So there is no way to see a Linux partition in Win 7? I can copy and write images, but I can't actually see any of the resultant Linux partitions? I tried Linux Reader but it didn't show the partitions on the uSD card. Is there any software or hardware that does this?

I know nothing about Linux. I was hoping if it were possible to see the Linux partitions that I could delete and replace corrupted or dysfunctional partitions. This is no doubt naive, it's probably much more complicated than I realize. You can read FAT32 directories in Linux. Why not the reverse? Think maybe I'll get a Windows version of Linux. Windows is no limiting. Would love to move onto a new OS.

[DNSB]

Originally Posted by Spode

So there is no way to see a Linux partition in Win 7? I can copy and write images, but I can't actually see any of the resultant Linux partitions? I tried Linux Reader but it didn't show the partitions on the uSD card. Is there any software or hardware that does this?

I know nothing about Linux. I was hoping if it were possible to see the Linux partitions that I could delete and replace corrupted or dysfunctional partitions. This is no doubt naive, it's probably much more complicated than I realize. You can read FAT32 directories in Linux. Why not the reverse? Think maybe I'll get a Windows version of Linux. Windows is no limiting. Would love to move onto a new OS.

I've played with ext2fsd under Windows but for the most part, I've used the DiskInternals freeware Linux Reader to grab files from Linux partitions. There are a couple of other ways of accessing Linux partitions but the best way is to have a Linux machine.

That said, I would not recommend playing with the 2 Linux partitions until you have a good backup -- good as in you've restored it to another uSD card and your ereader works with that card installed.

As for why Linux can read FAT32 but Windows can't read Ext2/Ext3/Ext4/ReiserFS/.../ZFS, just consider how common FAT32 is even for non-computer devices.