Exploitation of iPhones and other devices based on iOS requires very sophisticated ROP payloads because of the code signing and non executable memory protections. The trouble with generating ROP payloads for iDevices is that every device class and every firmware version comes with its libraries at a different base address. And newer firmwares even have ASLR built in. Choosing the right ROPe without any help from an information leak is therefore challenging. This session will reveal how bad the odds are to choose the right ROP payload and will introduce the idea of multi environment ROP payloads that are valid for more than one address layout. It will be discussed how such ROP payloads have to be designed and a toll will be presented that tries to find the best possible ROP payload that works in as many address layouts as possible.