Messed up internal partitions - cannot reflash. FIXED!

[offbeatdave]

Well, it had to happen...

I have been messing around with internal partitions, installing OS to them for a little while. Up to now, I've always been able to reflash with the great little reflash tool when I've made a mistake.

However, having messed around with Android on the internal flash, resizing partitions etc. it won't let me reflash any more to have another go like it has always done up to now.

There is no joy from the USB when booting normally so I have to boot with a hub and keyboard (otherwise I'm stuck on the o2 screen) and do the Esc thing.

When I try fs0: boot.nsh it attempts to load Android (but the kernel is not present or something - oops) and stops and asks to retry. When I try fs1: boot.nsh it seeks Android and does the detecting Android......................... thing. I can boot into a USB Android install by popping it into the hub and doing fs1: boot.nsh, but none of my Ubuntu installs will let me. They too hang on the detecting Android........................................(with ever increasing numbers of ...) screen.

Is there an obvious thing I have missed to be able to reflash and carry on tinkering? I'm hoping the presence of my o2 logo is a sign that all is not lost. It's just not an issue I've had before!

Edit: Further to the above, it is not even detecting other USB sticks other than the Android one as the fs1: boot.nsh does the detecting android ... thing without the stick. Any thoughts on how to get it to recognise the reflash or Ubuntu sticks (they have always worked on this Joggler and are still working on others).

[offbeatdave]

Why do I never learn?! Every time I have an issue I mess around with it for an hour or so, given up, post on here, try again and resolve it!

This morning, having left the problem Joggler unplugged overnight, I plugged in the hub, keyboard and reflash stick, Escaped and tried fs3: boot.nsh and away it went!

I'm sure I tried fs0: up to fs9: last night with no success but it went first time this morning. Therefore the test Joggler will be all ready again for messing around with tonight!

[dwl99]

Boot into Ubuntu & open Terminal

cd /backup
sudo wget http://dl.dropbox.com/u/1107587/part_table
cat part_table | sudo sfdisk /dev/mmcblk0

This will restore your empty partitions which will let you restore your (hopefully) backed up partitions.

[roobarb!]

The reflash tool, if you can boot it, will detect if there are the wrong number of partitions on the internal flash and recreate them. If you have the right number of partitions (but they're in different proportions) it won't realise - but you can force a repartition by creating a file called 'repart' in the 'reflash' directory on the stick.

I'm thinking of changing this behaviour in future and just recreating all partitions by default.

[offbeatdave]

Thanks for the tips.

As I say, fortunately, I managed to get reflash going this morning (I set it to 'repart' too) viathe Esc, fs3: boot.nsh routine. Not sure why it needed fs3: when normally fs0: does the trick. I must really have messed it up last night and couldn't boot into anything other than Android off a stick!

Anyway, all is well in my tinkering world - for now!

EDIT: Oops. Went wrong again this evening with my re-partitioning! Struggled to get booted off USB again but fs3: grub worked this time! Hours of fun!