[UPDATED 4/20][ROM]CyanogenMod 7.2.0-RC1 X2 [BETA]

Search This thread

spdsl

Member
Thank you both. That iso disk (ezSBF 2.3.4 and root for DX2) was a easy way to flash to 2.3.4... My wife's phone is currently running dragonzkiller cm7, but I've been looking at the Eclipse thread and I think I'm going to head on over there and flash that rom. Reason being it seems to be more active and up to date. Dragonzkiller has his hands full with CM10. No dis-respect to Dragonzkiller. His CM7 rom kept my wife's phone from going in the trash. :good:
 

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,650
2
9,290
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
don't use the ezSBF's root, it's zurg rush, and 2.3.5 ota update will fail
fine if staying on 2.3.4, but eclipse is flashed on 2.3.5

---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------

use pete's to root 2.3.4 and use voodoo root keeper
or flash 2.3.5 sbf with rsd lite and root with magic md5 root

---------- Post added at 06:29 PM ---------- Previous post was at 06:28 PM ----------

links in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
 

spdsl

Member
After reading your suggestions and going over the eclipse install I think I will stay with what I know... CM7 ...... Problem is I ran into a problem with Moon shadows root. For some reason busybox does not appear in my applications. I see that it installs when I run the batch file in the cmd box but after the reboot I only see the superuser and cm7 recovery apps ?
 

jsgraphicart

Senior Member
Nov 25, 2011
6,292
1,880
OnePlus 7T
After reading your suggestions and going over the eclipse install I think I will stay with what I know... CM7 ...... Problem is I ran into a problem with Moon shadows root. For some reason busybox does not appear in my applications. I see that it installs when I run the batch file in the cmd box but after the reboot I only see the superuser and cm7 recovery apps ?

I dont think busybox actually installs as an app in your app drawer. If I recall, I have never seen it like that unless you install it from the Play Store. But it has always been there for me. I know this because using the supercharger script, it checked for it and told me I had it.
 
  • Like
Reactions: bad bone

bad bone

Senior Member
Oct 24, 2012
400
121
There are two apps on the play store 1 by jrummy the other by Stephen busybox installers download one or both and then you will be able to see your busybox and update you will not find it in your app drawer but you will be able to use through te or adb

