Help trying boot new adnriod image and I just get the o2 sig

[kaiserc]

Hello everyone, I bought one of these last year and put ubuntu on a usb stick and play around with it for a while before I got bored. Also I noticed that after a while it only worked with the usb bootable ubuntu.
But now that android is up and working on the joggler i thought I would give it a go.

I followed the instructions from nigelh form this thread "new Android 2.2.2 Mijuu Build 1.2.3 ** TESTING PHASE **"

"This is the way I did it and it works fine. (even on a 2gb usb stick)

download the 1.2.3 joggler and package from http://www.mporting.com/download/
FAT format a usb stick
extract the contents of Froyo_Joggler_2.2.2_v1.2.3.zip to the usb stick,
extract the contents of Easy_to_use_package_Usbdisk_1.2.3.zip to the usb stick (overwriting any existing files)

You then have the bootable image. You will still have to manually install the google apps as per instructions."

All that happens is that I place th usb in to the Joggler and boot it . It just flickers on and then goes stright to the O2 sign.
I am using a 8gb usb stick and formatted it to be FAT32
Is there something I'm missing. is there a way to get the joggler back to normal and may be a clearer guide on how to do this.

Any help Or pointers guys.

Cheers
K

[kaiserc]

Can you guys also Advise me on how to section the usb space so that I can use some for apps & data, and some for the os

regards
k

[jp_hero]

Does you Joggler not boot into the stock os anymore?
Can you still boot into Ubuntu on your other usb stick?

If its two no's it sounds like the EFI System might be broken. If you can't boot into the stock OS I would try and restore that first and then worry about booting into Android.

This thread http://www.jogglerwiki.com/forum/viewto ... ?f=2&t=120 gives you info on restoring the stock OS.

As regards booting Android, do you have a bigger stick? Ideally one about 4gb then you can apply the 4gb image to the stick.

[photize]

Make sure your fat32 was primary and not logical can cause this error