Sunspot Home . . . Joggler menu
Mending a bricked Joggler

1 Find a "back door" into the O2 files so I can mend my mistakes
2 Make a dead Joggler like new.

I wanted to upgrade busybox to enable some of the missing commands.
I renamed the existing busybox to old_busybox - then cut the power by accident - result, one bricked Joggler

Help is on the forums but a bit lost in the listings - see some backup clippings below.

Bricked Joggler 1

I booted into Ubuntu on a memory stick and saw that in /dev there are partitions

It seems that mmcblk0p1 is a boot partition and the O2 file structure that I had been modifying was in partition mmcblk0p2

mmcblk0p4 contains folders app-cfg appshop media operamobile so if you make an error to a file here that bricks the Joggler it is no good just replacing mmcblk0p2 see below
mmcblk0p3 seems to be the same as mmcblk0p2 at the time of installing the raw system - it is held as a backup? - not sure how/when the Joggler uses these files

In Ubuntu I did -

sudo mkdir fgm
to create a new root folder
than did
sudo mount /dev/mmcblk0p2 fgm
Then found all the files in the fgm folder
I renamed bin/old_busybox to bin/busybox and the joggler booted fine again !!

Bricked Joggler 2 - this is the foolproof method when all else fails - but you lose your additions

This one was really dead - just kept recycling between the O2 logo and a black screen

But this worked!
In my Ubuntu stick I did
passwd root
and gave it a new password
then used ftp, Textwrangler, and Terminal from my iMac

I downloaded
and ftpd it to a folder on the Ubuntu stick

then in Mac terminal from that folder -

tar xvfz app-o2flash-26635.8686-S3-f1-reimage.tgz
sudo su
tools/bin/partimage -z2 restore /dev/mmcblk0p2 payload/image.myg
tools/bin/partimage -z2 restore /dev/mmcblk0p3 payload/image.myg
mount /dev/mmcblk0p1 /mnt
cp payload/vmlinux /mnt/vmlinux0
cp payload/vmlinux /mnt/vmlinux1
cd /mnt
md5sum vmlinux0 >>sum0
md5sum vmlinux1 >>sum1
sed -i '3d' sum0
sed -i '3d' sum1

On the first reboot without the Ubuntu stick it gave the GUI screen but the icons would not load the apps.
- on a second reboot it asked my name etc and all was like a new Joggler


Bricked Joggler 3 -restore your modified Joggler this way - but you need to have saved a backup when all was well !!!
After doing the above for Bricked Joggler 2 I had another crash while trying to intall an icon to run a script

While it was still OK I had saved the partitions to an Ubuntu stick using this script

dd if=/dev/mmcblk0p4 of=/home/graham/O2_backup/mmcblk0p4_101105.img bs=1M
dd if=/dev/mmcblk0p3 of=/home/graham/O2_backup/mmcblk0p3_101105.img bs=1M
dd if=/dev/mmcblk0p2 of=/home/graham/O2_backup/mmcblk0p2_101105.img bs=1M
dd if=/dev/mmcblk0p1 of=/home/graham/O2_backup/mmcblk0p1_101105.img bs=1M

I had prepared a re-install script -

dd if=/home/graham/O2_backup/mmcblk0p4_101105.img of=/dev/mmcblk0p4 bs=1M
dd if=/home/graham/O2_backup/mmcblk0p3_101105.img of=/dev/mmcblk0p3 bs=1M
dd if=/home/graham/O2_backup/mmcblk0p2_101105.img of=/dev/mmcblk0p2 bs=1M
dd if=/home/graham/O2_backup/mmcblk0p1_101105.img of=/dev/mmcblk0p1 bs=1M

but I just did
dd if=/dev/mmcblk0p2 of=/home/graham/O2_backup/mmcblk0p2_101105.img bs=1M
to see if that was enough - it was - all booting normally into the O2 OS again

Bricked Joggler 4

Just replacing mmcblk0p2 was not enough to cure a new crash - ( all I was doing was add an icon and a script by ftp! )
- but you can use the full re-install script above to get it running again !!
(however I guess mmcblk0p3 is least likely to be needed)

I see this on my ssh terminal to the O2 Joggler
# cat /etc/fstab
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mmcblk0p1 /efi vfat defaults 0 0
/dev/mmcblk0p2 / ext3 barrier=1 0 0
/dev/mmcblk0p4 /media ext3 barrier=1 0 0
proc /proc proc defaults 0 0
sys /sys sysfs defaults 0 0
udev /dev tmpfs defaults 0 0
devshm /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0

My backup of the help files are below - many thanks to all!!!!

These are some untested backup copies of some of the postings that deal with mending a dead O2 Joggler
- I am always scared that someone will remove these on line help files! Thanks to all posters.

I was messing about with the joggler and its stock FW, and bricked the thing.
When powered on the O2 screen flashed then it power cycled, basically no interaction at all.

BUT shortly before i bricked her i discovered that mmcblk0p3 was never mounted,
so i mounted it and seen that it was the same (or close) as mmcblk0p2 which was mounted at "/".
I figured it was some kind of backup partition.

When i bricked it i figured whats the worst that can happen and booted from usb to ubuntu
(thanks disca) and did:

EDIT: WARNING, dd is very powerful, please use carefully

sudo dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2

removed my usb stick and repowered, and it booted back to o2's software! an older
version of course but i'm sure it will update in time

Bricked O2

How to recover your Joggler if it won't boot

These tutorials are almost all copied & pasted from this forum
& the jogglerwiki forum but some of them are
spread over many pages of multiple posts. Hope they are of some help to anyone thinking of
unleashing the potential of what has turned out to be an amazing little gadget. Please
note that anything you do to your Joggler is entirely at your own risk and I take no
responsibility if you end up breaking your Joggler :'(

This is based on the original post at

Boot into one of the Ubuntu distros using a USB stick so that you have the time to do the
following. Do one line at a time ,it will seem as if it's hanging but give it time and it
works fine.


tar xvfz app-o2flash-26635.8686-S3-f1-reimage.tgz
sudo su
tools/bin/partimage -z2 restore /dev/mmcblk0p2 payload/image.myg
tools/bin/partimage -z2 restore /dev/mmcblk0p3 payload/image.myg
mount /dev/mmcblk0p1 /mnt
cp payload/vmlinux /mnt/vmlinux0
cp payload/vmlinux /mnt/vmlinux1
cd /mnt
md5sum vmlinux0 >>sum0
md5sum vmlinux1 >>sum1
sed -i '3d' sum0
sed -i '3d' sum1

Close down Ubuntu, remove the USB stick, unplug the Joggler for a minute or two then power
it up again.


For the common good I reformatted my Joggler's /media directory & did an upgrade to the most
recent O2 software. This effectively gives "factory-fresh" images of each partition which
ratx has kindly hosted.

Here is the link:

Restore Procedure

1. Boot into Ubuntu on USB stick

2. Copy or wget your backup files into /backup.

3. Run whichever of these you need to restore, depending on which partition is damaged
- most likely p2?

sudo dd if=/backup/mmcblk0p1.img of=/dev/mmcblk0p1 bs=1M
sudo dd if=/backup/mmcblk0p2.img of=/dev/mmcblk0p2 bs=1M
sudo dd if=/backup/mmcblk0p3.img of=/dev/mmcblk0p3 bs=1M
sudo dd if=/backup/mmcblk0p4.img of=/dev/mmcblk0p4 bs=1M

4. Shut down Ubuntu , disconnect power for a moment & boot into Joggler OS!

Please note that I accept no responsibility if you brick your Joggler, you proceed at your own risk.

Note - the Wired and Wireless ethernet links seem much more solid on the O2 software than in the Ubuntu images

Sunspot Home . . . .Joggler menu