Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)

Search This thread

xspyda

Senior Member
Mar 8, 2006
627
25
Ah OK so not the same f/w as in my screeny then, shame. I wanted to update as I said but that will likely cause problems with a return if I can't get back to stock.

WiFi just randomly stops working. No indication it has dropped, just no data throughput for a few minutes. I love way to resolve is turn off WiFi optimisation. Pretty sure it has to do with my Virginmedia Superhub 2 but I don't want to have to change that to make the phone work. Every other phone I've had works fine with it.
 

vpnair

Senior Member
Jun 12, 2010
133
186
Melbourne
If you want to update 4.4.3 EU/GB to 4.4.4, the easiest process (if you have unlocked bootloader) is to flash this this in recovery. Both GB and EU users have reported success.

I did it manually by flashing just the system.chunks from the firmware in the first post on my unbranded 4.4.4 EU and it allowed me to update to 4.4.4 via OTA (did not become Tesco).
 
  • Like
Reactions: Peace_B

xspyda

Senior Member
Mar 8, 2006
627
25
Well what do you know, mine just got the 4.4.4 update without having to do anything.

Would love to root now and add xposed but my problem remains getting this back to the official Tesco GB f/w if necessary.

This is what mine is showing now and I'm pretty sure this f/w isn't available to download for returning to stock purposes.

udyme7um.jpg
 
Last edited:
  • Like
Reactions: meekrawb

bleepyboop

Member
Mar 25, 2011
38
17
You seem to be saying that you installed this firmware, but you remain tesco - how did you actually flash the firmware?

Code:
mfastboot flash partition gpt.bin
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_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
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
 
  • Like
Reactions: Paraglider1982

lost101

Inactive Recognized Contributor
May 30, 2008
7,417
9,305
I suppose it's always possible the zip was mislabeled. Maybe someone else can confirm this is the case.
 

bleepyboop

Member
Mar 25, 2011
38
17
I suppose it's always possible the zip was mislabeled. Maybe someone else can confirm this is the case.

Two other people confirmed it earlier in the thread, although this may only be an issue with people coming from a tesco ROM (perhaps there are customisations that lie on another partition which hasn't been included).

Would be good to know whether people coming from a factory unlocked phone end up with a tescogb customisation by flashing the ROM by firmware-team.
 

vpnair

Senior Member
Jun 12, 2010
133
186
Melbourne
@bleepyboop

I can confirm that mine is unbranded factory unlocked and i flashed the Android 4.4.3 Retail EU to 'return it to stock'. But i only flashed the /system partition. And mine remained unbranded.

Code:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3

So if it is indeed a Tesco version, it may be in another file. Perhaps the boot.img... cant see anything else that would cause it?? Can anyone shed some light.

The other option, as suggested, is that flashing this firmware does not remove Tesco, and it remains that way.
 
Last edited:
  • Like
Reactions: Peace_B

xspyda

Senior Member
Mar 8, 2006
627
25
Any chance of a screeny of the 4.4.4 flash from the firmware team (on a Tesco handset)?

Mine has updated OTA now and I'd like to compare again.

Thanks.
 

Somcom3X

Inactive Recognized Developer
Aug 19, 2012
2,959
3,230
Metro Detroit
qupu9yvu.jpg


Still no update for the retail u.s.
The only good thing I find is a new kernel is coming.
That and the xt1042( us cellular CDMA?).
Looks like I'll be unifying the gsm.
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,417
9,305
Two other people confirmed it earlier in the thread, although this may only be an issue with people coming from a tesco ROM (perhaps there are customisations that lie on another partition which hasn't been included).

Would be good to know whether people coming from a factory unlocked phone end up with a tescogb customisation by flashing the ROM by firmware-team.
Just to clarify, while the images are provided by firmware-team - they originate from Motorola's servers. Following established tradition on Moto G, there should be a Retail EU firmware image and a TESCO branded-one.
 

bleepyboop

Member
Mar 25, 2011
38
17
Upon further inspection I suspect fsg.mbn is the culprit. With the original Moto G, fsg.mbn only contained the customisation for the ROM which was released. With the Moto G 4G, fsg.mbn detects which customisation it should use. If we could unpack it and manually flash the retail (emea) fsg.img, then the customisations should be removed.

Code:
RECIPE
------
eegb: 22a817b2457f776ab9238ba1f38c85d6eff8db4a  fsg.img
vffr: 98ff2c8dd26f115a1b1b92d98969cae2b84391bd  fsg.img
yoigo: 095e98052ffb90c79fb4647286bbf8917461d7a6  fsg.img
o2de: f6995b1213a7daad004fee870164a2cc9d1b92b0  fsg.img
safe: c8d74a52b014182386ee01d000fb85946298bb30  fsg.img
orafr: 4056d98292c57ff9631185a7b13d5e782b43db18  fsg.img
tmode: 3c396c8c967d776113b3cba90085ffccd0ff1b5a  fsg.img
emea: 87daed378c2c6d4bb97cee763bd12becd6a1e191  fsg.img
o2gb: c482d3674e0899f6d24442b724517887791d1390  fsg.img
emea_selfperso: dc00f6f9dac502d56e9d12f443fbee5ec8d41ad4  fsg.img
vfgb: d8c59095786ecb1b40781bbb24c427bf9c1fb573  fsg.img
tescogb: 31b730fbf3a0a86f9067b76a96dfa5e4420bbb64  fsg.img
vfde: 7689aacc3b1a4d4400142eaecae441098dc9632b  fsg.img
Code:
RECIPE
------
6010ba88074583847a09f6230852af89e9e21fc2  0.img.gz
ee9502c386e0a9381ab83aa62cc3a029e2b69b70  peregrine_o2de_3.img.gz
96cf4a41951412f05c6a399f80b364b0e78b64e9  peregrine_yoigo_3.img.gz
c506cd9ed9608b018c10d721cf7cce8e445f468e  peregrine_eegb_3.img.gz
657167127caa0d999a5c87447269a8bea54e3940  peregrine_vffr_3.img.gz
362298d498e5acdebf269f4607d9eda1ac4430b2  peregrine_tmode_3.img.gz
7a9298f49e58d3d924cd9d9883567d1b95ad9775  peregrine_orafr_3.img.gz
f22c2db0151256244595efe4f9db9f61d8d029c3  peregrine_vfgb_3.img.gz
1b5da86887ab534101cff5a0e270d9f981f05e30  peregrine_vfde_3.img.gz
10e10d32bc26453f1642f97d4193a90afc9e673a  peregrine_emea_selfperso_3.img.gz
c8c8b364ae9a9062a40d2770544c649c362a9797  peregrine_tescogb_3.img.gz
0370bce4334f8d3be370e15f29bc7a99f3092a78  peregrine_emea_3.img.gz
281de9e07684ecc2cec2d436b516d997347c5325  peregrine_o2gb_3.img.gz

Maybe someone with better knowledge can shed some light on this
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,417
9,305
Interesting stuff. I'll look into it asap.

EDIT: The fsg.mbn included in 4.4.3 Retail US for Moto G non-LTE also contains similar code. This may not be the reason branding is retained. Also I was under the impression the fsg partition only acted as a backup location for radio firmware. In theory someone (with branding other than Tesco) could dump their fsg partition as fsg.img and you could flash it. I doubt that is the reason branding is retained however.

If anyone wants to try the following prior to flashing: (if it works at all, but could result in lost IMEI - unknown outcome)
Fastboot erase fsg​
 
Last edited:
  • Like
Reactions: bleepyboop

xspyda

Senior Member
Mar 8, 2006
627
25
Just to clarify, while the images are provided by firmware-team - they originate from Motorola's servers. Following established tradition on Moto G, there should be a Retail EU firmware image and a TESCO branded-one.
I'm looking for the below f/w to enable me to 'stockify' a rooted moto g 4g on Tesco. Don't think it's available though?

8uqu2y6u.jpg
 

bleepyboop

Member
Mar 25, 2011
38
17
Interesting stuff. I'll look into it asap.

EDIT: The fsg.mbn included in 4.4.3 Retail US for Moto G non-LTE also contains similar code. This may not be the reason branding is retained. Also I was under the impression the fsg partition only acted as a backup location for radio firmware. In theory someone (with branding other than Tesco) could dump their fsg partition as fsg.img and you could flash it. I doubt that is the reason branding is retained however.

If anyone wants to try the following prior to flashing: (if it works at all, but could result in lost IMEI - unknown outcome)
Fastboot erase fsg​

Tried erasing fsg and reflashing fsg.mbn, but customisations remain. Really appreciate you looking into it though, thanks
 

clementinox

Senior Member
Jun 25, 2012
298
436
This is the link to Moto G 4G/LTE stock firmware for use by developers. Thanks to the Firmware-Team. Please Donate to them.

If you require it for other uses (Return to stock or updating) please refer to the relevant guides in the Moto G forum.

XT1039 (EU)
Android 4.4.3 (Retail EU) KXB21.14-L1.31
Android 4.4.4 (Retail EU-SS) KXB21.14-L1.46 + Mirror #1
Android 4.4.4 (ORA EU) KXB21.14-L1.46

XT1040 (BR)
Android 4.4.3 (Retail BR-SS) KXB21.14-L1.23-4

XT1042 (US)
Android 4.4.4 (USC) KXB21.14-L1.41

XT1045 (US)
Android 4.4.3 (Retail US) KXB21.14-L1.23-4

Enjoy!


Hi,
I currently have the MOTO G 4G on a canadian carrier Rogers and its also XT1040 with this version on it Android 4.4.3 KXB21.14-L1.23-4
DO you have a link for it? or would you recommend flashing the US version which seems to be closer to my version when looking at the numbers,
 

Top Liked Posts