Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
IMPORTANT NOTICE:
Because there are reports of devices becoming bricked due to downgrading, please disregard this thread and firmware. This is a link to the newly added factory firmware package for the most current build version for the xt1766 SPerry. Please go here:
https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
DISCLAIMER: Please take note that the following stock firmware package is not the official Motorola firmware package, nor is it signed by Motorola. This is a package I have compiled with partition dumps from a pure stock & unmodified Android OS. I have tested this procedure, as have other members, and no adverse issues have arisen upon installing the firmware. However, I am not responsible for devices bricked or otherwise rendered inoperable as a result of installing this firmware or using this guide. You and you alone are responsible for your device. Because this guide does involve fastboot flashing bootloader and other sensitive partitions, follow the instructions to the letter. One mishap while flashing a bootloader partition can leave a device fully inoperable. Also, I have only used this guide on Virgin Mobile variants of the xt1766. It should work on the Sprint and Boost Mobile variants as well, but I cannot personally confirm that at this time.
SPECIFICATIONS:
Hardware SKU: xt1766
Carrier/Provider: Sprint, Virgin Mobile, Boost Mobile
Android Version: 7.1.1 Nougat
Build No. NCQ26.69-64
Radio: M8920_15000.280.06.58.02R
Kernel Version: 3.18.31
Security Patch Level: January 1, 2018
NOTES: This firmware is the most recent version of the stock Android OS. It is completely unmodified.
REQUIREMENTS:
--An unlocked bootloader;
--A PC or laptop running Windows 7 or later;
--Motorola Device Manager: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222;
--Minimal ADB & Fastboot (v1.4.3 or later): https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk;;
--Rudimentary knowledge of fastboot flashing;
--Device charged to at least 60%.
INSTRUCTIONS:
Download the stock firmware package from the link below and save the files in your ADB/Fastboot directory on your PC. Boot your device into fastboot/bootloader mode and connect your device and PC with a suitable data sync cable. Open a command window within the ADB/Fastboot directory and execute the following set of commands:
NOTE: The larger image files (system.img & oem.img) will be automatically dissected into individual sparsechunks and incrementally flashed by fastboot. You will initially receive a "header size" error, but just be patient and wait. Fastboot will resolve this and flash the images.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash aboot aboot.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.img
fastboot flash keymaster keymaster.mbn
fastboot flash oem oem.img
fastboot flash prov prov.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot erase system
fastboot flash system system.img
fastboot erase DDR
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
Now boot your device normally. You should now be updated to the most recent pure stock Android build, and your device will be fully capable of installing future OTA updates.
DOWNLOAD LINK:
LINK HAS BEEN REMOVED: Please go here: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
iykeDROID™ said:
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
Click to expand...
Click to collapse
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
MotoJunkie01 said:
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
Click to expand...
Click to collapse
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Thank you. I sent the thread link and a PM to Az Biker.
Update: The Sperry xt1766 received an OTA update today for minor bug fixes, stability improvements, and security patches for March 1, 2018. The OTA is Bkur_Version 26.11.68.sperry_sprint.en.US. I will be updating this thread to the new build updated by the OTA. In the meantime, should you wish to revert to pure stock and install the OTA update package, the above fastboot firmware package will put your xt1766 in a pure stock state, and thus capable of installing the OTA update. NOTE: Many people skip recovery.img in order to retain TWRP custom recovery. Here, flashing stock recovery is necessary in order to successfully install the OTA update package.
iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Hey friend, thanks again for pointing out my oversight. Moderator Az Biker helped me out and moved the thread.
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
MotoJunkie01 said:
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
Click to expand...
Click to collapse
Rock on bro! Good luck.
Hard brick
My device is bricked flashing update on custom rom AICP
Please help
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
Hard brick
My device is bricked flashing update on custom rom AICP
Please help
Restore in emergency mode
Greetings.
I would like your help to restore a MOTO E4 XT1766. It does not start with fastboot, because the bootloader is corrupt. The phone connects in emergency mode. I need the file "prog_emmc_firehose_8920.mbn" to be able to restore it. Any idea where I can find it?
error cannot load gpt.bin
I have my phone in fastboot/bootloader mode. Should I be in recovery? I can run the command "fastboot oem fb_mode_set" but I cant run the command "fastboot flash partition gpt.bin" I get "error cannot load gpt.bin". Moto E4 XT1766 Qualcomm any help?
Edit: I am sure I have the files in the same folder as adb and fastboot.
UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry bricked my phone
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
[email protected] said:
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
Click to expand...
Click to collapse
Nope its dead u flash bootloader partitions that were older then your current version that edl'd you're phone
MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
Thanks man, worked perfectly.
Got some errors along the way, which I ignored (permissions on Erase Data, etc).
MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
resarfekim said:
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
Click to expand...
Click to collapse
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
madbat99 said:
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
resarfekim said:
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
Click to expand...
Click to collapse
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
madbat99 said:
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
Click to expand...
Click to collapse
I was originally rooted, but after running the commands in this OP, I did nothing else.
I did save the results of all the Fastboot commands, please see below. A couple commands toward the end gave errors.
______________________________________________
E:\Phone\E4\Factory_restore_image>fastboot devices
ZY224PTXGW fastboot
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.125s]
finished. total time: 0.140s
E:\Phone\E4\Factory_restore_image>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.655s]
finished. total time: 1.186s
E:\Phone\E4\Factory_restore_image> fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 1.970s]
finished. total time: 2.517s
E:\Phone\E4\Factory_restore_image> fastboot flash aboot aboot.mbn
(bootloader) has-slot:aboot: not found
target reported max download size of 536870912 bytes
sending 'aboot' (1536 KB)...
OKAY [ 0.047s]
writing 'aboot'...
OKAY [ 0.203s]
finished. total time: 0.265s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib cmnlib.mbn
(bootloader) has-slot:cmnlib: not found
target reported max download size of 536870912 bytes
sending 'cmnlib' (251 KB)...
OKAY [ 0.001s]
writing 'cmnlib'...
OKAY [ 0.078s]
finished. total time: 0.079s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib64 cmnlib64.mbn
(bootloader) has-slot:cmnlib64: not found
target reported max download size of 536870912 bytes
sending 'cmnlib64' (251 KB)...
OKAY [ 0.016s]
writing 'cmnlib64'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash devcfg devcfg.mbn
(bootloader) has-slot:devcfg: not found
target reported max download size of 536870912 bytes
sending 'devcfg' (128 KB)...
OKAY [ 0.016s]
writing 'devcfg'...
OKAY [ 0.062s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image> fastboot flash dsp dsp.img
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp'...
OKAY [ 1.686s]
finished. total time: 2.217s
E:\Phone\E4\Factory_restore_image>fastboot flash modem modem.img
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (102400 KB)...
OKAY [ 3.247s]
writing 'modem'...
OKAY [ 4.921s]
finished. total time: 8.168s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image> fastboot flash fsg fsg.img
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (8192 KB)...
OKAY [ 0.266s]
writing 'fsg'...
OKAY [ 2.795s]
finished. total time: 3.062s
E:\Phone\E4\Factory_restore_image>fastboot flash keymaster keymaster.mbn
(bootloader) has-slot:keymaster: not found
target reported max download size of 536870912 bytes
sending 'keymaster' (251 KB)...
OKAY [ 0.016s]
writing 'keymaster'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash oem oem.img
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'oem' 1/2 (507490 KB)...
OKAY [ 17.457s]
writing 'oem' 1/2...
OKAY [ 28.001s]
sending sparse 'oem' 2/2 (59511 KB)...
OKAY [ 2.081s]
writing 'oem' 2/2...
OKAY [ 6.231s]
finished. total time: 53.804s
E:\Phone\E4\Factory_restore_image> fastboot flash prov prov.mbn
(bootloader) has-slotrov: not found
target reported max download size of 536870912 bytes
sending 'prov' (187 KB)...
OKAY [ 0.016s]
writing 'prov'...
OKAY [ 0.062s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image>fastboot flash rpm rpm.mbn
(bootloader) has-slot:rpm: not found
target reported max download size of 536870912 bytes
sending 'rpm' (256 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash sbl1 sbl1.mbn
(bootloader) has-slot:sbl1: not found
target reported max download size of 536870912 bytes
sending 'sbl1' (507 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.047s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image> fastboot flash tz tz.mbn
(bootloader) has-slot:tz: not found
target reported max download size of 536870912 bytes
sending 'tz' (1792 KB)...
OKAY [ 0.062s]
writing 'tz'...
OKAY [ 0.265s]
finished. total time: 0.328s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image> fastboot flash system system.img
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/5 (509553 KB)...
OKAY [ 17.319s]
writing 'system' 1/5...
OKAY [ 12.350s]
sending sparse 'system' 2/5 (523636 KB)...
OKAY [ 17.753s]
writing 'system' 2/5...
OKAY [ 11.928s]
sending sparse 'system' 3/5 (519086 KB)...
OKAY [ 17.869s]
writing 'system' 3/5...
OKAY [ 11.983s]
sending sparse 'system' 4/5 (521399 KB)...
OKAY [ 17.949s]
writing 'system' 4/5...
OKAY [ 20.356s]
sending sparse 'system' 5/5 (411602 KB)...
OKAY [ 14.302s]
writing 'system' 5/5...
OKAY [ 35.077s]
finished. total time: 176.895s
E:\Phone\E4\Factory_restore_image> fastboot erase DDR
(bootloader) has-slotDR: not found
erasing 'DDR'...
OKAY [ 0.000s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 1.267s]
finished. total time: 1.267s
E:\Phone\E4\Factory_restore_image>fastboot erase cache
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>
Related
Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck
Reserved
reserved...:cyclops:
Mkdon said:
Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck
Click to expand...
Click to collapse
worked!!!!!!!!
you sir... are a legend!!!!!!!!!
thank you so much!!!!
flowerpoweruk said:
worked!!!!!!!!
you sir... are a legend!!!!!!!!!
thank you so much!!!!
Click to expand...
Click to collapse
I am glad it helped you. Enjoy the amazing device.
my phone german retail. can i use this tutorial?
sinkadorable said:
my phone german retail. can i use this tutorial?
Click to expand...
Click to collapse
I think so. Just give a shot. if it doesnt work then just replace the stock firmware from GB to DE. Alles Beste!
it gives me the same as the original method " < waiting for device > "
i have made a full swipe to the phone, cleaned the previous custom rom already, and a have cwm recovery.. dont know if this info is important
DONE!! i havent put the adb files in the firmware folder, but has flashed flawlessly now!! thank you for this solution!! :good:
Xin_TiGeR said:
it gives me the same as the original method " < waiting for device > "
i have made a full swipe to the phone, cleaned the previous custom rom already, and a have cwm recovery.. dont know if this info is important
Click to expand...
Click to collapse
What would you like to achieve? / is your Moto G stuck in loop after factory reset? Give a full background about the issue
Thank you.It works.Excellent.
Mkdon said:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
Click to expand...
Click to collapse
What is meant by this ? what exactly am I removing ? Do I need to rename it to the firmware I am about to flash?
Cheers.
EDIT: I figured it out, I just had a noob moment in my despair and couldn't take the information in, What a difference some nicotine and a cuppa makes!
Thanks OP great work.
Mkdon said:
Hello Folks:
This comes after a bit of struggle to get this Moto G XT1132 Retail version to stock. For some weird reason the phone refused to boot after factory wipe via CWM..That shouldn't have happened in the first case. But **** happens and that's XDA helps the troubled users. There is still shortage of complete toolkits with full features around for Moto G not privileged like Nexus 4 or Nexus 5 yet..
Symptoms :
1. Moto G refuse to start and STUCK at boot / bootloop.
2. Normal fastboot commands upsets you by not flashing system.img or any other stock firmware files.
Solution:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
2. Get your firmware from here : http://sbf.droid-developers.org/phone.php?device=14
3. Download the flash.txt file from this post rename it to flash.bat (its very important) put this in the extracted folder of your firmware.
4. Copy all the fastboot files in the extracted firmware folder along with the flash.bat
5. Rename the fastboot.exe to > fastboot-moto-windows.exe
6. Put your Moto G to bootloader mode
7. Click on the flash.bat file which is in the firmware extracted folder. It will do its stuff and may take few seconds. When the script stops just reboot the phone. And you are back to stock with no bootloop.
NOTE: You are on your own. I take no responsibility for any device getting bricked or whatsoever.
I take NO Credit for this and I have just gathered this information from various forums including XDA. I have just tried to put them at one place to make it Frustration Free...
If I helped you Hit the Thanks button down there...
I specially thank tillaz for the batch file which is a key tool to fix the mess
Good Luck
Click to expand...
Click to collapse
help me guys
2 days back I was using my fone and it juz went off blank screen. tried many times with power button bt nothing. den went it to fastboot mode and tried recovery/normal powerup/factory but everytime got msg "failed to validate system image". followed d procedure given here http://forum.xda-developers.com/showthread.php?t=2700502 and got this result
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd..
C:\Windows>cd..
C:\>g:
G:\>cd moto g
G:\moto g>mfastboot.exe oem lock begin
...
(bootloader) Device is already locked!
OKAY [ 0.014s]
finished. total time: 0.016s
G:\moto g>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.001s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.396s
G:\moto g>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 5.112s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash tz
FAILED (remote failure)
finished. total time: 11.343s
G:\moto g>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 5.059s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.084s
G:\moto g>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 5.554s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 11.077s
G:\moto g>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 5.532s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 11.061s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [ 19.204s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 33.653s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (237949 KB)...
OKAY [ 17.387s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 25.518s
G:\moto g>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (243326 KB)...
OKAY [ 18.015s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 34.875s
G:\moto g>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47476 KB)...
OKAY [ 7.540s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 12.576s
G:\moto g>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.987s
G:\moto g>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
G:\moto g>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 5.056s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 10.090s
G:\moto g>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.990s
G:\moto g>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.995s
G:\moto g>mfastboot.exe oem lock
...
(bootloader) Device is already locked!
OKAY [ 0.012s]
finished. total time: 0.015s
G:\moto g>pause
Press any key to continue . .
any solution guys
Don't you need to be unlocked to flash it?
Sent from my XT1032 using XDA Free mobile app
feartheanonymity said:
Don't you need to be unlocked to flash it?
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
does unlocking void the warranty?
yasir1234 said:
does unlocking void the warranty?
Click to expand...
Click to collapse
Yes, However you can flash to stock and just relock the bootloader and warranty is back intact.
26286998 5107
feartheanonymity said:
Yes, However you can flash to stock and just relock the bootloader and warranty is back intact.
Click to expand...
Click to collapse
how do I do dat?can u pls give me steps to do so..
well there are many threads explaining how to unlock bootloader, It basically consists of getting a code through adb, putting that code onto motorola website, getting the code and sending it to the phone. check the guides in the general section.
as for relocking it, is as simple as going into fastboot and typing (in adb / fastboot) fastboot oem lock.
Moto G Stuck in Boot Loop! Help
When I flash the stock firmware I keep getting these error messages
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
(bootloader) Failed to validate sparse image
and these all end with
FAILED (remote failure)
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.448s]
finished. total time: 0.486s
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.490s]
finished. total time: 1.603s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.361s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.915s
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.372s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.948s
target reported max download size of 536870912 bytes
sending 'system' (260606 KB)...
OKAY [ 8.415s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.950s
target reported max download size of 536870912 bytes
sending 'system' (239692 KB)...
OKAY [ 7.770s]
writing 'system'...
OKAY [ 9.293s]
finished. total time: 17.065s
target reported max download size of 536870912 bytes
sending 'system' (222205 KB)...
OKAY [ 7.165s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.684s
target reported max download size of 536870912 bytes
sending 'modem' (47484 KB)...
OKAY [ 1.583s]
writing 'modem'...
OKAY [ 1.304s]
finished. total time: 2.890s
erasing 'modemst1'...
OKAY [ 0.066s]
finished. total time: 0.067s
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.068s
target reported max download size of 536870912 bytes
sending 'fsg' (721 KB)...
OKAY [ 0.125s]
writing 'fsg'...
OKAY [ 0.104s]
finished. total time: 0.231s
erasing 'cache'...
OKAY [ 0.362s]
finished. total time: 0.364s
erasing 'userdata'...
OKAY [ 2.560s]
finished. total time: 2.562s
I have tried to flash many different firmwares on it to get it out of the boot loop like "US Retail" (4.3 and 4.4.2), "Boost US" (4.3 and 4.4.2), and "Verizon US" (4.3 and 4.4.2). This always results in one of the 3 error messages or more. I have found the one that works with the least error messages is the Boost US firmware for 4.4.2 and it gives only the error message (bootloader) Failed to validate sparse image on the 3rd system file. Whenever I try to install the firmware it doesn't seem to work, and it results in the phone turning on with the Motorola logo then the phone vibrates once then turns off and repeats, or the phone shows the android logo on its back with the exclamation point after the single vibration and sits like that until it turns off a few minutes later repeating the process. I have tried everything including trying to boot normally, resetting to factory, going into recovery and wiping cache and deleting all data, and even attempting to install from ADB. I have actually successfully done this process before a few hours before trying it on this one where it ended up like this. I looked this up and apparently you can still fix the phone if it can reach the boot loader screen, but when I was working with the phone I forgot to put it in developer mode and turn on USB debugging so that might be an issue. If there is a way I could fix it that would be very helpful, but if it doesn't I can still return the phone in the next 4 days.
Thanks for the help!
Extra Info:
The phone's bootloader is locked and because it is new I do not have any backups.
Also I already have these following programs
Minimal ADB and Fastboot
RSD Lite
DFS
Mfastboot v2
r1-motog-modifiedrecoveryroot.zip
adt-bundle-windows-x86_64-20140321.zip
platform-tools.zip
Fastboot+ADB(20926).zip
adbfix.zip
These are all from other threads that have explained this issue but the fix they provided did not work.
Thanks Again!
Guys, I have a Moto-G that was sold to me as a XT-1032 US global GSM model. The guy who sold it to me said that after the OTA update for 4.4.2 was applied to his phone it never would see a signal again, and kept saying to turn off airplane even though it saw that a sim was installed. looking at the status it kept saying the radio was turned off. When I got it from him it was showing the unlocked bootloader message, but when I checked the status on the fastboot screen it was showing locked status 2, which indicates it had never been unlocked. I unlocked the bootloader and started trying different versions of the firmware to see if I could fix the issue, but nothing ever worked until I tried this method.
I only flashed the radio from the GB 4.4.2 version that the OP had provided the XML file for using the modified xml file he provided, and now my cell radio is working again. Since I had already voided any warranty on it, I went ahead with flashing the CWM recovery and the latest nightly for CM11 and it's working beautifully, very smooth. I had bought this for my wife if I could fix it, so now she's getting a nice upgrade from her old GSM galaxy nexus that had started developing issues where it had to be rebooted to get the radio to work again (on the stock 4.3 firmware mind you, just a hardware problem I think due to it's age)
So in short Thanks OP!!
Mkdon said:
1. Edit the RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.txt (its an xml file though) as attached with this post.(You just need to remove one line from the top; don't worry if your .xml looks different from this one; as I have taken this as an example)
Click to expand...
Click to collapse
Thanks for posting this since my phone is having these exact issues! I was a little unsure of what you meant in step 1 above, so what I did is take the sample XML which you attached to the post and replaced the software version info in the header with the version information for my carrier's firmware. Not sure if that was what I was supposed to do. Anyway, everything works great except that it is failing to flash motoboot.img. The command windows says it's a remote error- preflash validation failed, and the phone displays an error that says the version has been downgraded for tz. Any ideas would be greatly appreciated!
MORE INFO: I would like to add that my bootloader is 41.19 and that bootloader/fastboot and recovery works ok. Only when I try to start system, it ends at BOOTLOADER UNLOCKED. I tried 4.4.4, 5.0.2 and 5.1 ... and none of them works ... And in TWRP, I can see "Unable to mount /cache" and "Unable to mount /system" ...
Hi, Ive got a problem:
Ive been using the stock DE 4.4.4. ROM + 5.0.2 OTA on my XT1032 fine for about six weeks. Today I wanted to lock it, so I
1) entered "sudo fastboot oem lock begin" (Im on Linux Mint btw)
2) flashed the DE 4.4.4 ... and the phone just doesnt boot to system; there is the WARNING BOOTLOADER UNLOCKED message and thats it.
The bootloader is still unlocked of course. And I dont think the problem is related to the locking ...
These are the commands I used (they are just from the DE 4.4.4 ROM):
Code:
sudo fastboot flash partition gpt.bin
sudo fastboot flash motoboot motoboot.img
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot reboot
And this is the output
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.027s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.305s
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.096s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.365s
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.077s]
writing 'logo'...
OKAY [ 0.131s]
finished. total time: 0.208s
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.372s]
writing 'boot'...
OKAY [ 0.794s]
finished. total time: 1.166s
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.375s]
writing 'recovery'...
OKAY [ 0.770s]
finished. total time: 1.146s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.639s]
sending 'system' (255397 KB)...
OKAY [ 8.085s]
writing 'system'...
OKAY [ 12.824s]
finished. total time: 21.548s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.576s]
sending 'system' (254868 KB)...
OKAY [ 8.054s]
writing 'system'...
OKAY [ 10.562s]
finished. total time: 19.192s
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.608s]
sending 'system' (231159 KB)...
OKAY [ 7.294s]
writing 'system'...
OKAY [ 19.144s]
finished. total time: 27.046s
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.527s]
writing 'modem'...
OKAY [ 1.407s]
finished. total time: 2.934s
erasing 'modemst1'...
OKAY [ 0.065s]
finished. total time: 0.065s
erasing 'modemst2'...
OKAY [ 0.065s]
finished. total time: 0.065s
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.081s]
writing 'fsg'...
OKAY [ 5.611s]
finished. total time: 5.693s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.415s]
finished. total time: 0.415s
erasing 'userdata'...
OKAY [ 6.911s]
finished. total time: 6.911s
rebooting...
finished. total time: 0.001s
And when I try to sideload the OTA phone says "Installation aborted" ...
Im using the same files I used six weeks ago.
I tried EU 4.4.4 but it is not working either - theres only Motorola logo and thats it.
Any suggestions, please?
The gpt.bin and motoboot files won't flash because you are trying to downgrade both versions which cannot be done.
There is no need to lock the bootloader to flash stock 4.4.4 or take the OTA update.
Alright, my not-so-perfect yet-working solution.
I flashed TWRP. In the recovery (wipe-advanced-repair or format) I realized that all the partitions (system, cache, data) are corrupted and showing size zero. So I formatted all of them to ext4 and (just to be sure) ran REPAIR.
After repairing the partitions I enabled MTP - it didnt show in my PC, but reboot helped - and copied GPE 5.1 Untouched (http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) into the storage. Then, I installed the ROM in TWRP and rebooted - dont let the recovery install SU, it ended in loopback (during first boot only: after successfully entering my google information and rebooting into recovery, I let it install SuperSU and it worked fine).
Voila, phone working again.
I checked the process once again and it worked. But when I try to flash anything now, partitions get corrupted. Weird.
audit13 said:
There is no need to lock the bootloader to flash stock 4.4.4 or take the OTA update.
Click to expand...
Click to collapse
I know, but I was going to sell the phone and I hoped relocking would make the Warning Bootloader Unlocked sign go away. Later, I read it doesnt - too bad.
But generally I'm quite satisfied now - the phone has a newer system, no Bootloader Warning, it has Czech language now and the new user is a total newbie so Im glad that (thanks to the TWRP) she wont lose her internal storage files when doing factory reset.
UPDATE: I flashed stock recovery (Brazilian 5.0.2) to make Factory reset be able to format even the /media/data partition, as was intended. Just to make sure the partition can be wiped in case of trouble. GPE 5.1 recovery didnt work btw.
sorry people, may be yo´ve heard about but if you know about the mbm-ci5 files needed to un hard brick a moto g ??? do you thing there is a hope o may be other methods to unbrick a moto g xt 1032 - sorry if its not the right place, just looking for help to revive mines...
Hi there!
Before I flashed these I had 5.1.1 Retail UK stock, rooted, xposed installed with gravitybox, disabled the softkeys with the build.prop command & turned the volume up with rx_mixerpaths
I downloaded XT1541_OSPREY_RETGB_5.1.1_LPI23.72-47_cid7_subsidy-DEFAULT_CFC.xml.zip from this thread & used this guide http://forum.xda-developers.com/2015...ctory-t3187750 to flash the phone to complete stock before I pass it down the family.
Upon booting it won't turn on the WiFi, I try to turn it on & it flicks off straight away. I had a quick search & came across this thread http://forum.xda-developers.com/moto...tooth-t2813308 I have checked the /persist folder & its empty unlike those guys in that thread.
I was wondering if someone could be generous enough to share these files with me? Unless there is another way to get the WiFi working again?
Many many thanks!
Below is a copy of the fastboot commands.
C:\adb>fastboot devices
ZY2223RTMH fastboot
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.713s]
finished. total time: 0.720s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.085s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.596s]
finished. total time: 1.683s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.033s]
writing 'logo'...
OKAY [ 0.074s]
finished. total time: 0.108s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.524s]
writing 'recovery'...
OKAY [ 0.446s]
finished. total time: 0.971s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 8.236s]
writing 'system'...
OKAY [ 6.949s]
finished. total time: 15.187s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 8.223s]
writing 'system'...
OKAY [ 6.777s]
finished. total time: 15.003s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (232608 KB)...
OKAY [ 7.297s]
writing 'system'...
OKAY [ 6.221s]
finished. total time: 13.519s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (233343 KB)...
OKAY [ 7.332s]
writing 'system'...
OKAY [ 6.012s]
finished. total time: 13.348s
C:\adb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (257130 KB)...
OKAY [ 8.067s]
writing 'system'...
OKAY [ 6.554s]
finished. total time: 14.623s
C:\adb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (228585 KB)...
OKAY [ 7.171s]
writing 'system'...
OKAY [ 5.850s]
finished. total time: 13.024s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36940 KB)...
OKAY [ 1.165s]
writing 'modem'...
OKAY [ 1.006s]
finished. total time: 2.172s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2031 KB)...
OKAY [ 0.068s]
writing 'fsg'...
OKAY [ 0.081s]
finished. total time: 0.151s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.019s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.795s]
finished. total time: 0.796s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.007s
I had the exact same problem when trying to flash the generic Canadian firmware. I flashed three times to no avail. Then I downloaded and flashed a carrier-specific version of the Canadian firmware and suddenly wifi worked.
Sevael said:
I had the exact same problem when trying to flash the generic Canadian firmware. I flashed three times to no avail. Then I downloaded and flashed a carrier-specific version of the Canadian firmware and suddenly wifi worked.
Click to expand...
Click to collapse
Any chance you'd be able to share your files in /persist folder if you are rooted?
I think this will sort it. The phone was a simfree one I don't really want to flash carrier-specific software if possible.
Powereh said:
I think this will sort it. The phone was a simfree one I don't really want to flash carrier-specific software if possible.
Click to expand...
Click to collapse
The carrier-specific one won't lock your phone or put any bloatware on it. It's simply one that was taken from a phone that somebody bought from that carrier. The one I used was from a different carrier than the one I bought the phone from originally.
Powereh said:
Any chance you'd be able to share your files in /persist folder if you are rooted?
Click to expand...
Click to collapse
I can't from where I am right now. Hopefully you can find someone who can upload it, otherwise I recommend giving a different firmware download a try.
Here ya go, keep in mind this is from XT1540 Canadian retail.
https://drive.google.com/file/d/0B4Gyz91x5k7gdUoxQUtldEZ3Wmc/view?usp=docslist_api
Sent from my MotoG3 using XDA Free mobile app
Cheers for the help guys, I will try those files out once i get home from work later.
I'll let you know the outcome in due course.
christopherrrg said:
Here ya go, keep in mind this is from XT1540 Canadian retail.
https://drive.google.com/file/d/0B4Gyz91x5k7gdUoxQUtldEZ3Wmc/view?usp=docslist_api
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
OK tried your files & it just keeps force closing every thing upon boot an endless amount.
I think I need XT1541 specific files.
Thank you so much for taking the time to upload those though! I really appreciate it.
Fixed it I had to flash this one instead Retail Great Britain (1GB) - XT1541_OSPREY_RETGB_5.1.1_LPI23.72-22_cid7
Cheers for the guys who tried to help
Powereh said:
Fixed it I had to flash this one instead Retail Great Britain (1GB) - XT1541_OSPREY_RETGB_5.1.1_LPI23.72-22_cid7
Cheers for the guys who tried to help
Click to expand...
Click to collapse
Glad you're back up! Change thread to solved in case passer bys need the information.
Sent from my MotoG3 using XDA Free mobile app
christopherrrg said:
Glad you're back up! Change thread to solved in case passer bys need the information.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think the issue is solved, he just returned to the previous factory image, I'm having the same issue with the US model. I posted in the factory image thread on general and I'm not the only one
at least for some people if you try to upgrade via fastboot, wifi is broken
sgloki77 said:
I don't think the issue is solved, he just returned to the previous factory image, I'm having the same issue with the US model. I posted in the factory image thread on general and I'm not the only one
at least for some people if you try to upgrade via fastboot, wifi is broken
Click to expand...
Click to collapse
Agreed - I have this problem as well. I've searched through the threads, but haven't found a solution yet.
cdluck said:
Agreed - I have this problem as well. I've searched through the threads, but haven't found a solution yet.
Click to expand...
Click to collapse
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'll try that, thanks - is flashing back to the original factory image the same process, just with a different zip (e.g. XT1540_OSPREY_RETUS_2GB_5.1.1_LPI23.72-44_cid9_subsidy-DEFAULT_CFC)?
Also, this wifi thing is weird - I was able to connect to my home wifi without issue, but my work wifi causes the shutdown problem (if I try to fiddle with it and get it to connect, it just crashes and reboots the phone).
cdluck said:
I'll try that, thanks - is flashing back to the original factory image the same process, just with a different zip (e.g. XT1540_OSPREY_RETUS_2GB_5.1.1_LPI23.72-44_cid9_subsidy-DEFAULT_CFC)?
Also, this wifi thing is weird - I was able to connect to my home wifi without issue, but my work wifi causes the shutdown problem (if I try to fiddle with it and get it to connect, it just crashes and reboots the phone).
Click to expand...
Click to collapse
no man [emoji33] that one you quoted is the bad apple, when I said "original" I meant the one your phone shipped with(16.3)
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
no man [emoji33] that one you quoted is the bad apple, when I said "original" I meant the one your phone shipped with(16.3)
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My mistake, I copied the name from the wrong file - thanks for catching that for me!
sgloki77 said:
you need to flash back to the original factory image and then take the OTA , do NOT try to upgrade directly with the latest factory image, or you will find yourself in brick city
Click to expand...
Click to collapse
:crying: really!?, I was thinking about update directly with latest firmware to avoid OTA
El_Nuevo said:
:crying: really!?, I was thinking about update directly with latest firmware to avoid OTA
Click to expand...
Click to collapse
by my experience
-flashing 16.3 image was ok,
-flashing 44 image (I only flashed system and radio) resulted in broken wifi
by other users' experiences I read
-flashing 44 image(all partitions) resulted in a brick
-flashing 47 image was ok at least by one user
my device is XT1540 US 1GB RAM at this point I would suggest you research your particular model/factory images compatible with your model and decide for yourself what factory image to flash, there's been a few bricks already so beware of dragons...
Deal all Great and Senior Devs specially @lost101 need yours extrem help
i was on rr rom 5.1 and later after that i have flash Stock Factory Firmware Image of same model via Fastboot
i was successfully booted and also received the MM update so i had downloaded it and install it after final step to reboot i was stuck on unlock boot loader warring image so after seeing many threads i have flashed Stock MM Factory Firmware Image of same model via Fastboot as i wanted to sell this phone so i have tried to relock the boot loader so i have tried
fastboot oem lock begin
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
all the commands was showing okay while flashing
also boot loader got locked on final fastboot reboot i stuck on boot loop :crying:
and now I can only get into Fastboot mode .but I can't flash anything because the bootloader is locked. and I can't unlock the bootloader because I can't toggle the stupid "Allow OEM Unlock" setting.
please don't tell to visit service center its boot loop image showing unlock boot loader warning
pls help all great devs if their is any solution
thanks in advace
Stop with all locking. You cannot undo Bootloader unlock, period. Do not use any lock commands. Begin again, this time with: fastboot oem unlock
It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
thanks @lost101 for the reply sir
but as in locked boot loader status code 2
all comments were flashing successfully but in the end on final reboot its stuck on boot loader warning logo again screen goes off again boot loader warning logo comes this process repeats
also i am not able to boot into stock recovery which agains open boot loader
following are the commands
C:\Users\Bhupesh\Desktop\Moto>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.733s]
finished. total time: 0.749s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.624s]
finished. total time: 1.718s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.047s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.156s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.562s]
writing 'boot'...
OKAY [ 0.938s]
finished. total time: 1.500s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 1.515s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.713s]
writing 'system'...
OKAY [ 11.861s]
finished. total time: 20.574s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (245933 KB)...
OKAY [ 8.190s]
writing 'system'...
OKAY [ 7.958s]
finished. total time: 16.164s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (249279 KB)...
OKAY [ 8.300s]
writing 'system'...
OKAY [ 7.769s]
finished. total time: 16.069s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.726s]
writing 'system'...
OKAY [ 9.734s]
finished. total time: 18.461s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (63875 KB)...
OKAY [ 2.150s]
writing 'system'...
OKAY [ 11.283s]
finished. total time: 13.436s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.237s]
writing 'modem'...
OKAY [ 1.056s]
finished. total time: 2.298s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.010s]
finished. total time: 0.020s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2159 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.172s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Users\Bhupesh\Desktop\Moto>fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.973s]
finished. total time: 3.976s
C:\Users\Bhupesh\Desktop\Moto>fastboot reboot
rebooting...
finished. total time: 0.008s
C:\Users\Bhupesh\Desktop\Moto>
also while
C:\Users\Bhupesh\Desktop\Moto>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.017s
thanks in advance
This is one of the reasons why it's important to unlock Bootloader. You are totally stuck as far as I can see. You have no choice but phone to return to Manufacturer.
EDIT: One possibility might be to flash the 5.1.1 Firmware (skipping bootloader.img) and if that does not boot to Android, then apply the MM OTA Update via Stock Recovery.
lost101 said:
This is one of the reasons why it's important to unlock Bootloader. You are totally stuck as far as I can see. You have no choice but phone to return to Manufacturer.
EDIT: One possibility might be to flash the 5.1.1 Firmware (skipping bootloader.img) and if that does not boot to Android, then apply the MM OTA Update via Stock Recovery.
Click to expand...
Click to collapse
thanks @lost101 for the reply again
its seems I am getting the failure message
"version downgrade for system"
"Invalid PIV signed system image "
C:\Users\Bhupesh\Desktop\Moto>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.421s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.156s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.281s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.702s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.357s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.718s]
writing 'recovery'...
OKAY [ 1.030s]
finished. total time: 1.763s
C:\Users\Bhupesh\Desktop\Moto>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (232264 KB)...
OKAY [ 7.769s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.424s
C:\Users\Bhupesh\Desktop\Moto>
also while using MM Factory Firmware Images before which was getting successfully flashed i was still not able to boot on stcok recovery with boot loop
i have done almost googleing abt this issue
and i bet u are the only who can make my device normal
thanks in advance
Try using RSD lite as described here by @thinkfreedom:
http://forum.xda-developers.com/showpost.php?p=64844324&postcount=275
Not i my case waited for 20-30 minute
Dear @lost101 pls help
Not i my case
I followed each steps All file were getting flash ok
Finally waiting for 20-30 minute the screen is still on off then stiching to boot loader repeating no change :crying:
please help @lost101
I'm having a similar problem, locked bootloader on bell Canada lollipop, tried to Flash US. Retail marshmallow, worked up until boot.Img now I'm stuck in fastboot and if I try to boot into recovery it just loops,can't flash twrp. . Can't unlock bootloader because of OEM Uncheck in developer option is not checked! No official marshmallow for bell yet..... Do you think MM 6.0 will flash when available?
tmmcbots said:
I'm having a similar problem, locked bootloader on bell Canada lollipop, tried to Flash US. Retail marshmallow, worked up until boot.Img now I'm stuck in fastboot and if I try to boot into recovery it just loops,can't flash twrp. . Can't unlock bootloader because of OEM Uncheck in developer option is not checked! No official marshmallow for bell yet..... Do you think MM 6.0 will flash when available?
Click to expand...
Click to collapse
yes i can via RSD Lite 6.2.4 try https://getmovil.com/motorola/moto-g-2015-android-5-1-1-lollipop/
hope u get booted
bhu999 said:
Dear @lost101 pls help
Not i my case
I followed each steps All file were getting flash ok
Finally waiting for 20-30 minute the screen is still on off then stiching to boot loader repeating no change :crying:
please help @lost101
Click to expand...
Click to collapse
Try flashing TWRP and than any custom rom i think CM13 will be better....U have tried so much so at least u can have shoot on this step...
Sent from my Toilet using Moto G3....
cant flash twrp with locked boot loader
its says Invalid partion size
bhu999 said:
cant flash twrp with locked boot loader
its says Invalid partion size
Click to expand...
Click to collapse
If you are in warranty just go to service center.. They will flash firmware.. Don't tell them you have previously unlocked boatloader.. They are just mad.. They even won't ask for money if you are in warranty period.. These guys are not aware of bootloader is previously unlocked or not.. That's the last option..
Sent from my Moto G(Osprey)
My phone just suddenly get bricked, I'm do not do anything before,not root ,not unlock bootloader ,not flash third-party roms.
I'm only update from ota (from 4.4 to 5.0 and 5.0 to 5.1), just the offical method to update.
now,i come here to find the way and get my phone back .
the situation now is unlocked bootloader (bootloader version :41.1A)
and try to flash stock rom XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
i just follow the guide in forum ,but get a trouble like that:
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash pa
rtition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.333s]
finished. total time: 0.375s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash mo
toboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.112s]
finished. total time: 1.232s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash lo
go logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.101s]
finished. total time: 0.173s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash bo
ot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.379s]
writing 'boot'...
OKAY [ 0.776s]
finished. total time: 1.166s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash re
covery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.392s]
writing 'recovery'...
OKAY [ 0.767s]
finished. total time: 1.171s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash sy
stem system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.318s]
writing 'system'...
OKAY [ 12.417s]
finished. total time: 20.747s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash sy
stem system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256949 KB)...
OKAY [ 8.258s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 29.086s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
I have try many times but still cant flash the sysem system.img_sparsechunk.1,
but i can flash the part system.img_sparsechunk.0
Does any one know what is my problem?(or my phone is already dead.)
PS: I'm sorry about that my english is not good,if anything wrong or can not understanding,please ask me.
thanks everyone.
Maybe that sparsechunk did not extract fully from the zip. Re-extract, or download the entire zip again.
lost101 said:
Maybe that sparsechunk did not extract fully from the zip. Re-extract, or download the entire zip again.
Click to expand...
Click to collapse
First, thanks to your suggestion.
I just re-download the roms from the different websites
then use 7 zip to extract the both file and try again ,still get the same result as i say that on the topic.
BY the way ,thank you for your suggestion.
Try an 'external' factory reset via Stock Recovery:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
lost101 said:
Try an 'external' factory reset via Stock Recovery:
motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
Click to expand...
Click to collapse
thanks your suggestion
i just follow the guide of the website,but i get the problem in step 4, i can see the Android figure lying on his back,but my screen continue twinkling ,after i press and hold the Power button then press and release the Volume Up button, the phone come back to the fastboot screen.
Is that root the phone can get help?
More: I'm use the 16GB version xt1033 ,is that wrong gpt.bin in rom?
tom0079 said:
i just follow the guide of the website,but i get the problem in step 4, i can see the Android figure lying on his back,but my screen continue twinkling ,after i press and hold the Power button then press and release the Volume Up button, the phone come back to the fastboot screen.
Click to expand...
Click to collapse
Keep trying, you should be able to enter recovery mode. The instructions are press and hold Vol up, then tap Power button - not what you describe.
lost101 said:
Keep trying, you should be able to enter recovery mode. The instructions are press and hold Vol up, then tap Power button - not what you describe.
Click to expand...
Click to collapse
After that ,i try several methods, and do some stupid things and relock the bootloader,
i can't flash any part of the roms now,is there any way to unlock the bootloader again?
(P.S. the status in fastboot mode still show up unlock)
mfastboot oem unlock
lost101 said:
mfastboot oem unlock
Click to expand...
Click to collapse
It's not work!
http://forum.xda-developers.com/moto-g/help/guide-root-xt1032-xt1033-moto-g-running-t2965507
i have done what in the link, so get trouble
New 5.1 Factory Firmware Images are now available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
For now, the only XT1033 image you can use is: XT1033_FALCON_RETBR_DS_5.1_LPBS23.13-56-2_cid12 (you can change language to english during setup)
I would try flashing that firmware image via mfastboot. When the new XT1033 Asia firmware image becomes available, you can change to that if you want.
lost101 said:
New 5.1 Factory Firmware Images are now available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
For now, the only XT1033 image you can use is: XT1033_FALCON_RETBR_DS_5.1_LPBS23.13-56-2_cid12 (you can change language to english during setup)
I would try flashing that firmware image via mfastboot. When the new XT1033 Asia firmware image becomes available, you can change to that if you want.
Click to expand...
Click to collapse
thanks for your reply, i had tried the rom you provided to me, it still get the same result,all the steps are showing the result "failure".
Can you tell me that have big chance to make my phone return normal ?
If not, that's the time for me to give up.
tom0079 said:
thanks for your reply, i had tried the rom you provided to me, it still get the same result,all the steps are showing the result "failure".
Can you tell me that have big chance to make my phone return normal ?
If not, that's the time for me to give up.
Click to expand...
Click to collapse
Show me the log from command prompt when flashing the firmware image.
I have some issue with my Moto G XT1033
tom0079 said:
My phone just suddenly get bricked, I'm do not do anything before,not root ,not unlock bootloader ,not flash third-party roms.
I'm only update from ota (from 4.4 to 5.0 and 5.0 to 5.1), just the offical method to update.
now,i come here to find the way and get my phone back .
the situation now is unlocked bootloader (bootloader version :41.1A)
and try to flash stock rom XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
i just follow the guide in forum ,but get a trouble like that:
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash pa
rtition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.333s]
finished. total time: 0.375s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash mo
toboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.112s]
finished. total time: 1.232s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash lo
go logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.101s]
finished. total time: 0.173s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash bo
ot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.379s]
writing 'boot'...
OKAY [ 0.776s]
finished. total time: 1.166s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash re
covery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.392s]
writing 'recovery'...
OKAY [ 0.767s]
finished. total time: 1.171s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash sy
stem system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.318s]
writing 'system'...
OKAY [ 12.417s]
finished. total time: 20.747s
C:\Program Files (x86)\Android\android-sdk\platform-tools>mfastboot.exe flash sy
stem system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256949 KB)...
OKAY [ 8.258s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 29.086s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
I have try many times but still cant flash the sysem system.img_sparsechunk.1,
but i can flash the part system.img_sparsechunk.0
Does any one know what is my problem?(or my phone is already dead.)
PS: I'm sorry about that my english is not good,if anything wrong or can not understanding,please ask me.
thanks everyone.
Click to expand...
Click to collapse
Getting some "Preflash validiation error" on my Moto XT1033 while flashing gpt.bin and motoboot.img and I'm also unable to factory reset and wipe dalvik cache and also I'm unablle to flash TWRP or any other custom recovery and unable to re-lock my bootloader Showing some Partition error....Help me plz....
MY device is bricked