don't be scared it's only a phone :)
ogd x d2g x2 sg3
old ladies :( ^
 

bad bone

Senior Member
Oct 24, 2012
400
121
Yes we did and thanks for all your work on the dx2,x,d2,etc... and your tutorials:thumbup:
Buy the way have you tried using the md5 iso on 2.3.4?

don't be scared it's only a phone :)
ogd x d2g x2 sg3
old ladies :( ^
 
Last edited:

spdsl

Member
All done and all is fine. I had to start over because the cm7 recovery app was not working. For some reason when I used (ezSBF 2.3.4 and root for DX2) the market would not show me busybox and cm7 recovery was not working. The phone would reboot when plugged into the charger but it would get hung up on the Moto icon. I started over and used the sbf method from the install instructions on the first post of this thread. Once I used the other sbf method I was able to install busybox from the market, give it supersuser permissions and then the cm7 recovery/restore app started working.

Thank you all.
 

Juice3250

Senior Member

appl3mac

Senior Member
Sep 12, 2011
135
49
I edited the xml file in the framework here's the link and something I've been playing with, with Ninja morph I no longer have a computer it took a crap on me. So all theming is all done on my phone :confused: one false flash and no way back thank god for rerecovery. Thats why I haven't tried JB. Btw my theming comes from several themes I pick apart as to no I am not able to edit the pics myself.

https://dl.dropbox.com/u/97176432/Cm7SBSoftKeys.zip
 

Attachments

  • uploadfromtaptalk1359592675400.jpg
    uploadfromtaptalk1359592675400.jpg
    60.6 KB · Views: 301
Last edited:
  • Like
Reactions: bad bone

bad bone

Senior Member
Oct 24, 2012
400
121
I edited the xml file in the framework here's the link and something I've been playing with, with Ninja morph I no longer have a computer it took a crap on me. So all theming is all done on my phone :confused: one false flash and no way back thank god for rerecovery. Thats why I haven't tried JB. Btw my theming comes from several themes I pick apart as to no I am not able to edit the pics myself.

https://dl.dropbox.com/u/97176432/Cm7SBSoftKeys.zip

uploadfromtaptalk1359595872377.jpg:(

don't be scared it's only a phone :)
ogd x d2g x2 gs3
old ladies :( ^
 

Top Liked Posts

  • There are no posts matching your filters.
  • 192
    dragonzkiller proudly presents:
    CyanogenMod 7.2.0-RC1 X2 BETA
    See Downloads Section​

    IC3iE.png
    815jX.png
    wZ18R.png


    d82ue.png
    cxpEU.png
    4PAPq.png


    Album Here: http://imgur.com/a/c6d3l#0

    Thanks to mastafunk for getting some of the hijack and 2nd-init issues worked out. Hashcode who has been a HUGE help getting the init binary users and telephony working. And definitely a huge thanks to MoonShadow-NM for being my guinea pig and helping me work out the kinks. Also a big thanks to ej1911 for pointing out the sdcard fix I missed!

    Features include (but not limited to):
    THE FIRST MOTOROLA DROID X2 ROM WITH ABSOLUTELY NO BLUR AT ALL! FULLY AOSP BASED
    Super fast! Like BLAZING fast!
    Full Theme Support For Every Aspect of Your Phone
    Incognito Browser Mode
    DSP Equalizer - Custom EQ settings for headset, bluetooth, and phone speaker
    Lockscreen Customizations
    Lockscreen Gestures
    Fully Customizable Pull Down Toggles (This includes a camera LED flashlight!)
    Swipe Away Notifications
    Removable sdcard is named sdcard (for compatibility)
    Internal memory sdcard is named emmc
    And MANY MANY MORE!


    How to install CM7 (Cyanogenmod) for the Motorola Droid X2.

    Please note that with all ROMs, you have the possibility of bricking your phone. Use caution and ask questions! I, dragonzkiller, am NOT responsible for what you choose to do with or to your phone!

    YOU MUST BE ON Gingerbread 2.3.4!!! This is the only version I will support! I have implemented a method to check for what version in the install, so you'll know. If you have ever upgraded to 2.3.5, you must SBF back to 2.3.4 as this check checks the kernel. This is the second BETA release, so that means most of the issues have been fixed, however there may still be problems! Please let me know what problems or issues you run into so I can address/fix them.


    Now, onto the good stuff! It MUST be done in this order!

    1. NANDROID BACKUP!
    2. SBF to 2.3.4 unless you are already there. See MoonShadow-NM's guide: HowTo: Perform a SBF ("factory restore") of your Motorola Droid X2
    3. Root your Motorola Droid X2. See MoonShadow-NM's guide: HowTo: Root your Motorola Droid X2 - UPDATED [14DEC2011]
    4. Install the Motorola Droid X2 Bootstrap Recovery (BSR). See MoonShadow-NM's guide: HowTo: Perform a bootstrap (or nandroid) backup and recovery of your Droid X2
    5. Put the Google Apps zip, the CM7 zip, and my patched BSR apk on your EXTERNAL sdcard.
    6. Boot into BootStrap Recovery. (You should know how to do this... See item number 4 above as a reference.)
    7. Install the CM7 zip.
    8. THEN the Google Apps Zip.
    10. IMPORTANT! Wipe data and cache (factory reset) and wipe dalvik cache!
    11. Boot your phone into CM7. (You will probably have to activate if you didn't after you SBF'd and setup your Google account here.)
    12. Install the patched Motorola Droid X2 Bootstrap Recovery (BSR). (This can be found in the download section of this post. Once you have CM7DX2 installed, you MUST install this BSR!)
    13. Go into the Superuser app and update the su binary.
    14. Go into the Android Market and update the apps on the phone. Keep in mind that once you update the Superuser app, you cannot update the su binary. (Looking into this, however, it might be a Superuser issue and not a CM7 issue.)
    15. Sit back and enjoy CM7 on your DX2!
    16. Never user RomManager! (Yes it's included, but that's a CM7 thing and won't work with the DX2.)
    17. NEVER DELETE ANYTHING FROM PREINSTALL! The hijack requires files in there that are installed with the BSR. I don't know why any non-dev would be messing with those files anyway.

    NOTE: If you get a hang on the M after the Google Apps Zip is flashed you didn't follow these steps. But you DON'T have to SBF! Try getting into stock recovery by having the phone off, pressing the Vol Down and Power Buttons until the "Fastboot" appears on your screen, scroll DOWN until you see the "Android Recovery" and press Vol Up. You will then see an android with an exclamation point. Press BOTH volume buttons and scroll down to "Wipe Data." Press the power button to select it and scroll down to "Yes" and select that. Then reboot and WAIT! The initial boot takes the longest. If this still doesn't work, THEN SBF and follow the directions above EXACTLY.

    Using the Patched Bootstrap Recovery With CM7DX2
    In order to get into recovery with CM7DX2 you ABSOLUTELY MUST download the patched BSR APK located in the download section of this post! There was a problem with the "hijack" name. It is conflicting with the CM7 hijack. NEVER install the original BSR while in CM7DX2! This is a guaranteed way to boot loop your phone! It might not boot loop the first couple of reboots, but it will... Eventually!


    FIXED ISSUES!
    init no longer hogs 100% of a core
    Bluetooth WORKS!
    DSP Manager WORKS!
    Torch (flashlight) WORKS!
    Google Voice WORKS!
    Dock Settings Re-Added
    Battery Fix (battery files from 2.3.3)
    Both SD Cards work
    WIFI and USB Tethering WORKS!
    WIFI sleep issue MIGHT be fixed in Beta 2
    Updating SU binary WORKS! (After update from Play Store)

    Known Issues!
    WIFI might still have some sleep issues. If this is the case, I'll look into it later.


    Currently Disabled Features (Because we don't support them)
    Reboot Recovery
    Reboot Bootloader
    HDMI - There is no native code for HDMI in CM7, so this probably won't be fixed.
    FM Radio - For now. Might be a fix later.

    This post will be updated as time goes on.

    DOWNLOADS:
    Put these on your EXTERNAL sd card.
    Patched BSR APK for ALL versions of CM7DX2
    Google Apps (Play Store, YouTube, etc.) MD5 Sum: 1647897d8ac3efb04723d2ad2c361a3f

    REFLASH THE GAPPS AFTER UPGRADING IN CASE OF FACTORY RESTORE
    Cyanogenmod 7 for the Motorola Droid X2 - BETA 2 MD5 Sum: a92b8bce58c92f6893c8c6e9881e6421

    Donations are appreciated, but not required. Buy me a sandwich or gas money to visit my family by clicking the donate link by my name. :)

    Bugs may be reported in this thread. It also would be a good idea to try to catch me in IRC at irc.freenode.net in the #cm7dx2 channel. You can also use the web IRC interface at http://webchat.freenode.net and join the #cm7dx2 channel. (Note that this is no longer #x2-aosp).

    Change Log

    update-cm-7.2.0-RC1-daytona-beta2
    updated to RC1
    included all fixes in one update

    update-cm-7.2.0-RC0-daytona-beta1 tethering patch 2
    fixed BT issues from bad init.rc

    update-cm-7.2.0-RC0-daytona-beta1 tethering patch
    added USB and WIFI tethering capabilities
    also fixed CM7 BSR (should work on stock, but untested)

    update-cm-7.2.0-RC0-daytona-beta1
    Cyanogenmod 7 beta released!
    Bluetooth is FIXED!
    DSP Manager is FIXED!
    Google Voice works!

    update-cm-7.2.0-RC0-daytona-alpha1
    Cyanogenmod 7 working on the Motorola Droid X2! - First public release
    Issues with several items:
    No bluetooth
    DSP Manager force closes when setting more than one EQ setting
    Google Voice force closes
    No HDMI
    No FM Radio
    14
    reserved for updates
    11
    Update to RC1 posted
    10
    Your mistake was assuming he was 'complaining' instead of merely reporting. Tone is difficult to convey on the internet and your writing style clearly differs from his so to prevent future confusion, do not mistake a curt reply for a complaint.

    Kill this already before a moderator does! Just sit back relax and wait for beta. I know every one is all pumped up but "can't we all get along" please no more on this. Even now I am adding to the cludder. Go watch dragonzkiller twitter and wait :)[COLOR="Silver
    10
    hey moonshadow, are you actually testing dragonz cm9? just wanna know how progress is going since hes been pretty quite on twitter :p

    I was testing the first pre-alpha build. That was before DZK's classes became a bear. Since then (about 2 months ago roughly), he is concentrating on his classes. As soon as things lighten up for him (read: probably summer break) he will probably pick things back up. I talked with him last night and he is still committed to CM7DX2 and CM9DX2. Something else that will help, I have a new laptop (Linux) that I can begin helping him out (as much as I can with my limited knowledge). All we are asking is patience. We both understand that everyone with a DX2 wants the rebase of CM7 and the release of CM9. With CM9 though, there are going to be some major hurdles that will have to be overcome since CM9 is a complete code re-write and the fact that CM9 is based on ICS AOSP. ICS does things much differently than Gingerbread.

    For those who are new to the DX2 community, welcome! Also, when DZK went to work on CM7, he had the Alpha build out in roughly a week and the stable RC release about 3 days after that. He is a committed DX2 developer and wants to provide a smooth, working, and as close to flawless, CM9 ROM as possible.

    For those that are chomping at the bit for CM9, think about this. Would you rather have CM9 in a pre-alpha state that DOESN'T work and just looks pretty, or would you rather have CM9 in a WORKING state? Personally, I would rather have CM9 in a working state.

    The pre-alpha that I was testing had MANY problems. During the time that he did put into it, before school became a bear, he was able to address a good number of the items on the "does not work" punch list.

    For everyone in the DX2 community, thank you for your support and understanding.

    Ciao!

    ---------- Post added at 10:45 AM ---------- Previous post was at 10:42 AM ----------

    That sucks cause I've changed Roms before and I have been able to transfer everything. But I like this rom just can't figure out why I can't see the folder for the drag racing

    Make sure it is NOT installed to run off the SDcard. It puts those files into a "file system folder". Essentially, it's a pseudo partition contained within a file. You should be able to use the CM7 Application Manager to move it from the SDcard and back to /data. Hope that helps.

    Ciao!

    ---------- Post added at 10:50 AM ---------- Previous post was at 10:45 AM ----------

    Solved my problem....but I have another question, how many people use task killers? Do you find them effective? I just deleted mine and an going to see what it is like to not use one

    Don't use task managers with CM7. There is a built in feature that allows you to purge assets to free up space. Also, task managers on Gingerbread and newer do not work. They kill the task alright, however, the Android OS will RESPAWN the task. This is a FEATURE that was build into Gingerbread to allow Android to manage the memory within the device and it works VERY well. I have a BOATLOAD of stuff running on my phone and I NEVER have less than 45MB free memory.

    To configure the built in asset manager within CM7, do this: Menu -> Settings -> CyanogenMod Settings -> Performance and check Allow purging of assets.

    Ciao!