Cyanogenmod ROM Motorola Droid 2 Global (droid2we)

Latest Cyanogen That Works

Unfortunately, none of the offical ROMs will work for Droid 2 Global. Neither the latest nightly (2013-03-01) nor the stable version 7.2.0. The only version which appears to work is an unofficial version 9, which is unstable. http://rootzwiki.com/topic/17976-cyanogenmod-9-unofficial-for-droid-2-global-ics403-update-31512/page-153#entry1117799

Downgrade to the 2.4.330 Firmware

If the Motorola Droid 2 Global is running firmware newer (higher) than 2.4.330 (Settings » About Phone) you need to downgrade the device first in order to root.

Downgrading the Firmware with RSD Lite (Windows)

1. Download the Motorola Drivers, RSD Lite & the 2.4.330 firmware:
   • RSD Lite 5.7: Download

     md5: feb9a71470ee539e074bf420a2e4d8bd

   • Motorola 5.5.0 device drivers: Download
   • 2.4.330 firmware: Download

     md5: 49cc34d07666c92c1a2a5779e2c74243 This firmware creates a bootloader error: Bootloader D0.11 Err:A5,70,70,00,1F. Do not install! If you accidentally install, VRZ_A956_4.5.608_1FF_01.sbf AND flash this after full 608 sbf.rar will get your phone working again. You have to flash both in succession.

2. Unzip the firmware and place it somewhere easy to access.
3. Install RSD Lite.
4. Once RSD Lite is installed, install the Motorola device drivers.
5. Power off the Motorola Droid 2 Global.
6. Boot into bootloader mode by holding down the Up Arrow on the keyboard & Power button.
7. Connect the Motorola Droid 2 Global to the computer via USB.
8. Open RSD Lite.
9. Click on the “…” button next to the filename box and select the 2.4.330 firmware .sbf file.
10. Once it is selected, hit Start and wait for it to finish flashing the device.
11. It should take about 20 minutes to flash the 2.4.330 firmware. Once it’s finished, the Motorola Droid 2 Global will reboot itself and it will go into a bootloader. Pull the battery and power back while holding the X button. Once you see an Android with the triangle & exclamation point, press the Search button on the keyboard press the ‘Volume Up’ and ‘Volume Down’ buttons at the same time.
12. The Motorola Droid 2 Global is now in the factory recovery image, use the arrow keys on the keyboard to move around and the Camera button (ClockworkMod Recovery only) or Enter on the keyboard to select.
13. Select the option to Wipe data/factory reset.
14. Once the wipe is finished, select Reboot system now.
15. The Motorola Droid 2 Global is now downgraded to the needed firmware.
16. Skip the activation of the phone by pressing once in the top left black corner, top right black corner, lower right black corner, and finally lower left black corner.
17. Turn on “Install Applications From Unknown Source” and “USB Debugging”.

Downgrading the Firmware with sbf_flash (Linux & OS X)

1. Download sbf_flash & the 2.4.330 firmware:
   • sbf_flash: Download

     md5: c0eedecde76f82b120161729428b59f7

   • 2.4.330 firmware: Download

     md5: 49cc34d07666c92c1a2a5779e2c74243

2. Unzip the sbf_flash zipfile.
3. Unzip the 2.4.330 firmware and place it somewhere easy to access.
4. Power off the Motorola Droid 2 Global.
5. Boot into bootloader mode by holding down the Up Arrow on the keyboard & the Power button.
6. Connect the Motorola Droid 2 Global to the computer via USB.
7. On the computer, open terminal and run the following commands:

   chmod +x sbf_flash

   ./sbf_flash VRZ_A956_2.4.33_1FF_01.sbf

8. It should take about 20 minutes to flash the 2.4.330 firmware. Once it’s finished, the Motorola Droid 2 Global will reboot itself and it will go into a bootloader. Pull the battery and power back while holding the X button. Once you see an Android with the triangle & exclamation point, press the Search button on the keyboard.
9. The Motorola Droid 2 Global is now in the factory recovery image, use the arrow keys on the keyboard to move around and the Camera button or OK on the keyboard to select.
10. Select the option to Wipe data/factory reset.
11. Once the wipe is finished, select Reboot system now.
12. The Motorola Droid 2 Global is now downgraded to the needed firmware.

Gain Root with Framaroot

1. Install Framaroot for one click root. http://forum.xda-developers.com/showthread.php?t=2130276 (Select Gimli.)
2. Run adb push Framaroot_9.9.9.apk /sdcard/
3. Open Files app, navigate to SDCard, select Framaroot, install, open, root, reboot.

Gaining Root Access with rageagainstthecage

1. You will need ADB on the computer to root the Droid 2 Global.
2. Download the following files:
   • rageagainstthecage-arm5: Download

     md5: bfa28d457b54508326ab55d11399c586

     (Note: Antivirus software may delete this because “it could be used by malware to root Android phones”. Either turn off your antivirus, or flag this as “allowed” while you are gaining root access, and un”allow” it when done.)

   • Superuser package: Download

     md5: 43d9a40b63e916635d5ad7ca32433fab

1. Unzip rageinthecage-arm5 & the Superuser package to the same folder as adb (the /platform-tools folder within the Android SDK folder).
2. Connect the Droid 2 Global to the computer via USB.
3. Allow “USB debug” on the device: Settings > Applications > Development and check USB debugging box.
4. On the computer, open terminal and run the following commands:

   adb push rageagainstthecage-arm5.bin /data/local/tmp/

   adb shell

   chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin

   /data/local/tmp/rageagainstthecage-arm5.bin

5. Once the exploit finishes, in terminal, run the following commands:

   exit

   adb kill-server

   adb start-server

   adb shell

   NOTE: You should see a “#”. If you see a “$”, then the exploit didn’t work, please repeat steps 4 & 5.

   mount -o rw,remount /dev/block/mmcblk1p21 /system

   exit

   adb push su /system/xbin/

   adb shell chmod 4755 /system/xbin/su

   adb push Superuser.apk /system/app/

6. The Droid 2 Global is now rooted, please continue to the next section.

Install Bootstrap

NEVER install or run Droid 2 Recovery Bootstrap when CyanogenMOD is already installed! It will brick your phone and you must re-flash stock SBF files with RSDLite. You will not even be able to enter recovery mode. Droid 2 Recovery Bootstrap is only for stock ROMs.

1. Download the Droid 2 Recovery Bootstrap:
   • Droid 2 Recovery Bootstrap 1.0.0.5: Download

     md5: c67a11b41f52b617d3656ba80016f003

2. Copy the Droid 2 Recovery Bootstrap to the same folder as adb (the /platform-tools folder within the Android SDK folder).
3. Connect the Motorola Droid 2 to the computer via USB.
4. On the computer, open terminal and run the following command:

   adb push bootstrap-1.0.0.5-droid2.apk /system/app/

5. The Droid 2 Recovery Bootstrap with the ClockworkMod Recovery should now be installed on the Motorola Droid 2.

Installing CyanogenMod from recovery

1. Make sure your computer has working adb.
2. Download the CyanogenMod build package for your device that you’d like to install to your computer.

   Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.

3. Boot to recovery mode, and connect the phone to your computer through USB.
   • X Key & Power
4. In ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm a menu selection, but for some devices a physical home key acts as a selector. Some devices have touch enabled ClockworkMod Recovery, in which case you may be able to swipe to, or touch, menu selections.
5. Optional (Recommended): Select backup and restore to create a backup.
6. Select wipe data/factory reset.
7. You have two options for transferring and installing the installation packages. The sideload method is more universal across devices, whereas the push and install method is more commonly used:
   • Sideload method: select install zip > install zip from sideload. Follow the on-screen notices to install the package. The installer does not necessarily display an “Install complete.” message. You can tell the install is complete if there were no fatal error messages and you have regained control over the menu.
   • Push and install method: Open a command prompt (or Terminal on Mac and Linux) and navigate to the directory holding the package(s) you would like to install. On the device, navigate to the mounts and storage menu. If you see /storage/sdcard0 or /sdcard as a mountable volume, go ahead and mount it. If you do not see one of these partitions, then instead mount the /data partition. Take note of which volume you mounted. Now, push the package(s) to your device (also, see tip below):

   – If you mounted /storage/sdcard0, then: adb push update.zip /storage/sdcard0/

   – If you mounted /sdcard or /data, then: adb push update.zip /sdcard/

   where update.zip should be replaced with the package filename. Go back to the main menu and select install zip. Choose to install from the same directory where you pushed the package(s). If you are installing multiple packages, install CyanogenMod first and then install any subsequent packages on top of it.

8. Once installation has finished, return to the main menu and select reboot system now. The device will now boot into CyanogenMod.

How To Build CyanogenMod For Motorola Droid 2 Global (droid2we)

Introduction

These instructions will hopefully assist you to start with a stock Droid 2 Global, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for CyanogenMod (based on Google’s Android operating system). Using these, you can build both CyanogenMod and CyanogenMod Recovery image from source code, and then install them both to your device.

It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.

Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :) And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

• A Droid 2 Global
• A relatively recent computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
• A USB cable compatible with the Droid 2 Global (typically micro USB, but older devices may use mini USB or have a proprietary cable)
• A decent internet connection & reliable electricity :)
• Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.

If you are not accustomed to using Linux– this is an excellent chance to learn. It’s free– just download and run a virtual machine (VM) such as Virtualbox, then install a Linux distribution such as Ubuntu (AOSP vets Ubuntu as well). Any recent 64-bit version should work great, but the latest is recommended.

Using a VM allows Linux to run as a guest inside your host computer– a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)

So let’s begin!

Build CyanogenMod and CyanogenMod Recovery

Prepare the Build Environment

Install the SDK

If you have not previously installed adb and fastboot, install the Android SDK. “SDK” stands for Software Developer Kit, and it includes useful tools that you can use to flash software, look at the system logs in real time, grab screenshots, and more– all from your computer.

Install the Build Packages

Several “build packages” are needed to build CyanogenMod. You can install these using the package manager of your choice.

For both 32-bit & 64-bit systems, you’ll need:

bc bison build-essential curl flex git gnupg gperf libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop maven openjdk-7-jdk pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev

In addition to the above, for 64-bit systems, get these:

g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev

For Ubuntu 15.10 (wily) and newer, substitute:

• lib32readline-gplv2-dev → lib32readline6-dev

For Ubuntu 16.04 (xenial) and newer, substitute (additionally see java notes below):

• libwxgtk2.8-dev → libwxgtk3.0-dev
• openjdk-7-jdk → openjdk-8-jdk

Java versions: Different versions of CyanogenMod require different versions of the JDK (Java Development Kit):

• CyanogenMod 7 – 9: Sun/Oracle Java SE 1.6
• CyanogenMod 10.1: Sun/Oracle Java SE 1.6 or 1.7
• CyanogenMod 10.2 – 11.0: Sun/Oracle Java SE 1.6 or 1.7 (OpenJDK 1.7 works fine, but the build system will display a warning)
• CyanogenMod 12.0 – 13.0: OpenJDK 1.7 (see note about OpenJDK 1.8 below)
• CyanogenMod 14.1: OpenJDK 1.8

Ubuntu 16.04 (Xenial Xerus) or newer and OpenJDK: Since OpenJDK 1.7 was removed from the official Ubuntu repositories, you have a couple options:

1. Obtain OpenJDK 1.7 from the openjdk-r PPA
2. Enable experimental OpenJDK 1.8 support in CyanogenMod 13.0 (not available in earlier version). To enable OpenJDK 1.8 support, add this line to your $HOME/.bashrc file: export EXPERIMENTAL_USE_JAVA8=true.

Also see http://source.android.com/source/initializing.html which lists needed packages.

Create the directories

You will need to set up some directories in your build environment.

To create them:

$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the “repo” binary and make it executable (runnable):

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Initialize the CyanogenMod source repository

Enter the following to initialize the repository:

Note: Make sure the cm branch entered here is the one you wish to build and is supported on your device.

$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b gingerbread

Download the source code

To start the download of all the source code to your computer:

$ repo sync

The CM manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Prepare to wait a long time while the source code downloads.

Get prebuilt Rom Manager

$ cd ~/android/system/vendor/cyanogen

then enter:

$ ./get-rommanager

You won’t see any confirmation- just another prompt. But this should cause the Rom Manager apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you are in the root of the source code (cd ~/android/system), then type:

$ source build/envsetup.sh
$ lunch

You should see a list of devices, including something like cm_droid2we-userdebug. Select it by typing its number. It is possible that lunch does not display your device. In that case try

$ lunch cm_droid2we-userdebug

or

$ lunch full_droid2we-userdebug

If all goes well, you should see that droid2we-specific directories are downloaded automatically.

Extract proprietary blobs

Now ensure that your Droid 2 Global is connected to your computer via the USB cable and that you are in the ~/android/system/device/motorola/droid2we directory (you can cd ~/android/system/device/motorola/droid2we if necessary). Then run the extract-files.sh script:

$ ./extract-files.sh

You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the ~/android/system/vendor/motorola directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with “command not found” errors.

Turn on caching to speed up build

You can speed up subsequent builds by adding

export USE_CCACHE=1

to your ~/.bashrc file (what’s a .bashrc file?). Then, specify the amount of disk space to dedicate to ccache by typing this from the top of your Android tree:

prebuilt/linux-x86/ccache/ccache -M 50G

where 50G corresponds to 50GB of cache. This only needs to be run once and the setting will be remembered. Anywhere in the range of 25GB to 100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s android build environment initialization page.

Start the build

Time to start building! So now type:

$ croot
$ brunch droid2we

The build should begin.

If the build breaks…

• If you experience this not-enough-memory-related error…

ERROR: signapk.jar failed: return code 1make: *** [out/target/product/droid2we/cm_droid2we-ota-eng.root.zip] Error 1

…you may want to make the following change to ~/android/system/build/tools/releasetools/common.py:

Search for instances of -Xmx2048m (it should appear either under OPTIONS.java_args or near usage of signapk.jar), and replace it with -Xmx1024m or -Xmx512m.

Then start the build again (with brunch).

• If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.

Install the build

Assuming the build completed without error (it will be obvious when it finishes), type:

$ cd $OUT

in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called… kernel.

But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains CyanogenMod Recovery, and (2) cm-7-20161224-UNOFFICIAL-droid2we.zip, which is the CyanogenMod installation package.

Install CyanogenMod

Back to the $OUT directory on your computer– you should see a file that looks something like:

cm-7-20161224-UNOFFICIAL-droid2we.zip

Now you can flash the cm...zip file above as usual via recovery mode. Before doing so, now is a good time to make a backup of whatever installation is currently running on the device in case something goes wrong with the flash attempt. While CyanogenMod Recovery doesn’t have a backup feature, there are other custom recoveries available that do. You can also use something like Titanium Backup (root required) as an alternative.

Success! So….what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Now that you’ve succeeded in building CyanogenMod for your device, here are some suggestions on what to do next.

Also, be sure to take a glance at the Dev Center on this wiki for all kinds of more detailed information about developer topics ranging from collecting logs, understanding what’s in the source code directories, submitting your own contributions, porting CyanogenMod to new devices, and a lot more.

Congrats again!

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.