Motorola Defy+ (MB526) Rooting & Dual-Booting Stock + Custom ROM Guide

Update: 20th Apr 2012 – Moving on from Motorola, support will not longer be provided.

* For Stock Defy+ (MB526) GingerBread Sets/Kernel Only

* Disclaimer:

– This guide is compiled with information from the XDA Motorola Defy/Defy+ Forum.

– It is intended for Defy+ users with basic knowledge on rooting/custom ROM installations and wish to dual-boot stock ROM alongside custom ROMs such as the CM7 & CM9.

– The following methods were tested on a Defy+ (MB526) with the system/kernel version as shown in the third photo on the left.

– What work for others may not work for you. Use this guide at your own risk.

– I claim absolutely no credits nor responsibilities for any successful/unsuccessful rooting and/or custom ROM installation attempts as a result of the use/misuse of this guide. :)

* Credits:

– To all the developers have who made it possible. Without the selfless works of developers such as DooMLoRD, Quarx, Epsylon, walter79, ksubedi, m11kkaa & others, Defy/Defy+ users would probably be stuck on stock ROMs forever! OMG!!!

XDA Motorola Defy/Defy+ Forum

Video is not of good quality. System information can be found on the screenshots below:

Screenshot Screenshot Stock ROM CM9 CM9 Deep Sleep SetVsel Under-Volt

1. Rooting

– Download DooMLoRD’s Easy Rooting Toolkit available at the XDA forum.

– Detailed instructions are available on the forum thread itself. It is vital to follow the instructions closely.

– Superuser will be installed with the rooting script. You’ll be able to control apps’ root access permissions with it.

* Rooting can also be done with other tools such as the Superoneclick, whichever works for you. Do take note that there are still some GingerBread ROMs (SBFs) that can’t be rooted (build 231/BL7).

2. Installing the Bootmenu

– Download & install 2ndInit Recovery Installer.

– Run the Defy 2ndInit app & choose ‘Install 2ndInit Recovery’.

– Allow if Superuser notifies of root access request from 2ndInit.

– Install the ‘Latest Release‘ (not the stable release) & reboot normally twice. You should see the blue LED lit up briefly on both reboots. This is normal.

3. Backup

a) Backup Apps & Data

– Download & install Titanium Backup (if you haven’t already) from Play Shop (former Android Market).

– Run Titanium Backup & select the items you wish to backup.

b) Entering the Bootmenu

– Reboot once more, this time press the volume down key/button once you see the blue LED.

– You should be brought to the Android Bootmenu.

c) Perfoming a NANDROID Backup

– Using the volume key, go to the ‘Recovery’ option and press the power button once.

– You should see ‘Stock Recovery’ and ‘Custom Recovery’.

– Using the volume key again, go to ‘Custom Recovery’ and press the power button once.

– Go to (volume key) & select (power button) ‘Backup and restore’.

– Go to ‘Backup (all)’ & hit the power button once.

– Once the backup is done, select ‘Go Back’ to return to the previous menu & select ‘Reboot system now’.

– NANDROID backups are stored in the ‘clockworkmod’ folder of your SD card.

4. Preparation for Custom ROM Installation

a) Choose Custom ROM

– Choose & download your desired Custom ROM.

– There are many Custom ROMs available at the XDA forum.

– For this guide, I’ll be using Quarx’s CM9 nightly (5th Mar).

– Once you have downloaded your desired custom ROM, place the entire zip file at the root of your phone’s SD card.

– Download the latest Google Apps for your custom ROM (the version here is compatible with CM9), if necessary, and place the zip file at the root of your phone’s SD card.

b) Download Bootmenu & CWM

– To dual-boot your stock ROM with CM9, you’ll need to update your bootmenu.

– Download the Bootmenu 1.0.4 and CWM file & place it at the root of your phone’s SD card.

c) Download Multiboot

– Download Multiboot & place the zip file at the root of your phone’s SD card.

– Multiboot v0.4 is used here.

– For, you’ll need to unzip all the 3 files in it to a folder named ‘fsimages’.

– Place the fsimages folder at the root of your phone’s SD card.

– Detailed instructions can be found on the XDA forum thread.

d) Update Bootmenu & CWM

– Reboot & enter the bootmenu.

– Go to ‘Recovery’ then ‘Custom Recovery’.

– Go to & select ‘Install zip from sdcard’

– Select & install the ‘’ file.

– ‘Go back’ to previous menu & ‘Reboot system now’.

e) Install Multiboot

– Enter the bootmenu & go to ‘Recovery’.

– You should now see ‘Stock Recovery’, ‘Stable Recovery’ & ‘Latest Recovery’.

– Go to either ‘Stable Recovery’ or ‘Latest Recovery’ (doesn’t matter which, though I used ‘Stable Recovery’).

– Go to & select ‘Install zip from sdcard’

– Select & install the ‘’ file.

– ‘Go back’ to previous menu & ‘Reboot system now’.

f) No Network Signal Fix

– You might not get any network signal on your CM9.

– To rectify it, download this and extract ‘’ file to the ‘system\bootmenu\script\’ folder of your phone (not SD card).

– You’d need a root explorer/file manager such as the ES File Manager to do this.

– Thanks to Quarx for this fix.

– A YouTube video on how to use the ES File Manager can be found below:

g) Install Custom ROM

– Enter the bootmenu & go to ‘Recovery’.

– Go to & select ‘Latest Recovery‘.

– Go to & select ‘Install zip from sdcard’

– Select & install the ‘’ file.

– Select & install the ‘’ file.

– ‘Go back’ to previous menu & ‘Reboot system now’.

* You do not need to flash any kernel. Stable Recovery contains your stock ROM (we are not going to flash any ROMs in Stable Recovery).

5. Booting

– To boot to stock ROM, you need not do anything.

– To boot to your freshly installed CM9, enter the bootmenu, go to & select ‘Boot’ followed by ‘2nd-boot’.

– It may help to wipe Cache and clear Dalvik Cache in the ‘Latest Recovery‘ should you get stuck in a boot loop.

6. Removing Custom ROM & Unrooting

– Should you wish to get rid of your custom ROM/virtual system (CM9 in this case), simply delete the entire ‘fsimages’ folder on your SD card.

– For unrooting, DooMLoRD’s Easy Rooting Toolkit should do the trick but I have yet to try unrooting myself.

* Backups

– The NANDROID & Titanium Backups are not mandatory but strongly recommended.

– Do remember, before you flash anything, that the ‘Stable Recovery’ contains your stock ROM and the ‘Latest Recovery’ contains your custom ROM/virtual system (on SD card).

– Restoring system data from Titanium Backup to a new ROM may cause problems. For example, your phone may fail to work properly if you restore system data, which was backed up in your stock ROM, to your CM9.

* SetVSel

– Only 3 clock settings are shown in the bootmenu (v1.0.4). However, it is still possible to configure clk4 through apps such as SetVSel.

– There are feedbacks on some XDA threads that over-clocking/under-volting should be done through the bootmenu instead of apps like SetVSel. Use at your own risk!

*** F.A.Q ***

Q1. Will this work on my Defy (MB525)?

A1. On theory it should. Defy (on stock Froyo) should work with custom ROMs for Froyo kernel. I’m unable to give Defy users a definite answer since the methods above were only tested on a Defy+ (MB526) on stock GingerBread with CM9 built for GB kernel.

Last updated: 19th Mar 2012

10 thoughts on “Motorola Defy+ (MB526) Rooting & Dual-Booting Stock + Custom ROM Guide

  1. On theory, it should work if you dual-boot Defy’s stock ROM (stock Froyo) with a CM7 (or CM9) for Froyo.

    Pardon me, however, I’m unable to provide a definite answer as I’ve only tested the methods on a Defy+ (GingerBread kernel) and not on a Defy (Froyo kernel).

  2. Soulness mate your blog is perfect.
    I had the same kind of phone and used your guide to a “T”.
    All went well. I have used CM9 lastest nightly and it is running fine.
    Just one change:
    In point e) the only options I get are
    1. Custom recovery
    2. Stock recovery.

    I used Custom recovery and proceeded as normal. All worked after that.
    What did do wrong?

    BTW thanks again for this brilliant checklist.

  3. Hi David,

    I am glad it worked for you. :D
    Credits to the XDA developers who have made it possible.

    I’m baffled too to be honest because the bootmenu 1.0.4 update should have brought out 3 recovery options. Usually flashing in the Custom recovery would have overwritten your stock ROM.


  4. Everything went well..but i am not getting the network signal even after replacing the existing file with the downloaded one!

  5. It is not necessary if you have the Stock, Stable & Latest Recovery options in your bootmenu.

  6. Pingback: Atualizando Motorola Defy+ para Android ICS 4.0.4 | Blog Ramon RDM