By GabePeters | February 28, 2011 1:42 PM
With Motorola’s implementation of a locked, encrypted bootloader on the Atrix 4G and other recent offerings, it was expected that custom ROM development would be difficult. DesignGears over at XDA decided to approach the problem a novel way, applying the ROM via a different method than usual, circumventing the bootloader issue.
The custom ROM, named “Adeo” is deployed via batch scripts executed on your PC and shell scripts executing on the device. The ROM is fully de-odexed, and adds a reboot option to the power menu. Rather than writing a new system image directly to the NAND storage on device via a flashing utility as a typical ROM does, the ROM is pushed to the device via the Android Debug Bridge (ADB). As ADB is a component of the Android SDK and requires proper drivers and configuration to operate, usage of this ROM is not recommended for those unfamiliar with the tool.
Because of this atypical deployment method, there are a few caveats. The device cannot be easily factory reset (doing so causes you to lose ADB access which must immediately be restored or risk a “soft brick”). There is also an increased risk of bricking during the process if power is interrupted because there is no currently available stock ROM to flash back to in case of emergency.
The ROM does make a back up of the original system files during its installation procedure, but there is currently no script available to revert back to stock. Because of this, there is high potential to put your Atrix 4G into an un-bootable situation with no ADB access to restore function.