birds like wires

Search

Reflash System for OpenFrame

Latest Release: 19th September 2014

Download System v1.11 – (160MB) MD5


Originally written for the O2 Joggler, the latest version of the Reflash System can be used on both types of the commonly available OpenFrame units. These are great devices; useful, hackable, affordable and fun. However, if you find yourself with one that’s less than happy, with any luck this system should bring it back to life.

This is designed to be a reliable method of reflashing any OpenFrame device, even in the event that the internal flash memory has had it’s partitions destroyed. These units are robust and will continue to boot from external USB devices even when the internal memory has given up, so unless you have a hardware failure or EFI problem this should get things working again.

In addition, this system can also be used to write a completely different OS to the internal memory, such as SqueezePlay OS. Instructions are provided below, but the alternative OS should have been designed to run from the internal memory. You could potentially flash anything, but not everything will work.


  • The Reflashing Tool has now been extensively tested on many OpenFrames, with a high degree of success. However, this software is used entirely at your own risk and will not repair a OpenFrame where the internal flash memory has become worn or damaged. If the internal memory has failed, you will no longer be able to run the default operating system, but there are many alternatives available that work extremely well from a USB storage device.

Instructions

If you are confident that you know what you are doing, here are the quick instructions.

If you are at all unsure, please move down to ‘Step 1: Create the Reflashing Device’ for more detailed steps.

The quick version is:

  1. Download the Reflash System from the link above and write it to a USB device of at least 1GB capacity.
  2. Mount the USB device on your system; you should see a volume named rfl-boot.
  3. On the rfl-boot volume there is a directory named reflash.
  4. Download the operating system image you would like to write, along with its MD5 file.
  5. Copy both the compressed .img.gz file and its .img.gz.md5 counterpart into the reflash directory.
  6. Eject the USB device.
  7. Power off your OpenFrame and insert the USB stick into the USB socket.
  8. Power on your OpenFrame and watch.

If your OpenFrame fails to boot or shows odd errors, try another USB device.

Step 1: Create the Reflash Device

Download the latest version of the Reflashing System from the link above and then follow the instructions for the operating system you are using. Note: Some browsers think they’re being very helpful by automatically decompressing files when you download them, but that’s not always what we want to happen. You may need to rescue the original .img.gz file from your Trash or Recycle Bin after the download has completed.

Linux

Open a Terminal window and run sudo fdisk -l to find your target device name. Then:

sudo umount /dev/sdX*
gzip -dc reflash111_of.img.gz | sudo dd of=/dev/sdX bs=1M

Where sdX is your target USB device. Once complete, disconnect and reconnect the USB device to have it mounted correctly.

Mac OS X

Open a Terminal window and run sudo diskutil list to find your device name. Then:

sudo umount -f /dev/diskX*
gzip -dc reflash111_of.img.gz | sudo dd of=/dev/rdiskX bs=1m

Where diskX is your USB device. Once complete, disconnect and reconnect the USB device to have it mounted correctly.

Windows

Download Win32DiskImager, then unpack the .img.gz file using a tool like 7-zip. Run W32DiskImager.exe and select the unpacked .img file. Choose the drive that corresponds to your USB stick and use ‘Write’ to write the image.

As with the other operating systems, you will likely then need to disconnect and reconnect the USB device to have it mounted correctly.

Step 2: Add the Firmware Image

Once mounted on your computer, there should be a volume named rfl-boot available. Take a look on this volume and you will find a directory named reflash. This is where the image files must be copied for them to be written to the OpenFrame internal memory.

There are additional files on the rfl-boot volume which are used by the system for booting. Please leave these as they are.

To flash an operating system to the OpenFrame’s internal memory, you will need that operating system’s compressed image file in .img.gz format and an accompanying .img.gz.md5 file, containing the checksum. Below is a link to the most recent operating system by OpenPeak, in case that’s what you’re after.




Copy both the .img.gz and .img.gz.md5 files to the reflash directory on rfl-boot.

Step 3: Boot the OpenFrame

Make sure the OpenFrame device is powered down, then connect the USB device to the socket. The OpenFrame should display its boot logo before changing to:

Booting ‘OpenFrame Reflash System v1.11’

After a few moments the screen will walk you through the automated process.

EFI Firmware

In the latest version, I’ve added the ability for the Reflash System to reprogram an OpenFrame’s EFI chip.

This is dangerous.

The EFI data, equivalent to a BIOS, is held on a 1MB capacity chip and should not be confused with the usual 1GB (or 2GB) internal storage. It’s accessed via the Intel Firmware Hub, which appears as /dev/fh on the system. On the OpenFrame 1 or Joggler, if you overwrite the data with something that doesn’t work, you’ll have a brick that will need to be dismantled so that you can replace the EFI chip with one that works. Reflash the OpenFrame 2 with a broken EFI and you will just have a brick, unless you are very handy with a soldering iron.

Reflashing the EFI

If your OpenFrame can boot the Reflash System, there’s almost certainly no need for you to do this. You need to know your reasons before attempting it and realise that if it goes wrong, you’ll have to find your way through it manually. Very likely with a screwdriver.

The Reflash System will only write files to the EFI chip which are properly named and accompanied by an MD5 checksum. As with the standard internal memory images, the EFI firmware image and its checksum should be placed in the reflash directory of rfl-boot and be the only files in that location. The firmware image should be a .img file and not be compressed.

The naming convention is <ofdevice>_efi_<identifyingname>.img so for the default O2 EFI on a Joggler, it would be of1_efi_o2.img.

The system will not flash a file beginning with ‘of1’ to a OpenFrame 2 or vice-versa.

How Does It Work?

The Reflashing System is a version of Ubuntu Trusty (14.04.1) built with debootstrap and running a mildly patched kernel.

On startup a script is triggered, which checks the contents of the reflash directory on rfl-boot and takes appropriate action. Image files are checked against the provided .md5 checksum to ensure it is intact. If this passes inspection, dd is used to write it directly to the internal storage.

Hopefully everything goes fine and the OpenFrame will shut down, ready for you to disconnect the USB device and power it back up. If things go awry, the system will hopefully be able to suggest a resolution. It’s basically a big wrapper for the dd command. ;)

Troubleshooting

If everything doesn’t go fine, here are the common faults:

“The reflash system doesn’t boot properly.”

So long as you see a boot logo on screen when you turn on the Joggler, it’s likely that you just need to use a different memory stick. There is a fair degree of variability on what works and what doesn’t, so trial and error is the best approach until you have found a memory stick that works for you.

If you’ve tried a couple of alternative USB sticks and the OpenFrame still won’t boot (but displays a boot logo) you can try telling it explicitly where to boot from. This can only be done using a USB keyboard and hub.

  1. Attach a keyboard and your memory stick to the Joggler through a USB hub.
  2. Turn on your Joggler and immediately begin pressing ESCAPE repeatedly for around 10 seconds.
  3. Type fs0: and press RETURN. You won’t see any text on screen.
  4. Type boot.nsh and press RETURN.

With luck, the Reflash System should fire up. If nothing happens, try again. If nothing continues to happen, try fs1: or fs2: etc. You may need to power off between attempts. Alternatively, try swapping around the order of devices on your USB hub or try another hub.

If you see no boot logo when powering on, you may have a fault with your EFI chip. There’s no fixing this without having a second working Joggler and nerves of steel. You will need to read ‘Recovering a Bricked EFI on the wiki.

“It seemed to work, but I’m still stuck on the boot screen!”

Interestingly, there are some Jogglers that will store the image perfectly, but still refuse to boot from their internal flash memory. Why this should happen is still a mystery, but if you have any insight, please let me know!

In the meantime, it might be worth looking at some of the other operating systems you can run on your Joggler, as a fix for this particular issue has not yet been found.

“It’s worked, but now it keeps trying to install an update and never stops rebooting!”

This happens on some Jogglers because of a response from OpenPeak’s servers when they look for updates. Why it happens on some and not on others is a bit of a mystery. However, there is an easy fix; with the kind donation of a misbehaving Joggler by Mr_Dave on the Joggler Forum, I have been able to create an update disabler (and re-enabler). Pop the files on a USB stick and allow the Joggler to reboot one more time.

“I can’t use SSH on my OpenFrame after reflashing.”

