Oh dear :(

[monkums]

One of my Joggers just died.

Was running PNP III and became unresponsive and then wouldn't reboot.

Tried to re flash with the Open peak reflasher and got the attached error.

Is there any hope?

[hawsey]

Try Roobarbs reflash tool? Sometimes one works and not the other ....

[offbeatdave]

Yes, there is hope! I had this problem and fixed it! I first tried roobarb's reflashers (old and new) with no success.

I had to use a Linux image with a complete clean image of mmcblk0 on it.
I then wrote this via dd command.
The Joggler booted into the class is o2 stock OS (but the very original version - I guess it booted from the recovery partition as I've used this image to restore the final o2 stock OS before.
I was then able to reflash as before.

Hopefully someone will have an original mmcblk0 uploaded. If not let me know and I'll try and upload one next week.

[dwl99]

I have an original mmcblk0, let me know if you need it.

[monkums]

I had to use a Linux image with a complete clean image of mmcblk0 on it.
I then wrote this via dd command.

Any step by step instructions for this?

[roobarb!]

I had to use a Linux image with a complete clean image of mmcblk0 on it.
I then wrote this via dd command.

Any step by step instructions for this?

If you want to 'quickly' test whether your internal memory is okay, you could use the instructions on my site to flash the SqueezePlay OS, as this uses dd to write to the internal memory. Then give the OpenPeak reflasher another shot - it should recreate the partitions, as the SqueezePlay OS uses a different arrangement, which the OpenPeak tool should detect and 'put right'.

[monkums]

It seemed to work but won't boot.

It went through things but the screen is distorted so the screen is difficult to read.

It says that it should take 5-7 minutes to flash but takes about 10 seconds and says finished so I assume something is going wrong.

[hawsey]

Sorry if I missed it but did you try Roobarbs reflash tool? I have had jogglers that only work with Roobarbs and another that only works with the OP tool
No rhyme or reason to it really!!

[monkums]

It seemed to work but won't boot.

It went through things but the screen is distorted so the screen is difficult to read.

It says that it should take 5-7 minutes to flash but takes about 10 seconds and says finished so I assume something is going wrong.

Sorry should have said I was trying Roobarb's reflash to SqueezeOS.

[roobarb!]

It seemed to work but won't boot.

It went through things but the screen is distorted so the screen is difficult to read.

It says that it should take 5-7 minutes to flash but takes about 10 seconds and says finished so I assume something is going wrong.

Sorry should have said I was trying Roobarb's reflash to SqueezeOS.

Something is definitely playing up there. Try leaving your Joggler on (on whichever screen it sticks on) for a little while to give it chance to warm up. This often gets rid of any screen distortion and will let you see why it's shutting down so quickly.

By 'little while' I mean half an hour or so.

[monkums]

Managed to squint through the fuzz and before it get's to the reflash section there are some MMC errors.

[Mevi]

It does sound like the eMMC (flash storage) is knackered. That it boots off the side port is some consolation, I guess. Sadly, the factory OS won't boot from USB, but there are quite a few alternatives for you to try.

[offbeatdave]

OK, what I did when all reflashing tools failed was equivalent to the following (with my own backup of mmcblk0)...

1) Boot into a Linux Mint/Ubuntu image from USB (which needs networking if you're downloading an image).
2) Open up terminal window on the Joggler (or telnet in once Linux is booted) and enter...

Code: Select all

sudo mkdir /backup
sudo chmod a+rwx /backup
cd /backup
sudo umount mmcblk0*
sudo wget http://files.exotica.org.uk/?file=joggler/files/mmcblk0.img.gz
gzip -cd mmcblk0.img.gz | sudo dd of=/dev/mmcblk0 bs=1M

That zipped up mmcblk0 is 159Mb to download and unzips to 1Gb. I wrote my clean backup image to the Joggler. I then booted and it booted into the very first version of the o2 OS (pre-Internet Radio!), even though this image usually booted into the final o2 version of the OS. I believe that the problems caused it to use the backup partition. I was then able to use the OpenPeak reflasher and, touch wood, I'm still working.

Of course, there is the possibility that it's completely screwed, as is the case with a different Joggler of mine!

[offbeatdave]

How did you get on?

[monkums]

Showing my Linux noobiness now.

Do I have to enable Telnet on the Mint Joggler and how do I find the IP address.?

[offbeatdave]

It doesn't need it if you're doing everything via the Joggler.
Can't remember off the top of my head which menu option the IP address will be in if you want to telnet in. Someone will point it out though.

[monkums]

Unfortunately I don't have a USB hub so can't connect a keyboard

Found the IP address

[offbeatdave]

you can use the on screen keyboard. fiddly but works.

[monkums]

I managed to use the on screen keyboard and some cut and past.

It seemed to not through up any errors but the Joggler still just boots to the o2 logo so maybe I missed something so I'll try again.

[monkums]

Ok I've tried again and definately no luck.

When I enter 'sudo umount mmcblk0*'

I get 'umount: mmcblk0.img.gz: not mounted'

and when I enter 'gzip -cd mmcblk0.img.gz | sudo dd of=/dev/mmcblk0 bs=1M'

I get:

dd: writing `/dev/mmcblk0': No space left on device
0+7504 records in
0+7503 records out
253321216 bytes (253 MB) copied, 25.0618 s, 10.1 MB/s