Database Users

[GUIDE] Restore softbricked phone after Lollipop update

FIRST OF ALL
(Also for downgrading to KitKat without softbricked phone!)
Okay, I decided to do the OTA to lollipop, everything went fine. So after some use I decided to play with the /system partition. I formatted it without making a working backup so my phone was kinda softbricked. REMEMBER THIS THREAD IS NOT FOR HARDBRICKED BOOTLOADERS, you guys have to wait.
SO WHAT TO DO?
1. Plug your phone into fastboot in your pc.
2. Flash a custom recovery, like CWM, I know you'll have a screen rimble effect due the new bootloader (doesn't matter)
3. Open recovery and keep it plugged into PC, recovery will have adb on by default so leave recovery as it is.
4. Open CMD and type:
Code:
cd directory-with-adb.exe-and-fastboot.exe-etc.
(I assume that you guys know how to use adb and fastboot with CMD)
5. Type:
Code:
adb devices
6. Your Moto's serial number should show up in the attached devices list (serialnumber, recovery), if not download the driver installer from http://adbdriver.com
7. Now download a firmware flashable zip to the directory in your CMD (CyanogenMod or stock firmwares from here)
8. Now you have to make sure you are able to mount the /sdcard in recovery: To make sure do a /data and media wipe. (Also helps on GPe ROM and the encryption problem!)
9. Now you can push the downloaded zip to the phone's sdcard using:
Code:
adb push yourrom.zip /sdcard/yourrom.zip
It will take some time.
10. Now you can install but you may face a not working SIM or WiFi, you need to download a .xml.zip firmware corresponding to your just flashed version. Navigate to your firmware folder using CMD. Then type:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
11. Now your phone should work. You will have that annoying screen rimble. Sometimes it's gone, just turn screen off for a few minutes. It will be fixed when you install the stock recovery and then flash an lollipop OTA zip just like before! (OTA's will still show up and works with updating )
WARNING!
SOME GUYS MADE A HUGE MISTAKE AND BRICKED THEIR BOOTLOADER. THEY FLASHED LOLLIPOP OTA, THEN DOWNGRADED TO 4.4.2 AND THEY TRIED TO UPDATE TO 4.4.4 BY OTA!
THAT RUINED THE BOOTLOADER SEE BELOW!
FOR HARDBRICKED DEVICES
You ruined your bootloader, we need a mbm-ci (blankflasher tool) with the 5.0 bootloader. We have to wait till Motorola releases it. So no support yet.
Sorry guys, that was the risk!
HOPE YOU GUYS LIKE THIS TUTORIAL!

Thanks for the guide.

restore
GI0\/\NNI said:
FIRST OF ALL
Okay, I decided to do the OTA to lollipop, everything went fine. So after some use I decided to play with the /system partition. I formatted it without making a working backup so my phone was kinda softbricked. REMEMBER THIS THREAD IS NOT FOR HARDBRICKED BOOTLOADERS, you guys have to wait.
SO WHAT TO DO?
1. Plug your phone into fastboot in your pc.
2. Flash a custom recovery, like CWM, I know you'll have a screen rimble effect due the new bootloader (doesn't matter)
3. Open recovery and keep it plugged into PC, recovery will have adb on by default so leave recovery as it is.
4. Open CMD and type:
Code:
cd directory-with-adb.exe-and-fastboot.exe-etc.
(I assume that you guys know how to use adb and fastboot with CMD)
5. Type:
Code:
adb devices
6. Your Moto's serial number should show up in the attached devices list (serialnumber, recovery), if not download the driver installer from http://adbdriver.com
7. Now download a firmware flashable zip to the directory in your CMD (CyanogenMod or stock firmwares from here)
8. Now you have to make sure you are able to mount the /sdcard in recovery: To make sure do a /data and media wipe. (Also helps on GPe ROM and the encryption problem!)
9. Now you can push the downloaded zip to the phone's sdcard using:
Code:
adb push yourrom.zip /sdcard/yourrom.zip
It will take some time.
10. Now you can install but you may face a not working SIM or WiFi, you need to download a .xml.zip firmware corresponding to your just flashed version. Navigate to your firmware folder using CMD. Then type:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
11. Now your phone should work. You will have that annoying screen rimble. Sometimes it's gone but not sure. It will be fixed when you install the stock recovery and then flash an lollipop OTA zip just like before! (OTA's will still show up and works with updating )
FOR HARDBRICKED DEVICES
You ruined your bootloader, we need a mbm-ci (blankflasher tool) with the 5.0 bootloader. We have to wait till Motorola releases it. So no support yet.
Sorry guys, that was the risk!
HOPE YOU GUYS LIKE THIS TUTORIAL!
Click to expand...
Click to collapse
thanks for this guide
but my phone is not bricked ,can i downgrade 5.0 to 4.4.4
because my moto g is asian retail, i already installed brasil firmware and ota file

mostwantedxda said:
thanks for this guide
but my phone is not bricked ,can i downgrade 5.0 to 4.4.4
because my moto g is asian retail, i already installed brasil firmware and ota file
Click to expand...
Click to collapse
Yeah just follow guide!

Hi I have updated my Asian XT 1033 to brazil 5.0 but experienced NO NETWORK on both the sim cards... and now i downgraded to my asian 4.4.4 but still NO NETWORK on both sim cards... Please help .... m worried ;(

Imei vanished
My imei numbers are vanished.... Please help me... is there any thing i can do now??

hunterhere said:
Hi I have updated my Asian XT 1033 to brazil 5.0 but experienced NO NETWORK on both the sim cards... and now i downgraded to my asian 4.4.4 but still NO NETWORK on both sim cards... Please help .... m worried ;(
Click to expand...
Click to collapse
Flash 4.4.4
NON-HLOS.bin
fsg.mbn
Read the guide!

hunterhere said:
My imei numbers are vanished.... Please help me... is there any thing i can do now??
Click to expand...
Click to collapse
@hunterhere,
I think I found a solution!
1. Download and extract zip
2. Connect phone in fastboot mode to your PC
3. Run IMEI_fix_gio.bat
4. Should work now!

first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?

poran123 said:
first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?
Click to expand...
Click to collapse
after downgrading from 5.0 i was able to flash any rom STOCK 4.4.4 of any region and 5.0 too again... so according to this u shld be able to flash....

poran123 said:
first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?
Click to expand...
Click to collapse
You can flash without problems. Promise!

hunterhere said:
after downgrading from 5.0 i was able to flash any rom STOCK 4.4.4 of any region and 5.0 too again... so according to this u shld be able to flash....
Click to expand...
Click to collapse
did you try any CM roms?
---------- Post added at 01:16 PM ---------- Previous post was at 01:15 PM ----------
GI0\/\NNI said:
You can flash without problems. Promise!
Click to expand...
Click to collapse
thanks for confirming ..:good:

Adb drivers not recoganizing.
when i plug in the phone some drivers get installed.
but my phone is not showing up in adb devices.
i flashed CMW & am running Windows 10 x64

Help!!!!!
I have XT1033 and i was on brazilian 5.0 soak test, after that i convert my phone to downgrade to gpe 4.4.4 and everything was fine but then i wanted to go back to stock 4.4.4 brazilian and now im stuck at the boot logo.
these are the commands i used to convert from 5.0 brazilian soak test to gpe 4.4.4
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
and these are the commands i used to convert from gpe 4.4.4 to stock brazilian 4.4.4
SET fastboot=fastboot.exe
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe reboot-bootloader
fastboot.exe continue
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
fastboot.exe reboot
exit
did i softbricked my phone or hardbricked ?

brick my moto g
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:

Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
i'm with you, brother....i have same problem...waiting for solution

Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
Did you read first page before flash? It s clearly stated there that some ppl bricked phones when flashed 4.4.2 then upto 4.4.3 and so on. Please next time read all that its writed...

ganeshkmr21 said:
when i plug in the phone some drivers get installed.
but my phone is not showing up in adb devices.
i flashed CMW & am running Windows 10 x64
Click to expand...
Click to collapse
Read OP, install adbdriver!
não-soi-jo said:
I have XT1033 and i was on brazilian 5.0 soak test, after that i convert my phone to downgrade to gpe 4.4.4 and everything was fine but then i wanted to go back to stock 4.4.4 brazilian and now im stuck at the boot logo.
these are the commands i used to convert from 5.0 brazilian soak test to gpe 4.4.4
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
and these are the commands i used to convert from gpe 4.4.4 to stock brazilian 4.4.4
SET fastboot=fastboot.exe
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe reboot-bootloader
fastboot.exe continue
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
fastboot.exe reboot
exit
did i softbricked my phone or hardbricked ?
Click to expand...
Click to collapse
Just follow the guide! Flashing with fastboot won't work so flash custom recovery and push a 4.4.4 stock zip.
Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
READ OP! You didn't read it properly so you made a huge mistake!
MadL1fe said:
i'm with you, brother....i have same problem...waiting for solution
Click to expand...
Click to collapse
Same... You should have read the OP!
samsontm said:
Did you read first page before flash? It s clearly stated there that some ppl bricked phones when flashed 4.4.2 then upto 4.4.3 and so on. Please next time read all that its writed...
Click to expand...
Click to collapse
Totally agree with you....

I did that last part... :\ Guess I'll wait for Moto.

GI0\/\NNI said:
@hunterhere,
I think I found a solution!
1. Download and extract zip
2. Connect phone in fastboot mode to your PC
3. Run IMEI_fix_gio.bat
4. Should work now!
Click to expand...
Click to collapse
Hey I flashed this file now the change is that previously my both the IMEI(S) were showing 0 now 1st one is showing 0 but 2nd one has changed to null.
Secondly i request you to please come and join the below mentioned thread and please please help us all who have erased IMEI(S) with your knowledge and skills.
http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970
Edit: can you help in telling me how you modified this fsg_gio.img file? Or if you have got it from somewhere else please point...
As it is a very important file and a developer on above mentioned thread needs to know how this file got modified this will lead us further in restoring the imei numbers... as because moto g is made in a very different way... there is a lot of encryption done in its partitions which is very difficult to decrypt.

[updated] THE ULTIMATE GUIDE TO FLASH GPE LOLLIPOP 5.1 on XT1032/33/34 WITH ROOT

Okay, so there has been a lot of confusion an ambiguity on how to successfully install the GPE lollipop update on the Moto G. The reason I am starting this guide is because I faced a lot of trouble myself trying to get this update and get stuff working.
DIFFICULTY LEVEL: EASY (NOOB FREINDLY )
WARNING:
I HAVE TESTED THIS FULL PROCEDURE MYSELF. BUT I SHALL NOT BE HELD RESPONSIBLE FOR ANY PROBLEMS THAT MIGHT OCCUR BY USING THIS PROCEDURE, THOUGH I SHALL TRY MY BEST TO SOLVE THEM IF YOU FACE ANY. DUAL SIM USERS, ONLY SINGLE SIM WORKS BECAUSE IT IS A GPE FIRMWARE AND THERE IS NO WORKAROUND FOR IT. THIS PROCEDURE DOES NOT WORK WITH XT1031 (confirmed by @goldeneagle1972 )
THIS PROCEDURE WILL WIPE ALL YOUR DATA ON THE PHONE. SO TAKE A BACKUP.
EXISTING GPE 5.0.1/2 USERS, FLASH THE ORIGINAL GPE MODEMS FIRST AND MAKE SURE YOUR SYSTEM ISN'T MODIFIED. (eg: rooted ). THEN DIRECTLY GO TO STEP 5.
THE REST OF YOU, FLASH THE 5.1 GPE FIRMWARE [HERE] FOLLOWING INSTRUCTIONS IN STEP 2.2 AND THEN GO DIRECTLY TO STEP 6
PREREQUISITES:
You will need an unlocked boot loader. If you have not already unlocked it, refer to [this]
STEP 1:
Download the 4.4.4 GPE XT1032 FIRMWARE from [here] [mirror]
Download mfastbootv2 from [here]
Download the minimal sdk from [here]
Download and install adb drivers from [here]
Download the batch files for all the commands from [here]. (OBSOLETE)
Download the batch files for flashing 5.1 firmware and fixing network from [here]
Download Motorola drivers from [here]
Reboot system after installing drivers.
Download THE 5.1 GPE FIRMWARE [HERE] FOLLOWING INSTRUCTIONS IN STEP 2.2 AND THEN GO DIRECTLY TO STEP 6
Extract the GPE firmware archive, batchfiles archive and mFastbootv2 archive to the Minimal ADB and Fastboot folder (or your folder containing the platform-tools)
Download OTA update from [here]. Rename it to "ota".
Copy this archive to the same folder mention above (do not extract this archive).
STEP 2:
Boot into fastboot (POWER+VOLUME DOWN) and connect phone to PC
If you are starting from scratch, skip 2.1 ) and go to 2.2 )
2.1 ) If you have already made a failed attempt to OTA, or have previously flashed the Brazilian OTA, then flash the GPE 4.4.4 firmware follow this step. SHIFT + RIGHT click in the folder where you have extracted everything and choose open command window here. Then double-click on "Step 2_1.bat" or type the following commands one by one.
Code:
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
You will not get network now but do not flash the modems of the firmware you use now because you will get a status 7 error when flashing the OTA. You will now be dumped at the welcome screen. Do not enter any details, just power off and boot into recovery via fastboot. Skip step 2.2)
YOU WILL GET SOME ERRORS LIKE HAB CHECK FAILED. JUST IGNORE AND PROCEED.
2.2 ) For those who haven't attempted the OTA or are not on the Brazilian Firmware, use the following method to flash the 4.4.4 GPE firmware. SHIFT + RIGHT click in the folder where you have extracted everything and choose open command window here. Then double-click on "Step 2_2.bat" or type the following commands one by one. (Thank you @jmonster141 for pointing out my silly error).
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
You will not get network now but do not flash the modems of the firmware you use now because you will get a status 7 error when flashing the OTA. You will now be dumped at the welcome screen. Do not enter any details, just power off and boot into recovery via fastboot.
IT SEEMS THAT SOME 4.4.4 FIRMWARE HAVE NEWER PARTITION TABLES THAN GPE 4.4.4, SO THE GPT.BIN WILL FAIL TO FLASH. JUST SKIP IT AND YOU'L BE FINE (confirmed by @SickBeast ) or TAKE A LOOK AT [THIS] (thank you @t4n017 ).
AFTER ERASING USERDATA AND REBOOTING, YOUR PHONE MIGHT BOOT DIRECTLY INTO FASTBOOT AND IT WILL SAY "UTAG FLASHFAIL CONFIGURED AS FASTBOOT. JUST REFLASH THE BOOTLOADER TO FIX
Code:
mfastboot flash motoboot motoboot.img
(thank you @t4n017 again )
YOU WILL GET SOME ERRORS LIKE HAB CHECK FAILED. JUST IGNORE AND PROCEED.
STEP 3:
Now we shall flash the OTA. Boot into recovery. You shall see a weird android logo with an exclamation mark. AFTER THAT HOLD VOL+ FOR 15 SECONDS, THEN TAP POWER BUTTON (KEEP HOLDING THE VOL+ BUTTON) (thank you @thestory101) and choose apply update from adb in the recovery. Then double-click on "Step 3.bat" or type the following command:
Code:
adb sideload ota.zip
OR just OTA from Settings>About phone>System updates (confirmed by @t4n017) though i would yet recommend using the former procedure.
STEP 4:
Once it has finished, select reboot system now from the recovery. DO NOT WIPE YOUR CACHE. YOU WILL BE STUCK AT THE GOOGLE BOOT LOGO SCREEN FOR AROUND 10-20 SECONDS. JUST BE PATIENT. If you are stuck for more than 20 seconds, just flash [this].
STEP 5:
Now check your phone for and update and you shall get an update notification for 5.1 lollipop. Follow onscreen procedures and complete the update.
STEP 6:
SKIP THIS if you have EUROPEAN XT1032.
Download XT1033 modems [here] if you have the Asian Moto G. THESE MODEMS APPARENTLY DON'T WORK. LOOK AT POST NO. 593 FOR FIX.
Download XT1034 modems [here] if you have the Canadian Moto G
Download XT1032 US GSM modems [here] if you have the us version (thank you @jmonster141)
I HAVE GIVEN LINKS TO ALL THE MODEMS OF THE COMMON VARIANTS OF THE MOTO G. IF YOU HAVE A DIFFERENT VARIANT, DOWNLOAD YOUR RESPECTIVE FIRMWARE, COPY THE "NON-HLOS.bin" and "fsg.bin" FROM YOUR ORIGINAL FIRMWARE TO THE FOLDER WHERE YOU HAVE THE SDK, mFastboot, GPE FIRMWARE AND OTA AFTER STEP 3 AND FOLLOW STEP 5 TO GET NETWORK. IT IS EXTREMELY TIME CONSUMING FOR ME TO HUNT DOWN MODEMS FOR ALL THE NUMEROUS VARIANTS AND LINK THEM IN THE OP (IM KINDA BUSY WITH MY STUDIES RIGHT NOW) SO PLEASE TAKE THE PAIN TO DO SO YOURSELF. ALSO, LINK THE MODEMS YOU USED,TO GET NETWORK, IN THE THREAD SO I CAN ADD IT TO THE OP AND HELP THE REST. (That's how the amazing XDA community works right ?! )
BryanByteZ said:
Link for Stock Roms to extract modem files:
[here]
(All Moto G Variants)
Click to expand...
Click to collapse
hacorn96 said:
I'll just drop this here:
http://forum.xda-developers.com/showthread.php?t=2649763
All variants/regions kernel/recovery/radio files...
Click to expand...
Click to collapse
We shall now flash the modems. You will be put at the welcome screen after a few minutes. Power off, boot into fastboot. Then double-click on "Step 5.bat" or type the following command:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
You shall now be running 5.1 GPE !
voilamos said:
For anyone having difficulties with their network on an XT1033 , try using network fix.bat from here :
http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472
Click to expand...
Click to collapse
ROOT: (OPTIONAL)
Download the latest superSU flashable zip from [here] and copy-paste it into to your phone.
Download the latest TWRP recovery image from [here]. Copy the image to the folder where you have adb and fastboot. Rename the image to "recovery". Open a command prompt in the folder containing this recovery (press shift + right-click, choose open command window here). Boot your phone into fastboot mode and execute the following code:
Code:
fastboot flash recovery recovery.img
Ignore the partition mismatch error.
Use your volume rockers to boot into the recovery. Go to install zip, and choose the SuperSU zip and flash it.
Reboot into rooted 5.1 GPE.
TO FIX THE LAGGY ANIMATIONS IN GOOGLE NOW LAUNCHER, SEE [THIS] POST.
nishantjian4u said:
- MOST IMPORTANT: please read and follow the steps as if your life depends on it. If you have any doubts, read the whole thread. I confirmed the steps with some other google searches wherever I thought I am confused. Luckily for me, if worked like a breeze for me the first time. Read all the messages on the command prompt / terminal on your computer and the information displayed on your phone while you are flashing all sorts of stuff. There are certain important information that you will on this displays. BE PATIENT
Click to expand...
Click to collapse
CREDITS TO ALL PEOPLE WHO HAVE CONTRIBUTED TO THE AMAZING MOTO G XDA COMMUNITY.

pfufle said:
Okay, so there has been a lot of confusion an ambiguity on how to successfully install the GPE lollipop update on the XT1033. The reason i am starting this guide is because I faced a lot of trouble myself trying to get this update and had to scavenge through multiple threads to get stuff working. I had flashed the update on my Moto G XT1033 converted to GPE using the mixed firmware by @deej_roamer [using this tutorial], OTAed to 4.4.4 and flashed the OTA manually using ADB. I was stuck at the bootlogo following this. This was because of the firmware being modified this interfering with the OTA. Since i was now stuck with the new 41.18 bootloader and the partition table (gpt.bin) of the OTA, i could not flash the XT1033 firmware. So this is what I did:
Click to expand...
Click to collapse
That's a nice way to convert I didn't think it could be done this way.... Cool bro

dual sim will work with this method right?
can you give feedback, is it stable enough to be used daily? have you encountered any bugs or features that doest work? force close?
im thinking jumping to 5.01 but need some idea of how stable it is as i dont have a spare phone at the moment if it fail or got bricked

thankyou !!!

No Network
Hey
I still don't see any network on my phone.
This is after I flashed the modem files
Any fix ? Thanks

For me GPE 4.4.4 doesn't boot anymore, because of the new bootloader I assume. GPE 5.0.1 also didn't boot. Only Motorola Firmware booted successfully. Do you know what I can do about that?

This works whit the xt1034 ?

aben.dc said:
dual sim will work with this method right?
can you give feedback, is it stable enough to be used daily? have you encountered any bugs or features that doest work? force close?
im thinking jumping to 5.01 but need some idea of how stable it is as i dont have a spare phone at the moment if it fail or got bricked
Click to expand...
Click to collapse
The build is epic! Flash it right away if you dont need dual sim.
voilamos said:
Hey
I still don't see any network on my phone.
This is after I flashed the modem files
Any fix ? Thanks
Click to expand...
Click to collapse
I am really sorry but i missed an important step in the OP (i realised it right away but my mom wouldnt allow me to touch my PC before i finished my homework :| )
Once you flash GPE 4.4.4 with the original modems, flash the OTA and after that reboot to bootloader and AFTER that flash the modems of the phone model you have. When you boot into lollipop it will say that it will take around 5 minutes to find network and wait patiently until it is done.
k-kuchen said:
For me GPE 4.4.4 doesn't boot anymore, because of the new bootloader I assume. GPE 5.0.1 also didn't boot. Only Motorola Firmware booted successfully. Do you know what I can do about that?
Click to expand...
Click to collapse
Make sure you follow step 2.1. And make sure you used thw links i provided in the OP. GPE 4.4.4 boots just fine for the rest of us. (Sans the screen flickering which is fixed after a screen unlock)

Hi,
I'm stuck on step 3 (can't adb sideload the ota). I can't boot to recovery - just a picture of android with the ! (red) sign.
GPE 4.4.4 is working just fine (with network too).
Thank you!

acid032 said:
This works whit the xt1034 ?
Click to expand...
Click to collapse
Assuming that it is the brazilian version, yes it should work.

Metalingus903 said:
Hi,
I'm stuck on step 3 (can't adb sideload the ota). I can't boot to recovery - just a picture of android with the ! (red) sign.
GPE 4.4.4 is working just fine (with network too).
Thank you!
Click to expand...
Click to collapse
I for got to mention in the OP, you are supposed to press volume up and power button simultaneously when that logo comes for 7 seconds and then release it.

It just reboots the system when I press volume up and power button when that logo shows up.
Thanks
EDIT: Got it to work! Just have to precise!

pfufle said:
Make sure you follow step 2.1. And make sure you used thw links i provided in the OP. GPE 4.4.4 boots just fine for the rest of us. (Sans the screen flickering which is fixed after a screen unlock)
Click to expand...
Click to collapse
Thanks.
As far as I can tell the difference is leaving bootloader (which fails to flash anyway) and GPT from the retail Firmware. I flashed the whole GPE before which resulted in being stuck at bootlogo

k-kuchen said:
Thanks.
As far as I can tell the difference is leaving bootloader (which fails to flash anyway) and GPT from the retail Firmware. I flashed the whole GPE before which resulted in being stuck at bootlogo
Click to expand...
Click to collapse
Yep. The old partirion tables are incompatible with the new bootloader apparantly.

Can somebody confirm if this works for XT1034 (Retail Canada/US AWS)?

Well it Works but i dont have any network I flashed my modems from the original firmware of the xt1034.
Any Help ?

acid032 said:
Well it Works but i dont have any network I flashed my modems from the original firmware of the xt1034.
Any Help ?
Click to expand...
Click to collapse
In the very last step can you try and flash these? Should work, they are XT1034.
https://drive.google.com/file/d/0ByPjgNaqEEYBU0lGenNxTmxwR0k/view?usp=sharing

Anyone of you who has flashed the ota, could you please upload an nandroid backup of the rom
Sent from my XT1031 using Tapatalk

If it is fully functional with moto g XT 1033
If it is fully functional with moto g XT 1033

ali4ek said:
In the very last step can you try and flash these? Should work, they are XT1034.
https://drive.google.com/file/d/0ByPjgNaqEEYBU0lGenNxTmxwR0k/view?usp=sharing
Click to expand...
Click to collapse
MAN I FCK LOVE YOU THANKS, IT WORKS IN THE XT1034
sorry for the caps but Im really happy

[XT1063] downgrade to 21.11.17 4.4.4 then update to 22.21.28 5.0.2

Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
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_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
http://forum.xda-developers.com/showthread.php?p=58136321
Please hit the thanks if it worked and report back.
P.S.
Still unable to lock bootloader until 5.0 firmware released.

