Oh dear :(

[offbeatdave]

Opps, missed out a /dev/

OK, let's try and correct that error and also try a different route (slightly) -

Code: Select all

sudo rm -r /backup/*
cd /backup
sudo wget http://files.exotica.org.uk/?file=joggler/files/mmcblk0.img.gz
sudo gzip -cd mmcblk0.img.gz 
sudo umount /dev/mmcblk0*
sudo dd if=/backup/mmcblk0.img of=/dev/mmcblk0 bs=1M

[monkums]

When i type in 'sudo gzip -cd mmcblk0.img.gz ' I get screens and screens of random text for about 15 minutes and the the work Putty repeated (I'm using Putty) and everything seems to stop and I don't get a prompt.

Is this right?

[offbeatdave]

oops. I've probably messed up the unzipping. I'll have another look later.

[jpharvey]

sudo gzip -d ....

the -c option puts the output to stdout

John

[offbeatdave]

ta

[monkums]

sudo gzip -d ....

the -c option puts the output to stdout

John

That stopped the random characters but I'm still getting the same errors ate the next stage:

sudo umount mmcblk0* gives umount: /dev/mmcblk0*: not found

and sudo dd if=/backup/mmcblk0.img of=/dev/mmcblk0 bs=1M gives

dd: writing `/dev/mmcblk0': No space left on device
242+0 records in
241+0 records out
253321216 bytes (253 MB) copied, 35.4134 s, 7.2 MB/s

[offbeatdave]

I'm still getting the same errors ate the next stage:

sudo umount mmcblk0* gives umount: /dev/mmcblk0*: not found

Make sure you are typing

Code: Select all

sudo umount /dev/mmcblk0*

[monkums]

This is what I'm using:

Code: Select all

sudo rm -r /backup/*
cd /backup
sudo wget http://files.exotica.org.uk/?file=joggler/files/mmcblk0.img.gz
sudo gzip -d mmcblk0.img.gz 
sudo umount /dev/mmcblk0*
sudo dd if=/backup/mmcblk0.img of=/dev/mmcblk0 bs=1M

And I still get 'umount: /dev/mmcblk0*: not found' after 'sudo umount /dev/mmcblk0*'

Not sure where I'm going wrong?

[BuZz]

mmcblk0 might be missing. check contents of /dev (ls -la) and if it's not there. post output from "dmesg"

[monkums]

mmcblk0 might be missing. check contents of /dev (ls -la) and if it's not there. post output from "dmesg"

Just checked and it isn't there.

I think I've attached what you need.

dmesg.txt

(10.31 KiB) Downloaded 318 times

[BuZz]

the problem is either your internal flash is damaged/dead or a corrupted efi.

[monkums]

Oh well. At least it boots from a stick (famous last words).

Now which OS to use.

[offbeatdave]

Running out of ideas. You could try this - it worked for me once or twice.

Working in a Linux terminal, first I did

Code: Select all

sudo umount /dev/mmcblk0*

Then did

Code: Select all

sudo fdisk /dev/mmcblk0

This presented me with the following:

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u').

So I pressed the following c and u followed by d, 1, d, 2, d, 3, d, n, p, enter enter and finally w. I think that they are the correct letters and numbers - you'll suss it out if not.

This scrubbed the device. I then gave Roobarb's reflash tool another go. Once again, it went through the motions but, lo and behold, one the first attempt the Joggler fired up and booted straight into a nice clean stock OS!

Otherwise, it probably has gone wrong for ever!

[BuZz]

that isn't going to help as the device doesn't exist. you can see in the dmesg output it errors when probing - which means the flash is dead, or the efi is corrupted in some manner which I suppose could also cause this, but I should think the flash is most likely kaput.

[offbeatdave]

that isn't going to help as the device doesn't exist. you can see in the dmesg output it errors when probing - which means the flash is dead, or the efi is corrupted in some manner which I suppose could also cause this, but I should think the flash is most likely kaput.

Ah! Fair enough!