Hey friends,
I have a motorola moto g 1st generation falcon version phone. I had rooted it nearly a month ago and installed cm12.1 in it and it was working fine. But i recently received an update from cm for cm13 and i installed it. It got installed too but when it started I was continuously getting a prompt that google play services has unfortunately stopped. and it was appearing again and again and not letting me do anything. That is why I switched off my phone and restarted my phone but it got stuck in the boot!! My recovery was also not responding. So I researched a bit and i found the factory framework of moto g!! I flash it using adb!! and my phone started. but it was restored to 4.4.4 kitkat! and the abnormal thing is it was not upgrading to lollipop also, whereas moto g has got 5.0.1 lollipop update!! still i again rooted it with cf-auto roo!! it got rooted well, i even flashed twrp recovery and that too worked well!! but when i flashed cm13, it again got stuck in the boot and again my recovery was not responding!! and this is happening again and again!!
Someone please help, i have lost my connectivity since last 4 days!!
thanks in advance......
Minor Ambekar said:
Hey friends,
I have a motorola moto g 1st generation falcon version phone. I had rooted it nearly a month ago and installed cm12.1 in it and it was working fine. But i recently received an update from cm for cm13 and i installed it. It got installed too but when it started I was continuously getting a prompt that google play services has unfortunately stopped. and it was appearing again and again and not letting me do anything. That is why I switched off my phone and restarted my phone but it got stuck in the boot!! My recovery was also not responding. So I researched a bit and i found the factory framework of moto g!! I flash it using adb!! and my phone started. but it was restored to 4.4.4 kitkat! and the abnormal thing is it was not upgrading to lollipop also, whereas moto g has got 5.0.1 lollipop update!! still i again rooted it with cf-auto roo!! it got rooted well, i even flashed twrp recovery and that too worked well!! but when i flashed cm13, it again got stuck in the boot and again my recovery was not responding!! and this is happening again and again!!
Someone please help, i have lost my connectivity since last 4 days!!
thanks in advance......
Click to expand...
Click to collapse
Hello,
I have reported this thread to move to right Q & A section in order to get help more quickly.
-Vatsal
Related
Hey guys!
I have a moto G XT1032. I have installed several roms since I bought my device and everything has been alright, but recently I've noticed that when I install any pure CM rom I can't restore any app with Titanium Backup, I always get the error message shown in the attachment. The same happens to me with CM11 or CM12, but just on these pure roms (this doesn't happen on roms like Pac-rom, N5Xperience or Vanir).
I can't restore apps via recovery either, the "update.zip" gets flashed fine, but when the phone reboots nothing has been installed.
I don't know what else to try. Thanks in advance for your help.
Few days ago I saw this guide (http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472) of converting a regular moto g into gpe 5.0.1. So I followed every step in the guide and finally got lollipop. I was testing it for the next few days and found out that 3G wasn't working. I didn't like it so I deleted the '5.0.1 GPE OTA' zip file (I am a newbie) and ran 'ANY FIRMWARE TO 4.4.4 GPE.BAT' again (I wanted to downgrade to kitkat). After the operation was finished and the phone rebooted, the kitkat was here, but I noticed flashing lines and glitches on the screen (and 3G still wasn't working, now I think it's because of converting to gpe). I don't know how to convey with words, but I am really scared now. After some time glitching stopped, but that was only a temporary effect, because after I rebooted it happened again. After a few minutes I happened to see this system update message about upgrading to 5.0.1. I agreed, and now my system is lollipop again. So now my purpose is to PROPERLY downgrade to non gpe kitkat. Do you know how to do it? Thanks
I want to ask if there is any problem (flicker screen, red notification on booting up...) when I install CM11 from stock 5.0.2 on Falcon Moto G XT1032? (follow this official guide on CyanogenMod: http://wiki.cyanogenmod.org/w/Install_CM_for_falcon)
Thank you.
I've done this recently and the only issue I've noticed is the screen flickering problem. The solution is to simply press the power button to lock the screen then unlock it and it should be fixed. You only have to do this once but if you reboot your phone you will have to lock/unlock again on first boot.
Thank you for your answer. Just to be sure, did you follow CM guide? Is there anything important which I should be careful about? (I did the same thing with several phones but still noob)
I just booted into custom recovery (I use Philz) and wiped the different partitions along with /cache and /dalvik. You can follow the guide and use the push method or you can use sideload which I did.
I did that and now i have problems with the mac address (i was using 5.1.1) my shows me a different mac and i don't know how fix it, but if i back to LP the problem is solved.
It's a bootloader issue for sure and general happen because you're bootloader is updated to Lolipop 5.0.2 and now you install kitkat as cm 11 over Lolipop.
In simple words your bootloader is new while the software is old
screen flickering issue can be resolved by downgrade bootloader but "BE EXTREMELY CAUTIOUS" failed to upgrade bootloader make your device permanently dead and downgrading is not recommended....
I will recommend try cm12.1 it's rock solid stable as cm11
I finished installed CM 11, firstly the prob is screen flickering. Then after installing all my apps, the android.com.systemui was crashed over and over and cannot use anymore. I reflashed CM and gapps and reinstalled apps but it happened again. Finally, I had to returned to Lollipop.
Anyway, thank you all for your help
Same thing happened to me unfortunately but I've found this one here and it is working beautifully. Try it and see if it works for you without the constant systemui errors.
Thank you. At the moment i am quite happy with GPE version. It seems that this version GPE 5.1.1 is better than Moto stock one.
Please pardon me for any faux pas as I am new here.
Mods please refer me to the appropriate thread and close this one, in case this one is a duplicate.
It seems my Moto G 1 Gen XT1033 is hardbricked. I had been running a CM 12 for falcon - nightly release since May 2015 and had had no problems so far. I had also upgraded my recovery to CWM Touch.
Two weeks ago, my phone got stuck in a boot loop (I now realise that that is called a softbrick), I managed to boot into recovery and updated my OS with the latest nightly release of CM 12 for my phone. I also tried to upgrade the recovery version with the same as that of the OS version but I don't think that it got upgraded. (I'm not sure what it said).
Anyway my phone was working fine for an hour or so until CM gave some errors on opening the themes configuration, so I thought rebooting my phone would solve the problem.
My phone never booted after that. It didn't even turn on or boot into the bootloader/recovery etc. I checked the battery etc. and it was fine. There was no issue with the hardware.
I then connected my phone to my laptop and it recognised it as qhsusb_bulk. I have spent a lot of time searching and trying various methods like:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076
Using the MotoTool All In One etc.
I cant seem to figure out the problem. I don't even know what my bootloader version was etc.
Is there a problem with my bootloader or recovery? I can't seem to understand.
Can someone please help me with this?
Thanks
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
motolollipop said:
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
Click to expand...
Click to collapse
Thanks man. But no help so far
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
CoolCrusader said:
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
Click to expand...
Click to collapse
That happened to me too, I think even the same image! It was a long time ago and I have now switched to a Oneplus One after using a Moto E which actually isn't that bad - I got it new super cheap. For me, Cyanogen restarted to update and after a LONG period of time stopped doing anything (I have upgraded before). I couldn't mount anything in CWM and I lost all data irrecoverably. The partition table got all messed up, and I had to flash a dual sim image as it was the only one that loaded - done through fastboot. I then flashed the original kitkat image and then massively messed up and updated, making my phone qhs_bulk.
Basically everyone who has had lollipop on their devices and have this are waiting for files to be leaked from Motorola so they can make their phones work. Not much is happening currently, you might as well get a new budget phone - some of the new ones are much better than the Moto G 1st gen! Or you could do what some people are doing which is ordering broken Moto Gs off eBay and replacing the board. Good luck!
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
You may want to go the fastboot method to flash a stock lollipop image and CWM recovery - if you don't have a backup, you may want to try just flashing something like TWRP to see if you can get some files off your device, then completely flash over it.
I couldn't wait to get the 5.1.1 update in the usual way. So I asked google to find update. I found a cm12 bacon download. I Neva done this before so I just downloaded n installed this bacon update. I think I flashed my device by mistake bcoz afta my phone bricked. I managed to unbrick my Oneplus one n now in about phone in the settings it says I'm running 5.1.1 lollipop. But my problem is I had to reset my phone for a different reason n afta reset it still says in about phone in running 5.1.1 lollipop but it's not displaying lollipop on phone is just like it was wen I first bought the phone. I want to know what do I do next?? Oh n also phone keeps asking me to do system update to 5.1.1 , I've tried but obviously phone doesn't recognize I've already done this update early so wants to update to 5.1.1 again. So what next?? For example do I have to root phone now so I can get 5.2 running on phone or what ??? Please help I am new to all this n haven't got a clue what I am doing???
ceasus said:
I couldn't wait to get the 5.1.1 update in the usual way. So I asked google to find update. I found a cm12 bacon download. I Neva done this before so I just downloaded n installed this bacon update. I think I flashed my device by mistake bcoz afta my phone bricked. I managed to unbrick my Oneplus one n now in about phone in the settings it says I'm running 5.1.1 lollipop. But my problem is I had to reset my phone for a different reason n afta reset it still says in about phone in running 5.1.1 lollipop but it's not displaying lollipop on phone is just like it was wen I first bought the phone. I want to know what do I do next?? Oh n also phone keeps asking me to do system update to 5.1.1 , I've tried but obviously phone doesn't recognize I've already done this update early so wants to update to 5.1.1 again. So what next?? For example do I have to root phone now so I can get 5.2 running on phone or what ??? Please help I am new to all this n haven't got a clue what I am doing???
Click to expand...
Click to collapse
There is nothing called 5.2
Just ask in this sub-forum's Q&A, Help and Trouble-shooting section for further help specific to your phone: One Plus One - XDA Forum
I'm a bit confused. If you installed an official ROM through the stock recovery, your probably OK. Maybe there is a newer 5.1 release than the you installed.
Sent from my A0001 using XDA Free mobile app