[ROM] CM 11.0 (Android 4.4) for AtrixHD

Search This thread

epinter

Inactive Recognized Developer
Feb 26, 2011
906
7,347
Sao Paulo
www.linuxmobile.org
This is a CM11.0 (Jelly Bean, Android 4.4) ROM for Atrix HD.

I'm not responsible by phone bricks of any kind, or any other damage this firmware may cause to you, to your phone or any accessories conected to your phone.

This rom should work with a unlocked bootloader.

DEVELOPERS (razrqcom-dev-team):
EPinter - Kernel Development, Build Setup, XT925 & MB886 Support
DHacker - Kernel Development, Build Setup, XT926 Support
Hashcode - Kernel Development, Build Setup, XT926 Support
Nadlabak - Kernel Development, Build Setup, XT897 Support
Skrilax_CZ - Kernel Development, Build Setup, XT897 Support


Download links and information about what is working can be found on the website:
http://www.linuxmobile.org/razrhd/cm11

Instructions:
Download the zip (cm-11-*-UNOFFICIAL-epinter-mb886.zip) and copy to your sdcard.
Boot into recovery.
Backup your firmware and data!
Format /system.
Install the firmware (install zip from...).
Install gapps (install zip from...).
Wipe data/cache
Reboot.

Developers builds:
Epinter: http://goo.im/devs/epinter
DHacker: http://androidhosting.org/Devs/Dhacker29/
 
Last edited:

jpcdeux

Senior Member
Mar 26, 2010
3,662
885
Laporte, IN
Scroll down for actual zip! Link towards top gives 404 error if (like me) you dont pay attention

Fair warning: This has NONE of the usual CM customization...
 
  • Like
Reactions: jasherpowers

TecknoFreak

Inactive Recognized Contributor
Can ART be enabled on any future CM roms? My guess would be no..?

Sent from my MB886 using XDA Premium 4 mobile app

If you flash dhacker gapps from link below yes you can enable Art. It runs a bit faster as I noticed and no errors.


I been running this since last night and i see it runs good.

This is a report i can provide since testing this rom for over night.

Clean flashed MB886 11/12/2013 Build.
Flashed latest ART-Compatible-Gapps-dHacker29.

Switched to ART. Reboot took a while as expected.
  • Same transition bug as in a few builds earlier on cm10.2
  • Plenty of Interface-related settings are missing
  • Video streaming services don't work on Hi Def videos
  • MXPlayer complains it can not play video using HW / HW+ video decoders, only SW decoder works
  • Front camera isn't working.

External SD card is there. :good:
But is NOT writing still :silly:


A probable side effect of ART: can't get root any longer

FIX:

How to maintain root using ART\-_-/DALVIK

1. Make sure your currently in dalvik mode.
2. Download SuperSU
3. Update the binary
4. Check it's option for "survive OTA"
5. Reboot using ART mode
 
Last edited:

TecknoFreak

Inactive Recognized Contributor
Ok after many tries on Art and going back to Dalvik. I can say I totally lost root with no way to re-root the device again. I have tried zip files, motochopper, Myth Tools etc... and no root eventhought it does flash superuser. I guess I will go back to AOSP for now

Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
 
  • Like
Reactions: harsho1

penser

Senior Member
Jan 17, 2013
619
112
Was the TiBu writing to external SD fixed in this?

Sent from my MB886 using Tapatalk
 

jram0421

Senior Member
Dec 22, 2012
284
104
San Diego, CA
Ok after many tries on Art and going back to Dalvik. I can say I totally lost root with no way to re-root the device again. I have tried zip files, motochopper, Myth Tools etc... and no root eventhought it does flash superuser. I guess I will go back to AOSP for now

Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Did u try to reflash the su binary?
 

sickkside13

Senior Member
Jul 15, 2012
1,076
1,013
Chicago
Front camera and video playback seems not to work and a few apps like xda premium don't work neither but overall really good
 
Last edited:

penser

Senior Member
Jan 17, 2013
619
112
So have you guys seen the news about CM Installer? I'm gonna try it out just for kicks in a few minutes. Doesn't say AHD is supported by the Installer but it's worth a shot.

EDIT: After asking for USB Debugging permission it says device not supported.
 
Last edited:

TecknoFreak

Inactive Recognized Contributor
Something odd, front camera works in Snapchat app but not Instagram or stock camera

Sent from my MB886 using xda app-developers app

