Database Info

[Q] XT1032 GB Retail - lollipop gpe back to f2fs based stock kitkat?

I had a dabble with the GPE ext4 lollipop on my GB XT1032 but found I cannot re lock my bootloader so would like to go back to stock f2fs 4.4.4 kitkat.
Im currently downloading XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip and was planning to go back with fastboot with the following commands:
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_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
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
After reading up before attempting this i'm understanding that if you go back to 4.4.3 you will brick on the next ota.
If I was to flash the gpt and bootloader from 4.4.4 as above i'm guessing that if it succeeds then the next ota being lollipop should go ok?
If anyone has tried the above and then got the 5.x ota and it worked out fine would be helpful to hear how you got it to work.
Thanks!

Before anything else, try formatting 'Data' to f2fs in custom recovery and flashing this: http://forum.xda-developers.com/moto-g/development/rom-titan-rom-single-sim-t3004757

I'll install twrp and have a go at formatting f2fs.......
Is there a reason for flashing the rom in the link first?

hmmm? I was thinking if i was to flash the gpt.bin from a stock moto rom then this would setup the partitions as f2fs anyway before proceeding onto the next components to flash?

Yes, you are correct; flashing gpt.bin will do as you say. I was suggesting you avoid fastboot if possible - to minimize the risk of bricking.

lost101 said:
Yes, you are correct; flashing gpt.bin will do as you say. I was suggesting you avoid fastboot if possible - to minimize the risk of bricking.
Click to expand...
Click to collapse
I had a go at flashing and everything went ok and it boots up fine but the display is acting like it has a scan line scrolling down the screen!
When I flashed everything flashed ok apart from motoboot.img which gave me the following error:-
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.105s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.368s
I'm guessing this is for the kernel and i'm now left running the lollipop kernel with kitkat, yeah?
Is there anyway I can get motoboot.img to flash?

rockyrobin said:
I'm guessing this is for the kernel and i'm now left running the lollipop kernel with kitkat, yeah?
Is there anyway I can get motoboot.img to flash?
Click to expand...
Click to collapse
motoboot.img is the Bootloader. Don't try flashing it again.
boot.img is the Kernel. Does the scan-line go away if you turn screen off and on?

lost101 said:
motoboot.img is the Bootloader. Don't try flashing it again.
boot.img is the Kernel. Does the scan-line go away if you turn screen off and on?
Click to expand...
Click to collapse
I'll leave the bootloader alone then like you recommend. Would be just my luck to invoke the straw that broke the camels back!
I performed all my updates with the play store and found an update for 'Motorola boot services' which I applied. Don't know if this is related but when I rebooted everything is now OK with the scan line gone.
Im going to leave alone for now, and when the lollipop update turns up will look again at relocking my bootloader.
Thanks for your help!

rockyrobin said:
I'll leave the bootloader alone then like you recommend. Would be just my luck to invoke the straw that broke the camels back!
I performed all my updates with the play store and found an update for 'Motorola boot services' which I applied. Don't know if this is related but when I rebooted everything is now OK with the scan line gone.
Im going to leave alone for now, and when the lollipop update turns up will look again at relocking my bootloader.
Click to expand...
Click to collapse
Every time you apply an OTA Update there is a risk of brick. I would suggest you are ready, flash a ROM zip for Lollipop instead via Custom Recovery. They are available in beta form at the moment in /Development - and Final ROMs will be available in the near future.

Messed up my Moto G, really need some help please :(

Hey guys. I got a telus moto g xt1032. It was on official 5.0.2. I flashed TWPR 2.8.5.0, and encountered the bootloop bug. I proceeded to flash the only stock telus firmware i could find- 4.4.4. I followed the guide on XDA to the tee and resulted in my moto go being stuck at the "Warning, boot loader unlocked" screen. I have no idea what to do and would really appreciate some help, as I am new to this. Am even willing to donate if it results in me fixing my phone. Thank for taking the time to read

Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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​
Provide a log of what happens, if this does not work.

lost101 said:
Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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​
Provide a log of what happens, if this does not work.
Click to expand...
Click to collapse
I also have this problem. I am trying to downgrade to 4.4.4 stock firmware (from 5.02) and I'm getting an this error:
$ fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.042s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.336s
Click to expand...
Click to collapse
All the other commands are successful but the device remain stucked on the boot screen after the reboot :crying:

I have this problem too, trying to factory reset my phone but it's still stuck on the bootloader. CWM says can't mount sd card now aswell so any help would be appreciated

I got the stock Telus 4.4.4 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1

lost101 said:
Try doing the following Fastboot commands manually:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILENAME ON HARD DISK)
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​
Provide a log of what happens, if this does not work.
Click to expand...
Click to collapse
hey man, ok ill try that again. The only thing is, there is no boot.img in the telus file I downloaded. Its named "motoboot." Should i replace that with the boot img part? Also, i recently read somewhere trying to downgrde from 5.0.2 to 4.4.4 will mess my phone up. Is that true?
EDIT- I do remember the first time i tried this after sparsechunk.1, is sad "image file is too large" but kept on goiing anyways

audit13 said:
I got the stock Telus 4.4.4 firmware from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
theres 2 telus ones. How do you know which one to use? Also i tried flashing one of them im pretty sure and am stuck at the screen in OP

butthurtlocker said:
hey man, ok ill try that again. The only thing is, there is no boot.img in the telus file I downloaded. Its named "motoboot." Should i replace that with the boot img part? Also, i recently read somewhere trying to downgrde from 5.0.2 to 4.4.4 will mess my phone up. Is that true?
EDIT- I do remember the first time i tried this after sparsechunk.1, is sad "image file is too large" but kept on goiing anyways
Click to expand...
Click to collapse
motoboot.img and boot.img are not the same thing. Be careful renaming these files, or else you will destroy your phone. If there is no boot.img included then that zip has been messed with by someone.
The 'image file is too large' message should not be ignored - it means the firmware has not flashed at all. Nothing has changed on your phone; flash has not been successful.

butthurtlocker said:
theres 2 telus ones. How do you know which one to use? Also i tried flashing one of them im pretty sure and am stuck at the screen in OP
Click to expand...
Click to collapse
I used this one: XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml
Then I updated Motorola Apps via Play store, then get the OTA update to 5.02.

lost101 said:
motoboot.img and boot.img are not the same thing. Be careful renaming these files, or else you will destroy your phone. If there is no boot.img included then that zip has been messed with by someone.
The 'image file is too large' message should not be ignored - it means the firmware has not flashed at all. Nothing has changed on your phone; flash has not been successful.
Click to expand...
Click to collapse
good to know thanks. theres only 2 stock telus files, and one didnt have the boot.img. so ill have to hope the other does. I managed to get my phone booted on GpE 4.4. now im just trying to get back to stock motorola. Is there a guide you could link me to?

audit13 said:
I used this one: XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml
Then I updated Motorola Apps via Play store, then get the OTA update to 5.02.
Click to expand...
Click to collapse
did that file have a boot.img?

butthurtlocker said:
good to know thanks. theres only 2 stock telus files, and one didnt have the boot.img. so ill have to hope the other does. I managed to get my phone booted on GpE 4.4. now im just trying to get back to stock motorola. Is there a guide you could link me to?
Click to expand...
Click to collapse
Fastboot Tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219​

Yes, the boot.img file is included.

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

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.

Stuck at Motorola Bootlogo after Security update

Device: XT1031 converted to XT1028 for use on Page Plus. Bootloader unlocked. Rooted with SuperSU 2.46 Running Stock Verizon 5.1 ROM 221.26.7.falcon_cdma.Verizon.en.US
Recovery: TWRP 2.8.7.0
I accepted the new security update - http://forum.xda-developers.com/moto-g/general/moto-g-1st-gen-actually-security-update-t3362323
and when it tried to install the update, the phone just rebooted into TWRP Recovery.
So I flashed stock recovery from the Verizon 5.1 ROM and then tried the update again. This time it completed the update and rebooted but is now stuck at the Motorola bootlogo.
I'm able to reboot into fastboot.
I tried flashing system.img_sparsechunk.0, .1, .2, and .3, and rebooted but there is no change.
What can I try to get past this?
Before starting this I made a backup using TWRP Recovery, can I reinstall TWRP and restore that backup?

it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata​

lost101 said:
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata​
Click to expand...
Click to collapse
The TWRP backup was saved to an external OTG USB drive, so that's safe.
I was originally going to do the same as I did for the last update - http://forum.xda-developers.com/showpost.php?p=63976723&postcount=109 but tried it first and when it went straight to recovery, I figured I needed to flash stock recovery. I also figured I needed to flash system also, but it through me off when the sparsechunks were numbered 0 - 3 instead of 1 - 4.
I didn't see any errors when I did the flashes.
Right now my battery is drained all the way to 0%. Hopefully it charges back up.
I appreciate the response. Thanks.

Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.

lost101 said:
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
Click to expand...
Click to collapse
I'm using this stock ROM: XT1028_FALCON_VERIZON_5.1_LPB23.13-33.7_cid2_CFC.xml.zip
The sparsechunk files in that zip are named:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
and I need to rename them:
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4
Correct?
Then I would run the following commands one at a time and checking for an OK on each, correct?
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 system system.img_sparsechunk4
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
After that I can check that I can boot into the OS and then I can flash TWRP and restore my saved backup.
Does that sound right?
Thanks.

Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
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​
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493

lost101 said:
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
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​
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
OK, I got an error on the first one I tried:
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot devices
TA965000I5 fastboot
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.318s
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>
And on the Moto G's screen:
cmd: getvar:max-sparse-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt
Is that a problem?

Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2​

lost101 said:
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2​
Click to expand...
Click to collapse
OK, that worked. I was able to flash back to the stock ROM.
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Thanks for your help.

bw 1 said:
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Click to expand...
Click to collapse
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.

lost101 said:
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
Click to expand...
Click to collapse
I decided to start over and not try to recover from the saved file. I don't think there was anything on there that I really needed anyway. All my pictures and stuff was synced to Google.
I'm guessing that I ran into a problem by not flashing the 4 system sparsechunks from the stock ROM to remove root and I wasn't able to flash the same 5.1 that I had on there since it was updated. Flashing the latest newer build Verizon ROM worked because it was the same as what was contained in the update.
I didn't receive another OTA update and system update shows my phone as up to date with:
Android version: 5.1
Android security patch level: 2016-03-01
System version: 221.201.2.falcon_cdma.Verizon.en.US
Build number: LPBS23.13-33.7-2
I'm back to having a working phone. Thanks for your help. Hopefully this will help others too.