Actually, the "image download / success report" ratio shows that only one percent report their success, which is close to what psychology tells us should be expected. So perhaps 12,000 might be a closer estimate for Kindles debricked. Remember that people have to go to the trouble of registering here to post a success report, and a LOT of people avoid that for sites that require email confirmation.
So, "over ten thousand served" could be a valid subtitle for this thread.
I even got a PM from somebody who said they were referred to this thread from Amazon.com.

The only problem with this view is that the pastebin only has 5200 views right now.

The only problem with this view is that the pastebin only has 5200 views right now.

I was basing my estimate on image downloads rather than pastebin accesses (and there was a previous pastebin before the current one, which also had significant views).

Even ignoring the various pastebin mirrors, and the image links in guides and posts at "other" websites", and ignoring the multiple debrickings using already-downloaded images, that is still the same order of magnitide (except about 2% reporting success instead of 1%). And the debrickings not using the pastebin tend to shrink that toward 1%, so reality is a lot closer to my 12,000 estimate than your 1,200 estimate...

The pastebin contains two mirrors for the K3 3.0.2 debricking repair images. The new 3.0.2 mirrors are single compressed files, not subject to the "size limit and multi-part zip file" limitations at Mediafire. Thanks guys.

There is also a mirror for the pastebin (http:/snipurl.com/debrickX, where X changes each time that mirror changes). Does anybody know how to edit a snipurl to point to a new location?

Yes, I know it wasn't too smart job, but I haven't found any 4.1.0 images.

I'm continuing my "risky" debricking. I've dumped /dev/mmcblk0p1 from a K4S updated to 4.1.0 fw, and replaced the K4B's /dev/mmcblk0p1 with this image. I was surprised it works but it does - in spite of that the kernel remains the 4.0.0 one left from my first hasty (and ballsy ) debrick. Now I have K4 SO with 4.1.0 fw and it's able to connect to my Amazon account. However, this 4.1.0 fw is not the same as the original K4B one - it has noticeably lesser contrast and worse font rendering.

I'm continuing my "risky" debricking. I've dumped /dev/mmcblk0p1 from a K4S updated to 4.1.0 fw, and replaced the K4B's /dev/mmcblk0p1 with this image. I was surprised it works but it does - in spite of that the kernel remains the 4.0.0 one left from my first hasty (and ballsy ) debrick. Now I have K4 SO with 4.1.0 fw and it's able to connect to my Amazon account. However, this 4.1.0 fw is not the same as the original K4B one - it has noticeably lesser contrast and worse font rendering.

The K4B ships with new bolder fonts, and perhaps an improved eink update algorithm. Perhaps flashing a K4B firmware onto a K4S will also improve the eink contrast on the old K4 too.

That (win-7) will limit how much help I can be, but if willing to take your answers in parts....

Part by me and part by someone else....

Thank you so much - somehow I failed to see this earlier.

Neither can I translate to Win-7; taught myself Win 3.1 but that was back when I had both time and brain.

Yes I have 32 bit!

I will have to have another go tomorrow (barely a half-hour to play, today, and no-brain this evening; see my sig) but

Quote:

Originally Posted by knc1

Removing the .001 and .002 was probably the "right thing to do" -
at least that would be my (non-Windows user) guess.Unless the remaining parts of the filenames where the same.
You need both files present to un-zip a multi-part zip file.

The image files will probably not use the zip compression once they are moved to other hosting.
You would be doing yourself a favor to install 7zip:http://www.7-zip.org/download.html

Thanks! That's what I needed! Never bothered much with zipping and as I say, this laptop is inherited together with its motley software.

I have never had anything to do with multi-part files so this is Here Be Dragons territory (always fun).

If we're lucky I won't need any more help but can't look at it now. If in trouble again, I'll be back...