Related
For all Condor Owners if you wish to restore your Moto E back to stock then follow the guide, Ask any doubts in the comments!
Droid-Developers Website is down, I don't have any locally stored copy. Please wait until the link is updated or better sources are found. If any of you are having the original firmwares in your Hard-drives, Please, upload them and share their links, this would help the community in general. For now I am helpless and this post will not make sense.
I did find some firmwares for moto E here
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research! YOU are choosing to follow this method to restore, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Pre-Requisite:
Installed Motorola Drivers.
Instructions:
Go to This This link, and download the firmware for your model! If you are unsure which one is yours please see Appendix 1
Download mfastboot-v2 and Extract it into the same folder
Reboot the phone into Bootloader using VolumeDown+Power Button
If you prefer an automatic one click process please go to step 5
Shift+RightClick in empty space in the extracted folder and choose open a command window here.
If you do not wish to lock bootloader skip 4.1 and 4.3
4.1
Code:
mfastboot.exe oem lock begin
4.2
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
4.3
Code:
mfastboot.exe oem lock
4.4
Code:
mfastboot.exe reboot
OR
If you just did 4th step, You can skip this
Download Restore.bat/Restore+lock.bat from Attachments, Extract it to the same folder and just run
And the phone is as good as new.
So now experiment all you want, flash different firmwares.
Appendix:
How to choose Correct Firmware for your phone
If you are unsure which one is your firmware, go to Settings>About Phone>System Version the text written there will be similar to the version you want to choose!
If You cannot access your phone or have changed ROM, then please go to bootloader mode using step 2 and 3 from instructions, Open command window like in step 4. Enter
Code:
fastboot getvar ro.build.version.full
. You will see the version to choose in output.
Still cant find, then wait the list at droid-developers is still expanding, your firmware version will be soon up
If you don't like the bootloader unlock logo then here is a method by @cschmitt originally posted here
Download this file, copy it to your fastboot location
Reboot to bootloader using Power+VolumeDown
Do following command from command prompt
Code:
fastboot flash logo logo.bin
Reboot and enjoy
If flashing is failed in any of the commands
Thanks @sw33ty4ppu for asking this question.
Critical Commands (Absolutely Necessary Commands, which if failed will hard brick)
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash boot boot.img
Non-Critical (If these failed, It will still allow you to go to bootloader and start flashing again)
Code:
mfastboot.exe flash logo logo.bin
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
First check which command gave you an error in flashing.
Any of the non-critical command fails to flash, You can start flashing again and hope it might work, you can also check if the downloaded files are proper or their extraction from zip is proper. You can ask for help here on XDA in Q&A section as well.
Any of the critical command fails to flash, it is absolutely necessary that you do not exit bootloader. Because when device is in bootloader mode, bootloader is loaded into RAM and is still the original copy, you can still take the phone which is already in bootloader mode to a friend's place and get the flashing done there. But if you reboot bootloader somehow(knowingly/unknowingly). Man, You're screwed. Morale of the story, don't turn off/ reboot your phone until correct flashing is performed.
This also is another reason that experienced users prefer to enter commands manually than rely on an automated .bat or .sh script.
If it helped, Hit thanks
Reserved!
Thanks for the guide!!:laugh::good:
Maybe a noob question but want to know how different is the mfastboot.exe from the normal fastboot commands?
Edit: I checked with the files in the directory linked for mfastboot and found the files are from android sdk. correct me if im wrong. Thanks in advance
phanitej said:
Maybe a noob question but want to know how different is the mfastboot.exe from the normal fastboot commands?
Edit: I checked with the files in the directory linked for mfastboot and found the files are from android sdk. correct me if im wrong. Thanks in advance
Click to expand...
Click to collapse
What mfastboot is basically a set of extended commands for normal fastboot, what Motorola has done is taken the fastboot protocol that is integrated into the bootloader code and added additional features and operations to fit with how there devices partition schemes are laid out and how they have designed the devices. In summary think of it as fastboot from the Android Open Source Project (Which is what is found in the Android SDK) with extra features for Motorola devices. The files in the directory you saw do come from the Android SDK however mfastboot and fastboot included in the Android SDK are not the same, mfasboot and the files from the Android SDK were bundled together for the convenience of downloading them. Let me know if you still have question's I'll be happy to answer them.
shimp208 said:
What mfastboot is basically a set of extended commands for normal fastboot, what Motorola has done is taken the fastboot protocol that is integrated into the bootloader code and added additional features and operations to fit with how there devices partition schemes are laid out and how they have designed the devices. In summary think of it as fastboot from the Android Open Source Project (Which is what is found in the Android SDK) with extra features for Motorola devices. The files in the directory you saw do come from the Android SDK however mfastboot and fastboot included in the Android SDK are not the same, mfasboot and the files from the Android SDK were bundled together for the convenience of downloading them. Let me know if you still have question's I'll be happy to answer them.
Click to expand...
Click to collapse
Thanks for the explanation
The reason why i wanted to know is, i use lubuntu and don have any windows PC i cud use. Was able to root and flash the device using fastboot, so in case i wish to lock it back, dint want to go through the hassle of searching for a windows PC
How to restore Moto logo instead of bootloader unlocked logo?? thanks
gaurav2009 said:
How to restore Moto logo instead of bootloader unlocked logo?? thanks
Click to expand...
Click to collapse
You could try the bootlogo restore method for moto G, it is unconfirmed weather it works or not!
Otherwise you will have to wait for someone to modify the logo!
deej_roamer said:
You could try the bootlogo restore method for moto G, it is unconfirmed weather it works or not!
Otherwise you will have to wait for someone to modify the logo!
Click to expand...
Click to collapse
Actually i tried it though the warning is removed but the M logo doesnot show up it is all black for some seconds then the bootanimation starts up
gaurav2009 said:
Actually i tried it though the warning is removed but the M logo doesnot show up it is all black for some seconds then the bootanimation starts up
Click to expand...
Click to collapse
Better than the pathetic white unlocked warning!
deej_roamer said:
Better than the pathetic white unlocked warning!
Click to expand...
Click to collapse
Yeah lol
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
cschmitt said:
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
Click to expand...
Click to collapse
Added to main thread!
cschmitt said:
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
Click to expand...
Click to collapse
Thanks it works perfectly
Nice guide
Sent from my XT1022 using XDA Free mobile app
lock bootloader
can the bootloader be locked without flashing whole firmware?
and will it wipe or erase all data like unlocking?
please tell me..
indrasen00 said:
can the bootloader be locked without flashing whole firmware?
and will it wipe or erase all data like unlocking?
please tell me..
Click to expand...
Click to collapse
No Locking bootloader needs a fresh firmware! you will need to wipe your device with its internal memory completely,
Thanks ! Worked Perfectly !
cschmitt said:
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
Click to expand...
Click to collapse
Thanks ! Worked Perfectly !
How to edit/create log.bin file in linux for moto E ?
cschmitt said:
Here is modified logo.bin for bootloader unlocked Moto E (shows normal boot splash instead of dire warning.)
1. Download and unzip logo.zip.
2. Reboot to fastboot mode (power + vol down)
3. fastboot flash logo logo.bin
4. Reboot, enjoy!
Click to expand...
Click to collapse
How to edit/create log.bin file in linux for moto E? How did u edit the original logo.bin file. pls give the steps to do the same.
paultsr said:
How to edit/create log.bin file in linux for moto E? How did u edit the original logo.bin file. pls give the steps to do the same.
Click to expand...
Click to collapse
I would recommend taking a look at this guide , it steps are essentially the same for the Moto E and since part of the guide involves GIMP you will be able to follow along on Linux.
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.
Pre-requisites:
a) Download and install Motorola Moto GDrivers
b) Download and extract the stock Firmware of your choosing
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot View attachment 2427667 (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
d) Get ADB (if you don't already have this, I suggest downloading and installing Minimal ADB and Fastboot by shimp208:
Direct Download
Disclaimer:
Follow these instructions at your own risk. If something goes wrong don't blame me!
These are the original stock signed image files from Motorola it should work on all Moto G (2015) Variants.
Steps to restore stock firmware:
1) Reboot the phone into bootloader mode. There are 2 ways to do this.
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 "Minimal ADB and Fastboot". Type:
Code:
adb reboot-bootloader
You should see the Moto G bootloader screen with the following options:
Code:
Normal Powerup
Recovery
Factory
Switch Console [NULL: null]
Barcodes
BP Tools
2) Open a command prompt / terminal (Start -> cmd.exe in Win7) and browse to the folder with the extracted firmware.
In my case:
Code:
cd c:\falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB
3)
Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Please make sure to verify the system.img parts from your corresponding firmware before flashing
4) Wait, you should now be rebooted into a fully stock Moto G firmware.[/FONT][/SIZE]
Original Thread
Creditstbon3
@lohanbarth for instructions and firmware images
FAQ
Q1: Will this work on locked bootloaders?
Ans: Yes as stock firmwares are digitally signed by Motorola.
RESERVED
The link to stock Firmware are broke.
Firmware link is broken
Your're link is broken can't download.
Can I flash this firmware on Moto G 2nd LTE XT1079 (buy from China)?
Gustavo47 said:
The link to stock Firmware are broke.
Click to expand...
Click to collapse
cagechen said:
Your're link is broken can't download.
Can I flash this firmware on Moto G 2nd LTE XT1079 (buy from China)?
Click to expand...
Click to collapse
The links aren't up yet
work
it will work on moto g 2014
Lucas Eugene said:
The links aren't up yet
Click to expand...
Click to collapse
you know when will be available for download?
aditya rockzz said:
it will work on moto g 2014
Click to expand...
Click to collapse
Yes it will but make sure you flash the right firmwares from your thread.
mtkpunisher said:
you know when will be available for download?
Click to expand...
Click to collapse
I don't know. It generally is uploaded within a month. But I could be wrong.
Firmware images are now uploaded for both 4g and 3g variants
Will this re-enable further OTA updates from Motorola?
Ashwin Prasad said:
Will this re-enable further OTA updates from Motorola?
Click to expand...
Click to collapse
In combination with a full un-root yes.
I updated my moto g 2 to lollipop through ota I want to downgrade to kk. Can I try this method to downgrade ? BTW I'm on stock
The XT1079(Buy from China) can flash the firmware?
thanks!
Noob question, the XT1072 ROMs you offer are fine for both 8GB and 16GB ? becouse i have the 8GB
Hi Lucas,
Am quite new at this so will try to be as clear as I can.
Got a new Moto G (4G) from China Model XT 1079 that is unlocked and has got TWRP already installed on it.
Since it has a lot of Chinese stuff on it which I dont need/cant understand I want to do either one fo the following
1) Install a good custom Rom (Either Cyanagen mod or Titan if any compatiblke custom ROMS for this model is available)
2) Get back to the original stock firmware
Your help is gratefully needed
Cheers
For me it said: "The image is too large"
How i can fix?
im stuck on the warning bootloader unlocked page??
any ideas?
it won't boot up
though i can get into bootloader
I flashed the EU firmware, and I changed 2° command 'fastboot flash bootloader bootloader.img' with 'fastboot flash motoboot motoboot.img' and i restored successfully the firmware.
Sorry for my english
Really work
successful!!!
I have been trying to root my phone. I have been have problems with twrp. I have installed twrp through both the moto g5 plus toolkit and manually(command prompt and adb/adb fastboobt). I have had several problems with twrp. Firstly I can't seem to install it without wiping everything off my phone. Secondly twrp won't install stock rom, flash zip files and sometimes img files. Thirdly It keeps failing to mount data.
Every time I install TWRP I have to use the moto g5 plus toolkit flash stock rom so I can use my phone.
After flashing twrp I reboot to recovery mode, go to wipe, then "swipe to factory reset." I the go to reboot or reboot to recovery. Most of the installation instruction regarding twrp say to do this. The problem is I have to install/re-install stock rom in my phone via the toolkit because there is nothing on my phone but a twrp after I swipe factory reset an I can't get twrp to install stock rom.
Since I can't get twrp to install stock rom from a zip file I have to use the moto g5 plus toolkit which wipes twrp and flashes the stock rom.
After flashing stock rom I tried again and was prompted for a password. I don't have password and there was something about decryption on the screen. I hit cancel went to Wipe then Format Data and typed yes at the prompt. I went to reboot hit recovery(reboot to recovery). My phone was wiped clean and I had nothing but twrp on it again. I tried install stock rom off my sd but I got allot of errors( can't mount data, ect...) I tried to fix this by using twrp to flash an install img of the latest version of twrp. This did not fix the problem.
I can't use twrp to install stock rom, or zips nor can I install twrp without having to flash stock rom and erase twrp from my phone because installing twrp removes everything and renders my phone useless. Every time I install twrp I'm left with nothing but twrp on my phone. Everything is wiped there is nothing there but twrp.
Could someone please tell me how to install twrp without wiping my phone completely and how to get around the problems I have been having. I have tried several different things but I can't fix the mount error nor can I get twrp to install stock rom. I just can't figure this out.
I have attached several screenshot below. If you are willing to help please take a look at them.
first of all stop using that toolkit. if you were flashing stock rom the right way you wouldnt be replacing recovery.
follow these steps PRECICELY
1. download the actual stock xml.zip and extract it
2. inside the folder make a txtfile called flash rom and rename it to flashrom.bat
2a. right click and select edit, paste this into notepad ans save it (as a .bat --important)
Code:
@echo off
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery twrp.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot flash recovery twrp.img
mfastboot oem fb_mode_clear
pause
mfastboot reboot
3. https://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280 download this and extract all files into where the stock xml.zip is extracted
4. place the twrp youre trying to use (should be the 64bit one from the 64bit thread) in the place you extracted the xml.zip named twrp.img
5. double click the batch file (flash rom.bat) and let it finish (ignore any errors about signature verification and/or corrupt image). when the flash is done it will say "press any key to continue" once you press a key it will reboot your phone, MAKE SURE YOU ARE HOLDING VOLUME DOWN WHILE YOUR PHONE REBOOTS FOR THE FIRST TIME AFTER THE FLASH
6. at this point you WILL have twrp, AND STOCK ROM. THIS IS A PROBLEM. stock rom will replace twrp at first boot, heres how to solve that, first by decrypting data:
6A. wipe cahce SPECIFICALLY by going to wipe, selecting advanced wipe, check cache, and then tap repair or change file system. then tap change file system then ext4 and swipe to apply
6B go back to twrp's main menu and tap reboot>recovery
6C. once back in recovery wipe data SPECIFICALLY by going to wipe, selecting advanced wipe, check data, and then tap repair or change file system. then tap change file system then f2fs and swipe to apply; reboot to recovery again
7. at this point you are running stock rom, decrypted, and have twrp BUT STOCK ROM WILL STILL REPLACE TWRP IF YOU BOOT, the easiest way to do this is by flashing magisk.
thats it, you should be at stock rooted decrypted with magisk and twrp.
8. come back if that doesnt work. but it should, i literally did the whole process while writing this to make sure i didnt steer you in the wrong direction
Ae3NerdGod said:
2. make a txtfile inside the folder called flash rom and rename it to flashrom.bat
Click to expand...
Click to collapse
The stock rom I downloaded doesn't have a folder call flash rom in it. Is the folder you extracted the Stock Rom called flash rom or should there be a folder called flash rom be in my extracted stock rom folder.
place the twrp youre trying to use (should be the 64bit one from the 64bit thread) in the place you extracted the xml.zip named twrp.img
Click to expand...
Click to collapse
I don't have an xml.zip name twrp.img. I have an image file.(img) not a zip name twrp.img. Did you mean place the twrp image file into the extracted xml.zip.
Would it be easier to place the replace the recovery.img in the extracted xml.zip with the twrp.img and then rename the twrp.img recovery(basicaly replace the recovery.img in the zip with twrp).
no, name the txtfile flash rom, i see the ambiguity though. ill reword it:
inside the folder make a txtfile called flash rom and rename it to flashrom.bat
Click to expand...
Click to collapse
also i meant to name the twrp image file you are using to "twrp.img" and drop it in the folder that contains all the files youve extracted from the xml.zip
and no, it wouldnt be easier because the batch file i wrote flashes "twrp.img" to recovery
attached is roughly what your xml.zip directory should look like (ive deleted a couple unneeded files you do not have to also)
I did everything correctly however when I run the batch file(flashrom.bat) the command prompt displays <waiting for device> and nothing happens.
I have developer setting enabled and usb debugging and my boot loader is unlocked(oem unlocking enabled). I have all the correct drivers for my phone and adb installed on my computer. I do not know why it cannot detect my phone.
:|
Why make it difficult and act like a ****. There no reason to make a .bat file or removing anything. Keep it simple FFS.
This >>> "mirrors . lolinet.com /firmware /moto /potter /official /RETAIL /POTTER_RETAIL_ 7.0_NPN25.137-92 _cid50_subsidy- DEFAULT_regulatory-DEFAULT_CFC .xml .zip" is the Nov 1st firmware for retus, assuming you have that. Extract "mega . nz / #!dqwE1ZJT!OA9N1pxNnDAs9UVkeiVKoVIkvSrZQNWUyKvtORB3" to your desktop for easy access, they are standalone adb/fastboot files. Now take the firmware and extract that into the folder with the adb/fastboot files. Press Shift+Right-click in the folder and choose "open command window here." Make sure you're phone is connected to your PC in bootloader mode. Run "adb shell" and let adb load. Then run "fastboot devices" to assure your device is being discovered. Now you can start manually entering or copy+pastaing the commands to install the firmware one line at a time after the previous command finishes. If you get an error after the "fastboot reboot" reboot, turn your phone off and on again. It should boot up just fine.
EXTREMELY sorry for breaking up the links. I'm not a huge poster and XDA only allows links after 10 posts. so just rebuild the links with h t t p s : / / ahead of them. Stupid rules.
I literally just did this myself because I'm unlocked with a custom kernal, so I do OEM updates manually. It's a slightly tedious task but you can see that everything is installs properly.
If you're not on retus, my time isn't in vein, we can find get the firmware for your device. Here's the commands: Some might say parts are unnecessary, but when you're not sure what's what, it's best to stick with the normal commands.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
ALSO: Install twrp after you've booted up once, not with the firmware. To make it simple drop the twrp.img into its own folder with the adb/fastboot files, run command prompt with the folder the same way you did before and enter these commands:
adb shell
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot recovery
If theres's s password when twrp loads, cancel writing and wipe your data only. Then reboot back into TWRP again before rebooting the system.
Hope this helps and goes smooth for you.
User0666 said:
Extract "mega. nz/#!dqwE1ZJT!OA9N1pxNnDAs9UVkeiVKoVIkvSrZQNWUyKvtORB3"
Click to expand...
Click to collapse
When I go to the above site I get a message asking for a Decryption Key. I don't know what the decryption key is. You a said that the download was a standalone add/fastboot package. Is the stand alone files you were referring to the same as the googles standalone platform-tools for Android.
Also my moto g5 plus is on retus but it is currently running on Potter NPN 25.137-35. I am going to assume that firmware you said to use(Potter NPN 25.137-92) will work.
Ae3NerdGod said:
first of all stop using that toolkit. if you were flashing stock rom the right way you wouldnt be replacing recovery.
follow these steps PRECICELY
1. download the actual stock xml.zip and extract it
2. inside the folder make a txtfile called flash rom and rename it to flashrom.bat
2a. right click and select edit, paste this into notepad ans save it (as a .bat --important)
Code:
@echo off
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery twrp.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot flash recovery twrp.img
mfastboot oem fb_mode_clear
pause
mfastboot reboot
3. https://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280 download this and extract all files into where the stock xml.zip is extracted
4. place the twrp youre trying to use (should be the 64bit one from the 64bit thread) in the place you extracted the xml.zip named twrp.img
5. double click the batch file (flash rom.bat) and let it finish (ignore any errors about signature verification and/or corrupt image). when the flash is done it will say "press any key to continue" once you press a key it will reboot your phone, MAKE SURE YOU ARE HOLDING VOLUME DOWN WHILE YOUR PHONE REBOOTS FOR THE FIRST TIME AFTER THE FLASH
6. at this point you WILL have twrp, AND STOCK ROM. THIS IS A PROBLEM. stock rom will replace twrp at first boot, heres how to solve that, first by decrypting data:
6A. wipe cahce SPECIFICALLY by going to wipe, selecting advanced wipe, check cache, and then tap repair or change file system. then tap change file system then ext4 and swipe to apply
6B go back to twrp's main menu and tap reboot>recovery
6C. once back in recovery wipe data SPECIFICALLY by going to wipe, selecting advanced wipe, check data, and then tap repair or change file system. then tap change file system then f2fs and swipe to apply; reboot to recovery again
7. at this point you are running stock rom, decrypted, and have twrp BUT STOCK ROM WILL STILL REPLACE TWRP IF YOU BOOT, the easiest way to do this is by flashing magisk.
thats it, you should be at stock rooted decrypted with magisk and twrp.
8. come back if that doesnt work. but it should, i literally did the whole process while writing this to make sure i didnt steer you in the wrong direction
Click to expand...
Click to collapse
I'm in a similar position... how ever I have no issue mounting my phone. I follow your steps to the T and I end up with my phone failing to load the operating system....Can you please let me know what I can do? I'm on the XT1687. If I try to flash other roms I get a TWRP error 255...
---------- Post added at 12:02 PM ---------- Previous post was at 11:49 AM ----------
bboygmoney said:
I'm in a similar position... how ever I have no issue mounting my phone. I follow your steps to the T and I end up with my phone failing to load the operating system....Can you please let me know what I can do? I'm on the XT1687. If I try to flash other roms I get a TWRP error 255...
Click to expand...
Click to collapse
OMG If you were here I'd kiss you!!!! Fixed. Had to wipe system then I believe i had the wrong firmware....Thank you soo!!!!!!!!
I followed the instructions, but I can't boot to anything except TWRP. No matter what I select in the reboot menu, the phone reboots to TWRP.
salsolomon said:
I followed the instructions, but I can't boot to anything except TWRP. No matter what I select in the reboot menu, the phone reboots to TWRP.
Click to expand...
Click to collapse
Open up adb command window and type these three commands,
Code:
adb devices
adb shell
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Then reboot.
I do not know whether my EFS and Persist are intact but I have backed them up. I had installed Pixel Experience 9.0 and then restored my TWRP backup to go to Stock Oreo, Build Number: OPSS28.85-13-5. This is my current Build, unlocked, rooted and has TWRP.
Can I follow this (https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738) guide to go back to Stock Nougat and then upgrade to the latest official update from moto?
I am asking to confirm as the Stock ROM given in the guide is Nougat ROM and I am on Oreo as mentioned above. I won't have any problems right? I do not want to lose VoLTE and my IMEI.
Any help will be appreciated.
Installed Oreo ROM via fastboot on my Moto G5 Plus [RETIN/Indian/ XT1686]
I am sharing my experience here so that it might help someone looking to flash stock ROM via fastboot. This is not meant to be a tutorial, but I will list out the steps I followed. I am not responsible if you mess up or hard/soft brick your device when following the steps I mentioned below. Always make a backup of your data/photos/videos/music and whatever else. Also make a backup with TWRP to be safe.
So instead of following the guide linked in the above post, I followed this one and successfully unrooted and returned to stock: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
But I did not use the ROM linked by the OP in that thread. Instead I downloaded this one : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This RETIN ROM works for me because I have the Indian XT1686. I don't know if it matters but I had the same version (13-5) before, but I am not sure whether it was RETAIL or RETIN.
Anyways guys make sure you download the right ROM for your device if you are going to install via fastboot. You can download the right ROM for your device from here: https://mirrors.lolinet.com/firmware/moto/potter/official/
There are different folders for ROMs of different regions in the above link. So carefully download the one your device is compatible with.
Also, I installed fastboot drivers from here: https://forum.xda-developers.com/showthread.php?t=2588979
Follow the instructions and also follow the video tutorials in the post to install fastboot drivers if your phone isn't detected in fastboot.
Then once I had downloaded the ROM and installed ADB, I extracted the ROM zip into a folder. Copy pasted ADB Files into the same folder (download ADB Files that worked for me _ attached to this post below).
FInally I put my phone in fastboot (turn off phone, then press volume down and power simultaneously till fastboot shows up). Connected the phone to my PC. Then opened CMD in the folder where I had extracted the ROM and copy pasted the ADB Files. To open cmd in a folder, just type cmd in the address bar of the folder and press enter.
And then I copy pasted the following code into the cmd window:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
The above commands will run when pasted in cmd and your phone will be flashed with the ROM. It took a couple minutes to install and then I had to press enter while still in cmd to reboot the phone. Then the phone rebooted. Took a couple minutes more to boot, so stay patient. Then once the phone booted, I disconnected it from my PC and set the phone up as usual. DO NOT disconnect the phone when the fastboot commands are running and the ROM is being flashed. Note that the above fastboot commands will only flash the ROM. It will not lock the bootloader.
If you want to lock the bootloader then follow the instructions here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
Note that I haven't locked my bootloader. So you will have to try and see for yourself whether it locks your bootloader.
Also once I booted up I got update notification and was able to update to the Feb 2019 OTA security update. So I can for sure say that updates work. VoLTE, calling, camera, almost everything I checked works.
Cheers. :victory: