Popping-in?

Our studio is filled with light and music.
There are multiple meeting rooms, a well stocked kitchen, and an indoor garden (with fishpond). Talk to us about access needs, environmental factors and any accommodations we might make to enhance your visit. Pop-in for tea and stay to use a spare desk for as long as you need.

11 Greenwich Centre Business Park,
53 Norman Road, Greenwich
London SE10 9QF

[email protected]

Public transport

We’re next to Greenwich train and DLR station. We have a door right on the concourse but it’s different to our postal address. Find us via: what3words.com/hungry.means.author

From Greenwich rail platform

This video shows the route to take from the train that will arrive at Greenwich rail station from London Bridge. There's a gentle slope next to the staircase.

From Greenwich DLR station

This video shows the route to take from the DLR that will arrive at Greenwich DLR station from Bank. There's a lift at the platform level if that's useful.

By car

If you have to come by car, we have a couple of parking spaces. We have a charging point that you are welcome to use if you have an electric car. Call ahead and we'll make sure the spaces are free. Use our postcode (SE10 9QF) to guide you in.

Get in touch

We’d love to hear from you. Use whichever medium works best for you.

11 Greenwich Centre Business Park,
53 Norman Road, Greenwich
London SE10 9QF

[email protected]

New project enquiry

It's exciting to chat about potential new projects. We don't have a ‘sales’ team or a form to fill in. Call us or give us a little detail via email and we'll get straight back to you.

[email protected]

Website support

If you're a client then you'll be best served by calling us or contacting us via ClickUp, otherwise you can use this dedicated email that reaches all of the digital team.

[email protected]

Finance questions

This email hits the inboxes of the people who deal with our bookkeeping and finances.

[email protected]

Just want a chat?

Sometimes enquiries don't fall neatly under a heading, do they?

[email protected]

Cultural Calendar

A round-up of recommendations and reviews, sent on the first Friday of each month, topped-off with a commissioned image from a talented new illustrator. Sign-up and tell your friends.

Sign me up Cultural Calendar

Cog News

An irregular update of activity from our studio. Showing off about great new projects, announcements, job opportunities, that sort of thing. Sign-up and tell your friends.

Sign me up Cog News

Oem-locked Cid 0x0032 Fixed May 2026

In the world of mobile devices, unlocking a phone's bootloader or modifying its firmware can be a thrilling experience for tech enthusiasts. However, this process can be fraught with risks, especially when dealing with OEM-locked devices. One error that has been causing frustration among users is the "OEM-locked CID 0x0032" error. In this article, we will delve into the world of OEM locking, CID, and the infamous 0x0032 error, providing you with a comprehensive guide on what it means and how to tackle it.

OEM (Original Equipment Manufacturer) locking is a mechanism used by device manufacturers to restrict users from modifying their device's firmware, bootloader, or other critical components. This is done to prevent unauthorized changes that could potentially compromise the device's security, stability, or functionality. When a device is OEM-locked, it means that the manufacturer has locked the bootloader, preventing users from flashing custom firmware, kernels, or recoveries. oem-locked cid 0x0032

The "OEM-locked CID 0x0032" error typically occurs when a user attempts to unlock their device's bootloader or flash custom firmware using tools like Fastboot or ODIN. The error message indicates that the device's CID value (0x0032) is not recognized or supported by the unlocking tool or firmware. This error can be frustrating, as it prevents users from modifying their device's firmware or unlocking the bootloader. In the world of mobile devices, unlocking a

The OEM-locked CID 0x0032 error can be a challenging issue to overcome, but understanding its causes and implications can help you navigate the complex world of mobile device modification. While this error may prevent users from unlocking their device's bootloader or modifying firmware, it also serves as a reminder of the importance of respecting manufacturer-imposed restrictions and ensuring device compatibility. In this article, we will delve into the