By Stephen Schenck | July 22, 2011 12:50 PM
Getting recovery software onto the Droid X2 was a big step towards readying the smartphone for some custom code, but with the bootloader still on lock-down, there was still a long way to go. It’s far from a decisive victory over Motorola’s protection methods, but the 2nd-init method has now been successfully employed to enable the DX2 to run a custom ROM.
This same technique has been used on the Atrix, Defy, and the original Droid X. Basically, the code hijacks the boot process to inject its own data, but this carries with it some limitations, like an inability to replace the kernel. Still, that’s been enough to get CyanogenMod 7 running on smartphones that would be otherwise still on stock ROMs.
Code for the DX2 was taken straight from what worked on the Atrix, and just re-compiled for the DX2. As a result, not a lot of testing has been done yet, but the principles it’s based on are sound. It doesn’t play nicely with other DX2 hacks, like the ClockWorkMod from earlier, so you might want to steer clear for the time being unless you know what you’re getting in to. The rest of us will wait for what should be the first custom DX2 ROMs to arrive in good time.