Database Info

[GUIDE] Rooted KitKat 4.4.2 on International phones

The below guide should result in a stock, rooted 4.4.2 phone for International (i.e. non AWS) Moto Gs without going through the monkey business of flashing 4.3 US and then hoping that the OTA works for you. Replacing the image files with the ones for AWS should give the same for the AWS version but lacking a phone I won't be able to test that.
All hardware will work just fine but there will be two side effects from going to the US firmware
1) You lose the carrier name in the topleft (which I actually like)
2) H icon will not show anymore (instead you will get 3G) but HSPA is used where available (i.e. you get the exact same speed as on the other firmwares that display the H)
First, we will assume you have an unlocked bootloader. If not, this is not for you.
Second, grab the 4.4.2 US International image from here: http://sbf.droid-developers.org/download.php?device=14&file=786
As outlined in various threads around here, it needs to be flashed in the bootloader with the following commands (this will wipe data so take precautions if you need any, note: it is recommended that you execute these line by line, as pasting the whole thing into a CMD shell has given weird results at times):
Edit: added mfastboot for convenience: http://forum.xda-developers.com/attachment.php?attachmentid=2475643&d=1388068310
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
(Linux or OSX users need to use the respective versions of mfastboot, obviously)
You now have a stock 4.4.2 US firmware on your phone, all hardware is working. If you do not need root, congrats, you are done.
Now, if you want root, the only way that worked for me was the following approach (thanks to http://forum.xda-developers.com/showthread.php?t=2583652) to restore CWM first, Grab http://forum.xda-developers.com/attachment.php?attachmentid=2473360&d=1387939887, unzip it and then run
Code:
mfastboot flash motoboot motoboot.img
Now reboot to bootloader and flash CWM as usual (get cwm from http://forum.xda-developers.com/showthread.php?t=2563599):
Code:
fastboot flash recovery CWMrecovery.img
Reboot to CWM and install supersu as usual (find it at http://download.chainfire.eu/supersu)
And finally, if you want to get rid of the ugly warning on boot (thanks to http://forum.xda-developers.com/showthread.php?t=2548530), you need to download http://forum.xda-developers.com/attachment.php?attachmentid=2422567&d=1385748174, unzip it and flash it with fastboot
Code:
fastboot flash logo logo.bin

What's AWS?

monchee said:
What's AWS?
Click to expand...
Click to collapse
The codename for the US version of the phone (uses different radio frequencies)

nupi said:
The codename for the US version of the phone (uses different radio frequencies)
Click to expand...
Click to collapse
does the US Global GSM count as non AWS? is the custom recovery and superSU already in the zip file or do we have to find and download it?

This is exactly what I did yesterday to my Koodo Moto G and it worked perfectly. I was sick of all the crashes I was getting under 4.3 and also needed root because I forgot how many ads there were in android (especially slacker radio which is an app I use often)

gwiqu said:
does the US Global GSM count as non AWS? is the custom recovery and superSU already in the zip file or do we have to find and download it?
Click to expand...
Click to collapse
US Global is non AWS.
You can find supersu here http://download.chainfire.eu/supersu and the recovery here http://forum.xda-developers.com/showthread.php?t=2563599 (will update the OP)

nupi said:
US Global is non AWS.
You can find supersu here http://download.chainfire.eu/supersu and the recovery here http://forum.xda-developers.com/showthread.php?t=2563599 (will update the OP)
Click to expand...
Click to collapse
i get i get
target max-sparse-size: 256MB
error: cannot load 'recovery.img': No error
what do i do? while trying to flash the recovery
edit: nvm, using cmd type out the command does not work, but using the .bat and putting the command in works, WTS siaaaaaa
btw can busybox work if i install it?

Yes once you have root busybox will work.

Excuse my potentially dumb question but i want to flash this on my german Moto G to get KitKat and i am not sure what mfastboot is compared to normal fastboot. Can i just use the fastboot command instead or is mfastboot part of the usual ADB?

bunnahabhain said:
Excuse my potentially dumb question but i want to flash this on my german Moto G to get KitKat and i am not sure what mfastboot is compared to normal fastboot. Can i just use the fastboot command instead or is mfastboot part of the usual ADB?
Click to expand...
Click to collapse
It is a different (customized for moto) fastboot. Let me dig it out
If someone feels really adventurous, I have put a ZIP of a CWM backup of the rooted system onto http://www.mediafire.com/download/1... 4.4.2 US Retail for XT1032 International.zip I presume it should upgrade any international Moto G to a rooted 4.4.2 but proceed with caution (you will need to unpack it into CWM backup folder, install ZIP from sdcard does not work with this).

Okay i copied that in /platform-tools, renamed it to mfastboot and i'll try to flash the files manually tonight!
Thanks for the digging!

bunnahabhain said:
Excuse my potentially dumb question but i want to flash this on my german Moto G to get KitKat and i am not sure what mfastboot is compared to normal fastboot. Can i just use the fastboot command instead or is mfastboot part of the usual ADB?
Click to expand...
Click to collapse
No absolutely not. I did this same thing and ended up in a bootloop (a pretty one but useless all the same). Use the mfastboot executable and do it line by line and it will work fine

Suggestion for OP:
It was already said many times before elsewhere but before somebody asks again -it might be useful to stress in OP that two side-effects will occur - loss of carrier name in stat bar (which is basically good thing) and loss of H+ icon too BUT NOT loss of UMTS connectivity. Data speeds are exactly the same as they were in your location with 4.3.

I have upgraded 4.3 GB to 4.4.2 using this guide - everything works!
Has not tried root yet.

drfr said:
Suggestion for OP:
It was already said many times before elsewhere but before somebody asks again -it might be useful to stress in OP that two side-effects will occur - loss of carrier name in stat bar (which is basically good thing) and loss of H+ icon too BUT NOT loss of UMTS connectivity. Data speeds are exactly the same as they were in your location with 4.3.
Click to expand...
Click to collapse
yea the lost of carrier is really good lol but the loss of the icon that say which kind of connection H+/Edge you can get even if you are not connected is a bit sad it was a good thing

alokhan said:
yea the lost of carrier is really good lol but the loss of the icon that say which kind of connection H+/Edge you can get even if you are not connected is a bit sad it was a good thing
Click to expand...
Click to collapse
you only loose the H logo, edge should still be displayed when 3g is not available
Sent from my phone

Hi, first of all, big thanks for this, you are doing an amazing job! I want to try 4.2.2 but im not sure about how i need to flash 4.4.2 US International image...
I've already downloaded 4.2.2 image and mfastboot.zip but i'm not sure what i have to do with this files...
Could someone post a more descriptive tutorial? like step by step? I have unlocked bootloader...
Sorry for my english, it's not my native language x)
Thanks!

Thanks for this worked perfect now on 4.2.2 on UK moto g
Sent from my XT1032 using XDA Premium 4 mobile app

ponxho said:
Hi, first of all, big thanks for this, you are doing an amazing job! I want to try 4.2.2 but im not sure about how i need to flash 4.4.2 US International image...
I've already downloaded 4.2.2 image and mfastboot.zip but i'm not sure what i have to do with this files...
Could someone post a more descriptive tutorial? like step by step? I have unlocked bootloader...
Sorry for my english, it's not my native language x)
Thanks!
Click to expand...
Click to collapse
Unzip all the individual files from the rom into the same folder as mfastboot and you should be good to go. Hold volume down when you power on to get the phone ready and then paste the commands into the dos window from the guide.
Sent from my XT1032 using Tapatalk

SickBeast said:
Unzip all the individual files from the rom into the same folder as mfastboot and you should be good to go. Hold volume down when you power on to get the phone ready and then paste the commands into the dos window from the guide.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
I did what you say, almost everything went ok but this... Is this normal ?
C:\Users\Dell\Downloads\mfastboot-windows-linux-osx>fastboot-moto-windows.exe fl
ash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (260606 KB)...
OKAY [ 10.566s]
writing 'system'...
(bootloader) Invalid signed image
OKAY [ 14.020s]
finished. total time: 24.589s
C:\Users\Dell\Downloads\mfastboot-windows-linux-osx>fastboot-moto-windows.exe fl
ash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (239692 KB)...
OKAY [ 9.069s]
writing 'system'...
OKAY [ 14.592s]
finished. total time: 23.665s
C:\Users\Dell\Downloads\mfastboot-windows-linux-osx>fastboot-moto-windows.exe fl
ash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (222205 KB)...
OKAY [ 8.033s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 23.909s]
finished. total time: 31.947s
Thanks!

(bootloader) Preflash validation failed

Hi I've Installed Chainfire(dumbest idea ever) -I had GLTools with only default plugin- ,too check whenever It would be possible to run Portal-So memory is almost full ,so I couldn't do neither full CWM backup ,and Advanced Backup didn't worked for me.
So What I did was flash 4.4.2(and I was on 4.4.4 europe rom -XT1032)
I have Fastboot Reason: UTAG *flashfail* configured as fastboot(no not after installing chainfire)
I was flashing with my premade /.sh file (fastboot flash partition gpt.bin etc.) and it seems like what have been flasheed is:
wirting 'partition'...
(bootloader) Preflash validation failed
FAILED(remote failure)
wirting 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
witing 'boot'...
OKAY
'system' -sparechunk.0
FAILED (data transfer failure (No such file or directory)) - lol? ,I've actually modified VM to have 512 mb of ram instead of 1536mb and cores from 2 to 1.
*fastboot resets*
Fastboot Reason: UTAG *flashfail* configured as fastboot
'system'-sparechunk.1
OKAY
and the rest wasn't flashed ,What can I do ,...I've just clicked factory(up button-congrats idiot-I wanted to go into recovery to say that I can go there and do something from there *facepalm* and clicked Up button ,because I was on factory option).
Okay ,so know I have no UTAG error recovery still works ,phone gets stuck on unlocked bootloader disclamer.
Btw before I started to install chainfire I've followed some instructions:
Code:
Backup
[B] * boot into recovery
* adb backup -f boot.img boot
* adb backup -f system.img system[/B]
Restore
[B] * boot into recovery[/B]
* adb shell echo -n boot > /tmp/ro.bu.restore
* adb restore boot.img
[I][B] * adb shell echo -n system > /tmp/ro.bu.restore
* adb restore system.img[/B][/I]
I've followed ,Failed
As boot.img from 4.4.2 have flashed can I actually flash that( * adb backup -f boot.img boot) boot.img and I don't magic will help me. Or can Actually someone who Have XT1032 falcon_umts do like CWM Backup without any personal stuff and I would try to flash it(Preloader/boot is not corrupted- device unlocked etc.-) ,when I used Used factory then everything seems to be working(expect for the android of course... and I don't know whenever VM will work If I don't have everything flashed).
Btw I can't Flash System.img from before I've destroyed it with Chainfire ,because the size is more than 600/700 mb and it just out numbers max number for sending system partition to fastboot.

Not saying this will definitely work, but if you get the gpt.bin and emmc_appsboot.mbn files from the 4.4.4 OTA zip (probably floating around here) and overwrite the originals from 4.4.2 in your factory image (delete the old ones or rename them to something else), then do the following:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Then flash as normal according to the guide that's floating around here, but leave out the gpt.bin and emmc_appsboot.mbn (you already flashed these) and the motoboot.img or it will brick it!

I just installed Paranoid Android ontop of it(adb sideload-I couldn't get into CWM ,and by accidently clicking factory in fastboot I could then go to CWM) and it works-then I launch PA install minimal gapps then factory reset it in cwm delete all data and slowly update pa update by update(installing 4.4RC2 into 4.45 is an bad idea for overall performance and stability) -I just kinda paniced.And I think ,because I was using generic fastboot instead of provided in guide ,preloadder didn't get corrupted(when to look at It only boot have been flashed correctly , and PA have boot.img in package).
So far so good.

This error has been associated with locked bootloader.

I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.

Shuttwind215 said:
I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.
Click to expand...
Click to collapse
My moto's bootloader is unlocked too, but it still gives the error...
Found an article:
https://giorgiosadventures.wordpres...rom-gpe-4-4-4-to-stock-and-recover-softbrick/
Try this... Lets see if it helps...
BTW, I got this error after converting xt1033 to gpe, then OTA'ing it to 5.0.1, then downgrading to 4.4.2.

@layman806 My moto g allready work look at post #3 this is what I did it[it looks extremly confusing]. It mightn't work for you through
,but if yours moto g have unlocked bootloader then you can do a lot ,and your situation isn't that bad.

lost101 said:
This error has been associated with locked bootloader.
Click to expand...
Click to collapse
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?

khiladi_786 said:
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?
Click to expand...
Click to collapse
I have the exact same problem on my xt1031 motog. I cant get any roms to boot and I cant figure out what version of gpt.bin i need to use. I get the same error.
Driving me crazy.

not solved
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....

heisenberg1546 said:
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....
Click to expand...
Click to collapse
This subforum is not for your phone. https://forum.xda-developers.com/2015-moto-g is the place for you.
If you are getting a 'pre-flash validation' error - even with the latest available firmware image - then you have to either wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.

help me plseeeeeeeeeeeeee i m getting preflash validation failed error on gpt.bin and sparsechunk plseee help me anyone i m using moto g3 xt1550 and trying to flash marshmallow.

No sim status after erasing modemst

Hi,
I was running CM12(5.0.2) on my xt1032 US GSM. I read in some thread for moto G 2014 that erasing modemst1 and modemst2 from bootloader fixed the no GPS fix. so i tried it in my moto g 2013 and after rebooting there is no network status. when i insert other sims, it shows no sim card. How can i fix this?
Thanks in advance

Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Report back how it goes.

lost101 said:
Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Report back how it goes.
Click to expand...
Click to collapse
Sir, I flashed CM 12 on top of 4.4.4 stock. I never updated my bootloader. Would it be okay to flash XT1032 Retail US 5.0.2 Lollipop Firmware's NON-HLOS.bin?

gearguy365 said:
Sir, I flashed CM 12 on top of 4.4.4 stock. I never updated my bootloader. Would it be okay to flash XT1032 Retail US 5.0.2 Lollipop Firmware's NON-HLOS.bin?
Click to expand...
Click to collapse
You can use the XT1032 Retail US 4.4.4 Firmware files instead to be safe.

I did that but it didnt solve the problem

Just FTR, erasing modemst1/2 can lead to problems: https://github.com/CyanogenMod/android_device_motorola_victara/issues/1#issuecomment-96288956
The method mentioned in the link above worked for me in this situation:
- newly bought xt1039
- ota updated to 5.1
- no gps activation in stock rom ever
- unlocked bootloader, flashed twrp
- backup of stock rom
- flashed cm12.1
- no gps lock
- restored stock rom from backup
- activated gps and got a lock
- re-flashed cm12.1
- gps works

gearguy365 said:
I did that but it didnt solve the problem
Click to expand...
Click to collapse
@gearguy365 - are you using mfastboot? Please provide a fastboot log if you still have problems.
mfastboot: https://www.androidfilehost.com/?fid=23578570567719065

lost101 said:
@gearguy365 - are you using mfastboot? Please provide a fastboot log if you still have problems.
mfastboot: https://www.androidfilehost.com/?fid=23578570567719065
Click to expand...
Click to collapse
I have the complete android SDK, so i am using the ADB provided in its platform tools. So only fastboot commands should work right?

gearguy365 said:
I have the complete android SDK, so i am using the ADB provided in its platform tools. So only fastboot commands should work right?
Click to expand...
Click to collapse
adb and fastboot are not the same thing. Put phone into fastboot mode and use mfastboot and the commands I stated.

lost101 said:
adb and fastboot are not the same thing. Put phone into fastboot mode and use mfastboot and the commands I stated.
Click to expand...
Click to collapse
I downloaded mfastboot and repeated the process, I have attached the cmd log and image of the phone's screen while in fastboot mode:
Code:
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.900s]
writing 'modem'...
OKAY [ 2.258s]
finished. total time: 4.166s
C:\mfastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.167s]
finished. total time: 0.170s
C:\mfastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.027s]
finished. total time: 0.031s
C:\mfastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (707 KB)...
OKAY [ 0.073s]
writing 'fsg'...
OKAY [ 6.819s]
finished. total time: 6.897s
C:\mfastboot>mfastboot reboot
rebooting...
finished. total time: 0.005s
The result is same. Still no network. My phone is even detecting the network name i'm in, but the signal bar is absolutely empty. Pressing and holding the power button gives the impression that its on ariplane mode, but turning the airplane mode off from there makes no effect. Please check the attached images. I'm really puzzled at this moment.....

gearguy365 said:
The result is same. Still no network.
Click to expand...
Click to collapse
Did you have Network connectivity in CM12.1 prior to flashing the GPS fix? Link me to the zip if possible.
I thought recent versions of CM12 required the Lollipop Bootloader to even boot?

lost101 said:
Did you have Network connectivity in CM12.1 prior to flashing the GPS fix? Link me to the zip if possible.
I thought recent versions of CM12 required the Lollipop Bootloader to even boot?
Click to expand...
Click to collapse
Yes, prior to attempting to solve that GPS problem i had full network/data connectivity on both GSM and HSPA on my operator. Only after trying to do modemst 1 & 2 clearing i am facing this problem. And yes, my CM 12 version is quite old. 20150322-NIGHTLY to be specific.
I didnt update to the later nightlys which required the up to date bootloader.

gearguy365 said:
Yes, prior to attempting to solve that GPS problem i had full network/data connectivity on both GSM and HSPA on my operator. Only after trying to do modemst 1 & 2 clearing i am facing this problem. And yes, my CM 12 version is quite old. 20150322-NIGHTLY to be specific.
I didnt update to the later nightlys which required the up to date bootloader.
Click to expand...
Click to collapse
Can you try doing a clean install of the ROM? Alternatively flash via mfastboot the entire Stock 4.4.4 Firmware files, excluding: motoboot.img and recovery.img - you could then wipe and flash CM12 if all was working.

lost101 said:
Can you try doing a clean install of the ROM? Alternatively flash via mfastboot the entire Stock 4.4.4 Firmware files, excluding: motoboot.img and recovery.img - you could then wipe and flash CM12 if all was working.
Click to expand...
Click to collapse
Okay, i will try to flash the 4.4.4 image i have, but i have never updated bootloader. Should i still avoid motoboot and recovery?

gearguy365 said:
Okay, i will try to flash the 4.4.4 image i have, but i have never updated bootloader. Should i still avoid motoboot and recovery?
Click to expand...
Click to collapse
It's dangerous to repeatedly flash the Bootloader (motoboot.img) - even if it is the KitKat one. And skipping recovery will mean you remain with current custom recovery.

lost101 said:
It's dangerous to repeatedly flash the Bootloader (motoboot.img) - even if it is the KitKat one. And skipping recovery will mean you remain with current custom recovery.
Click to expand...
Click to collapse
makes sense! i will try to revert back to 4.4.4 and keep things posted...

Flashing stock 4.4.4 brought back the network!
but when i was flashing the stock firmware, first i avoided flashing motoboot.img. That resulted in failing to erase userdata later on and ultimately resulting in "utag flash fail" and stuck in bootloader. Eventually flashing everything resulted in restoring stock firmware and now i have network again!

gearguy365 said:
Flashing stock 4.4.4 brought back the network!
but when i was flashing the stock firmware, first i avoided flashing motoboot.img. That resulted in failing to erase userdata later on and ultimately resulting in "utag flash fail" and stuck in bootloader. Eventually flashing everything resulted in restoring stock firmware and now i have network again!
Click to expand...
Click to collapse
I should have stated to do the commands manually, one at a time - rather than using the included script.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Report back how it goes.
Click to expand...
Click to collapse
Just saved my a**! Had a dead baseband. I somehow wrecked my modem on my XT1039. I downloaded a stock rom and used your commands and it worked like a charm! THANK YOU VERY MUCH!

Hello. I have the same issue... No sim/ network. I used mfastboot commands and fully restored to an unrooted stock XT1032 lollipop ROM. The confusing thing is that I still have no network. Does anyone have any suggestions?
Edit:
I used the downgrade to 4.4 thread... Ran the bat file and I'm back in business. The quick YouTube video walks you through the steps.
http://forum.xda-developers.com/showthread.php?t=2969729
Sent from my iPad using Tapatalk

moto g preflash validation failed-help me

i have done many moto g using file below
ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF.xml
but now this file error as below
C:\MOTO G>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.359s
phone screen flash logo error is """version downgraded for primary gpt"""
customer said he tried to upgrade-after it hang in logo
help me

Bootloader unlocking may resolve this. Try to not flash motoboot.img (Bootloader) - as it is dangerous and not even necessary.

lost101 said:
Bootloader unlocking may resolve this. Try to not flash motoboot.img (Bootloader) - as it is dangerous and not even necessary.
Click to expand...
Click to collapse
my phone bootloader shows unlocked in fastboot mode

you can not flash motoboot and a partition table from an older firmware if you already have a newer one i think (downgrade)

alwayspunk said:
you can not flash motoboot and a partition table from an older firmware if you already have a newer one i think (downgrade)
Click to expand...
Click to collapse
i think now 5.1 the lateset version.
from where i get official firmware?

zonetrichur said:
i think now 5.1 the lateset version.
from where i get official firmware?
Click to expand...
Click to collapse
i can not post spam, anyways check the ultimate guide to flash gpe in general section. theres a link to the firmware there

i tried many many recovery files also
that also error
so i think it emmc problem-am i right?

zonetrichur said:
i tried many many recovery files also
that also error
so i think it emmc problem-am i right?
Click to expand...
Click to collapse
May i know whether u flashed stock firmware, because i also getting same error and phone struck in "Bootloader unlocked warning screen" in startup...

XT1031 restore Boost baseband stuff

I got an xt1031 on ebay that was flashed to work on Page Plus. I have restored the ROM to falcon_KXB21.14-L1.57.zip but the baseband still says "VZW_CUST" and I get activation stuff when I start it up. How can I get this working like a regular xt1031 again? I am rooted, unlocked and have CWM installed. I also have a regular, working xt1031 if I need anything off of it.
I can't find any information about restoring baseband or anything like that. After flashing the stock ROM I restored the phone.

HardOnChairs said:
I got an xt1031 on ebay that was flashed to work on Page Plus. I have restored the ROM to falcon_KXB21.14-L1.57.zip but the baseband still says "VZW_CUST" and I get activation stuff when I start it up. How can I get this working like a regular xt1031 again? I am rooted, unlocked and have CWM installed. I also have a regular, working xt1031 if I need anything off of it.
I can't find any information about restoring baseband or anything like that. After flashing the stock ROM I restored the phone.
Click to expand...
Click to collapse
Factory Firmware Images are available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
I would start by only flashing the 'system.img.sparsechunk' files:
mfastboot flash system system.img_sparsechunk1 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot erase userdata
mfastboot reboot​

lost101 said:
by only flashing
Click to expand...
Click to collapse
Would that be more effective? Because I would be just as happy to flash the entire ROM again and start over if it would work as well.
Edit: nevermind I see what's going on now with the zip

HardOnChairs said:
Would that be more effective? Because I would be just as happy to flash the entire ROM again and start over if it would work as well.
Edit: nevermind I see what's going on now with the zip
Click to expand...
Click to collapse
My recommendation is for your safety. Messing with fastboot has destroyed many phones.

Code:
C:\Users\User\Desktop\New folder>mfastboot devices
'mfastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\User\Desktop\New folder>mfastboot devices
TA96506RJD fastboot
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (262084 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 14.144s]
finished. total time: 22.361s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (256888 KB)...
OKAY [ 8.052s]
writing 'system'...
OKAY [ 12.088s]
finished. total time: 20.142s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (238359 KB)...
OKAY [ 7.485s]
writing 'system'...
OKAY [ 11.907s]
finished. total time: 19.393s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (26644 KB)...
OKAY [ 0.875s]
writing 'system'...
OKAY [ 8.438s]
finished. total time: 9.313s
C:\Users\User\Desktop\New folder>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.500s]
finished. total time: 0.500s
C:\Users\User\Desktop\New folder>mfasboot reboot
'mfasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\User\Desktop\New folder>mfastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\User\Desktop\New folder>
Everything seems to have gone well but I still get the activation screen and the baseband still has VZW_CUST.
Edit: Here are all of the files in the zip for my phone if that helps:
HTML:
boot.img
falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.bat
falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml
fsg.mbn
gpt.bin
logo.bin
mfastboot.exe
motoboot.img
NON-HLOS.bin
recovery.img
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4

Now flash the Radio Firmware only. Use the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​

The baseband says BOOST_CUST now but I am still getting these activation screens that I never get on my other boost phones.

HardOnChairs said:
The baseband says BOOST_CUST now but I am still getting these activation screens that I never get on my other boost phones.
Click to expand...
Click to collapse
From memory, I do recall Verizon software being present in the Boost Firmare Images. But you can delete certain apks to stop those activation screens appearing. If you install TWRP, you can use the file explorer to delete the folders. I will try to get the correct names soon, but you might be able to guess them - they are located in /system/priv-app

The weird this is that it is a boost/sprint app.
com.motorola.android.omadm.sprint.client
Click to expand...
Click to collapse
But I have a bunch of these phones and none of them do this. There are some activation apps, but they are never intrusive like this.
On one hand I'd like to get it to go away any way I can, but I would most prefer all of my devices to be set up the same. Is there anything I can do given that I have an identical model that is set up the right way? I don't know enough about how android partitions work to understand why flashing a stock ROM and resetting it wouldn't make it act exactly the same as my other devices that I have done the same with.

HardOnChairs said:
The weird this is that it is a boost/sprint app.
But I have a bunch of these phones and none of them do this. There are some activation apps, but they are never intrusive like this.
On one hand I'd like to get it to go away any way I can, but I would most prefer all of my devices to be set up the same. Is there anything I can do given that I have an identical model that is set up the right way? I don't know enough about how android partitions work to understand why flashing a stock ROM and resetting it wouldn't make it act exactly the same as my other devices that I have done the same with.
Click to expand...
Click to collapse
Those are the stock activation apps that are needed if you plan to use the phone. Typically, they "go away" or are "unseen" when the device is activated.
Sent from my XT1031

@HardOnChairs - Apologies, I got confused between Verizon and Sprint. There are no Verizon files in the Boost Firmware, only those for Sprint.
The conversion to PagePlus includes flashing the XT1028 Bootloader - so that's still the Bootloader you have. Flashing the XT1031 Boost Bootloader may be a necessary step, but if something goes wrong you have a brick on your hands.

ATTACK said:
Those are the stock activation apps that are needed if you plan to use the phone. Typically, they "go away" or are "unseen" when the device is activated.
Sent from my XT1031
Click to expand...
Click to collapse
I do still get activation alerts on my other ones but they are not intrusive and they can be disabled. All of the xt1031 phones I have are on wifi only. Does that mean that they are still "activated" from before? In that case is it possible to activate these two that I have without actually buying service for them?

lost101 said:
@HardOnChairs - Apologies, I got confused between Verizon and Sprint. There are no Verizon files in the Boost Firmware, only those for Sprint.
The conversion to PagePlus includes flashing the XT1028 Bootloader - so that's still the Bootloader you have. Flashing the XT1031 Boost Bootloader may be a necessary step, but if something goes wrong you have a brick on your hands.
Click to expand...
Click to collapse
I have managed to update the bootloader of one of my devices and it actually caused some issues. The display constantly glitches. This was when I was trying to update to bootloader to work on 5.x. Do you know where I can find the original bootloader for 4.x? I never managed to find it. Is it possible to pull it off of one of my other devices? Or do you know if that zip I got has the original one?

HardOnChairs said:
I have managed to update the bootloader of one of my devices and it actually caused some issues. The display constantly glitches. This was when I was trying to update to bootloader to work on 5.x. Do you know where I can find the original bootloader for 4.x? I never managed to find it. Is it possible to pull it off of one of my other devices? Or do you know if that zip I got has the original one?
Click to expand...
Click to collapse
Be very careful with Bootloaders. You cannot go back now that you have upgraded. The display 'glitch' is caused by running KitKat ROM with a Lollipop Bootloader. Turn screen off once to stop it.

lost101 said:
Be very careful with Bootloaders. You cannot go back now that you have upgraded. The display 'glitch' is caused by running KitKat ROM with a Lollipop Bootloader. Turn screen off once to stop it.
Click to expand...
Click to collapse
I see. Well that aside, thats a different phone altogether, is it possible for me to check which bootloader these new phones have? And if they are on the 1028, is it possible for me to go back to the 1031 KK version?

HardOnChairs said:
I see. Well that aside, thats a different phone altogether, is it possible for me to check which bootloader these new phones have? And if they are on the 1028, is it possible for me to go back to the 1031 KK version?
Click to expand...
Click to collapse
Check the Fastboot screen:
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way.
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open Command Prompt or Terminal, navigate to the Firmware / ADB folder (i.e CD C:\motog_firmware ) and type:
Code:
adb reboot-bootloader
I don't know if you can safely flash the XT1031 KitKat Bootloader now that the phone has been converted to XT1028 - but it's likely considering that's the original Model of the phone.

The fastboot screen says
41.13 (sha-7dc8e78, 2014-06-16 16:33:29)
Click to expand...
Click to collapse

HardOnChairs said:
The fastboot screen says
Click to expand...
Click to collapse
v41.13 is KitKat, v41.18 is Lollipop.

lost101 said:
v41.13 is KitKat, v41.18 is Lollipop.
Click to expand...
Click to collapse
So I should try reflashing motoboot.img? Is there a way to be sure that it is KK?

HardOnChairs said:
So I should try reflashing motoboot.img? Is there a way to be sure that it is KK?
Click to expand...
Click to collapse
To be sure what is KitKat? v41.13 is 100% not a Lollipop Bootloader.