Hello, I have a XT1032 from Tesco Mobile.
I unlocked the bootloader and flashed the GPE Firmware GPE_XT1032_KOT49H.M004_CFC.xml
I used mototool at first and tried manually using fastboot.
Everything works except I keep getting some random error about my SIM card been removed and added (attached).
I tried to flash the fsg.mbn from stock but it makes no difference.
I did get some errors on fastboot but everything complete with the OKAY message.
any suggestion please?
thanks in advance
I realise its happened since you flashed so probably software related. But is it worth actually physically removing the sim and reinserting just to rule out a genuine dodgy/dirty sim connection.
Also I'm thinking of flashing GPE over my UK retail phone. Did you flash all files inc modem and gpt.bin etc. I am wondering if its worth me just flashing system and boot partitions and nothing else. No harm in me trying that I guess.
scott_doyland said:
I realise its happened since you flashed so probably software related. But is it worth actually physically removing the sim and reinserting just to rule out a genuine dodgy/dirty sim connection.
Also I'm thinking of flashing GPE over my UK retail phone. Did you flash all files inc modem and gpt.bin etc. I am wondering if its worth me just flashing system and boot partitions and nothing else. No harm in me trying that I guess.
Click to expand...
Click to collapse
Yes, I actually went to my carrier and got a replacement card but since it didnt work I went back to Stock and it works fine so it must be GPE related.
This is what I used ( I am on Mac osx):
./fastboot flash partition gpt.bin
./fastboot flash motoboot motoboot.img
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery recovery.img
./fastboot flash system system.img_sparsechunk1
./fastboot flash system system.img_sparsechunk2
./fastboot flash system system.img_sparsechunk3
./fastboot flash modem NON-HLOS.bin
./fastboot erase modemst1
./fastboot erase modemst2
./fastboot flash fsg fsg.mbn
./fastboot erase cache
./fastboot erase userdata
./fastboot reboot
I got some warnings but all commands gave "okay"
I wonder if its worth you keeping non-gpe for modem partition and fsg and just try flashing gpe system and boot partitions. Maybe as gpe is for USA really its causing some issues to use gpe modem bits and pieces.
scott_doyland said:
I wonder if its worth you keeping non-gpe for modem partition and fsg and just try flashing gpe system and boot partitions. Maybe as gpe is for USA really its causing some issues to use gpe modem bits and pieces.
Click to expand...
Click to collapse
Just tried that. Flashed back stock and confirmed everything was working fine. I then reflashed GPE without modem and fsg keeping the stock ones but got the same. Not sure the problem is on the radio at this point.
Sent from my XT1032 using Tapatalk
If anybody has the same problem, I was able to fix it by flashing the latest Radio 355.66.00R from the latest stock update.
I yesterday flashed GPE on my XT1032 (Germany Retail).
But i flashed it using the *.bat /eu file.
No SIM Card error.
Flashed gpe on french moto g, there is no errors.
only radio apps is missing.
It is not missing. It is simply not a feature of GPE.
Related
Someone can help me downgrading my MOTO G with unlocked bootloader from GPE to stock 4.3.
I've been trying but I get "Image is too large" when I try to flash "system.img".
I want to downgrade to stock 4.3 Claro Argentina firmware.
Please, I really need your help!
cocoralladoo said:
Someone can help me downgrading my MOTO G with unlocked bootloader from GPE to stock 4.3.
I've been trying but I get "Image is too large" when I try to flash "system.img".
I want to downgrade to stock 4.3 Claro Argentina firmware.
Please, I really need your help!
Click to expand...
Click to collapse
Could be two things:
1. You may need to flash gpt.bin from 4.3 (included in official 4.3 download) as this will create a new correctly sized partition table.
2. Make sure you use motorola fastboot to flash (known as mfastboot) and not the Google fastboot.
Not a problem. Download http://sbf.droid-developers.org/download.php?device=14&file=124
And follow:
Code:
fastboot flash partition gpt.bin #if this fails, ignore it and carry on
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I have same problem too...any firmware I flash I get those " image is too big " errors and when I restart I am stuck at bootloader? any ideas?
gd91 said:
I have same problem too...any firmware I flash I get those " image is too big " errors and when I restart I am stuck at bootloader? any ideas?
Click to expand...
Click to collapse
Unfortunately i'm in the same boat, stuck at boot. Flashing different zips doenst seem to help. I think the partition has changed since the 4.4.4 OTA from 4.4.2 on the GPE. It's impossible to flash a different rom at the moment. Hopefully there will be a fix soon.
Yes ...I read the same thing in several places...it has to do something with that gpe firmwares partition.....anyone have any idea how to fix this please?
same problem here. I was able to fix my phone partially with
1, factory reset in recovery (twrp)
2, adb Cyanogen rom
3, fixing reception with
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
using gpe 4,4 fsg
Can you explain that in "noob language " please ? ...did you managed to flash official firmware after that?
Is fastboot mode available? If yes then you could just either 'dd' them or flash via fastboot, starting with sys partition. Don't touch the efs.
Before i begin, i am aware there are mutliple other threads about downgrading from KitKat 4.4.2 to JB 4.3 and also have come across the procedure of downgrading. But my query is still different from other ones.
Here is my query, I own a XT1033 dual sim asia with 4.4.2 OUT OF THE BOX. Now, can i manually flash a 4.3 dual sim asia firmware with this status...?
Reason bcz my factory version is 4.4.2 and i was willing to try 4.3 because 4.4.2 has numerous problems with Signal drops, Huge fluctuation in signal, Auto switching to aeroplane mode and back. I came across users of 4.3 out of box and have heard that 4.3 JB had been great in signal quality. Please assist.
==vj== said:
Before i begin, i am aware there are mutliple other threads about downgrading from KitKat 4.4.2 to JB 4.3 and also have come across the procedure of downgrading. But my query is still different from other ones.
Here is my query, I own a XT1033 dual sim asia with 4.4.2 OUT OF THE BOX. Now, can i manually flash a 4.3 dual sim asia firmware with this status...?
Reason bcz my factory version is 4.4.2 and i was willing to try 4.3 because 4.4.2 has numerous problems with Signal drops, Huge fluctuation in signal, Auto switching to aeroplane mode and back. I came across users of 4.3 out of box and have heard that 4.3 JB had been great in signal quality. Please assist.
Click to expand...
Click to collapse
Are you willing to unlock bootloader? or you want to stick with a locked bootloader?
deej_roamer said:
Are you willing to unlock bootloader? or you want to stick with a locked bootloader?
Click to expand...
Click to collapse
I already have an unlocked bootloader and on CM11 since long time. But signal fluctuation issues seems to be in core of 4.4.2 release. I tried Stock Radios of XT1033 Asia, Brazil and India and also flashed stock rom via fastboot commands but none fixed this bug. I gathered feedback from 4.3 users that signal strength was great and there were no crashes in signal (Suddenly aeroplane mode and back normal during ongoing call or during idle status). So, was planning to give a try for 4.3. But i have 4.4.2 out of the box (factory version)
So i was puzzled whether its possible or not possible to try 4.3 with this status
Are there any side effects of downgrading alike breakage of OTA?
Breakage of Bootloader?
Sorry about the essay
Edit : Signal issues only on WCDMA only mode on KK.
==vj== said:
I already have an unlocked bootloader and on CM11 since long time. But signal fluctuation issues seems to be in core of 4.4.2 release. I tried Stock Radios of XT1033 Asia, Brazil and India and also flashed stock rom via fastboot commands but none fixed this bug. I gathered feedback from 4.3 users that signal strength was great and there were no crashes in signal (Suddenly aeroplane mode and back normal during ongoing call or during idle status). So, was planning to give a try for 4.3. But i have 4.4.2 out of the box (factory version)
So i was puzzled whether its possible or not possible to try 4.3 with this status
Are there any side effects of downgrading alike breakage of OTA?
Breakage of Bootloader?
Sorry about the essay
Edit : Signal issues only on WCDMA only mode on KK.
Click to expand...
Click to collapse
Ideally, There are not side effects but
there are increased chances of something to go wrong!
Well, Here is the firmware!
==vj== said:
I already have an unlocked bootloader and on CM11 since long time. But signal fluctuation issues seems to be in core of 4.4.2 release. I tried Stock Radios of XT1033 Asia, Brazil and India and also flashed stock rom via fastboot commands but none fixed this bug. I gathered feedback from 4.3 users that signal strength was great and there were no crashes in signal (Suddenly aeroplane mode and back normal during ongoing call or during idle status). So, was planning to give a try for 4.3. But i have 4.4.2 out of the box (factory version)
So i was puzzled whether its possible or not possible to try 4.3 with this status
Are there any side effects of downgrading alike breakage of OTA?
Breakage of Bootloader?
Sorry about the essay
Edit : Signal issues only on WCDMA only mode on KK.
Click to expand...
Click to collapse
If you are not using second sim, better flash single sim global retail.. and update it to 176.4.1.. I'm not facing any issues like signal drop, flight mode and all...
Sent from my XT1032 using XDA Premium 4 mobile app
Thank you bros for giving your view and ideas.
I undertook risk and tried straight way downgraded yesterday.
Conclusion: 4.4.2 Out of Box (factory version) phones are also downgrade able to 4.3 JB
I downloaded firmware version "Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03" from HERE and also downloaded mfastbootV2 tools. Extracted ROM and Mfastboot tools in same folder.
Saved following commands in notepad and saved it as StockJB.bat and placed in same folder. Executed the bat file and successfully downgraded to 4.3 within a minute.
Code:
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
pause
mfastboot reboot
==vj== said:
Thank you bros for giving your view and ideas.
I undertook risk and tried straight way downgraded yesterday.
Conclusion: 4.4.2 Out of Box (factory version) phones are also downgrade able to 4.3 JB
I downloaded firmware version "Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03" from HERE and also downloaded mfastbootV2 tools. Extracted ROM and Mfastboot tools in same folder.
Saved following commands in notepad and saved it as StockJB.bat and placed in same folder. Executed the bat file and successfully downgraded to 4.3 within a minute.
Code:
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
pause
mfastboot reboot
Click to expand...
Click to collapse
hello i have motto g dual sim indian version..kitktat out of the box...now as mentioned m also facing signle drop issue in 2nd sim sometimes.......now question is if flashed moto g with cwm then warranty will be void ? and after then can i receive OTA update ? or say..if comes to any hw prob...can i flash with stock android and go to service center in warranty time ? warrant is main concern..thats y m asking this silly question,,,,
ankitsuthar said:
hello i have motto g dual sim indian version..kitktat out of the box...now as mentioned m also facing signle drop issue in 2nd sim sometimes.......now question is if flashed moto g with cwm then warranty will be void ? and after then can i receive OTA update ? or say..if comes to any hw prob...can i flash with stock android and go to service center in warranty time ? warrant is main concern..thats y m asking this silly question,,,,
Click to expand...
Click to collapse
Warranty :The answer lies within your question mate. Before installing CWM you need to unlock Bootloader (Primary step without fail). And unlocking bootloader itself permanently voids your warranty bcz you will be submitting the oem code and requesting motorola for unlock key. Therefore, they void your warranty there and email you the unlock key.
Another case, if your factory version is 4.4.2 and you downgrade to 4.3 may also void your warranty (Not very Sure). Bcz you are flashing a non-factory version.
OTA Update : Yes, OTA will be working as confirmed by @Sk.D downgrading to 4.3. And upon upgrading back to 4.4.2 also OTA works as confirmed by me.
Signal : The signal crash (Auto switch to Aeroplane and back normal) bug is not available in 4.3. But the signal drop upon covering bottom half of your phone in a moderate 3g coverage area is same on 4.3 as well 4.4.2
==vj== said:
Warranty :The answer lies within your question mate. Before installing CWM you need to unlock Bootloader (Primary step without fail). And unlocking bootloader itself permanently voids your warranty bcz you will be submitting the oem code and requesting motorola for unlock key. Therefore, they void your warranty there and email you the unlock key.
Another case, if your factory version is 4.4.2 and you downgrade to 4.3 may also void your warranty (Not very Sure). Bcz you are flashing a non-factory version.
OTA Update : Yes, OTA will be working as confirmed by @Sk.D downgrading to 4.3. And upon upgrading back to 4.4.2 also OTA works as confirmed by me.
Signal : The signal crash (Auto switch to Aeroplane and back normal) bug is not available in 4.3. But the signal drop upon covering bottom half of your phone in a moderate 3g coverage area is same on 4.3 as well 4.4.2
Click to expand...
Click to collapse
Thank you mate....for this much clear ans.....its better to keep with stock until 1 year....
stuck up in bootloop
==vj== said:
Thank you bros for giving your view and ideas.
I undertook risk and tried straight way downgraded yesterday.
Conclusion: 4.4.2 Out of Box (factory version) phones are also downgrade able to 4.3 JB
I downloaded firmware version "Blur_Version.14.85.4.falcon_umtsds.AsiaRetail.en.03" from HERE and also downloaded mfastbootV2 tools. Extracted ROM and Mfastboot tools in same folder.
Saved following commands in notepad and saved it as StockJB.bat and placed in same folder. Executed the bat file and successfully downgraded to 4.3 within a minute.
Code:
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
pause
mfastboot reboot
Click to expand...
Click to collapse
followed all the process religiously but the phone stucks in bootloop where as when i flash it with the 4.4.2 it boots normal....i wipe cache and data before all this....what can be the reason please guide...bootloader is unlocked
syedihtisham said:
followed all the process religiously but the phone stucks in bootloop where as when i flash it with the 4.4.2 it boots normal....i wipe cache and data before all this....what can be the reason please guide...bootloader is unlocked
Click to expand...
Click to collapse
Easier way would be to Grab the OTA package of 4.4.4 and update it via stock recovery. Provided you need to on 4.4.2 unrooted and unaltered status.
I haven't tried downgrading from 4.4.4 nor have tried flashing 4.4.4 via fastboot yet. Maybe you made some typo in your command lines.
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
pause
mfastboot reboot
THIS IS WHAT I PASTED IN NOTEPAD AND SAVED AS .BAT FILE.....any corrections plz.....i tried doing ur stuff while i was running 4.4.2 rooted.....what can be causing this tuck on bootloop
---------- Post added at 11:56 PM ---------- Previous post was at 11:16 PM ----------
==vj== said:
Easier way would be to Grab the OTA package of 4.4.4 and update it via stock recovery. Provided you need to on 4.4.2 unrooted and unaltered status.
I haven't tried downgrading from 4.4.4 nor have tried flashing 4.4.4 via fastboot yet. Maybe you made some typo in your command lines.
Click to expand...
Click to collapse
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
pause
mfastboot reboot
THIS IS WHAT I PASTED IN NOTEPAD AND SAVED AS .BAT FILE.....any corrections plz.....i tried doing ur stuff while i was running 4.4.2 rooted.....what can be causing this tuck on bootloop........two problems that i feel can be causing this are there are a few folders other than the main folder in the firmware which are not extracted by me into the root folder may be that is causing this or may be i need to unroot before doing all this....any help..... very grateful for ur response
Hi guys, so i flashed a Moto G GPE rom onto my phone, got sick of seeing 3G rather then H or H+ and have decided to move back to Stock Retail.
I have a problem though when i use the guide on the FAQ ( the mfastboot way) everything i flash gets the okay appart from the system spasrsechunks? that gets some sort of error and it says error okay? Well apart from that after i reboot the phone, it has the warning sign but then uses the google bootanimation? ive left it on a good couple of minutes to see if it will boot but it doesnt seeem to want to..
Clarkiieh said:
Hi guys, so i flashed a Moto G GPE rom onto my phone, got sick of seeing 3G rather then H or H+ and have decided to move back to Stock Retail.
I have a problem though when i use the guide on the FAQ ( the mfastboot way) everything i flash gets the okay appart from the system spasrsechunks? that gets some sort of error and it says error okay? Well apart from that after i reboot the phone, it has the warning sign but then uses the google bootanimation? ive left it on a good couple of minutes to see if it will boot but it doesnt seeem to want to..
Click to expand...
Click to collapse
Google animation means that you still have the gpe rom on your phone. This happened to me before when i flashed the GPE rom too. What you need to do is flash your firmware again. Download the stock firmware form this guide: http://forum.xda-developers.com/showthread.php?t=2542219 Then what you need to do is run these commands MANUALLY! As in 1 by 1.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Yeah I sorted it thanks no 4.4.2 ROM would work trued multiple times until I tries a 4.3 and downgraded then it worked and updated to 4.4.2 ora
Sent from my XT1032 using Tapatalk
So,tpday was a hard day for me. Yesterday i installed 4.4.2 GPe rom on my xt1032 and immediately got a 4.4.4 update,and of course,i updated. Tried to install aero kernel,and i ended up in a boot loop,so i tried to install a stock eu xt1032 firmware,and ended in a brick. I managed to unbrick it and install a custom rom (i can post a tutorial on unbricking if you guys want) but,i want to install stock xt1032 firmware,but when i try to flash it,it's constantly giving errors. For instance, gpt.bin always throws an error,and i have to flash a custom rom again. Can anyone help? Thanks in advantage
Sent from my Moto G using Tapatalk
DeHuMaNiZeD said:
So,tpday was a hard day for me. Yesterday i installed 4.4.2 GPe rom on my xt1032 and immediately got a 4.4.4 update,and of course,i updated. Tried to install aero kernel,and i ended up in a boot loop,so i tried to install a stock eu xt1032 firmware,and ended in a brick. I managed to unbrick it and install a custom rom (i can post a tutorial on unbricking if you guys want) but,i want to install stock xt1032 firmware,but when i try to flash it,it's constantly giving errors. For instance, gpt.bin always throws an error,and i have to flash a custom rom again. Can anyone help? Thanks in advantage
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
gpt and motoboot will give you errors, you should skip those in order to downgrade, the rest of the files should flash without problems. I have flashed stock 4.4.3, downgraded to 4.4.2, installed GPE 4.4.2 to get 4.4.4 and then I flashed 4.4.2 Germany to get stock 4.4.4. Since I upgraded to 4.4.3 I had to skip gpt and motoboot and had no issues.
alresave said:
gpt and motoboot will give you errors, you should skip those in order to downgrade, the rest of the files should flash without problems. I have flashed stock 4.4.3, downgraded to 4.4.2, installed GPE 4.4.2 to get 4.4.4 and then I flashed 4.4.2 Germany to get stock 4.4.4. Since I upgraded to 4.4.3 I had to skip gpt and motoboot and had no issues.
Click to expand...
Click to collapse
Thanks bro,i did not know that! Saved me a lot of nerves!
So,does anyone want a tutorial on how to succesfully downgrade?
Sent from my Moto G using Tapatalk
edit:no,cannot install stock with this method man. i got sparsechunk errors. and i really want to boot stock rom,i'm sick of custom roms.i regret the day when i converted my moto g to GPe. if anyone has a way to return to xt1032 from 4.4.4 GPe,please share it.and for those that don't know,don't ever convert your moto g to GPe.
I went from GPE 4.4.4 back to stock yesterday without flashing gpt.bin and motoboot.img with no issues. I then got the official Moto 4.4.4 OTA which worked fine.
I have an unlocked UK device so I flashed the most recent UK 4.4.2 ROM (Blur_Version.176.44.1.falcon_umts.Retail.en.GB),
The sparsechunk files have different names to those mentioned in the downgrade guide though.
Here's the commands I used:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
rec71 said:
I went from GPE 4.4.4 back to stock yesterday without flashing gpt.bin and motoboot.img with no issues. I then got the official Moto 4.4.4 OTA which worked fine.
I have an unlocked UK device so I flashed the most recent UK 4.4.2 ROM (Blur_Version.176.44.1.falcon_umts.Retail.en.GB),
The sparsechunk files have different names to those mentioned in the downgrade guide though.
Here's the commands I used:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Yes,i know that..wierd,since i tried to flash UK rom yesterday and noting..when i try to flash sparsechunk files,it says image too large on my phone's screen..
Sent from my Moto G using Tapatalk
Let's see.
I was running 4.4.4 Paranoid Android, but then I decided revert to a stock motorola rom.
I'm using an XT1033 converted to 1032 GPE. Long story short, wiped everything and phone got stuck at bootlogo.
Used flashboot and flashed stock 4.4.2 GPE Rom running fine currently after several tries although mobile network won't work.
"Error while searching for networks"
Tried installing different modems, still nothing. Any help?
To get a working GPE (and GPE is only XT1032) you could try this way:
1) flash this
2) download GPE 4.4.4
3) when you flash the GPE exclude the following commands:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
You just gotta flash your 4.4.4 stock firmware. You can do that just by downloading the Motorola Device Software Updater and in like 15 min (depending on your internet speed) you will have your Moto G working again.