DROIDX2 Receives 2nd-init Support, Full Custom ROMs Potentially on the Way

Remember the breakthrough that allowed the flashing of CM7 onto the DROIDX back in June?  It looks like that same method (2nd-init) could potentially work on the DROIDX2 as well, opening up this device to some pretty fun times.  Everything was pulled from the Atrix’s 2nd-init and is still very beta at this time, so we’re not suggesting that just anyone go out and start playing around with this.  The best thing you can do is start talking about it (a lot), ask your favorite devs to take note of it, and then watch the magic happen.

More info at this XDA thread.

Cheers Adam and Thomas!

CM7 Nightlies Go Live For The DROIDX

If anyone was excited for the official release, then you should be just as excited for the release of CyanogenMod7 nightlies for the DROIDX. Anyone experiencing problems with the first build, should be reassured that all those bugs will get hammered out in some of these nightly builds. And even better is the fact that @cvpcs, the developer responsible for all this, has been amazingly kind and wrote out exactly what to expect from these builds. You can always grab nightlies on your DX from the CyanogenMod official site, or if you have Rom Manager Premium installed on your device – check there first.

In order to see the nightlies in RM you’ll need to do the following:

1.  Open RM Premium and hit the “Flash ClockworkMod” button.
2.  When prompted, choose the “Droid X (2nd-init) recovery.”
3.  Once that flashes, you’ll be able to view nightlies under “DownloadROM.”

So how excited are we all for this? Time to start squashing bugs.

Via:  @cvpcs

CyanogenMod 7 Finally Makes Its Way Onto the DROIDX (Updated)


No, that’s not a misprint in the title.  Our buddy @cvpcs has finally done what many considered to be impossible – he’s successfully ported/installed/awesomed CM7 onto the DROIDX.  A device that has seen developer almost come to a halt due to limitations may have a second life that is only getting started.

Back in January when he announced through Droid Life that he would be joining the CyanogenMod team, one of his goals was to get the DX into the CM family; it appears now as if we are closer than ever.  So how did he do it?  I’ll one quote from his post on the matter:

…this was done using my recently new-found-knowledge of 2nd-init, which I will describe later in a blog post (don’t want to get into it here). This still runs on top of the original motorola kernel though. I repeat, the bootloader is still locked, and you are still forced into using moto’s kernels, but that doesn’t really prevent us from doing all that much. 😀

While “2nd-init” means nothing to me, it sure sounds like the breakthrough that we’ve all needed in order to take DX development to the next level.  We’ll be eagerly awaiting his explanation.

…no, this means we are able to restart init and run a clean system using the currently existing kernel

Oh, he also plans to open up a testing period in the very near future, so stay close as we’ll definitely have more on that.  For now though, please let your feelings be known to the world – how does CM7 on the DX sound?

Update:  CVPCS offered some additional details in the comments to help clear up any confusion on the white M logo and whether or not this is Gingerbread:

Ok there seems to be some confusion.  CM7 is gingerbread.  it always has been gingerbread.  it always WILL be gingerbread.  The reason there’s a white moto logo is because it has to boot off of the 2.6.32 kernel which shipped with froyo.  That does NOT mean that it IS froyo.  That just means that it’s the 2.6.32 kernel instead of the 2.6.35 kernel that shipped with gingerbread.  This is NO way affects gingerbread, as the D1 is currently running gingerbread off of a .32 kernel as well.  Hopefully that will clear up some confusion.

Via:  RootzWiki

Cheers zepfloyd, Daniel, James and everyone else!