Depending on the image you have written, your OpenFrame could be in a totally factory-fresh state, so SSH may not be active. I created an SSH and SCP enabler which will get things working again.


I have followed these instructions but my Joggler is currently displaying ‘Stalling for network…’ and has been for some time. Any ideas?

Ashley Giles left this message 2237 days ago

Thank you very, very much for this. A bricked Joggler from eBay and I used your reflash and up it came. I couldn’t do it with the wired connection although it worked flawlessly when I copied the image file into the image directory.
One happy person. Thank you. Louis

lou1z left this message 2237 days ago

Ashley, I had the same issue. Simply copy the downloaded Joggler image into the image directory on the USB stick you are using to reflash. It takes about 5 mins and you will be back up and running with the original software.

lou1z left this message 2237 days ago

@lou1x Fantastic! First Joggler saved! :) Did you buy one of the ‘spares or repairs’ ones I’ve seen on there recently? I’ve been tempted to get another for testing…

@Ashley I’ve replied to your message on the forum.

Andy left this message 2236 days ago

I got it off eBay advertised as it wouldn’t boot the native OS but I wasn’t that bothered as I wanted it to run squeezeplay as I have another 5 devices in the home. I tried JoliOS which was OK but you needed a mouse etc for it so I looked around to see if I could get the native OS up and running and here I am. There’s not a lot of places about that do this so your blog is very valuable.
I actually like the native OS as it’s easier to use without a mouse. Now that I can get squeezeplay on it, I might just stick with the original. It’s a pity it doesn’t show photo’s, video’s etc of network drives rather that just the USB. I think I’m going to sit this in one of my bedrooms with some audio engine powered speakers and try to use it as as squeezebox, alarm clock and picture frame etc so I may consider another one if it all works out.

lou1z left this message 2236 days ago

Thanks very much for this. My Joggler is back in the land of the living. I had tried so many other solutions all of which had failed. Yours worked first time. Well second time. The first time the screen went black and I assumed it must have finished so I removed the USB and a sort of screen dump crash report came up. I think it must have just gone black like a screen saver. If I had left it a bit longer it would probably have worked. Second attempt I used a USB hub with a keyboard attached and occasionally pressed a key. Don’t know if that was coincidence but the display stayed on throughout the reflash and all went perfectly.

Mike left this message 2235 days ago

@Mike Great stuff – glad to hear another one is back to life! Yes, the display does timeout after a while, although I’ve never had that happen on my test units. I should add that to the troubleshooting section.

@lou1z Thanks for the info. Your plan sounds good, hope it goes well!

Andy left this message 2235 days ago

Hi, good stuff, and nice website!
Have you ever tried to make ZoneMinder or such kind of webcam server working on Joggler ?

Lynx left this message 2233 days ago

Excellent work. Just used this on 2 Jogglers – 1 just to clean up and the other I’ve never been able to boot into the stock OS, I’ve tried various other restoration methods without avail, this worked flawlessly, nice one, thanks.

Liam left this message 2233 days ago

@Lynx Thanks very much! :) As for ZoneMinder, I’d not heard of it before, but it looks like a nice system. If you grabbed a copy of Ubuntu for Joggler (check the forum – all the info is there) then you should be able to install and run it.

@Liam Superb – it’s great to hear! I don’t suppose either of your Jogglers boot with the OpenPeak logo, do they? I’m yet to hear from someone using one of those models and would be very keen to know that it works.

Andy left this message 2231 days ago

I am also getting Stalling for network, and I have both the image file in the image folder and a wired connection, any suggestions?

Psionguy left this message 2229 days ago

Thanks for the O2 Joggler fix.
I bricked my O2 Joggler months ago, turning it off while it was playing Audio, and couldn’t be arsed to send it back to O2, knowing it was just a file corruption problem.

Just tried it, and rebooted.
Waited a few minutes, O2 Logo, waited a few more minutes, black screen, and then finally…. An O2 user details home screen :)

You are an absolute STAR!!!!!!

Jay left this message 2229 days ago

Help! Reflash 1.03 worked great on 3 jogglers (with up-to-date fware), but only if image put on usb (not from net). BUT TIME DOES NOT SET! On 1st reboot,
Jogglers request 1st page of registration – but not things like “name or joggler”…
They all now work fine BUT time does not get set – very frustrating!
An unflashed joggler will prevent the command “ntpdate uk.pool.ntp.org” from native linux because “ntp in use”, but a flashed one allows this. So maybe other things are not running after flashing as well as time. I believe it’s connected to incomplete initial registration.
Please help

weeblies left this message 2229 days ago

@Psionguy Try a different memory stick – it sounds like there’s a problem with the reimage file you downloaded, otherwise it wouldn’t be waiting for a network connection. If that doesn’t work, please ask on the forum.

@Jay Hooray! :)

@weeblies Interesting. I shall investigate.

Andy left this message 2228 days ago

The issue with NTP has now been resolved in v1.04. Instructions for updating the flashing system are included above.

For those that have already reflashed, instructions will be appearing in the article tomorrow.

EDIT: Instructions are in the Troubleshooting section now!

Andy left this message 2227 days ago

Hi,

I have 3 Jogglers. 2 of them are running Squeezeplay perfectly. I can’t enable telnet access on the third because none of the USB ports work. I have also tried the 2 additional internal ports available on the PCB, but I still can’t get it to boot the stick. I know the stick is fine because it works on my other Jogglers.

This is really annoying because everything else (not wi-fi) works fine.
So is there another way to activate telnet?

I was thinking there might be a way to use the update program in the OS to get it to download and execute a custom script. If I run a wireshark session I should see the URL and filename it tries to download during the update. Once this is found I would only need to add this domain to my local DNS server and point it to a local web server containing the custom script.

I think this should work, but I don’t have a clue about how the Joggler updates work.

Does anyone know how this works?

Many thanks

Adam left this message 2207 days ago

Many thanks for all the info.
Suddenly stopped working (suspect power spike) 30 minutes later all good again.
Kept waiting for the network connection despite having the image in the reflash folder.
Copied the filename from the script and renamed image.

Once again many thanks for the clear and concise instructions.

Kipper left this message 2207 days ago

you are the man! After 2 hours of trawling the net, stumbled across these perfect instructions, has recovered my o2 branded joggler to its original state – thank you

MT left this message 2205 days ago

I think some of the correspondents above may have had the same problem I had. Download the image that goes in the reflash directory using firefox, Explorer changes the file and the script doesnt see it, renames from tgz to gz extension. Firefox leaves as is. I had the “stalling” problem until I did that.

edupit left this message 2203 days ago

Wow this is brilliant – my joggler died a few days ago after a power cut and wouldn’t boot up beyond 02 screen. I found this webpage and now its all working again. Only problem I had was my joggler couldn’t find network, so I installed the openpeak flash onto the USB drive, then it still wouldn’t work. Reading through the thread I soon realised my browser had changed the .tgz file to .gz – I put it right and its now running perfectly and all setup with apps as I had it before – Thank You….

Brian left this message 2203 days ago

Just reflashing again…. ! I tried to install the new Iplayer update from Spoyser in the forums, but after modifying the applications.xml file (correctly I think as I didn’t omit the slash and cat applications.xmil looks OK) all of the icons disappeared. I had squeezeplayer installed however, so just going to try Iplayer again on it’s own before installing squeezeplayer, and I will leave the USB stick reflashed so I can get back into the stock image straight away if it all goes pear shaped.

edupit left this message 2201 days ago

Thanks for the messages, everyone – great to hear this is still helping people out.

@Adam That’s a question for the forum. Ask again there and I’m sure help will be on it’s way.

Andy left this message 2199 days ago

Hi Andy,

Thanks for your reply, I will ask on the forum.

Adam left this message 2198 days ago

just reflashed without a hitch and the joggler powered up without a problem.

A BIG problem is that I can’t find how to set my wireless connection. When I check in “Settings” I only see “Wired”…..

Any suggestions?

Thanks

brian left this message 2190 days ago

@brian Settings > Network > Edit > Connect Wirelessly

Andy left this message 2186 days ago

Thank you roobarb and thank you Bejeezus; my joggler was knobbled by a power cut ages ago and I couldn’t get anything to boot properly till I found this site. But alas still no joy, tried different sticks and a powered hub no no avail. Eventually stumbled on a post on the forum that used 2 sticks and bizarrely it worked first time. No idea why but hey….

Simon left this message 2184 days ago

Thank you so much! Managed to corrupt the 2nd or 3rd partition of the flash by mapping them to the android SD card and formatting. It wouldn’t boot past the O2 screen, even when following your instructions with the special USB image.
However, I found another forum post which worked for me – stick tghe USB key into the first port of a hub and a keyboard into the second. For me the hub had to be unpowered even though it was capable of its own power supply. I then hit ESCAPE lots of times after powering on the joggler, then typed (blindly) “fs0:”<enter> and then “boot.nsh” <enter> This then got me booting into your recovery procedure. Hope this helps anyone with similar symptoms

Richard left this message 2182 days ago

Thank you, after days of grief this simple guide solved by bricked joggler. Much appreciated.

King Tubby left this message 2178 days ago

hi i bought a non working joggler which i think is dead.
there are 2 lights on the circuit board when plugged in a green one and a red one. i just dont see how it will boot to try the flash . i know the screen works as i tried it on one of my other jogglers..
just wondered what your view was. pity it cannot be plugged into a pc to flash n reimage
thx in advance for any good workable reply
cheers
peter

peter left this message 2176 days ago

@Simon, @Richard, @King Tubby Great to hear – thanks for letting me know!

@peter I recommend the Joggler Forum for that one.

Andy left this message 2172 days ago

Works perfectly, thank you very much.

Barry left this message 2156 days ago

One more time, you make a very great tool ;)
However, I’ve had to change extension of O2 image file on your script to work correctly (.gz)

Thanks ;)

ARJunior left this message 2148 days ago

You saved my Joggler! All worked perfectly on Win 7 ×64. (One note about Image Writer – I found that the .img source file needs to be in a root directory otherwise Image Writer gives an error when trying to write it to USB). Thanks for all the time and effort you’ve clearly put in.

Andrew left this message 2139 days ago

Thanks, worked fine over network to recover a friends Joggler. Will use it later to ‘factory fresh’ one of mine that gets hacked a lot.

One odd thing, when I tried to download the image file with my PC (Win XP /IE8) I ended up with a ‘.gz’ file but the same URL fetched a ‘.tgz’ file using wget on my linux box. Then tried Chrome on XP and it got the ‘.tgz’ file, so did a bit of googling and apparently this is a common problem with IE. You may wish to add a comment in the PC section.

Mark Leman left this message 2136 days ago

@Mark Leman Thanks for the information regarding that download issue – I’ll definitely add that to the instructions.

@everyone Thanks for the success reports!

Andy left this message 2135 days ago

Hi everyone, I bricked my Joggler trying to get it to do a manual update as it wouldnt do one on its own (its a replacement from O2 for one that failed).
I followed the instructions above but when I reboot and get the message “Booting Ubuntu Server (10.04.2 LTS) – 2.6.37.3joggler2” I immediately get the message “Error : no such partition” and a second error “Error : you need to load the kernel first”
Any ideas?

Penfold left this message 2125 days ago

Sorted, I shouldnt be so hasty.
Tried a different USB drive and my restore worked fine.
I now have a fully restored and updated Joggler.
Thanks for a fantastically easy solution.

Penfold left this message 2125 days ago

@Penfold Good stuff – the errors generated when a USB stick isn’t up to the task are quite variable. Glad you got it working.

Andy left this message 2121 days ago

Hi,I always failed to reflash my joggler, see the video here http://www.youtube.com/watch?v=5kzPEHkX7C4 , and here’s the picture: http://farm7.static.flickr.com/6079/6141962491_1960744dbe_z.jpg ,don’t know why,can you help?

Lynx left this message 2116 days ago

And now I run Vanilla Ubuntu Server with an Open SSH server on a external USB disk for my joggler,could you please connect to my joggler to see what’s wrong with it,when you got some free time,thank you :-)

Lynx left this message 2115 days ago

hi, i’ve got 2 jogglers, one of which was hacked fine, my 2nd is stuck on the o2 logo. having looked at the instructions to reflash i’m confused as to where to find jogglerflash.img.gz ?? i appear to be the only one who cant get past this basic of instructions. thanks !

w1ndrush left this message 2109 days ago

When you write copy the files to the “reflash” folder, I take it you mean on linux-root partition and not linux-boot? It’s confusing that “reflash” folders exist on both partitions

Alasdair left this message 2109 days ago

@Lynx Ooh, dear. That looks to me like the internal memory may have passed away. What happens in that last stage is that the reflash system tries to mount one of the newly restored partitions and use a utility to clear the NVRAM settings. The mount command is failing to identify the filesystem type on the partition, which means it is probably corrupt.

Does the reflash tool attempt to recreate the partition information every time it is run? If not, try editing line 124 of jogglerreflash.sh (v1.06) to read:

mount -o ro /dev/mmcblk0p3 /mnt

Then try it again. Good luck!

@w1ndrush Perhaps you are the only one following the instructions properly! That is my mistake – jogglerflash.img.gz was replaced by ubuntuserverlucid.img.gz some time ago. I have updated the instructions.

@Alasdair Nope, I mean linux-boot. The ext2 filesystem doesn’t (ordinarily) mount under Windows, so those users don’t see the other reflash directory. I will update the instructions.

Andy left this message 2109 days ago

I have tried it on my openpeak version.

Works perfectly UNTIL i connect to network and it loops through:

All updates have been successfully downloaded. System will be rebooted in a few seconds

Until I remove network.

Arm5 left this message 2096 days ago

This means I cant use the network and if i enable telnet to ftp into it it’ll reboot straight away any way before I can even access it ;(

Arm5 left this message 2096 days ago

@Arm5 This has been seen before, but to the best of my knowledge we’ve never entirely got to the bottom of it. I’ve never managed to provoke a Joggler into producing this reboot loop, so it’s been impossible for me to experiment.

Take a look on the forums and ask around in there – perhaps we can get to the bottom of it this time.

Andy left this message 2096 days ago

I’ve used this tool twice on other jogglers with tremendous success. Thanks.
The third one I tried was one previously stuck on the O2 logo at boot. The tool reflashes the joggler fine, prompts for reboot. But then on boot up gets stuck on O2 logo and makes no further progress.

Tried a variety of keys – which I know have worked in the past. Any ideas?

phander left this message 2095 days ago

Ignore the above. Tried one more USB key and it went through perfectly…
Thanks very much again. This has really been a very useful tool for me.

phander left this message 2094 days ago

Excellent write up, I now have my Joggler working agian, thanks!

Ricky302 left this message 2089 days ago

When my Joggler ‘died’ and just showed the O2 logo, I did some Googling and feared it was most likely the EFI chip issue. As I don’t know anyone else with a Joggler and I can’t afford to get another one, I guessed that was that.
Then I found your site and having just followed the instructions, I’m pleased to say my Joggler is revived and once again has pride of place on the shelf.
Thanks so much for these instructions and your wonderful script.

Masher left this message 2084 days ago

@Masher Excellent – always happy to hear of success! :)

Andy left this message 2073 days ago

Updated the system and reflash script; it should more reliably connect over ethernet now. Given the article a bump back on to the home page too. :)

Andy left this message 2070 days ago

just about to try reflashing but not really sure that it will solve my problem – recently my Joggler (openpeak tango) has started having screen problems – the screen just goes black every couple of seconds – as soon as I touch it it comes back to life and everything seems to be working – take my finger off and it goes blank again – do you think the reflash will help?

Susan McInnes left this message 2070 days ago

That’s interesting – it does sound like a software issue to me, as there’s nothing I can think of in hardware that would cause a problem like that (except for a bad internal connection).

Does it only turn the screen back on when you touch the image part of the screen? For example, it doesn’t come back when you touch or squeeze the black sides? The first points to software, the second to hardware. If it’s hardware it shouldn’t be a complicated repair; if it’s software, give this reflash tool a try.

Andy left this message 2070 days ago

Went for it and used your tool and it is miraculous (sp?) My Joggler is just like new now so can start to play around with it. It has been on for a while now and the screen has remained lit. It was going off both on wired and wireless settings but instantly on as soon as screen was touched. Anyway thank you so much for your Reflashing tool – and comprehensive instructions.

Susan McInnes left this message 2069 days ago

@Susan McInnes Fantastic! :)

Andy left this message 2069 days ago

For all those who bumped into the problem of your Joggler constantly trying to apply an update and rebooting, this is the fix for you. Instructions are in the README file. :)

Andy left this message 2050 days ago

Openpeak model of the joggler. (supplied by o2)
Stuck at openpeak logo, tried the procedure, nothing.
Tried again with keyboard, got to the yellow text but after 4 hours no further, and subsequently cannot get past openpeak logo no matter what I do.
Gonna try a 3rd usb stick tomorrow but then bin for the joggler!!

Gazhay left this message 2044 days ago

update – different keyboard, usb stick, booted to yellow text, 2 minutes later began the reflash process.

Now have a fully restored joggler PLUS my touchscreen was always really bad, it had dead spots on it, these are now gone!

Thank you so much for this tool

Gazhay left this message 2043 days ago

@Gazhay Phew – don’t like to hear of a Joggler in peril. Glad it worked! :)

Andy left this message 2043 days ago

Many thanks for the rescue. Exactly as prescribed. So many failures and now working again. Now I shall probably go on and try and mess it up again.

Gerry left this message 2039 days ago

Just flashed my Joggler that died after a power cut. All working well now, thanks so much,

Mike

Mike left this message 2028 days ago

Can people recommend a USB stick that they have restored with successfully. I have tried 3 USB sticks – 2 of them reflash the Joggler but upon reboot the Jogglers just get stuck at the logo

Dave left this message 2017 days ago

Andy, thanks very much for this. :) My brother-in-law’s Joggler stopped working one day and so I thought this was worth a try and it worked perfectly. First time didn’t work but I tried another USB stick and it was fine.

@Dave – I first tried an 8GB Dane-Elec which failed with the ‘no such partition’ error. I then tried a 4GB Integral which worked fine. I would have thought the Dane-Elec to be a superior stick but maybe that doesn’t have any bearing in this scenario.

Cricky left this message 2009 days ago

Came downstairs Saturday to find my Joggler stuck on O2 screen. Found this guide and tried to reflash the Joggler with a 2GB SanDisk but it failed. Tried again with an Integral 1GB USB drive and it worked first time. You are a star, many thanks for the tool and guide. Happy to have my Joggler back.

richard p left this message 1982 days ago

It worked!!! Had the ‘White Screen of Death’ first – cured that by heating up the screen to ambient + 4deg C……result! Tried your reflash – didn’t work…. tried WindowsXP off a stick – that worked…..went back to your reflash and lo! it worked and I’ve got my Joggler back!!!! Thanks for your efforts…..there’s a pint at the pub with your name on it!!! ;) EJ

EJ-Joggler left this message 1973 days ago

Having problems getting this tool to work on my Joggler. I insert USB to Joggler and boot up. O2 screen shows for few seconds before the Ubuntu screen kicks in. Semms to start to do what it’s supposed to do, but then the Joggler screen goes off part way through & Joggler shuts down. The only way to get it back is to reboot. Have tried the keyboard method and different USB drives. Littled stumped.

Joggler User left this message 1965 days ago

@Joggler User That sounds odd. Is the Joggler really shutting down (do you get shutdown messages on the screen), or is it just the screensaver kicking in. It shouldn’t be (I’m pretty sure it’s disabled), but worth an ask.

The best way to diagnose is if you could make a quick video of the issue and post it somewhere, unless you can make note of any error messages that appear.

Andy left this message 1965 days ago

No shutdown messages. Seems to do everything ok until the ‘waiting to settle’ screen. Then starts to load/unzips the files with a list starting to scroll down the screen but within a few seconds, powers off completely. No lights flashing on the USB drive etc. Have done this few times, sometimes leaving the Joggler alone to stand in this condition overnight. Just to mention, I can get XP to work on the Joggler without any problems.

Joggler User left this message 1965 days ago

@Joggler User What size memory stick are you using, and have you tried any others? It sounds like it’s having problems decompressing the files, because other than the information it gives when the data is being written, there shouldn’t be a file-list scrolling down the screen.

If you have any more issues, please post on the Joggler Forum because this comment list is getting a little oversized!

Andy left this message 1965 days ago

For further discussion, please use the Reflash System thread on the Joggler Forum.