Unicorn Engine VS qemu-t8030

OFRAK Tetris is a project I started at work about two weeks ago. It's a web-based game that works on desktop and mobile. I made it for my company to bring to events like DEF CON, and to promote our binary analysis and patching framework called OFRAK.

In the game, 32-bit, little-endian ARM assembly instructions fall, and you can modify the operands before executing them on a CPU emulator. There are two segments mapped – one for instructions, and one for data (though both have read, write, and execute permissions). Your score is a four byte signed integer stored at the virtual address pointed to by the R12 register, and the goal is to use the instructions that fall to make the score value in memory as high as possible. When it's game over, you can download your game as an ELF to relive the glory in GDB on your favorite ARM device.

The CPU emulator is a version of Unicorn (https://www.unicorn-engine.org/) that has been cross-compiled to WebAssembly (https://alexaltea.github.io/unicorn.js/), so everything on the page runs in the browser without the need for any complicated infrastructure on the back end.

Since I've only been working on this for a short period of time leading up to its debut at DEF CON, there are still many more features I'd eventually like to implement. These include adding support for other ISAs besides ARM, adding an instruction reference manual, and lots of little cleanups, bug fixes, and adjustments.

My highest score is 509,644,979, but my average is about 131,378.

I look forward to feedback, bug reports, feature requests, and strategy discussions!

Entails hundreds of hours of single-stepping through that opcode in Linux kernel using an indirect operand pointing toward its own opcode (self-modifying code).

Even the extraordinaire Fabrice Bellard (author of QEMU) admitted that it is broke and did a total rewrite, which fixed tons of other issues.

https://github.com/unicorn-engine/unicorn/issues/364

Macdu (Vita3K dev) also stated that this game is CPU bound so they used a CPU emulator known as unicorn2 , this is also the reason for the slow speed

This is how I found out a snippet of assembly code that can actually distinguished between a KVM hypervisor and most of today’s emulator.

https://github.com/unicorn-engine/unicorn/issues/364

It also depends on how much money you want to invest in. iOS development is much more expensive overall you have to buy a developer account which is around 100$ a year while on Android it only cost 25$ (one-time purchase). And I'm not even talking about the other requirements. There are some solutions out there for iOS development on windows like Corellium but you'll have to spend a lot of money to test your application (295$/month for 6 cores). That's why I look forward to what the community can bring and you can have nice surprises like this iOS emulator that's in development : https://github.com/TrungNguyen1909/qemu-t8030

Github: https://github.com/TrungNguyen1909/qemu-t8030

6) I haven't tried this one either, but there is a QEMU fork with T8030 support with a tutorial/guide too. I think this is enough to get you a shell, and maybe it can be used to run native binaries just like on a jailbroken device.

A qemu fork for this was posted on HN a while ago:

https://github.com/TrungNguyen1909/qemu-t8030