OpenFrame 2: Recover from 'Upgrade'

General discussion relating to the O2 Joggler, from the default O2 setup, to alternative operating systems and applications.
jover
Posts: 1
Joined: Wed May 21, 2014 8:24 pm

Re: OpenFrame 2: Recover from 'Upgrade'

Post by jover »

I acquired an OpenFrame 2 test device at work, it has Telio branding and the EFI is locked. I tried the usb flasher and EFI shell but it didn't work :(
Has there been progress in circumventing the locked down EFI?

It is a nice device, but i would like to run it as a squeezebox. Any tips would be welcome :)

regards,
Joost
User avatar
roobarb!
Posts: 1772
Joined: Sat Mar 05, 2011 1:30 pm
Location: Salford, UK
Contact:

Re: OpenFrame 2: Recover from 'Upgrade'

Post by roobarb! »

jover wrote:I acquired an OpenFrame 2 test device at work, it has Telio branding and the EFI is locked. I tried the usb flasher and EFI shell but it didn't work :(
Has there been progress in circumventing the locked down EFI?
Ooh, good luck. The only way I got mine unlocked was by a very nice person doing it 'officially'. Because the chip is soldered to the board on the OF2 (usually) it's no straight forward deal. :(

Perhaps have a word with pete on here - he's the guru at opening up the OF2, then you'll be able to see what the deal is with the chip.
BirdsLikeWires - Get fresh builds of Debian Bullseye, Bookworm, and Trixie for OpenFrame with the latest 5.10, 6.1, and 6.12 kernels! 8-)
User avatar
pete
Posts: 2962
Joined: Mon Aug 01, 2011 6:33 am
Location: Time Traveler

Re: OpenFrame 2: Recover from 'Upgrade'

Post by pete »

Yeah; that whole "chip soldered on the board of the OF2" is a "debbie downer".

I have learned to open up the OF2 physically. Its nice to see the board.

That said I do have one OF2 labeled with marker "Joggler" and it looks like some sort of test motherboard as much of the pieces are missing; but the boot chip is socketed into place. The rest of the OF2's have them soldered in place.

What is sort of neato (but not really neato) is that the OF2's are made never to break and always find the mothership and fix themselves; that is if the mothership is there and if you have a network connection. Fixing themselves though doesn't make it more user friendy or easier to modify.
I tried the usb flasher and EFI shell but it didn't work :(
It never used to work for me with any USB keyboard; until one time I hit that magical timing sequence of taps; it worked!

My only suggestion in this situation is try try again the "blind" typing to interrupt the EFI boot process. Way long time ago I could never get it to work with the variety of USB keyboards I had. One day I found out it was just relating to my timing of when I did the "blind" typing; then it worked for me.
Blind typing and an Openpeak recovery (well more related to the Joggler but it could work with the OF2).

1 - Don't Panic
2 - Attach keyboard and known good usb stick, and apply power to the Openpeak device
3 - Press escape frantically (oh yes just like the good ol' days)
4 - Once the num-lock key has lit, press escape a few more times. The process has worked if the numlock/caps lock key switches on and off when you press the appropriate key.
5 - type the following: fs1:boot and press enter. You are typing blind thanks to the Openpeak boot screen.
6 - If it doesn't boot the USB stick repeat the whole process.
7 - It it doesn't work repeat the whole process but type fs0:boot and press enter.
The above is a bit modified from here:

http://www.jwarburton.com/projects/joggler
- Pete
O2 Jogglers running EFI Ubuntu / Squeezeplayer
OpenPeak Voip Telephony / Zigbee tabletops hardware modded with Seabios / RTC / Ethernet ROM edits / SSD drives running XPe for automation screens

Auto mater
Post Reply