This is a lib file error which im trying to make a fix for camera to work correctly

Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
 

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    This is a CM11.0 (Jelly Bean, Android 4.4) ROM for Atrix HD.

    I'm not responsible by phone bricks of any kind, or any other damage this firmware may cause to you, to your phone or any accessories conected to your phone.

    This rom should work with a unlocked bootloader.

    DEVELOPERS (razrqcom-dev-team):
    EPinter - Kernel Development, Build Setup, XT925 & MB886 Support
    DHacker - Kernel Development, Build Setup, XT926 Support
    Hashcode - Kernel Development, Build Setup, XT926 Support
    Nadlabak - Kernel Development, Build Setup, XT897 Support
    Skrilax_CZ - Kernel Development, Build Setup, XT897 Support


    Download links and information about what is working can be found on the website:
    http://www.linuxmobile.org/razrhd/cm11

    Instructions:
    Download the zip (cm-11-*-UNOFFICIAL-epinter-mb886.zip) and copy to your sdcard.
    Boot into recovery.
    Backup your firmware and data!
    Format /system.
    Install the firmware (install zip from...).
    Install gapps (install zip from...).
    Wipe data/cache
    Reboot.

    Developers builds:
    Epinter: http://goo.im/devs/epinter
    DHacker: http://androidhosting.org/Devs/Dhacker29/
    8
    CM12

    Little Off-Topic

    This CM12 build is specific for MB886. Nobody from our team has a MB886 to test, so we will need somebody to test. I strongly recommend a full backup(including media).
    https://goo.im/devs/epinter/cm-12-20150217-NIGHTLY-mb886-epinter.zip
    7
    The epinter JB bootloader 7/28/14 build is still working great for me and there seems to be other good news for the jb bootloader people. Citing arrrghhh at http://xdaforums.com/show...&postcount=574 who cites kabaldan at http://xdaforums.com/show...&postcount=405, and a peek at change logs http://review.cyanogenmod.org/#/c/69482/ sounds like good things for JB bootloader folks. I'm not sure if this means separate builds for JB bootloaders or some compatibility flexibility in the installation (if that is even possible) but the Carbon thread mentions bi-weelky builds that would be separate.

    Everyone with JellyBean firmware/bootloader should use moto_msm8960_jbbl builds. Users who updated to KitKat firmware/bootloader need to use the moto_msm8960 builds. Thanks to kabaldan for setting up the build.
    6
    It's not newest. It's 11/21.

    Anyone have a mirror for the newest nightly? Goo isn't working

    Sent from my MB886 using Tapatalk

    Here (dropbox):
    11/24:cm-11-20131124-NIGHTLY-mb886-epinter
    11/25: cm-11-20131125-NIGHTLY-mb886-epinter MD5: 8E329B39B56D1D589E51DD52E42113B2
    11/27: cm-11-20131127-NIGHTLY-mb886-epinter
    5
    Not asking for ETAs, not pushing anything, but just a question... Any chance that we will get Lollipop by christmas?

    Zero. Zilch. A big 'ole goose egg.

    Take a look at the JBBL Github page.... There isn't even a CM12 branch yet. It's possible that kaldaban is testing/developing JBBL privately, but I wouldn't hold my breath for a xmas miracle. I doubt dhacker would even bother with JBBL, and Epinter has no commits since January, so we're effectively down to only two MSM8960 heavy lifters. For JBBL, it's just Kaldaban as a one-man team (with an occasional contributor here or there).

    Some oceanside-dwelling users would have you believe that getting LP is trivial, our device can easily run it, we don't even need the KK bootloader, just look at the A4G! Ah yes, but such claims ignore the realities of having "super" developers (i.e. giants whose shoulders all of our ROM builders stand upon). The A4G has Quarx. We lost Hashcode and (ostensibly) Epinter. Dhacker had conflicts and quit CM, but then he unexpectedly came back and single-handedly brought CM12 to KKBL. Kaldaban seems to be another one, but who knows how much longer CM12 would have taken if it wasn't for Dhacker. And now everyone wanting JBBL LP is waiting on kaldaban (one guy!) to do the immensely difficult task of figuring out how to remove and work around all of the KKBL-dependent code in CM12.

    So in conclusion, don't go around asking what's taking so long, making comparisons to other devices, or talking about porting CM12/KKBL to JBBL like it's some walk in the park for the "devs." I'll bet that many users didn't even know about our current developer situation! Be respectful, patient and grateful that they're even doing this. Without their device trees, the non-CM ROM builders wouldn't be able to do anything! Oh, and you can't forget about Dan Rosenberg for the bootloader exploit unlock.