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!!!
Related
Pre-requisites:
a) Download and install Motorola Drivers:
http://forum.xda-developers.com/showthread.php?t=2550635
b) Download and extract the stock firmware of your choosing from:
Looks like this link is now broken :'-( http://sbf.droid-developers.org/phone.php?device=14
The firmwares with '_umtsds' in the file name are for the 'dual-sim' versions of the Moto G, it's probably not a good idea to flash these onto single sim phones, or vice-versa.
Edit: More firmwares for international retail and carrier devices can be found here:
http://www.filefactory.com/folder/c6cdedc45a775d27
Edit: The firmware files have been updated most of the firmware archives are now in .tar.gz archives which include Motorola fastboot and flashing scripts for OSX, Linux and Windows.
On windows the .tar.gz archives need to be opened and extracted using a 3rd party archive manager. e.g. 7-zip, or PeaZip, Windows cannot extract these files natively, Linux and OSX can.
I used the retail British firmware (fastboot_falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB.tar.gz), extracted to c:\
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot View attachment mfastboot-v2.zip (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:
https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE
Disclaimer:
Follow these instructions at your own risk. If something goes wrong don't blame me!
I have only tested this on a UK Retail Moto G with an unlocked bootloader, however as these are the original stock signed image files from Motorola it should work on all devices.
See notes at the bottom of this post for downgrading from 4.4.2 to 4.3.
Edit: tkm89 reports that he was able to use this guide to restore Stock Retail British firmware on a bootloader locked Tesco-mobile Moto G
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
3a) If you downloaded and extracted a firmware in .tar.gz format
In windows, run the 'flashall.bat' script Type:
Code:
flashall.bat /eu
The "/eu" switch forces userdata to be erased from the device, this is the same as a factory reset or wipe this is recommended when restoring stock firmware.
In Linux/OSX run the flashall.sh script. Type:
Code:
chmod +x flashall.sh
./flashall.sh
Downgrading:
The scripts will fail with an error on downgrading from 4.4.2 to 4.3. Open the script in a text editor (notepad) and delete (or comment) the following:
Lines 89-90 in the flashall.bat file:
Code:
CALL :fastboot_flash partition gpt.bin
IF %errorlevel% NEQ 0 EXIT /b 1
Lines 120-121 in the flashall.sh file:
Code:
run $fastboot -s "$serial_number" flash partition gpt.bin
if [ $? -ne 0 ]; then echo "ERROR: fastboot failed."; exit -1; fi
3b) If you downloaded and extracted a firmware in .xml.zip format.
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 motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Downgrading:
The 1st command "mfastboot flash partition gpt.bin" will fail on 4.4.2 to 4.3 downgrade. Skip this command if you are downgrading and continue with the other commands, which should work.
4) Wait, you should now be rebooted into a fully stock Moto G firmware.
t-bon3 said:
[...]
Click to expand...
Click to collapse
added to FAQ
matmutant said:
added to FAQ
Click to expand...
Click to collapse
Can you please remove it temporarily, it's not working at the moment! Sorry about that.
t-bon3 said:
Can you please remove it temporarily, it's not working at the moment! Sorry about that.
Click to expand...
Click to collapse
ok
any news? rsd lite still not see Moto G on windows 8.
Bart123 said:
any news? rsd lite still not see Moto G on windows 8.
Click to expand...
Click to collapse
Guide is updated and working now. :fingers-crossed:
At the moment the flashing needs to be done one partition at a time using a specific motorola version of fastboot. Hopefully a new version of RSD lite will be released that simplifies the whole process.
I was having problems with RSD Lite, when trying to flash the retail British ROM (mine came with the Tesco ROM pre-installed). This worked perfectly on my Moto G with a locked bootloader!
thanks for the guide, ive also just flashed stock firmware over preinstalled tesco firmware with a locked bootloader.
Worked flawlessly on my Tesco Mobile Moto G. Many thanks for the guide fella
Is the bootloader warning Logo also removed?
Gesendet von meinem XT1032 mit Tapatalk
Wich of these stock rooms are the Brazilian XT1033 for the 16gb dual chip???
fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
alex1301 said:
Is the bootloader warning Logo also removed?
Click to expand...
Click to collapse
If you just follow the guide above then no, your unlocked bootloader and warning will remain after flashing.
The procedure for relocking the bootloader is to issue the following command in fastboot before flashing:
Code:
mfastboot oem lock begin
then after flashing but before rebooting enter the following:
Code:
mfastboot oem lock
This should lock the bootloader BUT I have seen reports that even after re-locking there is still a warning screen saying that the bootloader has been previously unlocked!
Allewar said:
Wich of these stock rooms are the Brazilian XT1033 for the 16gb dual chip???
fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
Click to expand...
Click to collapse
first one with ds 'dual-sim' in the name
C:\Motorola\falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-
Brasil_BR>mfastboot flash system system.img_sparsechunk.0
error: cannot load 'system.img_sparsechunk.0'
I had this message when I try, the previous commands worked right!
Daniel
moto g 16gb dual chip
djmgermanos said:
C:\Motorola\falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-
Brasil_BR>mfastboot flash system system.img_sparsechunk.0
error: cannot load 'system.img_sparsechunk.0'
I had this message when I try, the previous commands worked right!
Daniel
moto g 16gb dual chip
Click to expand...
Click to collapse
The south american firmwares do not have multi-part /system images. In that case use this command instead:
Code:
mfastboot flash system system.img
t-bon3 said:
The south american firmwares do not have multi-part /system images. In that case use this command instead:
Code:
mfastboot flash system system.img
Click to expand...
Click to collapse
Tanks
djmgermanos said:
Tanks
Click to expand...
Click to collapse
Now I have this message
C:\Motorola\falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-
Brasil_BR>mfastboot flash system system.img
sending 'system' (524288 KB)...
OKAY [ 18.111s]
writing 'system'...
Multi-Flash is not supported any more!
Please download latest fastboot from: xxxxxx
the link don´t work
Daniel
some of the lines show errors for me:
Sparsechunk2: Failed to validate sparse image
Sparsechunk0: Invalid signed image
other wise, it seems to work fine
thanks,
djmgermanos said:
Now I have this message
C:\Motorola\falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-
Brasil_BR>mfastboot flash system system.img
sending 'system' (524288 KB)...
OKAY [ 18.111s]
writing 'system'...
Multi-Flash is not supported any more!
Please download latest fastboot from: xxxxxx
the link don´t work
Click to expand...
Click to collapse
Can you try mfastboot.exe from the attached zip. This is taken from the south american firmware release.
Now it works
Thanks
Daniel
Moto G 16gb dual chip Brazil
XT1033
---------- Post added at 12:25 PM ---------- Previous post was at 12:13 PM ----------
Allewar said:
Wich of these stock rooms are the Brazilian XT1033 for the 16gb dual chip???
fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
Click to expand...
Click to collapse
Esta
fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
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.
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
Pre-requisites:
a) Download and install Motorola Moto EDrivers
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 E 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 E (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 E 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 oem fb_mode_set
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
mfastboot erase customize
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
If you want to skip typing these commands one by one use MOTOEFLASHALL.bat. Place the .bat file inside the extracted firmware folder and run it.
4) Wait, you should now be rebooted into a fully stock Moto E firmware.
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
nice job!,
edit
iB4STiD said:
nice job!, but links aren't working
Click to expand...
Click to collapse
Are stock images even available yet?
iB4STiD said:
nice job!, but links aren't working
Click to expand...
Click to collapse
qbking77 said:
Are stock images even available yet?
Click to expand...
Click to collapse
The stock firmware aren't up yet
Lucas Eugene said:
The stock firmware aren't up yet
Click to expand...
Click to collapse
ah, thought they were thats why u made the thread.. this will come in handy tho in the future thanks :good:
good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<
lohanbarth said:
good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<
Click to expand...
Click to collapse
Hi thanks for the link I've created a new thread to manage Firmware
any stock firmware for the XT1527?
Stock firmware, non carrier
I tried following the steps to restore the firmware, but no luck since I got Preflash validation failed, which I take it to mean the boot.img is not the right one for the moto e2 (bought it from motorola online store). I had everything working, but decided to re-lock the phone, and forgot to check allow oem unlock. When i ran fastboot oem lock it sat there, and then on reboot it didn't start up, just stayed on fastboot screen. No matter what I do I can't get it past it and trying again to unlock it it says:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
So now I am stuck in a fastboot loop. Any suggestions for things to would be great.
Thanks.
Useful subject
https://www.youtube.com/watch?v=S1myrGuMCQg
lohanbarth said:
good evening here Rom stock
XT1524_RETEUALL_MOTOE2 (4G-LTE) _5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml >>>> here <<<<
Click to expand...
Click to collapse
@lohanbarth
can you provide stock rom for moto e 2015 3g variant
has moto released source or the firmware from the US lte gsm varient? what you have posted is for the EU model.
i'm wondering if the EU model is maybe the international version? which could in fact be used in the US.
Hi all
Stocks firmwares repository:
http://forum.xda-developers.com/showpost.php?p=60154569&postcount=21
Thanks if you help
With the Verizon model still having a locked bootloader, is there a possible chance that restoring the stock images from Motorola would allow you past that, or even the bootloader from the same model with a different carrier, this is my only device right now but I would like to test it but can't. Has anyone else thought of this?
Edit: Figured this out... made new post.
Dangerous waters ... and questions
Hi, I own a currently unlocked/rooted XT1524 (LTE/4G) which came with stock rom LXI22.50-24.1 (retde = German retail version).
At the moment I'm running @scritch007's latest rom (cm-12-20150418-UNOFFICIAL-surnia) on it and I'm thrilled to bits that someone made this happen so soon on the device. - Boundless joy, thank you so much.
But now, I'm wondering:
Lucas Eugene said:
[...] 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 oem fb_mode_set
[...]
mfastboot oem config carrier vzw
[...]
Click to expand...
Click to collapse
1. Carrier VZW
What does the "... config carrier vzw" line exactly trigger/do when being applied on an European model?
Isn't VZW = Verizon Wireless?
Shouldn't this line read something like "... config carrier gsm"?
Couldn't we omit this line?
What were the consequences?
2. Risks
After unlocking/rooting I made a TWRP Backup (mfastboot boot <twrp>, didn't touch the original recovery) and also did I dd'ing all partitions living in /dev/block/platform/soc.0/by-name/ via adb root shell.
But regarding the soft-brick issues (oem re-lock) described by @Top_Quark and @squid2 here, I'm not sure (and feeling very uncomfortable with my limited knowledge) if I could re-lock the device without problems without my/any fitting original firmware (which one?). - There is only the one mentioned in the start posting (reteuall but with older LXI22.50-13, same cid 7). - So, can I re-lock my device after a TWRP restore/adb dd ... without flashing the mentioned original signed firmware (euretall)? - Or will I being "surprised" by a nice brick?
Checklist of preconditions to re-lock and go back:
Developer options: active
USB-Debugging: active
Enable OEM unlock: active
TWRP, adb, (m)fastboot set up and working
reteuall firmware: downloaded and at hand (retde firmware still has to show up somewhere yet)
_
Then processing @Lucas Eugene's flashing list
Is this right or am I missing something?
Thank you for your time reading and your replies.
Regards
Hi! I need your help... I bought a moto e xt1524 .... This phone isn't compatible with the frequencies using in Argentina... In my country works the xt1527 version... The question is if I can flash the 1527 firmware in the 1524...
Return to stock - Moto X 2014
What you need:
Minimal ADB and Fastboot
Stock ROM Alternative 1 (Faster option)
Stock ROM Alternative 2 (Downloads speed are super slow if you are not premium)
Moto fastboot (mfastboot.exe) (This one is only needed if the file system.img is too big to flash (More than 500MB))
Steps:
Connect your phone to your computer and make sure to have "USB Debugging" enabled (About phone > Tap several times "Build number" > Go back > Developer options > Enable USB debugging)
Make sure your phone is at least 50% charged
Open ADB cmd (MAF32.exe)
Run this command to make sure it recognizes your phone.
Code:
adb devices
After it recognizes it, run the command (It should reboot into bootloader)
Code:
adb reboot bootloader
Unzip the downloaded STOCK ROM into the same folder as where you installed minimal ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
Open the "flashfile.xml" file with any text editor
The file tells you how to flash the files into your phone
Mine said:
Code:
fastboot oem fb_mode_set oem
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 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
The sistem.img part was a big file divided into 9 files about 250MB each. If your system.img is bigger than 500MB you'll need to use mfastboot.
Do the commands one by one.
After you are done with everything, reboot and it should say in the Status: Official
EDIT 24/04/2016:
- Added faster alternative download to stock ROMS.
Tovagulet said:
Return to stock - Moto X 2014
What you need:
Minimal ADB and Fastboot
Stock ROM (That's the only download page with like all the stock ROMs, downloads speed are super slow if you are not premium)
Moto fastboot (mfastboot.exe) (This one is only needed if the file system.img is too big to flash (More than 500MB))
Steps:
Connect your phone to your computer and make sure to have "USB Debugging" enabled (About phone > Tap several times "Build number" > Go back > Developer options > Enable USB debugging)
Make sure your phone is at least 50% charged
Open ADB cmd (MAF32.exe)
Run this command to make sure it recognizes your phone.
Code:
adb devices
After it recognizes it, run the command (It should reboot into bootloader)
Code:
adb reboot bootloader
Unzip the downloaded STOCK ROM into the same folder as where you installed minimal ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
Open the "flashfile.xml" file with any text editor
The file tells you how to flash the files into your phone
Mine said:
Code:
fastboot oem fb_mode_set oem
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 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
The sistem.img part was a big file divided into 9 files about 250MB each. If your system.img is bigger than 500MB you'll need to use mfastboot.
Do the commands one by one.
After you are done with everything, reboot and it should say in the Status: Official
Click to expand...
Click to collapse
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !
md07 said:
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !
Click to expand...
Click to collapse
Not everybody uses windows. I am a linux user, so no RSDLite is available. Also not available for mac. This guide is great for people who can't use RSDLite or need to do specific steps only instead of blindly trusting RSDLite.
Sent from my XT1095 using Tapatalk
Thanks, I'm also not fond of flashing ROM images via program scripts, I prefer the old step by step method. :thumbup:
Any word on XT1095 or XT1097_retca-retca? How freaken hard is it to capture an OTA or factory image these days?
I still get "Software status: Modified"
md07 said:
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !
Click to expand...
Click to collapse
AGISCI said:
Not everybody uses windows. I am a linux user, so no RSDLite is available. Also not available for mac. This guide is great for people who can't use RSDLite or need to do specific steps only instead of blindly trusting RSDLite.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Also, RSDLite does not work in Windows 10.
Thanks for tutorial.
Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
thomstrack said:
Also, RSDLite does not work in Windows 10.
Click to expand...
Click to collapse
it works with Windows 10... try to upgrate RSD to the latest version
nikky2u20 said:
Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
Click to expand...
Click to collapse
well, it's got all the right words and numbers (although the one I'm running from the TWRP method thread is MPE24.11-18, and this appears to be MPE24.49-18). I'm downloading it now - has anybody else tried it?
niciolaux said:
it works with Windows 10... try to upgrate RSD to the latest version
Click to expand...
Click to collapse
The latest version that I see is the 6.2.4, and does not work in Windows 10.
There is another version?
unfnknblvbl said:
I still get "Software status: Modified"
Click to expand...
Click to collapse
I think "Modified" means you unlocked the bootloader, right?
I used to successfully update my xt1095 to 5.1 by these steps:
unroot by using the uninstalling root function in the SEusers, and flash the stock recovery.img back.
download the OTA update, and let it flash my phone automatically.
got a stock 5.1. then you may do whatever you want.
unfnknblvbl said:
I still get "Software status: Modified"
Click to expand...
Click to collapse
+1
This method don't change to Status Official.
thomstrack said:
Also, RSDLite does not work in Windows 10.
Thanks for tutorial.
Click to expand...
Click to collapse
RSD Lite works perfectly in Windows 10.
I followed these steps, and reflashed to 5.1-21.3, then update to 21.6 (security patch).
Now I'm running 6.0! The OTA works!
We def need to get this stock image re-upped, because I could get gray hairs waiting for this to download... Anyone have any other links? Thanks
help!!! I downloaded the recovery image from the official motorola site, i have system image of 2 Gb and have no idea about how to flash the system image. I have a folder called windows(which was included in the recovery image zip that i downloaded) that folder contains a fastboot.exe file so is that the mfastoot file?If yes then how do i use it?
EDIT- Solved!
nikky2u20 said:
Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
Click to expand...
Click to collapse
unfnknblvbl said:
well, it's got all the right words and numbers (although the one I'm running from the TWRP method thread is MPE24.11-18, and this appears to be MPE24.49-18). I'm downloading it now - has anybody else tried it?
Click to expand...
Click to collapse
Can confirm, this is the real deal. Works a treat, and none of those RPC errors that plagued me on the TWRP backup image.
I am on Brazilian frimware with 6.0 now on my device, but my actual model of the device is xt 1092 Indian version.
I want to go back to Indian frimware. Have anyone tried downgrading from 6.0 Brazilian frimware to 5.1 Indian frimware, is it possible? Is full image of 6.0 out for xt 1092, if so please share the link.
Sent from my XT1097 using Tapatalk
unfnknblvbl said:
Can confirm, this is the real deal. Works a treat, and none of those RPC errors that plagued me on the TWRP backup image.
Click to expand...
Click to collapse
Thnx for the info m8.
Could you upload it to something that is faster then filefactory perhaps? Cause this **** is SLOW
Thnx in advance
Cheers
Edit: it is also available here: https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
With thnx to @salaesp for finding the MU folder
Used this firmware on my MotoX
VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
And was able to get back to the stock state. The Bootloader is still unlocked but that I guess I can lock via OEM lock way?
Since this is the latest one couldn't verify if the OTA works or not.