My Motorola Milestone

1st of all: Droid = Milestone. No difference.

(Comment August 1, 2010: actually, there are both hardware, i.e. frequency band, and software differences. Droid firmware does not run on Milestone).

Out of the box,  no OTA firmware update offered; however, a lot of bugs which disappeared from the forums after the December update in the US. With a “Cable update” I get 2.1-update1, and e.g. the camera works now better.

However, the built-in e-mail application still crashes every 10th of my e-mails. I install K-9, which works fine.

I find an openstreetmap offline navigation (navit) and install it. Seems to work fine. (Comment August 1, 2010: did not really so; I buy Navigon, works fine, as good as my dedicated TomTom device.)

No problems with setting up three wireless accounts; the vanilla device (i.e. provider-independent) works with my A1 SIM card without any problems.


Root Motorola Milestone with Android 2.1 to install 2.2 (Froyo)

Motorola apparently will not update the (1 year old!) Milestone with Froyo. However, hackers have already ported the Nexus Rom to the milestone. I will try to install that.

Plan: root my Milestone following “How to Root Motorola Milestone on Android 2.1” ( Here are the instructions from there (without the links – please visit that site yourself):

The bootload process of Motorola Milestone running on Android operating system version 2.0 or 2.1 has been locked down by Motorola, as the firmware for Motorola Milestone has been digitally signed by Motorola with the company’s digital signature. As the result, the process to root the Motorola Milestone is slightly more complicated, as the user will need to flash vulnerable recovery image (SBF) to Motorola Milestone to make an “unrootable” firmware to become rootable.
Here’s the step-by-step guide to root the Motorola Milestone on Android 2.1.
Prerequisites to Root Android 2.1 based Motorola Milestone
* Download and install Motorola Mobile Phone USB Drivers from (32-bit Windows: or 64-bit Windows:

I’ve done this already earlier

* Download and install RSD Lite with at least minimum version of 4.5.3 or 4.6 (RSD Lite version 4.6: RSDLite4.6.msi)

Also this I’ve done earlier

* Vulnerable Recovery SBF (CG47) for mobile with bootloader RAMDLD 90.78 and lower only (vulnerable_recovery_only_RAMDLD90_78.sbf), which was made from SHOLS_U2_01.14.0 with SBF Recalc and HexEdit.
* Milestone root (

This I download…

I also want to install G.O.T. OpenRecovery, since I want to make a backup of my present status. Therefore I follow the instructions here instead: “[GUIDE] Root + Nandroid Backup/Restore with Open Recovery” (

* Motorola Milestone with Android 2.0 or higher
* If you have a Milestone with Android 2.1 or higher OR you have a Telus Milestone (with Android 2.0.1 or higher), then follow these steps to ensure you have downgraded to the vulnerable recovery with exploit (thanks to Ireas for these instructions):

This I have. So I do the following steps…

1. For this we need a Only-Recovery SBF file which we can flash via RSD Lite
2. First install the USB drivers from Motorola
3. Then you need the RSD Lite Tool | Linux machines can use the linux flasher (created by [mbm])
4. And the Recovery-Only SBF (which will downgrade the Recovery Partition and not the system)

Must not be in a path with a blank, otherwise the file will not be found by RSDLite (I think).

5. Start the RSD Lite, select the SBF file

(I have to start RSD Lite from the desktop icon produced during the installation, starting the binary directly does not seem to work.)

6. Plug in your phone (while it’s off)
7. Go into the Bootloader Mode by holding UP (on the hardware keyboard) and press Power-On for 2-3 seconds (if UP doesn’t work try pressing X)

The phone shows:
Battery OK
OK to Program
Transfer Mode:

8. Now select your phone which should be now visible in the RSD Lite tool
Does not show file. Ok, I have to unzip, produces a SHOLS_U2_01.14.0_recovery_only.sbf. Still does not allow “Start”…; I think I have done something similar already when I applied the bugfix for the alarm clock? ( – unfortunately, the forum has broken the link… I search for the title … and find… There they say I have this image.


I think the file is not recognized properly. It shows no file properties. I copy it to C:\.

Still not works. I try

– does not work…

I think the problem is that the phone is not recognized?

No! I have to start RSD Lite from the start Menu! Then the file is recognized!

9. Press Start

10. The phone will reboot 1-3 times during the downgrade process. DO NOT unplug it

Boots only once. RSD Lite says “PASS”.

Here is what my phone shows in the settings:

Firmware 2.1-update1



Baseband-Version 3GSMEPU91A_U_91.07.56I





milestcm@il93lnxebld05 #1



I decide to make a “Sicherung” (backup?) of all my Applications with ASTRO.



1. Download Open Recovery (choose one):

* Skrilax_CZ’s version (requires account registration):…07-2010-a.html

* G.O.T.’s mod of the above version (more features):

This is what I choose… I unpack the archive and get a folder “OpenRecovery” and file “”.

2. Extract the contents to the root of your SD card.

3. Reboot your phone into recovery menu:

1. Turn off phone

2. Press Camera button, then press Power. Hold them both till you see recovery screen.

3. Press Volume Up and Camera button at the same time till you see the recovery menu.

4. Apply the

What I get:

E: Can’t open /cache/recovery/command

then when i try to apply the

–Install from sdcard…

Finding update package…

Opening update package…

Verifying update package…

E:EOCD marker occurs after start of EOCD

E:signature verification failed

Installation aborted.

This is also mentioned in the [GUIDE]

I find:,

indiacam saying:

Based on Shatanus help I am putting above procedure as step-by-step IDIOTS guide in SIMPLE WORDS for newbies like me, so Experts please do not mind. I am still learning.

We are assuming that you have already installed necessary motorola milestone usb drivers. The device I have tested is Android 2.1-update1


NANDROID BACKUP/RESTORE of system WITH OpenRecovery 1.14


Nandroid Backup and Restore is something similar to SystemRestore of XP/Vista. Taking and

system backup image to keep safely to use in future, if you crash or mess-up your phone. YOU


1) For some technical reasons you cannot directly install any file to your

Milestone without flashing Vulnerable Recovery SBF file in RSDLite software.

Hence Download and extract vulnerable_recovery_only_RAMDLD90_78.sbf somewhere on your pc.

Download and Install RSDLite4.6,if it was not installed.

2) Also Download and extract somewhere on your pc. When you open zip file, you will

find a file named “” and a folder named “OpenRecovery”. Copy it to root location

of your SDCard. Power Off the phone

Now you are ready to start…

3) Run RSDLite4.6 on your pc and wait…

4) Start Milestone in BOOTLOADER mode by pressing UP-key on D-Pad and POWER key until you see some white

text on blackscreen showing “Bootloader 90.73, Battery Ok, Ok to Install, Connect USB, Data

cable.” Now connect USB Cable to phone and on RSDLite window you will see the message as


5) Now select Vulnerable Recovery SBF file and press Start button. RSDLite will quickly process the SBF file and

will show “Phone is rebooting” ****THIS IS TRICKY PART**** When phone restarts, you should

quickly press Up-key on D-pad when phone screen is blank, so you again get BOOTLOADER mode screen. Now RSDLite will show “PASS” message on window. SBF flashing is done. Now switch off phone. And remove USB Cable. RSDLite is no more required.

This is the difference! Now it works!

6) Now start phone in Original ADBrecovery mode by pressing CAMERA KEY and then POWER KEY

both together until you get Exclamation Icon inside Triangle. Release buttons and now Press

VOLUME-UP key with Camera key. Now you will see Original ADBrecovery menu where you should

select Install option by d-pad arrow keys and d-pad center key to install.

(Remember: Because you have flashed Vulnerable Recovery SBF file before installing, you will not get any error now while installing but you will need to flash SBF everytime you want to install new UPDATE.ZIP)

When done switch off phone.

Dunno whether problem, but my phone goes to OpenRecovery directly after installing, without switching off.

7) Now do NOT start phone in normal mode. Again start phone in ADBrecovery mode as

exactly shown in step-6, but this time you will not get Original ADBrecovery menu, YOU WILL

GET NEW OPENRECOVERY 1.14 MENU, where you will see many options like NANDROID BACKUP and

RESTORE and etc. YOU ARE DONE! You got OpenRecovery Menu.

(IMPORTANT: Everytime you want OPENRECOVERY 1.14 menu you must flash SBF first)

Now you can take NANDROID backup which will take some time to copy SYSTEM IMAGE (around

142mb) in /nandroid/adbrecovery/ folder which you should copy and keep safe in your pc or cd

for future reference.

I make a nandroid backup of both system and data.

Here is a list of many .sbf:

Here the xdadevelopers Dexter_nlb explain their froyo:

Now I root my phone with the OpenRecovery Menu and install Overclock to 800 MHz.

More to come…


Already I’m happy that I made the root. The 800 MHz overclock makes the device feelable more responsive. I install Setcpu. No time today to play…


I copy the nasdrois backup produced on Sunday to my laptop.

Found the following page(s), describing adb setup:

Maybe I should have gone with adb from the beginning, looks logical…

However, probably no time to play today also.

In the evening…

Here is the recipe from

I. Setting Up The SDK

1. Download the Latest Android SDK from Google

Android SDK

2. Extract the Android SDK .Zip file to C:\AndroidSDK (this should name the new folder created AndroidSDK in the C directory.

3. On your phone, click Settings > Applications > Development and make sure USB Debugging is on.

4. Plug your phone into your computer > via USB cable (it needs to be on). It should say installing drivers if using Windows.

!UPDATE 12.01.09 – If using Windows 7 skip steps 4 and 5 and use this procedure instead.

5. After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.

6. Type the following into the command prompt window (hitting enter at the end of every line):

cd AndroidSDK\tools\
adb devices

You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.

If you do NOT see a serial number, then we need to reinstall the drivers.

Fotunately, I see a serial number…

IV. Some Common ADB/Fastboot Commands

ADB Commands

adb devices – lists which devices are currently attached to your computer

adb install <packagename.apk> – lets you install an Android application on your phone

adb remount – Remounts your system in write mode – this lets you alter system files on your phone using ADB

adb push <localfile> <location on your phone> – lets you upload files to your phones filesystem

adb pull <location on your phone> <localfile> – lets you download files off your phones filesystem

adb logcat – starts dumping debugging information from your handset to the console – useful for debugging your apps

adb shell <command> – drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly

Fastboot Commands

fastboot devices – lists which devices in fastboot mode are currently attached to your computer

fastboot boot <filename> – boots a rom stored on your pc specified by the filename

fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}


I backup the baseband-files to my computer with adb pull:

C:\AndroidSDK\tools>adb pull /system/etc/motorola/bp_nvm_default/File_Audio moto
186 KB/s (3255 bytes in 0.017s)

C:\AndroidSDK\tools>adb pull /system/etc/motorola/bp_nvm_default/File_Audio2 mot
342 KB/s (4909 bytes in 0.014s)

C:\AndroidSDK\tools>adb pull /system/etc/motorola/bp_nvm_default/File_GSM motoro
127 KB/s (1562 bytes in 0.012s)

C:\AndroidSDK\tools>adb pull /system/etc/motorola/bp_nvm_default/File_Seem_Flex_
Tables motorola_baseband/File_Seem_Flex_Tables
230 KB/s (3539 bytes in 0.015s)

C:\AndroidSDK\tools>adb pull /system/etc/motorola/bp_nvm_default/generic_pds_ini
t motorola_baseband/generic_pds_init

268 KB/s (3572 bytes in 0.013s)

Some interesting information also here:


I decide to intall MotoFrenzy now.

I make another Nandroid All Backup, and copy it to the computer.

I download MotoFrenzy v0.4 from, and unzip it. Copy Folder MotoFrenzyv04 to /sdcard/nandroid/adbrecovery.

Go into OpenRecovery; wipe all user data. restore “MotoFrenzy” backup; reboot.

A new boot screen appears, like a red eye. After about 2 min the piece hums and a mobile setup assistant starts. I enter my SIM-no, google-account, … and is up, connected to G3.

I test my phone; I can do a phone call (actually I listen only to the other phone ringing…).

I can reinstall my purchased apps from the market. It asks for root – I accept – however, it shows only 550 MHz max.

Fter installing my mail account, also the mail program of Froyo stalls while loading the mails. I think I will have to use K-9 mail also here…

The camera works, but I do not hear it focussing; also photographed text looks a little unfocussed.

Ah, by the way: up to now the system is english… I will check for german later.

I set up the WiFi… works easily… connects.

I test the Browser Form editor … copy and paste of selected text works! Very importnat for me (2.1 always copied the whole field, not only the selected text).

I use the preinstalled Overlock to set to 800 MHz… works.

I pull the flashplayer com.adobe.flashplayer-1.apk coming with MotoFrenzy to the root of the SDcard, and install it with ASTRO File manager (which I fetch from the market). I install Dolphin Browser HD from the market to have the option to access the “dektop” version of the sites… I go to, and the video “kruger battle” runs nice!

I’m impressed. Everything seems to work so far. I go sleeping, and let it installed.


I’m happy with MotoFrenzy, everything works but the QURTZ keyboard (however, there seems to be a solution) and the ***CAMERA FOCUS***.

With 1 GHz overclock flash videos work very well, whatever people might say. Also the

I was already at going back (since I use the camera heavily for archiving real-paper documents, before I put them into the trash bin) – when MotoFrenzy 0.5 cam out! I will install this now…

First I make a backup of the applications I have installed now with ASTRO.

Download and unzip MotoFrenzy0.5, store the MotoFrenzv05 folder to /sdcard/nandroid/adbrecovery

go to G.O.T. open Recovery:

— I think now the following would not be required… —

start RSDLite on PC -> select SHOLS_U2_01.14.0_recovery_only.sbf; start phone with Dpad-Up + On; Connect to USB; Start in RSDLite; during phone reboots: Dpad-Up -> RSDLite shows pass, phone on Update screen agin. Disconnect USB.

— … till here. —

Switch off phone,  hold Camera + Press ON -> Triangle appears; VolUp+Camera: Stock Recovery Menu; apply -> phone goes to G.O.T.

Nandroid Menu->Nandroid Backup->Backup All; Takes some three minutes.

Wipe data/factory reset

Nandroid menu->Nandroid Restore ->MotoFrenzyv05

G.O.T. modding-<change keyboard Layout->quertz

Reboot System

… follow Android start procedure…

… Oops! The camera still does not focus! This should really be mentioned on the first page of the MotoFrenzy-homepage. Thus, Froyo and Flash good bye, I have to go back to my Android 2.1…

Additionally, I see that still only english and espaniol are available.

Power off, boot into recovery, upply -> GOT -> wipe -> nandroid restore.


There is a new Froyo rom out,

CyanogenMod 6.1.0 RC0 for Milestone


I check that I have saved all my apps with Astro, make a nandroid backup of the present 2.1 (named A2.1-20100925-1617) and copy it to the laptop. I download, unzip it, copy it to the SDcard into /nandroid/adbrecovery, try to install it with OpenRecovery – and it fails since cannot find nandroid.md5; indeed, there are only md5’s for the individual files.

When I try to go back to my old image, the data partition is lost!? – I try a wipe and nandroid restore again: no, it is really lost! Maybe the SDcard ran out of space during the backup? Was quite full.

I resume to the nandroid backup from Aug 22. – ok, works.

On the cyanogen home page I find a link to a nandroid.md5. I put this into the folder, and now the restore works.

I can get no phone connection and no data connection. – however, after a reboot, it works!

WIFI works. I install flash from market – works; The camera seems ok now. Installing most apps from an ASTRO backup works, update them on the market.

Re-installing my ***BOUGHT*** navigon from the original .apk does not work: asks for the activation code; the code I got from NAVIGON which did work when installing for the first time does not work any more. Similarly for a new free trial .apk from the market (which when I did install first actually was already the full version after paying for the activation key). So I deinstall navigon again in 2.2 – and it WIPES the maps from the SD! I will not be able to use navigon from 2.1 now also! I have no backup (mea culpa) but there is no info in navigons documentation how to make a backup (e.g. where the files are located). These navigon people apparently care more about possible thieves than about their honest customers; companies behaving like that are usually doomed, avoid! I decide to install a cracked .apk; it downloads the maps from the navigon site again (takes 1 1/2 hours) and then simply works. I’m sure it is completely legal what I do, I still have the bill.

I make another nandroid backup.

Finally, I modify /system/etc/init.d/10overclock using values from [How-To] vsel’s, mpu_opps etc. [Overclocking] –

1000 MHz, vsel = 60; 500 MHz, vsel = 36; 250 MHz, vsel = 28; 125 MHz, vsel = 28

… and reboot; seems to work.

I think I have now something which is as good as the Milestone 2! Let’s see whether it is stable.

I now try the built-in usb tethering; the Android 2.2 manual says I can simply connect it to Vista and it will “work”; however, this does nothing; additionally, no new usb modem or whatever is visible. I install “Wireless Tether for root users” from the market, and this works (however, this will consume more power from my laptop’s or phone’s battery). I still have PDANet usb tether, and this still seems to work.

I’ve got Froyo!


Cyanogen Mod too unreliable

Unfortunately, the cyanogen mod on the Milestone is very unstable; the worst thing is that the phone app is not working in most cases: every second call lost (without message), crashes on hang up, … Actually, I have to reboot before every outgoing call, and loose every second incoming call.

Go back to Android 2.1, though the Froyo features (especially the many bugfixes) are really valueable – however, at least the cyanogen mod adds much more bugs.


Install G.O.T. 2.2.1 – another Froyo Custom ROM

I’ll try out the G.O.T. ROM, since it is now based on the official DACH release and  has a 2.2. Kernel. Let’s see…

Here is what you need to know:

a) Contrary to previous releases, we would strongly recommend you to use our GOT OR V2.0.
One of the first things you should do is use the “Fix 2.2.1 bugs” selection in the new OR 2.2.1 menu after you flash the sbf file.
This tweak will fix some of the issues with the generic sbf build such as dual USB notifications, replacing some stock Motorola applications such as the old launcher/mediagallery  and adding the Wireless Tethering application.
DO NOT USE after installing the G.O.T. theme, as the services.jar is different between both versions. If you did it anyhow, simply install the G.O.T theme again.
b) The sbf firmware files are all modified by us including the vulnerable recovery, so you can flash and root straight away (same as with our previous releases)
c) If you flash the firmware, you might encounter a reboot after the first boot. This is normal and expected behavior, so do not be alarmed
d) We can only provide you with full sbf releases at this moment. We strongly recommend not to use any backup from 2.1 related kernels as you are bound to get into trouble. The best approach is to install the apps you need from the market, set up your accounts and customize your device by hand. This is the only way you can guarantee that any issues encountered are not due to an incompatible  data/settings backup.
e) Performing and restoring nandroid backup from 2.1based kernels will result in a bootloopunlessyou use our G.O.T V2.0 OpenRecovery (or any other ORs that have been updated to V1.44 of skrilax_CZ base). The simple reason is that we have worked together with Skrilax_CZ as we, and him, encountered issues when trying to restore 2.1 based nandroid images on top of the flashed 2.2.1 firmware. We are very happy our cooperation with him was as good as it was, and as such be in a position to already have solved this issue at launch.
f) We are extremely proud to give to you the new G.O.T Theme for 2.2.1. Some of you may see the familiarities to the SummerBluesTheme of he_stheone64. There is a reason for it – we are proud to be able to announce that he_stheone64 has worked with us, and agreed, that his SummerBluesTheme is now the new G.O.T theme.
g) NOTE: On some devices, we have encountered that rooting directly after flashing without rebooting after the initial flash can bring some issues with RootExplorer not asking for root permissions. To be safe, reboot after flash so that the “welcome to milestone” menu comes up, set up the device in general, then reboot to recovery and root the device as well as apply our 2.2.1 tweaks with Launcher, Services.jar fix and Wireless Tethering app.

We have seen user comments below that I think you guys should try regarding the Missing Android ID:
You can simply add the Android ID using an SQLITE Editor extension from Root Explorer: (SQLite Editor in market)

1. Open RootExplorer
2. Navigate to /data/data/
3. Add an entry insert into secure (‘android_id’,’16-digits-hex-number’) using the SQLite Editor ->New Record->name=android_id -> value= 16digit hex code;
4. You can either use a dummy 16-digit hex number, or what we would recommend, revert to a previous Nandroid from your phone, use root explorer(only view SQLITE db) the same way, and take a note of your AndroidID. Then simply add/enter this 16-digit number to your phone in 2.2.1 as per steps 1,2 and 3

david cummings Says:
27.10.2010 at 23:28

Fantastic job, used 64bit win 7, ran rsd 4.6, plugged usb cable in, made sure usb portal was selected, used the 90.78 sbf file, pressing d pad up before rsd said pass so it would not boot. Then camera power key, then camera and vol up. Applied update, camera power then camera vol up, then rooted phone from got menu. Started phone then usinf rsd, used uk firmware, press dpad up to stop phone from booting as before before rsd said pass, camera power then camera vol up. Select 2.2.1 bug fix and overlock 800mhz 66 vsel. booted up phone, every thing brill. finally got froyo on my milestone thank you to the team. keep up the good work lol

First I make a nandroid backup of the present system, and note my Android ID as described above. Then I put a new SDcard (32GB) into the device, and … install new OpenRecovery.

DOWNLOADS: G.O.T OpenRecovery V2.0:

Unzip, put OpenRecovery directory and on new card. Then  I download

DACH AUSTRIA -> some-strange-name.sfb

However, the file is not accepted by RSDLite. Start button remains dimmed.

I try


also this does not work.



does not work;

I have to install RSDLite 4.9  (I had 4.6). Now it works. Do first configurations; interestingly, my screen background from the cyanogen mod shows up.

When I try to apply the use the “Fix 2.2.1 bugs” selection in the new OR 2.2.1, but the device is stuck if I try to start the menu. GRMPF. I cannot even root my phone.

I see that there is a 2.01 already available:

Ok. Works now; I apply the Fix 2.2.1 Bugs. Then I root the phone. Overclock to 1000 MHz/Vsel=60. Install Busybox. Reboot.

I copy folders from the old SDcard to the new one (Old SDcard in Laptop, new in USB-connected Milestone, ~12 GB, 3 h).

First impression is good!

When I try to change my android ID with SQlite, I have to find out that I cannot find it on the market. Strange. I edit configuration-file in OpenRecovery-CFG, and fix ID from the OpenRecovery menu.

 [How-To] vsel's, mpu_opps etc. [Overclocking] -

II still feel comfortable with the G.O.T. Rom. However, does not seem to go to deep sleep mode, I have to charge it every night.


An official Motorola 2.2 was rolled out, but people are not happy with it; I will install cyanogenmod 7 instead, which is a 2.3 actually, no 2.2. I still have troubles with (german) voice control, and the text edit fields in forms.

I follow

I install the Androidani OpenRecovery: rename previous and OpenRecovery + .CFG folder on SDcard, download new; I do not install the vulnerable recovery, since I should have it already! I tworks, and I create a Nandroid backup with the new Androidani OpenRecovery.

I install Titanium backup pro from the market to backup my applications (I remember having bought it already – however, I have to buy it again!? – don’t care, it’s little money).

I copy and into /sdcard/OpenRecovery/updates, boot again into OpenRecovery (works without RSDLite). Wipe all, apply update.

Apply mods: Eclair/JitV7, Memhack, RecoveryBoot, App2sd, Busybox to /data/busybox, Overclock 900-…-250

Reboot… stays very long on M screen… after 10 min: take out battery, retry… same. Boot into Openrecovery again, wipe, install only Cm7, … boot animation after ~2 min… starts with usual startup dialog; I enter my google account. After that, I boot again into OpenRecovery, apply the quertz keyboard, and the googleapps update.

I have to enter the WiFi key again. While I go through the features, the market re-installs some 26 apps. I move them to sdcard with TitaniumBackup. I update 38 missing apps+data with titanium backup.

Calendar works, in sync. FX Camera works.

I cannot find the TwoTouchTimer widget, despite the app is there.

I go into market and update the apps, several are for update (probably because of new OS?).

I find out that CM7 is overclocked from the beginning (1 Ghz). Now tweaks required. Now I also know why the tweaks failed: they were for Eclair, this now is Gingerbread (I confused the names).

I switch off the 1% Battery level indication. Now I reboot.

Apparently, it would have been better to reinstall all apps with Titanium, since the new installed from market have lost their data. If I encounter this, I reinstall it with Titanium, seems to work for most.

Up to now good behaviour. I switch off all animations etc. Let’s see.

I edit /system/etc/init.d/ to 1000 MHz (vsel 60), 750 (53), 500 (36), 250(28), 125 (28)


CM7 on Milestone (up to RC 12) for me seems just to laggy: especially when switching between apps there seems to be no multitaksing; additionally, the launcher of the AWD browser is annoying, since the icons are jerking around for several seconds, making it difficult to hit the right one. Additionally, Navigon is stalling every 20 min or so, making it useless. I conclude Gingerbread is too bulky for Milestone’s small RAM. The only real advantage of Android 2.3 is the copy&paste functionality, which anyways does not cooperate well with most of the existig apps (especially if the are continuously killed when trying to use multitaksing).

Thus I decide to go back to 2.2 (Froyo). Since the WEB considers Motorola’s stock 2.2 practically a hoax, I check for custom roms. CM6 (Froyo) for Milestone is unfortunately no longer supported by Nadlabak the original developer, who’s jumped onto CM7 (Gingerbread). Therefore I try FroyoMod by 89luca89 ( from xda developers.

Before I make a Nandroid backup (for my own records: 20110724-1008) of the CM7 RC 12.

Now I install the FroyoMod v2.9.1 with a full wipe; the market unfortunately pushes a lot of apps back on my device immediately, and I see no possibility to stop it. I think it would be a good idea to start without specifying a google account in the future. The Titanium backup apk can be installed from the market without this, and then all other apks can be installed by Titanium; after that, they can be moved to SDcard with Titanium also, which works apparently also for many apps where froyo does not allow app2sd, and does not seem to cause any problems, besides preventing apps to display widgets (these again works after moving the apps back, anyways). Still a lot of manual work.I use it with Navigon, and it works nice the whole day; however, it drains the Battery with the default settings also if constantly on the car charger (a cheap one, does not even specify current). Later on, I change /system/etc/init.d/ with root explorer to my own values as shown above and interactive governor,  limit the max processor speed to 500 MHz, and switch to on 2G; during one hour driving the battery gains some 20%. However, it was night then already, and the automatic display brightness had dimmed the display to minimum. I will try next time with the 2A (!) charger from my wife’s old TomTom Navi.

I#m very happy with the mod; after 1 day I try to use the Wifi, however, and it fails; also some proposed fixes from the xda developers forum do not help.

As a trial, I flash FroyoMod 2.7.0 with DSI fix from Soxes (, after a full data wipe 😦 and the wifi works; the market again installs all my apps from the market. Hmpf; overwrite the most important ones from Titanium backup. However, this version does not feel so smooth than v2.9.1; I think I will continue with 2.8.0, 2.9.0, and 2.9.1 (similar to “First 2.9.0, then 2.9.1”, suggested at without data wipe.

I have a problem to find a link to the v2.8; so I will jump directly to 2.9.0, which like other old versions are found at (

Before, I make a nandroids (20110725-1118 and 20110725-1536) of the FroyoMod v2.7.0 with DSI fixes and adjusted

I did now flash v2.9.0 and then v2.9.1 (I did wipe dalvik and cache each time); the wifi worked for me with both versions, skadude66 was right. I find out that I have to clear the data of GoLauncher after flashing, to show my apps in the launcher; I think it has some cache where it stores the app list; I think I like it, because this cache prevents jerking icons.

I make a nandroid (20110725-1626).

I (again) restore many app data through Titanium backup and adjust

Actually, I’m impressed how smooth this mod runs.


Actually, I still had sporadic crashes, the deep sleep was blocked after GPS fixes (I made a workaround with Tasker), and I at least once saw an incoming call and the phone was not ringing; the phone was stuck about twice per hour (often in the search box) the UI was frozen, could however be recovered by temporariliy switching screen lock on/off with the power key. Navigon crashed twice after about 1/2 h of driving. Toggle2G worked if flashed form, but did not chancge the icons.

I decide to go back to 2.7.0 from above, but to keep the Go Launcher.

Titanium backup of all downloaded apps. GoLauncher EX 2.33 has to be backed up separately.

Reflash nandroid 20110725-1536. Restore apps with Titanium, also Tasker though already installed from Market.

I find out that also this version has the GPS bug; apparently, most people just do not try out things correctly; I reenable my tasker bugfix.


What happened in the meantime: I stay with FroyoMod 2.7.0 and have disabled tasker, since it is responsible for dysfunctional WiFi. This means most of my workarounds no longer work: Online Banking (the TAN comes as SMS, and opening the SMS app stalls the online banking app), power saving (if I forget switching off GPS manually, then the deep sleep mode fails), etc.

Moreover, the Android Market app, after an update, has lost track of 90% of my (payed) apps. The reappear when I go back with Titanium to the older market version, but only till the next time the market app updates itself. It takes some time until I find out that I can stop this with “freezing” the market updater app in titanium.

One general observation I have is that almost NO android app follows Androids’ User Interface Guidelines: they require that an app can be killed by the system when in background and memory becomes scarce, but should restart seamless in the same state as left by the user when calles again. Neither Bank Austrias Mobile Banking, nor Documents to Go, nor Navigon manage to do so.

Additionally, many apps chease to work with, since the developers just pack more and more functions into them, rendering them buggy, and auto update forces them onto the phone. Camera Zoom FX is such a case. Fortunately, I have root and Titanium Backup to go back to previous versions. God bless Apple’s system of checking the quality of the apps.

Finally, this device is a disappointment. I think my next buy will be an iPhone. It will be difficult to live without a hardware keyboard, but a device where nothing really works (see above) is no option.



7 Responses to “My Motorola Milestone”

  1. mark Says:

    Great instructions and description of experiences. Thank you.

  2. Andi cristian Says:

    Hello, i need a little help, i want to downgrade the CPU speed, now it’s set@1Ghz by rom, Cyanogen.I must edit the file 10overclock from /etc/init.d/10 overclock file but i don;t know how.I try with astro and edit as a text document but i can’t.
    i’m wainting your answer.
    Thank you very much

    • petersteier Says:

      Please describe your problem more precisely; probably you have to edit the file with root permissions, which ASTRO cannot do. I use Root Explorer (however, it is not free).

  3. Bariatric Surgery Says:

    ”` I am very thankful to this topic because it really gives useful information .-“

  4. Starke WLAN-Probleme bei Froyomod 2.9.1 - Says:

    […] […]

  5. thuis tanden bleken Says:

    I was wondering if you ever considered changing the layout of your website? Its very well written; I love what youve got to say. But maybe you could a little more in the way of content so people could connect with it better. Youve got an awful lot of text for only having one or 2 pictures. Maybe you could space it out better?

    • petersteier Says:

      Actually, I have no pictures at all (I would not know how to add one). Thank you that you love what I write, but due to time constraints I cannot scope too much with layout. Sorry!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: