Reflashing Tool for the O2 Joggler

Post by **roobarb!** » Sat Mar 03, 2012 12:53 pm

Juggler wrote:So If I reflashed the Joggler would I be offered the ability to get an O2 account, mobile number and free SMS ?

The SMS mobile number you are allocated is associated with the MAC address of the Joggler. Reflashing won't change that, so when the software has been restored, it connects to O2 and checks whether the Joggler's MAC address is linked to a number at their end.

The long and short of it is that a Joggler's mobile number is for life. I suppose, if they do time-out accounts, it might be possible to leave a Joggler disconnected from the internet until that time-out occurs, at which point it may associate a new number with the device. However, we have no idea if that time-out actually occurs, so you could be waiting for a very long time!

Juggler · Post by **Juggler** » Sun Mar 04, 2012 6:29 pm

Thanks roobarb! for your reply.

The guy I bought the Joggler off I'm pretty sure had it from new. I don't think he modified the stock os. I haven't used the stock os - well I did power it up when I bought it, something like Nov 2010, and it may have been connected to the net at the time. But I haven't been into the messaging application in the stock os, as far as I can recall.

As the O2 SMS number is dependent upon the MAC Id of the Joggler, I'm wondering if there is a logon to the messaging app, where whoever set it up would need to enter the password ? If this is so and O2 have kept the previous owners SMS account alive, then I may have problems. I'm asking the question now, as I don't want to try using the messaging app and mess my chances of getting this feature by locking the account or something similar.

Sorry this question is slightly off this topic, but I thought it was a feature that may become available again after reflashing the joggler.

TIA

PS - the O2 Joggler service terms and conditions are here :

http://www.o2.co.uk/termsandconditions/o2family

The section detailing messaging and non use of the messaging service is under the heading - "O2 Joggler Messaging Service terms and conditions"

The section regarding termination states :

4. Termination of Services

4.1 O2 reserves the right to suspend or terminate your access to the Service in accordance with the WAP and Web terms.
4.2 O2 can delete your account on the Services if your account is deemed inactive. A messaging account for an O2 Joggler is deemed inactive where the Joggler has not sent or received a message in the previous 6-month period.
4.3 O2 reserves the right to alter this definition of "inactive" from time to time. O2 may also, in its sole discretion, 'recycle' phone numbers (i.e. re-allocate a number which has previously been used on the O2 network) and delete accounts for the Services associated with such number.
4.4 O2 accepts no liability for the loss of data stored on the Services.

cbredfred · Post by **cbredfred** » Sun Mar 11, 2012 5:27 pm

Yesterday I was tinkering with my 2 Jogglers that the reflash tool fails to resurrect, trying to get them to boot as offbeatdave did in this thread:

http://www.jogglerwiki.com/forum/viewto ... ?f=2&t=472

So I went through several cycles of deliberately screwing up the partitions using fdisk and gparted from Xbuntu and then letting the reflash tool sort them back out and do it's thing.
After several time through my reflash USB stick fail to boot up so I used a hub and keyboard to tell it where to boot from as outlined here:

“The reflash system doesn’t boot properly.”

So long as you see a boot logo (O2 or OpenPeak) on screen when you turn on the Joggler, it’s likely that you just need to use a different memory stick. Most (but not all) will boot the Joggler, but then it’s important that the stick be robust and of good quality, otherwise the process will fail later on.

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

Attach a keyboard and your memory stick to the Joggler through a USB hub. Powered hubs are best, but you may have success if your keyboard has a built-in hub.
Turn on your Joggler and immediately begin pressing ESCAPE repeatedly for around 10 seconds.
Type fs0: and press RETURN. You won’t see any text on screen.
Type boot.nsh and press RETURN.
With luck, the reflashing system should fire up. If nothing happens, try again. If nothing continues to happen, try fs1:, 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.

From http://birdslikewires.co.uk/articles/jogglerflash

So my question is, what in the Joggler gets confused about where to boot from all of a sudden?
It seems to me that there is nothing wrong with the 1GB internal flash memory and it's contents.
People have tested it, reflash it, compared it, all with no indication that there is anything wrong with it.
So what if it's that the Joggler "forgets" where it's supposed to boot from internally just like it seems to randomly do with the external boot devices?
Is there a way to tell whichever bit of software whose attention we've gotten by pressing the escape key, lets call that software "Flibble", which internal boot device to use?
Maybe we Escape until we've got Flibble's attention and then type "sda:" ENTER "boot.nsh" ENTER. or "sdb:" or "sdc:".
Or is there no difference between internal and external boot device designations?
Also, if we only have the EFI chip, which we have ruled out, and the 1GB flash chip, where is Flibble storing the "which device to boot from" information?
After using the keyboard to tell Flibble where to boot from, away goes the reflash tool doing it's thing, then the reboot, then half an hour of looking at the O2 logo, then switch off, then connect the reflash USB stick in to the side USB port and BOOM it can find and boot the reflash USB stick without being tool where to find it!!!

I know this is very rambling and might not make too much sense, but I hope someone understands what I'm trying to ask and can shed some light on the subject.

andyf · Post by **andyf** » Mon Mar 12, 2012 11:57 pm

I'm trying to reflash my joggler but I have a problem.

I create the USB stick ok, and it boots fine with the yellow text. It the goes to the white text, but most commands fail with errors of 'command not found'. It culminates in deleting the image file, but that appears to only happen because it couldn't execute awk and md5sum.

I've tried two USB sticks, a 1MB and a 2MB, and both fail in the same way.

Any ideas?

rahulg247 · Post by **rahulg247** » Sun Mar 25, 2012 7:26 pm

Hi I am trying this as I want to get my joggler back to stock but everytime I try it I get yellow text displaying the following:

Booting 'Ubuntu Lucid - 3.1.9joggler1'
[Linux-bzImage, setup=0x3600, size=0x3585d0]
Video mode: 800x480-32
Frame buffer base: 0x1fc00000
Video line length: 3200
[Initrd, addr=0x178f8000, size=0x49349c]

Does anyone know how to fix this?

Post by **roobarb!** » Sun Mar 25, 2012 10:50 pm

rahulg247 wrote:Does anyone know how to fix this?

You don't want to fix that. It is correct behaviour. If it hangs there, I'd try another USB stick if you haven't already.

rahulg247 · Post by **rahulg247** » Mon Mar 26, 2012 11:15 am

roobarb! wrote:
rahulg247 wrote:Does anyone know how to fix this?
You don't want to fix that. It is correct behaviour. If it hangs there, I'd try another USB stick if you haven't already.

Oh I didn't realise thank you for the reply.

It does hang after that and I've tried all the USB sticks I have guess I will have to buy some more.

jollyjoggler · Post by **jollyjoggler** » Sat Apr 07, 2012 1:07 pm

hello roobarb!,

thank you very much for providing us with your reflashing tool!

after reflashing the partition structure looks like this:

Disk /dev/mmcblk0: 1028 MB, 1028128768 bytes
4 heads, 16 sectors/track, 31376 cylinders, total 2008064 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 16 125055 62520 ef EFI (FAT-12/16/32)
/dev/mmcblk0p2 125056 625151 250048 83 Linux
/dev/mmcblk0p3 625152 1125247 250048 83 Linux
/dev/mmcblk0p4 1125248 2008063 441408 83 Linux

is it intended to be exactly like mine above?

thanks

Post by **roobarb!** » Sat Apr 07, 2012 9:22 pm

jollyjoggler wrote:is it intended to be exactly like mine above?

Looks good to me!

jollyjoggler · Post by **jollyjoggler** » Sun Apr 08, 2012 12:19 pm

roobarb! wrote:
jollyjoggler wrote:is it intended to be exactly like mine above?
Looks good to me!

thank you. i´m asking this because i was just wondering if it is intented that the mmcblk0p1 boot partition is starting at sector 16.

sectors 0-15 should be the master boot record then if I´m assuming right?

Post by **roobarb!** » Mon Apr 09, 2012 9:09 am

jollyjoggler wrote:
roobarb! wrote:
jollyjoggler wrote:is it intended to be exactly like mine above?
Looks good to me!
thank you. i´m asking this because i was just wondering if it is intented that the mmcblk0p1 boot partition is starting at sector 16.

sectors 0-15 should be the master boot record then if I´m assuming right?

The Joggler also uses these first few kilobytes to store it's NVRAM settings, so yes, it's normal in a Joggler running the native OS to have this space outside of a usual partition.

If you're erasing the internal flash and putting something else on it (and don't intend to use the NVRAM binary) then a 'normal' partitioning layout can be used.

DaveDodd · Post by **DaveDodd** » Wed Apr 25, 2012 1:20 pm

Hi guys, really need some help here.

I was using Gparted in Xubuntu to format the internal flash to fat32 so i could write ICS to the internal.

This went fine, however a few minutes later when i opened terminal...Xubuntu crashed on me.

Ever since then I only get the O2 boot logo and nothing else...reflashing tool doesn't do anything, using a keyboard and powered hub then pressing escape repeatedly does nothing...I can't even boot into Xubuntu from USB.

I don't know what else to try? Hopefully someone here can help.

Thanks,

Dave.

DaveDodd · Post by **DaveDodd** » Wed Apr 25, 2012 2:09 pm

OK, fingers crossed i think i've got it...after reading hawsey's post i began trying different combos of hubs, usb sticks and keyboards.

As a final attempted i grabbed a logitech keyboard from my workstation and presto...currently reflashing.

lol....bricking a device is such a horrible feeling...much thanks to the forum.

Dave.

Post by **hawsey** » Wed Apr 25, 2012 2:20 pm

Good luck Dave, you will get there ,I had such little faith in my abilities to unbrick mine I snapped up another Joggler for 35 pound off eBay, one destined for the bedroom one the kitchen.

Waiting for updates now then PNP3 before I update the stock os on them both

mdolan · Post by **mdolan** » Fri May 04, 2012 8:51 pm

Can anyone help me with this - I must be doing something obviously wrong.

I'm trying to use the offline flash method, but when I created the USB key with Win32DiskImager, it creates a partition structure with waaaaay to little free space to actually copy the img.tgz files into!

I've tried 3 different sticks from different manufacturers, but all seem to end up with the same setup. 1x FAT32 partition (too small freespace), 1 x unreadable partition from windows (I assume its one of the linux filesystems) and a massive amount of unallocated space.

I then tried to mod the jogglerflash.sh file to point at the img.tgz on a server but although it starts the download sequence it again runs out of space!

Suggestions...?

Cheers,
Mike

Post by **roobarb!** » Fri May 04, 2012 10:26 pm

mdolan wrote:I'm trying to use the offline flash method, but when I created the USB key with Win32DiskImager, it creates a partition structure with waaaaay to little free space to actually copy the img.tgz files into!

Files plural? There's only the one to put in there and I promise that it does fit! Can you double check you're downloading the right thing to copy on there?

mdolan · Post by **mdolan** » Sat May 05, 2012 9:40 am

Ah - sorry. I've tried multiple tgz files, but I know only to use one. All of them are fairly large (e.g the base restore image or the squeezeplay os).

When the original flasher image is written to the USB stick, the fat partition it creates only 88MB. Nowhere near enough space to actually store the reflash TGZ file.

e.g. I end up with 3 sections on the stick. 88MB FAT, 387 MB "Other", and the rest of the drive is unallocated!

Cheers,
Mike

hg144 · Post by **hg144** » Sat May 05, 2012 12:25 pm

I ran into similar problems last week when I tried out the reflashing tool and loading squeezeplay. I was using a windows xp laptop to write the images to a usb memory stick, and ended up like you with a stick showing a capacity of 88MB.

Following some links from google i found some software which enabled me to 'recover' the unused space on the memory stick - though this involved a complete re-formatting. The software is called Bootice and I found it at the following link:

http://www.pendriveapps.com/bootice-par ... ot-sector/

The link to download the software is not the large green one near the top of the page - it's hidden a little further after the screenshot. If anybody else knows other software that will do this, please post details here.

After using this tool I was able to restore my memory stick to it's full 1GB capacity.

Many thanlks to roobarb for the reflashing tool, and the work on squeezeplay and squeezeOS. Once the dust settles on this 'update', which so far has not happened on my joggler, I'm sure I'll be using the reflashing tool. (and donating of course)

mdolan · Post by **mdolan** » Sat May 05, 2012 3:51 pm

Thanks for the link, but I think I'm still being a bit silly as I can't see how that tool actually helps? I can blow away the partitions and recover the space, but I still can't see how to get past the 88MB boundary so that I can copy the TGZ on...?

Or have I misunderstood?

Cheers,
Mike

hg144 · Post by **hg144** » Sat May 05, 2012 5:21 pm

After writing the image to the usb key, I used copy and paste to copy the reflashing script and the tgz file to the reflash directory, and the end result was a usb key with a capacity of 87.8MB, of which 79.5MB is used and 8.28MB is free.

What happens when ytou try and copy the tgz file to the reflash directory?

O2 Joggler Forum