Page 1 of 11 12345678910 ... LastLast
Results 1 to 15 of 156
  1. #1
    njones's Avatar
    offline So I Hear You Can Mod
    Join Date
    Jun 2010
    Location
    California, USA
    Posts
    103
    Thanks
    24
    Thanked 48 Times in 12 Posts
    Downloads
    13
    Uploads
    0

    Troubleshooting The Bell Mobility Dext Bible - How to ROOT, flash a 2.1 ROM and keep 3G



    Introduction:
    After witnessing more and more people messing up their phones and 3G connectivity, while attempting to root and flash ROMs, I felt that it was time to write up something dedicated for the Bell Mobility Dext. After all, most of what is on this forum centers around the T-Mobile US Cliq - or the European and Asian Dext. Some of the stuff overlaps each other - and indeed most of what is written in this guide apply also to the Cliq and UK/Asian Pacific Dext - but there are a couple of major differences between the devices. And not understanding these differences and what they mean, can have fatal consequences when rooting and flashing. Final note - Some steps may be redundant, but this is what worked for me. Also - please do let me know if you find an error

    Acknowledgments:
    tonymy01 - for patiently answering all of my questions and sharing his wisdom
    HandlerExploit/simply-android.com - for the 2.1 leak as well as the recovery
    adlx - for the 2.1 ROM without a radio to mess us up
    Skrilax_CZ - for the new method of rooting
    toxigenicpoem - for coming up with a solution on how to get the recovery working
    ModMyMobile.com - for being a great source of information

    Disclaimer:
    Tampering with your phone's firmware and software is not risk free. You will most likely void your warranty, and there's a possibility that you may end up with a non-working device. Understand the risks of what you are doing before you do it. Research and understand what you are actually doing to your device, and do not just follow a guide blindly. What is written in this guide works for me, but understand that it might - for whatever reason - create problems for you. You and only you is responsible for what happens to your device.


    Index:

    Chapter 1: About the different models of Cliq and Dext, 3G frequencies.
    Chapter 2: About firmware differences.
    Chapter 3: What is baseband and how to find what version you have.
    Chapter 4: How to find the baseband version.
    Chapter 5: About rooting, recovery and ROM.
    Chapter 6: Understanding the risks involved.
    Chapter 7: Setting up your computer for rooting.
    Chapter 8: How to root - the easy way.
    Chapter 9: How to backup your stock 1.5 recovery for unrooting.
    Chapter 10: How to backup your stock 1.5 APN's and prop files.
    Chapter 11: How to flash a custom recovery to your phone + Nandroid backup of your stock 1.5 firmware.
    Chapter 12: How to flash a custom ROM + restore your stock 1.5 APN's.
    Chapter 13: ROMs that will not screw up your Bell Mobility Dext.
    Chapter 14: How to undo everything: Return to stock 1.5 ROM, recovery and unroot.

    1. Understanding the differences between the Cliq and Dext:

    The Motorola MB200/MB220 comes in three flavors:

    The Motorola T-Mobile Cliq for the US market.
    The Motorola Dext for the European and Asia/Pacific market
    The Motorola Dext for the Latin American and Canadian market.

    The major difference between the versions is the 3G frequency that they use:

    The Cliq uses 900/1700/2100 3G bands.
    The EU/Asia Dext also uses 900/1700/2100 3G bands.
    The Americas Dext uses 850/1900/2100 bands.

    Most of Latin America uses the 850/1900 3G bands. Aruba, Brazil and Uruguay also uses the 2100 3G band.
    Bell Mobility is 850/1900 only. Other Canadian operators also use the 1700/2100 bands for 3G.
    AT&T uses 850/1900 only. T-Mobile USA only use the 1700/2100 bands for 3G.

    To learn more about the difference in 3G bands across the world, please refer to this website: http://en.wikipedia.org/wiki/List_of_UMTS_networks

    The Cliq and all versions of the Dext are quad band 2G - 850/900/1800/1900. Hence, an unlocked T-Mobile US Cliq could be used with a UK sim card and would have 3G. A T-Mobile US Cliq, UK Dext and Aussie Dext could be used with a Mexican sim card, but one would only have 2G connectivity. Aside from the differences in 3G bands, the models are also "branded" with custom firmware for each market and operator.

    Sources:
    UK Dext: Motorola DEXT - MOTOBLUR - Android phone - Tech Specs - Motorola United Kingdom
    Asia Pacific Dext: Motorola DEXT - MOTOBLUR - Android phone - Tech Specs - Motorola Asia Pacific
    Australia Dext: Motorola DEXT - MOTOBLUR - Android phone - Tech Specs - Motorola Australia
    Mexico Dext: Motorola DEXT - MOTOBLUR - teléfono Android - Especificaciones - Motorola México
    Canada Dext: Motorola DEXT - MOTOBLUR - Android phone - Tech Specs - Motorola Canada
    T-Mobile US Cliq: Motorola CLIQ - MOTOBLUR - Android phone - Tech Specs - Motorola, Inc. USA

    2. Understanding the difference in firmware:

    The Cliq as well as all versions of the Dext currently come with Android 1.5 pre-installed. However, because of the difference in the 3G bands, the models have variations in the firmware. One cannot apply T-Mobile USA firmware to an American Dext without the risk of at least loosing the 3G bands, if not bricking the phone completely.

    However, a UK Dext user may be successful in flashing T-Mobile firmware since the 3G frequencies - or 3G radio - is the same. Granted that the baseband versions match. However, the UK Dext user would now be presented with the issue of having T-Mobile bloatware and branding on his phone. And unless you've taken a backup of your stock recovery and a Nandroid backup of the stock Orange UK 1.5 firmware, you're going to be stuck with the T-Mobile US firmware.

    3. Finding your baseband:

    To determine what your baseband is:
    1. Go to "setting"
    2. Scroll down to "About Phone"
    3. Scroll down to "Baseband version"

    My Bell Mobility Dext shows the following: 76XXC-63805030-SDCBALUM.

    In baseband terminology when looking at ROM compatibility, my baseband would be "5030". This number is important for determining which ROMS are compatible with your device.

    4. Finding your bootloader version (Windows only):

    1. Install Motorola USB drivers:
    32-bit: http://direct.motorola.com/hellomoto..._bit_4.2.0.zip
    64-bit: http://direct.motorola.com/hellomoto..._bit_4.2.0.zip

    2. Google, download and install "RSD Lite 4.5.7"
    3. Turn off phone. While off, hold down "MENU" key first and then "Power" key. Release both when blue screen appears displaying: "Bootloader USB Init".
    4. Connect USB cable to computer, then to phone.
    5. Open RSD Lite and in the "Model" section click on the phone - In my case it says "Flash MSM7201A". Look in "Device properties" to find your bootloader versions. In my case it's "v0x000518"

    6. To exit "Bootloader USB Init" mode, press the "power" key on the phone. The phone should now restart.

    Hence, my bootloader version is 05.18. This number is important in determining what firmware is compatible with your phone.

    However, one might mistakenly make the assumption when looking through the Firmware Superthread, that T-Mobile US 1.4.8 firmware is compatible since it shares the 05.18 bootloader version. Yes and no. You will be able to flash it to your Dext, but since it's 3G bands cover 900/1700/2100, you will lose your 850/1900/2100 3G bands.

    As of writing, there doesn't seem to be any firmware available, that is compatible with the Bell Mobility Dext.

    5. Understanding ROOT, Recovery and ROM:

    To flash a custom ROM to your phone, you must first flash a custom recovery to the phone. For whatever reason, Motorola has made it impossible to flash custom ROMs to it's devices out-of-the-box. The recovery - this is where you would flash new ROMs - is locked down to prohibit you from doing this. Therefore we must first flash a custom recovery to the phone - one that has been altered slightly to allow for non-Motorola ROMs and other goodness. But to be allowed to flash a custom recovery, we must first ROOT the device. So to recap:

    1. Rooting allows for user access to the system files, device partitions, etc., and is needed to change the recovery.
    2. Flashing a custom recovery makes it possible to flash a custom ROM - one that is not made by Motorola.
    3. Flash a custom ROM makes it possible to upgrade your Android system to 2.1. (2.2 Anyone?)

    More on this process later.

    After a custom recovery has been installed, you should now be able to flash ROMs to your Dext. Extreme caution should be shown here because some ROMs contain 3G radios that are intended for T-Mobile US Cliqs and EU/Asia Dexts only. Flashing incompatible ROMs and radios is the number one way to lose your 3G connectivity on your Bell Mobility Dext.

    6. Understanding the dangers - Before you flash:

    If done right, it's possible to safely root and flash ROMs to your Dext. But understand that there are always risks involved in messing with your phone's firmware as well as flashing ROMs. Be sure to read everything twice. Search, google and ask questions about the stuff you don't understand. Don't go ahead with something without fully understanding what is involved.

    Also understand that as of writing there is no stock OEM firmware available for the Bell Mobility Dext. Therefore you must be sure to backup everything yourself on your end to make it possible to unroot and go back to stock recovery and OS in case you need to send your Dext back to Bell/Motorola for repairs. And even if everything is backed up and then restored, there no guarantee that some smart Moto repair guy won't be able to see that you've messed with your device and perhaps void your warranty.

    Finally - when flashing a ROM, make sure that it is compatible with your baseband. And be extra sure that it does not contain a radio. Most ROM Devs remember to include this information in their threads, but some forget. If you flash a ROM with a radio to your Bell Mobility Dext you can be almost certain to say goodbye to your 3G.

    A note about rooting as well. Gaining root on your device means that you gain "Superuser permissions", and will have access, and be able to change system files and folders. Be careful here. Be aware of what you're doing. Make sure you backup everything before starting to delete or move things around. If you root your device and start making changes to your stock 1.5 Android system, then these changes will be permanent. They will not be undone even by resetting the phone and returning to factory settings. This is not so much an issue for T-Mobile US Cliq users because they can simply go to the Firmware Superthread, flash a stock OEM firmware and everything will be good. Currently, the Firmware Superthread only covers firmware for T-Mobile US Cliq, Telcel Mexico (AmericaMovil) Dext and Italy retail Dext. IE. - If you flash T-Mobile US Cliq firmware to you European/Asian-Pacific Dext, it will not screw up your 3G - but it will give your phone a permanent T-Mobile tan.

    7. Preparing to root your Dext:

    There are already excellent guides available on how to setup your computer in preparation for root. These cover the Bell Mobility Dext just fine. Many thanks to sublime1184 and Danation for making them available:

    http://modmymobile.com/forums/399-mo...connected.html
    http://modmymobile.com/forums/399-mo...using-adb.html
    http://modmymobile.com/forums/399-mo...d-sdk-jdk.html

    8. Rooting your Bell Mobility Dext:

    Thanks to Sebastian Krahmer at C Skills (and Skrilax_CZ for posting it), rooting your Bell Mobility Dext has never been easier or safer. Using this method there is zero chance of messing up your 3G. Simple follow the steps in this guide:

    http://modmymobile.com/forums/399-mo...-3g-bands.html

    You should now be rooted. Now we need to take some backups to make it possible to return to the stock recovery.

    9. Backing up recovery etc.:

    Using your newfound ADB skills, launch the CMD in Windows. We will now backup the boot, system, userdata, misc, recovery, cache and splash partitions on your phone. The most important one here is the stock recovery, since we will replace this in the next couple of steps.

    1. Plug phone into computer.
    2. Make sure that "USB debugging" is enabled in "Settings-Applications-Development"
    3. Make sure you have a SD card in your phone with plenty of space
    4. Open CMD or command prompt
    5. Type in:

    cd C:\wherever-your-sdk-tools-folder-is
    adb devices (to verify the connection)
    adb shell
    su
    cat /proc/mtd

    - you should now see a list similar to the one below. Note that your mtd number for boot may differ.

    dev: size erasesize name
    mtd0: 00300000 00020000 "boot"
    mtd1: 08ac0000 00020000 "system"
    mtd2: 0df80000 00020000 "userdata"
    mtd3: 00040000 00020000 "misc"
    mtd4: 00500000 00020000 "recovery"
    mtd5: 06000000 00020000 "cache"
    mtd6: 00080000 00020000 "splash"

    - Now we backup everything to the SDCARD:

    cat /dev/mtd/mtd0 > /sdcard/boot.img
    cat /dev/mtd/mtd1 > /sdcard/system.img
    cat /dev/mtd/mtd2 > /sdcard/userdata.img
    cat /dev/mtd/mtd3 > /sdcard/misc.img
    cat /dev/mtd/mtd4 > /sdcard/recovery.img
    cat /dev/mtd/mtd5 > /sdcard/cache.img
    cat /dev/mtd/mtd6 > /sdcard/splash.img


    Make sure you keep these backed up in a safe place if you decide to revert back to stock.


    tonymy01 also suggests that it's a good idea to backup the original stock prop files found in /system as well as apns-conf.xml in /system/etc. More on that in the next chapter. If you're interested in what the above mtd's contain, here's an explanation from tonymy01:

    Boot = Core operating system - Kernel & root filesystem
    System = Ancillary operating system mounted in /system, includes all stock apps, blur, binaries etc
    Userdata = User added apps, all apps data (stored settings, contact history, SMS, MMS etc)
    Cache = Section for apps to leave cached versions of them for fast load/operation (I think the davlik cache is here).
    Recovery = 2nd boot partition that can be triggered by camera key on boot, has basic linux filesystem and tools to flash updates, clear cache, clear data, etc.
    Misc = Dunno, perhaps some carrier ancillary stuff? Mine is all 1s for 50% of it and all 0s for the rest.
    Splash = Dunno, mine doesn't have a custom splash screen (has 2 zero byte partitions splash1 and splash2 looking at some old nandroid backups), but presumably you could have some other logo instead of the M on bootup (I certainly know you can have bootanimation which is part of the main filesystem, I think this splash is more for the logo that proceeds any bootanimation, by default the M for motorola).

    10. House cleaning and more backup:

    This step is possible to do with a command prompt, but I will explain it using the method that worked for me. For this you'll need to buy and download the "Root Explorer (File Manager)" by Speed Software from the Android Market - well worth the money for other uses as well.

    1. When installed, open Root Explorer. You should be prompted by the superuser app for root permissions. Allow it.
    2. (Optional) Navigate to your "sdcard". Select menu and "new folder". Make a folder for your backups.
    3. Go back to the main root of your phone - not to be confused with the actual folder called "root".
    4. Tap and hold on the file "default.prop". Select "copy". Navigate to your sdcard and folder of choice, and select "Paste".
    5. Hit back and go into the "system folder". Hit menu and "multi-select". Select "build.prop" and "default.prop", and copy them to the sdcard.
    6. Navigate back to system and then the "etc" folder. Locate "apns-conf.xml". Copy to sdcard.
    7. Exit Root Explorer.
    8. Open Android Market App. Search for and download "APN Backup & Restore". When downloaded, open the app and backup your APN's to the SD card. You may need to restore them in step 12.9.

    11. Flashing custom recovery to allow custom ROMs:

    Again - there are other ways on doing this as well as other recoveries - but this is what worked for me:

    1. Download the HandlersExploit recovery from here (Thank you HandlerExploit): recovery.img - 4shared.com - online file sharing and storage - download
    2. Connect phone to computer and mount SDCARD so that it shows up in Windows.
    3. Copy the downloaded "recovery.img" to the SDCARD.
    4. Disconnect phone from computer and launch Root Explorer.
    5. Navigate to the location on the SDCARD where you copied the "recovery.img". Tap and hold on it and select "Copy".
    6. Navigate to /system/ folder. In upper left corner select the "Mount R/W" button. Then select paste.
    7. Turn off and on phone. Let it boot up. Then turn off again.
    8. While phone is off, press and hold "power" and "camera" button.
    9. Let go of both when message "Please release camera key" appears. Next press the "Volume down" button on the phone.

    The new recovery should now be installed, showing "Android System Recovery" by HandlerExploit. Note that this will be the same procedure to follow, should you choose to re-flash the stock recovery that we backed up earlier. IE. - Place the backup stock recovery.img in /system/ folder and reboot.

    Next, we need to do a few more backups:

    While still in the "Android System Recovery":

    1. Using the "Volume up" and "Volume down" keys, select "Backup/Restore" by pressing the "home" button.
    2. Select "Backup"
    3. Go back to main menu and select "Reboot device".

    This creates a "Nandroid" backup of everything, so that we can return to the Android 1.5 ROM should it be necessary or wanted. Look on your SDCARD for a folder called "Nandroid". Back it up somewhere safe.

    12. Flashing a custom ROM w/o screwing up 3G:

    As mentioned before, you need to make sure that the ROM you flash does not contain a radio. If it does, you will be pretty sure to be without 3G. Thanks again to tonymy01 for explaining, that you can check this by unziping/unraring the ROM files and check if it contains a "radio.img" file. If it does, then it has a radio and you don't want to flash that.

    On my Bell Mobility Dext, I went with adlxmod 2.1.5. Download it from here: http://modmymobile.com/forums/548-mo...cliq-dext.html

    1. Make sure that your baseband is at least 5025 - shouldn't be a problem since all Bell Mobility Dexts are 5030
    2. Unzip/unrar the downloaded ROM and make sure it doesn't have a radio - Things could have changed since last time.
    3. Connect phone to computer and mount SDCARD in Windows. Drag and drop file to SDCARD.
    4. Power cycle phone and boot into recovery by following instructions mentioned in step 11-8.
    5. Scroll down and select "Wipe data/factory reset". Press "HOME" key to confirm
    6. Go back to main menu. Scroll down to "Choose zip to install".
    7. Select "SDCARD:adlxmod-2.0-signed.zip" or other name of ROM you wish to install. Hit "HOME" key and again to confirm.
    7.1. Apply any patches that are available. Read the instructions from the thread, from which you downloaded the ROM.
    8. Wait for everything to finish and then select "Reboot device".
    9. Let device reboot. It may display the "Motorola Blur" logo for what seems to take forever. Just be patient. If you don't have 3G Internet connectivity when you get to the MotoBlur login, it means that you need to manually set up the APN's. You can solve this in two ways:

    A: Connect to a WiFi network, login to MotoBlur or skip MotoBlur, download the "APN Backup & Restore" app from the Android store and then restore the APN's from the SD card.
    B: Press "MENU" key at MotoBlur setup, go to APN settings and enter them manually:

    Name: Bell Internet
    APN: pda.bell.ca
    Proxy: web.wireless.bell.ca
    Port: 80
    MMSC: http://mms.bell.ca/mms/wapenc
    MMS proxy: web.wireless.bell.ca
    MMS port: 80
    MCC: 302
    MNC: 610
    APN type: Internet + mms
    Authentication Type: none

    You should now have a Bell Mobility Dext with Android 2.1 and 3G. Note that it took me two ROM flashes to get it to work. After the initial flash, the phone booted up and immediately showed repeated "Force Close" messages. This will happen if you forget to WIPE in step 12.5. If you forgot, simply repeat step 12 and remember to wipe this time.

    13. ROM's without radio and safe for the Bell Mobility Dext:

    http://modmymobile.com/forums/548-mo...-motoblur.html
    http://modmymobile.com/forums/548-mo...cliq-dext.html

    - Remember to unzip/unrar and check for a radio.img. The contents the ROM may have changed. radio.img = BAD BAD BAD.

    14. How to undo everything and return to stock ROM and recovery:

    1. Turn off phone. While off, press and hold "Power button" and "Camera button" as the same time.
    2. Release both when message "Please release camera key" appears.
    3. Press "Volume down" key. "Volume down key pressed" message will appear, and you should now be in the "Android System Recovery".
    4. Select "Backup/Restore" in the menu.
    5. Select "Restore" in the menu.
    6. Select the Nandroid backup we created earlier. Let it work it's magic and reboot.

    You should now have the Bell Mobility Android 1.5 stock back. Next, we replace the HandlerExploit/simply-android.com recovery with the stock recovery:

    7. Open RootExporer - We're assuming that it's already installed, if not then reinstall.
    8. Navigate to location on SD-CARD where you backed up the recovery in chapter 9.
    9. Copy recovery to device folder "/system/". Make sure you have enabled "R/W" as mentioned in chapter 11, step 6. If there is already a "recovery.img" file in the "/system/" folder, delete that first.
    10. Exit Root Explorer and power cycle phone. After it boots up, power it off again.
    11. Boot into recovery once again - following same procedure as mentioned in chapter 14.1.

    You should now have your old stock Motorola recovery back. Next, we unroot (Method by tonymy01):

    12. Make sure that "USB debugging" is enabled in "Settings-Applications-Development"
    13. Connect phone to PC.
    14. Open Windows CMD/command prompt.
    15. Type in:

    CD C:\Wherever-Your-SDK-Tools-Folder-Is
    adb devices (to verify the connection)
    adb shell
    su (This should give you a "#" prompt)
    rm /system/xbin/su
    rm /system/app/Superuser.apk
    exit
    exit

    16. Power cycle phone.

    Done! You are now back to stock (assuming you didn't remove or alter other system files along the way).

    ---------------------------

    Files:

    Stock Recovery.img: http://www.4shared.com/file/GkpwbMQA/recovery.html

    --------------------------

    I hope this guide will be of assistance to all Bell Mobility Dext users. Please don't hesitate to correct any mistakes there may be as well as help me update the guide to make it more streamlined or easy

    --------------------------

    Got fed up with T-Mobile and AT&T, and have now switched to Virgin Mobile and the Samsung Intercept, running Android 2.1. It's not as high-end as the Cliq/Dext, but the $40/month price tag for 1200 min and unlimited data/texts makes up for that in spades. I am keeping my Dext and will continue to offer support to users of this thread.
    Attached Images Attached Images
    Last edited by njones; 11-04-2010 at 11:30 PM. Reason: Spelling & grammar, house cleaning, how to unroot, Bell Mobility APN's, adding index, more house cleaning
    Bell Mobility Dext / AT&T USA

  2. 36 Users Say Thank You to njones For This Useful Post

    adlx (09-02-2010), ahiscox (01-19-2011), Bejam (05-02-2011), bloodyshyt (12-05-2010), Citizen86 (09-03-2010), danfm97 (01-17-2011), duncanlim (09-02-2010), eafreitas (11-07-2010), Electrify85 (07-01-2011), estevan_ (09-02-2010), fedegin (09-02-2010), Geezon (10-07-2010), giqbal (10-25-2010), grmreaper (10-07-2010), ichigo27 (09-10-2010), jethro650 (10-27-2010), j_r0dd (09-01-2010), mark i (09-01-2010), Modded (09-05-2010), PurelyHybrid (05-24-2011), Pzyduck (09-03-2010), RasMouSein (12-01-2010), shoosh (10-16-2010), Skrilax_CZ (09-02-2010), spartan.tenchu (12-01-2010), Stickee (09-16-2010), sublime1184 (09-01-2010), SuperJoker (09-11-2010), sushikid (02-19-2011), talico (10-08-2010), terminator.2012 (02-17-2012), the7keys (09-24-2010), Vicntc (04-17-2011), x86Daddy (02-11-2011), Xenocide (12-02-2010), xwinx (11-08-2010)

  3. #2
    adlx's Avatar
    online Maker of adlxmod
    Join Date
    Jan 2010
    Location
    Madrid, Spain
    Posts
    1,058
    Thanks
    635
    Thanked 1,531 Times in 380 Posts
    Downloads
    30
    Uploads
    0
    Very good article!

    There is something though, I believe is otherwise: you say that "The Motorola MB200/MB220 comes in three hardware flavors".

    I'm more inclined that the difference is in the radio, but given it can be flashed it's a software difference. Hence to me all three flavours are actually the same hardware, with baseband differences to accomodate to the local carriers, and of course the carrier customizations of the OS (custom boot screen, apps, and system configurations like APN,...). This is what I believe, but I could be wrong on that.

    Once you have installed and configured ADB properly, you can use the ddms.bat to open a UI, from where you'll be able to take screenshots :-).
    Download my 1-click Recovery Flasher to flash a custom or stock recovery to your phone: Cliq, CliqXT, Backflip, ...

    Like my work? Support me: & visit my adlxmod site and follow me on Twitter
    Tambien me puedes encontrar en Movilzona (Esp)

  4. The Following User Says Thank You to adlx For This Useful Post:

    njones (09-02-2010)

  5. #3
    njones's Avatar
    offline So I Hear You Can Mod
    Join Date
    Jun 2010
    Location
    California, USA
    Posts
    103
    Thanks
    24
    Thanked 48 Times in 12 Posts
    Downloads
    13
    Uploads
    0
    Thanks for commenting - It's an interesting thought, which would basically mean that the Bell Mobility Dext users who've lost 3G by flashing to 900/1700/2100, could just pop in a Mobilicity, Videotron or WIND Mobile SIM card and then have 3G on those networks since they use same freq as T-Mobile USA?

    I have changed the wording to allow for the possibility of your theory
    Last edited by njones; 09-02-2010 at 12:58 PM. Reason: Reason
    Bell Mobility Dext / AT&T USA

  6. #4
    offline Maybe Modder
    Join Date
    Feb 2007
    Posts
    31
    Thanks
    8
    Thanked 8 Times in 8 Posts
    Downloads
    1
    Uploads
    0
    After the phone was unlocked that seems like it would be possible. I'm by no means more than a simple end-user but I wonder if there's some way to enable all the available frequencies in software (or at least a way to easily switch back & forth). Would it even be possible to compare the radio.img from both a 900/1700/2100 and 850/1900/2100 ROM (using the same 5025 version) to see if a difference could be found, or is the data obfuscated?

    Thanks again for the guide, looks like you did a lot of work on it.

    I'll be sticking with stock 1.5 until the day I see the DEXT (Canada) listing change from "Upgrade to Android 2.1 under evaluation" to "Will not have software upgrade to Android 2.1" or my warranty runs out - whichever comes first.
    Last edited by mark i; 09-02-2010 at 04:31 PM.
    Bell Mobility DEXT(850/1900/2100) on.. Bell Mobility

  7. #5
    njones's Avatar
    offline So I Hear You Can Mod
    Join Date
    Jun 2010
    Location
    California, USA
    Posts
    103
    Thanks
    24
    Thanked 48 Times in 12 Posts
    Downloads
    13
    Uploads
    0
    Thanks Mark - I actually just flashed the 5025 Italy radio on my T-Mobile Cliq (I have multiple phones) to see if I could get 3G working with the AT&T SIM card. It flashed fine, but no 3G. What you are suggesting is interesting but over my head - for now

    Both the Latin American and European Dext won't get 2.1. Only Canada and Asia-Pacific are still "under evaluation" - which to me translates into "never". I speculate that the only reason the Cliq is getting 2.1 is because of T-Mobile's importance to Motorola. I don't see 2.2 officially ever coming to any Dext or the Cliq.

    I DO very much hope that Bell Mobility will release at least one firmware fix so we can get that damn radio....:P
    Bell Mobility Dext / AT&T USA

  8. #6
    adlx's Avatar
    online Maker of adlxmod
    Join Date
    Jan 2010
    Location
    Madrid, Spain
    Posts
    1,058
    Thanks
    635
    Thanked 1,531 Times in 380 Posts
    Downloads
    30
    Uploads
    0
    Actually I remember a guy from Claro BR (3g 850) who flashed a 5025 T-mobile radio and lost his 3g . After unlocking his Dext he changed to another local carrier (I believe it was something like Oi) that was operating 3g on 900Mhz and could then get 3g again.
    Download my 1-click Recovery Flasher to flash a custom or stock recovery to your phone: Cliq, CliqXT, Backflip, ...

    Like my work? Support me: & visit my adlxmod site and follow me on Twitter
    Tambien me puedes encontrar en Movilzona (Esp)

  9. #7
    offline Itty Bitty Modder
    Join Date
    Jan 2010
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Downloads
    7
    Uploads
    0

    Congrats!

    Very good! Now you finally clean up almost all the ("RRRR") mess! (Root, Radio, Recovery, Rom).
    A just dont understand why i cant flash ROMs that doenst have radio in phones that have 5012 baseband. What make them incompatibles?

    Im in btw..

    thanks!

  10. #8
    offline Itty Bitty Modder
    Join Date
    Sep 2009
    Posts
    1
    Thanks
    3
    Thanked 0 Times in 0 Posts
    Downloads
    4
    Uploads
    0
    "My Bell Mobility Dext shows the following: 76XXC-63805030-SDCBALUM.

    In baseband terminology when looking at ROM compatibility, my baseband would be "5030". This number is important for determining which ROMS are compatible with your device."

    What i dont get is that my tmobile cliq has the exact same baseband version and its stock! never been rooted or anything. does this mean i can flash dext firmware on my cliq since the numbers are the same?

  11. #9
    njones's Avatar
    offline So I Hear You Can Mod
    Join Date
    Jun 2010
    Location
    California, USA
    Posts
    103
    Thanks
    24
    Thanked 48 Times in 12 Posts
    Downloads
    13
    Uploads
    0
    Quote Originally Posted by kiel123 View Post
    "My Bell Mobility Dext shows the following: 76XXC-63805030-SDCBALUM.

    In baseband terminology when looking at ROM compatibility, my baseband would be "5030". This number is important for determining which ROMS are compatible with your device."

    What i dont get is that my tmobile cliq has the exact same baseband version and its stock! never been rooted or anything. does this mean i can flash dext firmware on my cliq since the numbers are the same?
    The baseband version just means that you are compatible with certain ROMs and other official firmware that require you to have a minimum baseband version - Ex. ADXL requires 5025 and above.

    But as I mentioned in my guide, there are differences in the 3G bands. You have a Cliq. That's T-Mobile US. That means you have a Cliq with a 900/1700/2100 3G radio. I have a Dext - Dext can mean Euro/Asia-Pacific/Latin American/Canadian. I got it from Bell Mobility. That means it has a 850/1900 radio.

    You can install Bell Mobility firmware (if it was available) on your T-Mobile Cliq if the bootloader/baseband versions match, but if the firmware/ROM comes with a (3G) radio then you're gonna get Bell frequencies = No 3G for you.

    This guide was written specifically with Bell Mobility users in mind - fact is that Cliq users don't face the same problems and issues as the Latin American and Canadian Dext users, since all radios out there are for the Cliq - exception being the Mexico firmware (I believe that has a radio) and some Italian radio floating around - which doesn't even make sense since Italy doesn't use 850/1900.

    Cliq users have never had it easier than now. If you want 2.1 you can either just grab the "official" 2.1 from the Firmware Superthread or root using the super easy new method and grab ADLX's 2.1 ROM which doesn't have a radio.



    Quote Originally Posted by adlx View Post
    Actually I remember a guy from Claro BR (3g 850) who flashed a 5025 T-mobile radio and lost his 3g . After unlocking his Dext he changed to another local carrier (I believe it was something like Oi) that was operating 3g on 900Mhz and could then get 3g again.
    There was also that Italian radio that some LATAM users were able to use to get 3G back. But it only seems to work if you are upgrading, which is also supported by my own experiment when I flashed the radio to a Cliq but still didn't get 3G working with AT&T. The whole thing makes little sense to me, since I've been unable to find a single operator in Italy that uses the 850/1900 bands.

    Anyway - Upgrading the radio brings back 3G - downgrading does not. Does that sound like a hardware limitation to you?

    Quote Originally Posted by leogariba View Post
    Very good! Now you finally clean up almost all the ("RRRR") mess! (Root, Radio, Recovery, Rom).
    A just dont understand why i cant flash ROMs that doenst have radio in phones that have 5012 baseband. What make them incompatibles?

    Im in btw..

    thanks!
    Let's ask ADLX - What's the reason that your 2.1 ROM is incompatible with a 5012 radio?
    Last edited by njones; 09-03-2010 at 08:58 PM. Reason: Automerged Doublepost
    Bell Mobility Dext / AT&T USA

  12. #10
    offline So I Hear You Can Mod
    Join Date
    Jun 2010
    Location
    Australia
    Posts
    489
    Thanks
    17
    Thanked 125 Times in 101 Posts
    Downloads
    16
    Uploads
    0
    I think 5012 radio devices have a very old kernel to support that radio. The kernel lives in the boot image (boot partition) which 99% of the time is part of any new ROM release, and for Android 2.1, and even the t-mobile 1.4.8MotoBlur, is different to the kernel in the older devices that had 5012 radios. So the if you try to run newer kernel with the old radio, you will end up with nothing much working, and the old "alpha" patches that adumont/etc put out to allow 5012 radio people to have a play with, say, the 2.1 leak, was simply to put an old kernel into the patch. But old kernel means camera, sensors etc don't work properly, as these are all dependent on drivers compiled into the kernel. Old kernel, new system means sensors/peripherals not working well, new kernel old radio means RF not working too well (no connection to your service provider for example).
    Regards

  13. #11
    adlx's Avatar
    online Maker of adlxmod
    Join Date
    Jan 2010
    Location
    Madrid, Spain
    Posts
    1,058
    Thanks
    635
    Thanked 1,531 Times in 380 Posts
    Downloads
    30
    Uploads
    0

    Solution

    Quote Originally Posted by tonymy01 View Post
    I think 5012 radio devices have a very old kernel to support that radio. The kernel lives in the boot image (boot partition) which 99% of the time is part of any new ROM release, and for Android 2.1, and even the t-mobile 1.4.8MotoBlur, is different to the kernel in the older devices that had 5012 radios. So the if you try to run newer kernel with the old radio, you will end up with nothing much working, and the old "alpha" patches that adumont/etc put out to allow 5012 radio people to have a play with, say, the 2.1 leak, was simply to put an old kernel into the patch. But old kernel means camera, sensors etc don't work properly, as these are all dependent on drivers compiled into the kernel. Old kernel, new system means sensors/peripherals not working well, new kernel old radio means RF not working too well (no connection to your service provider for example).
    Regards
    Hey, not all my kernel patch were ALPHA and "broken" as u seem to say

    Yes, the only kernels working with 5012 are kernels base on "old" sources (yet they are still 2.6.27).

    That is there are some kernel sources that will make a kernel compatible for 5012, and the other new sources that will make a kernel compatible with all later radio.

    Motorola changed something that is kernel related from 5012 to 5025 and affect the date.

    If you flash a kernel that is not compatible with that radio you will end at 1969 or 1970. Pretty much unusable. That is what happends if you flash a new rom (say adlxmod 1.2) on an old (5012) radio.

    For Android 1.5 I could make a working patch (iirc everyth was working fine) compiling a "old" source to make a kernel compatible with 5012. This was perfect for people stuck wth 5012 radio (before we found the Italian radio was also 850Mhz), because they finally could install new 1.5 roms on their phone.

    The same way worked quite well for Eclair2Cliq which was still based on a 2.6.27 kernel (from Android 1.5 Motorola kernel sources).

    Then came the 2.1 Motorola leak, and it came with a 2.6.29 kernel, for which we still have no sources.

    The thing is that replacing the 2.6.29 kernel with a 2.6.27 kenrel compat with 5012 was not working well. The only thing that actually worked is correctiong the date bug (so you dont get stuck at 1969/70), but everything else was broken because the rom library files were all made for a 2.6.29 kernel .
    Last edited by adlx; 09-04-2010 at 01:59 PM.
    Download my 1-click Recovery Flasher to flash a custom or stock recovery to your phone: Cliq, CliqXT, Backflip, ...

    Like my work? Support me: & visit my adlxmod site and follow me on Twitter
    Tambien me puedes encontrar en Movilzona (Esp)

  14. 2 Users Say Thank You to adlx For This Useful Post

    Citizen86 (09-04-2010), sublime1184 (09-04-2010)

  15. #12
    offline Itty Bitty Modder
    Join Date
    Jan 2010
    Posts
    6
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Downloads
    7
    Uploads
    0
    Quote Originally Posted by adlx View Post
    Hey, not all my kernel patch were ALPHA and "broken" as u seem to say

    Yes, the only kernels working with 5012 are kernels base on "old" sources (yet they are still 2.6.27).

    That is there are some kernel sources that will make a kernel compatible for 5012, and the other new sources that will make a kernel compatible with all later radio.

    Motorola changed something that is kernel related from 5012 to 5025 and affect the date.

    If you flash a kernel that is not compatible with that radio you will end at 1969 or 1970. Pretty much unusable. That is what happends if you flash a new rom (say adlxmod 1.2) on an old (5012) radio.

    For Android 1.5 I could make a working patch (iirc everyth was working fine) compiling a "old" source to make a kernel compatible with 5012. This was perfect for people stuck wth 5012 radio (before we found the Italian radio was also 850Mhz), because they finally could install new 1.5 roms on their phone.

    The same way worked quite well for Eclair2Cliq which was still based on a 2.6.27 kernel (from Android 1.5 Motorola kernel sources).

    Then came the 2.1 Motorola leak, and it came with a 2.6.29 kernel, for which we still have no sources.

    The thing is that replacing the 2.6.29 kernel with a 2.6.27 kenrel compat with 5012 was not working well. The only thing that actually worked is correctiong the date bug (so you dont get stuck at 1969/70), but everything else was broken because the rom library files were all made for a 2.6.29 kernel .
    Thanks for clarifying...

  16. #13
    Modded's Avatar
    offline Itty Bitty Modder
    Join Date
    Sep 2010
    Location
    Ontario, Canada
    Posts
    6
    Thanks
    3
    Thanked 0 Times in 0 Posts
    Downloads
    2
    Uploads
    0
    Hi there... Been waiting for someone to come up with a way to upgrade this Bell phone without losing 3G as the horror stories state. Did everything to the letter (and I have the identical phone with identical baseband) but I didn't notice that I was supposed to wipe the data before flashing. Obviously after I flashed it the first time I was getting non stop FCs. That's when I read in adlxs post for burning ROMS to wipe everything so I went back to the stock ROM (without a problem, the phone was exactly the same as before I started) and then wiped and reburned the 2.0 ROM followed by the update. The phone booted perfectly after that and then it started going through the setup of MotoBlur. After that was done (through wireless internet) I realized there was no 3G symbol on my tool bar. I attempted connecting to the internet with the wifi disabled and it tells me I have no internet connection. I can phone other people no problem and I can surf on wireless but I'm not sure what I messed up. Any help?

    Thanks for all your effort guys! This is STELLAR work!

  17. #14
    offline So I Hear You Can Mod
    Join Date
    Jun 2010
    Location
    Australia
    Posts
    489
    Thanks
    17
    Thanked 125 Times in 101 Posts
    Downloads
    16
    Uploads
    0
    Either adlx's rom apns-conf.xml doesn't contain your service provider or you did muck up. You don't need to return to stock to wipe, you can do that from the custom recovery menu. Either get njones to give u his orig apns-conf.xml, or manually add an apn when you go to log into blur or from the wireless settings menu for your mobile network.

  18. The Following User Says Thank You to tonymy01 For This Useful Post:

    Modded (09-05-2010)

  19. #15
    Modded's Avatar
    offline Itty Bitty Modder
    Join Date
    Sep 2010
    Location
    Ontario, Canada
    Posts
    6
    Thanks
    3
    Thanked 0 Times in 0 Posts
    Downloads
    2
    Uploads
    0
    Awesome! I just reverted back to 1.5, no problems again, went to the APN settings and grabbed the info from there. The only difference in 2.1 was it had an added setting of "Authentication type". I ended up with it set to PAP or CHAP although I believe when I had it set to none it may have worked but I needed to reboot the phone. Everything works great now!
    I had resolved to myself I wasn't going to see the 2.1 upgrade on my phone for a while, and Motorola seemed to agree... HA to them! Now time to take some of the bloatware off this thing and make it fast.

Page 1 of 11 12345678910 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •