Hey guys i just downloaded the recent nightly from CM ( 23/7/16) and when i flashed the ROM and rebooted the device it takes me to the set-up stages just like how google would, but there seems to be a problem. Whenever i try to tap on the "Next" button or go back, the notification panel drops down and i'm unable to proceed further. Is there anyone else facing a similar problem and whats the solution to this? oh and btw ive got a moto g 2013 (falcon)
Related
Hi guys, I've recently installed MIUI 1.11.11, and this friday there was an 1.11.18 update listed in the updater app which was already included.. I opened it, did a backup with the app and after that I downloaded the latest release and pushed UPDATE after that, and it went into reboot, then phone rebooted, I got into GALAXY S GT-I9000 screen, shortly after I got GALAXY S Cyanogen(mod) screen and shortly after that it went loading something for a quick second, then just rebooted, and then the phone started normally, I thought that was it, but when it loaded to the lockscreen I checked the version and it was still 1.11.11, so clearly something went wrong.. I did that several times after, but I get the same result everytime..
Looks to me like bootloops.. Bootloops gave me some problems while installing 1.11.11 in the first place, was stuck in bootloops in the middle of the installation of the rom until I pressed the three buttons to go into recovery mode and selected install .zip once again.. then it went through without a problem. Also I had no other problems with this rom so far..
So if anyone knows what could be wrong here, or what I could be doing wrong, so I can update I would really appreciate your help..
I recorded my screen. Recording has everything I did, nothing more nothing less, only after I stopped recording I pushed UPDATE in the updater as it clearly can't record screen while phone is rebooting.. Check it, I hope it helps with the problem.
The video is on youtube under -> watch?v=J01LpijBJ7c
Lumix357 said:
Hi guys, I've recently installed MIUI 1.11.11, and this friday there was an 1.11.18 update listed in the updater app which was already included.. I opened it, did a backup with the app and after that I downloaded the latest release and pushed UPDATE after that, and it went into reboot, then phone rebooted, I got into GALAXY S GT-I9000 screen, shortly after I got GALAXY S Cyanogen(mod) screen and shortly after that it went loading something for a quick second, then just rebooted, and then the phone started normally, I thought that was it, but when it loaded to the lockscreen I checked the version and it was still 1.11.11, so clearly something went wrong.. I did that several times after, but I get the same result everytime..
Looks to me like bootloops.. Bootloops gave me some problems while installing 1.11.11 in the first place, was stuck in bootloops in the middle of the installation of the rom until I pressed the three buttons to go into recovery mode and selected install .zip once again.. then it went through without a problem. Also I had no other problems with this rom so far..
So if anyone knows what could be wrong here, or what I could be doing wrong, so I can update I would really appreciate your help..
I recorded my screen. Recording has everything I did, nothing more nothing less, only after I stopped recording I pushed UPDATE in the updater as it clearly can't record screen while phone is rebooting.. Check it, I hope it helps with the problem.
The video is on youtube under -> watch?v=J01LpijBJ7c
Click to expand...
Click to collapse
I'm finding the same issue. Help please!
Situation is kinda strange.
Yesterday i was bored and i started to flash some roms on my OPO. I started with the latest ColorOS that i found here on XDA, but i didn't like it. So i flashed PA 4.6 beta 6. I noticed that the red boot logo of colorOS remained despite the full wipe of the internal storage. And the fastboot mode started to show some chinese characters instead of the regular ones.
But that's not the problem. Problem is that this morning i wasn't able to turn off a call because the screen turns off every time a call is made and there's no chance to turn it again on. The only thing i could do is to long press the power button and reset the phone. The call starts, the speaker works, the screen turns on and you can't do nothing than this.
I said "ok, it could be the PA rom, it's in beta, y'know"...So i flashed the PA stable and...same problem.
Then i tried the first rom i saw (vanir lollipop, last build) and...same problem? WTF?
Now i'm flashing the original 44s by fastboot and see what happens. In case nothing happens with the fastboot way, i will try to flash it by recovery. But i have a bad feeling about this.
Any similar experiences? I will keep the thread updated for people with the same problem.
EDIT 1: ok, after the fastboot flash of the cm11 44s i'm able to make calls without those problems. It will be amazing if the problem were still there.
EDIT 2: i have to say that the chinese fastboot and the red logo are gone now.
The reason your proximity sensor stopped working was because of the modem you flashed while you flashed ColorOS.
I flashed ColorOS aswell and has the same proximity sensor issue after flashing back a CM11 rom.
mumaster20 said:
The reason your proximity sensor stopped working was because of the modem you flashed while you flashed ColorOS.
I flashed ColorOS aswell and has the same proximity sensor issue after flashing back a CM11 rom.
Click to expand...
Click to collapse
Damn! I knew it!
That terrible ROM messed up all my phone -_-
After locking the phone, when i press to unlock black screen apperas some time even after trying again and again. Same problem sometimes while in call;sensor service, when phone brought far from ear black screen appears
Please some one help
Are you on cyanogenmod 12? This type of issue happened to me too when i flashed cm12.
No, my model is D2212 it doesn't have cm12. I have faced this problem on nitrogen rom and sometimes on stock too after updating to 4.4.4 from 4.4.2.
I've got a Moto G XT1032 16Gb.
I recently started experiencing random reboots, and often the phone gets in bootloop.
So if I long press power button, sometimes the phone restarts and does apps optimization again and then it boots normally.
I tried changing rom, from Cyanogenmod 13 nightly to [ROM][6.0.1][FALCON] AOSP-CAF [STABLE][9/3/16], but the problem is still there.
I need your help to check for sure if it's a software problem and not hardware.
I followed instructions here [GUIDE] Moto G - Restore stock firmware and flashed XT1032_FALCON_RETGB_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip
All mfastboot commands went fine, the phone rebooted, I was setting it and it started to reboot again and again...
Is this the end of my Moto g? Or there's still something I can try?
Hi Guys,
Prelude : 2 months back, my pure stock Moto G experienced i guess a battery drain and refused to start the next time onwards. When it was powered on, it just got stuck on the M Logo of the bootup. After the help from @lost101 & others, i was able to flash the custom recovery & rom and got the phone to bootup atleast although faced the same issue which i'll be writing below now.
Since that event has happened, everytime I flash a custom rom, the installation happens without any glitch which includes the rom.zip & gapps_pico.zip. Now when the ROM bootups, the startup screen shows up after which it starts optimizing apps. That's where is the issue starts.
For eg. optimizing app x (single digit) of 101, it doesn't goes beyond that point even after waiting for 15-20 mins or so, and i've to manually reboot using the power button after which again the optimizing apps screen comes up and this time the figure is optimizing app xx of 16/17, and in this turn the phone successfully boots up to the setup screen and works as normal. But after a few moments when i'm done setting up all my apps and everything, random issues turn up for eg. the notification quick tiles won't drop down. And when i restart the handset, again it shows the optimizing apps screen, the phones boots up to home screen but random issues pertain.
I've tried ROM's like Stock Debloated (5.1.1) , CrDroid, CyanPOP, RessurectionRemix all based on 6.0.1.
Before installing any ROM, i do an advanced wipe and all format the data. Right now the handset is running CyanPOP but the main issue is i'm unable to access the notification dropdown. It doesn't goes beyond the header.
One more thing, I installed RR (xt1022 specfic) with same pico_gapps on my Moto E & the rom booted up in no time and working as smooth as butter till date with no issues whatsoever.
I'll be helpful if some one can diagnose the issue. Thanks
BBThumbHealer.
Did you try flash stock firmware and then flash a costum ROM ?
@Eurofighter_ty : when the issue first happened, what I remember is that I tried installing the debloated stock ROM of 5.1.1 and not the pure stock having all the unnecessary gapps. And similar issue was encountered. Same thing happened with other custom ROMs.
Today I've now reverted to a previous version of CrDroid 6.0.1 released in April and it at least runs fine when in use although a reboot causes the same issue. However, CrDroid June update and CyanPOP had the issue in which the quick tiles didn't drop down along with refusal of bootup.
Try to flash the stock ROM via fastboot with all files