[ROM][SOURCE] CyanogenMod 11 [3/25/2016][STABLE]

Search This thread

dcfgfs

Member
Jun 27, 2015
8
2
Please go to recovery and choose format "/data and /data/media (/sdcard)". Don't just format /data, it is not enough.

I've tried to format all the partitions. But the data partition data is empty. Then I try to use OTG to transfer the firmware. There will be an error after the brush into the firmware.:(

There will be an error in the two position. One is "setting - security" Another is to insert the SIM card into the phone after the systemui error.:(
 
  • Like
Reactions: jianC

jianC

Senior Member
Sep 3, 2013
87
104
Please send me a logcat.. I would really like to help you fix the issue but I need to know what is causing it from the log messages. Also, I would recommend you to use adb sideload to flash the firmware("ROM") instead of transferring with OTG.

Again, to save the logs that I need:
Code:
adb logcat -d > logcat.txt
and attach the logcat in the post. Thanks.
 
Last edited:

dcfgfs

Member
Jun 27, 2015
8
2
Hello, I brought a good news.
I just try to use moonshine success unlock my mobile phone. (s-off)
I reinstall the firmware, you provide error happened the other day all have no.
Thank you very much for your pay, I will always pay attention to update this thread.
 
  • Like
Reactions: jianC

damir_nis

Senior Member
Jul 24, 2010
94
10
Hi everyone, i need some info on installing kernel and CWM as my phone is stuck on boot and i can only access original recovery.

so my question is can i flash custom recovery without S-off, and what should i do first kernel or CWM or some other step. i also need to make my external usb work so that i can try and side load all of this.

Thank you for support
 

damir_nis

Senior Member
Jul 24, 2010
94
10
Well I don't know is this forum still active. As my wife's phone stopped working I had to do something about it.

So I have started from scratch and managed to install fully working rom by first downgrading and switching to S-OFF. And installing CWM and side loading the room with USB stick.

As what I have noticed in two days phone works great and the battery time for normal usage is so far 13h and I am still left with 20%. haven't noticed any glitches or anything not working. I didn't understand what does the DSP and AMP stand for but external speakers work great. And the call speaker works great. I still haven't tested Bluetooth and NFC as I have nothing to test it with. (If anyone would like me to test it please tell me what.

Only small glitch I have noticed is that Google acc says it is not syncing but when I go to check what is not synced everything is fine.

Would like to test ART runtime but would like to know has anyone tryed it?

If anyone has any additional questions please ask?

All the best and thank you for great work.
 

damir_nis

Senior Member
Jul 24, 2010
94
10
Add-on to previous comment here is the screen shoot of the acc sync glitch. But when I go in everything is fine. Not bothering me. Thank you
 

Attachments

  • Screenshot_2016-05-22-23-49-25.png
    Screenshot_2016-05-22-23-49-25.png
    88.5 KB · Views: 83

jianC

Senior Member
Sep 3, 2013
87
104
ART is not supported. I tried using it and it is very very buggy. As for your google account issue, I doubt I can do much about it as I haven't experienced the issue myself and you didn't provide a logcat.

I'm glad you like the rom :)
 
  • Like
Reactions: damir_nis

devtee

Member
Mar 9, 2016
5
2
It seems like I have the same or similar sync problem.
My Google Account doesn't sync automatically however syncing manually works most of the time. This is hopefully not related to my specific account since it works without problems on a different device.
Other accounts (non-Google) don't seem to have this problem. I can get notifications for emails from my exchange account but to see whether I have received new mails in gmail, I have to open the app first.

Toggling sync and checking each item inside the Google Account one after another for inclusion into the sync process, has resulted in the sync status icon turning green at least once.

I have only tried it with some opengapps packages (nano and pico; later upgraded to micro).

Could you also update the recovery img link? The one linked here doesn't seem to contain the fix for the corrupted offmode charging images. Sorry I should have used the search function, recovery seems to have its own thread.

Except for the sync problem, everything else seems to work perfectly, you've done a great job.

Logcat from adding account and first sync:
https://gist.github.com/dev-tee/ccdeb10b469d80f5c2505ed955bc60c8
 
Last edited:

damir_nis

Senior Member
Jul 24, 2010
94
10
ART is not supported. I tried using it and it is very very buggy. As for your google account issue, I doubt I can do much about it as I haven't experienced the issue myself and you didn't provide a logcat.

I'm glad you like the rom :)

Thank you for the great build the Google sync is syncing for me with no problem it is just showing like it is not. If you would like to check that out I don't mind making a log. As long as someone explan how to do it. But I am not worried about it.

Thank you one more time
 

jianC

Senior Member
Sep 3, 2013
87
104
It seems like I have the same or similar sync problem.
My Google Account doesn't sync automatically however syncing manually works most of the time. This is hopefully not related to my specific account since it works without problems on a different device.
Other accounts (non-Google) don't seem to have this problem. I can get notifications for emails from my exchange account but to see whether I have received new mails in gmail, I have to open the app first.

Toggling sync and checking each item inside the Google Account one after another for inclusion into the sync process, has resulted in the sync status icon turning green at least once.

I have only tried it with some opengapps packages (nano and pico; later upgraded to micro).

Could you also update the recovery img link? The one linked here doesn't seem to contain the fix for the corrupted offmode charging images. Sorry I should have used the search function, recovery seems to have its own thread.

Except for the sync problem, everything else seems to work perfectly, you've done a great job.

Logcat from adding account and first sync:
https://gist.github.com/dev-tee/ccdeb10b469d80f5c2505ed955bc60c8

Thanks for the feedback and the logcat, I'll look into it.

Thank you for the great build the Google sync is syncing for me with no problem it is just showing like it is not. If you would like to check that out I don't mind making a log. As long as someone explan how to do it. But I am not worried about it.

Thank you one more time

Which gapps build (pico, nano, micro, etc) are you using?
 
  • Like
Reactions: devtee

damir_nis

Senior Member
Jul 24, 2010
94
10
Hi guys i am having a problem, when i am in a call it starts cutting conversation every second or so for a second. Did anyone experience something like this?

Edit: found out it is a network problem.
 
Last edited:

devtee

Member
Mar 9, 2016
5
2
Just wanted to report that my problem seems to be gone for now. After resetting, reflashing and trying a fresh install of opengapps again I've switched to the base-package from Delta Gapps and google sync as well as gmail push notifications seem to work correctly (for now at least).
 
  • Like
Reactions: jianC

devtee

Member
Mar 9, 2016
5
2
Could it be possible that it's hard to revert to stock after flashing this rom?
I don't seem to be able to get the stock rom to boot even after ruu. I seem to always get a bootlop.
Could this be caused by differing partition layouts? Is it even possible that this rom interferes with reverting to the stock rom?
Your cm11 still works without a problem, that's why I was thinking maybe there is a connection.
Or is it just me?

Edit:
Just for clarification: I was trying to remove the simlock and it seemed like I needed a stock or Sense based rom to do that. In the end I managed to do it with JMZs Sense rom after ruu and also flashing the corresponding kernel as well. Initially I thought that since I had an unlocked bootloader and was s-off as well, everything would be flashed automatically without me having to flash anything manually (for example the boot.img).
Was that assumption incorrect?

PS: I hope that wasn't too offtopic, but it has something to do with this rom since it was the only one that worked after flashing it and therefore I assumed it does some things differently.
 
Last edited:

jianC

Senior Member
Sep 3, 2013
87
104
Could it be possible that it's hard to revert to stock after flashing this rom?
I don't seem to be able to get the stock rom to boot even after ruu. I seem to always get a bootlop.
Could this be caused by differing partition layouts? Is it even possible that this rom interferes with reverting to the stock rom?
Your cm11 still works without a problem, that's why I was thinking maybe there is a connection.
Or is it just me?

Edit:
Just for clarification: I was trying to remove the simlock and it seemed like I needed a stock or Sense based rom to do that. In the end I managed to do it with JMZs Sense rom after ruu and also flashing the corresponding kernel as well. Initially I thought that since I had an unlocked bootloader and was s-off as well, everything would be flashed automatically without me having to flash anything manually (for example the boot.img).
Was that assumption incorrect?

PS: I hope that wasn't too offtopic, but it has something to do with this rom since it was the only one that worked after flashing it and therefore I assumed it does some things differently.

Don't worry, it's not off topic :) The partition layouts are the same as stock (it is managed by the bootloader, not the ROM). However, the main difference is that the partitions are formatted as ext4 for CM11 vs ext3 for stock. There should be no issues reverting back to stock with the RUU, unless the RUU is incomplete. Try to do a "fastboot erase system -w" (this will format your system, userdata, and cache partitions to ext3) before flashing the RUU.
 
  • Like
Reactions: devtee

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    As of 8/18/2016, this will no longer be supported by me. Thank you all for providing feedback.

    Hi everyone,

    I have ported cm11 to the HTC First along with the MSM8960 kernel. The rom is mostly working and is stable. The only major bug left is the DSP and AMP (see below)


    uEFPlK5xoCa5d2pyakroPdwSnR5dpPIniwuXB9fznZzz7mplKHAuUYazhgf39zO5mCLhpm9wPXSSSqpEQ1PadBnZGJKN8JNJfdontP4-DY3HVYHanLW1qD09LbfcGkhK4h_XSCBEwXOd-8jDyQaF9CXA45qNLZ6OzUeR-UuX4tw90yUZNGO0U5njGIzTquTJKA-rURZbmjumEM5mdSrNFd-3j7OrTIkF4puxEfRrS3TuFVWv0r1HMJQvzdfybvZFG74Lcahz30ClN2NYM0jVKDQssjXo_ujbVABrBLpIKAo2FtlgBeLzWwbNc5KAskiPZ-0H0S4ofuBCtS33IQDWyvcp8c8Wu546sXE63ERdHy67BYjEwKwJUuooKoZizxXUalbf7dEztQLWlJFpzfom-eFh4RcRDj6yVq-Ihwj0g7Kifm3TNxArMWXZnV-5WoIyCyQrS_Xk4qpfoTfRE2eLbDVKORQFK27BIiu1MiGss3VKnvhQzMiyEUQapq66q1S1uYEfSEk83mcwbapCWKglAZ4FW4ZRLmPmU-W1oCyan1JJyXWwY4vaSBQaLBmmy8kTsUFO=w355-h631-no

    zlVanRZdA0NwKdYGOw0pv83Fwp1aSw1VNRI8OJS_XF-W81c5Bl506wyDKS8LiiTjzgy9oqbaUQrNCfUgXlmsLCSAHNy2ayncS3tgF2Q_k4ubeSu417xGDb13tgGqJ8TEOJjsmdsjckpO_J-aw3Jm-5TBSDAFVSa6btAyx0fET5XjAg5lb4Q1G8DGV2oZcPTkwpQWl8C9Smq1LRPmB5g83MdIVovztg_1e6hnb-eo8iLH42Y6N19zhfglbhFcoAj6v6GF5iHzzpEtx75YoiK2co7dgvkkc6iYANtSuIYgdaLp7hdeYPLQfMN_3Ph7N-PhrGsWwC0Qs7EfDEBU04lp1ovxu1GNTuGHFinhBpH8NVHF_KgcpjFlvq5bYZJz9SQnl7bz5W3BDMrLYCvEC5xPCo1Eu8rc7iyV3HUX_LGVldq_hBMt334FRz0SdgxwxIwxlbQ7u3ORJbTxZk_sd2W8HlOnb_Tjk4HNVPvS1_-hHjvaLuSMHZQQfXFlTEdbdeJ4GVBy67FR_wSDJBD5SVr6UNdtEnBRakc4QjnMTuLNe-WPg4mnfPYYUE1o_Vptg7PLu28g=w355-h631-no


    What works:
    - Data (4G/3G)
    - GPU Acceleration
    - phone calls
    - NFC
    - USB Tethering/Hotspot

    What does't work:
    - Speaker DSP and AMP (dsp is currently disabled. It does not work because the open source hals for the tfa9887 dsp and amp do not initialize it correctly. Speaker volume is a bit lower and may not be as "crisp" as stock)


    Code:
    [B]Installation steps (If you are coming from stock rom, otherwise just flash the rom):[/B]
    1) S-OFF your phone.  HTC dev unlocked with S-ON is fine too, but you will have to flash boot.img manually after installing the update)
    2) backup your data (including your "sdcard") (Example: adb pull /data/media ~/Desktop/backup)
    3) flash recovery
    4) boot into recovery
    5) go to "mounts and storage" and format "/system", "/cache", and "/data and /data/media (/sdcard)" [COLOR="Red"]*[/COLOR]
    6) sideload rom
    7) [OPTIONAL] sideload cm11 gapps (get your gapps from [url=http://opengapps.org/]OpenGapps[/url].  I recommend at least "micro")
    8) reboot
    *If you do not format all the partitions (especially "/data and /data/media (/sdcard)" option) when migrating from stock, QSEECOM/TrustZone won't work correctly and may cause random app crashing.

    Download:

    cm-11-20160321-UNOFFICIAL-mystul.zip
    cm-11-20160324-UNOFFICIAL-mystul.zip
    cm-11-2016-0325-UNOFFICIAL-mystul.zip
    cm-11-20160717-UNOFFICIAL-mystul.zip (latest)

    Recovery:
    CWM 6.0.5.1

    Code:
    [center][b]Changelog:[/b][/center]
    [b]2016/07/17[/b]
    - Upstream kernel patches from CyanogenMod
    - June 1 Security Patch Level
    - Misc CM updates
    [b]2016/03/25[/b]
    - Enabled ZSL (Zero Shutter Lag) feature for camera
    [b]2016/03/24[/b]
    - Most stable release
    - Fully working camera/panorama/camcorder
    - Various small fixes
    [b]2016/03/21[/b]
    - Camera/Camcorder is partially working
    - Fixed audio bugs (mostly)

    Source for building ROM:
    GitHub

    Notes:
    - Recently opened apps is now mapped to 'long press home' instead of double tap.
    - "Sdcard" data is now stored under /data/media/0, and not /data/media.

    My support for this ROM is limited. Flash at your own risk. Please report all bugs in this thread (with a logcat and dmesg) and I will try to fix them.
    2
    Camera now partially works, but I cannot capture the image yet. Mic and all audio are now fixed. The proximity sensor is also fixed. I am still working on camera and NFC.

    Again, you can check for updates at https://github.com/CMyst and feel free to open an issue for whatever bug you find. I will be building another release soon!
    1
    @hohosanta @CornfedChris Rom updated! Fixed the microphone/speaker bug but camera/camcorder still doesn't fully work.

    Edit: I have fixed the camera issue and camcorder recording. Rom will be updated shortly.
    1
    Rom updated. Everything should be working (except for the speaker amp). Camera/Camcorder is fixed.. If there's still anyone around..
    1
    Rom updated. Everything should be working (except for the speaker amp). Camera/Camcorder is fixed.. If there's still anyone around..

    Of course :)

    Just out of curiosity since I don't own this phone (yet), the deactivated speaker dsp concerns the speaker that is used for music playback and not the one that is used for calls, correct?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone