Database Info

[Q] - No Calls or SMS OxygenOS or CM12

OK I am having a problem, when i rooted and followed the direction to install both OxygenOS or CM12 nightly I am unable to receive any SMS or phone calls except after a reboot. Once i reboot any saved messages come through and then once the phone sleeps it stops. I have rolled back to CM11S for the time being. Any steps or tricks to follow to get this issue resolved.

"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?

abhibnl said:
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
Click to expand...
Click to collapse
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot

pkp190 said:
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
Click to expand...
Click to collapse
Well all i could suggest it, also please flash the CM12 firmware once. In theory oxygenOS and CM12 firmwares are compatible. So flash like this:
Install CM12 fimrware zip
Wipe System, Data, Cache, Dalvik etc without Internal memory
Flash Rom Zip
Flash Gapps
Flash SuperSu
and then let it boot and settle down. Before restorign apps or data, check for any issues again

seems to be sitting stable at the moment, will keep testing. but thanks for the input.

pkp190 said:
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
Click to expand...
Click to collapse
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.

abhibnl said:
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
Click to expand...
Click to collapse
spoke too soon, after letting the phone sit ideal for a few hours and testing incoming calls\sms nothing came through. restored a backup of CM11S, for the week to have a working device. will keep trying to get to a root cause later in the week. will also open a help ticket with OnePlus to see if there is something I am missing as well since this happens with OxygenOS as well.

Cyanogen Mod 6.0 for OPPO R7 PLUS

I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus

Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom

Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk

Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).

Very exited, good job

so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back

Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...

Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.

Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)

coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it

Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone

coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.

Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.

coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE

coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..

Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk

unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.

Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!

No Response ,phone freeze on CM 13 ,CM12.1 Slim Bit, Resurrection Remix Help...

Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:

sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try using the base rom as v5.6.11 and try using the old twrp v2.8.7

I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.

Try provide with a logcat, might be more useful in helping you.

No other custom rom is working on my mi4i
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..?

sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
astro49 said:
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you restore your nandroid backup like CM12, Mowkee, Resurection if you from new MIUI ROM.
If you want to restore MIUI7 nandroid backup from CM12 you need to flash MIUI7 patch ROM first.
RIYAN X55TU said:
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you flash to CM13, if not you'll get bootloop. If you use default init.qcom.post_boot.sh and your phone heat up it will lags, so use edited init.qcom.post_boot.sh.

Confirmed
Glembozt said:
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
Click to expand...
Click to collapse
I can confirm that this DID magically works!
No need to use the old TWRP, just flash MIUI V6.6.6(I used the fastboot package[1], not sure if recovery package works) then flash TWRP then flash other custom OSes.
[1] bigota.d.miui.com/V6.6.6.0.LXIMICF/ferrari_global_images_V6.6.6.0.LXIMICF_20150521.0000.3_5.0_global_46b5474265.tgz

strange bootloops

hey y'all i have a 6045i US and it keeps bootlooping it all started by flashing CM 12.1 4/03/16 verison by the marionetteso i also flashed gapps xposed and root so it gave me the bootloops so what i did is wipe data factory reset nothing worked so i flashed another ROM wipe data everything and flashed bootloop fix kernel and nothing,same results im at the homescreen and im doing things and bootloops from there even recovery rebooted alot lol im not sure why so i flashed another older verison of it (i risked btw) and it worked so with that recovery i flashed a TWRP backup from one of the threads to stock ROM wipe data etc. and nothing same results!!! bootloops from homescreen so if theres another way to fix id appreciate it so much a clean install as in out of the box also i tried the alcatel upgrade app and nothing everytime i shut down the phone and plug the USB it just turns on for some reason bootloader works still with fastboot commands so i dont know whats going on this is my first issue with this phone,thank you
EDIT: fixed i finally got the alcatel app to work mods please close this thread

MOTO G (simcard issues with latest CM13 nightly)

I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......

iHackIt said:
I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......
Click to expand...
Click to collapse
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:

karanksj said:
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:
Click to expand...
Click to collapse
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.

iHackIt said:
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.
Click to expand...
Click to collapse
I quoted 5.0.1 not 5.1 brother It worked for me every time.

karanksj said:
I quoted 5.0.1 not 5.1 brother It worked for me every time.
Click to expand...
Click to collapse
Sorry for misreading...:silly:
I cant flash 5.0.1, 4.4.2,4.4.4
When i try to flash it gives errors and warnings (only 5.1 works )
i will share errors...
works in the sense it was flashed perfectly but it also boots to the recovery everytime like CM13
My bootloader version is 41.1A..