Q&A for [ROM][4.4.4][Official] CyanogenMod 11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][Official] CyanogenMod 11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Please help!
Please Help-
I have a HTC ONE M7 from Verizon that is rooted and running CM11 snapshot M10. I recently started using the phone after a couple of months. When I started using the phone it was still on CM10.2, working fine. I upgraded to CM11 and had an issue with google play services failing, so I wiped the device and did a fresh install of CM11. The install worked fine and but I had none of my previous apps so I began the process of setting my phone back up and downloading all of my apps. Certain apps would not install and come up with an error message. ( Unknown error code during application install "-24". So I did some research and found out how to get rid of the error code but it only worked for certain apps, others still came up with the same message. I had wanted to clean out my phones memory anyways because it was getting full so I decided to do a full factory data wipe/reset from the phones settings menu, not from recovery. So I proceeded to wipe the phone and it rebooted and showed the android logo with the crazy blue lines in his stomach and the blue loading bar below. I let the phone sit for a while and nothing was happening. It stayed on that screen for a couple of hours without rebooting or showing any signs that it was wiping the device. So I decided to to hard reboot the device with the power and volume down button ( probably a bad idea I know) and reboot the device. Now when I power on the device the CM logo shows up but it just keeps spinning, never boots into the device. If I try to boot into recovery, the bootloader shows up fine, and then I select recovery and it goes back to the same screen with the android logo and cray blue lines in his stomach and loading bar below. I have let the device sit for hours both trying to boot up or boot into recovery and it just either stays on the CM loading screen or the android logo with blue loading bar. I now do not know what to do and am a little worried. I am not new to rooting and roming android devices but I am also not a pro. Please help me recover my device to any rom.
Thank you for your help and sorry for the long post.
manklee said:
Please Help-
I have a HTC ONE M7 from Verizon that is rooted and running CM11 snapshot M10. I recently started using the phone after a couple of months. When I started using the phone it was still on CM10.2, working fine. I upgraded to CM11 and had an issue with google play services failing, so I wiped the device and did a fresh install of CM11. The install worked fine and but I had none of my previous apps so I began the process of setting my phone back up and downloading all of my apps. Certain apps would not install and come up with an error message. ( Unknown error code during application install "-24". So I did some research and found out how to get rid of the error code but it only worked for certain apps, others still came up with the same message. I had wanted to clean out my phones memory anyways because it was getting full so I decided to do a full factory data wipe/reset from the phones settings menu, not from recovery. So I proceeded to wipe the phone and it rebooted and showed the android logo with the crazy blue lines in his stomach and the blue loading bar below. I let the phone sit for a while and nothing was happening. It stayed on that screen for a couple of hours without rebooting or showing any signs that it was wiping the device. So I decided to to hard reboot the device with the power and volume down button ( probably a bad idea I know) and reboot the device. Now when I power on the device the CM logo shows up but it just keeps spinning, never boots into the device. If I try to boot into recovery, the bootloader shows up fine, and then I select recovery and it goes back to the same screen with the android logo and cray blue lines in his stomach and loading bar below. I have let the device sit for hours both trying to boot up or boot into recovery and it just either stays on the CM loading screen or the android logo with blue loading bar. I now do not know what to do and am a little worried. I am not new to rooting and roming android devices but I am also not a pro. Please help me recover my device to any rom.
Thank you for your help and sorry for the long post.
Click to expand...
Click to collapse
Are you s-off? You'll find it in your HBOOT
Help
I've upgraded my phone yesterday by CM 11.0 but i cant make a phone call or even draft a massage. It said Molbie network not available
hectorvo said:
I've upgraded my phone yesterday by CM 11.0 but i cant make a phone call or even draft a massage. It said Molbie network not available
Click to expand...
Click to collapse
You probably need to update your firmware to use the newer cm. Make sure you flash the latest with no boot.img.
Related
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
nkomp18 said:
Hello,
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
Click to expand...
Click to collapse
The single vibration with no screen normally means the batteries dead, and it's possible that it's not charging when hooked up to your computer, open it up, take the battery out for 15 seconds, put it back in, then plug it into the charger for an hour or so.
nkomp18 said:
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
Click to expand...
Click to collapse
Are you sure the zip you downloaded is cm11? There was an issue with yesterday's first cm12 build that resulted in bricked devices.
The device can be recovered
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
mikeioannina said:
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
Click to expand...
Click to collapse
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
nkomp18 said:
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
Click to expand...
Click to collapse
Go to your custom recovery, wipe /data /cache /Dalvik and /system, then flash CM+GApps. If you used the tool in my thread, you'll have to boot into COS before flashing anything.
Now it's almost perfect,
The power button only works to lock the screen, not to turn it back on again.
As you can imagine, the phone is unusable if I can't wake it up from sleep.
I tried a lot of things. First of all it's not a hardware issue because the power button works flawlessly to lock the phone or to reboot. It only fails to wake the phone up, which sounds like a software issue.
I tried the option "double tap to wake" and that does nothing. The only thing that wakes the screen is connecting it to a USB.
Any ideas?
I noticed after I followed the instructions some things changed in my phone. The OPPO logo is different when the phone loads and fastboot graphic is different. Now I get Chinese characters whereas before I believe it was an android robot.
I suspect this is causing the power button errors. Any ideas how to put it back?
Hi everyone,
Being the more adventurous kind of person I am, and also rather sick of LG's android overlay, I decided to finally try rooting and installing a custom ROM, as my previous device was the Nexus 5, and I longed to return to the stock android world. It is a first for me to try this, so I read a few forum posts about it, and finally I rooted my G3 (D855 model), which went flawlessly. I then installed cyanogenmod 12 (I cannot remember which version, it was the most recent at the time) and I was finally satisfied by the software, which was as smooth as butter, unlike LGs skin. After a few months, I made the terrible mistake of installing one of the updates that where suggested, and then the problems began. While the phone was performing the update, it froze on the "optimizing apps" screen, and stayed so for several hours, until I decided to pull the plug on it, and it slowly died of a flat battery. I then tried to reboot the device, which stayed on the LG logo screen for a long time, until I again had to leave it to die. I then rebooted into TWRP recovery, which was the recovery I had installed and used to install CM12, and I tried to recover from the last backup I had performed a week prior about, and it failed with "error executing binary in script". After some googling, I found a forum where someone recommended to wipe the cache, data, system, and dalvik partitions. Having done this , the backup was successful and the phone was up again. A few days later I saw that CM13 with android M was released for the G3, and I decided to try it. I downloaded the rom, backed up my old version again and flashed it with TWRP. It worked, and the device booted into CM13, but I was greeted with a "process has crashed" message. I dismissed it, and the OS seemed to work, but then I realised it failed to recognize my SD card, and the phone internal memory (I own the 32GB model) was listed at a mighty 2gb. I decided to return to CM12 for the moment, so I rebooted into recovery, flashed the backup and got the same "error executing binary in script". I then wiped the cache, data, system, and dalvik partitions, and flashed my backup with no error. The phone reeboted, showed the LG screen, and then went black, then the LG screen, then black, etc... I quickly discovered this to be a boot loop. After some attempts to fix this, the phone booted to the LG screen, then the Cm logo pulsing, and then the "optimising apps". At the end of the process, the lock screen appeared, and after unlocking the device, I discovered it was back in CM13. This was suprising, and the errors I previously had were still here, so I returned to TWRP and tried to flash the original CM12 file I had, and this showed no error. After booting the device, CM13 greeted me again. I decided the device was seemingly possessed, and made the decision to unroot and reinstall into factory settings. But the first step of this process was out of reach, as the phone goes no further then the "download mode" screen with the small blue dots in the middle when I hold the volume down and plug it into the PC. After an hour on said screen, I pulled the plug and tried to reboot again. CM13 appeared once again, as if it was haunting my dreams, and I also found out that TWRP is no longer accessible, as the device stays on the blue loading screen of TWRP.
I have searched and not found anything saying how to get any further then this. I know that as I am not very experienced with this, it was rather foolish to act as I did, so spare me the lectures about that. But I didn't learn to ride a bike without falling off it, so it's kind of the same isn't it? Anyhow, is there someone out there who may assist me?
Many thanks to anyone who has any advice, I'm sick of my backup samsung S3 D:
Ed
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
ride1226 said:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
Click to expand...
Click to collapse
You really have to investigate by adb. Look into the dmesg output and logcat as well. Maybe your sdcard is corrupt or 100 other issues are possible as well. What device do you own? H811? unlocked?
.
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
kunate said:
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
Click to expand...
Click to collapse
There are several users reporting that the latest cm version bootloop the best option is to start in download mode and Flash with LGUP Stock ROM.
You could also try to boot into Download Mode and then flash the latest twrp and then Boot into Factory Reset Mode again
I was an idiot and did a factory reset (not while in recovery mode) and when everything restarted I ended up with my tablet stuck trying to load TWRP - I am/was running the lastest CM nightly from the end of May, I don't know what version of TWRP is currently on there. I just get the blue teamwin screen that stays there for about 5 seconds, flashes black, then back to the teamwin screen again. I got it into download mode one time, but as I was not in a situation where I could take advantage, and have since forgotten what I did to get it into download mode. (I think) I've tried all the button combinations with the tablet in the bootloop, and with it off (dead battery) to no avail. I've checked the forums and the few that I've found with the same situation as me, there is either no solution offered, or the solution was never posted, just that the situation was resolved - the thread most resembling my situation is this one http://forum.xda-developers.com/galaxy-tab-s/help/galaxy-tab-s-sm-800-stuck-flashing-twrp-t3219865.
Any help would be greatly appreciated. If you need more information, let me know. Thanks!
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800