Android The Greek said:
First my bootloader is unlocked as I would always get PIV Signature errors in fastboot when downgrading.
Second, I have not be able to look the bootloader at all since I have been on Lollipop before.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I then flashed firmware using Shawn152's scrpt, but replacing the 21.11.23 files with the ones from the link above.
or you can do it manually:
adb reboot bootloader
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_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
Click to expand...
Click to collapse
I presume that you MAY NOT have to flash whole rom, if you 'JUST' flashed the needed version of recovery then you can upgrade with a OTA zip (can't test as only got xt1068) maybe someone can test this - but obviously some OTA's rely on being updated in order.

This is for XT1063 Only!

Android The Greek said:
Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
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_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
P.S.
Still unable to lock bootloader.
Click to expand...
Click to collapse
Bootloader can easily be locked. I've done it & even made a one click to do it as well. However I was able to update to 5.0 without the bootloader being locked. I'm back on KitKat for the third time. I'm not willing to give up root & deal with all the bugs of L.
There is also a custom ROM in these forms that run smoother than the stock & easier to install but still has the root bug.

kingmt01 said:
Bootloader can easily be locked. I've done it & even made a one click to do it as well. However I was able to update to 5.0 without the bootloader being locked. I'm back on KitKat for the third time. I'm not willing to give up root & deal with all the bugs of L.
There is also a custom ROM in these forms that run smoother than the stock & easier to install but still has the root bug.
Click to expand...
Click to collapse
What model do you have?
I can assure you I am not new at this, I bought my phone from Amazon with 21.11.23 and there was an addition added at some point that prevents a downgrade and in turn does not allow the system to be flashed with a locked or unlocked bootloader if you start with the command Fastboot oem lock begin.
if you have an XT1063 please tell me how you locked your bootloader without modifying anything that will then be unreversable.
Don't take it the wrong way, but I have seen people create tools that edit the hex to show bootloader locked then they can no longer unlock it or corrupt the phone and brick.

Android The Greek said:
What model do you have?
I can assure you I am not new at this, I bought my phone from Amazon with 21.11.23 and there was an addition added at some point that prevents a downgrade and in turn does not allow the system to be flashed with a locked or unlocked bootloader if you start with the command Fastboot oem lock begin.
if you have an XT1063 please tell me how you locked your bootloader without modifying anything that will then be unreversable.
Don't take it the wrong way, but I have seen people create tools that edit the hex to show bootloader locked then they can no longer unlock it or corrupt the phone and brick.
Click to expand...
Click to collapse
ETA: I'm not going to get upset over anything in a forum. I just post info to the best of my knowledge in hope to be helpful to someone else. Sometimes that changes as more knowledge is gained.
I have a xt1063 .17 & I did use "fastboot oem lock begin" I don't remember every command but the one click also restored the stock firmware at the same time. I'll have to look at my files in a few. I only made about 20 one clicks & was writing & rewriting a how to guide all at the same time as I was trying to figure it out & get on 5.0 all at the same time. Like I said tho my bootloader is unlocked again & it doesn't seem to affect the ability to flash OTA.
---------- Post added at 12:43 PM ---------- Previous post was at 11:55 AM ----------
OK. I used mfastboot to lock it.
mfastboot oem lock begin
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 oem lock

kingmt01 said:
ETA: I'm not going to get upset over anything in a forum. I just post info to the best of my knowledge in hope to be helpful to someone else. Sometimes that changes as more knowledge is gained.
I have a xt1063 .17 & I did use "fastboot oem lock begin" I don't remember every command but the one click also restored the stock firmware at the same time. I'll have to look at my files in a few. I only made about 20 one clicks & was writing & rewriting a how to guide all at the same time as I was trying to figure it out & get on 5.0 all at the same time. Like I said tho my bootloader is unlocked again & it doesn't seem to affect the ability to flash OTA.
---------- Post added at 12:43 PM ---------- Previous post was at 11:55 AM ----------
OK. I used mfastboot to lock it.
mfastboot oem lock begin
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 oem lock
Click to expand...
Click to collapse
I never said anything about needing to relock it. I just said I have not been able to for those of us that want 5.0.1 and want to lock the bootloader. If you are able to price steps on how you downgraded from 5.0 and locked the boot loader I sure would want to try it myself.
Ideally I would add in the commands above fastboot OEM lock begin and fastboot OEM unlock for those who want a relocked boot loader before flashing the otas. Its just not possible if you are not on 21.11.17 to begin with because of the signed zip downgrade verification

Android The Greek said:
I never said anything about needing to relock it. I just said I have not been able to for those of us that want 5.0.1 and want to lock the bootloader. If you are able to price steps on how you downgraded from 5.0 and locked the boot loader I sure would want to try it myself.
Ideally I would add in the commands above fastboot OEM lock begin and fastboot OEM unlock for those who want a relocked boot loader before flashing the otas. Its just not possible if you are not on 21.11.17 to begin with because of the signed zip downgrade verification
Click to expand...
Click to collapse
Stating that it didn't need locked to flash 5.0 is just added info for anyone fallowing the thread & based on my experience. That may change for flashing 5.0.1.
These commands was ran from a modified 21.11.17 build to lock the bootloader. I thought I read ether in this thread or another thread that you already found a way to flash back to the stock firmware 21.11.17 without the downgrade error. If your on stock 21.11.17 now then you could give the lock command a try from mfastboot. I restored a Nandroid to get back to KitKat from Lollipop.
The one click I made was for those that had tampered with their stock 21.11.17 & wanted to be back to stock & locked. I didn't even know there was a 21.11.23 build at the time.

kingmt01 said:
Stating that it didn't need locked to flash 5.0 is just added info for anyone fallowing the thread & based on my experience. That may change for flashing 5.0.1.
These commands was ran from a modified 21.11.17 build to lock the bootloader. I thought I read ether in this thread or another thread that you already found a way to flash back to the stock firmware 21.11.17 without the downgrade error. If your on stock 21.11.17 now then you could give the lock command a try from mfastboot. I restored a Nandroid to get back to KitKat from Lollipop.
The one click I made was for those that had tampered with their stock 21.11.17 & wanted to be back to stock & locked. I didn't even know there was a 21.11.23 build at the time.
Click to expand...
Click to collapse
Correct!

Android The Greek said:
Bootloader unlock required to avoid downgrade PIV Signature errors in fastboot.
Download firmware for XT1063 21.11.17 here
http://motofirmware.com/files/download/950-retuglb-xt1063-444-kxb2185-17-cid9-cfcxmlzip/
I flashed firmware using @Shawn5162's scrpt, but replaced the 21.11.23 files with the ones from the link above.
http://forum.xda-developers.com/showthread.php?t=2957167
or you can do it manually via fastboot:
adb reboot bootloader
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_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash modem NON-HLOS.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Fastboot flash erase cache
Fastboot flash erase userdata
fastboot reboot
Then I applied all the following OTAs successfully:
Note: download and copy all OTAs to SD card downloads folder then install via STOCK Recovery apply update from SD Card
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-11-6-android-t2939881
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-16-t2965161
http://forum.xda-developers.com/moto-g-2014/general/ota-moto-g-2014-xt1063-v22-21-25-t2978658
Please hit the thanks if it worked and report back. This should help all those stuck on 22.11.6. Please make sure you go all the way back to 21.11.17 first before reporting back.
P.S.
Still unable to lock bootloader.
Click to expand...
Click to collapse
Worked like a charm! Thank you so much, Updated my moto g 2014 xt1063 21.11.23 KitKat 4.4.4 Amazon unocked global using this method. :good:

Thank you for reporting in appreciate it

help
hello,i am somewhat new to these things but surely i can do it with detailed steps(thanks for those)
so here is the thing,i bought Moto G2 from amazon last month and my mobile has these details
System Version:-
21.11.23.titan_retuglb.retuglb.en.US retus
Build Number- KXB21.85-23
i am bored with KitKat ..
a few ques:-
After this tricky update will i be eligible for future updates too?
Can i root after the Lolipop update?
WIl this method format my mobile?
Thanks.
(sry for newbie type ques )

kkriop said:
hello,i am somewhat new to these things but surely i can do it with detailed steps(thanks for those)
so here is the thing,i bought Moto G2 from amazon last month and my mobile has these details
System Version:-
21.11.23.titan_retuglb.retuglb.en.US retus
Build Number- KXB21.85-23
i am bored with KitKat ..
a few ques:-
After this tricky update will i be eligible for future updates too?
Can i root after the Lolipop update?
WIl this method format my mobile?
Thanks.
(sry for newbie type ques )
Click to expand...
Click to collapse
You will get updates. You can Root, however I do not think there is a stable root yet. If you unlock your boot loader it will format, if you already unlocked your boot loader then you will not loose your data.

Android The Greek said:
You will get updates. You can Root, however I do not think there is a stable root yet. If you unlock your boot loader it will format, if you already unlocked your boot loader then you will not loose your data.
Click to expand...
Click to collapse
Its fine w/o root..as far as i am getiing lollipop experience.. My bootloader is unlcoked..will do the thing and post ..thanks again

kkriop said:
Its fine w/o root..as far as i am getiing lollipop experience.. My bootloader is unlcoked..will do the thing and post ..thanks again
Click to expand...
Click to collapse
No problem

Android The Greek said:
No problem
Click to expand...
Click to collapse
downgrade complete now the issue is when i check System Updates it doesnt pick up Lollipop update
and these manual update links doesnt open is there any mirror link?? :crying:

Do you mean you cannot download from mega?
Which one you need I'll put it in my Dropbox and pm you

Android The Greek said:
Do you mean you cannot download from mega?
Which one you need I'll put it in my Dropbox and pm you
Click to expand...
Click to collapse
The two from mega (first two) third one is already on dropbox so not a prob for that..
Thank u very much

so is safe to install ota updates with bootloader unlocked?

CrazyGenio said:
so is safe to install ota updates with bootloader unlocked?
Click to expand...
Click to collapse
Yes an unlocked boot loader has no effect on anything except the abity to flash a custom recovery. If your unlocked and have it all stock, then you should be good

FYI: recovered G5 XT 1676 to stock and updated. :)

Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
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 flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.

where do you get the stock firmware?

Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.

We're you able to revert to a locked bootloader after this, I am looking forward to do so

We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.

astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts

ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing

TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier

downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance

distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order

Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?

distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good

thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.

distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions

Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks

astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
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 flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition

I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.

distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader

astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?

astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan

Need help going back to full stock

Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers

guillermohs9 said:
Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers
Click to expand...
Click to collapse
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, with a TWRP flashable build you won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
You will lose your data so backup your stuff.

Wolfcity said:
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, a TWRP flashable build won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
Click to expand...
Click to collapse
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?

guillermohs9 said:
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?
Click to expand...
Click to collapse
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Yes, you have to unzip the firmware in your adb/fastboot folder on your PC and enter all fastboot commands, you can also use a flashall.bat with all commands in it. You have to copy that bat into your adb/fastboot folder too and just click it.
Here's one:https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
There are some tutorials around how to do it all but some are a bit outdated. I'm about to write an actual one.
You need Motorola drivers on your PC:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
and something like Minimal Adb & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=sharing
If you're not familiar with this procedure you can also give Lenovo Motorola Smart Assistant a shot:
https://support.lenovo.com/de/de/downloads/ds101291

Wolfcity said:
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Click to expand...
Click to collapse
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.

guillermohs9 said:
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.
Click to expand...
Click to collapse
I'll take a look what firmware has been pushed to your region. If you're on the wrong update channel you won't receive OTA updates because Motorola/Lenovo only pushes one update for every location, either the US version (17-x) or the other one (13-x).
I'm writing on that guide but it will be a bit extensive because it should cover unlocking/flashing/rooting/decrypting/locking, the whole thing.

Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:

BartKey said:
Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:
Click to expand...
Click to collapse
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot

I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Edit: flashed Twrp now it says "bad key" on the unlocked device screen but it boots into stock Oreo.
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.

guillermohs9 said:
I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Click to expand...
Click to collapse
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.

Wolfcity said:
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.
Click to expand...
Click to collapse
It used to say N/A instead. I don't mind. The problem now is that it always tries to boot into recovery.

guillermohs9 said:
....
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.
Click to expand...
Click to collapse
As I said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?

wolfcity said:
as i said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?
Click to expand...
Click to collapse
opss28.85-17-4

guillermohs9 said:
opss28.85-17-4
Click to expand...
Click to collapse
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.

Wolfcity said:
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.
Click to expand...
Click to collapse
Thanks! I figured the same about the future updates, now Motorola is focused on newer devices so december security patch is enough.
I am on stock, unrooted, relocked bootloader now. I used the commands you provided (included erase userdata) then had to flash TWRP, flash magisk, use adb shell and dd to clear that misc partition (so it boots into system), and finally did
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
to relock bootloader. It works as expected now and it's ready to be used by anyone.
Thanks a lot

Wolfcity said:
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thanks a lot @Wolfcity
I came from OPS28.85-17, without updates available.
Now I flashed OPS28.85-13 with your instructions not to erase userdata.
Checking for updates: 13.3 available -> installed
13.5 available -> installed and "up to date" security patch dec 2018
:good:

@guillermohs9 @BartKey: Great to hear everything is working! I will add your experiences to the upcoming tutorial.