Database Info

[Q] How to get new language!

Hi guys!
Recently i buy this Photon Q 4G LTE Sprint to my wife's birthday.
It's a wonderfull device with a nice hardware, but the best is the external keyboard (She likes it, because his old device was Motorola dextr, and she was used to), but we're from brazil and my first difficulty was to find a rom that support drivers without bugs.
So here i was: My first try was MIUI. I unlocked my bootloader, rooted and installed TRWP. Didi Backup, formated and installed MIUI, :good:
First i tryed with Kernell the UFO developed for it, and the device don't boot. After i tryed just the rom, but it has no modem or wifi. So i flashed up the stock rom modem img and worked fine.
But apks like "retrica" doesn't work with it, bringing black photos and others apks made for instragram. I love this rom and i have installed in my Xperia Play. It works perfect, but in this device have a lot of bugs, so i give up.
I know how to use it with bugs, but not my wife. Then i had to try another one.
I downloaded Cyanogenmod CM10.1, CM10.2, CM11 nightly, snapshot. Then after try all "Xt897" roms, i tryed all "moto_msm8960".
I can't get in any of this roms make my wifi or 3G work. I believe that modem is not compatible. Even if i tryed to flashed stock modem after, i still had no signal at all. No IMEI, no MAC Address, nothing. :crying:
This device have few alternative roms, so i decided try to translate the rom with less bugs at all. I picked up the stock rom JellyBeans 4.1.2, but this was my second failure. A language patch is something that you don't find in market, and to disassembly entire rom and work in a translate is something beyond my knowledges.
So i have an answer to someone that know how to do a fix patch to wifi in cyanogenmod(Specific "cm-11-20140518-NIGHTLY-moto_msm8960.zip" ), or someone good in translate rom, or input a language in stocked rom, like The Solutor did in " [Full ICS ROM] Multilanguage/Toggle2g /STK/Tethering" (but the rom he used was 4.0.4 and it have bugs).
I will be grateful for any help. :fingers-crossed:

Hmm, what's the language you want (CM11 already have lots of them - not in the list?), and what WiFi/3G problem are you having? And you also failed to RSD the phone back to stock?
My recommendation is you first sort the RSD thing out and get the phone back to stock 4.1.2, and flash everything from that onwards. Assuming that you don't do anything wrong in the process, you should have no quirks with WiFi/3G.
Sent from Google Nexus 4 @ CM11

Try MoreLocale2 for the stock ROM language issues.
As for the CM issues... I agree with Andy, if it works in stock form, it "should" work on CM - at least that has been my experience.
You are clean wiping / factory resetting before or after flashing CM yes? I see you have done this step for MIUI, so I am thinking that you have already done this step...
If you have, can you provide logs from CM if the wiping/RSD'ing doesn't work?

Thx for help guys...
AndyYan - The language i need is Portuguese(Brasil) and it has on CM 11 and MIUI.
I did it as you said. I downloaded stock from here:
http://sbf.droid-developers.org/phone.php?device=3
Rom version: Android 4.1.2 - Blur_Version.98.10.5.XT897.Sprint.en.US)
And flashed by RSD.
Everything ok till here. No errors, nothing wrong. Wifi working as well, and the network.
My MIUI was taken from here: http://forum.xda-developers.com/showthread.php?t=2444449 (GSM one).
Cool rom, it has wifi and network, but camera bugs with some apks. For me ok, but not for my wife. So this rom was discarded.
CM i dwonloaded from here: http://download.cyanogenmod.org/?device=moto_msm8960
The last one was: cm-11-20140521-NIGHTLY-moto_msm8960.zip (i tryed all of then "XT897" and "moto_msm8960", but none of them could get my network working. No wifi, no IMEI, no MAC, no wifi).
CM was my hope, because it has my language, but in all tries i did the wipe in cache, dalvik, system, factory, even internal memory, before installing, and cache or dalvik after flash. I tried this in all (tried not wiping too) and still has no modem.
After this, just for try, i flashed stock modem "NON-HLOS.bin". Still got no modem in any CM roms.
arrrghhh - i did try "MoreLocale2" for the stock rom, and "Set Locale and Language" (and more). This softwares did a nice job for keyboards and apks, but system stays intact in english. It need to be a real translation for my wife.
My guess is that this issue can be easily solved.
If all JB roms have the same system(at least for "moto_msm8960" processor kind ).
This ROM is generic for Motorola Atrix HD, Electrify M, Photon Q, RAZR HD, and RAZR M right?
Razr HD is a type of phone that came to my country.
Is it possible compile a system from Brasil career stock, for this phone with modem and anything else from my stock rom? Does it will crash my phone?

Please provide logs from the latest build of CM after booting and attempting to engage/connect to wifi.

Logs??
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.

Skymidt said:
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.
Click to expand...
Click to collapse
CM does create logs. If you're not familiar with them, the easiest way is to use an app from the Play Store... which I'm not sure how you will manage without wifi or mobile data, and I assume you are not familiar with adb.
I can go thru the detail, but it's a bit involved. Perhaps this thread will help you?
Once you know how adb works, there's actually an easier method than using adb logcat to output to a file - there are logs stored in '/data/logger'. So:
Code:
adb root
So you can have the permissions to pull the files, then pull them:
Code:
adb pull /data/logger
Will pull all of the log files to wherever your command prompt is. If you 'cd' (change directory) to your desktop, doing the adb pull will send all the log files to your desktop.
Let me know if you have any questions, good luck.

Logs from Adb
Yeap! I'm familiar with ADB!!
(i'm not expert in it, but i already did something with that...)
I don't know exactly what are you lookin for, so i did two logs.
First a complete boot:
Code:
adb reboot system
adb logcat -v long > boot_log.txt
And one for especific modem log from boot
Code:
adb reboot system
adb logcat WifiStateMachine:E *:S -v long > just_wifi_error.txt
(I believe this this won't help u a lot?!)
The first one is the most complete solution for this and have all the boot infos, errors and other things.
If am i wrong please say the correct command to use.

I forgot something...
In filemanager i can't access internal storage.
It shows /storage/emulated/0, and points to nothing.
If i'm right, this was a well know bug on CM 10.2, which supposedly been fixed in CM 11 right?!
I think that information can help to solve this bug...

Please try the adb pull command I sent... Those logs are not very helpful, and quite difficult to read.
However, I have a feeling if you use RSD Lite to flash everything back stock, confirm it works, then start with the latest CM, I'd be curious if it works.
Also, someone mentioned they needed to install the CM10.2 snapshot before going to CM11 - or else BT and wifi did not work.

Eureca...
That is something that i didn't tried! I'd never flashed CM 10 in first!!!
I'm downloading "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip ".
Fisrt i'll flash stock "Blur_Version.98.10.5.XT897.Sprint.en.US" with RSD.
Then fastboot "logo.bin" (to avoid warning unlocked), and TRWP(my stock have a original recovery that can't install CM. I can edit XML, but to cleanse my conscience i'll let this way).
After i'll install "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip" with TRWP and boot with this one.
Then i'll flash "cm-11-20140526-NIGHTLY-moto_msm8960.zip ".
But i'll have to do this at night(it's 12pm here), because i'm working today.
If that don't work i'll pull the log that you said here, but I come back to thank.

Same problem
I confess I was hopeful in that case you said to flash first the CM 10.2.
But again failed. I tried two ways:
In both I tried to install the Snapshot CM 10.2, then the CM 11.
There is no way that cell boot with "CM 10.2" in any case. That saty on boot animation for several time(i waited 30 minutos each).
In the first I downgraded to version 4.0.4 stock to see if the modem worked.
After that i flashed CM 10.2 that stood in boot animation, then CM 11 booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.0.4.7z)
On the second attempt, I used the default stock 4.1.2.
After CM 10.2 which was stucked on boot animation again, then CM 11 again booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.1.2.7z)
Strange thing happened on both CM 11 boot. When the system's load, it shows a message "The clock stopped". This is strange thing for me.

Can you wait for CM10.2 to boot...? There is a fsck process which sometimes takes quite a long time to boot.
Also, for your FC issue - you are clean flashing the ROM everytime? You are doing a factory reset everytime you flash a new ROM?
Edit - looking at your logs, I don't think the fsck is the issue... something is causing the CM10.2 boot to die over and over. Please try clean flashing...

I clean everything before.
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?

Skymidt said:
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?
Click to expand...
Click to collapse
Yes, factory reset == clean flash.
As for the long boot, I'm not sure the fsck is your issue - basically there is a process which runs a disk check, and sometimes this will make the boot take quite longer than usual. I can't say how long, I've never personally experienced the issue.
However, the fact that CM10.2 isn't booting is a little disturbing. I've heard some people report 45-60 mins... can you do me a favor, charge up the phone, and try to let it boot for at least 90 minutes?
If at the 90min mark it still hasn't booted, pull logs and post them.
Thanks.

The logs contain references to apps that are present only in stock firmware.
That means the CM boot is actually not happening in a clean environment (the data wipe/factory reset in TWRP hasn't worked as it should?).
Please try to use OpenRecovery 2.09 instead of TWRP (as OR is the recovery I personally use and watch for possible bugs) to wipe the device and to install CM11 - http://forum.xda-developers.com/showthread.php?t=2211579&page=10
When installing CM in recovery, you will probably also want to install the gapps package - http://wiki.cyanogenmod.org/w/Google_Apps
Btw., CM11 expects the baseband (modem) and other partitions the be at the 4.1.2 stock level. Experiments with 4.0.4 are useless.
Please post the logs from CM11 boot.
You will need to enable the logger under CM11 by
Code:
su
setprop persist.log.aplogd.enable 1
in Terminal app or ADB shell, it's not enabled on CM11 by default.

Links are broken
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?

Skymidt said:
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48551561&postcount=75
I'm on an older version of TWRP, and it has never failed me... that's a shame really. I'll try to update and see what's what. In the meantime, flash OpenRecovery I linked above ^^.

Skymidt said:
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
Click to expand...
Click to collapse
TWRP 2.6.3.x should also work properly.
@arrrghhh, so you see it's not just me having the "wiping /data reboots the recovery" problem... I've already sold my PQ (might buy a new one in the future), but please do help let this problem be known to whoever's developing TWRP for us
Sent from Google Nexus 4 @ CM11

I can't believe it works
Unbelievable! :laugh:
This very simple solution worked for me.
My TRWP did not work right.
He said he had done successfully in cleaning the cache and manufactures, but did not.
I downloaded the link you guys sent me and it worked on the first try.
Not needed before installing CM 10.2. Already installed in the first CM 11, has worked with modem and everything. Now I can configure the GSM network my country and language of the country for my wife (PR-BR).
I want to thank the efforts of user @ AndyYan to respond, the attention given by the user @ Arrrghhh teaching me with patience, and the solution given by the user @ kabaldan. :victory:
You are awesome for this forum. Thanks for everything.
If you still want the log I get, but I think with everything working, you guys should already know the outcome.

Having real trouble updating to Lollipop (recovery help?)

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.

Install CM11 from stock 5.0.2

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.

Trying to do CM13 to CM12.1 downgrade on soft-bricked

So I decide to upgrade a a couple of weeks after OTA update to CM13 arrived. Turns out it was a massive mistake, especially since no backup, no ADB enabled, no root and nothing custom. This is the best I have so far: https://jira.cyanogenmod.org/browse/BACON-4808 (summary: System UI and com.android.phone both crash on startup). Sad thing is I can see phone working just fine behind the crashed UI (getting mail, notifications etc.) I know my data is in there but cannot get to it.
Anyway, customer support is responsive but I am not sure they will let me keep my data.
I am pretty much starting from scratch regarding flashing, and the first few hours was deciphering abbreviations and other bull. Other than that I am decently proficient with the tech stuff.
Would be grateful if you guys can help point me in the right direction. The info I currently have:
* I want to keep my data
* images here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
* I know that my phone is recognized by PC if I put it into ADB sideload mode (didn't yet try whether it works though)
* phone is also recognized when in fastboot
* possibly downgrade might work, but I am trying to find a method that will let me keep the data, if I get glitches I don't care for now
What I am not so sure about:
* flashing for example cm-12.1-YOG7DAS2K1-bacon-signed.zip in full should let me keep the data, true?
* taking fastboot image and just flashing boot&system should also let me keep the data, true? Did I miss anything?
What do you guys suggest I do? I know that in the end I might crash everything anyway, but at least I want to do the best I can (And make that backup soon after). Thanks for all and any help!
edit: Did the sideload flashing, that went fine, is easy. Problem is those images seem not to work for me anyway (bootloop). Probably because I didn't wipe userdata.

maybe try to use the restore tool (http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851) its pretty old (CM11s) but if it workd then refalsh the TWRP and update your phone to cm12.1 (with the required firmware)

A good question after all I did: Did anyone ever successfully downgrade from 13 to 12.1 without full data wipe?
p.s. it is very very easy to downgrade, it just doesn't work since OS upgrade makes changes to local data making it incompatible. This is what I did:
1) down+power on
2) chose upgrade and sideload upgrade from adb
3) while in that menu phone will wait for the update, just connect it to pc and do adb sideload image.zip (image needs to be signed ordinary image not the fastboot one)
4) wait until it completes and reboot phone
Tried all 4 CM12.1 images to no avail.

Dear all,
After flashing cm-13.0-ZNH0EAS2JK-bacon-signed FROM cm-12.1-YOG7DAS2K1 through TWRP on my rooted OPO as usual i do. MY mobile stuck in boot loader "CYANOGEN MOD READY" And not starting even after 45 mins.
So again i installed cm-12.1-YOG7DAS2K1-bacon-signed. Working fine. Tried many tiimes by wiping data,cache,dalvik too. But every time im stucking at boot loader "CYANOGEN MOD READY" . Please suggest me the best way to shift to marshmallow. I dont want to unroot.

skundurthy said:
Dear all,
After flashing cm-13.0-ZNH0EAS2JK-bacon-signed FROM cm-12.1-YOG7DAS2K1 through TWRP on my rooted OPO as usual i do. MY mobile stuck in boot loader "CYANOGEN MOD READY" And not starting even after 45 mins.
So again i installed cm-12.1-YOG7DAS2K1-bacon-signed. Working fine. Tried many tiimes by wiping data,cache,dalvik too. But every time im stucking at boot loader "CYANOGEN MOD READY" . Please suggest me the best way to shift to marshmallow. I dont want to unroot.
Click to expand...
Click to collapse
Take a backup of your internal storage
Flash factory images of CM13 using Index #8 http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
After flashing factory images, flash TWRP (Index #8)
After flashing TWRP, flash SuperSu from TWRP http://download.chainfire.eu/supersu-stable

In a right mess trying to return to stock

Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?

What Firmware did your XT1032 originally come with? or which Carrier?

Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !

I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​

Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !

Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?

OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!

@aneng64 - You have not done what I told you to do. Read my post again.

Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.