thank you, I've downloaded and installed the rom, faced a bootloop for 3 times, but now it's okay I guess.. I only have one question, is image CRC in bootloader menu is the boot.img ? cause the phone at first was stuck on HTC logo till I did this image crc thing. if not, please advice me. thanks again
I had a moment to make a snapshot release so here's the first beta release based on upstream M4. Nothing fancy, just different development branch. http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items
Thanks for all the contributions!
Download:
http://downloads.codefi.re/mustaavalkosta/cm-11-unofficial-ace/releases
http://goo.im/devs/Mustaavalkosta/cm-11-unofficial-ace/releases
Maybe it's only me but br1 is messed up. On each boot there's fc for phone, mms and acore and then phone is getting hot reboot. Dirty flash from 8 march nighly. Dirty flashing 0803 nightly agan helped.
Sent from my Desire HD using xda app-developers app
CM 11 M# releases are a code path that lags behind nightlies.
This means a few things:
-Nightlies have newer code than the M-releases
-You should be extra careful flashing an M build on top of a new nightly due to #1
In Practice
As the Ghostbusters would say, “Don’t cross the streams”. While this isn’t a hard-stop rule, it is still very apt advice to take into account. Let’s give you a real-world scenario.
M4 was branched for release last week – let’s use an easy date and say February 28th. This means all the code that exists in the stable/cm-11.0 branches on Github contain code 8 days old, with only bugfixes placed on top (or unstable features removed). This also means that any change merged in the last 8 days to the master ‘cm-11.0′ branch is not captured in the branch for M4. On March 2nd, we merged in some relatively sweeping telephony changes based on QCRIL (Qualcomm specific radio code) and the beginnings of Multi-SIM phone support. If you are using a nightly from March 2nd to today, you have this new code. If you flashed M4, you don’t. Simple enough right?
But what happens if you are on nightly March 7, for example, and then flash M4? In terms of code, you have just downgraded. Downgrading can be perfectly benign, or flat out make your phone unbootable. In the QCRIL example, if you downgraded you would see broken phone calls and radio behavior. This is one of the many reasons veteran users advocate making a backup before making any changes, and we’d echo that advice.
What BR stands for?
I'm going to clean flash it, hopefully it will work well for me :fingers-crossed:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
fastboot flash boot boot.img
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon