Related
Q&A for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]
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][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]. 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!
no calls or data
I have an xt1031 flashed to page plus. I have bootloader 41.19 from a failed lollipop update attempt. I flashed the 4/8 build and I can't make calls and do not have 3g. The network shows as 31000. What should I do?
I have been trying each of his builds and anything newer than 4/8 data hasnt worked I'm on boost if that makes any difference
Verizon?
Good morning,
I'm on an XT1028 still with service through Verizon Prepaid; my bootloader is unlocked and I'm on an optimized KK stock ROM at the moment. I've been following the development of Meticulus' CM12.1 through the primary thread and there has been a lot of discussion as to problem solving and issues on the XT1031 and various carriers but little mention as to the status of the latest weekly builds on the XT1028 still on Verizon in terms of functionality or hiccups from users. Does anyone have the latest versions running on their 1028? Are any of the data or service issues present when running it on Verizon?
Thanks.
Followup: Installed the latest 4/25 weekly on my XT1028 on Verizon Prepaid. Installed fine, got phone and SMS, but the network is identified as Boost Mobile and I have no mobile data. Is there a fix? Is a build.prop edit necessary for Verizon? Thanks.
Reboot then bootloop
Hi, I've been trying to get my installation of this ROM working for two days now, but keep running into an issue that I cannot seem to solve
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
The issue has been occurring on build 4/8, 4/25, and 5/2.
The exact steps I have been taking to install this ROM (for all builds) and then what happens:
Bootloader is unlocked
Going into recovery and wiping dalvik cache then factory reset (wipe)
Installing CM11 (latest snapshot) [on my first attempts only, not afterwards since it made no difference anymore]
Factory reset again (just to be certain)
Installing the zip for a build specified above
Installation always succeeds with no errors
Installing gapps-L-3-28-15 with success
Reboot into android
First boot always succeeds (and takes appropriate length of time)
Set up the phone (connect to wifi, google account, restore my apps [18 of them, just common popular ones, mostly Google actually], and apply a theme
Use it for a couple minutes (enable root and usb debug in Developer Settings, set my apps up, etc)
Restart two or three times without any hiccups
Suddenly, after a random reboot, the boot animation happens twice (instead of only once how it supposed to be)
Phone boots and shows "Android is starting..." and optimizes the apps (104 of them) one by one
Goes to "Starting apps..." and succeeds
The phone shows the lockscreen, but only for approximately 1-2 seconds
Phone reboots
CM boot animation runs twice, once for a long time then again for a shorter period of time
Phone goes through process described above (Android is starting, optimizes, then flashes lockscreen)
This just happens again and again and again
Steps I've taken to try and remedy the issue:
Run: "adb reboot" from computer while phone is optimizing apps
Hard reset the phone by holding the power button for 15 seconds
Run: "adb reboot bootloader" from computer when possible, then go into recovery and wipe both dalvik and normal cache
Swipe on the lockscreen as soon as I see it to see if I can get in (lockscreen does not respond though)
Go into recovery and shut the phone off, then start again
Let it loop for about 2 hours
I had also tried leaving the phone overnight looping, and when I woke, it was still looping, but after a eight or so more hours, I came back and found that it had booted and stayed on (and was working completely normally).
The phone was running stock 4.4.2 completely fine before this (with no reboot issues). I attempted installing the latest version of BlissPop, which exhibits a similar but still different issue (it would always boot into android [and not loop], but after a couple restarts, it showed an error about the System UI crashing that would pop up every time I dismissed it, and continued doing so after each restart after that). CM11 seems to be running well on the phone (but only in my very limited test while transitioning between ROMs and such).
I unfortunately cannot provide a log due to not being able to run any logging app during bootup, but hopefully I have provided enough details above to allow understanding of the issue and maybe bring suggestions on how to fix it. I can provide any more information needed on request. I really would like to get this phone back up and running (and especially on this ROM as I do love the work the creator has put into it).
Sorry for the very large wall of text :| Thank you in advance for any suggestions on how to proceed from here
tartilc said:
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
Click to expand...
Click to collapse
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
a_gert said:
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
Click to expand...
Click to collapse
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
I now have a logcat! I'm having trouble understanding what it is talking about, but I started logging as soon as the "Android is starting..." box changed status from "Optimizing apps x of x" to "Starting apps" and then stopped logging after a couple seconds of the boot animation. It is attached below (split into three parts).
EDIT: Attached what might be a better logcat reading (recording started right before lockscreen showed, I tried unlocking it, then stopped as soon as I saw the blue animation)
tartilc said:
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
Click to expand...
Click to collapse
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
XPOSED on Meticulous Rom?
Is there any way to get XPOSED working? I really want gravity box for LL.
Awesome. I was going to download this from your site today but it is showing an error with connecting to its database. None of the computers i have access to can get on your site.
no wifi no cellular network
and after i flashed cynogenmod 12.0 in my moto g 2014, there is no wifi nor network :'( what am i suppose to do now?
Ui crash
Is there anything special i need to do to flash this update? i'm running on the 408 build and every time i try ti go the next version there is an issue. Either data stops working or i get a system Ui crash like on the 530 build. I would love to get this issue fixed with the 606 build. Besides that, great job.
a_gert said:
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
Click to expand...
Click to collapse
Yeah that is a lot of jumps I'd be hella nervous myself lol
K well guys today is your day , as a_gert stated there is a boost 5.02 , and it does work fine on any cdma xt1031 so first flash that
-depending on signal you may wish to update your modem also there is only 4.4 modem for boost public
Buuuutttt nvm all that for now
The problem the ONLY problem I have had when bootlooping was that it was not prepped correctly and my phone came with 41.19 and came unlocked-
1.) Make sure you are on c/O SuperR-Developer -- PhilZ-Touch-6.59.0_LPK .img OR twrp * twrp-2.8.6.0.1-falcon_STOCK.img
**Notice For Even PhilZ I only Named the -IMG- Version which means flash it with adb properly please
***if ever after you flash it via recovery it will show partition mismatch which apparently is no problem just that the custom recovery does not match the factory one is all.. ..
1.) Download PhilZ-Touch-6.59.0-LPK.img to PC
2.) Reboot to bootloader
3.) Plug phone into PC
4.) Open terminal in directory where the img is located
5.) Issue the following command:
Code:
fastboot flash recovery twrp-2.8.6.0.1-falcon_STOCK.img
2.) Do a format of System w/EXT4 AND REBOOT INTO RECOVERY
3.) Format dalvik/art + Cache + Data w/EXT4 & REBOOT INTO RECOVERY
4.) Format Data PLUS data/media with f2fs then Do the 'factory wipe' then manually format data/media with f2fs again please ..
- SIDELOAD THE ATTACHED STOCK LOLLIPOP NO GAPPS GIVE IT TEN MINUTES REBOOT FEW TIMES/ POWER DOWN ONCE & REBOOT AGAIN
5.) Reboot into recovery and flash the first zip I have attached (I_nomodem is just IF you find your 4.4 radio baseband worked better and want to format it for LP again in the future WITHOUT LP radio included)
****EDIT - SEE VERY BOTTOM OF POST CENTERED AREA LOL
6.) Power off & reboot into recovery manually
7.) Flash your Rom (OR STOCK LOLLIPOP DEBLOATED AGAIN) + Kernel(if any custom one) + Gapps -wait 5-15 minutes for initial boot
* I recommend AeroKernel for the included stock lollipop 5.0 debloated if not the stock kernel or after flashing and few reboots to settle ,just follow instructions from that thread if any are needed..
Please anyone with any moto g don't think updating your bootloader is needed or even really safe whatsoever it is THE main reason moto phones get bricked or messed up otherwise it is not necessary or any kind of improvement yes once you are on an LP one leave it be..
Other flashing yeah okay, bootloader no if so proceed with utmost caution.
After this your modem will be updated with the cdma LolliPop one, if you have any signal issues or what not go to the stock modems section for your specific phone and flash the one for your specific carrier and/or find the "update RIL" flash thingie on here in moto G section and follow instructions but the boost modems work on all cdma variants of Moto G..
For whatever reason I could not upload files to xda I tried five times it kept dying so here there are on googldrive :good:
**Do not Click individual Item Use the Download Arrow At the Very Top of Page to DL the zip properly plz
1.) Falcon LolliPop Part Updater + Modem
2.) Falcon LolliPops Part Updater (No Modem)
_____________________________________________________________________________________________________________________________
--EDIT #2-- LolliPop 5.0 Falcon XT1031 debloated
SIDENOTE: IF YOU FORMAT DATA/MEDIA & DO NOT KNOW HOW TO SIDELOAD THE ABOVE STOCK DEBLOATED ZIP I'M PRETTY SURE YOU'RE NOT GONNA LIVE TO TELL BOUT IT
BE PREPARED TO SIDELOAD - REBOOT IMMEDIATELY AFTER SIDELOAD THE ZIP ROM IS COMPLETE NOT INTO RECOVERY NOT ANYWHERE ELSE SYSTEM REBOOT
-And wait 5-10 Minutes For First Boot - You Only Need to Do this for the first LP rom loadin after that normal flashing do NOT format data/media anymore after this initial setup
--You can try to just use the script, but it did not work for me after many tries the above was the real solution and has been perfect since
2,3,4,5,6,7
·Install flashable (Boost Mobile/CDMA XT1031 only):
·Download falcon_PhilZ-Touch-6.59.0_LPK.zip to phone
·Reboot into current custom recovery
·Flash zip
·Enjoy!
Use the script again to prepare you partition properly anytime you are about to flash a new rom clean after factory wipe/ format is done..
As I said before data/media is never necessary again after this and MAY not be this time but it is the only thing that kept me out of bootloops ,and if you do it yeah it will force you to sideload your rom it erases all leftovers and your rom zips off the internal card and formats them for fresh start The script does not format /media guys k no worries
------TWRP 2.8.6..1 does not seem to restore properly- -system write only thing .. PhilZ-Touch is fine as is twrp-2.8.6..0 also
Nice, got 41.19 BL!
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
rammsteinaus said:
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
Click to expand...
Click to collapse
K welcome
Arrite guys for a little clearer step by step see here please apologies carrying on and on I have been gone quite some time here http://forum.xda-developers.com/mot...-moto-g-xt1031-lollipop-t3132974#post61346260
It actually Runs really nice, really REALLY nice once the system app package I am adding shortly was used and tweaked out ..
Is it safe to flash cyanogenmod onto the verizon moto G - 1028 4.3 plus
Hello community ,
I had serious problems flashing cyanogenmod onto a galaxy S3 that was running stock 4.3 , verizon bricked my S3 , and said that the software was not authorized by Verizon. Does this problem exist across the board for any verizon phone running 4.3 or higher ?? If so ... then anything to do with flashing cyanogenmod onto a verizon phone should have warnings in BIG RED LETTERS ... because you cannot even buy a new phone with 4.2 on it anymore.
Issues flashing cm12.1 on XT1031 Please Help
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Moto G CDMA issues
citizen3rased said:
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Click to expand...
Click to collapse
Hello Citizen 3 , You are farther along than me. I have only successfully flashed cyanogenmod once , and that was on an S3 so it was straightforward. I still have not unlocked my bootloader. I have not been able to copy and paste the long strings of characters from motorola , inside command prompt. It would be so nice if Meticulus or one of the other developers could get this to be an official release. The Moto G , and a few other inexpensive phones ( LG realm , Kyocera Hydro latest version ) would work like greased lightning , if they were running CM12. Any help that you could offer with pasting the strings of unlock code would be so appreciated.
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.
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.
Hello all,
tl;dr: Location-UK. Rooted MotoG and installed CM11, found that the mobile network connectivity is gone. Flashed EU spec stock 5.0.2, still no luck. Status says Radio is off. What can I do to salvage it? (Still shows the correct IMEI).
Long story:
- I had a terribly slow, practically unusable (GB Retail spec) Moto G running on 5.0. So I decided to roll back to 4.4.
- Unlocked the bootloader successfully, but couldn't root it following the easy procedures listed widely everywhere. In the process, somehow rendered the 'sdcard' storage read-only.
- Rooted successfully using another method specifically written for Lollipop MotoG. A restart after that made the 'sdcard' read-write again.
- Installed TWRP from Playstore and tried backing up the ROM, but after backing up, the phone went into a boot-loop.
- Tried flashing a US Retail spec 4.4 to get out of the boot-loop, didn't work.
- Flashed TWRP via fastboot, pushed CM11 with adb and flashed. Finally it worked!
- But, no network. If I search manually for networks, it throws up an error. Sometimes even the Networks option was grayed out.
- Tried flashing the GB spec radio zip, no change.
- Wiped it all, tried flashing stock 4.4.4 GB retail ROM, it failed for some reason. No idea why.
- Wiped it again, flashed EU retail spec 5.0, it flashed fine, but still no mobile network. Tried with multiple SIMs, and tried reflashing CM11 and 5.0 multiple times; no luck.
- IMEI number is not reset to '0', still shows the correct IMEI, verified it against the battery cover.
Please advise. I would be much grateful! Thank you all in advance.
It's possibly Bootloader corruption - /userdata becoming read-only being a symptom. Bootloader and Kernel are inter-related, and Kernel plays a role in how Radio functions on many newer Android devices.
Flashing another motoboot.img does not appear to resolve this, however the 'Hard Unbrick' method might - once it supports Lollipop Bootloader.
Related: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
EDIT: It might be worth trying custom ROMs other than those based on CyanogenMOD - with possibly differing implementations of RIL/Radio Interface Layer.
lost101 said:
It's possibly Bootloader corruption - /userdata becoming read-only being a symptom. Bootloader and Kernel are inter-related, and Kernel plays a role in how Radio functions on many newer Android devices.
Flashing another motoboot.img does not appear to resolve this, however the 'Hard Unbrick' method might - once it supports Lollipop Bootloader.
Related: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
EDIT: It might be worth trying custom ROMs other than those based on CyanogenMOD - with possibly differing implementations of RIL/Radio Interface Layer.
Click to expand...
Click to collapse
Thanks for the advice. Do you have any specific ROMs in mind? I tried the stock 5.0.2 back, as mentioned in my OP, but that didn't help. Also tried BissPop ROM to no avail, but that's based on CM12, so that might be the reason. I have just downloaded an Unofficial AOKP ROM. Is that a non-CM one that you have in mind?
I also flashed the UK radio zip multiple times, no luck again. Everything else is working just fine.
hashdoom said:
Thanks for the advice. Do you have any specific ROMs in mind? I tried the stock 5.0.2 back, as mentioned in my OP, but that didn't help. Also tried BissPop ROM to no avail, but that's based on CM12, so that might be the reason. I have just downloaded an Unofficial AOKP ROM. Is that a non-CM one that you have in mind?
Click to expand...
Click to collapse
I was thinking of some of SlimSaber, or Dirty Unicorns.
Tried both SlimSaber and DirtyUnicorns and didn't work. Finally, used this method (http://forum.xda-developers.com/showthread.php?t=2542219) to reflash to stock 4.4.4 and everything is working fine now. Hurray!
Thanks for all the suggestions and help!
i had upgraded my mexi-maxx to lollipop a few months ago and could no longer stand it. outside of being picky with my phone, the GPS didn't work as I had hoped.
i reverted back to kitkat by means of a TWRP backup I had. Had some issues with doing so. some of my images would not work, but a stock on of KK did. could not use any of @ChazzMatt images either; nor factory images as RSD pinged a FAIL. started getting worried, but just about all good now.
the phone now boots directly to bootloader mode and i have to choose 'start' to boot into system.
is there a way to change this? thanks all.
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Semseddin said:
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Click to expand...
Click to collapse
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
snowboardwcu said:
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
Click to expand...
Click to collapse
You need to downgrade to 4.4.4 with stock images except gpt.bin or else, it is normal having issues like you're facing. Lollipop bootloader is meant to work on lollipop system. Anyway, just flash 4.4.4 full images with mfastboot except gpt.bin, then flash your twrp recovery and restore your kitkat nandroid. It will be fine.
I downgraded my xt1225 back in time with the same tutorial and it works fine.
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
snowboardwcu said:
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
Click to expand...
Click to collapse
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Semseddin said:
India firmware is as bogus as a software can get
Click to expand...
Click to collapse
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Semseddin said:
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Click to expand...
Click to collapse
snowboardwcu said:
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Click to expand...
Click to collapse
If you were just running stock LP -- which you say you do not want to do -- then @Semseddin is correct that Brazil and Mexico factory images are better than India. Just because they both have newer updates India was never given.
In my images thread you can see,
Brazil: QUARK_RETBR_5.0.2_LXG22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
vs
India: QUARK_RETEU_INDIA_5.0.2_LXG22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
Then, @Jaocagomez has an OTA which takes it to:
OTA to 22.34.16 Brasil Retail Stock Lollipop 5.0.2 /// Blur_Version.22.34.16.quark_retbr.retbr.en.BR.zip
But CM12.1 beats all that by having 5.1.1.
Yes, CM 12.1 (5.1.1) is still using the stock 5.0.2 kernel source -- because Motorola has not yet released 5.1 kernel source they gave to the XT1254 Droid Turbo back at the beginning of July. But it's still 5.1.1 with 5.02 kernel source, NOT 5.0.2. with 5.02 kernel source. It's a vast improvement! Stock 5.0.2 was too laggy for me.
So, for me running CM12.1 (or another 5.1.1 custom ROM) gives me the best of both worlds. I have the latest kernel source/radio that Motorola has released for our phones, while still having 5.1.1.
_________
Now having said all that, my wife and I have two XT1225.
I flashed both to India LP 5.0.2, then flashed CM.
I also re-flashed the India radio and bootloader (5.0.2) found in the CM12.1 op post just to make sure.
I have no problem with GPS. I use GPS every day. But I use TopNTP. See this post:
http://forum.xda-developers.com/showpost.php?p=62320192&postcount=624
_____
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Fixed this issue. See here:
http://forum.xda-developers.com/showpost.php?p=63048064&postcount=696
ChazzMatt said:
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Click to expand...
Click to collapse